Bug 413103

Summary:	Slideshow on screenlocker shows same image on all monitors
Product:	[Plasma] kscreenlocker	Reporter:	Paul Lemmons <paul.lemmons>
Component:	greeter	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bhush94, katyaberezyaka, nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Paul Lemmons 2019-10-17 17:39:25 UTC

SUMMARY

When the screen locker is evoked the slideshow shows the same image on all monitors. This is a new behavior since my upgrade from 5.16 to 5.17. Prior to the upgrade, each screen would get a different image. 

STEPS TO REPRODUCE
1. Configure the screen locker to display a slideshow
2. Lock the screen on a system with multiple monitors

OBSERVED RESULT

The image on all monitors is the same image

EXPECTED RESULT

Each monitor should show a different random image

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Kubuntu 19.10 + backports
KDE Plasma Version: 5.17.0
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION

Comment 1 Paul Lemmons 2019-12-12 20:08:52 UTC

Problem persists in:

KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.4

Comment 2 Nate Graham 2021-06-21 22:54:05 UTC


*** This bug has been marked as a duplicate of bug 409226 ***

Comment 3 Paul Lemmons 2021-06-22 15:32:13 UTC

I have read bug 409226 and I cannot honestly see how it relates. It has to do with the greeter presenting a place to log in on multiple monitors. This bug had to do with the slide show showing the same image on each monitor instead of a different image on each monitor. 

I realize that the greeter works in tandem with the slide show and that this "bug", as well as the other, is one of personal taste as opposed to something actually being broken. But if ever there is a chance that the image could be different on multiple monitors in the slide show, I would not want this request to be lost by being closed as a duplicate of another simi-related bug that does not imply the intent of this request.

Please consider re-opening this bug.