telepathy-gabble crashed with SIGABRT in g_assertion_message()

Bug #928162 reported by psypher
80
This bug affects 11 people
Affects Status Importance Assigned to Milestone
telepathy-gabble (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Locked my desktop, went away for a minute, came back, unlocked, error was on the screen.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-gabble 0.15.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Tue Feb 7 11:44:24 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
Signal: 6
SourcePackage: telepathy-gabble
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: telepathy-gabble crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2011-12-21 (48 days ago)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
psypher (psypher246) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x5386e0 "wocky_auth_registry_success_async_func", message=0x7fae94017740 "assertion failed: (priv->handler != NULL)") at /build/buildd/glib2.0-2.31.16/./glib/gtestutils.c:1860
 g_assertion_message_expr (domain=0x509304 "wocky", file=0x5383ec "wocky-auth-registry.c", line=484, func=0x5386e0 "wocky_auth_registry_success_async_func", expr=<optimized out>) at /build/buildd/glib2.0-2.31.16/./glib/gtestutils.c:1871
 wocky_auth_registry_success_async_func (self=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at wocky-auth-registry.c:484
 wocky_auth_registry_success_async_func (self=<optimized out>, callback=<optimized out>, user_data=0xbcbb00) at wocky-auth-registry.c:475
 sasl_auth_stanza_received (source=<optimized out>, res=<optimized out>, user_data=<optimized out>) at wocky-sasl-auth.c:566

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in telepathy-gabble (Ubuntu):
importance: Undecided → Medium
summary: - telepathy-gabble crashed with SIGABRT in raise()
+ telepathy-gabble crashed with SIGABRT in g_assertion_message()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in telepathy-gabble (Ubuntu):
status: New → Confirmed
Revision history for this message
Bilal Shahid (s9iper1) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better,
* can you reproduce it ?
* if so than how can we reproduce it ? any steps ?

Changed in telepathy-gabble (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Bilal Shahid (s9iper1) wrote :

also attach the stacktrace with the debug symbols this stacktrace has no enough
#24 0x0000000000433479 in _start ()
No symbol table info available.

Bilal Shahid (s9iper1)
visibility: private → public
Revision history for this message
Bilal Shahid (s9iper1) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for telepathy-gabble (Ubuntu) because there has been no activity for 60 days.]

Changed in telepathy-gabble (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.