Open glassez opened 1 year ago
Installing org.qbittorrent.qBittorrent.Debug
should help.
Installing
org.qbittorrent.qBittorrent.Debug
should help.
Sorry, I'm not familiar with Flatpak ecosystem. What is org.qbittorrent.qBittorrent.Debug
? And if it really allows qBittorrent (Flatpak) to work correctly, why is it not an integral part of it?
It's extension which contains debug symbols thus should make function names available in stacktrace. It won't fix the crashes.
It won't fix the crashes.
Of course 😉 I mean, why is it not included in the main qBittorrent package if it is required for the correct operation of qBittorrent STACKTRACE feature (which is enabled in qBittorrent Flatpak build)?
Because it's 10x size of current qbitorrent package and when app doesn't crash it doesn't sever any purpose. On ubuntu or other linux distro you need to download debug symbols separately as well.
Some more info about debugging flatpaks can be found here: https://docs.flatpak.org/en/latest/debugging.html
I'm not sure if the stacktrace is even broken here since the original report came from unrelated package: https://github.com/qbittorrent/qBittorrent/issues/18663#issuecomment-1458786887
I'm not sure if the stacktrace is even broken here since the original report came from unrelated package
As I said above I'm not familiar with Flatpak ecosystem. Forgive me for my ignorance.
qBittorrent flatpak provides "broken" stacktrace output when crashed (function names aren't shown). E.g.: https://github.com/qbittorrent/qBittorrent/issues/18663.