Bug 446922 - desktop crashed when booting,including the relvant components.
Summary: desktop crashed when booting,including the relvant components.
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.23.4
Platform: Ubuntu Linux
: NOR crash
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: drkonqi, wayland
Depends on:
Blocks:
 
Reported: 2021-12-13 10:20 UTC by suntianchen2001
Modified: 2022-01-13 04:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description suntianchen2001 2021-12-13 10:20:55 UTC
Application: plasmashell (5.23.4)

Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.13.0-22-generic x86_64
Windowing System: Wayland
Distribution: Ubuntu 21.10
DrKonqi: 5.23.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
starting the system

- Unusual behavior I noticed:
a lot of notification about crashes emerged ,such as kwallet ,plasma, etc
 that means a lot of components of kde has crashed after the system started.

- Custom settings of the application:

The crash does not seem to be reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140543807760768) at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=140543807760768) at pthread_kill.c:80
#6  __GI___pthread_kill (threadid=140543807760768, signo=signo@entry=6) at pthread_kill.c:91
#7  0x00007fd2ebc68476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007fd2ebc4e7b7 in __GI_abort () at abort.c:79
#9  0x00007fd2ec0f5ba3 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fd2ea314e45 in  () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#11 0x00007fd2ea32506a in QtWaylandClient::QWaylandDisplay::flushRequests() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#12 0x00007fd2ec355a88 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007fd2ec358f63 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fd2ec359793 in QSocketNotifier::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007fd2ed00a6b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007fd2ec31e16a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007fd2ec378155 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007fd2ea7518bb in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fd2ea7a4f08 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fd2ea74f003 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fd2ec377548 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007fd2ec31ca9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007fd2ec325024 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00005582d7194d09 in  ()
#25 0x00007fd2ebc4ffd0 in __libc_start_call_main (main=main@entry=0x5582d7193eb0, argc=argc@entry=1, argv=argv@entry=0x7ffdb7ac41a8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x00007fd2ebc5007d in __libc_start_main_impl (main=0x5582d7193eb0, argc=1, argv=0x7ffdb7ac41a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdb7ac4198) at ../csu/libc-start.c:409
#27 0x00005582d7194e25 in  ()
[Inferior 1 (process 6492) detached]

Possible duplicates by query: bug 446351, bug 446195, bug 445778, bug 445669, bug 445479.

Reported using DrKonqi
Comment 1 Nate Graham 2021-12-14 20:30:21 UTC
This means that KWin itself crashed. Can you get a backtrace of the kwin_wayland crash? The `coredumpctl` utility may be helpful. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Comment 2 Bug Janitor Service 2021-12-29 04:35:02 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 3 Bug Janitor Service 2022-01-13 04:37:16 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!