unity-webapps-context-daemon crashed with SIGSEGV in g_slice_alloc()

Bug #1060966 reported by Scott Ladden
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libunity-webapps (Ubuntu)
New
Undecided
Unassigned

Bug Description

I logged in and left my computer....came back to bugs/problems reported. I didn't have anything opened.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity-webapps-service 2.3.9-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Wed Oct 3 06:39:57 2012
ExecutablePath: /usr/lib/libunity-webapps/unity-webapps-context-daemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/libunity-webapps/unity-webapps-context-daemon Launchpad launchpad.net icon://unity-webapps-launchpad [Invalid\ UTF-8]
SegvAnalysis:
 Segfault happened at: 0x7fd6fb97d852 <g_slice_alloc+210>: mov 0x8(%rdx),%rbx
 PC (0x7fd6fb97d852) ok
 source "0x8(%rdx)" (0x7fd600000008) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: libunity-webapps
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_variant_builder_end () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: unity-webapps-context-daemon crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to quantal on 2012-10-02 (1 days ago)
UserGroups: adm admin cdrom crontab dialout disk fuse lpadmin mediatomb plugdev sambashare users vboxusers video whoopsie

Revision history for this message
Scott Ladden (slicer777) 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 #1058784, 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
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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