I’ve been trying for days. So, I am wondering if the repo is broken on the Neon teams end. I get this in Discover any time I try to update:
Dependency resolution failed:
The following packages have unmet dependencies: neon-adwaita: Breaks: adwaita-icon-theme Breaks: humanity-icon-theme but 0.6.16 is to be installed Breaks: ubuntu-mono but 24.04-0ubuntu1 is to be installed Breaks: adwaita-icon-theme pipewire-audio: Conflicts: pulseaudio Conflicts: pulseaudio pipewire-alsa: Conflicts: pulseaudio Conflicts: pulseaudio
Both of these issues have been reported in the KDE Bug Tracker. The part that’s related to pulseaudio/pipewire is discussed here (with a seemingly effective work-around)
The one related to adwaita (or at least a similar one) is discussed here, not sure if the workarounds apply to your case:
I ran this from that: sudo pkcon update neon-desktop
That removed the conflicting packages.
Then I ran the standard pkcon update. And that screwed up my system. The desktop wouldn’t load.
Fortunately, I was able to restore from a backup I made earlier this week with Rescuezilla…
Yeah, I don’t trust this update at all now. So, next time I attempt it, without any hacky workarounds, I am just going to run it on a spare laptop with the same image as my desktop.
I’ll happily wait a month or two until this is sorted out officially. I’ll just stick to keeping my Flatpak apps updated for now. I absolutely getting stressed out when my main PC is ever down.
Sorry to hear of the extra hassle. But I believe the desktop startup might be a separate issue with this update. It appears that Neon is in the process of switching the desktop login from SDDM to plasmalogin. Supposedly one can re-install SDDM if you want to go back to that, or enable plasmalogin using
sudo systemctl enable plasmalogin
Alternately, assuming your system boots into a TTY you can log in and start Plasma using
XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
Hope this helps. Yes, overall it seems this update has had a few more serious bumps in the road than previous updates.
Well, I was presented with a login screen. I type in the password, and the desktop wouldn’t load after that. I assume that plasmalogin service was running.
Anyway, until it works without me having to tinker, I’m going to hold off. Besides, I have no need for newer features from the modern update. So, I’m in no rush.
What makes me wonder why they replacing SDDM with that plasmalogin. SDDM has worked great.
No wonder I went back to the flip phone and MP3 player. I got tired of keeping apps up-to-date on the smartphone. Less maintenance in my life. Less headaches.
But I’ll test this on a spare laptop with my backup image of my main PC on it periodically before I think about trying to update any of my other PCs again.
I think there is a mesa stack mismatch issue going on with packaging on KDE Neon.
But I restored my desktop image to a spare laptop with Intel graphics, and the upgrade worked there (after deselecting the conflicting packages in Discover).
So, I took a chance again on my main PC. But with my AMD rig with the RX 580, it doesn’t work.
My desktop won’t even load. Wayland gives me a black screen with no display output. And if I try X11, it’s a black screen with the cursor just showing.
When I ran this command: journalctl -b | grep -i drm
It said something like no suitable DRM backend
So, yeah. I’m not upgrading for a long time. This upgrade is just too iffy.
If it’s a repo issue like mentioned, testing on spare hardware with the same image probably won’t actually show you whether it’ll work — you’d just hit the same dependency errors on both machines.
But it’s weird. When I use the latest live USB image of Neon on my main rig, the desktop loads perfectly.
So, I don’t know what’s going on. I’m just going to leave it.
Maybe after a week, I’ll make another backup and then try the upgrade again when 6.7.3 drops.
I don’t think this is a binding issue with VFIO regarding my GPU pass through setup with the secondary Nvidia card. But I’ve added these to /etc/initramfs-tools/modules file just in case:
vfio
vfio_pci
vfio_iommu_type1
vfio_virqfd
But if 6.7.3 fixes this problem, I know it was likely the KWin/DRM side of things that was giving me trouble.
icon theme stuff is pretty low stakes honestly, but the pipewire+plasmalogin changes are the real question marks - that’s what’ll actually break things if it breaks at all.
Doesn’t seem like it. Because when I make a backup of my current install, and restore it to a laptop running Intel graphics, the upgrade works fine. I just need to uncheck the conflicting packages and it works.
My desktop with the AMD graphics is the issue when it comes to upgrading. It’s likely an ongoing issue with KWin/DRM that hasn’t been resolved in my case when it comes to some older AMD Polaris cards, like my RX 580.
Unfortunately for me, it seems like I got the short end of the stick in this regard.
Yup. Happens on an AMD laptop with an exact copy of my system drive with 6.7.3 also:
Jul 16 13:36:47 my-pc kernel: ACPI: bus type drm_connector registered
Jul 16 13:36:47 my-pc kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
Jul 16 13:36:47 my-pc kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
Jul 16 13:36:47 my-pc kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
Jul 16 13:36:47 my-pc systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
Jul 16 13:36:48 my-pc systemd[1]: modprobe@drm.service: Deactivated successfully.
Jul 16 13:36:48 my-pc systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
Jul 16 13:37:13 my-pc kernel: amdgpu 0000:00:01.0: [drm] ATOM BIOS: 113-C91400-005
Jul 16 13:37:13 my-pc kernel: amdgpu 0000:00:01.0: [drm] UVD is enabled in physical mode
Jul 16 13:37:13 my-pc kernel: amdgpu 0000:00:01.0: [drm] VCE enabled in VM mode
Jul 16 13:37:13 my-pc kernel: amdgpu 0000:00:01.0: [drm] Detected VRAM RAM=512M, BAR=512M
Jul 16 13:37:13 my-pc kernel: amdgpu 0000:00:01.0: [drm] RAM width 64bits UNKNOWN
Jul 16 13:37:13 my-pc kernel: amdgpu 0000:00:01.0: [drm] GART: num cpu pages 262144, num gpu pages 262144
Jul 16 13:37:13 my-pc kernel: amdgpu 0000:00:01.0: [drm] PCIE GART of 1024M enabled (table at 0x000000F400600000).
Jul 16 13:37:13 my-pc kernel: amdgpu 0000:00:01.0: [drm] Found UVD firmware Version: 1.43 Family ID: 15
Jul 16 13:37:13 my-pc kernel: amdgpu 0000:00:01.0: [drm] UVD ENC is disabled
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: values for Engine clock
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 200000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 300000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 400000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 496560
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 600000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 685720
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 757900
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 800000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: Validation clocks:
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: engine_max_clock: 80000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: memory_max_clock: 93300
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: level : 8
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: values for Display clock
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 300000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 400000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 496560
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 626090
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 685720
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 757900
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 800000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 847060
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: Validation clocks:
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: engine_max_clock: 80000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: memory_max_clock: 93300
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: level : 8
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: values for Memory clock
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 667000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: 933000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: Validation clocks:
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: engine_max_clock: 80000
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: memory_max_clock: 93300
Jul 16 13:37:13 my-pc kernel: [drm] DM_PPLIB: level : 8
Jul 16 13:37:13 my-pc kernel: amdgpu 0000:00:01.0: [drm] Display Core v3.2.369 initialized on DCE 11.0
Jul 16 13:37:13 my-pc kernel: amdgpu 0000:00:01.0: [drm] UVD initialized successfully.
Jul 16 13:37:14 my-pc kernel: amdgpu 0000:00:01.0: [drm] VCE initialized successfully.
Jul 16 13:37:14 my-pc kernel: amdgpu 0000:00:01.0: [drm] Using custom brightness curve
Jul 16 13:37:14 my-pc kernel: amdgpu 0000:00:01.0: [drm] Registered 2 planes with drm panic
Jul 16 13:37:14 my-pc kernel: [drm] Initialized amdgpu 3.64.0 for 0000:00:01.0 on minor 1
Jul 16 13:37:14 my-pc kernel: fbcon: amdgpudrmfb (fb0) is primary device
Jul 16 13:37:14 my-pc kernel: amdgpu 0000:00:01.0: [drm] fb0: amdgpudrmfb frame buffer device
Jul 16 13:38:00 my-pc kwin_wayland[1828]: No backend specified, automatically choosing drm
Jul 16 13:38:00 my-pc kwin_wayland[1828]: Failed to open drm device /dev/dri/card1
Jul 16 13:38:01 my-pc kwin_wayland[1898]: Failed to open drm node /dev/dri/renderD128: Permission denied
Jul 16 13:38:01 my-pc kwin_wayland[1898]: No backend specified, automatically choosing drm
Jul 16 13:38:01 my-pc kwin_wayland[1898]: Failed to open drm device /dev/dri/card1
Jul 16 13:38:01 my-pc kwin_wayland[1907]: Failed to open drm node /dev/dri/renderD128: Permission denied
Jul 16 13:38:01 my-pc kwin_wayland[1907]: No backend specified, automatically choosing drm
Jul 16 13:38:01 my-pc kwin_wayland[1907]: Failed to open drm device /dev/dri/card1
Jul 16 13:38:01 my-pc kwin_wayland[1919]: Failed to open drm node /dev/dri/renderD128: Permission denied
Jul 16 13:38:01 my-pc kwin_wayland[1919]: No backend specified, automatically choosing drm
Jul 16 13:38:01 my-pc kwin_wayland[1919]: Failed to open drm device /dev/dri/card1
Jul 16 13:38:02 my-pc kwin_wayland[1923]: Failed to open drm node /dev/dri/renderD128: Permission denied
Jul 16 13:38:02 my-pc kwin_wayland[1923]: No backend specified, automatically choosing drm
Jul 16 13:38:02 my-pc kwin_wayland[1923]: Failed to open drm device /dev/dri/card1
Jul 16 13:38:02 my-pc kwin_wayland[1926]: Failed to open drm node /dev/dri/renderD128: Permission denied
Jul 16 13:38:02 my-pc kwin_wayland[1926]: No backend specified, automatically choosing drm
Jul 16 13:38:02 my-pc kwin_wayland[1926]: Failed to open drm device /dev/dri/card1
Jul 16 13:38:02 my-pc kwin_wayland[1934]: Failed to open drm node /dev/dri/renderD128: Permission denied
Jul 16 13:38:02 my-pc kwin_wayland[1934]: No backend specified, automatically choosing drm
Jul 16 13:38:02 my-pc kwin_wayland[1934]: Failed to open drm device /dev/dri/card1
Jul 16 13:38:03 my-pc kwin_wayland[1941]: Failed to open drm node /dev/dri/renderD128: Permission denied
Jul 16 13:38:03 my-pc kwin_wayland[1941]: No backend specified, automatically choosing drm
Jul 16 13:38:03 my-pc kwin_wayland[1941]: Failed to open drm device /dev/dri/card1
Jul 16 13:38:03 my-pc kwin_wayland[1943]: Failed to open drm node /dev/dri/renderD128: Permission denied
Jul 16 13:38:03 my-pc kwin_wayland[1943]: No backend specified, automatically choosing drm
Jul 16 13:38:03 my-pc kwin_wayland[1943]: Failed to open drm device /dev/dri/card1
Jul 16 13:38:03 my-pc kwin_wayland[1945]: Failed to open drm node /dev/dri/renderD128: Permission denied
Jul 16 13:38:03 my-pc kwin_wayland[1945]: No backend specified, automatically choosing drm
Jul 16 13:38:03 my-pc kwin_wayland[1945]: Failed to open drm device /dev/dri/card1
Jul 16 13:38:03 my-pc kwin_wayland[1947]: Failed to open drm node /dev/dri/renderD128: Permission denied
Jul 16 13:38:03 my-pc kwin_wayland[1947]: No backend specified, automatically choosing drm
Jul 16 13:38:03 my-pc kwin_wayland[1947]: Failed to open drm device /dev/dri/card1
But 6.7.3 works on the Intel laptop.
Until, my current install boots up without an issue on the AMD laptop, I am not ever thinking of updating to 6.7.x.