gdm fails to start if it finds (EE) messages in Xorg.0.log

[Ákos Maróy]

Binary package hint: gdm

gdm fails to start if it finds (EE) messages in Xorg.0.log, even when this actually does not prevent X from starting - as it can be started by issuing startx just fine.

for example in my case, X logs errors like:

(**) "SynPS/2 Synaptics TouchPad": Device: "/dev/input/mouse1"
(EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device
(II) UnloadModule: "evdev"
(EE) PreInit returned NULL for ""SynPS/2 Synaptics TouchPad""
(II) config/udev: Adding input device "Macintosh mouse button emulation"
(/dev/input/event3)
(**) "Macintosh mouse button emulation": Device: "/dev/input/mouse0"
(EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device
(II) UnloadModule: "evdev"
(EE) PreInit returned NULL for ""Macintosh mouse button emulation""

...

(WW) RADEON(0): Direct rendering disabled
(EE) RADEON(0): Acceleration initialization failed
(II) RADEON(0): Acceleration disabled

but then starts just fine when issuing startx. but gdm seems to watch out for these errors, and instead of displaying the login screen, it displays a minimal X window with the above errors.

gdm should just show the login screen if X starts fine, even if it logs errors in the log.

[Sebastien Bacher (seb128)]

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

[Pedro Villavicencio (pedro)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.