Tootfinder

Opt-in global Mastodon full text search. Join the index!

@jamesthebard@social.linux.pizza
2025-08-18 23:42:17

Did run into an issue with `jellyfin` starting a bit too fast and somehow trying to read the metadata directory _before_ it's available. I added a delay to the `/etc/systemd/system/jellyfin.service.d/jellyfin.service.conf` by adding a line to the `[Service]`:
```
[Service]
ExecStartPre=bash -c "while [ ! -d /opt/jellyfin/metadata ]; do sleep 1; done"
```
This fixes the issue and now the service comes up after reboot without restarting the service man…

@pygospa@social.linux.pizza
2025-09-20 10:00:18

Me and my new #yubikey5 part 2:
Now we get to the nitty-gritty parts. I'm using #mbsync to sync multiple #imap accounts to local

Screenshot of a terminal in background showing a manual triggering of mbsync with one of my mail addresses, and a GTK window in foreground (pinentry-gtk) prompting me to insert the PIN to unlock my Yubikey to decript the passwords provided by the GPG encrypted password store from pass.
Full-screen terminal window showing the output from `journalctl -n0 -f` when I plug in the youbikey and wait while for the automatic mailsync service to trigger. The output shows that while the Yubikey is inserted and properly recognized, when mbsyncer starts it asks for the PIN, but directly gets a `PIN callback returned error: IPC call has been cancelled` message, which in turn makes the decription fail, which leads to a skipping of the account in mbsync. And this will continue for the next …
Termial showing the bat output from the udev rule I wrote: `ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1050", ATTR{idProduct}=="0407", TAG+="systemd", ENV{SYSTEMD_USER_WANTS}="yubikey-unlock.service"` This file lives under: `/etc/udev/rules.d/99-yubikey-unlock.rules`
Console with vim showing the content of the new `systemd` service I wrote, which lives in my home dir under: `.config/systemd/user/yubikey-unlock.service` Content: ``` [Unit] Description=Yubikey GPG Unlock After=graphical-session.target [Service] Type=oneshot ExecStart=/bin/bash -c 'TEMP_FILE=$(/usr/bin/mktemp); echo "unlock test" | /usr/bin/gpg --encrypt -r FEE1636BFD47D3E8 > "$TEMP_FILE"; /usr/bin/gpg --quiet --decrypt "$TEMP_FILE" >/dev/null 2>&1; /usr/bin/rm "$TEMP_FILE"' Environmen…
@hllizi@hespere.de
2025-06-25 06:53:13

I'm confronted with a very similar problem, has anything changed about the situation. (I.e. is it possible to start a process manually and then manually mark the systemd unit that would normally start it as running and have it behave like the service was started by systemd?)