Bug 300741

Summary: DOLPHIN crashes under normal working conditions
Product: [Applications] dolphin Reporter: Axel Krebs <axel.krebs>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED UPSTREAM    
Severity: crash CC: artiomjar, jakub77a
Priority: NOR    
Version: 2.0   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: 120526_tooltips.jpg
New crash information added by DrKonqi

Description Axel Krebs 2012-05-28 06:37:48 UTC 
Application: dolphin (2.0)
KDE Platform Version: 4.8.2 (4.8.2) (Compiled from sources)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-24-generic x86_64
Distribution: Ubuntu 12.04 LTS

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

just searching /watching files ind a directory; nothing irregluar conscious

The crash can be reproduced some of the time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa2917fd780 (LWP 4064))]

Thread 3 (Thread 0x7fa27d526700 (LWP 4065)):
#0  0x00007fa2910bfb03 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fa2890a2ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fa2890a3124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fa28e151426 in QEventDispatcherGlib::processEvents (this=0x7fa2780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007fa28e120c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fa28e120ed7 in QEventLoop::exec (this=0x7fa27d525dd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fa28e01ffa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007fa28e1009ff in QInotifyFileSystemWatcherEngine::run (this=0x1f673a0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fa28e022fcb in QThreadPrivate::start (arg=0x1f673a0) at thread/qthread_unix.cpp:298
#9  0x00007fa289967e9a in start_thread (arg=0x7fa27d526700) at pthread_create.c:308
#10 0x00007fa2910cb4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fa277fff700 (LWP 4066)):
#0  0x00007fa2890de5a8 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fa2890a2fea in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fa2890a3124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fa28e151426 in QEventDispatcherGlib::processEvents (this=0x7fa2700008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007fa28e120c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fa28e120ed7 in QEventLoop::exec (this=0x7fa277ffedd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fa28e01ffa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007fa28e1009ff in QInotifyFileSystemWatcherEngine::run (this=0x20219d0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fa28e022fcb in QThreadPrivate::start (arg=0x20219d0) at thread/qthread_unix.cpp:298
#9  0x00007fa289967e9a in start_thread (arg=0x7fa277fff700) at pthread_create.c:308
#10 0x00007fa2910cb4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa2917fd780 (LWP 4064)):
[KCrash Handler]
#6  0x00007fa28e121fbe in size (this=0x1fdd170) at ../../include/QtCore/../../src/corelib/tools/qlist.h:98
#7  size (this=0x1fdd170) at ../../include/QtCore/../../src/corelib/tools/qlist.h:137
#8  QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<optimized out>, receiver=0x2d4dd60, event=0x7fff2902aa90) at kernel/qcoreapplication.cpp:978
#9  0x00007fa28d22785f in notify_helper (e=0x7fff2902aa90, receiver=0x2d4dd60, this=0x1dd2010) at kernel/qapplication.cpp:4555
#10 QApplicationPrivate::notify_helper (this=0x1dd2010, receiver=0x2d4dd60, e=0x7fff2902aa90) at kernel/qapplication.cpp:4531
#11 0x00007fa28d22c713 in QApplication::notify (this=0x7fff2902b4e0, receiver=0x2d4dd60, e=0x7fff2902aa90) at kernel/qapplication.cpp:4420
#12 0x00007fa28eb81b46 in KApplication::notify (this=0x7fff2902b4e0, receiver=0x2d4dd60, event=0x7fff2902aa90) at ../../kdeui/kernel/kapplication.cpp:311
#13 0x00007fa28e121e9c in QCoreApplication::notifyInternal (this=0x7fff2902b4e0, receiver=0x2d4dd60, event=0x7fff2902aa90) at kernel/qcoreapplication.cpp:876
#14 0x00007fa28d22811b in sendEvent (event=0x7fff2902aa90, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#15 QApplicationPrivate::dispatchEnterLeave (enter=0x2d4dd60, leave=<optimized out>) at kernel/qapplication.cpp:2824
#16 0x00007fa28d2a69f1 in QApplication::x11ProcessEvent (this=0x7fff2902b4e0, event=0x7fff2902b0d0) at kernel/qapplication_x11.cpp:3805
#17 0x00007fa28d2d00d2 in x11EventSourceDispatch (s=0x1dc7e30, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#18 0x00007fa2890a2c9a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fa2890a3060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fa2890a3124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fa28e1513bf in QEventDispatcherGlib::processEvents (this=0x1dac4a0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#22 0x00007fa28d2cfd5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007fa28e120c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#24 0x00007fa28e120ed7 in QEventLoop::exec (this=0x7fff2902b470, flags=...) at kernel/qeventloop.cpp:204
#25 0x00007fa28e125f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#26 0x00007fa2913de4c7 in kdemain (argc=5, argv=0x7fff2902ba38) at ../../../dolphin/src/main.cpp:89
#27 0x00007fa290ffa76d in __libc_start_main (main=0x400640 <main(int, char**)>, argc=5, ubp_av=0x7fff2902ba38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff2902ba28) at libc-start.c:226
#28 0x0000000000400671 in _start ()

Possible duplicates by query: bug 300703, bug 300321, bug 297832, bug 297815, bug 296852.

Reported using DrKonqi
Comment 1 Peter Penz 2012-05-28 09:20:23 UTC 
Created attachment 71405 [details]
120526_tooltips.jpg

Thanks for the report. Did you enabled tooltips? The backtrace might indicate that this is an issue in Qt: https://bugreports.qt-project.org/browse/QTBUG-19363
Comment 2 Axel Krebs 2012-05-28 09:34:01 UTC 
Dear Peter:

I do not even know, what "tooltips" are meant to be, unfortunately.


Axel

Am 28.05.2012 11:20, schrieb Peter Penz:
> https://bugs.kde.org/show_bug.cgi?id=300741
> 
> Peter Penz <peter.penz19@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
> 
> --- Comment #1 from Peter Penz <peter.penz19@gmail.com> ---
> Thanks for the report. Did you enabled tooltips? The backtrace might indicate
> that this is an issue in Qt:
> https://bugreports.qt-project.org/browse/QTBUG-19363
>
Comment 3 Peter Penz 2012-05-28 09:37:45 UTC 
@Axel:
> I do not even know, what "tooltips" are meant to be, unfortunately.

If you move your mouse above a file or directory: Does a small box appear after a very short time that shows more detailed information about the file or directory? A screenshot of a tooltip can be seen at http://ppenz.blogspot.com/2011/03/dont-crash-when-reading-metadata.html at the top of the article.
Comment 4 Axel Krebs 2012-05-28 09:57:30 UTC 
Peter:

this holds true: I see a small box...!


Axel
Am 28.05.2012 11:37, schrieb Peter Penz:
> https://bugs.kde.org/show_bug.cgi?id=300741
> 
> --- Comment #3 from Peter Penz <peter.penz19@gmail.com> ---
> @Axel:
>> I do not even know, what "tooltips" are meant to be, unfortunately.
> 
> If you move your mouse above a file or directory: Does a small box appear after
> a very short time that shows more detailed information about the file or
> directory? A screenshot of a tooltip can be seen at
> http://ppenz.blogspot.com/2011/03/dont-crash-when-reading-metadata.html at the
> top of the article.
>
Comment 5 Peter Penz 2012-05-28 19:25:09 UTC 
Thanks for the update Axel! OK, then it looks like the root-cause is in Qt: https://bugreports.qt-project.org/browse/QTBUG-19363

We try to bypass this issue in KDE 4.9 but of course the fix must be done in Qt in the longterm.
Comment 6 Frank Reininghaus 2012-08-06 00:59:39 UTC 
*** Bug 303439 has been marked as a duplicate of this bug. ***
Comment 7 Artiom Jarcov 2013-11-06 13:24:40 UTC 
Created attachment 83372 [details]
New crash information added by DrKonqi

dolphin (2.0) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1

- What I was doing when the application crashed:
I just positioned the mouse cursor to the file
- Custom settings of the application:
tooltip and information panel is enabled

-- Backtrace (Reduced):
#6  QCoreApplication::notifyInternal (this=0x7fff7f119b50, receiver=0x26c0020, event=0x7fff7f117930) at kernel/qcoreapplication.cpp:864
#7  0x00007f8940f7711b in sendEvent (event=0x7fff7f117930, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#8  QApplicationPrivate::dispatchEnterLeave (enter=0x26c0020, leave=<optimized out>) at kernel/qapplication.cpp:2824
#9  0x00007f8940ff59f1 in QApplication::x11ProcessEvent (this=0x7fff7f119b50, event=0x7fff7f117f70) at kernel/qapplication_x11.cpp:3805
#10 0x00007f894101f0d2 in x11EventSourceDispatch (s=0x1985c00, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146