[opensuse-factory] Cups behaviour in actual TW
Hi, I have to admit that I'm not printing that much...so the issue may already be older In current TW there is CUPS 2.2.3 installed. I originally had only one network printer (Queue: MFC9340CDW) defined, using a lpd connection to lpd:// 192.168.1.103/binary_p1 Works properly. Now a second printer shows up - same device, different name (Brother_MFC_9340CDW) connecting to ipp://BRW3C77E658BC0F.local:631/ipp/print This one is probably auto-detected, but not working properly (test page is empty) To make things worse, when printing from KDE, KDE print dialog shows a third Queue "Brother MFC-9340CDW", which is working neither. From the KDE-system settings, only the two queues are shown that are in Cups as well How can I switch the auto-detection off? Does it make sense to change the default setting in TW-Distro? Thanks Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On dimanche, 1 octobre 2017 19.37:11 h CEST Axel Braun wrote:
Hi, I have to admit that I'm not printing that much...so the issue may already be older
In current TW there is CUPS 2.2.3 installed. I originally had only one network printer (Queue: MFC9340CDW) defined, using a lpd connection to lpd:// 192.168.1.103/binary_p1 Works properly.
Now a second printer shows up - same device, different name (Brother_MFC_9340CDW) connecting to ipp://BRW3C77E658BC0F.local:631/ipp/print This one is probably auto-detected, but not working properly (test page is empty)
To make things worse, when printing from KDE, KDE print dialog shows a third Queue "Brother MFC-9340CDW", which is working neither. From the KDE-system settings, only the two queues are shown that are in Cups as well
How can I switch the auto-detection off? Does it make sense to change the default setting in TW-Distro?
Thanks Axel
I can also confirm this strange behaviour under plasma All my printing goes to my print server which export 2 printers. I have both of them visible, but now cups insist to recreate that printer ipp://bla.local:631/ipp/port1 Model Local Raw Printer Status Paused So basically can't serve anything useful. It setup as default printer, and thus any software that want to print take long time to show the print dialog box. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bruno Friedmann wrote:
On dimanche, 1 octobre 2017 19.37:11 h CEST Axel Braun wrote:
Hi, I have to admit that I'm not printing that much...so the issue may already be older
In current TW there is CUPS 2.2.3 installed. I originally had only one network printer (Queue: MFC9340CDW) defined, using a lpd connection to lpd:// 192.168.1.103/binary_p1 Works properly.
Now a second printer shows up - same device, different name (Brother_MFC_9340CDW) connecting to ipp://BRW3C77E658BC0F.local:631/ipp/print This one is probably auto-detected, but not working properly (test page is empty)
I did have issues with my TW laptop for some time now, where I had to restart cups after a suspend-to-ram, else it wouldn't find my (remote) printers anymore.... I don't print that much either, so it was only a minor nuissance.
I can also confirm this strange behaviour under plasma All my printing goes to my print server which export 2 printers.
I have both of them visible, but now cups insist to recreate that printer ipp://bla.local:631/ipp/port1
Huh, so I restarted cups to check, and now instead of seeing the two printers my print server exports, samsung and samsung_color, I get an Samsung_CLP_620_Foomatic_pxlcolor_royac6_royac_iac_es WTF, do you want me to type this in an lpr command line!? Why does it suddenly create this stupid names? And why don't I get the two different printqueues that my server exports? This is ****** -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Peter Suetterlin wrote:
Huh, so I restarted cups to check, and now instead of seeing the two printers my print server exports, samsung and samsung_color, I get an Samsung_CLP_620_Foomatic_pxlcolor_royac6_royac_iac_es
Ah, new entry in the rpmnew config of cups-browsed, and a change of the old default... You now have to set LocalQueueNamingRemoteCUPS RemoteName -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/02/2017 08:04 AM, Bruno Friedmann wrote:
On dimanche, 1 octobre 2017 19.37:11 h CEST Axel Braun wrote:
Hi, I have to admit that I'm not printing that much...so the issue may already be older
In current TW there is CUPS 2.2.3 installed. I originally had only one network printer (Queue: MFC9340CDW) defined, using a lpd connection to lpd:// 192.168.1.103/binary_p1 Works properly.
Now a second printer shows up - same device, different name (Brother_MFC_9340CDW) connecting to ipp://BRW3C77E658BC0F.local:631/ipp/print This one is probably auto-detected, but not working properly (test page is empty)
To make things worse, when printing from KDE, KDE print dialog shows a third Queue "Brother MFC-9340CDW", which is working neither. From the KDE-system settings, only the two queues are shown that are in Cups as well
How can I switch the auto-detection off? Does it make sense to change the default setting in TW-Distro?
Thanks Axel
I can also confirm this strange behaviour under plasma All my printing goes to my print server which export 2 printers.
I have both of them visible, but now cups insist to recreate that printer ipp://bla.local:631/ipp/port1
Model Local Raw Printer Status Paused
So basically can't serve anything useful. It setup as default printer, and thus any software that want to print take long time to show the print dialog box.
If you do export QT_DISABLE_PRINTER_DISCOVERY=1 on konsole before running the KDE/Qt application that tries to print, it should disable the discovery and use the printer configuration as usual. You can of course also set QT_DISABLE_PRINTER_DISCOVERY=1 in /etc/environment or in ~/.profile to fix the option for all applications. Can you (both) try that and see if that fixes the problems? Greetings, -- Antonio Larrosa -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Montag, 2. Oktober 2017, 14:24:14 CEST schrieb Antonio Larrosa:
On 10/02/2017 08:04 AM, Bruno Friedmann wrote:
On dimanche, 1 octobre 2017 19.37:11 h CEST Axel Braun wrote:
Hi, I have to admit that I'm not printing that much...so the issue may already be older
In current TW there is CUPS 2.2.3 installed. I originally had only one network printer (Queue: MFC9340CDW) defined, using a lpd connection to lpd:// 192.168.1.103/binary_p1 Works properly.
Now a second printer shows up - same device, different name (Brother_MFC_9340CDW) connecting to ipp://BRW3C77E658BC0F.local:631/ipp/print This one is probably auto-detected, but not working properly (test page is empty)
To make things worse, when printing from KDE, KDE print dialog shows a third Queue "Brother MFC-9340CDW", which is working neither. From the KDE-system settings, only the two queues are shown that are in Cups as well
[...]
If you do export QT_DISABLE_PRINTER_DISCOVERY=1 on konsole before running the KDE/Qt application that tries to print, it should disable the discovery and use the printer configuration as usual.
You can of course also set QT_DISABLE_PRINTER_DISCOVERY=1 in /etc/environment or in ~/.profile to fix the option for all applications.
Can you (both) try that and see if that fixes the problems?
After logging off and on again, KDE print dialog now only shows the two queues as visible in cups. Maybe we make this a default setting? Thanks Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/02/2017 03:21 PM, Axel Braun wrote:
Am Montag, 2. Oktober 2017, 14:24:14 CEST schrieb Antonio Larrosa:
On 10/02/2017 08:04 AM, Bruno Friedmann wrote: If you do export QT_DISABLE_PRINTER_DISCOVERY=1 on konsole before running the KDE/Qt application that tries to print, it should disable the discovery and use the printer configuration as usual.
You can of course also set QT_DISABLE_PRINTER_DISCOVERY=1 in /etc/environment or in ~/.profile to fix the option for all applications.
Can you (both) try that and see if that fixes the problems?
After logging off and on again, KDE print dialog now only shows the two queues as visible in cups.
Maybe we make this a default setting?
If we can't find a better solution, I guess that could be an option. But I'd prefer to fix it properly so the discovered printer can be used automatically. Just to know better your configuration... you only have one computer (no cups print server, just cups configured on the same computer) with one printer (brother MFC-9340CDW) connected by wifi, BRW3C77E658BC0F.local resolves as 192.168.1.103 and you only configured the lpd connection in your local cups, right? Can you send me your local cups configuration (/etc/cups/*.conf) and the output of running "avahi-browse -art" ? (directly if you prefer, so we don't spam the list) . Note you might have to install avahi-utils if you don't have it, since avahi-browse is included there. Thanks, -- Antonio Larrosa -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Antonio Larrosa -
Axel Braun -
Bruno Friedmann -
Peter Suetterlin