Ubuntu
policykit-1-gnome package

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

Bug #694032 reported by pschonmann
14
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

Just started with autologin

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: policykit-1-gnome 0.99-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7
Uname: Linux 2.6.37-11-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Dec 23 14:45:51 2010
ExecutablePath: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
ProcEnviron:
 LANGUAGE=cs_CZ:cs:en_GB:en
 LANG=cs_CZ.UTF-8
 LC_MESSAGES=cs_CZ.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ffaeee4f968 <g_datalist_id_set_data_full+744>: cmp 0x8(%rax),%r12d
 PC (0x7ffaeee4f968) ok
 source "0x8(%rax)" (0x00000038) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: policykit-1-gnome
StacktraceTop:
 g_data_set_internal (datalist=0x1e93840, key_id=52, data=0x0, destroy_func=0) at /build/buildd/glib2.0-2.27.5/glib/gdataset.c:325
 g_datalist_id_set_data_full (datalist=0x1e93840, key_id=52, data=0x0, destroy_func=0) at /build/buildd/glib2.0-2.27.5/glib/gdataset.c:598
 g_object_unref (_object=0x1e93830) at /build/buildd/glib2.0-2.27.5/gobject/gobject.c:2703
 ?? ()
 __libc_start_main (main=0x408130, argc=1, ubp_av=0x7fff2969add8, init=<value optimised out>, fini=<value optimised out>, rtld_fini=<value optimised out>, stack_end=0x7fff2969adc8) at libc-start.c:226
Title: polkit-gnome-authentication-agent-1 crashed with SIGSEGV in g_data_set_internal()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (nautilus:1504): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Revision history for this message
pschonmann (pschonmann) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_datalist_id_set_data_full (datalist=0x1e93840,
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
pschonmann (pschonmann)
visibility: private → public
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

I am able to reproduce this bug on a Natty i386 system. It came up after I updated (via 'sudo apt-get update', 'sudo apt-get upgrade'), rather than immediately after logging in. But I updated very soon after logging in, and I cannot be sure that it had anything to do with this bug.

(I originally reported this as Bug 695243, thinking that my stack trace might be better than the one here. It isn't, so I've marked that as a duplicate of this bug.)

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

Possibly relevant information from my now-duplicate-marked bug report:

"This bug might be related to Bug 685168, which I have been experiencing from time to time lately on this machine (as duplicate bug 692397). When I saw the Apport icon, I had assumed it was that bug again. However, in that bug, the segfault was in g_datalist_id_set_data_full() rather than g_data_set_internal() as is the case here."

tags: added: i386
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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