Couldn't close f-spot

Bug #206319 reported by sleepstupid
4
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: f-spot

Couldn't close f-spot

ProblemType: Crash
Architecture: i386
Date: Mon Mar 24 21:42:48 2008
Disassembly: 0xb6b9a648:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/f-spot/f-spot.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: nvidia
Package: f-spot 0.4.2-0ubuntu4
PackageArchitecture: i386
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_US.UTF-8
Signal: 11
SourcePackage: f-spot
Stacktrace: #0 0xb6b9a648 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

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

Revision history for this message
sleepstupid (jcvold) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

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

Can you tell us a few steps in order to reproduce the crash? thanks. maybe another dup of bug 199496

Changed in f-spot:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
sleepstupid (jcvold) wrote :

Pretty simple, I opened F-spot to get a quick look at it, but when I tried to close it, it just sat there frozen until the dialog box came up saying something about the program not responding, etc.

This was shortly after installing the 8.04 beta for the first time.

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

ok, thanks you that's another dup of 199496 then, thanks again.

Changed in f-spot:
status: Incomplete → Invalid
Revision history for this message
Davegod75 (goddard) wrote : Re: [Bug 206319] Re: Couldn't close f-spot

Sorry, for the dupes, I am using Hardy crash report feature to submit
and it's hard to tell when there is duplicate sometimes.

David

On Wed, Mar 26, 2008 at 8:20 PM, Pedro Villavicencio <email address hidden> wrote:
> *** This bug is a duplicate of bug 199496 ***
> https://bugs.launchpad.net/bugs/199496
>
> ok, thanks you that's another dup of 199496 then, thanks again.
>
> ** Changed in: f-spot (Ubuntu)
> Status: Incomplete => Invalid
>
> ** This bug has been marked a duplicate of bug 199496
> Tomboy.exe crashed with SIGSEGV in exit()
>
> --
> Couldn't close f-spot
> https://bugs.launchpad.net/bugs/206319
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 199496).
>

Revision history for this message
Andrew Conkling (andrewski) wrote :

No problem, David! That happens and is all just part of the game. :) It's Apport that helps us easily determine all of the bug shtuff.

-----Original Message-----
From: Davegod75 <email address hidden>

Date: Wed, 26 Mar 2008 20:24:32
To:<email address hidden>
Subject: Re: [Bug 206319] Re: Couldn't close f-spot

*** This bug is a duplicate of bug 199496 ***
    https://bugs.launchpad.net/bugs/199496

Sorry, for the dupes, I am using Hardy crash report feature to submit
and it's hard to tell when there is duplicate sometimes.

David

On Wed, Mar 26, 2008 at 8:20 PM, Pedro Villavicencio <email address hidden> wrote:
> *** This bug is a duplicate of bug 199496 ***
> https://bugs.launchpad.net/bugs/199496
>
> ok, thanks you that's another dup of 199496 then, thanks again.
>
> ** Changed in: f-spot (Ubuntu)
> Status: Incomplete => Invalid
>
> ** This bug has been marked a duplicate of bug 199496
> Tomboy.exe crashed with SIGSEGV in exit()
>
> --
> Couldn't close f-spot
> https://bugs.launchpad.net/bugs/206319
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 199496).
>

--
Couldn't close f-spot
https://bugs.launchpad.net/bugs/206319
You received this bug notification because you are a direct subscriber
of a duplicate bug (via bug 199496).

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.