SUMMARY Apparently it becomes impossible to use an image as wallpaper if it has a name that coincides with one of the built-in wallpapers'. STEPS TO REPRODUCE 1. Load a wallpaper with the name of `elarun.png` (as an example) 2. Set the wallpaper to elarun (note: not the Elarun wallpaper that comes with Plasma wallpapers but the elarun.png you loaded) and click on Apply 3. The default Plasma wallpaper (Shell) loads instead of elarun.png OBSERVED RESULT The default Plasma wallpaper (Shell) loads instead of elarun.png EXPECTED RESULT elarun.png should be loaded SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Linux linux 5.4.61-rt37-1-rt-lts #1 SMP PREEMPT_RT Sat, 12 Sep 2020 21:01:23 +0000 x86_64 GNU/Linux/5.19.90 (available in About System) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION I would suggest to **not** close the issue only because there already is an Elarun wallpaper bundled with Plasma. Furthermore, what if I add a wallpaper that by coincidence has an identical name?
I can imagine that happening, we have another requirement to load the correct resolution of a package if the screen changes. For this we deliberately do not store the full file path in the config. I changed that this release. Though when trying, I couldn't reproduce the bug. The custom image always got saved as a full path. Can I have your ~/.config/plasma-org.kde.plasma.desktop-appletsrc after choosing your custom elarun.png? Is the preview also broken? Are you sure you selected the right Elarun in the config UI?
Created attachment 131996 [details] after setting elarun.png
Preview not broken, however.
Weird, the only images saved in that config are: Image=file:///usr/share/wallpapers/Kokkini/contents/images/3840x2160.png Image=file:///home/reporter/overscan.png Image=file:///home/reporter/tildearrowback.png Image=file:///usr/share/wallpapers/Next/contents/images/3840x2160.jpg Image=file:///usr/share/wallpapers/Path/contents/images/2560x1440.jpg
Requested information was provided; changing status.
Can you test 5.26 to see if the bug is still reproducible?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!