Hi , How may I fix this issue

Ahmed.AL

New Member
Joined
Mar 12, 2022
Messages
6
Reaction score
0
Credits
56
W: http://deb.anydesk.com/dists/all/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: https://dl.google.com/linux/chrome/deb/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://download.opensuse.org/repositories/home:/strycore/Debian_11/./InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: https://linux.teamviewer.com/deb/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://http.kali.org/kali/dists/kali-rolling/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: Failed to fetch https://download.wavebox.app/stable/linux/deb/amd64/InRelease The HTTP server sent an invalid Content-Range header Bad header data [IP: 188.114.97.13 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.
 


see this announcement from the developer issued 5 days ago


are you new to Linux , if so you should not even be trying to install Kali..
 
see this announcement from the developer issued 5 days ago


are you new to Linux , if so you should not even be trying to install Kali..
knowledge of Linux OS yes I have and I try to solve it using different solution but not fix this issue
 
Unfortunately there doesn't seem to be a good fix that I can find
 
I have been playing with Ubuntu 22.04 Developmental and had same issue - I went into root and moved "Key is stored in legacy" from /etc/apt/trusted.gpg - to here - /etc/apt/trusted.gpg.d/ - folder rebooted and ran - sudo apt update - again and did not get the error
 
Last edited by a moderator:
Same as @Lord Boltar moved the key and all seems well now on 22.04 Daily build. Remember the 22.04 is not yet final and will have some hiccups.
 
22.04 still isn't even in beta stage - it's still alpha, I'm pretty sure. (I haven't seen the announcement saying otherwise.) Use it at your own peril, and do consider reporting any bugs you find along the way. Bug reporting can be a bit onerous, but once you've done it the first couple of times you start to see why it is the way it is.

 
I have been playing with Ubuntu 22.04 Developmental and had same issue - I went into root and moved "Key is stored in legacy" from /etc/apt/trusted.gpg - to here - /etc/apt/trusted.gpg.d/ - folder rebooted and ran - sudo apt update - again and did not get the error
Thanks
 

Members online


Top