Bug 316797 - plasma-overlay doesn't start and hereby kills all X input
Summary: plasma-overlay doesn't start and hereby kills all X input
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: screensaver overlay (show other bugs)
Version: 4.10.1
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL: https://bugs.freedesktop.org/show_bug...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-15 20:23 UTC by Elias Probst
Modified: 2018-06-08 19:00 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Configuration of plasma-overlay (590 bytes, application/octet-stream)
2013-03-15 20:23 UTC, Elias Probst
Details
Screensaver configuration (201 bytes, application/octet-stream)
2013-03-15 20:23 UTC, Elias Probst
Details
Debug output in ~/.xsession-errors (7.69 KB, text/plain)
2013-03-15 20:25 UTC, Elias Probst
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elias Probst 2013-03-15 20:23:10 UTC
Created attachment 78099 [details]
Configuration of plasma-overlay

I have the plasma-overlay configured to show up after 1 minute of inactivity and to require a password after another 30 seconds.

The configuration of the plasma-overlay is pretty much the default configuration - at least I can't remember having anything changed.

After 1 minute, no plasma-overlay shows up and from this point on, X doesn't react on any input at all (no mouseclicks, no keyboard input).

I've captured the corresponding output in ~/.xsession-errors during that time by running:
sleep 55 && echo "" > .xsession-errors && sleep 45 && cp .xsession-errors locker-bug.xsession-errors

The following configuration files will be attached to this bug:
plasma-overlay-appletsrc
kscreensaverrc

A possible cause for this "might" be the fact, that the resolution in plasma-overlay-appletsrc is 2560x1440 (the external screen I connect every once in a while), while the current resolution is 1920x1080.
Comment 1 Elias Probst 2013-03-15 20:23:40 UTC
Created attachment 78100 [details]
Screensaver configuration
Comment 2 Elias Probst 2013-03-15 20:25:59 UTC
Created attachment 78101 [details]
Debug output in ~/.xsession-errors
Comment 3 Elias Probst 2013-03-15 20:29:24 UTC
Should have probably added the information, that this problem doesn't happen, when kscreensaver is configured to use the "Simple locker" instead of "Desktop Widgets".
Comment 4 Chaoting Liu 2013-10-22 12:05:35 UTC
it happens again on 4.11.2
my system is Chakra x64
Comment 5 Chris Xiong 2013-12-29 06:14:57 UTC
I have the same problem on 4.11.3@debian sid x86_64
Comment 6 Chris Xiong 2014-01-25 04:26:03 UTC
I reinstalled debian twice recently, first with live cd then with net inst iso.
The problem happens immediately after both installations.
After setting the screen locker to "Desktop Widgets", I pressed the shortcut for locking session.
Then everything froze. I have to execute "killall Xorg" in tty and login again.
Exactly the same, if I use "Simple locker", everything works properly.
However I just need the clock when screen is locked...
Comment 7 Ryan K 2014-01-30 18:19:53 UTC
I'm also seeing this on Kubuntu 13.10 x64 with Intel Haswell graphics. 

For me, the "simple locker" works but the graphics are corrupt - some of the text is illegible and there are white boxes covering a portion of the unlock dialog.
Comment 8 Nate Graham 2018-06-08 19:00:05 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham