Hello all,

I am a new member around here and a recent Linux user - by all means a newbie, so forgive me if the following will seem like a silly issue to have.

Basically, for the last few days, I've received the following issue multiple times as a result of running apt-get update:

Reading package lists... Done
W: GPG error: http://download.opensuse.org/reposit...sser/Debian_10 InRelease: The following signatures were invalid: EXPKEYSIG 0FAD31CA8719FCE4 home:stevenpusser OBS Project <home:stevenpusser@build.opensuse.org>
E: The repository 'http://download.opensuse.org/repositories/home:/stevenpusser/Debian_10 InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

I have found a few posts which seem to get this issue resolved - but in most cases the OP's are running some version of Ubuntu rather than Debian stable (buster) as in my case.

I have tried the following (with various server addresses):

gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0FAD31CA8719FCE4
gpg --export --armor 0FAD31CA8719FCE4 | sudo apt-key add -

But then I run into a different problem, namely:
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

So then I run

ps aux | grep -i apt

and I try to do sudo kill on whatever process id I find, but that also does not work.
Right at this moment, when I do that I have the following output:

masacra+ 18587 0.0 0.8 467404 65148 ? SNl 21:16 0:00 /usr/bin/python /usr/bin/apt-notifier.py
root 24549 0.0 0.0 70424 892 pts/1 S+ 21:29 0:00 grep -i apt

So I run

sudo kill 18587

which works fine, and

sudo kill 24549

which gives me

kill: (24549): No such process

and then I'm back to trying to run ps aux | grep -i apt which gives me a different PID from root

I thought I could just remove the file home:stevenpusser.gpg from /etc/apt/trusted.gpg.d/
but alas the "delete" option is greyed out.

And so I'm stuck in this loop where the /var/lib/dpkg/lock error prevents me from running apt-get update or installing the firejail package which I wanted to download to learn a bit more about sandboxing and run Ungoogled Chromium on my system.

My Distro: MX-19.3_x64 patito feo February 15 2020 base: Debian GNU/Linux 10 (buster)

Could the problem be that I am on the InRelease version of MX ?
Any suggestions most welcome.

This looks for processes that contain apt in their name. There might be other processes that keep that lock, for example dpkg.
That process was the grep command. It doesn't run anymore.
Your system configures a regular check of which packages should be updated. This is probably what holds the lock. Wait a few minutes and try again.
I don't know where you see a delete option. Why don't you just use a command-line text editor like nano or vim?

The original problem is an unsigned repository. You can either remove it from your repo list, which you were not successful doing because some delete option was grey, or you can run the apt command without signature check (which increases your security risk).

You "should be able to" get things done allot faster by just compiling the source yourself rather than chasing down this "won't install" bug.

Which source needs to be compiled to prevent apt-get update from issuing an error?