Comment 17 for bug 1600622

I have noticed that
a) systemctl suspend
does actually suspend, but it takes about 30 seconds.
I'm on 18.04.1 with kernel 4.18.0-13-generic from the proposed PPA
This is quite surprising, but good news. I don't know why this is working
now. It works with either Chromium or Chrome open, with hangouts running.
Because gnome uses systemctl suspend, this means that manual suspend from
gnome shell is also working.
I just suspended right now with a hangouts conversation in progress and a
Zoom meeting started, and it succeeded.

Maybe the more recent kernel fixes it?

b)
pkexec systemctl -i suspend
(run with root privileges)

always works, but this is less suprising, since -i means ignore inhibitors.

On Thu, 13 Dec 2018 at 12:16, ethanbrown <email address hidden> wrote:

> I agree with W-barath-hotmail that this is a serious problem that needs
> to be addressed. I believe on some occasions suspend fails even after
> I've killed Chrome.
>
> Please increase the Importance ranking of this bug.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1600622
>
> Title:
> Screen doesn't lock or go to sleep when certain Chrome tabs are open
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions
>

--
Tim Richardson