I am using Ubuntu 20.04 and need help with this:


The Authentication Required window is stuck and I can't close it :(

Is there any easier ways to remove it than rebooting?

  • 1
    we are in 2020, linux completing so many years and we still face this annoying kind of "bugs" ... that time we consider just not using gnome anymore...
    – Digao
    Mar 26 at 11:48

5 Answers 5


I faced the same problem on Pop_!OS, no need to reboot actually;
The easier way is to just restart GNOME by one of two ways:

  • press Alt + F2, type r then Enter


  • in terminal, type killall -3 gnome-shell

This should just restart Gnome Shell. You will not lose your open windows, but you should be reminded to save all your work regularly!

Related bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874

  • I used the killall command and that worked.
    – tnk479
    Jan 2, 2021 at 22:34
  • 7
    Note that this will not kill your session nor any open programs. It is non-destructive. Jan 29, 2021 at 14:53
  • 1
    I was about to restart the whole computer and then I see this solution. Thank you so much. Feb 4, 2021 at 11:45
  • @AnanRaddad Hi, I used your method several times, but I changed gnome keyboard shortcut, and assigned Alt+F2 to something else. So I can't use Alt+F2. (a search tells me the default Alt+F2 was 'Run Console' but I can't find the menu in the keyboard shortcut edit window) Please help me.. what can I do in this case?
    – Chan Kim
    May 25, 2021 at 5:40
  • 1
    For me, this kills emacs windows on ubuntu 20.04.
    – Ryogi
    Oct 18, 2021 at 17:49

I don't recommend the killall -3 gnome-shell approach because:

  • It causes Steam and any running games within to exit.
  • It has a weird side effect of bringing up new instances of GUI apps like 1Password rather than bringing up the existing minimized process.

I use the following alias 'gf' for "gnome fix":

For zsh and bash:

alias gf='dbus-send --type=method_call --dest=org.gnome.Shell /org/gnome/Shell org.gnome.Shell.Eval string:"global.reexec_self()"'

For fish:

alias gf 'dbus-send --type=method_call --dest=org.gnome.Shell /org/gnome/Shell org.gnome.Shell.Eval string:"global.reexec_self()"'
  • Now when I see that your solution also works, I am not gonna change the accept mark since I already placed it for a year ago but you got my upvote :)
    – yang mandi
    Feb 27 at 16:26
  • Both solutions work! I'm just noticing weird artifacts with one versus the other. Thank you. :)
    – Michael
    Feb 28 at 17:09

Thank you for the nice tip!

For me it started happening seemingly all of a sudden. I am on a fresh Linux installation. Other than playing around with power management (suspend and hibernate) to make them work better, I did not fiddle around with anything else. It is happening after I login from suspension/reboot.

After a couple of days of trying to understand what might be wrong, I noticed a couple of things:

  • When trying to restart the window did not only display the 3 buttons Cancel, Restart, Power off BUT it stated that there is another user logged in (with the same name as me). I checked how many users were logged in but there was only one (me)
  • The authenticate window popup was popping up when I was trying to reboot (with the message ~= "authentication is needed for reboot")
  • All of a sudden the brightness control stopped working and my screen brightness was not changing when I was updating the slider (I know weird...but again I had done nothing to fiddle around with it)

Those clues led me to think that the latest package I had installed might be the culprit. It was the "chrome remote desktop" package which is related to logging the user to the current active window session and touching on display properties..

And after uninstalling the package everything worked as before! No stuck authentication popups, no duplicate ghost users and I can control my display's brightness.

I hope those observations and my experience is useful to someone out there.

  • Very interesting. However, I'm using RDP to connect into multipass! hahaha. Still upvoting.
    – jhchnc
    Jul 1 at 23:25

The most upvoted answer is emphatically not helpful. It may have 127 upvotes, but 'killall -3 gnome-shell' blacked out my screen; and after a few presses of the 'power' button to get my MBP back to life, I was left with HDD corruption & inconsistencies requiring manual fsck.

luckily nothing in 'lost+found', but an orderly 'shutdown', working around the stuck window much more preferable than disk inconsistencies.

PS BTW I've been doing 'fscks' since Bell UNIX V32, but don't have the online presence nor reputation to refute the /most preferred/ answer.

one fatal error IMHO, offsets all the other votes.

  • Do you use ubuntu 22.04 with Wayland?
    – yang mandi
    May 5 at 16:57
  • This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. To get notified when this question gets new answers, you can follow this question. Once you have enough reputation, you can also add a bounty to draw more attention to this question. - From Review
    – Pilot6
    May 10 at 9:41
  • 1
    can you provide your environment info? May 17 at 6:31
  • No, this does not answer the question. Much as a judge will hew to outdated premises for engagement, let's not lose the value of Stack, which is to provide value to developers
    – jhchnc
    Jul 1 at 23:24

I solved same problem this way:

  1. I opened terminal: Ctrl + Alt + T,
  2. I found nautilus PID: ps ax | grep /usr/bin/nautilus
  3. I killed process by kill command: kill 1234

One-line command is: echo $( ps ax | grep /usr/bin/nautilus )

  • I don't think your echo command will kill nautilus. Also, there's pgrep nautilus and even killall nautilus etc for lazy typists like me...
    – Zanna
    Oct 27, 2021 at 15:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.