Arch Linux User Repository

Yeah, it is currently not easy with the various compositors (looking at you wayfire and your restrictions). Or mostly because of the backward incompatible changes of wlroots.
Good that you still could somehow sort it out. (And I don't mention that there was a third option... The wlroots-git PKGBUILD could have been pinned to a specific tag (v0.14.1 for example). Kinda forgot about this possibility >.>)
As a sidenote: If there are patches (or rather fixes) for labwc which are worth picking up, you can always leave a comment for that package. And if I can rather easily backport those, they may be added :D

Okay, updating wlroots-git was a washout. But after a few hours sleep, I took half an hour or so to rebuild everything to use the stable wlroots version. I was then able to install hikari without problems.

While I have successfully booted into the environment, I haven;t had a chance to check out the configuration, and, more importantly, whether the layer-shell protocol works with my panel and task-bar, but, touch wood, things are looking good.

Thanks for your prompt attention Irvine

Okay, I to need sleep on this for a couple of hours first:

Updating wlroots-git is not a problem, and I will do so as soon as I can.

With regard to switching to the stable wlroots, I would love to. The problem is that the current stable labwc is not properly implementing the layer-shell protocol. In the git-version, the bug was fixed a week or so ago.

My other wlroots compositors are wayfire and sway. So, mainly because of the wayfire dependency chain, but also the various peripherals needed for a working environment, switching between wlroots versions is non-trivial

Anyway, I hope you can see why I really need to sleep on switching to the stable wlrootsfor a bit first.

Irvine

Not that surprising, that it even happens with the VCS package. Development seems to have slowed down.
But looking at the version of your wlroots-git package, could you please update it? Upstream introduces rather often breaking changes and the compositors don't add support for older wlroots packages.
Which can also mean, that current wlroots-git also has breaking changes again. So better would be, if possible, you switched to the stable wlroots package.

wlroots-git 0.14.0.r303.gf7ea33da-1

It may be worth noting that I get the exact same error with * hikari-darcs*

Irvine

Hello Irvine.
Which of the one do you have installed? wlroots or wlroots-git? And what version of those?.

I get the following bmake error src/layer_shell.c:202:35: error: ‘struct wlr_layer_surface_v1’ has no member named ‘client_pending’

The surrounding context is here:

--- layer_shell.o ---
src/layer_shell.c: In function ‘hikari_layer_init’:
src/layer_shell.c:202:35: error: ‘struct wlr_layer_surface_v1’ has no member named ‘client_pending’
  202 |   layer->layer = wlr_layer_surface->client_pending.layer;
      |                                   ^~
src/layer_shell.c: In function ‘damage_popup’:
src/layer_shell.c:312:49: error: ‘struct wlr_xdg_surface’ has no member named ‘geometry’
  312 |   int popup_sx = popup->geometry.x - popup->base->geometry.x;
      |                                                 ^~
src/layer_shell.c:313:49: error: ‘struct wlr_xdg_surface’ has no member named ‘geometry’
  313 |   int popup_sy = popup->geometry.y - popup->base->geometry.y;
      |                                                 ^~
*** [layer_shell.o] Error code 1

bmake: stopped in /home/stupidme/Git/Aur/hikari/src/hikari-2.3.2
1 error

bmake: stopped in /home/stupidme/Git/Aur/hikari/src/hikari-2.3.2
==> ERROR: A failure occurred in build().
    Aborting...
=$ 

Irvine

Good if it was working with makepkg.
But I'm curious what the error was with the AUR-helper. But don't expect to much in that regard. There is no need to cover corner cases with those, as they're officially unsupported.

I was unable to successfully install the latest version with paru. Pulling the git repo manually and building manually seemed to work!

Oh, sorry. I completly misunderstood your question, central_thing :D And agree. Should be fine adding this.

What is the version of your wlroots package Dariusity? Or formulated differently: Do you have wlroots from the repo or wlroots-git installed?

I get this while making..

Starting build()...
cc -pipe -march=x86-64 -mtune=generic -O2 -pipe -fno-plt  -DNDEBUG -D_POSIX_C_SOURCE=200809L -DHAVE_XWAYLAND=1 -DHAVE_GAMMACONTROL=1 -DHAVE_SCREENCOPY=1 -DHAVE_LAYERSHELL=1 -DHAVE_VIRTUAL_INPUT=1 -Wall -I. -Iinclude -DHIKARI_ETC_PREFIX=/ -I/usr/include/libdrm -I/usr/include/pixman-1 -I/usr/include/uuid  -DWLR_USE_UNSTABLE=1  -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/lzo -I/usr/include/pixman-1 -pthread   -I/usr/include/cairo -I/usr/include/lzo -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1   -I/usr/include/pixman-1         -I/usr/include/  -D_FORTIFY_SOURCE=2 -c src/action.c
In file included from include/hikari/layer_shell.h:4,
                 from include/hikari/server.h:29,
                 from src/action.c:7:
/usr/include/wlr/types/wlr_layer_shell_v1.h:52:52: error: field 'keyboard_interactive' has incomplete type
   52 |  enum zwlr_layer_surface_v1_keyboard_interactivity keyboard_interactive;
      |                                                    ^~~~~~~~~~~~~~~~~~~~
*** Error code 1

I doubt there's any dependencies for keyboard-related packages provided though.

Oh I had no trouble building it! Rather, I think WTIH_VIRTUAL_INPUT=yes should be set by default. That's just my opinion, though.

Added WITH_VIRTUAL_INPUT=YES to the PKGBUILD in build() and building the package worked fine for me.
Best would be if you posted your error message.

Any reason the AUR package does not build with WITH_VIRTUAL_INPUT=YES by default? This is required for wayland vnc.

Anyone else having the problem, that hikari launches for a brief moment and crashes down with glamor: No eglstream capable devices found?
Ran updates yesterday and got today this surprise present. Still looking for the culprit, but maybe someone already figured it out? And a rebuild doesn't help..

Edit: Nothing to do with the "error" message. Something broke with pango 1.48.3.
Back to 1.48.2 and everything is fine. But who is now at fault? Bug in pango or did something change and hikari needs to adapt.. Openbox worked fine with the latest pango.

Why downgrade? Just rebuild this package, Katsuki.

"hikari: error while loading shared libraries: libwlroots.so.6: cannot open shared object file: No such file or directory"

I updated my system and libwlroots.so updated to version 7. How to install older version of this library?

It seems that hikari doesn't need suid to run on archlinux, and WITHOUT_SUID=YES should be added to bmake install.

Building in a chroot environment fails, suggesting that wayland-protocols should be added to makedepends.

 Starting build()...
bmake: "/build/hikari/src/hikari-2.0.0/Makefile" line 59: warning: "pkg-config --variable pkgdatadir wayland-protocols" returned non-zero status
Package wayland-protocols was not found in the pkg-config search path.
Perhaps you should add the directory containing `wayland-protocols.pc'
to the PKG_CONFIG_PATH environment variable
Package 'wayland-protocols', required by 'wlroots', not found
bmake: "/build/hikari/src/hikari-2.0.0/Makefile" line 102: warning: "pkg-config --cflags wlroots" returned non-zero status
wayland-scanner server-header /stable/xdg-shell/xdg-shell.xml xdg-shell-protocol.h
Could not open input file: No such file or directory
*** Error code 1

Stop.
bmake: stopped in /build/hikari/src/hikari-2.0.0
==> ERROR: A failure occurred in build().

@TrialnError: Thanks! I fixed it as per your suggestion.

After testing a bit, the install line needs to look like this:

bmake DESTDIR="${pkgdir}" PREFIX=/usr ETC_PREFIX=/ install

Edit: One thing that still seems off to me is the placement of the wallpaper. In my opinion it should be /usr/share/hikari/background and not /usr/share/backgrounds/hikari. But maybe it is a canonical path. Dunno. It bothers me not that much if this wrongly placed or not.

Apparantly the changes to the build-system made their way into 2.0 which produces the following result:

.
└── hikari
    ├── etc
    │   └── etc
    │       ├── hikari
    │       │   └── hikari.conf
    │       └── pam.d
    │           └── hikari-unlocker
    └── usr
        ├── bin
        │   ├── hikari
        │   └── hikari-unlocker
        └── share
            ├── backgrounds
            │   └── hikari
            │       └── hikari_wallpaper.png
            ├── man
            │   └── man1
            │       └── hikari.1.gz
            └── wayland-sessions
                └── hikari.desktop

The files in /etc are placed in the wrong spot with an extra etc directory. Looking at the changes there is DESTDIR support and now it should suffice to simply set PREFIX. Will test it locally and report back.

Oh? Did I get tricked by a feature of darcs? :D Well, okay. Thanks for letting me know :)

@TrialnError: 1.0.2 does not have layer-shell support. According to the author it is going to be part of 1.1.0 (probably by the end of the month).

Could maybe WITH_LAYERSHELL=YES added to support apps which rely on the layer-shell protocol? 1.0.2 added support for this.
See: https://hub.darcs.net/raichoo/hikari/patch/a550b3b6af6559624c991f2c57ab0aa16ed65f5b

Best regards