I've freshly installed Fedora 27 on two machines; neither have a printer directly connected, but rely on cups-browsed to display the LAN's printers that are attached to, and managed by other (F26) machines.
Not any more. cups-browsed seems to have lost its ability to detect automatically those network printers. Is anyone else seeing this? Or have I screwed up, somehow?
For earlier Fedoras I've edited /etc/cups/cups-browsed.conf to add: BrowseAllow 192.168.2.0/24 to restrict browsing to my LAN, but now there's a comment # If there are no "Browse..." lines at all, all servers are accepted. so that edit shouldn't be necessary. I've tried with and without it, but F27 browsing still fails.
In the system-config-printer GUI I can still click thru a bunch of steps to search for and find those network printers. And then use them. But that's tedious and much less useful than the previous totally automatic availability of all printers across the LAN.
Is this a regression?
On Fri, Nov 24, 2017 at 2:03 PM, David A. De Graaf dad@datix.us wrote:
I've freshly installed Fedora 27 on two machines; neither have a printer directly connected, but rely on cups-browsed to display the LAN's printers that are attached to, and managed by other (F26) machines.
Not any more. cups-browsed seems to have lost its ability to detect automatically those network printers. Is anyone else seeing this? Or have I screwed up, somehow?
For earlier Fedoras I've edited /etc/cups/cups-browsed.conf to add: BrowseAllow 192.168.2.0/24 to restrict browsing to my LAN, but now there's a comment # If there are no "Browse..." lines at all, all servers are accepted. so that edit shouldn't be necessary. I've tried with and without it, but F27 browsing still fails.
In the system-config-printer GUI I can still click thru a bunch of steps to search for and find those network printers. And then use them. But that's tedious and much less useful than the previous totally automatic availability of all printers across the LAN.
Is this a regression?
Definitely a bug of some sort. I'm in a similar situation. It does find the printer but says something about it's unable to print to it. I can add one manually via wifi and I can print to it but when I try to make it as default it always "unchecks" itself. The screen hinda flashes like a refresh. Something weird going on for sure.
Glad it's not just me.
Thanks, Richard
Allegedly, on or about 24 November 2017, David A. De Graaf sent:
I've freshly installed Fedora 27 on two machines; neither have a printer directly connected, but rely on cups-browsed to display the LAN's printers that are attached to, and managed by other (F26) machines.
Not any more. cups-browsed seems to have lost its ability to detect automatically those network printers.
Do you also have the Avahi/zero-conf stuff running? It seems to depend on that nonsense, too, these days.
On Fri, Nov 24, 2017 at 2:03 PM, David A. De Graaf dad@datix.us wrote:
I've freshly installed Fedora 27 on two machines; neither have a printer directly connected, but rely on cups-browsed to display the LAN's printers that are attached to, and managed by other (F26) machines.
Not any more. cups-browsed seems to have lost its ability to detect automatically those network printers. Is anyone else seeing this? Or have I screwed up, somehow?
I installed dnf-plugin-versionlock and then did:
# dnf --releasever=26 downgrade cups # dnf versionlock cups-2.2.2
So far so good so I think I'll stick with this until all my machines are upgraded at least.
Thanks, Richard
On 11/25/17 11:20, Richard Shaw wrote:
On Fri, Nov 24, 2017 at 2:03 PM, David A. De Graaf <dad@datix.us mailto:dad@datix.us> wrote:
I've freshly installed Fedora 27 on two machines; neither have a printer directly connected, but rely on cups-browsed to display the LAN's printers that are attached to, and managed by other (F26) machines. Not any more. cups-browsed seems to have lost its ability to detect automatically those network printers. Is anyone else seeing this? Or have I screwed up, somehow?I installed dnf-plugin-versionlock and then did:
# dnf --releasever=26 downgrade cups # dnf versionlock cups-2.2.2
So far so good so I think I'll stick with this until all my machines are upgraded at least.
Richard: Did that actually work for you? Ie, does cups-browsed now show your LAN printers? Because it didn't for me.
The downgrading step did downgrade five cups packages, but not cups-filters, which is the source of /usr/sbin/cups-browsed. When I tried to downgrade it also, dnf wanted to downgrade 381 packages including the libreoffice collection, x2go-server, vim and a slew of perl items. That seemed too extreme. So cups-browsed remains broken for me.
Time to visit bugzilla, I think.
On 11/25/17 14:18, David A. De Graaf wrote:
On 11/25/17 11:20, Richard Shaw wrote:
On Fri, Nov 24, 2017 at 2:03 PM, David A. De Graaf <dad@datix.us mailto:dad@datix.us> wrote:
I've freshly installed Fedora 27 on two machines; neither have a printer directly connected, but rely on cups-browsed to display the LAN's printers that are attached to, and managed by other (F26) machines. Not any more. cups-browsed seems to have lost its ability to detect automatically those network printers. Is anyone else seeing this? Or have I screwed up, somehow?I installed dnf-plugin-versionlock and then did:
# dnf --releasever=26 downgrade cups # dnf versionlock cups-2.2.2
So far so good so I think I'll stick with this until all my machines are upgraded at least.
Time to visit bugzilla, I think.
*It's not much, but here it is: * https://bugzilla.redhat.com/show_bug.cgi?id=1518415
*Bug 1518415* https://bugzilla.redhat.com/show_bug.cgi?id=1518415 -cups-browsed has stopped working in F27