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
Error message {RESOLVED}
Error message {RESOLVED}
"The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user 'root' executing apt-key". I upgraded to the 4.8.7-1 kernel, running sid, started after the update. i've looked around for a solution, but no luck so far. when I tried apt-key update it says it is depreciated. I can still update, although not in the normal way, install packages etc. If anyone could point me in the right direction it would be greatly appreciated.
Thanks
Thanks
Last edited by wmittz on 2016-12-16 12:46, edited 1 time in total.
Re: Error message
Most apps that warn about deprecated usage still perform the task. Does apt-key have any other info like a --vvv setting or something? Maybe the new keys aren't available yet? can you download them somewhere?when I tried apt-key update it says it is depreciated
debian-archive-keyring (for sid) would possibly be the package you need to update?
Funny trick.. well is the file there? who is it readable by if not root?/etc/apt/trusted.gpg are ignored as the file is not readable by user 'root' executing apt-key
resigned by AI ChatGPT
Re: Error message
W: http://http.us.debian.org/debian/dists/ ... /InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user 'root' executing apt-key.
W: http://www.deb-multimedia.org/dists/sid/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user 'root' executing apt-key.
Above is what I get from apt-get update. You may be right about new keys being available. I read somewhere that they increased security for the new kernel, but i have not been able find the article again. I fell back to an earlier kernel, same results, I've been looking for change logs but haven't seen mention of the changes.
The results for apt-key update,
Warning: 'apt-key update' is deprecated and should not be used anymore!
Note: In your distribution this command is a no-op and can therefore be removed safely.
It seems like there is a security/permission issue.
W: http://www.deb-multimedia.org/dists/sid/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user 'root' executing apt-key.
Above is what I get from apt-get update. You may be right about new keys being available. I read somewhere that they increased security for the new kernel, but i have not been able find the article again. I fell back to an earlier kernel, same results, I've been looking for change logs but haven't seen mention of the changes.
The results for apt-key update,
Warning: 'apt-key update' is deprecated and should not be used anymore!
Note: In your distribution this command is a no-op and can therefore be removed safely.
It seems like there is a security/permission issue.
Re: Error message
What happens when you use the previous kernel? You did save it, didn't you?wmittz wrote:"The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user 'root' executing apt-key". I upgraded to the 4.8.7-1 kernel, running sid, started after the update.
Sid (Unstable) is the bad boy of Debian. Breaks are expected. As a user of Sid you should find a fix and send a bug fix. Or you could wait a week or two for someone else to fix and report and the software to catch up. If you are in a hurry, install Jessie (Stable) which won't have this problem.i've looked around for a solution, but no luck so far. when I tried apt-key update it says it is depreciated. I can still update, although not in the normal way, install packages etc. If anyone could point me in the right direction it would be greatly appreciated.
Re: Error message
"What happens when you use the previous kernel? You did save it, didn't you?" I get the same error message. I went back and rebooted the 4.7 kernel, deleted the 4.8, still the same. As a side note I had the 4.8 headers running for a few days before the kernel update with no issues. So to me the issue is how the kernel is looking at different security permissions which have changed with the install of the 4.8 kernel.
"Sid (Unstable) is the bad boy of Debian. Breaks are expected." I've been running Sid for about 5 yrs, I find that if you are careful, lol, its not to bad, although I've made my share of mistakes. Sid is a hobby type of thing, stable is great, but a little boring. I'll continue to look for a solution, when I installed the 4.8 kernel there were no bug reports at that time. Thanks
"Sid (Unstable) is the bad boy of Debian. Breaks are expected." I've been running Sid for about 5 yrs, I find that if you are careful, lol, its not to bad, although I've made my share of mistakes. Sid is a hobby type of thing, stable is great, but a little boring. I'll continue to look for a solution, when I installed the 4.8 kernel there were no bug reports at that time. Thanks
Re: Error message
Sorry about that. As you know we get newbies here who jump in head first.wmittz wrote:"What happens when you use the previous kernel? You did save it, didn't you?" I get the same error message. I went back and rebooted the 4.7 kernel, deleted the 4.8, still the same. As a side note I had the 4.8 headers running for a few days before the kernel update with no issues. So to me the issue is how the kernel is looking at different security permissions which have changed with the install of the 4.8 kernel.
"Sid (Unstable) is the bad boy of Debian. Breaks are expected." I've been running Sid for about 5 yrs, I find that if you are careful, lol, its not to bad, although I've made my share of mistakes. Sid is a hobby type of thing, stable is great, but a little boring. I'll continue to look for a solution, when I installed the 4.8 kernel there were no bug reports at that time. Thanks
Now that we have my lecture out of the way here's an experiment you can try. No guarantees.
Copy and save /etc/apt/trusted.gpg under another name, maybe /etc/apt/trusted.gpg.wmittz. Then do
Code: Select all
rm /etc/apt/trusted.gpg
apt-key update
Re: Error message
I still consider myself a newbie, lol. My skill level isn't that great.
I'll try some experiments.
Thanks
I'll try some experiments.
Thanks
Re: Error message
I know the feeling. Generally I find that it isn't Debian or Linux that caused a problem but it was me doing something inadvertently. Sometimes the best troubleshooting tool is a mug of coffee a pencil and a notepad or whatever it takes to get comfortable and think about what I might have done.wmittz wrote:I still consider myself a newbie, lol. My skill level isn't that great.
Re: Error message
Well after trying a lot of things to resolve this problem, I gave up trying to repair it. I re-installed stable, then proceeded to upgrade to sid. I was able to replicate the same error message 3 different times at different times during the each upgrade (3). The first two attempts I ran into issues with docutils and the 4.8.0-1 kernel. The third attempt I held back upgrading the kernel to mid upgrade, ran the 4.7 bpo kernel, upgraded and continued on with no issues. Somewhere during during the last hundred or so upgrades the dreaded message reappeared. Last Sunday I started fresh again, this time they had upgraded the kernel to 4.8.11 which I used and it went well. Went directly from stable to sid on this upgrade, after the basic system packages, I bounced around upgrading the packages. I have had no issues since then and the system seems quite stable. Its not the typical "fix" but it worked for me.
- Onsemeliot
- Posts: 333
- Joined: 2010-12-15 14:43
- Has thanked: 20 times
- Been thanked: 5 times
not readable by user ‘_apt’ executing apt-key
The problem of an unreadable "/etc/apt/trusted.gpg" seems to have surfaced again in Stretch. I expect many others might encounter this issue by getting the following error message when updating the software sources: "The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key."
After reading the whole long thread on the Debian user mailing list at least I could resolve the issue on a fresh install of Stretch by just deleting the file causing the problem: sudo rm -f /etc/apt/trusted.gpg.
After reading the whole long thread on the Debian user mailing list at least I could resolve the issue on a fresh install of Stretch by just deleting the file causing the problem: sudo rm -f /etc/apt/trusted.gpg.
- eor2004
- Posts: 251
- Joined: 2013-10-01 22:49
- Location: Puerto Rico
- Has thanked: 4 times
- Been thanked: 5 times
Re: Error message
Thank you Bulkley for this command, worked like a charm for me, I did encountered this same issue with a new Debian stretch installation, I was pulling my hair off because I didn't find a clear answer for this on the interweb, only here in this forum, thank you again!Bulkley wrote:
Copy and save /etc/apt/trusted.gpg under another name, maybe /etc/apt/trusted.gpg.wmittz. Then doIf that doesn't work, there is How to fix missing gpg key even though it should have been imported which has more detailed instructions.Code: Select all
rm /etc/apt/trusted.gpg apt-key update
Debian 12 Gnome on a MSI H61M-P25 (B3) PC & on a Dell Latitude E6410 & HP EliteBook 8540p Laptops.
LMDE 6 on a Panasonic ToughBook CF-C1 Laptop.
Bodhi Linux 7 on a HP Compaq DC5750 Small Form Factor PC.
Windows 11 on a Intel DH55TC PC.
LMDE 6 on a Panasonic ToughBook CF-C1 Laptop.
Bodhi Linux 7 on a HP Compaq DC5750 Small Form Factor PC.
Windows 11 on a Intel DH55TC PC.
-
- Posts: 5
- Joined: 2017-01-11 00:45
Re: Error message {RESOLVED}
I have the same error message when i use "sudo apt update" or "sudo apt-get update"
- GrantWilson
- Posts: 6
- Joined: 2019-10-02 06:16
Re: Error message {RESOLVED}
Hi,Bulkley wrote:
Now that we have my lecture out of the way here's an experiment you can try. No guarantees.
Copy and save /etc/apt/trusted.gpg under another name, maybe /etc/apt/trusted.gpg.wmittz. Then doIf that doesn't work, there is How to fix missing gpg key even though it should have been an imported_tool which has more detailed instructions.Code: Select all
rm /etc/apt/trusted.gpg apt-key update
Thanks for the code. It worked for me. I also tried to add debian multimedia, however, the following error occurred:
"The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key"
I tried to extract the key deb-multimedia-keyring_2016.8.1_all.deb and then I placed it in the trusted.gpg.d folder.
- sdibaja
- Posts: 96
- Joined: 2005-10-22 21:14
- Location: Baja California, Mexico
- Has thanked: 31 times
- Been thanked: 11 times
Re: Error message
thanks Bulkley, it worked for me too.Bulkley wrote:
As you know we get newbies here who jump in head first.
Now that we have my lecture out of the way here's an experiment you can try. No guarantees.
Copy and save /etc/apt/trusted.gpg under another name, maybe /etc/apt/trusted.gpg.wmittz. Then doIf that doesn't work, there is How to fix missing gpg key even though it should have been imported which has more detailed instructions.Code: Select all
rm /etc/apt/trusted.gpg apt-key update
I don't consider myself a real newbie, but this is a rare one for me... very logical, rm the key then update
getting old is not for pussies, every day I need to relearn something