wayland (river 0.5+) advice
2026-07-05 14:55 UTC
Replies (4)
-
@fozid@feddit.uk 2026-07-05 15:22
Can’t help you with river specifically, but I went from running x11 with openbox, to Wayland with sway. Sway has a really good ecosystem of tools like swaybg for wallpaper. I use waybar, pcmanfm, and rofi.
-
@atomkarinca@lemmygrad.ml 2026-07-05 15:39
river is cool but it’s heavily modular. i love it. first off, you should choose a window manager. there’s a list on their page. for example, rill is a scrolling wm like niri. there are also stacking and tiling wms on that list. then you should also install some tools. their wiki also includes a brief list. a bar (e.g. waybar) an output manager (e.g. kanshi) an input manager (e.g. channel) a screen lock tool (e.g. waylock, swaylock) a launcher (e.g. wofi, fuzzel, tofi) a notification daemon (e.g. fnott, mako) a wallpaper tool (e.g. awww, swaybg) this would give you a fully working wm.
-
@ZWQbpkzl@hexbear.net 2026-07-05 16:06
Because you’ve chosen the river >=0.4 any advice will depend completely on the window manager you choose. Things like keybindings and decorations are punted are punted to the window manager with that release. If you want to write your own then you’ll have to implement all that yourself. Look at the source code for existing river window managers. We’re still in gtk territory, right? Lol no. Even with river-classic you’re several layers below individual GUI toolkits. If you want to stay in gtk land then you must only choose widgets/apps that only use GTK. Your toolbar could be GTK, and your launcher could be QT if you want. It could also eschew all that and use pango-cairo if it wants. For the general flow: Display manager starts river River executes ~/.config/river/init and you’re on your own. The init file should start your window manager. Your window manager should start communicating with the river server over the protocols that river implements. In river classic there’s only 2 protocol methods to implement, layout and user command. In river-classic: everything else, keybindings, hooks, decorations, all get set by executing riverctl commands In new river: there’s more protocol methods covering all that for the window manager to implement.
-
@meurglys@lemmy.world 2026-07-05 20:59
River-classic has long been a favorite of mine. It’s easy to setup and maintain. I use that, or Sway on Void linux. Here’s a list of apps that might help you get started. arewewaylandyet.com For my own River setup, I used waybar, fuzzel, mako, nwg-look, hyprpicker, brightnessctl, swaybg, kitty, imv, grim udiskie, mpd/rmpc, and mpv. I would suggest looking for user dot files of the the window manager you are interested in, and getting a feel for the syntax and how they set up their system. From there, you could start making small edits to a basic config file, to make it more in line with your workflow. Most ricers, myself included, started this way. You see something you like, look at how they did it, and alter, or adapt it to suit your needs. At first, it may seem difficult, but with time, and a little patience, it’s fun and make for a system that’s your own. Happy ricing!