home.social

#wayvnc — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #wayvnc, aggregated by home.social.

fetched live
  1. #river #wayland

    Some tips I've learned from writing #cow...

    1. Nested River (on #wayland/#x11) is your friend. This makes it very easy to run a nested WM instance on whatever one is using to test features. The inner-WM will need separate bindings from the "host" because that takes priority.

    2. Remotely with wayvnc. Because #river is built on wlroots, #wayvnc is a great alternative if you want to do remote testing/development.

    3. As with point 2., you can set the environment variable WL_HEADLESS_OUTPUTS=n, where "n" represents number of screens. This can be used with some VNC clients to allow "multi-monitor" support. This can be made even better with #wayvnc version 0.10 as this can render multiple outputs appropriately.

    I'm sure there's more, but this is a practical start to some of the things I've been using with #cow.

  2. #river #wayland

    Some tips I've learned from writing #cow...

    1. Nested River (on #wayland/#x11) is your friend. This makes it very easy to run a nested WM instance on whatever one is using to test features. The inner-WM will need separate bindings from the "host" because that takes priority.

    2. Remotely with wayvnc. Because #river is built on wlroots, #wayvnc is a great alternative if you want to do remote testing/development.

    3. As with point 2., you can set the environment variable WL_HEADLESS_OUTPUTS=n, where "n" represents number of screens. This can be used with some VNC clients to allow "multi-monitor" support. This can be made even better with #wayvnc version 0.10 as this can render multiple outputs appropriately.

    I'm sure there's more, but this is a practical start to some of the things I've been using with #cow.

  3. (more Linux news in original post)

    IPFire 2.29 Core Update 201 Linux Firewall Distro Released with DNS Firewall:
    9to5linux.com/ipfire-2-29-core

    DietPi 10.3 brings Orange Pi 4 LTS image, Prometheus monitoring, USB auto-mount, and more:
    alternativeto.net/news/2026/4/

    Grml 2026.04 Linux Distro Is Out with Linux Kernel 6.19, Based on Debian 14 Forky:
    9to5linux.com/grml-2026-04-lin

    Wine 11.8 Improves VBScript Compatibility, Finally Fixes Microsoft Golf 1999:
    phoronix.com/news/Wine-11.8-Re

    Proton Experimental and Proton 11 Beta updated to fix issues with the EA App:
    gamingonlinux.com/2026/04/prot

    Proton Experimental updated to get Crimson Desert working again on Linux / SteamOS:
    gamingonlinux.com/2026/04/prot

    D7VK 1.8 further improves retro Direct3D games on Linux:
    gamingonlinux.com/2026/04/d7vk

    Someone got Ubuntu running on a PS5 – and played Steam:
    omgubuntu.co.uk/2026/04/ps5-li
    (This is what Sony gets for adding DRM to their system lol)

    Steam On Linux In April Pulled Back From Its Record High Marketshare:
    phoronix.com/news/Steam-April-

    Framework’s new Linux laptop is selling faster than its Windows one:
    pcworld.com/article/3123900/fr

    Linus Torvalds Announces First Linux Kernel 7.1 Release Candidate:
    9to5linux.com/linus-torvalds-a

    Copy Fail exploit lets 732 bytes hijack Linux systems and quietly grab root:
    nerds.xyz/2026/04/copy-fail-li

    Devuan developer working on reviving GTK2:
    devuanusers.com/thread-gtk2-re

    XWayland 24.1.11 released with bug fixes:
    lists.x.org/archives/xorg/2026

    WayVNC 0.10 Released For Advancing This Leading VNC Server For Wayland:
    phoronix.com/news/WayVNC-0.10-

    (FOSS news in comments)

    #WeeklyNews #News #Linux #LinuxNews #IPFire #DietPi #OrangePi #Grml #Wine #Proton #ProtonExperimental #D7VK #LinuxMarketshare #FrameworkLaptop #LinuxKernel #GTK2 #XWayland #WayVNC #FosseryTech

  4. (more Linux news in original post)

    IPFire 2.29 Core Update 201 Linux Firewall Distro Released with DNS Firewall:
    9to5linux.com/ipfire-2-29-core

    DietPi 10.3 brings Orange Pi 4 LTS image, Prometheus monitoring, USB auto-mount, and more:
    alternativeto.net/news/2026/4/

    Grml 2026.04 Linux Distro Is Out with Linux Kernel 6.19, Based on Debian 14 Forky:
    9to5linux.com/grml-2026-04-lin

    Wine 11.8 Improves VBScript Compatibility, Finally Fixes Microsoft Golf 1999:
    phoronix.com/news/Wine-11.8-Re

    Proton Experimental and Proton 11 Beta updated to fix issues with the EA App:
    gamingonlinux.com/2026/04/prot

    Proton Experimental updated to get Crimson Desert working again on Linux / SteamOS:
    gamingonlinux.com/2026/04/prot

    D7VK 1.8 further improves retro Direct3D games on Linux:
    gamingonlinux.com/2026/04/d7vk

    Someone got Ubuntu running on a PS5 – and played Steam:
    omgubuntu.co.uk/2026/04/ps5-li
    (This is what Sony gets for adding DRM to their system lol)

    Steam On Linux In April Pulled Back From Its Record High Marketshare:
    phoronix.com/news/Steam-April-

    Framework’s new Linux laptop is selling faster than its Windows one:
    pcworld.com/article/3123900/fr

    Linus Torvalds Announces First Linux Kernel 7.1 Release Candidate:
    9to5linux.com/linus-torvalds-a

    Copy Fail exploit lets 732 bytes hijack Linux systems and quietly grab root:
    nerds.xyz/2026/04/copy-fail-li

    Devuan developer working on reviving GTK2:
    devuanusers.com/thread-gtk2-re

    XWayland 24.1.11 released with bug fixes:
    lists.x.org/archives/xorg/2026

    WayVNC 0.10 Released For Advancing This Leading VNC Server For Wayland:
    phoronix.com/news/WayVNC-0.10-

    (FOSS news in comments)

    #WeeklyNews #News #Linux #LinuxNews #IPFire #DietPi #OrangePi #Grml #Wine #Proton #ProtonExperimental #D7VK #LinuxMarketshare #FrameworkLaptop #LinuxKernel #GTK2 #XWayland #WayVNC #FosseryTech

  5. WayVNC 0.10 porta funzioni avanzate per il remote desktop su Wayland, con supporto multi‑output e miglioramenti utili per utenti e sviluppatori. #Wayland #WayVNC #Linux #RemoteDesktop

    linuxeasy.org/wayvnc-0-10-remo

  6. WayVNC 0.10 porta funzioni avanzate per il remote desktop su Wayland, con supporto multi‑output e miglioramenti utili per utenti e sviluppatori. #Wayland #WayVNC #Linux #RemoteDesktop

    linuxeasy.org/wayvnc-0-10-remo

  7. "Hmm, I wonder if I can use the external screen of my other computer as an external screen for my laptop over wifi?"

    2 minutes of Kagi'ing later...

    `sway create_output`, `swaymsg output HEADLESS-1 resolution 2560x1440 scale 1.5`, `wayvnc -o HEADLESS-1 0.0.0.0`, and it works!

    Seriously impressed now by #Wayland and #Sway now, this is much better than last time I tried something similar with Xorg. Kudos to everyone who made that possible! #wlroots #wayvnc

  8. So it looks like my wayvncctl IPC and command line tool are almost all grown up!

    It's come a long way since my vague idea back in September, and I'm proud of what it's become, largely thanks to the patient guidance of @andriyngvason and all the work he's already done on

    fosstodon.org/@lack/1093921353

  9. There we go. About 3 months after looking into it, I have opened the last PR in a series that implements the feature I wanted in

    github.com/any1/wayvnc/pull/200

    It was fun, and now there's more I want to do in the project!

  10. Now it's time to add more commands and events:
    • command to list all clients
    • command to list all outputs
    • command to disconnect a client
    • event when output capture device changes
    • command to terminate

    Each one is in its own git commit, but all in the same area, so there's the age-old question; one PR per command (but they have to be done sequentially else code conflicts), or one bigger PR that's harder to review…

    The maintainer preferred one big one:
    github.com/any1/wayvnc/pull/192

  11. So that's close... But if isn't running my example-event script doesn't start, and if wayvnc exits my script exits too.

    So I added optional '--wait' and '--reconnect' flags to wayvncctl; the '--wait' flag will poll for the Unix domain socket before running a command or listening for events, and '--reconnect' will, as the name implies, try to reconnect if wayvnc edits.

    github.com/any1/wayvnc/pull/185

    And events that indicate when each of these things happen:

    github.com/any1/wayvnc/pull/186

  12. So on with github.com/any1/wayvnc/pull/178 : Here I built that event mechanism, plus a registration IPC so that we only send events to control socket clients that are expecting them. And of course started with the events I wanted most: client-connected and client-disconnected which give details about a VNC client plus the current connected client count.

    I added an example script showing how to use a bash read-loop and to have a function that fires when the connection count changes.

  13. So wayvncctl was born (or will be, next release). I can bind a key in to run:

    wayvncctl set-output --cycle=next

    And my session cycles through the Wayland outputs - a working mechanism to use all the outputs!

    But what about my original dream to temporarily disable inputs when VNC connects, and restore when VNC disconnects? The control socket allowed remote control, but I needed asynchronous events that could send out when, say, a new VNC session was established…

  14. So wayvncctl was born (or will be, next release). I can bind a key in #sway to run:

    wayvncctl set-output --cycle=next

    And my #wayvnc session cycles through the Wayland outputs - a working mechanism to use all the outputs!

    But what about my original dream to temporarily disable inputs when VNC connects, and restore when VNC disconnects? The control socket allowed remote control, but I needed asynchronous events that #wayvnc could send out when, say, a new VNC session was established…

  15. After some experimentation, I was able to refactor the main code to do just that: stop capturing one output, move the virtual inputs, and start capturing another!

    To test it I had code that caught SIGUSR1 and rotated through the outputs. Fun, but not a great user interface. So I went about making a key-bind engine in wayvnc, and I submitted the PR:

    github.com/any1/wayvnc/pull/163

    Soon after, I got a wonderful review from the maintainer @andriyngvason - it was not quite ready…

  16. After some experimentation, I was able to refactor the #wayvnc main code to do just that: stop capturing one output, move the virtual inputs, and start capturing another!

    To test it I had code that caught SIGUSR1 and rotated through the outputs. Fun, but not a great user interface. So I went about making a key-bind engine in wayvnc, and I submitted the PR:

    github.com/any1/wayvnc/pull/16

    Soon after, I got a wonderful review from the maintainer @andriyngvason - it was not quite ready…

  17. No! I can't. There didn't seem to be any way to get to run a script for me, so I opened a GitHub issue asking for what I wanted, fully intending to implement it myself: github.com/any1/wayvnc/issues/

    In the course of this great discussion, we arrived at 3 important conclusions:

    • Wayvnc running a script itself has security implications
    • An external control socket like swaymsg could do all this and more
    • Multi-output support has more interesting use-cases

    So time to consider the use-cases…

  18. No! I can't. There didn't seem to be any way to get #wayvnc to run a script for me, so I opened a GitHub issue asking for what I wanted, fully intending to implement it myself: github.com/any1/wayvnc/issues/

    In the course of this great discussion, we arrived at 3 important conclusions:

    • Wayvnc running a script itself has security implications
    • An external control socket like swaymsg could do all this and more
    • Multi-output support has more interesting use-cases

    So time to consider the use-cases…

  19. Yet again, came through with exactly the timing I needed. If I connect to VNC and just disable the right-most output, everything automatically shifts to the one remaining output. No need to even involve kanshi or reconfigure waybar:

    swaymsg output DP-3 disable

    Then when I'm done, this brings it back again:

    swaymsg output DP-3 enable

    This actually worked very nicely!

    Next: Can I automate this so the "disable" happens when I connect over , and "enable" when I disconnect...?

  20. Yet again, #sway came through with exactly the timing I needed. If I connect to VNC and just disable the right-most output, everything automatically shifts to the one remaining output. No need to even involve kanshi or reconfigure waybar:

    swaymsg output DP-3 disable

    Then when I'm done, this brings it back again:

    swaymsg output DP-3 enable

    This actually worked very nicely!

    Next: Can I automate this so the "disable" happens when I connect over #wayvnc, and "enable" when I disconnect...?

  21. I'm currently implementing a control socket and related wayvncctl command line tool for , and it's been a fun journey! Thought I'd share my (ongoing) experiences.

    It all began, as all fun projects begin, with an itch I needed to scratch....

  22. I'm currently implementing a control socket and related wayvncctl command line tool for #wayvnc, and it's been a fun journey! Thought I'd share my (ongoing) experiences.

    It all began, as all fun #OpenSource projects begin, with an itch I needed to scratch....

    #OpenSource #developer #OpenSourceSoftware #development #stories

  23. I haven't coded in for a while, but have been working on a fun contribution to over the last few weeks. The kindness of the main dev on IRC and GitHub reviews as I revive my rusty C skills reminds me why I love ❤️

  24. Actually, can any one tell me what "average reported frame damage" means? This is in the context of , and my "frame damage" starts out low, but pretty quickly climes to 95.9% and holds there -- and my screen starts flickering. I'm _assuming_ that those two are related, but I don't really know what "frame damage" means.
    all the Internet results seem to assume that I'm concerned about damage to the frame of my car and I'm _pretty_ sure my car isn't involved in getting pixies to my monitor