f-spot.exe crashed with SIGSEGV

Bug #214939 reported by Troy James Sobotka
6
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: f-spot

Thus far seems to happen after an import of raw Canon images.

Any idea on how to flesh this report trace out further for the devs?

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Apr 9 22:14:40 2008
Disassembly: 0x4144de00:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/f-spot/f-spot.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: nvidia
Package: f-spot 0.4.2-1ubuntu2
PackageArchitecture: amd64
ProcCmdline: f-spot /usr/lib/f-spot/f-spot.exe
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
Signal: 11
SourcePackage: f-spot
Stacktrace: #0 0x000000004144de00 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: f-spot.exe crashed with SIGSEGV
Uname: Linux 2.6.24-15-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Revision history for this message
Troy James Sobotka (troy-sobotka) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Could you please run f-spot as: f-spot --debug &> fspot-log.txt and attach that file to the report? Thanks in advance.

Changed in f-spot:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Troy James Sobotka (troy-sobotka) wrote :

Ok. Done and done after my last batch of photos.

Frequency: Always (Seems to happen every time I do an import)

Symptoms: Import succeeds. Initial autolaunch of F-Spot fails when plugging in media. When finished, shutting down the window via the close function simply hangs the application.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

there's no indication of a crash in the log, are you still getting the issue?

Revision history for this message
Troy James Sobotka (troy-sobotka) wrote :

Been extremely busy.

I will try to test soon.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

Changed in f-spot:
status: Incomplete → Invalid
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.