PorteuX 1.8 has been released

[Kulle]

I can't say exactly what I experimented with yesterday in detail.
Today I proceeded meticulously and systematically.
Four carefully executed tests:

1) In the modules folder, only printing-current-x86_64.xzm
and the library programs libcupsfilters-2.1.0-x86_64-2.xzm libpaper-2.2.5-x86_64-1.xzm libppd-2.1.0-x86_64-2.xzm poppler-25.01.0-x86_64-1.xzm

The system doesn't start, it hangs:
INIT: Id "x1" respawning too fast

2) Start in "always fresh"
and subsequently manually activated the modules mentioned above one by one.
Then installed the printer via localhost:631/admin.
Success! I can print from Mousepad

3) In the Modules folder only (!) printing-current-x86_64-updated
The system doesn't start, it hangs:
INIT: Id "x1" respawning too fast

4) Start in "always fresh"
and manually activated printing-current-x86_64-updated
Then installed the printer via localhost:631/admin.
No success! The printer is not displayed in Mousepad. I cannot print.

[porteux]

I can't replicate this. Booting with only the base modules (000-kernel-6.12.5.xzm, 001-core-current-20241215.xzm, 002-gui-current-20241215.xzm, 002-xtra-current-20241215.xzm, 003-xfce-4.20-current-20241215.xzm) and the latest printing module (printing-current-x86_64-updated.xzm) works just fine, goes directly to Xfce desktop with no issues.

Most likely you're mixing some other modules. To make sure, try to should run in the terminal: ls /mnt/live/memory/images/

Once you figure it out, could you tell us what's missing in the latest printing module?

[Kulle]

I tested it again.
when booting the following appears on the screen:
creating live filesystem
001-kernel
002-gui
002-extra
003-Xfce
printing-current-updated
and nothing else!!
and then it hangs:
INIT: Id "x1" respawning too fast

[porteux]

This is not ls /mnt/live/memory/images/

[Kulle]

I first boot into "always fresh" and confirm that only the file printing-current-x86_64-updated is in the modules folder.
Then I log out.

I now reboot normally
It gets stuck: INIT: Id "x1" respawning too fast
When I log in then, I am prompted to log in again (infinite loop)
This means I cannot access the system!
So I cannot execute ls /mnt/live/memory/images/.

I have this strange error in two systems:
One system on the internal SSD
One system on a USB stick

[Kulle]

Hi porteux,
==> It gets stuck: INIT: Id "x1" respawning too fast
This problem is solved!!
rootcopy caused this error. I removed it.
It was rootcopy with /etc/profile.d/lang.sh
But why can rootcopy cause such an error?
Do you have an explanation for this??

printing-current-x86_64.xzm works with the library programs libcupsfilters-2.1.0-x86_64-2.xzm libpaper-2.2.5-x86_64-1.xzm libppd-2.1.0-x86_64-2.xzm poppler-25.01.0-x86_64-1.xzm

printing-current-x86_64-updated alone doesn't work, the printer is not displayed in Mousepad
Error log:

Code: Select all

guest@porteux:~$ cat /var/log/cups/error_log 
E [20/Jan/2025:16:04:03 +0100] Unknown directive IdleExitTimeout on line 32 of /etc/cups/cupsd.conf.
W [20/Jan/2025:16:04:03 +0100] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103
W [20/Jan/2025:16:04:03 +0100] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [20/Jan/2025:16:04:03 +0100] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [20/Jan/2025:16:04:03 +0100] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
guest@porteux:~$