https://bugs.kde.org/show_bug.cgi?id=395070
--- Comment #2 from Bryan Willis <forle...@protonmail.com> --- (In reply to Boudewijn Rempt from comment #1) > Outch, that's been some work! It is usually easier to just select all the > text in the terminal and paste it in the bug report. And it's a pity the > ubuntu crash dialog apparently isn't as good as the Plasma crash dialog, > which allows you to report a bug directly, and warns if the debug symbols > aren't installed. > > Which is the case here, and that means that we cannot do much with all these > screenshots :-( > > What would be best is if you could install the corresponding debug symbols > to krita, then start Krita from a terminal with gdb, like this: > > gdb krita > > on the gdb prompt type 'r' and press enter: that should start krita. > > Make sure the terminal is set to provide unlimited scrollback! > > Now reproduce the crash, and when the crash happens, in the gdb terminal type > > "set pagination off" > > then > > "thread apply all bt" > > That will scroll a lot of text over the screen, which you can cut and paste > into this bug report. Okay I've been told this before. But I have to beg here, is there any other way for you guys to get even the tinest inkling of what's going on here? The debugger from what I told absolutely fucks performance and memory. Like, I use Krita to work. I have deadlines to meet, and these bugs, from what I can tell, are sporadic and aren't easily repeatable. I don't know if I have the capability to run a massive debugger and pray for my program to fail so I can happen to have a chance at getting a log report. So I ask again, is there any other way here? Clearly Krita isn't working well on ubuntu (for me anyways) crashing is a major no no for an art program, and it would benefit everyone if we got to the bottom of this. -- You are receiving this mail because: You are watching all bug changes.
