black screen after a few user switches

[Guillaume Giroux]

Up-to-date Lucid with radeon driver. After switching user a few times (usually between 3 and 5 times), the screen goes black with only the mouse cursor visible after entering the user's password. VTs are also completely black. Restarting gdm fixes the issue, and nothing odd appears in XOrg.0.log when the black screen occurs. It also happens with KMS disabled. It also happens with compiz disabled for all users.

WORKAROUND: Uninstall gnome-screensaver (see bug #555870 - something gnome-screensaver does is triggering this X bug).
WORKAROUND: Blindfold: Unlock session by typing password, then press <Alt>-<F2> (call "Run ..." dialog), then type "xgamma -gamma 1.0" and hit <Enter>
WORKAROUND: Update gnome-screensaver to 2.30.0-0ubuntu2 or higher (yet in proposed repo). Those versions are compiled with disabled "fade on lock".

ProblemType: Bug
Architecture: i386
Date: Wed Mar 24 21:43:21 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP dx5150 MT(PV753AA)
Package: xorg 1:7.5+3ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=2f620498-4095-49f2-8ea6-7355f3d696ec ro
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SourcePackage: xorg
Uname: Linux 2.6.32-17-generic i686
dmi.bios.date: 03/08/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 1.19
dmi.board.name: 09AC
dmi.board.vendor: MSI
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr1.19:bd03/08/2007:svnHewlett-Packard:pnHPdx5150MT(PV753AA):pvr:rvnMSI:rn09AC:rvr:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HP dx5150 MT(PV753AA)
dmi.sys.vendor: Hewlett-Packard
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-17-generic

[lspci]
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS480 [Radeon Xpress 200G Series] [1002:5954]
     Subsystem: Hewlett-Packard Company Device [103c:3009]

[brassman5 (chiporo)]

I have experienced the same thing on a fully updated Lucid with an ATI Radeon Xpress 200m video card. I can switch from the primary user to a secondary user just fine, however, attempting to return leaves me with a black screen and only a mouse.

[brassman5 (chiporo)]

Test and had the same issue on my desktop machine as well. Also an ATI video adapter. A Radeon 9600.

[Bryce Harrington (bryce)]

radeontool can be used to assist in debugging issues where the screen blanks like this. After installing it, you run it like this:

    radeontool regmatch '*' > regdump_good.txt

    radeontool regmatch '*' > regdump_broke.txt

Run it two times. Once when you have a good, working screen (for any driver including -vesa), and once in the broken case (either from the tty console or logged into the sick box remotely).

[brassman5 (chiporo)]

Bryce,

On running radeontool, the only output generated is "mapping ctrl region". This is on both machines whether the screen is blank or not. I would be happy to provide any other information that could be helpful.

[Bryce Harrington (bryce)]

Did you run the commands exactly as shown? Look to see if it generated the regdump_*.txt files. Attach them if so.

[brassman5 (chiporo)]

The commands were entered exactly as shown and generated only "mapping ctrl region" to the screen, and created empty regdump_*.txt files.

[Bryce Harrington (bryce)]

Did you run the commands as sudo?

[Bryce Harrington (bryce)]

Forwarding this bug from Ubuntu reporter Guillaume Giroux:
http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/546578

[Problem]
Screen goes black after switching from primary to secondary user and back several times. Occurs regardless of whether KMS or compiz are enabled or disabled.

[Original Description]
Up-to-date Lucid with radeon driver. After switching user a few times (usually between 3 and 5 times), the screen goes black with only the mouse cursor visible after entering the user's password. VTs are also completely black. Restarting gdm fixes the issue, and nothing odd appears in XOrg.0.log when the black screen occurs.

- It also happens with KMS disabled.
- It also happens with compiz disabled for all users.

Another user adds that they see the same issue on an Xpress 200m, and finds the black screen always happens on the return to the primary user, never in the primary->secondary user case.

Architecture: i386
Date: Wed Mar 24 21:43:21 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP dx5150 MT(PV753AA)
Package: xorg 1:7.5+3ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=2f620498-4095-49f2-8ea6-7355f3d696ec ro
ProcEnviron:
 LANG=en_US.utf8
 ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SourcePackage: xorg
Uname: Linux 2.6.32-17-generic i686
dmi.bios.date: 03/08/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 1.19
dmi.board.name: 09AC
dmi.board.vendor: MSI
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr1.19:bd03/08/2007:svnHewlett-Packard:pnHPdx5150MT(PV753AA):pvr:rvnMSI:rn09AC:rvr:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HP dx5150 MT(PV753AA)
dmi.sys.vendor: Hewlett-Packard
system:
  codename: lucid
 architecture: i686
 kernel: 2.6.32-17-generic

[Bryce Harrington (bryce)]

00:00.0 Host bridge [0600]: ATI Technologies Inc RS480 Host Bridge [1002:5950] (rev 01)
 Subsystem: Hewlett-Packard Company Device [103c:3009]
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS480 [Radeon Xpress 200G Series] [1002:5954]
 Subsystem: Hewlett-Packard Company Device [103c:3009]

[Bryce Harrington (bryce)]

Created an attachment (id=34561)
XorgLogOld.txt

[Bryce Harrington (bryce)]

Created an attachment (id=34562)
XorgLog.txt

[Bryce Harrington (bryce)]

Created an attachment (id=34563)
CurrentDmesg.txt

[Bryce Harrington (bryce)]

Created an attachment (id=34564)
BootDmesg.txt

[Bryce Harrington (bryce)]

Created an attachment (id=34565)
regdump_good.txt

[Bryce Harrington (bryce)]

Created an attachment (id=34566)
regdump_bad.txt

[Bryce Harrington (bryce)]

Created an attachment (id=34567)
regdump.diff

[agd5f (agd5f)]

This kms drm patch may help for the kms case:
http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=d805f50aa1d9eef63fec356b2be557e2da3cd643

[Bryce Harrington (bryce)]

Guillaume - I've forwarded this bug upstream to https://bugs.freedesktop.org/show_bug.cgi?id=27382 - please subscribe yourself to this bug, in case they need further information or wish you to test something. Thanks ahead of time!

[Guillaume Giroux (gug-microflex)]

Bryce - thanks for reporting upstream, I'm now subscribed to said bug. Please let me know if there's anything else I can do to help diagnose - willing to install ppa stuff or play around with gdb on X|gdm if needed.

[Michel Dänzer (michel-daenzer)]

This might be related to other reports about the CLUT not getting properly restored after VT switching away from the X server while the screensaver is doing its fade-out effect. Does something like

xgamma -gamma 1.0

restore the proper display?

[Guillaume Giroux (gug-microflex)]

(In reply to comment #10)
> Does something like
>
> xgamma -gamma 1.0
>
> restore the proper display?

Yes it does.

[Rafael Monica (monraaf-deactivatedaccount)]

(In reply to comment #10)
> This might be related to other reports about the CLUT not getting properly
> restored after VT switching away from the X server while the screensaver is
> doing its fade-out effect. Does something like
>
> xgamma -gamma 1.0
>
> restore the proper display?
>

The binary fglrx driver is also affected by this bug. And also here xgamma -gamma 1.0 saves the day. So does this mean that the problem lies with the X server? And is there anyway distro's can workaround this bug till it's get fixed?

[Michel Dänzer (michel-daenzer)]

(In reply to comment #12)
> The binary fglrx driver is also affected by this bug. And also here xgamma
> -gamma 1.0 saves the day. So does this mean that the problem lies with the X
> server?

Yes, there have also been reports with the intel driver. Reassigning, this should probably also block the xserver 1.8 blocker bug, if there was one...

[Guillaume Giroux (gug-microflex)]

workaround from upstream bug: running "xgamma -gamma 1.0" fixes the display.

so to ease the pain, go to System->Preferences->Keyboard shortcuts, and add a custom entry that executes this command for each user. Ctrl+Alt+Backspace is a good one for the nostalgic.

[Chris Coulson (chrisccoulson)]

The symptoms here look like bug 555870. Would people experiencing this please test the updated gnome-screensaver package here: http://people.canonical.com/~chrisccoulson/lp555870/

Note that you will need to restart after installing this package

Thanks

[DevenPhillips (deven-phillips)]

That appears to have resolved the issue for me in my initial testing.
I will continue to monitor and replay with any changes to that
assesment.

Thanks,

Deven

On Tue, Apr 6, 2010 at 7:15 AM, Chris Coulson
<email address hidden> wrote:
> The symptoms here look like bug 555870. Would people experiencing this
> please test the updated gnome-screensaver package here:
> http://people.canonical.com/~chrisccoulson/lp555870/
>
> Note that you will need to restart after installing this package
>
> Thanks
>
> --
> [RS480] black screen after a few user switches
> https://bugs.launchpad.net/bugs/546578
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Chris Coulson (chrisccoulson)]

Deven - ok, thanks. That sounds promising anyway, so I will get gnome-screensaver uploaded this afternoon

[DevenPhillips (deven-phillips)]

Problem is not resolved. The problem came back after playing music inside of
one of the sessions.

Deven

On Apr 6, 2010 8:46 AM, "Chris Coulson" <email address hidden> wrote:

Deven - ok, thanks. That sounds promising anyway, so I will get gnome-
screensaver uploaded this afternoon

--

[RS480] black screen after a few user switches
https://bugs.launchpad.net/bugs/546578
You received t...

[Guillaume Giroux (gug-microflex)]

@Chris Coulson: your gnome-screensaver package didn't resolve the issue for me either.

[Bryce Harrington (bryce)]

Upstream suggests this kernel patch may help the RS480 for when KMS is active:
http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=patch;h=d805f50aa1d9eef63fec356b2be557e2da3cd643

[Bryce Harrington (bryce)]

Upstream reports workaround: xgamma -gamma 1.0

Waiting on patch or way to force the above to occur automatically, but seems this is a bug in xserver, so reassigning there for now.

I've added a release nomination since this feels to me like a type of bug which could be acceptable for an SRU. However we need to get an upstream-approved patch first.

[Bryce Harrington (bryce)]

A workaround we could apply at the distro level would be very helpful.

[Ernst Persson (ernstp)]

This isn't RS480 specific is it? Someone reported on an 9600 and it happens on my 4770 also.

[DevenPhillips (deven-phillips)]

And on my Radeon HD 3200

Deven

2010/4/16 Ernst Sjöstrand <email address hidden>:
> This isn't RS480 specific is it? Someone reported on an 9600 and it
> happens on my 4770 also.
>
> --
> [RS480] black screen after a few user switches
> https://bugs.launchpad.net/bugs/546578
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Justin Forest (umonkey)]

I have this problem with Intel 82G33/G31 (xgamma helps), so I'm not
sure this is related to ATI.

[Chris (chris3)]

I'm having the same issues with an Intel Mobile GM965/GL960.

Chris

[Alwin Garside (yogarine)]

*** Bug 27505 has been marked as a duplicate of this bug. ***

[Bryce Harrington (bryce)]

Please no more me-too's.

Note that I moved the bug from -ati to xorg-server, so yeah I know it's probably not a hw-specific bug. My comment about RS480 is just repeating what upstream said.

[Bryce Harrington (bryce)]

Given the nature of this bug, it looks eligible for an SRU fix if we can find one. The bug does not prevent installation or booting into X, it shows up during regular usage.

[Bryce Harrington (bryce)]

Chris Coulson suggests this sounds very similar to a gnome-screensaver issue (bug #555870) he saw reported, where gnome-screensaver does not reliably reset the gamma back to the correct value after its faded.

To verify if this bug is the same as that bug, please collect an xtrace of gnome-screensaver while reproducing the behavior.

[DevenPhillips (deven-phillips)]

Bryce,

    Do you have instructions on how to do that?

Deven

On Fri, Apr 16, 2010 at 1:47 PM, Bryce Harrington
<email address hidden> wrote:
> Chris Coulson suggests this sounds very similar to a gnome-screensaver
> issue (bug #555870) he saw reported, where gnome-screensaver does not
> reliably reset the gamma back to the correct value after its faded.
>
> To verify if this bug is the same as that bug, please collect an xtrace
> of gnome-screensaver while reproducing the behavior.
>
> --
> [RS480] black screen after a few user switches
> https://bugs.launchpad.net/bugs/546578
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Chris Coulson (chrisccoulson)]

Deven,

To get an xtrace log, please run the following in one terminal:

xtrace -d :0 -D :9 -k 2>&1 | tee ~/xtrace.log

In another please run:
killall gnome-screensaver
DISPLAY=:9.0 gnome-screensaver

Replace ":0" with the actual number of your X display, although :0 will be correct if you are the first user to log in to the machine. If you're unsure, please run "env | grep DISPLAY | cut -d = -f 2 | cut -d . -f 1"

Once you have this all running, please perform the steps which recreate the issue. Once you have recreated it, please attach your xtrace log to this bug report (note that xtrace is likely to produce a huge amount of information)

***IMPORTANT***
The xtrace log will show any kepresses received by gnome-screensaver. If you unlock your screen with your password whilst running gnome-screensaver with xtrace, then it will be possible to extract your password from the log. In this case, please compress the log to a tar.gz and e-mail it directly to me (<email address hidden>), and I will cut out the relevant parts to attach to the bug report.

[Pauli (paniemin)]

Problem seems to be to be commented out option xf86HandleColormaps.

Bool drmmode_setup_colormap(ScreenPtr pScreen, ScrnInfoPtr pScrn)
{
    xf86DrvMsgVerb(pScrn->scrnIndex, X_INFO, RADEON_LOGLEVEL_DEBUG,
                  "Initializing kms color map\n");
    if (!miCreateDefColormap(pScreen))
        return FALSE;
    /* all radeons support 10 bit CLUTs */
    if (!xf86HandleColormaps(pScreen, 256, 10,
                             drmmode_load_palette, NULL,
                             CMAP_PALETTED_TRUECOLOR
#if 0 /* This option messes up text mode! (<email address hidden>) */
                             | CMAP_LOAD_EVEN_IF_OFFSCREEN
#endif
                             | CMAP_RELOAD_ON_MODE_SWITCH))
         return FALSE;
    return TRUE;
}

If I enable the disabled option lut is restored correctly when
switching back from VT.

But there is still problem that lut is not restored when switching
away from xserver. So this is not correct fix to the problem.

[Michel Dänzer (michel-daenzer)]

(In reply to comment #14)
> A workaround we could apply at the distro level would be very helpful.

I doubt finding a workaround in the server would be significantly easier than fixing the problem in the first place.

[Jeremy Foshee (jeremyfoshee)]

Hi Guillaume,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

[Guillaume Giroux (gug-microflex)]

@automated Jeremy:

I just tried with linux-image-2.6.34-020634rc5-generic and the black screen still occurs, and xgamma still saves the day.

[Guillaume Giroux (gug-microflex)]

@Chris, Bryce

interestingly, after purging the gnome-screensaver package, and rebooting on linux-image-2.6.34-020634rc5-generic, the problem goes away entirely.

However, when using the lucid stock kernel with gnome-screensaver removed, I get a garbled/corrupted screen after the first attempt to switch user. And this time it is fixed by a switch to/from a VT.

Summary: this issue is just getting murkier. But Chris might be on to something with the gnome-screensaver/ bug #555870 linkage.

[Alejandro E Moreno Ruiz (alexmoreno)]

@Chris, I emailed you an xtrace log. Thanks.

[Bryce Harrington (bryce)]

On Thu, Apr 22, 2010 at 03:44:08AM -0000, Guillaume Giroux wrote:
> Summary: this issue is just getting murkier. But Chris might be on to
> something with the gnome-screensaver/ bug #555870 linkage.

Yeah, it's sounding more like gnome-screensaver is the path to study
here.

[Michel Dänzer (michel-daenzer)]

*** Bug 27821 has been marked as a duplicate of this bug. ***

[Antonio Rodriguez (taserian)]

One workaround is to use the User Switcher panel applet, instead of the Indicator Applet Session. For some reason, the Indicator Applet Session dims the display before switching; when you come back to that user's session, you either get a dimmed screen (which you can fix with "xgamma -gamma 1.0") or a completely black screen, which I've have to reboot from.

The User Switcher returns you to the main login screen, instead of the windowed user switch from Indicator Applet Session.

[Bryce Harrington (bryce)]

Another workaround mentioned on a dupe of the upstream bug:

I was able to further work around this issue by putting a script
into /etc/pm/sleep.d which simply "sleep"s for 3 seconds on
suspend and hibernate events. This lets gnome-screensaver and
xscreensaver to fade out fully before the system actually suspends
to disk or RAM.

[Toni Förster (stonerl)]

I think this is bug has something to do with the gnome-screensaver package. I have exactly the same problem here. I first installed the gnome-screensaver package mentioned above, but this didn't solve the problem. So I removed the package and now i can switch between users as many times as I want and it works perfectly.

[Hansen (moteprime)]

I can also confirm that after removing the gnome screensaver i can now switch users again.
running: lucid lynx RC 2.6.32-21-generic

[Giovanni Battista Salvietti (giovannibattista-salvietti)]

Hi, some useful hints: on my system, with intel g3100, the screen goes totaly black if I have firefox open, otherwise it dims and can be restored with the xgamma trick.
Investigating if other apps makes the system unrecoverable....

P.S.
removing gnome.screensaver resolves the problem.

[DjznBR (djzn-br)]

My hardware: ATI HD 3200. I can confirm this bug, and I can confirm the workaround. Switching users from the User Switcher panel applet DOES WORK instead of using the Indicator panel applet.

What a damn annoying bug !

It cost me a few reboots until I figured it out.

[Leo Milano (lmilano)]

With my hardware (ATI HD 3500), I get the black screen in Kubuntu with the open source stack (radeon, etc). If I enable fglrx in the Hardware Drivers section, the issue is gone. The latest packages from the xorg-edgers ppa also produce the crash.

[Luca Borrione (luca.borrione)]

Same problem here with a fresh installation of Lucid Lynx 10.04 final release:
Motherboard -> Intel D850GB (Garibaldi)
cpu -> Intel Pentium 4 - 2.0 GHz
graphic card -> ATI Radeon 9250 128 MB DDR

problem:
1. logged in as admin user
2. try to switch to any other user by pressing "switch user" under the menu of the Indicator Applet Session
3. get a blank screen with no pointer. alt+f7 no effect, ctrl+alt+f7 no effect, ctrl+alt+f1/f2 etc sometimes got a console mode sometimes not.

It seems a problem of memory: if I switch without any app opened everything can go right, but if I just open some firefox windows and an openoffice document and then try to switch sure I get the blank screen.

I tried to use the User Switcher panel applet, instead of the Indicator Applet Session as suggested and it seems to go well with desktop effects turned off. However even in this case if I close all the user sessions through the User Switcher panel applet the gdm panel is no more shown and can only press ctrl+f1 login and write sudo /etc/init.d/gdm restart to get it.

Do you think this could be another bug to report?

[Leo Milano (lmilano)]

Here is something encouraging.

This morning (May 9) I tried the xorg-edgers ppa again, and now the crash on logout is gone. No workarounds, no mess. This is, again, in Kubuntu/KDM.

If anyone wants to try, here are the instructions. From the command line:

To install:
"sudo add-apt-repository ppa:xorg-edgers/ppa"
Then refresh your packages and upgrade.

To uninstall:
"sudo ppa-purge xorg-edgers"

For more, please see here:
https://launchpad.net/~xorg-edgers/+archive/ppa

I had tried this before with no luck. If we can confirm that this has been fixed upstream, then there is hope we can get a fix backported.

[jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount)]

Third confirmation that removing gnome-screensaver and rebooting fixes the issue entirely.

[Martin Pitt (pitti)]

@Chris Coulson:

> we need some way for gnome-screensaver to signal that it has finished fading, or revert the fading mechanism to what we had in karmic, which didn't seem to have this problem
> what do you think is more appropriate for a SRU?

I'm afraid I can't say without more information. It seems that this is fundamentally a race of gnome-power-manager calling g-screensaver to fade, but not waiting for it to finish, and then calling pm-utils too early? Why do we have a VT change here at all, due to pm-utils having a quirk for this platform?

For an SRU, I recommend a small sleep() hack. We (should) know how long the fading takes, so we can sleep long enough for g-s to finish fading?

[David Tombs (dgtombs)]

Changed title to avoid confusing newcomers to this bug (like me).

[Anton Gladky (gladky-anton)]

>>"sudo add-apt-repository ppa:xorg-edgers/ppa"

Does not fix the problem for me.

[Yuioup (mghaoui)]

Hey all,

I'm having this problem on my EEE PC.

I want to add that I have 2 users on my system and they both have the option "Password: not asked at login".

Steps to reproduce:

1. Log in as user A
2. Quickly switch to user B.
3. Switch back to user A.

I get a blank screen. CTRL+ALT+F1 does not do a think. I need to hard reset the netbook.

[loe (thabastlwastl)]

I am not sure if I have the same problem but the result looks similar.
I just reinstalled lucid on my z61m with an ati x1400 build in.

After a couple of hours the screen gets blank and I have to do a hard reset. This happened to me now two times while I was surfing.

[David Tombs (dgtombs)]

Ioe, sounds like a different issue. Please report a new bug with "ubuntu-bug xorg". Thanks!

[Chris Coulson (chrisccoulson)]

I suspect that most people here are experiencing the problem described in https://bugs.edge.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/555870/comments/11. However, I'd like to keep bug 555870 separate, as that is really reporting a separate issue, and I should have put that comment in this bug report really.

For now, I'll probably disable fade-on-locking in gnome-screensaveer, but keep the fade-on-idle effect.

[Chris Coulson (chrisccoulson)]

Incidentally, I can demonstrate this quite reliably on my Intel box by doing "xgamma -gamma 0.5" from within my X session whilst it is active, then switching to a VT and doing "DISPLAY=:0.0 xgamma -gamma 1.0". On karmic, the gamma goes back to the correct value in my X session on the inactive VT, but it stays at 0.5 on lucid despite the X calls completing successfully (note, this tests the XF86VM gamma fade only).

Sarvatt said on IRC that ATI and nouveau users are experiencing the same behaviour too, it isn't limited to Ubuntu, and disabling fading fixes it. My computer with the binary nvidia driver is not affected by this though

[Takkat (takkat-nebuk)]

@Chris Coulson:

I can confirm here, that the machine with nvidia binary driver is not affected, but machines on ATI and Intel (GMA 950) are.

[Chris Coulson (chrisccoulson)]

I've just uploaded gnome-screensaver to lucid-proposed with fade-on-lock disabled

[loe (thabastlwastl)]

@David: Since I removed the gnome-screen saver it did not happen again.
So it seemed to help. What I am now experiencing is a screen going blank in idle although it is disabled in the propertys (screen comes back by mouse movement or keystroke, I think this might be related to the fact that I removed the gnome-screensaver).
And another really funny thing: my mouse pointer is gone after suspend. I can move the mouse and click on things - I just cant the the pointer. oO

I have to admit most things worked totaly fine with lucid - until i put in my ssd and did a reinstall. Since then I have the weirdest issues :-?

[Giovanni Battista Salvietti (giovannibattista-salvietti)]

@Chris

I don't see gnome-screensaver in lucid-proposed repo. Some problems?

[Colin Watson (cjwatson)]

Accepted gnome-screensaver into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Wolfgang Kufner (wolfgangkufner)]

gnome-screensaver 2.30.0-0ubuntu2 looks good here (Acer Extensa 5630Z with intel 8086:2a42] (rev 07)) . No incidents in 25+ user switches.

Nice work. Thanks :-)

[Takkat (takkat-nebuk)]

2.30.0-0ubuntu2 works fine here on ATI (open radeon driver) and Intel (GMA950)

Many thanks for this fast and preciuos work.

[emigrant (fromwindowstolinux)]

Am I doing this correct?
i don't get any changes... :(
I enabled the repo using this guide:
https://wiki.ubuntu.com/Testing/EnableProposed

$ sudo aptitude install gnome-screensaver /lucid-proposedReading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Couldn't find package "", and more than 40
packages contain "" in their name.
Couldn't find package "", and more than 40
packages contain "" in their name.
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 85 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done

[emigrant (fromwindowstolinux)]

I uninstalled the default gnome screensaver and installed back.
and still i cant switch back to the first user from the second user.
the black screen thing still exists :(

[Anton Gladky (gladky-anton)]

I have just updated all packages from proposed-repo, and the problem is gone!

I switched several times between users with no problems.

Thank you!

PS I have Dell Mini 10v

[emigrant (fromwindowstolinux)]

Please some one tell me what to do to solve this problem step by step.
thanks

[Anton Gladky (gladky-anton)]

https://wiki.ubuntu.com/Testing/EnableProposed

then update your packages and (maybe) reboot.

[Wolfgang Kufner (wolfgangkufner)]

@emigrant

Make sure you have the the new package installed by typing
sudo apt-cache policy gnome-screensaver
in a terminal window.
It should say:
gnome-screensaver:
  Installed: 2.30.0-0ubuntu2
  Candidate: 2.30.0-0ubuntu2

[emigrant (fromwindowstolinux)]

Anton,
Is your reply to me?
thats what i did and i still have the prob :(

[David Clayton (dcstar)]

After reinstalling this new version of gnome-screensaver, I notice that when I switch users the unlock screen for the original user appears and is then quickly replaced by the unlock screen for the switched user (as anticipated) - so it seems this new update successfully refreshes the screen.

[emigrant (fromwindowstolinux)]

@Wolfgang Kufner,
I appreciated your reply.
this is what i get to your code (I removed the screensaver package again):

gnome-screensaver:
  Installed: (none)
  Candidate: 2.30.0-0ubuntu1
  Version table:
     2.30.0-0ubuntu2 0
        400 http://archive.ubuntu.com/ubuntu/ lucid-proposed/main Packages
        100 /var/lib/dpkg/status
     2.30.0-0ubuntu1 0
        500 http://lk.archive.ubuntu.com/ubuntu/ lucid/main Packages

[emigrant (fromwindowstolinux)]

Hi Wolfgang Kufner,
I appreciate very much you replying to me.

this is what i get to your code:
(at the moment i again removed gnome-screensaver bcz it didnt help)

gnome-screensaver:
  Installed: (none)
  Candidate: 2.30.0-0ubuntu1
  Version table:
     2.30.0-0ubuntu2 0
        400 http://archive.ubuntu.com/ubuntu/ lucid-proposed/main Packages
        100 /var/lib/dpkg/status
     2.30.0-0ubuntu1 0
        500 http://lk.archive.ubuntu.com/ubuntu/ lucid/main Packages

[emigrant (fromwindowstolinux)]

@ Wolfgang Kufner,
finally i correctly got installed it (rebooted).
gnome-screensaver:
  Installed: 2.30.0-0ubuntu2
  Candidate: 2.30.0-0ubuntu2

but the problem refuses to fade out.

PS: sorry for the above double post.

[Erik Meitner (e.meitner)]

@emigrant: First, try to avoid using bug reports as support forums. Second, you need to make sure you are actually affected by the bug. When your screen turns black, can you switch back to a session with CTRL-ALT-F7 , CTRL-ALT-F8, CTRL-ALT-F9, etc? If so, then you are affected by bug 40011. If not, then re-read this bug and all the duplicates to help verify that you are actually having the exact same problem.

[Giovanni Battista Salvietti (giovannibattista-salvietti)]

Ok, the gnome-screensaver package in proposed solved the problem for me.
Excellent work, thank you!

[Ivan Frederiks (idfred)]

The gnome-screensaver package in proposed solved the problem for me.
Thank you!

[Michael Reiger (mighyflea)]

Seems to have solved the problem for me too. No more black screen after user switching.

It was actually necessary to reboot after installing the package from -proposed, btw.

[Ivan Frederiks (idfred)]

A really positive thing: after removing "fade on lock", locked desktop content does not become visible (it was just a blink, but it was anoying) during user-switch process.

[jeffbl (jeff-mulb)]

I considered that screen flash a security issue - the "flash" lasted several seconds if my machine was bogged down, and let anyone see what was going on for any logged in user, which should *never* be possible. Glad that is fixed as a side-effect of this, and hope it doesn't return later.

[Ivan Frederiks (idfred)]

@jeffbl, all
Oops, I hurried... After some swithes, locked desktop "flash" appeared again. But it's subject for a separate bug. Who knows, where should it be reported? Or it already has an open discussion?

[NoOp (glgxg)]

I am exeriencing the same issue - with the exception that both the keyboard and mouse go dead as well. If there is another bug report the more closely matches my symptions, please advise.

Steps to reproduce:
1. While logged in as user A, System|Log Out <username>|Switch User
2. Login to user B, ensure all is working properly and logout from user B.
- screen goes black
- keyboard no longer works
- mouse no longer works

100% reproduceable.

However, I can:
1. ssh -X into the machine w/o issue. I can bring up gui's from the affected machine (i.e., gnome-system-log, vino-preferences, etc).
2. remote login to the machine via VNC and get a screen; however I then get multiple tserver instances & have to kill it.
3. reboot the machine from the remote ssh.

Attempted to use 'apport-collect 546578' to supply additional info, but response was that I wasn't a subscriber to this bug (I am) and the report was a duplicate (it isn't). So I'll manually add the bits that may be relevant:

2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux

$ apt-cache policy gnome-screensaver
gnome-screensaver:
  Installed: 2.30.0-0ubuntu2
  Candidate: 2.30.0-0ubuntu2
  Version table:
 *** 2.30.0-0ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid-proposed/main Packages
        100 /var/lib/dpkg/status
     2.30.0-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
$ apt-cache policy xorg
xorg:
  Installed: 1:7.5+5ubuntu1
  Candidate: 1:7.5+5ubuntu1
  Version table:
 *** 1:7.5+5ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status
$ apt-cache policy xserver-xorg-core
xserver-xorg-core:
  Installed: 2:1.7.6-2ubuntu7
  Candidate: 2:1.7.6-2ubuntu7
  Version table:
 *** 2:1.7.6-2ubuntu7 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status
$ apt-cache policy nvidia-96
nvidia-96:
  Installed: 96.43.17-0ubuntu1
  Candidate: 96.43.17-0ubuntu1
  Version table:
 *** 96.43.17-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/restricted Packages
        100 /var/lib/dpkg/status

*-display
                description: VGA compatible controller
                product: NV25GL [Quadro4 900 XGL]
                vendor: nVidia Corporation

Note that there is no ATI in this machine. Given that I can reproduce & can get into the machine to gather information, please let me know if I can provide any added logs etc.

[Erik Meitner (e.meitner)]

NoOP: Reproduce the problem, ssh to the machine(without -X option), find the X display number with "ck-list-sessions" , do "export DISPLAY=:z" where "z" is the display number, then run "xgamma -gamma 1.0". Does this resolve the problem? If not, then you are experiencing another bug.

[NoOp (glgxg)]

Erik Meitner wrote:
> NoOP: Reproduce the problem, ssh to the machine(without -X option), find
> the X display number with "ck-list-sessions" , do "export DISPLAY=:z"
> where "z" is the display number, then run "xgamma -gamma 1.0". Does this
> resolve the problem? If not, then you are experiencing another bug.
>

I guess it's another bug:

$ ck-list-sessions
Session1:
 unix-user = '1001'
 realname = 'gg'
 seat = 'Seat1'
 session-type = ''
 active = TRUE
 x11-display = ':0'
 x11-display-device = '/dev/tty7'
 display-device = ''
 remote-host-name = ''
 is-local = TRUE
 on-since = '2010-05-24T18:10:36.520276Z'
 login-session-id = ''
 idle-since-hint = '2010-05-24T19:20:52.676562Z'
Session5:
 unix-user = '1001'
 realname = 'gg'
 seat = 'Seat2'
 session-type = ''
 active = FALSE
 x11-display = ''
 x11-display-device = ''
 display-device = '/dev/ssh'
 remote-host-name = 'gg-laptop'
 is-local = FALSE
 on-since = '2010-05-24T19:21:59.087478Z'
 login-session-id = ''
$ export DISPLAY=:0
$ xgamma -gamma 1.0
And the terminal hung after the last cmd Ctrl-C gets it back. Keyboard,
mouse are still dead on target/problem machine, screen black. I just
NX'ed in the problem machine & that is working fine. Anything else you'd
like me to check while it's in this state?

[Toni Förster (stonerl)]

I can confirm NoOPs experience. This just happens out of the blue, e.g while writing an e-mail the screen turns black and mouse and keyboard are dead (USB turned off?).

[Chris Coulson (chrisccoulson)]

That doesn't sound in any way related to this bug at all. Please report a different bug

[NoOp (glgxg)]

 Possibly https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/561538 instead? I'll join that bug report. Thanks.

[Chris Coulson (chrisccoulson)]

crash, please don't change the status of the bug without leaving any comment

[crash (crash369)]

My apologies. I changed it by accident and tried to change it back, without success apparently.

[Jeremy Yoder (jyoder)]

Finally got a chance to test this last night and it works like a charm on my 2 systems. Thanks!

[nigra (nigra)]

I installed _only_ the gnome-screensaver 2.30.0-0ubuntu2 from proposed-repo and the problem persists.
Should I install all the packages from that repo? The only difference I've found is this...

[Wolfgang Kufner (wolfgangkufner)]

>Should I install all the packages from that repo?
Not necessary . The package gnome-screensaver is supposed to fix this by itself. If you still have a problem chances are you have a different bug. You should file a separate bug report with a detailed description of your problem.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-screensaver - 2.30.0-0ubuntu2

---------------
gnome-screensaver (2.30.0-0ubuntu2) lucid-proposed; urgency=low

  * debian/patches/15_dont_crash_on_no_fade.patch:
    - Don't crash on systems that don't support XF86VM or XRANDR gamma fade,
      by testing if fade is supported on a particular screen before
      calling the fade_setup and fade_finish virtual functions (LP: #558721)
  * debian/patches/16_dont_crash_in_kvm.patch:
    - Don't crash when the XF86VM extension doesn't allow the gamma
      to be set (LP: #581864)
  * debian/patches/14_no_fade_on_user_switch.patch:
    - Disable fade on locking to work around LP: #546578 and prevent
      the screen remaining blank after user switching. The screensaver
      will still fade-in on idle though
 -- Chris Coulson <email address hidden> Wed, 19 May 2010 11:51:40 +0100

[Martin Pitt (pitti)]

Copied gnome-screensaver to maverick, too.

[Alejandro E Moreno Ruiz (alexmoreno)]

Bug was fixed for me with new screensaver.

But now the screensaver asks for password even if I uncheck the "Lock up desktop" option in Power Management.

Has anybody else experienced this?

[Stefan Pappalardo (sjuk)]

I updated gnome-screensaver but bug persists (black screen after user switch).

Description: Ubuntu 10.04 LTS
Release: 10.04

gnome-screensaver:
  Installiert: 2.30.0-0ubuntu2
  Kandidat: 2.30.0-0ubuntu2
  Versions-Tabelle:
 *** 2.30.0-0ubuntu2 0
        500 http://de.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
        100 /var/lib/dpkg/status
     2.30.0-0ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages

xorg:
  Installiert: 1:7.5+5ubuntu1
  Kandidat: 1:7.5+5ubuntu1
  Versions-Tabelle:
 *** 1:7.5+5ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

nvidia-173:
  Installiert: 173.14.22-0ubuntu11
  Kandidat: 173.14.22-0ubuntu11
  Versions-Tabelle:
 *** 173.14.22-0ubuntu11 0
        500 http://de.archive.ubuntu.com/ubuntu/ lucid/restricted Packages
        100 /var/lib/dpkg/status

  *-display
       description: VGA compatible controller
       product: NV34 [GeForce FX 5200]
       vendor: nVidia Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 32 bits
       clock: 66MHz
       capabilities: pm agp agp-3.0 bus_master cap_list rom
       configuration: driver=nvidia latency=248 maxlatency=1 mingnt=5
       resources: irq:16 memory:fb000000-fbffffff memory:f0000000-f7ffffff(prefetchable) memory:faf00000-faf1ffff(prefetchable)

[NoOp (glgxg)]

@Stefan: given that you are running an nvidia card, your issue may be related to mine. I've filed a separate bug:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-96/+bug/585685
Have a look at that & see if perhaps it may be caused by your nvidia-173 driver. If so then it's something common between the -96 and -173 drivers.

[Robert B (robertbub)]

This is still a problem for me with gnome-screensaver 2.30.0-0ubuntu2. I have an Acer Aspire 5740-5513, which various websites say is an Intel GMA video card.

My workaround is to essentially disable gnomesaver by "sudo mv /usr/bin/gnome-screensaver /usr/bin/gnome-screensaver.bak".

I hope whatever new version of gnome-screensaver comes out fixes this problem.

[David Tombs (dgtombs)]

@Robert: If it's still broken for you (did you try rebooting?), then you have a different bug. Please file a new one with "ubuntu-bug gnome-screensaver".

[Marcos Wasem (mwasem)]

The same happened to me yesterday after a few switches between two accounts. I had this problem, and I had upgraded to gnome-screensaver 2.30.0-0ubuntu2 in a Dell Inspiron 530 a few days ago. Yesterday I had the black sreen.again.

[Robert B (robertbub)]

OK, I created https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/587668 .

[Ludovic Rousseau (ludovic-rousseau-gmail)]

I had a similar bug: switching to a new user display a black screen with only the mouse cursor.

I can switch to the text consoles (Ctrl-Alt-Fn) and to the first X session. But it looks like the second X is "mixed" with the first one. I can see the user selector a few milliseconds before the first X session is displayed if I switch to F8. And I have the black screen with mouse cursor on F9.

My Lucid 10.04.1 system is an upgrade from 8.04. It looks like the use switching applet is the source of the problem (in my case).
Removing ~/.gnome* and ~/.gconf* to reinitialization the gnome configuration solved the problem.

The old (and problematic) user switching applet was the one with the green running man. The new (and working) user switching applet has a power sign as icon.

[Carey (carey)]

Ludovic Rousseau, thanks for your comment but your report is not the same bug, as I can confirm this bug occurs with a fresh install of Ubuntu 10.04 (i.e. irrespective of any .gnome or .gconf configuration).

[Samuel (altas)]

I had similar bug, but i add that before the black screen showed the desktop all compress on full width and 1cm height.
And the last thing i did was to try to login on a user with no password, but the system ask me for the password and did not ascept a blank one , then try to switch to other user, then black screen.

[Connie (diacalc)]

I had the same bug. After logging more than one user and logout one of them I got the black screen.

I've updated nvidia drivers to 173.14.27 and the bug has gone.

Adding repo with the latest drivers for nvidia cards

sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
sudo apt-get update
sudo apt-get upgrade

Now I can switch between users and logging out at any moment.

$ nvidia-settings -q NvidiaDriverVersion

  Attribute 'NvidiaDriverVersion' (connie-desktop:0.0): 173.14.27

$ uname -a
Linux connie-desktop 2.6.32-25-generic #43-Ubuntu SMP Wed Sep 1 09:46:39 UTC 2010 i686 GNU/Linux

[chavez (texasflyfisher)]

I can confirm that after installing nvidia driver 173.14.27, the problem with the black screen after switching to a new user and logging off is gone!

I have had this problem for a long time! I tested it four times in a row. Prior to installing the new driver, I hit the failure each time after switching to a new user and logging out.

Thanks Connie!

[PAB (pablhomme)]

I am a victim of this bug since version 10.04. I've been using Ubuntu since 2006 and it's the first time that a bug last this long and is so annoying.

I have a full updated 10.10-64 bit Ubuntu version and the bug is still affecting me. I can almost tell when the crash will arrive.

The only thing that works when the bug arrives is Alt+PrintSc+S+U+B. Alt+F1 or Alt+F7 or any other combination does not do anything.

We are four on the same family computer. I run a lot of image processing and I never know when my process will crash just because on of my child only wants to chat with someone in there account.

I'm almost at the point were I would like to test some other distribution or even go back to Windows.

I really like Ubuntu and since 2006 I'm a passionate user but this one is realy bad, a real showstopper.

Please help!

[Richard Genoud (richard-genoud)]

2010/11/12 PAB <email address hidden>:
> I am a victim of this bug since version 10.04.  I've been using Ubuntu
> since 2006 and it's the first time that a bug last this long and is so
> annoying.
>
> I have a full updated 10.10-64 bit Ubuntu version and the bug is still
> affecting me.  I can almost tell when the crash will arrive.
>
have you tried to uninstall gnome-screensaver ?
I had no more problems after that.

[David Tombs (dgtombs)]

PAB: The workaround currently in gnome-screensaver "fixes" the issue. If you're stilling having a problem, file a new bug with "ubuntu-bug xorg".

[dasumin (da-sumin)]

Updating nvidia drivers also worked for me (from #123). Thanks!

[Bryce Harrington (bryce)]

Sounds like this wasn't really an xorg-server bug. Several people report updates to -nvidia solved it, so going to go ahead and mark it fixed.

[Ernst Persson (ernstp)]

I'm pretty sure this is fixed now.