polkitd crashed with SIGSEGV in dbus_message_iter_append_basic()

Bug #526314 reported by George Kontis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
policykit-1 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: policykit-1

After updating last night it is not possible to conect wireless.

ProblemType: Crash
Architecture: i386
Date: Tue Feb 23 11:35:45 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/policykit-1/polkitd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
Package: policykit-1 0.96-1
ProcCmdline: /usr/lib/policykit-1/polkitd
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0x5a8790: pcmpeqb (%esi),%xmm0
 PC (0x005a8790) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: policykit-1
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 dbus_message_iter_append_basic () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libeggdbus-1.so.0
Title: polkitd crashed with SIGSEGV in dbus_message_iter_append_basic()
Uname: Linux 2.6.32-14-generic i686
UserGroups:

Revision history for this message
George Kontis (giormatsis) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #509651, 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.

visibility: private → public
tags: removed: need-i386-retrace
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.