Cannot debug ksplashqml segmentation fault

Asked by Max W Chase

Earlier today, plasmashell stopped working for me on my main user account. I've tried various advice from the internet, but with no luck.

Starting with the first thing that I see, when I log in, I get a black screen and a popup window.
The window is called "ksplashqml --- The KDE Crash Handler", and has two tabs:

In the "General" tab, it says
"We are sorry, ksplashqml closed unexpectedly.
You cannot report this error, because ksplashqml does not provide a bug reporting address.

Details:
Executable: ksplashqml PID: 3321 Signal: Segmentation fault (11) Time: 2/19/22 17:23:35"

In the "Developer Information" tab, it says
"The debugger application is missing or could not be launched."
"You need to first install the debugger application () then click the Reload button."

Outside of the tabs, there's a grayed-out "Report Bug" button, and usable "Restart Application" and "Close" button.

I'm trying to figure out what I should be installing or doing to get more information about the segmentation fault.

I've tried starting plasmashell directly using `kstart5 plasmashell --windowclass plasmashell`, and it prints out
```
Icon theme "breeze-dark" not found.
Icon theme "breeze-dark" not found.
QObject::disconnect: Unexpected null parameter
Constructing a KPluginInfo object from old style JSON. Please use kcoreaddons_desktop_to_json() for "" instead of kservice_desktop_to_json() in your CMake code.
Warning: corona package invalid
Invalid home screen package
Containment graphic object not valid
```
I tried comparing this to the output of that command on the other account, which does work, but I don't think the output has anything in common.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu plasma-workspace Edit question
Assignee:
No assignee Edit question
Solved by:
Max W Chase
Solved:
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said :
#1

For diagnostic purposes please provide the output that you receive for the following commands (to be executed in a terminal window):

uname -a
lsb_release -crid
apt-cache policy kde-workspace plasma-workspace

Revision history for this message
Tim-millerwilliams (tim-millerwilliams) said (last edit ):
#2

I've encountered the same problem. It started yesterday (2022-02-19). I'm not sure if it's related but the following packages were updated (from /var/log/apt/history.log):

Start-Date: 2022-02-19 10:04:41
Commandline: packagekit role='update-packages'
Requested-By: tim_wcbs (1002)
Upgrade: snapd:amd64 (2.54.3+20.04.1, 2.54.3+20.04.1ubuntu0.1), base-files:amd64 (11ubuntu5.4, 11ubuntu5.5)
End-Date: 2022-02-19 10:05:18

Here's my output for those commands:

$ uname -a
Linux tim-desktop-kubuntu 5.4.0-100-generic #113-Ubuntu SMP Thu Feb 3 18:43:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Codename: focal

$ apt-cache policy kde-workspace plasma-workspace
kde-workspace:
  Installed: (none)
  Candidate: (none)
  Version table:
plasma-workspace:
  Installed: 4:5.18.8-0ubuntu0.1
  Candidate: 4:5.18.8-0ubuntu0.1
  Version table:
 *** 4:5.18.8-0ubuntu0.1 500
        500 http://gb.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages
        100 /var/lib/dpkg/status
     4:5.18.4.1-0ubuntu1 500
        500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

Revision history for this message
Manfred Hampl (m-hampl) said (last edit ):
#3

Based on Tim-millerwilliams's output I relocate the question from kde-workspace to plasma-workspace. I assume that this is the affected package (kde-workspace was only for releases up to utopic)

If the same problem is seen by more than one person, then this may be a bug that probably should be reported in the bug tracker.

Revision history for this message
Tim-millerwilliams (tim-millerwilliams) said :
#4

Weirdly if I change my default shell from fish to bash things are less broken. I don't get the KDE crash handler window. I can see my desktop background but nothing else at all (no panels, widgets etc). I can open a terminal with ctrl+alt+t.

I wonder if this could be related to recent changes to snapd which mention fish shell in changelog: http://changelogs.ubuntu.com/changelogs/pool/main/s/snapd/snapd_2.54.3+20.04.1ubuntu0.1/changelog

Revision history for this message
Max W Chase (max-chase) said :
#5

So, my output is:

↪ uname -a
Linux ThinkPad-P1 5.8.14-050814-generic #202010070730 SMP Wed Oct 7 07:35:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

↪ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Codename: focal

kde-workspace:
  Installed: (none)
  Candidate: (none)
  Version table:
plasma-workspace:
  Installed: 4:5.18.8-0ubuntu0.1
  Candidate: 4:5.18.8-0ubuntu0.1
  Version table:
 *** 4:5.18.8-0ubuntu0.1 500
        500 http://us.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages
        100 /var/lib/dpkg/status
     4:5.18.4.1-0ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

Revision history for this message
Manfred Hampl (m-hampl) said (last edit ):
#6

If I interpret it correctly, then Bug #1961365 indicates that the fish problem was mainly affecting Ubuntu bionic.

I see a higher probability that the problem was introduced in the update of the plasma-workspace package from 4:5.18.5-0ubuntu0.1 to 4:5.18.8-0ubuntu0.1 on Feb 08, 2022

In my opinion this deserves creating a bug report.

Revision history for this message
Max W Chase (max-chase) said (last edit ):
#7

Hm, switching to bash fixed some of the issues, and put it in about the same state as Tim-millerwilliams. The most broken element appears to be that my desktop isn't displaying the directory contents. I added back the default widget, and I'll see if that persists through a logout.

EDIT: This is an okay workaround for now, so far.

EDIT: The desktop thing was a result of whatever messed up my configuration, which could have been this issue, or could have been my attempts to fix it. That's addressed, so now all that's left is getting fish to work as the shell again.

Revision history for this message
Patrizio Bekerle (pbek) said :
#8

I had the exactly same issue with ksplashqml (but with a lot more crashes afterwards):

Icon theme "breeze" not found.
Icon theme "breeze" not found.
kf.xmlgui: cannot find .rc file "systemsettingsui.rc" for component "systemsettings"
kf.service.services: KServiceTypeTrader: serviceType "KCModule" not found
kf.service.services: KServiceTypeTrader: serviceType "SystemSettingsExternalApp" not found
Failed to find desktop file for "systemsettings"
Fatal error while loading the sidebar view qml component
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings path = /usr/bin pid = 40411
KCrash: Arguments: /usr/bin/systemsettings kcm_icons
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
Icon theme "breeze" not found.
Icon theme "breeze" not found.
org.kde.drkonqi: Unable to find an internal debugger that can work with the crash backend
fish: Job 3, 'systemsettings kcm_icons' has stopped

Changing my shell in /etc/passwd to /bin/bash instead of /usr/bin/fish fixed the issue!
Thanks a lot!

Revision history for this message
Jean Sitja (jeannotfr62) said :
#9

Same issue here.
I do the following test.

  - Install fresh kubuntu 21.10 on virtual machine (vmware)
  - do full updates
  - install shell fish (at this stage all is working)
  - change default shell for the user to fish
  - disconnect from plasma and reconnect (i have the issue)
  - switch to a console alt-ctl-F2 and change back the default shell to bash
  - reboot the machine

After change back to bash fixed the issue.

Revision history for this message
James Fidler (terrarum) said :
#10

I use fish, I have encountered the same problem this morning (2022-02-22).

❯ uname -a
Linux jwork 5.13.0-30-generic #33-Ubuntu SMP Fri Feb 4 17:03:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

❯ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 21.10
Release: 21.10
Codename: impish

❯ apt-cache policy kde-workspace plasma-workspace
kde-workspace:
  Installed: (none)
  Candidate: (none)
  Version table:
plasma-workspace:
  Installed: 4:5.22.5-0ubuntu1
  Candidate: 4:5.22.5-0ubuntu1
  Version table:
 *** 4:5.22.5-0ubuntu1 500
        500 http://gb.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Manfred Hampl (m-hampl) said :
#11

Repeating my advice to everyone affected:

Please create a bug report!

I assume that this bug should be targeted at both, plasma-workspace on Ubuntu as well as fish on Ubuntu.

Revision history for this message
Max W Chase (max-chase) said :
#12

I linked the bug for the underlying issue. With the config.fish change linked in the bug comments, everything looks good to me.

Revision history for this message
Manfred Hampl (m-hampl) said :
#13

There is one additional step that should be done:

Everyone affected should open the bug report Bug #1961791 and click the "Does this bug affect you?" button to indicate that this is a general issue and not a case for just one person.