Chris Vogel @me@chrichri.ween.de

not yet

intent

no sarcasm, no irony

hashtag

#packetfence, #yunohost, #flohmarkt, #librem5, #ShotOnLibrem5, #microblogpub, #Lite3DP, #deskhop, #espressi

matrix

@chrichri:ween.de

sourcehut

https://git.sr.ht/~chrichri/

codeberg

https://codeberg.org/ChriChri

member

@ev@social.phosh.mobi, @noybeu@mastodon.social, https://www.duh.de/

  • Notes
  • Articles
  • Remote follow
Chris Vogel's avatar
Chris Vogel
@me@chrichri.ween.de

#PostmarketOS allows to have multiple users. If automatic login is disabled on start a login screen is shown presented by #greetd typically running as the system user greetd.

greetd is logged in automatically to do its magic and systemd starts all the configured user services for that user.

#udiskie is integrated as such a service and mounts all removable media to /run/media/greetd - on my #Shift6mq the sdcard.

After logging in the greetd user session is logout out and the new session for the authenticated user is started. udiskie for the greetd session is stopped leaving the sdcard mounted to the path for greetd.

udiskie starts for the authenticated user, but does not mount the removable media, because it is already mounted for the former logged in greetd.

No music in #gapless 🤷

An easy way around this is to change the service file for udiskie to the new version from the example directory of udiskies repository by copying it to /etc/systemd/user/.

Once systemd picked up the changes udiskie will not be started for system users anymore and systemd will run udiskie-umount after stopping the service on user logout.

Now one UserA can logout and UserB can use the same sdcard if file permissions allow.

udiskie/example/udiskie.service at master · coldfix/udiskie GitHub
  • permalink
  • interact from your instance
  • an hour ago
Powered by microblog.pub 2.0.0+ynh2 and the ActivityPub protocol. Admin.