[hardy] f-spot SIGSEGV at startup

Bug #214385 reported by Matt Mets
2
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: f-spot

f-spot has refused to start since an update late last week (unfortunately, I don't remember which one). I tried re-naming the .gnome2/f-spot config directory, but this did not change anything.

The error message I get when running 'f-spot --debug &> f-spot.txt' is attached.

1. Ubuntu release
$ lsb_release -rd
Description: Ubuntu hardy (development branch)
Release: 8.04

2. Package version
$ apt-cache policy f-spot
f-spot:
  Installed: 0.4.2-1ubuntu2
  Candidate: 0.4.2-1ubuntu2
  Version table:
 *** 0.4.2-1ubuntu2 0
        500 http://us.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Matt Mets (matt-mets) wrote :
Revision history for this message
Matt Mets (matt-mets) wrote :

After updating the system today (April 9th), the issue seems to be resolved. The version info for f-spot seems to be the same, so it must have been an issue with a different package.

Question: If a bug I have reported goes away, should I change its status?

Revision history for this message
Matt Mets (matt-mets) wrote :

I spoke too soon; f-spot started and ran correctly once. It crashed on shutdown, then refused to start again, even after resetting the system. The crash at startup appears to be the same as before.

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

thanks for your report, as per your last comment that's a known bug, thanks.

Changed in f-spot:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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