Bug 46410 - dcompserver on thin clients with same user name
Summary: dcompserver on thin clients with same user name
Status: RESOLVED FIXED
Alias: None
Product: dcop
Classification: Frameworks and Libraries
Component: dcopserver (show other bugs)
Version: unspecified
Platform: unspecified Other
: NOR normal
Target Milestone: ---
Assignee: Matthias Ettrich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-12 19:48 UTC by Keith Graves
Modified: 2003-11-24 11:55 UTC (History)
2 users (show)

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 Keith Graves 2002-08-12 19:37:57 UTC 
(*** This bug was imported into bugs.kde.org ***)

Using RedHat 7.3 with KDE 3.0.0 and two Disklessworkstations.com Jammin
125 xterms. The server is running LTSP 3.0.5.

When a user logs into one thin client and does not log out but goes to
the other system and logs in as the same user the first session on the
first thin client will complain about the dcompserver not running.
Investigating the problem is was discovered that the dcop file in
/tmp/ICE-unix that was running for the
first session is killed and replace by the dcop process of the second
login. Is there a way to have the user
be able to use both sessions at the same time?

Keith Graves
keith.graves@kodak.com
Comment 1 Simon Hausmann 2002-10-01 00:29:57 UTC 
Yes, this is supposed to just work. When the user is logged in on both 
clients, do both logins have a different value for $DISPLAY set?
Comment 2 keith graves 2002-10-01 23:46:57 UTC 
Yes each xterm has a different DISPLAY name:

First xterm - DISPLAY=ltsp1:0.0
Sec. xterm  - DISPLAY=ltsp2:0.0

The names and IPs are set up in the /etc/dhcpd.conf file according to MAC
address. 

What is the same is the hostname. If you just type in hostname. It reports the
hostname of the DHCP server. I have since tried this with ICE window manager and
it appears to work properly. KDE however still has the problem I described.

Thanks.
Comment 3 Waldo Bastian 2003-03-19 17:29:49 UTC 
Check that your startkde script does not have any lines referring to ICE-unix. 
If it has, remove it.
Comment 4 Waldo Bastian 2003-11-24 11:55:17 UTC 
Assumed to be fixed.