Bug 678993

I can reproduce this bug on a system that is updated from 11.3, and with a different set of repositories.

Successive systematic disabling of various repositories does not affect the bug happening.

In /etc/sysconfig, *_PROXY settings (HTTP_PROXY,...) are all empty, and PROXY_ENABLED is "no", NO_PROXY is set to "localhost, 127.0.0.1".

I can also reproduce this on a system that was updated from 11.3x86_64, however I also have a second system that was upgraded that does not have the issue.

Ive read reports of the issue being resolved by removing ~/,kde4/share/config/kioslaverc, however this resolution didnt work for me.  I did notice that in this file on the machine that wasnt working it had an additional Proxy Settings block to it with ProxyType=1

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

[Proxy Settings]
ProxyType=1

I removed those lines from the file to match the one on the working machine but it didnt resolve the issue.

Also an additional detail, the machines are quite different but the one thing that stands out is that on the machine that didnt have the problem I am using the traditional ifconfig to control my network, on the machine with the problem I am using network manager.

Both machines have the same repos setup and on the one where kpackagekit doesnt work, I have no problems using zypper/yast.

I can verify that removing ~/,kde4/share/config/kioslaverc did not solve the problem.

I, too, connect via Network Manager.

I can verify that changing the connection method to ifup scheme (wireless connection), KPackageKit seems to work as expected.

same here - all my machines connect via networkmanager and have this bug
(the old updater applet, still available in KDF) is also affected)

as this is also keeping users from receiving updates, I'd consider this bug as critical

I can add to my previous post:
I switched back from ifup to Network manager in Yast.
Now, everything seems to work fine, even after a reboot. KPackagekit checks for updates and installs them without problems.

Could somebody verify this as a temporary solution (this is what I think I did):
1) Switch to ifup method in Yast Network and connect.
2) Start KPackagekit, check for updates and/or install some
3) Switch back to Network Manager in Yast, and check if it works.

I switched network to ifup and verified I had a working internet connection.  I started kpackagekit but still had the HTTP_PROXY error message (even after restarting kde).  Then I switched back to networkmanager and restarted kde and kpackagekit now works.

My workaround:
Open the KDE systemsettings (german Systemeinstellungen),
choose "Networksettings" (german Netzwerkeinstellungen), then "Proxy" and
activated "Directly connected to the Internet" (german "Direkt mit dem Internet
verbunden").

BUT ATTENTION: I'm not sure, if that maybe caused this problem on my system:
https://bugzilla.novell.com/show_bug.cgi?id=679650

I've this bug after update (from 11.3), workaround suggested on previous posts didn't work for me.
The real big problem with this bug is that in my PC Kpackagekit system tray doesn't appear at all (I've seen the error going to KDE system settings), so you are not advised that there are problems with system updates.
This is really a wrong behavior for a program that does system updates, it has never happened with previous SUSE Update applet.
I think severity of the bug should be raised from 'normal' to 'critical'

Same problem here (resolving HTTP_PROXY in KPackageKit) on a system with fresh install of 11.4M6 & update to 11.4 Release.

I was able to solve it by editing out the entire [Proxy Settings] stanza from ~/.kde4/share/config/kioslaverc, then logout/login.

When I ran KPackageKit after login, I was immediately given the "Authorization required to set Proxy" window asking for root password, which I canceled as I don't use any proxies.

OK, now I'm thoroughly confused.   KPackagekit worked yesterday afternoon, but today when I booted this laptop, it was back to failing to resolve HTTP_PROXY.  While I was busy looking at various files, every few minutes I'd see a transient window pop up asking for Authentication required to set proxy (or whatever that message is - it went away before I could record it).  I did note that .kde4/share/config/kioslaverc was as I edited it - no [Proxy Settings].  Then I fired up konqueror to read the KDE help, and next time I looked at the kioslaverc, the [Proxy settings] was back.  I repeated the edit to remove it, logged out and back in, and now KPackageKit is working!

Where is the reference to HTTP_PROXY coming from?

I think I figured this one out.

KPackageKit does the repo-updates as root, so your user's proxy settings have no effect on root.

If root has no .kde4/share/config/kioslaverc then it takes the default in /etc/kde4/... and that one has the dreaded HTTP_PROXY in it.

A workaround is to create a .kde4/share/config folder in /root/  and copy your user's kioslaverc to there.

Another would probably be to log in to KDE as root and fix the proxy settings. This should also write out a working kioslaverc.

Why the defaults in /etc/kde4 are broken is probably the real question here.

That didn't help in my case.  I have the same .kde4/share/config/kioslaverc (without [Proxy Settings]) in both ~ and ~root.  But I still can't get kpackagekit to run from my desktop - just tried it, and 'can't resolve HTTP_PROXY'.

Reported this bug upstream:
https://bugs.kde.org/show_bug.cgi?id=274184