[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #19 from Camille Bissuel --- Another user (Jasper Mattsson) confirmed this is also happening with a Lenovo Thinkpad Yoga S13 : https://bugreports.qt.io/browse/QTBUG-54085 In a desperate attempt (because this is really annoying for my daily

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #22 from Camille Bissuel --- @Dimitry I can't reproduce with the Appimage, because I didn't found which QT package is responsible for a real touch input since I reinstalled my whole distribution (I can't pinch to zoom in Krita now)... And I

[krita] [Bug 368789] New: Can't modify a Clone brush: the Clone engine Painting mode options can't be checked

https://bugs.kde.org/show_bug.cgi?id=368789 Bug ID: 368789 Summary: Can't modify a Clone brush: the Clone engine Painting mode options can't be checked Product: krita Version: 3.0.1 Platform: Other OS: Linux

[krita] [Bug 368789] Can't modify a Clone brush: the Clone engine Painting mode options can't be checked

https://bugs.kde.org/show_bug.cgi?id=368789 --- Comment #2 from Camille Bissuel --- Arg... I searched but didn't found the other bug. Sorry for the duplicate and thanks mvowada ! -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #24 from Camille Bissuel --- Hi Dimitry, sorry if I have been unclear. Yes, I ran the Appimage (and the Alpha 2 equally). they both work, as my packaged Krita. But none of these are actually correctly enabling touch events, so I can't repr

[krita] [Bug 362869] Shortcuts not working after Configure Krita

https://bugs.kde.org/show_bug.cgi?id=362869 --- Comment #7 from Camille Bissuel --- By downloading the file, and opening it with Totem player, I was able to see it (but it's crashing VLC).… The video itself is nicely done by the way ! I tried to reproduce under Antergos Linux with Krita 3 , but

[krita] [Bug 342005] Touch support for pan, zoom, rotation, etc.

https://bugs.kde.org/show_bug.cgi?id=342005 Camille Bissuel changed: What|Removed |Added CC||welc...@nylnook.com --- Comment #10 from Cami

[krita] [Bug 363225] Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #11 from Camille Bissuel --- As if it's not awful enough, the bug occur even if I disable touch events with : xsetwacom set "Wacom Cintiq 27QHD touch Finger touch" Touch off confirmed with Krita 3 release too… -- You are receiving this ma

[krita] [Bug 363225] Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #12 from Camille Bissuel --- Can't reproduce the steps at comments 7 and 8 with a Wacom Cintiq Companion 2 under Windows 10. It's probably Linux only. -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 363225] QT5 under Linux get stuck in "clicking" state, and Krita become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 Camille Bissuel changed: What|Removed |Added Summary|Sometimes the pen inputs|QT5 under Linux get stuck |

[krita] [Bug 363225] QT5 under Linux get stuck in "clicking" state, and Krita become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #13 from Camille Bissuel --- I installed the latest plasma desktop, tested Krita with it and the bug occurred, and the whole Plasma desktop became totally stuck in clicking state. So I was clicking everywhere by simply hovering any interfac

[krita] [Bug 363225] QT5 under Linux get stuck in "clicking" state, and Krita become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #14 from Camille Bissuel --- After a discussion on the Linux Wacom mailing list : https://sourceforge.net/p/linuxwacom/mailman/message/35151033/ Jason Gerecke, the Linux Wacom maintainer was able to reproduce on a Cintiq 24 HD Touch and conf

[krita] [Bug 363225] QT5 under Linux get stuck in "clicking" state, and Krita become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 Camille Bissuel changed: What|Removed |Added Version|3.0 Beta|3.0 -- You are receiving this mail because:

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #16 from Camille Bissuel --- So, what can I do to help more ? Do you need more logs ? On which hardware did you try to reproduce ? What do you think of Jason Gerecke insight : "It almost sounds like Qt is dropping events from other devices

[krita] [Bug 363283] Mouse cursor occasionally being displayed in brush mode

https://bugs.kde.org/show_bug.cgi?id=363283 --- Comment #15 from Camille Bissuel --- I'm sorry I still can't reproduce with your file, but I confirm it happened to me also to see the system cursor after saving. And we both use Gnome 3. I confirm also this tend to happen after some time using Krit

[krita] [Bug 363225] Qt5 under Linux get stuck in "clicking" state, and Krita become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #18 from Camille Bissuel --- Thanks Tyson ! -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 363225] New: Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 Bug ID: 363225 Summary: Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable Product: krita Version:

[krita] [Bug 363225] Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #1 from Camille Bissuel --- Video uploaded here (file was too large) : https://drive.google.com/open?id=0B-5J--XsvWh-LWFVM0pjRTdSa0E -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 363225] Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #2 from Camille Bissuel --- For lsmod, xinput, and xinput list-props : https://paste.kde.org/pikypoadn a tablet log event where the strange behavior partially occured, and finished by a crash… : https://paste.kde.org/pvgt2lcra I'll try to

[krita] [Bug 363225] Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #4 from Camille Bissuel --- Created attachment 99092 --> https://bugs.kde.org/attachment.cgi?id=99092&action=edit krita bug363225 better tablet log events So here is a more genuine tablet log where the bug occured from krita start. For t

[krita] [Bug 363225] Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #5 from Camille Bissuel --- Happen both with open source ati radeon drivers and amdgpu drivers (My card is a Radeon R9 290) -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 363320] New: Very bad performances on large files (can't draw)

https://bugs.kde.org/show_bug.cgi?id=363320 Bug ID: 363320 Summary: Very bad performances on large files (can't draw) Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severi

[krita] [Bug 363320] Very bad performances on large files (can't draw)

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #2 from Camille Bissuel --- No it's not a duplicate : you can see a small monitor (gnome system-monitor extension) in the top right in the video : green is for RAM, it's not even full, and SWAP appear in violet right to it if used. Take you

[krita] [Bug 363320] Very bad performances on large files (can't draw)

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #4 from Camille Bissuel --- Overall it's good, but I hit very bad bugs… Maybe it's just with my config… but I can't tell how it's specific… maybe an update in a library on Arch which is not already released on other distribs ? Or because I'

[krita] [Bug 363320] Very bad performances on large files (can't draw)

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #6 from Camille Bissuel --- I have 16 Gig of RAM… I tried to use default in the performance tab, and I try increased them almost to a maximum, and it doesn't change anything. I need to reinstall Krita 3 to provide a screenshot, I'll try with

[krita] [Bug 363320] Very bad performances on large files (can't draw)

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #7 from Camille Bissuel --- Created attachment 99097 --> https://bugs.kde.org/attachment.cgi?id=99097&action=edit screenshot of default performance tab Not more luck with the RC1 appimage -- You are receiving this mail because: You are

[krita] [Bug 363320] Very bad performances on large files (can't draw)

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #8 from Camille Bissuel --- Created attachment 99098 --> https://bugs.kde.org/attachment.cgi?id=99098&action=edit screenshot of upgraded performance tab -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 363320] Very bad performances on large files (can't draw)

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #11 from Camille Bissuel --- Cross posts ;) Sorry to bring bad news in such a positive moment for Krita ;( -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 363320] Very bad performances on large files (can't draw)

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #9 from Camille Bissuel --- By the way, disable progress reporting doesn't affect this (nor the other logging or disable vector optimizations) -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 363320] Very bad performances on large files (can't draw)

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #13 from Camille Bissuel --- Your last comment made me do one last test : Open other big files in Krita 3 RC1 (based on the same 8K template). Interestingly, only the file created today with Krita 3 triggered this bug. Older files created wi

[krita] [Bug 363320] Very bad performances on large files (can't draw)

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #15 from Camille Bissuel --- Another idea : the original very rought sketch in this file was done with mypaint in the .ora format. I add it to the Drive (named "croquis-mlle-solange-4.ora"). So one layer in the kra file is coming from ora.

[krita] [Bug 363320] Very bad performance on some large files

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #21 from Camille Bissuel --- It probably make no difference, but I don't remember I have used any layer style in this file… and I don't find any style by opening the document. I may have opened the layer style panel… but by accident, I didn'

[krita] [Bug 363320] Very bad performance on some large files

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #23 from Camille Bissuel --- Investigating further, I tried to compare the file with others… and it is set to an unusual resolution of 75 ppi : I suppose this is coming from MyPaint because I didn't set it up. If I change the resolution to

[krita] [Bug 363320] Very bad performance on some large files

https://bugs.kde.org/show_bug.cgi?id=363320 --- Comment #26 from Camille Bissuel --- I just compiled the latest Krita, and I confirm it's fixed ! Many thanks to both of you Boud and Dmitry, even I don't have any clue how you actually fixed that ;) -- You are receiving this mail because: You are

[krita] [Bug 360785] Fill layers not updating

https://bugs.kde.org/show_bug.cgi?id=360785 Camille Bissuel changed: What|Removed |Added CC||welc...@nylnook.com --- Comment #7 from Camil

[krita] [Bug 363468] New: No preview of the "Greater" Blending mode in the brush preset editor depending on the brush engine

https://bugs.kde.org/show_bug.cgi?id=363468 Bug ID: 363468 Summary: No preview of the "Greater" Blending mode in the brush preset editor depending on the brush engine Product: krita Version: git master Platform: Other

[krita] [Bug 363178] Some brush settings can change weirdly when using toolbar sliders or shift-drag resize

https://bugs.kde.org/show_bug.cgi?id=363178 Camille Bissuel changed: What|Removed |Added CC||welc...@nylnook.com --- Comment #2 from Camil

[krita] [Bug 363225] Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #6 from Camille Bissuel --- May be related to Bug 344415 (can't reproduce) Seem to happen when switching from pen to mouse or from mouse to pen. -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 363225] Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #7 from Camille Bissuel --- I'm trying to reproduce… and I'm close to it but a partial behaviour can be obtained like this : 1/ pen away from the tablet, zoom or unzoom with a touch pinch 2/ holding the touch event, let the pen enter tablet

[krita] [Bug 363225] Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 --- Comment #8 from Camille Bissuel --- A variant without touch events : 1/ pan on the canvas with the middle mouse button 2/ while panning with the mouse, let the pen enter tablet detection over the interface 3/ pen cursor is locked in an "always panni

[krita] [Bug 351434] [AMD] Visibility of Liquify transformations of transform mask depends on view scaling size

https://bugs.kde.org/show_bug.cgi?id=351434 Camille Bissuel changed: What|Removed |Added CC||welc...@nylnook.com --- Comment #8 from Camil

[krita] [Bug 362869] Shortcuts not working after Configure Krita

https://bugs.kde.org/show_bug.cgi?id=362869 Camille Bissuel changed: What|Removed |Added CC||welc...@nylnook.com --- Comment #4 from Camil

[krita] [Bug 363470] Krita crashes after drag&drop specific *.kra over the canvas to insert as layers

https://bugs.kde.org/show_bug.cgi?id=363470 Camille Bissuel changed: What|Removed |Added CC||welc...@nylnook.com --- Comment #3 from Camil

[krita] [Bug 363468] No preview of the "Greater" Blending mode in the brush preset editor depending on the brush engine

https://bugs.kde.org/show_bug.cgi?id=363468 --- Comment #3 from Camille Bissuel --- Ok, fine for me ;) -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 363283] Mouse cursor occasionally being displayed in brush mode

https://bugs.kde.org/show_bug.cgi?id=363283 --- Comment #8 from Camille Bissuel --- Can't reproduce under Antergos Linux with QT 5.6 and a git complied Krita from yesterday… Is this with a wacom tablet ? -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 363225] Sometimes the pen inputs events are locked in "clicking" state on the Krita interface, and the interface become unusable

https://bugs.kde.org/show_bug.cgi?id=363225 Camille Bissuel changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

https://bugs.kde.org/show_bug.cgi?id=359030 --- Comment #10 from Camille Bissuel --- Many thanks to both of you ! I've just complied a fresh Krita 3 with AUR https://aur.archlinux.org/packages/krita-git/ to test your work … and parallel processing is now working, it's great ! BUT : Setting expl

[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread

https://bugs.kde.org/show_bug.cgi?id=359030 --- Comment #13 from Camille Bissuel --- The two filters where I can set up the rationalization number I found are Artistic > Dream smoothing Repair > Smooth [thin brush] as mentioned above ;) There may be more, but I can't find any other right know… m

[krita] [Bug 345055] On-canvas color selectors doesn't disappear if invoked while panning

https://bugs.kde.org/show_bug.cgi?id=345055 Camille Bissuel changed: What|Removed |Added Severity|major |minor --- Comment #9 from Camille Bissuel --

[krita] [Bug 362704] New: Can't hide Assistant Previews with the "View" menu

https://bugs.kde.org/show_bug.cgi?id=362704 Bug ID: 362704 Summary: Can't hide Assistant Previews with the "View" menu Product: krita Version: 3.0 Beta Platform: Other OS: Linux Status: UNCONFIRMED Severit

[krita] [Bug 361653] Show Painting Assistants has no effect

https://bugs.kde.org/show_bug.cgi?id=361653 --- Comment #4 from Camille Bissuel --- Sorry for the duplicate… was working for me on 2.9, but is not on 3.0 under Antergos (Arch linux). -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 354946] "Could not save" error is not a way to get out of endless computation...

https://bugs.kde.org/show_bug.cgi?id=354946 --- Comment #5 from Camille Bissuel --- Great, thank you ;) -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 359030] New: G'Mic for Krita is limited to one CPU thread

https://bugs.kde.org/show_bug.cgi?id=359030 Bug ID: 359030 Summary: G'Mic for Krita is limited to one CPU thread Product: krita Version: 2.9.11 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED S