I just updated to a recent xfce cvs today, and realized that I couldn't get the menu when I right click on my desktop... looking in my home directory showed a bunch of ~3meg core files, so I thought maybe it was xfdesktop. I tried running it from a terminal, and got a mysterious error. When I tried using gdb to run a backtrace, there were lots of ?? even though I had enabled debug in libxfce4util and xfdesktop. Perhaps this is occurring in another part of xfce. I'm recompiling everything with --enable-debug=yes for now, but here's the initial program error and backtrace: $ gdb xfdesktop GNU gdb 6.0-2mdk (Mandrake Linux) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-mandrake-linux-gnu"...Using host libthread_db l ibrary "/lib/tls/libthread_db.so.1". (gdb) run Starting program: /usr/bin/xfdesktop [Thread debugging using libthread_db enabled] [New Thread 1082212000 (LWP 328)] *** attempt to put segment in horiz list twice xfdesktop: art_render_gradient.c:338: art_render_gradient_linear_render_8: Asser tion `offset_fraction <= stops[ix].offset' failed. Program received signal SIGABRT, Aborted. [Switching to Thread 1082212000 (LWP 328)] 0xffffe410 in ?? () (gdb) bt #0 0xffffe410 in ?? () #1 0xbfffc040 in ?? () #2 0x00000006 in ?? () #3 0x00000148 in ?? () #4 0x40601640 in raise () from /lib/tls/libc.so.6 #5 0x40603149 in abort () from /lib/tls/libc.so.6 #6 0x405fad43 in __assert_fail () from /lib/tls/libc.so.6 #7 0x4099bb58 in art_render_image_solid () from /usr/lib/libart_lgpl_2.so.2 #8 0x409ab5e0 in ?? () from /usr/lib/libart_lgpl_2.so.2 #9 0x409ab612 in ?? () from /usr/lib/libart_lgpl_2.so.2 #10 0x00000152 in ?? () #11 0x409ab520 in ?? () from /usr/lib/libart_lgpl_2.so.2 #12 0x8049667b in ?? () #13 0x405b449a in g_spawn_command_line_async () from /usr/lib/libglib-2.0.so.0 #14 0x085f4a12 in ?? () #15 0x40556c39 in g_source_set_closure () from /usr/lib/libgobject-2.0.so.0 #16 0xb1704ff4 in ?? () #17 0x405b6ba2 in ?? () from /usr/lib/libglib-2.0.so.0 (gdb)
i think this is actually a libart_lgpl bug. you should report it to them. apparently they're doing an internal consistency check, and instead of handling errors properly, they're causing the application to abort, which i think is a terrible practice. the symptom is likely caused by an oddly-formatted SVG image. may sure you're running both the latest versions of libart_lgpl and librsvg. reopen if necessary.
Just as a note - I had this exact same problem and installing the newest libart_lgpl corrected the problem and all was well.
*** Bug 425 has been marked as a duplicate of this bug. ***
*** Bug 424 has been marked as a duplicate of this bug. ***