SUMMARY I have installed Plasma 6.2 and the desktop as well as the lock screen both get the new wallpaper, but SDDM still has the 6/0 wallpaper. When I go into the SDDM settings in System Settings, the Info button shows the new wallpaper, while the set background button shows the 6.0 wallpaper. I can set the background to the new wallpaper, and while the SDDM settings page is open, the setting is remembered. As soon as I leave the SDDM settings page and go back to it however, the wallpaper goes back to the 6.0 wallpaper. That is also what I get when I reboot the computer. I tried looking in /etc/sddm.conf/, but the file there doesn't explicitly point to any wallpaper. STEPS TO REPRODUCE 1. Install Plasma 6.2 2. Set the new wallpaper in the SDDM settings page 3. Reboot the computer 4. The 6.0 wallpaper is shown by SDDM OBSERVED RESULT The 6.0 wallpaper is used by SDDM EXPECTED RESULT The new wallpaper should be used by SDDM SOFTWARE/OS VERSIONS Linux: 6.8.0 KDE Plasma Version: 6.2 KDE Frameworks Version: 6.6 Qt Version: 6.7.2 ADDITIONAL INFORMATION
You probably have a malformed theme.conf.user in your /usr/share/sddm/themes/breeze folder. This overrides the entries in /usr/share/sddm/themes/breeze/theme.conf The default in theme.conf should be something like background=/usr/share/wallpapers/Next/contents/images/5120x2880.png. This will ensure that the current wallpaper is used. Move the theme.conf.user file to another location, log out and see if the current wallpaper is now used.
(In reply to Martin Schnitkemper from comment #1) > You probably have a malformed theme.conf.user in your > /usr/share/sddm/themes/breeze folder. This overrides the entries in > /usr/share/sddm/themes/breeze/theme.conf > > The default in theme.conf should be something like > background=/usr/share/wallpapers/Next/contents/images/5120x2880.png. This > will ensure that the current wallpaper is used. > > Move the theme.conf.user file to another location, log out and see if the > current wallpaper is now used. Yes, that solved the problem. I will close this bug now.