[Bug 1125184] Re: whoopsie crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
Launchpad Bug Tracker
1125184 at bugs.launchpad.net
Thu Feb 14 18:45:11 UTC 2013
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: whoopsie (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1125184
Title:
whoopsie crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
Status in “whoopsie” package in Ubuntu:
Confirmed
Bug description:
There was nothing special happening. Just started the virtual machine
then the error appeared.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: whoopsie 0.2.13
ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic i686
ApportVersion: 2.8-0ubuntu4
Architecture: i386
CrashReports: 640:106:110:347198:2013-02-14 14:22:48.238487958 +0100:2013-02-14 14:22:49.238487958 +0100:/var/crash/_usr_bin_whoopsie.106.crash
Date: Thu Feb 14 14:22:49 2013
ExecutablePath: /usr/bin/whoopsie
InstallationDate: Installed on 2012-11-30 (76 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20121129)
MarkForUpload: True
ProcCmdline: whoopsie
ProcEnviron:
PATH=(custom, no user)
TERM=linux
SegvAnalysis:
Segfault happened at: 0x804c3f8: mov 0x4(%eax),%ebp
PC (0x0804c3f8) ok
source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
destination "%ebp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: whoopsie
StacktraceTop:
?? ()
g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: whoopsie crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
WhoopsieLog:
Using lock path: /var/lock/whoopsie/lock
Using lock path: /var/lock/whoopsie/lock
Using lock path: /var/lock/whoopsie/lock
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1125184/+subscriptions
More information about the foundations-bugs
mailing list