polkitd crashed with SIGSEGV in dbus_message_iter_append_basic()

Bug #636270 reported by JR
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
policykit-1 (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: policykit-1

Crash came on authenticating to change login screen preferences - it asked for my password several times and then crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: policykit-1 0.96-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Sun Sep 12 10:55:58 2010
ExecutablePath: /usr/lib/policykit-1/polkitd
ProcCmdline: /usr/lib/policykit-1/polkitd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x537770: pcmpeqb (%esi),%xmm0
 PC (0x00537770) 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/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()
UserGroups:

Revision history for this message
JR (jonathanrodgers-hotmail) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __strlen_sse2 () from /lib/libc.so.6
 _dbus_marshal_write_basic (str=0x8fca638, insert_at=54,
 _dbus_type_writer_write_basic (writer=0xbfb93e10, type=115,
 dbus_message_iter_append_basic (iter=0xbfb93e08, type=115,
 egg_dbus_append_value_to_iter (iter=<value optimized out>,

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 (Ubuntu):
importance: Undecided → Medium
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.