Gaim crash on deleting an account when it begin a connection (gaim_presence_get_active_status)

this is the bug report

Thanks for your bug. Could you get a backtrace with gaim-dbg installed and gdb?
- gdb gaim
(gdb) run
get the crasher

I've tried to make gaim crash when deleting an account while it was connecting and it didn't crash

It is similar to the bug watch linked. Is seems Gaim crashes on Windows too.

@Sebastiuen
I confirm. I deleted account in connection handshake, not when it was yet connected. I did what you suggested, and I found a seg fault:

Starting program: /usr/bin/gaim
[Thread debugging using libthread_db enabled]
[New Thread -1220466496 (LWP 4998)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1220466496 (LWP 4998)]
gaim_presence_get_active_status (presence=0x13000000)
    at ../../src/status.c:1532
1532 ../../src/status.c: Nessun file o directory.
        in ../../src/status.c
(gdb) backtrace
#0 gaim_presence_get_active_status (presence=0x13000000)
    at ../../src/status.c:1532
#1 0x0808a47e in check_idleness () at ../../src/idle.c:101
#2 0xb790ddd6 in g_source_get_current_time () from /usr/lib/libglib-2.0.so.0
#3 0xb790d802 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#4 0xb79107df in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#5 0xb7910b89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#6 0xb7c43574 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#7 0x0810fd0c in main (argc=2, argv=0xbff35f84) at ../../src/gtkmain.c:764

I can't use gdb properly, may you help me to help you?
Ciao.

The backtrace looks correct, thank you for the update, marking the bug as confirmed

I can confirm this too. See backtrace attached for more info.

Hi!
I need a little help!
I buy an HP 1018 Laser Jet Printer it works with usb, but it does not
work. No printing :(
Ist configured, but nothing happens.

csirke1, your requestion is not at the right place, you might want to make a support request on https://answers.launchpad.net/ubuntu/+addticket

This is no longer reproducible with latest versions.
Please, reopen this bug if you still notice this behaviour. Thank you.