I've been a tester of Devuan since the first beta release, and while most issues I've encountered have been resolved, there always remains work to be done. Allow me to shed some light on and draw attention towards ACPI event handling.

First, let me preface this with stating the obvious. My download of Devuan matched both the signature and the checksum provided. I installed using a flash drive with default install options.
I wrote the ISO file to my flash drive using:

dd if=ISOIMAGE of=DeviceName

.

My hardware is as follows:

System:
           Kernel: 3.16.0-4-amd64 x86_64 (64 bit) 
           Desktop: N/A Distro: Devuan GNU/Linux 1 

Machine:
           System: Dell product: Latitude D630
           Mobo: Dell model: 0KU184 Bios: Dell v: A15 date: 11/24/2008

CPU:
           Dual core Intel Core2 Duo T9300 (-MCP-) cache: 6144 KB 
           Clock Speeds: 1: 800 MHz 2: 1600 MHz

Graphics:  
           Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary)
           Display Server: X.Org 1.16.4 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1440x900@59.90hz
           GLX Renderer: Mesa DRI Intel 965GM GLX Version: 2.1 Mesa 10.3.2

Audio:
           Card Intel 82801H (ICH8 Family) HD Audio Controller 
           driver: snd_hda_intel 
           Sound: Advanced Linux Sound Architecture v: k3.16.0-4-amd64

Network:
           Card-1: Intel Ultimate N WiFi Link 5300 driver: iwlwifi
           IF: wlan0 state: up mac: ##:##:##:##:##:##
           Card-2: Broadcom NetXtreme BCM5755M Gigabit Ethernet PCI Express
           driver: tg3
           IF: eth0 state: down mac: ##:##:##:##:##:##

Everything went without a hitch during installation. Once I booted into my new Devuan Jessie install, I proceeded to configure the panel.

• The Xfce Power Manager Plugin for the Panel does not display the battery icon properly and is frozen, displaying a static image of a power plug (the one usually only displayed when charging).

• ALSA or the Audio Mixer plugin will function with the Mute Button on my Laptop; however, only the Master channel works as expected while the Speaker channel will only mute but never unmutes. I must meticulously open ALSA Mixer and manually unmute the Speaker channel in order to restore audio functionality to my Laptop.

• Now, for the pinnacle of dysfunction, my Laptop Lid Debacle. I attempted configuring Xfce Power Manager, as I have done hundreds/thousands of times before, to Suspend my Laptop when the Lid is closed (irrespective of charging status). Closing the lid had no effect other than to turn my screen off. Opening my laptop turned the screen on. The problem isn't that the Lid Button ACPI event wasn't registering but, rather, that the event wasn't triggering suspend as it was configured in Xfce Power Manager.

~$ acpi_listen
button/lid LID close
button/lid LID open

The aforementioned code snippet proves that my Laptop Lid is capable of registering to my system, so I delved deeper and found some ACPI events from various contributors on obscure support forums which could function in /etc/acpi/events/ for the purpose I intend (and perhaps others as well). I followed all recommended permissions attributes on all of these files foremost.

This was saved as lm_lid in /etc/acpi/events/

event=button/lid.*
action=/etc/acpi/lid.sh

This shell script was the counterpart to lm_lid and was saved as lid.sh in /etc/acpi/

#!/bin/sh

grep -q closed /proc/acpi/button/lid/*/state
if [ $? = 0 ]
then
    /etc/acpi/Laptop/lidman-trigger;
else
    /etc/acpi/Laptop/lidman-trigger;
fi

I saved the following in /etc/sudoers.d/Lidpermit using visudo -f

InsertUsernameHere ALL=(ALL:ALL) NOPASSWD:/etc/acpi/Laptop/export_x_info

This was saved as export_x_info in /etc/acpi/Laptop/ and added to Xfce Session and Startup.

# Export the dbus session address on startup so it can be used by any other environment
sleep 5
env | grep DBUS_SESSION_BUS_ADDRESS >> /home/clokedfigure/.Laptop/lidman
echo 'export DBUS_SESSION_BUS_ADDRESS' >> /home/clokedfigure/.Laptop/lidman
# Export XAUTHORITY value on startup so it can be used by cron
env | grep XAUTHORITY >> /home/clokedfigure/.Laptop/lidman
echo 'export XAUTHORITY' >> /home/clokedfigure/.Laptop/lidman

lidman was saved in /home/InsertUsernameHere/.Laptop/ & since it is generated by export_x_info, I suspect therein lies the dilemma. The DBUS_SESSION_BUS_ADDRESS is most notably missing, yet when I manually enter the command as root, the expected DBUS_SESSION_BUS_ADDRESS makes an appearance in Lidman.

  
export DBUS_SESSION_BUS_ADDRESS
XAUTHORITY=/home/clokedfigure/.Xauthority
export XAUTHORITY

And finally the insignificant lidman-trigger saved in /home/InsertUsernameHere/.Laptop/

source /home/clokedfigure/.Laptop/lidman

If anyone can inform me of the best approach to resolving this sooner, I'd very much appreciate your efforts. I've shown most of what I could glean from a day's worth of research, trial, and error; please throw some compassion my way. Thank you!