Have to click "Restart" and "Shutdown" button twice to make button work.

Bug #1683867 reported by Jesse
172
This bug affects 30 people
Affects Status Importance Assigned to Milestone
GNOME Shell
Fix Released
Medium
Ubuntu GNOME
Fix Released
Undecided
Unassigned
gnome-shell (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

After left-clicking the menu in the top-right, then clicking the "Shutdown" button, the dialog window appears with three options: Cancel, Restart and Shutdown.

In 16.10 you just have to single-click the buttons to shutdown or restart. In 17.04, the buttons don't respond to a single click -- you have to click them a second time for the click to register.

EXPECTED BEHAVIOR: as before, click either button once to shutdown or restart PC.

Bug discovered on:
Ubuntu GNOME 17.04 x64
GNOME shell 3.24.0
Linux kernel 4.10.0-19-generic

Nvidia GTX 980ti graphics
Nvidia 375.39 proprietary graphics driver.
Xorg 1.19.3

Jesse (jessedubord)
affects: ubuntu-gnome → gnome-shell (Ubuntu)
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Does this always happen?

Revision history for this message
Jesse (jessedubord) wrote :

I believe so. Just checked running one of my workstations. Clicking "Restart" the first time did nothing. The Restart button didn't even react like it being pressed. Second click behaved normally.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Jonatã Bolzan Loss (jbopen) wrote :

I can confirm that this is happening on Ubuntu GNOME 17.04.

Revision history for this message
Saurav Sengupta (sauravsengupta) wrote :

This is an upstream bug and a regression - it happens on Fedora too, and it doesn't happen on GNOME 3.22. It doesn't happen every time, but mostly does. It may be that the shutdown dialog does not get focus on being opened.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Thank you also for reporting this issue to GNOME.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Low
Changed in gnome-shell:
importance: Unknown → High
status: Unknown → Invalid
Jeremy Bícha (jbicha)
Changed in gnome-shell:
importance: High → Unknown
status: Invalid → Unknown
Changed in gnome-shell:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Justin (justinkterry) wrote :

It also effects the cancel button for me, not just the reboot button.

Revision history for this message
Justin (justinkterry) wrote :

It also causes a blue ring around the shut down button. I confirmed it on two different computers.

Revision history for this message
Justin (justinkterry) wrote :

I had to take a video of rebooting in Ubuntu Gnome 17.04 to report some other bugs, so here's a video of this phenomenon if it helps anyone.

https://www.youtube.com/watch?v=P1lOxS8zx1o

(Sorry that it's vertical, YouTube won't let me turn it without installing flash)

Please let me know if you have any questions or need me to test anything.

Revision history for this message
martincasc (martincasco) wrote :

This bug also affect me since beta version at least every time I want to reboot, shutdown or cancel. I'm using 17.04 from a fresh install.

Revision history for this message
sdnflsdnflsdg (sdnflsdnflsdg-deactivatedaccount) wrote :

Also affects me with up-to-date Arch and GNOME. It always occurs and is very annoying.

Revision history for this message
Wise Melon (wise-melon-deactivatedaccount) wrote :

Same issue on Arch and GNOME 3.24.2, for some reason the Cancel button has also started acting up today and needing the two clicks.

Changed in ubuntu-gnome:
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This appears to be fixed and working in Ubuntu 17.10. Please try it. If you experienced a problem with 17.04 but it's fixed in 17.10 then the primary status of this bug can become Fix Released.

Changed in gnome-shell (Ubuntu):
status: Triaged → Incomplete
Changed in ubuntu-gnome:
status: Confirmed → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

And then it happened on 17.10 :)

Changed in gnome-shell (Ubuntu):
status: Incomplete → Triaged
Changed in ubuntu-gnome:
status: Incomplete → Confirmed
tags: added: artful zesty
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Curious. I can't reproduce this problem with artful today. Everything works better and I can't see what if any relevant packages changed.

Revision history for this message
Léo (leeo97one) wrote :

I've the same problem on Arch Linux so I think this is not related to Ubuntu.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes the bug will be in all distros. See upstream: https://bugzilla.gnome.org/show_bug.cgi?id=781738

Revision history for this message
empirical epistemologist (ironclad-chomskyan) wrote :

I can confirm that this is present, and readily replicable, in Ubuntu 17.04 Gnome running on my Skylake Alienware 17 R3 with GTX 970M!

In addition, the 60 second counter that we see in the Shutdown and Log Out dialogue windows ("This computer will Shut Down/Log Out automatically in 60 seconds.") is now frozen, and does not actually count down from 60 seconds anymore.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

sayantan, the counter intentionally only updates in 10-second increments (from 60 to 50 to 40…) until the final 10 seconds because that level of detail is not needed there and it's just distracting to have the dialog change so often.

Revision history for this message
empirical epistemologist (ironclad-chomskyan) wrote :

@Jeremy Ooops! Thanks a lot for pointing that out! Yeah, it does seem to work like that. I guess I was recalling seeing the last 10 seconds at some point!

However, the two-clicks thing still seem to be an issue. Hopefully it gets patched soon!

Revision history for this message
Cubic PPA (cubic-wizard) wrote :

Semantics question: Should this bug be in Confirmed status, instead of Triaged?

(Is it Triaged because clicking twice is the workaround to achieve the desired result? I ask because having to click twice is actually the bug itself!).

Revision history for this message
Wise Melon (wise-melon-deactivatedaccount) wrote :

@cubic-wizard, I'm pretty sure that 'Triaged' indicates that a developer here was able to reproduce it and that it is more than just users having the issue. That's what I've always taken it to mean anyway.

Please correct me if I am wrong.

Revision history for this message
Wise Melon (wise-melon-deactivatedaccount) wrote :

Yes, that's what it says if you click on the 'Triaged' button at the top where you can change it, for it is says as a description "Verified by the bug supervisor.".

Changed in gnome-shell (Ubuntu):
status: Triaged → Confirmed
Revision history for this message
Jeremy Bícha (jbicha) wrote :

I use "Triaged" when the bug has been forwarded upstream and there is enough information for a developer to duplicate the bug.

Changed in gnome-shell:
status: Confirmed → Fix Released
tags: added: julyshakedown
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I believe this was fixed in gnome-shell 3.25.4, which artful now has.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Paul White (paulw2u) wrote :

Marking fixed to fully close.

Changed in ubuntu-gnome:
status: Confirmed → Fix Released
Revision history for this message
r.fabbeni@gmail.com (r-fabbeni) wrote :

ubuntu 21.04
after upgrading to ubuntu 21.04 this bug is back.
the bug is under gnome-shell and cinnamon, so i suppose it's a system bug.
with shutdown now command from terminal works ok but the problem is the buttons.
if you select a countdown will never shutdown
if you remove countdown will have to select an option twice before something happens.
gnome-shell 3.38.4

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug is closed so please open a new bug for 21.04.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.