su (or kdesu) still leaves you running only one xorg stack owned by Joe, and it maps things across as best it can, but its still one xorg, one dbus and (I suspect) one of several other things.

This has never worked well in the same machine since kde3. (At least not under KDE4/5/Plasma).

This worked without problem in openSUSE 10.3 and also works without problem in openSUSE 12.1 but 12.1 has so many other problems with its KDE plasma desktop that it is essentially unusable.

As far as I am concerned, Start / Leave / Switch user is the only safe and valid way to run two users (alternately) as it replicates an entire new instance of xorg stack on a different vt.

The problem with Start / Leave / Switch user is that it is extremely awkward and cumbersome to use. As you might have guessed, given that this is my own personal computer, john is really an extension of joe but I have set up john as a separate user in order to safeguard data that I don't want user joe to have unconditional access to, since it is under user joe that I use the computer to access the internet and if a hacker were to compromise joe, the data under john would be inaccessible since john is a separate user on my system. Yet, at the same time, again for security reasons, I want to minimize the use of root as much as possible, which is why I don't keep the data belonging to john under user root. Almost all of the time, I only need to do minor updates to john's data or move data belonging to joe over to john. A file manager running under user john that I can open up from joe's KDE desktop is more than capable of doing those things and is far quicker and a lot less cumbersome and awkward to use. Then again, there are times when I do want to open up a full KDE desktop session under john and it is always when I would already have a file manager window open under john on joe's KDE desktop. That is why I am looking for a way for both those actions to work at the same time without problem. The openSUSE development team recognizes that people would want to be able to do this since they have provided the means to do so with user root by having the openSUSE install program install the Start / Applications/ System/ File Manager/ File manager (superuser mode) option to start up dolphin under user root. I want to be able to do the exact same thing, except with a user other than root. Unfortunately, this same collision problem also occurs with user root. If you use Start / Applications/ System/ File Manager/ File manager (superuser mode) and then start up a full GUI session under user root, you will also get the KDE desktop collision I described. Again, there wasn't this problem with user root either in openSUSE 10.3 or 12.1.

su (or kdesu) still leaves you running only one xorg stack owned by Joe, and it maps things across as best it can, but its still one xorg, one dbus and (I suspect) one of several other things.

To get su (or kdesu) to even pull up a working dolphin file manager under user john, I found out that I have to first set enable-linger for user john using loginctl, or do something else equivalent to that. Perhaps, using a shell script, it is possible replicate a new instance of that xorg stack prior to using kdesu? ----- Original Message ----- From: "John Andersen" <jsamyth@gmail.com> To: <opensuse@opensuse.org> Sent: Saturday, October 29, 2016 2:50 PM Subject: Re: [opensuse] Collision between openSUSE 13.2 KDE sessions if dolphin from another user run under first user's KDE session.

On 10/29/2016 02:32 PM, Alec Destry wrote:

...

from joe's KDE desktop, run Kdesu, enter john's password and then have Kdesu run dolphin.

That's what I was afraid you might be doing.

su (or kdesu) still leaves you running only one xorg stack owned by Joe, and it maps things across as best it can, but its still one xorg, one dbus and (I suspect) one of several other things.

This has never worked well in the same machine since kde3. (At least not under KDE4/5/Plasma). It will try to make things work (poorly) that would have otherwise have failed outright if you were accessing via ssh from afar. (Or might have worked with no corruption in some cases).

I think some desktop environments handle this more elegantly, but KDE has leakage when you do it this way.

. .

As far as I am concerned, Start / Leave / Switch user is the only safe and valid way to run two users (alternately) as it replicates an entire new instance of xorg stack on a different vt.

-- After all is said and done, more is said than done.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 10/29/2016 04:32 PM, Alec Destry wrote:

I found out that I have to first set enable-linger for user john using loginctl, or do something else equivalent to that. Perhaps, using a shell script, it is possible replicate a new instance of that xorg stack prior to using kdesu?

Linger is only to get around an (utterly unwarranted) assumption made by the systemd devs that when you log out you automatically want every process you started to be killed. I'm not sure why you are seeing the need for linger. Its lot like you were logging out. Mystifying. su is not exactly the same as sudo. And kdesu does not run the target user's shell profile as best as I can tell. I would suggest you try Carlos's suggestion of "su - username" just to see if it behaves different. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 10/29/2016 10:09 PM, Alec Destry wrote:

Originally, on linuxquestions.org, I was given the suggestion of using "ssh - username" instead of "su -l username" and that worked.

ssh joe@localhost dolphin Does that not in fact work and keep things separate? It does for me, but I've not done extensive testing. (if you push your public key to joe's .ssh/authorized_keys file it won't even ask for a password, and you can place that in a little shell script somewhere.) -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org