wf-recorder VS mako

Try wf-recorder.

The closest thing is probably wf-recorder.

The spec is designed to be minimal and it's expected for compositors to work together and add additional features, for example here is the tool for screen recording on wlroots compositors (sway and what most wayland WM's use) https://github.com/ammen99/wf-recorder, even though most people claim wayland doesn't support screen-recording/screenshotting. We just don't have a universal tool for that that works on all compositors, pipewire however seems to be coming to fill that niche.

If you are on Wayland, wf-recorder Is a good choice .

As for screen recording, I’ve used wf-recorder (IIRC, not at PC atm) several times the past couple of weeks, works equally well.

The issue I'm encountering is described here in more detail (including images).

Wfrecorder [0] is what I use, doesn't have a fancy gui but it just works

0: https://github.com/ammen99/wf-recorder

A workaround for sharing the whole screen is to use wf-recorder [1], which supports capturing the whole screen, and feeding its output to a virtual V4L2 device using v4l2loopback [2]. Software that is able to capture from a V4L2-compatible webcam (i.e. most) can them capture from the virtual device without knowing anything about Wayland. It's not exactly the most CPU-efficient way of doing things, but if you can afford the cycles it works very well!

[1] https://github.com/ammen99/wf-recorder

[2] https://github.com/umlaeute/v4l2loopback

You want to use wf-recorder. This is in my sway config:

> set $screenrecord wf-recorder -g "$(slurp)" -f ~/screenshots/mov-$(date +"%Y-%m-%d--%H-%M-%S.mp4")

> bindsym Shift+Control+F6 exec $screenrecord

> bindsym Ctrl+Shift+BackSpace exec killall -s SIGINT wf-recorder

Hitting shift-control-f6 will spawn slurp which lets you click and drag to set the area you want to record. This will then launch wf-recorder and record the selected area, saving to ~/screenshots/mov-${date}. You can use ctrl-shift-backspace to kill the recorder and end recording.

https://github.com/ammen99/wf-recorder

https://github.com/emersion/slurp

So, using this github issue as a reference, I'm trying to make a wofi menu that appears when a bluetooth file transmission is sent to my PC from my phone (or any other device for that matter).

I currently use mako for the notifications. When I play Strategy Games (Mouse is all over the place) and a notifcation pops up, the mouse gets stuck on the notification message until I click it.

I use avizo as a volume indicator, mako for notifications generally.

I guess some standard notifications app like https://github.com/emersion/mako doesn't suffice, as it isn't related to a window?

mako is a Wayland notification daemon from one of the principal Sway/wlroots devs, and is currently provided with openSUSEway. It's pretty minimalist, but so are most things in the Sway/wlroots ecosystem.

It's a notification, I use mako: https://github.com/emersion/mako

Notifications: mako

Is there any way to force dbus to use a specific notification daemon? On one of my systems, I run both Plasma and Sway. The latter obviously doesn't have a notification system, so I'm using mako. As far as I can tell, mako automatically launches when a notification is fired, however this causes an issue with Plasma. Plasma seems to be shutting down its own notification daemon in favor of anything else that's running, and I'm not sure if there's a way to prevent it from doing that

I don’t use Thunderbird, but does it support using FreeDesktop notifications e.g. that would work with Mako? Some applications will fall back to their own windows if there’s no notification daemon running.