double window to enter password in a locked session

Bug #36938 reported by Albert Cardona on 2006-03-28
14
Affects Status Importance Assigned to Milestone
ubuntu-meta (Ubuntu)
Medium
Unassigned

Bug Description

Ever since late February, after some kernel updates (KDE was and is 3.5 and remains the same version), the KDE 'session locked' window to enter the password first appears, one starts typing, then disappears and reappears with the password field empty, which finds me pushing return in an incomplete or empty text box. Very annoying, considering I lock the screen dozens of times everyday.
Kubuntu breezy ppc.

Kenny Duffus (kduffus) wrote :

Please can you try logging in either from another machine or for instance by doing ctrl-alt-1 and check if you have multiple copies of the screensaver running? I sometimes experienced this with breezy

Changed in kubuntu-meta:
assignee: nobody → kubuntu-team
status: Unconfirmed → Needs Info
Albert Cardona (cardona) wrote :

What is the name of the screensaver application, so I can find it in a 'top' ? Thanks for looking into this.

Albert Cardona (cardona) wrote :

I've logout-login and every thing seems fine. I know this is a minor issue, but issues like this one is what keeps people in macosx, for example, instead of in kubuntu-ppc. In the macosx I never logout for a year. In kubuntu, I have to logout every week or the computer engages into what appears as malfunctioning, such as the double locking windows, lots of kio_http that take up half the RAM, the Xorg growing in memory usage up to 25 %, Adept undergoing crashes when finishing and re-filtering, konserve not working, and then yes, and then no ... consistency, convenience and optimal performance are what makes an OS desirable in a production environment. Ubuntu is *almost* there! Keep going guys.

Albert Cardona (cardona) wrote :

After the third locking of the screen the problem is back. I would appreciate the name of the screensaver app so I can kill it/HUP it/see if there are two copies or what.

Loïc Corbasson (cnb) wrote :

If you run pstree you'll find the following line:
    --snip--
     |-kdesktop---kdesktop_lock---kblankscrn.kss
    --/snip--
So I presume kdesktop (which cares about desktop-related things) launches kdesktop_lock which locks the screen, and the latter launches the actual screensaver (here, the blank one).

Albert Cardona (cardona) wrote :

You're right, if I disable the "require password to stop screensaver" option in the System Settings, I don't get the problem anymore. But then, I need to lock the screen manually all the time (which is what I do anyway, so it works for me).
The screensaver then needs to be aware that the password should not be required if the screen is already locked.

Albert Cardona (cardona) wrote :

More: although I have unchecked the "Require password to stop" for the screensaver, if the screen remains locked (and the computer sleeping) for a few minutes, I get the same double-window problem. I have the screensaver to kick in after 3 minutes, so maybe the screensaver is launching right after waking up the computer if it has been 'idle' for longer than the 3 minutes, and this refreshes the screen or something? It's really puzzling.

Albert Cardona (cardona) wrote :

This bug is still present in Dapper 6.06 as of 20060525. And annoying just the same.

Richard Johnson (nixternal) wrote :

I am going to fix release this report for 2 reasons, 1) lack of activity, and 2) it doesn't seem present here for me. If you feel this is still an issue, I urge you to reopen this report. Thank you!

Changed in kubuntu-meta:
status: Needs Info → Fix Released
Albert Cardona (cardona) wrote :

Well, this bug is still present:

- lock the screen manually
- close the lid
- wait long enough so that the powersave thinks, on resuming, that the screen has to be locked
- on resume, a locking window appears and disappears, then one has to move the mouse to get the locking window again.

Observed in gnome, feisty dist-upgraded to today.

Albert

Richard Johnson (nixternal) wrote :

OK, I don't have this problem, however you just stated that you are experiencing this issue in GNOME as well, which makes me wonder why Kubuntu meta is selected. I am reopening this report in the meantime and hopefully going to find the right package.

Changed in kubuntu-meta:
status: Fix Released → Confirmed
Changed in ubuntu-meta:
assignee: kubuntu-team → nobody
JC Hulce (soaringsky) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Does this issue still exist in newer versions of Ubuntu?

Changed in ubuntu-meta (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu-meta (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers