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

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

  • This topic has 300 replies, 26 voices, and was last updated May 2-2:26 pm by anticapitalista.
Viewing 15 posts - 286 through 300 (of 301 total)
  • Author
    Posts
  • #105127
    Member
    Robin
      Helpful
      Up
      0
      ::

      I found a way to reproduce this bug by reinstalling desktop-menu-antix.
      This changed all /usr/share/desktop-menu/.*/menu-applications to root;root ownership.

      That’s what I’d call a catch. Congrats! This explains how and when the permission change occurs.

      So we’ll apply a fix to desktop-menu-antix and whatever is used on antiX

      That’s great news. Many thanks @anticapitalista !

      I’ve just looked up the precise commit, where the respective fix was added:
      https://gitlab.com/antiX-Dave/desktop-menu-antix/-/merge_requests/7/diffs?diff_id=407608702&start_sha=7daa9bf4ce6e6c2a20483df78f4f42b117c5a9cd

      With this info it should be pretty easy to backport these few lines to the previous versions of desktop-menu, so all antiX versions currently being officially supported can get it.

      However, we still need to find out why the Applications sub-menu fails to show sometimes.

      Let me venture a guess: This might happen, if one of the .desktop files has a bug, causing the script to stall on its processing. Some of the original desktop files provided by some programs are pretty buggy, I had to fix a couple of them when processing for transifex translation. (Unfortunately I didn’t write down which ones.) Maybe the desktop-menu script chokes also on the bugs, so the update of menus is not completed then. For this to check we’d need to know precisely after which program installation it happened in each individual case. I guess, some info could be retrieved from the forum threads, but the limited search functionality available on the board currently wouldn’t allow to filter for this.

      Windows is like a submarine. Open a window and serious problems will start.

      #105153
      Member
      marcelocripe
        #105170
        Member
        Wallon
          Helpful
          Up
          0
          ::

          It’s great, we just got new packages with new translations and a new refresh menu (desktop-menu-antix). Thanks anticapitalista.

          
          2023-04-21  20:56:28  upgrade  yad-goodies-antix                       all    0.1.1                        0.1.2
          2023-04-21  20:56:27  upgrade  icewm-goodies-antix                     all    0.1.1                        0.1.2
          2023-04-21  20:56:21  upgrade  icewm-common                            amd64  3.3.3-1.0antix1              3.3.3-1.0antix2
          2023-04-21  20:56:20  upgrade  icewm                                   amd64  3.3.3-1.0antix1              3.3.3-1.0antix2
          2023-04-21  20:56:19  upgrade  desktop-menu-antix                      all    0.1.9                        0.1.10
          2023-04-21  20:56:15  upgrade  antix-user                              amd64  2023.04.09                   2023.04.16
          2023-04-21  12:36:11  install  antixscreenshot2                        all    <none>                       1.08e-antiXcommunity
          2023-04-21  11:53:56  upgrade  tlp                                     all    1.5.0-1                      1.5.0-2
          2023-04-21  11:53:55  upgrade  libgnutls30                             amd64  3.7.9-1                      3.7.9-2
          
          

          You can also see that I have installed the latest version of antixscreenshot2. I didn’t make a mistake on the Github site, I took the right version (1.08e).

          #105223
          Member
          marcelocripe
            Helpful
            Up
            0
            ::

            Another topic with problems related to displaying menus and .desktop files:

            https://www.antixforum.com/forums/topic/no-menu-application-after-update/

            #105330
            Member
            olsztyn
              Helpful
              Up
              0
              ::

              As a matter of caution in today’s upgrade of antiX 23:
              Avahi daemon components have been upgraded on Debian side, overriding antiX version if indiscriminate upgrade is performed. I suggest wait for anticapitalista to update antiX version before upgrading…

              Also just to remind: The chrony antiX version has not been updated to a working one as yet.
              I reported this previously but I have it uninstalled until a new antiX version appears… I am not sure I need it though. Currently not running ntpsec either…

              • This reply was modified 1 week, 2 days ago by olsztyn.

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

              #105405
              Member
              RJP
                Helpful
                Up
                0
                ::

                icewm-goodies-antix package is missing after the first update, so it must install manually after the first update.

                #105415
                Member
                calciumsodium
                  Helpful
                  Up
                  0
                  ::

                  System: antiX23 b1

                  In a previous post, I tried out the antiX wifi switch program from connman to ceni on a system with ethernet. Then I removed the dbus runit service. And that was it to switch from connman to ceni with ethernet. Ceni works good.

                  I found out that switching from connman to ceni with wifi was a little bit more involved.
                  But I was able to make it work.

                  1. Use the antiX wifi switch program from connman to ceni.
                  2. As root, remove the /etc/resolv.conf sym link.
                  3. Create a new sym link.
                  sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf
                  4. As root, edit the file /etc/network/interfaces and add the last four lines:

                  #------------------------------------------------------------------------------
                  # /etc/network/interfaces
                  #
                  # interfaces(5) file used by ifup(8) and ifdown(8)
                  # Used by ceni but not by connman
                  #------------------------------------------------------------------------------
                  
                  #auto lo
                  #iface lo inet loopback
                  auto wlan0
                  iface wlan0 inet dhcp
                  wpa-essid yourwifiname
                  wpa-psk yourwifipassword

                  You may have to adapt these lines to your particular system.

                  Notice: that I had to comment out the original last two lines in the original interfaces file.

                  5. Remove the dbus runit service using the runit service manager.
                  6. Reboot.

                  Notice: that I did not have to delete any connman programs or files.

                  Now, my b1 system whether with ethernet or with wifi only has the runit services: getty-tty1, getty-tty2, seatd, slimski, and udevd.

                  Attachments:
                  #105419
                  Member
                  Robin
                    Helpful
                    Up
                    0
                    ::

                    Then I removed the dbus runit service.

                    What side effect did you notice this step has on other programs which expect dbus service to be started? Would be great to know which programs actually need it and will fail without finding dbus service running. Did you see everything still work as before, or fail some functionality in some programs now?

                    Windows is like a submarine. Open a window and serious problems will start.

                    #105421
                    Member
                    calciumsodium
                      Helpful
                      Up
                      0
                      ::

                      q

                      What side effect did you notice this step has on other programs which expect dbus service to be started? Would be great to know which programs actually need it and will fail without finding dbus service running. Did you see everything still work as before, or fail some functionality in some programs now?

                      On my ethernet system where I have tested the longest without dbus, I do not see any negative effects on the video or sound quality in google-chrome or firefox-esr or mpv. The ethernet system is connected to the family tv. My family uses it all the time. They did not notice any difference before I switched to ceni from connman and removed dbus and afterwards. That is my experience.

                      @anticapitalista would have more experience and can give you a better answer because he has used this system all the way back to antiX19.

                      #105441
                      Member
                      RJP
                        Helpful
                        Up
                        0
                        ::

                        In Lenovo B575e alsa uses the wrong card so it must set manually by editing /etc/asound.conf file like unticking and editing defaults.pcm.card line as:

                        # Audio card/chip and device to use and control
                        # In most cases these settings should remain commented (#)
                        # When commented, card and device 0 are usually automatically selected
                        # When uncommented, the item corresponding to the number is selected
                        defaults.pcm.card 1
                        defaults.pcm.device 1
                        defaults.ctl.card 1
                        
                        • This reply was modified 1 week ago by RJP.
                        #105455
                        Member
                        calciumsodium
                          Helpful
                          Up
                          0
                          ::

                          What side effect did you notice this step has on other programs which expect dbus service to be started? Would be great to know which programs actually need it and will fail without finding dbus service running. Did you see everything still work as before, or fail some functionality in some programs now?

                          I went ahead and did a comparison with sysvinit.

                          I went back to my antiX21 and antiX19 sysvinit systems and switched the wifi from connman to ceni and removed dbus.

                          In my antiX21 system after the wifi switch and removing dbus, booting caused a boot “error” message that avahi did not start properly. But after boot, I did not see any performance change. So in startup services in control center, I disabled avahi and rebooted. This time, there was another “error” message saying that elogind did not start properly. But after boot, I did not see any noticeable performance issues. So I then also disabled elogind and rebooted. Booting did not show any error changes after dbus, avahi, and elogind were disabled. Moreover, I did not notice any performance changes in the usual programs that I normally run.

                          This may be an advantage of runit over sysvinit. In sysvinit, the various startup programs are more interconnected than in runit, in my experience.

                          In my antiX19 system, there was no avahi daemon in the startup service. But I removed elogind, and rebooted, and saw no noticeable performance issues.

                          This exercise was good for me because I realized that many startup services are not essential to what I normally do in my antiX systems. Instead of blindly accepting the defaults, I am starting to think a little bit more critically about specific startup services.

                          As an aside, switching wifi from connman to ceni in my antiX19 system was particularly great for me. I have been using ndiswrapper with connman in my antiX19 system. About 1 out of 2 times, there is a wifi connect failure after boot using connman with ndiswrapper driver. With ceni, the wifi connect is more robust. Although ceni wifi connect is noticeably slower in antiX19. Ceni wifi connect in antiX21 and antiX23 a1 and b1 are fast.

                          #105577
                          Member
                          RJP
                            Helpful
                            Up
                            0
                            ::

                            SEVERE BUG!

                            After last updates beta 23 does not execute os-prober so no one other system does not found in /boot/grub/grub.cfg file.

                            #105578
                            Forum Admin
                            anticapitalista
                              Helpful
                              Up
                              0
                              ::

                              Upstream grub change.
                              In /etc/default/grub add/uncomment
                              #GRUB_DISABLE_OS_PROBER=false

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

                              antiX with runit - leaner and meaner.

                              #105711
                              Member
                              calciumsodium
                                Helpful
                                Up
                                0
                                ::

                                Then I removed the dbus runit service.

                                What side effect did you notice this step has on other programs which expect dbus service to be started? Would be great to know which programs actually need it and will fail without finding dbus service running. Did you see everything still work as before, or fail some functionality in some programs now?

                                Another update:

                                On an INSTALLED antiX23 b1 system: works great with ceni for internet,with connman and dbus runit services removed.

                                Then I took an isosnapshot of the working installed system.
                                I then ran live of the isosnapshot.

                                It was bad!

                                First, during boot, I saw that internet interfaces failed. Once it was booted up, no internet as expected. When I launch roxterm, and everytime I launch roxterm, an error message related to dbus popped up.

                                I tried to launch runit-service-manager to try to add dbus runit service. But a pop up error says do I want to remember the password. I typed in the password, but the error message repeats in a loop. So I cannot add dbus in this live system.

                                I was wondering, why is it good with the installed system to remove dbus, but why is dbus absolutely essential for the live system?

                                #105845
                                Member
                                Wallon
                                  Helpful
                                  Up
                                  0
                                  ::

                                  To the team of developers,

                                  There is a bug in the antiX 23 iso.
                                  Two JWM themes are misplaced.
                                  They are in the /home/user/.jwm directory
                                  The names of the two files;
                                  theme.dark
                                  theme.light
                                  You can delete them because they are exactly the same themes.
                                  Furthermore, these two files correspond to the theme “black” which is in the correct directory /home/user/.jwm/themes.
                                  In short, there are 3 times the same theme under 3 different names.
                                  theme.dark = theme.light = black

                                  Kind regards,
                                  Wallon

                                Viewing 15 posts - 286 through 300 (of 301 total)
                                • You must be logged in to reply to this topic.