| Summary: | The wallpapers reset after a feature version upgrade | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Répási Dávid <hu.repasidavid> |
| Component: | Image & Slideshow wallpaper plugins | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | nate, notmart, qydwhotmail |
| Priority: | NOR | ||
| Version First Reported In: | 6.4.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | EndeavourOS | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Répási Dávid
2025-10-02 21:14:22 UTC
This is definitely not intended. The usual way this happens is when the wallpaper is not available anymore; in this case, the system falls back to the default one. Was your custom wallpaper located on a location that might have been inaccessible at the time you upgraded? I'm familiar with that fallback method, since I can't set a wallpaper from an external disk (which is not set to auto mount) and survive a reboot, because plasma doesn't copy current wallpapers to a dedicated folder for them for as long as they are set (windows does it this way, but it also automounts whatever it can, oh well, windows is weird) Because of that experience I started keeping my wallpapers in /$USER/Pictures/, so that can't be the issue. In the linked fedora post, the user mentions he used a network drive, that may have caused the issue in his case. Sadly/ thankfully this is a rare issue, and because of that its hard to test, but also pretty easy to just re-set my wallpapers. I shall try to test this feature cycle and get a distro iso with 6.4, install that and upgrade it in a vm to 6.5, if it reproduces there as well, at least there will be something to grab onto. I will also be checking out two systems (both endeavour) that have plasma on them, see if it happens there as well! 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME. |