| Summary: | plasma(wayland) crash every time at login | ||
|---|---|---|---|
| Product: | [Unmaintained] ksplash | Reporter: | nuletbip |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | fabian, nate, nicolas.fella, plasma-bugs-null |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.23.90 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
one of the coredumps
drkonqui coredumps drkonqi coredumps (2) plasmashell gdb log plasmashell gdb log 2 ksplash gdb log |
||
|
Description
nuletbip
2022-01-19 18:31:23 UTC
Can you please check the logs for error messages? Is kwin_wayland also crashing? This backtrace often means "we crashed because KWin crashed". Can you check `coredumpctl` for kwin_wayland crash logs, and attach the most recent one, if you find any? (In reply to Nicolas Fella from comment #1) > Can you please check the logs for error messages? (In reply to Nate Graham from comment #2) > Is kwin_wayland also crashing? This backtrace often means "we crashed > because KWin crashed". Can you check `coredumpctl` for kwin_wayland crash > logs, and attach the most recent one, if you find any? Hi, How can I test it? Like I said:
> Can you check `coredumpctl` for kwin_wayland crash
> logs, and attach the most recent one, if you find any?
`coredumpctl` is a command line program you will need to run in a terminal window.
Created attachment 145731 [details]
one of the coredumps
Created attachment 145732 [details]
drkonqui coredumps
Created attachment 145733 [details]
drkonqi coredumps (2)
(In reply to Nate Graham from comment #4) > Like I said: > > > Can you check `coredumpctl` for kwin_wayland crash > > logs, and attach the most recent one, if you find any? > > > `coredumpctl` is a command line program you will need to run in a terminal > window. Hi, I still have another coredump for plasmashell but it's too big (6Mo) We don't need the whole coredump; you use it to generate a backtrace, which is a simple piece of text. https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl may help. Sorry, I probably should have provided that link earlier. Created attachment 146043 [details]
plasmashell gdb log
plasmashell gdb log
Created attachment 146044 [details]
plasmashell gdb log 2
Created attachment 146045 [details]
ksplash gdb log
(In reply to Nate Graham from comment #9) > We don't need the whole coredump; you use it to generate a backtrace, which > is a simple piece of text. > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > may help. Sorry, I probably should have provided that link earlier. Hi, I have just upload backtraces. I hope it'will help. regards. Vincent Stack trace of thread 189503:
#0 0x00007f4a44909808 __pthread_kill_implementation (libc.so.6 + 0x9a808)
#1 0x00007f4a448b5476 __GI_raise (libc.so.6 + 0x46476)
#2 0x00007f4a401dd57c _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x857c)
#3 0x00007f4a448b5520 __restore_rt (libc.so.6 + 0x46520)
#4 0x00007f4a44909808 __pthread_kill_implementation (libc.so.6 + 0x9a808)
#5 0x00007f4a448b5476 __GI_raise (libc.so.6 + 0x46476)
#6 0x00007f4a4489b7b7 __GI_abort (libc.so.6 + 0x2c7b7)
#7 0x00007f4a44d40ba3 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x90ba3)
#8 0x00007f4a441c6354 _ZNK15QtWaylandClient15QWaylandDisplay10checkErrorEv (libQt5WaylandClient.so.5 + 0x7a354)
#9 0x00007f4a441c706a _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x7b06a)
#10 0x00007f4a44fa0dd8 n/a (libQt5Core.so.5 + 0x2f0dd8)
#11 0x00007f4a44fc2802 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x312802)
#12 0x00007f4a44f67deb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b7deb)
#13 0x00007f4a44f70374 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2c0374)
#14 0x000055d540de3d6b n/a (ksplashqml + 0x4d6b)
#15 0x00007f4a4489cfd0 __libc_start_call_main (libc.so.6 + 0x2dfd0)
#16 0x00007f4a4489d07d __libc_start_main_impl (libc.so.6 + 0x2e07d)
#17 0x000055d540de3dc5 n/a (ksplashqml + 0x4dc5)
We're somewhere in KSplash. Unfortuntely we don't have enough debug symbols to know more than that. Can you install debug symbols for ksplash and do it again?
The backtrace means it printed an error message with helpful info. Please get that from either the journal or ~/.local/share/sddm/wayland-session.log. 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! 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! |