Porteus

Hi Rava and roadi,
I have Python2 not loaded as a module!
For safety:
I have now launched in "always fresh mode".
Same bug!

Kulle wrote: ↑

21 Nov 2021, 08:41

I have Python2 not loaded as a module!
For safety:
I have now launched in "always fresh mode".
Same bug!

yes, this has been reported earlier in this topic(by none other than Rava, i believe ) and has been fixed in my tree..
for reference: the bug is caused by the script(xpsinfo) not handling an exception raised when one(or more) of the log files is not encoded in UTF-8 (cause somewhat random and unknown, possibly hardware related)

as far as python2 is concerned, as it went end of life a while back and is no longer in slackware current, avoid where possible and if it must be used, tweek it so /usr/bin/python does not link to it.

roadie wrote: ↑

21 Nov 2021, 06:14

Possibly, but is python2 even needed with 5.0-rc3? […] But someone using an older version of Porteus might have problems if they've installed python3 and the program does want python2.

Usually a script should be coded that way that when you run an older script (e.g. from the time when python2 was the most recent and python3 not existed yet) using python3 - it still should work okay.
While I personally like the python approach to scripting very much, sadly I never had time to learn the finer details of the language myself so it all is a noob's POV on python what I say about such matters anyway.

The only python scripting related thingy I managed was some many months ago to tweak a python script and edited one single line of code (as I recall, maybe it was more than one line, though) since the script would malfunction using Porteus otherwise.

Using Nemo to access a folder with .jpg files on a NTFS drive displays the images.
Using Nemo to access a folder with .jpg files on an iPhone displays the files as icons.

I do not know if this has been reported, but in Kde, when I want to restart, computer freezes ... With CPU 100% on ksmserver-logou
(although with very few modules activated with only firefox and abiword, and not running)

I do not know if this has been reported, On Mate, the numeric keypad of the keyboard does not work
(no problem for other desktops)

Still on Mate, problem of permissions to modify/edit in text mode a launcher (*.desktop)

Apparently the launchers (*.desktop) to start a small script do not work on Kde.
By the way, how do you create it on the desktop ? (apart from creating a *.desktop file)

@Rapha, I can't replicate your CPU issue on KDE but it has changed a bit since RC3, so hopefully the next release you'll have this issue fixed.

Numeric keypad works for me on Mate. Are you sure numlock is on? In order to edit .desktop files that are stored in any system folder (usually /usr/share/applications) you need root previleges otherwise editors will open in read only mode.

@ fulalas

Thank you for your reply,
(the freezing is repeated today on the exit)

Sorry, forget the numeric keypad on Mate, I had checked by mistake, with the keyboard setting (Mouse Keys : X Pointer can be controlled using the keypad )

Curiously the problem of permissions of the Launcher did not repeat itself

I am using 5.0RC3 Xfce
While browsing with Chromium, this popup is thrown:

Choose password for new keyring

An application wants to create a new keyring called 'Default'. Choose password you want to use for it.

it is very, very annoying.

Yeah, Kulle. It's very annoying indeed, but just keep pressing Enter/OK and it will generate /home/guest/.local/share/keyrings, so you just need to restore this folder everytime you reboot

fulalas wrote: ↑

18 Dec 2021, 09:44

Yeah, Kulle. It's very annoying indeed, but just keep pressing Enter/OK and it will generate /home/guest/.local/share/keyrings, so you just need to restore this folder everytime you reboot

What is even more annoying to me:

The Chromium makes itself the default browser without asking.
I want Palemoon to still be my default browser, thank you very much, even what I temporarily activate the Chromium module.

Is there a way by tweaking Chromium's settings to get Chromium to abandon that rude behaviour?

If so, the update-browser script should incorporate that by default. At least Chromium needs to ask if it can set itself up to be the default browser, and if the user answers that with a "no" then Chromium should not set itself up as default browser.
Seems Chromium still has some behaviour left of Chrome in that regard.

@Rava, if you're using Xfce try this:

1- create: /usr/share/xfce4/helpers/palemoon.desktop
2- put this inside: 3- create this file: /home/guest/.config/xfce4/helpers.rc
4- put this insise:

^
And Chromium would not overwrite /home/guest/.config/xfce4/helpers.rc ?

I presume it would not overwrite /usr/share/xfce4/helpers/palemoon.desktop … I implement both files and report back how it works out.

And I presume² I can put both /home/guest/.config/xfce4/helpers.rc and /usr/share/xfce4/helpers/palemoon.desktop into my 005-palemoon-VERSION.linux-x86_64-gtk3.xzm from now on.
(Or maybe better into my xxx-palemoon-settings-YYYY-MM-DD.xzm instead. )


Added in 18 minutes 23 seconds:
Update
While the activation of the Chromium module is done by root, the execution of the chromium binary is done by guest.
So, when I have root create both /home/guest/.config/xfce4/helpers.rc and /usr/share/xfce4/helpers/palemoon.desktop and keep both as (even the one in /home/guest/) Chromium and any other program should be unable to tamper with any of these files, since they would need root privilege doing so. And that they should not have or get.

Like so:
($PWD folder I am in is my extracted 980-palemoon-settings-YYYY-MM-DD.xzm soon to be made into 980-palemoon-settings-2021-12-18.xzm)

Lots of wording but I don't know if it's working