antiX-23 released.

[Member PPC]

Helpful

Up

0

::

I hesitated posting my latest suggestion to improve antiX-23 usability here or in a different new thread, not to “pollute” what’s supposed to be a thread about this latest version (and possible bugs/problems).
Anyway: @blur13 – what didnt work and if it did not work, how did the “yad part work”? This is supposed to just let arandr do it’s thing and, after the first screen resolution change, remind users to save that setting, if they so want…
I tested on my antiX 23 64bits sysv Live, multiple times, at it always works- I noticed an error, on the yad message – users should either click the “Save button” on arandr menu or select the first menu entry and then “save as” > “default.sh”. It’s just a reminder/explanation, that does not automate anything…
Many thanks for testing and reporting back!

EDIT: and the best way to implement this suggestion is, like you seem to agree, via .desktop file, so that it does not conflict with arandr’s cli usage. I attach a .desktop that includes my proposed change…

P.

• This reply was modified 2 months, 1 week ago by PPC.

Attachments:

1. arandr2.tar

[Member blur13]

Helpful

Up

0

::

Well, if I just paste it into the terminal, and close the arandr window (making no changes), the process does not stop. I have to use ctrl+c to make it quit, and then the yad window comes up. What I mean with that the yad part works is if I just paste the yad part of the script then it brings up the yad window. So it has something to do with the first part.

[Member PPC]

Helpful

Up

0

::

@blur13: Thanks for clarifying. Hum… That’s why I like people testing my scripts. There’s always something thank I don’t think about. I can see a way around that, using a more complex script, that loops around, while arandr is running, and displays the warning at the first resolution/screen change… When I have the time I’ll try to get my suggestion fixed.
Thanks for the input!

P.

Edit: I though about this on my coffee break. It’s probably better go old school and simply show a yad warning (reminding users to save the changes if they want those changes to produce effects after exiting the session/reboot), when launching arandr (with a future option that users can check to disable that warning…)

Edit2: Revised proposal:
arandr’s .desktop file could launch a script that goes something like this:

#!/bin/bash
pkill arandr; arandr &
if [ -f "$HOME/.config/no_arandr_warning" ]; then
    echo "FLAG FILE exists, don't show warning..."    
else     
    sleep 1 &&
    warning_result=$(yad --center --window-icon='/usr/share/icons/papirus-antix/48x48/devices/display.png' --title='antiX'  --form --text="\n Important tip: \n \nIf you want to keep any resolution change after your reboot, please do not forget, in the Screen Layout Editor window, to save that configuration under the name default.sh,\n in the default folder $HOME/.screenlayout\n That way, the command that sets the resolution you want on your screen(s) will run every time antiX starts" --field "Do not show this warning again":chk --button=" OK ")
	if [[ "$warning_result" == *"TRUE"* ]]; then
		touch $HOME/.config/no_arandr_warning 
	fi
fi
exit

P.

• This reply was modified 2 months, 1 week ago by PPC.
• This reply was modified 2 months, 1 week ago by PPC.
• This reply was modified 2 months, 1 week ago by PPC.

[Member PPC]

Helpful

Up

0

::

Good news, everyone:
Like @Marcelocripe noticed on another thread – anticapitalista already made abc-nix’s fix to solve the lack of audio under pipewire that some hardware was having, available in the Repository. If you are affected, just update antiX (you can run antiX Updater) and, to be on the safe side, reboot.
Any lack of sound due to pipewire problems should be fixed.
Please notice that this may (or may not) work in antix Live- if you are running Live, try to update and log off and log back on, it should work: volume icon should pop up and audio should work normally. It’s been reported that, in a few cases volumeicon does not load automatically, but even so, audio works correctly…

Unfortunately, this fix won’t solve the lack of sound quality some users are reporting- in that case, the “fix” really seems to be uninstall pipewire and stick with pure Alsa…

P.

• This reply was modified 2 months, 1 week ago by PPC.
• This reply was modified 2 months, 1 week ago by PPC.

[Member Wallon]

Helpful

Up

0

::

PPC wrote:

Good news, everyone:
Like @Marcelocripe noticed on another thread – anticapitalista already made abc-nix’s fix to solve the lack of audio under pipewire that some hardware was having, available in the Repository. If you are affected, just update antiX (you can run antiX Updater) and, to be on the safe side, reboot.
Any lack of sound due to pipewire problems should be fixed.
Please notice that this may (or may not) work in antix Live- if you are running Live, try to update and log off and log back on, it should work: volume icon should pop up and audio should work normally. It’s been reported that, in a few cases volumeicon does not load automatically, but even so, audio works correctly…

Unfortunately, this fix won’t solve the lack of sound quality some users are reporting- in that case, the “fix” really seems to be unisntall pipewire and stick with pure Alsa…

P.

Dear PPC,

Thank you for the information. This is really great news.

Kind regards,
Wallon

[Member blur13]

Helpful

Up

0

::

@PPC,

Thats a better script. Not sure about its usefulness. I mean, if a user forgets to save the arandr script they will notice fairly quickly that the changes dont stick, and save it the next time around. Not sure if thats merits the complication of having a custom desktopfile.

[Member PPC]

Helpful

Up

0

::

@anticapitalista – I confirm the problem with WINE, and I think the fix is to delete the ~/.wine folder, after installing the required 32bits libs (please see my post https://www.antixforum.com/forums/topic/problem-wine-not-working-in-antix-23/ for more details and a possible solution to this problem, that was also reported on some other distros).

EDIT: this seems to be a WINE bug (with a couple of years now): http://bugs.winehq.org/show_bug.cgi?id=51086

• This reply was modified 2 months ago by PPC.

[Member andfree]

Helpful

Up

0

::

anticapitalista wrote:

andfree wrote:

Thanks. I downloaded antiX-23_386-base.iso, but md5sum doesn’t seem to match:

$ md5sum antiX-23_386-base.iso
b3eb7fc9a767e0f55c2fdc9762f9dc8d  antiX-23_386-base.iso

Yes the md5sum is wrong.

Try downloading again from a different miror

Thanks. I downloaded it from mxlinux and the hash is the right one, although the size of the file is exactly the same as the size of the file I had downloaded from sourceforge.

[Member andfree]

Helpful

Up

0

::

In Menu => Applications, there’s only Vim.tiny and nothing else.

[Member PPC]

Helpful

Up

1

::

andfree wrote:

In Menu => Applications, there’s only Vim.tiny and nothing else.

Just below the “Applications” menu is an entry called something like “refresh the menu”. Guess what it does…

P.

[Member andfree]

Helpful

Up

0

::

Many thanks

[Author]

Posts