Bug 438933 - Dolphin crash
Summary: Dolphin crash
Status: RESOLVED UPSTREAM
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 20.12.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-06-20 02:11 UTC by John Shellshear
Modified: 2021-06-20 17:55 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 John Shellshear 2021-06-20 02:11:08 UTC
Application: dolphin (20.12.3)

Qt Version: 5.15.2
Frameworks Version: 5.80.0
Operating System: Linux 5.11.0-18-generic x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.4
Distribution: Ubuntu 21.04

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

I was using the Firefox browser (Curren version) - I had several tabs open and was looking at a news article from Google when the browser seized, mouse and keyboard access halted. Even the caps lock light did not respond for two minutes until the system recovered itself. Browser, Dolphin all crashed.

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#5  0x00007f6615330864 in __GI_abort () at abort.c:79
#6  0x00007f66130f7c77 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f6610b92d39 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#8  0x00007f6610ba1f9a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#9  0x00007f6613357600 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f661335abe3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f661335b413 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f6613e0f783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f661331f7ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f6613379e05 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f66111648eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f66111b7d28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f6611162023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f6613379204 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f661331e11b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f6613326604 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f6615549570 in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_dolphin.so
#22 0x00007f6615332565 in __libc_start_main (main=0x55e1b2245060, argc=1, argv=0x7ffca0289998, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffca0289988) at ../csu/libc-start.c:332
#23 0x000055e1b224509e in _start ()
[Inferior 1 (process 6696) detached]

Possible duplicates by query: bug 436342, bug 435068, bug 434860, bug 434456, bug 434435.

Reported using DrKonqi
Comment 1 Harald Sitter 2021-06-20 17:55:49 UTC
The crash log only tells us that KWin crashed; sadly it's a known and unavoidable issue that when kwin_wayland crashes, all apps crash too (see https://bugreports.qt.io/browse/QTBUG-85631). The app crash logs are not useful; all they do is tell us that KWin crashed. But we need to know why KWin crashed. For that, we need a backtrace of the KWin crash itself. You may be able to retrieve it with `coredumpctl`. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl