GNOME Printer Setup Tool: Printers are discovered only through a hard-coded list of CUPS backends
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center |
Fix Released
|
High
|
|||
gnome-control-center (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
For development of printing infrastructure I use a test CUPS backend (attached, to be installed in /usr/lib/
The source code of gnome-control-
----------
[...]
static void
get_device_
{
[...]
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-
Changed in gnome-control-center (Ubuntu): | |
status: | New → Triaged |
Changed in gnome-control-center: | |
importance: | Unknown → High |
status: | Unknown → New |
Changed in gnome-control-center: | |
status: | New → Fix Released |
Changed in gnome-control-center (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in gnome-control-center (Ubuntu): | |
status: | Fix Committed → Fix Released |
This is a regression compared to Quantal. There system- config- printer was used which did it correctly.