Bug 181128 - Dolphin crashes when an open folder is renamed
Summary: Dolphin crashes when an open folder is renamed
Status: RESOLVED DUPLICATE of bug 180156
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Compiled Sources Unspecified
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-18 02:01 UTC by Todd
Modified: 2009-01-18 18:26 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 Todd 2009-01-18 02:01:02 UTC
Version:            (using Devel)
Installed from:    Compiled sources

If I open a folder as a tab or in another window in Dolphin, then rename that folder, Dolphin crashes immediately.

Steps to reproduce (version 1):
1. Open Dolphin
2. Right click on a blank area and click Create New > Folder
3. Name it "test"
4. Middle-click on the new folder to open it in a background tab (but stay in the current tab)
5. Right click on the "test" folder and click Rename.
6. Name it "test2"

Steps to reproduce (version 2):
1. Open Dolphin
2. Right click on a blank area and click Create New > Folder
3. Name it "test"
4. Right click on the folder and click "Open in New Window"
5. A new dolphin window will open.  Go back to the original window.
6. Right click on the "test" folder and click Rename.
7. Name it "test2"


Dolphin should crash if you do either of these.
Comment 1 Dario Andres 2009-01-18 03:23:15 UTC
Here using:

Qt: 4.4.3 + qt-copy-patches-910240
KDE: 4.2.60 (KDE 4.2.60 (KDE 4.3 >= 20090116))
kdelibs svn rev. 912325 / kdebase svn rev. 912325
on ArchLinux x86_64 - Kernel 2.6.28

I can't reproduce the crashes.

What KDE version (or SVN revision) are you using?

(I think David made some change related to a similar bug)
Comment 2 Todd 2009-01-18 05:15:41 UTC
I am using the latest opensuse 11.1 factory release, which should be version 4.2 RC.
Comment 3 Paweł Prażak 2009-01-18 10:58:41 UTC
I can reproduce this bug.

openSUSE 11.1 x86_64
Qt: 4.4.3
KDE: 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) "release 78.1"
Plasma Workspace: 0.3

backtrace

Application: Dolphin (dolphin), signal SIGSEGV
0x00007fea65649ce1 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7fea69b5c750 (LWP 20137))]

Thread 2 (Thread 0x7fea598dd950 (LWP 20155)):
#0  0x00007fea65674642 in select () from /lib64/libc.so.6
#1  0x00007fea663be366 in ?? () from /usr/lib64/libQtCore.so.4
#2  0x00007fea662f5f72 in ?? () from /usr/lib64/libQtCore.so.4
#3  0x00007fea66082070 in start_thread () from /lib64/libpthread.so.0
#4  0x00007fea6567b0ed in clone () from /lib64/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fea69b5c750 (LWP 20137)):
[KCrash Handler]
#5  0x00007fea66390fd9 in QUrl::operator=(QUrl const&) () from /usr/lib64/libQtCore.so.4
#6  0x00007fea6751d1f9 in KUrl::operator=(KUrl const&) () from /usr/lib64/libkdecore.so.5
#7  0x00007fea69611bfd in KFileItem::setUrl(KUrl const&) () from /usr/lib64/libkio.so.5
#8  0x00007fea695fc922 in ?? () from /usr/lib64/libkio.so.5
#9  0x00007fea695ff49a in KDirModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5
#10 0x00007fea663f2454 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#11 0x00007fea695e627a in KDirLister::redirection(KUrl const&, KUrl const&) () from /usr/lib64/libkio.so.5
#12 0x00007fea695f4cbe in ?? () from /usr/lib64/libkio.so.5
#13 0x00007fea695f54e7 in ?? () from /usr/lib64/libkio.so.5
#14 0x00007fea695f5c79 in ?? () from /usr/lib64/libkio.so.5
#15 0x00007fea695f5ef8 in ?? () from /usr/lib64/libkio.so.5
#16 0x00007fea663f2454 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#17 0x00007fea696009d7 in OrgKdeKDirNotifyInterface::FileRenamed(QString const&, QString const&) () from /usr/lib64/libkio.so.5
#18 0x00007fea69600af8 in OrgKdeKDirNotifyInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5
#19 0x00007fea671fc4cf in ?? () from /usr/lib64/libQtDBus.so.4
#20 0x00007fea6720361f in ?? () from /usr/lib64/libQtDBus.so.4
#21 0x00007fea663ed105 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#22 0x00007fea6685b1bd in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#23 0x00007fea66862f8a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#24 0x00007fea67ce5afb in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#25 0x00007fea663de091 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#26 0x00007fea663ded3a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#27 0x00007fea66406863 in ?? () from /usr/lib64/libQtCore.so.4
#28 0x00007fea627920db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#29 0x00007fea627958ad in ?? () from /usr/lib64/libglib-2.0.so.0
#30 0x00007fea62795a6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#31 0x00007fea664064ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#32 0x00007fea668eb9af in ?? () from /usr/lib64/libQtGui.so.4
#33 0x00007fea663dc9a2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#34 0x00007fea663dcb2d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#35 0x00007fea663deffd in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#36 0x0000000000441ced in _start ()

Comment 4 Dario Andres 2009-01-18 13:16:14 UTC
Bug 180156 is the report I talked about... (same backtrace and situation). It's already fixed in trunk and ready for KDE4.2 (that explains how I couldn't reproduce it ) :)
Thanks to all

*** This bug has been marked as a duplicate of bug 180156 ***
Comment 5 Todd 2009-01-18 18:26:10 UTC
Yeah, that looks like the same thing to me as well.  Good to know it was fixed, I was a bit surprised when it looked like no one had run into it before.