PorteuX 0.8 has been released

[porteux]

@beny, the kernel .config is on Github: https://github.com/porteux/porteux/tree/main/000-kernel

[beny]

hi porteux, thanks i can rebuild the 6.6.2 with your config..

[seed_clapper]

please paste the content of your /mnt/live/memory/images/

do you mean names of these files?

000-kernel-6.6.1.xzm
001-core-current-20231118.xzm
002-xorg-current-20231118.xzm
002-xtra-current-20231118-no-libmpv-neon-updated-mpv.xzm
003-lxqt-1.4.0-current-20231115.xzm

I tried 0.8 current with old mpv 0.36.0 and result is same - "segmentation fault". But in stable version mpv works fine. Maybe it is just my hardware is not compatible with current version.

This 0.9 alpha with new mpv 0.37.0 works on other ten year old laptop so I played 3m19sec long 1080p HEVC video:
mpv 0.36.0 - 139 frames dropped
mpv 0.37.0 - 787 framed dropped
mpv 0.37.0 with --profile=fast - 369 frames dropped

New mpv automatically disabled something

[vo/gpu] Disabling scaler #0 lanczos (GLSL version too old).
[vo/gpu] Disabling scaler #1 hermite (GLSL version too old).
[vo/gpu] Disabling linear/sigmoid scaling (GLSL version too old).
[vo/gpu] correct-downscaling requires non-bilinear scaler.

but dropped frame count is higher than in older mpv

Using --profile=fast and enabling decoding queue reduced dropped frame count to zero
--vd-queue-enable=yes # makes mpv keep decoding video until one of limits is reached
--vd-queue-max-bytes=800MiB # how much ram can be used for storing decoded video data
--vd-queue-max-samples=8000 # just some random high number because default is too low
--vd-queue-max-secs=80 # just some random high number because default is too low

[SaintAnd]

Hi all!
Porteux 0.8 LXDE (Same problem in Porteus 5.01)

When you log in, this window appears


There are long-standing problems with Internet connection and logout.



Cheat code:

Code: Select all

title Porteus-LXQT-v5.01-x86_64
find --set-root --ignore-floppies --ignore-cd /porteux/porteux-v0.8-lxde-0.10.1-stable-x86_64/porteux/porteux-v5.0-x86_64.cfg
kernel /porteux/porteux-v0.8-lxde-0.10.1-stable-x86_64/boot/syslinux/vmlinuz kmap=us,ru timezone=Europe/Moscow from=/porteux/porteux-v0.8-lxde-0.10.1-stable-x86_64 cfgfile=porteux-v5.0-x86_64.cfg
initrd /porteux/porteux-v0.8-lxde-0.10.1-stable-x86_64/boot/syslinux/initrd.zst

But everything works well in virtualbox, but it doesn't suit me. Why doesn’t everything work as expected on real hardware?

[porteux]

@seed_clapper, interesting finding this performance regression! Maybe you should report to the mpv guys on Github: https://github.com/mpv-player/mpv/issues/ Now, regarding the segmentation fault, you should try to get the log:

Code: Select all

mpv --log-file=output.txt

Or even better the backtrace (if you can compile):

Code: Select all

$ git clone https://github.com/mpv-player/mpv
$ cd mpv
$ meson setup debug -Dbuildtype=debug -Db_sanitize=address,undefined
$ meson compile -C debug

And then run ./debug/mpv.

@SaintAnd, could try in Always Fresh and if it doesn't work, please paste the content of your /mnt/live/memory/images/ and the output of the command uname -r.

[SaintAnd]

porteux,

I'm using the stock iso. That is, the entire assembly is unchanged. I run it via grub4dos. This issue has not been resolved since porteux 0.3

In addition
Another problem is that glib-networking does not work. Even if you install the module

Code: Select all

xdg-open "https://google.com"

Of course it works without http"S"

Code: Select all

xdg-open "http://google.com"

But there are many sites that need to be opened
For example

Code: Select all

xdg-open "https://linux-gaming.ru/portproton/"

[porteux]

@SaintAnd, can you try a boot without absolute no changes, no cheatcode, nothing? I see you're using 'porteux-v5.0-x86_64.cfg' and this file name has never been part of PorteuX, which uses 'porteux.cfg' instead.

If you still can't fix your issues, I would recommend booting directly via USB stick (no grub, no ISO).

You shouldn't have any NetworkManager issues, but you might face some firmware missing depending on your hardware. Is your network card being detected?

Why are you installing glib-networking?

I don't have any issues using xdg-open with any of the addresses you provided. I'm on Xfce 4.12.

[SaintAnd]

porteux,
1. I changed the cfg names for my convenience. I did not change the contents of the files.
I use the lxde version as you understand

2. I install glib-networking because this error asks me to do this, but nothing happens.
I checked in xfce and indeed there are no problems with xdg-open, apparently the error lies in the lxde version. I can't find the reason for this error.

[SaintAnd]

porteux,
1. Regarding the first one. I realized my mistake. When I extracted the iso image via the context menu (extract here), it turned out that the directories did not have rights for “groups” and “others”
It looked like this:

Code: Select all

porteux:
total 32
drwx------ 6 guest users 4096 Oct 15 21:02 ./
drwxr-xr-x 6 guest users 4096 Nov 26 04:43 ../
drwx------ 2 guest users 4096 Nov 16 01:41 base/
-rw-r--r-- 1 guest users 1103 Mar 22  2023 create-iso.sh
drwx------ 2 guest users 4096 Oct 15 21:02 modules/
drwx------ 2 guest users 4096 Oct 15 21:02 optional/
-rw-r--r-- 1 guest users  719 Mar 22  2023 porteux.cfg
drwx------ 2 guest users 4096 Apr 17  2023 rootcopy/

I solved the problem with command:

Code: Select all

chmod -R +rwx ./porteux-v0.8-lxde-0.10.1-stable-x86_64 

2. But regarding the second, it is not clear why glib-networking does not work normally in lxde

[porteux]

porteux,
1. Regarding the first one. I realized my mistake. When I extracted the iso image via the context menu (extract here), it turned out that the directories did not have rights for “groups” and “others”

This is the default behavior with any ISO image extraction regardless of the distro, right? That's why it's recommended to use the PorteuX installer because it fixes all the permissions.

Anyway, it's not clear which problem you fixed by doing this.

2. But regarding the second, it is not clear why glib-networking does not work normally in lxde

You shouldn't have to install glib-networking in LXDE. You should try what I said in the previous post:

can you try a boot without absolute no changes, no cheatcode, nothing?

If you still can't fix your issues, I would recommend booting directly via USB stick (no grub, no ISO).

[Ed_P]

I'm using the stock iso. That is, the entire assembly is unchanged. I run it via grub4dos.

Your grub4dos menu doesn't look like the ones I use to boot ISOs.

Code: Select all

title Windows 7 System Repair Disc - 32-bit\n\n\ When prompted press Enter to boot disc.
find --set-root /ISOs/w7repairdisc_32_bit.iso
map /ISOs/w7repairdisc_32_bit.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)

title Windows 7 System Repair Disc - 64-bit\n\n\ When prompted press Enter to boot disc.
find --set-root /ISOs/repair_disc_windows_7_64_bit.iso
map /ISOs/repair_disc_windows_7_64_bit.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)

title Acronis Recovery Manager\n
find --set-root /ISOs/Acronis.iso
map /ISOs/Acronis.iso (hd32)
map --hook
chainloader (hd32)

title Kon-Boot v1.1 - Windows Password Recovery\n\n Once Windows has booted; create a new administrator account, log off, log on\n to the new administrator account and reset your account's password.\n * May not work with 64-bit systems.
map --mem /ISOs/konFloppy.img (fd0)
map --hook
chainloader (fd0)+1
map (hd1) (hd0)
map --hook
rootnoverify (fd0)

This looks more like my grub2 menus.

Code: Select all

title Porteus-LXQT-v5.01-x86_64
find --set-root --ignore-floppies --ignore-cd /porteux/porteux-v0.8-lxde-0.10.1-stable-x86_64/porteux/porteux-v5.0-x86_64.cfg
kernel /porteux/porteux-v0.8-lxde-0.10.1-stable-x86_64/boot/syslinux/vmlinuz kmap=us,ru timezone=Europe/Moscow from=/porteux/porteux-v0.8-lxde-0.10.1-stable-x86_64 cfgfile=porteux-v5.0-x86_64.cfg
initrd /porteux/porteux-v0.8-lxde-0.10.1-stable-x86_64/boot/syslinux/initrd.zst

To which I would suggest trying this version:

Code: Select all

title PorteuX-LXQT-v0.8-x86_64
find --set-root /porteux/porteux-v0.8-lxde-0.10.1-stable-x86_64/porteux/porteux.cfg
kernel /porteux/porteux-v0.8-lxde-0.10.1-stable-x86_64/boot/syslinux/vmlinuz kmap=us,ru timezone=Europe/Moscow 
initrd /porteux/porteux-v0.8-lxde-0.10.1-stable-x86_64/boot/syslinux/initrd.zst

[Rava]

3- this keyring thing happens to all (most?) Chromium-based browsers. One solution is to hit OK on all these dialogs and then persisting the contents of ~/.local/share/keyrings/

Some solutions are suggested here:
https://dev.to/rahedmir/how-to-fix-goog ... linux-1dl0
One is to add this to the end of your Exec line in your /usr/share/applications/google-chromium.desktop (or whatever your .desktop file for opening that kind of browser is named)

Code: Select all

--password-store=basic 

as seen here:

but be aware that by doing this when you use Chromium to store any password - these are now stored in a less secure manner.
As I understand the issue, the same is the case by pressing OK on all these dialogues and persisting the contents of ~/.local/share/keyrings/ … but I might be wrong.

[SaintAnd]

You shouldn't have to install glib-networking in LXDE. You should try what I said in the previous post:

1. I was able to run the image without problems on real hardware.

2. On real hardware and a virtual machine, everything was done exactly as you asked, because I’m trying to run it through a virtual machine from an iso image without any changes, through an iso image via cd-rom. Try to launch yourself (via virtualbox, kvm, etc.) any iso with the LXDE shell and make sure that by running:

Code: Select all

xdg-open "https://google.com"

The error described above will appear.
Everything is fine in lxQT, but for some reason it doesn’t work in lxDE

Ed_P,
Yes, I don’t use the image, because if you transfer it to a flash drive, this image needs to be defragmented or there may be little RAM on the computer of the person who needs help, so for myself I decided it was better to unpack the system so as not to have unnecessary problems. And besides, this method allows you to add modules that are necessary. Thanks, I figured out the first problem. The only problem left is lxde

[seed_clapper]

Maybe you should report to the mpv guys on Github

They pursue "quality" over "performance".

get the log

https://gofile.io/d/fVY1xj

New mpv can play videos when using --vo=xv or --vo=x11.
Last current version with working mpv is 0.6. Using xtra module from 0.6 in PorteuX 0.7 does not work.

[porteux]

@seed_clapper, have you tried to compile to get the backtrace as I said previously? Also, can you replicate these regressions on any other distro that ships mpv 0.37.0?

@SaintAnd, I see what you mean now. This looks like a xdg-open issue related to LXDE -- the error is even different between PorteuX stable and current. LXQt doesn't come with glib-networking and opening https URLs just works, as you said.