Depends on what you plan to use it for. I only have limited hours with devilspie (and that was an older version). In the time I used it, I couldn't get it to apply transparency levels to certain (GTK) windows I wanted in Scrotwm, and eventually gave up. Didn't really see the need for it on a tiler.

Of course, your reasons for wanting to use it might be different. I'm a bit skeptical since ScrotWM uses a certain algorithm (study the source, very lean) to control window resizing, which might cause problems with devilspie. I suspect you want to launch apps in certain specific workspaces?... or maybe set rules for certain app windows to open at a certain size? If that's the case, I think a better solution would be to upgrade ScrotWM to 0.9.34 (snapshot source or git). it's got autorun functions to have certain apps launch in certain workspaces on start, and also has the very powerful (if a bit confusing)  layout functions which you can use to preset layouts for each workspace (and I'm not talking about the simple horiz/vert/fullscreen layouts, but more cutomized types). See the layout section in the  man page:  https://opensource.conformal.com/cgi-bin/man-cgi?scrotwm

Not saying it's the answer you're looking for, but might be worth considering. I've seen some BSD people get some really sick workflow with a proper combination or autorun, layout and quirk functionality.

Apologies for not having enough experience with devilspie, though. Its a decent app for sure, but I just don't have much experience with it.

Can be one of many reasons, really. Some people say this is KMS related, others have stated it's some other kernel parameter or ehci,, some have even suggested it's a bug in the way shutdown interfaces with some networking related apps (nm, for example). I can't say for sure unless you give a lot of details like lshw output, various logs, battery type (if notebook), kernel version, types of modules loaded...etc.

For now, try "shutdown -now -hP" to do a full shutdown. If that doesn't work, try "poweroff -fihp" or "halt -fihp" (as superuser/root).

Cheerz

Ahh, I typoed one of em. Added an extra dash

Should be "shutdown now -hP"

@farkinid
Yours is technically the safer route, since you're telling init to wait 10 sec before sending a kill signal, giving time for some processes to disable themselves. But truthfully, once you're logged out of X and don't have something like GDM or KDM running in the background, you shouldn't need to. For @scorps, I just added a P to specify powerdown, since -h alone sometimes causes system to halt without actually powering down on some computers.