I've searched every place I could think of, but nobody seems to have had this issue or didn't bother asking about it.
I just installed Ubuntu 11.10 freshly with the gnome fallback shell. Everything works perfectly fine, except for one thing.
My WINE applications start on the wrong screen, this isn't really a big issue, but when I drag the window to my main screen, the mouse doesn't work on the application anymore. The app doesn't freeze, and is fully responsive to keyboard input, I just can't click on anything anymore.
My specs (relevant):
- NVidia Geforce 540M
- 1 laptop screen 1366x768
- 1 Samsung Syncmaster SA550 27" - 1920x1080
Thanks in advance!
Did you create the application on a resolution smaller then the current on your pc?
If so, do the following (I have a laptop with 1366x768 on the internal monitor and 1920x1080 on the external monitor):
Open winecfg
Check the Virtual Desktop checkbox and set the size to the largest resolution you are going to use
Start the app and check if it's working properly now (You can check that with the battlenet launcher :))
Start winecfg again and uncheck the Virtual Desktop box
Related
I'm happily using x2go to connect to a remote Ubuntu Server 16.04 with XFCE installed from my local pc with a local resolution of 1920x1080 on a HiDPI screen (13''). If I run the x2go client from a virtualized Linux (Linux Mint 18.03 with XFCE), everything works well and I can see a really sharp image of the remote desktop. Problem is, when I try to connect directly from Windows 10 the image is blurred and the resolution is wrong. I tried to play around with the x2go client settings but no way, the image is always terrible. I also tried to use PyHoca and different X-servers but the result is the same.
Is it a well-known problem? Any suggestion on how to fix it?
Thanks in advance.
I had a very similar problem: A Dell laptop with an Nvidia graphics card, having a resolution of the built-in flat panel of 1280x800. I connected this to an external screen with HDMI with a resolution of 1920x1080. However, X2Go seemed to pick up the resolution of the built-in screen instead of the actual screen, making everything seem blurry (interpolating 1280x800 to 1920x1080).
This is what fixed it for me: Navigate to the C:\Program Files (x86)\X2GoClient\VcXSrv\ directory in Explorer. Select the vcxsrv.exe file and right-click it, choosing Properties from the popup menu. Go to the Compatibility tab, and in the Settings section there, select the option "Override high DPI scaling behavior. Scaling performed by:" and then select "Application" in the combo-box below.
Restart the X2Go Client to have its X server start with this new setting.
This fix also solved X2Go Windows Client crashes in my setup.
I have basically the same scenario: connecting from a high DPI Windows laptop to KDE on Debian, in my case for Desktop Sharing. The client would connect okay, but display only a portion of the remote host's screen.
Keyboard shortcuts would not scroll the client window.
Any attempt to show more (maximize, go full screen, click-and-drag client window border) would seem to work for a second, then crash.
The Compatibility scaling change fixed the instability - no more crashes, yay! - but did lead to slow repaints as noted by Algeboy.
Upgrading to a newer version of VcXsrv also did not resolve the crashes - Compatibility change still required, but screen repaints are quicker.
To upgrade, download and install the latest VcXsrv in its own directory. Using Explorer or whathaveyou, apply the HiDPI setting to vcxsrv,exe.
Start x2go client but don't start a session. Click Options, Settings, then X.Org Server settings tab. Select "use custom x server". Point to the newly installed vcxsrv.exe and click okay. Restart the x2go client.
This apparently takes the version from 1.20.6.0 supplied by x2go to 1.20.14.0 (2022-04).
Screen refreshes are quicker if I minimize all applications on the host, allowing it to repaint the desktop, then restore whatever I want to work on.
I've Installed the newest version of Android studio, including the newest version of HAXM, ndk, sdk and whatever other related dependencies it installs. Intel Virtualization bios setting thingy I can't remember the name of is enabled and I have no trouble in virtual box and such.
I created an empty activity and tried testing it on the phone, works perfectly. Then I tried it on the emulator and there is a problem when it is hardware accelerated. It just opens a white window. The android studio displays 0 errors and thinks it ran the app properly. The graphics card I have is a gtx 1060 6gb. When it is software accelerated it works but is so slow I would rather use a chisel on a rock to draw the application usage.
So if someone knows a fix it would be nice.
Thanks
Well I have discovered that in order to solve the issue you have to go to the sidebar menu click More>Settings>OpenGL ES Renderer and(in my case) set it to Angle(D3D11) or Angle(D3D9) or Swiftshader. After that you simply restart the emulator and the issue should be gone.
For me Desktop native OpenGL and Autodetect based on host(which probably sets it to the first thing) don't work and leave you with a white screen.
In case someone finds this useful, you can set software acceleration as below and this solved the issue for me on Mac OS. (OP also mentions it works with software acceleration)
Tools > AVD Manager
Select virtual device
Click on Edit (pencil icon for me)
Click "Show Advanced Settings"
Look for Emulated Performance - Graphics
Select "Software" option
Current version of the emulator (27.1.3) doesn't work for me. The emulator just shows a white screen. Even playing with the gpu in the .ini configuration didn't work.
Once I downgraded to 26.1.4 (https://dl.google.com/android/repository/emulator-darwin-4266726.zip) the emulator started working again.
It seems that the Android Emulator is somehow conflicting with the NVidia Web driver on Mac OS. I had the latest NVidia Web driver (378.05.05.25f04) installed and I was having this same problem - the white screen whenever I used Desktop Native rendering (or left it at the automatic default which selects that as well).
I tried the Swift Shader as well, it works but the performance is abysmal!
On a hunch, I switched back to the OS X Default Graphic Driver from the Nvidia Pref Pane in Apple menu settings, and the Desktop Native driver is now working great after the computer restart!
The same problem can happen to the lightning fast Microsoft Android Emulators utilizing Hyper-V that work on both Intel and AMD CPU based PCs. The solution is in the same line as the accepted answer. For those who use Microsoft Android Emulators and land here by searching "android emulator white screen", here is the screenshot showing how to solve the problem by changing the default hw.gpu.mode from the default "auto" to "mesa":
So sorry
Check your onCreate method in your MainActivity.java, it should have setContextView(R.layout.activity_main)
I develop mostly in one of two layouts:
Laptop with its native 1920x1080 resolution OR
Laptop with attached 2nd monitor (with 1650x900 resolution)
Lets call the top one LAYOUT-A and the bottom one LAYOUT-B.
When I open the Delphi and Visual Studio IDEs (or Excel, or any other application) and set up the layout of the main window, debugging, find-and-replace windows, etc I find it all works nicely...until I switch between LAYOUT-A or LAYOUT-B. Then the main Windows desktop gets messed up (icons bunched up haphazardly) and the IDEs windows need to be reset.
This gets even worse if I have to connect to a projector with some low resolution like 1024x768 for a client demo! Then I face 10-20 minutes of painful resetting up!
Is there any way, perhaps early after boot, where I can tell Windows "Hey, I'm using LAYOUT-A today!" and then everything just works??
Using Windows 8.1 here.
I'm trying something very different. We have legacy Windows Mobile programs that we need to run on Windows 8.1 tablets with capacitive screens. To do this we've installed the stand alone Windows Mobile 6.1 Emulator which runs without a problem. Doing this, we can load and run our old Windows Mobile programs on the 8.1 Tablet and they run well but we are having problems with the touch or mouse click. The emulator is meant to be used with a mouse button to select and click not a touch screen. When we run our old programs we have to double-tap in order to select anything. This is not a problem until we try to enter text from the emulator keyboard. We have to tap each key twice in order to enter a character. This becomes very tiresome and makes the legacy program useless. Our legacy Win Mobile program was designed to allow our field people to collect large amounts of text and numeric data. Having to tap each key twice will not work.
We've examined the limited mouse and touch option in Windows 8.1 and nothing seems to help. So here are my questions:
Is there third party software that may improve on Windows 8.1 mouse customization? Synaptic maybe?
Is there a command line switch for the emulator we could add that would fix this problem?
Does anyone know of a method to fix this?
Thanks
I have asked this question to MS support.
http://www.microsoft.com/en-us/download/details.aspx?id=17284
System Requirements:
Supported Operating System
Windows Server 2003 Service Pack 2, Windows Vista, Windows XP Service Pack 3
Windows Mobile 6.5 Developer Tool Kit is not supported by Windows 8.x
My Double click test video
http://youtu.be/0QIilCg1kxg
I think the problem is in Windows 8 touchscreen API driver, I have tested this emulator with Win7 tablet, no problems with double click.
For a project I was given a virtualbox image to work on. I don't have virtualbox but opened it in VMware and it works great except that in full screen the vm stays small and in the middle. I tried changing the autosize to stretch but it turns out obviously distorted and hard to work with. How do i get the fullscreen to work properly?
You probably lack VMWare Tools. You can install it with VM > Install VMware Tools.
I had to change the display resolution within the OS, though I thought it should have done that automatically