Using Vine Server 4.0Beta (1109201627) on Mac OS X Server 10.7.2.
Everything is working fine except the System Server when it is started automatically after a reboot instead of a logged in user.
The following errors are logged when I try to connect to the System Server when it was started automatically after a reboot:
Code:
11-10-21 11:02:29.241 AM OSXvnc-server: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
11-10-21 11:02:29.241 AM OSXvnc-server: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
11-10-21 11:02:29.241 AM OSXvnc-server: (ipc/send) invalid destination port: CGSNewConnection cannot get connection port
11-10-21 11:02:29.242 AM OSXvnc-server: (ipc/send) invalid destination port: CGSNewConnection cannot get connection port
11-10-21 11:02:29.242 AM OSXvnc-server: kCGErrorInvalidConnection: CGSGetRegisteredCursorDataSize: Invalid connection
11-10-21 11:02:29.244 AM OSXvnc-server: CGSLookupServerPort: _CGSSessionDeathWatchPort(gSessionPort) returns 268435459
11-10-21 11:02:29.287 AM OSXvnc-server: (ipc/send) invalid destination port: CGSNewConnection cannot get connection port
11-10-21 11:02:29.321 AM OSXvnc-server: (ipc/send) invalid destination port: CGSNewConnection cannot get connection port
11-10-21 11:02:29.327 AM OSXvnc-server: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
11-10-21 11:02:29.345 AM OSXvnc-server: kCGErrorFailure: CGSColorProfileCreateWithColorProfileID: Cannot initialize color profile client
11-10-21 11:02:29.402 AM ReportCrash: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
11-10-21 11:02:29.954 AM com.apple.launchd: (VineServer[2318]) Job appears to have crashed: Bus error: 10
11-10-21 11:02:30.018 AM OSXvnc-server: 3891612: (connectAndCheck) Untrusted apps are not allowed to connect to or launch Window Server before login.
11-10-21 11:02:30.018 AM OSXvnc-server: Window Server is not available.
11-10-21 11:02:30.018 AM OSXvnc-server: Window Server is not available.
11-10-21 11:02:30.019 AM OSXvnc-server: CGSCreateEventSourceState: cannot resolve shmem.
11-10-21 11:02:30.124 AM ReportCrash: Saved crash report for OSXvnc-server[2318] version ??? (???) to /Library/Logs/DiagnosticReports/OSXvnc-server_2011-10-21-110230_localhost.crash
I'm wondering if:
11-10-21 11:02:30.018 AM OSXvnc-server: 3891612: (connectAndCheck) Untrusted apps are not allowed to connect to or launch Window Server before login.
I'm having the same problem as macona and Markus Keller on a Mac Mini running Lion Server. Connecting with RealVNC client, I get RFB protocol error: unknown message type 131. Also with the "connection reset by peer" message in the console. If I restart Vine server, I can connect correctly on the first try. It must always be reset before a connection.
If you are not testing with 10.7 Server, you probably aren't going to track down the issue.
I'm having the same problem as macona and Markus Keller on a Mac Mini running Lion Server. Connecting with RealVNC client, I get RFB protocol error: unknown message type 131. Also with the "connection reset by peer" message in the console. If I restart Vine server, I can connect correctly on the first try. It must always be reset before a connection.
If you are not testing with 10.7 Server, you probably aren't going to track down the issue.
I have this exact same problem with regular Lion 10.7. It has come to the point that I trained myself to run "killall OSXvnc-server" in a terminal on the host instead of simply closing my VNC viewer window. This makes sure I always connect to a fresh VNC server. When I forgot to do this, or I have to reconnect after an unexpected connection drop, I first SSH to the Mac and run that command. It is less hassle than retrying in vain to connect multiple times in a row.
I'm having the same problem as macona and Markus Keller on a Mac Mini running Lion Server. Connecting with RealVNC client, I get RFB protocol error: unknown message type 131. Also with the "connection reset by peer" message in the console. If I restart Vine server, I can connect correctly on the first try. It must always be reset before a connection.
If you are not testing with 10.7 Server, you probably aren't going to track down the issue.
Same problem here. 10.7.3 on the Mac, RealVNC on the client-side.
Joined: 27 Apr 2012 Posts: 8 Location: SF Bay Area, CA
Posted: Fri Apr 27, 2012 3:46 pm Post subject:
Well, add us to the list, too. Sure, it's beta. But it's also been over 7 months. We're in the process of doing an upgrade from a working 10.6.8 environment with Vine 3.1 to a 10.7 environment with 4.0... and this is going to prevent us from finishing it or we'll have to try and find an alternative to Vine.
One interesting data point: The bug doesn't seem to affect all clients equally. So far, I have used:
Linux: TigerVNC 1.1.0
Mac: Screen Sharing (vnc:// URL) in 10.6
Windows: UltraVNC 1.0.9.6.2
Windows: vncviewer 3.3.3 R2 (yeah, OLD)
So far, the only clients that appear affected by the complete inability to connect once this situation occurs are those on Windows. The other clients (Linux and Mac in my case) *can* connect, even if you have to try 2 or 3 times.
Joined: 27 Apr 2012 Posts: 8 Location: SF Bay Area, CA
Posted: Sat Apr 28, 2012 12:47 am Post subject:
Well, after seeing a reference to the new multi-user features of built-in Mac OS X screen sharing in 10.7 -- which had major bugs in earlier releases -- I decided to give it a try in our 10.7.3 environment. OMG! Stunning. I'm not sure what the value add for Vine will be in a 10.7.x world, but for our needs we've now gone directly to screen sharing and aren't looking back.
Well, after seeing a reference to the new multi-user features of built-in Mac OS X screen sharing in 10.7 -- which had major bugs in earlier releases -- I decided to give it a try in our 10.7.3 environment. OMG! Stunning. I'm not sure what the value add for Vine will be in a 10.7.x world, but for our needs we've now gone directly to screen sharing and aren't looking back.
My experience with the built-in screen sharing in Lion is plain horrible. Obeying Apple's ideal of graphical perfection, it does not allow any compression method that degrades the image in any way like JPEG or 8-bit color. This makes it sluggish on slower network connections. Logging in from a Linux or Windows VNC client is almost impossible, it requires far more attempts than with Vine server. And it exhibits the same annoying implicit command-keypress as Vine whenever I type an ‘i’ or ‘r’ in the spotlight search field.
Posted: Thu May 31, 2012 5:47 am Post subject: sent not same as received
Some Keyboard Shortcuts sent from iPad via Vine 4.0 beta are being reinterpreted as different shortcuts. Some are not working at all, or working differently depending on the application. For example Esc will unselect and close dialogs on the QWERTY keyboard, but if sent via iPad, then Esc only unselects, it won't close dialogs. After a reboot it will close dialogs for a while but after a few edits, it ceases to work again.
Space via iPad is opening Spotlight, instead of entering a space char. Shift+Opt+d is not sending anything recognised by the host application, and Esc+Esc+Ctrl+v behaved as though Cmd V had been pressed.
Mac OS 10.7.4 If the Apple VNC is used, none of the inconsistencies are apparent, but the Apple VNC is unusable because it requires you to log out in order to reconnect a dropped server.
The behaviour changes after a reboot and relaunch, but the result is that the characters sent cannot be relied upon to mimic those of the QWERTY keyboard.
All times are GMT - 8 Hours Goto page Previous1, 2, 3, 4
Page 4 of 4
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
Forum Index
Forums FAQ
Search Forums
Memberlist
Usergroups
Register
Your Profile
Log in
