On every boot, a message appears that my wireless printer has been added
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I have a Brother HL 3170CDW printer on my wifi network. Every time I boot Ubuntu, a notification appears at the top of the login screen saying that "The printer Brother_
This is a nuisance/cosmetic issue only -- the printer is not actually added multiple times. It only appears once in the Printers section of Settings.
To be clear, I have not installed any drivers or printer-related software other than what is supplied in the default Focal 20.04 installation.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSign
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Tue May 12 09:17:34 2020
InstallationDate: Installed on 2020-05-11 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lpstat: device for Brother_
MachineType: Razer Blade
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/16/2019
dmi.bios.vendor: Razer
dmi.bios.version: 1.05
dmi.board.name: Razer CH20
dmi.board.vendor: Razer
dmi.chassis.type: 10
dmi.chassis.vendor: Razer
dmi.modalias: dmi:bvnRazer:
dmi.product.family: 1A582002 Razer Blade
dmi.product.name: Blade
dmi.product.sku: RZ09-02888E92
dmi.product.
dmi.sys.vendor: Razer
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1725955, so it 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. Feel free to continue to report any other bugs you may find.