Parallels Desktop Linux Mint internet connection not working - linux-mint

i wanted to take my first steps into a linux dist. So I got myself Parallels Desktop and downloaded Linux Mint. Now im stuck because I don't have internet connection inside my VM. The network seems to be established correctly and i can ping anything but not browse. Anyone knows this problem and can help me out? Parallels Network Settings are using "Shared Network". Im using Mint 20 and because of the problem im not able to install the necessary "parallels tools"

It seems that its a problem with the version of parallels desktop from the app store. I tried my luck with the normal version of parallels desktop downloaded from their website and after setting up my linux everything works now.

Related

Error "This app can't run on your pc" when i run .exe from win10 Home

I am new to Unity and from my PC (MAC) i have created 3 builds of my project (1-MAC, 2-Windows x86_64, 3-WebGL)
I state that my version of Unity Hub is 2.4.2 and my Unity version is 2019.4.18f1
When i start my game on mac everything works fine (obviously starting the build for mac), later I put the x86_64 windows build in a compressed folder and then transferred it into a USB, to try the game from another pc (win 10 PRO). In this PC the same version of unity was already present.
So far, so good.
The problem starts when I take the same USB with the same files, which, as previously said on win10 pro work, I put them on a win10 home (32 bit) and when I try to start the .exe it gives me this error "This app can't run on your PC. To find a version for your PC, check with the software publisher "
Looking on the internet I tried to get around the problem they change the local settings policy, but the result is the same :(
These are the files inside my compressed folder
And these are my build settings
I thank whoever will be able to help me and I apologize for my bad English
You say your other PC is 32 bit!
That's your issue!
You are building for the Architecture
x86_64 => 64-bit CPU
It does not mean 32 or 64 bit.
To run it on a 32 bit system you have to build for x86 instead.
See Unity Manual - PC, Mac & Linux Standalone build settings

Rad Studio 10 and Mac OSX Sierra (virtualbox guest)

Since i started developping applications using Rad Studio 10 i'm able to test the windows and android versions on my desktop.
However, i do not have a Mac. So i decide to create a virtualbox guest Mac OSX Sierra on my Windows 10 Pro 64-bit. It works fine but i'm not able to connect and share files between Mac/Windows or test iPhone using Rad Studio.
What steps do it requires to configure my virtualbox to work with RAD Studio 10 ?
You are lucky if virtual box work fine, me i always have trouble with it (especially connecting the ios device). However i found that vmware is much more stable, full screen resolution, much (much) better to handle the iphone connection via usb, and i didn't have yet any crash when on virtual box it's quite often
on vmware, you can also copy/past text from the virtual machine to the host that is very usefull when debuging (on virtual box you can not)
on both (vmware and virtual box) you need to setup the connection as bridged connection. after you successful installed the emb pa server, you can get the ip of the machine with the command "i"

Unable to create Genymotion Virtual Device

I have successfully downloaded and installed Genymotion and Virtualbox as well as a Virtual Device Image but I am unable to create a virtual device.I get an error message stating
Unable to create Virtual Device:
Failed to import OVA
My laptop Specs
8gb RAM
Intel Core i7 (Sandy Bridge)
Hardware Virtualization is enabled in the BIOS.
Deleting the Genymotion cached .ova file, deleting the corrupted deployed image, redownloading the image, and reinstalling it addressed the issue for me.
Note that the deployed images are under:
~/.Genymobile/Genymotion/deployed
the cached ova files are under:
~/.Genymobile/Genymotion/ova
I solved the problem.It was my mistake.
It works fine by running genymotion with administrative privileges.
I solved the issue deleting the deployed images in
~/.Genymobile/Genymotion/deployed
I didn't touch ova files
I just ran into this problem too, so just in case anyone needs it:
The reason why it needs admin privileges is probably because of your settings on where it store the virtual device..
Go to Settings - Virtual Box - and change your virtual devices storage area. I got mine set to something like \Program Files\Genymotion, that's why it needs Admin privileges. I only blanked the field, clicked ok, and it got set to the default which is in my home directory..
After that no need to run as admin anymore..
(I need 50 reputations to comment, so had to use this answer..)
I solved the issue myself by deleting all old devices (the folders of previously made devices) from my .android/avd folder.
In my case, the DHCP server was missing from Virtual Box's Host Only Adapter. I added a DHCP server at 192.168.56.100 with addresses from 192.168.56.101 - 192.168.56.254 and it came up.
I also had the issue. Had to delete Genymotion cached files/devices then redownload devices and reinstall.
We had the same issues, it was because we had wrong version of Oracle VM Virtual Box. Make sure you uninstall wrong version and re-install Compatible Oracle VM Virtual Box.
just delete the file in your ova and it should fix it, thats what i did, no need to run program under admin or anything. didnt delete my deployed files either. (I was trying to create new virtual machines not open them)
Have a look at this blog.
Genymotion is previously known as AndroidVM.
As the blog stated:
Known bugs (same as 20121119 release) :
Hardware OpenGL/Intel HD/Windows : On most Intel HD drivers running Windows, the AndroVMplayer might crash (in the driver DLL) when starting Android ; you may have to restart AndroVMplayer an important number of times before it suceeds
Hardware OpenGL/WebView : On some GPUs (mostly NVidia ?), the browser and all apps which use the WebView component might show scrambled HTML content
AndroVMplayer now support window resizing, as well as fullscreen mode ; to use AndroVMplayer in fullscreen mode, you have to :
select “manual resolution” and tick the “fullscreen” box
press F11 (Ctrl+F11 on Mac) to switch to fullscreen when the player window has appeared
When starting the virtual machine, AndroVMplayer now check different things :
If your AndroVM virtual machine doesn’t have the “hardware OpenGL” option enabled, it can enable it for you before starting the VM.
If your AndroVM virtual machine first network adapter is not configured, it can configure it for you (as well as create the host-only network for you).
To summarize that, with this new AndroVMplayer, to use OpenGL hardware you just have to :
Import the AndroVM ova in VirtualBox
Start AndroVMplayer, choose your resolution and the virtual machine you’ve just imported
Click “Run” and it should work
You can still use AndroVMplayer with non-VirtualBox systems (e.g VMWare) but, obviously, you won’t benefit from automatic VirtualBox configuration and VM start/stop ; in this case, you have to choose ‘none’ as the VM name and directly type the IP address of your virtual machine.
Please note that, due to the change in communication, old AndroVMplayer won’t work with 20130222 OVAs and old OVAs won’t work with 20130222 AndroVMplayer.
Disadvantage of deleting the deployed and .ova files is obvious i.e. you have to download the massive 200mb image again. A better choice is to :
Open genymotion and open settings --> virtualBox --> virtual devices browse and set the path to a folder which can be completely accessed without administrative pivileges e.g. for ubuntu set virtual devices path to any folder in your home directory for example /home/user/deployed and for windows you can use a folder like C://deployed.
That's it . Now you can use your already existing .ova file again to deploy image to new locatioin without any problem.
I followed following steps
I removed everything under {~/.Genymobile/Genymotion/ova} folder (with only doing this step it works sometimes)
removed everything under {~/.Genymobile/Genymotion/bin} folder
After which I downloaded the fresh copy and it worked like magic.
Hope this helps.
I solved this error message by fixing the path to the virtual machines folder (Setting > VirtualBox - Virtual devices). Yes, I had broken settings...
In case someone is using Mac OSX YOSEMITE or earlier. Follow this post. It worked for me. http://forums.macrumors.com/showthread.php?t=1196027
Run these two command in Terminal:
sudo chmod 755 /Applications
sudo chmod 755 /Applications/Virtualbox.app
Took me hours to get it to work!
Check if you have problem with your virtual device path under
Genymotion > Settings > Virtual Box > Virtual Device >
If it is still an issue remove files under ~/.Genymobile/Genymotion/ova
If it is still an issue remove files under ~/.Genymobile/Genymotion/bin
Remove Genymotion and all files under ~/.Genymobile/ & reinstall
If you have installed the Genymotion plugin without VirtualBox then make sure the version of VBox is compatible with the plugin, otherwise the plugin will not deploy the virtual device regardless of the OVA file.Install the latest versions of both if you are unsure
Once you verified the versions, you may need to either:
a: Give administrative privileges for Genymotion via properties
OR
b: Change the location for the deployed devices via Settings/VirtualBox to somewhere more accessbile like D:/GenyMotion VMs/
If both step 1 and 2 doesnt work for you, sadly you will have to clear the cache via Settings/Misc and reinstall the OVA file.Hopefully your efforts will be worth it. Good Luck.
It works fine by running genymotion with administrative privileges.
I solved it by deleting all of file in Ova,Templates and Deployed folder, I can run download and reinstall again and run without Administrative privileges
I solved this problem on windows setting up sdk path in configuration option.
Double check the virtual device you're trying to create has the same version on Genymotion that you have running.
I just upgraded to 2.1.1 but all the virtual devices I was trying to install were for 2.1.0. Downgrading Genymotion did the trick.
A very simple Solution that i just Tried is:
1) Delete your Instalation Folder at ~/Genymobile
2) Delete the Virtual Device Folder at C:\Users\ your_name\AppData\Local/Genymobile
3) Reinstall
4) Done.
Oracle VM ware has an update for Windows 10. I was getting this error until I installed this update.
I had the same problem because i had an old version of Virtual Box (4.0.0).
So, I uninstalled genymotion and the old version of VB,
and I installed genymotion with virtual box (5.0.28).
And Its worked fine.
This fixed the issue:
Just go to ~/.Genymobile/Genymotion/ova (Either you are on Mac OSX
or Windows, you can find this path by looking for Virtualbox path at
the Genymotion Settings, there is a path to Genymotion/deployed
folder, you should go to Genymotion/ova folder)
Open the ova file with your virtualbox.
At the Virtualbox startup dialog box, Appliance settings, It shows Guest OS type set to Other Linux 64, you should double click and change it to your OS type (e.g Mac OSX El Captain (64-bit)) and Import:
Now launch Genymotion and find the virtual device in the list of already deployed ones ready to run
Run the virtual device, after first run you get a warning saying Genymotion version does not match with Virtualbox version and choose Continue.
I hope it helps future visitors to this page.
Any of above solutions didn't work for me but I finally found it!
You should remove under folders in C:\Users\[your user]\VirtualBox VMs.
I hope it helps you.
First you go to ova inside the folder and delete all files
C:\Users\UserName\AppData\Local\Genymobile\Genymotion\ova
After you uninstall the genymotion and virtual box. next you can do for install of genymotion and virtual box as check your support your OS(windows) capability version install then work fine.
Now you can create virtual device.
This way for work my windows 10 OS.
Solved!!
I am using OS X 10.9 (Mavericks), Genymotion v1.3.1
While adding the device, instead of adding Nexus, I added Galaxy S4/HTC One/Xperia Z - 4.2.2 with Google Apps.
This one just worked.

Problem connecting real Android device to Eclipse

I just got a new computer and am trying to set up my developing environment but I'm having trouble getting eclipse to connect with my phone. I have a HTC Aria android device and I was able to use it with eclipse on my old Windows XP computer. On my new Windows 7 64bit computer though, its not working.
When I run my program, I see my HTC device in the device chooser, however, its state is "offline" and it randomly disappears then reappears. I can select it, but I cannot push "OK" to run on the device. I've tried reinstalling my driver and updating it through HTC's website, but nothing has changed.
Any ideas?
I ended up reinstalling my OS, installing Eclipse Indigo 64bit, and then installing my phone driver. Works perfectly now. Have no idea what was wrong before

Android Emulator 'No Service'

I am new to both the android and android development so I'm not on familiar ground here.
When I start the emulator I have no service. Therefore I have no internet connection on the emulator.
I am running Windows 7 and I generally run the emulator via eclipse.
My host machine is connected to the internet via the Local Area Network. There is no proxy.
I have tried:
Disabling all network adapters except for the Local Area Network [link]
Running the emulator from cmd line with: emulator -avd -dns-server 8.8.8.8
Reinstalling the SDK Tools 9 and Platform Tools (rev 2).
Restarting the machine! :P
Is there a setup needed to specify to simulate a 3G connection? Or could this be a Windows 7 permissions issue? Or am I doomed like these folks: link link
Ah! found the solution.. I uninstalled the entire SDK and reinstalled it to C:/Android. I deleted the C:/Users/[your-name]/.android folder and recreated an avd. Voila.. Something in there worked!
[edit]
Actually it looks like you have to keep restarting the emulator until it connects. I will often get no service so I restart a bunch of times till it works.
I found that 'Airplane Mode' was enabled by default in the standalone android emulator - this may also be the cause in the sdk version. Turning this off (by holding down the red power button until the menu came up, and then toggling the airplane mode button/section) allowed the emulator to 'find service' and connect properly through the LAN.