[ubuntu-mono] [Bug 297406] Re: f-spot crash at startup AMD64 Ubuntu 8.10

Christian Irlinger irlinger at gmx.de
Tue Nov 18 21:06:47 GMT 2008

got the same after upgrade 8.4 to 8.10 on Intel.

$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug   **
[Info  21:13:54.326] Initializing DBus
[Debug 21:13:54.595] DBusInitialization took 0,244245s
[Info  21:13:54.595] Initializing Mono.Addins
[Debug 21:13:54.980] Mono.Addins Initialization took 0,384162s
[Info  21:13:54.992] Starting new FSpot server
[Debug 21:13:55.349] Db Initialization took 0,227092s
Domain: 'Gtk' Level: Critical
Message: gtk_window_resize: assertion `height > 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:13:56.573] QueryToTemp took 0,401082s : 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 21:13:57.432] PhotosPerMonth took 0,529724s
[Debug 21:13:57.440] TimeAdaptor REAL Reload took 0,743182s
[Debug 21:13:57.459] Query took 0,402552s : 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 335 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.)

** Attachment added: "gdb backtrace"

f-spot crash at startup AMD64 Ubuntu 8.10
You received this bug notification because you are a member of MOTU Mono
Team, which is subscribed to f-spot in ubuntu.

More information about the Ubuntu-mono mailing list