gnome-shell currently refuses to start without hardware acceleration, but I forced it on with the new llvmpipe on Fedora 15 and the performance was quite adequate. There were a bunch of graphics bugs, but those could be Xvnc issues. It might be worthwhile to fix up the final things so that we can offer gnome-shell to our users. Upstream is probably not going to bother.
It should now work fine with the latest llvmpipe: http://www.happyassassin.net/2011/11/03/fedora-16-is-gold-but-more-importantly/
More info: http://lists.fedoraproject.org/pipermail/devel/2011-November/158976.html https://fedoraproject.org/wiki/Features/Gnome_shell_software_rendering
When GNOME Shell runs fine, we should probably also add a separate profile for it. (This was earlier part of bug 4226.)
*** Bug 4292 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > It should now work fine with the latest llvmpipe: Should, but doesn't (F17). It seems that mutter has some problem starting on our Xvnc. See https://bugzilla.redhat.com/show_bug.cgi?id=836565
See also https://bugzilla.redhat.com/show_bug.cgi?id=896648
Works like a charm with our new upgraded Xvnc! Tested on Fedora 18. Performance is surprisingly good.
Broken in Fedora 19 Alpha: https://bugzilla.redhat.com/show_bug.cgi?id=959941
(In reply to comment #8) > Broken in Fedora 19 Alpha: > > https://bugzilla.redhat.com/show_bug.cgi?id=959941 Reopening bug as this seems to be partly our fault. gnome-shell crashes when it tries to retrieve the current session (a systemd thing). It expects the environment variable XDG_SESSION_ID to be set, but it is not in ThinLinc. This is supposed to be set by pam_systemd.so. The reason it fails is because PAM has a convoluted way of changing the environment, and tl-session isn't handling this.
As a side note, the above could also explain why the locking screen didn't work right in Fedora 18.
(In reply to comment #9) > gnome-shell crashes when it tries to retrieve the current session (a systemd > thing). It expects the environment variable XDG_SESSION_ID to be set, but it is > not in ThinLinc. This is supposed to be set by pam_systemd.so. The reason it > fails is because PAM has a convoluted way of changing the environment, and > tl-session isn't handling this. Fixed in r27317.
*** Bug 4644 has been marked as a duplicate of this bug. ***
Works like a charm on Ubuntu 13.04 (see bug #4644). Closing.