Whenever I start Gaim, it segfaults. At first I was using Gaim 2 beta 3, then I switched back to 1.5 which also segfaulted and now I'm back at Gaim 2. Removing the tray-icon plugin from prefs.xml or some other plugin has made it possible for me to start Gaim, but then later my X-server spontaneously crashes and when I boot back up, Gaim again segfaults. I have no other issues with my installation, so I'm pretty sure this is a GTK/Gaim/Xorg 7.0 issue. Here's the output from a backtrace i GDB: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1218324816 (LWP 18633)] 0x0810f906 in gtk_gaim_status_box_new_with_account () (gdb) bt full #0 0x0810f906 in gtk_gaim_status_box_new_with_account () No symbol table info available. #1 0x080c6910 in gaim_gtk_cell_renderer_progress_new () No symbol table info available. #2 0xb6c500b3 in jabber_stream_set_state () from /usr/lib/gaim/libjabber.so No symbol table info available. #3 0xb6c504d1 in jabber_stream_set_state () from /usr/lib/gaim/libjabber.so No symbol table info available. #4 0x080942c7 in gaim_gethostbyname_async () No symbol table info available. #5 0x080dd106 in dnd_hints_show_relative () No symbol table info available. #6 0xb77e0507 in g_vasprintf () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #7 0xb77b1ecb in g_source_remove_poll () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #8 0xb77b4550 in g_main_context_acquire () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #9 0xb77b48c1 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #10 0xb7d5a1b9 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #11 0x080f14bf in main () Should I compile Gaim with the -debug flag? Whatever you need to track it down, I'm here at my laptop awaiting instructions =) / Benjamin
I had a similar problem today with gaim 1.5, and removing all the profile (~/.gaim) solved it. Don't know if it can help.
Okay, yes please compile gaim with the debug use flag and re-post the gdb output again if it is still an issue.