On 02/05/2017 11:56 PM, Carsten Haitzler (The Rasterman) wrote: [...] > i have no idea why. i don't think it's that though... something gets stuck. > something stops future system actions. what requires throwing printfs in > e_sys.c and printing out the logic flow and finding what piece of logic is > failing.
That could probably be narrowed down, in that when I was running e17 under Ubuntu 14.04 (I think) it worked perfectly. How much of e_sys.c has changed? > well a bit of basic C and printfs and then reading your logs would do it. I can do that; the hard bit is working out what module to look at, and knowing how to find out what bit gets triggered when an events occurs, like a hardware event (closing the lid) or a menu gets clicked. >> All fixed, however, by installing uswsusp which provides commands s2ram >> and s2disk which work just fine. > > there you go then. :) Yep, happy bunny :-) P ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
