GNOME Bugzilla – Bug 600349
X Window System error at startup: BadAlloc
Last modified: 2010-05-16 11:08:36 UTC
Running F-Spot version 0.6.1.4 on a fresh Ubuntu 9.10 system, the program exits during startup with: The program 'f-spot' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 3047 error_code 11 request_code 53 minor_code 0) This is a fresh installation and first use of f-spot, so everything should be at default settings. This system runs X.Org X Server 1.6.4 using the radeon display driver (version 6.12.99). The graphics card is a ATI Technologies Inc Radeon Mobility X1400. Here's the full output of 'f-spot --debug'. There are some warnings before the X window System error, but I suspect that they are unrelated: $ f-spot --debug ** Running f-spot in Debug Mode ** ** Running Mono with --debug ** [Info 22:39:09.850] Initializing DBus [Debug 22:39:10.042] DBusInitialization took 0,173869s [Info 22:39:10.042] Initializing Mono.Addins [Debug 22:39:10.305] Mono.Addins Initialization took 0,263783s [Info 22:39:10.324] Starting new FSpot server (f-spot 0.6.1.4) [Debug 22:39:10.495] Db Initialization took 0,068913s ** (f-spot:19316): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:19316): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:19316): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:19316): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (f-spot:19316): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed [Debug 22:39:10.878] Query Started : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC [Debug 22:39:10.882] QueryToTemp took 0,003648s : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC [Debug 22:39:10.882] Reloading the query took 0,008896s [Debug 22:39:11.186] PhotosPerMonth took 0,044519s [Debug 22:39:11.188] TimeAdaptor REAL Reload took 0,255225s [Debug 22:39:11.245] Query Started : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC [Debug 22:39:11.246] QueryToTemp took 0,000805s : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC [Debug 22:39:11.315] Reloading the query took 0,068236s [Debug 22:39:11.320] Query Started : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC [Debug 22:39:11.330] QueryToTemp took 0,010556s : SELECT * FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY time DESC, filename DESC [Debug 22:39:11.361] Reloading the query took 0,041398s [Info 22:39:11.366] Starting BeagleService [Debug 22:39:11.367] BeagleService startup took 2,4E-05s [Info 22:39:11.394] Hack for gnome-settings-daemon engaged (f-spot:19316): 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. [Debug 22:39:11.471] PhotosPerMonth took 0,001611s [Debug 22:39:11.471] TimeAdaptor REAL Reload took 0,140078s [Debug 22:39:11.545] PhotosPerMonth took 0,013439s [Debug 22:39:11.545] TimeAdaptor REAL Reload took 0,214129s The program 'f-spot' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 3046 error_code 11 request_code 53 minor_code 0) (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.)
Running it with GDK_NATIVE_WINDOWS=true seems to work around the problem.
could you give details on the theme you use? the new wave one makes f-spot crash on start in a similar way
MONO_XDEBUG=1 f-spot --sync --gdb b gdk_x_error xdb bt and report please
The theme is "New Wave Dark Windows" indeed. I tried to get the requested backtrace, but either there is another problem or something is wrong about your instructions: $ MONO_XDEBUG=1 f-spot --sync --gdb GNU gdb (GDB) 7.0-ubuntu Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/mono...(no debugging symbols found)...done. Starting program: /usr/bin/mono /usr/lib/f-spot/f-spot.exe --sync --gdb [Thread debugging using libthread_db enabled] [New Thread 0x6ceb70 (LWP 2518)] ** ERROR:unwind.c:28:mono_hw_reg_to_dwarf_reg: code should not be reached Program received signal SIGABRT, Aborted. 0x00f89422 in __kernel_vsyscall () (gdb) b gdk_x_error Function "gdk_x_error" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (gdk_x_error) pending. (gdb) xdb Undefined command: "xdb". Try "help".
your mono is not xdb enabled :/ let se if I can install the theme and repro over here
oh, for gdb < 7.0 you need to add the following to your .gdbinit: define xdb shell rm -f xdb.so && as -o xdb.o xdb.s && ld -shared -o xdb.so xdb.o add-symbol-file xdb.so 0 end
after spending a few hours debugging this, it really looks like a theming issue.
*** Bug 601289 has been marked as a duplicate of this bug. ***
*** Bug 601812 has been marked as a duplicate of this bug. ***
Can we agree on closing this bug, so you guys can follow it on launchpad and fix it on ubuntu ? s
Ok
*** Bug 605351 has been marked as a duplicate of this bug. ***
*** Bug 605648 has been marked as a duplicate of this bug. ***
*** Bug 611540 has been marked as a duplicate of this bug. ***
*** Bug 610974 has been marked as a duplicate of this bug. ***
*** Bug 613538 has been marked as a duplicate of this bug. ***