Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
1. There are reports here that Zoom works fine with Pipewire in the browser.
2. Have you tried: https://github.com/SeaDve/Kooha ?
I really hope that Arcan has a future, if only for their crash resilient Wayland support. It can even cope with a GPU going away.
sway laptop user here (for almost 2 years I think?).
I spent a little while on this, but I migrated from i3, so I just ported every little section of my config bit by bit.
In terms of battery bar and other "bar" type things, I use waybar[0] which basically does all the things you'd expect by default (just install and it "works").
For multi-monitor, config, I initially setup with wdisplays[1] (think arandr for wayland) and then manually copied the positions into my sway config. Monitor positioning was the only thing I needed to setup (and telling it that one monitor was HDPI) and then all of the scaling and everything worked perfectly. This was my biggest selling point for wayland, I now get nice crisp fonts and application scaling works nicely (which was not the case with X).
volume control from the keyboard took no time, just a couple of extra lines.
There was some stuff to do with the clipboard (wl-clipboard[2]) and screenshots (grim[3] + slurp[4]) that required some setup, but again, just a few lines, and didn't take much mental load.
Oh and I needed to change my notifications daemon(dunst[5]), and chose to change my program launcher to one with a nicer interface and cleaner fonts (wofi[6]).
I think that's all the tweaking that I did. Oh, and I needed to do something with pipewire to sort out screensharing at the start, don't remember that too well though...
[0] https://github.com/Alexays/Waybar
[1] https://github.com/artizirk/wdisplays
[2] https://github.com/bugaevc/wl-clipboard
[3] https://github.com/emersion/grim
[4] https://github.com/emersion/slurp
sway laptop user here (for almost 2 years I think?).
I spent a little while on this, but I migrated from i3, so I just ported every little section of my config bit by bit.
In terms of battery bar and other "bar" type things, I use waybar[0] which basically does all the things you'd expect by default (just install and it "works").
For multi-monitor, config, I initially setup with wdisplays[1] (think arandr for wayland) and then manually copied the positions into my sway config. Monitor positioning was the only thing I needed to setup (and telling it that one monitor was HDPI) and then all of the scaling and everything worked perfectly. This was my biggest selling point for wayland, I now get nice crisp fonts and application scaling works nicely (which was not the case with X).
volume control from the keyboard took no time, just a couple of extra lines.
There was some stuff to do with the clipboard (wl-clipboard[2]) and screenshots (grim[3] + slurp[4]) that required some setup, but again, just a few lines, and didn't take much mental load.
Oh and I needed to change my notifications daemon(dunst[5]), and chose to change my program launcher to one with a nicer interface and cleaner fonts (wofi[6]).
I think that's all the tweaking that I did. Oh, and I needed to do something with pipewire to sort out screensharing at the start, don't remember that too well though...
[0] https://github.com/Alexays/Waybar
[1] https://github.com/artizirk/wdisplays
[2] https://github.com/bugaevc/wl-clipboard
[3] https://github.com/emersion/grim
[4] https://github.com/emersion/slurp
sway laptop user here (for almost 2 years I think?).
I spent a little while on this, but I migrated from i3, so I just ported every little section of my config bit by bit.
In terms of battery bar and other "bar" type things, I use waybar[0] which basically does all the things you'd expect by default (just install and it "works").
For multi-monitor, config, I initially setup with wdisplays[1] (think arandr for wayland) and then manually copied the positions into my sway config. Monitor positioning was the only thing I needed to setup (and telling it that one monitor was HDPI) and then all of the scaling and everything worked perfectly. This was my biggest selling point for wayland, I now get nice crisp fonts and application scaling works nicely (which was not the case with X).
volume control from the keyboard took no time, just a couple of extra lines.
There was some stuff to do with the clipboard (wl-clipboard[2]) and screenshots (grim[3] + slurp[4]) that required some setup, but again, just a few lines, and didn't take much mental load.
Oh and I needed to change my notifications daemon(dunst[5]), and chose to change my program launcher to one with a nicer interface and cleaner fonts (wofi[6]).
I think that's all the tweaking that I did. Oh, and I needed to do something with pipewire to sort out screensharing at the start, don't remember that too well though...
[0] https://github.com/Alexays/Waybar
[1] https://github.com/artizirk/wdisplays
[2] https://github.com/bugaevc/wl-clipboard
[3] https://github.com/emersion/grim
[4] https://github.com/emersion/slurp
sway laptop user here (for almost 2 years I think?).
I spent a little while on this, but I migrated from i3, so I just ported every little section of my config bit by bit.
In terms of battery bar and other "bar" type things, I use waybar[0] which basically does all the things you'd expect by default (just install and it "works").
For multi-monitor, config, I initially setup with wdisplays[1] (think arandr for wayland) and then manually copied the positions into my sway config. Monitor positioning was the only thing I needed to setup (and telling it that one monitor was HDPI) and then all of the scaling and everything worked perfectly. This was my biggest selling point for wayland, I now get nice crisp fonts and application scaling works nicely (which was not the case with X).
volume control from the keyboard took no time, just a couple of extra lines.
There was some stuff to do with the clipboard (wl-clipboard[2]) and screenshots (grim[3] + slurp[4]) that required some setup, but again, just a few lines, and didn't take much mental load.
Oh and I needed to change my notifications daemon(dunst[5]), and chose to change my program launcher to one with a nicer interface and cleaner fonts (wofi[6]).
I think that's all the tweaking that I did. Oh, and I needed to do something with pipewire to sort out screensharing at the start, don't remember that too well though...
[0] https://github.com/Alexays/Waybar
[1] https://github.com/artizirk/wdisplays
[2] https://github.com/bugaevc/wl-clipboard
[3] https://github.com/emersion/grim
[4] https://github.com/emersion/slurp
sway laptop user here (for almost 2 years I think?).
I spent a little while on this, but I migrated from i3, so I just ported every little section of my config bit by bit.
In terms of battery bar and other "bar" type things, I use waybar[0] which basically does all the things you'd expect by default (just install and it "works").
For multi-monitor, config, I initially setup with wdisplays[1] (think arandr for wayland) and then manually copied the positions into my sway config. Monitor positioning was the only thing I needed to setup (and telling it that one monitor was HDPI) and then all of the scaling and everything worked perfectly. This was my biggest selling point for wayland, I now get nice crisp fonts and application scaling works nicely (which was not the case with X).
volume control from the keyboard took no time, just a couple of extra lines.
There was some stuff to do with the clipboard (wl-clipboard[2]) and screenshots (grim[3] + slurp[4]) that required some setup, but again, just a few lines, and didn't take much mental load.
Oh and I needed to change my notifications daemon(dunst[5]), and chose to change my program launcher to one with a nicer interface and cleaner fonts (wofi[6]).
I think that's all the tweaking that I did. Oh, and I needed to do something with pipewire to sort out screensharing at the start, don't remember that too well though...
[0] https://github.com/Alexays/Waybar
[1] https://github.com/artizirk/wdisplays
[2] https://github.com/bugaevc/wl-clipboard
[3] https://github.com/emersion/grim
[4] https://github.com/emersion/slurp
sway laptop user here (for almost 2 years I think?).
I spent a little while on this, but I migrated from i3, so I just ported every little section of my config bit by bit.
In terms of battery bar and other "bar" type things, I use waybar[0] which basically does all the things you'd expect by default (just install and it "works").
For multi-monitor, config, I initially setup with wdisplays[1] (think arandr for wayland) and then manually copied the positions into my sway config. Monitor positioning was the only thing I needed to setup (and telling it that one monitor was HDPI) and then all of the scaling and everything worked perfectly. This was my biggest selling point for wayland, I now get nice crisp fonts and application scaling works nicely (which was not the case with X).
volume control from the keyboard took no time, just a couple of extra lines.
There was some stuff to do with the clipboard (wl-clipboard[2]) and screenshots (grim[3] + slurp[4]) that required some setup, but again, just a few lines, and didn't take much mental load.
Oh and I needed to change my notifications daemon(dunst[5]), and chose to change my program launcher to one with a nicer interface and cleaner fonts (wofi[6]).
I think that's all the tweaking that I did. Oh, and I needed to do something with pipewire to sort out screensharing at the start, don't remember that too well though...
[0] https://github.com/Alexays/Waybar
[1] https://github.com/artizirk/wdisplays
[2] https://github.com/bugaevc/wl-clipboard
[3] https://github.com/emersion/grim
[4] https://github.com/emersion/slurp
The Zoom issue is related to the API they chose to use on Wayland. There's an API for sharing stuff like screens and windows, but Zoom is calling the GNOME (not even standard) screenshot API in a loop instead. As you might expect, that doesn't exactly work smoothly; performance is lacking and window coordinates would need to be tracked manually.
There's a whole thread about it here (https://community.zoom.com/t5/Meetings/Wayland-screen-sharin...) but I don't think Zoom cares enough about their Linux client to fix these issues.
I don't know about the shortcut issues you're facing, my guess would be the key logger protections built into wayland prevent your shortcut daemon from capturing the necessary keys. Autokey certainly runs into that problem (https://github.com/autokey/autokey/issues/87). Other programs seem to get similar features working, but not everyone had the time or expertise to bring out compatible versions of their software.
The frustration I see most from this is on hiDPI displays and any electron apps (which there are plenty)
Supposedly it's been fixed recently: https://github.com/electron/electron/pull/29618
If anyone else finds themselves in my situation re: Spectacle, I put together this script which may or may not work (I've only tested it by dry-running it so far): https://github.com/Sharparam/dotfiles/blob/master/bin/sharps...