Ubuntu
telepathy-haze package

telepathy-haze crashed with SIGSEGV in peer_connection_find_by_type()

Bug #809277 reported by David Baucum
146
This bug affects 31 people
Affects Status Importance Assigned to Milestone
telepathy-haze (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Crash came when Empathy started.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: telepathy-haze 0.4.0-1ubuntu
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Tue Jul 12 07:47:10 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/telepathy-haze
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/telepathy/telepathy-haze
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f79c09f9c33 <peer_connection_find_by_type+19>: mov 0x1a8(%rdi),%rbp
 PC (0x7f79c09f9c33) ok
 source "0x1a8(%rdi)" (0x000001a8) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-haze
StacktraceTop:
 peer_connection_find_by_type () from /usr/lib/purple-2/liboscar.so.0
 oscar_send_typing () from /usr/lib/purple-2/liboscar.so.0
 purple_conversation_destroy () from /usr/lib/libpurple.so.0
 ?? ()
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: telepathy-haze crashed with SIGSEGV in peer_connection_find_by_type()
UpgradeStatus: Upgraded to natty on 2011-07-11 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
David Baucum (maxolasersquad) wrote :
David Baucum (maxolasersquad)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 peer_connection_find_by_type (od=0x0, bn=0x1e95eb0 "AOL System Msg", type=4) at /build/buildd/pidgin-2.7.11/./libpurple/protocols/oscar/peer.c:77
 oscar_send_typing (gc=0x1bb0950, name=0x1e95eb0 "AOL System Msg", state=PURPLE_NOT_TYPING) at /build/buildd/pidgin-2.7.11/./libpurple/protocols/oscar/oscar.c:3158
 purple_conversation_destroy (conv=0x1d7f860) at /build/buildd/pidgin-2.7.11/./libpurple/conversation.c:464
 ?? ()
 g_object_unref (_object=0x1b8f4c0) at /build/buildd/glib2.0-2.28.6/./gobject/gobject.c:2697

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-haze (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor)
Changed in telepathy-haze (Ubuntu):
status: New → Confirmed
Revision history for this message
legrus (legrus) wrote :

Also in my new Oneiric beta2 on every startup.

Revision history for this message
Ritesh Raj Sarraf (rrs) wrote :

Seen on my box with Precise 12.04

Revision history for this message
bwat47 (bwat47) wrote :

Same here with precise beta 1

Revision history for this message
David Velazquez (lemonsforlemonade) wrote :

Just occurred for me with Precise beta 1 x64 updated this morning. I wasn't doing anything at the time to have caused it and I cannot reproduce it easily.

Revision history for this message
bwat47 (bwat47) wrote :

It seems to happen for me shortly after I first start empathy. This crash message comes up, but It doesn't seem to have any noticeable adverse effects (besides the crash report popping up)

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. Please answer these questions:

* Is this reproducible now ?
* 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-haze (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Torsten Krah (tkrah) wrote :

Yeah it is. Login and crash dialog pops up. Crash report stacktrace does show:

SegvAnalysis:
 Segfault happened at: 0x7f43b17e8873 <peer_connection_find_by_type+19>: mov 0x1a8(%rdi),%rbp
 PC (0x7f43b17e8873) ok
 source "0x1a8(%rdi)" (0x000001a8) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
SourcePackage: telepathy-haze
Stacktrace:
 #0 peer_connection_find_by_type (od=0x0, bn=0x2710050 "402573797", type=4) at /build/buildd/pidgin-2.10.3/./libpurple/protocols/oscar/peer.c:77
         cur = <optimized out>
         conn = <optimized out>
 #1 0x00007f43b17e45d9 in oscar_send_typing (gc=0x221f210, name=0x2710050 "402573797", state=PURPLE_NOT_TYPING) at /build/buildd/pidgin-2.10.3/./libpurple/protocols/oscar/oscar.c:3162
         od = 0x0
         conn = <optimized out>
 #2 0x00007f43b6c73205 in purple_conversation_destroy (conv=0x2912290) at /build/buildd/pidgin-2.10.3/./libpurple/conversation.c:483
         prpl_info = 0x7f43b1c010e0
         ops = 0x62da60
         gc = 0x221f210
         name = 0x2710050 "402573797"
         hc = {type = 36474960, name = 0x1 <Address 0x1 out of bounds>, account = 0x1}
         __PRETTY_FUNCTION__ = "purple_conversation_destroy"
...

Steps to reproduce: Login to your gnome3 session and watch the crash popup dialog appearing; don't know the exact trigger.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers

Remote bug watches

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