Bug 335932

Summary:	DrKonqi cannot file bugs against kdeinit5
Product:	[Frameworks and Libraries] frameworks-kinit	Reporter:	Louis Moureaux <m_louis30>
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	bshah, bugseforuns, kde, kdelibs-bugs-null
Priority:	NOR
Version First Reported In:	4.100.0
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Louis Moureaux 2014-06-07 23:51:17 UTC

WARNINGS:
1. The following steps will end your current session!
2. You will need to be root or restart your computer to restart a normal session

Steps to reproduce (that's not the way I found the bug, but since kdeinit5 doesn't crash anymore, we need to help him):
1. Start a Plasma 5 session from within SDDM (didn't test with other DMs)
2. From a terminal, type "killall -s SIGSEGV kdeinit5" to crash kdeinit
3. Close the X error message dialog (could not start xxx)
4. DrKonqi should appear, complaining about no email being set
5. Restart SDDM using "systemctl restart sddm" (systemd) or "service sddm restart" (upstart), or by restarting your computer. This ensures there are no process left from the previous session.

I'm using up-to-date Project Neon packages in KVM.

Reproducible: Always

Comment 1 David Edmundson 2014-06-13 18:09:34 UTC

Moved to kdeinit

Comment 2 Andrew Crouthamel 2018-11-12 02:46:34 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Louis Moureaux 2018-11-12 11:11:38 UTC

I can still reproduce this problem in Arch Linux with Plasma 5.14, Kde Frameworks 5.51.0 and Qt 5.11.2.

However, kdeinit has been very stable on my machines for the last few years, so having no easy way to report crashes hasn't been a problem.

Comment 4 Patrick Silva 2018-12-04 19:22:38 UTC

same thing on neon dev unstable.
I can crash kdeinit5 on Wayland opening a folder containing a font file while font preview feature is enabled in Dolphin settings.

Comment 5 Justin Zobel 2023-01-19 00:18:52 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 6 Louis Moureaux 2023-01-19 11:02:43 UTC

Thanks Justin for the reminder!

I no longer have a running kdeinit5 process in recent Plasma versions (on both Arch and Neon). I don't know what happens now when kdeinit crashes, but I don't have an easy way to trigger it. Setting as WORKSFORME since I can no longer easily trigger a kdeinit crash and hence cannot reproduce...