Bug 362534 - Plasma Black Screens after crashing during update to Ubuntu 16
Summary: Plasma Black Screens after crashing during update to Ubuntu 16
Status: RESOLVED BACKTRACE
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Engine (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-05-01 10:23 UTC by ph4sesaber
Modified: 2020-10-26 16:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ph4sesaber 2016-05-01 10:23:47 UTC
Application: krunner (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-21-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
A notification popped up that there was a new Ubuntu version out.
The update was taking a while to process, so I started doing other things.
All the files had downloaded and it was in the process of installing them (about
90% complete). This is when I decided to open I saw that the update was going
to take a long time, so I hit Ctrl+Alt+L to lock my screen. Something triggered
Plasma to crash, and the crash report box appeared, except I couldn't close it
because my mouse and keyboard both stopped working. After a while of
fiddling with it, I decided to restart my computer.

I entered my disk encryption password and was greeted with a black screen.
I'm able to access TTYs, so I tried running some commands.
`dpkg --configure -a` ran through the packages, and I noticed some error
with Qt or KDE, I'm not sure which one. I removed ~/.cache and ~/.kde (copied
elsewhere), and running kbuildsyscocoa5 && startx brought up a popup that
says:

"All shell packages missing.
This is an installation issue, please contact your distribution,"

another box saying the system tray couldn't load, and this Crash Reporting
Assistant.

The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

Possible duplicates by query: bug 362377, bug 362265, bug 362088, bug 361975, bug 361929.

Reported using DrKonqi
Comment 1 Nate Graham 2020-10-26 16:49:40 UTC
Can't do anything without a backtrace of the crash, sorry. However most Baloo crashes have been fixed in the last four and a half years, and I strongly suspect this one has too.