Bug 52243

Summary: The use of @daemon_user@ does not work.
Product: colord Reporter: Dennis Veatch <dennisveatch>
Component: daemonAssignee: Richard Hughes <richard>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Dennis Veatch 2012-07-18 18:51:36 UTC 
While compiling from source and using --with-daemon-user the word "yes" is used as the user name for User= in /usr/share/dbus-1/system-services/org.freedesktop.ColorManager.service.

If --without-daemon-user is used, "no" is used for the user name. The same thing also happens to /usr/lib/systemd/system/colord-sane.service.



A snippet of the relevant journalctl output;

Jul 18 10:09:21 sidney dbus-daemon[2945]: dbus[2945]: Encountered error 'Failed to open "/etc/dbus-1/system.d/org.freedesktop.ColorManager.conf": Permission denie...nager.conf'
Jul 18 10:09:21 sidney dbus[2945]: Encountered error 'Failed to open "/etc/dbus-1/system.d/org.freedesktop.ColorManager.conf": Permission denied' while parsing '...anager.conf'
Jul 18 10:09:21 sidney dbus-daemon[2945]: Unknown username "no" in message bus configuration file
Jul 18 10:09:21 sidney dbus-daemon[2945]: dbus[2945]: [system] Reloaded configuration
Jul 18 10:09:21 sidney dbus[2945]: [system] Reloaded configuration
Jul 18 10:09:21 sidney dbus-daemon[2945]: Unknown username "no" in message bus configuration file
Jul 18 10:09:21 sidney dbus-daemon[2945]: Unknown username "no" in message bus configuration file
Jul 18 10:09:21 sidney dbus-daemon[2945]: dbus[2945]: [system] Reloaded configuration
Jul 18 10:09:21 sidney dbus[2945]: [system] Reloaded configuration
Jul 18 10:09:21 sidney systemd[1]: Reloading.
Jul 18 10:09:39 sidney systemd[10393]: Failed at step USER spawning /usr/libexec/colord-sane: No such process
Comment 1 Richard Hughes 2012-07-30 09:56:03 UTC 
I think you want to use: --with-daemon-user=colord rather than --with-daemon-user on it's own.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.