Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
New Bullseye Install VBox key not verified
- MikeLieberman
- Posts: 164
- Joined: 2013-01-29 17:26
- Location: General Santos City, Philippines
- Has thanked: 17 times
- Been thanked: 2 times
New Bullseye Install VBox key not verified
I have a clean / new Bullseye install (the upgrade from 10.10 failed in the final 'full' part) on my Dell laptop.
VitrualBox is working.
All is reinstalled and fine EXCEPT for the sources.list line for virtualbox.
Here's the line:
deb http://download.virtualbox.org/virtualbox/debian bullseye contrib
Here's what I get:
Err:2 http://download.virtualbox.org/virtualbox/debian bullseye InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A2F683C52980AECF/b]
I even tried this command to fix it:
sudo apt update 2>&1 1>/dev/null | sed -ne 's/.*NO_PUBKEY //p' | while read key; do if ! [[ ${keys[*]} =~ "$key" ]]; then sudo apt-key adv --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys "$key"; keys+=("$key"); fi; done
But the result was:
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.uiLPlMPfm2/gpg.1.sh --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys A2F683C52980AECF
gpg: keyserver receive failed: No name
So I read the man apt-key(8) but I'm sorry, I don't have a clue about how to use this deprecated command and the associated files.
VitrualBox is working.
All is reinstalled and fine EXCEPT for the sources.list line for virtualbox.
Here's the line:
deb http://download.virtualbox.org/virtualbox/debian bullseye contrib
Here's what I get:
Err:2 http://download.virtualbox.org/virtualbox/debian bullseye InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A2F683C52980AECF/b]
I even tried this command to fix it:
sudo apt update 2>&1 1>/dev/null | sed -ne 's/.*NO_PUBKEY //p' | while read key; do if ! [[ ${keys[*]} =~ "$key" ]]; then sudo apt-key adv --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys "$key"; keys+=("$key"); fi; done
But the result was:
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.uiLPlMPfm2/gpg.1.sh --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys A2F683C52980AECF
gpg: keyserver receive failed: No name
So I read the man apt-key(8) but I'm sorry, I don't have a clue about how to use this deprecated command and the associated files.
- MikeLieberman
- Posts: 164
- Joined: 2013-01-29 17:26
- Location: General Santos City, Philippines
- Has thanked: 17 times
- Been thanked: 2 times
Re: New Bullseye Install VBox key not verified
I have used that page and it does NOT address this problem. I did download the code from that site and installed via it. Like I said, the install works.
It mentions this for Debian 10 and older versions, NOTHING for bullseye:
Code: Select all
The Oracle public key for apt-secure can be downloaded
Debian-based Linux distributions
Add the following line to your /etc/apt/sources.list. According to your distribution, replace '<mydist>' with 'eoan', 'bionic', 'xenial', 'buster', 'stretch', or 'jessie' (older versions of VirtualBox supported different distributions):
deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian <mydist> contrib
here for Debian 8 ("Jessie") / Ubuntu 16.04 ("Xenial") and later
here for older distributions.
You can add these keys with
sudo apt-key add oracle_vbox_2016.asc
sudo apt-key add oracle_vbox.asc
or combine downloading and registering:
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
I am also not upgrading nor using RPM.
So exactly where on that page do you think I should be looking?
-
- Global Moderator
- Posts: 2960
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 73 times
- Been thanked: 405 times
Re: New Bullseye Install VBox key not verified
Hello,
In my Debian Bullseye, I've added for test purposes the following line to the repositories (as per instructions):
So, I've given the following commands (as per instructions) as root user:
As you can see, there's no error. :wink:
Therefore, I suppose you have typed something wrong or you have executed some command (for example, sudo) without the required privileges (note: I've left the sudo command as per instructions, but it can be removed if commands are executed as root user).
If you wish, you can send the logs of the given commands you gave: let me know.
In my Debian Bullseye, I've added for test purposes the following line to the repositories (as per instructions):
Code: Select all
deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian bullseye contrib
Code: Select all
# wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
# wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -
# LC_ALL=C apt update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 https://download.virtualbox.org/virtualbox/debian bullseye InRelease
Hit:3 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:4 https://deb.debian.org/debian bullseye-updates InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Therefore, I suppose you have typed something wrong or you have executed some command (for example, sudo) without the required privileges (note: I've left the sudo command as per instructions, but it can be removed if commands are executed as root user).
If you wish, you can send the logs of the given commands you gave: let me know.
- MikeLieberman
- Posts: 164
- Joined: 2013-01-29 17:26
- Location: General Santos City, Philippines
- Has thanked: 17 times
- Been thanked: 2 times
Re: New Bullseye Install VBox key not verified
Here's the source.list line:
Here's the result:
I ran grep on every log file in /var/log and find not a single hit on this, so where should I look?
All other lines in the sources.list load. I have my sources line for VBox exactly like yours and you can see what my result is. Someone had a similar problem while running secure boot and there was a fix for that but is does not apply to my install.
I am NOT saying it's not my fat fingers, but where do I look?
Code: Select all
deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian bullseye contrib
Code: Select all
mike@Traveler:~$ sudo apt-get update
Get:1 https://download.virtualbox.org/virtualbox/debian bullseye InRelease [7,735 B]
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Err:1 https://download.virtualbox.org/virtualbox/debian bullseye InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A2F683C52980AECF
Get:4 http://deb.debian.org/debian bullseye-updates InRelease [36.8 kB]
Reading package lists... Done
W: GPG error: https://download.virtualbox.org/virtualbox/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A2F683C52980AECF
E: The repository 'https://download.virtualbox.org/virtualbox/debian bullseye 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.
All other lines in the sources.list load. I have my sources line for VBox exactly like yours and you can see what my result is. Someone had a similar problem while running secure boot and there was a fix for that but is does not apply to my install.
I am NOT saying it's not my fat fingers, but where do I look?
- MikeLieberman
- Posts: 164
- Joined: 2013-01-29 17:26
- Location: General Santos City, Philippines
- Has thanked: 17 times
- Been thanked: 2 times
Re: New Bullseye Install VBox key not verified
UPDATE!!!
I had been running the command below as
sudo su -c 'wget -q -O- http://download.virtualbox.org/virtualb ... x_2016.asc | apt-key add -'
and was getting an error.
I used 'su -' became root and ran
su -c 'wget -q -O- http://download.virtualbox.org/virtualb ... x_2016.asc | apt-key add -'
THAT WORKS! The problem is gone!
I had been running the command below as
sudo su -c 'wget -q -O- http://download.virtualbox.org/virtualb ... x_2016.asc | apt-key add -'
and was getting an error.
I used 'su -' became root and ran
su -c 'wget -q -O- http://download.virtualbox.org/virtualb ... x_2016.asc | apt-key add -'
THAT WORKS! The problem is gone!
-
- Global Moderator
- Posts: 2960
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 73 times
- Been thanked: 405 times
Re: New Bullseye Install VBox key not verified
Hello,
The wget command was successfully executed when you acquired root privileges with the su (switch user) command.
Why did not log in as root user ?
I’m glad I helped you to sort it out.
Therefore there is something wrong with the sudo command: can you report the error with sudo ?MikeLieberman wrote: ↑2021-09-09 03:05 UPDATE!!!
I had been running the command below as
sudo su -c 'wget -q -O- http://download.virtualbox.org/virtualb ... x_2016.asc | apt-key add -'
and was getting an error.
I used 'su -' became root and ran
su -c 'wget -q -O- http://download.virtualbox.org/virtualb ... x_2016.asc | apt-key add -'
THAT WORKS! The problem is gone!
The wget command was successfully executed when you acquired root privileges with the su (switch user) command.
Why did not log in as root user ?
I’m glad I helped you to sort it out.
- MikeLieberman
- Posts: 164
- Joined: 2013-01-29 17:26
- Location: General Santos City, Philippines
- Has thanked: 17 times
- Been thanked: 2 times
Re: New Bullseye Install VBox key not verified
sudo is installed. I do most all I need to do with sudo.
As the issue is fixed, the sudo command gives me nothing now. I didn't use 'su' rather I used 'su-' to run the command when it worked. So I wasn't in 'switch user' I was in superuser, root.
In fact I am using sudo to get around a problem right now with synaptic. The package manager doesn't load from "Applications" but if I am in terminal emulation I can type "sudo synaptic" and the programs loads. (When selected from the "Applications" menu, I get a lot of disk churn but no window.) Yes, I checked for a broken install. The OS reports all is fine and up to date, and yet...
Bullseye is IMHO a little on the not ready for prime time end of the spectrum. In the past I had no problems going from Debian 8 to 9 and 9 to 10, but 11 blew me up. And now the issues with the public key for VB and with synaptic... well it really ought not to be this hard. Not after all these years.
As the issue is fixed, the sudo command gives me nothing now. I didn't use 'su' rather I used 'su-' to run the command when it worked. So I wasn't in 'switch user' I was in superuser, root.
In fact I am using sudo to get around a problem right now with synaptic. The package manager doesn't load from "Applications" but if I am in terminal emulation I can type "sudo synaptic" and the programs loads. (When selected from the "Applications" menu, I get a lot of disk churn but no window.) Yes, I checked for a broken install. The OS reports all is fine and up to date, and yet...
Bullseye is IMHO a little on the not ready for prime time end of the spectrum. In the past I had no problems going from Debian 8 to 9 and 9 to 10, but 11 blew me up. And now the issues with the public key for VB and with synaptic... well it really ought not to be this hard. Not after all these years.
-
- Global Moderator
- Posts: 2960
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 73 times
- Been thanked: 405 times
Re: New Bullseye Install VBox key not verified
Hello,
You can also check the system log about sudo errors and sudo commands: there should be plenty of it in the system logs with all the attepts you have done. Anyway, the "offending command" should be sudo and, therefore, you could easily replicate it.
The second part of previous command cannot work because of pipe redirection. But it's just a guess, the exact command with the exact error is required for an analysis, everything else is just speculation.
Not to bore you, but if you need so frequently to use the sudo command, you could consider to open a shell with root privileges (for example, with su command) for a sequence of commands instead of using sudo for every command.
I think it would be interesting to identify the cause of the error you reported. If you wish, you can easily remove the vbox installed keys as root user with the following command to replicate the error:
Code: Select all
# apt-key del "B9F8 D658 297A F3EF C18D 5CDF A2F6 83C5 2980 AECF"
# apt-key del "7B0F AB3A 13B9 0743 5925 D9C9 5442 2A4B 98AB 5139"
You used su -c (watch space between "u" and "-") to acquire root privileges: I mean that you used the command "su" to temporary "switch user" between your user and root user. Of course, this should be an unnecessary workaround, because there was something wrong in the command you gave using sudo without su.MikeLieberman wrote: ↑2021-09-09 05:38 I didn't use 'su' rather I used 'su-' to run the command when it worked. So I wasn't in 'switch user' I was in superuser, root.
I'm sorry, but I disagree with you: there's no evidence (e.g., from the logs you sent) that what you are experiencing for the specific topic is related to Debian by itself, at least by now. I wasn't able to replicate an error whatsoever. What I could suspect is that you typed a command like this:MikeLieberman wrote: ↑2021-09-09 05:38Bullseye is IMHO a little on the not ready for prime time end of the spectrum. In the past I had no problems going from Debian 8 to 9 and 9 to 10, but 11 blew me up. And now the issues with the public key for VB and with synaptic... well it really ought not to be this hard. Not after all these years.
Code: Select all
$ sudo wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | apt-key add -
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
E: This command can only be used by root.
- MikeLieberman
- Posts: 164
- Joined: 2013-01-29 17:26
- Location: General Santos City, Philippines
- Has thanked: 17 times
- Been thanked: 2 times
Re: New Bullseye Install VBox key not verified
With the potential that you are correct of the first. I note that there was no mention on the docs does that a sudo will be ineffective and it must be done as root.
Regarding the second matter, I see no reason why there should be a of pipe redirection causing synaptic to fail to load properly on a new clean install.
The 'observation of yours' of a pipe redirection simply points to a poor implementation. Are you making an excuse for a troubled rollout? The installation of Synoptic is part of the iso as it was made bootable on a USB stick. It installed without modification on the the laptop. As you are not responsible for the poor work, I think that you might consider that all is not well in Mudville.
Regarding the second matter, I see no reason why there should be a of pipe redirection causing synaptic to fail to load properly on a new clean install.
The 'observation of yours' of a pipe redirection simply points to a poor implementation. Are you making an excuse for a troubled rollout? The installation of Synoptic is part of the iso as it was made bootable on a USB stick. It installed without modification on the the laptop. As you are not responsible for the poor work, I think that you might consider that all is not well in Mudville.
-
- Global Moderator
- Posts: 2960
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 73 times
- Been thanked: 405 times
Re: New Bullseye Install VBox key not verified
Hello MikeLieberman,
I tried to give you some advice about your questions, the facts are clearly reported in the thread especially for other users with similar questions.
If you have questions about synaptic, you can open a specific thread, if you need: I have not specifically covered this topic in my answers because off-topic in this thread.
Blaming on the operating system or on the way shell commands are parsed for something that is not fully understood by you is not a positive way of thinking or of learning.
Therefore, I quit my participation to this thread.
Have a nice day.
I tried to give you some advice about your questions, the facts are clearly reported in the thread especially for other users with similar questions.
If you have questions about synaptic, you can open a specific thread, if you need: I have not specifically covered this topic in my answers because off-topic in this thread.
Blaming on the operating system or on the way shell commands are parsed for something that is not fully understood by you is not a positive way of thinking or of learning.
Therefore, I quit my participation to this thread.
Have a nice day.