[krita] [Bug 427039] Stylus offset in Krita (bug in xf86-input-wacom)
https://bugs.kde.org/show_bug.cgi?id=427039 --- Comment #12 from Bernhard Liebl --- Hi Dmitry, this is interesting. I can confirm that I did all my tests on a HiDPI display with scale factor 2. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427039] Stylus offset in Krita (bug in xf86-input-wacom)
https://bugs.kde.org/show_bug.cgi?id=427039 --- Comment #8 from Bernhard Liebl --- Checked again: I can very reliably reproduce this issue with the flatpak version (QT 5.14.2) and with the Manjaro package version (QT 5.15). I also added a detailed description of the issue in the QT tracker at: https://bugreports.qt.io/browse/QTBUG-77826?focusedCommentId=529613=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-529613 Really hope that this thing does not get ping-ponged between QT and xf86-input-wacom. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427039] Stylus offset in Krita (bug in xf86-input-wacom)
https://bugs.kde.org/show_bug.cgi?id=427039 --- Comment #7 from Bernhard Liebl --- The QT version seems to be 5.14.2. >From the krita's flatpak manifest.json (see attachment), it includes org.kde.Platform 5.14, which on the other hand (see attachment for manifest.json of org.kde.Platform) seems to be based on QT 5.14.2. This makes me wonder whether the bug from https://bugreports.qt.io/browse/QTBUG-77826 is actually really fixed in 5.14.1, as the ticket there states. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427039] Stylus offset in Krita (bug in xf86-input-wacom)
https://bugs.kde.org/show_bug.cgi?id=427039 --- Comment #6 from Bernhard Liebl --- Created attachment 132084 --> https://bugs.kde.org/attachment.cgi?id=132084=edit manifest.json for org.kde.platform -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427039] Stylus offset in Krita (bug in xf86-input-wacom)
https://bugs.kde.org/show_bug.cgi?id=427039 --- Comment #5 from Bernhard Liebl --- Created attachment 132083 --> https://bugs.kde.org/attachment.cgi?id=132083=edit flatpak manifest.json -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427039] Stylus offset in Krita (bug in xf86-input-wacom)
https://bugs.kde.org/show_bug.cgi?id=427039 --- Comment #3 from Bernhard Liebl --- Hi Dmitry, I tried the 4.3.0 AppImage and it works out of the box. So it is a issue only with flatpak. The only reason I use flatpak and not the AppImage is that only flatpak supports the QT Breeze style (via QT_STYLE_OVERRIDE), but that's a different issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427039] New: Stylus offset in Krita (bug in xf86-input-wacom)
https://bugs.kde.org/show_bug.cgi?id=427039 Bug ID: 427039 Summary: Stylus offset in Krita (bug in xf86-input-wacom) Product: krita Version: 4.3.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: poke1...@gmx.de Target Milestone: --- SUMMARY Hi guys, just wondering if you are aware of: https://github.com/linuxwacom/xf86-input-wacom/issues/93 This is *not* a Krita bug, but I'm wondering if Krita's flatpak distro should set / mention `QT_XCB_TABLET_LEGACY_COORDINATES=1` as this fixed the issue. STEPS TO REPRODUCE 1. Use Krita 4.3.0 via flatpak on current Manjaro / Gnome Desktop 2. Use external USB Wacom tablet stylus to click user interface 3. Offset in clicks on UI OBSERVED RESULT Clicks with Stylus are offset so that Krita is basically unusable via Stylus. Strangely, the offset does not occur when drawing inside the canvas. Anyway, it's a xf86-input-wacom bug (see above). EXPECTED RESULT Correct offsets. SOFTWARE/OS VERSIONS macOS: Manjaro/ gnome ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398911] New: Top region in window will block wacom pen cursor on retina displays
https://bugs.kde.org/show_bug.cgi?id=398911 Bug ID: 398911 Summary: Top region in window will block wacom pen cursor on retina displays Product: krita Version: 4.1.1 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: poke1...@gmx.de Target Milestone: --- Here's a strange effect I observed on two retina Macs (iMac, MacBook Pro) natively running Elementary OS Loki (i.e. Ubuntu 16.04, no vm involved): https://www.dropbox.com/s/xna6kv4vdqi4ken/krita-retina.webm?dl=0 Coming from the bottom, the cursor will stop at a certain line. However, if you're already drawing, this won't happen. Also, if you come from the top, things work fine. Also, this only happens with a Wacom pen, not with a mouse. I suspect this is related to the retina screens. It doesn't happen on a regular Linux machine I work on. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387557] Chaos with working with shortcuts and simple operations on canvas.
https://bugs.kde.org/show_bug.cgi?id=387557 Bernhard Liebl <poke1...@gmx.de> changed: What|Removed |Added CC||poke1...@gmx.de --- Comment #6 from Bernhard Liebl <poke1...@gmx.de> --- Hi Kamil, can you check out krita-4.0.0-prealpha.2 from https://krita.org/en/item/4-0-development-update/ ? It seems to me the problem is fixed there (it uses QT 5.10 as opposed to the other builds, which seem to use QT 5.7). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386165] Krita Crash inside KisBrushMaskScalarApplicator::processScalar(()
https://bugs.kde.org/show_bug.cgi?id=386165 --- Comment #5 from Bernhard Liebl <poke1...@gmx.de> --- Haven't tested last two weeks, but let's close this then. If it still occurs, we'll see it again sooner or later, then have another backtrace for the updated code - I'll post that one then. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386620] Canvas framerate limiter might not be working as intended
https://bugs.kde.org/show_bug.cgi?id=386620 --- Comment #2 from Bernhard Liebl <poke1...@gmx.de> --- see https://phabricator.kde.org/D8804 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386279] Random crash in KisUpdateJobItem
https://bugs.kde.org/show_bug.cgi?id=386279 --- Comment #2 from Bernhard Liebl <poke1...@gmx.de> --- Created attachment 108602 --> https://bugs.kde.org/attachment.cgi?id=108602=edit same thing again -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386279] Random crash in KisUpdateJobItem
https://bugs.kde.org/show_bug.cgi?id=386279 --- Comment #1 from Bernhard Liebl <poke1...@gmx.de> --- Oh, I just detected some more info from the console: krita.core: BUG: The walker hasn't reached the root layer! krita.core: Start node: KisPaintLayer(0x7fa5c4bde050, name = "Layer 2") Requested rect: QRect(7929953,7471205 -4653120x-4784194) krita.core: There must be an inconsistency in the walkers happened! krita.core: Please report a bug describing how you got this message. Segmentation fault: 11 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386279] New: Random crash in KisUpdateJobItem
https://bugs.kde.org/show_bug.cgi?id=386279 Bug ID: 386279 Summary: Random crash in KisUpdateJobItem Product: krita Version: 4.0 pre-alpha Platform: Compiled Sources OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: poke1...@gmx.de Target Milestone: --- Happened with c6473821e095b6b4462259ab119265423de80c8d The access looks like a nullptr memory exception (KERN_INVALID_ADDRESS at 0x0038). So it seems like it's inside KisUpdateJobItem::runMergeJob (inlined) and then gets a nullptr memory exception when accessing m_walker->changeRect() as m_walker is null. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386165] New: Krita Crash inside KisBrushMaskScalarApplicator::processScalar(()
https://bugs.kde.org/show_bug.cgi?id=386165 Bug ID: 386165 Summary: Krita Crash inside KisBrushMaskScalarApplicator::processScalar(() Product: krita Version: 4.0 pre-alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: poke1...@gmx.de Target Milestone: --- Created attachment 108552 --> https://bugs.kde.org/attachment.cgi?id=108552=edit Crash Log A strange crash inside KisBrushMaskScalarApplicator this morning. Actually looks like a nullptr from KisFixedPaintDevice::data() to me (as the fault is at 0x000b). Happened with 783767179388e8e48ba4e44bcb622613b27b5bd0. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385276] New: Krita canvas lags on larger displays on macOS
https://bugs.kde.org/show_bug.cgi?id=385276 Bug ID: 385276 Summary: Krita canvas lags on larger displays on macOS Product: krita Version: unspecified Platform: Compiled Sources OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: bernhard.li...@gmx.org Target Milestone: --- Krita's graphics output on macOS is relatively slow, and it is very slow on 5k iMacs. This seems to be related to QT's QWidget implementation on macOS. And this is probably a well-known problem. If not, this ticket can keep track of infos about QT's state of things. Two useful pointers I found: https://forum.qt.io/topic/59578/rendering-performance-problems-on-imac-with-retina-5k/24 https://bugreports.qt.io/browse/QTBUG-44228 As QT's OpenGL compositing internally happens with and without Krita's OpenGL canvas, switching to Krita's raster canvas does not make a difference. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385238] Floating dockers not resizable on OS X
https://bugs.kde.org/show_bug.cgi?id=385238 --- Comment #2 from Bernhard Liebl <bernhard.li...@gmx.org> --- Yes, disabling the custom titlebar is the only fix in Krita, I looked at the QT code and there's no way to fix it from the outside. I'll look into titlebar disabling on OS X a bit more, it would need to only happen if palettes are floating. I also hope the QT guys take the report seriously, it's a small but highly annoying issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385238] New: Floating dockers not resizable on OS X
https://bugs.kde.org/show_bug.cgi?id=385238 Bug ID: 385238 Summary: Floating dockers not resizable on OS X Product: krita Version: 4.0 pre-alpha Platform: Other OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: bernhard.li...@gmx.org Target Milestone: --- On OS X (and maybe certain Linux window managers), floating docker windows are not properly resizable (the margin for resizing them seems to be 1 pixel wide and the resize cursor is not working properly). This is a QT bug related to custom titles, reported now as https://bugreports.qt.io/browse/QTBUG-63526. -- You are receiving this mail because: You are watching all bug changes.
