PorteuX 1.8 has been released
PorteuX 1.8 has been released
I thought about what the cause is:
Chromium does not require avahi for its functions.
Therefore, initially works without an installed Avahi daemon.
However, the printer module adds dependencies that require avahi libraries.
Specifically, the library libavahi-common.so.3 is needed
When Chromium is launched after activating the printer module,
it attempts to load this Avahi library as it is now part of the dependencies.
Since the library is not present, Chromium fails to start.
Conclusion: avahi is absolutely needed in PorteuX
Chromium does not require avahi for its functions.
Therefore, initially works without an installed Avahi daemon.
However, the printer module adds dependencies that require avahi libraries.
Specifically, the library libavahi-common.so.3 is needed
When Chromium is launched after activating the printer module,
it attempts to load this Avahi library as it is now part of the dependencies.
Since the library is not present, Chromium fails to start.
Conclusion: avahi is absolutely needed in PorteuX
PorteuX 1.8 has been released
It's not needed for the system itself. If your personal needs require this package, just download it (and put in your porteux/modules folder):
Code: Select all
getpkg -m -q avahi
PorteuX 1.8 has been released
Hi porteux, but you have this package in the current branch
PorteuX 1.8 has been released
@beny, you're right, but I think Kulle is using PorteuX stable, which doesn't contain avahi. I just checked and it seems Slackware stable repo doesn't contain this package either. So the only solution is to build it manually: https://slackware.uk/slackbuilds.org/15 ... ork/avahi/
PorteuX 1.8 has been released
So the only solution is to build it manually: https://slackware.uk/slackbuilds.org/15 ... ork/avahi/
Too complicated, I've never done it before.
And all this effort, just to make cups work in PorteuxX 1.8 stable ???
Too complicated, I've never done it before.
And all this effort, just to make cups work in PorteuxX 1.8 stable ???
PorteuX 1.8 has been released
Hi porteux,
The module 07-printing-x86_64-2023-04-22.xzm worked for me in Porteux 0.4.
I tried using this same module in PorteuX 1.8 for testing.
These errors occur:
The module worked in 0.4 but no longer works in 1.8.
How can this be explained?
Newer printing modules also don't work in 1.8.
What should I do now?
I can't use 1.8 because printing is a basic necessity.
The module 07-printing-x86_64-2023-04-22.xzm worked for me in Porteux 0.4.
I tried using this same module in PorteuX 1.8 for testing.
These errors occur:
Code: Select all
guest@porteux:/var/log/cups$ cat error_log
E [10/Jan/2025:13:31:18 +0000] Unknown directive IdleExitTimeout on line 32 of /etc/cups/cupsd.conf.
E [10/Jan/2025:13:33:18 +0000] [cups-deviced] PID 1811 (bjnp) stopped with status 1!
E [10/Jan/2025:13:33:18 +0000] [cups-deviced] PID 1814 (cups-pdf) stopped with status 1!
E [10/Jan/2025:13:33:18 +0000] [CGI] Unable to execute ippfind utility: No such file or directory
E [10/Jan/2025:13:35:03 +0000] [cups-driverd] Bad driver information file \"/usr/share/cups/drv/sample.drv\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/C410sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/C420sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/C43xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLP-300sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLP-310sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLP-320sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLP-360sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLP-600sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLP-610sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLP-620sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLP-660sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLX-216xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLX-3160sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLX-3170sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLX-3180sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/CLX-6220sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/K2200sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/M2020sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/M2070sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/M262xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/M267xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/M283xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/M288xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/M301xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/M306xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/M332xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/M337xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/ML-2160sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/ML-2540sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/ML-2950sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/SCX-3400sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/SCX-4650sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/SCX-470xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/SCX-472xsc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [cups-driverd] Bad driver information file \"/usr/share/ppd/suld/cms/SF-760sc.cts\"!
E [10/Jan/2025:13:35:06 +0000] [CGI] Unable to execute ippfind utility: No such file or directory
W [10/Jan/2025:13:35:32 +0000] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [10/Jan/2025:13:35:32 +0000] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [10/Jan/2025:13:35:32 +0000] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
How can this be explained?
Newer printing modules also don't work in 1.8.
What should I do now?
I can't use 1.8 because printing is a basic necessity.
PorteuX 1.8 has been released
Hi porteux,
Blaze has informed me:
Regarding the issue with printing in GTK3 apps, you must report it to the PorteuX team.
libprintbackend-cups.so is missing !
printing and scanning do not work in Porteux 1.8 stable Xfce
See here:
Blaze has informed me:
Regarding the issue with printing in GTK3 apps, you must report it to the PorteuX team.
libprintbackend-cups.so is missing !
printing and scanning do not work in Porteux 1.8 stable Xfce
See here:
Code: Select all
guest@porteux:~$ ls -l /usr/lib64/gtk-3.0/3.0.0/printbackends/libprintbackend-cups.so
/bin/ls: cannot access '/usr/lib64/gtk-3.0/3.0.0/printbackends/libprintbackend-cups.so': No such file or directory
Code: Select all
guest@porteux:~$ find /usr/lib /lib /lib64 -name libprintbackend-cups.so
guest@porteux:~$
PorteuX 1.8 has been released
hi kulle you can strip a gtk3 package and bring the lib from gtk 3.0.0 and put into the system at the same location, /usr/lib64/gtk-3.0/3.0.0/printbackends, you are right is the only one that miss into the directory on porteux stable
PorteuX 1.8 has been released
Hi beny,
I don't exactly understand what you mean.
What exactly should I download and where?
Where can I find libprintbackend-cups.so
I don't exactly understand what you mean.
What exactly should I download and where?
Where can I find libprintbackend-cups.so
PorteuX 1.8 has been released
Hi beny,
In the Porteux 0.4 stable version:
/usr/lib64/gtk-3.0/3.0.0/printbackends/libprintbackend-cups.so
/usr/lib64/gtk-2.0/2.10.0/printbackends/libprintbackend-cups.so
So both gtk-2.0 and gtk-3.0 were present!!
Can I simply transfer the libprintbackend-cups.so file from Porteux 0.4 to PorteuX 1.8?
and libprintbackend-file.so and libprintbackend-lpr.so ??
In the Porteux 0.4 stable version:
/usr/lib64/gtk-3.0/3.0.0/printbackends/libprintbackend-cups.so
/usr/lib64/gtk-2.0/2.10.0/printbackends/libprintbackend-cups.so
So both gtk-2.0 and gtk-3.0 were present!!
Can I simply transfer the libprintbackend-cups.so file from Porteux 0.4 to PorteuX 1.8?
and libprintbackend-file.so and libprintbackend-lpr.so ??
PorteuX 1.8 has been released
Kulle, try this module that contains cups for stable: https://www.mediafire.com/file/fiixy81r ... 6_64-1.xzm
PorteuX 1.8 has been released
Hi Porteus,
Thank you very much,
but printing still didn't work.
See here #160
Printing and scanning for Porteus (Post by Kulle #101633)
I suspect that something is still missing in version 1.8, because printing worked without any problems in version 0.4
Thank you very much,
but printing still didn't work.
See here #160
Printing and scanning for Porteus (Post by Kulle #101633)
I suspect that something is still missing in version 1.8, because printing worked without any problems in version 0.4
PorteuX 1.8 has been released
hi porteux, i have seen that you have removed from glibc package the 32 bit support,this on porteux current,the user is unable to run 32 bit software because of this, the gcc is untouched,remeber that multilibs core now is merged into the slackware current,ok for me solved.
PorteuX 1.8 has been released
@beny, if you need 32-bit support, please download Multilib Lite module from the App Store.
PorteuX 1.8 has been released
Hi porteux,
Blaze says libprintbackend-cups.so (module cups-3.24.43-x86_64-1.xzm) alone is not enough.
All GTK3 apps must be recompiled.
Does this mean I have to abandon my plan (installation of a printer in Porteux 1.8 stable)?
Could switching to Porteux current be sensible for me?
Does cups work there?
Alternatively, I have already tested booting Porteus 5.01,
it is on my notebook significantly slower
Blaze says libprintbackend-cups.so (module cups-3.24.43-x86_64-1.xzm) alone is not enough.
All GTK3 apps must be recompiled.
Does this mean I have to abandon my plan (installation of a printer in Porteux 1.8 stable)?
Could switching to Porteux current be sensible for me?
Does cups work there?
Alternatively, I have already tested booting Porteus 5.01,
it is on my notebook significantly slower