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 555058 - [backup-restore] Backup cann't be saved in folder which has space in name
[backup-restore] Backup cann't be saved in folder which has space in name
Status: RESOLVED DUPLICATE of bug 540516
Product: evolution
Classification: Applications
Component: Plugins
2.12.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-plugin-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-10-05 04:00 UTC by steven
Modified: 2009-10-29 16:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description steven 2008-10-05 04:00:17 UTC 
Version: 2.12

Evolution Backup
Can not use file names or directories that have spaces in them.
If a the path to the backup file has a space in it will not back up correctly.



Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.3 2008-01-08 (Red Hat, Inc)
BugBuddy Version: 2.20.1
Comment 1 André Klapper 2008-10-05 20:58:42 UTC 
Can you please provide an explicit example of your case?
Comment 2 steven 2008-10-06 10:44:42 UTC 
Just use the program with spaces in the path and you will see what I
mean.

It is not that it crashes as such just that it does not out the file in
the correct location.

ie if the path is

/home/steven/My Backup/evolution.tar.gz

will try and save it in "/home/steven/My" 

If the the path has no spaces everything OK

Just try it you will see.
Steven
Comment 3 Milan Crha 2009-10-29 16:43:52 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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