Bug#901147: marked as done (gnome: system suspended-to-ram does not resume work)
Your message dated Thu, 12 Jul 2018 10:03:52 +0200
with message-id <[hidden email]>
and subject line Re: Bug#901147: Info received (gnome: system suspended-to-ram does not resume work)
has caused the Debian Bug report #901147,
regarding gnome: system suspended-to-ram does not resume work
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [hidden email] immediately.)
I sinsirely apoligise if I'm reporting the wrong module, but although the
problem seem related to the kernel, I've chacked some older kernel wich worked
corectly before, those were not modified by recent upgrades and still do not
restore system after suspend-ro-ram is executted.
* What led up to the situation?
system update, which I've done on May 28th. Previous update I've done on May
8th didn't have this unfortunate outcome.
* What exactly did you do (or not do) that was effective (or ineffective)?
I've tried to use kerenl vmlinuz-4.9.0-5-amd64, which on my system dates back
to January 4th, and its initrd to January 15th. This does not help. My system
after May 28th does not resume from suspend to RAM.
* What was the outcome of this action?
* What outcome did you expect instead?
should the problem related to kernel, an old kernel should correctly suspend-
restore the system (as it did so at the time it was current).