f-spot.exe crashed with SIGSEGV

Bug #189335 reported by Zartan
50
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: f-spot

I tried Ubuntu Hardy Alpha 4. I got this crash after it when I have imported images from camera and I tried close app.

ProblemType: Crash
Architecture: i386
Date: Tue Feb 5 20:42:39 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/f-spot/f-spot.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: cdrom
Package: f-spot 0.4.1-4ubuntu3
PackageArchitecture: i386
ProcCmdline: f-spot /usr/lib/f-spot/f-spot.exe --import gphoto2:usb:000,000
ProcCwd: /home/mattik
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
Signal: 11
SourcePackage: f-spot
StacktraceTop:
 ?? () from /lib/ld-linux.so.2
 ?? ()
 ?? () from /lib/ld-linux.so.2
 ?? ()
 ?? ()
Title: f-spot.exe crashed with SIGSEGV
Uname: Linux mattik-laptop 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev video

Tags: apport-crash
Revision history for this message
Zartan (mattik-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_dl_close () from /lib/ld-linux.so.2
dlclose_doit () from /lib/tls/i686/cmov/libdl.so.2
_dl_catch_error () from /lib/ld-linux.so.2
_dlerror_run () from /lib/tls/i686/cmov/libdl.so.2
dlclose () from /lib/tls/i686/cmov/libdl.so.2

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in f-spot:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Changed in f-spot:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.

Changed in f-spot:
status: Incomplete → Invalid
Revision history for this message
Andrew Conkling (andrewski) wrote :

Reopening and confirming. Better stacktraces were uploaded to bug 264537 and bug 267628, but they were removed by Apport. How do I go about getting the information uploaded now?

Changed in f-spot:
status: Invalid → Confirmed
Revision history for this message
Jean.c.h (slug71) wrote :

got this too, just opened f-spot to see what functions it has and closed it.
Intrepid Ibex Alpha 5 64 bit, All updates Applied.

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

traces are not good, may you run f-spot as: f-spot --debug &> f-spot-debug.txt perform the operation to make it crash and after that upload that file as an attachment to this report? thanks.

Changed in f-spot:
status: Confirmed → Incomplete
Revision history for this message
Andrew Conkling (andrewski) wrote : Re: [Bug 189335] Re: f-spot.exe crashed with SIGSEGV

On Fri, Oct 10, 2008 at 12:02 PM, Pedro Villavicencio <email address hidden>wrote:

> traces are not good, may you run f-spot as: f-spot --debug &> f-spot-
> debug.txt perform the operation to make it crash and after that upload
> that file as an attachment to this report?

Did you see mine on bug 267628?

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

Andrew, Yes, that's why i'm asking for a new one.

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

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

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.