Bug 253537 - Dolphin crashed while closing
Summary: Dolphin crashed while closing
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
: 201593 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-10-07 20:30 UTC by Ron Katzir
Modified: 2018-03-19 07:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Katzir 2010-10-07 20:30:10 UTC
Application: dolphin (1.5)
KDE Platform Version: 4.5.2 (KDE 4.5.2) "release 5"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-0.3-default i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
Dolphin crashed while closing, after dragging a file from it to a program. On openSUSE 11.3 with KDE 4.5.2

-- Backtrace:
Application: Dolphin (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5983710 (LWP 11426))]

Thread 2 (Thread 0xa9ffab70 (LWP 14401)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6cf0452 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xaf35a1d7 in metronom_sync_loop () from /usr/lib/libxine.so.1
#3  0xb6cebb25 in start_thread () from /lib/libpthread.so.0
#4  0xb60d846e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5983710 (LWP 11426)):
[KCrash Handler]
#7  QCoreApplication::postEvent (receiver=0x8a94920, event=0x89db1b8, priority=0) at kernel/qcoreapplication.cpp:1127
#8  0xb6e632fb in QCoreApplication::postEvent (receiver=0x8a94920, event=0x89db1b8) at kernel/qcoreapplication.cpp:1088
#9  0xb6e70ce4 in QObject::deleteLater (this=0x8a94920) at kernel/qobject.cpp:2158
#10 0xb64309fb in QDragManager::timerEvent (this=0x8652480, e=0xbff8d7c0) at kernel/qdnd_x11.cpp:1258
#11 0xb6e72774 in QObject::event (this=0x8652480, e=0xbff8d7c0) at kernel/qobject.cpp:1212
#12 0xb6398c64 in QApplicationPrivate::notify_helper (this=0x80b3aa8, receiver=0x8652480, e=0xbff8d7c0) at kernel/qapplication.cpp:4302
#13 0xb63a0bf7 in QApplication::notify (this=0xbff8db30, receiver=0x8652480, e=0xbff8d7c0) at kernel/qapplication.cpp:3706
#14 0xb747e911 in KApplication::notify (this=0xbff8db30, receiver=0x8652480, event=0xbff8d7c0) at /usr/src/debug/kdelibs-4.5.2/kdeui/kernel/kapplication.cpp:310
#15 0xb6e5fe0e in QCoreApplication::notifyInternal (this=0xbff8db30, receiver=0x8652480, event=0xbff8d7c0) at kernel/qcoreapplication.cpp:726
#16 0xb6e8e70e in sendEvent (this=0x80b6c34) at kernel/qcoreapplication.h:215
#17 QTimerInfoList::activateTimers (this=0x80b6c34) at kernel/qeventdispatcher_unix.cpp:618
#18 0xb6e8b675 in timerSourceDispatch (source=0x80b67b0) at kernel/qeventdispatcher_glib.cpp:184
#19 idleTimerSourceDispatch (source=0x80b67b0) at kernel/qeventdispatcher_glib.cpp:231
#20 0xb5be6b49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb5be7350 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0xb5be760e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0xb6e8bd4b in QEventDispatcherGlib::processEvents (this=0x80b2f78, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#24 0xb644919a in QGuiEventDispatcherGlib::processEvents (this=0x80b2f78, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#25 0xb6e5f11d in QEventLoop::processEvents (this=0xbff8da84, flags=...) at kernel/qeventloop.cpp:149
#26 0xb6e5f319 in QEventLoop::exec (this=0xbff8da84, flags=...) at kernel/qeventloop.cpp:201
#27 0xb6e63c70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#28 0xb6396164 in QApplication::exec () at kernel/qapplication.cpp:3581
#29 0xb2d58b7d in kdemain () from /usr/lib/libkdeinit4_dolphin.so
#30 0x0804e3f1 in _start ()

Possible duplicates by query: bug 208900, bug 201593.

Reported using DrKonqi
Comment 1 Peter Penz 2010-11-21 11:38:02 UTC
*** Bug 201593 has been marked as a duplicate of this bug. ***
Comment 2 Peter Penz 2010-11-21 11:40:15 UTC
Thanks for the report. Did the other program handle the dragged file already before you closed Dolphin? Is there a way you can reproduce this issue (e.g. which other program you've used, what kind of file you've dragged...)
Comment 3 Julian Steinmann 2018-03-19 07:29:33 UTC
Cannot reproduce this bug with Dolphin 17.12.3, closing for missing information. If you still experience this crash, please attach steps to reproduce (programs used etc.).