blank screen after log out if other user is logged in.

It is the same for me. Need help!

Exactly the same problem. Lucid fresh install and nvidia graphic card with propertary driver. No problems when Karmic was inside. Switching users goes nicely but if "user2" logs out the screen goes black.

Has it anything to do with this one?

https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/549632

maybe, but i can't reproduce that bug, while mine persists. I think they're different.

Well, unfortunately deactivating the nvidia-driver (173) took care of the problem for me. Does that mean that the Ubuntu-team can't do anything about it? On the other side, that driver worked under Karmic as well as Jaunty...

I have exactly the same issue. But on machine with GF6600 since I've switched to 195 driver (from 173), problem disappeared. Now I can switch and logout user freely.
On another machine with GF5200 I cannot install the newest driver. I also have tried 96 driver, but that didn't solve a problem.

Hi nicola,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 578139

Also, if you could 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.]

I'm experiencing this bug on an up-to-date Lucid install with an Intel graphics card and no proprietary drivers.

Ame here, on Intel Integrated HD Graphic chip on Acer 5740

Updated Lucid using Nvidia proprietry drivers, when I've got two users logged in and log out of one I (much) more often than not end up with a completely blank and unresponsive screen.

I have the same problem with 10.04 on an dell laptop with intel graphics. The only thing I can add is that it was the same on 9.10 for me. Never added it as a bug as very rarely had two concurrent users, and mostly forgot about it.

A few of you(Intel gfx card users) should verify that you are not affected by bug 546578.

I confirm that the issue exists with lucid lynx installed as new and upgraded to the most recent version.

I will collect debug information as soon as I will use my laptop, today or tomorrow.

For what concerns upstream-testing, I will read and understand what it is :) then eventually do what the automatic message from Jeremy Foshee asks!

Thanks for following.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Informations added, but i think i won't do the upstream-testing, because I don't understand well what it is.

I'm still not sure if "kernel" is the right package-tag for this bug.
It could be also gdm, but in the ubuntuforums a kubuntu user said he has the same issue, so gnome would not be responsible.

Just updated Lucid, had hoped that the new gnome-screensaver would solve the problem when the fading effect is disabled. But no...

The bug is reproduced also with the "guest" session.

Forum entries:
http://ubuntuforums.org/showthread.php?p=9387908#post9387908
http://ubuntuforums.org/showthread.php?p=9266253#post9266253

suggested walkaround:
http://chanflee.com/?p=1682

Uninstalling gnome-screensaver did not work for me. :(

I am new at this bug-subscribing thing. Could anyone tell me how to
help, if there is something I can do...?

mån 2010-05-31 klockan 13:08 +0000 skrev nicola de mitri:
> Forum entries:
> http://ubuntuforums.org/showthread.php?p=9387908#post9387908
> http://ubuntuforums.org/showthread.php?p=9266253#post9266253
>
> suggested walkaround:
> http://chanflee.com/?p=1682
>

This bug happens to me, but it appears to be tied to settings. I had problems with this bug, so I do a fresh lucid 64 bit install and moved over my old /home settings, and the bug still happened. Then I did a fresh install with new settings and I hasn't happened so far in the couple of hours that I've been using it.
If I remember correctly, my settings have come from 9.10 and were migrated to a testing version of 10.04, and then migrated to the released version of 10.04.
So, I guess I'm curious to know:
Where all have the settings of the bug reporter been?

I'm using a nvidia card, which some people think is related. I'm not sure.
Also, I'm going to see if I can use a test install to test my settings, dividing them up until I get an idea of what setting is causing the problem.

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.]

I'm having this problem as well. I'm using 32-bit Ubuntu 11.04.

the following fixed it for me (in lucid, 32bit):

removing /home/username/.gconfd/saved_state before login. Appearently gnome freaks out if it exists before logging in and contains odd information, like with a crash, it barfs on log-out.

Atleast that's what it looks from here.. Still a bug though, in LTS.

nicola de mitri, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could 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 . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]