f-spot fails to start - gtk_window_resize

Bug #300820 reported by yeeking on 2008-11-21
4
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
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://gb.archive.ubuntu.com intrepid-updates/main Packages
        100 /var/lib/dpkg/status
     0.5.0.3-0ubuntu2 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages

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.PrintTraceLogFunction(System.String domain, LogLevelFlags level, System.String message)
   at GLib.Log.PrintTraceLogFunction(IntPtr , LogLevelFlags , IntPtr )
   at Gtk.Window.gtk_window_resize(IntPtr , Int32 , Int32 )
   at Gtk.Window.gtk_window_resize(IntPtr , Int32 , Int32 )
   at Gtk.Window.Resize(Int32 width, Int32 height)
   at MainWindow.LoadPreference(System.String key)
   at MainWindow..ctor(.Db db)
   at FSpot.Core.get_MainWindow()
   at FSpot.Core.Organize()
   at FSpot.Driver.Main(System.String[] args)
[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 :

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+SourceItem
cleanup context

The error was 'BadRequest (invalid request code or no such operation)'.

Could that refer to item ImportCommand+SourceItem ?

Schelfhout (schelf404) wrote :

Bug #297406 seems to be about the same problem, f-spot crash when run on 64-bit arch.

Schelfhout (schelf404) wrote :

Bug #297406 is about the same error message, so marking this bug as duplicate.
Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.
Thank you for taking the time to report this bug and helping to make Ubuntu better.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers