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

QStandardPaths: wrong permissions on runtime directory /run/user/1000/ 0755 instead of 0700 #1111

Open
jiaweiz9 opened this issue Dec 26, 2023 · 5 comments
Labels

Comments

@jiaweiz9
Copy link

jiaweiz9 commented Dec 26, 2023

When running rviz2 on WSL2:
QStandardPaths: wrong permissions on runtime directory /run/user/1000/, 0755 instead of 0700
[INFO] [1703573194.517531901] [rviz2]: Stereo is NOT SUPPORTED
[INFO] [1703573194.517620901] [rviz2]: OpenGl version: 4.2 (GLSL 4.2)
[INFO] [1703573194.556220302] [rviz2]: Stereo is NOT SUPPORTED

Same issue happens when running rqt, however running gazebo-classic is okay.

platform: windows 11 wsl2 Ubuntu 22.04.3 LTS (Jammy Jellyfish)
qt version: QMake version 3.1; Using Qt version 5.15.3
ros2 version: humble

It looks like something wrong when running Qt libraries. Qt needs more permissions on that directory? Really appreciate any suggestions

@clalancette
Copy link
Contributor

We don't regularly test RViz on WSL2, so I don't think we have a lot of good advice here. If you figure it out, please feel free to update this issue or add some documentation to http://docs.ros.org/en/rolling/How-To-Guides/Installation-Troubleshooting.html

@OneCraftZRX
Copy link

just run chmod 0700 /run/user/1000/ to fix it

@surfaceowl
Copy link

the fix chmod 0700 /run/user/1000/ is only temporary for that shell session, as the 1000 directory is recreated at reboot with 0755 permissions every time. Perhaps the app should be changed to look for permissions of at least 0700, rather than exactly 0700, so that users with default permissions at 0755 for 1000 dir would pass.

@RAYaRayaRay
Copy link

I'm having the exact same issue and I've searched everywhere, waiting for an answer.

@nicholascabrera
Copy link

I added chmod 0700 /run/user/1000/ to .bashrc and I haven't encountered the problem again

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

No branches or pull requests

6 participants