Originally posted by 01xB100D
View Post
Now regarding your specific situation. The desktop environment (DE) -- KDE in our case -- has no control over the power management system until after the DM has completely loaded the DE. While the DM is running, only the DM can control the power system. KDM, being very old code, likely has no mechanism to handle a modern laptop's suspend state. I can't say for sure, as I haven't tested this particular scenario. You're most likely using LightDM; from your problem description, it would appear that LightDM also has no mechanism to handle suspend. To be honest, it's probably an edge case for a DM to implement that much functionality, as typically a DM executes for only a few seconds -- the goal is to get the DE loaded fast, not to give you a break that requires closing your lid.
I realize this isn't an excuse -- it's simply an explanation for the behavior you've observed. The great thing about open source is that you can (1) file bugs for the developers and (2) actually offer improvements yourself! In fact, a quick search of Google shows that there are already some reports of LightDM not properly handling suspend/resume; it seems there were some partial fixes after 14.04 was first released.
Leave a comment: