Andrei Borzenkov wrote:

Linda Walsh <suse@tlinx.org> пишет:

...

What should it be set to?

bor@opensuse:~> echo $XDG_RUNTIME_DIR /run/user/501 bor@opensuse:~> su - root -c 'echo $XDG_RUNTIME_DIR' Пароль: /run/user/0

...

Mine has always been empty and it seems most programs don't a consistent, standard value for such.

I don't know if anyone would know the answer to this, but if 'X' DesktopGraphical[?]_RuntimeDir is running on a remote "v." local How would that be specified? I.e. -- not *real sure* where this is used, but say I click on a help link in some program that is displaying on my "Desktop" (as pointed to by "DISPLAY"), so prog is running on server and displaying on another machine that is optimized for displaying. A click on help in prog tries to take you to some URL on the web -- so it sends a message to the Desktop manager to open the URL in the desktop's "selected" browser. Usually, for most purposes, I prefer the web browser executing locally on the display computer -- same with email. How would someone configure where they would like the message to be handled? I.e. similar to choosing what browser you want to handle your URL's, is there a place to tell it to dispatch that message to a different machine? NOTE: I would think this especially important if people are connecting to apps in the 'cloud', that might have high-compute ability, but less good graphical interactivity -- and might wish for basic functions to be provided from local programs. I'd guess this is being thought about "somewhere", in the same way static-content is being optimized to come from caches nearer to the requester than always coming from the cloud-app's host. It seems this would also apply to 'dbus', and is 'theoretically' possible, but haven't heard of anyone who "knows" how to configure it, actually doing so nor anyone verifying that this really works (I've tried a few variations, but never hit a working combo...). ---- BTW -- so if a display is at someone's home, and they are running a compute app in the cloud, where is the all important "seat"? I.e do they need a seat for each remote machine (seems excessive), but where is this seat stuff going? How is it different than group or site license managers that keep track of how many concurrent licenses are being used at any given point? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org