Bug 392748 - kdeinit crashes at start
Summary: kdeinit crashes at start
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (show other bugs)
Version: 5.17.5
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-05 06:43 UTC by Mathias Bavay
Modified: 2022-11-02 14:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
backtrace (7.77 KB, text/plain)
2018-04-05 06:43 UTC, Mathias Bavay
Details
imrpoved backtrace (10.15 KB, text/plain)
2018-05-15 08:22 UTC, Mathias Bavay
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mathias Bavay 2018-04-05 06:43:23 UTC
Created attachment 111835 [details]
backtrace

After every start, I have this message that kdeinit crashed. If I try to activate my vpn, it does not work (ie clicking on the button does nothing). After clicking on "configure network connections" (and closing the configuration window without doing anything), clicking on the vpn activates it (it seems to me that because kdeinit crashed, some other things are left in an unusable state).
Comment 1 Rajeesh K V 2018-05-02 05:38:56 UTC
The trace doesn't offer much details to debug or code location, unfortunately. Is it possible to get the backtrace with debug symbols enabled or installed?
Comment 2 Mathias Bavay 2018-05-02 06:40:57 UTC
(In reply to Rajeesh K V from comment #1)
> The trace doesn't offer much details to debug or code location,
> unfortunately. Is it possible to get the backtrace with debug symbols
> enabled or installed?

I will try to get more debug symbols (I already had a hard time trying to figure out which packages would provide the required debug symbols)...
Comment 3 Mathias Bavay 2018-05-15 08:22:03 UTC
Created attachment 112662 [details]
imrpoved backtrace

Much better backtrace (all relevant symbols should be there)
Comment 4 Mathias Bavay 2018-05-15 08:22:38 UTC
After fighting with the *-dbgsymb packages, the backtrace is much better...
Comment 5 Rajeesh K V 2018-05-15 10:02:57 UTC
Thanks for the improved backtrace. That still doesn't give any clues on what the actual problem is, though.

Could you confirm the plasma-desktop version, libinput version and xorg-x11-drv-libinput version?
Comment 6 Mathias Bavay 2018-05-16 07:00:42 UTC
libinput10 is version 1.10.6-1, xserver-xorg-input-libinput is version 0.27.1-1, plasma-desktop is version 4:5.12.5-1 (it is all Debian Buster).
Comment 7 Justin Zobel 2022-10-03 10:36:21 UTC
Thank you for reporting this crash 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 crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 8 Bug Janitor Service 2022-10-18 04:57:44 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Mathias Bavay 2022-10-18 07:35:44 UTC
With version 5.18.8, this bug seems to be gone (I've never experience it on this version)
Comment 10 Bug Janitor Service 2022-11-02 05:05:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

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