If im not wrong, it uses systemd, which should simply work correctly (elive-pm also uses is as first option), but the E mode does some extra things, so I think this is a bug that should be reported to E, but, don't tell them about elive-pm works correctly (they dont have this tool) but instead tell them which other standard tools works correctly, also verify it with plain systemd, like: "systemctl suspend"
Which doesn't shows the suspend and other calls anymore... and there's also two same files (i think that it migrated to a new one so why to keep both?) - another thing to report
yesterday I played with E24 and it works very good but at the same time I see a good amount of things that needs to be polished / fixed, specially from the options which are confusing and some not working correctly
BTW I suggest you to add this line to your ~/.elxstrt file:
(and make sure that "elxstart" is added to your Startup Applications). It will show in a terminal all the messages that runs on your graphical system, like errors or messages by E, unfortunately there's a good amount of garbage too so maybe on E24 is hard to see. You can also edit the .xsession-errors file after suspension in order to search some information from E like it were a syslog file
Which works just fine when invoked.
Maybe it's the "screen blanking" that uses "dpms" that gets in the way.
Yes, I find E24 itself is quite stable and hardly ever crashes....it just requires some extra polish.
OTH I agree that a lot of settings are very unclear as to what they actually do and maybe confusing for noobs.
Where do the messages that permanently run on F12 come from ?
They're clearly more than "syslog" or "dmesg" sometimes including info I'd want to copy but evidently cannot, from there.
sounds like something like this, as said, E does some extra things when suspending (so, if you call suspend from a command, E dont knows about it, but if you do it from E, E does some things before to suspend) - in any case sounds like something to report to E, except for the fact that maybe has relation with your settings (E devs can point you that), by other side if there's a buggy / useless / crappy setting in E maybe is good to report it too
this is a delicated thing, the source code can be modified to improve them, like the wording of the options and also the options themselves (some has been deprecated / useless over the time, they neeeds some rewrite), but this can introduce new bugs too so its a delicated thing
I even wonder if the "advanced / basic" settings mode is a useful feature at all or should be removed (makes the overall configurations more confusing! but for the composite ones in fact is useful to have it much simpler like switching between hardware and software modes)
grep tty12 /etc/rsyslog.conf
yes you can you have mouse featured in console in elive lol (gpm), but you can only use it between consoles imho
Well actually it doesn't work 100%...nicely, it even suspends my console on F1 and F12 (as does "systemctl suspend").
It wakes up fine on lid open/close but not through touch, moving mouse or hitting keys or power button (albeit the button gives a short flash of the screen).
Invoking it gives me this:
do_connect: could not connect to socket
connect: No such file or directory
^/usr/bin/elive-pm: line 265: 25115 Quit sleep 3
Running "tail -f ~/.xsession-errors" does give a similar message when it works as system, suspend on E24:
BL: set [/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight] -> 994
BL: set [/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight] -> 998
BL: set [/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight] -> 999
BL: set [/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight] -> 1000
Alas setting the backlight either in the console or in a terminal (blindly in the dark session) doesn't bring up the screen it only affects the brightness overall.
I use: "echo 852 | sudo tee /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/intel_backlight/brightness"
where 852 is my max_brightness.
So clearly screen-blanking is not the culprit.
Doing the same on another machine (Lenovo Yoga with 3.8.12 and E24) suspends fine and (only) wakes up on lid close/open with these messages:
SSS: systemd said to prepare for sleep! bool=1 @220274.25602859
SSS: systemd said to prepare for sleep! bool=0 @220278.56221303
SSS: sys resume @ 220278.56318186
SSS: sys resume2 @ 220279.16368903
Something I rarely get to see on the Thinkpad.
So I think I'll wait a while and test some more before reporting this behaviour as a bug.