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

Bug #578139 reported by nicola dmt
84
This bug affects 16 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

System: 10.04 LTS i386 (on a 64bit architect.) fresh install. Sony Vaio VGN-NR.... laptop. nVIDIA propertary.

"userone" and "usertwo" are logged in. I'm using "usertwo". When i log out "usertwo" i expect to get the screensaver of "userone" and a unlock dialog. On the contrary, i get a blank screen where neither ctrl+alt+f# nor the caps lock light work. SysRq "k" works but obviously kill "userone".

(This happens all the time in that circumstance. No failing happens if only one user is logged in and only him logs out.)

P.S. I don't know if the responsible package is "linux" or "gdm".
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nicola 1426 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc300000 irq 22'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,104d2800,00100100 HDA:14f12c06,104d1700,00100000'
   Controls : 19
   Simple ctrls : 12
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=1555e2a9-0589-4c4a-865e-05a68671503c
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Sony Corporation VGN-NR31S_S
NonfreeKernelModules: nvidia
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=72ed167b-1b07-4956-8955-5f6115f4b855 ro quiet splash
ProcEnviron:
 LANG=it_IT.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: lucid kconfig regression-release needs-upstream-testing
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/24/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R1150J9
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR1150J9:bd12/24/2007:svnSonyCorporation:pnVGN-NR31S_S:pvrC3LR43U5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-NR31S_S
dmi.product.version: C3LR43U5
dmi.sys.vendor: Sony Corporation

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote :

It is the same for me. Need help!

Revision history for this message
Magnus Ljungqvist (magnus-ljungqvist) wrote :

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.

Revision history for this message
Magnus Ljungqvist (magnus-ljungqvist) wrote :
Revision history for this message
nicola dmt (nicola-dmt) wrote :

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

Revision history for this message
Magnus Ljungqvist (magnus-ljungqvist) wrote :

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

Revision history for this message
Adam Wujtewicz (adahow) wrote :

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.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

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

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Anthony Hertzler (plant-sequoias) wrote :

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

Revision history for this message
suntania (ozerki) wrote :

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

Revision history for this message
Martin Sandin (msandin) wrote :

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.

Revision history for this message
Mike Gaffney (mike-gaffney) wrote :

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.

Revision history for this message
Erik Meitner (e.meitner) wrote :

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

Revision history for this message
nicola dmt (nicola-dmt) wrote :

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.

Revision history for this message
nicola dmt (nicola-dmt) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
nicola dmt (nicola-dmt) wrote : BootDmesg.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : Card0.Codecs.codec.1.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : CurrentDmesg.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : IwConfig.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : Lspci.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : Lsusb.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : PciMultimedia.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : ProcInterrupts.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : ProcModules.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : UdevDb.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : UdevLog.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote : WifiSyslog.txt

apport information

Revision history for this message
nicola dmt (nicola-dmt) wrote :

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.

Revision history for this message
Magnus Ljungqvist (magnus-ljungqvist) wrote :

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

Revision history for this message
nicola dmt (nicola-dmt) wrote :

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

Revision history for this message
nicola dmt (nicola-dmt) wrote :
Revision history for this message
Magnus Ljungqvist (magnus-ljungqvist) wrote : Re: [Bug 578139] Re: blank screen after log out if other user is logged in.

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
>

Revision history for this message
Erik B. Andersen (azendale) wrote :

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.

Revision history for this message
Jeremy Foshee (jeremyfoshee) 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 → Expired
Martin Sandin (msandin)
Changed in linux (Ubuntu):
status: Expired → New
Brad Figg (brad-figg)
tags: added: acpi-apic
tags: added: acpi-brightness
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Jason Van Biezen (jason-vanbiezen) wrote :

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

Revision history for this message
webmind (webmind) wrote :

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.

Revision history for this message
penalvch (penalvch) wrote :

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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.