polkitd crashed with SIGSEGV in dbus_message_iter_append_basic()

Bug #586276 reported by ERE
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
policykit-1 (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: policykit-1

polkitd crashed with SIGSEGV in dbus_message_iter_append_basic()

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: policykit-1 0.96-2
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Thu May 27 12:06:23 2010
ExecutablePath: /usr/lib/policykit-1/polkitd
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/policykit-1/polkitd
ProcEnviron:

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

Revision history for this message
ERE (karfter) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 _dbus_marshal_write_basic (str=0x94a84c0, insert_at=54,
 _dbus_type_writer_write_basic (writer=0xbf8cd200, type=115,
 dbus_message_iter_append_basic (iter=0xbf8cd1f8, 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
ERE (karfter)
visibility: private → public
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.