Screen Sharing issues with ML and SL with dual displays??

Don't know if this is a ML issue or was present in Lion (which I never upgraded to)
Setup...
Old setup was 2010ish MBP and only 2006 iMac. Both with SL 10.6.8 and both have two monitors...no issues.
Upgraded to ML on the MBP on release. Realtively painless process. I tried screen sharing today and I get odd responses with the MBP to the iMac. Just so everyone knows, screen 1 is the main iMac screen and screen 2 is the additional monitor. When showing both screens I could see all screen realestate. However, when I changed to only display screen 1 I started having issues. I couldn't get the entire screen to fit within the window nor scroll to show areas not displayed. Sometimes switching between fit in window and no fit, I would get a blank screen. Screen 2 only displayed and all is fine. I noticed on screen 1 that there was a little black bar or open space on the bottom of the window that was exactly the same size that was missing from the top. No ability to fit or scroll would allow the black space to move so that the menu bar on the top of the main monitor would display.
After doing a bit of searching with no luck and scratching my head, I took a look at the Arrangement screen in the display settings. Wouldn't you know it that the main screen (having a smaller resolution than screen 2) was aligned so that the top of each display was even with each other leaving a small space on the bottom of screen 1 compared to screen 2. When I moved screen 1 in the arrangement screen to a more drastic alignment to verify this was the problem...screen sharing crashed when going from both screens to only display screen 1. Tried screen sharing again going from two displays to one, crashed again.
It appears there is some sort of bug or maybe ML and SL screen sharing doesn't like each other when the remote computer has two monitors.
Submitting bug report to Apple but was curious if anyone else has seen this or knows a work around.
Mike

I have a similar configuration (Lion 2011 MBP and SL 2009 iMac w/ second display). After installing the recent Remote Desktop update things went awry when trying to share the iMac SL displays with the MPB Lion.
The displays on the iMac are the same resolution, however the second display physically sits a bit lower than the iMac display, so I had adjusted the arrangement to compensate the different heights. The second display is located physically to the left of the iMac display, but that shouldn't have any effect as far as I'm concerned. Screen sharing had worked in this config until the recent Remote Desktop update (on Lion).
I thought about what you mentioned about the display screen arrangement, so I decided to just test it for myself, arranging both displays side-by-side on the displays arrangement control panel. Surprisingly, it worked!
I do consider the Remote Desktop update to be the culprit and there must be some bug associated with that. I'm getting ready to submit a bug report, so hopefully we'll see a fix soon.

Similar Messages

Screen Sharing problem with dual monitors in 10.6

When I'm using Screen Sharing from my Macbook to my iMac with dual displays (10.6.1 on both machines) It works fine when I initially connect, but when I switch to Display 1, it shows me Display 1, but though my cursor moves, I can't click on anything. It won't let me go back to viewing both displays either, and changing from Adaptive to Full Quality or vice-versa makes no difference, as does Scaling. This happens whether I'm on my local network or using Back-to-my-Mac. It was working fine under Leopard, but has been exhibiting this behavior since the 10.6 upgrade.
Mark

This is a very irritating bug. One thing that has worked for me a couple of times (I think a couple of times it also didn't work) is to turn on mirroring. Screen sharing then only shows one monitor, since they are both the same. I'm not sure if the monitors have to have the same resolution for this to work, mine do. The nice thing about this is that before quitting the screen sharing app you can just turn mirroring off again and it will go back to normal. It's easiest to do this by enabling the 'show displays in menu bar' in your displays preferences.

Screen Sharing issue with VNC from Mac to PC - Black Screen

I have a Mac mini at my place of work. From it, using the built-in VNC capabilities in Leopard, I am able to successfully VNC to any Windows-based PC. I have a Mac Pro at home that tomorrow I am taking to my office. From my home I VPN into my office and want to VNC to my computers from the Mac Pro sitting at home. VPN connects just fine and when I attempt to VNC, I get a response from the computer at work and am prompted for the password and then I get connected. The problem is that the VNC screen is black. I can see that I am connected to the right computer because it's name is at the top, but there is basically no display. Tomorrow the Mac Pro will leave my home to be placed in my office. However, I am going to get an iMac for my home and need this functionality. I anticipate that I will have a similar problem with the iMac and would like to get it fixed now. Any thoughts on why I am seeing this? BTW...VNC works fine using Chicken of the VNC on my old iMac G3 running Panther over the VPN.
Thanx...Jon
Message was edited by: jhyiesla

I have the exact same problem! I can connect using RealVNC viewer, but, on Leopard's in-built Screen Sharing app, I can authenticate, and see the computer name on top, but, there is simply no display! I have opened all ports on my router, and completely doing away with the Leopard firewall also doesn't seem to help!
Any leads yet?

FCP 7, issue with dual display (video frozen but audio plays)

I have just installed FCP 7 (Studio 3) onto a new MacPro 8-core with Radion5770 GFX card.
Primary monitor is running via DVI, secondary monitor is running via DisplayPort to HDMI.
My problem is that if i enable the secondary display so that I get a full screen image from the timeline and then attempt to play the video remains frozen whilst the audio plays.
Its the same on the primary display video viewer window as well.
If I TURN OFF the secondary display then the video viewer on the primary window returns to normal play back without any issues.
If I turn the seconday display back on, then "scratch" along the timeline then the video refeshes corectly - but every time i hit play the video remains frozen.
Any ideas???

Ive found the solution.
its quite easy.
symply go to
Final Cut Pro -> Audio/Video Settings
Navigate to A/V Devices and under video select the screen your using. If your using the computers screen, like a macbooks screen make sure to check the box. "Miror on desktop". If you do not do this you will have a black frozen immage and the sound will continue playing.
I set a shortcut for "All frames" so that when I press a cmd+p it automatically plays full screen on my macbook.
Hope that helps.
Sylvain Cruiziat
http://www.vimeo.com/sylvaincruiziat

Major Issues with Thunderbolt Display in Yosemite

I have a MacBook Pro (Retina, 13-inch, Early 2013). I'm having issues with thunderbolt display connectivity despite recent Thunderbolt Firmware update. The sleep wake function is not working and display with shut off sporadically.
MacBookPro10,2 Processor Name: Intel Core i7 Processor Speed: 3 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache (per Core): 256 KB L3 Cache: 4 MB Memory: 8 GB

Same problem here. I was so excited to see a firmware update this morning for my mac pro, and sure enough as i sat here, the display went black again.

Messages Screen Sharing Ends with a "Hanging" Desktop Screen

Since the OS X 10.8.1 update, Messages screen sharing – that used to work well in my environment – everytime ends up with a hanging desktop screen. That means: The screen of the desktop, where Messages screen sharing took place, freezes. I have to swipe to another desktop in order to successfully quit Messages via the dock context menu. After that, its desktop screen is responsive again.
This happens independant of who ends the screen sharing session.
It used to work seemlessly before OS X 10.8.1. So I think there is an issue with this update, Messages and the screens (desktops) management.
Message was edited by: Kurt J. Meyer

Hi,
As Screen Sharing does tend to involve a change from the Shared Screen at one resolution changing to your screen at possibly another (which for some produces the White Screen In Sharing) I thought it might pay to look at the method when wanting to go back to your own screen during a Screen Sharing Chat
I would still report it here
http://www.apple.com/feedback/ichat.html
Obviously you have to use some of the free text area to state your OS version and Messages version at it will not appears in any of the drop downs.
7:55 PM Wednesday; September 19, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.1)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Mac Pro Screen Freezing Issue with NVIDIA 8800 GT too

There were lots of entry in threads, where the screen freezing issue was described (disorted screen with strange lines, only reboot helps). Nearly all cases seem to be related to the ATI 2600 card.
http://discussions.apple.com/thread.jspa?threadID=1358062&tstart=30
http://discussions.apple.com/thread.jspa?threadID=1365277&tstart=0
I opened this new thread to show, that this problems occurs not only for the ATI card but for the NVIDIA 8800 card, too.
My MacPro was delivered 8 days ago and was running without any problems. But all of a sudden, I got that screen freeze. And it wasn't the first time, I was heavely working 2-3 hours with that computer.
In total, 2 screen freezes showed on my computer. The first one during working with the computer. The second one during booting into MacOS X. The screen freeze occured during the boot phase with the grey screen and the spinning wheel.
My configuration:
MacPro 2.8, Dual Quad Core
6 GB RAM
3 harddisks, 1 standard from Apple, 2 Samsung with 750GB
MacOS 10.5.2
Formac 20" Monitor
Perhaps others have this problem, too? Than we should emphasize, that this is not an ATI related problem.

I've actually been having the freezing issue for a while now but I didn't have the know-how to troubleshoot it (PC tech trying to support the only Mac lab in the building).
MacPro will freeze randomly (no trend in time, system strain, or open programs). The mouse will operate but will not interact with anything.
Specs:
MacPro - Model 1,1
Dual Core Xeon 2.66
2gb RAM
nVidia GeForce 7300 GT
Mac OS 10.4.11
The machine always has 2 displays connected to it so the workaround that was discussed for the ATI 2600 doesn't apply. I had 1 display connected here in my shop and it froze for that as well.
Message was edited by: DocturKnowles

Home Sharing issues with iPhone 6 Plus

Hi guys,
I'm having problems with streaming music and video on my iPhone 6 plus from my Macbook Pro (mid 2010 model) using iTunes' Home Sharing . I am able to stream without any issues using my iPhone 4S and my Apple TV, however.
I am using iTunes version 12.0.1.26, iOS 8.1.2, and OSX 10.9.5.
Using my 6 plus, I am able to connect to my iTunes library, both music and video. Album art shows up for music but no cover art for the videos. So, all in all, I am able to see the contents of my library.
However, when I try to play songs, a couple things may happen. First, nothing plays for about 10 seconds; then a second or two of the song plays followed by silence again, appearing as if it's buffering. Second thing that may happen is that a second or two plays immediately followed by silence. If I press next to play the next song, what usually happens is that nothing plays, although the song title does appear.
As seen in this video, I don't have any issues with my WIFI connection or internet speed, as demonstrated using the iPhone 4S and Apple TV.
I have no clue as to why this is happening.
Hopefully someone could shed some light with this issue. Please feel free to comment. I'm open to and appreciate any suggestions while Apple tries to find a solution. Thanks.

UPDATE
So, after working with the guys at Apple, they we were to provide a solution. Now I have no problems using Home Sharing with my iPhone 6 Plus!!!
(I should add that I have the Linksys Advanced Dual-Band N Router (E2500))
The issue was fixed by giving one of the wi-fi channels a different name, thus splitting the channels into 2.4 GHz and 5 GHz. Then, I connected my iPhone to one channel (2.4 GHz) and my MacBook Pro to the other channel (5GHz). In this configuration, I have had no issues streaming my music and video.
It seems that the problem is some kind of interference between both devices when using the same channel (i.e., when both the 2.4 GHz and 5 GHz channel share the same name).

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.

Firefox version 22 screen tearing issue with video

So I've updated to Firefox 22 and have recently started noticing this really annoying screen tearing issue when scrolling. its only when i use Firefox sometimes it happens when I'm watching videos sometimes it just happens on normal every day pages. I've tried to duplicate this issue in other browsers (Chrome) and it just only seems to happen with Firefox. anyone else experienced this and knows how to stop it? kinda annoying

Hello,
'''Try Firefox Safe Mode''' to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.
''(If you're not using it, switch to the Default theme.)''
* You can open Firefox 4.0+ in Safe Mode by holding the '''Shift''' key when you open the Firefox desktop or Start menu shortcut.
* Or open the Help menu and click on the '''Restart with Add-ons Disabled...''' menu item while Firefox is running.
''Once you get the pop-up, just select "'Start in Safe Mode"''
'''''If the issue is not present in Firefox Safe Mode''''', your problem is probably caused by an extension, and you need to figure out which one. Please follow the [[Troubleshooting extensions and themes]] article for that.
''To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.''
''When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.''
Thank you.

Full screen mode - Issue with Aperture freezing

Hi I have an issue with Aperture 3 freezing if I send an image to a plug-in or external editor while in full screen dual display mode. I have to exit full screen mode first and then send to photoshop/external plugin.
It is not a huge deal and a simple workaround but if I forget to do it Aperture will freeze and I will have to force quit the application.
Any thoughts or suggestions welcome.
Thanks!

Just send a comment to Apple via "Aperture→Provide Aperture Feedback".
IME, both full-screen mode and dual-display mode have some rough edges. (I don't expect any improvements until OS 10.7, which is widely reported to include a full re-design of full-screen mode.)

Screen refresh issue with SQL Developer 1.5.5 on Vista 64 bit

I am using the latest version of SQL Developer.
I have screen refresh issues in sql developer. On scrolling up and down the display gets jumbled, some time screen do not display at all. Its making working with SQL Developer very difficult. I don't have such an issue with any of my other editors.
Is this something specific to Vista? Is there any know solution to this issue.
Thanks
Edited by: user5899685 on Sep 1, 2009 11:14 AM

Specific? Not really, but judging from the posts here Vista is more prone. It usually indicates incompatibility between Java and video drivers.
If updating your JDK or video driver doesn't work or isn't an option, just disabling DirectDraw in \sqldeveloper\bin\sqldeveloper.conf usually works too:
AddVMOption -Dsun.java2d.noddraw=trueHope that helps,
K.

[SOLVED] Screen brightness issues with Acer 5372Z

The screen of my laptop goes black whenever I boot into ArchLinux, after "reading Udev events" on startup. Most of the time I have to use a flashlight to see the console on my screen and type
sudo setpci -s 00:02.0 F4.B=20
to set screen brightness manually. The `Fn` + `Brightness up` combination doesn't work on my machine, but that's not an issue with Arch, but fault to sugar in coffee.
There are a lot of similar threads in this forum, but none of the solutions described there really worked 100% or not at all, that's why I'm opening a new thread as this seems to be specific to my hardware.
Details:
Graphics controller:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
Screen resolution:
1366*766
/boot/grub/menu.lst:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/sda10 resume=/dev/sda5 ro vga=775
initrd /initramfs-linux.img
/etc/rc.conf#DAEMONS:
DAEMONS=(hwclock syslog-ng network netfs crond laptop-mode dbus gdm)
I will describe here what I have did so far on hacking:
Installed the video driver for my Intel card as described here in the wiki
Set kernel mode to `nomodeset`, without specifying vga, of course, which surprisingly solved the issue, but prevented me from using Gnome.
The supposed solution in the Arch wiki doesn't work for me. It makes it worse, in the sense of dumping screen brightness even before "reading udev events" on boot.
My current workaround (to avoid using a flashlight) is to put this line into my `/etc/rc.local`:
setpci -s 00:02.0 F4.B=20
I wonder if you can help me to solve this issue, or point me to any of the great documentation provided by the Arch community I might have missed...
Last edited by kennym (2011-09-06 16:03:58)

rg_arc wrote:I have this problem as well for my Acer Aspire 4810TZ. The only thing I can think of is to make some sort of temporary fix. But I agree with you, There should be a permanent fix. Every time I've installed Arch on this computer the same problem arises and the only way I can change the brightness is the setpci terminal method.
This is bad news for new Arch (and Linux) users. This will be probably the point where they will turn over to another distribution.
It seems to be something which has been included in newer kernels, because I can remember that in the 2.6 series this issue did not exist.
Last edited by kennym (2011-09-05 16:05:08)

IChat screen sharing problem with AIM

Hi,
I have two laptops - one is a MacBook and the other is a PowerBook. Both are running Leopard. At first, when I had tried using the screen sharing feature of iChat, it had worked flawlessly on both the Bonjour network as well as the AIM network.
Now, for some reason, I cannot get screen sharing to work using the AIM network. I am able to conduct text chats, audio chats and video chats, but no screen sharing over AIM. Screen sharing over the Bonjour network continues to work without a problem.
Any advice?

For some reason ichat does not work when internet sharing is on.
Therefore that might be the problem with your screen sharing since you seem to not be able to get it to work (audio is part of the feature and if you have recently relocated you might not realize that internet sharing is on).

Potential Solution: Home Sharing issues with iTunes 10.6

TL;DR: On a hunch, I changed the power settings of the ATV to never sleep. Since then, I have not had any issues. Granted, it's only been a couple of days, but it seems to have done the trick.
Folks,
Wanted to share my experience with Home Sharing issues after upgrading to iTunes 10.6. These forums a rampant with reports of the issue, so I'll defer to the search field above if you don't know what I am talking about. In short: iTunes 10.6 seems to have busted Home Sharing.
For those who do, here's what I found:
For some reason, is saw a very large number of established sessions from my Apple TV (ATV) into port 3689 on my Mac. This is the port that ATV uses to query iTunes to see what's available via Home Sharing (e.g.: what movies, songs, pictures, etc are available for display on the ATV).
A sniffer cap and some observation of the power indicator on the ATV indicated that while it was sleeping, the ATV was querying iTunes. It would power on for a sec (wake on LAN, maybe?), issue some queries, then sleep.
When this happened, the TCP sessions created were never town down. As such, I would eventually see 200+ established sessions on port 3689. I don't know exactly how many it took to make this happen, but when I saw this, iTunes stopped accepting new connections.
Of course, bouncing iTunes would remedy the issue for a while, but it would return.
On a hunch, I changed the power settings of the ATV to never sleep. Since then, I have not had any issues. Granted, it's only been a couple of days, but it seems to have done the trick.
I would be interested to hear if it works for others.
Happy viewing,
Chris

Thanks for posting this.
I've been searching for an option of how to approach this problem.
I picked up the new AppleTV when it was released, but it has made iTunes fairly useless from a Home Sharing standpoint.
I also observed the massive number of TCP connections being opened against iTunes, but never closed.
As expected, I could manually kill a few of these connections, and then could connect again, even without closing iTunes.
I performed most of my testing with Windows 7, but while troubleshooting I had the same issue with iTunes on an old Mac Mini I had sitting around.
I will try your solution, which makes a lot of sense, but it would be nice if Apple fixed the real problem.
Thanks again.

Screen Sharing issues with ML and SL with dual displays??

Similar Messages

Maybe you are looking for