After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 324331 - overwrite confirmation dialog with extra button leads to crash when overwriting.
overwrite confirmation dialog with extra button leads to crash when overwriting.
Status: RESOLVED DUPLICATE of bug 324262
Product: nautilus
Classification: Core
Component: File and Folder Operations
0.x.x [obsolete]
Other Linux
: High major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-12-17 12:45 UTC by Claudio Saavedra
Modified: 2005-12-17 13:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
propossed fix (2.22 KB, patch)
2005-12-17 12:49 UTC, Claudio Saavedra 		none Details | Review

Description Claudio Saavedra 2005-12-17 12:45:45 UTC 
There is an extra button in the "overwrite confirmation" dialog in nautilus.
This button says "Conflict While Copying" and I really think this was intended
to be the "secondary-text" parameter in eel_run_simple_dialog () call (the
attached should clarify this).

This extra button leads to the following wrong behaviour: 

1. Choosing "skip" will overwrite the files anyway.
2. Choosing "overwrite" will make nautilus crash.
3. Similar strange behaviours...

I will attach a patch that fixes this issue.

I am setting to "major" severity and "high" priority because this is leading
users to loose files.
Comment 1 Claudio Saavedra 2005-12-17 12:49:45 UTC 
Created attachment 56093 [details] [review]
propossed fix

Removing extra button and moving default action to the end of the switch
statement.

Ok to commit?
Comment 2 Sebastien Bacher 2005-12-17 13:00:45 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

This is due to an eel API change as explained by the other bug

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