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

Bug #760376 reported by Lemuel Cantos
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
policykit-1-gnome (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: policykit-1-gnome

it crashed on startup

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: policykit-1-gnome 0.99-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Wed Apr 13 18:03:01 2011
ExecutablePath: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110327)
ProcCmdline: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
ProcEnviron:
 LANGUAGE=en_PH:en
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa7a79889d8 <g_datalist_id_set_data_full+744>: cmp 0x8(%rax),%r12d
 PC (0x7fa7a79889d8) ok
 source "0x8(%rax)" (0x6e6f697373655336) 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/x86_64-linux-gnu/libglib-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: polkit-gnome-authentication-agent-1 crashed with SIGSEGV in g_datalist_id_set_data_full()
UpgradeStatus: Upgraded to natty on 2011-04-13 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Lemuel Cantos (lemuelinchrist) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 697095, so it 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.

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.