** Changed in: apt (Ubuntu)
Status: Invalid = Confirmed
** Changed in: update-manager (Ubuntu)
Status: Invalid = Confirmed
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of
This happens to me in karmic with ftp as well.
Whether it is ubuntu's fault or not, there needs to be a fix. Throwing
up your hands just makes it impossible for a lot of people to use
Ubuntu.
Apt-get on Ubuntu is too fragile right now, and breaks whenever anyone
sneezes in its general direction.
I'm getting this in karmic. Is this a bug or what the fuck.
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I am having the same problem, but using ftp without a proxy (we have
proxy authentication problems using http/apt here):
Reading package lists... Done
W: GPG error: ftp://au.archive.ubuntu.com jaunty-updates Release: The following
signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive
I got:
W: A error occurred during the signature verification. The repository is not
updated and the previous index files will be used.GPG error:
http://de.archive.ubuntu.com jaunty-proposed Release: The following signatures
were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing
Thanks to everyone for this thread, and especially to knokkels for the
keyring solution that has worked for me. I've just been able to update
my system for the first time in weeks.
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug
** Attachment added: apt-http.log
http://launchpadlibrarian.net/20874638/apt-http.log
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
As it's impossible for apt or update-manager to work around truly broken
proxies, I'm closing this bug.
** Changed in: update-manager (Ubuntu)
Status: New = Invalid
** Changed in: apt (Ubuntu)
Status: New = Invalid
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
Medibuntu has a HOWTO hosted on ubuntu's website.
https://help.ubuntu.com/community/Medibuntu
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Thanks for this knokkels,
sudo apt-get install medibuntu-keyring
sudo apt-get update
you rock! Another annoyance bites the dust.
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of Ubuntu
Bugs,
w00t :)
thanks you all .. Guess I am not that much of a n00b after all :)
*bows*
On Fri, Sep 5, 2008 at 10:17 PM, billythekid [EMAIL PROTECTED] wrote:
Thanks for this knokkels,
sudo apt-get install medibuntu-keyring
sudo apt-get update
you rock! Another annoyance bites the dust.
--
GPG
heh thx .. has been running smoothly eversince :)
Knokkels
On Tue, Sep 2, 2008 at 11:27 PM, Eiht [EMAIL PROTECTED] wrote:
Same as everyone above I was getting this error on Hardy. I added the
keyring like knokkels did and it went awayso far. Thanks for the
help everyone. It first was
Same as everyone above I was getting this error on Hardy. I added the
keyring like knokkels did and it went awayso far. Thanks for the
help everyone. It first was just annoying but then it started to show
an error on auto updates too. Thanks.
Eiht.
--
GPG error with apt-get (BADSIG
wget -q http://packages.medibuntu.org/medibuntu-key.gpg -O- | sudo apt-
key add -
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
This has been giving me problems for several weeks and I was beginning
to despair of gettign a solution (meaning I would have to give in to my
peers and install RHEL)
Using a Bluecoat proxy at work I tried the suggestions to run the following
commands with no success:-
sudo apt-get update -o
** Changed in: update-manager (Ubuntu)
Status: Incomplete = New
Target: ubuntu-6.06 = None
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
I was in the same boat as knokkels, but with a regular google search for
the 'medibuntu keyring' i found
sudo apt-get update sudo apt-get install medibuntu-keyring
I also changed mirrors, like Andrew suggested, and the sudo bash code
like Dirk exampled, and now it's smooth sailing.
--
GPG
Hi, I am also a newbie with the same problem, and as I was reading this thread
I decided to look up medibuntu in the repo's.. There is a package called
medibuntu keyring (search for medibuntu and you will find it). select and
install (apply) it and it won't give the error anymore.
What it does
Let's be clear: the problem is not with the medibuntu repositories, but
the symptoms might be more pronounced when using those repositories.
Here's another temporary work-around for the people who don't use the medibuntu
repositories:
Go to System - Administration - Software Sources
Select a
NuclearPeon's suggestion worked. I was playing with the medibuntu.list
today and thats where all the problems starting coming in. After logging
into root and deleting it, everything returned back to normal.
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
I think I may have found a fix. I would get this error and none of the
above solutions would work.
W: GPG error: http://packages.medibuntu.org gutsy Release: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 2EBC26B60C5A2783
W: You may want to run
Guys...I have a problem with my update manager. I'm a new ubuntu user.
Right now I'm having this error and I can't update my OS:
Fetched 422kB in 8s (50.6kB/s)
W: GPG error: http://archive.canonical.com hardy Release: The following
signatures
I think Andrew pegged the issue. I am experiencing the same problem
which started shortly after we added a Bluecoat web filtering / caching
device in to our network. I tried setting up an SSH connection to my
house and forwarding the traffic through my home connection (bypassing
our cache) and
Dirk's instructions worked for a couple of days, but the BADSIG error
showed up again this morning.
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
I believe that this error is caused by a caching proxy which returns
stale files, instead of actually retrieving the latest files from the
mirror and returning that. In my case, it is a transparent squid proxy.
I added
Acquire::http::No-Cache true;
Acquire::http::Max-Age 0;
to
I have no idea what Dirk's instructions did, but I no longer see the
error. I'll post back if it shows up again.
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
sudo bash
apt-get clean
cd /var/lib/apt
mv lists lists.old
mkdir -p lists/partial
apt-get clean
apt-get update
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Hi Dirk
Can you please explain what the above list of commands is trying to
achieve?
Thanks
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
I have this same problem with Hardy. But it goes away after 1/2 a day or
so.
My take on this is that apt is doing its job correctly, but the alert /
message that is being displayed to the user could be reviewed.
W: GPG error: http://archive.ubuntu.com hardy-updates Release: The
following
I am also still receiving this error after trying the fix by
DogFoodTaster.
W: GPG error: http://archive.ubuntu.com hardy-updates Release: The
following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu
Archive Automatic Signing Key [EMAIL PROTECTED]
I have been steadily receiving this
I get the same error message, but in my native spanish
W: Ha ocurrido un error durante la verificación de la firma. El
repositorio no se ha actualizado y se usarán los archivos de índice
anteriores. Error de GPG: http://ar.archive.ubuntu.com hardy-updates
Release Las siguientes firms fueron
DogFoodTaster:
I try with that solution, but doesnt work for me. I have the same error
message than before.
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
I followed the fix found in this thread (
http://ubuntuforums.org/showthread.php?t=179303 ). The person in the
thread, though, seemed to reexperience the problem after a short while,
but so far I have not.
The fix is just to back up sources.list, delete everything in it and run
apt-get update.
W: GPG error: http://archive.canonical.com hardy Release: The following
signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic
Signing Key [EMAIL PROTECTED]
W: GPG error: http://packages.medibuntu.org hardy Release: The following
signatures were invalid: BADSIG
apt-get update http debug logfile
** Attachment added: apt-get update http debug logfile
http://launchpadlibrarian.net/13548346/apt-http.log
--
GPG error with apt-get (BADSIG 40976EAF437D05B5)
https://bugs.launchpad.net/bugs/24061
You received this bug notification because you are a member
I was having this problem consistently today. After reading through the
above when I ran with apt-get update -o Acquire::http::No-Cache=True
everything worked fine. As another datapoint, I know that our company
recently installed a transparent http(s) proxy, so maybe there is
something to do with
36 matches
Mail list logo
