f-spot crash on edit image or presentation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
f-spot (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
user@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-
(f-spot:4793): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_
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@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-
(f-spot:4808): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_
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@
[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-
(f-spot:4822): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_
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
ProcVersionSign
Uname: Linux 2.6.32-
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
After updating: 0ubuntu0. 10.04) to 2011l-0ubuntu0. 10.04 0ubuntu0. 10.04) to 2011l-0ubuntu0. 10.04 6-2ubuntu7. 8) to 2:1.7.6-2ubuntu7.9 6-2ubuntu7. 8) to 2:1.7.6-2ubuntu7.9
tzdata (2011k-
tzdata-java (2011k-
xserver-common (2:1.7.
xserver-xorg-core (2:1.7.
it's solved