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 602325 - Can't restore settings from a backup file with a space in the path
Can't restore settings from a backup file with a space in the path
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: general
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-11-18 17:19 UTC by Martin Mai
Modified: 2010-11-15 03:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Martin Mai 2009-11-18 17:19:38 UTC
Origonally reported on https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/428795:

I've put my 'evolution-backup.tar.gz' on my desktop in Serbian localization. The folder name is "~/Radna površ", so the full path to the backup tarball was "/home/danilo/Radna površ/evolution-backup.tar.gz".

If I try to use that (either from the initial configuration window, or later from the "File > Restore configuration" menu), Evolution pops up a dialog box saying "Please select a valid backup file to restore."

Moving the backup file to a path which contains no spaces (even if it contains non-ASCII letters in it — I've tried with /home/danilo/бекап/evolution-backup.tar.gz) works correctly.
Comment 1 asharpham 2010-03-06 01:27:07 UTC
I moved it to a path with no spaces:
/home/alan/evolution_backups/evolution-backup.tar.gz
and it still doesn't work.

Alan
Comment 2 Vibha Yadav 2010-10-01 10:05:33 UTC
Can you please check again whether this issue still happens in Evolution
2.32.0 and update this report by adding a comment and changing the
"Version" field? Thanks a lot.
Comment 3 Felipe Besoaín Pino 2010-11-15 03:22:26 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!