Bug 204416 - Dolphin crash drag drop tabs location (QX11PaintEngine, .., KIconEngine::pixmap, .., KFileItemDelegate::paint)
Summary: Dolphin crash drag drop tabs location (QX11PaintEngine, .., KIconEngine::pixm...
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
Depends on:
Reported: 2009-08-19 16:22 UTC by Maxime Corteel
Modified: 2018-03-26 22:29 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Maxime Corteel 2009-08-19 16:22:40 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-15-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
Dolphin crashed as I was dragging files (on a usb external hard drive) from a tab to another. It actually crashed when I hovered the location bar.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 0 (LWP 11817)]

Thread 2 (Thread 0x7fefe8e67950 (LWP 11835)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:217
#1  0x00007fefedd7af91 in ?? () from /usr/lib/libxine.so.1
#2  0x00007feff797f3ba in start_thread (arg=<value optimized out>) at pthread_create.c:297
#3  0x00007feff9d55fcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7feffe679750 (LWP 11817)):
[KCrash Handler]
#5  malloc_consolidate (av=0x7feff9fdda00) at malloc.c:4891
#6  0x00007feff9cea8f1 in _int_malloc (av=0x7feff9fdda00, bytes=38821744) at malloc.c:4229
#7  0x00007feff9cec828 in *__GI___libc_malloc (bytes=1024) at malloc.c:3551
#8  0x00007feffaf2e4f1 in QX11PaintEngine (this=0x24a7c60) at ../../include/QtGui/private/../../../src/gui/painting/qdatabuffer_p.h:66
#9  0x00007feffae3c30d in QX11PixmapData::paintEngine (this=<value optimized out>) at image/qpixmap_x11.cpp:2083
#10 0x00007feffae86be8 in QPainter::begin (this=0x7fff066b9850, pd=0x7fff066b97f0) at painting/qpainter.cpp:1681
#11 0x00007feffc2b861e in KIconEngine::pixmap (this=<value optimized out>, size=<value optimized out>, mode=<value optimized out>, state=<value optimized out>)
    at /build/buildd/kde4libs-4.3.0/kdeui/icons/kiconengine.cpp:127
#12 0x00007feffae05175 in QIcon::pixmap (this=<value optimized out>, size=@0x235d650, mode=38771024, state=QIcon::On) at image/qicon.cpp:713
#13 0x00007feffe129b04 in KFileItemDelegate::paint (this=0x244fc00, painter=0x7fff066ba180, option=@0x7fff066b9e80, index=@0x251e780)
    at /build/buildd/kde4libs-4.3.0/kio/kio/kfileitemdelegate.cpp:1211
#14 0x00007feffd67b50b in DolphinFileItemDelegate::paint (this=0x244fc00, painter=0x7fff066ba180, option=@0x235d650, index=@0x251e780)
    at /build/buildd/kdebase-4.3.0/apps/dolphin/src/dolphinfileitemdelegate.cpp:60
#15 0x00007feffb27bb50 in QListView::paintEvent (this=0x244b720, e=0x7fff066ba0a0) at itemviews/qlistview.cpp:1190
#16 0x00007feffc2db2f5 in KCategorizedView::paintEvent (this=0x244b720, event=0x7fff066bb0c0) at /build/buildd/kde4libs-4.3.0/kdeui/itemviews/kcategorizedview.cpp:727
#17 0x00007feffadbaed6 in QWidget::event (this=0x244b720, event=0x7fff066bb0c0) at kernel/qwidget.cpp:7687
#18 0x00007feffb12df0b in QFrame::event (this=0x244b720, e=0x7fff066bb0c0) at widgets/qframe.cpp:559
#19 0x00007feffb263c0d in QAbstractItemView::viewportEvent (this=0x244b720, event=0x7fff066bb0c0) at itemviews/qabstractitemview.cpp:1476
#20 0x00007feffa8d39b8 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0x2431940, event=0x7fff066bb0c0) at kernel/qcoreapplication.cpp:726
#21 0x00007feffad69f1c in QApplicationPrivate::notify_helper (this=0x10f25c0, receiver=0x2431940, e=0x7fff066bb0c0) at kernel/qapplication.cpp:4052
#22 0x00007feffad7218a in QApplication::notify (this=0x7fff066bc0d0, receiver=0x2431940, e=0x7fff066bb0c0) at kernel/qapplication.cpp:4021
#23 0x00007feffc2f171b in KApplication::notify (this=0x7fff066bc0d0, receiver=0x2431940, event=0x7fff066bb0c0) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302
#24 0x00007feffa8d46ac in QCoreApplication::notifyInternal (this=0x7fff066bc0d0, receiver=0x2431940, event=0x7fff066bb0c0) at kernel/qcoreapplication.cpp:610
#25 0x00007feffadc2125 in QWidgetPrivate::drawWidget (this=0x244bbd0, pdev=0x1568ab8, rgn=@0x7fff066bb430, offset=@0x7fff066bb420, flags=68, sharedPainter=0x0, backingStore=0x227d1d0)
    at kernel/qwidget.cpp:5079
#26 0x00007feffaf3c89e in QWidgetBackingStore::sync (this=0x227d1d0) at painting/qbackingstore.cpp:1261
#27 0x00007feffadb3e00 in QWidgetPrivate::syncBackingStore (this=0x227d490) at kernel/qwidget.cpp:1603
#28 0x00007feffadbad6d in QWidget::event (this=0x227bab0, event=0x24f4680) at kernel/qwidget.cpp:7827
#29 0x00007feffb14889b in QMainWindow::event (this=0x227bab0, event=0x24f4680) at widgets/qmainwindow.cpp:1399
#30 0x00007feffc3fea88 in KXmlGuiWindow::event (this=0x7feff9fdda00, ev=0x2505f70) at /build/buildd/kde4libs-4.3.0/kdeui/xmlgui/kxmlguiwindow.cpp:131
#31 0x00007feffad69f4d in QApplicationPrivate::notify_helper (this=0x10f25c0, receiver=0x227bab0, e=0x24f4680) at kernel/qapplication.cpp:4056
#32 0x00007feffad7218a in QApplication::notify (this=0x7fff066bc0d0, receiver=0x227bab0, e=0x24f4680) at kernel/qapplication.cpp:4021
#33 0x00007feffc2f171b in KApplication::notify (this=0x7fff066bc0d0, receiver=0x227bab0, event=0x24f4680) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302
#34 0x00007feffa8d46ac in QCoreApplication::notifyInternal (this=0x7fff066bc0d0, receiver=0x227bab0, event=0x24f4680) at kernel/qcoreapplication.cpp:610
#35 0x00007feffa8d531a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x10cd320) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#36 0x00007feffa8fde03 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#37 0x00007feff5f5320a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#38 0x00007feff5f568e0 in ?? () from /usr/lib/libglib-2.0.so.0
#39 0x00007feff5f56a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#40 0x00007feffa8fda8f in QEventDispatcherGlib::processEvents (this=0x10ccb50, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#41 0x00007feffae02bdf in QGuiEventDispatcherGlib::processEvents (this=0x7feff9fdda00, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#42 0x00007feffa8d2f42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 107724800}) at kernel/qeventloop.cpp:149
#43 0x00007feffa8d3314 in QEventLoop::exec (this=0x7fff066bc040, flags={i = 107724880}) at kernel/qeventloop.cpp:201
#44 0x00007feffa8d55e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#45 0x00000000004396ed in main (argc=6, argv=0x7fff066bc5b8) at /build/buildd/kdebase-4.3.0/apps/dolphin/src/main.cpp:94

Reported using DrKonqi
Comment 1 Dario Andres 2009-08-19 17:03:14 UTC
- Do you think you will be able to reproduce the crash at will ?
Comment 2 Maxime Corteel 2009-08-19 17:58:41 UTC
I'm not sure what really causes the crash but it has happened twice. I suppose I could do it again yes...
Comment 3 Peter Penz 2009-12-18 18:25:13 UTC
I've set this report to WAITINGFORINFO, I cannot reproduce the crash :-(
Comment 4 Julian Steinmann 2018-03-25 11:59:56 UTC
I cannot reproduce this crash either. Unless @Maxime still experiences this behavior, I am going to close this bug soon.
Comment 5 Julian Steinmann 2018-03-25 13:47:14 UTC
After taking a closer look at the backtrace it seems like this is a crash in libxine, which is no longer in use. Closing.
Comment 6 Maxime Corteel 2018-03-25 18:41:30 UTC
Wow, I had forgotten all about that. Sorry for not closing it sooner!
Comment 7 Christoph Feck 2018-03-26 13:23:20 UTC
Julian, it is thread 1 which crashes. This is most probably unrelated to the xine thread, but would need a valgrind log to investigate the memory corruption.

Let's avoid these steps for the Qt4 versions, though.
Comment 8 Julian Steinmann 2018-03-26 19:28:08 UTC
Apparently I suck at reading backtraces... I guess we can still mark this RESOLVED, or should I reopen the report in such a case?
Comment 9 Christoph Feck 2018-03-26 22:29:52 UTC
No, because the is the Qt4 version, which is unmaintained anyway.