Bug 423252 - [Wayland] Dolphin crashed while extracting a compress file with ark.
Summary: [Wayland] Dolphin crashed while extracting a compress file with ark.
Status: RESOLVED UPSTREAM
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-06-20 00:38 UTC by Tony
Modified: 2020-07-14 21:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
ark bactrace (6.58 KB, text/plain)
2020-06-20 00:57 UTC, Tony
Details
New crash information added by DrKonqi (2.86 KB, text/plain)
2020-06-26 02:45 UTC, Tony
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tony 2020-06-20 00:38:53 UTC
Application: dolphin (20.07.70)

Qt Version: 5.15.0
Frameworks Version: 5.72.0
Operating System: Linux 5.7.2-zen1-1-default x86_64
Windowing system: Wayland
Distribution: "openSUSE Tumbleweed"

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

Created a folder named s in ~/Building.
Opened a compress file with ark, in my case the sources for zen kernel.
Drag the sources folder into s from ark's window.

- Unusual behavior I noticed:

Ark goes into a not responding state, around this point is when the dolphin crash happens, sometimes the sad face pops more than once. 
The decompressing task still going though and afer a while i get the notification status bar for the task which completes OK.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x00007f2fce2544b1 in raise () from /lib64/libc.so.6
#5  0x00007f2fce23d539 in abort () from /lib64/libc.so.6
#6  0x00007f2fcc0b6c27 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal (this=this@entry=0x7fffa25f1650, msg=msg@entry=0x7f2fc742d0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8  0x00007f2fc7373f25 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
#9  QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at qwaylanddisplay.cpp:204
#10 0x00007f2fc73842ae in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55bf43e1c0f0) at qwaylanddisplay.cpp:222
#11 0x00007f2fcc306020 in doActivate<false> (sender=0x55bf43e41380, signal_index=3, argv=argv@entry=0x7fffa25f1790) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#12 0x00007f2fcc2ff340 in QMetaObject::activate (sender=sender@entry=0x55bf43e41380, m=m@entry=0x7f2fcc5b1b00 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffa25f1790) at kernel/qobject.cpp:3946
#13 0x00007f2fcc30941f in QSocketNotifier::activated (this=this@entry=0x55bf43e41380, _t1=..., _t2=<optimized out>, _t3=...) at .moc/moc_qsocketnotifier.cpp:178
#14 0x00007f2fcc309c1b in QSocketNotifier::event (this=0x55bf43e41380, e=0x7fffa25f18a0) at kernel/qsocketnotifier.cpp:302
#15 0x00007f2fcceed0cf in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55bf43e41380, e=0x7fffa25f18a0) at kernel/qapplication.cpp:3671
#16 0x00007f2fcc2cfb0a in QCoreApplication::notifyInternal2 (receiver=0x55bf43e41380, event=0x7fffa25f18a0) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325
#17 0x00007f2fcc327b05 in socketNotifierSourceDispatch (source=0x55bf43e355f0) at kernel/qeventdispatcher_glib.cpp:107
#18 0x00007f2fca0542c7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#19 0x00007f2fca054648 in ?? () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f2fca0546ff in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f2fcc326f4f in QEventDispatcherGlib::processEvents (this=0x55bf43e44050, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x00007f2fcc2ce4cb in QEventLoop::exec (this=this@entry=0x7fffa25f1ab0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141
#23 0x00007f2fcc2d6730 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#24 0x00007f2fce432160 in kdemain () from /usr/lib64/libkdeinit5_dolphin.so
#25 0x00007f2fce23ecca in __libc_start_main () from /lib64/libc.so.6
#26 0x000055bf43dc908a in _start ()
[Inferior 1 (process 11649) detached]

Possible duplicates by query: bug 423132, bug 417285, bug 414922, bug 413943, bug 411017.

Reported using DrKonqi
Comment 1 Tony 2020-06-20 00:47:00 UTC
> completes OK.

After double checking no, it does NOT complete OK. 
The decompression task gets killed at some point as well after the decompression notification pops and not all files get decompressed.
Comment 2 Tony 2020-06-20 00:57:04 UTC
Created attachment 129537 [details]
ark bactrace

I ran coredumpctl and see both Dolphins and arks dumps due to this.
See attachtment for ark's backtrace.
Comment 3 Tony 2020-06-26 02:45:19 UTC
Created attachment 129687 [details]
New crash information added by DrKonqi

dolphin (20.07.70) using Qt 5.15.0

- What I was doing when the application crashed:

Log in into a wayalnd session after a previous wayland session crashed.
Opened dolphin and minimized it.
Opened telegram and and minimized it. 

I tried to repeat what triggered the previous crash, drag a text file from the desktop and hover it over dolphin and telegram to maximized their windows.
As dolhin window maximized i dropped the text file, clicked F4 to close the terminal and then dolphin crashed.

The funny thing is the wayland session did not crashed this time.

-- Backtrace (Reduced):
#6  0x00007fafff08ec27 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal (this=this@entry=0x7ffc7deeed80, msg=msg@entry=0x7faffa4050b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8  0x00007faffa34bf25 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
#9  QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at qwaylanddisplay.cpp:204
#10 0x00007faffa35c2ae in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x563954df3120) at qwaylanddisplay.cpp:222
Comment 4 Christoph Feck 2020-07-14 21:29:59 UTC
Error is: The Wayland connection broke. Did the Wayland compositor die?

Qt cannot recover from this error.