Bug 198607 - need to kill kwin after suspend
Summary: need to kill kwin after suspend
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-02 08:49 UTC by Salvo "LtWorf" Tomaselli
Modified: 2011-04-16 21:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Salvo "LtWorf" Tomaselli 2009-07-02 08:49:03 UTC
Version:           unknown (using 4.2.4 (KDE 4.2.4), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.30-final

When i suspend and open the laptop again, _sometimes_ it is impossible to unlock the screen. I can see the mouse so X11 is working but the unlock box doesn't appear. Then i go to a terminal session and i do:

killall krunner_lock
killall kwin
export DISPLAY=:0
nohup kwin &
exit

And then i can go back to X11 and everything will be working. If i just kill krunner_lock, i'll get a black screen with the cursor. Moving it around it changes, so the windows are there but just... not painted.
Comment 1 Martin Flöser 2009-07-17 22:35:21 UTC
What if you only kill kwin without killing krunner_lock?
Comment 2 Salvo "LtWorf" Tomaselli 2009-08-12 08:57:28 UTC
Then krunner_lock works again after i restart kwin, and i can unlock the screen.
Comment 3 Martin Flöser 2009-08-12 10:31:41 UTC
just an idea: press alt+shift+f12 before doing the suspend. That will temporarily turn off compositing and perhaps it's working. If that works we will have a look at your effects and try to find one that could be causing the trouble ;-)
Comment 4 Salvo "LtWorf" Tomaselli 2009-08-12 12:40:34 UTC
The problem occurs randomly, so how would i know if it is not occurring because disabling the composite works or just because it is randomly not occurring for a while?
Comment 5 Martin Flöser 2009-08-12 12:43:51 UTC
Good point. And I have no idea how to solve those problems. I don't know how often it happens to you, but perhpas you can try for two weeks. If it happens you can enter "doesn't work", if it doesn't happen for two weeks we could assume it helped
Comment 6 Thomas Lübking 2009-08-12 14:13:09 UTC
maybe this is another unredirection issue?

@Michael Dorn
add "UnredirectFullscreen=false" to ~/.kde/share/config/kwinrc, [Compositing] section, don't suspend compositing and try whether you can reproduce this (in case, try with suspending compositing...)
Comment 7 Salvo "LtWorf" Tomaselli 2009-09-28 08:13:17 UTC
I did not try what you say, but i've noticed that disabling lock on wakeup i don't have problems. At least.. for now :-D
Comment 8 Pavlo84 2010-10-08 16:01:21 UTC
Sorry for my english please.
I have this bug too on Archlinux 64bit.
I think, that problem is in compositing of kwin, because lock screen is shown when i press alt+shift+f12 after opening screen of my laptop.
I set lock screen when laptop screen locked in powerdevil settings.
I may reproduce this bug for me by doing next steps:
1. close laptop screen.
2. plug off AC adapter from laptop.
3. plug on AC adapter.
4. open laptop screen, and thats it. I have this bug.