Vine 4.0Beta for Mac OS X 10.6 and 10.7

EggplantMattEggplantMatt ForumAdmin admin
We've posted a beta of Vine 4.0, which provides compatibility with Mac OS X 10.7 (Lion). It will also work on OS X 10.6, but not on versions of the OS prior to that. Aside from the compatibility issue, the new server offers the same functionality as Vine 3.12. You can get the Beta from our downloads page. Please respond here with any feedback.
«1

Comments

  • I tried Vine Server 4.0Beta with Vine Viewer under Lion 10.7.1 on both sides. It is great, but I noticed one thing: prefix keys such as control, option, command, etc. seems to stick on the server. It happens very often and I need to restart the server or send the prefix again.
    I have tried all combinations of event handling, but no effect.
  • This issue of wrong prefix keys occurs every time at a reconnection. At the first connection after restarting the server is fine.
  • xorxor Member
    Thanks for the beta!

    However, there is an issue when the Mac Mini 2011 (Lion) goes to sleep and is then woken up with a WOL packet: in this case, the Mac Mini's physical screen stays black and Vine VNC appears to be frozen (just comes back with the screen before the Mac went to sleep).

    This issue was also present in Real VNC and has recently been fixed there. In fact, if you connect to a Real VNC server installed on the same machine alongside the Vine VNC server, then the VNC server will also come back to life.
  • The Server beta runs ok in my iMac. However the Vine client on my macbook only displays grey - anything I am missing?
  • EggplantMattEggplantMatt ForumAdmin admin
    Sounds like you may be connecting to the built-in screen-sharing server. Make sure that you've disabled screen sharing in System Preferences > Sharing.
  • Thanks. Working now (internal network). Will test remotely tomorrow.
  • I have the Vine Server running on my Mac Mini (2009). I've recently upgraded to Lion and have run into an issue. I can connect to the Vine Server using Mocha VNC on my iPhone 4 and iPad2 along with all my windows machines in the house via RealVNC client.

    When I try to connect using my MacBook Pro, it times out. I've tried using the RealVNC client for MAC, Chicken of the VNC, and the Vine Client. Each ones times out on connecting.

    I haven't made any changes to my MacBook Pro during the Lion upgrade to the Mac Mini.
  • My config:
    iMac with latest Lion update and Vine Server 4.0beta. Vine Server is configured to start in system server mode. No user server is running.

    Client computer is Win 7 x64 connecting with UltraVNC 1.0.9.6.1.

    When I attempt to connect, the window opens and immediately closes. If I choose the "Ultra" speed setting, the window stays open a fraction of a second longer, enough to see the actual host desktop. All others from Auto down to slow close too fast to see anything but a black/grey window that disappears immediately. On the Mac, the log looks like this:
    Oct 18 23:05:07 elle OSXvnc-server[14010]: Protocol version 3.8
    Oct 18 23:05:10 elle OSXvnc-server[14010]: Pixel format for client 192.168.2.7:
    Oct 18 23:05:10 elle OSXvnc-server[14010]:   32 bpp, depth 24, little endian
    Oct 18 23:05:10 elle OSXvnc-server[14010]:   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
    Oct 18 23:05:10 elle OSXvnc-server[14010]: ENCODING: ZRLE for client 192.168.2.7
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Unknown Encoding Type(ignored): 17 (11)
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Unknown Encoding Type(ignored): 10 (A)
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	ULTRA Encoding not supported(ignored): 9 (9)
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Using compression level 6 for client 192.168.2.7
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Enabling Cursor Shape protocol extension for client 192.168.2.7
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Enabling Cursor Position protocol extension for client 192.168.2.7
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Using jpeg image quality level 6 for client 192.168.2.7
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Unknown Encoding Type(ignored): 4294901766 (FFFF0006)
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Enabling LastRect protocol extension for client 192.168.2.7
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Enabling Dynamic Desktop Sizing for client 192.168.2.7
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Unknown Encoding Type(ignored): 4294901761 (FFFF0001)
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Unknown Encoding Type(ignored): 4294934528 (FFFF8000)
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Unknown Encoding Type(ignored): 4294934529 (FFFF8001)
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Unknown Encoding Type(ignored): 4294934530 (FFFF8002)
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Unknown Encoding Type(ignored): 4294934531 (FFFF8003)
    Oct 18 23:05:10 elle OSXvnc-server[14010]: 	Unknown Encoding Type(ignored): 3231835598 (C0A1E5CE)
    Oct 18 23:05:10 elle OSXvnc-server[14010]: Client Connected - Registering Screen Update Notification
    Oct 18 23:05:10 elle OSXvnc-server[14010]: rfbSendUpdateBuf: write: Bad file descriptor
    Oct 18 23:05:10 elle OSXvnc-server[14010]: Client 192.168.2.7 disconnected
    Oct 18 23:05:10 elle OSXvnc-server[14010]: Statistics:
    Oct 18 23:05:10 elle OSXvnc-server[14010]:   key events received 0, pointer events 1
    Oct 18 23:05:10 elle OSXvnc-server[14010]:   framebuffer updates 1, rectangles 2, bytes 1044716
    Oct 18 23:05:10 elle OSXvnc-server[14010]:     Cursor Shape Updates rectangles 1, bytes 1068
    Oct 18 23:05:10 elle OSXvnc-server[14010]:     ZRLE rectangles 1, bytes 1043648
    Oct 18 23:05:10 elle OSXvnc-server[14010]:   raw bytes equivalent 14745612, compression ratio 14.114469
    Oct 18 23:05:10 elle OSXvnc-server[14010]: UnRegistering Screen Update Notification - waiting for clients
    

    Obviously there's an error in there with rfbSendUpdateBuf. On the Mac, if I kill the OSXvnc-server process I see a new one immediately start. Then I am able to connect 2-3 times in a row with no problems before the rfbSendUpdateBuf error occurs again. Restart server, it's fixed again for a few tries. Obviously I'd like it to work on every try without having to physically access the target machine first, which defeats the purpose of VNC. Is there anything else I can try?
  • I am using four iMac's which are running Lion and Vine Server 4.0 Beta.
    Three of the iMacs use Quad-Core i7 processors.
    One of the iMacs use a Core 2 Duo.
    Built-in screen sharing is disabled on all four Macs.
    These four Macs reside at four independent locations.
    Three of them reside in the same city.
    The fourth resides two-hundred miles away.
    Two of the Macs use high speed connections (20Mbps / 8Mbps).
    Two of the Macs use slower speed Internet connections (2.4Mbps / 1.5Mbps (the other city) ).
    I use the JollysFastVNC client on all four Macs.
    I use Mocha VNC on my iPhone.

    I confirm KatsOide's experience with sticking modifier keys. This problem is very persistent on all four remote Macs and all four local Macs in all connection combinations.

    I confirm xor's experience with connecting to a sleeping Mac. During the first ten days after I installed Lion and Vine Server 4.0 Beta on all four Macs, the problem that I experienced while attempting to connect to sleeping Macs, only occurred on the two Macs that used the slower speed Internet connections. I did not experience the problem on the two Macs that used the higher speed connections. This morning, the eleventh day, I can not establish a VNC connection to the Mac that uses the 20Mbps Internet connection. Yet, I can now establish a VNC connection to the Mac that uses the 1.5Mbps Internet connection (two-hundred miles away).

    Vine's is the finest VNC server that I have ever used on any platform. TightVNC takes a close second place. I read that Apple deprecated some APIs in Lion that Vine depended on. Please don't let this dissuade you from continuing to develop such a fine product.

    Kurt Todoroff

    Markets, not mandates and mob rule.
    Consent, not coercion.
  • Traveling at the moment. I can connect to my iMac from my MacBook. iMac is running the beta. I can use the mouse, but not the keyboard. Any setting I am missing?
  • EggplantMattEggplantMatt ForumAdmin admin
    If you have the mouse working, try restarting Vine Server. There's some problem that we haven't been able to track down yet where the keyboard stops working, but restarting the server usually restores it.
  • Hi - I'm wondering if the reverse connection functionality has been implemented in this Beta. When initiating reverse connection from 10.6 and 10.7 machines with Beta 4, there's no connection, but with older Vine Server 3.12 on the same machine (at least on 10.6), it works fine.
  • doomedtx wrote:
    <snip>On the Mac, the log looks like this:
    <snip>
    Oct 18 23:05:10 elle OSXvnc-server[14010]: rfbSendUpdateBuf: write: Bad file descriptor
    
    <snip>

    Bumping my own question from almost 2 months ago since I haven't seen any sort of reply. Is anyone else experiencing this error, and is there a solution? The full post is on page 1 of this thread.
  • I was wondering if there was a chance to update Vine Viewer as well. My biggest request would be to update full screen mode to Lion.

    thanks.
  • doomedtx wrote:
    doomedtx wrote:
    <snip>On the Mac, the log looks like this:
    <snip>
    Oct 18 23:05:10 elle OSXvnc-server[14010]: rfbSendUpdateBuf: write: Bad file descriptor
    
    <snip>

    Bumping my own question from almost 2 months ago since I haven't seen any sort of reply. Is anyone else experiencing this error, and is there a solution? The full post is on page 1 of this thread.

    I have the exact same issue. Have to ssh in and kill and restart the server, which is annoying. The old version (3.12) used to do it sometimes as well (window would pop-up for a fraction of a second and close), but would succeed after 2-3 re-tries. In the new version, multiple re-tries do not work and the server needs to be killed.
  • alik55 wrote:
    doomedtx wrote:
    doomedtx wrote:
    <snip>On the Mac, the log looks like this:
    <snip>
    Oct 18 23:05:10 elle OSXvnc-server[14010]: rfbSendUpdateBuf: write: Bad file descriptor
    
    <snip>

    Bumping my own question from almost 2 months ago since I haven't seen any sort of reply. Is anyone else experiencing this error, and is there a solution? The full post is on page 1 of this thread.

    I have the exact same issue. Have to ssh in and kill and restart the server, which is annoying. The old version (3.12) used to do it sometimes as well (window would pop-up for a fraction of a second and close), but would succeed after 2-3 re-tries. In the new version, multiple re-tries do not work and the server needs to be killed.

    I am encountering the same problem. I connect from the RealVNC client on Windows, and the error I encounter is "unknown message type".
  • Isarian wrote:
    alik55 wrote:
    doomedtx wrote:
    doomedtx wrote:
    <snip>On the Mac, the log looks like this:
    <snip>
    Oct 18 23:05:10 elle OSXvnc-server[14010]: rfbSendUpdateBuf: write: Bad file descriptor
    
    <snip>

    Bumping my own question from almost 2 months ago since I haven't seen any sort of reply. Is anyone else experiencing this error, and is there a solution? The full post is on page 1 of this thread.

    I have the exact same issue. Have to ssh in and kill and restart the server, which is annoying. The old version (3.12) used to do it sometimes as well (window would pop-up for a fraction of a second and close), but would succeed after 2-3 re-tries. In the new version, multiple re-tries do not work and the server needs to be killed.

    I am encountering the same problem. I connect from the RealVNC client on Windows, and the error I encounter is "unknown message type".
    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)
      [/list:u]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.

      Why? No clue. But it is the pattern we've seen.
  • 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.
  • I am finding different results if I change the order of modifier keys. For example Alt (=Apple Cmd) seems to work better if placed at the start of the string, and Shift should not be placed just before an alphabetic character or it gets ignored.

    Also Esc is not working consistently with the equivalent QWERTY Esc. It unselects objects and closes edit fields ok, but it doesn't activate Cancel buttons in dialogs like the QWERTY Esc does.

    Another key that is not working on Mac is the TAB key. Zero response.

    All these keys work perfectly using the built in Mac VNC, but unfortunately, hence why i am trying Vine, if there is any interruption to the handshake, then I have to log out and log in again - a death sentence in a recording studio where samples can take up to an hour to reload.

    I bought the iPad solely to use as a VNC controller, and so far it has been a Gargantuan waste of both time and money.

    If this cannot be made to work with either Vine or Apple OS, does anyone know of another VNC Server, or perhaps whether these issues are acknowledged by the Vine developers and perhaps fixable?
  • Installed v4 (non-beta, on 10.7.4) - still the same issue - disconnects on subsequent connects. Starting from v4beta Vine was unusable until I put this line in my ~/.profile:
    alias rvnc='killall 9 "Vine Server";osascript -e "tell app \"Vine Server\" to launch"'

    I connect to VNC over ssh tunnel, so need to ssh in anyway, this way the first thing I do after logging in is type rvnc and then I can connect no problem.
Sign In or Register to comment.