X crash at login: 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
In Ubuntu 11.04, when I login using "Ubuntu" or "Ubuntu classic" mode, I have an immediate crash. Here I have filled this report using apport-bug informaiton.
Note that when I login using "Ubuntu classic (without effect)", I don't have the crash and the desktop seems to work fine.
This bug report is the same as this one I already filled https:/
But here you have the apport crash report.
I hope it will help to find out the problem.
The crash is in fact in X server, as you can see in the attached Xorg.0.log.old
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: policykit-1-gnome 0.99-1ubuntu4
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Jun 12 16:06:41 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/
ProcCwd: /home/loic
ProcEnviron:
LANGUAGE=fr_FR:en
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f3d982229d8 <g_datalist_
PC (0x7f3d982229d8) ok
source "0x8(%rax)" (0x7375424437) 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 () from /lib/x86_
?? ()
Title: polkit-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.