KPackageKit HTTP_PROXY error on update 11.4

OK the point is that here is a case it makes sense. If you know how to create the KDE4 directory structure from scratch from the command line please post the instructions. It of course should have been created at the install and the creation of the root user. But something must be broke in at least some CD installs. IMO In this case it is worth the risk. The file ownership changes seem to only occur when you log to the GUI as root then do things in the regular user areas. Besides they are easy ti fix if you know how. But you do need to know how!!!

Rules are made to be broken :slight_smile:

On 04/02/2011 06:06 AM, gogalthorp wrote:
>
> OK the point is that here is a case it makes sense.

thank you for not being ‘insulted’…

> If you know how to
> create the KDE4 directory structure from scratch from the command line
> please post the instructions.

i think i should know how, but i’m not sure i do…i think the secret
is finding the ‘skeleton’ for the user’s hidden .kde4 directory…but,
i don’t know offhand if or where that is hidden…but, maybe this
might work [maybe: do not try this at home without a safety net!]:

-use YaST to create a testUser
-open terminal
-become root with su -
-open mc
-copy /home/[testUser]/.kde4 to /root/.kde4

not easy, granted!!
might not work, granted…but, i guess it would…

> It of course should have been created at the install and the creation of the root user.
> But something must be broke in at least some CD installs.

the most important part of this thread is the need to get THAT bug
reported…anyone know if it has it been?

it is so bad that (imHo) the image with the problem should be re-issued…

> IMO In this case it is worth the risk.

on this we need to agree to disagree…because there are
alternatives, like:

  • turn off the pesky, obtrusive YOU replacement and use YaST > Online
    Update instead…sure, you have to remember to do that (or set a cron
    to remind you)…but mostly only on friday or saturday, as that is
    when the updates usually flow…

  • or build the structure as laid out above

AND, more importantly (from my point of view) is the potential impact
on not only the few persons seen in the thread and being answered
(who may have a known level of understanding and EASILY able to stay
out of trouble), but the dozens (hundreds, thousands ??) which will
(may?) google in and see the direction to log into the GUI as root,
and NOT know the dangers, pitfalls, less easy but more safe ways, etc
etc etc…

so, in my mind, not giving dangerous to inexperienced user advice to
even a very experienced users is the best move hereor lay in a
lot more caveats and why not to do this or that than was in this
thread’s #11 (which included zero warnings to the inexperienced
lurkers or late comers), making it therefore ill advised, as written…

> The file ownership changes seem to only occur when you log to the
> GUI as root then do things in the regular user areas.

true

> Besides they are
> easy ti fix if you know how. But you do need to know how!!!
>
> Rules are made to be broken :slight_smile:

all very true!

i’ve broken more than my share of rules, some VERY dangerous to
break–but, here i try not to recommend other to do so…especially
i try to not recommend known insecure and unsafe administrative
practices…even for one time, special use…because my observation
of human nature has been that if i “get away with” the “easy way”
once, i am VERY likely to try it again…and, again…and,
again…until catastrophe!

as always, ymmv.


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]

Neither workaround worked for me. After reboot the error returned.

Apparently some system script is resetting this proxy setting and rendering kpackagekit unusable except as root.

I’ll just wait for the bug to be fixed and continue making manual updates :frowning:

Well the issue came back on my laptop, but I believe I have fully fixed the problem on my end.

First someone mentioned that they think its a live cd install issue, however it seems more prevalent in 11.4 that was upgraded from 11.3.

Alright so the problem seems to be that Suse decided to randomly set (I cant say for sure randomly but I have no idea how or why this was set this way) a proxy setting that tells KDE to “use preset proxy environment variables”. This setting was enabled on my laptop that had the issue, but was not set on my desktop that has never had the issue. This setting can be found in System Settings (Personal Settings)->Network Settings->Proxy from there you will want to check “Connect to the internet directly”. I cant remember if I had to logout and log back in before it took effect but you may want to try that if it doesnt immediately take effect.

Like I said I have no idea how or why this ever got enabled on my laptop since Ive always used a direct connection, but it did get set as part of the upgrade. I do not know why switching from Network Manager to traditional with ifup and back resolved the issue for a while, but when it came back I found the setting mentioned above. I have not had the issue return since I changed that setting.

Mine is set to directly connect but I still get the proxy error.

On 04/02/2011 06:06 PM, Ski K2 wrote:
> Mine is set to directly connect but I still get the proxy error.
>
>

all here with new information or details different from that already
logged, should join the fun, here:

https://bugzilla.novell.com/show_bug.cgi?id=678993


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]

Unlike Windows there is really no reason to log onto GUI as Root (and Windows is working hard to move to this path, you’ve dealt with UNC right)

Windows talk aside (since that’s my day job) launching a single GUI app with Root elevation in Linux is always a simple command away:

kdesu <app_name>

In this case
kdesu kpackagekit

There’s still a bug here as it’s supposed to prompt for elevation by default, but even after prompting something is wrong. Running the above command got kpackagekit working for me

I had the same problem with KPackagekit. Thw switching from Networkmanager to ifup, ant then back to Networkmanaegr does not solved the problem.
And i deleted the 2 files:
( .kde4/share/config/kioslaverc
.kde/share/config/kioslaverc ).
Now the updating with KPackagekit work’s fine.

Thank you for helping!