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 405372 - broken jpegs make beagle go into infinite loop
broken jpegs make beagle go into infinite loop
Status: RESOLVED FIXED
Product: beagle
Classification: Other
Component: General
0.2.16
Other Linux
: Normal critical
: ---
Assigned To: Beagle Bugs
Beagle Bugs
: 411943 424236 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-07 14:33 UTC by Andy Wingo
Modified: 2007-03-29 19:28 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
first 16 kB of a jpeg (16.00 KB, application/octet-stream)
2007-02-07 14:33 UTC, Andy Wingo 		  Details
patch from f-spot (392 bytes, patch)
2007-02-10 05:05 UTC, Larry Ewing 		none Details | Review

Description Andy Wingo 2007-02-07 14:33:13 UTC 
To reproduce: run beagle-extract-content on the attached file, which I produced using head --bytes=16k foo.jpg.

0.2.15.1 from Feisty.
Comment 1 Andy Wingo 2007-02-07 14:33:56 UTC 
Created attachment 82087 [details]
first 16 kB of a jpeg
Comment 2 Debajyoti Bera 2007-02-07 14:52:44 UTC 
You mean you "invented" the bad jpeg file by using only the first 16K bytes of a valid jpeg file ? Also, do you by any chance have F-Spot and if you do, does this image load file in F-Spot ? (Its not an excuse, I need to know this because beagle uses F-Spot's jpeg handling code).
Comment 3 Joe Shaw 2007-02-07 18:44:11 UTC 
Still an issue with 0.2.16, updating version.
Comment 4 Andy Wingo 2007-02-08 09:50:12 UTC 
I do have f-spot, and 0.3.2.0 does hang in an infinite loop when trying to import this one. Funny, because I had imported it before with an older version, and no such problems (it just ignored the file).

It's irrelevant where the file came from :) If you want to know, it was produced by a bad file transfer when copying photos, or possibly even when taking the photo. My old digital camera was flaky.
Comment 5 Debajyoti Bera 2007-02-08 11:38:35 UTC 
Thanks. I asked how you got it to understand if you were merely attaching the first 16 KB of the bad file or that the bad file _is_ the first 16 KB of another good file. Since now I know, I will be able to test with other similar files. 

Since F-Spot has this problem too, is there an open bug in F-Spot about this ? I want to link this to F-Spot; fixing it there will fix it here too.
Comment 6 Andy Wingo 2007-02-08 14:09:28 UTC 
Changing status to new, as it seems this is confirmed. Just cloned this one to f-spot bug #405736. The bad file is the first 16 kb of a good file.
Comment 7 Larry Ewing 2007-02-10 05:05:37 UTC 
Created attachment 82262 [details] [review]
patch from f-spot

this is the fix from f-spot
Comment 8 Larry Ewing 2007-02-10 05:11:51 UTC 
Fix is in 3408.
Comment 9 Debajyoti Bera 2007-02-25 16:23:49 UTC 
*** Bug 411943 has been marked as a duplicate of this bug. ***
Comment 10 Debajyoti Bera 2007-03-29 19:28:27 UTC 
*** Bug 424236 has been marked as a duplicate of this bug. ***