At first, I couldn’t login to KDE 4.10.5, so I have to delete the hidden folder named .kde4, then the KDE 4.10.5 can be login again, but I find that Privoxy(use to transform the socksproxy to httpproxy that can be used to the softwares only support http proxy) stop working, I check the values of Service and Proxy in YaST panel, it’s OK, so I want to ask Did I delete the file(s) I shoudn’t delete, and which files are?
What I see in these forums is that when the advice is given to try a clean .kde4, that it is either of the form “create a new user and see if that new user gets the same problem”, or “move (that is rename in Linux parlance) .kde to another name and see if that helps”.
In both cases you would:
a. prove that the problem is indeed related to something inside .kde4;
b. still have the old contents of .kde4 so you can e.g. copy parts step by step and check when the problem reemerges.
So when that advice that you “have to delete the hidden folder named .kde4” comes from these forums, we would like to know in what thread, so we can contact the one who gave it.
If you suspect a corrupted KDE profile, then you might delete the hidden kde folder and start over.
But, as you’ve found it really does delete <the entire profile>
So, now specifically your Privoxy Q.
I haven’t looked looked closely at how Privoxy is configured by default, but more generally Proxy settings can be and are configured a number of ways.
Can be at the OS level (eg YAST)
Can be at the Desktop level (eg KDE “Configure Desktop”)
Can be at the Application Level (eg Web Browser settings)
Typically SOCKS and HTTP proxies can be configured at any of the levels I described, an work well. There are reasons for doing so in each case, eg Do you want all Users and System to use the same proxy settings? Only specific apps?
So, there is no single place that’s guaranteed to be where your proxy settings are configured.
I have configured the in YaST before, so after deleting the .kde will have anything changed in YaST, I configured the proxy for Online Update and Software Management and others that can through privoxy.
When I run the Proxy test, it returns this message less than one second
About to connect() to proxy 127.0.0.1 port 8118 (#0)
Trying 127.0.0.1…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
Please, a mall interuption. We have a feature on these forums software that is not easy to be found. It is the CODE tags. You get them by clicking on the # button in the tool bar of the poste editor.
All here like it very much when you post computer text (like you did above) to copy/paste the prompt, the command, the output and the next prompt between CODE tags. This wll prevent the layout as you see it on the terminl and in the same time tell people what command you exactly used and more.
Just a technical remark on forums usage.
You use CODE tags around your computer output, which is very fine. But when you would extend your copy movement with the mouse a little bit so that it includes the prompt and the command (and preferable the following prompt), we have everyting inside the CODE tags. There is then no need for you to explain what command you gave, because it is there in full glory.
Thus not:
This is the output of ls -dl /home/henk
drwxr-xr-x 84 henk wij 4096 22 aug 11:42 /home/henk
But
henk@boven:~> ls -dl /home/henk
drwxr-xr-x 84 henk wij 4096 22 aug 11:42 /home/henk
henk@boven:~>
Just means that the privoxy configuration is intended to be specific to the logged in User.
Well, there you have it, you need a config file. Maybe a template file can be downloaded from somewhere or remove/re-install will install a new default file.
I remember the config file was /etc/privoxy/config, and it is in /etc/privoxy for now, not in the home folder, how to move the config to the /etc/privoxy/
Although the location is likely specified in a config file, if you have a working config file in a wrong place, it’s likely easier to simply copy the working file to the location the app(Privoxy) is expecting.
Of course, as I speculated, it’s likely that because of the location it will only work for the logged in User but that is likely sufficient for most people.