"white" gdm freeze on logout

Bug #48974 reported by Stéphane Marguet
12
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-restricted-modules-2.6.17 (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

Binary package hint: gdm

On startup gdm just work fine, but after login (and working) if I try to logout then gdm appear white and freeze the system (can't do ctrl+alt+1).
I've use the usual gdm theme and other customs.
Ubuntu Dapper i386.

Tags: kj-expired
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report. What do you mean by "other customs"? Do you see anything possibly related to the freeze in /var/log/syslog? Does .xsession-errors show something? Which video driver do you use?

Changed in gdm:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Stéphane Marguet (stemp) wrote :

Nothing in /var/log/syslog and .xsession-errors
I'm using fglrx drivers (7.0.0-8.25.18+2.6.15-1)

I've changed the /etc/gdm/gdm.conf-custom and added «AlwaysRestartServer=true» and it's now working.

Revision history for this message
Sebastien Bacher (seb128) wrote :

does it happen if you use ati instead of fglrx?

Revision history for this message
imclean (ipxdesign) wrote :

I have the same problem, I can "shutdown" but "logout" gives white screen with small grey box in position where logon name is normally entered in login manager.
What section do you put AlwaysRestartServer=true in?

Revision history for this message
john goodland (zaniah) wrote :

I get this too with fglrx ati driver have to swithch machine off and on again:
this is my .Xession-errors file if this helps:

Revision history for this message
john goodland (zaniah) wrote :

/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "john"
/etc/gdm/Xsession: Beginning session setup...
SESSION_MANAGER=local/himeji:/tmp/.ICE-unix/4486
esd: Esound sound daemon already running or stale UNIX socket
/tmp/.esd-1000/socket
This socket already exists indicating esd is already running.
Exiting...
Gnome-Message: gnome_execute_async_with_env_fds: returning -1

(gnome-panel:4916): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed

(gnome-panel:4916): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed

(gnome-panel:4916): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 32
/usr/lib/vmware/bin/vmplayer: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)

** (nautilus:4918): WARNING **: file already in tree (parent_ptr: (nil))!!!

** (nautilus:4918): WARNING **: file already in tree (parent_ptr: (nil))!!!

Revision history for this message
Stéphane Marguet (stemp) wrote :

@imclean : in [daemon]

Revision history for this message
Kamil Páral (kamil.paral) wrote :

Same problem here. Radeon 9800Pro with 7.0.0-8.25.18+2.6.15.11-3 fglrx driver. It happens only sometimes, most of logouts are fine. Some are not. Seems to me, that it could possible have some connection with amarok (KDE libs) running in gnome? Up to now I had never problem when not starting amarok or other KDE app. Is it possible?

After logout, there are white screen with gray box (login prompt), the computer is not freezed, just graphically distorted. You can type in login and password (it is not visible), and then happens freeze, or you can try ctrl+alt+f1 (freeze) or ctrl+alt+backspace (black and orange lines throughout whole screen and freeze).

Where exactly try to put "AlwaysRestartServer=true" line?

Revision history for this message
Stéphane Marguet (stemp) wrote :

In /etc/gdm/gdm.conf-custom :

[daemon]
AlwaysRestartServer=true
RemoteGreeter=/usr/lib/gdm/gdmgreeter
[security]
AllowRoot=true

Revision history for this message
Kamil Páral (kamil.paral) wrote :

The "AlwaysRestartServer=true" line seems to be helping. no crash since that time.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Marking as unconfirmed since it's not waiting for a reply, could somebody having the issue bringing it on bugzilla.gnome.org, upstream guys know that code much better and will probably have an idea on it

Changed in gdm:
importance: Untriaged → Low
status: Needs Info → Unconfirmed
Revision history for this message
Kamil Páral (kamil.paral) wrote :

after upgrade to Edgy (which erased AlwaysRestartServer=true line, so it is in the default state), I have experienced no crash, even since I tried few times to log in and out. seems that it is fixed, at least on my computer.

Revision history for this message
Matteo Dell'Amico (della) wrote :

I can confirm the bug happens to me too. I use fglrx on a Radeon 9000 on edgy.

Revision history for this message
Kamil Páral (kamil.paral) wrote :

Ok, I take back my statement, just happend. So it is not ok even in Edgy...

Revision history for this message
Sebastien Bacher (seb128) wrote :

does it happen if you use the "ati" driver instead of fglrx?

Revision history for this message
Stéphane Marguet (stemp) wrote :

I'm using the ati/radeon driver in Edgy (2.6.17-10-generic) and I have no problem.
It seems to be a fglrx bug.

Revision history for this message
Matteo Dell'Amico (della) wrote : Re: [Bug 48974] Re: "white" gdm freeze on logout

Il giorno ven, 24/11/2006 alle 12.30 +0000, Stemp ha scritto:
> I'm using the ati/radeon driver in Edgy (2.6.17-10-generic) and I have no problem.
> It seems to be a fglrx bug.

Yep, the problem started to happen when I switched to the fglrx driver.

Matteo

Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for the comment, reassigning to linux-restricted-modules-2.6.17 then

Changed in linux-restricted-modules-2.6.17:
assignee: desktop-bugs → nobody
Revision history for this message
Rodney Lane (roddles) wrote :

Hi

I have an ati Radeon 9600 Pro, and this problem occurs for me on both the ati driver and the fglrx driver every time i try to shut down or restart.

I am using Fesity.

If I use

sudo shutdown -P now or sudo shutdown -R now

from the command prompt the system will restart or shutdown properly. Its only when i use the GUI to shut down or restart that this occurs - but its happening every time.

I'll try the AlwaysRestartServer=true value to see if that helps.

Rod.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Closing an old bug, concerns a closed source driver which we can't fix, and possibly is fixed in a newer release.

Changed in linux-restricted-modules-2.6.17:
status: New → Invalid
Revision history for this message
Casey Watson (watsoncj) wrote :

I'm not sure that I agree with Timo's assessment.

I am experiencing this problem of a white screen after switching with the fast user switcher. I can type my password into the blank screen and the login is successful.

However, I am using the proprietary nvidia video driver that gets installed by the restricted device manager. So the issue seems to be independent of which driver is used.

Assuming the issue is fixed in the latest driver release doesn't seem to warrant closing this bug.

Revision history for this message
Jamie Arseneault (spoom) wrote :

I'm experiencing this bug on Hardy, and I'm using the nVidia driver. So it's not specific to the ATI driver, and I doubt it is specific to both.

AlwaysRestartServer=true fixes it for me as well, though that's not ideal as it kicks back to the console before going back to the greeter.

GeForce 4 MX here, with desktop effects (Compiz Fusion) enabled and a bunch of extras in CCSM. As mentioned by someone else, the greeter seems to be "available" in that one can move the mouse over to where the username / password box should be, type the relevant info, and press enter and it will login to that user, but it's not getting drawn to the screen. Could this have to do with Compiz? Do others experiencing this bug have desktop effects enabled as well?

Revision history for this message
Jamie Arseneault (spoom) wrote :

This bug also seems to happen upon resuming from DPMS monitor shutoff. Reopening as it doesn't seem to be a result of the fglrx driver (please accept my apologies if this assessment is incorrect).

Changed in linux-restricted-modules-2.6.17:
status: Invalid → New
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Edgy Eft 6.10 has reached its end of life several months ago.
As a result, we are closing the linux-restricted-modules-2.6.17 task.
It would be helpful if you could test the new Jaunty Jackalope 9.04 release
and confirm if this issue remains - http://www.ubuntu.com/getubuntu/releasenotes/904overview.
If the issue still exists with the Jaunty release, please update this report by changing
the Status of the "linux (Ubuntu)" task from "Incomplete" to "New". Thanks in advance!

Changed in linux-restricted-modules-2.6.17 (Ubuntu):
status: New → Won't Fix
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
kernel-janitor (kernel-janitor) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.