Bug 482067 - No wallpaper after upgrading from 5.27 to 6.0
Summary: No wallpaper after upgrading from 5.27 to 6.0
Status: RESOLVED NOT A BUG
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-02-29 17:51 UTC by mattias.lundahl
Modified: 2024-03-01 18:20 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description mattias.lundahl 2024-02-29 17:51:46 UTC 
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
I upgraded from 5.27 to 6.0 using Discover and after a reboot there is no wallpaper.

STEPS TO REPRODUCE
1. Upgrade from 5.27 to 6.0 via Discover
2. Reboot
3. Log in

OBSERVED RESULT
There is no wallpaper on any monitor

EXPECTED RESULT
There should be a wallpaper on both my external monitors like I had in 5.27

SOFTWARE/OS VERSIONS
Linux: 6.5
KDE Plasma Version: 6.0
KDE Frameworks Version: 6.0
Qt Version: 6.6

ADDITIONAL INFORMATION
Booting from the latest Neon User ISO works as expected
Comment 1 Harald Sitter 2024-03-01 17:19:57 UTC 
What happens if you run

pkcon refresh
pkcon update
Comment 2 mattias.lundahl 2024-03-01 17:34:26 UTC 
(In reply to Harald Sitter from comment #1)
> What happens if you run
> 
> pkcon refresh
> pkcon update

I ran those commands about an hour ago and got several updated packages. After rebooting, I still experience this bug.
Comment 3 mattias.lundahl 2024-03-01 18:17:53 UTC 
I uninstalled the Nvidia driver according to this page:

https://linuxconfig.org/how-to-uninstall-the-nvidia-drivers-on-ubuntu-22-04-jammy-jellyfish-linux

After rebooting, I now see the correct wallpaper. From my point of view, this bug can be closed now.