-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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
No prompt when selecting "Open File" or "Open Folder" within VSCode on Linux arm64 ubuntu using proot #228965
Comments
Any update on this? I can provide any logs if needed |
Is the dialog not opening at all or opening behind the main window? Can you please follow the steps in https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues to get at more details around the crash and attach the result here? Thanks! |
I posted on Reddit and someone mentioned this as well. So I minimized VSCode and it would appear the dialog is not opening at all
I tried to follow the steps, but no crash log was generated. My guess is simply because it doesn't crash lol. It just does nothing. It still runs and everything is fine, just without the file open/folder open dialog showing Is there a way to put it into verbose logging mode? Or something similar? Thanks for the update! I'm more than willing to generate/test anything you need! |
Please see if you can find any logged output that could help us find the source of the issue:
Thanks! |
Sorry for the delay here, could you also try our insiders version https://code.visualstudio.com/insiders and confirm if the issue is present. |
Hey friends! Thanks for the --verbose switch. Can't believe I didn't try that myself lol. After running code --verbose, I was able to see the logs, the error comes from this: Which I have been having other issues with /proc stuff in this build. But found solutions for. I have been using andronix cause I found it first, this lead me to discover I tested out an installation of ubuntu under proot-distro, and vscode successfully shows the open file dialog. Also, weirdly, the error was output to the terminal, instead of the log files. So I redirected all output to a file instead. Here it is: I guess this can be marked solved then. Not sure if its worth updating vscode to be able to open dialogs without the /proc accessor. Which, maybe it is cause all other programs can open files like geany, mousepad, etc. Its up to you. But I think I will go ahead and get proot-distro setup for myself. Which ultimately fixes this issue |
Glad you were able to identify the issue.
We don't have control over this, it is a call made by the portal implementation on the distro. |
I see! Thanks a lot for helping me figure it out and find a solution! Seriously appreciate it |
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: