Summary: | Krita Random Crash While Idle | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Leo <leo> |
Component: | Tablets (tablet issues are only very rarely bugs in Krita!) | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | dimula73, halla, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | 3.1.2 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Krita output including crash
Krita output to shell Krita crash after turning monitors back on again. |
Description
Leo
2017-03-18 16:19:24 UTC
*** Bug 377884 has been marked as a duplicate of this bug. *** These are the official OpenSUSE packages? Does this also happen with the 3.1.2 appimage we release? (In reply to Boudewijn Rempt from comment #2) > These are the official OpenSUSE packages? Does this also happen with the > 3.1.2 appimage we release? Yes, official OpenSuse package. 3.1.2.1-2.1-x86_64 from openSUSE:Tumbleweed I am also running the appimage now to see if the same crash occurs. Give me a few days. I use Krita frequently and for long periods. Sure, that's fine! (In reply to Boudewijn Rempt from comment #4) > Sure, that's fine! Yes, I can confirm a similar crash with the most current Krita appimage. In all instances, I have file/s open that I have been working on. I will leave the computer for a break, perhaps an hour or more and return to find that Krita has crashed and no longer running. Hm... And are you using plain X11 or Wayland + X11? What desktop environment? And do you have a drawing tablet connected? The crash happens somewhere in the xcb code, apparently we get a window/widget that doesn't have a valid windowHandle. I don't have tumbleweed, just the latest leap. But I'll start krita, load some stuff and wait a while... Could you also start krita from a terminal and attach all terminal output? Especially xcb errors are interesting. (In reply to Boudewijn Rempt from comment #7) > Could you also start krita from a terminal and attach all terminal output? > Especially xcb errors are interesting. (In reply to Boudewijn Rempt from comment #6) > Hm... And are you using plain X11 or Wayland + X11? What desktop > environment? And do you have a drawing tablet connected? > > > The crash happens somewhere in the xcb code, apparently we get a > window/widget that doesn't have a valid windowHandle. > > I don't have tumbleweed, just the latest leap. But I'll start krita, load > some stuff and wait a while... loginctl show-session 2 -p Type Type=x11 Desktop: KDE 5 Plasma No drawing tablet. =( I want one. Created attachment 104725 [details]
Krita output including crash
This output from Krita also includes when it crashed as I reported.
Created attachment 104726 [details]
Krita output to shell
This is the output from Krita to the shell, without any crash.
Looks like it is *not* wayland, but some problem is XCB... QXcbConnection: XCB error: 3 (BadWindow), sequence: 56311, resource id: 34089088, major code: 40 (TranslateCoords), minor code: 0 Leo, does your computer sleeps/hibernates in the meantime? (In reply to Dmitry Kazakov from comment #11) > Looks like it is *not* wayland, but some problem is XCB... > > QXcbConnection: XCB error: 3 (BadWindow), sequence: 56311, resource id: > 34089088, major code: 40 (TranslateCoords), minor code: 0 > > Leo, does your computer sleeps/hibernates in the meantime? sleeps/hibernates no, but when it goes idle after 30min, I have the screen set to blank and lock. So when I log back in, Krita has already crashed. I am now running Krita 3.1.3-beta.1 appimage. (In reply to Dmitry Kazakov from comment #11) > Looks like it is *not* wayland, but some problem is XCB... > > QXcbConnection: XCB error: 3 (BadWindow), sequence: 56311, resource id: > 34089088, major code: 40 (TranslateCoords), minor code: 0 > > Leo, does your computer sleeps/hibernates in the meantime? If I turn the monitors off, and then on again, even in a short time, so hence, no lock screen, this will cause Krita to crash. This occurs with the current Krita 3.1.3-beta.1 appimage. Created attachment 105119 [details]
Krita crash after turning monitors back on again.
Um... htat's not a krita crash, it's a crash in plasmashell. Comment #14 is unrelated to the original reported crash. Reassigning back. If this crash is not caused by Krita's KisXi2EventFilter, then it is most likely an upstream (Qt) bug. I'm really sorry, but there just isn't anything we can do with this report. It's not reproducible on any of my test devices, and without a gdb backtrace we cannot even begin to figure out where the problem could be :-( |