Bug 443884 - Plasmashell crash after screen switched off according to energy saving settings
Summary: Plasmashell crash after screen switched off according to energy saving settings
Status: RESOLVED DUPLICATE of bug 438839
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.22.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: 1.0
Assignee: David Edmundson
Keywords: drkonqi
Depends on:
Reported: 2021-10-17 12:31 UTC by forusim
Modified: 2021-10-17 23:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description forusim 2021-10-17 12:31:48 UTC
Application: plasmashell (5.22.5)

Qt Version: 5.15.2
Frameworks Version: 5.86.0
Operating System: Linux 5.13.0-19-generic x86_64
Windowing System: Wayland
Drkonqi Version: 5.22.5
Distribution: Ubuntu 21.10

-- Information about the crash:
- What I was doing when the application crashed: Nothing, therefore the screen was switched off according to energy saving settings.
Display is running via HDMI of UHD750 from Intel i7-11700.

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139731755444608) at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=139731755444608) at pthread_kill.c:80
#6  __GI___pthread_kill (threadid=139731755444608, signo=signo@entry=6) at pthread_kill.c:91
#7  0x00007f15d9af1476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007f15d9ad77b7 in __GI_abort () at abort.c:79
#9  0x00007f15d9f7cba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f15d81b4354 in QtWaylandClient::QWaylandDisplay::checkError() const () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#11 0x00007f15d81b506a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#12 0x00007f15da1dca88 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f15da1dff63 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f15da1e0793 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f15dae8f6b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f15da1a516a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f15da1ff155 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f15d85e28bb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f15d8635f08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f15d85e0003 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f15da1fe548 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f15da1a3a9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f15da1ac024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x000055cf253b0e0c in ?? ()
#25 0x00007f15d9ad8fd0 in __libc_start_call_main (main=main@entry=0x55cf253afec0, argc=argc@entry=1, argv=argv@entry=0x7ffc53b77538) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x00007f15d9ad907d in __libc_start_main_impl (main=0x55cf253afec0, argc=1, argv=0x7ffc53b77538, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc53b77528) at ../csu/libc-start.c:409
#27 0x000055cf253b0f35 in ?? ()
[Inferior 1 (process 5147) detached]

Reported using DrKonqi
Comment 1 Nate Graham 2021-10-17 23:27:41 UTC

*** This bug has been marked as a duplicate of bug 438839 ***