f-spot crash at startup AMD64 Ubuntu 8.10

[rrichter]

Binary package hint: f-spot

1. insert SD-CARD in Printerslot
2. automatic sd-card identification {Question-Window (gnome)}
3. f-spot import question
4. -- no answer --
5. start f-spot in bash
6. crash

Crash when f-spot startup:
System: Ubuntu 8.10 64-Bit

Log:

[Info 19:03:25.886] Initializing DBus
[Info 19:03:26.004] Initializing Mono.Addins
[Info 19:03:26.206] Starting new FSpot server

(f-spot:9568): 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 336 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.)

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[rrichter (rrichterzittau-deactivatedaccount)]

I have no idea!

[Tobias Abarbanell (tobias-abarbanell)]

I have the same bug in Ubuntu 8.10 on Intel.
GNOME f-spot 0.5.0.3

This is new since I upgraded from 8.4 to 8.10

[Christian Irlinger (irlinger)]

Hi,
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.)

[Schelfhout (schelf404)]

my comment from the duplicate bug:

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 ?

[cr1stobal (chris-farnham)]

chris@chris-t500:~$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 11:02:40.741] Initializing DBus
[Debug 11:02:40.878] DBusInitialization took 0.122129s
[Info 11:02:40.879] Initializing Mono.Addins
[Debug 11:02:41.097] Mono.Addins Initialization took 0.218141s
[Info 11:02:41.104] Starting new FSpot server
[Debug 11:02:41.316] Db Initialization took 0.090155s
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 11:02:41.650] QueryToTemp took 0.000557s : 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 335 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.)

[Schelfhout (schelf404)]

From the upstream bugreport:

launch gconf-editor
navigate on the left to apps/f-spot/ui
on the right you should find

main_window_width
main_window_height

set them to something, like 100. if they don't exist create them, as integer.
------------

What output do you get after changing these?

[pemakela (perttu-makela)]

I have the same error (Ubuntu 8.10, 32bit on AMD Athlon), but at least for me the f-spot window opens for a split of a second after the 'Starting new FSport server' line, then closes and the error message is displayed.

I added keys main_window_width and main_window_height with gconf-editor. Error remains the same, but the flashing f-spot window size is what they define. Without those keys the f-spot window is maybe 300 pixels wide and about half that high.

[Christian Irlinger (irlinger)]

I have added the above mentioned main_window* entries via gconf-editor, error is still the same

$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 20:08:11.267] Initializing DBus
[Debug 20:08:11.570] DBusInitialization took 0,262519s
[Info 20:08:11.570] Initializing Mono.Addins
[Debug 20:08:11.984] Mono.Addins Initialization took 0,413741s
[Info 20:08:11.997] Starting new FSpot server
[Debug 20:08:12.279] Db Initialization took 0,182147s
[Debug 20:08:13.034] QueryToTemp took 0,00115s : 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 20:08:13.312] PhotosPerMonth took 0,029502s
[Debug 20:08:13.372] TimeAdaptor REAL Reload took 0,276291s
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.)

[Schelfhout (schelf404)]

Set to confirmed as 2 people reported to still have the problem and debug information is provided.

[LinuxGuyInVA (ppmurphy)]

I don't think this is a 64-bit or AMD issue. Running 32-bit:

: samhain_pmurphy; uname -a
Linux samhain 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux
: samhain_pmurphy; cat /proc/cpuinfo | grep ^model\ name
model name : Intel(R) Pentium(R) M processor 1.86GHz
: samhain_pmurphy;

and I get the same symptoms: f-spot (which was working fine under 8.04) no longer works
after I upgraded (not re-installed) to 8.10. Debug trace below.

One other point: I have the screen saver set to show f-spot favourites, and *that* continued
to work up to the point where I tried running f-spot from the command line. This was after the
8.10 upgrade.

Finally, I ran it from my regular account (which had thousands of imported photos) and also
from a "virgin" clean account which had never run f-spot before. Same end result (f-spot died)
but different traceback. Also shown below (2nd traceback).

: samhain_pmurphy; f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 14:27:43.508] Initializing DBus
[Debug 14:27:43.739] DBusInitialization took 0.20894s
[Info 14:27:43.739] Initializing Mono.Addins
[Debug 14:27:44.098] Mono.Addins Initialization took 0.35828s
[Info 14:27:44.110] Starting new FSpot server
[Debug 14:27:44.461] Db Initialization took 0.155755s
[Debug 14:27:45.084] QueryToTemp took 0.000943s : 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 332 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.)
**
ERROR:../../mono/io-layer/handles-private.h:160:_wapi_handle_set_signal_state: assertion failed: (thr_ret == 0)
Stacktrace:

  at (wrapper managed-to-native) System.Threading.NativeEventCalls.SetEvent_internal (intptr) <0x00004>
  at (wrapper managed-to-native) System.Threading.NativeEventCalls.SetEvent_internal (intptr) <0xffffffff>
  at System.Threading.EventWaitHandle.Set () <0x0001c>
  at (wrapper remoting-invoke-with-check) System.Threading.EventWaitHandle.Set () <0xffffffff>
  at Banshee.Database.QueuedSqliteDatabase.QueueCommand (Banshee.Database.QueuedSqliteCommand) <0x0007b>
  at Banshee.Database.QueuedSqliteDatabase.ExecuteNonQuery (Banshee.Database.DbCommand) <0x00038>
  at Banshee.Database.QueuedSqliteDatabase.ExecuteNonQuery (object) <0x00035>
  at PhotoStore.PhotosPerMonth (FSpot.Query.IQueryCondition[]) <0x00073>
  at FSpot.TimeAdaptor.DoReload () <0x0008a>
  at (wrapper runtime-invoke) System.Object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

 f-spot [0x817b4ae]
 [0xb7f5c410]
 /lib/tls/i686/cmov/l...

[Thomas Ohms (tohms)]

I can confirm this bug!

System: Linux lokarabia 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux (Ubuntu Intrepid 8.10)

[Pedro Villavicencio (pedro)]

There's no need to reconfirm bugs if the state is Triaged and they have an upstream task, thanks.

[khink (kees-fmf)]

I won't also confirm it, then. Let me know if you want more info or have a patch that needs testing.

When i set the values in gconf-editor (as suggested by Shanta Schelfhout on 2008-11-24), f-spot still fails to start but the line "Message: gtk_window_resize: assertion `width > 0' failed" does not appear: see attachment.

[khink (kees-fmf)]

If i connect via ssh -X and start f-spot remotely, making it draw its screen on the laptop i'm connecting from, it does not crash.
(Hoping this is helpful, sorry if it's is a redundant remark.)

[LinuxGuyInVA (ppmurphy)]

This is slightly embarrassing... :-} but after some rather tortuous struggles with an entirely different problem (trying the fglrx driver and reverting to the open source radeon one after finding the former couldn't handle my 2 monitor setup), f-spot once more works for me. Another app that was giving me problems (Stellarium) also works again, so I can only conclude this was an X11 problem at least in part.

I'm happy to do more tests if there are specific ones that would help... otherwise please accept my apologies for possibly throwing a red herring or two into the mix!

For whatever it's worth, I haven't been futzing with xorg.conf (unlike years past) but letting the gnome-display-properties applet do its thing (with xrandr presumably).

[Antoine Pairet (b-ly)]

Confirming the idea that it is linked to the driver one is using:

Crash happens only if I use radeon or radeonhd drivers.
Using fglrx driver, f-spot works perfectly.

[Thomas Ohms (tohms)]

Indeed - I changed to fglrx and f-spot is running fine!

[Giacomo Alessandroni (g-alessandroni)]

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.

[Sebastien Bacher (seb128)]

upstream says the issue is a video driver one, is somebody still having the bug on lucid and using what driver?

[jerzyo (jerzyo)]

I have a problem in lucid

After clicking on Import:

f-spot
[Info 23:11:18.434] Initializing DBus
[Info 23:11:18.553] Initializing Mono.Addins
[Info 23:11:18.724] Starting new FSpot server (f-spot 0.6.1.5)
[Info 23:11:20.198] Starting BeagleService
[Info 23:11:20.220] Hack for gnome-settings-daemon engaged

(f-spot:5092): 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.
Stacktrace:

  at (wrapper managed-to-native) GdkGlx.Context.glXChooseVisual (intptr,int,int[]) <0x00075>
  at (wrapper managed-to-native) GdkGlx.Context.glXChooseVisual (intptr,int,int[]) <0xffffffff>
  at GdkGlx.Context..ctor (Gdk.Screen,GdkGlx.Context,int[]) <0x000eb>
  at GdkGlx.Context..ctor (Gdk.Screen,int[]) <0x0001f>
  at FSpot.Widgets.PhotoImageView.OnRealized () <0x0007f>
  at Gtk.Widget.realized_cb (intptr) <0x0005a>
  at (wrapper native-to-managed) Gtk.Widget.realized_cb (intptr) <0xffffffff>
  at (wrapper managed-to-native) Gtk.Widget.gtk_widget_show (intptr) <0x00056>
  at (wrapper managed-to-native) Gtk.Widget.gtk_widget_show (intptr) <0xffffffff>
  at Gtk.Widget.Show () <0x00017>
  at ImportCommand.ImportFromFile (PhotoStore,string) <0x006ef>
  at MainWindow.HandleImportCommand (object,System.EventArgs) <0x00063>
  at (wrapper runtime-invoke) MainWindow.runtime_invoke_void__this___object_object (object,intptr,intptr,intptr) <0xffffffff>
  at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke (object,object[],System.Exception&) <0x0004e>
  at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke (object,object[],System.Exception&) <0xffffffff>
  at System.Reflection.MonoMethod.Invoke (object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo) <0x000bb>
  at System.Reflection.MethodBase.Invoke (object,object[]) <0x0002a>
  at System.Delegate.DynamicInvokeImpl (object[]) <0x0017b>
  at System.MulticastDelegate.DynamicInvokeImpl (object[]) <0x0003b>
  at System.Delegate.DynamicInvoke (object[]) <0x00015>
  at GLib.Signal.ClosureInvokedCB (object,GLib.ClosureInvokedArgs) <0x0013b>
  at GLib.SignalClosure.Invoke (GLib.ClosureInvokedArgs) <0x0002a>
  at GLib.SignalClosure.MarshalCallback (intptr,intptr,uint,intptr,intptr,intptr) <0x0027f>
  at (wrapper native-to-managed) GLib.SignalClosure.MarshalCallback (intptr,intptr,uint,intptr,intptr,intptr) <0xffffffff>
  at (wrapper managed-to-native) Gtk.Application.gtk_main () <0x00052>
  at (wrapper managed-to-native) Gtk.Application.gtk_main () <0xffffffff>
  at Gtk.Application.Run () <0x0000b>
  at FSpot.Driver.Main (string[]) <0x01dbb>
  at (wrapper runtime-invoke) FSpot.Driver.runtime_invoke_int_object (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

 f-spot() [0x47b77f]
 f-spot() [0x4aef3f]
 /lib/libpthread.so.0(+0xf8f0) [0x7f910bd0b8f0]
 /usr/lib/fglrx/libGL.so.1(XF86DRIQueryVersion+0xae) [0x7f90f413d12e]
 /usr/lib/fglrx/libGL.so.1(XF86DRIQueryExtension+0x79) [0x7f90f413d2c9]
 /usr/lib/fglrx/libGL.so.1(+0x55c70) [0x7f90f413cc70]
 /usr/lib/fglrx/libGL.so.1(+0x35ff...

[Pedro Villavicencio (pedro)]

Jerzyo which video driver are you using there?