-
Notifications
You must be signed in to change notification settings - Fork 24
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
Error at launch (fresh install) Linux Mint (Ubuntu 22.04) #270
Comments
I guess you don't have pipewire, but latest should work without that. Can you try the build in #259 ? |
I tried but :
|
But running
Result in (no more the line with pipewire error) :
|
Have you changed any permissions in flatseal/kde settings? |
I guess removing the |
Also, what's your flatpak version |
Yes, no change removing Pulseaudio from flatseal. I'm using default from my distrib packages.
Showing version of application show me interesting hints :
Thanks |
If I launch kodi via
then I hit CTRL + C before the segmentation fault, kodi launch 😮 . I have splash screen then HomeScreen but Kodi is frozen and crash after a few seconds. With the following message :
|
please update |
Updated to Flatpak 1.14.8, same result, with identical crash report |
This is Linux Mint 21.3 "Virginia" with which spin? |
I use Linux Mint 21.3 Cinnamon |
I just succeeded in compiling Kodi myself, all is working with this compiled version. Is there something I can do with this version to help you ? |
Experiencing this same issue on a fresh install on MX Linux. |
Installed linux mint 21.3 cinnamon in a vm, updated packages and installed the flatpak. Did work on first try. I'm not sure what else to try. |
Sorry I don't know what to say. I managed to compile Kodi from source and all is working fine (21 & 22 alpha). So I don't need the flatpak version anymore. But if I can help you in any way by testing something, let me know. |
Hi,
Kodi 21 crash at first launch on a fresh install on Linux Mint (Ubuntu 22.04).
Any hints to solve this ?
Thx
The text was updated successfully, but these errors were encountered: