Screen sharing bugs?

Hi,
I have several problems with screen sharing:
1. When closing the browser window the "Adobe Acrobat Connect Pro" tab on the bottom is still running.
     When doing it several times I'm getting several tabs. (windows XP, Chrome).
2. It takes several seconds for the screen sharing popup to show which might confuse users.
     Are there events I can use to show and hide a loading indication like "loading screen sharing... please wait"?
     Is it possible that the plugin will show this loading indication?
3. Sometimes the "Start Screen Sharing" popup is displayed behind the browser window.
     This is very confusing for the user that can't guess what to do.
     It might happen if you focus the browser window or some other app, not sure.
4. A user that tries to stop publishing is kicked out of the room.
     I've tried
     sspublisher.stop();
     or
     ss.publsher.stop(cSession.userManager.myUserID)
I'm using latest LCCS SDK and screen sharing plugin with Flash 11.1 under windows XP with chrome.
Thanks

This is a reproducible example for the ScreenSharePublisher.stop() bug.
Win XP, FF9, latest SDK, latest Flash player
You login by calling the swf from javascript with login(roomURL, authToken) or replace it with manual authentication.
Trace messages are shown in FireBug. Replace it with something else if needed.
Click on the button to start screen sharing.
Click on the button again and see that the user gets logged out.
Thanks
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
        xmlns:s="library://ns.adobe.com/flex/spark"
        xmlns:mx="library://ns.adobe.com/flex/mx"
        xmlns:rtc="http://ns.adobe.com/rtc"
        width="600"
        height="700"
        paddingBottom="0"
        paddingTop="0"
        paddingLeft="0"
        paddingRight="0"
        applicationComplete="init()">
  <fx:Script>
    <![CDATA[
        import flash.external.ExternalInterface;
        import com.adobe.rtc.util.DebugUtil;
        [Bindable]
        private var roomURL:String;
        [Bindable]
        private var authToken:String;
        private function init(e:Event = null):void
        removeEventListener(Event.ADDED_TO_STAGE, init);
        DebugUtil.traceFunction = traceMessage;
        ExternalInterface.addCallback("login", login);
        private function traceMessage(message:String):void
        ExternalInterface.call("console.log", message);
        private function login(roomURL:String, authToken:String):void
        this.authToken = authToken;
        this.roomURL = roomURL;
        cSession.login();
        private function onSSClick(event:MouseEvent):void
        if(event.target.selected) {
            event.target.label = "Stop Screen Share" ;
            if(ssPublisher != null && !ssPublisher.isPublishing) {
            ssPublisher.publish();
        } else {
            event.target.label = "Start Screen Share" ;
            if(ssPublisher != null && ssPublisher.isPublishing) {
            ssPublisher.stop();
    ]]>
  </fx:Script>
  <fx:Declarations>
    <!-- Place non-visual elements (e.g., services, value objects) here -->
  </fx:Declarations>
  <fx:Style>
  </fx:Style>
  <rtc:ConnectSessionContainer id="cSession"
                   autoLogin="false"
                   width="600"
                   height="700"
                   roomURL="{roomURL}">
    <rtc:authenticator>
      <rtc:AdobeHSAuthenticator requireRTMFP="true"
                protocol="RTMFP"
                authenticationKey="{authToken}">
      </rtc:AdobeHSAuthenticator>
    </rtc:authenticator>
    <rtc:ScreenSharePublisher id="ssPublisher"/>
    <s:VGroup>
      <s:ToggleButton label="Start Screen Share"
                      click="onSSClick(event)" />
      <rtc:ScreenShareSubscriber width="500" height="500"
                                 showMyStream="false"/>
    </s:VGroup>
  </rtc:ConnectSessionContainer>
</mx:Application>

Similar Messages

  • Screen Sharing bug (erroneously activating Spaces and Dashboard)

    I'm a recent upgrade to Snow Leopard, and also, as it turns out, a complete newbie to Screen Sharing, which generally works quite well.
    My one hitch is that under certain circumstances, the remote machine activates Spaces or Dashboard when I don't want it to. Those circumstances are clicking on one or multiple files, and then attempting to drag them somewhere while holding down the mouse button. For some reason, this problem does not occur while, say, dragging a Finder window around on the desktop.
    I have hot corners for Spaces and Dashboard in the top-right and bottom-left corners of my screen, respectively. However, the accidental activation occurs when my cursor is nowhere near the screen corners. I thought it might have been issue with scaling, but the same problem occurs without scaling. I also have a hot corner in the bottom-right for display sleep, but this never seems to activate accidentally.
    I guess I could disable hot corners, but I'd prefer not to. Any advice would be appreciated.
    Thanks in advance.

    No; my local machine is a MBP and I was only using the trackpad. When I get home I'll check to see if the side buttons are enabled on the remote machine (iMac), but I doubt that's the issue.
    Thanks for your reply.

  • Screen Sharing problem - is it a security problem?

    OK, so I'm having the same screen sharing bug with remote machines.... except when I have my VPN active. Then the remote machines work exactly as normal. With the VPN off, I get the Screen Sharing only error. Anyone who is more familiar with VPNs know what is up?
    Thanks!
    -c

    You may be interested in this helppage<br>
    http://support.mozilla.com/en-US/kb/Is%20my%20Firefox%20problem%20a%20result%20of%20malware<br>
    If you recently had a crash and have sent the crashreport to Mozilla, then you can post a crashreport ID on the forum. Sometimes we can see signs of a virus in the crashreport.

  • Screen Sharing and Hot Corners/expose bug?

    I tried searching but I came up with nothing. I have an iMac and a Macbook. On the iMac I have hot corners set up to use expose. On the bottom left I have it show the desktop and on the bottom right I have it show all windows. Now when I use my macbook to screenshare with my iMac and try to drag a file on the iMac, it activates one of the hot corners even though my mouse cursor is no where near either of the corners. If I deactivate the hot corners, I can drag just fine but I don't want to have to do that every time I use screen sharing. So this is making screen sharing pretty useless. Anyone else have this problem? I just submitted a bug report too.

    I have the same problem. Very annoying.

  • HDMI: Mini - Receiver - TV resolution bugs triggered by Screen Sharing

    Hi all,
    I'm having an issue when connecting my Mini to my Samsung TV when running it through a receiver (Pioneer).  Before we had the receiver in the mix, this issue never came around.  Now that the receiver is involved, I believe this may be an issue related to the "handshake" that I've been reading about when HDMI devices try to connect to eachother.
    What works:
    - If I sit down on the living room couch, turn on the TV, receiver, and Mini, there are no issues.  The resolution is correct.
    - If I leave the TV off, receiver on, boot up the mini, and connect to it via OSX Screen Sharing... I am able to use it as a media center and play music through the mini and receiver, leaving the TV off to save power.
    What doesn't work:
    If I try to switch between "living room" mode (couch / TV) and "Screen Sharing" mode, the resolution gets all fouled up and I need to reboot the mini in order to make it usable.  Here is a screenshot showing how it looks when trying to go from "living room" mode to "Screen Sharing" mode:
    The only way to get out of here is to hold down the power button, forcing the mini to shut off abruptly, then reboot.
    Conversely, if I try to switch from "Screen Sharing" mode to "living room" mode, it's a little different - the top and bottom of the screen is cut off.  Part of the dock is off of the screen, and the menu at the top of the screen is virtually gone.  With this method, I'm actually able to move the mouse off the screen and navigate to "Apple -> Restart" so that it reboots and starts working fine again.
    I've been on the phone with Apple (yes, I have Apple Care) and they pointed me to Pioneer, saying that the mini was receiving instruction from the receiver.  When I called Pioneer, they had me turn off some "HDMI auto detect" features in the receiver but this did not resolve my problem.
    Any suggestions?  Any help would be much appreciated!
    Thanks,
    -Nate

    this is not an elegant solution but here goes.  there may be something in the pioneer that would fix you but here is a solution around the receiver.   plug the computer video into an input on the tv.  if you use hdmi - you will need a separate audio out of the computer to the receiver.  program your remote control so that it switches the audio on the receiver to the separate audio from the mini and program the remote so it switches the tv input to the hdmi.  if you keep the hdmi to the receiver you will need a different video out of the mini to the tv.  its a little complicated but it should work.

  • Why do I need to start up Screen Sharing twice to get it to work ?

    I have an Intel Mac Mini connected to my TV, so I started using Screen Sharing from my MacBook Pro to be able to work on it when others were watching TV.
    Both Macs used to have OSX 10.5 Leopard, and everything worked fine.
    Now they both have OSX 10.6 Snow Leopard, and whenever I startup Screen Sharing, the connection-windows asking for my Name & Password comes up properly, but then it hangs... it stays in "Connecting..." for ever (litteraly).
    I'm not able to quit or force-quit the connection-window by then, so it stays in view...
    (Screen Sharing isn't even listed in the force-quit list as a running app)
    but...
    when I just try Screen Sharing again, I get connection immediately and it seems to work flawlessly...
    ...it's just that the connection-window is impossible to quit...
    it stays in view an is really annoying...
    this looks really crappy...
    can anyone tell me why I do need to startup Screen Sharing twice to get it to work ?
    Is this a bug ?
    (If so : please apple fix this a.s.a.p.)
    ...or am I doing something wrong ?
    (if so : what am I doing wrong ? and how can I get rid of this annoying screen ?)
    Thank you for your kind reply.
    Toon.B

    it's October and this really annoying problem still exists !
    the unnamed screensharing-loginwindow keeps "Connecting...", and I'm unable to shut it down...
    ...even after my screen sharing session is over
    ...even force-quitting is impossible (this 'app' just isn't showing up in the force-quit-window...)
    please Apple - fix this ; under 10.5 it was working great !
    Does anyone have any idea how to fix this ?
    (besides restarting my Mac)
    Thanks !
    Toon.B

  • Ichat Screen Sharing will not work no matter what I try...

    I have read all the forums and can't find an answer. Something that should be so simple such as screen sharing through iChat (as advertised) is virtually impossible. This I can not explain. Especially since video chat works!
    Both computers in question here are macbooks, both have leopard, both are or wireless networks. Is the router blocking the connection and if so, why will it allow video chat but not screen sharing?
    There is either something real simple that I am missing here, or this is not possible at all.
    some things that i have tried:
    disabling stealth mode
    on the firewall, enabling incoming traffic from ichat
    made sure screen sharing is enabled in ichat
    made sure the settings were the same on the remote apple computer
    tried unchecking everything in the sys pref "sharing"
    Both of the parties involved are using the same ISP, this really is mind boggling.
    Is this a bug that is being fixed or what? I am not trying to perform a miracle here, but this is getting ridiculous.
    If this is a router issue, apple should release some documentation on how to configure ichat screen sharing through your router.
    If anyone has had this problem and has a fix, I would love to hear it. Keep in mind I have googled this many times and tried just about every piece of advice that I could find on this.
    Thanks

    iChat Screen sharing does not as such for the screen bit use the Video/Audio port.
    The Documentation was lacking last time I looked.
    This one tells you the port changes in Leopard http://docs.info.apple.com/article.html?artnum=306688 compared to Tiger
    Tiger is linked in the first to here http://docs.info.apple.com/article.html?artnum=93208 where most of the other ports are.
    However Screen sharing was not part of iChat 3.
    If you do a Quick Look at the .plist(s) you will see the reference to ARD which is Apple Remote Desktop which is what the screen ending part is based on.
    This Doc will tell you which ports ARD is likely to use
    http://docs.info.apple.com/article.html?artnum=106439
    (It says 5900 and 5988)
    This should be allowed through the use of UPnP in your routing device or specifically opened.
    Now the not so good news.
    I run Little Snitch, A utility that tells you ports and IPs of incoming and outgoing network connections by any app you have.
    This has told me that in fact the Screen port seems almost completely random normally in the 50000 range of ports
    It may not be all you wnat to hear but I hope it helps.
    9:57 PM Tuesday; February 12, 2008

  • After Lion install screen sharing won't accept my password

    I just updated my *headless* mac-mini to 10.7.  As soon as it rebooted
    Since updating to OS 10.7 on my Mac Mini, I have been unable to log in via Screen Sharing (using my 10.7 installed Mac Pro).  I continually receive the error "Authenticaion failed to 'MacMini'. Please verify you have entered the correct name and password."  The name and password are correct, and the mac-mini lets me "Connect As ..." with the username and password.  Only the Screen Sharing application fails to authenticate.  I had no troubles  an hour ago when it had Snow Leopard installed.
    Any solution before I have to travel to this mini?
    Thanks,
    Jim

    My family has multiple Macs at home and I also help a friend at a remote location.  What is weird, is I was able to do screen sharing with the Mac at the remote location and a couple at home, but was not able to get screen sharing to work on the majority of our Macs at home.  Rebooting did not help.  Deleting my user login and corresponding home folder (then rebooting) and recreating a new user under the same login name that was deleted did not help.  Repairing permissions in Disk Utility did not help.  I did not try creating a user under a totally different login name and setting up screen sharing to share with that user name.  I was going to try that this morning.  However, on another thread, someone offered another thing to try.  I tried it and it worked.
    This is what eventually worked for me...  This work around seems to expose that there is definitely a bug:
    https://discussions.apple.com/message/15812668#15812668
    Quote from andifor:
    "Full name and account name on my computers are also the same.
    But I did some deviation last time I tried. I changed my name on the connection dialog. I changed the name from "user" to "uSer" (changed one letter to capital) and it did work!
    So if you login name is "peter", change it to "pEter" or "peTer", just on the login screen.
    Looks more and more like a bug and only Apple can help. Does anybody know, if they are monitoring these discussions or is there a possibility to log some bug report?"

  • Screen Sharing / vnc with OS X 10.5.6 fails

    I can not get the Screen Sharing that comes with OS X 10.5.6 to work with any vnc client. The server is my laptop, an MBP 2.4 GHz Intel running OS X 10.5.6.
    *I enable Screen Sharing by doing the following:*
    1) +System Preferences > Sharing > Screen Sharing+ is checked
    2) +System Preferences > Sharing > Screen Sharing > Computer Settings > Anyone may request permission to control screen+ is checked
    3) +System Preferences > Sharing > Screen Sharing > Computer Settings > VNC viewers may control screen with password+ is checked and I've entered a password
    4) I also have Remote Login enabled for SSH access, but no other services are enabled.
    *I see two different behaviors depending on one of two clients that I try using:*
    1) +Chicken of the VNC v2.0b4+ running on same machine- Always says "Connection Terminated / Authentication Failed" without ever asking for a password. Logs the following in system.log (dates, hostnames and pids removed):
    Chicken of the VNC: Server reports Version RFB 003.889
    Chicken of the VNC: Bogus RFB Protocol Version Number from AppleRemoteDesktop, switching to protocol 003.007
    I believe that the information in system.log is OK, and is just warning me that Chicken of the VNC is working around Apple's strange protocol version.
    2) +TightVNC 1.3.9 on Windows XP sp2+- Says "Security type requested", then asks for a password. I enter it, click OK and tightvnc simply waits endlessly.
    *Other Notes:*
    1) I have tried configuring and starting the server using kickstart from the command line as suggested at http://support.apple.com/kb/HT2370 (+sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -activate -configure -access -on -restart -agent -privs -all+)
    2) I have tried unchecking +VNC viewers may control screen with password+, but in this case Chicken of the VNC says "Please configure Apple Remote Desktop to allow VNC Viewers to control the screen. Unknown authType 30,31,32" and TightVNC says "Server did not offer supported security type!"
    3) If I disable the Screen Sharing feature that comes out of the box with OS X, I CAN install and successfully run the OSXVnc server available at http://sourceforge.net/projects/osxvnc/. In this case, both Chicken of the VNC and TightVNC are able to connect.
    *So Apple's Screen Sharing does not work. Does anyone know what the problem is? Are there any log files I can look at, or is there another way I can debug this? I'm not impressed. :)*

    Thanks for the suggestion. It was possible that one of these files had become corrupted, so I tried moving each of these files to another directory but unfortunately I'm still seeing the same behavior.
    Here's what happens with each of these files individually after they're moved:
    1) When I set the VNC password in the system prefs, com.apple.VNCSettings.txt gets re-created (with the same contents as the original unless I change the password, so that just looks like a hash of the password).
    2) com.apple.RemoteManagement.plist also gets recreated when I change the system prefs. If I use "sudo plutil -convert xml1 com.apple.RemoteManagement.plist" I get the following:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>ARD_AllLocalUsers</key>
    <true/>
    <key>ARD_AllLocalUsersPrivs</key>
    <integer>2</integer>
    <key>ScreenSharingReqPermEnabled</key>
    <true/>
    <key>VNCLegacyConnectionsEnabled</key>
    <true/>
    </dict>
    </plist>
    3) For me, com.apple.RemoteDesktop.plist does not exist.
    4) Interestingly, com.apple.ARDAgent.plist does not get created until I run "sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -activate -configure -access -on -restart -agent -privs -all". Its XML contents are as follows:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>AdminConnectInfoList</key>
    <dict/>
    <key>AgentLogLevel</key>
    <integer>3</integer>
    <key>ServerConnectInfoList</key>
    <dict/>
    <key>Version</key>
    <real>3</real>
    </dict>
    </plist>
    Looking at this, I tried setting ScreenSharingReqPermEnabled to false, but that didn't help. Then I increased AgentLogLevel to 100 and got a lot of output in system.log (12:28:45 is when I restart the server and 12:29:34 is when I try to connect):
    Feb 24 12:28:45 ARDAgent [749]: ******ARDAgent Launched******
    Feb 24 12:28:45 ARDAgent [749]: got a sessionDict, onConsoleRef is 0xa04cd400
    Feb 24 12:28:45 ARDAgent [749]: grUserOnConsole is 1
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 122
    Feb 24 12:28:45 ARDAgent [749]: LoadMenuExtra: Attempting to unload menu extra
    Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Going to send notifation value 9
    Feb 24 12:28:45 ARDAgent [749]: UpdatePrefs: versionFlt : 0.000000 kCurrentPrefsVersion : 3.000000
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 44
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 22
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 100
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 94
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 96
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 18
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 106
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 74
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 130
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 60
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 45
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 65
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 66
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 105
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 115
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 38
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 12
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 61
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 20
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 62
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 39
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 30
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 101
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 53
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 103
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 107
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 109
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 135
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 41
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 110
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 111
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 28
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 36
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 48
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 59
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 57
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 116
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 58
    Feb 24 12:28:45 ARDAgent [749]: InitAppUsageHandlers: Called gTrackingDays is set to 0
    Feb 24 12:28:45 ARDAgent [749]: CheckRFBServerPIDFile: return 679
    Feb 24 12:28:45 ARDAgent [749]: RemoteCommandListenerThread init communications
    Feb 24 12:28:45 ARDAgent [749]: RFBServerStart - did not kill 679
    Feb 24 12:28:45 ARDAgent [749]: DOCStartDOC: No serial number. Task Server not started.
    Feb 24 12:28:45 ARDAgent [749]: DT_InitLocalProcessing: Loading existing tasks from disk.
    Feb 24 12:28:45 ARDAgent [749]: DT_InitLocalProcessing: Found 0 tasks
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 158
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 117
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 118
    Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 162
    Feb 24 12:28:45 ARDAgent [749]: ARD Agent: RFB Server exited quickly after starting - probable failure.
    Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Going to send notifation value 6
    Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Setting lastNotification to value 6
    Feb 24 12:28:45 ARDAgent [749]: ******ARDAgent Ready******
    Feb 24 12:29:34 Chicken of the VNC[693]: Server reports Version RFB 003.889
    Feb 24 12:29:34 Chicken of the VNC[693]: Bogus RFB Protocol Version Number from AppleRemoteDesktop, switching to protocol 003.007
    Feb 24 12:29:36 ARDAgent [749]: PostNotificationForced: Going to send notifation value 1
    Feb 24 12:29:36 ARDAgent [749]: PostNotificationForced: Got request for kCurrentStateNotification. Sending value 6
    Interesting that it says "ARD Agent: RFB Server exited quickly after starting - probable failure." That doesn't sound too good.
    I will try to watch fs_usage more closely to see what else gets modified and accessed, but I'm increasingly suspicious that there's simply a bug which is showing up under whatever specific conditions I have on my machine. Perhaps the included log info will trigger an idea for someone.

  • Screen sharing Macbook/Mac Mini - typed letters do not match

    I'm runnung a Mac Mini and a Macbook with network. Both have Leopard 10.5.5 and German localisation with German keyboard layout. When screen sharing and typing a "z" on Macbook, Mac Mini shows a "y"; it seems to be the English keyboard layout.
    When typing the same on the Mac Mini's Alu-Keyboard (German layout), the letters appear as typed.
    What's the bug?
    Thanks

    You need Leopard and iChat 4 to work with Shinywhitebox's[Chatter|http://www.shinywhitebox.com/chatter/chatter.html]

  • Slow cursor during screen sharing

    Hello,
    Running Mavericks on both my 2009 MBP and 2012 2.5 it Mac Mini- I am noticing that the cursor is sluggish- up to the point where I can swirl it around on my trackpad from my MBP- and the controlled Mac Mini lags behind up to 20 seconds.  I have not seen this prior to Mavericks so I am guessing it is a bug (even running a fan control app to see if cooling the Mac Mini which is mounted in a gator rack case but with ample circulation is causing the issues).
    I am wondering if anyone else has experienced this.  I am running an external Thunderboth to VGA display (and have even tried connecting via HDMI).  Normally I use the hdmi headless dongle for live music use and don't notice the issue (but am not using the trackpad much as I have MainStage controlled via my controller).
    Any other suggestions

    Only the screen content is being shared during screen sharing. Audio sharing is currently not part of the functionality.
    What's a use case you can see for transferring audio as well?
    Follow the latest Skype Community News
    ↓ Did my reply answer your question? Accept it as a solution to help others, Thanks. ↓

  • Screen Sharing Spinning Connection

    I have been using Screen Sharing to access a headless Mac Mini. The screen sharing portion works fine, but something in the Finder throws up a dialog asking me to:
    "Enter the name and password to share the screen of the: name of Mac Mini""
    I put in the correct information and the dialog box goes into spin cycle, with the words in the lower left corner: Connecting ...
    Since it never connects this dialog box is left on the screen and there is no way to get rid of it - the Cancel & Connect buttons are dimmed. Very frustrating ...
    Does anyone have any idea what's happening here, and how to avoid this is the future?
    Screen Sharing in working fine.
    Thanks

    This seems to be a HUGE bug that has been around for ages - I found at lest one thread of people complaining about this over a year ago!
    Screen sharing usually works ok for me but this lingering login window is a real bust!
    You can get the window to go away by logging off or pulling up activity monitor and killing "NetAuthAgent"

  • Will Mountain Lion fix the major Internet Sharing bug in Lion?

    Does anyone know if Apple have indicated that they will be issuing a fix to the Internet Sharing bug in Lion (i.e. Internet Sharing does not work) in the new Mountain Lion?

    Hmmm. Pete, suggest cease dissing people's problem with VNC in Mt Lion as "doesn't exist here" syndrome. Maybe for you, it's working just fine....for some of us...NOT.
    Following several threads on issues with VNC and Lion and the vague hope that Mt Lion would fix the problem, I also upgraded to Mt Lion. Worse.
    Prior to Lion, VNC worked every time with any Mac I tried, inside or outside the local network. With Lion, VNC worked correctly until around 10.7.4, then with intermittent connections (requiring restarts on the target Mac in order to connect a second time).
    Now, with Mt Lion (target Mac is still on Lion and restarted), I cannot connect externally to the Lion Mac even with it being restarted (and Screen Sharing and Remote Management turned off/on as one thread suggested).
    As another thread suggested, I had deleted the iCloud System Pref on both Macs while on Lion (with no effect to VNC).
    While I'm sure there's a solution out there, I have yet to find it.
    Thanks for any suggestions, but will someone at Apple please address this issue?

  • Screen sharing connect dialog hung

    last nite i tried 2 connect 2 a m.b.pro (running 10.6.8) over wifi from my 10.7.4 m.b.pro. it was still spinning when i closed up 4 the nite, and now this morning the dialog is still spinning, and even when selected, the dialog's cancel button is disabled...see attached screengrab:
    also note that even tho the dialog is selected, the menubar still shows the previous f/g app (ffx as i type this msg;-) so i don't even kow what process 2 kill;-\
    perhaps i should file a bug report, but i'll have 2 figure out again where apple hides that;-\
    also note that i am able 2 screen share no problem w/ my 10.6.8 minimac (ethernetted to the wifi router) so the only difference is wifi2wifi...nope: i just tried s.s'ing from the minimac to the problem m.b. (via s.s from my m.b.) and got the same hung dialog:
    bouncing screen sharing doesn't help, but bouncing finder allowed s.s. to finally go thru, but the dialog is still there:-( now  i got 2 machines w/zombie dialogs:-P

    No, not looking to disable Screen Sharing, just to clear the dialog box (it floats above all other windows) without restarting.
    Found this post that resolves the issue:
    "This happens to me often if I have a problem connecting a remote computer -- those connecting windows just never go away if they hang. The issue is that NetAuthAgent is hanging. To get rid of these without rebooting:
    From GUI:
    1. Launch the Activity Monitor program.
    2. In the Process Name list, look for "NetAuthAgent". It may show as "Not Responding".
    3. Select NetAuthAgent, and then click Quit Process (the red stop sign button at the top of the Activity Monitor window). Then, click Force Quit.
    From Terminial:
    1. ps ax | grep NetAuthAgent
    2. kill <pid-of-the-process-found-above>
    This should get rid of the dialog boxes and the hung process, and VNC/Screen Sharing should continue to work, as it will launch NetAuthAgent again when it needs it."
    This did just what I was looking to do!

  • Screen sharing not exactly the same as the host computer's screen

    Hi all
    I am using a mac mini as a media server connected via HDMI to my big TV downstairs.  I am using screen sharing from my macbook air to do little tasks while not downstairs.  This has been a very good setup.
    One thing I wanted to do is maintain my iphoto library - going through old albums, confirming faces, red-eye etc.  whatever.
    Using screen sharing works for this, mostly.
    When I choose a photo and click "edit", my TV downstairs shows the photo fine, but my screen sharing on my laptop shows nothing but black where the photo should be.  When I zoom in, I see the navigator window appear (with the image) but I do not see the photo itself.  I am including a screenshot.  Note how at the bottom, you can see images, and in the zoom window you can see that there is an image there, but the image field itself is empty.  On my TV I can see the image (a squirrel, as it turns out).
    Others I have talked to about this claim that some video sources do not "play well" with screen sharing and/or VNC. I haven't encountered these things but I do recall old versions of windows would only display a movie on one of two screens, even when the screens were mirrored (a big pain for presentations if I recall)
    Hoping that this is a bug in screen sharing that apple can fix?  anyone else have this problem? anyone else can try this and confirm? 
    The mac mini isn't running Lion yet but the macbook air is.  Other than that all software etc is up to date. 
    I tried screen sharing on an older laptop running the same os as the mini (snow leopard) and the same thing happens, so it isn't a problem running between 10.6 and 10.7.

    I saw similar problems.  Please see my Aug 21 post on vnc at https://discussions.apple.com/thread/3267893

Maybe you are looking for

  • Not able to display error message in PR creation.

    HI Experts, In PR creation process i am not able to display error message. BADI: ME_PROCESS_REQ_CUST method : PROCESS_ACCOUNT, PROCESS_ITEM I have used Include mm_messages_mac for handling error . MESSAGE e112(XXX) WITH XX-XX. this is my error messag

  • Consingment process for Brazil using item category K

    Colleagues, I found in SAP Help this document describing the use of item category K for Brazil environment. This document shows the use of the item category together the brazilian movement 821, tax codes K5/K6 and notas fiscais. http://help.sap.com/b

  • Purchase and download

    I just started using Itunes again after a very long time. I don't know how to purchase and add to my ipod. I added songs to a wish list and thought at that point I would have an options to purchase. Can't seem to figure it out.

  • Problems deleteting PCD-objects at level 9

    Hi Recently our PCD-structure have gotten deeper. Our PCD-structure starts with the folder "Portal Content" at level 1. As a result of the structure getting deeper, I am experiencing problems with deleting PCD-objects, iViews or pages, at level 9. Wh

  • Wont charge

    Ok so I have reset everything i can think of on my powerbook but nothing seems to get it to charge. I orderd a new battery i am hoping that will fix it. if i push down on the power cord it will turn orange but still wont charge.. please help