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

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 #1047236, 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/1067926/+attachment/3402061/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private 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/1067926

Title:
  gwibber-service crashed with SIGSEGV in g_slist_foreach()

Status in “gwibber” package in Ubuntu:
  New

Bug description:
  no idea what was going on when this happened. I wasn't using gwibber
  in any way. I haven't even configured it. I hope the debug tool has
  extracted enough information to help somebody in tracking the problem
  down, as I am probably not going to be able to help in any way :-/.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gwibber-service 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Oct 17 23:46:50 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gwibber-service
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=<set>
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f45b9ca8314:        subq   $0x1,(%rcx)
   PC (0x7f45b9ca8314) ok
   source "$0x1" ok
   destination "(%rcx)" (0x00000000) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gwibber
  StacktraceTop:
   ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slist_free_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
   ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
  Title: gwibber-service crashed with SIGSEGV in g_slist_foreach()
  UpgradeStatus: Upgraded to quantal on 2012-10-04 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vde2-net

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to