Porteus-v5.1-alpha4 bug reports

[spa_time]

Hello....all the appreciations for the teamwork...
Just a few bugs to perfect the final version...
Changed boot/sylinux/initrd.xz with version from alpha2 to work iso in ventoy
Added some python libs to run opensnitch firewall - not working in alpha4
All the best..

[AcnapyxoB]

On the KDE desktop the audio device is not detected after logout and login.
It's not a big deal, but I'll mention it anyway!

Description of the problem:
- Turning on the PC (like guest) - there's sound, everything is fine.
- Logout and login (like guest) - audio device is missing!?
- Logout and login (now like root) - there's sound again.
- Once again logout/login like root - the audio is lost again!?

Tested on two physical computers and on VirtualBox.

There are no issues with XFCE and Cinnamon desktops and also no issue with Porteus 5.01 KDE.

Sond Cards:
PC 1 - Dell 5500:
HDA-Intel - HDA Intel PCH
CONTROLLERS:
Intel Corporation Device 9dc8 (rev 30)
0 alsa_card.pci-0000_00_1f.3 module-alsa-card.c
PC 2 - Lenovo T540p:
HDA-Intel - HDA Intel PCH
HDA-Intel - HDA Intel HDMI
CONTROLLERS:
Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)

https://www.mediafire.com/view/hm6eaeev ... g.png/file

[ncmprhnsbl]

Changed boot/sylinux/initrd.xz with version from alpha2 to work iso in ventoy

i don't have much knowledge of ventoy at this point

On the KDE desktop the audio device is not detected after logout and login.

confirmed, thanks
quick workaround: when it happens on relogin, alt+F2 or just start typing for the runner, insert: pipewire-launcher restart
and a more permanent fix: extract 002-xorg and edit /etc/xdg/autostart/pipewire.desktop, in the Exec= line, add restart at the end and recompress the module.
not sure why plasma is more sensitive to this than the others, could be due to differences in the way sddm and lxdm handle things..

[AcnapyxoB]

insert: pipewire-launcher restart

Thanks, adding restart did the job!

Now 'pipewire.desktop' looks like this:

Code: Select all

[Desktop Entry]
Version=1.0
Name=PipeWire Media System
Comment=Start the PipeWire Media System
Exec=/usr/local/bin/pipewire-launcher restart
Terminal=false
Type=Application
X-GNOME-Autostart-Phase=Initialization
X-KDE-autostart-phase=1

[Otto]

Thx for releasing alpha4.
The clock for mate and openbox wont change after reboot.
Mate speaker tray shows 100%, sound volume is changeable only from pavucontrol.
Openbox, how to setup the auto-display to external monitor?.

[ncmprhnsbl]

The clock for mate and openbox wont change after reboot.

need more details of what you're doing for this: are you setting a timezone? how? is you hardware clock in local or UTC? what sort of persistence are you using?

Mate speaker tray shows 100%, sound volume is changeable only from pavucontrol.

mate doesn't have pavucontrol, but it's own builtin version(sound preferences) that i would have thought would sync with the applet ..idk, maybe fiddle with hardware section settings.. or maybe do a `mate-panel --replace` to restart the panel..

Openbox, how to setup the auto-display to external monitor?.

not sure what you mean by "auto-display to external monitor" .. you mean when you plug in the cable or at startup?
afaik, open settings>arandr , set up things as you like (particularly in the 'outputs' menu) then file>save as to 'somewhere'(in the guest folder somewhere) then add to the ~/.config/openbox/autostart :

Code: Select all

sh /path/to/name_of_arandr_settings.sh

i don't think there's a way of doing any hotplugging setup..

[Otto]

Sorry my mistake: it is LXDE not mate
~/porteus settings center/time config/:
- "set date/time": the year showed 2021 and I changed it to 2026.
- "set timezone": set to UTC and got the correct clocktime, but
the clock for Lxde and openbox wont keep my setting after reboot.

Lxde speaker tray shows 100%, sound volume is changeable only from pavucontrol from start-menu.

Openbox display for external monitor is solved (followed your instruction). Thx.

[ncmprhnsbl]

Sorry my mistake: it is LXDE not mate

ok ..maybe : right click on the speaker icon> 'volume control' panel > audio card dropdown .. see if changing any options if present helps..

~/porteus settings center/time config/:
- "set date/time": the year showed 2021 and I changed it to 2026.
- "set timezone": set to UTC and got the correct clocktime, but
the clock for Lxde and openbox wont keep my setting after reboot.

you're using some sort of saved changes. right?
hmm.. to me, if your hardware clock is utc and your timezone is utc, that's functionally the same as the hardware clock being localtime ... buut.. apparently not i guess?
what sort of time difference do you see when it's wrong?
what about if you use the cheatcodes: utc timezone=UTC

[Otto]

The cheatcodes work only for lxde.
My clock is 11:00, openbox time shows 16:00


Mate problem:
Let say I run Pluma (pluma window will open on the desktop) or any apps,
but there is no sign on the taskbar that pluma is opened.
The problem is once I click minimize window, pluma will gone forever/can not recall/recover.

[pterid]

Hello everyone... I just want to say a huge thanks to ncm for including my tools in the new alpha release, and I'm looking forward to receiving reports about them and trying to improve them please do report issues here!

[AcnapyxoB]

When opening a directory as root (in my case /tmp), strange messages appear in a pop-up window.

Porteus 5.1 alpha4 Cinnamon (looks similar in XFCE):

Authentication is needed to run '/usr/bin/env
DISPLAY=:0 ZAUTHORITY=/ho ... ON= dbus-run-session
nemo file:///tmp' as the super user

An application is attempting to perform an action that requires privileges.
Authentication as the super user is required to perform this action.

screenshot:
https://www.mediafire.com/view/4hatv7k5 ... 1.png/file

This is how it looks like in KDE 5.1 alpha4:

The action you requested needs root privileges. Please enter root's password below
or click ignore to continue with your current privileges.

Command:
/bin/sh -c 'pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY
KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true PATH=/usr/local/sbin:/usr/local/
bin:/sbin:/usr/sbin:/bin:/usr/bin PORTDIR=$PORTDIR BOOTDEV=$BOOTDEV
XDG_DESKTOP_SESSION=$XDG_DESKTOP_SESSION dolphin /tmp'

screenshot:
https://www.mediafire.com/view/rhlobd27 ... 1.png/file

And how it normally looks on Porteus 5.01 KDE:

The action you requested needs root privileges.
Please enter root's password below or click ignore
to continue with your current privileges.

Command: dolphin /tmp

screenshot:
https://www.mediafire.com/view/qz0vwkk2 ... 1.png/file

[ncmprhnsbl]

strange messages appear

welcome to the new normal
i think you'll find it's been this way since alpha1 .. somewhere along the line changes to either pkexec or more likely the polkit-agents, they started displaying the command used to invoke them (or did they always?)
the env BUNCH_O_VARS part being the variables needed to be passed to the elevated app so that it can work, since pkexec doesn't pass these by default.
with kde, the old way: kdesu, which "just worked", just doesn't anymore(at least for dolphin), so the workaround using pkexec requires a bunch of extra vars for that, hence the horrible looking dialog..
last time i looked at plasma 6 , it gets even worse..
there's a fairly strong push amongst developers out there to make using graphical apps as root (or any other user than the one logged in graphically)impossible, which is fair enough, but does make it difficult for porteus which relies on a lot of graphical admin tools..

[AcnapyxoB]

Thanks ncmprhnsbl, that explains it. I'll just take it as 'new normal'.

[Ed_P]

Cinnamon: I like the new Low Battery task bar icon. Red makes it very obvious to spot.

[Florenz1]

With Alpha 3, the correct Nvidia driver I need for the RTX 400 was installed – could we include it in the next release, or better still, in the current version 5.01?