Announcement

**dibl** · May 15, 2009, 07:19 AM

Re: Upgrade from Kubuntu9.04 KDE 4.2.1 to KDE4.2.3 - Public key will not install

I think you have two problems there.

GPG Key problem (which will NOT prevent downloading the package!):

http://kubuntuforums.net/forums/inde...1085#msg181085

The other (real) problem appears to be a networking or internet service issue. You are not connecting to the repository.

What do you see if you open the Konsole and enter

Code:

ifconfig

?

**rusty** · May 15, 2009, 07:42 AM

Re: Upgrade from Kubuntu9.04 KDE 4.2.1 to KDE4.2.3 - Public key will not install

ifconfig
eth0 Link encap:Ethernet HWaddr 00:0a:e4:d4:fd:9a
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20a:e4ff:fed4:fd9a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21764 errors:0 dropped:0 overruns:0 frame:0
TX packets:18362 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:16900797 (16.9 MB) TX bytes:2433852 (2.4 MB)
Interrupt:20 Base address:0x3000

eth1 Link encap:Ethernet HWaddr 00:12:f0:a8:4b:d6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:20 Base address:0x4000 Memory:b0106000-b0106fff

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:154 errors:0 dropped:0 overruns:0 frame:0
TX packets:154 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10372 (10.3 KB) TX bytes:10372 (10.3 KB)

dont know what it means though

I looked at the reference you mentioned - in my case I get an ERROR and synaptic does not want to go on
Rusty

**dibl** · May 15, 2009, 08:07 AM

Re: Upgrade from Kubuntu9.04 KDE 4.2.1 to KDE4.2.3 - Public key will not install

OK, your network setup appears to be working. Verify that you have functioning internet access by issuing

Code:

ping [url]www.google.com[/url]

and observe that it is receiving replies from the site. Use Ctrl-C to end the pinging.

Next, can you use kate to open /etc/apt/sources.list and post it here for review?

**rusty** · May 15, 2009, 08:11 AM

Re: Upgrade from Kubuntu9.04 KDE 4.2.1 to KDE4.2.3 - Public key will not install

I will, but my battery is going flat - will respond later Rusty

**GreyGeek** · May 15, 2009, 03:49 PM

Re: Upgrade from Kubuntu9.04 KDE 4.2.1 to KDE4.2.3 - Public key will not install

He should add:

deb http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu jaunty main

to his /etc/apt/sources.list file, then do
sudo apt-get update
sudo apt-get dist-upgrade

My KDE 4.2.3 installation is running fantastically. (which is probably why I don't have many of those problems that guy created a large web page about.)

**rusty** · May 16, 2009, 02:43 AM

Re: Upgrade from Kubuntu9.04 KDE 4.2.1 to KDE4.2.3 - Public key will not install

Dibl, thanks again for your kind assistance - such is the reason I am still using Kubuntu and have not gone back to other software or even back to MS.
this is the result of the ping - what can you interprete from it? >
(sorry if I make spelling mistakes along the way, but English is not my mother lamguage)

ping www.google.com
PING www.l.google.com (72.14.205.104) 56(84) bytes of data.
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=2 ttl=237 time=335 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=3 ttl=237 time=332 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=4 ttl=237 time=334 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=5 ttl=237 time=333 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=6 ttl=237 time=334 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=7 ttl=237 time=335 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=8 ttl=237 time=339 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=9 ttl=237 time=332 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=10 ttl=237 time=331 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=11 ttl=237 time=331 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=12 ttl=237 time=336 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=13 ttl=237 time=337 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=14 ttl=237 time=336 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=15 ttl=237 time=334 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=16 ttl=237 time=337 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=17 ttl=237 time=332 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=18 ttl=237 time=333 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=19 ttl=237 time=335 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=20 ttl=237 time=334 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=21 ttl=237 time=331 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=22 ttl=237 time=340 ms
64 bytes from qb-in-f104.google.com (72.14.205.104): icmp_seq=23 ttl=237 time=338 ms
^C

--- www.l.google.com ping statistics ---
23 packets transmitted, 22 received, 4% packet loss, time 22027ms
rtt min/avg/max/mdev = 331.064/334.972/340.053/2.527 ms

The ping worked - thanx for showing me how to do all this -

I had already added the item
< deb http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu jaunty main >
to the sources list some time before I started this forum request - that is what got me to the point where Symantec gave me an error regarding the publick key and would not upgrade.

I am now trying to go the route Greygeek suggested and for some reason or other it is working - probably as it should - without the guidance however I would not be able to have done it

Lets hope it completes fully and gets me out of this quagmire? in which I currently am.
for Greygeek, > I was happy with Kubuntu8.10 with KDE4.1 - however when I installed Kubuntu9.04, I had a number of issues which other guys also reported (random stalling, Kmail difficulties etc). That is why THIS GUY wanted to upgrade to KDE4.2.3 - be glad that your installation worked just out of the box - mine didn't, and I am not even a greygeek - I am just a PC user with no knowledge of programming - as I said in the very beginning - so if I made a large web page (as you mention), it is because I have no other venue to address my questions or ask elsewhere and I do not know how to address the issue of a public key or such errors.
I do not know why such things happen - hopefully KDE 4.3 will be better in this regard - so that I will be able to upgrade gui-wise with no problems.
Opening the Konsole and trying everything out as you said is OK -as long as there is very good instructions.

(The instructions which I got from the forum re upgrading to KDE 4.2.3 was not at all clear to me and got me into the problems which I had. After adding the important line to the software list, It said >Then refresh and do a full upgrade< That is what I tried to do and NOTHING worked.)

Now, with the guidance, if all goes well with this konsole thing I will report back
Rusty

**dibl** · May 16, 2009, 07:22 AM

Re: Upgrade from Kubuntu9.04 KDE 4.2.1 to KDE4.2.3 - Public key will not install

Looks like progress -- good job Rusty!

Your ping statistics are not good, however -- that Internet connection is not working very well. Here's what it should look like:

dibl@jaunty:~$ ping www.google.com
PING www.l.google.com (66.102.1.104) 56(84) bytes of data.
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=1 ttl=245 time=41.1 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=2 ttl=245 time=33.6 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=3 ttl=245 time=35.8 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=4 ttl=245 time=40.1 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=5 ttl=245 time=41.0 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=6 ttl=245 time=45.4 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=7 ttl=245 time=44.0 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=8 ttl=245 time=50.0 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=9 ttl=245 time=43.1 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=10 ttl=245 time=44.5 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=11 ttl=245 time=40.8 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=12 ttl=245 time=51.2 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=13 ttl=245 time=34.7 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=14 ttl=245 time=40.6 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=15 ttl=245 time=37.3 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=16 ttl=245 time=35.9 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=17 ttl=245 time=53.1 ms
64 bytes from he-in-f104.google.com (66.102.1.104): icmp_seq=18 ttl=245 time=34.0 ms
^C
--- www.l.google.com ping statistics ---
18 packets transmitted, 18 received, 0% packet loss, time 17021ms
rtt min/avg/max/mdev = 33.641/41.505/53.109/5.699 ms

Notice how much shorter the reponse times are (about one-tenth of yours) and also that there were zero lost packets. You can't be losing a lot of packets and get a correct download of anything. I'd be re-booting the router, if you have one, to clear the cache, and if that doesn't help you might want to consult with your ISP provider. Something is not working quite right there.

**rusty** · May 18, 2009, 07:17 AM

Re: Help- not solved - Upgrade from K9.04 KDE 4.2.1 to KDE4.2.3 - Public key issue

Help - I thought the issue was solved and reported so - but NO - it's not
1) when I test with Dolfin which version I have of KDE, it reports KDE 4.2.3

2) when I try to download anything now with Synaptic, it gives me an download error

I tried to download a small piece called VYM
and got this error

W: Failed to fetch http://za.archive.ubuntu.com/ubuntu/...untu2_i386.deb
Size mismatch

W: Failed to fetch http://za.archive.ubuntu.com/ubuntu/...2.2-1_i386.deb
Size mismatch

----------------------------------------------
before that I tried to download some games and got this result

W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2836CB0A8AC93F7A
W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used.GPG error: http://za.archive.ubuntu.com jaunty Release: The following signatures were invalid: NODATA 1 NODATA 2

W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used.GPG error: http://za.archive.ubuntu.com jaunty-updates Release: The following signatures were invalid: NODATA 1 NODATA 2

W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used.GPG error: http://za.archive.ubuntu.com jaunty-security Release: The following signatures were invalid: NODATA 1 NODATA 2

W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used.GPG error: http://za.archive.ubuntu.com jaunty-backports Release: The following signatures were invalid: NODATA 1 NODATA 2

W: Failed to fetch http://za.archive.ubuntu.com/ubuntu/...jaunty/Release

W: Failed to fetch http://za.archive.ubuntu.com/ubuntu/...pdates/Release

W: Failed to fetch http://za.archive.ubuntu.com/ubuntu/...curity/Release

W: Failed to fetch http://za.archive.ubuntu.com/ubuntu/...kports/Release

W: Some index files failed to download, they have been ignored, or old ones used instead.

I can still use the PC, but cannot download anything with synaptic
any ideas
rusty

**dibl** · May 18, 2009, 07:29 AM

Re: Help- not solved - Upgrade from K9.04 KDE 4.2.1 to KDE4.2.3 - Public key issue

Originally posted by rusty

W: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2836CB0A8AC93F7A

OK, this error is actually just a warning -- it is saying that you have not entered the GPG key for this repo, so there's no guarantee that you are connected to a secure repository.

W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used.GPG error: http://za.archive.ubuntu.com jaunty Release: The following signatures were invalid: NODATA 1 NODATA 2

W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used.GPG error: http://za.archive.ubuntu.com jaunty-updates Release: The following signatures were invalid: NODATA 1 NODATA 2

These errors indicate connection problems -- downloaded index files aren't passing their checksums, or some such problem. Probably this is related to the spotty connectivity indicated by your previous ping results. Did you learn anything about the quality of service from your ISP?

**rusty** · May 18, 2009, 07:34 AM

Re: Help- not solved - Upgrade from K9.04 KDE 4.2.1 to KDE4.2.3 - Public key issue

Hi - thanx again for the quick reply - I thouhgt I had a BIG probem on hand

no, as it was the weekend, I have not yet tried to contact my ISP provider - I did think my problems were over - but now I will contact them - I will also try to download something at another access point with another provider to see what happens
rusty

**rusty** · May 19, 2009, 12:13 PM

Re: Help- not solved - Upgrade from K9.04 KDE 4.2.1 to KDE4.2.3 - Public key issue

By now I have contacted my ISP provider and they said they will look into the problem

However, 3 things
1) since upgrading to KDE 4.2.3 I have had this problem - never before! Also my other (desktop) PC with Ubuntu 8.10 does not have this problem - same ISP.

This leads me to ask if this is not (partly) an upgrading problem - and if possibly so, how to solve the problem which I am experiencing

2) why does the public key issue come up (is it part of upgrading to KDE 4.2.3 or a problem which only some people experience - me but not graygeek).

3) why would the public key not install? I did everything as I understood how it had to be done.

will it not help to try to install the public key (again)?
here is the key which I got and tried to install
>>

mI0ESXS1/wEEALis4to4JdgrkdRunmSTfB2tYRq99Cdcgdh9up4HzAf1yTZ U1EtmETPP1Uy2
vnAFf/cCunL5VRywNJB3QOxiHdvNlijbdsa0H/fT/ulq+A4iDljUEfsaJug+dAB5uEJE0BzZ
agRjgLbFvRYtsKf3BwZizbo4XtWSAm3JSjZCGZKTABEBAAG0Ik xhdW5jaHBhZCBQUEEgZm9y
IEF3biBUZXN0aW5nIFRlYW2IRgQQEQIABgUCSXqnWgAKCRBBf7 ZCSCH+JPZMAJ4xW7gbpuA+
yedehvDQWdJHHUgseQCgy6NOmAyXqRKrIXWERkXw6h9TsRuItg QTAQIAIAUCSXS1/wIbAwYL
CQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEH0seiO/gQzVpSID/0FXxTSLtxPHrT7IE9eif5qJ
vjOjzcmOCXe9/3G0ctV8IfYHx0VynddjxgTqJ9WuEjMLVHRgXvK1Rw1XMlik+Me yyHrr9EWQ
DUFbUs+Yc2usRyZY8pVe2Uwy2x7lFsi6VBfo0k9jVsu1l1qBU9 BhANJDUTHjR15aPYiUJiZa
13CZ
=a6Gh

I will appreciate any ideas
rusty

**dibl** · May 19, 2009, 12:28 PM

Re: Help- not solved - Upgrade from K9.04 KDE 4.2.1 to KDE4.2.3 - Public key issue

KDE 4.3 is EXPERIMENTAL -- I would not advise installing it unless you are tired of looking at KDE 4.2 and interested in working at the CLI for a few days!

http://kubuntuforums.net/forums/inde...opic=3103850.0

If your internet connection is working, review this and maybe you can fix the GPG key issue:

http://en.kioskea.net/faq/sujet-809-...bkey-gpg-error

But again, that GPG warning is not a cause of actual problems on your system -- the package download is not stopped due to lack of a GPG key. Problems with installing the packages are caused by something else.

**GreyGeek** · May 19, 2009, 01:24 PM

Re: Help- not solved - Upgrade from K9.04 KDE 4.2.1 to KDE4.2.3 - Public key issue

The PGP key msg is a warning only, it does not prevent installing the KDE 4.2.3 desktop. I ran into that same error and continue on with my installation exactly as I described in a previous msg on this thread.

However, my Kubuntu 9.04 installation was not upgraded from Kubuntu 8.x, it was installed from the alpha5 release and continuously upgraded from there.

As far as the public key goes, the example you pasted into your msg is lacking the header...

**rusty** · May 20, 2009, 03:58 AM

Re: Help- not solved - Upgrade from K9.04 KDE 4.2.1 to KDE4.2.3 - Public key issue

Originally posted by dibl

If your internet connection is working, review this and maybe you can fix the GPG key issue:

http://en.kioskea.net/faq/sujet-809-...bkey-gpg-error

Hi - finally it seems solved - I used this link with this item >

Solution:
Simply type the following commands, taking care to replace the number of the key that displayed in the error message:

gpg --keyserver pgpkeys.mit.edu --recv-key 010908312D230C5F
gpg -a --export 010908312D230C5F | sudo apt-key add - <

I changed nothing and just follwoed it and now at least I can download stuff as I previously could - I do not know if the key is installed or not and do not care - the system is working.
If it did not come right this time I would have re-installed 4.2 and the rest
thanx for all the help
rusty

Announcement

Finally solved - Upgrade from K9.04 KDE 4.2.1 to KDE4.2.3 - Public key issue

Finally solved - Upgrade from K9.04 KDE 4.2.1 to KDE4.2.3 - Public key issue

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment