Antix 17.4.1 Qjackctl not working

Forum Forums Orphaned Posts antiX-17 “Heather Heyer, Helen Keller” Antix 17.4.1 Qjackctl not working

  • This topic has 8 replies, 4 voices, and was last updated Apr 7-7:46 pm by caprea.
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #19905
    Member
    jono

      Live-booted 17.4.1 freezes desktop after starting qjackctl. Only mouse cursor moves but no actions by clicking possible. I had tested previous Antix versions: same behaviour.

      #19906
      Anonymous
        Helpful
        Up
        0
        ::

        ok, thanks for the tip!

        .
        interpreted as a tip because…
        if your intent was a “help request”, you would have provided details useful toward troublshooting, right?

        #19909
        Moderator
        caprea
          Helpful
          Up
          0
          ::

          It’s a known problem ,just search for qjackctl in the search-box.
          Solution could be to compile it yourself from github , with the ./configure option ,
          mentioned in the github-issues-thread( scroll down )
          Maybe.
          https://www.antixforum.com/forums/topic/qjackctl-freezes-system/#post-12467

          #19912
          Moderator
          christophe
            Helpful
            Up
            0
            ::

            The only help I could find is:
            https://github.com/dnschneid/crouton/wiki/Access-audio-hardware-directly-(ALSA,-JACK)
            where it specifies settings for qjackctrl:
            “I found jack2 to be quite finicky with DBUS issues, so make sure you uncheck Enable DBUS Interface in Qjackctrl -> Setup -> Misc”

            Maybe this will help.

            confirmed antiX frugaler, since 2019

            #19996
            Member
            jono
              Helpful
              Up
              0
              ::

              AntiX 17.4.1 and MX 18.1 use the same version of qjackctl (0.4.4-1) but on MX it works.

              Analysis with ldd:

              AntiX loads additional libraries which likely cause the desktop freezing.

              (AntiX 17.4.1)
              >ldd /usr/bin/qjackctl

              linux-gate.so.1 (0xb7735000)
              libjack.so.0 => /usr/lib/i386-linux-gnu/libjack.so.0 (0xb75d6000)
              libasound.so.2 => /usr/lib/i386-linux-gnu/libasound.so.2 (0xb74b2000)
              libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xb7364000)
              libQt5X11Extras.so.5 => /usr/lib/i386-linux-gnu/libQt5X11Extras.so.5 (0xb735f000)
              libQt5Widgets.so.5 => /usr/lib/i386-linux-gnu/libQt5Widgets.so.5 (0xb6c51000)
              libQt5Gui.so.5 => /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5 (0xb66e3000)
              libQt5DBus.so.5 => /usr/lib/i386-linux-gnu/libQt5DBus.so.5 (0xb663b000)
              libQt5Xml.so.5 => /usr/lib/i386-linux-gnu/libQt5Xml.so.5 (0xb65f8000)
              libQt5Core.so.5 => /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 (0xb6111000)
              libGL.so.1 => /usr/lib/i386-linux-gnu/libGL.so.1 (0xb60a0000)
              libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb6081000)
              libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb5f07000)
              libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb5eb2000)
              libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb5e94000)
              libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb5cdc000)
              libopus.so.0 => /usr/lib/i386-linux-gnu/libopus.so.0 (0xb5c8a000)
              librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xb5c81000)`
              libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb5c7c000)
              /lib/ld-linux.so.2 (0xb7737000)
              libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xb5c50000)
              libharfbuzz.so.0 => /usr/lib/i386-linux-gnu/libharfbuzz.so.0 (0xb5bb3000)
              libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xb5b98000)
              libpng16.so.16 => /usr/lib/i386-linux-gnu/libpng16.so.16 (0xb5b5c000)
              libdbus-1.so.3 => /lib/i386-linux-gnu/libdbus-1.so.3 (0xb5b00000)
              libicui18n.so.57 => /usr/lib/i386-linux-gnu/libicui18n.so.57 (0xb5863000)
              libicuuc.so.57 => /usr/lib/i386-linux-gnu/libicuuc.so.57 (0xb56b5000)
              libpcre16.so.3 => /usr/lib/i386-linux-gnu/libpcre16.so.3 (0xb5648000)
              libdouble-conversion.so.1 => /usr/lib/i386-linux-gnu/libdouble-conversion.so.1 (0xb5633000)
              libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 (0xb5507000)
              libexpat.so.1 => /lib/i386-linux-gnu/libexpat.so.1 (0xb54dd000)
              libxcb-dri3.so.0 => /usr/lib/i386-linux-gnu/libxcb-dri3.so.0 (0xb54d9000)
              libxcb-present.so.0 => /usr/lib/i386-linux-gnu/libxcb-present.so.0 (0xb54d5000)
              libxcb-sync.so.1 => /usr/lib/i386-linux-gnu/libxcb-sync.so.1 (0xb54cb000)
              libxshmfence.so.1 => /usr/lib/i386-linux-gnu/libxshmfence.so.1 (0xb54c8000)
              libglapi.so.0 => /usr/lib/i386-linux-gnu/libglapi.so.0 (0xb54ac000)
              libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xb5497000)
              libXdamage.so.1 => /usr/lib/i386-linux-gnu/libXdamage.so.1 (0xb5493000)
              libXfixes.so.3 => /usr/lib/i386-linux-gnu/libXfixes.so.3 (0xb548c000)
              libX11-xcb.so.1 => /usr/lib/i386-linux-gnu/libX11-xcb.so.1 (0xb5489000)
              libxcb-glx.so.0 => /usr/lib/i386-linux-gnu/libxcb-glx.so.0 (0xb546c000)
              libxcb-dri2.so.0 => /usr/lib/i386-linux-gnu/libxcb-dri2.so.0 (0xb5466000)
              libXxf86vm.so.1 => /usr/lib/i386-linux-gnu/libXxf86vm.so.1 (0xb545f000)
              libdrm.so.2 => /usr/lib/i386-linux-gnu/libdrm.so.2 (0xb544d000)
              libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xb5447000)
              libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xb5440000)
              libfreetype.so.6 => /usr/lib/i386-linux-gnu/libfreetype.so.6 (0xb538c000)
              libgraphite2.so.3 => /usr/lib/i386-linux-gnu/libgraphite2.so.3 (0xb535d000)
              libicudata.so.57 => /usr/lib/i386-linux-gnu/libicudata.so.57 (0xb3adf000)
              libpcre.so.3 => /lib/i386-linux-gnu/libpcre.so.3 (0xb3a66000)
              libbsd.so.0 => /lib/i386-linux-gnu/libbsd.so.0 (0xb3a4a000)

              (MX 18.1)
              > ldd /usr/bin/qjackctl

              linux-gate.so.1 (0xb7f07000)
              libjack.so.0 => /usr/lib/i386-linux-gnu/libjack.so.0 (0xb7da3000)
              libasound.so.2 => /usr/lib/i386-linux-gnu/libasound.so.2 (0xb7c7f000)
              libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xb7b31000)
              libQt5X11Extras.so.5 => /usr/lib/i386-linux-gnu/libQt5X11Extras.so.5 (0xb7b2c000)
              libQt5Widgets.so.5 => /usr/lib/i386-linux-gnu/libQt5Widgets.so.5 (0xb741e000)
              libQt5Gui.so.5 => /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5 (0xb6eb0000)
              libQt5DBus.so.5 => /usr/lib/i386-linux-gnu/libQt5DBus.so.5 (0xb6e08000)
              libQt5Xml.so.5 => /usr/lib/i386-linux-gnu/libQt5Xml.so.5 (0xb6dc5000)
              libQt5Core.so.5 => /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 (0xb68de000)
              libGL.so.1 => /usr/lib/i386-linux-gnu/libGL.so.1 (0xb687a000)
              libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb685b000)
              libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb66e1000)
              libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb668c000)
              libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb666e000)
              libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb64b6000)
              libopus.so.0 => /usr/lib/i386-linux-gnu/libopus.so.0 (0xb6464000)
              librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xb645b000)
              libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb6456000)
              /lib/ld-linux.so.2 (0xb7f09000)
              libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xb642a000)
              libharfbuzz.so.0 => /usr/lib/i386-linux-gnu/libharfbuzz.so.0 (0xb638d000)
              libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xb6372000)
              libpng16.so.16 => /usr/lib/i386-linux-gnu/libpng16.so.16 (0xb6336000)
              libdbus-1.so.3 => /lib/i386-linux-gnu/libdbus-1.so.3 (0xb62da000)
              libicui18n.so.57 => /usr/lib/i386-linux-gnu/libicui18n.so.57 (0xb603d000)
              libicuuc.so.57 => /usr/lib/i386-linux-gnu/libicuuc.so.57 (0xb5e8f000)
              libpcre16.so.3 => /usr/lib/i386-linux-gnu/libpcre16.so.3 (0xb5e22000)
              libdouble-conversion.so.1 => /usr/lib/i386-linux-gnu/libdouble-conversion.so.1 (0xb5e0d000)
              libglib-2.0.so.0 => /usr/lib/i386-linux-gnu/libglib-2.0.so.0 (0xb5cdd000)
              libGLX.so.0 => /usr/lib/i386-linux-gnu/libGLX.so.0 (0xb5cba000)
              libGLdispatch.so.0 => /usr/lib/i386-linux-gnu/libGLdispatch.so.0 (0xb5c5a000)
              libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xb5c56000)
              libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xb5c4d000)
              libfreetype.so.6 => /usr/lib/i386-linux-gnu/libfreetype.so.6 (0xb5b90000)
              libgraphite2.so.3 => /usr/lib/i386-linux-gnu/libgraphite2.so.3 (0xb5b61000)
              libsystemd.so.0 => /lib/i386-linux-gnu/libsystemd.so.0 (0xb5ace000)
              libicudata.so.57 => /usr/lib/i386-linux-gnu/libicudata.so.57 (0xb4250000)
              libpcre.so.3 => /lib/i386-linux-gnu/libpcre.so.3 (0xb41d7000)
              libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xb41c2000)
              libbsd.so.0 => /lib/i386-linux-gnu/libbsd.so.0 (0xb41a6000)
              libselinux.so.1 => /lib/i386-linux-gnu/libselinux.so.1 (0xb4179000)
              liblzma.so.5 => /lib/i386-linux-gnu/liblzma.so.5 (0xb414d000)
              liblz4.so.1 => /usr/lib/i386-linux-gnu/liblz4.so.1 (0xb4138000)
              libgcrypt.so.20 => /lib/i386-linux-gnu/libgcrypt.so.20 (0xb4069000)
              libgpg-error.so.0 => /lib/i386-linux-gnu/libgpg-error.so.0 (0xb4052000)

              I conclude that qjackctl works differently on AntiX and MX – but it works correctly on MX!

              • This reply was modified 4 years, 1 month ago by jono.
              • This reply was modified 4 years, 1 month ago by jono.
              • This reply was modified 4 years, 1 month ago by jono.
              #20054
              Member
              jono
                Helpful
                Up
                0
                ::

                AntiX 17.4.1 and MX 18.1 use the same version of qjackctl (0.4.4-1) but on MX it works.

                Analysis with ldd:

                AntiX loads additional libraries which likely cause the desktop freezing.

                These are:

                libexpat.so.1 => /lib/i386-linux-gnu/libexpat.so.1 (0xb54dd000)
                libxcb-sync.so.1 => /usr/lib/i386-linux-gnu/libxcb-sync.so.1 (0xb54cb000)
                libxshmfence.so.1 => /usr/lib/i386-linux-gnu/libxshmfence.so.1 (0xb54c8000)
                libX11-xcb.so.1 => /usr/lib/i386-linux-gnu/libX11-xcb.so.1 (0xb5489000)
                libxcb-glx.so.0 => /usr/lib/i386-linux-gnu/libxcb-glx.so.0 (0xb546c000)

                #20071
                Moderator
                caprea
                  Helpful
                  Up
                  0
                  ::

                  OK. I got it installed and it doesn’t hang.
                  Following this issue-thread on github they mention the problem is related to the window-manager and the solution is to configure it with
                  ./configure –disable-xunique

                  https://github.com/rncbc/qjackctl/issues/13

                  So here’s what I did.
                  Installed with the package-installer ” QT5 Dev Enviroment “(under developement)
                  Installed with synaptic ” libjack-jackd2-dev ”

                  From jack on my system is installed
                  jack
                  jackd
                  jackd2
                  libjack-jackd2-0

                  Downloaded the qjackctl-0.5.6.tar.gz from this side
                  https://qjackctl.sourceforge.io/

                  Extracted the tar.gz, then went into the extracted folder qjackctl-0.5.6
                  There opened a terminal and typed
                  ./configure --disable-xunique

                  When done
                  make

                  afterwards
                  sudo make install

                  The qjackctl.desktop will get installed under /usr/local/share/applications and can be moved as a desktop-icon to the desktop.
                  To start it from terminal run /usr/local/bin/qjackctl

                  Probably the next version of qjackctl 0.5.7 will have a fix for the problem, but when the fixed version will appear in debian remains open.Even sid version is still 0.5.0

                  I am not experienced with qjackctl but it doesn’t freeze the desktop and seems running good.

                  Attachments:
                  #20217
                  Member
                  jono
                    Helpful
                    Up
                    0
                    ::

                    I was able to build a qjackctl with your instructions. But qjackctl starts with an error because it can’t find the audio ports.
                    Look at the added screenshot from what I’m getting when using qjackctl under MX.
                    Under AntiX there is nothing to choose from for the audio-ports. I only get fixed entries “default” for the Input- and Output-Device.

                    Attachments:
                    #20221
                    Moderator
                    caprea
                      Helpful
                      Up
                      0
                      ::

                      Yes, by default there is “default” as devices, but can you not type in there ? I can.
                      From the FAQ
                      http://jackaudio.org/faq/device_naming.html

                      I hope there will soon someone else participate here with more experience than mine with qjackctl

                    Viewing 9 posts - 1 through 9 (of 9 total)
                    • You must be logged in to reply to this topic.