Summary: | Dolphin crashed while I was interacting with a Samba share | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Patrick Silva <bugseforuns> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | crash | CC: | estudioepc, kfm-devel, nate |
Priority: | NOR | Keywords: | accessibility |
Version: | 20.12.1 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
kwin_wayland crash kills all running apps |
Description
Patrick Silva
2021-01-12 21:17:03 UTC
Ugh #6 QMessageLogger::fatal (this=this@entry=0x7fffd70c5ba0, msg=msg@entry=0x7ff994ac00b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #6 QMessageLogger::fatal (this=this@entry=0x7fffd70c5ba0, msg=msg@entry=0x7ff994ac00b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 This means that the compositor crashed. Due to a Qt issue, when this happens, the app using it will crash too. KDE developers submitted a fix, but sadly it was not merged. See https://codereview.qt-project.org/c/qt/qtwayland/+/308984. Until we get better handling of this in Qt, the best we can do is debug why the compositor crashed in the first place. So can you please get a backtrace of the crash in kwin_wayland and then file a new bug report with it on kwin | wayland-generic? Thanks! You may be able to use the `coredumpctl` utility to retrieve the backtrace. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl Created attachment 134994 [details]
New crash information added by DrKonqi
dolphin (19.12.3) using Qt 5.12.8
- What I was doing when the application crashed:
I was trying to access to samba share folder in a windows10 PC.
When I puted the ip adress and accepted user and password Dolphing simply shuted down .
-- Backtrace (Reduced):
#6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7 0x00007fe2fedc8859 in __GI_abort () at abort.c:79
[...]
#11 0x00007fe2fdf30c60 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#12 0x00007fe2fdf3176b in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#13 0x00007fe2fe74daf8 in KIO::SimpleJob::slotFinished() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#6 QMessageLogger::fatal (this=this@entry=0x7fffd70c5ba0, msg=msg@entry=0x7ff994ac00b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 This means the compositor died. Can you grab a backtrace for kwin_wayland? You may be able to use coredumpctl. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl If you are, please file a new bug report against kwin | wayland-generic. Thanks! Plasma and all running apps are killed when kwin_wayland crashes. This was not the case when the Dolphin crash reported here occured. Thread 1 (Thread 0x7f09fb6e4800 (LWP 9342)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x00007f0a01e6e859 in __GI_abort () at abort.c:79 #8 0x00007f0a0173bded in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #9 0x00007f0a01852223 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #10 0x00007f09ffe4c458 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00007f0a00fd6c60 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #12 0x00007f0a00fd776b in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #13 0x00007f0a017f3af8 in KIO::SimpleJob::slotFinished() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #14 0x00007f0a017eb06e in KIO::ListJob::slotFinished() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #15 0x00007f09ffe4c458 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007f0a017c4252 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #17 0x00007f0a017c1f4f in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #18 0x00007f0a017cb152 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #19 0x00007f09ffe4c458 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00007f09ffe4cd5a in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x00007f0a00911a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x00007f0a0091b0f0 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x00007f09ffe2093a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00007f09ffe235b8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00007f09ffe78f67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x00007f09fdd69fbd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007f09fdd6a240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x00007f09fdd6a2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x00007f09ffe78565 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x00007f09ffe1f4db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x00007f09ffe27246 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x00007f0a020878b5 in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_dolphin.so #33 0x00007f0a01e700b3 in __libc_start_main (main=0x55687f429060, argc=1, argv=0x7ffc8febdf08, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc8febdef8) at ../csu/libc-start.c:308 #34 0x000055687f42909e in _start () [Inferior 1 (process 9342) detached] (In reply to Patrick Silva from comment #5) > Plasma and all running apps are killed when kwin_wayland crashes. Not anymore; we've been working on fixing that. :) Estudio, is this a backtrace from kwin_wayland? (In reply to Nate Graham from comment #7) > (In reply to Patrick Silva from comment #5) > > Plasma and all running apps are killed when kwin_wayland crashes. > Not anymore; we've been working on fixing that. :) > > Estudio, is this a backtrace from kwin_wayland? I am using KDE Plasma. I don't know what you mean with kwin_wayland. This event happens when I use Samba share option in Dolphing. But if a use the option Open net folder, it works well. Created attachment 134997 [details] kwin_wayland crash kills all running apps (In reply to Nate Graham from comment #7) > (In reply to Patrick Silva from comment #5) > > Plasma and all running apps are killed when kwin_wayland crashes. > Not anymore; we've been working on fixing that. :) > is that a recent improvement? I have just reproduced a kwin_wayland crash changing font settings on neon unstable. As we can see in the attached screenhot, all running apps were killed. Yes it is, in git master/Plasma 5.21. Estudio, can you use the coredumpctl utility to get a backtrace of the process named "kwin_wayland", which is crashing? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl 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! I changed global theme and it worked well. |