whoopsie crashed with SIGSEGV in g_object_newv()

Bug #961901 reported by lucky
262
This bug affects 1 person
Affects Status Importance Assigned to Milestone
whoopsie-daisy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Bug dans le bureau avec ubunu one

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: whoopsie 0.1.19
ProcVersionSignature: Ubuntu 3.2.0-19.31-generic 3.2.12
Uname: Linux 3.2.0-19-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Thu Mar 22 07:48:31 2012
ExecutablePath: /usr/bin/whoopsie
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: whoopsie
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SegvAnalysis:
 Segfault happened at: 0x7fd47b39c92b <g_string_sized_new+43>: movq $0x0,0x10(%rax)
 PC (0x7fd47b39c92b) ok
 source "$0x0" ok
 destination "0x10(%rax)" (0x7fd47b97ddb4) in non-writable VMA region: 0x7fd47b87e000-0x7fd47b9d3000 r-xp /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.3122.0
SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.3122.0
Signal: 11
SourcePackage: whoopsie-daisy
StacktraceTop:
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: whoopsie crashed with SIGSEGV in g_object_newv()
UpgradeStatus: Upgraded to precise on 2012-03-22 (0 days ago)
UserGroups:

Revision history for this message
lucky (jlbrand) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #960757, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.