polkit-gnome-authentication-agent-1 crashed with SIGSEGV in g_datalist_id_set_data_full() got error report on startup.

Bug #685168 reported by Sven van Vossen
646
This bug affects 148 people
Affects Status Importance Assigned to Milestone
policykit-1-gnome (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: policykit-1-gnome

Using 11.04 daily build (04-12-10) on a usb stick with 12gb casper-rw partition.

version:
  Geïnstalleerd: 0.99-1ubuntu1
  Kandidaat: 0.99-1ubuntu1
  Versietabel:
 *** 0.99-1ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

Got an error report when gnome came up. I got a message that 3d-support was disabled though.
As far i i know nothing strange happened.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: policykit-1-gnome 0.99-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-7.19-generic 2.6.37-rc3
Uname: Linux 2.6.37-7-generic i686
Architecture: i386
Date: Sat Dec 4 12:50:05 2010
ExecutablePath: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101204)
ProcCmdline: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
ProcEnviron:
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x909e58 <g_datalist_id_set_data_full+744>: cmp 0x4(%eax),%edi
 PC (0x00909e58) ok
 source "0x4(%eax)" (0x00000005) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL 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

Revision history for this message
Sven van Vossen (svenvv) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_datalist_id_set_data_full (datalist=0x8399208, key_id=52,
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in policykit-1-gnome (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libc-bin: installed version 2.12.1-0ubuntu9, latest version: 2.12.1-0ubuntu10
libc6-dbg: installed version 2.12.1-0ubuntu9, latest version: 2.12.1-0ubuntu10
libc6: installed version 2.12.1-0ubuntu9, latest version: 2.12.1-0ubuntu10

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
Revision history for this message
Andree (dreewill-deactivatedaccount) wrote :

it also happened for me right after the login.

tags: added: amd64 macbook
Revision history for this message
Peter Cooper (pcooper-gaitor) wrote :

Same here

Antono Vasiljev (antono)
Changed in policykit-1-gnome (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Jacopo Moronato (jmoronat) wrote :

Happened to me after mounting a partition.

Revision history for this message
Per Kongstad (p-kongstad) wrote :

I have a fully updated Natty based on main server and this is still happening.

Revision history for this message
Tyler R (hunterkasy) wrote :

it happened to me after login

Revision history for this message
IKT (ikt) wrote :

Still happening, virtualbox with latest updates.

Revision history for this message
mick222 (michaelcranie) wrote :

Happened after updates. Natty wouldn't boot no xorg so instlled xorg with apt-get then rebooted got this error.

Revision history for this message
Jasper Frumau (jfrumau) wrote :

Just had the same issue with latest Natty Narwhal Desktop built in Virtual Nox

Revision history for this message
Greg Adams (adamsgn) wrote :

Got this error when logging into Classic mode

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.