-
Notifications
You must be signed in to change notification settings - Fork 40
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
BeeRef fails to boot on the flatpak version #75
Comments
Hey, I'm in the same case. There is complimentary info on the flatpak repo "issues" thread: flathub/org.beeref.BeeRef#2 (comment) , but it looks like it will require modification to the source code. @rbreu Hello! Can you have a look into this? |
Wow! really? interesting, if there is something I can do, just tell me! P.S: David, you're my hero! Since I started using Krita I always admired how you blended in the Krita Community, how you actively contributed to every single brush, code and setting, making comics open to everyone and at anytime, I'm reading your series "Pepper and Carrot", and I'm loving every single episode of it to the heart.. Now I'm relatively young, but one day, I'll be an artist as successful as you! I promise! And I'll be there to help you fix Krita one byte at a time! Cheers! |
Oh Wow Roland! That's so good to read 🤩 Thank you! |
Graziee!!!!! Thank you!!!!!! ❤️ |
The flatpack version was using a newer version of PyQt than I was using. I have now fixed the PyQt version in setup.py and also upgraded to the latest PyQt version, doing the according necessary fixes. |
Describe the bug
BeeRef fails to start after loading settings by using the flatpak version 0.2.0
To Reproduce
Steps to reproduce the behavior:
flatpak run org.beeref.BeeRef
Starting BeeRef version 0.2.0
Using settings: ~/.var/app/org.beeref.BeeRef/config/BeeRef/BeeRef.ini
andLogging to: ~/.var/app/org.beeref.BeeRef/config/BeeRef/BeeRef.log
Expected behavior
The program starts
Screenshots
If applicable, add screenshots to help explain your problem.
Debug log:
For crashes and similar, provide the last 20 lines or so of your debug log. To get the debug log, open BeeRef and go to Help -> Show Debug Log. If in doubt, paste the whole debug log to a paste service like paste.bin
~/.var/app/org.beeref.BeeRef/config/BeeRef/BeeRef.log:
The text was updated successfully, but these errors were encountered: