After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 784575 - List of discovered/detected printers in add-printer dialog is cluttered by SMB entries of local printers
List of discovered/detected printers in add-printer dialog is cluttered by SM...
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: Printers
3.24.x
Other Linux
: Normal major
: ---
Assigned To: Marek Kašík
Control-Center Maintainers
triaged
Depends on:
Blocks:
 
 
Reported: 2017-07-05 19:41 UTC by Till Kamppeter
Modified: 2021-06-09 16:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Till Kamppeter 2017-07-05 19:41:05 UTC
The list of detected/discovered printers shows as first the available local (USB) printers, then printers on the local network (IPP, AppSocket, LPD, ...) but after that it lists for each local CUPS queue a printer entry with the name of the local CUPS queue with "-2" added and "Location: //WORKGROUP/HOSTNAME" (HOSTNAME being the name of the local machine in all uppercase).

So (at least on machines with smbd running) it picks up all SMB shares of the local printers. It does absolutely make no sense to set up these queues as the local CUPS queues are already available. These entries (SMB printers of local machine) should be suppressed.
Comment 1 Till Kamppeter 2017-09-19 12:47:33 UTC
Note that the problem only occurs when the smbd is running locally (and perhaps also if there are local printers which are shared).
Comment 2 André Klapper 2021-06-09 16:30:33 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new bug report at
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/

Thank you for your understanding and your help.