f-spot.exe crashed in Print Preview

Bug #453729 reported by Christian Berg
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: f-spot

I clicked the "Preview" Button in the Print Dialog, and F-Spot crashed.
I wanted to see if the Printfunction still outputs placeholders, instead of the photos, instead it crashed completly

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Oct 17 08:17:19 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/f-spot/f-spot.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: nvidia
Package: f-spot 0.6.1.3-2
ProcCmdline: f-spot /usr/lib/f-spot/f-spot.exe
ProcEnviron:
 SHELL=/bin/zsh
 LANG=de_AT.UTF-8
 LANGUAGE=de_AT.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 11
SourcePackage: f-spot
StacktraceTop:
 cmsDeleteTransform () from /usr/lib/liblcms.so.1
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: f-spot.exe crashed with SIGSEGV in cmsDeleteTransform()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout disk fuse lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:3211): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:3267): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:3245): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (empathy:3249): empathy-CRITICAL **: empathy_contact_set_is_user: assertion `EMPATHY_IS_CONTACT (contact)' failed
 (f-spot:4111): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference.
SegvAnalysis:
 Segfault happened at: 0x7f0f48d77e34 <vfprintf+148>: callq 0x7f0f48db7e90 <strchrnul>
 PC (0x7f0f48d77e34) ok
 source "0x7f0f48db7e90" (0x7f0f48db7e90) ok
 destination "(%rsp)" (0x7f0f49e43ea0) in non-writable VMA region: 0x7f0f49e3e000-0x7f0f49e44000 r--p /usr/lib/f-spot/FSpot.Utils.dll
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA /usr/lib/f-spot/FSpot.Utils.dll

Revision history for this message
Christian Berg (xeniac) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:_IO_vfprintf_internal (s=0x7f0f49e46540,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in f-spot (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

Changed in f-spot (Ubuntu):
importance: Medium → Low
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report?

Revision history for this message
Christian Berg (xeniac) wrote :

HowTo Reproduce:
Prepeation: Import some JPEG Files with 5 Megapixels into F-Spot.

1.) Doubleclick one Imge to change into Image-Viewmode
2.) Select File/Print....
3.) Choose Printpreview...
     -- At this point i am affected by Bug #450456 (https://bugs.launchpad.net/bugs/450456)
4.) Close the Printpreview
5.) Choose an other Image in F-spot, it does'nt matter if you use Prev/Next or the Imagebar. F-Spot crashes (now silently without an Apport Window)

I installed the debug-Symbols, and started mono --debug /usr/lib/f-spot/f-spot.exe
The Consoleputput is attached.

Revision history for this message
Sebastien Bacher (seb128) wrote :

can you try to run "eog file:///home/christian/Fotos/2009/09/12/pict6544.jpg", does it work correctly?

Revision history for this message
Christian Berg (xeniac) wrote :

Yes, file:///home/christian/Fotos/2009/09/12/pict6544.jpg does exist and i can open it with eog, also rebuilding the preview Images in F-Spot does work.

I now found the culprid.
To reproduce this Bug you have to set "Color profile for Printing" to sRGB built-in, or rgb built-in. On the other side, disabling Color-Management fixes this and Bug #450456

I now tried this on 3 different Machines:
Ubuntu 9.10 64bit: reproduce-able
Ubuntu 9.10 32bit: reproduce-able
Ubunut 9.04 32bit: Printing with Color-Management works

Revision history for this message
Sebastien Bacher (seb128) wrote :

good catch there

Changed in f-spot (Ubuntu):
status: Incomplete → New
Revision history for this message
Christian Berg (xeniac) wrote :

Thank's for looking into this!

Im very curious about this error, and thought that it might be a conflict with a newer version of liblcms in Karmic.

1a.) I apt-get --purge removed f-spot from my system
2a.) The i installed the f-spot build-dep from Ubuntu and build the new 0.6.1.4 Tarball from f-spot.org on my own.
This again leaded to the placeholder images in the Print-Preview and crashed f-spot.

2a.) After that i installed Ubuntu 9.04 on a Virtualbox
2b.)I again removed the old but working f-spot 0.5, installed the build-dependecies (including libmono-cairo) and compiled f-spot 0.6.1.4 on my own for Jaunty.
This configuration also crashed and showed me placeholders in the print-preview. (Debuglog is attached)

I'm now very shure that this is an upstream bug. Maybe nobody else uses color-correction so this error has not been recognized yet.
Or it is a more fuzzy depency issue, f-spot.org lists liblcms as dependency as exactly 0.12, but ubuntu ships liblcms 0.18 since Jaunty.

Revision history for this message
Sebastien Bacher (seb128) wrote :

The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Kees Cook (kees)
description: updated
tags: added: stack-exhaustion
Revision history for this message
Jean Levasseur (levasseur.jean) wrote :

Hello there, I'm unable to reproduce that bug with color profiles enabled in Ubuntu Lucid with F-Spot 0.6.1.5 . I know some work have been done to the color management of F-Spot, that might have fixed this issue. Can you try again with an updated version of F-Spot an see of it is still an issue for you? Thank you!

Revision history for this message
Christian Berg (xeniac) wrote :

Hello!

I followed my own prcedure from the "How to reproduce" in Post Nr.6.

* The Printpreview now shows the right photo, instead of a placeholder image.
* F-Spot does not crash anymore.

Imho this Bug can be set to fixed, also #450456 seems to be fixed.

Revision history for this message
Jean Levasseur (levasseur.jean) wrote :

This bug report is being closed due to your last comment regarding this being fixed. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in f-spot (Ubuntu):
status: New → Fix Released
Revision history for this message
Jean Levasseur (levasseur.jean) wrote :

Sorry, wrong status...

Changed in f-spot (Ubuntu):
status: Fix Released → 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.