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?
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?
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:
r
then Enteror
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 don't recommend the
killall -3 gnome-shell
approach because:I use the following alias 'gf' for "gnome fix":
For zsh and bash:
For fish:
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:
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.
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.
I solved same problem this way:
ps ax | grep /usr/bin/nautilus
kill 1234
One-line command is:
echo $( ps ax | grep /usr/bin/nautilus )