Incorrect information about the number of jobs the printer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
If you launch two printer's jobs and next delete those jobs, you can see the number "2" when you click on the indicator of printer (near the clock): that information is incorrect because I delete the jobs
Description: Ubuntu 12.04.1 LTS
Release: 12.04
I use the release-version of system-
What you expected to happen: I want see "0 jobs" of my printer
What happened instead: I see "2 jobs" of my printer (but I delete those jobs!)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: system-
ProcVersionSign
Uname: Linux 3.2.0-35-
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: i386
Date: Fri Jan 4 15:23:22 2013
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for ML-2240-Series: usb://Samsung/
MachineType: Compaq Evo D510 CMT
MarkForUpload: True
PackageArchitec
Papersize: a4
PpdFiles: ML-2240-Series: Samsung ML-2240, 2.0.0
ProcEnviron:
LANGUAGE=it:en
PATH=(custom, no user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: system-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2002
dmi.bios.vendor: Compaq
dmi.bios.version: 686O2 v2.20
dmi.board.name: 07E8h
dmi.board.vendor: Compaq
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Compaq
dmi.modalias: dmi:bvnCompaq:
dmi.product.name: Evo D510 CMT
dmi.sys.vendor: Compaq
mtime.conffile.
Hello Davide, config- printer package. You made this bug report in 2013 and Ubuntu and the system- config- printer package have been updated since then.
Thank you for submitting this bug and reporting a problem with the system-
Could you confirm that this is no longer a problem and that we can close the ticket?
If it is still a problem, are you still interested in finding a solution to this bug?
If you are, could you let us know and, in the current version, could you run the following (only once):
apport-collect 1096080
and upload the updated logs and and any other logs that are relevant for this particular issue.
Thank you again for helping make Ubuntu better.
G
[Ubuntu Bug Squad volunteer triager]