Bug 53639

Summary: Session dbus-daemon started with --address=systemd: couldn't start services on demand
Product: dbus Reporter: Oleksii Shevchuk <public.avatar>
Component: coreAssignee: Havoc Pennington <hp>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Oleksii Shevchuk 2012-08-17 10:29:26 UTC 
Aug 17 13:17:08 CLU dbus-daemon[6940]: (process:9665): GVFS-RemoteVolumeMonitorDaemon-WARNING **: Cannot connect to session bus: org.freedesktop.DBus.Error.BadAddress: '=' character not found or has no value following it
Aug 17 13:17:08 CLU dbus-daemon[6940]: Activated service 'org.gtk.Private.GPhoto2VolumeMonitor' failed: Process /usr/libexec/gvfs-gphoto2-volume-monitor exited with status 1

$ ps aux | grep dbus
102       1705  0.0  0.1   4140  2336 ?        Ss   09:46   0:10 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
avatar    6940  0.0  0.0   4032  1952 ?        Ss   11:59   0:01 /usr/bin/dbus-daemon --session --address=systemd: --nofork --systemd-activation

Manually started service runs ok:
 $ srv status dbus-org.gtk.Private.GPhoto2VolumeMonitor.service
gvfs-gphoto2-volume-monitor.service - Start GVFS daemon gphoto2 volume monitor
	  Loaded: loaded (/home/avatar/.config/systemd/user/gvfs-gphoto2-volume-monitor.service; enabled)
	  Active: active (running) since Fri, 17 Aug 2012 13:17:23 +0300; 15min ago
	Main PID: 9670 (gvfs-gphoto2-vo)
	  CGroup: name=systemd:/user/avatar/3/systemd-6916/gvfs-gphoto2-volume-monitor.service
		  └ 9670 /usr/libexec/gvfs-gphoto2-volume-monitor
Comment 1 Simon McVittie 2012-08-21 07:44:39 UTC 
(In reply to comment #0)
> Aug 17 13:17:08 CLU dbus-daemon[6940]: (process:9665):
> GVFS-RemoteVolumeMonitorDaemon-WARNING **: Cannot connect to session bus:
> org.freedesktop.DBus.Error.BadAddress: '=' character not found or has no value
> following it

I think this is Bug #50962.

As far as I'm concerned, systemd for non-system buses is not a supported configuration yet. If you want it to be, Bug #50962 is the place to start (hopefully I'll have some time to re-review soon), but regression tests with a mock systemd (for both system and session cases) would be even better.

*** This bug has been marked as a duplicate of bug 50962 ***

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.