Bug 88215

Summary: KDE 3.3 does not work with SOCKS anymore
Product: [I don't know] kde Reporter: Florian Evers <florian-evers>
Component: generalAssignee: Thiago Macieira <thiago>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Florian Evers 2004-08-27 13:38:50 UTC 
Version:            (using KDE KDE 3.3.0)
Installed from:    Gentoo Packages
OS:                Linux

Hi,

importing this bug from gentoo's bugzilla:
http://bugs.gentoo.org/show_bug.cgi?id=58414

KDE 3.3 does not work correctly when activating socks.

Activate SOCKSv5 with dante-libs installed:

K-Menu ->
Control Center ->
Internet & Network ->
Proxy ->
Tab "SOCKS" ->
[x] Enable SOCKS support
(o) Dante
"Test" -> "Success: SOCKS was found and initialized."

Ok, no problem. But from this moment on, you can't
start konqueror anymore:

florian@powerstation ~ $ konqueror
konqueror: ERROR: Error in BrowserExtension::actionSlotMap(), unknown action : searchProvider
florian@powerstation ~ $


Amarok freezes:

florian@powerstation ~ $ amarok
[amaroK loader] connecting to /home/florian/.kde//socket-powerstation/amarok.loader_socket
[amaroK loader] amaroK not running. Trying to start it..
---freeze---


... and the worst thing will happen when you do
log out of kde with socks-settings kept activated.
"This user" will not be able to login to KDE
anymore. You have to grep through all the
configfiles in ~/.kde to search the socks-config
(I failed with this, and had to deinstall the
dante-libs... this helped).

Greetings, Florian
Comment 1 Alex de Kruijff 2004-09-04 13:45:29 UTC 
I'm on FreeBSD 5.2 and also have this.
I found a workaround. Edit the file ~/.kde/config/kdeglobals and set            
SOCKS_enable to false.
Comment 2 Mindaugas 2004-09-15 10:26:59 UTC 
Hi,

I have same problem with Kopete and dante socks.

Mindaugas
Lithuania
Comment 3 Thiago Macieira 2005-03-30 16:03:31 UTC 
This is no crash.

Bug has also been fixed already.

*** This bug has been marked as a duplicate of 98018 ***