desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #120566
[Bug 1115653] Re: GNOME Printer Setup Tool: Printers are discovered only through a hard-coded list of CUPS backends
** Changed in: gnome-control-center (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1115653
Title:
GNOME Printer Setup Tool: Printers are discovered only through a hard-
coded list of CUPS backends
Status in GNOME Control Center:
Fix Released
Status in gnome-control-center package in Ubuntu:
Fix Released
Bug description:
For development of printing infrastructure I use a test CUPS backend
(attached, to be installed in /usr/lib/cups/backend/ and to be made
executable) reporting printers as detected which in reality do not
exist, so that I do not need the actual printer models for the test.
Other users use manufacturer-supplied printer drivers which bring
their own CUPS backends, and Ubuntu also ships the "hpfax" backend
which is not in the hard-coded list.
The source code of gnome-control-center, file panels/printers/pp-
utils.c contains
----------
[...]
static void
get_device_attributes_async_scb (GHashTable *result,
gpointer user_data)
{
[...]
const gchar *backends[] =
{"hpfax", "ncp", "beh", "bluetooth", "snmp",
"dnssd", "hp", "ipp", "lpd", "parallel",
"serial", "socket", "usb", NULL};
[...]
----------
and tests show that the tool is actually only discovering printers
through these backends. It is easy to make CUPS using all backends for
detecting printers, one can do it by a single function call. Other
printer setup tools do it this way and I expect gnome-control-center
to also use all CUPS backends, so that users who use special backends
can set up their printers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1115653/+subscriptions