Anyone using Android for X86? profile problem

For interesting topics. But remember this is a Linux Forum. Do not post offensive topics that are meant to cause trouble with other members or are derogatory towards people of different genders, race, color, minors (this includes nudity and sex), politics or religion. Let's try to keep peace among the community and for visitors.

No spam on this or any other forums please! If you post advertisements on these forums, your account may be deleted.

Do not copy and paste entire or even up to half of someone else's words or articles into posts. Post only a few sentences or a paragraph and make sure to include a link back to original words or article. Otherwise it's copyright infringement.

You can talk about other distros here, but no MX bashing. You can email the developers of MX if you just want to say you dislike or hate MX.
Post Reply
Message
Author
User avatar
duane
Posts: 266
Joined: Sun May 20, 2007 3:08 pm

Anyone using Android for X86? profile problem

#1 Post by duane »

I have been using Android for x86 in Virtual Box. When I set it up it asked for my name.
So it has me logged in by my name.
Later I got this message when I tried to launch Google browser on the same computer.

"Google Chrome
The profile appears to be in use by another Google Chrome (16037) on another computer (calvin). Chrome has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile you can unlock the profile and relaunch Chrome."

The options are
Quit
or
Unlock Profile and Relaunch

Since there is no way to use Android without being signed in I assume my options are to hit the Unlock the Profile and Relaunch assuming I am out of Android in VBox or create another user in Android and delete my original one so I won't have this conflict in the future.

Anyone run into this before?
Lenovo M92p Quad Core i5 3470 3.2Ghz
Top
TauTsar
Posts: 38
Joined: Thu Jun 21, 2018 4:49 am

Re: Anyone using Android for X86? profile problem

#2 Post by TauTsar »

I received the same message when launching Chromium in Virtual Box. At that point I just quit the browser so nothing would be screwed up. This wasn't using Android x86, so the problem generally applies to Virtual Box and Chromium.

Sorry this isn't a resolution.
Top
Post Reply

Return to “General”