antiX-25-full-beta1 for public testing

[anticapitalistaForum Admin]

@olsztyn
Try creating a file called fuse3.conf in /etc/modules load.d with the word fuse3 (or maybe just fuse).
It will probably need a reboot to check that it works.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[olsztynMember]

anticapitalista wrote:

Try creating a file called fuse3.conf in /etc/modules load.d with the word fuse3 (or maybe just fuse).

Thanks again.
Yes, this worked… With ‘fuse’ as module name. Fuse3 did not seem to work.
It seems this is what it needs, in order to survive reboot or rather remaster and to avoid loading ‘sudo modprobe’ each time.

This seems to have closed the only remaining issue on Beta1 I had in my scope of testing. Perhaps just one might be left – I need to check if boot disk is left in clean state after normal shutdown.
Beta1 works very nicely, with runit at least… Thanks again.

• This reply was modified 9 months, 3 weeks ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Brian MasinickModerator]

anticapitalista wrote:

Try sudo modprobe fuse and maybe sudo modprobe tun
then open the app.
If that works, you will probably have to add fuse (and tun) to /etc/modules file.
Does MX have that already?

Funny, it’s actually my MAIN distro that was acting up – and I ended up removing the Ungoogled Chromium App Image and installing an archive instead, untarred it and that worked.

Probably something bad in my cache; in any case I worked around it.

• This reply was modified 9 months, 3 weeks ago by Brian Masinick.

--
Brian Masinick
Alternate "Search B":
This search page

[anti-apXosMember]

I’m getting a reproducible crash in zzzfm in this beta.

If I have a partition mounted and a tab for it open and focused in zzzfm, then I middle-click on the partition’s entry in the devices list to unmount it, most of the time (but not absolutely always) zzzfm will crash entirely. Same happens if I right-click the entry and choose either unmount or remove/eject from the context menu.

On antix-23, in this same situation, only the open tab is closed, which is what should happen according to the zzzfm manual.

I guess zzzfm itself hasn’t changed, but it’s due to sone interaction with another lib or something.

Another thing: I noticed that the ‘service’ command no longer recognizes runit services, as it does on antix-23. Is this a known/expected side-effect if the init diversity system? In the final release, will we still be able to have one command like ‘service’ that can be used regardless of init or will we have to use different commands to control services for each init?

"--"

[dolphin_oracleForum Admin]

anticapitalista wrote:

Try sudo modprobe fuse and maybe sudo modprobe tun
then open the app.
If that works, you will probably have to add fuse (and tun) to /etc/modules file.
Does MX have that already?

mx has fuse3 pre-installed.

[anticapitalistaForum Admin]

dolphin_oracle wrote:

anticapitalista wrote:

Try sudo modprobe fuse and maybe sudo modprobe tun
then open the app.
If that works, you will probably have to add fuse (and tun) to /etc/modules file.
Does MX have that already?

mx has fuse3 pre-installed.

antiX also has it pre-installed, but (it seems) it is not automatically probed. hence, the need to create the fuse.config file.
I’m guessing this might be a kernel issue.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[dolphin_oracleForum Admin]

anticapitalista wrote:

dolphin_oracle wrote:

anticapitalista wrote:

Try sudo modprobe fuse and maybe sudo modprobe tun
then open the app.
If that works, you will probably have to add fuse (and tun) to /etc/modules file.
Does MX have that already?

mx has fuse3 pre-installed.

antiX also has it pre-installed, but (it seems) it is not automatically probed. hence, the need to create the fuse.config file.
I’m guessing this might be a kernel issue.

could be I guess. I don’t have any modifications to the modules files.

BTW I just pushed up an update to gazelle-installer that should help those with 32 bit UEFI get grub installed. old apple devices mostly, but some other low power machines as well.

• This reply was modified 9 months, 3 weeks ago by dolphin_oracle.
• This reply was modified 9 months, 3 weeks ago by dolphin_oracle.

[Brian MasinickModerator]

@anticapitalista wrote: “I’m guessing this might be a kernel issue.”

Now that you mention it, maybe that IS the case. I now have THREE kernels I’ve been experimenting with on my main setup. Both our 6.6 and 6.1 kernels have been working great. I brought in another kernel that I often use, the Liquorix kernel because they had a brand new one, and it worked really well. I was surprised and pleased to see FEWER rather than more memory resources used with their latest, but MAYBE they trimmed out a lot of modules, and it’s possible that introduced issues, though that’s just a wild guess, because their kernels have always worked well in the past.

Even though the kernel is a variable, in my case I’m still suspicious about my environment somehow getting garbage in either the config or cache directories for that browser; just as the kernels really haven’t been a frequent problem, neither have these browsers; that always makes me consider what OTHER variables MIGHT be a part of the PROBLEM and the SOLUTION, so I’m not quite ready to point at anything definite – I DID add the two modules you noted; they didn’t impact the problem I experienced one way or the other, which is why in my case DID NOT solve the problem. What DID solve the problem in my case was getting rid of the AppImage and downloading an archived instance of the browser instead; that DID work without any of the module additions.

--
Brian Masinick
Alternate "Search B":
This search page

[olsztynMember]

anticapitalista wrote:

antiX also has it pre-installed, but (it seems) it is not automatically probed. hence, the need to create the fuse.config file.
I’m guessing this might be a kernel issue.

I am not an expert to make a determination in this matter, one way or the other, but just want to mention that I am running the same kernel (6.16.12 Liquorix) both in antiX 25Beta1 and MX 25. However in MX it (fuse) works by default, while in antiX the fuse module needs to be explicitly specified as above, instructed by @anticapitalista for this to work.

• This reply was modified 9 months, 3 weeks ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Brian MasinickModerator]

olsztyn wrote:

Just a question to follow-up on running Appimage on antiX 25 Beta1:
Does an appimage, such as Ungoogled Chrome or Helium start successfully for anyone on antiX 25 Beta1? In spite of being executable and libfuse2t64 installed that is…
So far unsuccessful for me.

YES. I had it working with Beta 1 and it works on most of my configurations except one. I scrapped that one and replaced it with an image that I untarred instead of the App Image. That one works so the workaround for me is quicker than wasting more time on this. My guess is that by removing my config and cache entries, I probably could have gotten it working again too, but I want time to do other things so I went a different direction and solved the problem another way.

--
Brian Masinick
Alternate "Search B":
This search page

[melodieMember]

rej wrote:

Xfce with lightDM did not appear to install properly – tried sudo dpkg-reconfigure lightdm, resulting in same error of missing packages.

Have you had a look into the /var/log/lightdm directory to see what the lightdm.log says? Else, do you have a “/var/lib/lightdm/data/lightdm” directory, with owner and group lightdm:lightdm for it?

[Brian MasinickModerator]

Brian Masinick wrote:

@anticapitalista wrote: “I’m guessing this might be a kernel issue.”

Now that you mention it, maybe that IS the case. I now have THREE kernels I’ve been experimenting with on my main setup. Both our 6.6 and 6.1 kernels have been working great. I brought in another kernel that I often use, the Liquorix kernel because they had a brand new one, and it worked really well. I was surprised and pleased to see FEWER rather than more memory resources used with their latest, but MAYBE they trimmed out a lot of modules, and it’s possible that introduced issues, though that’s just a wild guess, because their kernels have always worked well in the past.

Even though the kernel is a variable, in my case I’m still suspicious about my environment somehow getting garbage in either the config or cache directories for that browser; just as the kernels really haven’t been a frequent problem, neither have these browsers; that always makes me consider what OTHER variables MIGHT be a part of the PROBLEM and the SOLUTION, so I’m not quite ready to point at anything definite – I DID add the two modules you noted; they didn’t impact the problem I experienced one way or the other, which is why in my case DID NOT solve the problem. What DID solve the problem in my case was getting rid of the AppImage and downloading an archived instance of the browser instead; that DID work without any of the module additions.

CORRECTION: I removed everything, packages, config and cache entries and reinstalled the AppImage and it worked, so my suspicion that it may have been on my end at least WAS correct; AppImages install fine and no special trickery is needed. Also, someone was asking if this worked in test images; yes, it worked there too.

--
Brian Masinick
Alternate "Search B":
This search page

[Brian MasinickModerator]

http://www.antixforum.com/forums/topic/antix25-xfce-sysvinit-trixie-stable-respin/page/3/#post-191422 contains a well-written defect report –
[Bug Report] antiX 25 GRUB Installation Fails on UEFI Systems – EFI Partition Not Mounted

--
Brian Masinick
Alternate "Search B":
This search page

[BobCModerator]

I also had problems with Grub failing to install on a Dell EFI laptop that was dual booting Windows 10 or 11 as well as Devuan. When it failed, it said to run boot repair, which I did, but oddly it thought it should use MBR instead of ESP. It said it wasn’t allowed to update the EFI. Anyway,the result was that boot repair on antiX 25b also failed. I was eventually able to get it to boot to Grub again by running the boot repair from antiX 23, but now Grub no longer shows or allows me to boot to Windows as a result.

Here is the link to SEARCH THE FORUM >> http://www.antixforum.com/search-forums

[BassmanMember]

anti-apXos wrote : I’m getting a reproducible crash in zzzfm in this beta.

Got the same behavior using spaceFM in MX-25 (installed). Here’s just a workaround:
to unmount/eject a device, first close the tab (or right-click on the device-entry in the side-column and select “Close”),
now you can select either “remove/eject” or “unmount” and its done without application crashing.
Perhaps this may work for zzzFM too.
Greetings

[Author]

Posts