[Expired for cups (Ubuntu) because there has been no activity for 60
days.]
** Changed in: cups (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Have you, after starting CUPS again, completely closed and restarted the
app (Firefox and Okular)? Die you try to restart the desktop (log out
and log in again)? Or the system (reboot)? Does this make the printers
appear again? Also note that DNS-Sd sometimes can have some delay.
CUPS never reads
Made the quick check you suggested. Switching off cups, all printers
disappear both in okular (QT) and firefox. So it looks like the
driverless network printers come from cups.
Weird enough now after the switch off - switch on sequence for cups, I
do not have the driverless printers them in
@Till
Thanks! This is a great explanation. I am sure that it took you some
time to write it in this clear way and I would like to let you know that
I really appreciate it. Things look a bit clearer to me right now.
I am looking forward to seeing method (4) materialize as the current
situation
There are different methods for auto-discovering driverless IPP network
printers.
First, all these printers advertise themselves via DNS-SD, so that
clients (computers, phones, TVs, ...) find them. The first step which
then happens in your computer is that avahi-daemon picks up the
printer's
And I think that the conclusion is the following:
- The KDE print dialog bypasses cups-browsed to list the driverless
network printers, if cups-browsed is not running. In this case it fails
to gather some information such as the "type" of the printer, though.
- For the KDE print dialog not to
One weird phenomenon is that
- if cups-browsed is active, the okular print dialog shows the
driverless printers and indicates their type as driverless
- if cups-browsed is not active, the okular print dialog shows the
driverless printers but fails to indicate their type (type is empty).
--
You
One weird phenomenon is that
- if cups-browsed is active, the okular print dialog shows the
driverless printers and indicates their type as driverless
- if cups-browsed is not active, the okular print dialog shows the
driverless printers but fails to indicate their type (type is empty).
--
You
1) cups-browsed does not appear in ps auxwww
2/3) The driverless printers appear in the print dialog of okular
4) avahi-browse -v -t -r --all returns tons of printers in forms such as
= eth0 IPv4 Lexmark MS610dn _ipps._tcp
local
hostname =
My printing almost always happens from okular which uses a QT print
dialog.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1738432
Title:
Regression, poor user experience,
You were very clear in your first message that cups-browsed had been
stopped. I can think of a reason for your observations (and why
disabling avahi-daemon is a way of not seeing network discoverd
printers) but it depends on what applications you are using. This is why
I was interested in the
Thanks for the clarification in the last answer, that is helpful for me
to find out which ones among the many attempts I made to disable the
display of the driverless entries eventually worked (since it could be
nice for me to script enabling/disabling actions to place into some
network
I do not know if I am allowed to publish details of my company intranet
that I expect to be collected with the avahi-browse or the lpstat -v.
I'll try to find out first. In any case, I'll try to provide what I can
when I am again at the office with the newer printers appearing as
driverless
> Don't know what I did, but finally I have succeeded disabling the display of
> the driverless
> network printers.
Till asked for six pieces of information. Answers would be appreciated.
> Can it be the case that you need /both/ the process stopped /and/ the
> BrowseRemoteProtocols in
> its
Don't know what I did, but finally I have succeeded disabling the
display of the driverless network printers.
Right before systemd reported cups-browsed as stopped.
Can it be the case that you need /both/ the process stopped /and/ the
BrowseRemoteProtocols in its conf file set to none /at the
Do you actually have no cups-browsed process running at all?
In which print dialogs do the driverless extra printers appear? Of which
applications?
Please also run the commands
avahi-browse -v -t -r --all
lpstat -e
lpstat -v
and post the output here.
** Changed in: cups (Ubuntu)
16 matches
Mail list logo
