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 624283 - --confirm-overwrite only works with --save
--confirm-overwrite only works with --save
Status: RESOLVED NOTABUG
Product: zenity
Classification: Core
Component: general
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: Zenity Maintainers
Zenity Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-07-13 20:46 UTC by Victor Vargas
Modified: 2011-01-04 16:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Victor Vargas 2010-07-13 20:46:30 UTC
This report was originally filled at:
https://bugs.edge.launchpad.net/ubuntu/+source/zenity/+bug/432570


Steps to reproduce this issue:

zenity --file-selection --confirm-overwrite
will not warn you if you select an existing file, you will need to add the --save option
#This doesn't works

zenity --file-selection --confirm-overwrite --save
#This works
Comment 1 Arx Cruz 2011-01-03 19:14:20 UTC
This is not a bug, this is a normal behavior of zenity.
If you use zenity --file-selection --confirm-overwrite it just return the directory or filename you select when you click ok.
If you use zenity --file-selection --save (without --confirm-overwrite) that's means you don't care if you replace or not the filename you save.
If you use zenity --file-selection --confirm-overwrite --save, now that's will ask you if you want replace or not the file / directory.
Anyway, the only way to enter im save dialog mode is using the --save, zenity gives you a choice asking you if you want to be advised if a file already exists and you'll override this file (using the --confirm-overwrite) or not.
Perhaps, the use of --confirm-overwrite should be marked to be used only when the user use --save option, but this probably will break dependencies with old versions of zenity.
Comment 2 Arx Cruz 2011-01-04 16:27:48 UTC
I'm closing this bug since this is the normal behavior expected by zenity.