Summary: | Screen locking not working after upgrading from 5.27 to 6.0 | ||
---|---|---|---|
Product: | [KDE Neon] neon | Reporter: | mattias.lundahl |
Component: | Packages User Edition | Assignee: | Neon Bugs <neon-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | jr, neon-bugs, sitter |
Priority: | NOR | Keywords: | qt6 |
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
mattias.lundahl
2024-02-29 18:07:34 UTC
What happens if you run pkcon refresh pkcon update (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. I'd like to see the output. (In reply to Harald Sitter from comment #3) > I'd like to see the output. I see the following when running them now: mattias@XPS15:~$ sudo pkcon refresh Refreshing cache [=========================] Loading cache [=========================] Downloading update information [=========================] Running [=========================] Finished [=========================] Enabled http://archive.ubuntu.com/ubuntu jammy InRelease Enabled http://security.ubuntu.com/ubuntu jammy-security InRelease Enabled http://archive.ubuntu.com/ubuntu jammy-updates InRelease Enabled http://archive.neon.kde.org/user jammy InRelease Enabled http://archive.ubuntu.com/ubuntu jammy InRelease Enabled https://apt.svtplay-dl.se svtplay-dl InRelease Enabled https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu jammy InRelease Enabled https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease Enabled http://security.ubuntu.com/ubuntu jammy-security InRelease Enabled http://archive.ubuntu.com/ubuntu jammy-updates InRelease Enabled http://archive.neon.kde.org/user jammy InRelease Enabled https://apt.svtplay-dl.se svtplay-dl InRelease Enabled https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu jammy InRelease Enabled https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease mattias@XPS15:~$ sudo pkcon update Getting updates [=========================] Finished [=========================] No packages require updating to newer versions. Enabled https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu jammy InRelease Pretty sure we don't support that. What you can try is to do the following: sudo apt update sudo apt install neon-desktop plasma-desktop neon-settings-2 sudo apt update sudo apt dist-upgrade Should that not change anything please paste the output again :) (In reply to Harald Sitter from comment #5) > Enabled > https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu jammy InRelease > > Pretty sure we don't support that. > > What you can try is to do the following: > > sudo apt update > sudo apt install neon-desktop plasma-desktop neon-settings-2 > sudo apt update > sudo apt dist-upgrade > > Should that not change anything please paste the output again :) I get the following (since it doesn't seem to install anything, I haven't rebooted afterwards): mattias@XPS15:~$ sudo apt update Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease Get:2 http://archive.neon.kde.org/user jammy InRelease [189 kB] Hit:3 https://apt.svtplay-dl.se svtplay-dl InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:5 https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu jammy InRelease Hit:6 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease Hit:7 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Fetched 189 kB in 1s (172 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. mattias@XPS15:~$ sudo apt install neon-desktop plasma-desktop neon-settings-2 Reading package lists... Done Building dependency tree... Done Reading state information... Done neon-desktop is already the newest version (4+p22.04+vrelease+git20240301.1330). neon-settings-2 is already the newest version (0.5+p22.04+vrelease+git20240220.1128). neon-settings-2 set to manually installed. plasma-desktop is already the newest version (4:6.0.0-0xneon+22.04+jammy+release+build52). plasma-desktop set to manually installed. Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. mattias@XPS15:~$ sudo apt update Get:1 http://archive.neon.kde.org/user jammy InRelease [189 kB] Hit:2 https://apt.svtplay-dl.se svtplay-dl InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:5 https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu jammy InRelease Hit:6 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease Hit:7 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Fetched 189 kB in 1s (185 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. mattias@XPS15:~$ sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Entering ResolveByKeep Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I'm inclined to say the graphics PPA is causing graphics problems. https://bugs.kde.org/show_bug.cgi?id=482070 Certainly makes it sound like something is wrong with your graphics driver. (In reply to Harald Sitter from comment #7) > I'm inclined to say the graphics PPA is causing graphics problems. > > https://bugs.kde.org/show_bug.cgi?id=482070 Certainly makes it sound like > something is wrong with your graphics driver. I think you are correct. I followed the instructions here to uninstall the proprietary Nvidia drivers: https://linuxconfig.org/how-to-uninstall-the-nvidia-drivers-on-ubuntu-22-04-jammy-jellyfish-linux After rebooting, it solved the problem I reported in this bug report, so from my point of view this report can be closed now. Cool. Thanks for the update. |