Sway 1.11-rc1 contains 163 changes from 48 contributors.
This release depends on wlroots 0.19.0-rc1. See the wlroots release notes.
New features
All of the enhancements from wlroots 0.19.0-rc1.
Ad...
I recently upgraded from an RX 570 to an RX 6600. Everything is working great, except that the font in my menu program Fuzzel as well as the font in my terminal foot is really big on one monitor and the correct size on the other monitor. I thought it might be because the monitor with the big text had a displayport to hdmi adapter, but I switched that monitor to hdmi and the other monitor to dp, and the same monitor still had big font in the menu and the terminal. The scaling seems to be correct, both monitors seem to be identical. What is going on? Any ideas? I'm running Debian Bookworm. I also installed the amd drivers as instructed on the Debian Wiki.
Attached: 1 image
This is Sway in HDR mode, but unlike last time, there are no hacks nor tricks. It supports both SDR and HDR content on both SDR and HDR outputs. Phew!
Want to try it out? Instructions here: https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/5002
I've been suggested to use a tiling window manager like Sway since it allows for controlling windows with hotkeys, but I'm having trouble getting started. I installed it in Fedora and tried logging back in with SwayFX (since it has features like blurring) but after I'm just shown a wallpaper with a top bar, the top left shows a 1 and the top right shows the time. I don't know what to do there. I tried looking up guides but didn't find anything, can you link me some if you know of any?
Attached: 1 image
First ever HDR video on Sway + mpv. The left screen is SDR, right one is HDR. Of course it's impossible to tell the difference on the picture because my camera is SDR. You'll have to take my word for it: the right screen shows a lot more various colors (orange, yellow, white) whil...
Adds support for the new protocol for output capture (individual toplevel capture is not yet implemented).
References: https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4545
I love i3wm and would like to switch to sway for the advantages of not using xorg. But is it worth it with a laptop that has an old nividia/intel hybrid video card? I had read that it was complicated to use nvidia cards with wayland
Fuzzel is a Wayland-native app launcher and fuzzy finder for Linux, inspired by Rofi and dmenu.
The five-year-old Fuzzel project recently had a feature-packed 1.11 release. Here's a visual rundown of what's new.
Instant filtering of huge lists
0:00
/0:08
1×
...
Here's how I set up my keybindings for the Sway window manager for Linux.
Most of the tips here would apply to any keyboard, but let's get one detail out of the way first that's specific to 40% keyboards like the Corne. It doesn't have a number row, and this
I noticed this immediately because I use kanshi (highly recommended for laptops running sway!).
I don't know the how or why (maybe it's the wlroots bump), but when I upgraded Sway to 1.9 today, the Hex ID form one of my external monitors changed. So I had to update it in the config for kanshi to work again.
Just a heads up for other kanshi users, and people whose scripts may be influenced by this.
So I migrated from i3 to sway. Had a python script that I found on the internets that did this, and really like the functionality. Figured I'd give an attempt at making my own script in bash. My programming skills and bash scripting aren't great, so I had chatGPT help me with some syntax. Thought others might be interested so am sharing here.
undefined
#!/bin/bash
# this script moves a container to an empty workspace
# and switches to that workspace
# Define list of available workspaces
all_workspaces_list=(1 2 3 4 5 6 7 8 9 10)
# get workspaces currently being used
used_workspaces=$(swaymsg -t get_workspaces | grep -oP '"name": "\K\d+')
# create a list from used workspaces
used_workspaces_list=($used_workspaces)
# Check for first of all_workspaces_list not in used_workspaces_list
for workspace in "${all_workspaces_list[@]}"; do
if [[ ! "${used_workspaces_list[*]}" =~ "$workspace" ]]; then
free_workspace=$workspace
break # stop loop after finding first available
Okay, I am super new to tiling windows managers, and let me just say - Sway made me an instant convert. I'm obsessed. But I still have no clue what I'm doing.
So I have been trying out every status bar I can to see what looks good, what feels good, and what has the best efficiency for some of my SUPER low-grade hardware.
This brings me to yambar. It is touted as the most resource efficient status bars, and because I only want to see a few things (battery, ram, cpu, volume, time/date), I figured it was a good fit. I downloaded and installed it (used AUR) and I had a few issues getting it installed, but eventually go there. (I should probably say right now that I'm also new to Arch. All my previous Linux experience has been Debian based.)
So now that yambar is installed, I snagged the example config.yaml and moved/renamed it to ~/.config/yambar/config.yaml. Now most of the previous status bars I've been trying required you to add/change something in the `~/.config/sway/con
I'm using Firefox Developer edition on sway, and since version 121 it shows a small border on top. I have the option hide_edge_borders both
enabled, so this border is displayed by Firefox, not Sway (cf. the terminal on the right end of the screenshot).
Does someone else have this issue? Do you have an idea for a workaround? Is this a bug I should report to Firefox?
PS: I've seen this issue on Arch, NixOS and Firefox 122