| Summary: | Black screen with cursor after upgrade to Plasma 6.0 | ||
|---|---|---|---|
| Product: | [KDE Neon] neon | Reporter: | matz908 <bhend-matz> |
| Component: | general | Assignee: | Neon Bugs <neon-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | grave | CC: | carlosd.kde, jr, kde, nate, neon-bugs-null, nicolas.fella, sitter |
| Priority: | NOR | Keywords: | qt6 |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
new journalctl log after the newest updates
This is the output from the apt commands suggested by Harald Sitter |
||
|
Description
matz908
2024-03-01 14:47:58 UTC
Does this still happen after applying latest updates? Created attachment 166272 [details]
new journalctl log after the newest updates
(In reply to Nicolas Fella from comment #1) > Does this still happen after applying latest updates? Yes it is still happening. I added my journalctl logs that I took after the update Thanks. It looks like you have a weird mix of Plasma 5 and 6 installed Is there a way to fix that? other than a fresh install? What's the output of sudo apt update sudo apt -o Debug::pkgProblemResolver=true dist-upgrade Created attachment 166313 [details]
This is the output from the apt commands suggested by Harald Sitter
I added the output. It seems that there is one package broken. I'm not sure how I should progress now. Comment on attachment 166313 [details] This is the output from the apt commands suggested by Harald Sitter >Hit:1 http://packages.microsoft.com/repos/code stable InRelease >Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease >Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease >Get:4 http://archive.neon.kde.org/user jammy InRelease [194 kB] >Hit:5 https://repo.waydro.id jammy InRelease >Hit:6 https://ppa.launchpadcontent.net/danielrichter2007/grub-customizer/ubuntu jammy InRelease >Hit:7 https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu jammy InRelease >Ign:8 http://packages.linuxmint.com ulyssa InRelease >Hit:9 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease >Hit:10 http://security.ubuntu.com/ubuntu jammy-security InRelease >Hit:11 http://packages.linuxmint.com ulyssa Release >Fetched 194 kB in 1s (215 kB/s) >Reading package lists... >Building dependency tree... >Reading state information... >5 packages can be upgraded. Run 'apt list --upgradable' to see them. >Reading package lists... >Building dependency tree... >Reading state information... >Calculating upgrade... >The following packages have been kept back: > libdecor-0-0 libdecor-0-plugin-1-cairo libsdl2-2.0-0 plasma-desktop > plasma-desktop-data >0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. >Starting pkgProblemResolver with broken count: 1 >Starting 2 pkgProblemResolver with broken count: 1 >Investigating (0) plasma-desktop:amd64 < 4:5.27.10-0xneon+22.04+jammy+release+build47 @ii umH Ib > >Broken plasma-desktop:amd64 Depends on plasma-desktop-data:amd64 < 4:5.27.10-0xneon+22.04+jammy+release+build47 >-> 4:6.0.0-0xneon+22.04+jammy+release+build52 @ii umU > (= 4:5.27.10-0xneon+22.04+jammy+release+build47) > Considering plasma-desktop-data:amd64 104 as a solution to plasma-desktop:amd64 5310 > Added plasma-desktop-data:amd64 to the remove list > Fixing plasma-desktop:amd64 via keep of plasma-desktop-data:amd64 > Try to Re-Instate (0) plasma-desktop-data:amd64 >Done >Entering ResolveByKeep Hi. Can you confirm this is no longer an issue. Several rounds of updates have been released since that the packaging has been rectified. Indeed, and if it's not fixed yet, it's very likely Bug 483163. I can't confirm that the bug is now fixed, as it annoyed me so much that I made a new installation on my system. I looked at Bug483163, and it's not the same behavior. My blank screen came up when I was in the session and not in the lock screen. The lock screen worked fine. confirmed to be be fixed by original reporter |