[Desktop-packages] [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,
gpointeruser_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
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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: Triaged => Fix Committed
--
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 Committed
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,
gpointeruser_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
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1115653] Re: GNOME Printer Setup Tool: Printers are discovered only through a hard-coded list of CUPS backends
** Changed in: gnome-control-center
Status: New => 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:
Triaged
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,
gpointeruser_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
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1115653] Re: GNOME Printer Setup Tool: Printers are discovered only through a hard-coded list of CUPS backends
(changing the milestone since we are past feature freeze, setting to
beta2)
** Changed in: gnome-control-center (Ubuntu)
Milestone: ubuntu-13.04-feature-freeze => ubuntu-13.04-beta-2
--
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:
New
Status in “gnome-control-center” package in Ubuntu:
Triaged
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,
gpointeruser_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
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1115653] Re: GNOME Printer Setup Tool: Printers are discovered only through a hard-coded list of CUPS backends
** Changed in: gnome-control-center
Status: Unknown => New
** Changed in: gnome-control-center
Importance: Unknown => High
--
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:
New
Status in “gnome-control-center” package in Ubuntu:
Triaged
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,
gpointeruser_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
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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: New => Triaged
--
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:
Unknown
Status in “gnome-control-center” package in Ubuntu:
Triaged
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,
gpointeruser_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
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1115653] Re: GNOME Printer Setup Tool: Printers are discovered only through a hard-coded list of CUPS backends
** Bug watch added: GNOME Bug Tracker #693182
https://bugzilla.gnome.org/show_bug.cgi?id=693182
** Also affects: gnome-control-center via
https://bugzilla.gnome.org/show_bug.cgi?id=693182
Importance: Unknown
Status: Unknown
--
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:
Unknown
Status in “gnome-control-center” package in Ubuntu:
Triaged
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,
gpointeruser_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
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1115653] Re: GNOME Printer Setup Tool: Printers are discovered only through a hard-coded list of CUPS backends
This is a regression compared to Quantal. There system-config-printer
was used which did it correctly.
--
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” package in Ubuntu:
New
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,
gpointeruser_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/ubuntu/+source/gnome-control-center/+bug/1115653/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
