- This topic has 251 replies, 23 voices, and was last updated Nov 12-4:22 pm by Brian Masinick.
-
Posts
-
Anonymous
like it so far. had to change my sound card in the control center
from hdmi-audio to audio-generic and log out and back
in for the volume icon on the taskbar to show up just in case others have to do that.
running on live usb with the modern kernel on hp g6 laptop (amd-a6 cpu with 8gb ram)
boots fast. Here is a shot of zzzfm-icewm desktop session.olsztyn
Based on my limited playing with this B2 runit version I have good feelings about runit init architecture, although it will take me some time to understand better.
The only material issues I have failed to resolve yet perhaps have to do with starting services:
– UFW actually starts successfully on ‘sudo ufw enable’ or from Control Center -> Firewall but does not restarts automatically upon reboot.
– Bluetooth – I am unable to start Bluez service and not sure what I am missing. On 19.4 on the same machine no problem.
– CUPS service fails to start on me. Not sure what makes it fail. Again, on 19.4 works fine. Perhaps it must be started a different way, not from Control Center Printers?Other than that seems fine so far…
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
marcelocripe
anticapitalista wrote:
@marcelocripe – thanks for the feedback.
I’ll try to get all the latest translations on the final iso and update the packages before then.
About the menus, please send me your corrected menu entries of the files in /usr/share/antiX/localisation/pt-brThanks.
Could you please let me know what is the deadline I will have to send you corrections?
I can send you the corrected ISO files “antiX-21-b2-runit_x64-full.iso”:
– the menu files (of the first level) of the Fluxbox, IceWM and JWM folders that are in the path /usr/share/antiX/localisation/pt-br with the corrections pt-BR;
– toolbar files from IceWM and JWM folders that are in the path /usr/share/antiX/localisation/pt-br with the corrections pt-BR; and
– the “.desktop” files that are in the path /usr/share/applications and /usr/share/applications/antix with the corrections in pt-BR and with the corrections made by Zeh in pt.Without the deadline information, I have no way of knowing if everything I want to do, if I will be able to send you in time to be used in antiX ISOs and antiX updates.
Thanks.
marcelocripe
(Original text in Brazilian Portuguese)– – – – –
anticapitalista wrote:
@marcelocripe – thanks for the feedback.
I’ll try to get all the latest translations on the final iso and update the packages before then.
About the menus, please send me your corrected menu entries of the files in /usr/share/antiX/localisation/pt-brThanks.
Por favor, você poderia me informar qual é a data limite que eu terei para te enviar as correções?
Eu posso te enviar os arquivos corrigidos da ISO “antiX-21-b2-runit_x64-full.iso”:
– os arquivos de menu (do primeiro nível) das pastas Fluxbox, IceWM e JWM que estão no caminho /usr/share/antiX/localisation/pt-br com as correções pt-BR;
– os arquivos toolbar das pastas IceWM e JWM que estão no caminho /usr/share/antiX/localisation/pt-br com as correções pt-BR; e
– os arquivos “.desktop” que estão no caminho /usr/share/applications e /usr/share/applications/antix com as correções em pt-BR e com as correções feitas pelo Zeh em pt.Sem a informação da data limite, eu não tenho como saber se tudo que eu quero fazer, se conseguirei te enviar a tempo para ser utilizado nas ISOs do antiX e nas atualizações do antiX.
Obrigado.
marcelocripe
(Texto original em Português do Brasil)Just another thing – minor and cosmetic (nothing material) – about Herbstluftwm, which I reported in Herbstluftwm thread and which apparently got carried over to B2:
– If I select Herbstluftwh from ‘Other desktops’ it gives me Herbstluftwm desktop with the following tags: 1,2,1,2,3,4,5,6,7,8,9. I have effectively 11 tags. Previously the first two were not numbered (blank) and subsequent numbered (1-6).
– If I select Herbstluftwm through F1 after prior logoff, I get Herbstluftwm with the expected tag numbers 1-9. No additional 1,2 in front.
– After logoff from Herbstluftwm (Windows key + Shift + q) I get the expected login screen with sessiontype:icewm (default) showing on top . However after login from here I get logged in to Herbstluftwm, not IceWM as indicated on the login screen. If I F1 cycle on the login screen, making a round trip through selections back to IceWM and log in, then I get logged in to IceWM as indicated on the login screen.
Just to mention, I am using Default slimski theme, not tested this with multiple slimski themes…Just to stress again, these are cosmetic and not material. They have no impact at all since I know what the behavior is, so I know what to do in order to arrive at desired desktop. Therefore it is not any priority to pay attention to, in comparison…
- This reply was modified 1 year, 8 months ago by olsztyn.
- This reply was modified 1 year, 8 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
Xecure
– UFW actually starts successfully on ‘sudo ufw enable’ or from Control Center -> Firewall but does not restarts automatically upon reboot.
Sorry. This was a bug in the ufw service. The “pause” command isn’t included in the current version of runit (I copied part of the sv script from void linux).
I am trying to build a different version of runit with this command included (but it isn’t working right now). For now, stop the ufw service withsudo sv stop ufw sudo touch /etc/sv/ufw/down– Bluetooth – I am unable to start Bluez service and not sure what I am missing. On 19.4 on the same machine no problem.
First, enable bluetooth from cmst interface (connman disables bluetooth, the same as it did with wifi on previous versions)
cmst -d
and switch bluetooth to ON.
Then, check that the runit service is working
sudo sv status bluetooth
Its state should be “run”.
Then you can connect to any bluetooth device with blueman. You can launch the applet with
blueman-applet &– CUPS service fails to start on me.
Works for me on my system. Check the service status
sudo sv status cups
If it is not up, then we can explore if there is something stopping it from starting (a down file) or if it is even enabled.Are your tests from Live USB or from installed? If from live-USB, maybe one of the disable=[] parameters is set, which has some of the services also disabled (you need to tell us for us to test properly).
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure
– If I select Herbstluftwh from ‘Other desktops’ it gives me Herbstluftwm desktop with the following tags: 1,2,1,2,3,4,5,6,7,8,9. I have effectively 11 tags.
Cannot reproduce on installed (no matter from where I start herbstluft, I get the same amount of tags).
– After logoff from Herbstluftwm (Windows key + Shift + q) I get the expected login screen with sessiontype:icewm (default) showing on top
Cannot reproduce. If I disable default user and log-out, the sessiontype is displayed as rox-icewm, but as soon as I enter the username and hit Enter, the sessiontype changes to whatever I was using (herbstluft included).
Is this on live-USB or installed? VM or real hardware?antiX Live system enthusiast.
General Live Boot Parameters for antiX.Thank you Xecure!
On sudo sv status cups I am getting:down: cups: 8325s
I am not sure what is the meaning but on Htop I see runsv cups but with 0 memory footprint.
From Control Centre Printers the button ‘Start Service’ is grayed out, so I am not sure if enabled.Are your tests from Live USB or from installed? If from live-USB, maybe one of the disable=[] parameters is set, which has some of the services also disabled (you need to tell us for us to test properly).
It is from Live USB but I have boot parameter Disable=F, instead of Disable=lxF. So CUPS should be available to start, just like in 19.4.
Cannot reproduce. If I disable default user and log-out, the sessiontype is displayed as rox-icewm,
The difference in my testing causing this might be that I am using the Default slimski theme, not the default one it comes with. In other words, I changed (first thing I did) the slimski theme to use Default one, which shows just login line. After entering login it asks for password. I also blanked out all messages (Msg1 through Msg5).
As I mentioned, this issue is just cosmetic, not worth of your time, but I appreciate you checked it anyway…
Thanks and Regards.- This reply was modified 1 year, 8 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersXecure
I will do some more slimski testing tomorrow.
For the ufw service problem, I have built a experimental runit-antix package that also creates the pause command (to be used in the future by other services).
I have also added the backlight-brightness fix I mentioned in another runit topic.Anyone interested, please install both packages linked here and reboot. From that moment on, the system will remember the brightness (laptop brightness set with backlight-brightness) in last session on each reboot, and ufw should now start without a problem.
For the cups problem, see if
sudo rm /etc/sv/cups/down sudo sv start cupsgets cups service to properly start and work.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
andyprough
Now that antiX has this Bullseye beta, we can install the latest bleeding edge plasma/KDE from this Debian KDE packager’s personal repos: https://www.preining.info/blog/2021/08/obs-builds-of-kde-plasma-for-debian-bullseye-testing-unstable/
Here’s the latest plasma desktop 5.22.4 on my installation of antix 21 runit beta today (official Bullseye repo is only going to package version 5.20.5, which is already over six months old).
Attachments:
For the cups problem, see if
sudo rm /etc/sv/cups/down
sudo sv start cups
gets cups service to properly start and work.Thank you Xecure!
It resolved cups start issue…Question about general service management in runit environment: Is there a service management tool that would allow to manage services?
In any case, thank you for all solutions to service issues…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameterscalciumsodium
That does the job of moving the login screen to the middle top of the screen. But did not change position of the texts. They are still on the left.
How do I change the position of the texts to match the position of the login screen in slimski?I had posted this question earlier in post #65518. I did not see an answer, so I wanted to ask again if there is a way to change the position of the texts in slimski.
Thanks.Edit: I figured it out. In order to shift the login screen and the texts to the middle of the screen, use these values in the file
/usr/share/slimski/themes/antiX/slimski.theme
input_panel_x 50% input_panel_y 10% sessiontype_x 50% sessiontype_y 40% F1_x 50% F1_y 45%- This reply was modified 1 year, 8 months ago by calciumsodium.
I am trying to build a different version of runit with this command included (but it isn’t working right now). For now, stop the ufw service with
sudo sv stop ufw
sudo touch /etc/sv/ufw/downThanks Xecure for interim solutions. Just to update on testing:
– CUPS resolution worked perfectly. CUPS service started and works going forward.
– UFW still does not start automatically upon reboot. I did install your two patches (ufw and backlight). However, as before, it can be started via sudo ufw enable each time after reboot.
– Bluetooth shows powered on in CMST, however service continues to be down:
sudo sv status bluetooth comes back with:
down: bluetooth: 664s
– It appears to me that maintaining backlight level is not working for me automatically. Even after installation of the patch. Not that important though. I just press Fn + Home and comes back to level.
– When from slimski login screen (Default theme, not the theme that comes as default, at least) selecting sessiontype not one of those included with antiX (DWM in this case) is working but the well known screen appears that wm is not one of approved, allowing to Cancel, select one of approved, etc., like in 19.4, however the ‘Disable’ button is missing. Therefore disabling this screen popping up is not possible and and needs to be cancelled every time. Not a big issue, just an annoyance…Thanks and Regards…
- This reply was modified 1 year, 8 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersPPC
Two tiny but annoying situations that may be solvable:
-It just came to me that the “Update menu” entry does not work on my system – because it needs root privileges- I edited my fluxbox menu so it includes “gksu” first- does that issue still happens in antiX 21 (sorry, I’m away from my test machine).
-Is it possible to solve the bug- when you download anything in firefox and click the file from firefox’s downloads list- the “search file” window pops up, instead of opening the associated program… This was solved in my antiX 19.x when I made spacefm/zzzfm my default file manager- I haven’t tested doing that in a21 b2
P.
Xecure
– It appears to me that maintaining backlight level is not working for me automatically. Even after installation of the patch. Not that important though. I just press Fn + Home and comes back to level.
It seems live-USB is a bit more complicated than I can manage.
On installed, when exiting the system, the last step runit does is stop any configured K (stop) scripts in /etc/runit-core/, but on live USB this happens AFTER all persistence changes have been saved, so this new change doesn’t save at all (on live USB with persistence).
I tried activating savestate, but this only seems to work (not tested) on non-persistent antiX-live.
My guess is that there is a script that runs at some point in time after pressing Shutdown/reboot that saves the brightness value before giving the option to save persistence changes, and that only works with sysvinit scripts. Or maybe savestate is not working on runit version at all (I need to test this).
For now, nothing I can do until I learn more.Question about general service management in runit environment: Is there a service management tool that would allow to manage services?
This is experimental, and isn’t a package yet, but if you install dialogbox from the repos and run this script from terminal (with sudo), you can manage runit services in a graphical interface.
Try to enable ufw and bluetooth Startup option and see if this fixes the issues you are experiencing on your system.– When from slimski login screen (Default theme, not the theme that comes as default, at least) selecting sessiontype not one of those included with antiX (DWM in this case) is working but the well known screen appears that wm is not one of approved
I think the most left option is used to disable it for the future. I will have a look.
-It just came to me that the “Update menu” entry does not work on my system – because it needs root privileges
I will see if I can send a merge request adding gksudo to the update menu command.
-Is it possible to solve the bug- when you download anything in firefox and click the file from firefox’s downloads list- the “search file” window pops up, instead of opening the associated program…
Same method, changing the default file manager from preferred applications. For some reason, desktop-defaults-follow-fm.desktop is not a valid option for mime-update.
The problem resides in $HOME/.local/share/applications/mimeinfo.cache, line inode/directory
inode/directory=zzzfm-find.desktop;zzzfm-folder-handler.desktop;zzzfm.desktop;
I think if rox-filer.desktop and desktop-defaults-follow-fm.desktop had this option inside:
MimeType=inode/directory;
and run
sudo update-desktop-database
it should work for firefox (at least rox-filer).
If you move desktop-defaults-follow-fm.desktop outside of the /usr/share/applications/antiX/ folder, it should also pick up by mimeinfo and work properly.
I will edit the zzzfm package to remove the MimeType option for zzzfm-find, so that at least it doesn’t bring up the same problem.antiX Live system enthusiast.
General Live Boot Parameters for antiX.It seems live-USB is a bit more complicated than I can manage.
On installed, when exiting the system, the last step runit does is stop any configured K (stop) scripts in /etc/runit-core/, but on live USB this happens AFTER all persistence changes have been saved, so this new change doesn’t save at all (on live USB with persistence).Thank you Xecure for looking into these things.
On the quoted above regarding backlight:
I do not think this would be the related to persistence save timing. The reason for my thinking is I do not use persistence at all. After I make all changes and the system is perfectly working, at the end I just remaster so all changes are in place at the point of remastering. After remaster is complete I reboot to use the new linuxfs file.I think the most left option is used to disable it for the future. I will have a look.
Yes, this is the one, to disable that screen going forward. In 21 it is missing.
Also thanks for the experimental service management tool…
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
- You must be logged in to reply to this topic.
