https://bugs.kde.org/show_bug.cgi?id=498535
Ron <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO CC| |[email protected] | |z.net Status|REPORTED |NEEDSINFO --- Comment #12 from Ron <[email protected]> --- (In reply to dreamer from comment #11) > I tried running pipewire and then it did work, so maybe that's why the > appimage is failing?. I doubt it's *why* the AppImages are failing for you, but I wouldn't be surprised to learn those two things are somehow related in the grander scheme of things. Basically, what it boils down to, if you've been having this problem for over a year with multiple Kdenlive and Debian releases, is that it's going to be something very specific to your machine, and more specifically probably very specific to something that *you* have done to it, either accidentally or deliberately. And we can't possibly guess what that is going to be if you don't put in some legwork to try and isolate and debug this yourself, because nobody else can reproduce it. I've been using all of those AppImages with all of those Debian versions myself without any problem at all, as have others, and there's been no other reports of trouble like this. So you need to figure out what it is that makes this machine of yours the special snowflake that it is. I'd probably put my first bet on something like an overzealous apparmor configuration, or some 3rd party proprietary driver or package you installed - but they are just guesses because there is not enough information here to do more than that. But if you figure out what it is, and that reveals something we might be able to improve about the binaries we release, then we have something that's actionable by *us*, but at the moment, there is nothing here that anyone else can use to learn more about this problem because it's not happening to anyone else and you haven't explained what someone else can do to reproduce it. Sorry. But until or unless we get past that information gap, there's not a lot that we can do from our end. I'd start by isolating anything external or Clever that you've done with this machine, especially things you did around the time you first started having this problem. -- You are receiving this mail because: You are watching all bug changes.
