Bug 206925 - dolphin crashes when I cut a folder
Summary: dolphin crashes when I cut a folder
Status: RESOLVED DUPLICATE of bug 200125
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-10 02:02 UTC by Gatoso
Modified: 2009-09-11 09:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gatoso 2009-09-10 02:02:43 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-ARCH i686

What I was doing when the application crashed:
I cut a folder from another folder then I opened a new tab on dolphin (to paste the folder) and it crashed...

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  0xb66ff6f9 in QUrl (this=0xbfe846b0, other=@0x8) at io/qurl.cpp:3936
#7  0xb730e8b9 in KUrl::KUrl () from /usr/lib/libkdecore.so.5
#8  0xb7d3998e in KFileItem::url () from /usr/lib/libkio.so.5
#9  0xb7bfc2f6 in KFilePreviewGenerator::Private::applyCutItemEffect () from /usr/lib/libkfile.so.4
#10 0xb7bfe636 in KFilePreviewGenerator::Private::updateIcons () from /usr/lib/libkfile.so.4
#11 0xb7bfe8a2 in KFilePreviewGenerator::Private::delayedIconUpdate () from /usr/lib/libkfile.so.4
#12 0xb7bff916 in KFilePreviewGenerator::qt_metacall () from /usr/lib/libkfile.so.4
#13 0xb67609ac in QMetaObject::activate (sender=0x92a21f8, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x8) at kernel/qobject.cpp:3112
#14 0xb67615e2 in QMetaObject::activate (sender=0x92a21f8, m=0xb683c264, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#15 0xb679aa87 in QTimer::timeout (this=0x92a21f8) at .moc/release-shared/moc_qtimer.cpp:128
#16 0xb676605e in QTimer::timerEvent (this=0x92a21f8, e=0xbfe84cf0) at kernel/qtimer.cpp:261
#17 0xb675ab5f in QObject::event (this=0x92a21f8, e=0xbfe84cf0) at kernel/qobject.cpp:1074
#18 0xb695e964 in QApplicationPrivate::notify_helper (this=0x8c44418, receiver=0x92a21f8, e=0xbfe84cf0) at kernel/qapplication.cpp:4056
#19 0xb696604c in QApplication::notify (this=0xbfe8505c, receiver=0x92a21f8, e=0xbfe84cf0) at kernel/qapplication.cpp:3603
#20 0xb768c46a in KApplication::notify () from /usr/lib/libkdeui.so.5
#21 0xb674afcb in QCoreApplication::notifyInternal (this=0xbfe8505c, receiver=0x92a21f8, event=0xbfe84cf0) at kernel/qcoreapplication.cpp:610
#22 0xb677879e in QTimerInfoList::activateTimers (this=0x8c3c194) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#23 0xb6775780 in timerSourceDispatch (source=0x8c3c160) at kernel/qeventdispatcher_glib.cpp:165
#24 0xb5d6cd98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb5d703e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#26 0xb5d70513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb67756cc in QEventDispatcherGlib::processEvents (this=0x8c38f18, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:327
#28 0xb69fc695 in QGuiEventDispatcherGlib::processEvents (this=0x8c38f18, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#29 0xb6749579 in QEventLoop::processEvents (this=0xbfe84fb4, flags=) at kernel/qeventloop.cpp:149
#30 0xb67499ca in QEventLoop::exec (this=0xbfe84fb4, flags={i = 0}) at kernel/qeventloop.cpp:201
#31 0xb674be3f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#32 0xb695e7e7 in QApplication::exec () at kernel/qapplication.cpp:3525
#33 0x0807a725 in main (argc=5, argv=0xbfe85234) at /home/jofko/kdemod/core/kdebase/src/kdebase-4.3.1/apps/dolphin/src/main.cpp:94

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-09-10 19:33:16 UTC
Thanks for the bug report! This looks like it might be related to bug 200125, but the backtrace is not 100% equal.

Does it always crash for you if you cut a folder and open a new tab? I could not reproduce that in KDE 4.3.1 and trunk.
Comment 2 Gatoso 2009-09-11 01:23:28 UTC
This happened twice or three times (I don't remember exactly how many times)

Now I can't reproduces the crashes... if I have the same issue, ever, I will report it...
Comment 3 Frank Reininghaus 2009-09-11 09:14:40 UTC
Thanks for the update! I think this is a duplicate of the other bug - the reason why the backtrace is different is probably that no items were cut in the other case, such that it couldn't crash in KFilePreviewGenerator::Private::applyCutItemEffect

This should be fixed now, please reopen this report if I'm wrong and you still see this crash in KDE 4.3.2 when it's out. Thanks.

*** This bug has been marked as a duplicate of bug 200125 ***