Printer managed wrongly in Settings -> Printers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
gnome-control-center (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Settings -> Printers automatically adds "EPSON_
When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues).
Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers.
1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui
2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it
3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer.
Why is this happening and can it be improved?
---
ProblemType: Bug
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-11-16 (395 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lpstat: device for EPSON_L3160_Series: implicitclass:
MachineType: HP OMEN by HP Laptop 17-cb0xxx
NonfreeKernelMo
Package: gnome-control-
PackageArchitec
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/
ProcCmdline: BOOT_IMAGE=
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
Tags: focal
Uname: Linux 5.4.0-45-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/05/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.16
dmi.board.
dmi.board.name: 8603
dmi.board.vendor: HP
dmi.board.version: 45.38
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.
dmi.modalias: dmi:bvnAMI:
dmi.product.family: 103C_5335KV HP OMEN
dmi.product.name: OMEN by HP Laptop 17-cb0xxx
dmi.product.sku: 7NG00EA#BED
dmi.sys.vendor: HP
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1908334/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]