It happens using the CD reliably. (I suspect the same thing has happened after install, because I have been put into the low-graphics dialog since installing. But I don't have a way to reproducibly get to the low graphic mode configuration tool after install.)
I've just finished verifying the exact same issue using the amd64 desktop CDs for Gutsy, Hardy Alpha3, and Hardy Alpha4 and captured /var/log onto a thumb drive for each of them. In each case: I took the default boot path, "Start or install ubuntu". No splash was displayed. X started in low resolution presenting the "Ubuntu is running in low-graphics mode". I configured to use the nv driver and the 1440x900 display. I tested the configuration successfully I then clicked the [OK] button on the config dialog. The result was to drop me into a VT with the boot progress text displayed. The last boot progress message displayed was: --------------------------------------------------- * Running local boot scripts (/etc/rc.local) [OK] --------------------------------------------------- At this point, the boot has aborted and I switched to VT1 and tar'ed /var/log onto a thumb drive. The last entries in /var/log/daemon.log from the Gutsy boot are: --------------------------------------------------- Feb 22 17:50:10 ubuntu gdm[8683]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 22 17:50:14 ubuntu gdm[8829]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 22 17:50:18 ubuntu gdm[8843]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 22 17:50:18 ubuntu gdm[8682]: CRITICAL: gdm_config_value_get_bool: assertion `value->type == GDM_CONFIG_VALUE_BOOL' failed Feb 22 17:53:08 ubuntu gdm[8979]: WARNING: GDM already running. Aborting! --------------------------------------------------- The last entries in from the Hardy Alpha4 boot are: --------------------------------------------------- Feb 22 18:32:31 ubuntu gdm[8563]: CRITICAL: gdm_config_value_get_bool: assertion `value->type == GDM_CONFIG_VALUE_BOOL' failed Feb 22 18:33:38 ubuntu gdm[8846]: WARNING: GDM already running. Aborting! --------------------------------------------------- The end of /var/log/gdm/:0.log from the Hardy Alpha4 boot is: --------------------------------------------------- configure * Stopping GNOME Display Manager... [80G [74G[ OK ] * Starting GNOME Display Manager... [80G [74G[[31mfail[39;49m] waiting for X server to shut down FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing. --------------------------------------------------- It turns out that "sudo /etc/init.d/gdm restart" is sufficient to fix things at this point, the desktop comes up with the driver and resolution I configured. I can supply logs, or we can wait and see what Hardy Alpha5 produces. On Fri, Feb 22, 2008 at 11:14 AM, Sebastien Bacher <[EMAIL PROTECTED]> wrote: > The ticket has been closed because your description is rather confusing > and seems to describe different issues you had and workarounds rather a > specific bug on the software. The revelant part there is that gdm is not > restarted after using the xorg low graphic mode configuration tool > right? Does that happen using the CD only or only after installation? > > -- > livecd gdm failure after low-graphics dialog > https://bugs.launchpad.net/bugs/194187 > You received this bug notification because you are a direct subscriber > of the bug. > -- livecd gdm failure after low-graphics dialog https://bugs.launchpad.net/bugs/194187 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
