Originally, after finding out that kdesu, followed by dolphin, did not work, I had posted to the openSUSE forum in the section on openSUSE 13.2 at https://forums.opensuse.org/showthread.php/510414-Running-Dolphin-under-user-other-than-root-or-currently-logged-in-user?s=6795fc249da4d553e5dcd9c83e4cf140&p=2783332#post2783332 asking how I could open up a file manager window under a user other than the one the full GUI session belonged to. For example, if I have the computer booted into a full KDE GUI desktop session under user [joe], I had posted on the openSUSE forum asking how I could open up in [joe]'s KDE desktop session a file manager window running under user [john] and with the privileges of user [john] (instead of [joe]). Ultimately, I got that first question answered, but then encountered another problem. If I have the computer booted into a full KDE GUI desktop session (on vt7) under user [joe] and open up a file manager window under user [john] in [joe]'s KDE desktop session, and then open up a full KDE GUI desktop session (on vt8) under user [john] as shown in the screenshot at http://techccu.com/users/compwiz/pictures/opensuse-forums/thread1/snapshot4...., the two KDE GUI desktop sessions will collide. Specifically, [john]'s desktop screen and keyboard input will show up on vt7 and will hide [joe]'s desktop screen and keyboard input. However, some of john]'s windows (e.g. the logout confirmation screen) will still show up on vt8 and will only accept input on vt8. This collision will occur even if I close out the file manager window for [john] in [joe]'s KDE desktop session before opening up a full KDE GUI desktop session under user [john]. If I already have a full KDE GUI desktop session under user [john] open before I open up a file manager window under [john] in [joe]'s KDE desktop session, the collision will occur if I close out [john]'s KDE desktop session and then open another KDE desktop session under [john]. This collision also occurs with user [root]. If I open up a file manager window under [root] using the command as setup by the openSUSE 13.2 install program and then open up a full KDE desktop session under [root], the same collision between [joe] and [root] will occur. The only way to prevent the collision is to log [joe] out and then log [joe] back in again after having closed out the file manager window under [john] (or [root]) and before opening up any full KDE GUI desktop sessions under any other users. Since the following sockets get replaced when [joe] logs out and then back in again: /run/user/<UID joe>/ksocket-joe/kdeinit4__0 /run/user/<UID joe>/ksocket-joe/kdesud_:0 I had asked on the forum for the names of the programs that are responsible for creating and removing those sockets, and the names of the RPM files those programs belong to. A moderator on the forum had referred me to this mailing list and suggested that I pose my questions here. My questions are: (1) has this collision problem already been fixed and is it just a matter of upgrading some RPMs in order to get rid of this collision problem? If that is the case, could you please give me the full filenames for those RPMs so that I can manually upgrade them. The computer on which I have the openSUSE 13.2 installed does not connect to the internet so I will need to download and install those RPMs manually. (2) if this collision problem hasn't been fixed, is there a workaround available where I can refresh those sockets, and anything else that might also need refreshing, such that I don't have to log [joe] out and back in again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org