>> KDE ain't supposed to be run like that. Different users on different
>> X sessions is okay. The same user on different X sessions is a no-no.
>I'm not at all disputing this. But could you please provide an example of
>why? I can imagine hypothetical reasons, such as the uid being used to
>identify the session out of multiple sessions, but I would like to be
>enlightened by an actual example.
I don't have an example at hand. The mailing list archives
at kde.org might. I do know it has to do with all the updating
that goes on in the .kde directory. It _may_ also have to do
with dcop as well.
Quote:>Another question I suppose I'll ask is, is this a good design choice?
>perhaps an oversight or assumption and things just evolved around
Maybe not a good design choice, but we do pressure the developers
to release our FAV desktop when it might need just a little bit
more time maturing ;-). Having said that, I am sure that they
are aware of this problem. As Rex Dieter said, there is at least
one KDE developer who has solved part of the problem.
Registered Linux User # 125653 (http://counter.li.org)
BOFH excuse #145:
Flat tire on station wagon with tapes. ("Never underestimate the bandwidth of a station wagon full of tapes hurling down the highway" Andrew S. Tanenbaum)
7:54pm up 2:14, 5 users, load average: 0.00, 0.00, 0.00