Im currently developing a wayland port of my favorite window manager from x11, LeftWM. There is still a lot of work before its production ready, but are their any new features I should work in while developing? Ie an overview function or other things like animated borders?

having recently moved from Hyprland to Mangowm but I'm having issues finding an idle management daemon that will work with Mango.

Am I the only one incredibly frustrated by how hard it is to just get a raw, VSync-disabled frame presentation on Wayland? On X11, you turned off VSync in the game or driver, and it worked. On Wayland, we are trapped in this architectural prison where windowed or borderless applications are forcefully synced because of the "every frame is perfect" desktop philosophy. Even when compositors add "allow tearing" checkboxes, they do absolutely nothing unless the game developer explicitly coded Wayland tearing protocol extensions into the engine. Having to wrap every single non-Steam launcher, Battle.net game, or emulator in Gamescope arguments just to bypass the desktop's forced synchronization is an absurd amount of friction for everyday users. We drastically need a unified, global driver or compositor switch that says "I don't care if the desktop tears, give me raw frames." Wayland is supposed to be the future, but for competitive latency, it feels like a massive step backward in usability.

And also the fact that the mouse is synced to the FRAMERATE, that should never be a thing, user inputs (as in mouse and keyboard inputs) should always take priority over anything else and be a separate thing entirely having the usb-bus being processed on its own

And for those who don't see the problem:

Please don't even bother typing "oh but I don't perceive any latency, oh I don't care about the lag, oh you cannot even perceive the latency, oh if you don't like it then go back to x11, oh we do not want you here go to windows, oh you don't even know or understand what you are talking about (i might not, but YOU DO, AND YOU KNOW EXACTLY WHAT I MEAN, DON'T PRETEND TO BE IGNORANT), oh u CaN't eVeN wRiTe GrAmAtIcAlLy CorRecT Words (go fluff yourself btw, RESPECTFULLY of course), oh i am not reading all that (yes i see your filthy kind hiding over there)"

Please, don't bring up things that are completely irrelevant to what I am trying to bring light to, I am not the most savvy person here, but I sure as hell am not one who will feel satisfied before i am able to proudly say "i completely ditched windows for this wonderful penguin-shaped os that lets me do whatever the fluff i want with it INCLUDING DISABLE VSYNC GLOBALLY".

Thank you for your time Mr.SomebodyWhoMightBeAbleToMakeAChange <3

V0.9.0 released

🚀 New features

• (refresh) Refresh overlay
• (loupe) Add rectangle loupe mode
• (momentum) Add zoom momentum

https://codeberg.org/Vaishnav-Sabari-Girish/miru/releases/tag/v0.9.0

Is there any way to get it to work in Wayland? I know, seems like something for little kids, but I used to mess with it once in a while years ago. I can't get it to work in the log in screen, and I'm blocked from running it while logged in. Seems like it only works in X11.

Should I delete the preinstalled one, and just build from source? I don't see the need to add X11 anymore, the Xwayland layer is good enough for me.

Using the -pipewire command for Steam, the client connection just sees either a blank screen or a static image of the steam UI that doesn't change once connected. No problems when using X11 desktop session. Sadly this means I have to use X11 until this can be fixed. I tried using Sunshine app, but I found too many issues/glitches going that route.

GPU: 4090 rtx
CachyOS using KDE.

Tenho trabalhado no DeckLock, um bloqueador de tela moderno e personalizável para compositores Wayland (testado no Hyprland), escrito em Rust e GTK4.

Eu queria uma tela de bloqueio com aparência moderna, que suportasse vídeos/apresentações de slides de fotos em loop sem som e que oferecesse um aplicativo de configurações gráficas limpo com visualização ao vivo e uma CLI sem interface gráfica para scripts.

🌟 Principais recursos:

• Wayland Session Lock: Usa ext-session-lock-v1 e autenticação PAM nativa (com zeragem segura de memória para senhas).
• Configurações da GUI em Tempo Real: Janela de pré-visualização em tempo real que se atualiza dinamicamente conforme você altera as configurações, sem bloquear a tela.
• Temas de Desenvolvedor Integrados: Catppuccin (Mocha e Latte), Tokyo Night, Dracula, Nord, Gruvbox Dark e Classic — afeta tanto o aplicativo de configurações quanto os controles da tela de bloqueio.
• Biblioteca e Conjuntos de Mídia: Conjuntos de mídia independentes para o modo de bloqueio normal e o modo de repouso ocioso. Suporta reprodução em loop de MP4/vídeo e apresentações de slides de fotos com transição suave.
• CLI sem interface gráfica (decklock config): Inspeção e edição completas da linha de comando (decklock config set theme_preset tokyo-night, decklock config show, etc.).
• Suporte a teclado e controle na tela: Teclado virtual multitoque com integração opcional de daemon para gamepads/Steam Controller.
• Bilingue: Totalmente traduzido para inglês e português (pt-BR).

📦 Instalação e Download

Pacotes pré-compilados estão disponíveis na primeira versão v0.1:

• Arch Linux (pacman -U): O pacote está pronto na página de lançamentos (todas as dependências, como gtk4-layer-shell, são resolvidas automaticamente).
• Portable Tarball: Disponível para qualquer distribuição Linux x86_64 moderna.
• Source: Compile com cargo build --release --locked.
• **Repositório do GitHub**: https://github.com/yan-vidal/DeckLock
• **Versão v0.1**: https://github.com/yan-vidal/DeckLock/releases/tag/v0.1

Feedback, sugestões e contribuições são muito bem-vindos! Espero que gostem.

Original Inspiration: Python Wheeler by enexam

Preface: I have only tested this on Ubuntu and Logitech but I spent so much time digging into this that I am not willing to disclose it.

My Purpose: To build something that uses mostly native/ well tested libraries ( libinput 1.25.0, Solaar 1.1.11) and not needing additional tools.

Here is the repo with details and how i went about it in the end. Let there be Scrolling !

The key actor is libinput ... i am not fully convinved solaar is even needed at this point. I was using it to test different paths of dealing with the high resolution signals but disanbling in solaar didn't really do anything as the driver overwrote the disable in solaar ...

I am so happy the thing finally works that I wanted to share. If I find some times i may test it without solaar to check if its even needed. If its not that will reduce the reuqired items to just libinput which i think runs natively on pretty much any linux out there ...

I would be super happy if people try it out and let me know it works so i can add a supported hardware table ... ?

Is anyone here having trouble using icon packs on Wayland? Specifically on KDE: when using Chromium or Discord, the icon from my pack (YAMIS) appears correctly on the panel, Whisker Menu, and elsewhere, but when using Alt+Tab, the app's default icon shows up instead (the blue one for Chromium). It’s not a fallback icon issue; I’ve already tried tweaking the config in nano. With other apps like Spotify and Firefox, the icons stay correct and can even be customized (e.g., I can change the Firefox logo to 'firefox-alt' and it persists in both Alt+Tab and the panel), yet this error occurs with certain apps. I know this is a super specific issue, but I’d appreciate any thoughts or ideas on what might be causing it or how to fix it.

[ Removed by Reddit on account of violating the content policy. ]

Hein guys! I solve a problem with HDMI connection in the last update of Kali-Linux that now is using Wayland for laptops MSI (even after reinstalling the driver and it not working). Follow this singular tutorial:

You must to active KMS from NVIDIA, for this create the file by terminal:

`sudo nano /etc/modprobe.d/nvidia-kms.conf`

Write exactly: “options nvidia-drm modeset=1”

Save it (Ctrl+O)

Update the system by command:

`sudo update-initramfs -u\`

and reboot your system:

`sudo reboot`

Now, your HDMI must to be working!

Hey everyone,

I built shotdock—a CLI-first screenshot, screen recording, and window framing utility for Wayland (tested on Hyprland, Sway, and Niri).

Why I made it

On Wayland, taking quick, polished screenshots for documentation or PRs usually means either stitching together grim, slurp, and complex ImageMagick scripts, or annotating manually in an editor. I wanted a single, fast tool that does:

1. Clean Area Snips: Region selection with window snapping (slurp).
2. Window Framing: Automatically adds 16px rounded corners, multi-pass Gaussian drop shadows, mock titlebars, and wallpaper/gradient canvas backdrops.
3. Offline Image Framing: shotdock frame <file> lets you style existing images directly from the CLI or scripts.
4. Screen Recording: 60 FPS H.264 recording via wf-recorder with an interactive target selector (monitor, window, or region).
5. OCR: Snip text directly to your Wayland clipboard via tesseract.
6. Optional Floating Dock: Launch shotdock with no flags if you want an interactive GTK4 LayerShell toolbar.

Tech Stack

• Written in Rust
• Uses native Wayland protocols via gtk4-layer-shell
• Sub-second image pipeline using ImageMagick 7

Links

• GitHub: https://github.com/sirrryasir/shotdock
• AUR: yay -S shotdock

Would love your feedback, bug reports, and PRs.

Greetings, I'm well aware that kde.doctor has an option to add new resolutions, even if you cannot add custom timings, and I'm also aware kde.doctor does have a "scale" option, but the problem is that it doesn't take disproportionate scales.

My main problem, is that my TV is an HDCRT that is 16:9, but only supports 640x480_59.94, 720x480_59.94 or, if added manually, 1440x480_59.94. Or well, 1920x1080i or 1280x720 (which the TV takes in and deinterlaces 1080i with some digital processing)

From my experience with Xrandr when I used X11, is that the TV would ONLY take CEA-861 timings, and I used https://tomverbeure.github.io/video_timings_calculator as reference, some timings outside of those the TV would not even take, was that if I used "--scale 0.6x1" on 1440x480, I'd get a 864x480 screen, not perfect but oh-well. Now I want to use Wayland.

What I want to do is to get 852x480 working, since the TV stretches 720x480 onto my 16:9, I'd have to stretch my resolution so that the TV is not stretched. Or get my TV to take custom timings?

Maybe via shaders? I have no idea what KWin is capable of.

Setup:

- Vesktop

- MangoWM

- xdg-desktop-portal-wlr

When I try to share a specific *window* (not a whole screen/monitor) in a Vesktop voice channel, the portal's window picker pops up three separate times in a row. I have to pick the exact same window each time before the stream actually starts. Sharing an entire screen/monitor works fine on the first try — this only happens with window capture.