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 314631 - Executing "beagle-build-index --recursive ~" deletes all user data.
Executing "beagle-build-index --recursive ~" deletes all user data.
Status: RESOLVED FIXED
Product: beagle
Classification: Other
Component: General
0.0.x
Other Linux
: Normal critical
: ---
Assigned To: Beagle Bugs
Beagle Bugs
: 315994 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-08-27 02:20 UTC by Alasdair Dinsdale-Arsenault
Modified: 2005-09-12 16:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alasdair Dinsdale-Arsenault 2005-08-27 02:20:45 UTC 
Distribution/Version: Gentoo

Here's a little bit of frightening functionality that should be removed from
Beagle-Build-Index. I was playing around the Beagle earlier this night on my
Gentoo box when I decided to see if I couldn't get more results. So, I executed
"beagle-build-index --recursive ~" on my system. But apparently Beagle
recursively went through everything and nuked it - Bookmarks, images, projects,
etc. I'm glad I had backups, but geez, this can't be right, can it? Even if I'm
not using Beagle-Build-Index correctly, there should be safeguards to ensure
that Beagle can't nuke a users /home directory, right?

By the way, a demonstration of what I'm talking about can be seen at this
address: http://sec.sankyuu.com/beagle-bug/ 
(It's my personal webserver so do be patient if it is slow.)

By the way, I was lucky enough to recover most of my files doing some fancy dd
and reiserfsck stuff, and got the rest from a previous backup I did a week ago
(first backup in a year and a half - pretty lucky, huh?) But this scared the
crap out of me.
Comment 1 Debajyoti Bera 2005-08-27 06:14:43 UTC 
I vote for this bug. Somehow the version I am using needs a --target argument. I
by mistake gave the wrong to --target (dunno what was thinking at that moment
:P) and whoops... my music collection vanished into thin air. I was quick in
pressing ctrl-c but the damage was already done.

I stronly suggest a confirmation regarding the index_path and to_index_dir
before carrying out the actual creation.

PS: I have to store the music on Fat32 for various reasons - got back the files
using an undelete software but with garbled names. Sigh ...
Comment 2 Joe Shaw 2005-09-07 20:07:37 UTC 
This has been fixed in CVS for some time.  We'll get a release with it out there
soon.
Comment 3 Joe Shaw 2005-09-12 16:21:24 UTC 
*** Bug 315994 has been marked as a duplicate of this bug. ***