f-spot crashes on LTSP-client

[Simon Schmidig]

Binary package hint: f-spot

I can start f-spot and show summary/icons of the images. When I try to open one image, f-spot crashes.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: f-spot 0.6.1.5-2ubuntu7
ProcVersionSignature: Ubuntu 2.6.32-23.37-server 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-server x86_64
Architecture: amd64
Date: Mon Jul 5 10:33:47 2010
ProcEnviron:
 LANGUAGE=fr_CH.UTF-8
 LANG=fr_CH.UTF-8
 SHELL=/bin/bash
SourcePackage: f-spot

[Simon Schmidig (schmidig)]

Same problem with full-screen and dia-show.

[Pedro Villavicencio (pedro)]

Thanks for the report Simon, could you run f-spot as : f-spot --debug &> f-spot-debug.txt ; reproduce the bug and attach that resulting log file to the report? Thanks in advance.

[Simon Schmidig (schmidig)]

simon@ltsp:~$ f-spot --sync
[Info 09:43:07.193] Initializing DBus
[Info 09:43:07.337] Initializing Mono.Addins
[Info 09:43:07.530] Starting new FSpot server (f-spot 0.6.1.5)
[Info 09:43:09.135] Starting BeagleService
[Info 09:43:09.154] Hack for gnome-settings-daemon engaged

(f-spot:18567): 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.
GLib.GException: Erreur à l'ouverture du fichier : Aucun fichier ou dossier de ce type
  at GLib.FileAdapter.Read (GLib.Cancellable cancellable) [0x00000]
  at FSpot.ImageFile.Open () [0x00000]
  at FSpot.JpegFile.PixbufStream () [0x00000]
  at FSpot.ImageFile.Load (Int32 max_width, Int32 max_height) [0x00000]
  at ImageLoaderThread.ProcessRequest (.RequestItem request) [0x00000]
The program 'f-spot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 27199 error_code 1 request_code 136 minor_code 1)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

[Pedro Villavicencio (pedro)]

any chance to run f-spot with gdb as:

gdb f-spot
(gdb) break gdk_x_error
(gdb) run --sync
reproduce the crash and
(gdb) thread apply all bt

then attach that resulting log file to the report? thanks in advance.

[Simon Schmidig (schmidig)]

simon@ltsp:~$ gdb /usr/bin/f-spot
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
"/usr/bin/f-spot": not in executable format: Format de fichier non reconnu
(gdb) break gdk_x_error
Aucune table de symboles n'est chargée. Utiliser la commande " file "
Make breakpoint pending on future shared library load? (y or [n])
(gdb) run --sync
Starting program: --sync
No executable file specified.
Use the "file" or "exec-file" command.
(gdb)

f-spot was not starting.

[Launchpad Janitor (janitor)]

[Expired for f-spot (Ubuntu) because there has been no activity for 60 days.]