No printer output after cups security update on 2/12/2010
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: cups
I've reinstalled the drivers. When printing, the computer says the data is sent successfully and the screen on the printer (Brother MFC7820N) says "receiving", but when the data transfer is complete, the printer just goes back to sleep instead of printing.
ProblemType: Bug
Architecture: amd64
Date: Sun Feb 14 10:07:33 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Lpstat:
device for Brother-MFC-7820N: dnssd:/
device for HP-Officejet-6300: hp:/net/
MachineType: System76, Inc. Pangolin Performance
NonfreeKernelMo
Package: cups 1.4.1-5ubuntu2.2
Papersize: letter
PpdFiles:
Brother-MFC-7820N: Brother MFC-7820N Foomatic/Postscript
HP-Officejet-6300: HP Officejet 6300 Series hpijs, 3.9.8
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: cups
Uname: Linux 2.6.31-19-generic x86_64
dmi.bios.date: 11/24/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 1.00.14MN
dmi.board.
dmi.board.name: Pangolin Performance
dmi.board.vendor: System76, Inc.
dmi.board.version: panp4n
dmi.chassis.
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Pangolin Performance
dmi.product.
dmi.sys.vendor: System76, Inc.
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. Ubuntu 9.10 is no longer supported and 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. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.