It was importing about 20000 photos from my ntfs hard disk when crached

Bug #69373 reported by Manolis
36
Affects Status Importance Assigned to Milestone
F-Spot
Fix Released
Critical
f-spot (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

When it was about to finish

Revision history for this message
Andrew Mitchell (ajmitch) wrote :

Do you have any other information, like a backtrace from the crash? Without this, the bug cannot be reproduced or fixed.

Changed in f-spot:
status: Unconfirmed → Needs Info
Revision history for this message
Manolis (polemidis) wrote : RE: [Bug 69373] Re: It was importing about 20000 photos from my ntfs harddisk wh

>From: Andrew Mitchell <email address hidden>
>Reply-To: Bug 69373 <email address hidden>
>To: <email address hidden>
>Subject: [Bug 69373] Re: It was importing about 20000 photos from my ntfs
>harddisk when crached
>Date: Tue, 31 Oct 2006 01:21:43 -0000
>
>Do you have any other information, like a backtrace from the crash?
>Without this, the bug cannot be reproduced or fixed.
>
>** Changed in: f-spot (Ubuntu)
> Status: Unconfirmed => Needs Info
>
>--
>It was importing about 20000 photos from my ntfs hard disk when crached
>https://launchpad.net/bugs/69373

Sorry but I am begginer. If you want, tell me what to do next time to help
the community.
I attached a file of 17MB which was produced after the crash.

_________________________________________________________________
Try Search Survival Kits: Fix up your home and better handle your cash with
Live Search!
http://imagine-windowslive.com/search/kits/default.aspx?kit=improve&locale=en-US&source=hmtagline

Revision history for this message
Andrew Mitchell (ajmitch) wrote :

Please attach it via the web interface - attachments via email currently don't work, I believe.

Changed in f-spot:
status: Unknown → Needs Info
Changed in f-spot:
status: Needs Info → Confirmed
Changed in f-spot:
status: Needs Info → Confirmed
Revision history for this message
Oxenfrogga (tlatlik) wrote :
Download full text (11.4 KiB)

Perhaps I found a related (or exactly the same) bug. I imported much less photos (ca. 100) when the application crashed. It does not happen often.

Version: f-spot 0.3.4

terminal output:

*******

open uri = file:///media/storage1/bilder/Photos/0609/10060902/PICT0001.JPG
item changed
open uri = file:///media/storage1/bilder/Photos/0609/10060902/PICT0001.JPG
open uri = file:///media/storage1/bilder/Photos/0609/10060902/PICT0001.JPG
open uri = file:///media/storage1/bilder/Photos/0609/10060902/PICT0002.JPG
open uri = file:///media/storage1/bilder/Photos/0609/10060902/PICT0002.JPG
Stopping
open uri = file:///media/storage1/bilder/Photos/0609/10060902/PICT0001.JPG
open uri = file:///media/storage1/bilder/Photos/0609/10060902/PICT0001.JPG
Stacktrace:

Native stacktrace:

        f-spot [0x818f7de]
        f-spot [0x8171be4]
        [0xb7eed440]
        f-spot(mono_code_manager_destroy+0x20) [0x813281c]
        f-spot [0x817187b]
        f-spot [0x80b32d8]
        f-spot [0x80cf0b6]
        f-spot [0x80ca262]
        f-spot [0x813adcc]
        f-spot [0x80c9a6c]
        f-spot [0x80ca45b]
        f-spot [0x80e4f16]
        f-spot [0x812c50d]
        f-spot [0x8145972]
        /lib/tls/i686/cmov/libpthread.so.0 [0xb7e1531b]
        /lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xb7d773ee]

Debug info from gdb:

(no debugging symbols found)

using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1211472160 (LWP 8229)]
[New Thread -1299076208 (LWP 19197)]
[New Thread -1301185648 (LWP 19160)]
[New Thread -1317094512 (LWP 18949)]
[New Thread -1316041840 (LWP 18878)]
[New Thread -1314989168 (LWP 18817)]
[New Thread -1304355952 (LWP 18712)]
[New Thread -1326969968 (LWP 18414)]
[New Thread -1323816048 (LWP 18333)]
[New Thread -1325917296 (LWP 18202)]
[New Thread -1322763376 (LWP 17377)]
[New Thread -1271075952 (LWP 16436)]
[New Thread -1270023280 (LWP 16248)]
[New Thread -1259340912 (LWP 16081)]
[New Thread -1247806576 (LWP 15554)]
[New Thread -1296872560 (LWP 8274)]
[New Thread -1298023536 (LWP 8250)]
[New Thread -1274430576 (LWP 8247)]
[New Thread -1273377904 (LWP 8246)]
[New Thread -1222059120 (LWP 8241)]
[New Thread -1209177200 (LWP 8240)]

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7eed410 in __kernel_vsyscall ()
  21 Thread -1209177200 (LWP 8240) 0xb7eed410 in __kernel_vsyscall ()
  20 Thread -1222059120 (LWP 8241) 0xb7eed410 in __kernel_vsyscall ()
  19 Thread -1273377904 (LWP 8246) 0xb7eed410 in __kernel_vsyscall ()
  18 Thread -1274430576 (LWP 8247) 0xb7eed410 in __kernel_vsyscall ()
  17 Thread -1298023536 (LWP 8250) 0xb7eed410 in __kernel_vsyscall ()
  16 Thread -1296872560 (LWP 8274) 0xb7eed410 in __kernel_vsyscall ()
  15 Thread -1247806576 (LWP 15554) 0xb7eed410 in __kernel_vsyscall ()
  14 Thread -1259340912 (LWP 16081) 0xb7eed410 in __kernel_vsyscall ()
  13 Thread -1270023280 (LWP 16248) 0xb7eed410 in __kernel_v...

Changed in f-spot:
status: Confirmed → Fix Released
Maia Everett (linneris)
Changed in f-spot:
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Maia Everett (linneris) wrote :

Fixed upstream long ago.

Changed in f-spot:
status: Triaged → Fix Released
Changed in f-spot:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.