Login

Recent searches

No recent searches

Search options

Only available when logged in.
fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

9.9K
active users

fosstodon.org: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#waybar

0 posts0 participants0 posts today
Public *
TFed 🍉🌻

I haven't changed the #waybar config yet, but i did installed some font packages (i will list them soon)...

Pure Waybar on Guix didn't had all these Unicode ASCII-like symbols right.

But now waybar partially got Unicode chars fixed.

You can notice two characters are still missing at the Temperature and Custom/Power modules

Screenshot of sway with Waybar (that has been made with grim and slurp). Mostly all glyphs on waybar are drawn correctly. You can see Closed-Eye glyph and glyphs for headphones, muted-microphone, WiFi, CPU, RAM, (yet unknown Unicode glyph for Temperature) and light with battery glyph. I still need to install somehow few temperature and battery glyphs...
Public
Adam Harvey

I've been playing around with Niri as a Wayland compositor for the last few weeks, as opposed to my normal Sway. It's nice!

Anyway, I decided I wanted a more Niri-specific taskbar module for Waybar, and ended up using Waybar's CFFI interface to build one in Rust, which turned out to be (mostly) fun. I wrote about it here: lawngno.me/blog/2025/03/06/nir

A scrollable-tiling Wayland compositor. Contribute to YaLTeR/niri development by creating an account on GitHub.
GitHubGitHub - YaLTeR/niri: A scrollable-tiling Wayland compositor.A scrollable-tiling Wayland compositor. Contribute to YaLTeR/niri development by creating an account on GitHub.
#niri#rust#waybar
Public
𝘋𝘪𝘳𝘬

After lots and lots of waiting and trying out multiple different things regarding single window recording in #OBS :obs: on #Wayland :wayland: running #labwc :labwc: there is now a solution in place I can work with.

I wrote a wrapper script (see here) that does the following things when added as #pipemenu in labwc and I click the menu entry to create the output.

  1. Add a virtual output
  2. Use wlr-randr to set the geometry
  3. Use swaybg to set the wallpaper
  4. Send an update signal to a custom #Waybar module

I can now start #OBS and can add a #PipeWire screen recording and select the output (I have to do it blindly by just moving the cursor outside my actual display, because there is no menu, but that’s fine).

For what I’m doing the performance of the OBS preview is fast enough so I simply move the cursor over to the virtual output and use it “inside OBS”.

When I’m done, I invoke the script again, by clicking the remove entry which is dynamically shown if the output is active.

  1. Remove the output
  2. Remove “the output’s swaybg instance”
  3. Send an update signal to a custom Waybar instance

Until individual-window recording will be possible this is a good workaround.

#JustLinuxThings #ModernLinuxProblems #SharingIsCaring #scripting #Luanti #MinetestGame

//cc @whynothugo (thanks) @LXQt (thanks, too)

Screenshot of a dual-output setup. The right output in 2K resolution and shows Luanti in fullscreen. The left output is in 4K resolution and shows OBS with a PipeWire screen recording of the right output and a small circular webcam image in the top right corner.
ExploreLive feeds
About