I am running Sway on Fedora 26 and want my laptop to be locked when I close my screen. I changed HandleLidSwitch to lock in /etc/systemd/logind.conf and ran systemctl restart systemd-logind after that. However, closing the lid does nothing. The lock program I intend to use is Swaylock and I can manually call it by runnig the command swaylock in a terminal. How do I make Systemd call swaylock when it tries to close the screen (as instructed to do in logind.conf)?

I have the same problem like: - How do I run the same linux command in more than one tab/shell simultaneously? But for sway containers, not just a terminal emulator. For example, having three instances of a browser in a workspace and sending input through keystrokes to all of them simultaneously. Maybe something like an option to focus on multiple containers at the same time? Is there any way to achieve this?

One thing I like about GNOME, KDE, and other desktops is that I can click and drag to make a selection box on the desktop: (Image from [this question](https://askubuntu.com/questions/1258027/where-in-a-theme-is-the-selection-box-color-for-the-desktop-for-ubuntu-20-04) on Ask Ubuntu.) Apparently this is called [rubber-band selecting](https://web.archive.org/web/20200811041619/https://www.peachpit.com/articles/article.aspx?p=598654&seqNum=6) . I rarely use this for its intended purpose (selecting icons), but I fidget with this rectangle all the time. If you move it really fast in a circle around the point where you clicked, it almost draws a +. Can I replicate this in the sway window manager? There would be nothing to select; I just want the rectangle on top of my wallpaper that I can play with.

I'm pretty new to Linux. I'm using Debian 12 on a laptop (and a dock) with the SwayWM wayland compositor. I have 2 external monitors connected to the dock, one landscape (DVI) monitor and another portrait (VGA) monitor. How could I: - Change the arrangement and rotation of the monitors - Set the background of any monitor to an image - Have persistence of everything when I undock and dock again Using Xubuntu, I can easily do everything using Xfce4 Display Settings and xfdesktop. But how do I do the aforementioned in Sway? (I don't need a GUI though since I'm rarely gonna change anything) Any advice would be appreciated. Thanks in advance.

I have an external monitor connected to a thunderbolt dock which I would like to utilize. For whatever reason, the monitor appears to be recognized by the system but fails to display anything. - I can confirm that the cable and monitor are fine, as it works perfectly when booted into Windows - The thunderbolt dock seems to not be the issue, as USB peripherals are working fine - Running swaymsg -t get_outputs shows the built in monitor as eDP-1 and the external monitor as DP-2. There is no indication here that the second monitor would not be working. - Running wdisplays shows a preview of what the second display should look like, so evidently the system is rendering what is meant to be sent to the monitor - When I reboot the machine, the tty output is mirrored onto the second monitor. So evidently it is recognized. - There are no errors in sway --debug - There are no entries in dmesg which appear related to the issue - Running lspci -k | grep -A 4 VGA shows that the video driver is loaded

00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07)
	DeviceName:  Onboard IGD
	Subsystem: Hewlett-Packard Company Device 86f9
	Kernel driver in use: i915
	Kernel modules: i915

- I have set the environment variable WLR_DRM_NO_MODIFIERS=1 as has been recommended to solve related issues - I have attempted to install other versions of wlroots to no avail, though I honestly don't know whether this would be expected to fix the problem. - While the refresh rate is very bad during normal use (hence why I am attempting this method), I can successfully use this monitor with an external Nvidia RTX 2060 GPU, connected via thunderbolt 3, with the the noveau driver. I don't really have a sense of how to best approach troubleshooting this problem, so any advice would be appreciated! If there is any additional information that would be relevant, I am more than happy to provide it. System information: - OS: Manjaro 21.1.6 Pahvo - WM: sway 1.6.1 - wlroots 0.14.1-2

I will have soon a setup, where my desktop has an integrated and a dedicated graphics card, both AMD, and I already searched but didn't find any good answer in how the multi-GPU setup works. I would like to have a setup where I primarily use my integrated graphics card and can select the GPU for the starting application with an environment variable, similar to primusrun from NVIDIA. I've read that you can use the environment variable WLR_DRM_DEVICES so the first device will be used for rendering and copied to the other graphics cards. But is it possible that you can select another GPU on the fly for more computation intensive applications like games? Another thing I've read that it manages this automatically with GBM, but then again, how am I able to choose which GPU to use? Background information: I'm getting a new CPU which I chose to have integrated graphics, so I have 2 renderable devices. Reason is I want to be able to unplug my dedicated graphics card in software, so I can use it for my Windows VM setup via PCI passthrough, if applications (games in particular) don't work with wine. Before anyone mentions dual os setup, I already have this, but it's extremely annoying if you have to reboot the system to change the OS, especially if you're talking with someone over Discord, Teamspeak, etc. TL;DR: How does multi-GPU setup in sway work?

am using Fedora 41 with sway 1.10.1 with 2 monitors (2560x1080@60Hz 1920x1080@60Hz). After a while I get logged out of sway session randomly meanwhile my gnome session works fine. I am fairly new to linux, system programming, not able to understand the logs mentioned below to debug the issue. Summary: The program terminated with signal 11, a segmentation fault, due to IPC connection failure. Sway is opensource, the error line is shown as swaybar/bar.c:465 saying some kind of polling error on display output. The question is why is the Wayland failing to poll for monitors middle of the Sway session while everything works fine for GNOME session. error [tag:swaybar/bar.c:465] Wayland display poll error. Source code : https://github.com/swaywm/sway/blob/master/swaybar/bar.c Following are sequence of logs. journalctl | grep -ie sway

Feb 12 21:27:10 fedora kernel: nouveau 0000:07:00.0: fifo:c00000:0006:0030:[sway] errored - disabling channel
Feb 12 21:27:10 fedora kernel: nouveau 0000:07:00.0: sway: channel 48 killed!
Feb 12 21:27:10 fedora kernel: sway: segfault at 55c000000000 ip 00007f0c82664e9f sp 00007fff9fcab130 error 4 in libgallium-24.3.4.so[a64e9f,7f0c81c01000+1a4a000] likely on CPU 15 (core 7, socket 0)
Feb 12 21:27:10 fedora audit: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=8 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=127631 comm="sway" exe="/usr/bin/sway" sig=11 res=1
Feb 12 21:27:10 fedora systemd-coredump: Process 127631 (sway) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Feb 12 21:27:13 fedora systemd-coredump: Process 127631 (sway) of user 1000 dumped core.
                                                 Module sway from rpm sway-1.10.1-1.fc41.x86_64
                                                 #12 0x000055b2d98bf2be output_repaint_timer_handler.part.0 (sway + 0x172be)
                                                 #13 0x000055b2d98bf52e handle_frame (sway + 0x1752e)
                                                 #20 0x000055b2d98b0446 main (sway + 0x8446)
                                                 #23 0x000055b2d98b0905 _start (sway + 0x8905)
Feb 12 21:27:13 fedora /usr/libexec/gdm-wayland-session: [ERROR] [swaybar/bar.c:465] Wayland display poll error
Feb 12 21:27:13 fedora /usr/libexec/gdm-wayland-session: ERROR:assign-cgroups:Sway IPC connection error:
Feb 12 21:27:13 fedora systemd: Stopped target sway-session.target - Sway session.
Feb 12 21:27:13 fedora systemd: Reached target sway-session-shutdown.target - Shutdown running Sway session.
Feb 12 21:27:13 fedora systemd: Stopped target sway-session-shutdown.target - Shutdown running Sway session.
Feb 12 21:27:15 fedora abrt-notification: Process 12660 (sway) crashed in pushbuf_dump()
Feb 12 21:27:31 fedora systemd: Reached target sway-session.target - Sway session.

Let me know if any additional info is required.

Under X, I can make Caps Lock behave as Esc when pressed briefly, but as Ctrl when held down with: setxkbmap -option 'caps:ctrl_modifier' xcape -e 'Caps_Lock=Escape' -t 100 How can I replicate this behavior under Sway / Wayland?

It seems that Sway is not setting WAYLAND_DISPLAY, which is causing wl-clipboard to not work. I start sway from .zlogin like this:

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

I don't know what else might be relevant. I'm using Void Linux with elogind.

I've recently had Sway WM stop working on my Lenovo ThinkPad T490 with Debian 12 Bookworm. I suspect the issue was my having done an apt upgrade which may have moved some low-level packages causing the break. * Previously, sway would work just fine - I'd log into my account with command line, type in sway and the window manager would start up. * Now when I type sway I get

[wlr] [backend/backend.c:217] Found 0 GPUs, cannot create backed
    [wlr] [backend/backend.c:386] Failed to open  any DRM device
    [sway/server.c:56] Unable to create backend

* I've tried

-sh
    sudo apt remove sway
    sudo apt install sway

but the problem persists. Any ideas on how to fix this and get Sway working again?

I have switched from i3 to Wayland and everything works fine except for a script I wrote some time back. The script uses i3-msg to focus on a window via it's class name or id (from i3-msg tree). Sway has the command swaymsg -t get_tree which does the same thing as in i3. With the command I can extract the id, app_id, window, pid or any other data from the command line with the command

swaymsg -t get_tree | jq -c -r '..|try select(.focused == true) | [.id]' | tr -d "[]"

(Depending on the attribute, .id will of course be replaced by the correct query). When I try to use the container information to focus on a specific window with

swaymsg for_window -r [id=10] focus

nothing happens, even though I have checked the id to be the right one. Due to the -r option, swaymsg even outputs (the flag has no effect on the fact that nothing happend):

[
  {
    "success": true
  }
]

so there does not seem to be any error. I have tried multiple parameters, from other sources I have read that app_id seems to be the way to go in Wayland when interacting with windows or containers via swaymsg, but nothing happens. I have also tried the command with different programs like terminals or browsers, nothing changes. In the manual of swaymsg it also says to put quotes around the command, but that doesn't help either. Since I don't receive any errors, I am puzzled how to debug.

Arch Linux/Sway/Wayland Nvidia gpu 3070 with proprietary driver 565.57.01 Running apps like chrome or vscode in native wayland mode (with

--ozone-platform=wayland

flag) results in terrible flickering and glitching experience, albeit refresh rate is good (144 fps). When i run them on x11, I see no flickering, but fps is capped to 60. I have tried

--disable-gpu-compositing

flag, and many others, but all of them seem to either cap frame rate or introduce flickering. How do I solve this dilemma and is it even possible to solve?

Arch Linux

wayland/sway

nvidia proprietary driver 565.57.01

60 hz | 144 hz | 60 hz monitor setup

All is smooth except chromium (chrome, vscode). Notably, when I unplug my two lesser monitors and reboot, chromium becomes smooth, but only until I reboot next time. I read on similar refresh rate issues, but they mostly seem to be targeting xorg. This question over manjaro forum addresses pretty much the same issue, but the thread did not lead to a solution https://forum.manjaro.org/t/all-chromium-based-programs-are-running-only-at-60-fps/68175 Arch wiki page leads to an opened issue over google bug tracker, but no luck there either, google does not seem to care that much https://issues.chromium.org/issues/40761642 Is it even possible to fix, given the current state of things? Or is there some usable workaround? Any help would be greatly appreciated!

I've been observing an unusual behavior from Sway on Fedora 39 (which also has GNOME installed, and I need to keep GNOME installed). The desktop starts up, but any GTK apps I launch won't open until about 25 seconds have passed. Also, my [waybar](https://github.com/Alexays/Waybar) never appears until I _reload_ the configuration after the 25 seconds have elapsed. **How do I prevent this delay?** Answers I've seen and tried: - [Uninstall xdg-desktop-portal and xdg-desktop-portal-gnome](https://github.com/swaywm/sway/issues/7600#issuecomment-1556804679) (it turns out these are dependencies for GNOME, so it isn't an option). - [Set GTK_USE_PORTAL=0](https://github.com/swaywm/sway/issues/5732#issuecomment-1365295979) . - [Set WAYLAND_DISPLAY=wayland-1](https://github.com/swaywm/sway/issues/5732#issuecomment-708016469) . - [Run exec systemctl --user import-environment in my sway config](https://github.com/swaywm/sway/issues/5732#issuecomment-707534297) (I tried putting this before and putting it after the waybar line). - [Comment out the pam_gnome_keyring.so line](https://utcc.utoronto.ca/~cks/space/blog/linux/XdgDesktopPortalSlownessWhy) in a file under /etc/pam.d (in my case, /etc/pam.d/gdm-autologin). - [Export a certain set of variables by name](https://github.com/swaywm/sway/wiki#systemd-and-dbus-activation-environments) (WAYLAND_DISPLAY, DISPLAY, XDG_CURRENT_DESKTOP, etc.), so that systemd and dbus can use them. Unfortunately, the delay persisted after a reboot with each of these changes. I'm posting this because I finally found a solution, but an explanation would be welcome (I don't really understand the solution).

I am using Arch Linux with Sway and a pseudoterminal which is currently termite. Typically inside of that I am running tmux and then vim inside of tmux. My problem is that I cannot get ctrl+1 or alt+1 key bindings to work or ctrl+shift+1 etc. I tried creating a binding in tmux like this (in the tmux conf): bind -n C-1 send-keys -X "xzy whatever" but it did not work. How can I get these kinds of bindings to work? I notice that I can get ctrl bindings to work if I define them in the sway config, but I do not want to try to make vim commands defined in my sway config.

I am trying to mix two audio source into one virtual audio source, that I later use with wf-recorder and slurp to capture a screen selection, my audio mic and my audio speakers output. The virtual device is created with https://docs.pipewire.org/page_module_combine_stream.html and works fine but does not mix the two sources properly. Here my config file:

$ cat ~/.config/pipewire/pipewire.conf.d/combined.conf
context.modules = [
	{
		name = libpipewire-module-combine-stream
		args = {
			combine.mode = source
			node.name = "combined"
			node.description = "Record Device"
			combine.props = {
				audio.position = [ FL FR ]
			}
			stream.rules = [
				{
					matches = [
						{
							media.class = "Audio/Source"
							node.name = "alsa_input.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp__source"
						}
					]
					actions = {
						create-stream = {
						}
					}
				}
				{
					matches = [
						{
							media.class = "Audio/Sink"
							node.name = "alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp__sink"
						}
					]
					actions = {
						create-stream = {
							stream.capture.sink = true
						}
					}
				}
			]
		}
	}
]

If I remove the microphone from the config file, I can hear my speakers fine, but as soon as the two sources are in there, I hear only the mic. Here is how run wf-recorder:

wf-recorder --audio="combined" -g "$(slurp)" -f

See my setup below: * OS: Fedora release 40 (Forty) * sway: 1.9 * kernel: 6.10.3-200.fc40.x86_64 * Wayland & Pipewire:

gnome-session-wayland-session.x86_64                   46.0-1.fc40       
libwayland-client.x86_64                               1.22.0-3.fc40     
libwayland-cursor.x86_64                               1.22.0-3.fc40     
libwayland-egl.x86_64                                  1.22.0-3.fc40     
libwayland-server.x86_64                               1.22.0-3.fc40     
pipewire.x86_64                                        1.0.7-2.fc40      
pipewire-alsa.x86_64                                   1.0.7-2.fc40      
pipewire-gstreamer.x86_64                              1.0.7-2.fc40      
pipewire-libs.x86_64                                   1.0.7-2.fc40      
pipewire-pulseaudio.x86_64                             1.0.7-2.fc40      
pipewire-utils.x86_64                                  1.0.7-2.fc40      
qemu-audio-pipewire.x86_64                             2:8.2.2-1.fc40    
qt5-qtwayland.x86_64                                   5.15.14-1.fc40    
qt6-qtwayland.x86_64                                   6.7.2-2.fc40      
vlc-plugin-pipewire.x86_64                             3-2.fc40          
xisxwayland.x86_64                                     2-4.fc40          
xorg-x11-server-Xwayland.x86_64                        24.1.2-1.fc40     
wf-recorder.x86_64                                     0.4.0-5.fc40

I have trouble debugging my setup as I'm not huge in audio, but could someone help me figure out what is wrong with my config file ?

So...I'm using Vim (in the terminal, not any sort of other gui; whenever Vim is used by itself, assume it's terminal vim). Vim is decent, I actually don't find the learning curve to be too bad. I'm a bit less efficient than I would be in a normal text editor, though, primarily due to the act of switching to and from normal mode. But there is one thing about vim that drives the nails in the coffin for me. Normally, when I press Ctrl+Shift+C in my terminal, it copies the text that I've highlighted to the window manager clipboard, and I can then paste that. Ctrl+C and Ctrl+V (or their variants) work absolutely fine in every application that I've used on my system. With Vim, I can press Ctrl+Shfit+V and it will paste the data that I have in my clipboard. But for the life of me, Vim does not copy to the global clipboard. I have tried... - Ctrl+Shift+C with visual mode - using both "*y and "+y (or another copy command) - using set clipboard=unnamed and set clipboard=unnamedplus - installing gvim for "clipboard support" (for terminal vim) and repeating the other steps. Vim just...*refuses* to copy to the clipboard. But I had a thought. I don't need Vim copy to the clipboard *itself*. I just need it to *stop blocking / intercepting the terminal's behavior for Ctrl+Shift+C in visual mode*. But I'm still new to Vim, and I have absolutely no idea how one would accomplish this. All of my attempts to search for something this specific are rather vapid. This is my question to this form: **is there a way to get Vim to allow the terminal emulator (Alacritty) to copy to it's clipboard using Ctrl+Shift+C?** If someone with more Vim experience than myself could give me a pointer, I would really appreciate it. My system, for reference, is Arch Linux using the Sway window manager with the Alacritty terminal emulator. I've seen various things about installing a clipboard manager for Sway, because default Sway doesn't hold the clipboard data if you exit the program you've copied the text from. However, I've never really had a problem with this; even when I quit a program completely, the data is still there. The default clipboard works absolutely fine for me and I don't necessarily want to install and configure a clipboard manager just to get vim to *maybe* work, unless it's the only option. This doesn't seem like the issue anyways. Also, if it helps, the gvim standalone application ***does*** support copying to the clipboard, but standard terminal Vim ***does not***. If possible, I would really like to use a terminal text editor. But I guess I'll just use the gvim app if nothing can be done.

I am trying to set nautilus to dark mode but with no luck. I tried: - run this command:

gsettings set org.gnome.desktop.interface color-scheme 'prefer-dark'

- setting color scheme in ~/.config/gtk-4.0/gtk.css

@import url("resource:///org/gtk/libadwaita/ado.css");

AdwStyleContext {
  color-scheme: dark;
}

- to set it in ~/.config/gtk-4.0/settings.ini

[Settings]
gtk-enable-animations=true
gtk-icon-theme-name=Adwaita-dark
gtk-application-prefer-dark-theme=0

But this has no effect and drops this warning:

(org.gnome.Nautilus:69565): Adwaita-WARNING **: 23:24:29.934:
Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported.
Please use AdwStyleManager:color-scheme instead.

What should I do set globally dark mode for gtk4 apps on my system ? Additional information: I use Arch linux + wayland + sway I am using [ly](https://github.com/fairyglade/ly) display manager. I start ly as systemd service:

● ly.service - TUI display manager
     Loaded: loaded (/usr/lib/systemd/system/ly.service; enabled; preset: disabled)
     Active: active (running) since Wed 2024-01-03 10:31:36 CET; 3h 52min ago
   Main PID: 1042 (ly-dm)
      Tasks: 0 (limit: 8734)
     Memory: 2.5M (peak: 5.0M)
        CPU: 39ms
     CGroup: /system.slice/ly.service
             ‣ 1042 /usr/bin/ly-dm

In my .sway/config, I have exec swayidle -w \ timeout 30 'swaylock -f -c 000000' \ timeout 30 'swaymsg "output * dpms off"' \ resume 'swaymsg "output * dpms on"' \ before-sleep 'swaylock -f -c 000000' Let's say I decide that I want to increase that timeout, so I make it, exec swayidle -w \ timeout 180 'swaylock -f -c 000000' \ timeout 180 'swaymsg "output * dpms off"' \ resume 'swaymsg "output * dpms on"' \ before-sleep 'swaylock -f -c 000000' How can I reload these settings? Moreover, when I try to killall swayidle and run this command manually, I get Failed to find session name: PID 8472 does not belong to any known session No command specified! Nothing to do, will exit How can I get swayidle running with updated timeouts?

One problem I have using Sway is zombie apps that get hung and cannot be killed from within Sway. Sway has a "kill" command which by default is bound to the hotkey mod+Shift+Q, however this command is a soft kind of kill that apparently just nicely asks the process to quit. So, if the process is hung, then it just ignores the command and the window stays open. In this situation what I have to do is switch to a terminal and kill the offending application from the command line which seems kind of ridiculous to me that I have to do this. Is there some functionality in Sway that I am missing that allows me to kill a window with a hung process in it?