f-spot fails to start - gtk_window_resize
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| f-spot (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: f-spot
Running a fresh install of intrepid ibex 8.10 64 bit
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
Description: Ubuntu 8.10
Release: 8.10
2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
f-spot:
Installed: 0.5.0.3-0ubuntu4
Candidate: 0.5.0.3-0ubuntu4
Version table:
*** 0.5.0.3-0ubuntu4 0
500 http://
100 /var/lib/
0.
500 http://
3) What you expected to happen
I type f-spot in a terminal
The program should start
4) What happened instead
I type f-spot in a terminal
A window pops up then disappears
The following text is printed in the console:
-----
f-spot
[Info 21:52:13.599] Initializing DBus
[Info 21:52:13.690] Initializing Mono.Addins
[Info 21:52:13.818] Starting new FSpot server
(f-spot:29051): Gtk-CRITICAL **: gtk_window_resize: assertion `width > 0' failed
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 329 error_code 1 request_code 143 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.)
----
Or with the debug option:
----
f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 21:53:19.495] Initializing DBus
[Debug 21:53:19.607] DBusInitialization took 0.100973s
[Info 21:53:19.607] Initializing Mono.Addins
[Debug 21:53:19.777] Mono.Addins Initialization took 0.169856s
[Info 21:53:19.782] Starting new FSpot server
[Debug 21:53:19.922] Db Initialization took 0.068707s
Domain: 'Gtk' Level: Critical
Message: gtk_window_resize: assertion `width > 0' failed
Trace follows:
at GLib.Log.
at GLib.Log.
at Gtk.Window.
at Gtk.Window.
at Gtk.Window.
at MainWindow.
at MainWindow.
at FSpot.Core.
at FSpot.Core.
at FSpot.Driver.
[Debug 21:53:20.211] QueryToTemp took 0.000516s : SELECT id, time, uri, description, roll_id, default_version_id, rating, md5_sum FROM photos WHERE id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC
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 329 error_code 1 request_code 143 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.)
----
cheers
Matthew
| Schelfhout (schelf404) wrote | #1 |
| Schelfhout (schelf404) wrote | #2 |
| Schelfhout (schelf404) wrote | #3 |
Could not reproduce on a 32-bit system using the same Ubuntu and f-spot version.
This appears in my terminal:
(f-spot:7157): Gtk-CRITICAL **: gtk_window_resize: assertion `width > 0' failed
item ImportCommand+
cleanup context
The error was 'BadRequest (invalid request code or no such operation)'.
Could that refer to item ImportCommand+