f-spot crashes when attempting to close after unsuccessfully opening a psd

Bug #259545 reported by Joshua Blount
2
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: f-spot

I've got a very vanilla Hardy 64 install, and my wife was using the web interface to gmail on Firefox 3:

1. click on a download link to download a .psd file a friend sent her
2. double click in the firefox 3 download window to open the file in the default application
3. F-Spot opens, but does not successfully load the .psd
4. Upon realizing F-Spot would not open previously mentioned .psd, she clicked the x symbol on the top right of the window, and the application, and entire computer locks up. I couldn't alt+ctrl+backspace to restart X, and was unsure how to move forward without a hard reboot.

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. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in f-spot:
status: New → Invalid
Revision history for this message
Joshua Blount (jblount) wrote :

It's unclear what you want me to do. What is a .crash file? I walked through the steps you mentioned and there are no files in /var/log. I could use some assistance, this is a bug that I can repeat ad nauseum, but without a way to report it, I'm unsure how I can be helpful.

Thanks!

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

When a program crashes it generate a .crash file in /var/crash/ which is used to report the bug, if it doesn't generate for you that's probably because you don't have apport running or isn't enabled, for enabling apport you can do the following:

gconftool -s /apps/update-notifier/show_apport_crashes --type bool true

Change the 0 to 1 in :

sudo nano /etc/default/apport

Once Apport is enabled you need to start the process do that with the following command.

sudo /etc/init.d/apport start

Thanks,

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.