Suspending on login screen removes "Shutdown" button from menu

[Wise Melon]

On the login screen (I am not talking about the locked screen) if you click the menu it looks like this:

    LoginScreenShutdownButtonAvailable.png

This is how it should look on the login screen. However if you then suspend before logging in (I just close the lid of my laptop), when you wake it back up again the menu treats it as though you are on the locked screen where there is no shutdown button rather than on the login screen where is one:

    LoginScreenShutdownButtonNotAvailable.png

And this is rather annoying because if you don't have the login password or decide you want to shutdown without first logging, you can't and may be forced to do a hard shutdown.

---

OS Information:

    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 15.10
    Release: 15.10
    Codename: wily
    Flavour: GNOME
    GNOME Version: 3.18

Package Information:

    gdm:
      Installed: 3.18.0-0ubuntu1~wily1
      Candidate: 3.18.0-0ubuntu1~wily1
      Version table:
     *** 3.18.0-0ubuntu1~wily1 0
            500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ wily/main amd64 Packages
            100 /var/lib/dpkg/status
         3.16.2-0ubuntu2 0
            500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
         3.16.1.1-0ubuntu1~vivid1 0
            500 http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ wily/main amd64 Packages

[Wise Melon (wise-melon-deactivatedaccount)]

I have now also filed a report on this issue upstream: https://bugzilla.gnome.org/show_bug.cgi?id=763148

[Tim Lunn (darkxst)]

I think the power button is displayed based on no users being logged in, but clearly you aren't logged in yet?

[Wise Melon (wise-melon-deactivatedaccount)]

No, I'm definitely not logged in when this happens...

[Tim Lunn (darkxst)]

ok, confirmed here on Xenial.

Nikita, on another note would you be interested in joining the UBuntu GNOME QA team, and perhaps even help out with bug triage as you get more experience? You have filed a lot of bugs, so you are already doing some good testing, but have you helped with ISO testing etc?

[Tim Lunn (darkxst)]

Nikita, perhaps you would also like to try fix this bug? its almost certainly a bug in the gnome-shell javascript..

[Wise Melon (wise-melon-deactivatedaccount)]

@Tim, I believe that I have actually already joined that team you mentioned, though I haven't got that much done in association with it but I think I'll have another look at the stuff available to test there!

Ok, well I've downloaded the source for gnome-shell and I'll have a look to see if I can find and fix anything!

[Tim Lunn (darkxst)]

ok, I hadn't noticed you active in the ISO testing rounds, but then I mostly lead dev team, and not so much involved in QA team. we do however
need more QA team members triaging/tracking bugs ;)

cool, ping me on IRC if you need any help with gnome-shell bug.

On 08/03/16 20:53, Nikita Yerenkov-Scott wrote:
> @Tim, I believe that I have actually already joined that team you
> mentioned, though I haven't got that much done in association with it
> but I think I'll have another look at the stuff available to test there!
>
> Ok, well I've downloaded the source for gnome-shell and I'll have a look
> to see if I can find and fix anything!
>

[Wise Melon (wise-melon-deactivatedaccount)]

@Tim, Yeah, I have been making progress with the bug, but there are a few things I would like to ask you about it... I went to the GNOME IRC server but you didn't seem to be online... What time (or between what times) do you think I could catch you there?

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life on April, 2019

https://ubuntugnome.org/ubuntu-gnome-16-04-lts-is-here/
https://wiki.ubuntu.com/XenialXerus/ReleaseNotes/UbuntuGNOME

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.