GLib-GObject-CRITICAL **: g_value_get_pointer: assertion `G_VALUE_HOLDS_POINTER (value)' failed aborting... zsh: trace trap GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/libexec/telepathy-gabble
Definitely a regression from 0.7.6. I still cant manage to get a sane backtrace :-(.
Wasn't able to reproduce. Which distribution are you using?
have same... additionally - few lines earlier: ** (telepathy-gabble:9010): DEBUG: send_next_request: processing request 0x9881660 ** (telepathy-gabble:9010): DEBUG: connection_iq_unknown_cb: got unknown iq: <iq type="get" id="794100" to="piotr.skamruk@gmail.com/Telepathy@6DBA2556" from="livedelu@jobble.uaznia.net"> <query xmlns="jabber:iq:version"></query> </iq> ** (telepathy-gabble:9010): DEBUG: gabble_presence_cache_do_update: pjakubow@gmail.com (20) resource Home914750D9 prio 0 presence 6 message "(null)" GLib-GObject-CRITICAL **: g_value_get_pointer: assertion `G_VALUE_HOLDS_POINTER (value)' failed aborting... telepathy-gabble version 0.7.7 on telepathy-glib 0.7.13 (from debian package, under debian)
How often (how many times out of 10) does this happen? Is there anything special you need to do to trigger it? Can either of you get a backtrace for this? Instructions (using Debian or Ubuntu packages, and assuming you're using Empathy): * disable all your XMPP/Jabber/GTalk accounts in Empathy * apt-get install telepathy-gabble-dbg libtelepathy-glib0-dbg libglib2.0-0-dbg * GABBLE_DEBUG=all GABBLE_PERSIST=1 gdb /usr/lib/telepathy/telepathy-gabble * in gdb, type "run" * re-enable one of your XMPP/Jabber/GTalk accounts in Empathy * wait for Gabble to crash * in gdb, type "bt full" In Red-Hat-derived OSs, replace step 2 with "install appropriate debug symbols" (I don't know where they're kept in Fedora...), and in step 3 replace /usr/lib/telepathy with /usr/libexec. If you installed from source, delete step 2, and in step 3 use /usr/local/libexec.
Created attachment 18100 [details] bt full result additionally libloudmouth1-0-dbg was installed... telepathy-gabble crashes every time (10/10), when i'm trying to connect to ANY xmpp account.
Created attachment 18101 [details] better bt full result ups. previous was from some trace point, not from SIGSEGV time... proper attachment this time...
Sorry, still not seeing this crash. Could you put G_DEBUG=fatal_warnings in your gdb's environment (in addition to GABBLE_*), and get the backtrace from that in the same way?
Created attachment 18105 [details] next bt if this helps...
Aha, I see the problem. You're using GLib from experimental! I'll try building Gabble with GLib 2.17 and see if it's suddenly pickier about arguments. (It would have been helpful if you'd mentioned any experimental packages in the dependency chain... :-)
Got it. Fixed in Darcs. It turns out development GLib is really, really picky... hunk ./src/presence-cache.c 300 - g_cclosure_marshal_VOID__POINTER, G_TYPE_NONE, 1, DBUS_TYPE_G_UINT_ARRAY); + g_cclosure_marshal_VOID__BOXED, G_TYPE_NONE, 1, DBUS_TYPE_G_UINT_ARRAY);
telepathy-gabble in version 0.7.7 is only in experimental tree on debian at this time ;) temporarly, i have to downgrade this package to 0.7.6 found in unstable... btw. thx for fix.
I'm currently building Gabble 0.7.7-2 for Debian, which has this fix. 0.7.7-1ubuntu1 in Ubuntu intrepid also has it. You do know that you're not meant to upgrade your entire system to experimental, right? :-) The way experimental is meant to work is that you upgrade only the packages you're particularly interested in, and keep the unstable versions of everything else (and if you add experimental to your sources.list, apt-get/aptitude shouldn't automatically upgrade everything).
i know this, but: dpkg --get-selections | grep install | wc -l 3043 and i have experimental as default connected to unstable ;) such probblems are very rarely, and it gives me chance to help such maintainers like you ;)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.