-
Notifications
You must be signed in to change notification settings - Fork 8
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 longer starting after latest update, last message is 'failed to find primary PersonaStore' #51
Comments
This is the right bugtracker. GNOME Sofware doesn't expose "bugtracker" links currently, but hopefully will start doing so soon.
I believe |
I also have this problem. Running from the command line gives the following. I waited for a few minutes, but nothing else seemed to happen. Running on Fedora 34 x86_64.
I've tried removing the flatpak and reinstalling it with no luck. I've since downgraded to 1.58.2 (using the method here: https://docs.flatpak.org/en/latest/tips-and-tricks.html) and that now works. |
I am experiencing the same problem on Fedora 34 Workstation (x86_64). The following three lines are printed and nothing else happens.
|
|
Hi @gasinvein, I had the same problem and identified the source. The behavior of the crash reporter configuration changed [1][2]. This change causes a js error. Update: I did a little more research and found the problem to be more complex than I thought. It came up with the migration to Electron v13 [1] (with a new check in Electron), however the issue with auto-enabling crash reporting (which explains why it works with --nofilesystem=host) is caused by an old issue. I did a PR (on vscode) with a possible fix for new installations. I found two possible solutions: 1 - Disable the crash reporter:
2 - Configure the crash reporter directory (may be used the $XDG_CONFIG_HOME for config directory):
Since there is already a patch that changes the start command, I think it's just necessary to choose the proper solution and update the patch. [1] microsoft/vscode#124666 |
This error doesn't seem to happen when running Code-OSS without full filesystem access, e..g Update: |
Disabled crash reporter until we come up with a better solution. So sorry for pushing a broken update. I have a global |
I am using "Code - OSS" available in flathub. It says "This open source build of Visual Studio Code is not supported by Microsoft. Issues should be reported through linked bug tracker."
There was no linked bug tracker— so apologies if i've found my way to the wrong place, but if i did find the right place please do link to the bugtracker from the description!
OK, on to my error, there was an update to apply and i did, and then tried to start Code - OSS and it doesn't, no error printed to the screen (i have not yet restarted my computer to see if that helps).
The messages in syslog end with:
The text was updated successfully, but these errors were encountered: