← Back to team overview

dx-packages team mailing list archive

[Bug 1216758] Re: indicator-messages-service crashed with SIGSEGV in g_bit_lock()

 

*** This bug is a duplicate of bug 1217014 ***
    https://bugs.launchpad.net/bugs/1217014

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1217014, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   https://bugs.launchpad.net/bugs/1216758/+attachment/3787883/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   https://bugs.launchpad.net/bugs/1216758/+attachment/3787885/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   https://bugs.launchpad.net/bugs/1216758/+attachment/3787887/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   https://bugs.launchpad.net/bugs/1216758/+attachment/3787888/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   https://bugs.launchpad.net/bugs/1216758/+attachment/3787889/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   https://bugs.launchpad.net/bugs/1216758/+attachment/3787890/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   https://bugs.launchpad.net/bugs/1216758/+attachment/3787891/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1217014

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1216758

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

Status in “indicator-messages” package in Ubuntu:
  In Progress

Bug description:
  indicator-messages-service crashed randomly after recent update. Not
  sure how to reproduce, but the stack trace may indicate in which
  circumstances it crashed.

  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 x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Mon Aug 26 08:28:29 2013
  ExecutablePath: /usr/lib/indicator-messages/indicator-messages-service
  InstallationDate: Installed on 2012-02-05 (567 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/indicator-messages/indicator-messages-service
  SegvAnalysis:
   Segfault happened at: 0x7f5a0f27b1c8 <g_bit_lock+72>:	lock bts %r12d,(%rbx)
   PC (0x7f5a0f27b1c8) ok
   source "%r12d" ok
   destination "(%rbx)" (0x00000020) not located in a known VMA region (needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: indicator-messages
  StacktraceTop:
   g_bit_lock (address=address@entry=0x20, lock_bit=lock_bit@entry=0) at /build/buildd/glib2.0-2.37.6/./glib/gbitlock.c:211
   g_variant_lock (value=value@entry=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=0x0, index_=3) at /build/buildd/glib2.0-2.37.6/./glib/gvariant-core.c:977
   ?? ()
  Title: indicator-messages-service crashed with SIGSEGV in g_bit_lock()
  UpgradeStatus: Upgraded to saucy on 2013-05-19 (98 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1216758/+subscriptions


References