Raphael Nestler

But I should definitely fix the panic :slightly_smiling_face:

@dbrgn Can you try setting `$DBUS_SESSION_BUS_ADDRESS` to something like `unix:path=/run/user/1000/bus` where `1000` is your `UID`?

I found a solution: `/etc/pacman.d/scripts/reboot-arch-btw-hook.sh` ``` #!/bin/bash sudo -u $SUDO_USER DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$SUDO_UID/bus /usr/bin/reboot-arch-btw ``` `/etc/pacman.d/hooks/99-reboot-arch-btw.hook` ``` [Trigger] Operation = Upgrade Type = Package Target = * [Action] Description = Check whether...

> great, it works! I'm not sure if this is something that could be part of the AUR package? (Or maybe just a separate package that depends on reboot-arch-btw.) It's...

> Checking for D-Bus service presence of [rfjakob/systembus-notify](https://github.com/rfjakob/systembus-notify), and utilizing it to alert the user when available would resolve this issue. @emansom This looks interesting as well, but I don't...

> It'd be stellar if these would be translatable through PO files. Does it necessarily need to be PO files or would something like `.yml` files also work? A quick...

> Maybe we should make the location required again, but allow omitting all fields? I don't think this provides much value. What's the purpose of an empty object? > Alternatively,...

My favored solution would be to have `location` optional but require that if it is provided that at least one subkey must be provided (so making `"location": {}` illegal).

I'd suggest to leave it as is for v15 (optional `location` field, but if it is present have at least `lat`/`lon`) to not block the release. > But to keep...

I'd prefer to solve it at the directory level an be able to provide multiple endpoints like: ```json [ { "url": "https://my.space.api/013/status.json", "supported_api_versions": ["0.13"] }, { "url": "https://my.space.api/status.json", "supported_api_versions": ["14",...