Bug 500537 - dolphin crash at undo to overwrite a file
Summary: dolphin crash at undo to overwrite a file
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-13 08:05 UTC by Nelson Chan
Modified: 2009-05-30 00:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-30 00:42:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 192547 0 None None None Never

Description Nelson Chan 2009-05-13 08:05:55 UTC
Description of problem:
dolphin crash at undo to overwrite a file 

Version-Release number of selected component (if applicable):
kdebase-4.2.2-2.fc11.x86_64
qt-4.5.0-14.fc11.x86_64
qt-4.5.0-14.fc11.i586

How reproducible:
Seems to be able to reproduce at will

Steps to Reproduce:
#1. navigate to any folder, move a file to trash by hitting [del]
#2. use another application other than dolphin itself to create a file of the
same name & path of the one remove in #1
------
E.g. 
i move a file called  "abc" in ~/test/ for #1
i open a terminal, echo "" > ~/test/abc
to make another "abc" file
------
#3. now switch back to dolphin and press ctrl-z to undo change,  dolphin claims
that file already exists and a information notification pop up (knotify4?) an
message of "Moving file.."
#4. click on the stop button (black square next to the pause button)
#5. dolphin crashes
#6. Notification stays there forever

  
Actual results:
#5 , #6

Expected results:
dolphin prompt for overwrite Y/N ?
Notification should disappear

Additional info:

Backtrace captured by kcrash:
--------------------------
Application: Dolphin (dolphin), signal SIGSEGV
0x0000003b772a5151 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f3cb84d2820 (LWP 2196))]

Thread 2 (Thread 0x7f3cb1505910 (LWP 3481)):
#0  0x0000003b772d9092 in select () from /lib64/libc.so.6
#1  0x0000003c66f21691 in ?? () from /usr/lib64/libQtCore.so.4
#2  0x0000003c66e5a221 in ?? () from /usr/lib64/libQtCore.so.4
#3  0x0000003b77e0687a in start_thread () from /lib64/libpthread.so.0
#4  0x0000003b772e04cd in clone () from /lib64/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f3cb84d2820 (LWP 2196)):
[KCrash Handler]
#5  0x0000000100000007 in ?? ()
#6  0x0000003c690e98e9 in KJob::kill(KJob::KillVerbosity) () from /usr/lib64/libkdecore.so.5
#7  0x0000003c69c01065 in KUiServerJobTracker::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdeui.so.5
#8  0x0000003c66f58612 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#9  0x0000003c69d42a88 in ?? () from /usr/lib64/libkdeui.so.5
#10 0x0000003c67c23314 in ?? () from /usr/lib64/libQtDBus.so.4
#11 0x0000003c67c2b02f in ?? () from /usr/lib64/libQtDBus.so.4
#12 0x0000003c66f526c9 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#13 0x0000003c6858deac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x0000003c685954de in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x0000003c69c05c66 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#16 0x0000003c66f42b7c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#17 0x0000003c66f4366a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#18 0x0000003c66f6c333 in ?? () from /usr/lib64/libQtCore.so.4
#19 0x0000003b7963818e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#20 0x0000003b7963b8e8 in ?? () from /lib64/libglib-2.0.so.0
#21 0x0000003b7963ba5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#22 0x0000003c66f6bfa6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#23 0x0000003c686220de in ?? () from /usr/lib64/libQtGui.so.4
#24 0x0000003c66f41452 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x0000003c66f41824 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x0000003c66f43919 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#27 0x000000000043fb95 in _start ()

--------------------------

Comment 1 Nelson Chan 2009-05-13 08:08:23 UTC
i've also reported on
https://bugs.kde.org/show_bug.cgi?id=192547

Comment 2 Chitlesh GOORAH 2009-05-13 12:30:04 UTC
Reassigned the bug properly

rpm -qf /usr/bin/dolphin
kdebase-4.2.2-3.fc10.i386

Comment 3 Steven M. Parrish 2009-05-30 00:42:41 UTC
Thank you for taking the time to report this issue upstream.  Going to close this as UPSTREAM, but don't worry we will monitor the upstream report for a resolution.


Note You need to log in before you can comment on or make changes to this bug.