Ari Pollak wrote:
> Please run pidgin under gdb like this and attach the backtrace after the
> crash:
> G_DEBUG=fatal_warnings gdb pidgin
>
I run it like that and right away after 'run' i got SIGABRT. The output is at
the bottom of the email. But anyway since last upgrade (>week ago) where I saw
Please run pidgin under gdb like this and attach the backtrace after the
crash:
G_DEBUG=fatal_warnings gdb pidgin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Ari Pollak wrote:
> Please install pidgin-dbg, libgstreamer0.10-0-dbg, libglib2.0-0-dbg, and
> gstreamer0.10-plugins-base-dbg, and then get a new backtrace.
>
OK will do. In a meantime pidgin crashed again with:
(pidgin:6552): GStreamer-CRITICAL **: gst_element_set_state: assertion
`GST_IS_ELEME
Please install pidgin-dbg, libgstreamer0.10-0-dbg, libglib2.0-0-dbg, and
gstreamer0.10-plugins-base-dbg, and then get a new backtrace.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi,
sending pidgin bug report. Pidgin crashed exactly when I was sending message.
Jozef.
System: Linux 2.6.18-6-xen-686 #1 SMP Sun Feb 10 22:43:13 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
5 matches
Mail list logo