Bug 32425 - DCOP communication problem! after login on second X-Terminal
Summary: DCOP communication problem! after login on second X-Terminal
Status: RESOLVED FIXED
Alias: None
Product: dcop
Classification: Frameworks and Libraries
Component: dcopserver (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Matthias Ettrich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-09-13 07:33 UTC by Tobias Kretschmar
Modified: 2003-11-24 11:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Kretschmar 2001-09-13 07:25:13 UTC 
(*** This bug was imported into bugs.kde.org ***)

Package:           dcopserver
Version:           KDE 2.2.0 
Severity:          normal
Installed from:    SuSE RPMs
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

I have a server and a X-Terminal. 

The server is running kde local. I am logged in with my userid on the server. 

The X-Terminal runs LTSP (get his kernel system X etc) from server and show KDM login screen from server.

After login on X-Terminal with same user as on server I cannot start any DCOP using application on the server. Here is a example for kmail:

DCOPClient::attachInternal. Attach failed Authentication Rejected reason : None
 of the authentication protocols specified are supported and host-based authenti
cation failed
DCOPClient::attachInternal. Attach failed Authentication Rejected reason : None
 of the authentication protocols specified are supported and host-based authenti
cation failed
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running remove /home/tk/.DCOPserver_hecker_:0
and start dcopserver again.
---------------------------------

tk@hecker: ~ > kmail
DCOPClient::attachInternal. Attach failed Authentication Rejected reason : None
 of the authentication protocols specified are supported and host-based authenti
cation failed
DCOPClient::attachInternal. Attach failed Authentication Rejected reason : None
 of the authentication protocols specified are supported and host-based authenti
cation failed
FATAL: DCOP communication problem!
kdeinit: Communication error with launcher. Exiting!
DCOPClient::attachInternal. Attach failed Authentication Rejected reason : None
 of the authentication protocols specified are supported and host-based authenti
cation failed
DCOPClient::attachInternal. Attach failed Authentication Rejected reason : None
 of the authentication protocols specified are supported and host-based authenti
cation failed
DCOPClient::attachInternal. Attach failed Authentication Rejected reason : None
 of the authentication protocols specified are supported and host-based authenti
cation failed
ERROR: KUniqueApplication: Can't setup DCOP communication.
DCOPClient::attachInternal. Attach failed Authentication Rejected reason : None
 of the authentication protocols specified are supported and host-based authenti
cation failed
FATAL: DCOP communication problem!
tk@hecker: ~ > kmail


(Submitted via bugs.kde.org)
Comment 1 Waldo Bastian 2003-03-19 19:10:07 UTC 
Make sure that your startkde script does not contain anything that touches 
/tmp/.ICE-unix  
 
If it has, remove those parts.
Comment 2 Krzysztof Dubowik 2003-04-18 10:14:13 UTC 
I had a similar problem with KDE 3.0.3. And yes, removing the 3 lines, that 
modify /tmp/.ICE-unix from /usr/bin/startkde solved the problem.


I also think this bug is a duplicate of 49169.


Regs,


Krzysztof Dubowik
Comment 3 Waldo Bastian 2003-11-24 11:46:19 UTC 
*** Bug has been marked as fixed ***.