segmentation fault while importing photos from F-Spot

Bug #930799 reported by Alex Peters
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
shotwell (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Shotwell segfaulted while trying to import a large F-Spot photo collection (possibly including many duplicates, as this was the third attempt) into a large existing Shotwell collection.

Shotwell was invoked in this manner:

$ SHOTWELL_LOG=1 shotwell
Segmentation fault

The log generated by Shotwell was gzipped and is attached. Sadly, the log doesn't seem to provide any useful information related to the segfault.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: shotwell 0.11.6-0ubuntu0.1 [modified: usr/share/glib-2.0/schemas/gschemas.compiled]
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sun Feb 12 10:06:40 2012
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: shotwell
UpgradeStatus: Upgraded to oneiric on 2012-02-04 (7 days ago)

Revision history for this message
Alex Peters (alex-peters) wrote :
Revision history for this message
Bruno Girin (brunogirin) wrote :

Alex,

There are currently two known problems with the F-Spot import:
* Dealing with issues in the F-Spot database itself: http://redmine.yorba.org/issues/4487
* A memory usage issue (although this seems to affect all imports, not jut F-Spot): http://redmine.yorba.org/issues/4498

The first one is being resolved as part of a re-factoring of the F-Spot import code. A patch has been provided and I'm hoping that it will make its way to trunk in the next few days.

The second one is being looked at too. To validate whether you are hitting the memory issue, can you check how much memory Shotwell uses when doing the import please? You should be able to do that using the system monitor.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in shotwell (Ubuntu):
status: New → Confirmed
Revision history for this message
marco.pallotta (marco-pallotta) wrote :

In Ubuntu 12.04 x86_64 (real host) all seems to work well whereas in x86 version (tested inside VirtualBox) the bug happened.

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.