FS#58856 - [usbmuxd]: User is not created

Attached to Project: Arch Linux
Opened by Tobias Hunger (hunger) - Sunday, 03 June 2018, 18:40 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 04 June 2018, 17:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After installing usbmuxd I get errors in the log about the service being unable to start due to no usbmux user/group.

The unit file references those, but they are not known in a freshly installed arch Linux system.

Adding a small sysusers.d snippet fixes the issue. This is what I have in /usr/lib/sysusers.d/usbmuxd.conf:

# User for usbmuxd
g usbmux - - -
u usbmux - - -


Additional info:
* usbmuxd 1.1.0+28+g46bdf3e-1


Steps to reproduce:
* Install usbmuxd in a fresh Arch Linux
* Reboot
* Check journalctl for entries of usbmuxd service.


This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 04 June 2018, 17:07 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Sunday, 03 June 2018, 18:56 GMT
So it would have been created in the post-install hook. Why wasn't it?

Edit: Oh, I misread,sorry.

Edit2: No, I'm wrong again. The user and group are created in the post_install scriptlet. Everything should work fine.
Comment by Tobias Hunger (hunger) - Sunday, 03 June 2018, 19:01 GMT
@Scimmia: Sorry if I was not clear in my description. I did want to provide the fix along with the report, but I should have had that more clearly separated.

Adding this sysusers.d snippet fixes the issue for me. That snippet was added by myself and is *not* part of the Arch Linux package.
Comment by Doug Newgard (Scimmia) - Sunday, 03 June 2018, 19:04 GMT Comment by Jan de Groot (JGC) - Sunday, 03 June 2018, 22:12 GMT
The postinstall script uses a static uid/gid, so if that is used by a different user or group the user and/or group will not be created by the install script.

We should change this package to sysusers.d.
Comment by Doug Newgard (Scimmia) - Sunday, 03 June 2018, 22:17 GMT
Nothing else should be using 140, and the switch to sysuser.d is covered by a todo already.
Comment by Tobias Hunger (hunger) - Monday, 04 June 2018, 17:02 GMT
Sorry, this was my mess-up:-/ The user should indeed exist on normal systems.

Loading...