https://bugs.kde.org/show_bug.cgi?id=513557
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO CC| |[email protected] Status|REPORTED |NEEDSINFO --- Comment #3 from [email protected] --- There is a matching thread on KA now, anyone looking here later may want to also check there: https://krita-artists.org/t/krita-5-3-0-alpha-appimage-crashes-on-startup/157165 Having a report where someone needs specific hardware and a specific Linux distro with the correct desktop environment with the correct version makes this very hard for a developer to triage, since they would have to spend several hours setting up this specific configuration to even try to confirm it. I can tell you it works fine running Arch on an AMD machine with dwm on X11, but that’s not sufficient to confirm or deny the bug. If you just want to have the bug be confirmed, it is sufficient for someone else to reproduce it, it doesn’t need to be a developer. If you want progress on the bug, you can do the following: * Check again with the current AppImage. * Try again with a clean application data directory. You can do this by running HOME=”$(pwd)/kritahome ./Krita-*.AppImage, that’ll just create a new home directory with everything fresh. * See how it behaves with different window managers or other permutations of the prerequisites. If it reproduces with other ones, you have more of a chance that someone already has the same setup or at least is able to install something more lightweight. * Get a trace with gdb. There’s some instructions on the KDE wiki that are shown to you when reporting the bug: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
