polkit-gnome-authentication-agent-1 crashed with SIGSEGV in g_datalist_id_set_data_full()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| policykit-1-gnome (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: policykit-1-gnome
This is probably a duplicate of an already reported bug, but there are many already and not sure what one. This happened after login while connecting to a wireless network.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: policykit-1-gnome 0.99-1ubuntu4
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Tue Apr 12 18:33:19 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100316)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f9314f359d8 <g_datalist_
PC (0x7f9314f359d8) ok
source "0x8(%rax)" (0x7974697a) 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_
g_object_unref () from /usr/lib/
?? ()
__libc_start_main (main=0x408130, argc=1, ubp_av=
?? ()
Title: polkit-
UpgradeStatus: Upgraded to natty on 2011-04-12 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare video
XsessionErrors: (nautilus:2829): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
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 #743623, 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.