polkit-gnome-authentication-agent-1 crashed with SIGSEGV in g_datalist_id_set_data_full()

Bug #719922 reported by Raf
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
policykit-1-gnome (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: policykit-1-gnome

System open. Open Channel Software and Crash

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: policykit-1-gnome 0.99-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 16 01:50:16 2011
ExecutablePath: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110212)
ProcCmdline: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
ProcEnviron:
 LANGUAGE=pt_BR:en
 LANG=pt_BR.UTF-8
 LC_MESSAGES=pt_BR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6fb2a039c8 <g_datalist_id_set_data_full+744>: cmp 0x8(%rax),%r12d
 PC (0x7f6fb2a039c8) ok
 source "0x8(%rax)" (0x2474894828ec8350) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: policykit-1-gnome
StacktraceTop:
 g_datalist_id_set_data_full () from /lib/libglib-2.0.so.0
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
Title: polkit-gnome-authentication-agent-1 crashed with SIGSEGV in g_datalist_id_set_data_full()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:1296): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nm-applet:1306): Gtk-CRITICAL **: IA__gtk_widget_is_toplevel: assertion `GTK_IS_WIDGET (widget)' failed

Revision history for this message
Raf (rmtx28) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
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.