whoopsie crashed with SIGSEGV in g_slice_alloc()

[Emanuele Sottocorno]

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:

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

whoopsie version 0.1.18 required, but 0.1.19 is available
outdated debug symbol package for whoopsie: package version 0.1.19 dbgsym version 0.1.18

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Andy S (andy-speed)]

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

[Francesco Muriana (f-muriana)]

The same for me: once the latest updates were installed, I had this bug

[Launchpad Janitor (janitor)]

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

[godlike (godlike73)]

I have it with a fresh install

[Barry Drake (b-drake)]

This occurred after tonight's updates and re-boot. Had tried to launch ubuntu-tweak when whoopsie crashed.

[Philip Prudhomme (lady-lawdown)]

Seems to have been provoked by Rhytmbox.

[kjeld Olsen (kjeldo)]

This one crashed a while after coming out of suspend, the lid had been closed for a couple of hours.

[J B (scottie)]

just happened with all updates installed.

( no new updates with sudo apt-get update, sudo apt-get upgrade, sudo apt-get dist-upgrade.)

pc still running which is good. hopefully no updates that will make systems unusable.

actually just had one, but it was because amd/ati radeon binary driver was installed manually. fixed by promptly reinstalling with --force

[John McCabe-Dansted (gmatht)]

I have attached a stacktrace generated with: apport-retrace --stdout /var/crash/_usr_bin_whoopsie.111.crash

[Evan (ev)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This is fixed in the latest version of whoopsie, 0.1.23.