Bug 42212 - Multiple simultaneous logins (KDE) yields errors.
Summary: Multiple simultaneous logins (KDE) yields errors.
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdebase   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-05-24 20:25 UTC by Rex Dieter
Modified: 2007-04-18 16:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-05-29 16:42:18 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Rex Dieter 2001-05-24 20:25:59 UTC 
Description of Problem:
When logging in to multiple machines with shared home directories (NFS) 
to kde sessions, only the current one works completely.  Previous 
concurrent logins cannot lauch programs via KDE panel.

How Reproducible: every time

Steps to Reproduce:
1. login to machine a into KDE session
2. login to machine b into KDE session (same user)
3. go back to machine a, and try to launch a program from the KDE menu.  
It sometimes works once, but not more than that.  Afterward, every 
attempted program launch yields error:
Sorry - KDE Panel
! Couldn't launch konqueror (or whatever your program may be).

I used to successfully login multiple times when I used KDE 2.0.1 on 
RedHat 6.2.
Comment 1 Rex Dieter 2001-05-29 16:42:13 UTC 
I found the root cause of this problem.  It's a section of the startkde script:
rm -f ~/.DCOPserver*

If I comment this out, the problem goes away.  Unfortunately, this leads to lots
of ~/.DCOPserver_`hostname` files laying around, but that's better than
non-functional kde sessions.
Comment 2 Bernhard Rosenkraenzer 2001-08-13 13:51:49 UTC 
Fixed in 2.2-3
Note You need to log in before you can comment on or make changes to this bug.