There are several issues:1. '/usr/local/etc/init.d/acpid start' does not work when called from bootlocal.sh. Instead, I get startup messages that 1 rule is loaded, and that event logging is off. Why I don't know. If I stop and start acpid manually aft...
I've tried the following to stop the daemon: Code:stop() { killall acpid 2>/dev/null}..which works with the bluetooth and cups daemons, but for some reason with acpid, it will stop the daemon, but restart will not work.I've searched vario...
I don't use any display manager and when login input line appears it is distorted by acpid message:acpid:1 rule loaded
acpid:waiting fore events: event logging is offHow can I disable that annoying message?
WoldemarShiPa
https://bbs.archlinux.org/profile.php?id=60817
2012-08-24T08:01:35Z
In the old days, I configured acpid to launch vlock-cmatrixreloaded when I press Fn + F2, now it no longer works since systemd handles TTYs, I just got a screen flash when I press those keys.
The only way to invoke it is launch it manually from a tty or xterm, anyway to fix that?
EDIT
Fn is a standard function key (like shift) on laptops, and acpi_listen prints:
button/screenlock SCRNLCK 00000
After the lastest big upgrade I'm having some issues in the load of udev, vhba and acpid. I don't know if it's related but the lastest package that I installed was acpid.
I'm trying to get some acpi stuff working, and I came to the following situation:
When running acpi in foreground like acpid -ddl everything works as expected, I can see all the events, all scripts are executed.
But when I just start the service using service acpid start my scripts don't get executed.
What am I missing? Does the service thing does anything in a different way?
I had this problem several months ago but it never got fixed. Basically, I set up acpid to handle closing and opening the lid according to the wiki, so when I close it, it should do pm-suspend, and when I open it, it should resume. When I close it, it works fine (I think. It turns off and gets quiet, anyway). But when I open it, it seems to resume everything except the screen.
When I use the terminal, lines generally start with:
user@ubuntu:~$
and you type in your commands etc. but sometimes this disappears and there's nothing at the start of each line (i.e. if you open the terminal and type in grep -l file).
The only way I know to get back to the 'normal' mode with user@ubuntu:~$ starting each line is to close the terminal and re-open it.
The power went out on my PC running CentOS 6.3 while I was logged in as a regular user. Since then, when I try to login from the GUI, my screen flashes to black then returns to the login screen, without any message (as if my user was rejected).