cupsd crashed with SIGSEGV in dbus_message_iter_append_basic()

Bug #768274 reported by Alexander Kallenbach
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: cups

Happend to me while updating. Don't know if it is the same as bug #754567.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: cups 1.4.6-5ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Tue Apr 19 11:16:01 2011
ExecutablePath: /usr/sbin/cupsd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: Acer AOA150
Papersize: letter
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: /usr/sbin/cupsd -F
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=36fd85ae-df28-44ca-80f1-5cf34fe89b61 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x886416: cmpb $0x0,(%edx)
 PC (0x00886416) ok
 source "$0x0" ok
 destination "(%edx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 dbus_message_iter_append_basic () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? ()
Title: cupsd crashed with SIGSEGV in dbus_message_iter_append_basic()
UpgradeStatus: Upgraded to natty on 2011-04-11 (9 days ago)
UserGroups:

dmi.bios.date: 05/09/2008
dmi.bios.vendor: Acer
dmi.bios.version: v0.3305
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrv0.3305:bd05/09/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AOA150
dmi.product.version: 1
dmi.sys.vendor: Acer

Revision history for this message
Alexander Kallenbach (kallenbachalex) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __strlen_sse2 () at ../sysdeps/i386/i686/multiarch/strlen-sse2.S:46
 marshal_string (str=0x21c85284, insert_at=0, type=115, value=0x21c61338, byte_order=108, pos_after=0xbfe5eb0c) at dbus-marshal-basic.c:778
 _dbus_marshal_write_basic (str=0x21c85284, insert_at=0, type=115, value=0x21c61338, byte_order=108, pos_after=0xbfe5eb0c) at dbus-marshal-basic.c:858
 _dbus_type_writer_write_basic_no_typecode (writer=0xbfe5eafc, type=115, value=0x21c61338) at dbus-marshal-recursive.c:1589
 _dbus_type_writer_write_basic (writer=0xbfe5eafc, type=115, value=0x21c61338) at dbus-marshal-recursive.c:2311

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 cups (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in cups (Ubuntu):
status: New → Confirmed
visibility: private → public
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.

This was reported against a now obsolete release so I'm going to close the report.

Changed in cups (Ubuntu):
status: Confirmed → Invalid
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.