Page 3 of 3

Printing and scanning for Porteus

Posted: 02 Sep 2019, 17:49
by Blaze
A new current version of 07-printing module Printing and scanning for Porteus (Пост Blaze #73426)

Code: Select all

Sun Sep  1 19:03:23 UTC 2019
ap/cups-2.3.0-x86_64-2.txz:  Rebuilt.
  Fixed manpages. Thanks to TurboBlaze.
  Quit renaming/symlinking binaries for LPRng compatibility.
ap/cups-filters-1.25.4-x86_64-1.txz:  Upgraded.
  Compiled against qpdf-9.0.0.
ap/qpdf-9.0.0-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
Ed_P, it's includes a new qpdf-9.0.0 and you can try with this version.

I removed x (execute) bit for /etc/rc.d/rc.cups-browsed by the reason https://packages.debian.org/en/sid/cups-browsed
but the main reason is cups for Slackware builds with this options https://mirror.slackbuilds.org/slackwar ... SlackBuild

Code: Select all

  --disable-pam \
  --disable-avahi \
  --disable-dnssd \
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.
if run this command you will get

Code: Select all

# 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.
If look at cups-2.2.12-alt2.x86_64.from AltLinux

Code: Select all

# ldd /home/guest/Загрузки/cups-2.2.12-alt2.x86_64/usr/bin/ippfind | grep -i found
	libavahi-common.so.3 => not found
	libavahi-client.so.3 => not found
ippfind requires avahi.

More info is here: @all,
My plan is to drop system-config-printer with all his dependencies and stay with
Manage Printing = CUPS Web Interface (only)
Print Settings = system-config-printer
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

Code: Select all

smbtree
for get host name and name of network printer, for example

Code: Select all

smb://BEN-DESKTOP/HP Color LaserJet CP1510 series PCL6
just need to replace spaces with %20

Code: Select all

smb://BEN-DESKTOP/HP%20Color%20LaserJet%20CP1510%20series%20PCL6
and copy to Manage Printing = CUPS Web Interface > to the connection field via smb

Any suggestion are welcome (who are the pros and cons) :Search:

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. :good:

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:
Image <<< Windows print server (PC called by OKSANA) - Printer not found at the specified address
Image <<< 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).

With socket all ok:
Image

Image

Image

UPDATE:
Seems it's bug of samba

Code: Select all

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:

Code: Select all

"NT_STATUS_ACCESS_DENIED opening remote spool 1_txt"

Code: Select all

cat /etc/samba/smb.conf | grep 'client max protocol'
   client max protocol = NT1
is here.

Printing and scanning for Porteus

Posted: 03 Sep 2019, 16:05
by Ed_P
The printer is using Samba.

From my 4.0 system.

Code: Select all

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:~$ 
Image

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

Code: Select all

smbd -V
and SMBv1 in this version is not disabled.
For Linux is better to use IPP, then samba.

I have troubles with PC (ip 10.3.0.141).
He is works on Windows 10 + I activated SMB1 in control panel
Image
but it does not give a result.

I try to print from Porteus 5 RC1 to this PC with Windows 10 and as you can see I stuck on this :wall:
Interesting topic about this https://www.linuxquestions.org/question ... 175624745/

Printing and scanning for Porteus

Posted: 03 Sep 2019, 22:42
by Ed_P
From my 5.0rc1 system.

Code: Select all

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:~$ 
Looks like the same version of samba.

My 5.0rc1 system.

Code: Select all

System Memory: 3809M
Boot device:   /mnt/sda6
Boot device format: "ntfs" 
Boot folder:   /porteus5.0/
Boot mode:     ISO /ISOs/Porteus-CINNAMON-v5.0rc1-x86_64.iso
OS:       Porteus-v5.0
ARCH:     x86_64
Desktop:  Jinnamon  Cinnamon 4.2.3
Kernel:   Linux porteus 5.1.5-porteus
Cmdline:  quiet BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/Porteus-CINNAMON-v5.0rc1-x86_64.iso volume=33 reboot=cold extramod=/porteus5.0/003Modules;/porteus5.0/Modules noload=cinnamon

Printing and scanning for Porteus

Posted: 04 Sep 2019, 05:33
by Blaze
Ed_P, try like this:

Code: Select all

su
toor
chmod +x /etc/rc.d/rc.samba && /etc/rc.d/rc.samba start
smbd -V

Printing and scanning for Porteus

Posted: 04 Sep 2019, 06:19
by Ed_P
Thank you Blaze :friends: but actually I tried this. :)

Code: Select all

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# 
:showoff:

Printing and scanning for Porteus

Posted: 17 Sep 2019, 17:02
by Blaze
A new version of printing module is available here >>> Printing and scanning for Porteus (Пост Blaze #73426)

Отправлено спустя 13 часов 17 минут 58 секунд:
Some news from samba

Code: Select all

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.
https://www.samba.org/samba/history/samba-4.11.0.html

Printing and scanning for Porteus

Posted: 09 Nov 2019, 18:01
by Blaze
Download 07-printing-x86_64-2019-11-12.xzm for Porteus 5rc1 x86_64

Code: Select all

# md5sum 07-printing-x86_64-2019-11-12.xzm
27b90e247d34a0701bdd9c2c9e957479
@all, please test simple-scan and scangearmp2 and report to this topic. Thanks.

Important information! Please look at this spoiler: