leafing through porteux

wendy-lebaron

Well-Known Member
Joined
May 3, 2023
Messages
661
Reaction score
273
Credits
9,291
i have tried porteux 2.6. which was released right at the end of february 2026. i chose the iso for mate desktop.

i would like to deeply thank. the porteux developers. for continuing to offer the "devel" and "multilib" modules. because of "multilib" module. i could continue using the wine 8 appimage. instead of the version 10. which is less friendly with drag-and-drop. in the two or three windows programs. i still insist on using. although the emulation of "syswow64" works wonders. but i choose to do without it in certain situations.

i had tried porteux with lxqt desktop before. (this was the 1.7 released in october 2025.) but it doesn't seem to matter which desktop. it keeps crashing every other time at startup. i set up an "autostart" script on lxqt. to take care of the screen brightness. because it's not done automatically. when the panel comes on. the session manager doesn't seem to like my script. it's done correctly one time i fire up the system. then the next time i try to fire it up. it brings a dialog saying, "panel crashed too many times." then i get no panel and no wallpaper. i only get the context menu. where i have to open a terminal. to shut down the computer. or to do anything else. except correct this problem.

with mate desktop? it messes up something with "libpam" or other. so it refuses to reset the screen brightness. this one time the session is started. in the next time. it could decide to get it right.

wait there's more. the panel in mate is still buggy! i want to move whatever is "system monitor". to have more room for launchers. but the "system monitor" disappears. even worse sometimes when i start a session. the battery widget plays hide-and-seek. this is for mate 1.28 which shouldn't have this problem anymore. that i suffered on debian "bullseye" with mate 1.24. basically the user cannot ask for the panel widgets to be locked into positions. because it could mess it up.

i had to give up on sparky linux also with this desktop. because i don't want the clock hogging the bottom-right corner of the screen. if i put the "show desktop" widget as the last item instead. upon the next session. it goes right back and puts the clock instead. but that had mate 1.26.

the mate terminal is buggy too. had it crash a couple of times. after visiting the keystroke configuration dialog.

it was really a shame. opensuse "tumbleweed" totally crapped out on me. in the summer of last year. had to get the big iso. install it with xfce desktop. to then request mate desktop instead. i got mate 1.28. which was working very well. behaved itself although i didn't test. to see if the problems with the panel persisted. it looked great too. something close to "menta" theme. not like the sparky linux "ghosty white" themes. that cannot be used anymore with gimp 3.

back to porteux. discovered something else depressing about this product. the "porteux store" was never changed from its first version! from there download a web browser. and a handful of other programs. in case the user missed those "devel" and "multilib" modules. that "store" is the place to request to download them. i desired, for example geany 2.1. instead i have to get the "deb" package for debian "forky testing." and see if it could work via "rootcopy" trick.

i don't want to use "gslapt" ever again. i had mixed experiences with that. using slackel for several months a few years ago. this was while i still had an unlimited internet connection. a bit faster than what i could afford now. otherwise i have to recourse with "slackbuilds." but i have had build failures with debian as well as slackware. generally whatever uses only "c" language. compiles successfully for me these days.

i have to rely on appimages more than ever. otherwise install "flathub" mechanism. which wastes a serious amount of diskspace. it has other issues so i refuse. i wanted to benefit from nixos package manager. but that has complications i don't want to go into right now.

the main reason to use porteux 2.6. is because it comes with "glibc" 2.43. two versions ahead of debian "trixie". some programs are getting too high. for me to run on debian "bookworm." which doesn't justify the higher library requirements. because they are clunky. or have some other problem. but because most of them are virtual music instruments. alternatively something like the latest version of "lla". which raises eyebrows. because it's a terminal-only program.

i only wanted to reveal some of my experiences lately. also to thank the porteux developers. for offering a highly accessible alternative to slackware. which is "dirt cheap", not being said as an insult. but the user will deal with its limitations.
 


Hey Wendy

I stay updated on Porteus(X) forum and have not seen you posting your problem. Where did you post?

Vektor
 
i had forgotten to clarify. that i've been running porteux like any other linux operating system. ie. with "esp" partition and with "ext4" partition. on a 32gb usb "pen" drive. not forcing it from "fat32" partition. although more (somewhat reliable) disk space for backups is always welcome.

i downloaded the porteux 2.6 iso. with lxqt desktop instead. it works well. although not much different from 1.7. however i'm afraid of creating an "autostart" entry. to reset the screen brightness. i know a program has to be run that comes with lxqt. but now the system i have starts into the desktop without any problems. i'd rather have that now.

---

i don't participate on porteus forum any longer. i don't want to talk about it here. because it's off topic.
 
porteux 2.6 with lxqt desktop. with lxqt 2.3 on "x11". still gives me the "panel crashed too many times" error dialog at session start. i did nothing to it. not even add anything to "autostart." this is becoming a bit frustrating.

i try from "qps" program. to restart "lxqt-session" or other program. i have to go back and check again. (i'm not on that operating system while writing this.) log in "guest" account giving the password. then i get the same dialog box again, "panel crashed too many times."

i haven't tried porteux with wayland session.

should obtain a few applications. i was able to run the gimp 3.0.0 appimage. (not "anylinux" version. the one that was released almost a perfect year ago, 17-march-2025.) looks great with the current theme. my ancient licensed copy of 64-bit renoise 2.8.2 (music production software) works quite well too. this is before going a bit further. to see if it supports pipewire like on debian.

i was able to "steal" the geany 2.1 "deb" files. from debian "forky testing." plus four "plug-ins." it works well on porteux. one thing to watch out for. slackware doesn't use "/lib/x86_64-linux-gnu" directory. the libraries that go in that place in debian. need to be in the main "/lib" directory. with everything else of a few hundred with "so" suffix.

---

i don't know how to really describe this. but porteux (powered by active slackware "current") inherited a bug from porteus (based on four-year-strong stable slackware 15). this is its inability to deal consistently with drive/partitions beyond "sda9". which have two-digit integer identifiers. i have a "/mnt/sda10" but it's not indicated at all by volume label by pcmanfm. i could still select it. if i navigate to "/mnt" and from that list of directories. but the sidebar leaves it out. unless it's included as bookmark. and then it doesn't show the "drive connected" icon with it.

on porteus 5.1 i think i discovered a complex "bash" script. that dealt with partitions on a single disk. it also was unable to reach "sda10" or other partition that wasn't a single integer.

i know this is an operating system. used by people who want to load it quickly. get their internet fix for the good part of an hour. then disconnect and disappear. but i explain something like this. it's not a great annoyance. but i would like to see if it's noticed and fixed.
 
Last edited:
update on usage.

so far only once has the desktop protested starting up properly.

cautiously i created "autostart" entry again. to discover with some annoyance. there are two programs to do the same thing. to take the screen out of blinding maximum battery-killing brightness. "lxqt-backlight-backend" which requires "root" permission. and "lxqt-config-brightness" which could be run by ordinary user. each one has slightly different options.

i tried the program which required elevation. of course it didn't work. so i've just changed to the other program. hoping for the best now.

i've been using krita 5.2.16. with a program i wrote that shows images. and could copy a portion of an image to the clipboard. then use "new document" command in krita. to retrieve the image portion from the clipboard. it works faster than on debian "bullseye". with krita 5.2.5. on the same 15-year-old computer.

however my program begs for zenity to create message box dialogs. but it's not on the system. so it misbehaves. if it can't do anything greater than lowly "xmessage". now i have to figure out. how to include the zenity "anylinux" appimage. as if it were a program originally installed.

oh one more thing. somehow pcmanfm decided to display my "/dev/sda10" like the others automatically mounted. (shrugs)(scratch head)

edit: argh! i remove the bookmark for my "/dev/sda10". but the file manager then refuses to list it as device above that on the sidebar! why do i have to keep a duplicate entry just for this? edit: above, corrected name of one of the programs.
 
Last edited:


Follow Linux.org

Members online


Top