Bug 200458 - Leave note plasmoid locks up the screensaver + leave notes plasmoid
Summary: Leave note plasmoid locks up the screensaver + leave notes plasmoid
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma4
Classification: Unmaintained
Component: screensaver overlay (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-16 17:12 UTC by Diederik van der Boor
Modified: 2010-09-07 07:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Diederik van der Boor 2009-07-16 17:12:47 UTC 
Version:           onbekend (using 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) "release 142", KDE:KDE4:Factory:Desktop / openSUSE_11.0)
Compiler:          gcc
OS:                Linux (i686) release 2.6.25.20-0.4-default

The "leave a note" plasmoid seams to freeze up. After leaving a note, the screensaver no longer accepts mouse input.

Killing the screensaver application (kflux.kss in my case) from the console seams to fix it.
Comment 1 Kolia 2010-01-03 02:17:04 UTC 
Hi,

Can you please details the steps to reproduce the problem? It does not seem very clear to me :)

Thanks!
Comment 2 Diederik van der Boor 2010-01-03 20:57:35 UTC 
To reproduce (KDE 4.3.4)
- configure the screensaver to allow "widgets on the screensaver"
- add a "leave a note" plasmoid to the screensaver.
- leave two notes within the same minute/second.

Behind the screensaver, the note tool will prompt the user to "rename the title for this note". The screensaver application itself won't receive user input anymore (e.g. a mousemove/keypress to unlock it).

The only way to leave the screensaver, is by killing it from the virtual terminal (Ctrl+Alt+F1, login, killall -9 "screensavername.kss")
Comment 3 George Kiagiadakis 2010-01-04 00:50:23 UTC 
I can reproduce this too on 4.3.4 with the steps from comment 2.