Bug 334811

Summary: global proxy settings are not read by KDE4
Product: [openSUSE] openSUSE 11.1 Reporter: Dieter Jurzitza <dieter.jurzitza>
Component: KDE4 WorkspaceAssignee: E-mail List <kde-maintainers>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P2 - High CC: robin.knapp, romil, scott
Version: Alpha 0   
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 10.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: plaster for the proxy-problem

Description Dieter Jurzitza 2007-10-18 12:08:57 UTC 
When installing kdetoys and trying to use kweather, everything is fine with openSUSE 10.2.
However, on openSUSE 10.3 kweather refuses to work though the proxy entries in /etc/sysconfig/proxy are identical and the network interface is not hindered by any firewall. No station is being found at all.
Using the old version of kdetoys from openSUSE 10.2 does not work either, so I assume there is some bug with the proxy - configuration.
If you enter runlevel 3 and set things manually:

export HTTP_PROXY="<PROXY>:<PORTNUMBER>"

and do a startx afterwards, kweatherservice works fine.
Must be some basic configuration issue.
Thank you for taking care
Comment 1 Dieter Jurzitza 2007-10-18 14:04:44 UTC 
Created attachment 179243 [details]
plaster for the proxy-problem

Hi,
this patch to /opt/kde3/bin/startkde fixes the behaviour, however, I cannot imagine that this is how it should be fixed. Better suggestions are welcome!
Comment 2 Dirk Mueller 2008-05-08 12:19:59 UTC 
I've submitted this to the kde3 startup scripts.. kde4 is still missing.
Comment 4 Lubos Lunak 2009-03-20 16:24:59 UTC 
*** Bug 298809 has been marked as a duplicate of this bug. ***
Comment 5 Lubos Lunak 2009-06-08 11:48:18 UTC 
Fixed for KDE4 too.
Comment 6 Lubos Lunak 2009-06-10 16:53:20 UTC 
*** Bug 511626 has been marked as a duplicate of this bug. ***
Comment 7 Lubos Lunak 2009-06-12 13:29:01 UTC 
*** Bug 504114 has been marked as a duplicate of this bug. ***