On 2017-03-08 01:44, stakanov wrote:

So, the situation was: a machine with existing home. A fresh install of 41.1 without using / installing any printer. An update with zypper dup (and only the standard opensuse repos of 42 activated and without having packman installed).

Ok.

That leads to a perfectly installed and working 42.2. But when you will try to install a printer (at least me) you get a surprise: The printer e.g. attached to usb is seen in lsusb. Is seen in CUPS (localhost:631 in the browser) and is seen in yast as expected. But listing the filters / printer drivers gives an entirely empty window.

Window? In what app?

So I did read through howtos and wikis and found a note about cups-browsing: with this updated system cups.browsing service is deactivated and not running. I found in the release notes the following: "The network printer discovery protocol has changed. The native method to discover network printers is now based on DNS Service discovery (DNS-SD, that is, via Avahi). The cups-browsed service from the cups-filters package can be used to bridge old and new protocols. Both cupsd and cups-browsed need to run to make "legacy" clients discover printers (that includes LibreOffice and KDE)."

Ah... rings a bell.

That is great information...only that I do not understand it. Does this mean: for discovering and registering the filter driver cups-browsing has to run always? Or can it be deactivated once the filter / printer is registered?

I think that once the printer is registered cups-browsed is not required. Unless there is a capability to find a printer that changes IP day to day via dhcp. Where I am I don't have a printer, so I can't test.

DNS-SD is the same as DNS-m? I ask this, because before finding the trick with usb I tried to find the printer on the network. DNS-m was activated in the printer, IP was in the same subnet. Still Leap did not see any printer (firewall was stopped too). Now the printer Lexmark C543 is using postscript. Does this mean that in order to work out of the box, a network or otherwise printer has to be DNS-SD and PDF native compatible otherwise it is not seen anyway? Even if the printer offers DNS-m?

No, I don't think the printer needs to be pdf capable. Mine is not. However, my network printer was never seen: I had to configure in YaST telling it the IP to test. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

In data mercoledì 8 marzo 2017 02:47:51, Carlos E. R. ha scritto:

Both cupsd and cups-browsed need to run

...

to make "legacy" clients discover printers (that includes LibreOffice and KDE)." This is my fear that: if I deactivate cups-browsing have problems printing with these. But I feel that the release notes are not very clear (to say the minor) about the implications that will have on printer recognition and about how it manifests. Easiest may be: "yast may fail to present any printer driver. In this case please activate CUPS-browsing" in yast-services".

Cheers. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

In data martedì 7 marzo 2017 23:22:04, Patrick Shanahan ha scritto:

* stakanov [03-07-17 19:46]:

...

In data martedì 7 marzo 2017 21:22:19, Carlos E. R. ha scritto:

...

On 2017-03-07 19:59, stakanov wrote:

...

I tried already to reinstall all cups related packages but nothing changes. BTW during the update must have been something "forgotten" because when I go on download.opensuse.org then the driver proposed is for 42.1 not for 42.2.

You have to configure the search so that it defaults to search for your release.

So, the situation was: a machine with existing home. A fresh install of 41.1 without using / installing any printer. An update with zypper dup (and only the standard opensuse repos of 42 activated and without having packman installed). That leads to a perfectly installed and working 42.2. But when you will try to install a printer (at least me) you get a surprise: The printer e.g. attached to usb is seen in lsusb. Is seen in CUPS (localhost:631 in the browser) and is seen in yast as expected. But listing the filters / printer drivers gives an entirely empty window. So I did read through howtos and wikis and found a note about cups-browsing: with this updated system cups.browsing service is deactivated and not running. I found in the release notes the following: "The network printer discovery protocol has changed. The native method to discover network printers is now based on DNS Service discovery (DNS-SD, that is, via Avahi). The cups-browsed service from the cups-filters package can be used to bridge old and new protocols. Both cupsd and cups-browsed need to run to make "legacy" clients discover printers (that includes LibreOffice and KDE)."

do you have: cups-filters cups-filters-cups-browsed cups-filters-ghostscript cups-filters-foomatic-rip

packman is not necessary/relevant for printer support

...

That is great information...only that I do not understand it. Does this mean: for discovering and registering the filter driver cups-browsing has to run always? Or can it be deactivated once the filter / printer is registered? DNS-SD is the same as DNS-m? I ask this, because before finding the trick with usb I tried to find the printer on the network. DNS-m was activated in the printer, IP was in the same subnet. Still Leap did not see any printer (firewall was stopped too). Now the printer Lexmark C543 is using postscript. Does this mean that in order to work out of the box, a network or otherwise printer has to be DNS-SD and PDF native compatible otherwise it is not seen anyway? Even if the printer offers DNS-m?

With this latest change I am really lost.

yast2 -> hardware -> printers "find and assign a driver" "search for" Lexmark C543 provides: Lexmark C543 [OpenPrintingPPDs/postscript/Lexmark-C543.Postscript-Lexmark.ppd.gz] Lexmark C543 Foomatic/Postscript [OpenPrintingPPDs/postscript/Lexmark-C543.Postscript.ppd.gz]

and I do not have a "Lexmark C543" printer.

With cups-browsed installed (and all the other packages) what happens is that with the update (which may be a situation that people encounter, it is not so rare that you begin and do not have a printer, do an update and then you decide to attach that printer, you have cups-browsed installed but it is not running but deactivated by default. Which is odd, how many laserprinter have pdf 1.7 emulation. I went to a sellers webpage and searched actively: brother, lexmark, all have but(!) only the higher models. A lot of what is out there still is a) convenient - because not brand new and b) does have postscript by default. So in my view, at least a popup in yast (where I did do my trials) would not be bad. I did read at the time the release notes, so that is why I recalled "something with cups....." but that after a while - it is like when you "recall" that your mobile phone might be again in the fridge.... :-( So, at the end I "discovered" the printer over usb. But before it was over the LAN, correctly set IP, activated DNS-m (this is a venerable office printer that is so attractive because of his low cost, well working, "after-market" toner cartriges. So 3+1 toners cost now as 1 black of the originals... you may understand my nostalgic views) and with AVAHI running and asking discover....he did not see anything. Maybe you have to run discover of "all network server / printers" in yast differently. Firewall: as I wanted to minimize factors, the firewall was down. CUPS: cups interface on 631 did(!) see the printer...but did give me: SUCCESS - printer driver not found (while it was there). Which is some way funny if you think. Well, I have in the end the doubt that for a postscript printer without integrated pdf integration you have to run forcefully the CUPS-browsing thing, even if (like in this case) I have DNS-m over LAN. And in all cases, printer discovery over LAN has to be either fixed in YAST, either set-up differently. The printer discover up to leap was the most userfriendly thing I can remember in opensuse. It becomes tedious, so I immagine it could become a source of constant irritation. Mainly because of missing info and of generational change of devices. Curretly all works as expected after the change to USB (also double sided printing) but I would be enjoying to have it run also over the LAN (in case I wish to put the printer in another location and for other devices). Thank you for having answered. I appreciate. BTW. There is an existential question that is in my heard since some time. I have both: the foomatic and the gutenprint driver. Is there a difference and why we have two projects for filters? Does anybody know by chance? Currently I am running foomatic. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* stakanov [03-08-17 03:36]:

In data martedì 7 marzo 2017 23:22:04, Patrick Shanahan ha scritto: [...] With cups-browsed installed (and all the other packages) what happens is that with the update (which may be a situation that people encounter, it is not so rare that you begin and do not have a printer, do an update and then you decide to attach that printer, you have cups-browsed installed but it is not running but deactivated by default. Which is odd, how many laserprinter have pdf 1.7 emulation. I went to a sellers webpage and searched actively: brother, lexmark, all have but(!) only the higher models. A lot of what is out there still is a) convenient - because not brand new and b) does have postscript by default. So in my view, at least a popup in yast (where I did do my trials) would not be bad. I did read at the time the release notes, so that is why I recalled "something with cups....." but that after a while - it is like when you "recall" that your mobile phone might be again in the fridge.... :-(

So, at the end I "discovered" the printer over usb. But before it was over the LAN, correctly set IP, activated DNS-m (this is a venerable office printer that is so attractive because of his low cost, well working, "after-market" toner cartriges. So 3+1 toners cost now as 1 black of the originals... you may understand my nostalgic views) and with AVAHI running and asking discover....he did not see anything. Maybe you have to run discover of "all network server / printers" in yast differently. Firewall: as I wanted to minimize factors, the firewall was down. CUPS: cups interface on 631 did(!) see the printer...but did give me: SUCCESS - printer driver not found (while it was there). Which is some way funny if you think.

Well, I have in the end the doubt that for a postscript printer without integrated pdf integration you have to run forcefully the CUPS-browsing thing, even if (like in this case) I have DNS-m over LAN. And in all cases, printer discovery over LAN has to be either fixed in YAST, either set-up differently. The printer discover up to leap was the most userfriendly thing I can remember in opensuse. It becomes tedious, so I immagine it could become a source of constant irritation. Mainly because of missing info and of generational change of devices. Curretly all works as expected after the change to USB (also double sided printing) but I would be enjoying to have it run also over the LAN (in case I wish to put the printer in another location and for other devices).

Thank you for having answered. I appreciate.

if/when you switch back from usb to lan, it should be a simple matter to discover the lan address of the printer and give that to yast after searching for and configuring the "Lexmark C543" printer.

BTW. There is an existential question that is in my heard since some time. I have both: the foomatic and the gutenprint driver. Is there a difference and why we have two projects for filters? Does anybody know by chance? Currently I am running foomatic.

I presently have and tend to perfer hp printers and utilize their hplip provided drivers. hp presently printer wise is very linux friendly and I find easy to work with. In the past I tended to utilize foomatic as istr it was recommended first, but memory fades in my age and it has been some time since I used a non hp printer. there is a site I used to frequent when needing information about configuring a printer, https://wiki.linuxfoundation.org/openprinting/start it provides a wealth of information and recommendations. your printer: http://www.openprinting.org/printer/Lexmark/Lexmark-C543 ftr: I have to provide the lan address to configure the hplip software but it is a simple thing. the printer itself advertises its ip address. all in all, I feel you are getting too deeply into this, a simple thing. I understand how we get started too specifically into a direction and have a problem off-times seeing the solution. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

In data mercoledì 8 marzo 2017 08:52:19, jdd ha scritto:

Le 08/03/2017 à 01:44, stakanov a écrit :

...

So, the situation was: a machine with existing home. A fresh install of 41.1 without using / installing any printer. An update with zypper dup (and only the standard opensuse repos of 42 activated and without having packman installed).

same for me (with packman, what should not be relevant here)

...

(localhost:631 in the browser) and is seen in yast as expected. But listing the filters / printer drivers gives an entirely empty window.

in cups, for me, managing the printers gives a full list of drivers

I in long time past read that yast printer module is no more maintained, and I know it to be desperately slow, so I use plain cups web interface (like you)

I also remember than Susefirewall2 gives problem discovering network printers, but that should neither be your problem

on my 42.2, the cups daemon is running, but nothing else cups related afaik

jdd The watershed seems to be that availability of integrated pdf 1.7 emulation. If your printer has it: works. If it does only postscript (as a lot of older network printer) it does not without "cups-browsing"). So if you have a historical system from 13.2 updated, it will work because the filter is already installed. But if you do install from scratch (or at least from 42.1 updating to 42.2 then you run into it. FYI: in TW I did not encounter this problem. I think their Yast module and system charges "cups-browsing" by default. Everything there worked out of the box.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org