acpid exiting on system startup; possible dbus involvement

Natanji · 2011-11-21 09:24:34

On startup of my system, acpid shuts down almost immediately when dbus gets started. I have to manually start acpid at a later point, then it stays running. I also have the problem of acpid sometimes shutting down randomly during operation.

This is what happens on startup (taken from /var/log/everything.log):

Nov 21 08:09:48 localhost acpid: starting up with netlink and the input layer
Nov 21 08:09:48 localhost acpid: 4 rules loaded
Nov 21 08:09:48 localhost acpid: waiting for events: event logging is off
(...)
Nov 21 08:10:05 localhost acpid: client connected from 1781[0:0]
Nov 21 08:10:05 localhost acpid: 1 client rule loaded
Nov 21 08:10:08 localhost dbus[1155]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Nov 21 08:10:08 localhost dbus[1155]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Nov 21 08:10:08 localhost polkitd[1853]: started daemon version 0.102 using authority implementation `local' version `0.102'
Nov 21 08:10:08 localhost dbus[1155]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Nov 21 08:10:08 localhost dbus[1155]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Nov 21 08:10:08 localhost acpid: exiting

This is my DAEMONS array from rc.conf:

DAEMONS=(hwclock syslog-ng dnsmasq net-auto-wireless netfs crond acpid @dbus @alsa @sshd @cupsd @privoxy @laptop-mode @wireless-regdom)

Can anyone point me into a direction of finding out why acpid exits? Is this dbus fucking with my system because of doing its own stuff or something like that?

Last edited by Natanji (2011-11-21 09:25:12)

Natanji · 2011-11-24 21:38:53

Ping.

HeSaid · 2011-11-25 19:39:19

Place dbus after syslog-ng in your daemons array. It should be started earler than you have it.
--
Neal

Natanji · 2011-12-02 11:19:25

In my understanding, dbus requires acpid to be running already to work properly. The other modules shouldn't really make a difference either; or is there a reason to start dbus and acpid before crond, dnsmasq, etc.? Please explain why it "should" be started earlier.

Shark · 2011-12-02 13:29:16

acpid module should be in front of dbus.

EDIT: sorry, i see you already have it in front of dbus. Maybe you should not background dbus daemon.

Last edited by Shark (2011-12-02 13:34:23)

Arch Linux

#1 2011-11-21 09:24:34

acpid exiting on system startup; possible dbus involvement

#2 2011-11-24 21:38:53

Re: acpid exiting on system startup; possible dbus involvement

#3 2011-11-25 19:39:19

Re: acpid exiting on system startup; possible dbus involvement

#4 2011-12-02 11:19:25

Re: acpid exiting on system startup; possible dbus involvement

#5 2011-12-02 13:29:16

Re: acpid exiting on system startup; possible dbus involvement

Board footer