Printing and scanning for Porteus

[Korkoran]

Hi Korkoran.
Try Porteus-v5.1-alpha
Thanks for your feedback.

Hi Blaze,

thanks for reply with tip.

Honestly in paralel to all other actions I have bought the same printer HP P1005 with some guarantee and test lists printed, on the first start list of paper went through, later nothing, still on Porteus 5.01. Also through the checks the different status for proper printer recognition has happened, so the USB cable is one of suspicious root causes. But even with proper recognition no print at all.

Anyway to set a task to try new OS (Porteus 5.1) is a hard job as no free USB-flash available means tricky procedure to copy files out of iso to the same USB through Archive Manager after renaming old ones (no Disk Image Writer as big damage to other files can happen).

So if no new report about Porteus 5.1 will occur here soon than I am without OS, not only w/o printer. So let`s try with fingers crossed..

[Korkoran]

Hi Blaze:

Good news: Porteus 5.1 alpha can be installed via procedure above, it works with a lot of new icons, backgrounds, artwork...

Mediocre news: With false idea from wish-list to replace 07-printing_x64_01.01 from mirror by other 07-printing_x64_01.02 to have it more updated it will block possibility to open printer installing dialog at all, either through Menu-Preferences-System settings-Printer or Menu- Administration-Print settings, nothing would be opened, no reaction, no new dialog.

Surprisingly also not possible to login to forum (!) Only after restoring 07-printing_x64_01.01 module back the chance for login to provide feedback or chance to install printer are back.

Bad news: HP Laser Jet P1005 can be installed, and giving failure message about stopped printer. So yes, Porteus 5.1 Alpha + 07-printing_x64_01.01 is giving more precise feedback to BFU, what is (not) happening with printer, at least in case of HP P1005 Laser Jet.

Print status: still not serviceable. Print settings - localhost (correctly probably in this case) with red exclamation mark, Document Print Status is reporting "Stopped - printer error", Printing Troubleshooter is providing two printers, both HP P1005, one with _porteus extension and "unknown" location and information. In printing test page through debugging "Printer error not found".

Shattering update: in collapsing Windows Vista HP LaserJet P1005 it is printing documents, not only test page.

Observed detail: in Porteus 5.1 the fact of printer error is even on system tray with extension of hp-lipo module, the required proprietary one.

Hard to say, how to improve Porteus printing conclusion...?

[Blaze]

Korkoran, probably you can try to print in Alway Fresh mode at boot up as test in Porteus 5.1 with lastest printing module (and with extra dep fir your DE. BTW what kind of DE do you use?)?

[Kulle]

I cannot install/set up a printer in PorteuX 1.8.

I started the system minimally, with only the two printer modules in the modules folder:

Code: Select all

guest@porteux:~$ ls /mnt/live/memory/images
000-kernel-6.12.5.xzm/                   001-core-stable-20241215.xzm/
002-gui-stable-20241215.xzm/             002-xtra-stable-20241215.xzm/
003-xfce-4.18-stable-20241215.xzm/       07-printing-x86_64-2025-01-01.xzm/
07-printing-xfce-x86_64-2025-01-01.xzm/
guest@porteux:~$ 

However, cups does not work:

Code: Select all

guest@porteux:~$ sudo /etc/rc.d/rc.cups start

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

For security reasons, the password you type will not be visible.

Password: 
/usr/sbin/cupsd: error while loading shared libraries: libavahi-common.so.3: cannot open shared object file: No such file or directory
cups: unable to start scheduler.

I think this error is reproducible.
Who can help?
Thank you

[Blaze]

Kulle, do you have avahi package (seems PorteuX does not have in the box)?

Porteus is have avahi

Code: Select all

# ls /var/lib/pkgtools/packages/*avahi*
/var/lib/pkgtools/packages/avahi-20240306_709e60f-x86_64-3

Download avahi-20240306_709e60f-x86_64-3.txz and convert to xzm (activate it).

[Kulle]

Hi Blaze,
Avahi cannot be activated, process hangs:

Code: Select all

guest@porteux:/mnt/nvme0n1p2/porteux/optional$ activate avahi-20240306_709e60f-x86_64-3.xzm 

(sudo.py:1527): Gtk-WARNING **: 16:34:53.203: Locale not supported by C library.
	Using the fallback 'C' locale.
Password: guest@porteux:/mnt/nvme0n1p2/porteux/optional$ Updating shared library links:  /sbin/ldconfig
/usr/sbin/avahi-daemon: error while loading shared libraries: libdaemon.so.0: cannot open shared object file: No such file or directory
Starting Avahi mDNS/DNS-SD Daemon:  /usr/sbin/avahi-daemon -D
/usr/sbin/avahi-daemon: error while loading shared libraries: libdaemon.so.0: cannot open shared object file: No such file or directory
/usr/sbin/avahi-dnsconfd: error while loading shared libraries: libdaemon.so.0: cannot open shared object file: No such file or directory
Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon:  /usr/sbin/avahi-dnsconfd -D
/usr/sbin/avahi-dnsconfd: error while loading shared libraries: libdaemon.so.0: cannot open shared object file: No such file or directory

And now ??

[Korkoran]

Korkoran, probably you can try to print in Alway Fresh mode at boot up as test in Porteus 5.1 with lastest printing module (and with extra dep fir your DE. BTW what kind of DE do you use?)?

Hi Blaze,

all starts of Porteus any version were done without any records from previous sessions, always started from USB and with set of modules in "Modules" exclusively. Better for privacy and better for diagnotic, I believe. No technology used to store changes during any session.

Last printing module surprised me a lot, 07-printing from 2nd January available on mirrors with 5.01 Porteus prevented me to even to enter "Add" printer screen, no chance. No chance to login on this forum. Checked repeatedly. Only with one day older 07-printing from 1st January provided at given time with Porteus 5.1 Alpha restored chance to set a printer at all.

Regarding DE exclusively Cinnamon has been used, I have noticed specific modules related to the printing dedicated apparently to other specific DE ones, but no special module to "Cinnamon" has been observed on mirrors.

[beny]

hi Kulle here you have: https://slackware.nl/slakfinder/index.p ... e=#results

[Blaze]

Kulle, open terminal and run

Code: Select all

su
toor
getpkg libdaemon

Korkoran, try manualy install hp-plugin.
1) Download and activate net-snmp-5.9.4-x86_64-6.xzm
2) Open terminal and run

Code: Select all

hp-plugin -i
# Enter d option
# Do you accept the license terms for the plug-in (y=yes*, n=no, q=quit) ? y
# Press y
# Please enter the root/superuser password: 
# password is toor

3) in the same terminal run

Code: Select all

su
toor
system-config-printer
# add your printer HP laserjet 1005 Series, hpcups 3.24.4
# try to print

yep, Cinnamon is include all dependencies and does not request an extra modules.

[Kulle]

Hi beny and Blaze
No success!
See here:

Code: Select all

guest@porteux:~$ ls /mnt/live/memory/images
000-kernel-6.12.5.xzm/                   001-core-stable-20241215.xzm/
002-gui-stable-20241215.xzm/             002-xtra-stable-20241215.xzm/
003-xfce-4.18-stable-20241215.xzm/       07-printing-x86_64-2025-01-01.xzm/
07-printing-xfce-x86_64-2025-01-01.xzm/  avahi-20240306_709e60f-x86_64-3.xzm/
libdaemon-0.14-x86_64-1salix15.0.xzm/
guest@porteux:~$ sudo /etc/rc.d/rc.cups start
Password: 
/usr/sbin/cupsd: error while loading shared libraries: libcrypt.so.2: cannot open shared object file: No such file or directory
cups: unable to start scheduler.

What is libdaemon needed for?
Porteux 1.8 is apparently a heavily reduced system ??
Now libcrypt is still missing, and what else is missing?
My goal: I want to use cups

[Blaze]

Hi Kulle,
check on missing deps

Code: Select all

# ldd /usr/sbin/cupsd

# it's must to looks like this:
	linux-vdso.so.1 (0x00007fa6e3add000)
	libpam.so.0 => /lib64/libpam.so.0 (0x00007fa6e3a38000)
	libavahi-common.so.3 => /usr/lib64/libavahi-common.so.3 (0x00007fa6e3a29000)
	libavahi-client.so.3 => /usr/lib64/libavahi-client.so.3 (0x00007fa6e3a16000)
	libacl.so.1 => /lib64/libacl.so.1 (0x00007fa6e3a0b000)
	libdbus-1.so.3 => /usr/lib64/libdbus-1.so.3 (0x00007fa6e39b5000)
	libm.so.6 => /lib64/libm.so.6 (0x00007fa6e38c9000)
	libcrypt.so.2 => /lib64/libcrypt.so.2 (0x00007fa6e388c000)
	libz.so.1 => /lib64/libz.so.1 (0x00007fa6e3872000)
	libcups.so.2 => /usr/lib64/libcups.so.2 (0x00007fa6e37d0000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fa6e35c3000)
	libattr.so.1 => /lib64/libattr.so.1 (0x00007fa6e35bb000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fa6e3adf000)
	libssl.so.3 => /lib64/libssl.so.3 (0x00007fa6e34b3000)
	libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007fa6e2f41000)

ibcrypt.so.2: cannot open shared object file: No such file or directory

seems somthing with your glibc
you can download https://slackware.uk/slackware/slackwar ... 6_64-5.txz or via terminal

Code: Select all

su
toor
getpkg -m -q glibc

[Kulle]

Hi Blaze,
wouldn't it be easier for me if I didn't use 07-printing-x86_64-2025-01-01.xzm from 01/01/2025,
but an older printer module that avahi doesn't require?

[beny]

hi blaze so you suggest install on a stable version the glibc of the slackware current,the libcrypt.so.2 is into the glibc stable package,the user maybe have to make a link to it,lib64/incoming/libcrypt-2.33.so, it is nested.

Code: Select all

 PACKAGE NAME:     glibc-2.33-x86_64-7_slack15.0
COMPRESSED PACKAGE SIZE:     5.1M
UNCOMPRESSED PACKAGE SIZE:     33M
PACKAGE LOCATION: glibc-2.33-x86_64-7_slack15.0.txz
PACKAGE DESCRIPTION:
glibc: glibc (GNU C libraries)
glibc:
glibc: This package contains the GNU C libraries and header files. You'll
glibc: need this package to compile programs.
glibc:
glibc: The GNU C library was originally authored by Roland McGrath.
glibc:
glibc: Homepage: https://www.gnu.org/software/libc/
glibc:
glibc:
glibc:
FILE LIST:
./
bin/
etc/
etc/nscd.conf.new
etc/profile.d/
etc/profile.d/glibc.csh.new
etc/profile.d/glibc.sh.new
etc/rpc
install/
install/doinst.sh
install/slack-desc
lib64/
lib64/incoming/
lib64/incoming/ld-2.33.so
lib64/incoming/libBrokenLocale-2.33.so
lib64/incoming/libanl-2.33.so
lib64/incoming/libc-2.33.so
lib64/incoming/libcrypt-2.33.so                                                                   

[Kulle]

Hi beny,
wouldn't it be easier for me if I didn't use 07-printing-x86_64-2025-01-01.xzm from 01/01/2025,
but an older printer module that avahi doesn't require?

[Blaze]

so you suggest install on a stable version the glibc of the slackware current

No. This may cause the system to crash. Kulle didn't write which version of PorteuX 1.8 current or stable is used.

1st this module Printing and scanning for Porteus (Пост Blaze #101472) for stable (no need in avahi)
2nd Printing and scanning for Porteus (Пост Blaze #101462) for current (avahi is need)