#wlroots — Public Fediverse posts

PSA for distributions that use an older phoc with current phosh:

Starting from Phosh 0.56.0 (planned release date 2026-07-05) components like stevia (and likely phosh) will depend on phoc >= 0.55 (and thus #wlroots 0.20).

While it was always recommended to have the versions of the components of the stack in sync, some distros use phoc as old as 0.44.0 / wlroots 0.17 (from 2024). This already causes various issues for users but the session would at least start.

This won't be the case for 0.56.0 and later versions, unless you revert the changes. For 0.56 this will be rather small changes but it will become more involved over time so please update the compositor.

You can completely ignore this message if phosh, phoc and stevia are the same version.

#LinuxMobile #Phosh

PSA for distributions that use an older phoc with current phosh:

Starting from Phosh 0.56.0 (planned release date 2026-07-05) components like stevia (and likely phosh) will depend on phoc >= 0.55 (and thus #wlroots 0.20).

While it was always recommended to have the versions of the components of the stack in sync, some distros use phoc as old as 0.44.0 / wlroots 0.17 (from 2024). This already causes various issues for users but the session would at least start.

This won't be the case for 0.56.0 and later versions, unless you revert the changes. For 0.56 this will be rather small changes but it will become more involved over time so please update the compositor.

You can completely ignore this message if phosh, phoc and stevia are the same version.

#LinuxMobile #Phosh

PSA for distributions that use an older phoc with current phosh:

Starting from Phosh 0.56.0 (planned release date 2026-07-05) components like stevia (and likely phosh) will depend on phoc >= 0.55 (and thus #wlroots 0.20).

While it was always recommended to have the versions of the components of the stack in sync, some distros use phoc as old as 0.44.0 / wlroots 0.17 (from 2024). This already causes various issues for users but the session would at least start.

This won't be the case for 0.56.0 and later versions, unless you revert the changes. For 0.56 this will be rather small changes but it will become more involved over time so please update the compositor.

You can completely ignore this message if phosh, phoc and stevia are the same version.

#LinuxMobile #Phosh

PSA for distributions that use an older phoc with current phosh:

Starting from Phosh 0.56.0 (planned release date 2026-07-05) components like stevia (and likely phosh) will depend on phoc >= 0.55 (and thus #wlroots 0.20).

While it was always recommended to have the versions of the components of the stack in sync, some distros use phoc as old as 0.44.0 / wlroots 0.17 (from 2024). This already causes various issues for users but the session would at least start.

This won't be the case for 0.56.0 and later versions, unless you revert the changes. For 0.56 this will be rather small changes but it will become more involved over time so please update the compositor.

You can completely ignore this message if phosh, phoc and stevia are the same version.

#LinuxMobile #Phosh

PSA for distributions that use an older phoc with current phosh:

Starting from Phosh 0.56.0 (planned release date 2026-07-05) components like stevia (and likely phosh) will depend on phoc >= 0.55 (and thus #wlroots 0.20).

While it was always recommended to have the versions of the components of the stack in sync, some distros use phoc as old as 0.44.0 / wlroots 0.17 (from 2024). This already causes various issues for users but the session would at least start.

This won't be the case for 0.56.0 and later versions, unless you revert the changes. For 0.56 this will be rather small changes but it will become more involved over time so please update the compositor.

You can completely ignore this message if phosh, phoc and stevia are the same version.

#LinuxMobile #Phosh

#phoc now uses #wlroots 0.20, floating windows now show focus using an accent-colored frame and tiled windows have a small margin. We also support the xdg-dialog-v1 protocol to handle modal dialogs better.

2/x

phosh 0.55.0 is out 🚀📱:

There are multiple 🐛 fixes and some new features.

Check out the full release notes at https://phosh.mobi/releases/rel-0.55.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release.

#phosh #gtk #wlroots #gnome #linux #mobile #LinuxMobile #Librem5 #PinePhone

phosh 0.55.0 is out 🚀📱:

There are multiple 🐛 fixes and some new features.

Check out the full release notes at https://phosh.mobi/releases/rel-0.55.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release.

#phosh #gtk #wlroots #gnome #linux #mobile #LinuxMobile #Librem5 #PinePhone

phosh 0.55.0 is out 🚀📱:

There are multiple 🐛 fixes and some new features.

Check out the full release notes at https://phosh.mobi/releases/rel-0.55.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release.

#phosh #gtk #wlroots #gnome #linux #mobile #LinuxMobile #Librem5 #PinePhone

phosh 0.55.0 is out 🚀📱:

There are multiple 🐛 fixes and some new features.

Check out the full release notes at https://phosh.mobi/releases/rel-0.55.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release.

#phosh #gtk #wlroots #gnome #linux #mobile #LinuxMobile #Librem5 #PinePhone

phosh 0.55.0 is out 🚀📱:

There are multiple 🐛 fixes and some new features.

Check out the full release notes at https://phosh.mobi/releases/rel-0.55.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release.

#phosh #gtk #wlroots #gnome #linux #mobile #LinuxMobile #Librem5 #PinePhone

We've just tagged and relesed phoc 0.55~alpha1 🥳. This is basically 0.54.0 but using the recently released #wlroots 0.20.0 instead of 0.19.3. Please give it a try!

#phosh #LinuxMobile

The Wayland compositor #phoc saw some workspace related improvements but the major changes affect the handling of override-redirect windows in #X11 applications. This allows X11 applications like #emacs, #ardour, etc. to work better. We also updated to #wlroots 0.19.3.

4/x.

phosh 0.54.0 is out 🚀📱:

There's 🐛 fixes, improvements and some new features this time.

Check out the full release notes at https://phosh.mobi/releases/rel-0.54.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release:

#phosh #gtk #wlroots #gnome #linux #mobile #LinuxMobile #Librem5 #PinePhone

Let me get this straight: The only reason why I can't mirror my screens on most #wayland compositors is that wlr-output-management does not contain a property for screen mirroring?

Why is this not a feature????

I know wl-mirror exists but it's really not that good. The battery drain is real.

#niri #wlroots #sway

Its a fact, #HDR on #Linux, its taken 6 years from buying this TV to getting here, congratulations on everyone who worked on color-management-v1 for #Wayland.

This setup shows #wlroots (git) #sway (git) and #mpv

Set:

'output xxx { render_bit_depth 10; hdr off }'

In sway config then toggle using:

'swaymsg output xxx hdr toggle'

Next launch mpv using:

'mpv --target-colorspace-hint "path/file"'

Its a fact, #HDR on #Linux, its taken 6 years from buying this TV to getting here, congratulations on everyone who worked on color-management-v1 for #Wayland.

This setup shows #wlroots (git) #sway (git) and #mpv

Set:

'output xxx { render_bit_depth 10; hdr off }'

In sway config then toggle using:

'swaymsg output xxx hdr toggle'

Next launch mpv using:

'mpv --target-colorspace-hint "path/file"'

phosh 0.53.0 is out 🚀📱:

There's plenty of 🐛 fixes, improvements and refinements of existing features this time.

Check out the full release notes at https://phosh.mobi/releases/rel-0.53.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release.

#phosh #Librem5 #PinePhone #gtk #wlroots #gnome #linux #mobile #LinuxMobile

wlroots 0.20.0-RC1 just released 16 hours ago and it has "Foreign toplevel support for ext-image-capture-source-v1" (quoting from the changelog). This means that when it's fully out and when Sway has a release that supports it, direct window screenshots using grim will "just work" without git versions.

https://gitlab.freedesktop.org/wlroots/wlroots/-/releases/0.20.0-rc1

#wlroots

phosh 0.52.0 is out 🚀📱:

There's some important 🐛 fixes and some user visible improvements - maybe a bit less than usual as the end of the year got a bit busy and we decided to rather not rush things in.

Check out the full release notes at https://phosh.mobi/releases/rel-0.52.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release.

#phosh #Librem5 #PinePhone #gtk #wlroots #gnome #linux #mobile #LinuxMobile

Would be great if that would happen:

https://social.phosh.mobi/@ev/statuses/01KB51N0TPZ0MS45Y082E99J5J

#phosh #LinuxMobile #gtk #wlroots #pcm2026

Would be great if that would happen:

https://social.phosh.mobi/@ev/statuses/01KB51N0TPZ0MS45Y082E99J5J

#phosh #LinuxMobile #gtk #wlroots #pcm2026

Would be great if that would happen:

https://social.phosh.mobi/@ev/statuses/01KB51N0TPZ0MS45Y082E99J5J

#phosh #LinuxMobile #gtk #wlroots #pcm2026

Would be great if that would happen:

https://social.phosh.mobi/@ev/statuses/01KB51N0TPZ0MS45Y082E99J5J

#phosh #LinuxMobile #gtk #wlroots #pcm2026

Would be great if that would happen:

https://social.phosh.mobi/@ev/statuses/01KB51N0TPZ0MS45Y082E99J5J

#phosh #LinuxMobile #gtk #wlroots #pcm2026

phosh 0.51.0 is out 🚀📱:

Another 6️⃣ weeks have passed and we have some new features, quality of life improvements, and 🐛 fixes. Check out the full release notes at https://phosh.mobi/releases/rel-0.51.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release.

#phosh #Librem5 #PinePhone #gtk #wlroots #gnome #linux #mobile #LinuxMobile

phosh 0.50.1 is out 🚀📱:

This is just a small point release update over 0.50.0 to fix some critical 🐛. Check out the full release notes at https://phosh.mobi/releases/rel-0.50.1 for details.

🙏 to everyone who contributed to this release.

#phosh #Librem5 #PinePhone #gtk #wlroots #gnome #linux #mobile #LinuxMobile

#Phosh and Phoc had nightlight support since ages but the only phone with out of the box gamma LUT support that could make use of it so far was the #PinePhone.

Thanks to @fizzo 's kernel work it works on Qualcomm based phones too now and makes the (optional) night light quick toggle useful on way more devices and looking at the bright AMOLED displays at night much more pleasant.

Demo below is on a #SHIFT6mq.

#LinuxMobile #wlroots

Phosh's compositor phoc gained workspace support. This is mostly useful in
docked setups with external mouse and a keyboard attached but we
intend to make use of it in the future for the mobile use case too.

We also switched to #wlroots 0.19.1.

2/x

phosh 0.50.0 is out 🚀📱:

We have some new features, quality of life improvements, (a bit more than usual) under the hood work and 🐛 fixes, check out the full release notes at
https://phosh.mobi/releases/rel-0.50.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release.

#phosh #Librem5 #PinePhone #gtk #wlroots #gnome #linux #mobile #LinuxMobile

I keep forgetting Phoc is wlroots. I wonder how well Sway runs on Halium phones, then. Can't seem to find any info about that.

#Sway #Phoc #Phosh #wlroots #Halium #LinuxMobile #LinuxPhones

phosh 0.49.0 is out 🚀📱:

We have some new features, quality of life improvements, under the hood work and 🐛 fixes, check out the full release notes at https://phosh.mobi/releases/rel-0.49.0/ for details or see 👇 for a short 🧵

🙏 to everyone who contributed to this release.

#phosh #Librem5 #PinePhone #gtk #wlroots #gnome #linux #mobile #LinuxMobile

Some #wayland news on #OpenBSD from #l2k25:
- pointer acceleration works now in libinput (thanks volker@)
- volker@ also has prepared a wlroots patch to enable outputs hotplugs (when you add an external monitor) that should land in the short future.
- I've done some work on wscons / wsmux to have wayland (and also eventually Xorg) behave better with multiple keyboards without needing ugly hacks. That also manages hot-plugin of input devices (and disconnect/reconnect during suspend/resume). That code will take longer to be put in shape to be reviewed and hopefully committed.
- A number of the wayland ports have been updated, and an update of pixman to 0.46.4 (which is needed to upgrade to #wlroots 0.19) is also almost ready. Once it's in wlroots, sway and labwc can be updated.

dwl - dwm for Wayland

A hackable (~3200 line single .c file implementation) compositor for Wayland based on wlroots.

https://codeberg.org/dwl/dwl

#linux #wayland #wlroots

Erstes Release: Wayback 0.1 erschienen
https://linuxnews.de/wayback-0-1-erschienen/ #xorg #wayland #wayback #xwayland #wlroots #alpinelinux #linux

@mms It's a tricky one.

I don't necessarily blame the #wlroots developers here, but each release has breaking changes which they could do better to document/manage.

Take the release notes:

https://gitlab.freedesktop.org/wlroots/wlroots/-/releases

Some of this information is excellent, but doesn't go far enough. When you have a API in flux, having tooling to help might be worthwhile.

#hare #harelang did this with their hare-update(1) tool recently:

https://harelang.org/blog/2025-06-11-hare-update/

I'd rather see something like #coccinelle scripts in #wlroots to help with the transition, akin to what #harelang are doing.

I know #hikari is coming from 0.15 as its starting point, but the fact remains there's going to be further breaking changes, and I feel this should be addressed.

I might have to see what I can do to help as I do feel this is important.

I know that if the delta between releases is small, the changes might be small, but that's not guaranteed to cause big, sweeping changes. Case in point is the whole wlr_output_damage deprecated for wlr_damage_ring -- we're not just talking changes to the API, but rather, changes in *functionality* which I still don't see documented anywhere.

Hmm. The future.... great....

#wayland #compositors #hikari

So I've slowly been trying to resurrect hikari -- a cwm(1)-like compositor for #wayland, written by @acmelabs but hasn't received any love.

http://hikari.acmelabs.space/

I know that darts is preferred. but... fuck that.

I've moved it over to git (history intact), and mirrored things here:

https://github.com/ThomasAdam/hikari

In trying to drag this thing free of dust, I've been working on a few things:

1) Use meson to build
2) Upgrade wlroots from the support 0.15 version to 0.18

Guess how point 2 is going...

Abysmally.

https://github.com/ThomasAdam/hikari/tree/ta/wlroots-upgrade

So far, I'm at 0.16, working on 0.17. The end goal is 0.18 support.

#wlroots is great to wrap up the so-called boilerplate, but it's an absolute joke for developers trying to hop from release-to-release. The documentation sucks, the rationale is non-existent for changes made, and I've had to build each 0.X release to then `git-diff` between the releases.

wlroots needs to do a lot better at not fucking with the API so much -- and if they must -- they must do better to document where the changes are breaking, why, and what the expected fix is.

I shouldn't have to `git diff` releases to determine this.

Heya folks! It's sync day, and that means it's time for the weekly Solus roundup! This week, we have the @kde #Plasma 6.4 update going out to everyone, along with KDE #Frameworks, #Gear, #wlroots, and much more.

Read all about it on our forums: https://discuss.getsol.us/d/11786-sync-updates-for-week-29-2025

#FOSS #Linux #Solus #OpenSource

- Evan

In a bitterly predictable twist, things didn't work out with #Wayland because of #Nvidia and #wlroots compatibility issues.

I also wanted to be able to switch tiling and floating layouts at will, so #i3 (my love) ended up being a no serve.

I settled on the deeply unpopular combination of #lxqt and cortile.

Maybe eventually I switch to something like AwesomeWM but for now this seems good.

https://github.com/leukipp/cortile

#Linux

Turning my bare-metal #popos install into a virtual machine was an act of supreme hubris. Like all tragic heroes, I was punished by the machine gods for my defiance of nature.

(I got my data out, at least.)

But my #fedora install is looking good, I setup #sway for productivity and #kdeplasma for gaming compatibility. #wlroots doesn't brick itself when the #nvidia GPU is in a hybrid configuration, but it HATES rendering on it.

#virtualization #Fedora42 #linux

#Phosh's compositor #phoc got updated to the latest stable #wlroots release 0.19.0 giving us all the goodies from there. Apart from that it now remembers your phone's display resolution in case you want something different than the calculated default. It also supports adaptive sync now and gained support for protocols like shortcuts-inhibit.

2/x

WTAF how is #gtk getting n_planes = 1079097857 (consistently the same number across executions) from eglExportDMABUFImageQueryMESA when trying to export a GdkGLTexture containing a #wlroots gles2 rendered scene? 0.o

Wait, that's not just some random number, that's the low 32 bits of the modifier field!!

OHHHH SHIT it's not mentioned in the extension spec at all but with current Mesa code, modifiers is expected to be AN ARRAY of per-plane entries. The spec only says that the stuff passed to the next step eglExportDMABUFImageMESA is expected to be arrays. #egl #mesa3d #dmabuf

Reported: https://gitlab.freedesktop.org/mesa/mesa/-/issues/12771

WTAF how is #gtk getting n_planes = 1079097857 (consistently the same number across executions) from eglExportDMABUFImageQueryMESA when trying to export a GdkGLTexture containing a #wlroots gles2 rendered scene? 0.o

Wait, that's not just some random number, that's the low 32 bits of the modifier field!!

OHHHH SHIT it's not mentioned in the extension spec at all but with current Mesa code, modifiers is expected to be AN ARRAY of per-plane entries. The spec only says that the stuff passed to the next step eglExportDMABUFImageMESA is expected to be arrays. #egl #mesa3d #dmabuf

Reported: https://gitlab.freedesktop.org/mesa/mesa/-/issues/12771

WTAF how is #gtk getting n_planes = 1079097857 (consistently the same number across executions) from eglExportDMABUFImageQueryMESA when trying to export a GdkGLTexture containing a #wlroots gles2 rendered scene? 0.o

Wait, that's not just some random number, that's the low 32 bits of the modifier field!!

OHHHH SHIT it's not mentioned in the extension spec at all but with current Mesa code, modifiers is expected to be AN ARRAY of per-plane entries. The spec only says that the stuff passed to the next step eglExportDMABUFImageMESA is expected to be arrays. #egl #mesa3d #dmabuf

Reported: https://gitlab.freedesktop.org/mesa/mesa/-/issues/12771

WTAF how is #gtk getting n_planes = 1079097857 (consistently the same number across executions) from eglExportDMABUFImageQueryMESA when trying to export a GdkGLTexture containing a #wlroots gles2 rendered scene? 0.o

Wait, that's not just some random number, that's the low 32 bits of the modifier field!!

OHHHH SHIT it's not mentioned in the extension spec at all but with current Mesa code, modifiers is expected to be AN ARRAY of per-plane entries. The spec only says that the stuff passed to the next step eglExportDMABUFImageMESA is expected to be arrays. #egl #mesa3d #dmabuf

Reported: https://gitlab.freedesktop.org/mesa/mesa/-/issues/12771

WTAF how is #gtk getting n_planes = 1079097857 (consistently the same number across executions) from eglExportDMABUFImageQueryMESA when trying to export a GdkGLTexture containing a #wlroots gles2 rendered scene? 0.o

Wait, that's not just some random number, that's the low 32 bits of the modifier field!!

OHHHH SHIT it's not mentioned in the extension spec at all but with current Mesa code, modifiers is expected to be AN ARRAY of per-plane entries. The spec only says that the stuff passed to the next step eglExportDMABUFImageMESA is expected to be arrays. #egl #mesa3d #dmabuf

Reported: https://gitlab.freedesktop.org/mesa/mesa/-/issues/12771

Happy new year everyone!

phosh 0.44.1 is out 🚀📱 :

This is a small bug fix release containing stability fixes for #phosh and #phoc that shouldn't wait 'til 0.45.0. Most of them (but not all) address issues introduced in 0.44.0.

Check out the release notes at https://phosh.mobi/releases/rel-0.44.1/.

🙏 to everyone who contributed to this release.

#phosh #librem5 #pinephone #gtk #wlroots #gnome #linux #mobile #LinuxMobile

Are there any tiling #Wayland #compositors that work well with the proprietary #Nvidia drivers? #Wlroots insists Nvidia doesn't work well with it, and I'm looking to switch my desktop off of KDE.

Дрю ДеВолт — автор языка Hare и платформы кодохостинга SourceHut

Дрю ДеВолт объясняет , что веб-интерфейс Github.com требует множества лишних действий. Гораздо эффективнее использовать консольный почтовый клиент , отправляя тот же пулл-реквест одной командой из консоли Американский разработчик Дрю ДеВолт (Drew DeVault) известен как создатель и исполнительный директор платформы для хостинга проектов SourceHut , которую Фонд сохранения свободы ПО выбрал как альтернативу майкрософтовскому сервису GitHub (наряду с CodeBerg ) в рамках кампании Give Up GitHub по уходу свободных проектов с этого коммерческого хостинга, задача которого — генерировать продажи Copilot. ДеВолт также известен как автор нового языка системного программирования Hare, который похож на С, только лучше и проще его.

https://habr.com/ru/companies/ruvds/articles/863866/

#ruvds_статьи #Дрю_ДеВолт #Drew_DeVault #sway #wlroots #srht #scdoc #aerc #chopsui #TrueCraft #KnightOS #qutebrowser #vim #IRCклиент #WeeChat #mutt #fish #mrsh #Redict #Redis #Hare #Helios #Himitsu #QBE #LLVM

Дрю ДеВолт — автор языка Hare и платформы кодохостинга SourceHut

Дрю ДеВолт объясняет , что веб-интерфейс Github.com требует множества лишних действий. Гораздо эффективнее использовать консольный почтовый клиент , отправляя тот же пулл-реквест одной командой из консоли Американский разработчик Дрю ДеВолт (Drew DeVault) известен как создатель и исполнительный директор платформы для хостинга проектов SourceHut , которую Фонд сохранения свободы ПО выбрал как альтернативу майкрософтовскому сервису GitHub (наряду с CodeBerg ) в рамках кампании Give Up GitHub по уходу свободных проектов с этого коммерческого хостинга, задача которого — генерировать продажи Copilot. ДеВолт также известен как автор нового языка системного программирования Hare, который похож на С, только лучше и проще его.

https://habr.com/ru/companies/ruvds/articles/863866/

#ruvds_статьи #Дрю_ДеВолт #Drew_DeVault #sway #wlroots #srht #scdoc #aerc #chopsui #TrueCraft #KnightOS #qutebrowser #vim #IRCклиент #WeeChat #mutt #fish #mrsh #Redict #Redis #Hare #Helios #Himitsu #QBE #LLVM