indicator-messages-service crashed with SIGSEGV in g_bit_lock()

Bug #1217014 reported by Alex_ander
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
indicator-messages (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

indicator-messages-service was crashed, when pidgin session is worked

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-messages 13.10.1+13.10.20130822.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic i686
ApportVersion: 2.12.1-0ubuntu2
Architecture: i386
Date: Mon Aug 26 19:49:12 2013
ExecutablePath: /usr/lib/indicator-messages/indicator-messages-service
InstallationDate: Installed on 2013-07-26 (30 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130726)
MarkForUpload: True
ProcCmdline: /usr/lib/indicator-messages/indicator-messages-service
SegvAnalysis:
 Segfault happened at: 0xb7381060 <g_bit_lock+64>: lock bts %ebp,(%esi)
 PC (0xb7381060) ok
 source "%ebp" ok
 destination "(%esi)" (0x00000010) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-messages
StacktraceTop:
 g_bit_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_n_children () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_get_child_value () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: indicator-messages-service crashed with SIGSEGV in g_bit_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Alex_ander (ks-alexandr) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_bit_lock (address=address@entry=0x10, lock_bit=lock_bit@entry=0) at /build/buildd/glib2.0-2.37.6/./glib/gbitlock.c:211
 g_variant_lock (value=0x0) at /build/buildd/glib2.0-2.37.6/./glib/gvariant-core.c:223
 g_variant_n_children (value=value@entry=0x0) at /build/buildd/glib2.0-2.37.6/./glib/gvariant-core.c:931
 g_variant_get_child_value (value=value@entry=0x0, index_=index_@entry=3) at /build/buildd/glib2.0-2.37.6/./glib/gvariant-core.c:977
 app_source_action_check_draw (action_name=0x8fd64c0 "im:prpl-bigbrownchunx-skype:alexdenkin:ivan.kravchenko21", app=0x8fb79b0) at im-application-list.c:228

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in indicator-messages (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in indicator-messages (Ubuntu):
status: New → Confirmed
information type: Private → Public
Revision history for this message
Lars Karlitski (larsu) wrote :

Thanks for reporting this bug. The code in which this crash happened for you was rewritten in r391. I'm pretty sure that rewrite also fixed this bug as a side effect.

Changed in indicator-messages (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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