GNOME Bugzilla – Bug 626290
f-spot crashes on attempting to print
Last modified: 2010-08-12 11:07:09 UTC
Pushed from downstream Ubuntu on behalf of the original reporter (http://www.omgubuntu.co.uk/2010/08/ubuntu-1010-alpha-3-released-whats-new.html#comment-66812411): https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/609713 Binary package hint: f-spot f-spot: Installed: 0.7.1-1 Candidate: 0.7.1-1 Version table: *** 0.7.1-1 0 500 http://gb.archive.ubuntu.com/ubuntu/ maverick/main Packages 100 /var/lib/dpkg/status Description: Ubuntu maverick (development branch) Release: 10.10 Steps to reproduce: 1. Select a photo, either in browse or edit views. 2. Click on the Menu > File > Print F-spot instantly closes without warning or any kind of error message. Output when running in a terminal: (f-spot:2851): 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. Exception in Gtk# callback delegate Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception. System.EntryPointNotFoundException: f_pixbuf_from_cairo_surface at (wrapper managed-to-native) FSpot.PrintOperation:f_pixbuf_from_cairo_surface (intptr) at FSpot.PrintOperation.CreatePixbuf (Cairo.Surface s) [0x00000] in <filename unknown>:0 at FSpot.PrintOperation.OnCustomWidgetChanged (Gtk.Widget widget) [0x00000] in <filename unknown>:0 at FSpot.PrintOperation.OnCreateCustomWidget () [0x00000] in <filename unknown>:0 at Gtk.PrintOperation.createcustomwidget_cb (IntPtr operation) [0x00000] in <filename unknown>:0 at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal) at Gtk.PrintOperation.createcustomwidget_cb(IntPtr operation) at Gtk.PrintOperation.gtk_print_operation_run(IntPtr , Int32 , IntPtr , IntPtr ByRef ) at Gtk.PrintOperation.Run(PrintOperationAction action, Gtk.Window parent) at FSpot.MainWindow.HandlePrintCommand(System.Object sender, System.EventArgs e) at System.Reflection.MonoMethod.InternalInvoke(System.Object , System.Object[] , System.Exception ByRef ) at System.Reflection.MonoMethod.Invoke(System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) at System.Reflection.MethodBase.Invoke(System.Object obj, System.Object[] parameters) at System.Delegate.DynamicInvokeImpl(System.Object[] args) at System.MulticastDelegate.DynamicInvokeImpl(System.Object[] args) at System.Delegate.DynamicInvoke(System.Object[] args) at GLib.Signal.ClosureInvokedCB(System.Object o, GLib.ClosureInvokedArgs args) at GLib.SignalClosure.Invoke(GLib.ClosureInvokedArgs args) at GLib.SignalClosure.MarshalCallback(IntPtr raw_closure, IntPtr return_val, UInt32 n_param_vals, IntPtr param_values, IntPtr invocation_hint, IntPtr marshal_data) at Gtk.Application.gtk_main() at Gtk.Application.Run() at FSpot.Driver.Startup() at Hyena.Gui.CleanRoomStartup.Startup(Hyena.Gui.StartupInvocationHandler startup) at FSpot.Driver.Main(System.String[] args) Printing is working normally in every other application tried, this is strictly confined to f-spot.
As the originator of this bug report (on launchpad), I would like to say the problem appears to be resolved in version 0.7.2 released 11th August. It now opens the print dialog instead of instantly crashing the application.
That's right, this has been fixed. Thanks for letting us know!