← Back to team overview

desktop-packages team mailing list archive

[Bug 847034] Re: gwibber crashed with SIGSEGV in g_bit_lock()

 

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

Thank you for taking the time to report this crash and helping to make
Ubuntu better.  This particular crash has already been reported and is a
duplicate of bug #834762, 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/847034/+attachment/2386159/+files/CoreDump.gz

** Attachment removed: "Dependencies.txt"
   https://bugs.launchpad.net/bugs/847034/+attachment/2386160/+files/Dependencies.txt

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

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

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

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

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

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

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

** Visibility changed to: Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/847034

Title:
  gwibber crashed with SIGSEGV in g_bit_lock()

Status in “gwibber” package in Ubuntu:
  New

Bug description:
  Just starting gwibber.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gwibber 3.1.90-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  Date: Sun Sep 11 15:50:23 2011
  ExecutablePath: /usr/bin/gwibber
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110909)
  ProcCmdline: gwibber
  ProcEnviron:
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f3f7b834cd8 <g_bit_lock+72>:	lock bts %r12d,(%rbx)
   PC (0x7f3f7b834cd8) ok
   source "%r12d" ok
   destination "(%rbx)" (0x00000020) not located in a known VMA region (needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gwibber
  StacktraceTop:
   g_bit_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_n_children () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_iter_init () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libgwibber.so.2
   ?? () from /usr/lib/libgwibber.so.2
  Title: gwibber crashed with SIGSEGV in g_bit_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/847034/+subscriptions