cupsd assert failure: cupsd: ../avahi-common/dbus-watch-glue.c:205: timeout_data_ref: Assertion `t->ref >= 1' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
no idea what caused it
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: cups 1.5.0-5
ProcVersionSign
Uname: Linux 3.0.0-10-generic i686
NonfreeKernelMo
Architecture: i386
AssertionMessage: cupsd: ../avahi-
CupsErrorLog:
W [05/Sep/
W [05/Sep/
W [05/Sep/
Date: Wed Sep 7 12:43:59 2011
ExecutablePath: /usr/sbin/cupsd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
Lpstat: device for Officejet-
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business
MachineType: Compaq-Presario NP185AA-ABA CQ5110F
Papersize: letter
PpdFiles: Officejet-
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: /usr/sbin/cupsd -F
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: cups
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/i386-
abort () from /lib/i386-
__assert_fail () from /lib/i386-
?? () from /usr/lib/
Title: cupsd assert failure: cupsd: ../avahi-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 03/20/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.38
dmi.board.name: NARRA5
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 5.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: NP185AA-ABA CQ5110F
dmi.sys.vendor: Compaq-Presario
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 #835462, 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.