Bug 246133 - plasmoids not shown over screensaver
Summary: plasmoids not shown over screensaver
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: screensaver overlay (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 227338 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-07-29 10:37 UTC by Antonio Rojas
Modified: 2010-10-06 10:34 UTC (History)
5 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 Antonio Rojas 2010-07-29 10:37:54 UTC 
Version:           unspecified (using KDE 4.4.95) 
OS:                Linux

Plasmoids are not shown over the screensaver since updating to 4.5. If i select "configure plasmoids" in the screensaver KCM I just get a screensaver preview without any configuration dialog. 
The plasmoids are only shown when the "unlock screen" dialog appears.

Reproducible: Always
Comment 1 tnemeth 2010-08-22 09:30:06 UTC 
I can confirm this too.

After I upgraded to KDE SC 4.5.0 in Kubuntu 10.04, not only was I not able to
add plasmoids to the screensaver in the screensaver KCM (although it was
possible from the screensaver itself when running) but also the plasmoid I
added (analog clock) was not fully displayed.
Comment 2 whashnez 2010-08-27 11:24:47 UTC 
I can confirm exactly this too. Here is my post in KDE community forums:
http://forum.kde.org/viewtopic.php?f=67&t=89827&p=168477#p168477
Comment 3 whashnez 2010-08-31 19:25:13 UTC 
Not resolved in KDE 4.5.1
Comment 4 Kai Uwe Broulik 2010-09-02 03:46:46 UTC 
Yep, I can neither add or configure the widgets as triggering the configurable screen saver either makes the system crash or I cannot do anything but hammering on escape till the screensaver finally diappers after like 30 seconds.
Also plasmoids are not displayed anymore.
Comment 5 Chani 2010-09-07 07:32:27 UTC 
whoops, somehow this BR didn't reach me until today - however, I've known about the problem and fixed it a couple of days ago. :)
it'l be in... 4.5.2..?

tnemeth: the analog clock is a separate problem, been around for ages and still nobody knows what's causing it :/
Comment 6 Chani 2010-09-07 07:41:54 UTC 
*** Bug 227338 has been marked as a duplicate of this bug. ***
Comment 7 tnemeth 2010-09-07 13:14:09 UTC 
(In reply to comment #5)
> tnemeth: the analog clock is a separate problem, been around for ages and still
> nobody knows what's causing it :/

    It used to work perfectly in 4.4.x... At least for me :)
Comment 8 whashnez 2010-10-06 10:34:04 UTC 
Fixed in 4.5.2