telepathy-gabble crashed with signal 5 in g_return_if_fail_warning()

[lipstick]

.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-gabble 0.15.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-8.14-generic-pae 3.2.0
Uname: Linux 3.2.0-8-generic-pae i686
NonfreeKernelModules: wl
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Wed Jan 11 22:27:22 2012
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120104)
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
Signal: 5
SourcePackage: telepathy-gabble
StacktraceTop:
 g_return_if_fail_warning () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_hash_table_foreach () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? ()
Title: telepathy-gabble crashed with signal 5 in g_return_if_fail_warning()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_return_if_fail_warning (log_domain=0xb710b66e "GLib", pretty_function=0xb710f820 "g_hash_table_foreach", expression=0xb710f574 "version == hash_table->version") at /build/buildd/glib2.0-2.31.8/./glib/gmessages.c:801
 g_hash_table_foreach (hash_table=0x993c808, func=0x8108e50 <disconnect_entry_foreach>, user_data=0x0) at /build/buildd/glib2.0-2.31.8/./glib/ghash.c:1510
 gabble_vcard_manager_dispose (object=0x99318c8) at vcard-manager.c:590
 g_object_unref (_object=0x99318c8) at /build/buildd/glib2.0-2.31.8/./gobject/gobject.c:2971
 gabble_connection_dispose (object=0x9924440) at connection.c:1211

[Bilal Shahid (s9iper1)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
 Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem

[lipstick (sinanaykut-gmail)]

Unfortunately, I am not sure how to recreate this bug.

2012/1/29 Bilal Shahid <email address hidden>

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
> Please answer these questions:
>
> * Is this reproducible?
> * If so, what specific steps should we take to recreate this bug?
>
> This will help us to find and resolve the problem
>
> ** Changed in: telepathy-gabble (Ubuntu)
> Status: New => Incomplete
>
> ** Visibility changed to: Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/915015
>
> Title:
> telepathy-gabble crashed with signal 5 in g_return_if_fail_warning()
>
> Status in “telepathy-gabble” package in Ubuntu:
> Incomplete
>
> Bug description:
> .
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: telepathy-gabble 0.15.2-0ubuntu1
> ProcVersionSignature: Ubuntu 3.2.0-8.14-generic-pae 3.2.0
> Uname: Linux 3.2.0-8-generic-pae i686
> NonfreeKernelModules: wl
> ApportVersion: 1.90-0ubuntu1
> Architecture: i386
> Date: Wed Jan 11 22:27:22 2012
> ExecutablePath: /usr/lib/telepathy/telepathy-gabble
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386
> (20120104)
> ProcCmdline: /usr/lib/telepathy/telepathy-gabble
> Signal: 5
> SourcePackage: telepathy-gabble
> StacktraceTop:
> g_return_if_fail_warning () from /lib/i386-linux-gnu/libglib-2.0.so.0
> g_hash_table_foreach () from /lib/i386-linux-gnu/libglib-2.0.so.0
> ?? ()
> g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> ?? ()
> Title: telepathy-gabble crashed with signal 5 in
> g_return_if_fail_warning()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/915015/+subscriptions
>

--
twitter.com/sinan_aykut

[Bilal Shahid (s9iper1)]

any steps or some which version of telepathy gabble are you using?
is your system fully updated?

[lipstick (sinanaykut-gmail)]

It is fully updated now. However, I don't know how to get the version of
telephathy gabble

2012/1/29 Bilal Shahid <email address hidden>

> any steps or some which version of telepathy gabble are you using?
> is your system fully updated?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/915015
>
> Title:
> telepathy-gabble crashed with signal 5 in g_return_if_fail_warning()
>
> Status in “telepathy-gabble” package in Ubuntu:
> Incomplete
>
> Bug description:
> .
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: telepathy-gabble 0.15.2-0ubuntu1
> ProcVersionSignature: Ubuntu 3.2.0-8.14-generic-pae 3.2.0
> Uname: Linux 3.2.0-8-generic-pae i686
> NonfreeKernelModules: wl
> ApportVersion: 1.90-0ubuntu1
> Architecture: i386
> Date: Wed Jan 11 22:27:22 2012
> ExecutablePath: /usr/lib/telepathy/telepathy-gabble
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386
> (20120104)
> ProcCmdline: /usr/lib/telepathy/telepathy-gabble
> Signal: 5
> SourcePackage: telepathy-gabble
> StacktraceTop:
> g_return_if_fail_warning () from /lib/i386-linux-gnu/libglib-2.0.so.0
> g_hash_table_foreach () from /lib/i386-linux-gnu/libglib-2.0.so.0
> ?? ()
> g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> ?? ()
> Title: telepathy-gabble crashed with signal 5 in
> g_return_if_fail_warning()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/915015/+subscriptions
>

--
twitter.com/sinan_aykut

[Bilal Shahid (s9iper1)]

if fully updated than there must be 0.15.3 so if you again get this than please note its steps or get the gabble log.or mission control log tomorrow i will talk with kenvandine he will see your bug report more.

[Guillaume-desmottes (guillaume-desmottes)]

Original bug report: https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/915015

I observed this once as well when running master iirc.

#0 g_logv (log_domain=0xb710b66e "GLib", log_level=<optimized out>, format=0xb7113a5e "%s: assertion `%s' failed", args1=0xbfbc7d2c " \370\020\267t\365\020\267\255\001") at /build/buildd/glib2.0-2.31.8/./glib/gmessages.c:765
        domain = 0x0
        data = <optimized out>
        depth = <optimized out>
        log_func = <optimized out>
        domain_fatal_mask = <optimized out>
        masquerade_fatal = <optimized out>
        test_level = <optimized out>
        was_fatal = 0
        was_recursion = 0
        i = <optimized out>
#1 0xb70d00b3 in g_log (log_domain=0xb710b66e "GLib", log_level=G_LOG_LEVEL_CRITICAL, format=0xb7113a5e "%s: assertion `%s' failed") at /build/buildd/glib2.0-2.31.8/./glib/gmessages.c:792
        args = 0xbfbc7d2c " \370\020\267t\365\020\267\255\001"
#2 0xb70d00fd in g_return_if_fail_warning (log_domain=0xb710b66e "GLib", pretty_function=0xb710f820 "g_hash_table_foreach", expression=0xb710f574 "version == hash_table->version") at /build/buildd/glib2.0-2.31.8/./glib/gmessages.c:801
No locals.
#3 0xb70b8328 in g_hash_table_foreach (hash_table=0x993c808, func=0x8108e50 <disconnect_entry_foreach>, user_data=0x0) at /build/buildd/glib2.0-2.31.8/./glib/ghash.c:1510
        node_hash = <optimized out>
        node_key = <optimized out>
        node_value = <optimized out>
        i = <optimized out>
        version = 190
        __PRETTY_FUNCTION__ = "g_hash_table_foreach"
#4 0x08109df7 in gabble_vcard_manager_dispose (object=0x99318c8) at vcard-manager.c:590
        self = 0x99318c8
        priv = 0x99318d8
        __PRETTY_FUNCTION__ = "gabble_vcard_manager_dispose"
#5 0xb718f922 in g_object_unref (_object=0x99318c8) at /build/buildd/glib2.0-2.31.8/./gobject/gobject.c:2971
        weak_locations = 0x0
        object = 0x99318c8
        old_ref = <optimized out>
        __PRETTY_FUNCTION__ = "g_object_unref"
#6 0x080c4aa5 in gabble_connection_dispose (object=0x9924440) at connection.c:1211
        _tp_clear_pointer_tmp = <optimized out>
        self = 0x9924440
        base = 0x9924440
        priv = 0x9924548
        __PRETTY_FUNCTION__ = "gabble_connection_dispose"
#7 0xb718f922 in g_object_unref (_object=0x9924440) at /build/buildd/glib2.0-2.31.8/./gobject/gobject.c:2971
        weak_locations = 0x0
        object = 0x9924440
        old_ref = <optimized out>
        __PRETTY_FUNCTION__ = "g_object_unref"
#8 0xb718fab2 in g_value_object_free_value (value=0x9db8f30) at /build/buildd/glib2.0-2.31.8/./gobject/gobject.c:3291
No locals.
#9 0xb71b15c6 in g_value_unset (value=0x9db8f30) at /build/buildd/glib2.0-2.31.8/./gobject/gvalue.c:276
        value_table = <optimized out>
        __PRETTY_FUNCTION__ = "g_value_unset"
#10 0xb71a50f6 in g_signal_emit_valist (instance=0x9924440, signal_id=18, detail=0, var_args=<optimized out>) at /build/buildd/glib2.0-2.31.8/./gobject/gsignal.c:3063
        instance_and_params = 0x9db8f30
        signal_return_type = 4
        param_values = 0x9db8f44
        node = 0x0
        i = <optimized out>
        n_params = 0
      ...

[Bilal Shahid (s9iper1)]

i have talked with the developer and he sent it to upstream by himself..so here is the link subscribe to that bug as well
https://bugs.freedesktop.org/show_bug.cgi?id=45537

[Will Thompson (wjt)]

Taking a look at this. The problem, in broad terms, is:

#3 0xb70b8328 in g_hash_table_foreach (hash_table=0x993c808, func=0x8108e50
<disconnect_entry_foreach>, user_data=0x0) at

disconnect_entry_foreach, in some situations, ultimately ends up calling g_hash_table_remove(), thereby modifying the table being iterated. I haven't figured out exactly what that situation is, yet.

[Will Thompson (wjt)]

Can't figure out how to reproduce it, sorry.

This line in the backtrace:

#15 0x08098972 in connection_force_close_cb (source=0x9d0b560, res=0x9d236f0,
user_data=0x9910c10) at wocky-c2s-porter.c:1257

tells us that this was an unclean disconnection. My thinking was that we need a vcard cache entry with ->vcard_node, ->pipeline_item, and ->pending_requests to be NULL in order for the code in cache_entry_attempt_to_free() which modifies the hash table to fire, so I tried requesting a vCard, sending back an error of type='wait' to tell it to try again later, and then uncleanly disconnecting the connection in a variety of ways… but no dice.

I did make the surprising discovery that if I change connect/stream-closed.py to send a spurious stanza right before the </stream:stream>:

- # server closes its stream
+ # server tells us it hates us then closes the stream cleanly.
+ stream.send(
+ elem('message', from_='lol@localhost')(
+ elem('body')(u'piss off')
+ ))
     stream.sendFooter()

then the test fails! Gabble never sends the corresponding </stream:stream>. The issue seems to be related to the state transitions of WockyXmppConnection at the end of a stream when it gets a blob of data containing both a stanza and the </stream:stream> — if you stick a q.expect('dbus-signal', signal='MessageReceived') before sendFooter(), the test passes. But I couldn't track it down further. :(

So I am donating these bugs back to the public domain.

[Rigved Rakshit (rigved)]

I have got this crash as well.

Description: Ubuntu precise (development branch)
Release: 12.04

telepathy-gabble:
  Installed: 0.15.3-0ubuntu1
  Candidate: 0.15.3-0ubuntu1
  Version table:
 *** 0.15.3-0ubuntu1 0
        500 http://in.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

[Juha Siltala (topyli)]

I get this right after waking up from suspend. I think something panics too soon when it finds the network connection is not yet ready, but I'm not sure.

[Platon Pukhlechev (ifalkorr-deactivatedaccount)]

caught on 12.10 latest builds. and not only me

[Platon Pukhlechev (ifalkorr-deactivatedaccount)]

i can reproduce this bug. all i need is just switch off my internet or set offline status.

[Sasa Paporovic (melchiaros)]

On the launchpad report one of the users says:

https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/915015/comments/17

"i can reproduce this bug. all i need is just switch off my internet or set offline status."

[Sasa Paporovic (melchiaros)]

This is still actual with the latest version of telepathy. No newer stacktrace is available(identification by apport on launchpad on stacktrace top).

[Bilal Shahid (s9iper1)]

still affecting in ubuntu 13.04 with telepathy gabble 0.15.2-0ubuntu1