[ubuntu-mono] [Bug 878519] Re: f-spot crash on edit image or presentation

Dexo 878519 at bugs.launchpad.net
Thu Oct 20 15:07:30 UTC 2011


After updating:
tzdata (2011k-0ubuntu0.10.04) to 2011l-0ubuntu0.10.04
tzdata-java (2011k-0ubuntu0.10.04) to 2011l-0ubuntu0.10.04
xserver-common (2:1.7.6-2ubuntu7.8) to 2:1.7.6-2ubuntu7.9
xserver-xorg-core (2:1.7.6-2ubuntu7.8) to 2:1.7.6-2ubuntu7.9

it's solved


** Changed in: f-spot (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to f-spot in Ubuntu.
https://bugs.launchpad.net/bugs/878519

Title:
  f-spot crash on edit image or presentation

Status in “f-spot” package in Ubuntu:
  Fix Released

Bug description:
  user at computer:~$ f-spot # Will crash in edit
  [Info  23:23:19.192] Initializing DBus
  [Info  23:23:19.279] Initializing Mono.Addins
  [Info  23:23:19.405] Starting new FSpot server (f-spot 0.6.1.5)
  [Info  23:23:21.423] Starting BeagleService
  [Info  23:23:21.435] Hack for gnome-settings-daemon engaged

  (f-spot:4793): 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.
  The program 'f-spot' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadLength (poly request too large or internal Xlib length erro'.
    (Details: serial 25312 error_code 16 request_code 153 minor_code 17)
    (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.)

  
  user at computer:~$ f-spot --sync  # Will crash in edit ,again
  [Info  23:23:45.339] Initializing DBus
  [Info  23:23:45.424] Initializing Mono.Addins
  [Info  23:23:45.533] Starting new FSpot server (f-spot 0.6.1.5)
  [Info  23:23:47.531] Starting BeagleService
  [Info  23:23:47.543] Hack for gnome-settings-daemon engaged

  (f-spot:4808): 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.
  The program 'f-spot' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadLength (poly request too large or internal Xlib length erro'.
    (Details: serial 30228 error_code 16 request_code 153 minor_code 17)
    (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.)

  
  alicia at tacensbuntu:~$ f-spot # Will crash pushung F5
  [Info  23:24:00.777] Initializing DBus
  [Info  23:24:00.862] Initializing Mono.Addins
  [Info  23:24:00.971] Starting new FSpot server (f-spot 0.6.1.5)
  [Info  23:24:02.906] Starting BeagleService
  [Info  23:24:02.919] Hack for gnome-settings-daemon engaged

  (f-spot:4822): 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.
  The program 'f-spot' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadLength (poly request too large or internal Xlib length erro'.
    (Details: serial 14641 error_code 16 request_code 153 minor_code 17)
    (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.)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: f-spot 0.6.1.5-2ubuntu7
  ProcVersionSignature: Ubuntu 2.6.32-34.77-generic-pae 2.6.32.44+drm33.19
  Uname: Linux 2.6.32-34-generic-pae i686
  Architecture: i386
  Date: Wed Oct 19 23:19:48 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=gl_ES.utf8
   SHELL=/bin/bash
  SourcePackage: f-spot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/878519/+subscriptions



More information about the Ubuntu-mono mailing list