-
Notifications
You must be signed in to change notification settings - Fork 13
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
wip: build from source #172
Conversation
Started test build 164269 |
Started test build 164270 |
Build 164269 failed |
Build 164270 failed |
Started test build 164319 |
Started test build 164325 |
Build 164319 successful
|
Build 164325 successful
|
Started test build 164382 |
Build 164382 successful
|
Started test build 164746 |
Build 164746 failed |
Started test build 164748 |
Build 164748 successful
|
@nehemiagurl here's a workaround: https://youtu.be/Sungl8gWU_8?si=_foyH8Z1mI0eiYUR&t=129 |
@nehemiagurl Looks like something similar to #154, which I cannot debug because I neither daily drive KDE nor have I been able to reproduce it. Looks like this on my kde testing (fedora, default configuration): Probably look there for more guidance, I am not sure if there is anything I can do in the flatpak to fix this, seems something to do with kde not being able to resolve the app id correctly. |
well, the issue seems to have resolved itself after a restart. might have just been an issue switching from the old pyenv shortcut to the flatpak shortcut 🤷♀️ |
closes #125, #162
obseletes #32, #31, #17, #163