Bug 450639 - ksplashqml segmentation fault when using fish shell
Summary: ksplashqml segmentation fault when using fish shell
Status: RESOLVED FIXED
Alias: None
Product: ksplash
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-21 10:32 UTC by Noé Lopez
Modified: 2022-03-02 18:18 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
The backtrace (4.87 KB, text/plain)
2022-02-21 10:32 UTC, Noé Lopez
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Noé Lopez 2022-02-21 10:32:35 UTC
Created attachment 146993 [details]
The backtrace

SUMMARY
ksplash qml crashes when I start plasma either through sddm or startplasma-x11. Then the whole thing won't work, and plasma will not start, leaving me on a black screen.

STEPS TO REPRODUCE
1. Start plasma

OBSERVED RESULT
crash appears

EXPECTED RESULT
splash screen appears

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  KDE Neon  5.24
(available in About System)
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3
Comment 1 David Edmundson 2022-02-21 11:30:25 UTC
#6  QObject::setProperty (this=this@entry=0x0, name=name@entry=0x56243ae78868 "stage", value=...) at kernel/qobject.cpp:4030
Comment 2 Floreal 2022-02-21 12:26:28 UTC
Same problem for me. I can't start KDE anymore!
Comment 3 Unknown 2022-02-22 02:28:17 UTC
I experienced this too and fixed it temporarily by changing my shell from Fish back to Bash from a different TTY. I was then was able to login no problems.
Comment 4 Nate Graham 2022-02-22 19:56:18 UTC
Are you also using Fish shell, Noé and/or Floreal?
Comment 5 Tom 2022-02-22 23:33:08 UTC
New to linux, don't know what I'm doing. Also use Fish.
Linux 5.15.23-76051523-generic

sddm allows password, then a dialogue shows ksplashqml has crashed (and that it doesn't have any crash details to submit?). Black screen immediately after, tty to the yescue. First encountered on Sunday's first boot after blindly apt updating on Saturday. Did a fresh install of Pop 21.10 because noob, updated 172 separate packages through apt, rebooted and tried kde-full as I had been using. Logged out of Gnome and into KDE and it worked fine, and everything I used worked as expected too. Could login/out multiple times, no issue. Reliably reoccurs on reboot. Reinstalled Pop again, repeat apt update 172 packages, reboot, kde-full, same issue. Reinstalled a third time, tried kde-standard from apt, same; could login/out okay, just refuses to work after reboot.

Does this even help?
Comment 6 Floreal 2022-02-23 12:53:40 UTC
(In reply to Nate Graham from comment #4)
> Are you also using Fish shell, Noé and/or Floreal?

Yes I use fish. The problem was at work so I can't wait to have my PC working, so I reinstalled Neon and problem was solved. But now I have bash as default for my user and fish only in yakuake. I didn't test with fish as default.
Comment 7 Nate Graham 2022-02-23 20:04:12 UTC
Possibly Bug 446438?
Comment 8 Floreal 2022-02-23 21:02:54 UTC
In my case I use X11 not wayland, and I had no issue until several months. Problem appears on 21/02/2021 just after a system update
Comment 9 Jose Antonio 2022-02-25 16:22:10 UTC
I found this bug today after upgrading my Kubuntu 21.10 installation to the latest Plasma 5.24.1.
I can't start my session in either Wayland or X11 if I set my default shell to fish.
Comment 10 Floreal 2022-02-25 18:04:32 UTC
I do the upgrade on another PC where I have fish as default shell, and there is no bug here. So... fish alone is not the problem. Maybe something in fish I don't have here. Or the problem is elsewhere
Comment 11 Jose Antonio 2022-02-26 09:37:58 UTC
After upgrading to Plasma 5.24.2, the problem is gone.
Comment 12 Unknown 2022-03-01 03:23:09 UTC
(In reply to Jose Antonio from comment #11)
> After upgrading to Plasma 5.24.2, the problem is gone.

Also fixed for me on Plasma 5.24.2.
Comment 13 Nate Graham 2022-03-01 03:57:42 UTC
Oh, that's good to hear. Noé, how about you?
Comment 14 Noé Lopez 2022-03-02 18:18:04 UTC
Its also fixed for me on plasma 5.24.2!