<p>That's true, using freenx to access a whole desktop works well with xfce and no sound. I can't imagine it working so well if trying to run gnome-shell, sound etc remotely. </p>
<p>I get the impression a lot of the current desktop infrastructure doesn't make sense when accessed remotely, eg if I ssh'ed into a machine what could I usefully do with nm-applet or a lot of other desktop infrastructure? A lot of the desktop is already beyond the reach of X.</p>
<p><blockquote type="cite">On 9 Nov 2010 22:26, "Lennart Poettering" <<a href="mailto:mzerqung@0pointer.de">mzerqung@0pointer.de</a>> wrote:<br><br><p><font color="#500050">On Tue, 09.11.10 23:14, Miloslav Trmač (<a href="mailto:mitr@volny.cz">mitr@volny.cz</a>) wrote:<br>
<br>> Lennart Poettering píše v Út 09. 11...</font></p>Oh, of course you can blame X for that. There's simply no sane way how<br>
to get a "parallel" connection for D-Bus/GConf/ICE/PA/whatever to the<br>
main X11 display connection. Something like that has been tried a number<br>
of times, but in some way or the other it just failed in the end. It's a<br>
can of worms. Really, for example in the GConf case I know that Havoc<br>
spent quite some time to design the IPC so that it could be used<br>
alongside X11 on the network, but eventually gave up on it.<br>
<br>
I think it is fundamentally wrong to ask us to support setups where you<br>
might or might not share $HOME, might or might not share the D-Bus<br>
session bus, might or might not share the D-Bus system bus, might or<br>
might not share PA, might or might not share GConf, might or might not<br>
share X11 displays, in all combinations over the network at all times.<br>
<br>
Complete flexibility like that is not only impossible to manage or test,<br>
but also inherently slow. For example: if you say the D-Bus bus should<br>
be shared across the network, but $HOME shouldn't, then applications<br>
could not refer to files anymore in the bus protocols, which would<br>
basically require them to pipe everything through a bus, which is a<br>
textbook example how to make things slow. Of course, it's easy to assume<br>
that all the building blocks we build our desktop off would be<br>
completely independent black boxes, but turns they aren't, and are<br>
deeply integrated these days.<br>
<br>
The pixel-scraping approach is the only thing that in the end makes<br>
sense, since you have a very clear idea of what you share, and what you<br>
don't share, and what you share is only at the very very end of what you<br>
do, i.e. the last step of presentation of the app to the user.<br>
<p><font color="#500050"><br>Lennart<br><br>-- <br>Lennart Poettering - Red Hat, Inc.<br>-- </font></p><p><font color="#500050">devel mailing list<br><a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/de.">https://admin.fedoraproject.org/mailman/listinfo/de.</a>..</font></p></blockquote></p>