tl;dr After running Kubuntu 16.04 for years on a vanilla Dell desktop, I upgraded to 18.04, but on booting the computer freezes at the splash screen. After great effort I managed to achieve a terminal login. I want to get my computer upgraded all the way to 22.04. Should I try to fix this botched upgrade before proceeding, or try a command-line upgrade to 20.04 and hope the problem goes away?
The only clue I could find about what might be causing the freeze is entries in the .xsession-errors file:
Detail:
Computer freezes at splash screen showing only the word "Kubuntu". I tried getting a terminal prompt by hitting ctrl-alt-f2, but only got a blinking cursor.
I thought it was a boot loader issue, so I got a live USB with boot-repair and had it do the recommended repair. This made no change except now I see the grub screen at startup instead of going straight to the splash screen.
I edited the grub entry by following the directions at: itsfoss com/fix-ubuntu-freezing/. Tried "nomodeset" , then "nouveau.noaccel=1"
No change until I tried "noapic noacpi nosplash irqpoll" which got me to a terminal login. Trying "startx" had no effect and created no error notifications in xsession-errors.
I copied and pasted the messages above from error output generated from previous boot attempts.
Any idea why an upgrade that should have been routine on a very plain desktop that had been running 16.04 without issues for years would fail so badly? Any ideas for a fix? I want to get eventually to 22.04. Should I try a command-line upgrade to 20.04 and hope that solves things?
The only clue I could find about what might be causing the freeze is entries in the .xsession-errors file:
Code:
Menu "applications-kmenuedit.menu" not found.
The desktop entry file "/usr/share/applications/org.kde.drkonqi.desktop" has Type= "Application" but no Exec line
kf5.kservice.sycoca: Invalid Service : "/usr/share/applications/org.kde.drkonqi.desktop"
The desktop entry file "/usr/share/applications/org.kde.systemmonitor.desktop" has Type= "Application" but no Exec line
kf5.kservice.sycoca: Invalid Service : "/usr/share/applications/org.kde.systemmonitor.desktop"
Saving
kf5.kded: Could not load kded module "plasmavault":"The plugin '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kded/plasmavault.so' uses incompatible Qt library. (5.9.5) [release]" (library path was:"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kded/plasmavault.so")
kf5.kded: Could not load kded module "colord":"The shared library was not found." (library path was:"colord")
Currrent active notifications: QHash(("notification 7", "KDE DaemonSystem Notification Helper"))
Guessing partOf as: 7
New Notification: "System Notification Helper" "A system restart is needed to complete the update process" 10000 & Part of: 7
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:115:23: QML Text: Binding loop detected for property "height"
should recheck... QProcess(0x376e0d0) 0
None
None
PolicyKit daemon disconnected from the bus.
We are no longer a registered authentication agent.
The X11 connection broke (error 1). Did the X11 server die?
Detail:
Computer freezes at splash screen showing only the word "Kubuntu". I tried getting a terminal prompt by hitting ctrl-alt-f2, but only got a blinking cursor.
I thought it was a boot loader issue, so I got a live USB with boot-repair and had it do the recommended repair. This made no change except now I see the grub screen at startup instead of going straight to the splash screen.
I edited the grub entry by following the directions at: itsfoss com/fix-ubuntu-freezing/. Tried "nomodeset" , then "nouveau.noaccel=1"
No change until I tried "noapic noacpi nosplash irqpoll" which got me to a terminal login. Trying "startx" had no effect and created no error notifications in xsession-errors.
I copied and pasted the messages above from error output generated from previous boot attempts.
Any idea why an upgrade that should have been routine on a very plain desktop that had been running 16.04 without issues for years would fail so badly? Any ideas for a fix? I want to get eventually to 22.04. Should I try a command-line upgrade to 20.04 and hope that solves things?
Comment