Bug 456789 - Segmentation fault plasmashell Crashes on system Boot.
Summary: Segmentation fault plasmashell Crashes on system Boot.
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Startup process (show other bugs)
Version: 5.24.5
Platform: Debian testing Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-16 05:12 UTC by Charlie Ramirez Animation Studios MX
Modified: 2022-08-15 04:35 UTC (History)
1 user (show)

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


Attachments
Plasmashell Backtrace by DrKonqui (20.32 KB, text/vnd.kde.kcrash-report)
2022-07-16 05:12 UTC, Charlie Ramirez Animation Studios MX
Details
Dr Konqui Screen at boot (38.59 KB, image/png)
2022-07-16 05:14 UTC, Charlie Ramirez Animation Studios MX
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Charlie Ramirez Animation Studios MX 2022-07-16 05:12:40 UTC
Created attachment 150666 [details]
Plasmashell Backtrace by DrKonqui

SUMMARY
Plasmashell Hangs during normal debian boot Launching Dr Konqi at the same time it starts the graphical environment.
 indicating that "Plasma unexpectedly quit" due to plasmashell PID: 1736 Signal: Segmentation fault (11)

STEPS TO REPRODUCE
1.  The problem started to occur suddenly after one of the Debian kernel updates around March 2022.
2. there is no clear way to observe the faulty component as it occurs during startup (after log in. During the black animated screen loading the Plasma desktop and the appearance of the desktop or windows from the previous session)
3. Reinstalling plasma through Apt and updating debian daily does not solve the problem,

OBSERVED RESULT
at boot time during desktop loading, the screen stays black for a few extra seconds after which the Dr Konqui screen appears stating that Plasma quit unexpectedly as the desktop background finishes loading. sometimes the error reporting window does not appear immediately instead an icon is displayed on the bar indicating that plasma failed and press if you want to report the failure
[The desktop and plasma seem to work normally after this. until the equipment is turned off and starts up again].

 # Suspend does not generate hang only on boot.


EXPECTED RESULT
The report wizard always returns that backtraces are not useful [See Attachment]. and requieres report manually. - because it only happens during boot I haven't been able to find a way to replicate it other than power off and on. [try to use gdb but it returns nothing] and coredumpctl is not located  when using terminal.

SOFTWARE/OS VERSIONS

Operating System: Debian GNU/Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.18.0-2-amd64 (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
Memory: 13.6 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics
ADDITIONAL INFORMATION
-Debian 11 stable with Testing Repo and dual boot with Windows 11 .
Comment 1 Charlie Ramirez Animation Studios MX 2022-07-16 05:14:21 UTC
Created attachment 150667 [details]
Dr Konqui Screen at boot
Comment 2 David Edmundson 2022-07-16 07:34:04 UTC
>The report wizard always returns that backtraces are not useful [See Attachment]. and requieres report manually

Installing debug symbols for plasmashell ahead of time could work, or looking at the second tab of that window and attaching that.
Or we can just hope that someone else has reported the same bug and it gets fixed in the meantime when you upgrade.
Comment 3 Bug Janitor Service 2022-07-31 04:35:37 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 4 Bug Janitor Service 2022-08-15 04:35:33 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

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