[Bug 1102540] Re: Screen unlock password dialog stays visible and on top forever after unlocking
Bug Watch Updater
1102540 at bugs.launchpad.net
Mon Jan 21 20:27:06 UTC 2013
Launchpad has imported 42 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=306186.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2012-09-03T06:48:00+00:00 Mikopp wrote:
This does not happen all the time, but once it has only restarting KDE
removes the dialog
1) lock your desktop
2) unlock you desktop
the dialog that you get to enter your password stays on the screen (see screenshot) and does not go away unless you kill KWIN (which obviously doesn't help really) or restart KDE all together.
Even locking and unlocking the screen afterwards doesn't improve the situation, even worse, I have a dual screen and after several lock/unlock I have that dialog in the middle of both my displays.
The dialog can not be clicked or interacted with, actually the windows
below it can be clicked at, so it seems a drawing issue, the window
doesn't seem to exist anymore.
Reproducible: Sometimes
Steps to Reproduce:
1) lock your desktop
2) unlock you desktop
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/0
------------------------------------------------------------------------
On 2012-09-03T06:49:24+00:00 Mikopp wrote:
Created attachment 73620
screenshot of the situation after unlock
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/1
------------------------------------------------------------------------
On 2012-09-03T07:24:52+00:00 Mgraesslin wrote:
I have seen this issue once but had no chance to properly investigate
it. An easy solution is to press Alt+Shift+F12 twice to suspend and
resume compositing.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/2
------------------------------------------------------------------------
On 2012-09-03T07:36:00+00:00 Thomas-luebking wrote:
@Michael:
- can you reproduce this somewhat often?
- do you unredirect fullscreen windows?
- does it remain if you export QT_NO_GLIB=1 from some ~/.kde/env script
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/3
------------------------------------------------------------------------
On 2012-09-03T10:31:27+00:00 Mikopp wrote:
@Martin
Thanks workaround works!
@Thomas
* Happens pretty regularly
* ??? not sure what you mean here. I have "maximized" windows but no fullscreen windows.
* Not tested, and as this is my work desktop I won't be able for a couple of days to do this, I will try to test it though
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/4
------------------------------------------------------------------------
On 2012-09-03T14:44:30+00:00 Thomas-luebking wrote:
"kcmshell4 kwincompositing", last tab, "suspecnd comspositing for
fullscreen windows" checkbox
How keen are you in using shell tools - do you think you can switch to VT1, there
export DISPLAY=:0
check for the password window (this has to happen really fast: move the mouse to trigger the locker, then move to VT1 where this command is already present or in history)
xwinfo -root -tree | grep "KDE Screen Locker"
and then monitor events for UnmapNotify
xev -root | grep -A1 UnmapNotify
and see whether the WinId found by the xwinfo command matches an
UnmapNotification
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/5
------------------------------------------------------------------------
On 2012-09-23T06:30:30+00:00 Juha Tiensyrjä wrote:
I can confirm this bug, happens to me also every couple of days or so
both with 4.9.0 and 4.9.1 from Kubuntu packages.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/6
------------------------------------------------------------------------
On 2012-09-23T19:58:22+00:00 Thomas-luebking wrote:
much (MUCH) more important than "me too" would be to answer the
questions of comments #3 & #5 ;-)
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/7
------------------------------------------------------------------------
On 2012-09-24T07:44:57+00:00 Mikopp wrote:
can you reproduce this somewhat often: Seems to happen every time that I
leave my screen unattended on a multi screen, never happened to me when
working on the notebook without external screens.
do you unredirect fullscreen windows: not sure what you mean, I do have
fullscreen windows, in particular VirtualBox in seamless mode running
sometimes. I have ""kcmshell4 kwincompositing", last tab, "suspecnd
comspositing for fullscreen windows" checkbox" activated, does not
change anything, problem still occurs.
- does it remain if you export QT_NO_GLIB=1 from some ~/.kde/env script
not tested yet, what other implications does this setttin have
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/8
------------------------------------------------------------------------
On 2012-09-28T05:26:15+00:00 Mgraesslin wrote:
*** Bug 307473 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/9
------------------------------------------------------------------------
On 2012-09-28T12:36:23+00:00 Thomas-luebking wrote:
Is this also reproducible if you turn all active screen edges off?
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/10
------------------------------------------------------------------------
On 2012-10-02T06:11:49+00:00 Mikopp wrote:
Turned screenedges off, still same problem
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/11
------------------------------------------------------------------------
On 2012-10-02T07:45:58+00:00 Mikopp wrote:
I can't seem to reproduce it if I force screen lock and then switch to
VT1 and back. window id is the same between xwinfo and unmap then.
I see if I can reproduce it if the lock screen comes via normal screen
timeout
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/12
------------------------------------------------------------------------
On 2012-10-02T19:23:29+00:00 Thomas-luebking wrote:
(In reply to comment #12)
> I can't seem to reproduce it if I force screen lock and then switch to VT1
> and back.
you might be more lucky by ssh'ing into the machine.
> if you export QT_NO_GLIB=1 from some ~/.kde/env script
> not tested yet, what other implications does this setttin have
the setting makes Qt use the more straight forward unix event dispatcher instead of the glib one, exporting it to the global environment applies that to all Qt applications (after re-logging in)
The setting does not cause permanent changes (at least it's not supposed to, but oc. any application could check for that value, store "CrashMe=true" in it's settings and from now on just crash on start =)
Ie. the moment you remove the script, the alteration is gone with the next login.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/13
------------------------------------------------------------------------
On 2012-10-05T05:08:23+00:00 Mikopp wrote:
ok could reproduce it now, xwinfo shows a different window id than the
first unmap notify.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/14
------------------------------------------------------------------------
On 2012-10-09T12:21:55+00:00 Thomas-luebking wrote:
*** Bug 308116 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/15
------------------------------------------------------------------------
On 2012-10-11T09:27:41+00:00 Paul Fee wrote:
Also present on Fedora 17.
$ rpm -qf /usr/bin/kwin
kde-workspace-4.9.2-3.fc17.x86_64
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/16
------------------------------------------------------------------------
On 2012-10-22T18:09:13+00:00 Mgraesslin wrote:
I had the chance to have a look at a system which showed the same
problem. Relevant part of supportInformation:
Currently Active Effects:
-------------------------
kwin4_effect_fade
kwin4_effect_blur
Unloading the fade effect, made the window go away.
@Thomas: could something trigger an incorrect unref in AnimationEffect?
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/17
------------------------------------------------------------------------
On 2012-10-22T19:14:12+00:00 Thomas-luebking wrote:
>From the screenshot (the window is opaque. did it perform a fedeout on
your side at all?) i suspect a time problem, ie. AniData::startTime
being much much bigger than QTime::currentTime()
Can you reproduce to test it? (or anyone else, including injecting debug
out, ie. recompile)
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/18
------------------------------------------------------------------------
On 2012-10-22T19:18:54+00:00 Thomas-luebking wrote:
Daybreak issue?
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/19
------------------------------------------------------------------------
On 2012-10-22T20:28:18+00:00 Mgraesslin wrote:
> From the screenshot (the window is opaque. did it perform a fedeout on your
> side at all?)
yes, it was completely opaque, which I found odd, given that fade was active.
> Can you reproduce to test it?
No pattern seen so far
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/20
------------------------------------------------------------------------
On 2012-10-26T11:58:32+00:00 Eric Erfanian wrote:
I am able to reproduce this bug frequently by switching between two
users.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/21
------------------------------------------------------------------------
On 2012-10-26T14:03:38+00:00 Thomas-luebking wrote:
(In reply to comment #21)
> I am able to reproduce this bug frequently by switching between two users.
- do you use the fade effect?
- does it go away when disabling it?
- can you run some self compiled code with a debug out patch?
@Martin
i'm gonna write some dbus inspection code for the animationeffect class, basically print AniData for running animations on request
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/22
------------------------------------------------------------------------
On 2012-10-26T14:12:05+00:00 Mgraesslin wrote:
> i'm gonna write some dbus inspection code for the animationeffect class,
> basically print AniData for running animations on request
sounds good, I'm going to add something to the Scripted Effects
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/23
------------------------------------------------------------------------
On 2012-10-29T01:44:24+00:00 Eric Erfanian wrote:
(In reply to comment #22)
> (In reply to comment #21)
> > I am able to reproduce this bug frequently by switching between two users.
>
> - do you use the fade effect?
Yes, both users use the fade effect.
> - does it go away when disabling it?
I'll have to try again when it appears. No luck reproducing it right
now.
> - can you run some self compiled code with a debug out patch?
Sure; please just tell me what to checkout and any special compile /
installation instructions,and then how to dump the debug information
when it happens again.
>
> @Martin
> i'm gonna write some dbus inspection code for the animationeffect class,
> basically print AniData for running animations on request
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/24
------------------------------------------------------------------------
On 2012-10-31T12:24:17+00:00 Eric Erfanian wrote:
Bug reappeared today. I disabled the fade effect in the account in
desktop effects, and the lock screen dialogue went away.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/25
------------------------------------------------------------------------
On 2012-10-31T22:00:11+00:00 adaptee wrote:
*** Bug 309321 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/26
------------------------------------------------------------------------
On 2012-10-31T23:05:06+00:00 Eric Erfanian wrote:
Interesting.Still on the same desktop session after disabling and then
re-enabling the fade effect to get rid of the dialogue.
The dialogue still appears when switching between virtual desktops.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/27
------------------------------------------------------------------------
On 2012-11-01T00:04:55+00:00 Thomas-luebking wrote:
The window is onyl visible during the transition, i assume?
Are you using the fade desktop effect for the desktop transition?
Unloading the fade effect would not have unreferenced the window anyway (that is a bug) so i don't actually see why that should have removed the window in the first place.
-> does reloading the fade desktop effect have an impact?
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/28
------------------------------------------------------------------------
On 2012-11-01T01:13:31+00:00 Eric Erfanian wrote:
(In reply to comment #28)
> The window is onyl visible during the transition, i assume?
Correct.
> Are you using the fade desktop effect for the desktop transition?
No, it is the cube animation. When I try the fade desktop effect it does
not appear.
> Unloading the fade effect would not have unreferenced the window anyway
> (that is a bug) so i don't actually see why that should have removed the
> window in the first place.
Me neither, but disabling and re-enabling the fade effect worked!
> -> does reloading the fade desktop effect have an impact?
Negative; loading and unloading the fade desktop effect does not make
the dialogue disappear from the desktop switching cube animation.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/29
------------------------------------------------------------------------
On 2012-11-01T07:40:11+00:00 Thomas-luebking wrote:
(In reply to comment #29)
> No, it is the cube animation. When I try the fade desktop effect it does not
> appear.
Ok, de/activating the "fade desktop" effect would make no sense then, but it explains why the ref'd window suddenly shows up again.
Can you (unless you restarted meanwhile) provide the output of
qdbus org.kde.kwin /KWin supportInformation
and did i ask whether you can compile a patch into kwin?
In particular this one: https://git.reviewboard.kde.org/r/107063/
It will allow you to print extended debug data from the fade effect.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/30
------------------------------------------------------------------------
On 2012-11-01T12:23:26+00:00 Eric Erfanian wrote:
Created attachment 74913
Kwin Support Info
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/31
------------------------------------------------------------------------
On 2012-11-01T12:24:54+00:00 Eric Erfanian wrote:
(In reply to comment #30)
> (In reply to comment #29)
>
> > No, it is the cube animation. When I try the fade desktop effect it does not
> > appear.
> Ok, de/activating the "fade desktop" effect would make no sense then, but it
> explains why the ref'd window suddenly shows up again.
> Can you (unless you restarted meanwhile) provide the output of
> qdbus org.kde.kwin /KWin supportInformation
>
Attached.
> and did i ask whether you can compile a patch into kwin?
> In particular this one: https://git.reviewboard.kde.org/r/107063/
> It will allow you to print extended debug data from the fade effect.
I'll look into it tonight and see if I can do it.
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/32
------------------------------------------------------------------------
On 2012-11-02T11:20:05+00:00 adaptee wrote:
*** Bug 309412 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/33
------------------------------------------------------------------------
On 2012-11-02T13:30:39+00:00 Thomas-luebking wrote:
last dupe suggests daybreak relevance
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/34
------------------------------------------------------------------------
On 2012-11-02T19:52:19+00:00 Thomas-luebking wrote:
Created attachment 74942
Pot. fixing patch
Due to the possible daybreak relevance, attached is a patch that invokes
also the date for the starttime of the effect..
Stupid question:
does the screensaver come with an STR (ie. the clock gets out of sync and then is resynced by ntp, causing a major jump?)
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/35
------------------------------------------------------------------------
On 2012-11-11T03:16:22+00:00 Christoph-maxiom wrote:
*** Bug 305083 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/36
------------------------------------------------------------------------
On 2012-11-14T20:33:47+00:00 Thomas-luebking wrote:
Git commit a0aacdae08a6bdae0a30139d65ef92d5dff136e5 by Thomas Lübking.
Committed on 03/11/2012 at 21:33.
Pushed by luebking into branch 'master'.
use QELapsedTimer to measure animation delay
QElapsedTimer uses a monotic clock on all relevant systems
and is thus invarant against date/time changes (while the
bug was likely caused by daybreaks)
REVIEW: 107250
FIXED-IN: 4.10
use monitc clock
M +3 -3 kwin/libkwineffects/anidata.cpp
M +1 -2 kwin/libkwineffects/anidata_p.h
M +12 -7 kwin/libkwineffects/kwinanimationeffect.cpp
M +6 -0 kwin/libkwineffects/kwinanimationeffect.h
http://commits.kde.org/kde-
workspace/a0aacdae08a6bdae0a30139d65ef92d5dff136e5
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/37
------------------------------------------------------------------------
On 2012-11-16T01:28:23+00:00 adaptee wrote:
*** Bug 306941 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/38
------------------------------------------------------------------------
On 2012-11-30T14:22:16+00:00 Thomas-luebking wrote:
*** Bug 310924 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/39
------------------------------------------------------------------------
On 2012-12-15T09:19:57+00:00 Thomas-luebking wrote:
*** Bug 311721 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/40
------------------------------------------------------------------------
On 2012-12-28T07:18:04+00:00 Mgraesslin wrote:
*** Bug 312292 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/kde-
workspace/+bug/1102540/comments/41
** Changed in: kdebase-workspace
Status: Unknown => Fix Released
** Changed in: kdebase-workspace
Importance: Unknown => High
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1102540
Title:
Screen unlock password dialog stays visible and on top forever after
unlocking
To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1102540/+subscriptions
More information about the kubuntu-bugs
mailing list