Avahi is an implementation of the auto-discovery protocol and required for ipptool.
For automatic discovery, you need an extra component from CUPS called cups-browsed, which queries the Avahi daemon and then populates CUPS configuration based on what the Avahi daemon sees.
# driverless list
DEBUG: Started ippfind (PID 4137)
DEBUG: Started post-processing (PID 4138)
ERROR: Unable to execute ippfind utility: No such file or directory
DEBUG: PID 4137 (ippfind) stopped with status 1!
DEBUG: PID 4138 (Post-processing) exited with no errors.
Because I do not see the point in it - a lot of dependencies, bugs, does not see network printers through samba since there is no support of avahi and dnssd in the cups package.
The same things we can to do in Manage Printing = CUPS Web Interface
and for scanning printers in the local network we can use this command
and copy to Manage Printing = CUPS Web Interface > to the connection field via smb
Any suggestion are welcome (who are the pros and cons)
Printing and scanning for Porteus
Posted: 03 Sep 2019, 01:01
by Ed_P
09-02 working in rc1 AF mode with HP network printer.
Printing and scanning for Porteus
Posted: 03 Sep 2019, 05:57
by Blaze
Ed_P, what is protocol do you apply for HP network printer (socket or samba)? With socket all works fine, but with samba - no.
I have Windows print server (for e.g. PC called by OKSANA) and when I try to seach this printer from my Porteus-PC via Samba (not a socket) - this printer does not found for me automatically.
With samba is faile:
<<< Windows print server (PC called by OKSANA) - Printer not found at the specified address
<<< if press the 'Browse ...' button - it will show nothing to you.
but if I manually type the path that I got from smbtree with %20 all works fine (look at my previous post).
smbclient -N -L 10.3.0.141
Sharename Type Comment
--------- ---- -------
Canon iR2422 UFRII LT Printer Canon iR2422 UFRII LT
D Disk
IPC$ IPC Удаленный IPC
print$ Disk Драйверы принтеров
Users Disk
Reconnecting with SMB1 for workgroup listing.
do_connect: Connection to 10.3.0.141 failed (Error NT_STATUS_RESOURCE_NAME_NOT_FOUND)
Unable to connect with SMB1 -- no workgroup available
For printer (Windows PC too) shared via samba is the same:
guest@porteus:~$ smbtree
WORKGROUP
\\LINKSYS08419 Samba 3.0.28a
\\LINKSYS08419\IPC$ IPC Service (Samba 3.0.37-(Optimized by Tuxera Inc, 3015.11.5.2_1))
guest@porteus:~$ smbclient -N -L 192.168.200.190
Server does not support EXTENDED_SECURITY but 'client use spnego = yes' and 'client ntlmv2 auth = yes' is set
Anonymous login successful
Sharename Type Comment
--------- ---- -------
IPC$ IPC
MEMORY_CARD Disk FLASH MEMORY PHOTO
Reconnecting with SMB1 for workgroup listing.
Server does not support EXTENDED_SECURITY but 'client use spnego = yes' and 'client ntlmv2 auth = yes' is set
Anonymous login successful
Server Comment
--------- -------
Workgroup Master
--------- -------
guest@porteus:~$
Printing and scanning for Porteus
Posted: 03 Sep 2019, 16:51
by Blaze
Ed_P, seems Porteus 4.0 is use old version of samba - you can check this via command
guest@porteus:~$ smbtree
Unable to initialize messaging context
Enter WORKGROUP\guest's password:
WORKGROUP
\\LINKSYS08419 Samba 3.0.28a
\\LINKSYS08419\IPC$ IPC Service (Samba 3.0.37-(Optimized by Tuxera Inc, 3015.11.5.2_1))
guest@porteus:~$ smbclient -N -L 192.168.200.190
Unable to initialize messaging context
Server does not support EXTENDED_SECURITY but 'client use spnego = yes' and 'client ntlmv2 auth = yes' is set
Anonymous login successful
Sharename Type Comment
--------- ---- -------
IPC$ IPC
MEMORY_CARD Disk FLASH MEMORY PHOTO
Reconnecting with SMB1 for workgroup listing.
Server does not support EXTENDED_SECURITY but 'client use spnego = yes' and 'client ntlmv2 auth = yes' is set
Anonymous login successful
Server Comment
--------- -------
Workgroup Master
--------- -------
guest@porteus:~$ smbd -V
bash: smbd: command not found
guest@porteus:~$
guest@porteus:~$ smbd -V
bash: smbd: command not found
guest@porteus:~$ su
Password:
root@porteus:/home/guest# smbd -V
Version 4.10.4
root@porteus:/home/guest#
SMB1 is disabled by default
---------------------------
The defaults of 'client min protocol' and 'server min protocol'
have been changed to SMB2_02.
This means clients without support for SMB2 or SMB3 are no longer
able to connect to smbd (by default).
It also means client tools like smbclient and other,
as well as applications making use of libsmbclient are no longer
able to connect to servers without SMB2 or SMB3 support (by default).
It's still possible to allow SMB1 dialects, e.g. NT1, LANMAN2
and LANMAN1 for client and server, as well as CORE and COREPLUS on
the client.
Note that most commandline tools e.g. smbclient, smbcacls and others
also support the '--option' argument to overwrite smb.conf options,
e.g. --option='client min protocol=NT1' might be useful.
As Microsoft no longer installs SMB1 support in recent releases
or uninstalls it after 30 days without usage, the Samba Team
tries to get remove the SMB1 usage as much as possible.
SMB1 is officially deprecated and might be removed step by step
in the following years. If you have a strong requirement for SMB1
(except for supporting old Linux Kernels), please file a bug
at https://bugzilla.samba.org and let us know about the details.
# Openbox
[-] babl
[-] libgusb
[-] colord
[+] pygobject3 (Note. pygobject3 will be included in the 002-xorg base)
[+] gobject-introspection (Note. gobject-introspection will be included in the 002-xorg base)
[-] json-glib (Note. json-glib will be included in the Openbox base)
# MATE
[+] babl
[-] libgusb
[-] colord
[+] pygobject3 (Note. pygobject3 will be included in the 002-xorg base)
[+] gobject-introspection (Note. gobject-introspection will be included in the 002-xorg base)
[-] json-glib (Note. json-glib will be included in the MATE base)
# XFCE
[-] babl
[-] libgusb
[-] colord
[-] pygobject3 (Note. pygobject3 will be included in the 002-xorg base)
[-] gobject-introspection (Note. gobject-introspection will be included in the 002-xorg base)
[+] json-glib
# LXQT
[-] babl
[-] libgusb
[-] colord
[-] pygobject3 (Note. pygobject3 will be included in the 002-xorg base)
[-] gobject-introspection (Note. gobject-introspection will be included in the 002-xorg base)
[+] json-glib
# LXDE
[-] babl
[-] libgusb
[-] colord
[-] pygobject3 (Note. pygobject3 will be included in the 002-xorg base)
[-] gobject-introspection (Note. gobject-introspection will be included in the 002-xorg base)
[-] json-glib (Note. json-glib will be included in the LXDE base)
# KDE5
[-] babl
[-] libgusb
[-] colord
[-] pygobject3 (Note. pygobject3 will be included in the 002-xorg base)
[-] gobject-introspection (Note. gobject-introspection will be included in the 002-xorg base)
[-] json-glib
ls -1 /var/lib/pkgtools/packages/{*babl*,*libgusb*,*colord*,*pygobject3*,*python3*,*gobject-introspection*,*json-glib*}
Printing and scanning for Porteus
Posted: 13 May 2020, 19:36
by jano
In my Canon MF4140:
Porteus 4 x86-64 Mate (with the drivers from 21 April 2018)
* Simple Scan & XSane do work
* ScanGear MP & ImageScan don't work
Porteus 5rc1 x86-64 Mate (with the drivers from 09 Nov 2019
* Document Scanner & XSane do work
* ScanGear MP doesn't start (from the menu, at least), and
* ImageScan also doesn't work: when started from the menu, opens a windows with the message "Could not send command scanner. Check the scanner status.", while if started from the terminal gives the message (iscan:3124): Gtk-WARNING **: 19:30:03.248: Unable to locate theme engine in module_path: "murrine" several time and then the window.
Printing and scanning for Porteus
Posted: 14 May 2020, 17:03
by Blaze
jano, thanks for the report.
ScanGear MP, ImageScan and XSane (no GTK3 support) is removed in current version.
Printing and scanning for Porteus
Posted: 05 Oct 2021, 05:26
by Jack
Which printers has the best support? And what brands or type?
[*] Slackware printing and scanning packages updated to Slackware 15.0 base 2023-02-04
[*] some packages compiled from source via SBo (dropped/replaced some packages from others distro, such as ALT Linux, Mageia, etc...)
[*] removed a couple of stuff =) and the size of 07-printing module now is some smaller.
For example 07-printing-x86_64-2022-07-02.xzm vs 07-printing-x86_64-2023-02-04.xzm
# 92 Mb vs 87.6 Mb
ls -1 /var/lib/pkgtools/packages/{*babl*,*colord*,*json-glib*,*libgusb*,*python-certifi*,*python-chardet*,*python-idna*,*python-requests*,*python-urllib3*}