dbus-daemon crashed with SIGSEGV

Bug #1014292 reported by Chris Johnston on 2012-06-17
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Medium
Unassigned

Bug Description

Crashed overnight

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: dbus 1.4.18-1ubuntu1
ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
Uname: Linux 3.4.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.2.3-0ubuntu3
Architecture: amd64
Date: Sun Jun 17 00:05:41 2012
ExecutablePath: /bin/dbus-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis: Failure: 'dx'
Signal: 11
SourcePackage: dbus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: dbus-daemon crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-06-12 (5 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Chris Johnston (cjohnston) wrote :

StacktraceTop:
 _dbus_header_load (header=0x7fe1716d9d58, mode=DBUS_VALIDATION_MODE_DATA_IS_UNTRUSTED, validity=0x7fffaf7f2644, byte_order=108, fields_array_len=134, header_len=152, body_len=22, str=0x7fe1714ff438, start=0, len=174) at ../../dbus/dbus-marshal-header.c:993
 load_message (body_len=22, header_len=152, fields_array_len=<optimized out>, byte_order=108, message=0x7fe1716d9d50, loader=0x7fe1714ff430) at ../../dbus/dbus-message.c:3978
 _dbus_message_loader_queue_messages (loader=0x7fe1714ff430) at ../../dbus/dbus-message.c:4181
 _dbus_transport_get_dispatch_status (transport=0x7fe171501520) at ../../dbus/dbus-transport.c:1099
 _dbus_transport_queue_messages (transport=0x7fe171501520) at ../../dbus/dbus-transport.c:1126

Changed in dbus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dbus (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers