I think this bug report can be closed depending on vinos functionality: Here is probably what happened:
- Somehow I set it to boot automatically into xfce instead of gnome (as the computer is headless, it took me a while to figure it out) - Consequently, vnc did only connect to a gnome session if I opened one remotely through nx (otherwise there was no gnome session running, which one could connect to); thus -- if vino is meant to only connect to the gnome session that has been opened localy, the bug can be closed unless one wants to refine it, so that it does not try to forward other sessions -- if vino should also forward gnome sessions that have been opened from a remote computer, there is a bug in vino because it is under this situation that the problems arise, I have in the meantime managed to make the headless computer again automatically open a gnome session when it is started, and under this situation vino behaves properly. Sorry if I made you waste your time... -- [apport] vino-server crashed with SIGSEGV in g_type_check_class_cast() https://launchpad.net/bugs/91973 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
