epoch icon indicating copy to clipboard operation
epoch copied to clipboard

Epoch and Lightdm: InitMemBus(): Failed to connect to memory bus.

Open darkshram opened this issue 8 years ago • 2 comments

I'm doing testing with epoch as an alternative init system for my Linux distro (ALDOS -> http://www.alcancelibre.org/staticpages/index.php/notas-lanzamiento-aldos-1-4 ). So far I have managed to setup epoch.conf for every thing needed for a Fedora-like (systemd-less) based OS. Basically replicating most of the rc.sysvinit contents (automatic and forced fsck check, quotacheck, LVM, MDADM, FCOE, etc). I still have to work on cryptsetup, but that will have to wait.

The only issue I have not been able to solve is LightDM. System boots perfectly, but once LightDM starts epoch stops to respond. I got 'InitMemBus(): Failed to connect to memory bus'. If I manually kill lightdm, epoch starts responding again.

Any clue what's happening with LightDM? Any help or suggestion would be appreciated. Should I try to switch to another display manager? epoch-conf.tar.gz

I'm attaching to this message a copy of the files I'm currently using.

darkshram avatar Nov 15 '17 12:11 darkshram

I figured out myself what was wrong. LightDM needs an & at the end of ObjectStartCommand. Now I have it working perfectly. You may close this issue.

ObjectID=lightdm
	ObjectDescription=LightDM Display Manager
	ObjectStartCommand=/usr/sbin/lightdm -c /etc/lightdm/lightdm-epoch.conf &
	ObjectStopCommand=PIDFILE /var/run/lightdm.pid
	ObjectStartPriority=20
	ObjectStopPriority=1
	ObjectEnabled=true
        ObjectOptions=SERVICE
	ObjectRunlevels=gui

darkshram avatar Nov 15 '17 14:11 darkshram

Actually it should theoretically work with the options FORK and no &.

Subsentient avatar Nov 16 '17 01:11 Subsentient