Host machine: Debian 10 running NoMachine 7.2.3
Settings:
Specified H264
User Hardware Encoding enabled
Use Specific Frame Rate enabled (60FPS)
Use Acceleration enabled
Client: Windows 10 running NoMachine 7.2.3
Both machines have monitors attached.
Using NX protocol for connection.
FullScreen / Scale to Window / Desktop is currently 2560x1440 (reduced from native while testing this issue)
Specific issue:
I do a ton of work in the terminal and when viewing desktop via nomachine, the terminal caret is randomly not visible. The same issue is less noticeable with right click menus and other areas of "visual updates in small screen space." If this were another remote desktop vendor I would try to find the "don't update just regions" setting to force the entire display to update regularly, but I can't find similar settings for nomachine. I have a dedicated gigabit connection between the two machines with no other traffic on that line, so bandwidth is not an issue.
To recreate:
I disabled caret blink (using universal access / accessibility settings) so the caret is a solid block in terminal / vi. If I edit a text file in vi and move up and down, the caret will only update visually every other line or so (verified on the physical screen it is moving correctly). Same if I highlight or insert, etc. You inevitably miss a character or so or lose your place).
I have tried changing speed vs quality slider, resolutions, swapping from h264 to VP8, etc.
I have disabled:
multi-pass display encoding
frame buffering on decoding
client side image post-processing
Nothing seems to change this specific issue. Yes I can make dragging a quarter-screen-sized terminal window smoother, but that doesn't help me follow the caret in vi/vim. Both machines are nicely spec'd (client has 16G / RTX2080, server has 32G / GTX1080)
Is there a way to get nomachine to update all the screen all the time, or at least better refresh small areas like a terminal caret?
(OP): Based on a night of troubleshooting, the issue seemed to be either:
An issue with the Debian install of the nvidia drivers
The server machine is a laptop with a broken main screen (but with an HDMI external monitor plugged in). The Debian X-server may have been confused as to whether it was headless or not and caused issues with nomachine (which tries to detect headless and start a virtual session).
The solution to this exact problem would be to disable the GUI and force a virtual session, per https://www.nomachine.com/AR03P00973 (dummy dongles won't work because the laptop's main display is not a standard plug).
In my specific case, I needed GUI access on the server at times so I couldn't use the above methods, and I could not remedy the problem with Debian, so I wiped the system and installed Ubuntu 20.04, which is more forgiving with graphics drivers and monitors. After setting up the Ubuntu system as similarly as possible to the Debian system and letting the proprietary nvidia drivers auto install, nomachine connected at the same resolution and worked perfectly, without the lag in small screen areas.
Using Blender 2.82a I encountered this screen glitch:
But I had a similar issue with Photoshop 2020 where the GUI had similar glitches. And lastly, Minecraft with the SevTech Ages modpack. This doesn't happen with other software (Firefox, Excel, VSC, Sublime Text, WSL). This makes me think it's should be a graphic drivers issue. I uninstalled the NVIDIA drivers and left Windows reinstall them. I didn't encounter the issue again yet. Can anyone confirm this is a bad drivers issue? I couldn't find much information online (or didn't know what to search for).
I cannot assuredly say that this is a driver problem, but the same happened with me with my old PC. My old PC was very low-end. It was very slow in Blender, but got the work done. To make my PC faster, I saw a youtube tutorial which showed that going to System > advanced system options > graphics and switching off all 'fancy' features will make your PC faster. Doing this resulted in the same glitches in blender and inkscape, but got fixed by switching those options bak to what they were before.
I came across with a problem these days!
The problem is that after I writing debian os from microSD card to emmc, beaglebone clould i9 says:
Failed to write to 'state.settings'. ENOSPC: no space left on device, write
and nothing works at all!
So I decide to format the emmc on beaglebone!
Can anyone help me how to get this done?
Maybe you are using the wrong debian version. Currently (12.03.2020) the version "Debian 9.9 2019-08-03 4GB SD IoT" is just usable for microSD card and is not recommended for eMMC flashing. If you want to flash the eMMC you can currently use the version "Debian 9.5 2018-10-07 4GB eMMC IoT Flasher". Unfortunatley, does this version not include the graphical desktop.
I'm in an unusual spot. The built in screen on the laptop I'm using right now is broken so bad I can barely see anything besides random flickering lights on it. Because of that, I got and plugged in a monitor to my laptop. This moniter works fine once Windows 7 has already loaded.
The issue is: I'm trying to open the BIOS/boot menu to live boot off of my USB, but I can't see anything. How do I make it so that I get visual output on my monitor early enough to open the BIOS/boot menu?
If it's a Dell laptop, try FN&F1 or F1
Dell Forum
I've installed JDK, Android SDK and Mono Android for Visual Studio 2010, I've created an empty solution and I got the emulator up and running with Android 2.3.3 - so far so good.
When I try to deploy (F5) the app to the emulator, it connects to the emulator, and all goes fine until it starts "Installing the platform framework". Then it loads for several minutes, and finally throws an exception that looks like this:
I have tried googlin' it, but the INSTALL_FAILED_MEDIA_UNAVAILABLE doesn't seem to be described anywhere else.
I don't know if this is an important detail, but on my PC I have remapped my home folders (Documents, Favorites, Desktop, etc.) to folders like "D:\Mikkel\Dokumenter". It seemed to cause some problems when starting the emulator initially, but after adding the environment variable "ANDROID_SDK_HOME" pointing to "D:\Mikkel.android" the emulator started up with no problems.
Please advise.
Ensure that you have enough internal and external free space in your device. You can determine the free space available with the command:
$ adb shell df
Filesystem Size Used Free Blksize
/dev 192M 32K 192M 4096
/mnt/asec 192M 0K 192M 4096
/mnt/obb 192M 0K 192M 4096
/system 145M 124M 20M 4096
/data 196M 167M 29M 4096
/cache 95M 32M 62M 4096
/mnt/sdcard 3G 177M 3G 32768
In the above output, /data (which is the default install location) has 29MB free, while /mnt/sdcard (the SD card, and the external install location) has 3GB free.
For Debug builds, you need to have ~40MB free (for the Runtime package, Platform package, and apps). Release builds are significantly smaller, but Release builds cannot be created with the Evaluation version.
It's plausible that if your emulator doesn't have an SD card, then Android would generate the INSTALL_FAILED_MEDIA_UNAVAILABLE error. (To add an SD card to your emulator, start the android app, go to Virtual devices, select a device, click Edit, and look at the SD Card section.)
A cursory grepping of Android suggests that DefaultContainerService.java is the controlling factor, specifically DefaultContainerService.recommendAppInstallLocation(), and that if you're out of internal space and the package specifies auto (as Mono for Android does) and the SD card is unavailable (status.equals(Environment.MEDIA_MOUNTED) is false), then RECOMMEND_MEDIA_UNAVAILABLE is returned, which is translated into INSTALL_FAILED_MEDIA_UNAVAILABLE. This still seems odd to me (wouldn't RECOMMEND_FAILED_INSUFFICIENT_STORAGE make more sense?), but this appears to be what's happening.
Possible Problems :
No Internal/ External space in the Drive(or sdcard).
Connection is lost during the installation (apk to device or emulator).
Solution :
Try to create some space( remove some apps).
Try to reconnect the phone/emulator restart (worked for me)
This can be caused by having insufficient space on the device. So it goes looking for an SD card to install on to instead. if that isn't there it will trigger this response.
I had this problem even with 1GB of free space and an .apk of 1,5Mb. What I did was building an .apk and moving it to data/app folder. This worked for me. The problem is that I think your device must be rooted in order to access this folder.
I've solved the problem - it seems that if you close the (weird) empty DOS prompt that opens when the emulator is started, the connection to the emulator is lost.
Leaving the DOS window open, everything works like a charm.
In my case, it helped me out to switch the usb connection mode. You have to "just load" the device by usb instead of providing the sd card to the pc file system.
INSTALL_FAILED_MEDIA_UNAVAILABLE
Because of low memory. Delete unnecessary files and apps.
This problem appeared for me when I installed Facabook app on my phone. so I uninstalled it and problem solved.
It is due to not enough space on the phone.
Check your build packaging In my case it was packiging all kinds of assets, psd, etc.. and the .apk file was huge and the phone did not have that much space