indicator-application-service crashed with SIGSEGV in g_object_unref()

Bug #636394 reported by Claitom
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-application (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: indicator-application

Error em upgrade

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: indicator-application 0.2.7-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Sep 12 01:39:29 2010
ExecutablePath: /usr/lib/indicator-application/indicator-application-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100630.2)
ProcCmdline: /usr/lib/indicator-application/indicator-application-service
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x4041b5: cmpb $0x0,(%rbx)
 PC (0x004041b5) ok
 source "$0x0" ok
 destination "(%rbx)" (0x6f74616369646e69) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: indicator-application
StacktraceTop:
 ?? ()
 ?? ()
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 __libc_start_main () from /lib/libc.so.6
Title: indicator-application-service crashed with SIGSEGV in g_object_unref()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (bluetooth-applet:1362): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
 (polkit-gnome-authentication-agent-1:1370): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #637202, 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.