System Update 'Authentication Required' prompt popping up on Lock Screen

Hi all,

This is a minor issue but has been fairly annoying. For the past six months or so, every time I sit down to my computer for the first time that day, I have an ‘Authentication Required’ pop up sitting on my lock screen, preventing me from unlocking my computer until I press cancel (with my mouse - no ‘Escape’ key!):

https://i.imgur.com/vXdCjN6.jpg

I have no clue how to disable this and DuckDuckGo/Google gives me no clues. I’m fairly good about keeping my system up to date so I thought I would just disable all checks for system updates, but it doesn’t seem to prevent this from popping up (and to be honest I’m not sure I even did this correctly…)

Is this a bug? Should this prompt really be coming up on the lock screen, preventing me from unlocking my computer until I click cancel? Or is this something I did wrong?

Any suggestions would be very much appreciated!

Cheers,

Dman

I am not sure where that is coming from.

Normally, software updating in openSUSE does not require a root password, though adding new software does require it.

What desktop environment are you using – Gnome/KDE/whatever?

Is it possible that this is coming from some software package that you have installed, and the software is wanting to update itself?

Thanks for your reply nrickert!

Oops, should’ve mentioned this. I am using GNOME 3.26.2.

Very possible I guess! Would flatpak / snap packages do this? If not any suggestions for how I might find out what package is causing this?

Thanks again!

That does seem possible.

I am not using any of those, so I don’t have first hand experience.

So this does indeed appear to be an issue with snap. Apparently you cannot disable snap from auto updating, but following the directions here: https://askubuntu.com/questions/930593/how-to-disable-autorefresh-in-snap I changed the time at which snap auto updates, and now the prompts are coming up in the evening instead of the morning.

Frustrating there’s no way to actually disable it, but at least I know the problem now! Thanks nrickert again for your help!

Thanks for that update.