Red Hat Bugzilla – Bug 154286
greeter program crashes sometimes when restarting
Last modified: 2009-01-09 01:52:22 EST
Description of problem:
When trying to restart X at the GDM login with CTRL-ALT-BACKSPACE I sometime get:
"The greeter program appears to be crashing.
I will attempt to use a different one."
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Get to the login screen
correctly restart X all the times
I have the same problem except it's fully consistent here.
Themed greeter always crashes (on boot, logout, etc) then I get the restart
popup, then the non-svg greeter is displayed
Can you attach your /etc/X11/gdm.conf file please? Also, would you mind setting
enable=true in the [debug] section of the conf file, restarting and then
attaching your /var/log/messages file?
I have the same problem.
I will attach a /var/log/messages file with debug enabled.
Created attachment 115652 [details]
Here is the /var/log/messages file with the debug infos.
Created attachment 115705 [details]
cat /var/log/messages | grep gdm
This attachment is smaller and only includes gdm messages.
I also tried with early-login and it keeps crashing.
Created attachment 117150 [details]
grep gdm /var/log/messages, gdm debug enabled
I have this problem too.
Intermittent: perhaps 5-10% of restarts overall. Since doing a yum update
yesterday morning, the greeter has crashed on 2/2 restarts.
on my new box 64bit fc4 x86_64 this does not happen..
old box 32bit fc4 i386 still buggy (both have same config )
My instance of the problem has become much worse since my yum update on 25th
July. The themed Fedora login screen now crashes almost every time I boot or
logout. One of the following then happens:
(1) I get the dialog saying "The greeter program appears to be crashing. I will
attempt to use a different one." Followed by the grey login box.
(2) The themed login screen appears on a second attempt.
(3) Two failures occur and I am left with a blank screen with an X cursor.
I suspect that a more fundamental problem is at work here, as I am also unable
to switch from a virtual console back to X with Ctrl-Atl-F7: instead of
returning me to my desktop, this kills my X session and returns me either to (2)
Please advise if I should file this as a separate bug report.
I get the same behaviour with various versions of xorg-x11.
Just a thought - is there any code in gdm that relies on volatile casts, that
may therefore fall victim to the gcc 4.0.0 optimisation bug, as in bug #161242 ?
For now, let's just keep it on one bug. When I fix this bug, we'll see if the
problem goes away for you, and if it doesn't we can do another bug report if
I tried building and installing my own gdm rpm from gdm-22.214.171.124-16.src.rpm using
gcc-4.0.1-4.fc4, in case this was a gcc 4.0.0 optimisation issue. This did not
solve the problem, however.
In case it is relevant, I am currently using Xavier Bachelot's Unichrome-enabled
xorg-x11 srpm, which again I built with gcc-4.0.1-4 .
fc5 test3 (gdm-126.96.36.199-1) has still this problem. The greeter crashes for me
after a few CTRL-ALT-BACKSPACE.
Still occurs in fc7 test 4; after a few CTRL-ALT-BACKSPACE in a row I get this
"The greeter application appears to be crashing. Attempting to use a different
Seems to be harmless (once you click OK, you get the login screen), but still...
Still occurs in Fedora 8 (gdm-2.20.2-2.fc8).
Pressing ok just pops up the same dialog over and over again. To actually get
around it, you have to wait for ~1mn and then click ok.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. 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 '8'.
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 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.
Thank you for reporting this bug and we are sorry it could not be fixed.