Summary: | Ctrl-commands do not work at all | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | alindebe <irishmangoes> |
Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | halla, portnov |
Priority: | NOR | ||
Version: | 2.9.4 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
alindebe
2015-07-10 15:07:09 UTC
When I say simultaneous installation, I mean sequential. And when I say tablet, I mean an Intuos5 drawing tablet (and not a tablet computer or anything else). This seems to be duplicate of https://bugs.kde.org/show_bug.cgi?id=320423. Yup, it appears this is indeed related to that. I have an Arabic layout as my default, and even when English is the active layout it still has a problem. Changing the order in my keyboard settings so that English is on top (and thus default) fixed the issue. I'm not sure I want to mark this as Resolved since putting a latin-alphabet keyboard as default is a workaround, not a fix, but maybe it should be reassigned to a different component? Sorry to keep adding comments, but there's a little bit more to the story: Simultaneous with the ctrl-command problems, my drawing tablet had stopped responding to pressure input (so all pen strokes were 100% pressure, as if I were just clicking a mouse). I had assumed it was a small hitch related to upgrading (something something drivers something), but as soon as I fixed the ctrl-commands it turned out to be fixed as well. I have no idea why the two issues would be related in the underlying code, but it seems like they are. Pressure sensitivity is ignored when a non-latin keyboard layout is the default. Hi, I'm sorry, but this isn't a bug in Krita; it's a bug in the underlying Qt library: https://bugreports.qt.io/browse/QTBUG-32908 Yeah, that's why I said it should probably be reassigned to a different component. It's not resolved, though - it's still a bug. *** This bug has been marked as a duplicate of bug 320423 *** |