Bug 322969 - Crash when closing Dolphin
Summary: Crash when closing Dolphin
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 2.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-30 00:10 UTC by Rodrigo Alonso
Modified: 2013-08-24 18:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 4.11.1


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rodrigo Alonso 2013-07-30 00:10:15 UTC
Application: dolphin (2.2)
KDE Platform Version: 4.10.5
Qt Version: 4.8.4
Operating System: Linux 3.9.11-200.fc18.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
I opened some files. The files were opened correctly. Then I closed Dolphin using the close button, and it crashed.

Specs:
Fedora 18
Pentium T4500
2GB RAM

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fdcdb867880 (LWP 5345))]

Thread 2 (Thread 0x7fdcce132700 (LWP 5348)):
#0  0x00000038782e9a5d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x000000387aa47d24 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7fdcc8002bb0, timeout=-1, context=0x7fdcc80009a0) at gmain.c:3584
#2  g_main_context_iterate (context=context@entry=0x7fdcc80009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3285
#3  0x000000387aa47e44 in g_main_context_iteration (context=0x7fdcc80009a0, may_block=1) at gmain.c:3351
#4  0x00000038827a5fa6 in QEventDispatcherGlib::processEvents (this=0x7fdcc80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x00000038827765ef in QEventLoop::processEvents (this=this@entry=0x7fdcce131cd0, flags=...) at kernel/qeventloop.cpp:149
#6  0x0000003882776878 in QEventLoop::exec (this=0x7fdcce131cd0, flags=...) at kernel/qeventloop.cpp:204
#7  0x0000003882678980 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#8  0x0000003882756e1f in QInotifyFileSystemWatcherEngine::run (this=0x1520ee0) at io/qfilesystemwatcher_inotify.cpp:256
#9  0x000000388267b95c in QThreadPrivate::start (arg=0x1520ee0) at thread/qthread_unix.cpp:338
#10 0x0000003878a07d15 in start_thread (arg=0x7fdcce132700) at pthread_create.c:308
#11 0x00000038782f253d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 1 (Thread 0x7fdcdb867880 (LWP 5345)):
[KCrash Handler]
#6  QTextEdit::mouseMoveEvent (this=0x1bd7d80, e=0x7fff5610e190) at ../../src/gui/image/qpixmapfilter_p.h:149
#7  0x0000003886819f7b in QWidget::event (this=0x1bd7d80, event=0x7fff5610e190) at kernel/qwidget.cpp:8360
#8  0x0000003886bc49f6 in QFrame::event (this=0x1bd7d80, e=0x7fff5610e190) at widgets/qframe.cpp:557
#9  0x0000003882777aa6 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<optimized out>, receiver=0x1b59530, event=0x7fff5610e190) at kernel/qcoreapplication.cpp:1059
#10 0x00000038867ca59c in QApplicationPrivate::notify_helper (this=0x131c970, receiver=0x1b59530, e=0x7fff5610e190) at kernel/qapplication.cpp:4558
#11 0x00000038867cf2ab in QApplication::notify (this=<optimized out>, receiver=0x1b59530, e=0x7fff5610e190) at kernel/qapplication.cpp:4105
#12 0x000000388b0455c6 in KApplication::notify (this=0x7fff5610ee10, receiver=0x1b59530, event=0x7fff5610e190) at /usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311
#13 0x000000388277793e in QCoreApplication::notifyInternal (this=0x7fff5610ee10, receiver=0x1b59530, event=0x7fff5610e190) at kernel/qcoreapplication.cpp:949
#14 0x00000038867cb40b in QApplicationPrivate::sendMouseEvent (receiver=0x1b59530, event=0x7fff5610e190, alienWidget=0x162fa10, nativeWidget=0x13a2090, buttonDown=0x388729e268 <qt_button_down>, lastMouseReceiver=..., spontaneous=true) at ../../src/corelib/kernel/qcoreapplication.h:231
#15 0x0000003886845b74 in QETWidget::translateMouseEvent (this=0x13a2090, event=<optimized out>) at kernel/qapplication_x11.cpp:4537
#16 0x0000003886844901 in QApplication::x11ProcessEvent (this=0x7fff5610ee10, event=0x7fff5610e900) at kernel/qapplication_x11.cpp:3660
#17 0x000000388686aa5c in x11EventSourceDispatch (s=s@entry=0x1316760, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#18 0x000000387aa47a55 in g_main_dispatch (context=0x131cb50) at gmain.c:2715
#19 g_main_context_dispatch (context=context@entry=0x131cb50) at gmain.c:3219
#20 0x000000387aa47d88 in g_main_context_iterate (context=context@entry=0x131cb50, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3290
#21 0x000000387aa47e44 in g_main_context_iteration (context=0x131cb50, may_block=1) at gmain.c:3351
#22 0x00000038827a5f86 in QEventDispatcherGlib::processEvents (this=0x12e0260, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#23 0x000000388686a73e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#24 0x00000038827765ef in QEventLoop::processEvents (this=this@entry=0x7fff5610ecd0, flags=...) at kernel/qeventloop.cpp:149
#25 0x0000003882776878 in QEventLoop::exec (this=0x7fff5610ecd0, flags=...) at kernel/qeventloop.cpp:204
#26 0x000000388277b708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#27 0x000000388ea4f857 in kdemain (argc=5, argv=0x7fff5610ef48) at /usr/src/debug/kde-baseapps-4.10.5/dolphin/src/main.cpp:90
#28 0x0000003878221a05 in __libc_start_main (main=0x4008a0 <main(int, char**)>, argc=5, ubp_av=0x7fff5610ef48, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff5610ef38) at libc-start.c:225
#29 0x00000000004008d1 in _start ()

Possible duplicates by query: bug 310801, bug 309421, bug 268533, bug 267850, bug 262675.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2013-07-30 08:22:56 UTC
Thanks for the bug report. Hm, the backtrace looks like bug 309421.

Did you rename a file before the crash? At the moment, I don't see any other explanation why QTextEdit::mouseMoveEvent() appears in the backtrace.

Moreover, is the crash reproducible for you?

Thanks for your help.
Comment 2 Rodrigo Alonso 2013-07-30 13:49:03 UTC
Yes, I renamed several files (8, to be more precise) before the crash.

Unfortunately, I've been unable to reproduce the crash. Sorry.

Rodrigo Alonso


2013/7/30 Frank Reininghaus <frank78ac@googlemail.com>

> https://bugs.kde.org/show_bug.cgi?id=322969
>
> --- Comment #1 from Frank Reininghaus <frank78ac@googlemail.com> ---
> Thanks for the bug report. Hm, the backtrace looks like bug 309421.
>
> Did you rename a file before the crash? At the moment, I don't see any
> other
> explanation why QTextEdit::mouseMoveEvent() appears in the backtrace.
>
> Moreover, is the crash reproducible for you?
>
> Thanks for your help.
>
> --
> You are receiving this mail because:
> You reported the bug.
>
Comment 3 Frank Reininghaus 2013-08-24 18:08:29 UTC
Git commit 85f29746327f6242b0084b0492462112d8d2635c by Frank Reininghaus.
Committed on 24/08/2013 at 18:06.
Pushed by freininghaus into branch 'KDE/4.11'.

Delay the deletion of the role editor as long as possible

This should prevent crashes that can be caused if the view is closed in
a nested event loop that is run from the role editor.
FIXED-IN: 4.11.1
REVIEW: 111988

M  +14   -7    dolphin/src/kitemviews/kstandarditemlistwidget.cpp

http://commits.kde.org/kde-baseapps/85f29746327f6242b0084b0492462112d8d2635c