-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Clapper flatpak won't launch on NixOS #389
Comments
I do not think this is the same issue here. We do not use Qt but GTK instead. If this was a fresh install from store, a reboot might fix this. I have actually seen issues where newly installed apps that launch with D-Bus need to restart D-Bus service for it to work with them for some reason. |
A reboot did not help, nor did an uninstall + reboot + reinstall + reboot. If I click the icon to launch Clapper, it immediately, silently fails to launch. If I try to open an associated media file, it shows a spinner if I hover over my panel, but silently fails after trying for ~15s. Is there anything I can do to diagnose the issue further? |
In this case, the best place to look at what is going on on your system is probably |
The guilty error
I'm on NixOS so I'm guessing that has something to do with it. I tried doing it extra clean with a full If I had to guess, maybe Clapper (or the flatpak) writes some hardcoded paths somewhere? |
Clapper also uses Dunno when these fixes reach end users, not really familiar with NixOS. |
I'll try a nixos-update later tonight. If that doesn't fix it, It'll probably be fixed with 23.11 (current is 23.05 but 23.11 will launch very soon). Thanks for bearing with me and finding the relevant NixOS problem! I'll link the relevant issue just for posterity: NixOS/nixpkgs#138956 Edit 2023/12/02: isn't fixed in NixOS 23.11 so far |
The Clapper flatpak currently won't launch unless launched from the Software center or manually via the CLI.
I suspect it is the same problem the Telegram flatpak has, as it exhibits the same issues and is worked around via the same tricks.
Here is the relevant Github issue: telegramdesktop/tdesktop#27134 (comment) and they have already fixed it
The text was updated successfully, but these errors were encountered: