Bug 922047

Summary: GDM and Gnome just don't start without any helpful error message
Product: [Fedora] Fedora Reporter: Peter Ganzhorn <peter.ganzhorn>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: projects.rg, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 19:59:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Peter Ganzhorn 2013-03-15 13:06:08 UTC
Description of problem: GDM / Gnome fail to start


Version-Release number of selected component (if applicable):


How reproducible: Everytime


Steps to Reproduce:
1. service gdm start
  
Actual results: GDM or Gnome fail to start.


Expected results: GDM and Gnome start.


I got the following, very strange problem with both GDM and Gnome: When trying to start gdm, it will show nothing but a spinning cursor icon on black background for about 30 seconds and then finish with the message "Oh no something has gone wrong, please contact your system administrator".
So I installed lxdm which started just fine. Trying to log in and starting gnome, the same "Oh no ..."-screen shows and that's it.
The X log shows no errors, the only related errors I could find were in

/var/log/gdm/\:0-greeter.log

      JS LOG: GNOME Shell started at Fri Mar 15 2013 13:46:36 GMT+0100 (CET)
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
Window manager warning: Log level 8: g_source_remove: assertion `tag > 0' failed
gnome-session[22667]: WARNING: Detected that screensaver has left the bus
gnome-session[22667]: CRITICAL: gsm_manager_set_phase: assertion `GSM_IS_MANAGER (manager)' failed
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

(gnome-settings-daemon:22689): GLib-GIO-WARNING **: Error releasing name org.gnome.SettingsDaemon: The connection is closed

(gnome-settings-daemon:22689): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:22689): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:22689): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:22689): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:22689): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:22689): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:22689): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:22689): GLib-GIO-WARNING **: Error releasing name org.freedesktop.ScreenSaver: The connection is closed


I just installed F18 yesterday and for the first boot GDM and Gnome worked just fine. I did a "yum update", installed a few packages I needed, removed a few packages (which I tried to re-install, but that did not resolve the situation).
For now I am using lxdm + fluxbox which are working just fine. Gnome-applications are running within fluxbox without any problems.

Please tell me in what logfiles I can find some *USEFUL* information to pinpoint the problem - "Oh no, something has gone wrong" is one of the most bullshitty and dumb error messages I ever encountered. I knew something went wrong without actually reading that great informative message.

Comment 1 Raphael Groner 2013-05-07 07:00:09 UTC
I see two bugs here.
1) Broken log messages
2) Gnome crash

Comment 2 Fedora End Of Life 2013-12-21 12:10:36 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2014-02-05 19:59:35 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.