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 157149 - a running beagle causes blam to corrupt collection.xml
a running beagle causes blam to corrupt collection.xml
Status: RESOLVED DUPLICATE of bug 303918
Product: blam
Classification: Other
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Mikael Hallendal
Mikael Hallendal
: 156141 157388 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-11-02 17:49 UTC by Alex Graveley
Modified: 2005-05-12 13:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alex Graveley 2004-11-02 17:49:40 UTC 
If you run beagle while blam is running and then exit blam, blam throws a
Sharing Violation exception while trying to write the collection.xml file.  The
next time you run blam, it will revert to the default feed list.

You can try writing collection.xml to temp file in the same directory, and then
move it over using File.Move.
Comment 1 Mikael Hallendal 2004-11-05 01:27:54 UTC 
*** Bug 157388 has been marked as a duplicate of this bug. ***
Comment 2 Fredrik Hedberg 2005-01-06 09:25:01 UTC 
This was Beagle's fault and should have been fixed in CVS. Please confirm.
Comment 3 Alex Graveley 2005-01-06 09:53:30 UTC 
Well, even if it is beagle's fault, blam needs to handle this more gracefully.
Comment 4 Mikael Hallendal 2005-01-06 12:37:53 UTC 
I totally agree that this should be handled better by Blam.
Comment 5 Mikael Hallendal 2005-04-10 20:25:44 UTC 
*** Bug 156141 has been marked as a duplicate of this bug. ***
Comment 6 Mikael Hallendal 2005-05-12 13:13:05 UTC 

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