KPackageKit HTTP_PROXY error on update 11.4

English Install/Boot/Login
1

I am having an issue with KPackageKit, actually 2 issues but one makes it unusable.

The major issue is that when I go to apply the updates I get the following error message (at least here are the details of the message)


Download (curl) error for 'http://download.nvidia.com/opensuse/11.4/repodata/repomd.xml':
Error code: Connection failed
Error message: Couldn't resolve proxy 'HTTP_PROXY'

I do not run my connection through a proxy and my internet works correctly. This is on a laptop I upgraded using zypper from 11.3 to 11.4 (I did the same with a desktop which does not have this issue). zypper refresh successfully refreshes the repositories, and the various Yast repo tools all work correctly. Additionally after I am shown the updates and am prompted for root pw, the packages will no longer show up for a while, each time it tries to look for updates the message comes through but they will show up after a while again.

The other issue I have is that it requests my pw multiple times, this also happens on my desktop that actually will update. I get prompted twice, they are immediate and back to back. This one is a little minor annoyance but there should be no reason that it needs to make this request multiple times.

Any help would be appreciated, and I am more concerned about the HTTP_PROXY issue. Please note that I use NetworkManager to control my connections on my laptop that has the issue, and my desktop I use the traditional ifconfig to control my connections.

Additionally I have the same repos setup on both computers.

2

I had the same problem and solved by deleting two files (make a backup first!):

.kde4/share/config/kioslaverc
.kde/share/config/kioslaverc

I am not sure why this file is duplicated, maybe a remnant of my openSUSE 11.2 installation.

Hernan

3

I had the same problem with the beast that is KPackageKit. Updating via Yast/zypper continued to work well and provides more information that is useful at this early stage a new release. :slight_smile:

4

I removed .kde4/share/config/kioslaverc however it didnt solve anything, also interestingly enough the file did not get recreated when I restarted kde (or ran kpackagekit manually).

5

Strange! I started openSuSE, tested KPackageKit (it was not working), deleted these files, rebooted and then KPackageKit was working!

While I was trying to solve this I found this bug report. You might keep and eye on this to see what the developers say.

Hernan

6

So I still have the issue, but wanted to give some more information.

my original ~/.kde4/share/config/kioslaverc file was


$Version]
update_info=kioslave.upd:kde2.2/r1,kioslave.upd:kde2.2/r2,kioslave.upd:kde2.2/r3

[Proxy Settings]
ProxyType=1

I checked the file on my desktop that works and copied it over. It simply didnt have the Proxy Settings section to it


$Version]
update_info=kioslave.upd:kde2.2/r1,kioslave.upd:kde2.2/r2,kioslave.upd:kde2.2/r3

I also verified that the /root/.kde4/share/config/kioslaverc file did not contain proxy settings (it didnt and matches the above).

I also checked /etc/kde4/share/config/kioslaverc it matches the file on my desktop that works. It contents are


[Proxy Settings]
NoProxyFor=NO_PROXY
ProxyType=4
ftpProxy=FTP_PROXY
httpProxy=HTTP_PROXY
httpsProxy=HTTPS_PROXY

Still have no clue why its not working.

7

Just an update on this if anyone else is looking at this thread. Another user and myself were able to resolve the issue by switching the network configuration to traditional with ifup restarting kde, and then switching back to network manager and restarting kde.

8

In contrast with the problem above, on my system, I’m not prompted at all for a password. Updating fails using KPackageKit with an authentication error message. I can only use YAST online update. Also, YAST and KPKit don’t show the same list of available updates - updates are listed in KPKit that do not appear in YAST.

Other specifics of my system that might be relevant - I’m operating with a clean install of 11.4 on a newly formatted partition; and, I enabled the superuser (unchecked “use same password” for root) during installation. Perhaps that is adding to KPackageKit’s confusion.

This would appear to be a bug that would presumably be addressed by an update, but any assistance with a workaround for the problem would be appreciated.

9

I had that problem occur. This was on a clean install from the live KDE 32 bit CD.

I did an online update via Yast. The problem has not occurred again, even though additional updates have come through.

10

@Rulls I have the same experience; however, the reason why all the updates that appear in KPackageKit do not appear in YaST is that KPackageKit lists both security updates - which appear under Patches in Online update - and new versions - which you can only get in Repositories>System by clicking Packages>All in this list>Update if new version available.

If you don’t have a Repositories tab, go to View and click on Repositories.

11

This is one for the palm-meet-forehead department…

I had the same problem and it took me a while to figure out why it would not respect the settings in my .kde4… Then I realized that the repositories can only be updated by root.

A quick check revealed that indeed my root account does not have any .kde4 and that the global settings in /etc/kde4 contain the useless “HTTP_PROXY” that seems to cause the error.

The workaround is as follows:

Create a .kde4 config directory for root with something like
sudo mkdir -p /root/.kde4/share/config
Then copy your own kioslaverc over there:
sudo cp ~/.kde4/share/config/kioslaverc /root/.kde4/share/config

You can probably avoid the console-fu if you log in KDE as root and then go fix the proxy settings.

Hope this helps!

12

Interesting.

This happened to me on the system that I installed from a live CD.

I did a Yast online update, which worked. The problem has not occurred again.

So perhaps the online update created the necessary “.kde4” information for the root account.

13

This doesn’t seem to have worked for me.

I get a they are the same file when I copy kioslaverc.

14

You are onto something here.

The command line voodoo didn’t work but logout as normal user login to KDE as root Kmenu > Applications > System Configuration > Kpackagekit and Kpackagekit updated successfully for the first time on this system :slight_smile:

Thank you very much!

Logout and back in as normal user and ran Kpackagekit fine from Kmenu.

Now to see if it runs automatically on startup :slight_smile:

15

This issue could be related to LiveCD install.

I have 3 11.4 64bit KDE systems here. Two where Kpackagekit worked fine were installed from DVD.

My system has a bad DVD reader and wouldn’t boot from the install DVD so I installed from the LiveCD and it would never run Kpackagekit automatically and would give the proxy error if I ran it manually.

It’s fixed now thanks to Answerinator :slight_smile:

16

On 04/01/2011 12:36 PM, Answerinator wrote:
>
> You can probably avoid the console-fu if you log in KDE as root and
> then go fix the proxy settings.

ill advised…
http://en.opensuse.org/SDB:Login_as_root
http://tinyurl.com/ydbwssh
http://tinyurl.com/4nsaqst
and many others…logging into KDE is not advised and should not be
used…

–
CAVEAT: http://is.gd/bpoMD
Tried LibreOffice? Do that and help at http://is.gd/dZ9j2W
[NNTP via openSUSE 11.3 + KDE4.5.5 + Thunderbird3.1.8]

17

In this case maybe. For some reason the .kde4 is not being created in /root. So PackageKit has no place to go. I guess there must be some initialization function that may create /root/.kde4 from the command line. But I have yet to find it. By far the easiest way is to log into the GUI as root. But you are right care should be taken. Login logout you should not need to run anything from the GUI you should only need the create the proper directories for KDE which the simple logging in will do. But this all points to an installation problem that if fixed would eliminate the need.

18

On 04/01/2011 05:06 PM, gogalthorp wrote:
>
> By far the easiest way is to log into the GUI as root.

it may be the easiest, but only so long as other stuff doesn’t get
messed up in the process…

my usual: no administrative duty requires anyone to log into the DE
as root still holds, and in fact the Answerinator gave the correct
litney to solve the missing file problem without logging in as
root…which is maybe not as easy but . . .

imHo: anyone who craves easy is in the wrong operating system.

–
CAVEAT: http://is.gd/bpoMD
Tried LibreOffice? Do that and help at http://is.gd/dZ9j2W
[NNTP via openSUSE 11.3 + KDE4.5.5 + Thunderbird3.1.8]

19

As I said in my post, in my case the command line failed to resolve the issue!

It isn’t a matter of which is easiest but rather which method resolved my issue!

Your previous caveat regarding the care to be taken using a root gui login seemed well advised for absolute noobs.

Insulting the OP “imHo: anyone who craves easy is in the wrong operating system.” isn’t of any help :slight_smile:

20

On 04/01/2011 07:06 PM, Ski K2 wrote:
> Your previous caveat regarding the care to be taken using a root gui
> login seemed well advised for absolute noobs.

then i am an absolute noob because it is advice i follow…and, there
are lots of system administrators that also follow that advice…

in fact, i learned that advice from a *nix sysadmin who has been a
granddad many years when he taught me how to do it right…

> Insulting the OP “imHo: anyone who craves easy is in the wrong
> operating system.” isn’t of any help :slight_smile:

it is not insulting, it is a fact…

if you or s/he or i or anyone wants an easy operating system they
should buy Mac…the next easiest i don’t know, but it is not openSUSE…

note: i’ve not owned or used a Mac so, that is just what i hear…

anyway, if gogalthorp thought i was insulting him personally, i’m sure
he can and will speak for himself…but, my experience with the folks
from West by God Virginia can tell the difference between a slap and a
fact.

–
CAVEAT: http://is.gd/bpoMD
Tried LibreOffice? Do that and help at http://is.gd/dZ9j2W
[NNTP via openSUSE 11.3 + KDE4.5.5 + Thunderbird3.1.8]