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 410954 - beagle-exercise-file-system destroys any contents of directory named "1"
beagle-exercise-file-system destroys any contents of directory named "1"
Status: RESOLVED FIXED
Product: beagle
Classification: Other
Component: General
0.2.8
Other All
: Normal critical
: ---
Assigned To: Beagle Bugs
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2007-02-22 20:23 UTC by Jacek Konieczny
Modified: 2007-04-07 23:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jacek Konieczny 2007-02-22 20:23:38 UTC 
Please describe the problem:
beagle-exercise-filesystem command without any warning destroys any contents of a directory "1" in the current working directory.

Unfortunately my wife keeps a lot of precious files in $HOME/1... fortunately, we have backup.  

Steps to reproduce:
1. Create directory "1"
2. Put some important data there (just kidding)
3. Run "beagle-exercise-filesystem"



Actual results:
The data from directory "1" is lost. Numbered directories and empty files are put there instead.

Expected results:
When directory "1" already exists the tool should abort or ask for confirmation before continuing.

Does this happen every time?
Yes.

Other information:
Comment 1 Joe Shaw 2007-02-22 20:35:57 UTC 
Oof, I'm really sorry about that.

We should stop installing beagle-exercise-file-system, it's only supposed to be used for debugging by developers.
Comment 2 Jacek Konieczny 2007-02-23 07:43:45 UTC 
Yes, not installing it by default will solve the problem for regular users. Though, do not developers make mistakes too? I guess adding the check may be a good idea anyway.
Comment 3 Maciej (Matthew) Piechotka 2007-02-23 09:57:52 UTC 
May it should do not run if directory already exists? Except force option or something like that.
Comment 4 Łukasz Jernaś 2007-02-23 20:37:56 UTC 
Maybe it could run in the directory specified by the TMP variable, so it won't mess with anything needed? One can always change TMP for testing purposes on other mount points...
Comment 5 Debajyoti Bera 2007-04-07 23:49:04 UTC 
Its just a debugging tool. Developers are used to playing with fire ;-)
Anyway, it has been removed from svn (moved to attic/).