-
Notifications
You must be signed in to change notification settings - Fork 23
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
[BUG] unexpected keyword argument thread_local while starting app from flatpak #377
Comments
I can't replicate it locally although in case it becomes relevant, in my case the flatpak is installed as |
Console logs were more useful than the ones in the dialog:
Based on path it was Workaround is to disable home directory access via Flatseal. |
I cannot see why it would load something outside of the flatpak environment unless it is configured in your environment. Your suggestion to unset Restricting access to the user's home folder is not something we can easily do because we need it to access Steam's directories for proton and compatibility tools in general. |
…rectory Should work around RareDevs/Rare#377
Can you please test the build from the flatpak PR above using the link to the test build to see it actually works around the issue? Generally though, Rare's flatpak package is lacking in other areas too. |
I tested: Still crashing but I don't think Another suggestion Stable:
Test:
|
So In my case, running produces the following and with The other thing I can think of is that you (though installing packages through The last thing is setting I will add the last one in the flatpak manifest too just to be sure. |
It works: no crash! Thanks for the help in likely rare (pun intended) bug :) Now
|
Awesome, glad it works now! I will go ahead and keep this open until the flathub PR is is merged for tracking purposes. |
Describe the bug
Crash while staring rare freshly installed from flatpak.
Relevant code:
Rare/rare/lgndr/lfs/lgndry.py
Lines 11 to 12 in 59eee7e
To Reproduce
Steps to reproduce the behavior:
System information
Please complete the following information
Error message
The text was updated successfully, but these errors were encountered: