Comment 135 for bug 160264

Revision history for this message
Sam Liddicott (sam-liddicott) wrote : RE: [Bug 160264] Re: [nvidia] compiz displays white screen when locked

Related I think:

If I switch users and insert mdia or do som other action that causes a popup on my original desktop and then switch back and unlck, thn on that desktop I see some pure white windows slightly largr than what the popup window would be.

I can only get rid f these winds using the brokn-window killer.

Sam

-----Original Message-----
From: Patryk J <email address hidden>
Sent: 16 December 2008 06:49
To: <email address hidden>
Subject: [Bug 160264] Re: [nvidia] compiz displays white screen when locked

Just thought I'd add this:

I just tried locking my screen as User1. The screen-saver started
running. I hit ESC to exit the screen-saver and log back in. I was
prompted with the standard unlock login prompt (no white screen).

At this screen I chose "Switch User" instead of logging in. I was
prompted through the GDM login screen for a username and password. I
entered User2 / password and was dropped into User2's desktop
immediately (as if I had switched users; i.e. it didn't login a new
User2 session, but rather switched me to User2 --this all seems
correct).

At this point I switched back to User1 and was prompted with User1's
unlock screen --NOT the white screen. I was able to unlock the screen
with User1's password and was back to User1's desktop.

My reason for mentioning this is because it seems that when I went from
the unlock screen (where U1's screen was locked), I was able to return
without the white screen. When I go directly from my desktop and switch
users, I return to the white screen. I'm hoping that this will help to
isolate the offending code.

To tie this into the permissions idea; the locked screen prompt is
publicly visible, while my desktop isn't. ?? M'eh. Just a thought.
Anyway, I hope this helps shed some light.

--
[nvidia] compiz displays white screen when locked
https://bugs.launchpad.net/bugs/160264
You received this bug notification because you are a direct subscriber
of a duplicate bug.