Bug 340408

Summary:	Cannot have multiple Picture Frame widgets with remote content (because of shared cache)
Product:	[Unmaintained] plasma4	Reporter:	MartinG <gronslet>
Component:	widget-frame	Assignee:	Anne-Marie Mahfouf <annma>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description MartinG 2014-10-27 17:50:40 UTC

It is not possible to have two or more Picture Frame widgets with remote content, ie. an "Image" from different urls: When the second picture frame is added, the first one will show the same content as the second (although the settings are still intact).

Reproducible: Always

Steps to Reproduce:
1. Add Picture Frame Widget to desktop, use Image and eg. http://www.yr.no/place/United_States/New_York/New_York/meteogram.png
2. Add new Picture Frame Widget to desktop, use Image and eg. http://www.yr.no/sted/Frankrike/Île-de-France/Paris/meteogram.png


Actual Results:  
Notice that both frames will show the same image.

Expected Results:  
The image that was requested (and that is still reflected by the settings of each of the widgets)

I assume that this is because remote images are being cached to the same file.

Comment 1 Christoph Feck 2014-10-27 19:26:19 UTC

Yep, it uses only m_currentUrl.fileName() for the cached file, see picture.cpp:152.

Comment 2 Christoph Feck 2014-10-27 20:40:43 UTC

https://git.reviewboard.kde.org/r/120829/

Comment 3 Nate Graham 2018-06-08 18:35:56 UTC

Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham