Bug 191512

Summary:	name of wallpaper stored in plasma-appletsrc
Product:	[Unmaintained] plasma4	Reporter:	chepioq <chepioq>
Component:	wallpaper-image	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	asraniel, kde, lasse.liehu, vasyl.demin
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description chepioq 2009-05-03 21:19:11 UTC

Version:            (using KDE 4.2.2)
Installed from:    Fedora RPMs

I use conky with kde 4, and for have pseudo transparency with conky I use a script, this script use the name of wallpaper in plasma-appletsrc file.
This work fine with kde 4.2.1, but with kde 4.2.2, when I change my wallpaper the fist time the name of new wallpaper appear after 30 second in plasma-appletsrc (wallpaper=/home/dominique/Images/leonidas-1-noon-normal.jpg, for example), and it is normal; but when I change for a second wallpaper, the name of this new wallpaper don't appear in plasma-appletsrc (I wait for 10 minutes and nothing appear).
If I restart my session, the name of this new wallpaper is in plasma-appletsrc.
It is uncomfortable for my conky.
And I have a just a question:
Where is stored the name of current wallpaper between the time where I change the wallpaper and when this name appear in plasma-appletsrc ?

Comment 1 chepioq 2009-05-05 20:53:07 UTC

Hi
Nobodies have same issues?...

Comment 2 Beat Wolf 2009-10-21 15:31:32 UTC

Sounds like the autosave of plasmasrc has a problem here.
Is this still an issue for 4.3?

Comment 3 Vasyl Demin 2009-11-30 01:46:08 UTC

Same problem
Arch Linux i686, KDE 4.3.3

Comment 4 Lasse Liehu 2010-01-02 15:36:45 UTC

The issue is still present in KDE 4.4 beta 2, Qt 4.6.0 (OpenSUSE 11.2 packages). The wallpaper config was in plasma-desktop-appletsrc.

Comment 5 Nicolas L. 2010-06-07 08:21:55 UTC

I just tested in kde 4.4 and after changing about 10 times the wallpaper the line Wallpaper= is changed after some seconds each time


Please reopen if this bug is still valid for you