hikari wayland compositor (fork of raichoo's hikari) (https://hikari.acmelabs.space)
#51Feature Request: add wlr-output-management-unstable-v1 protocol
I have wanted to use hikari for quite awhile but I have been unable to get wayland to use 144hz refresh rate as its default. The only way I found to make wayland use it is with something like wlr-randr which requires this protocol to be implemented.
edit: I understand this is a fork I just stumbled upon it today when repackaging hikari on NixOS for myself (it was removed due to being unmaintained), but I saw you were keeping it up to date with the latest version of wlroots on here. After updating my build file and finally getting it to build it with this fork I am getting errors when attempting to launch things, foot giving the no sub compositor error and wmenu the other one. Here is a log of my session (hikari 2> log) https://pastebin.com/5EsYvhnG. It seems the errors are coming from the programs but they work fine under labwc. Was anything else added that was required to build maybe that isn't just the update to wlroots that I didn't catch?
Not sure if this is maybe just a problem with my building of it or not, https://pastebin.com/4YweaeQ8 is my mkderivation if it helps at all. It is mostly the same mkderivation that 2.3.3 had. Except it is using wlroots 0.17.3 and I added xcbutilwm because I think wlroots/xwayland didnt provide xcb_ewmh.h that something needed. Maybe I need to use 0.17.0? Sorry this kinda turned into 2 issues instead of one 😅.
- description updated
- description updated
Thank you for keeping an eye on this repository. I am thinking of implementing wlr-output-management-unstable-v1 protocol, but there is a lot to do to fully support the protocol. To start with, what you need now is 1) resolve foot and wmenu-run aborting, and 2) use 144hz refresh rate, right?
For the foot aborting issue, please try this patch: https://hub.darcs.net/hiroo/hikari/patch/6661747014986f7b41ee9f723d1370325b345620
Thank you for getting back so quick, yeah that issue order makes the most sense, I assume the protocol will take a bit of work to implement. I just updated my build file with the latest patch and it allows foot to open. Still no wmenu, I know wmenu also wouldn't run on 2.3.3.
For wmenu-run to work, we need to implement xdg_activation_v1 protocol.
Ah I see, I can use something like bemenu or tofi instead as those work without it (gives me more control of customization anyways). wmenu was just a nice drop in for dmenu that was fairly close as a wayland implementation.
