antiX-23-alpha1-runit-full (64bit) for testing

Forum Forums antiX-development Development antiX-23-alpha1-runit-full (64bit) for testing

Tagged: 

  • This topic has 436 replies, 24 voices, and was last updated Mar 21-8:50 pm by Brian Masinick.
Viewing 15 posts - 121 through 135 (of 437 total)
  • Author
    Posts
  • #99061
    Member
    stevesr0
      Helpful
      Up
      0
      ::

      Hi again,

      Just noticed that the message in the terminal “printout” of the .desktop-session/startup script notes that the bluez5-dbus object_manager_handler is trying to use the legacy bluez5 API for LE audio and only A2DP is supported. It calls for an upgrade of bluez5.

      Goodnight for now.

      stevesr0

      #99062
      Moderator
      christophe
        Helpful
        Up
        0
        ::

        I have the alpha 1 system running and it seems nearly perfect. Once the packages are solidified by debian, it seems that nearly everything will be set up. Bravo!
        Great work, and many thanks!

        confirmed antiX frugaler, since 2019

        #99066
        Moderator
        Brian Masinick
          Helpful
          Up
          0
          ::

          I have the alpha 1 system running and it seems nearly perfect. Once the packages are solidified by debian, it seems that nearly everything will be set up. Bravo!
          Great work, and many thanks!

          I agree!
          Imagine how much better it’ll be since the very first build is so useful and good looking too!

          --
          Brian Masinick

          #99069
          Member
          Xunzi_23
            Helpful
            Up
            0
            ::

            Thank you caprea for below links. Confirms my observations, a 5.18 kernel was in my case
            key to the presently running sid system. I did not mention the boot code, tried it but as
            the system crashed so early it was not relevant. Assumed you would see that in the screen
            pics, had to use phone for those.

            PPC many thanks, latest mount phone script works fine.

            https://forums.developer.nvidia.com/t/510-39-01-on-5-16-0-kernel-green-screen/200476
            https://forum.manjaro.org/t/green-screen-on-kde/62100/3

            @calciumsodium, I did try the rtl code, it made and installed ok but kernel or modules
            build still failing. Needs some parameter change it seems.

            As the issue is going to be widespread it really needs a fix for the distro.
            Nvidia was pretty much the gold standard for many years and much of the hardware is still
            running well. Core duo reported by sasa is still in daily usage in many thousands of
            devices probably hundreds of thousands. With an ssd and memory upgrade fine for daily private
            and office usage.

            • This reply was modified 3 months ago by Xunzi_23.
            #99071
            Member
            sasa_
              Helpful
              Up
              0
              ::

              Core duo reported by sasa is still in daily usage in many thousands of
              devices probably hundreds of thousands. With an ssd and memory upgrade fine for daily private
              and office usage.

              The PC is very old, 13-14 years old. antiX 19, antiX 21, Slackware 15, Salix 15, wattOS 12, work great on old hardware.antiX 19, Slackware 15 and Salix 15 even support the proprietary 340.xxx driver for the nvidia GS 8400 graphics card. With the mentioned editions, it will work for a long time.

              #99074
              Member
              Xunzi_23
                Helpful
                Up
                0
                ::

                @sasa
                Regarding the pc is very old, in many countrys the device would be a coveted posession.
                Here in germany for many poorer familys too. Devices with the socket 775 core 2 duo were still
                on sale new about 6 years ago. Production start of newer CPU was 2008 to 2010.

                The computer I am writing with now is green screening on the alpha, it runs fine with fully
                updated sid and a change of kernel. It is I5 and will run all day at 4500Mhz. ie, not
                energy efficient but Fast trouble free and recently updated to semi passive cooling.

                When a kernel build and maybe minor parameter change reportedly fixes the issue without much
                effort my personal opinion is that is desireable. When users get a green screen crash but other
                distros boot fine the user reaction is call antiX crap. It is not.

                • This reply was modified 3 months ago by Xunzi_23.
                #99076
                Member
                PPC
                  Helpful
                  Up
                  0
                  ::

                  I’m not sure if this was a antix23a1 bug- I was running the live system from usb and inserted a pen-drive- zzzfm popped up instantly (very, very nice).
                  I copied what I wanted to copy to that pendrive and tried to eject it using zzzfm – that failed with a message stating the drive was busy.
                  I tried antiX’s usb ejector – it did not ask for the password (as it does on antiX 22, and that was good) but, in the default look of the window I could not find the check box that I needed to click to confirm what drive I wanted to unmount. I was in a hurry, and since I was certain the drive was not busy, I just unplugged it.

                  @anticapitalista – someone else reported, like I did that since new zzzfm bookmarks are not localized (by this I mean both the bookmark name that shows up on zzzfm left column but mainly the path it points to) and so, do not work when the system local is not English – the best way I can think of to take care of that is running a mini script, when the user boots into antiX Live, that using “sed”, would replace both the bookmarks names and their paths. This would work localizing also the “Recent files” bookmark name, I guess.
                  Do you want me to strip down my ft10-zzzfm script to do that – it would solve that problem, leaving you free to worry about more important stuff…

                  P.

                  #99078
                  Member
                  mcpderez
                    Helpful
                    Up
                    0
                    ::

                    Time Format (IceWM for sure, possibly others). This is not new with AntiX-23. It has been present since at least AntiX-19. I’m not sure if MX might be affected by this gazelle-installer implementation as well.

                    The IceWM (and perhaps others) Time Format is not respecting the selection made in gazelle-installer, because the way this is implemented in gazelle-installer/oobe.cpp by doing a find and replace with sed but the original string that is meant to be replaced is not present in the IceWM file in /etc/skel.

                    gazelle-installer/oobe.cpp lines 438-441 [for the 12-hour clock case]:

                    
                            //antix systems
                            proc.shell("sed -i 's/%H:%M/%l:%M/g' " + skelpath + "/.icewm/preferences");
                            proc.shell("sed -i 's/%k:%M/%l:%M/g' " + skelpath + "/.fluxbox/init");
                            proc.shell("sed -i 's/%k:%M/%l:%M/g' " + skelpath + "/.jwm/tray");

                    gazelle-installer/oobe.cpp lines 457-460 [for the 24-hour clock case]:

                            //antix systems
                            proc.shell("sed -i 's/%H:%M/%H:%M/g' " + skelpath + "/.icewm/preferences");
                            proc.shell("sed -i 's/%k:%M/%k:%M/g' " + skelpath + "/.fluxbox/init");
                            proc.shell("sed -i 's/%k:%M/%k:%M/g' " + skelpath + "/.jwm/tray");

                    Lines 639-641 of /etc/skel/.icewm/preferences (after the 24-hour selection has been run on it with the installer. Note it is commented out, but shouldn’t be.

                    #  Clock Time format (strftime format string)
                    #TimeFormat="%a %m/%d %l:%M" #US format?
                    #TimeFormat="%I:%M" #UK format?
                    #99080
                    Forum Admin
                    anticapitalista
                      Helpful
                      Up
                      0
                      ::

                      Re- localisation of zzzFM folders and trash entry.
                      Anyone know how to do this so that on live boot the folders in Bookmarks do become automatically localized with no input from user 9as is the case with rox-icewm for example.

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

                      antiX with runit - leaner and meaner.

                      #99097
                      Member
                      PPC
                        Helpful
                        Up
                        0
                        ::

                        @anticapitalista:

                        Re-localisation of zzzFM folders can be easily done, if a script like this can be run before loading the desktop (because zzzfm can’t be running when edits to it’s config files are being done, and, by default zzzfm is being used to run desktop icons:

                        #!/bin/bash
                        targetfile=~/.config/zzzfm/session
                        
                        #localize Downloads Bookmark and path
                        downloads_label=$(echo $XDG_DOWNLOAD_DIR| cut -d/ -f4)
                        sed -i "s/cstm_6c99bdd2-label=.*/cstm_6c99bdd2-label=$downloads_label/g"  $targetfile
                        sed -i "s|cstm_6c99bdd2-z=.*|cstm_6c99bdd2-z=$HOME/$downloads_label|g"  $targetfile
                        
                        #localize Documents Bookmark and path
                        documents_label=$(echo $XDG_DOCUMENTS_DIR| cut -d/ -f4)
                        sed -i "s/cstm_1f966a72-label=.*/cstm_1f966a72-label=$documents_label/g"  $targetfile
                        sed -i "s|cstm_1f966a72-z=.*|cstm_1f966a72-z=$HOME/$documents_label|g"  $targetfile
                        
                        #Pictures
                        documents_label=$(echo $XDG_PICTURES_DIR| cut -d/ -f4)
                        sed -i "s/cstm_23f8698b-label=.*/cstm_23f8698b-label=$documents_label/g"  $targetfile
                        sed -i "s|cstm_23f8698b-z=.*|cstm_23f8698b-z=$HOME/$documents_label|g"  $targetfile

                        Note: it’s missing the localization of the “Videos” folder and bookmark, but I guess you saw how it’s done.

                        Note2: doing this, I noticed that there’s no bookmark to one of the default folder’s: “Music” was that by design?

                        Adding localization of “home”, “trash” and “recent files” bookmarks is a bit trickier… I’ll try to add it here soon…

                        Edit: anyone wanting to run this script to test localization of zzzfm’s bookmarks: just add this line to the start of the script:
                        pkill zzzfm && slep 0.5

                        This ensures zzzfm is not running (note: desktop icons will disapear for the session, if you do this)

                        P.

                        • This reply was modified 3 months ago by PPC.
                        #99099
                        Forum Admin
                        dolphin_oracle
                          Helpful
                          Up
                          1
                          ::

                          Re- localisation of zzzFM folders and trash entry.
                          Anyone know how to do this so that on live boot the folders in Bookmarks do become automatically localized with no input from user 9as is the case with rox-icewm for example.

                          if the bookmark can do text expansion and run a command, can you use xdg-user-dir FOLDER

                          $ xdg-user-dir DOWNLOAD
                          /home/dolphin/Downloads
                          

                          so something like this in a bookmark

                          $(xdg-user-dir DOWNLOAD)

                          alternately you could on first login update the bookmarks with a script.

                          • This reply was modified 3 months ago by dolphin_oracle.
                          • This reply was modified 3 months ago by dolphin_oracle.
                          • This reply was modified 3 months ago by dolphin_oracle.
                          #99104
                          Member
                          PPC
                            Helpful
                            Up
                            1
                            ::

                            alternately you could on first login update the bookmarks with a script.

                            That’s my proposal, D.O.

                            I tested adding the script to icewm’s startup file and it worked perfectly. Updated version, that also localizes the “Videos” folder:

                            #!/bin/bash
                            #Script to ensure that zzzFM has localized bookmarks
                            
                            targetfile=~/.config/zzzfm/session
                            #Localize Downloads Bookmark and path
                            label=$(echo $XDG_DOWNLOAD_DIR| cut -d/ -f4)
                            sed -i "s/cstm_6c99bdd2-label=.*/cstm_6c99bdd2-label=$label/g"  $targetfile
                            sed -i "s|cstm_6c99bdd2-z=.*|cstm_6c99bdd2-z=$HOME/$label|g"  $targetfile
                            
                            #Localize Documents Bookmark and path
                            label=$(echo $XDG_DOCUMENTS_DIR| cut -d/ -f4)
                            sed -i "s/cstm_1f966a72-label=.*/cstm_1f966a72-label=$label/g"  $targetfile
                            sed -i "s|cstm_1f966a72-z=.*|cstm_1f966a72-z=$HOME/$label|g"  $targetfile
                            
                            #Localize Pictures Bookmark and path
                            label=$(echo $XDG_PICTURES_DIR| cut -d/ -f4)
                            sed -i "s/cstm_23f8698b-label=.*/cstm_23f8698b-label=$label/g"  $targetfile
                            sed -i "s|cstm_23f8698b-z=.*|cstm_23f8698b-z=$HOME/$label|g"  $targetfile
                            
                            #Localize Videos Bookmark and path
                            label=$(echo $XDG_VIDEOS_DIR| cut -d/ -f4)
                            sed -i "s/cstm_3be1d265-label=.*/cstm_3be1d265-label=$label/g"  $targetfile
                            sed -i "s|cstm_3be1d265-z=.*|cstm_3be1d265-z=$HOME/$label|g"  $targetfile
                            • This reply was modified 3 months ago by PPC.
                            #99106
                            Member
                            PPC
                              Helpful
                              Up
                              0
                              ::

                              To be able to localize Trash related entries (bookmark and contextual menu entries), it will be necessary to use localization files.
                              The 2 variables at the start of this proposed part of the script are marked as localizable. This should be added to the end of the previous script (I suggest adding all variables to the start of the finished script, for easier localization:

                              #Localize Trash related entries 
                              trash_label=$"Trash"
                              trash_menu_entry=$"Send to Trash" 
                              restore_menu_entry=$"Restore" 
                              #Trash bookmark
                              sed -i "s/cstm_3ca29516-label=.*/cstm_3ca29516-label=$trash_label/g"  $targetfile
                              #Send to Trash contextual menu entry
                              sed -i "s/cstm_25a291d5-label=.*/cstm_25a291d5-label=$trash_menu_entry/g"  $targetfile
                              #Restore from Trash contextual menu entry
                              sed -i "s/cstm_2b015761-label=.*/cstm_2b015761-label=$restore_menu_entry/g"  $targetfile
                              #99107
                              Member
                              PPC
                                Helpful
                                Up
                                0
                                ::

                                Localization of the “home” folder:

                                #localize Home bookmark:
                                TEXTDOMAINDIR=/usr/share/locale
                                TEXTDOMAIN=zzzfm
                                homie=$"Home"
                                sed -i "s/cstm_2b7f3cb1-label=.*/cstm_2b7f3cb1-label=$homie/g"  $targetfile
                                #99108
                                Member
                                olsztyn
                                  Helpful
                                  Up
                                  0
                                  ::

                                  @olsztyn, on antiX full there is already everything installed you need for bluetooth in general.
                                  For pipewire install
                                  pipewire
                                  wireplumber
                                  gstreamer1.0-pipewire
                                  libspa-0.2-bluetooth
                                  pipewire-audio-client-libraries
                                  pavucontrol
                                  pipewire-pulse

                                  Thanks again @caprea for detals (as well as thanks to dolphin_oracle, stevesr0 and anticapitalista for additional thoughts).
                                  Starting with new baseline production system (antiX SID Full/Bookworm SID), which looks like equivalent to antiX 23 alpha, except my baseline system does not include libelogind0.
                                  Problem seems to be that installing pipewire components appears to entail installation of libelogind0, and this is what I am trying to avoid. Installing pipewire components first and then removing libelogind0 does not seem to work too well. My system is completely *elogind*-free, consistent, and I want to keep this way.
                                  Is there a solution to install minimum pipewire components and not let libelogind0 slip in?

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

                                Viewing 15 posts - 121 through 135 (of 437 total)
                                • You must be logged in to reply to this topic.