Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emulator Manager + Device Manager not loading #18

Closed
samcday opened this issue Aug 15, 2020 · 3 comments
Closed

Emulator Manager + Device Manager not loading #18

samcday opened this issue Aug 15, 2020 · 3 comments

Comments

@samcday
Copy link

samcday commented Aug 15, 2020

Trying to launch either Emulator or Device Managers from Tizen Studio does nothing.

I then tried attaching a shell to the running container (docker exec -it <container id> bash) and running the emulator manager directly (~/tizen-studio/tools/emulator/bin/emulator-manager), which yielded the following output:

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  151 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  37
  Current serial number in output stream:  38

I'm guessing maybe something is up with my host X11 config? I'm running stock Ubuntu 20.04 LTS with the Nvidia proprietary drivers on a RTX 2060.

@samcday
Copy link
Author

samcday commented Aug 15, 2020

What's interesting is I can run the emulator manager directly (outside of the Docker environment) and it boots up. It then freaks out because paths are mismatched between the Docker environment and the host - but that's irrelevant. So maybe something up with the way X11 is passed through to the container?

@kamildzi
Copy link
Owner

Hello,

If the main IDE window starts up when you use runTizen.sh script, then I believe that your X11 configuration is fine.

I have installed Ubuntu 20.04 inside VirtualBox, hoping that I will be able to reproduce the issue.
Unfortunately I wasn't able to reproduce this. Installation inside VM went fine and the problem didn't occurred for me.

I am not really sure what might be causing the issue, but I think that I have found something interesting.
Please check out following issue, it seems to be related to your problem:
SoonminHwang/dockers#1

It seems like Nvidia drivers require some additional libraries to be shared with the docker container.
Solution above is to use docker volumes:
obraz

It might be worth checking. You might try to configure something similar in docker-compose.yml file:
obraz

@samcday
Copy link
Author

samcday commented Aug 17, 2020

Thanks for the fast reply! I tried some stuff similar to what you suggested already but didn't have much luck. I gave up and just installed Ubuntu 16.04 natively to finally get a working Tizen Studio. Thanks anyway! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants