-
Notifications
You must be signed in to change notification settings - Fork 168
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
Issue starting flatpak on Fedora 36 #895
Comments
Hey! Flatpak is running for me on F36. Same version. @averyfreeman are you still experiencing this issue? BTW now that upstream is not dead but maintained, we can think about unretiring the RPM package. |
@averyfreeman could your issue be #683 by any chance? @gombosg for the Fedora RPM packaging, we'd be happy to see that happen, see also the work that some people had started in #709, maybe you can help there? |
Nope, I had uninstalled it because I couldn't get through startup. I just installed it again as a user flatpak from flathub, same error:
I noticed I was having an issue opening remmina flatpak, too, which I hadn't in the past. Seemed to alleviate the problem by enabling access to system libraries. I'm on a new installation of F36 and have been installing all my flatpaks as user to make migrating easier. Another thing I noticed is the system python version is 3.10 while GTG is looking for 3.9. |
Here's gmessages output in case that helps |
As an added info, my system Python version is 3.10.4, too, and GTG is working fine. @averyfreeman let's rule out Python version issues:
If it's not Python version, then it can be some config reading isse? 🤔 |
Sorry for lateness of reply, haven't been on GH in a while. I'm really not sure tbh, I have a vanilla Fedora 36 installation, so there's nothing extraordinary I've done with the system that would suggest it should respond differently than anyone else's.
I've run a general |
Hi @averyfreeman, I'm starting to suspect this might be the same issue as #845. Could you see if this has anything to do with your session keyring not being unlocked or being inaccessible somehow? |
Hello, sorry for the late reply. I have no idea why it would be related to my keyring being inaccessible when everything else but GTG works without issue. I don't know much about the keyring, but I did notice permissions look pretty open:
I tried running So, hopefully that answers your question a bit. I did some poking around inside the flatpak at the code referenced in the error, it looks to me like maybe it's related to the first-run file that's created, as I still had this file from a previous installation, but not the I tried renaming I went through my tracks a bit before writing this synopsis. Not sure if this data is particularly relevant, but I thought I'd include it just in case: [earlier]
Looks good. So then, let's just run it and see if invoking it still produces the error on this new version:
I had not been aware of any manual configuration required outside of the direction of the GUI for GTG. Therefore, any changes in the config files are the result of my use of the GUI, or during installation. Here's these configuration files for your reference:
Not sure why any of the Poking around inside the flatpak:
|
Inside the Actually, it seems stuff like server and username hasn't been filled out yet, so it should be no problem to remove the entire
|
Duplicate of #845 |
Hey, was just opening program and saw this happen:
Context: Startup
Software versions:
Is flatpak:
Fedora release info:
I just tried updating all the flatpaks, there were outdated runtimes, and ran flatpak repair, and still got the same error message.
It looks like a python 3.9 error. I notice python version incompatibilities cause errors quite frequently, might just want to stick a copy of tested python version in the flatpak going forward (?)
Hope this report helps. Thanks for everything!
The text was updated successfully, but these errors were encountered: