Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #256848 > unrolled thread

cups not sharing printers with other bullseye machines

Back to article view | Back to linux.debian.user

Contents

  cups not sharing printers with other bullseye machines gene heskett <gheskett@shentel.net> - 2023-04-08 04:30 +0200
    Re: cups not sharing printers with other bullseye machines "Gareth Evans" <donotspam@fastmail.fm> - 2023-04-08 08:50 +0200
      Re: cups not sharing printers with other bullseye machines gene heskett <gheskett@shentel.net> - 2023-04-08 18:50 +0200
      Re: cups not sharing printers with other bullseye machines gene heskett <gheskett@shentel.net> - 2023-04-08 23:20 +0200
        Re: cups not sharing printers with other bullseye machines "Gareth Evans" <donotspam@fastmail.fm> - 2023-04-09 17:40 +0200

#256848 — cups not sharing printers with other bullseye machines

Greetings all;

Where do I turn on cups debugging so I'll see every bit of traffic 
addressed to cups from my local 192.168/xx.yy network?

The problem is: other buster machines on this local network can see and 
use the two brother printers just as if the printer was local to that 
buster machine.

But no bullseye, debian or armbian can see anything at 
localhost:631/printers except the search screen when there are no printers.

These printers are marked as shared in this bullseye machines /etc/cups 
files.

There's a new roadblock someplace, I've asked about before. I'd like to 
find it.

Buster machines can, other bullseye machines can't.

Thank you.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [next] | [standalone]

#256857

On Sat  8 Apr 2023, at 03:20, gene heskett <gheskett@shentel.net> wrote:
> Greetings all;
>
> Where do I turn on cups debugging so I'll see every bit of traffic 
> addressed to cups from my local 192.168/xx.yy network?
>
> The problem is: other buster machines on this local network can see and 
> use the two brother printers just as if the printer was local to that 
> buster machine.
>
> But no bullseye, debian or armbian can see anything at 
> localhost:631/printers except the search screen when there are no printers.
>
> These printers are marked as shared in this bullseye machines /etc/cups 
> files.
>
> There's a new roadblock someplace, I've asked about before. I'd like to 
> find it.
>
> Buster machines can, other bullseye machines can't.
>
> Thank you.
>
> Cheers, Gene Heskett.
> -- 
> "There are four boxes to be used in defense of liberty:
>   soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author, 1940)
> If we desire respect for the law, we must first make the law respectable.
>   - Louis D. Brandeis
> Genes Web page <http://geneslinuxbox.net:6309/>

Hi Gene,

Not sure if CUPS debugging may be helpful, see eg.

https://sysadminera.com/2020/09/10/linux-how-to-enable-and-capture-cups-debugging-logs/

But first, I seem to recall you removed avahi and cups-browsed from Bullseye machines.  Is that correct?  Do the Buster machines have either or both of those installed?

What are the exact models of the Brother printers "missing" from Bullseye systems?

Do other printers appear on Bullseye systems?  

Thanks,
Gareth

[toc] | [prev] | [next] | [standalone]

#256908

On 4/8/23 02:40, Gareth Evans wrote:
> On Sat  8 Apr 2023, at 03:20, gene heskett <gheskett@shentel.net> wrote:
>> Greetings all;
>>
>> Where do I turn on cups debugging so I'll see every bit of traffic
>> addressed to cups from my local 192.168/xx.yy network?
>>
>> The problem is: other buster machines on this local network can see and
>> use the two brother printers just as if the printer was local to that
>> buster machine.
>>
>> But no bullseye, debian or armbian can see anything at
>> localhost:631/printers except the search screen when there are no printers.
>>
>> These printers are marked as shared in this bullseye machines /etc/cups
>> files.
>>
>> There's a new roadblock someplace, I've asked about before. I'd like to
>> find it.
>>
>> Buster machines can, other bullseye machines can't.
>>
>> Thank you.
>>
>> Cheers, Gene Heskett.
>> -- 
>> "There are four boxes to be used in defense of liberty:
>>    soap, ballot, jury, and ammo. Please use in that order."
>> -Ed Howdershelt (Author, 1940)
>> If we desire respect for the law, we must first make the law respectable.
>>    - Louis D. Brandeis
>> Genes Web page <http://geneslinuxbox.net:6309/>
> 
> Hi Gene,
> 
> Not sure if CUPS debugging may be helpful, see eg.
> 
> https://sysadminera.com/2020/09/10/linux-how-to-enable-and-capture-cups-debugging-logs/

I'll look at this, thank you.

> But first, I seem to recall you removed avahi and cups-browsed from Bullseye machines.  Is that correct?  Do the Buster machines have either or both of those installed?

No for avahi, not sure about browsed. Yes cups-browsed is installed on 
the buster machines. 4 of my machines are still on buster because the 
changes in python3 aren't yet compatible with linuxcnc, which is those 
machines main application. Bookworm will I think fix that.

> What are the exact models of the Brother printers "missing" from Bullseye systems?

Brother MFC-J6920DW, Brother HL-L2320D_series.
The ink squirter 6920 is a total disaster when cups try's to drive it, 
cups does not acknowledge that it has 2 supply trays and a rear port for 
tabloid paper. Its a monster sized machine, scanner can do tabloid also. 
Let cups drive it, no color controls, and only paper it knows about is 
the 50 cents a sheet glossy photo stuff in the top tray. 300 sheets of 
decent duplex copy paper in the bottom tray is ignored.

In this case, printers not well supported by cups, but which work to 
their full capability's with brothers own linux drivers, which they 
supply for their users. But cups won't allow them to be used unless 
cups-browsed is removed from this machine, it overrides any attempt to 
use the brother drivers. so browsed has been removed from bullseye machines.

Avahi too, but for a different network wrecking reason, it insists on 
assigning your routing address to the non-existent 169.xxx.yy.yy thing. 
So your routing of 192.168 for your local network is out of scope. Most 
frustrating, can't even ping your router, 6 feet of cat6 away...

> Do other printers appear on Bullseye systems?
> 
No, its a blank screen with a search line for printers when printers 
menu is selected.
Just to confirm, I just put cups-browsed back on one of the armbian 
machines, localhost:631/printers is empty, rebooted it, still empty.
Also, the avahi bug has been fixed, it no longer overrides your attempt 
to set the local route, so both are running, I checked with htop, but no 
shared printers are seen.

> Thanks,
> Gareth
> 

Thank you Gareth, take care & stay well.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#256923

[Multipart message — attachments visible in raw view] — view raw

On 4/8/23 02:40, Gareth Evans wrote:
> On Sat  8 Apr 2023, at 03:20, gene heskett <gheskett@shentel.net> wrote:
>> Greetings all;
>>
>> Where do I turn on cups debugging so I'll see every bit of traffic
>> addressed to cups from my local 192.168/xx.yy network?
>>
>> The problem is: other buster machines on this local network can see and
>> use the two brother printers just as if the printer was local to that
>> buster machine.
>>
>> But no bullseye, debian or armbian can see anything at
>> localhost:631/printers except the search screen when there are no printers.
>>
>> These printers are marked as shared in this bullseye machines /etc/cups
>> files.
>>
>> There's a new roadblock someplace, I've asked about before. I'd like to
>> find it.
>>
>> Buster machines can, other bullseye machines can't.
>>
>> Thank you.
>>
>> Cheers, Gene Heskett.
>> -- 
>> "There are four boxes to be used in defense of liberty:
>>    soap, ballot, jury, and ammo. Please use in that order."
>> -Ed Howdershelt (Author, 1940)
>> If we desire respect for the law, we must first make the law respectable.
>>    - Louis D. Brandeis
>> Genes Web page <http://geneslinuxbox.net:6309/>
> 
> Hi Gene,
> 
> Not sure if CUPS debugging may be helpful, see eg.
> 
> https://sysadminera.com/2020/09/10/linux-how-to-enable-and-capture-cups-debugging-logs/
> 
The most intelligent output I can get from the error_log on one of the 
armbian bullseye machines is a garbled attempt to open a pipe (I think)
from that log a snippet is attached. Tail end of a cups restart. Looks 
like something in the name resolution is totally fubar to me.

But, I can send ff to the exact entry in client.conf, and it can see all 
the shared printers here on this machine. But cups on that machine can't.

> But first, I seem to recall you removed avahi and cups-browsed from Bullseye machines.  Is that correct?  Do the Buster machines have either or both of those installed?

avahi and cups-browsed have both been re-installed on that armbian machine.
And its networking continues to work thru a reboot, something I could 
not do at the original install.
Then I check this machines error_log which is flooded with thousands of 
lines of this from my attempts to get a printer list on the armbian machine:

E [08/Apr/2023:12:25:16 -0400] [Client 18] Returning IPP 
server-error-version-not-supported for CUPS-Get-Printers (no URI) from 
192.168.71.12.
E [08/Apr/2023:12:25:16 -0400] [Client 18] Returning IPP 
server-error-version-not-supported for CUPS-Get-Default (no URI) from 
192.168.71.12.
E [08/Apr/2023:12:25:16 -0400] [Client 18] Returning IPP 
server-error-version-not-supported for CUPS-Get-Printers (no URI) from 
192.168.71.12.
E [08/Apr/2023:12:25:16 -0400] [Client 18] Returning IPP 
server-error-version-not-supported for CUPS-Get-Default (no URI) from 
192.168.71.12.
E [08/Apr/2023:12:25:16 -0400] [Client 18] Returning IPP 
server-error-version-not-supported for CUPS-Get-Printers (no URI) from 
192.168.71.12.

So the armbian machine is trying, and its this machine that is rejecting 
its attempts.  That's progress ;o)>

Whats next?

Thanks Gareth, take care and stay well.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#256978

On Sat  8 Apr 2023, at 22:12, gene heskett <gheskett@shentel.net> wrote:
> On 4/8/23 02:40, Gareth Evans wrote:
>> On Sat  8 Apr 2023, at 03:20, gene heskett <gheskett@shentel.net> wrote:
>>> Greetings all;
>>>
>>> Where do I turn on cups debugging so I'll see every bit of traffic
>>> addressed to cups from my local 192.168/xx.yy network?
>>>
>>> The problem is: other buster machines on this local network can see and
>>> use the two brother printers just as if the printer was local to that
>>> buster machine.
>>>
>>> But no bullseye, debian or armbian can see anything at
>>> localhost:631/printers except the search screen when there are no printers.
>>>
>>> These printers are marked as shared in this bullseye machines /etc/cups
>>> files.
>>>
>>> There's a new roadblock someplace, I've asked about before. I'd like to
>>> find it.
>>>
>>> Buster machines can, other bullseye machines can't.
>>>
>>> Thank you.
>>>
>>> Cheers, Gene Heskett.
>>> -- 
>>> "There are four boxes to be used in defense of liberty:
>>>    soap, ballot, jury, and ammo. Please use in that order."
>>> -Ed Howdershelt (Author, 1940)
>>> If we desire respect for the law, we must first make the law respectable.
>>>    - Louis D. Brandeis
>>> Genes Web page <http://geneslinuxbox.net:6309/>
>> 
>> Hi Gene,
>> 
>> Not sure if CUPS debugging may be helpful, see eg.
>> 
>> https://sysadminera.com/2020/09/10/linux-how-to-enable-and-capture-cups-debugging-logs/
>> 
> The most intelligent output I can get from the error_log on one of the 
> armbian bullseye machines is a garbled attempt to open a pipe (I think)
> from that log a snippet is attached. Tail end of a cups restart. Looks 
> like something in the name resolution is totally fubar to me.
>
> But, I can send ff to the exact entry in client.conf, and it can see all 
> the shared printers here on this machine. But cups on that machine can't.
>
>> But first, I seem to recall you removed avahi and cups-browsed from Bullseye machines.  Is that correct?  Do the Buster machines have either or both of those installed?
>
> avahi and cups-browsed have both been re-installed on that armbian machine.
> And its networking continues to work thru a reboot, something I could 
> not do at the original install.
> Then I check this machines error_log which is flooded with thousands of 
> lines of this from my attempts to get a printer list on the armbian machine:
>
> E [08/Apr/2023:12:25:16 -0400] [Client 18] Returning IPP 
> server-error-version-not-supported for CUPS-Get-Printers (no URI) from 
> 192.168.71.12.
> E [08/Apr/2023:12:25:16 -0400] [Client 18] Returning IPP 
> server-error-version-not-supported for CUPS-Get-Default (no URI) from 
> 192.168.71.12.
> E [08/Apr/2023:12:25:16 -0400] [Client 18] Returning IPP 
> server-error-version-not-supported for CUPS-Get-Printers (no URI) from 
> 192.168.71.12.
> E [08/Apr/2023:12:25:16 -0400] [Client 18] Returning IPP 
> server-error-version-not-supported for CUPS-Get-Default (no URI) from 
> 192.168.71.12.
> E [08/Apr/2023:12:25:16 -0400] [Client 18] Returning IPP 
> server-error-version-not-supported for CUPS-Get-Printers (no URI) from 
> 192.168.71.12.
>
> So the armbian machine is trying, and its this machine that is rejecting 
> its attempts.  That's progress ;o)>
>
> Whats next?
>
> Thanks Gareth, take care and stay well.
>
> Cheers, Gene Heskett.
> -- 
> "There are four boxes to be used in defense of liberty:
>   soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author, 1940)
> If we desire respect for the law, we must first make the law respectable.
>   - Louis D. Brandeis
> Genes Web page <http://geneslinuxbox.net:6309/>
>
> Attachments:
> * cups-error-log

> server-error-version-not-supported for CUPS-Get-Printers (no URI) from 
> 192.168.71.12.

The only reference to this error I could find was this

https://bbs.archlinux.org/viewtopic.php?id=168485

which (a long time ago) seems to have been resolved by using matching cups versions.

I find my Brother MFC-L2740DW is only detected on Bullseye if both devices use the same wifi band (the printer supports only 2.4GHz).  I'm sure this was never a thing in Buster, but I may have switched bands at some point and forgotten about having done that.  I imagine it could conceivably be due to a dodgy ISP router firmware update too.  

Are either of the printers you want access to from Bullseye currently shared via Buster CUPS, or Bullseye CUPS, or just via own wifi?  

HL-L2320D seems to be USB-only.  MFCJ6920DW seems to support both airprint but this may be susceptible to the wifi band thing.

If shared via Buster CUPS, does Bullseye (with cups-browsed installed) fail to detect these queues?  

Is one or more firewalls involved?  Does it make any difference if this/these are temporarily disabled?

cups-browsed here doesn't interfere with Brother drivers, but only "applies" them to printers specifically added with those drivers selected.  As I can't reproduce the behaviour you report, are you by any chance expecting airprint/driverless printers already detected to use the Brother drivers after the drivers have been installed? 

I have a couple of hunches to test so I'm trying to set up a Buster VM with bridged networking so accessible from "outside".  The bridged networking part is proving more challenging than several sets of instructions would appear to indicate.  I think I shall abandon virt-manager and try qemu with -netdev tap or macvtap, but this will have to wait a couple of days.  If anyone can recommend approaches or good, up-to-date documentation, that would be appreciated.  

So I hope to be able to dig a bit further on this.

Best wishes,
Gareth

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web