abrt version: 1.1.13
Attached file: backtrace
reason: Process /usr/bin/audacious2 was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Created attachment 460227 [details]
> assertion failed: (link != NULL)
> #6 0x00255d6a in dbus_g_proxy_dispose (object=0x9ae2990) at dbus-gproxy.c:1491
> #7 0x0089491b in IA__g_object_unref (_object=0x9ae2990) at gobject.c:2453
> #8 0x080771a0 in audacious_rc_init (object=0x9ac4f00) at dbus.c:153
What are the steps to reproduce this crash?
You somehow managed to crash the glib dbus-proxy, which is outside of Audacious. I could proof-read the code to see whether audacious_rc_init() does proper error-handling and only passes a valid value to g_object_unref(driver_proxy), but I do need info from you about reproducibility.
Please also try to evaluate Audacious 2.4 in Fedora 14 as it is upstream's current
stable release. Fedora 14 has been released officially. Eventually (but only after
additional testing), Audacious 2.4 may be offered as an update for Fedora 13.
There are no free resources for examining sporadic crashes in Audacious 2.2.