[Bug 961499] Re: whoopsie crashed with SIGSEGV in g_slice_alloc()

[Andy S]

This has started to affect me this morning after applying latest
updates.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to whoopsie-daisy in Ubuntu.
https://bugs.launchpad.net/bugs/961499

Title:
  whoopsie crashed with SIGSEGV in g_slice_alloc()

Status in “whoopsie-daisy” package in Ubuntu:
  Invalid

Bug description:
  The message appeared  immediatly after login

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: whoopsie 0.1.18
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
  Uname: Linux 3.2.0-19-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Wed Mar 21 15:56:16 2012
  ExecutablePath: /usr/bin/whoopsie
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120217)
  ProcCmdline: whoopsie
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  SegvAnalysis:
   Segfault happened at: 0x7f46679f0f5a <g_slice_alloc+490>:	mov    (%rbx),%rdx
   PC (0x7f46679f0f5a) ok
   source "(%rbx)" (0x3000000000) not located in a known VMA region (needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: whoopsie-daisy
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: Upgraded to precise on 2012-03-13 (8 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie-daisy/+bug/961499/+subscriptions