Sway

Sway is a tiling Wayland compositor and a drop-in replacement for the i3 window manager. It works with your existing i3 configuration and supports most of i3's features, plus a few extras.

Prerequisites

• Internet connectivity, unless the packages have been pre-fetched into a local cache.
• Install appropriate Graphics driver drivers for your hardware. Without graphics drivers errors are likely to occur.
• A non-root user account.
• The community repositories must be enabled.
• Set up eudev.
• Wayland compositors need raw access to input and output devices, typically mediated by a seat manager. Either seatd or elogind work fine, but installing both leads to conflicts.

Tip: Except for the first two prerequisites, all of the others are automatically handled if the desktop is installed using the following setup-desktop script.

Setup-desktop

The setup-desktop command automates the Sway desktop installation with eudev and elogind.

# setup-desktop sway

Proceed to the Starting Sway section, as no display manager is being installed nor configured by the script that would boot into a graphical login screen.

Manual Installation

The installation steps below allow you to pick and choose various components for your Sway desktop.

Install Fonts

Install DejaVu fonts (font-dejavu), which have good Unicode coverage:

# apk add font-dejavu

Install Sway

# apk add sway \ xwayland \ # if you need the xserver foot \ # default terminal emulator. Modify $term in config for a different one. wmenu \ # default Wayland native menu for choosing program and screensharing monitor swaylock swaylockd \ # lockscreen tool swaybg \ # display wallpaper grim \ # screenshot tool wl-clipboard \ # clipboard management i3status \ # simple status bar swayidle # idle management (DPMS) daemon

For complimentary software alternatives, see Sway's wiki or Gentoo's wiki.

Configuration

Sway config File

Copy the default Sway configuration file to ~/.config/sway/config so that it can be customized as per each user's choices:

$ mkdir -p ~/.config/sway $ cp /etc/sway/config ~/.config/sway/

Read through it to learn the default keybindings. Sway's configuration is mostly backward compatible with that of i3's, and if you are looking for a solution for a specific issue, you could try checking whether it hasn't been provided for the i3 window manager.

Quickstart - config File

To set up an environment that launches applications full-sized and to Alt+Tab between these much as in XFCE or in various other desktop environments, then a quick setup of the config file could effect this. This proposed setup may be of benefit for both desktop/non-technical and technical use. Step 4 is indicated to be sidestepped by those electing an i3-style, tiled default layout.

A launchbar is not set up "out of the box", nor here, so this section only reviews essential keybindings (or "shortcuts"), saving first-time users from immediately requiring to digest a longer "cheatsheet" of keybindings that might include resizing, moving and swapping windows (called "views"), say, from smaller tiles (called "containers") into larger tiles; these may be learned at a later stage.

The quickstart configuration of the config file may be prepared within or without Sway e.g. within an Xorg session or another compositor, or on another installation, before eventually copying over the finished config file onto the target system – except:

• If one prefers alternative applications to those proposed initially in Step 6 for assignment into specific workspaces. Any such modifications (to be executed in Step 7) could be performed: (a) simply during one's first Sway session; or (b) by determining what those applications' app_id / class are (as detailed in Step 7), possibly in another Wayland session or externally e.g. from documentation.
• One will likewise require to verify at some point whether one's chosen applications are installed on the target system; and to install those missing (last step, Step 12).

Step 1: Assign the main modifier key. In a text editor, open the /home/username/.config/sway/config file that had been copied over. We will declare what would be the main modifier key for many of our keybindings: Window, Alt or otherwise. The config file has already set the main modifier, called the $mod key, to default as the Mod4 key, also known as the Window, Super or Logo key. Verify this towards the beginning of the file:

# Logo key. Use Mod1 for Alt.
set $mod Mod4

As proposed there, one could change that $mod key to be the Alt key a.k.a. the Mod1 key. To change the $mod key assignment, as with any line in this file, one could edit/delete the lines or comment such line out i.e. add a hashtag (#) at the start of any line that does not begin with a hashtag, so that such line would not be executed by Sway but would be left there for reference; and then enter the customised version of that line below it. Note that Sway does not support comments at the end of an executable line, following a hashtag.

According to the man 5 sway page, XKB modifier names can be used to refer to modifier keys, plus certain aliases found among the following list, all of these "codes" being acceptable for use throughout the configuration file:

• Mod1 - Alt - Alternatively expressed as Alt;
• Mod2 - Although not universally mapped, here it refers to the Num Lock key;
• Mod3 - It could be programmed, as an XKB modifier key;
• Mod4 - Alternatively expressed as the Super key, a.k.a. the Window or Logo key;
• Mod5 - AltGr;
• Lock - Caps Lock;
• Control - Ctrl - Alternatively expressed as Ctrl; and
• Shift - Shift.

It might be best not to use the Ctrl key as the main modifier, as it is often used in applications e.g. Control+c to copy, Control+b for bold, etc. Similarly when considering the Shift as main modifier.

So, if one were to choose, say, the Alt key as the main modifier, that Mod4 line could be changed to: set $mod Alt or set $mod Mod1. We will preserve the default, Mod4 (Window), as the main modifier. Note that any modification will not be manifested until one chooses at any time to reload the config file by hitting $mod+Shift+c (cf. Step 10).

Step 2: Declare what your default terminal and menu launcher will be. In this config file, these are currently configured to be the foot terminal; and wmenu, which supplies the wmenu-run command:

# Your preferred terminal emulator
set $term foot
# Your preferred application launcher
set $menu wmenu-run

You could leave these 'as is' if you are happy with these selections. Otherwise, substitute any of them.

A word to the wise regarding one's initial choice of terminal if not currently running Sway: if a different terminal were to be chosen, then one would not be able to Alt+Tab back and forth from a launched foot terminal into other opened workspaces unless that terminal's app_id / class could somehow be determined and specified by the user in Step 7. It may be more suitable therefore to leave foot as the default terminal until one of these could be determined once a Sway session is run, so that the terminal (foot) would land in a specified workspace when launched, and then easily Alt+Tab to and from it. Alternatively, one could left-click on the chosen terminal's workspace button on the top swaybar in order to switch to that workspace. (Note also that foot would already be installed if Sway had been installed using $ doas setup-desktop sway). On the other hand, if one is currently running Sway, then it is straightforward to change this default terminal choice here, if so wished; a tweak for the preferred terminal could be made in Step 7.

One's choice of menu launcher here is more flexible, regardless of the compositor/window manager currently being used, as the launcher will appear in any workspace currently displayed on-screen – a.k.a. the workspace in focus – using the keybinding declared in the following step (Step 3). Insert the preferred launcher's launch command here. For example, one may prefer rofi over wmenu; Alpine Linux's rofi port now supports Wayland, just as rofi's mainline version officially has since 2025. If so, that set $menu wmenu-run line could be changed as follows:

set $menu '/usr/bin/rofi -combi-modi run,drun,window,filebrowser -show combi -sort'

With that menu instruction, whenever rofi is launched using the keybinding reviewed in the next step, it would first offer a combi (combination) menu of all packages and of .desktop files that match the the command name while it is being typed in; alternatively, one could follows this on by hitting Control+Tab, which in turn would offer (a) a drun menu (a launcher strictly of .desktop files); (b) a listing of opened "window"/view selections; or (c) a simple filebrowser, etc.

A tally of the chosen packages is being kept for any required installation later.

Step 3: Choose key combinations to open the terminal and launcher and others. From the configuration file:

bindsym $mod+Return exec $term
[...]
bindsym $mod+d exec $menu

Modify these keybindings if so wished, which refer to the terminal and application launcher chosen in Step 2. Ensure that any different chosen key combination(s) has/have not already been assigned elsewhere in this config file. Make note of your chosen terminal and menu keybindings so as to know how to launch them later. As it stands:

• Window+Return for your terminal;
• Window+m for your menu launcher;

Substitute the Window key for your assigned $mod key, or with any other chosen combination that has not been used elsewhere in the configuration file.

Keybindings may also be made without requiring to define applications as variables that use the set instruction and the $ variable prefix. For example, having ensured that there was no previous binding for Control+Alt+w, one could add the following keybinding:

# LibreOffice Writer shortcut
bindsym Control+Alt+w exec '/usr/bin/libreoffice --writer'

Step 4: Applications to launch full-sized and in tabbed layout (Optional). At the beginning of the # Layout stuff: section, Consider inserting:

workspace_layout tabbed

Then, each launched application will launch full-sized. Each application will be named in a tab. If opting for a default tiled layout, this step is omitted. Tiling sends applications by default into tiles/"containers", splitting the screen, unless assigned to different workspaces in Steps 6-7. A further alternative would be: workspace_layout stacking.

Step 5: Focus when launched (Optional). Make Sway to immediately focus on any newly-opened application. At the end of the # Workspaces: section in this config file, consider adding:

for_window [app_id=.*] focus

This may be suitable to avoid having to navigate to its tab/workspace. It also ensures that dialog boxes such as "Open ..." and "Save as..." appear in the currently focused workspace.

Step 6: Assign workspaces. This is proposed for your most oftenly-used applications, so that most applications will land into different workspaces, and then one could Alt+Tab between those applications/workspaces.

Consider copying and pasting the following model in this same # Workspaces: passage. Customise each line for user preferences. These specify the app_id for various applications, including that of the keepassxc password vault, the lean corepad text editor and okular pdf viewer. Then, one finishes off each line with a chosen workspace number. (There may be no documented upper limit of workspaces, but one would need two keystrokes to move applications into two-digit workspaces if and when such keybindings were eventually learned and used.)

# APPLICATIONS TO APPEAR IN SPECIFIC WORKSPACES
 assign [app_id="foot"] 1
 assign [app_id="chromium"] 2
 assign [app_id="org.keepassxc.KeePassXC"] 3
 assign [app_id="cc.cubocore.CorePad"] 4
 assign [app_id="libreoffice-writer"] 5
 assign [app_id="libreoffice-calc"] 6
 assign [app_id="org.kde.okular"] 7
 assign [app_id="thunar"] 8

One could use workspace names instead of numbers, but then one would need to change their instances in the default config file. Some applications, not listed here, may require identification by their class name instead of by app_id – particularly, some that were originally designed for X11 (such as xterm) – see Step 6. Sway supplies the swaymsg command that could determine the app_id and/or class name of one's chosen applications.

Tip: The keepassxc password vault is assigned to appear in a different workspace than the chromium browser. After both are launched, then one would be able to Alt+Tab between the two workspaces to fetch/paste password data without engaging a browser password extension, if preferred.

If alternative applications are to be assigned workspaces, proceed to the next step.

Step 7: Assign alternative application choices for specific workspaces (Optional). This may require being run in a Sway session. If not currently running Sway, then consider conserving whichever part of the code block in Step 6 that is applicable for user purposes in the configuration file and resuming this Step 7 once the first Sway session is run.

This step may succeed alternatively in a different Wayland compositor provided that: (a) Sway or sway-bash-completion has been installed, seeing how either supply the required swaymsg command; or (b) one has a different means of determining the app_id / class of the alternative application(s).

1. Launch the alternative applications that are to be assigned to workspaces.
2. Run swaymsg -t get_tree | grep "app_id" in a terminal. The command examines metadata for your opened windows, and the result is then whittled down (or "grepped") to display app_id values. For example:

 $ swaymsg -t get_tree | grep "app_id"
                  "app_id": "Alacritty",
                  "app_id": "firefox-esr",
                  "app_id": "librewolf",
                  "app_id": "pavucontrol-qt",
                  "app_id": "featherpad",
                  "app_id": "audacious",
                  "app_id": "org.gnome.Epiphany",
                  "app_id": "org.qutebrowser.qutebrowser",

3. Plug the app_id values for any preferred applications into the assign listings code block above; end each line with a chosen workspace number.
4. In case any application name did not appear with an app_id, then it is possible that the application was originally designed for Xorg and has not been fully adapted for "pure Wayland": for example, xterm. In that case, one would need to determine what its class is instead: with xwayland installed and not disabled in Sway, launch xterm; then, in a terminal, run:

$ swaymsg -t get_tree | grep "class"
                    "class": "XTerm",

5. Determine the class values for the remainder of the preferred applications that required class identifiers instead of app_id and create lines for them in the assign code block above. For instance, for xterm to land in workspace 9, add a line to specify its class and its assigned workspace number:

    assign [class="XTerm"] 9
   

Step 8: Navigating between applications in different workspaces. Tell Sway what will be the chosen way to tab back through the workspaces that contain launched applications on a single monitor, say, Alt+Tab. In the # Moving around: passage, consider adding:-

bindsym Alt+Tab workspace prev_on_output
bindsym Super+Tab workspace next_on_output

We have additionally assigned Super+Tab to tab forwards through workspaces, in case that this could be useful to the user (optional).

As mentioned, one can alternatively focus a different workspace by left-clicking on its worskpace button in the swaybar.

Step 9: Navigating between applications within the same workspace. If two or more instances of the same application get launched (say, two instances of foot), then they will both appear in the same workspace that had been assigned to them, if any. In such case, Alt+Tab would not work to navigate between these because that keybinding navigates between applications being displayed in different workspaces. Instead, one may navigate between those two instances/tabs within that same workspace in three alternative ways; no edits need be done, but one may need to make note of these methods:-

• The default config file has already bound $mod+Left and $mod+Right to switch focus onto tabs shown to the left and right within the same workspace; in our setup, that would be Window+← and Window+→.
• The default config file has similarly bound $mod+$left and $mod+$right for these same commands; the $left and $right "key variables", along with two others, have been defined in a fashion that would be familiar to those using vim:

 set $left h
 set $down j
 set $up k
 set $right l 

Although the Left key (←) is distinct from the $left key (assigned here to be the h key), this config file has bound them both to enact the same action when combined with the $mod key, specifically, to move left through tabs in the same workspace (different users prefer alternative methods):

    bindsym $mod+$left focus left
 [...]
    bindsym $mod+Left focus left 

Similarly for the $right and Right keys.

• Alternatively, one could left-click on a tab to focus on a specific application instance, similarly to how one might click on taskbar items in other desktop environments.

Any applications that were not assigned into a workspace in the assign Steps 6-7 above will also launch into the workspace currently focused. In such cases, therefore, their tabs would be created in the current workspace too, and one could navigate between such applications, within that same workspace, using any way reviewed in this step also.

Step 10: Floating, dragging, tiling, fullscreen, etc.

• One may make a focused application to float, and to toggle "floating" off as-and-when needed, with: $mod+Shift+space . In our setup: Window+Shift+Space.

• The config file points out that one may "drag floating windows by holding down $mod and left mouse button". Seeing how $mod was kept assigned as the Window key: Window+drag. The window needs to be floating first; in some instances, one may need to drag at the tab.

• One could make some applications to launch "floating" by default (optional). An application that is sometimes made to float by default is the galculator calculator pad; just add:

for_window [app_id="galculator"] floating enable

• To toggle through tiled layouts within a workspace: $mod+e / Window+e

• To return to full-sized tabs i.e. window-sized after being in a tiled layout, yet not fullscreen, thereby retaining toolbars, etc: $mod+w / Window+w . Floating windows and fullscreen windows need to be toggled off first.

• To toggle in and out of fullscreen: $mod+f / Window+f

Take note of two final keybindings, or modify these first:

• To reload the Sway configuration file after editing it during a session: $mod+Shift+c / Window+Shift+c

• To exit Sway and the login session (save your work first): $mod+Shift+e / Window+Shift+e

Step 11: Add variables and autostart instructions. These could be added to the beginning of this config file. Typically, various environment variables would require being set before launching a Wayland compositor, for example, in ~/.profile . Do not add ampersands (&) at the end of each line in config, unlike with .xinitrc syntax in Xorg.

xwayland, if not required, can be disabled by inserting a line here to that effect. Alternatively, omit that line or comment it out by using a hashtag, as in the following example of autostart instructions, where Sway is assumed to have been launched using a dbus-run-session; gui runlevel is started now if PipeWire and associated services are being launched as user services; and where chromium is also autostarted:

exec dbus-update-activation-environment WAYLAND_DISPLAY DISPLAY XDG_CURRENT_DESKTOP=sway SWAYSOCK I3SOCK XCURSOR_SIZE XCURSOR_THEME
# xwayland disable
# Start gui runlevel for PipeWire and associated services to launch now
exec openrc -U gui
exec /usr/bin/chromium

Tip: Running "pure Wayland" – i.e. without the xwayland layer/package – may remove a possible attack surface. Xwayland could be required, however, to run certain Xorg-designed software, such as xterm. One may also investigate libreoffice and okular functionality.

Step 12: Install selected packages. Ensure that all mentioned applications have been installed: apk info -e package1 package2. Substitute entries in the following list with one's packages mentioned in the config file:

$ apk info -e foot wmenu chromium keepassxc corepad libreoffice okular thunar xterm galculator

wmenu was preserved for that listing; swap it out for rofi or otherwise, if necessary. One may have decided also not to include xterm, etc.

Install any application not appearing in the output of that instruction.

For additional information, start at man 5 sway and read the upstream wiki.

PipeWire and Screensharing

The Sway compositor has no involvement with audio playback. In order for screensharing to work, PipeWire is required. Therefore, installing PipeWire is recommended for audio playback too.

Since v3.22, Alpine Linux provides the necessary scripts to start PipeWire as a user service in OpenRC. Alternatively, PipeWire can be launched with Sway by adding the following line to Sway's config file:

exec /usr/libexec/pipewire-launcher

From a screensharing perspective, applications are split into two categories:-

• Those which use the native Wayland wlr-screencopy protocol
• Those which use the API from Flatpak's xdg-desktop-portal (this portal is also used by native non-Flatpak applications).

Applications in the first group require no additional setup. Applications in the second group (which include Firefox and Chromium) require setting up xdg portals in addition to PipeWire.

# apk add xdg-desktop-portal xdg-desktop-portal-wlr

If you are using a dbus-run-session wrapper to launch Sway, you will also need to set D-Bus variables in order for the portal and for screensharing features to work; add the following line to the beginning of Sway's config file:

exec dbus-update-activation-environment WAYLAND_DISPLAY DISPLAY XDG_CURRENT_DESKTOP SWAYSOCK I3SOCK XCURSOR_SIZE XCURSOR_THEME

The XDG_CURRENT_DESKTOP environment variable may be set by various methods, including:-

• by amending its mention in that dbus-update-activation-environment line, editing it to specify XDG_CURRENT_DESKTOP=sway ; or
• by exporting it from within an applicable environment configuration file, such as:

Contents of $XDG_CONFIG_HOME/.profile

export XDG_CURRENT_DESKTOP=sway

However, this method is not universal, as it would require resetting the XDG_CURRENT_DESKTOP variable for any different desktop/compositor/window manager that may be launched afterwards, possibly by employing a launcher similar to the wrapper script alternative described for Sway below; or

• by being set automatically by the display manager, as is commonplace, but none is supplied by Sway.

Screen Lock and suspend-to-RAM

Tip: For a seat manager-agnostic and DE-/WM-agnostic tool, consider installing the zzz utility, available in the community repository, or the powerctl utility from the testing repository, in order to manage suspend and hibernation.

Putting the system to sleep with the loginctl suspend command from Elogind requires elevated privileges or additional configuration.

To put the system to sleep after 600 seconds, use:

exec swayidle -w timeout 600 'doas /bin/loginctl suspend'

Do not lock the screen if program is running in full screen:

for_window [app_id="^.*"] inhibit_idle fullscreen

Todo: The option below, related to wayland-pipewire-idle-inhibit, needs to be tested. If you find the option below to be working, please remove this Todo.

If you do not want to lock the screen while media is being played through PipeWire, then install the wayland-pipewire-idle-inhibit package, and add the following to Sway's config file:

exec wayland-pipewire-idle-inhibit

Make changes to the ~/.config/wayland-pipewire-idle-inhibit/config.toml configuration file or to whichever configuration file you may have referenced instead through the --config <PATH>, if required, as per the project's website.

Elogind and swayidle

swayidle has integration with elogind, and it can handle before-sleep events.

If using swayidle before-sleep, then there will be a race condition, so that when you resume the computer from suspend, the screen will show the contents of the unlocked screen for a second before showing the actual lock screen. This can be a privacy concern.

To solve this issue, do the following.

Create the /etc/elogind/system-sleep/10-swaylock.sh file, and then add the following script to this file:

Contents of /etc/elogind/system-sleep/10-swaylock.sh

#!/bin/sh if [ "${1}" == "pre" ]; then touch /tmp/swaylock-sleep sleep 1 fi

Then set it to executable.

Later, once Sway is installed, add the following line to its config file:

exec touch /tmp/swaylock-sleep && inotifyd swaylock /tmp/swaylock-sleep

With this line, the screen will be promptly locked before suspend-to-RAM starts.

Brightness Control

Refer to Backlight for information on brightness control.

Output Scaling for High Resolution Displays

Without further configuration, program interfaces may be too small to use on high resolution displays.

Sway supports the per-display configuration of:-

• fractional (e.g. 1.5x); and
• integer scaling (e.g. 2x)

However, fractional scaling is discouraged due both to the performance impact and to the blurry output it produces. In this case, where 1x scaling is too small and 2x scaling is too large, program-specific GTK/QT-based toolkit scaling is recommended. See See below.

Scaling with wdisplays

To enable Sway scaling, the user can first preview different scaling factors with the wdisplays package. Note the output name (eDP-1, LVDS-1) and try apply scaling factors such as 1 and 2. To make changes permanent, add the following line, completed with your settings, to Sway's config file.

output <name> scale <factor>

Toolkit Scaling

To use toolkit scaling, say, at x2, add the following, for instance, to your ~/.profile:

# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
# or if still too small, use a custom DPI
export QT_WAYLAND_FORCE_DPI=192 # 2x scaling
export QT_QPA_PLATFORM="wayland-egl"

Notification Daemon

mako is a lightweight notification daemon that works seamlessly with Sway.

Screenshots

A simple tool that works well under Wayland is grimshot. Example keybindings:-

bindsym Print exec grimshot copy area
bindsym Shift+Print exec grimshot copy screen
bindsym Control+Print exec grimshot save area ~/Pictures/$(date +%d-%m-%Y-%H-%M-%S).png
bindsym Control+Shift+Print exec grimshot save screen ~/Pictures/$(date +%d-%m-%Y-%H-%M-%S).png

See Sway's wiki article for a listing of further screenshot tools.

Make Clipboard Content Persistent

By default, the clipboard content does not persist after terminating the program: if you copy some text from Firefox and then exit Firefox, then the copied text is also lost.

Install clipman from the community repo, and then add the following to Sway's config file:

exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"

Firefox Picture-in-Picture Mode/Floating Windows

Add this to your Sway configuration file (modify the numeric values to suit your needs and your display):

for_window [app_id="firefox" title="^Picture-in-Picture$"] floating enable, move position 877 450, sticky enable, border none

Start with NumLock Enabled

Add the following to your Sway config file:

input type:keyboard xkb_numlock enabled

Change mouse cursor theme and size

Add to your Sway config file:

seat seat0 xcursor_theme my_cursor_theme my_cursor_size

For example, set a mouse cursor using the GNOME Adwaita theme:

seat seat0 xcursor_theme Adwaita 16

You can inspect their values with echo $XCURSOR_SIZE and echo $XCURSOR_THEME. If reloading your configuration does not result in change, try logging out and in.

Note: Wayland allows for client-side cursors. It is possible that applications do not evaluate the values of $XCURSOR_SIZE and $XCURSOR_THEME.

Custom Keyboard Layout

To use a custom keyboard layout, just use:

input type:keyboard {
  xkb_file /path/to/my/custom/layout
}

Flatpaks

Main article: Flatpak

Due to their sandboxing, flatpaks require the use of a portal frontend (xdg-desktop-portal) and backends (such as xdg-desktop-portal-wlr, xdg-desktop-portal-gtk, xdg-desktop-portal-gnome) that implement the methods. When in doubt, install multiple backends. For more information on backends, see flatpak's page on the subject. In addition to the steps under the screensharing section, it may also be necessary to launch additional backends in your Sway config file. Otherwise, you may run into GDBus errors, as your flatpak fails to interface with the portal. This can cause issues such as with opening your file directories from a flatpak application.

After installing different backends, you might need to add the relevant backends to your Sway config file similar to those shown in the Firefox screensharing section above. For example, an autostart section in your Sway config file may include:

exec /usr/libexec/xdg-desktop-portal-gtk
exec /usr/libexec/xdg-desktop-portal-wlr
exec /usr/libexec/xdg-desktop-portal-gnome

These instructions are only needed if these backends are not started automatically via other means.

Starting Sway

Manually Launch Sway

You can launch Sway manually by issuing the sway command from a TTY.

$ sway

Tip: When using Wayland, for PipeWire and screensharing to work in Firefox and Chromium, a D-Bus is required. In the absence of a user service manager, consider running sway with dbus-run-session, a convenient wrapper that will explicitly export the path of the session bus.

$ dbus-run-session sway

Automatically Launch Sway on tty1

Adding the following lines to ~/.profile or to its equivalent will ensure that sway launches automatically, with a D-Bus, only from tty1. This is handy for troubleshooting, because if the Sway configuration ever falters, one could troubleshoot by logging into a different TTY (tty2-tty6), and your startup script then will not attempt to launch the faulty Sway environment from there also.

Contents of ~/.profile

... if [ "$(tty)" = "/dev/tty1" ]; then exec dbus-run-session sway fi ...

Using a Wrapper Script to Launch Sway

Instead of using ~/.profile or its equivalent file, a wrapper script can be placed at /usr/local/bin/sway-run. This script can be used to launch sway from either a TTY or by greetd, a lightweight display manager, as follows:

Contents of /usr/local/bin/sway-run

#!/bin/sh # Session export XDG_SESSION_TYPE=wayland export XDG_SESSION_DESKTOP=sway export XDG_CURRENT_DESKTOP=sway # Wayland stuff export MOZ_ENABLE_WAYLAND=1 export QT_QPA_PLATFORM=wayland export SDL_VIDEODRIVER=wayland export _JAVA_AWT_WM_NONREPARENTING=1 # Launch Sway with a D-Bus server exec dbus-run-session sway "$@"

Make the file executable:

# chmod +x /usr/local/bin/sway-run

Troubleshooting

If you encounter any issues, try running sway -Vc /etc/sway/config. It will run sway with the default config file and set the output to be more verbose. It is generally a good idea to track your configuration files with git (if and when you use a remote repository for them, keep it private, for security reasons).

To capture the Sway error log in a file for troubleshooting, replace sway in your startup file by:

sway -d 2> ~/sway_error.log

Alternatively, you can also issue the below command from TTY.

$ sway -d 2> ~/sway_error.log

Video Driver Issues

After installing Sway, and while launching it for the first time, a lack of appropriate video drivers may cause various error messages such as:

• "unable to create backend"
• "Failed to create renderer"

Install the necessary drivers in order for your graphics card to work with Sway.

XDG_RUNTIME_DIR is not set in the environment. Aborting

If seatd is used instead of elogind, the error message XDG_RUNTIME_DIR is not set in the environment. Aborting might be encountered.

Ensure that the mandatory steps outlined in the Seatd wiki page are completed in order to set the XDG_RUNTIME_DIR variable.

No backend was able to open a seat

If no seat manager is available, then the error below will appear.

[libseat] [libseat/libseat.c:73] libseat_open_seat : No backend was able to open a seat
[backend/session/libseat.c:102] Unable to create seat : Function not implemented
[backend/backend.c:303] Failed to open any DRM device
[sway/server.c:49] Unable to create backend

Ensure that either Elogind or Seatd is properly configured and running.

Firefox (Flatpak) and/or GTK Apps

Disappearing Cursor

You may need to get an icon pack and possibly a theme from Pling store and set GTK_THEME environmental variable. Alternatively, one could install an icon theme package for all users.

Missing file picker/cannot download

Go to about:config and set widget.use-xdg-desktop-portal.file-picker to 0.

Nvidia Issues

This material is work-in-progress ... This section is partly outdated and could benefit from contributions in view of Nvidia's current support of Wayland. Help is encouraged. (Last edited by John3-16 on 9 Oct 2025.)

Main article: NVIDIA

As of Dec 31 2022, Nvidia still doesn't fully support Wayland. Therefore, the possible solutions are as outlined in the link, or setting your WLR_BACKENDS environmental variables to drm,libinput or x11 (add libinput here as well if you cannot use your mouse and keyboard after starting Sway). The latter also works for AMD/ATI cards (make sure to install libinput first).

See also

• Sway Wiki
• Archwiki
• Gentoo Wiki
• PostmarketOS Wiki