Installing sway on antix

Forum Forums New users New Users and General Questions Installing sway on antix

  • This topic has 10 replies, 3 voices, and was last updated Nov 22-11:48 am by bbyfacekiller.
Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #124077
    Member
    bbyfacekiller

      Hello,

      I got a laptop from work 2 weeks ago which comes in with a super locked down version of Windows & BIOS.
      I made a persistent AntiX USB stick and was able to boot into it and use it at home.
      The laptop came with an integrated Intel video card and I noticed some screen tearing on Xorg, so I want to switch to Wayland.
      The tearing is gone when I use Gnome, but I don’t like it at all, so having used i3wm in the past, I want to give sway a shot.

      I installed sway but there is no way to select it from the login screen.
      Also, running sway from the terminal, I get this output:

      00:00:00.042 [wlr] [types/wlr_drm_lease_v1.c:705] No DRM backend supplied, failed to create wlr_drm_lease_v1_manager
      00:00:00.046 [sway/commands/output/background.c:122] Unable to access background file '/usr/share/backgrounds/sway/Sway_Wallpaper_Blue_1920x1080.png': No such file or directory
      00:00:00.059 [wlr] [xwayland/server.c:443] Cannot find Xwayland binary "/usr/bin/Xwayland"
      00:00:00.059 [sway/server.c:273] Failed to start Xwayland
      sh: 1: systemctl: not found
      dbus-update-activation-environment: error: unable to connect to D-Bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
      00:00:00.010 [swaybar/tray/tray.c:42] Failed to connect to user bus: No such file or directory
      

      I assume it has something to do with the init system not being systemd.
      Does anyone know a fix?

      #124094
      Member
      abc-nix
        Helpful
        Up
        0
        ::

        HI. I used sway on antiX before and I am currently running Hyprland, so I know that wayland works on antiX.

        The first issue is slimski (the login manager). I have yet to find a good way to start wayland-based compositors from this login manager, so I recommend trying a different-one (later, let us first get it to wor from terminal).

        Let’s explore this one issue at a time.

        1. What version/release of antiX? If possible, share the full system info with
        inxi -Faz
        It will also help with the following issue.

        2. The DRM issue

        00:00:00.042 [wlr] [types/wlr_drm_lease_v1.c:705] No DRM backend supplied, failed to create wlr_drm_lease_v1_manager

        Once we know the graphical device you are using (example, intel), you can install the drm related packages. For my system, I have: libdrm-intel1 and libdrm2. Check your graphics card and install the correct libdrm.

        3. Xwayland

        `00:00:00.059 [wlr] [xwayland/server.c:443] Cannot find Xwayland binary “/usr/bin/Xwayland”
        00:00:00.059 [sway/server.c:273] Failed to start Xwayland`

        Install xwayland
        sudo apt install xwayland
        it should also install other required packages.

        4. Edit your /home/.config/sway/config and change the wallpaper path

        00:00:00.046 [sway/commands/output/background.c:122] Unable to access background file ‘/usr/share/backgrounds/sway/Sway_Wallpaper_Blue_1920x1080.png’: No such file or directory

        After this, you should be able to start sway from the console with:
        dbus-run-session -- sway

        Once you get sway to work, we can explore other ways to make it start automatically.

        #124097
        Member
        bbyfacekiller
          Helpful
          Up
          0
          ::

          Hi, thanks a lot for your answer and for the help!

          These are my graphic card info:

          Graphics:
            Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Hewlett-Packard
              driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
              ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1
              bus-ID: 00:02.0 chip-ID: 8086:9a49 class-ID: 0300
          

          libdrm-intel1 and libdrm2 are already installed on my system, yet that error about DRM not being supplied is still there. 🙁

          xwayland is already installed.
          I changed the config file, it was in /etc/sway/config.

          I am able to start sway. Thank you. What suggestions do you have to start it automatically?

          #124098
          Member
          PPC
            Helpful
            Up
            0
            ::

            I noticed some screen tearing on Xorg, so I want to switch to Wayland.
            The tearing is gone when I use Gnome

            Not related to installing sway, but directly related to what you reported- probably Gnome does not have any screen tearing because it uses a compositor. antiX 23 includes a compositor (and a GUI to enable it). If you just enable the compositor, tearing should be gone, even on default antiX – it’s much faster and easier that installing a new Window Manager, not to mention Wayland.

            #124101
            Member
            bbyfacekiller
              Helpful
              Up
              0
              ::

              I noticed some screen tearing on Xorg, so I want to switch to Wayland.
              The tearing is gone when I use Gnome

              Not related to installing sway, but directly related to what you reported- probably Gnome does not have any screen tearing because it uses a compositor. antiX 23 includes a compositor (and a GUI to enable it). If you just enable the compositor, tearing should be gone, even on default antiX – it’s much faster and easier that installing a new Window Manager, not to mention Wayland.

              I did enable xcomp, and tried compton as well. It did not fix it. 🙁

              #124107
              Member
              abc-nix
                Helpful
                Up
                0
                ::

                There are many ways to reach sway from a login screen. I need to experiment with slimski still, so I recommend using a different login manager. I am using greetd, but there is no init file right now for it, so you can use sddm. If you are running the runit edition, I can share the runit service (be it for greetd or sddm).

                I use greetd, with no GUI (only TUI logging), and a hacked desktop-session script. I find desktop-session much better to setup some environment variables that sway doesn’t set on its own (like the xdg related variables, the display and WM variables and so).

                Try with sddm first (if you are using the sysvinit edition).Another option is setting autologin in runit (I cannot find the post to do the same on sysvinit right now) without a display manager (you would not use the startx command, and instead the same command you used to start it from the console).

                When I have some time I will explore how to do this for slimski, or try creating a init script for greetd.

                #124113
                Member
                bbyfacekiller
                  Helpful
                  Up
                  0
                  ::

                  Well, I tried ssdm to log in to sway, but dmenu and terminal are not functional.
                  I don’t have time to deal with this.
                  And Gnome is too big anyway for my 30mb/s pendrive (besides being ugly).

                  I don’t even know what to do.

                  #124126
                  Member
                  abc-nix
                    Helpful
                    Up
                    0
                    ::

                    dmenu only works with xorg-based systems or with xwayland enabled. And I don’t know what terminal you are using, but foot or kitty work on wayland natively (though I can get roxterm to also work with xwayland).

                    Getting sway to work is a big change. If you don’t have time now, leave it installed and explore it some other time.

                    You can improve screen tearind using the intel-xorg driver. See this post.

                    That should help for xorg (hopefully), but little by little xorg drivers will be phased out for the kernel drivers. I think they should still work right now though.

                    #124189
                    Member
                    bbyfacekiller
                      Helpful
                      Up
                      0
                      ::

                      dmenu only works with xorg-based systems or with xwayland enabled. And I don’t know what terminal you are using, but foot or kitty work on wayland natively (though I can get roxterm to also work with xwayland).

                      Getting sway to work is a big change. If you don’t have time now, leave it installed and explore it some other time.

                      You can improve screen tearind using the intel-xorg driver. See this post.

                      That should help for xorg (hopefully), but little by little xorg drivers will be phased out for the kernel drivers. I think they should still work right now though.

                      I managed to install bemenu instead of dmenu and got foot working on sway but thre are too many programs I use daily who do not run at all. I just purged it completely now.
                      Unfortunately, X doesn’t start with that config file for me. 🙁

                      Just tried i3 too. The tearing is so visible even when I fire up just one roxterm.

                      • This reply was modified 1 week, 3 days ago by bbyfacekiller.
                      #124194
                      Member
                      PPC
                        Helpful
                        Up
                        0
                        ::

                        You can improve screen tearind using the intel-xorg driver. See this post.

                        That should help for xorg (hopefully)

                        Did you try that, @bbyfacekiller?

                        In my experience (and I seldom had problems with screen tearing) the right graphical driver and a compositior solved all problems.

                        If you really want to use another UI, to check if it solves your screen tearing issues, Enlightenment works pretty well in antiX (I made a post about that recently). It’s light and looks great too (and in X)

                        P.

                        #124205
                        Member
                        bbyfacekiller
                          Helpful
                          Up
                          0
                          ::

                          You can improve screen tearind using the intel-xorg driver. See this post.

                          That should help for xorg (hopefully)

                          Did you try that, @bbyfacekiller?

                          In my experience (and I seldom had problems with screen tearing) the right graphical driver and a compositior solved all problems.

                          If you really want to use another UI, to check if it solves your screen tearing issues, Enlightenment works pretty well in antiX (I made a post about that recently). It’s light and looks great too (and in X)

                          P.

                          I did try it and X couldn’t start with that config file.

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