antiX-19-b1-full (64 and 32 bit) available

[Member skidoo]

“Are you in vbox or running live?”

That’s a good troubleshhoting question.

Apparently my occasional, but not consistent, disclaimers within individual posts have introduced confusion as to “virtualbox or not”

Reiterating the blanket statement I had posted pages ago (or, over in the alpha topic?):
Contrary to my bare metal testing during past releases, I’m only testing via Virtualbox.

ps, additional details regarding the context of these latest tests:
antiX-19.b1_x64-full.iso
md5sum: 343c2f0ad8ea36d73459c2ee4222522e
apt-cache policy virtualbox-5.2: 5.2.30-130521~Debian~stretch

• This reply was modified 3 months, 2 weeks ago by skidoo.

[Member linuxdaddy]

thx for clarifying that.
I think it might be a vbox setting causing because I just rebooted my machine
from the 64-bit live 19-b1 dvd and can’t reproduce. It killed the pid for gweled
from the welcome screen.
I currently don’t have any setup with vbox to check different versions/settings
to check with … maybe will do that later today.
screenshot 3 shows my current testbox hardware setup for 19-b1-64-bit
so far only been on bare-metal install to hdd and live dvd boot.
I thought maybe it was because my installed one had been updated.

Attachments:

1. 

   livegweled.png
   

2. 

   gweledliveclosed.png
   

3. 

   currenthardwaresetup.png
   

Normal == 🙂
depends on the surrounding crowd ?!

[Member linuxdaddy]

I wrote:

I currently don’t have any setup with vbox to check different versions/settings
to check with … maybe will do that later today.

Not anytime soon as this machine doesn’t support 64-bit inside vbox. It
also has no gl on updated buster or sid. So 19-b1 will have to be
on my A10 one as soon as I get time for anything newer than stretch.

Normal == 🙂
depends on the surrounding crowd ?!

[Member fungalnet]

I asked this a couple of weeks ago but nobody responded.
Today it is more of essence.
If someone running testing in antix and buster in debian for a while they were parallel.
If someone runs testing in debian (bullseye today http://ftp.debian.org/debian/dists/bullseye/) is antix/testing buster or bullseye?
I understand that this bullseye distribution is all new, so it can’t be expected to be forseen by antix (an internal secret of debian) but before any testing users run aground shouldn’t there be an announcement with a clarification on what to do or not do and what to expect? Is antix 21 in the making? 🙂

anti-X - Adélie - obarun - Void - systemd Free Space

[Forum Admin anticapitalista]

antiX testing is antiX testing.

If you want to ‘roll’ with testing, enable the Debian testing repo or debian bullseye one.

antiX-buster repo will be new antiX stable. Once we are satisfied that the apps in antiX buster work and only need serious bugfixes or security updates, it will be ‘frozen (just like Debian buster). HTH

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

[Member fungalnet]

So Debian bullseye along antix testing works, now?

anti-X - Adélie - obarun - Void - systemd Free Space

[Forum Admin anticapitalista]

There is nothing new in antiX testing since buster went stable.
At the moment, antiX buster, antiX testing and antiX sid have basically the same apps.
Once antiX buster is ‘frozen’ any new/upgraded apps will go to antiX testing and sid.

How reliable/safe/’unbreakable’ is debian testing/bullseye? No idea.

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

[Forum Admin anticapitalista]

BobC wrote:

Yes, i noticed that the default theme wasn’t so good but was worried that it would break if i removed it.

The Default theme option at the bottom of the menu cannot be removed (or I can’t find a way to do it or change its default)

• This reply was modified 3 months, 2 weeks ago by anticapitalista.
• This reply was modified 3 months, 2 weeks ago by anticapitalista.

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

[Member skidoo]

a quick patch can be done to suppress that portion of the menu

src/themes.cc
outcomment lines 90 and line 91
//addSeparator();
//add(newThemeItem(app, smActionListener, _(“Default”), CONFIG_DEFAULT_THEME));

result:

anticapitalista would probably prefer to use a proper “patch” file, but for anyone who cares to repeat+test this hack, here’s a howto walkthrough:
https://pastebin.com/raw/EzLbq1ng

( successfuly tested in an antiX19b1 virtualbox instance )

[Author]

Posts