telepathy-butterfly crashed with SIGSEGV in g_thread_self()

Bug #537797 reported by kyleabaker
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
telepathy-butterfly (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: telepathy-butterfly

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
Description: Ubuntu lucid (development branch)
Release: 10.04

2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
telepathy-butterfly:
  Installed: 0.5.4-1
  Candidate: 0.5.4-1
  Version table:
 *** 0.5.4-1 0
        500 http://us.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
Not crash

4) What happened instead
Crashed. It happened immediately when I typed the character 's'. Doesn't seem to happen again now so it must have not been related, but I'm not sure.

ProblemType: Crash
Architecture: amd64
Date: Thu Mar 11 20:33:12 2010
Disassembly: 0x7f85366a18a0: Cannot access memory at address 0x7f85366a18a0
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/telepathy/telepathy-butterfly
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: telepathy-butterfly 0.5.4-1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/telepathy/telepathy-butterfly
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x7f85366a18a0: Cannot access memory at address 0x7f85366a18a0
 PC (0x7f85366a18a0) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: telepathy-butterfly
StacktraceTop:
 ?? ()
 g_thread_self () from /lib/libglib-2.0.so.0
 g_static_private_get () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch ()
Title: telepathy-butterfly crashed with SIGSEGV in g_thread_self()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

StacktraceTop:
 ?? ()
 g_thread_self () from /lib/libglib-2.0.so.0
 g_static_private_get () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch ()

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-butterfly (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in telepathy-butterfly (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in telepathy-butterfly (Ubuntu):
status: Incomplete → Invalid
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.