Sure I can do that, but the problem lies even deeper — in the PackageKit, or curl. Whom should I ask what to do now?
And I’ll say again, I have both desktop PC and a laptop and this problem happens only on the former.
I just tried to enter superuser shell with sudo -i and run pkcon -v update. And it worked!
So, the problem is somewhere in my profile settings.
Any ideas?
Please wait for others and not for me. I haven’t PackageKit installed, nor the applet.
The only thing I can say that when it is bound to that user, then try to find within that user’s .config and/or .kde4 directories if there is a place for the Applet (I forgot it’s real name). And then remove that.
I don’t know. I would guess that either it is in your shell startup script (usually “.bashrc”) or in your desktop settings. If you are using KDE, then under System Settings, look for Network Settings, and check the Proxy setting there. Here, I have it set for “No Proxy”.
Edit: everything started to work and I don’t even how.
Okay.
By the way, I removed the “test” user, rebooted the PC and stopped working. [Now I removed .config/plasma-pk-updates and moved .kde4 to .kde4.bak, and voila, it works.]]] It doesn’t. I rebooted and it stopped working again.
Another strange thing noticed.
When I log out and log in, everything works (pkcon, Plasma applet); but when I reboot and log in for the first time, they throw me an error (that “curl couldn’t resolve proxy: HTTP_PROXY”).
What is this sorcery?
I ran *dhcpdump *and found nothing except some “Vendor specific info”:
OPTION: 43 ( 40) Vendor specific info 0126687474703a2f .&http:/
2f31302e3139322e /10.192.
3234312e3234392f 241.249/
74723036392f7365 tr069/se
727665722e706870 rver.php
What bothers me more is that everything starts to work when I log out and log in into KDE again, but after reboot and first log in (I don’t do it automatically) it refuses to even check updates.
At some time in the past, I use the KDE update icon. I always did updates from root command line. But by enabling the update applet, I could look at the tray. If the update applet reported updates, then it had already refreshed the repos. It the update applet was still showing but not indicating updates, then it was busy refreshing. So I would wait.
But, at some time, that stopped working. The update applet never showed in the tray. If I looked at the hidden tray, the applet said there was a network problem. So perhaps that was the same problem.
Recently, I have been doing a first login to “icewm” to update, and then a later login to KDE. So I haven’t been seeing this. But I’ll go back to the previous ways and see if I can monitor what is happening.
If it’s a bug, then I don’t know where to report it and how to report it. Since looks like I am the only suffering I doubt it would be easy to reproduce and take measures against.
I can only summarize:
Launching sudo -i and then pkcon -v update or just doing sudo pkcon -v update works, but doing it as the main user doesn’t work. (i.e. without sudo)
Both pkcon and applet complains they couldn’t resolve proxy (perhaps through curl) HTTP_PROXY, which I haven’t even set.
Logging out and logging in back solves the problem. Rebooting and logging in for the first time brings error back.
