Bug 173725 - it crashes as I rename folder
Summary: it crashes as I rename folder
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:
Depends on:
Blocks:
 
Reported: 2008-10-28 02:44 UTC by Ricardo Varas Santana
Modified: 2009-01-02 11:46 UTC (History)
6 users (show)

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


Attachments
Dolphin with two windws before a crash (558.26 KB, image/png)
2009-01-01 12:39 UTC, Pedro Sá (kunst uber alles)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ricardo Varas Santana 2008-10-28 02:44:23 UTC
Version:           1.1 (using KDE 4.1.2)
OS:                Linux
Installed from:    SuSE RPMs

after renaming the folder, dolphin crashes right away and I get:
Application: Dolphin (dolphin), signal SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f11d2066700 (LWP 4497)]
[KCrash handler]
#5  0x00007f11d1687823 in KFileItem::isLocalFile () from /usr/lib64/libkio.so.5
#6  0x00007f11d1673e7d in ?? () from /usr/lib64/libkio.so.5
#7  0x00007f11d1674208 in ?? () from /usr/lib64/libkio.so.5
#8  0x00007f11cff43274 in QMetaObject::activate (sender=0x784bf0, 
    from_signal_index=<value optimized out>, to_signal_index=5, argv=0xcfa140)
    at kernel/qobject.cpp:3031
#9  0x00007f11d167cef7 in OrgKdeKDirNotifyInterface::FileRenamed ()
   from /usr/lib64/libkio.so.5
#10 0x00007f11d167d018 in OrgKdeKDirNotifyInterface::qt_metacall ()
   from /usr/lib64/libkio.so.5
#11 0x00007f11ced594a1 in QDBusConnectionPrivate::deliverCall (this=0x684c60, 
    object=0x784bf0, msg=@0x7b1ed8, metaTypes=@0x7b1ee0, slotIdx=5)
    at qdbusintegrator.cpp:849
#12 0x00007f11ced605ef in QDBusCallDeliveryEvent::placeMetaCall (this=
0xddbfd87ec820, object=0x7f11cb10efb8) at qdbusintegrator_p.h:130
#13 0x00007f11cff3df3d in QObject::event (this=0x784bf0, e=0x7b1e90)
    at kernel/qobject.cpp:1155
#14 0x00007f11ccba717d in QApplicationPrivate::notify_helper (this=0x68c850, 
    receiver=0x784bf0, e=0x7b1e90) at kernel/qapplication.cpp:3803
#15 0x00007f11ccbaef2a in QApplication::notify (this=0x7fffda0a2b10, 
    receiver=0x784bf0, e=0x7b1e90) at kernel/qapplication.cpp:3768
#16 0x00007f11d11b5dcb in KApplication::notify () from /usr/lib64/libkdeui.so.5
#17 0x00007f11cff2ee71 in QCoreApplication::notifyInternal (
    this=0x7fffda0a2b10, receiver=0x784bf0, event=0x7b1e90)
    at kernel/qcoreapplication.cpp:587
#18 0x00007f11cff2fb2a in QCoreApplicationPrivate::sendPostedEvents (
    receiver=0x0, event_type=0, data=0x66dd10) at kernel/qcoreapplication.h:209
#19 0x00007f11cff57713 in postEventSourceDispatch (s=<value optimized out>)
    at kernel/qcoreapplication.h:214
#20 0x00007f11c9c5f93a in g_main_context_dispatch ()
   from /usr/lib64/libglib-2.0.so.0
#21 0x00007f11c9c63040 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f11c9c631dc in g_main_context_iteration ()
   from /usr/lib64/libglib-2.0.so.0
#23 0x00007f11cff5739f in QEventDispatcherGlib::processEvents (this=0x68bb80, 
    flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319
#24 0x00007f11ccc37ccf in QGuiEventDispatcherGlib::processEvents (
    this=0x7f71c8, flags=<value optimized out>)
    at kernel/qguieventdispatcher_glib.cpp:198
#25 0x00007f11cff2d772 in QEventLoop::processEvents (
    this=<value optimized out>, flags={i = -636868032})
    at kernel/qeventloop.cpp:143
#26 0x00007f11cff2d8fd in QEventLoop::exec (this=0x7fffda0a2a80, flags=
      {i = -636867952}) at kernel/qeventloop.cpp:194
#27 0x00007f11cff2fded in QCoreApplication::exec ()
    at kernel/qcoreapplication.cpp:845
#28 0x000000000044066d in _start ()
#0  0x00007f11cb08e230 in nanosleep () from /lib64/libc.so.6
Comment 1 Oliver Putz 2008-10-28 08:02:48 UTC
Hi, did you perhaps directly level up from the folder you renamed? Could you please check if this bug is still valid in KDE-4.1.3 once it is released? I ask because the backtrace and description seem similar to bug #172945. (which should be fixed in KDE-4.1.3)
Comment 2 Ricardo Varas Santana 2008-10-28 19:12:47 UTC
Hi,
I was not doing anything with the renamed folder. I just opened a new dolphin window and browsed to the folder.
Of course I will check if this happens in KDE 4.1.3.
Comment 3 Simon St James 2008-11-01 18:14:47 UTC
If it still occurs in 4.1.3, please give precise steps to reproduce (e.g. it's not clear whether you renamed a folder in an instance of Dolphin and it crashed immediately or whether you renamed a folder, opened a new Dolphin, and had that one crash) and ensure that you have the KDE debug packages (as well as the Qt ones) and we should be better able to get to the bottom of things.  Thanks!
Comment 4 FiNeX 2008-11-14 14:40:13 UTC
Bug #174703, #173725 and #172643 seems similar.
Comment 5 francis 2008-11-27 11:43:34 UTC
Systeem:  openSUSE 11.1 Beta 5 (x86_64)
  KDE:  4.1.3 (KDE 4.1.3) "release 2.1"

I had the dolphin window split up in two. Then I created a symlink in the left window to a folder in the right window. And then I directly renamed that symlink.
consequence: 
1/ immediate crash
2/ after reopening dolphin, found that symlink was correctly renamed and still working

crashreport:
Programma: Dolphin (dolphin), signaal SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fcf7261b950 (LWP 4720)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00007fcf80a08c20 in ?? () from /usr/lib64/libkio.so.5
#6  0x00007fcf80a08cf0 in ?? () from /usr/lib64/libkio.so.5
#7  0x00007fcf80a0bfd7 in ?? () from /usr/lib64/libkio.so.5
#8  0x00007fcf80a0d1e6 in KDirModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5
#9  0x00007fcf81acc444 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib64/libQtCore.so.4
#10 0x00007fcf809f6825 in KDirLister::newItems(KFileItemList const&) ()
   from /usr/lib64/libkio.so.5
#11 0x00007fcf809f7520 in KDirLister::Private::emitItems() ()
   from /usr/lib64/libkio.so.5
#12 0x00007fcf809f8ebe in ?? () from /usr/lib64/libkio.so.5
#13 0x00007fcf80a04e95 in ?? () from /usr/lib64/libkio.so.5
#14 0x00007fcf80a051f8 in ?? () from /usr/lib64/libkio.so.5
#15 0x00007fcf81acc444 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib64/libQtCore.so.4
#16 0x00007fcf80a0dba7 in OrgKdeKDirNotifyInterface::FileRenamed(QString const&, QString const&) () from /usr/lib64/libkio.so.5
#17 0x00007fcf80a0dcc8 in OrgKdeKDirNotifyInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5
#18 0x00007fcf7e5154cf in ?? () from /usr/lib64/libQtDBus.so.4
#19 0x00007fcf7e51c61f in ?? () from /usr/lib64/libQtDBus.so.4
#20 0x00007fcf81ac70f5 in QObject::event(QEvent*) ()
   from /usr/lib64/libQtCore.so.4
#21 0x00007fcf7db741bd in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib64/libQtGui.so.4
#22 0x00007fcf7db7bf8a in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib64/libQtGui.so.4
#23 0x00007fcf80f69b6b in KApplication::notify(QObject*, QEvent*) ()
   from /usr/lib64/libkdeui.so.5
#24 0x00007fcf81ab8081 in QCoreApplication::notifyInternal(QObject*, QEvent*)
    () from /usr/lib64/libQtCore.so.4
#25 0x00007fcf81ab8d2a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#26 0x00007fcf81ae0853 in ?? () from /usr/lib64/libQtCore.so.4
#27 0x00007fcf7a86b0db in g_main_context_dispatch ()
   from /usr/lib64/libglib-2.0.so.0
#28 0x00007fcf7a86e8ad in ?? () from /usr/lib64/libglib-2.0.so.0
#29 0x00007fcf7a86ea6b in g_main_context_iteration ()
   from /usr/lib64/libglib-2.0.so.0
#30 0x00007fcf81ae04df in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x00007fcf7dc0496f in ?? () from /usr/lib64/libQtGui.so.4
#32 0x00007fcf81ab6992 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#33 0x00007fcf81ab6b1d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#34 0x00007fcf81ab8fed in QCoreApplication::exec() ()
   from /usr/lib64/libQtCore.so.4
#35 0x000000000043ffad in _start ()
Comment 6 Dario Andres 2008-12-19 03:09:49 UTC
Here using:

Qt: 4.4.3
KDE: 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2))
kdelibs svn rev. 898705 / kdebase svn rev. 898705
on ArchLinux x86_64 - 2.6.27.8

I can't reproduce the crash following the steps in comment 5.
Comment 7 Ricardo Varas Santana 2008-12-21 04:21:53 UTC
(In reply to comment #1)
> Hi, did you perhaps directly level up from the folder you renamed? Could you
> please check if this bug is still valid in KDE-4.1.3 once it is released? I ask
> because the backtrace and description seem similar to bug #172945. (which
> should be fixed in KDE-4.1.3)
> 

Hi, I confirm it is not happening in KDE-4.1.3. Have done it multiple times and it works perfectly.
Comment 8 francis 2008-12-21 14:59:07 UTC
tried it again, couldn't reproduce anymore 
after upgrade to :
OS:  Linux 2.6.27.7-9-default x86_64
Systeem:  openSUSE 11.1 (x86_64)
KDE:  4.1.3 (KDE 4.1.3) "release 4.9"

looks like it's solved
Comment 9 Pedro Sá (kunst uber alles) 2009-01-01 12:39:18 UTC
Created attachment 29796 [details]
Dolphin with two windws before a crash
Comment 10 Dario Andres 2009-01-01 13:24:45 UTC
@Pedro Sá: in that screenshot, Dolphin crashes after renaming the folder using the properties dialog and Clicking OK in a Split view? What KDE version or SVN revision are you using?

I can't reproduce the crash using:

Qt: 4.4.3 + qt-copy-patches-889120
KDE: 4.1.86 (KDE 4.1.86 (KDE 4.2 >= 20081221))
kdelibs svn rev. 903705 / kdebase svn rev. 903706
on ArchLinux x86_64 - Kernel 2.6.27.10
Comment 11 Pedro Sá (kunst uber alles) 2009-01-01 14:48:09 UTC
Yes, it crashes after renaming the folder using the properties dialog or F2 and clicking OK in a split view. 
maybe a small detail could be important, the folders have similar names 
/home/pedro/imagens-fotos/fotos (left)
/home/pedro/imagens/fotos (right)

i have tried in others folders and works ok, no crash
i'm reinstall dolphin

i'm using KDE 4.1.85 (KDE 4.2 Beta2)
kubuntu intrepid
Comment 12 Pedro Sá (kunst uber alles) 2009-01-01 23:11:37 UTC
i've reinstall Dolphin, now i can rename the folders, but if i move a renamed folder from left to right, dolphin crashes, the folder is moved. 
If i move a not renamed folder everything works fine.
Comment 13 FiNeX 2009-01-02 11:46:38 UTC
@Pedro Sà: If you can reproduce the crash, please open a new bug report. And don't forget to write the backtrace:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!