F-spot crashes with 'error checking orientation'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
f-spot (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: f-spot
F-spot starts up quite normally, GUI and all. When double-clicking any picture, it swiftly turns belly up and dies.
When running it as 'f-spot --debug --synch', and waiting half a minute for the output to calm down. Trying to open any picture provokes the following:
[Debug 18:58:49.065] open uri = file://
[Debug 18:58:49.161] open uri = file://
error checking orientation
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 13506 error_code 1 request_code 153 minor_code 19)
(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.)
Mandatory stuff:
Description: Ubuntu 9.10
Release: 9.10
f-spot:
Installed: 0.6.1.5-0ubuntu1
The machine is freshly upgraded from 9.04 and I have tried to nuke the settings in .config to no avail. If anybody can tell me how to wrap the thing in a debugger, I'd be happy to give it a spin.
Changed in f-spot (Ubuntu): | |
status: | New → Confirmed |
Changed in f-spot (Ubuntu): | |
importance: | Undecided → Low |
OK. Tried removing every mono-, cli- and gac-package from the system and re--install f-spot & tomboy from there. Also removed my f-spot database and all other relevant files, I could find.
When running f-spot the very first time, the window shows up and then promptly crashes: f-spot/ f-spot. exe (hamilton)
~ >mono --debug /usr/lib/
[Info 10:41:58.302] Initializing DBus
[Info 10:41:58.487] Initializing Mono.Addins
[Info 10:41:59.787] Starting new FSpot server (f-spot 0.6.1.5)
** (f-spot:10375): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:10375): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:10375): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:10375): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:10375): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
cleanup context
cleanup context
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 978 error_code 1 request_code 153 minor_code 19)
(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.)
I then run f-spot a second time, to see if it repeats. It doesn't, as f-spot starts up just fine. BUT when I click the "add photos", it crashes:
~ >mono --debug /usr/lib/ f-spot/ f-spot. exe (hamilton)
[Info 10:44:09.702] Initializing DBus
[Info 10:44:09.899] Initializing Mono.Addins
[Info 10:44:10.181] Starting new FSpot server (f-spot 0.6.1.5)
** (f-spot:10390): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:10390): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:10390): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:10390): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed
** (f-spot:10390): CRITICAL **: atk_object_ set_name: assertion `name != NULL' failed daemon engaged
[Info 10:44:11.176] Starting BeagleService
[Info 10:44:11.202] Hack for gnome-settings-
# Clicking 'add photos' (+) button...
(f-spot:10390): 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 'BadRequest (invalid request code or no such operation)'.
(Details: serial 2896 error_code 1 request_code 153 minor_code 19)
(Note to programmers: normally, X error...