antiX-19.3 (Manolis Glezos) released

Forum Forums News Announcements antiX-19.3 (Manolis Glezos) released

  • This topic has 55 replies, 15 voices, and was last updated Dec 5-7:24 pm by userzero.
Viewing 15 posts - 16 through 30 (of 56 total)
  • Author
    Posts
  • #43169
    Moderator
    BobC
    Helpful
    Up
    0
    :D

    script that allows IceWM to memory window position and size? (Sorry, I don’t recall it’s name)

    icewm-remember-settings was suggested by anticaptialista

    Latest version was by Xecure on June 11th https://www.antixforum.com/forums/topic/hotkey-to-remember-window-size-and-position-for-icewm/page/4/#post-37246

    Code for that version was/is at: https://pastebin.com/UtqWrFga

    On mine, in my keys file, I hooked it to Win+R for Remember Window so I don’t need to select from 100 windows
    key "Super+r" icewm-remember-settings

    PS: I updated the antix-goodies package and its not there yet

    PSS: I updated this machine (Alienware I7 Laptop) to 19.3. I originally had a little trouble with trying to do it with the updater icon, but I tried again via terminal, and its running just fine. I can paste an inxi listing if you want.

    • This reply was modified 8 months, 1 week ago by BobC.
    • This reply was modified 8 months, 1 week ago by BobC.
    #43184
    Member
    marcelocripe
    Helpful
    Up
    0
    :D

    @masinick wrote:
    PPC, thanks again for your efforts, and thanks to anticapitalista, skidoo, Dave, BobC, Xecure, and everyone else who has made helpful suggestions, contributed scripts, tools, feedback, and artistic skills. Thanks also to all who have helped in any capacity to get this work done. Everything from the suggestions, testing, code, and helpfulness is appreciated. Thank you antiX community!

    Mr. Brian Masinick is absolutely right to record thanks to all the people who collaborated in some way, it is very good to be able to see in this new version, several and several programs that facilitate the use of antiX. This is concrete proof that the union of everyone in the community is recognized and can be seen in each new version.

    “I make your words mine, Mr. Brian Masinick. Because you made mine my thoughts” (Ulisses Formiga)

    Thank you all!

    marcelocripe

    ———-

    O sr. Brian Masinick tem toda razão em registrar os agradecimentos a todo o pessoal que colaborou de alguma forma, é muito bom poder ver nesta nova versão, vários e vários programas que facilitam o uso do antiX. Esta é a prova concreta de que a união de todos na comunidade é reconhecida e pode ser vislumbrada a cada nova versão.

    “Faço minhas as suas palavras, sr. Brian Masinick. Pois fizeste seus os meus pensamentos” (Ulisses Formiga)

    Muito obrigado a todos!

    marcelocripe

    #43192
    Member
    Koo
    Helpful
    Up
    0
    :D

    Install 19.3 runit X64 works fine on X220 was booting to the wrong drive before take no notice of that post about grub.

    Setup wifi with connman works great just enter password in passphrase dialog box click ok and your connected. No need for ceni.

    I always run repo manager first for the fastest connection seems to fix any repos at may not be quite right.

    Got this error.

    
    $ sudo apt update
    Hit:1 http://deb.debian.org/debian buster-backports InRelease
    Hit:2 http://security.debian.org buster/updates InRelease                      
    Get:3 https://mirrors.evowise.com/mxlinux-packages/antix/buster buster InRelease [27.4 kB]
    Get:4 https://mirrors.evowise.com/mxlinux-packages/antix/buster buster/main amd64 Packages [281 kB]
    Get:5 https://mirrors.evowise.com/mxlinux-packages/antix/buster buster/main i386 Packages [283 kB]
    Get:5 https://mirrors.evowise.com/mxlinux-packages/antix/buster buster/main i386 Packages [283 kB]
    Get:5 https://mirrors.evowise.com/mxlinux-packages/antix/buster buster/main i386 Packages [283 kB]
    Get:5 https://mirrors.evowise.com/mxlinux-packages/antix/buster buster/main i386 Packages [283 kB]
    Get:5 https://mirrors.evowise.com/mxlinux-packages/antix/buster buster/main i386 Packages [283 kB]
    Err:5 https://mirrors.evowise.com/mxlinux-packages/antix/buster buster/main i386 Packages
      File has unexpected size (282589 != 282594). Mirror sync in progress? [IP: 172.67.6.37 443]
      Hashes of expected file:
       - Filesize:282594 [weak]
       - SHA256:6fa8cd6b1bf3cd837c0f6cf4c768ee9838c830e12b3cd0a8d680d3c735731908
       - SHA1:07ada268cd44b5390dc0ea468d5ed2994013f582 [weak]
       - MD5Sum:6eefeef2c121516c776c989da7409673 [weak]
      Release file created at: Wed, 14 Oct 2020 12:47:30 +0000
    Hit:10 http://ftp.au.debian.org/debian buster-updates InRelease                
    Hit:11 http://ftp.au.debian.org/debian buster InRelease                        
    Reading package lists... Done                                                  
    E: Failed to fetch https://mirrors.evowise.com/mxlinux-packages/antix/buster/dists/buster/main/binary-i386/Packages.gz  File has unexpected size (282589 != 282594). Mirror sync in progress? [IP: 172.67.6.37 443]
       Hashes of expected file:
        - Filesize:282594 [weak]
        - SHA256:6fa8cd6b1bf3cd837c0f6cf4c768ee9838c830e12b3cd0a8d680d3c735731908
        - SHA1:07ada268cd44b5390dc0ea468d5ed2994013f582 [weak]
        - MD5Sum:6eefeef2c121516c776c989da7409673 [weak]
       Release file created at: Wed, 14 Oct 2020 12:47:30 +0000
    E: Some index files failed to download. They have been ignored, or old ones used instead.

    But did run upgrade any way. Is their a reason why we use backports ?

    
    sudo apt upgrade
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    Calculating upgrade... Done
    The following packages will be upgraded:
      firmware-ralink
    1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    Need to get 18.9 kB of archives.
    After this operation, 0 B of additional disk space will be used.
    Do you want to continue? [Y/n] 
    Get:1 http://deb.debian.org/debian buster-backports/non-free amd64 firmware-ralink all 20190717-2~bpo10+1 [18.9 kB]
    Fetched 18.9 kB in 0s (90.3 kB/s)    
    (Reading database ... 111570 files and directories currently installed.)
    Preparing to unpack .../firmware-ralink_20190717-2~bpo10+1_all.deb ...
    Unpacking firmware-ralink (20190717-2~bpo10+1) over (20190717-1~mx19+1) ...
    Setting up firmware-ralink (20190717-2~bpo10+1) ..

    Thanks to every one who contributed to this new version.

    T430 i7-3632QM 16gb , antiX-19.2.1-runit_x64-base Hannie Schaft 29 March 2020 , 5.8.16-antix.1-amd64-smp

    #43211
    Member
    Xecure
    Helpful
    Up
    0
    :D

    grub installation problem I think started from 2 updates ago of the minstaller. Sometimes (most times), it works perfectly. Other times, the installation stops at 90-95% with “Unable to install grub” error. It is a rare error, but without knowing why this happens no good bug report can be reported. The good thing is that grub installation is the last step, so if there is an error, using Boot Repait program to install and then repair grub will fix the issue, as I tested in this post: https://www.antixforum.com/forums/topic/cannot-install-antix-grub-installation-problem/#post-39997

    I always run repo manager first for the fastest connection seems to fix any repos at may not be quite right.

    Got this error.

    I have also experienced this with one of the repo mirrors (can’t remember which). It is the fastest one but has sync problems. I opted to manually select one from a nearby country and use that one instead.

    Is their a reason why we use backports ?

    It was added after 19.1 release because a lot of people demanded the ewer Libreoffice from backports. anticapitalista added it but it is set as a very low preference, so normal package installation should always come from stable first. See the post here:
    https://antixlinux.com/buster-backports-repo-enabled/

    #43227
    Member
    Koo
    Helpful
    Up
    0
    :D

    @Xecure
    Thanks for your reply. The grub error was my fault have two drives in the laptop and was trying boot from the wrong one.
    Will manually adjust the repo.
    I installed libre office Version: 6.1.5.2 Build ID: 1:6.1.5-3+deb10u6 with backports on.

    T430 i7-3632QM 16gb , antiX-19.2.1-runit_x64-base Hannie Schaft 29 March 2020 , 5.8.16-antix.1-amd64-smp

    #43229
    Member
    Xecure
    Helpful
    Up
    0
    :D

    I installed libre office Version: 6.1.5.2 Build ID: 1:6.1.5-3+deb10u6 with backports on.

    That is the intended behavior. You can see that the announcement (https://antixlinux.com/buster-backports-repo-enabled/) says:

    By default, only apps that have already been installed from this repo will get updates […]
    If users install latest libreoffice via the package installer, it will download the version from buster-backports and any future updates from buster-backports automatically when upgrading.

    This means backports is enabled but you need to specify them if you want to download a package from them.
    Using the package installer, search for LO latest (that is the one from buster backports).
    If you want to manually update your librefoffice installation (if you used apt to install it and the packagename you installed was named libreoffice) to buster-backports, you can execute in terminal
    sudo apt -t buster-backports install libreoffice
    The repo and sources list world is very complicated. That is as far as I understand, and I may even be wrong on my interpretation of how it works.

    • This reply was modified 8 months, 1 week ago by Xecure. Reason: Fix some typos
    #43232
    Moderator
    BobC
    Helpful
    Up
    0
    :D

    I installed antiX 19.3 386 base on the old Dell 620 and it installed with no problems whatsoever.

    It also connected to WiFi on the first try by just left clicking the network monitor (2nd window to the left of the clock in the bottom status row), left clicking WiFi to turn it on, left clicking the Wireless tab, left clicking my router, clicking connect, typing in my WiFi password, and clicking Ok.

    Something I do on mine is to check for an internet connection in my IceWM startup, and if there isn’t any connection, I pop up the Connection Manager to prompt for a connection rather than expecting the user (who may not guess so well) try to guess where to click and figure out what to do.

    Here is the code that goes in ~/.icewm/startup

    # test internet connection and bring up connman if not connected
    # Give it a chance to connect, then test for connection
    sleep 3
    connected_addr=$(ip addr | grep "inet " | sed '/ scope host /d')
    if [ -z "$connected_addr" ]; then
       cmst -d &
    fi
    • This reply was modified 8 months, 1 week ago by BobC.
    #43233
    Moderator
    Brian Masinick
    Helpful
    Up
    0
    :D

    I chose the image antiX-19.3-runit_x64-full.iso to download…

    After trying out a few live logins using Frugal and Live, I installed the full runit X64 instance to a 23 GB partition at the end of my disk.
    It’s on partition 12; a previous antiX 19.2.1 runit instance is on partition 8, and a Base instance of the sysinitV scheduler is installed on partition 10. All of them are recognized through GRUB EFI, which is installed on MX Linux 19.2 on partition 3, and the EFI partition containing the /boot/efi directory is on partition 4; this works just as well on the latest instance as on the previous instances.

    I’ve been able to “trip” the live login by selecting a persistent or frugal state that conflicts with previously stored instances; that’s probably not “fair” or reasonable. I’ve not had any trouble at all using the system as intended with out feeding it things outside of the designed behavior.
    The installation went cleanly with no regressions in the installed functionality detected. My efforts have not been exhaustive, but they do indicate that the software is generally stable and of good quality.

    • This reply was modified 8 months, 1 week ago by Brian Masinick.

    Brian Masinick

    #43312
    Member
    xinomilo
    Helpful
    Up
    0
    :D

    I have also updated the Debian sid based net and core versions (sysvinit and runit, 32 and 64 arch).

    can’t see those in any mirror, can you confirm? (also, no torrents yet…).

    and a question about newest sid isos: are the errors from 19.2 release fixed?
    link: https://www.antixforum.com/forums/topic/antix-19-2-based-on-debian-sid-isos-available/#post-34395

    thanks for everyone’s work on newest antix 🙂

    #43314
    Forum Admin
    anticapitalista
    Helpful
    Up
    0
    :D

    Mirrors still haven’t synced, but they are available at Sourceforge.
    Still no torrents.

    Hmm, I’d forgotten about that bug report. Sorry about that.
    Not sure if the issue is fixed since I didn’t see (nor further test) the issue on my box.

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

    antiX with runit - leaner and meaner.

    #43366
    Member
    xinomilo
    Helpful
    Up
    0
    :D

    so, tried antiX-19.3-runit-sid_x64-core.iso in kvm/qemu :

    – no issues as in 19.2 release. probably newer kernel fixed those(?).
    – “toram” option reports the same error as written in 19.2 report..: “it would start copying-progress, then throw this: “bash: write error: Invalid argument”. then report copying to ram finished succesfully..”
    – cli-installer :
    1) missing partition-info package (not installed in iso)
    2) couldn’t install on vda1, stuck at: “Root partition : vda1 -> vda1 invalid Retry”. it seems cli-installer only works with hd*|sd* partitions. (maybe this is something to fix?). after manually changing script in driveCheck(), install proceeded normally.
    – there’s an error in shutting down iso, in runit. some unexpected operant “]” iirc, will have to look at it again..

    thx,

    #43370
    Forum Admin
    Dave
    Helpful
    Up
    0
    :D

    2) couldn’t install on vda1, stuck at: “Root partition : vda1 -> vda1 invalid Retry”. it seems cli-installer only works with hd*|sd* partitions. (maybe this is something to fix?). after manually changing script in driveCheck(), install proceeded normally.

    Yes not so long ago it was reported to only support hd[a-z][0-9].
    I had the same problem on my computer for the original release with nvme drives.
    I added the vd drive to the case statement. I am assuming the naming convention is the same as sd/hd drives.

    https://gitlab.com/antiX-Dave/cli-installer-antix/-/commit/84219726cce5fd51541ecdc6d7878117c1e476ad

    Are there any other drive name conventions that you know of?
    Currently have sd, hd, vd, mmcblk, nvme, and md.

    Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

    #43471
    Member
    xinomilo
    Helpful
    Up
    0
    :D

    Are there any other drive name conventions that you know of?
    Currently have sd, hd, vd, mmcblk, nvme, and md.

    not really. only use physical sata/ssd (sdX) and qemu virtual (vdX). ( haven’t seen hdX in years 🙂 )

    and thx for the super-fast fix in cli-installer-antix 🙂

    • This reply was modified 8 months ago by xinomilo.
    #43591
    Member
    namida12
    Helpful
    Up
    0
    :D

    I am guessing my kernel is newer than this new release?

    $ inxi -Fxz
    System:    Host: green615 Kernel: 4.19.100-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: IceWM 1.8.3 
               Distro: antiX-19.2-4.19_kernel_x64-full Hannie Schaft 6 April 2020 base: Debian GNU/Linux 10 (buster) 
    Machine:   Type: Desktop Mobo: ASRock model: B450M Pro4 serial: <filter> UEFI [Legacy]: American Megatrends v: P3.90 
               date: 12/09/2019 
    #43592
    Member
    ile
    Helpful
    Up
    0
    :D

    hello namida12 , No. Get a
    Newer than release, kernel
    https://antixlinux.com/fixed-bluez-security-vulnerabilities-kernels-available/

Viewing 15 posts - 16 through 30 (of 56 total)
  • You must be logged in to reply to this topic.