Bug 379580

Summary:	Wallpaper slideshow displays two consecutive images at login.
Product:	[Plasma] plasmashell	Reporter:	Paul <pip.kde>
Component:	Image Wallpaper	Assignee:	Marco Martin <notmart>
Status:	RESOLVED FIXED
Severity:	normal	CC:	nate, notuxius, plasma-bugs
Priority:	NOR
Version:	5.9.5
Target Milestone:	1.0
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Paul 2017-05-06 13:20:56 UTC

When using the wallpaper slideshow two consecutive images are shown at login.

The first image is shown for only a very brief period (blink and you'll miss it), the second image then correctly remains for the duration set by "Change every:", (which in this case is set to 1 hour, 0 minutes, 0 seconds).

The first image appears random, it is not for example the last displayed image.

This is consistent and repeatable.

Comment 1 Paul 2017-11-07 16:13:13 UTC

This appears to be fixed by the patch authored by "Vova Mshanetskiy" in relation to High CPU Utilisation by wallpaper slideshow. 

https://bugs.kde.org/show_bug.cgi?id=381000#c147

Comment 2 Christoph Feck 2017-11-24 00:40:59 UTC

But this patch has not yet been applied, right?

Comment 3 Paul 2017-11-24 12:07:30 UTC

It appears this patch doesn't fix the issue.  It "fixed" it for myself probably due to running on slow elderly hardware :)

See comments:
https://bugs.kde.org/show_bug.cgi?id=381000#c149
https://bugs.kde.org/show_bug.cgi?id=381000#c150

Comment 4 Alexander Mentyu 2018-02-06 18:14:35 UTC

Can reproduce in:

Plasma: 5.11.5
Apps: 17.12.1
Frameworks: 5.42.0
Qt: 5.10.0
Kernel: 4.14.16-1-MANJARO

The first image appears same at login - and then right after the first one - second image is random

Comment 5 Nate Graham 2019-11-14 00:48:23 UTC

Wallpaper processing was massively simplified and improved for 5.17. Can anyone who was originally experiencing this issue still reproduce it in Plasma 5.17?

Comment 6 Paul 2019-11-14 10:12:15 UTC

I've been using a static wallpaper image, but have now switched back to slideshow.

So far (although very limited testing) it seems OK.

Comment 7 Paul 2019-11-16 09:13:20 UTC

OK. I think it is safe to say this does indeed appear to be fixed. :)

Comment 8 Nate Graham 2019-11-16 16:01:10 UTC

Great!