This may not be exactly the same problem as others are having...but hopefully someone can suggest a solution. I too have found that adding -extension XFIXES with the latest version of the binary fixes the immediate disconnection problem - just the same as backdating to an older version of the binary.
However...when I'm presented with a login prompt...a correct ID and password yield....nothing - an immediate return to the login prompt. The syslog yields the following: warning: can't get client address: Transport endpoint is not connected VNC worked perfectly for me under Edgy with the backdated binary, but this started as soon as I did a repository upgrade to Feisty. Now that the server binary is working properly, can anyone suggest what else might cause this error? Thanks, -- vnc4server does not start Desktop environment after security update https://bugs.launchpad.net/bugs/78282 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
