[kde] [Bug 491369] New: Cannot set desktop wallpaper to SVG file since Plasma 6.1.4
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Wed Aug 7 01:27:00 BST 2024
https://bugs.kde.org/show_bug.cgi?id=491369
Bug ID: 491369
Summary: Cannot set desktop wallpaper to SVG file since Plasma
6.1.4
Classification: I don't know
Product: kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: triallax at tutanota.com
Target Milestone: ---
Created attachment 172366
--> https://bugs.kde.org/attachment.cgi?id=172366&action=edit
Sample SVG wallpaper (the dark version of the Chimera Linux wallpaper, licensed
under the CC BY-SA-4.0)
SUMMARY
Since we updated KDE Plasma from 6.1.3 to 6.1.4 for Chimera Linux, SVG
wallpapers have been broken for some reason. Selecting an SVG wallpaper then
pressing apply will save the selection successfully, but the previous wallpaper
will remain displayed on the desktop. This has not been an issue before as far
as we're aware.
STEPS TO REPRODUCE
1. Download the attached SVG file
2. Open system settings
3. Open the "Wallpaper" tab
4. Set the wallpaper type to "Image"
5. Press on "Add...", select the SVG file, then press "Open"
6. Select the SVG wallpaper that was just added, then press "Apply"
OBSERVED RESULT
The previous desktop wallpaper remains on the desktop. If I log out and in, KDE
Plasma stays a lot longer than usual on the loading screen (around 30 seconds
versus the usual 2-3 seconds), and when it does fire up the desktop, the
background is simply black.
EXPECTED RESULT
The wallpaper changes to the selected SVG file without issue.
SOFTWARE/OS VERSIONS
Operating System: Chimera
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.6.44-0-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list