Bug 453774 - Dolphin crashed when attaching another monitor
Summary: Dolphin crashed when attaching another monitor
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 21.08.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-05-14 11:18 UTC by Warren Head
Modified: 2022-06-15 04:35 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 Warren Head 2022-05-14 11:18:35 UTC
Application: dolphin (21.08.1)

Qt Version: 5.15.2
Frameworks Version: 5.86.0
Operating System: Linux 5.13.0-40-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:
I attached a second monitor, via daisy chaining, which triggered a reset of the original monitor. Dolphin crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140703845939648) at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=140703845939648) at pthread_kill.c:80
#6  __GI___pthread_kill (threadid=140703845939648, signo=signo@entry=6) at pthread_kill.c:91
#7  0x00007ff82f786476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007ff82f76c7b7 in __GI_abort () at abort.c:79
#9  0x00007ff82fc15ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ff82d887354 in QtWaylandClient::QWaylandDisplay::checkError() const () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#11 0x00007ff82d88806a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#12 0x00007ff82fe75a88 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007ff82fe78f63 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007ff82fe79793 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007ff83092c6b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007ff82fe3e16a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007ff82fe98155 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007ff82da9a8bb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ff82daedf08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007ff82da98003 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007ff82fe97548 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007ff82fe3ca9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007ff82fe45024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x0000557143df0a24 in ?? ()
#25 0x00007ff82f76dfd0 in __libc_start_call_main (main=main@entry=0x557143deb0b0, argc=argc@entry=1, argv=argv@entry=0x7ffeef6cc808) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x00007ff82f76e07d in __libc_start_main_impl (main=0x557143deb0b0, argc=1, argv=0x7ffeef6cc808, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffeef6cc7f8) at ../csu/libc-start.c:409
#27 0x0000557143df11a5 in ?? ()
[Inferior 1 (process 24402) detached]

Possible duplicates by query: bug 452621, bug 452138, bug 451511, bug 450494, bug 450245.

Reported using DrKonqi
Comment 1 Nate Graham 2022-05-16 17:01:12 UTC
Was it *only* Dolphin that crashed, or did all other apps and Plasma crash too?
Comment 2 Bug Janitor Service 2022-05-31 04:35:47 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-06-15 04:35:23 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!