Comment 21 for bug 297406

Revision history for this message
Giacomo Alessandroni (g-alessandroni) wrote :

f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 17:59:40.115] Initializing DBus
[Debug 17:59:41.286] DBusInitialization took 1,085223s
[Info 17:59:41.286] Initializing Mono.Addins
[Debug 17:59:43.524] Mono.Addins Initialization took 2,236911s
[Info 17:59:43.732] Starting new FSpot server
[Debug 17:59:45.667] Db Initialization took 1,222151s
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 17:59:49.775] QueryToTemp took 0,428734s : 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
[Debug 17:59:50.486] PhotosPerMonth took 0,364881s
[Debug 17:59:50.521] TimeAdaptor REAL Reload took 0,627484s
[Debug 17:59:51.205] Query took 0,059262s : SELECT * FROM photoquery_temp_0 LIMIT 100 OFFSET 0
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 319 error_code 1 request_code 156 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.)

But the question is: F-spot, one aponce a time, worked.