Bug 167086 - Dolphin crashes after move if duplicated files were renamed while being moved
Summary: Dolphin crashes after move if duplicated files were renamed while being moved
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: RedHat Enterprise Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-20 19:23 UTC by Marcelo Sales
Modified: 2008-11-20 02:22 UTC (History)
2 users (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 Marcelo Sales 2008-07-20 19:23:59 UTC
Version:            (using KDE 4.0.98)
Installed from:    RedHat RPMs
OS:                Linux

A little difficult to explain, but easy to reproduce:
1. Drag two files from one folder to another where files with their names already exist.
2. Choose "Move" in the menu which opens when you drop them
3. Dolphin opens the duplicated file dialog. Give another name to the file and click "Rename"
4. Dolphin opens the duplicated file dialog for the second file (*).  Click the "Ignore" button.
5. Dolphin crashes

(*) Here, notice that the dialog offers again the options to rename, ignore, overwrite or cancel. This behaviour may be related to the crash that happens later, because this is the last file being moved and normally, in this case, the given options are rename, overwrite or cancel. The simplified dialog would have been shown if you had chosen ignore at the first file.


As a suggestion, I think that, from the usability point of view, it would be better to keep the same duplicated file dialog in all cases, instead of using a different one on the last file. Uniformity is better and I see no prejudice in doing this. When the user is moving/copying many files, and many of them are duplicated, he/she gets used with the permitted actions and the position of the buttons during the long operation. He/she is concentrated in renaming, ignoring or overwriting each file and the last dialog, being different from the previous ones, breaks the pattern and distracts the user.
Comment 1 Pino Toscano 2008-07-20 19:27:09 UTC
Could you please attach a backtrace, as explained in the page:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
? Thanks!
Comment 2 Dario Andres 2008-07-21 03:35:25 UTC
May be related to this : http://bugs.kde.org/show_bug.cgi?id=157601#c9 ?
Comment 3 Christophe Marin 2008-11-19 13:56:37 UTC
No backtrace was provided (comment #1). Closing.
Comment 4 Marcelo Sales 2008-11-19 14:07:23 UTC
I don't know how to generate the backtrace with debug symbols, but I've provided short step by step procedures on how to get the error. Those are reproducible 100% of the time. Did you try it before closing?
Comment 5 Christophe Marin 2008-11-19 21:36:47 UTC
> I don't know how to generate the backtrace with debug symbols

That's why the comment #1 contains a link : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports 

If you're able to reproduce the crash, the crash window will contain the debug symbols once the appropriate packages are installed.

Comment 6 Marcelo Sales 2008-11-20 02:09:01 UTC
I'm not able to reproduce this crash any more. It must have been already solved. Thanks.
Comment 7 Christophe Marin 2008-11-20 02:22:28 UTC
Thank you for your feedback. Changing the resolution.