[kdenlive] [Bug 459707] New: Toggling off keyframes in Transform effect makes Size and Opacity unreachable
https://bugs.kde.org/show_bug.cgi?id=459707 Bug ID: 459707 Summary: Toggling off keyframes in Transform effect makes Size and Opacity unreachable Classification: Applications Product: kdenlive Version: 22.08.1 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: camille.mou...@free.fr Target Milestone: --- Created attachment 152445 --> https://bugs.kde.org/attachment.cgi?id=152445&action=edit With keyframes desactivated SUMMARY *** Hello folks, When disabling keyframes in Transform effect, the layout changes and makes Size and Opacity settings unreachable. Thanks ! *** STEPS TO REPRODUCE 1. Create a new project, add some footage on the timeline, add Transform effect to the clip 2. Select the clip 3. Disable Keyframes by clicking on the icon OBSERVED RESULT The keyframe part in the effect window disappears, but the Rotation setting now overlaps the Size and Opacity settings EXPECTED RESULT The keyframe part in the effect window disappears, and the Size and Opacity settings are still reachable SOFTWARE/OS VERSIONS Kdenlive: 22.08.1 Package Type: appimage MLT: 7.9.0 Qt: 5.15.5 (built against 5.15.5 x86_64-little_endian-lp64) Frameworks: 5.97.0 System: Ubuntu 22.04.1 LTS Kernel: linux 5.15.0-48-generic CPU: x86_64 Windowing System: xcb Movit (GPU): disabled Track Compositing: frei0r.cairoblend ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 459707] Toggling off keyframes in Transform effect makes Size and Opacity unreachable
https://bugs.kde.org/show_bug.cgi?id=459707 Camille changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Camille --- Tested with current appimage and it seems fixed Kdenlive: 22.11.70 (rev. 75806ee2b) Package Type: appimage MLT: 7.9.0 Qt: 5.15.5 (built against 5.15.5 x86_64-little_endian-lp64) Frameworks: 5.98.0 System: Ubuntu 22.04.1 LTS Kernel: linux 5.15.0-48-generic CPU: x86_64 Windowing System: xcb Movit (GPU): disabled Track Compositing: frei0r.cairoblend -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 460060] New: In Appimage, Online resources are listed twice
https://bugs.kde.org/show_bug.cgi?id=460060 Bug ID: 460060 Summary: In Appimage, Online resources are listed twice Classification: Applications Product: kdenlive Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: camille.mou...@free.fr Target Milestone: --- Created attachment 152623 --> https://bugs.kde.org/attachment.cgi?id=152623&action=edit Menu listing each service twice SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Launch AppImage 2. Display Online Resources (View : Online Resources) 3. Click on Service list OBSERVED RESULT Every service is listed twice (see image attached) EXPECTED RESULT Each service is listed once SOFTWARE/OS VERSIONS Kdenlive: 22.11.70 (rev. 03ccdcddd) Package Type: appimage MLT: 7.9.0 Qt: 5.15.5 (built against 5.15.5 x86_64-little_endian-lp64) Frameworks: 5.98.0 System: Ubuntu 22.04.1 LTS Kernel: linux 5.15.0-48-generic CPU: x86_64 Windowing System: xcb Movit (GPU): disabled Track Compositing: frei0r.cairoblend ADDITIONAL INFORMATION This doesn't happen with the version I build locally : Kdenlive: 22.11.70 (rev. f9a8774c1) Package Type: Unknown/Default MLT: 7.8.0 Qt: 5.15.3 (built against 5.15.3 x86_64-little_endian-lp64) Frameworks: 5.92.0 System: Ubuntu 22.04.1 LTS Kernel: linux 5.15.0-48-generic CPU: x86_64 Windowing System: xcb Movit (GPU): disabled Track Compositing: frei0r.cairoblend But this happens with the following all the appimages I tested since : kdenlive-22.04.2-x86_x64.AppImage -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 460060] In Appimage, Online resources are listed twice
https://bugs.kde.org/show_bug.cgi?id=460060 --- Comment #2 from Camille --- Merci :-) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 398589] New: Crash when trying to move color clip
https://bugs.kde.org/show_bug.cgi?id=398589 Bug ID: 398589 Summary: Crash when trying to move color clip Product: kdenlive Version: git-master Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: camille.mou...@free.fr Target Milestone: --- Hi, I compiled kdenlive from the git repo f77309cfd6a0a112f6416e4e68bf38ef46a7bcc0 (HEAD -> refactoring_timeline, origin/refactoring_timeline) Here are the steps that lead to crash : 1) Launch Kdenlive 2) Add a color clip via the menu above the bin 3) Choose green as a color (actually the color doesn't seem to matter) 4) Drag the clip on the first video track (called "V2") 5) Try to move it. 6) It crashes. Below is the terminal output. One "suspicious" part is: > Trying to construct 5 tracks. > > SUSPICIOUS: we weren't expecting a producer when parsing the timeline Just let me know if you need more info (if it's not part of the timeline corruption pb you're already trying to solve. Cheers, Camille [...] - hevc_vaapi - mjpeg_vaapi - mpeg2_vaapi - vp8_vaapi - vp9_vaapi ... kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 3776, result = 0 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit5: opened connection to :0 kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' Shortcut for action "rename" "Renommer" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. QWidget::setMinimumSize: (effect_list/QDockWidget) Negative sizes (0,-1) are not possible QWidget::setMinimumSize: (transition_list/QDockWidget) Negative sizes (0,-1) are not possible QXcbConnection: XCB error: 8 (BadMatch), sequence: 769, resource id: 50331712, major code: 155 (Unknown), minor code: 11 QFile::setFileName: File (/home/camille/.local/share/stalefiles/kdenlive/_untitled.kdenlivejIzfile_%2Fhome%2Fcamille%2FVid%C3%A9osUH3WVjIz) is already opened Loading bin playlist... // Trying to construct 5 tracks. SUSPICIOUS: we weren't expecting a producer when parsing the timeline $ Planting effect REGISTER TRACK 1 0 $ Planting effect REGISTER TRACK 2 1 $ Planting effect REGISTER TRACK 3 2 $ Planting effect REGISTER TRACK 4 3 /// requestAddBinClip "-1" /// found id "2" /// constructed Setting parent to "-1" MANAGE BIN ITEM INSERT "2" Inserting clip "2" Inserting invalid clip "2" /// added true ### JOB finished 0 ### loadjob COMMIT ### ProjectClip::setproducer ### ClipController::updateProducer ### ClipController::addmasterproducer $ Planting effect Setting parent to "-1" QPoint(0,125) MUTEX LOCK setmodel MUTEX UNLOCK setmodel MUTEX LOCK loadEffects: ### JOB finished 2 ### JOB finished 1 /// CLI DURATION: 125 qml: dropped data: 2 requestClipInsertion "2" 4 90 requestClipCreation "2" producer request 5 1 $ Planting effect // /REQUEST TL CLP REGSTR: 5 CLIPS COUNT: 0 REGISTRATION 5 ptr count 3 // FINAL MOVE: false , UPDATE VIEW: true starting to simplify updates merging changes Insert Update of item 5 to track 4 at pos 90 // /REQUEST TL CLP REGSTR: 5 CLIPS COUNT: 0 REGISTRATION 5 ptr count 2 refresh 0 1 0 124 producer request 5 1 qml: keyframe model changed qml: loaded clip: 90 , ID: 5 , index: 0 , TYPE: Color // FINAL MOVE: false , UPDATE VIEW: true /// REQUESTOING CLIP DELETION_: true starting to simplify updates merging changes Change Update of item 5 roles: StartRole /// REQUESTOING CLIP DELETION_: true starting to simplify updates merging changes // /REQUEST TL CLP REGSTR: 5 CLIPS COUNT: 0 REGISTRATION 5 ptr count 2 requestClipInsertion "2" 4 105 requestClipCreation "2" producer request 6 1 $ Planting effect // /REQUEST TL CLP REGSTR: 6 CLIPS COUNT: 0 REGISTRATION 6 ptr count 3 // FINAL MOVE: true , UPDATE VIEW: true starting to simplify updates merging changes Insert Update of item 6 to track 4 at pos 105 // /REQUEST TL CLP REGSTR: 6 CLIPS COU
[kdenlive] [Bug 398589] Crash when trying to move color clip
https://bugs.kde.org/show_bug.cgi?id=398589 Camille changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 500873] New: None of the blur effects seems to work correctly on a png with transparency
https://bugs.kde.org/show_bug.cgi?id=500873 Bug ID: 500873 Summary: None of the blur effects seems to work correctly on a png with transparency Classification: Applications Product: kdenlive Version: 24.12.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Effects & Transitions Assignee: j...@kdenlive.org Reporter: camille.mou...@free.fr Target Milestone: --- Created attachment 178988 --> https://bugs.kde.org/attachment.cgi?id=178988&action=edit Archive of a test .kdenlive project to see blur problems *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY STEPS TO REPRODUCE 1. Add a png with some transparent parts 2. Apply any of the blur effects OBSERVED RESULT The image is somehow distorted, but not the way that would be expected from a blur effect EXPECTED RESULT A proper blur effect SOFTWARE/OS VERSIONS Kdenlive: 24.12.2 Package Type: AppImage MLT: 7.30.0 Qt: 6.8.1 (built against 6.8.1 x86_64-little_endian-lp64) Frameworks: 6.10.0 System: Ubuntu 24.04.2 LTS Kernel: linux 6.11.0-17-generic CPU: x86_64 Windowing System: xcb GPU: Intel/Mesa Intel(R) Graphics (MTL) Movit (GPU): disabled Track Compositing: qtblend ADDITIONAL INFORMATION Please find attached an archive of a project to reproduce the problem. The first image is the original png. The code this image blured with Gimp. The others one the original png with various blur filter applied. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 492763] [Feature Request] Option to exclude proxy files from project archive
https://bugs.kde.org/show_bug.cgi?id=492763 Camille changed: What|Removed |Added CC||camille.mou...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 500873] None of the blur effects seems to work correctly on a png with transparency
https://bugs.kde.org/show_bug.cgi?id=500873 --- Comment #2 from Camille --- Thanks Eugen for the prompt review :-) Here is my understanding about BoxBlur vs box_blur : In Kdenlive interface, the filter is called `BoxBlur`, but in the `.kdenlive` file, it is noted as `box_blur` ( box_blur), so I think it is not related to the deprecated MLT Filter: BoxBlur. Currently, it is linked to this page https://docs.kdenlive.org/en/effects_and_filters/video_effects/blur_and_sharpen/boxblur.html, and I think that this is correct. So I think the filter should be renamed "Box Blur" (with a space) in the UI and in the documentation. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 507495] 25.08-RC1 - Mask apply doesn't work.
https://bugs.kde.org/show_bug.cgi?id=507495 Camille changed: What|Removed |Added Version First|git-master |25.07.90 Reported In|| -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 507495] 25.08-RC1 - Mask apply doesn't work.
https://bugs.kde.org/show_bug.cgi?id=507495 --- Comment #1 from Camille --- Created attachment 183519 --> https://bugs.kde.org/attachment.cgi?id=183519&action=edit File with no problem -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 507495] New: 25.08-RC1 - Mask apply doesn't work.
https://bugs.kde.org/show_bug.cgi?id=507495 Bug ID: 507495 Summary: 25.08-RC1 - Mask apply doesn't work. Classification: Applications Product: kdenlive Version First git-master Reported In: Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Audio Effects & Transitions Assignee: j...@kdenlive.org Reporter: camille.mou...@free.fr Target Milestone: --- Created attachment 183518 --> https://bugs.kde.org/attachment.cgi?id=183518&action=edit File with the problem Hello folks, STEPS TO REPRODUCE 1. Create a green color clip 2. Add it to the timeline 3. Add an Alpha Shape (Mask) effect on the clip in the timeline 4. Add a Colorize color effect on the clip in the timeline 5. Add a Mask apply effect on the clip in the timeline OBSERVED RESULT In the project monitor, a blue rectangle on black background EXPECTED RESULT In the project monitor, a blue rectangle on green background SOFTWARE/OS VERSIONS Kdenlive: 25.07.90 MLT: 7.33.0 FFmpeg KDE Frameworks: 6.16.0 Qt: Using 6.8.3 and built against 6.8.3 Ubuntu 25.04 (Wayland) Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.14.0-24-generic ADDITIONAL INFORMATION You'll find attached 2 project files - the first one created with kdenlive-25.04.3-x86_64_b27c4a7b2c8c5684c3aa5d1e3b32e2df.AppImage - the second one created with kdenlive-25.08-RC-linux-gcc-x86_64_503ab06ddedad5801e3f64940f60dc77.AppImage By comparing the files, you'll notice that for Mask apply, you have 0 rgba mask_apply mask_apply when it should be frei0r.composition rgba mask_apply mask_apply (the difference being frei0r.composition instead of 0 ) If I correct the file by hand, it is correctly interpreted, so the problem is only during the creation. Ping me if you need any additional info. Thanks ! Camille -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400241] New: Can't double click to edit text
https://bugs.kde.org/show_bug.cgi?id=400241 Bug ID: 400241 Summary: Can't double click to edit text Product: krita Version: 4.1.5 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: welc...@nylnook.art Target Milestone: --- I'm testing the new 4.0 text tool, and its works much better than before, but there is a small usability issue : Once a text is created, I can't double click to edit it, as explained in the wiki (https://docs.krita.org/en/reference_manual/tools/text.html) But there is a workaround : it works if I select it and press "Enter". Tested under Ubuntu 18.04 with Krita 4.1.5 PPA Thanks again ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400243] New: Should not have to select text globally in the text editor window to edit it
https://bugs.kde.org/show_bug.cgi?id=400243 Bug ID: 400243 Summary: Should not have to select text globally in the text editor window to edit it Product: krita Version: 4.1.5 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: welc...@nylnook.art Target Milestone: --- Testing the new 4.0 text tool, another usability issue bother me : If I edit a text (clicking on it, then pressing Enter and seeing the text editor window), changes like selecting another font doesn't apply to the text if I don't select it first. So we have to select it on the main canvas to edit it once, then select it globally again (Ctrl+A) in the editor window to edit it. It's very slow and it's not obvious, and my first impression was "it doesn't work". I suggest change to text apply globally to all text in the editor window if no text is selected inside it (it's interesting to apply some change to part of it, but it shouldn't affect basic usage). Tested with Krita 4.1.5 under Ubuntu 18.04 with PPA -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400243] Should not have to select text globally in the text editor window to edit it
https://bugs.kde.org/show_bug.cgi?id=400243 --- Comment #3 from Camille Bissuel --- Hi Scott, yes it would be a good improvement, and would work for my needs, but I'm asking myself if having a "text-over" window in the Gimp style would not be better if you plan to separate basic and advanced text tools ;) Thanks for your proposal anyway, it's nice to ear I'm not the only one interested ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400243] Should not have to select text globally in the text editor window to edit it
https://bugs.kde.org/show_bug.cgi?id=400243 --- Comment #5 from Camille Bissuel --- You convinced me : I agree the UI should not rotate with the text, so it's probably better to have it in the tool options panel. Maybe the advanced text option should be in the same panel, in another tab than basic text options in a similar way than the transform tool. So you would have tree tabs in the the tool options panel if you select the text tool : basic text, advanced text (with menu entries like search and replace but with buttons) and SVG markup edit. Maybe Tyson workflow is specific to his language, but I think it's compatible with your and my workflow of board changes. So you change text globally if you have no selection, locally if you have a selection, and local edit is not removed by global edit (keep it's markup). You just need to add a button like "reset local edits" to be able to go back to global edits and remove local edits (only one global markup). It would be similar to the way Scribus handle paragraph styles and text styles, and I believe it's useful in a comic workflow when you want some effect on one word sometimes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland
https://bugs.kde.org/show_bug.cgi?id=379174 --- Comment #8 from Camille Bissuel --- Good news, Krita 4.1 is almost working with Wayland on Ubuntu 18.04. Stylus works, touch gestures are working, I only miss Rotation support for the Wacom Art Pen (see bug 396409). Maybe the borders of drawing strokes are a little too sharp using Wayland. Boud, can you explain us what is the status of Wyaland support in Krita ? Thanks in advance, Camille -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396409] New: Rotation support for Wacom Art Pen under Wayland
https://bugs.kde.org/show_bug.cgi?id=396409 Bug ID: 396409 Summary: Rotation support for Wacom Art Pen under Wayland Product: krita Version: 4.1.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: welc...@nylnook.art Target Milestone: --- Hi dear Krita Team, Good news, Krita 4.1 is almost working with Wayland on Ubuntu 18.04 (See bug 379174) ! Stylus works, touch gestures are working, I only miss Rotation support for the Wacom Art Pen. It seems that Krita is simply not using the corresponding lipinput event (see https://gitlab.freedesktop.org/libinput/libinput/issues/76). So this is an humble request to add it... and finally enjoy drawing and touching my cintiq at the same time ;) Thanks a lot -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland
https://bugs.kde.org/show_bug.cgi?id=379174 --- Comment #11 from Camille Bissuel --- OK, it works so well I through your worked in it ! I just warned Peter Hutterer you need help, but I don't know if he can spare time for that, even if I hope so ;) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388531] Brush Rotation broken with Wacom Art Pen
https://bugs.kde.org/show_bug.cgi?id=388531 --- Comment #12 from Camille Bissuel --- It appeared recently with some dependency update, I'm sorry but I suppose you have to test with Ubuntu 17.10 or an Arch-based distrib like Antergos or Manjaro... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388531] Brush Rotation broken with Wacom Art Pen
https://bugs.kde.org/show_bug.cgi?id=388531 --- Comment #14 from Camille Bissuel --- I just compiled a fresh Krita from Git, and I can confirm it work again ! Thanks a lot Dmitry, amazing work ! ;) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388531] New: Brush Rotation broken with Wacom Art Pen
https://bugs.kde.org/show_bug.cgi?id=388531 Bug ID: 388531 Summary: Brush Rotation broken with Wacom Art Pen Product: krita Version: 3.3.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: welc...@nylnook.art Target Milestone: --- Hi dear Krita team, I first reported this bug in the Linux Wacom Project, here : https://sourceforge.net/p/linuxwacom/bugs/354/ I'm using Antergos Linux 64b (Arch based) with a Cintiq 27 and an Art Pen. To test, you can get my Krita Brushes supporting rotation here : https://nylnook.art/en/blog/krita-brushes-pack-v2/ or use Wolthera Calligraphy brushes in her Inking pack : https://www.dropbox.com/s/4nj8t4538f5wx2s/Wolthera_Inking_Pack.bundle?dl=0 I had a bad surprise after an update in december, my Art Pen cursor stopped to rotate in Krita... It works in Gimp. Cursor do not rotate at all, but pressure and tilt are working as usual. It's strange because it was working with the same Krita version previously, so my best guess is that is a Krita dependency that have been updated and broke rotation. I tried to downgrade several packages with no success. After tests with Jason Gerecke, it's confirmed and it seems that the Linux Wacom drivers or Xorg are not responsible of this. Here is what he reported : "Further tests in Krita have been pretty confusing. I tried modifying one of your brushes to rotate based on "Tangential Pressure" (airbrush wheel) and was able to get that working. After restarting Krita and ensuring the brush was still set up to use "Tangential Pressure", however, I could no longer get it to work. The "Tangential Pressure" data is sent by our driver in a[5] just like "Rotation" data is, so clearly Krita can sometimes read it... I've looked through Krita's code and don't see anything /obviously/ wrong with it, but when I enable tablet debugging (CTRL+SHIFT+T and then watch console output) I notice that although it correctly reports pen pressure and tilt, other information is hit-and-miss. Sometimes I get the pen's unique ID, sometimes its reported as "0". I assume that rotation and tangential pressure would also be reported when it works, but I see "0" for these values at the moment (and haven't figured out why tangential pressure suddenly stopped working after restarting the program). I almost wonder if Krita is failing to initialize some of its variables correctly, or if it has issues when multiple tablets are plugged in... More things to test..." Please read the full bug report for details. This is pretty annoying for my drawing style, specially for inking. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388531] Brush Rotation broken with Wacom Art Pen
https://bugs.kde.org/show_bug.cgi?id=388531 --- Comment #7 from Camille Bissuel --- Amazingly, it worked again today after Krita run several hours... but I rebooted Krita to check, and it's no more working at startup... A bad initialization as Jason said ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375878] Eraser will not switch back to brush after turning Wacom pen back around
https://bugs.kde.org/show_bug.cgi?id=375878 Camille Bissuel changed: What|Removed |Added CC||welc...@nylnook.com --- Comment #6 from Camille Bissuel --- Confirmed for me with Krita 3.1.2 under Antergos linux with a Cintiq 27... Like in previous comments, removing Krita config files didn't solve the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388531] Brush Rotation broken with Wacom Art Pen
https://bugs.kde.org/show_bug.cgi?id=388531 Camille Bissuel changed: What|Removed |Added Version|3.3.2 |4.0.0-beta.1 --- Comment #8 from Camille Bissuel --- Confirmed also in Krita 4 beta 1 build from git... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 337328] Advanced color selector do not allow to show Shade selector only
https://bugs.kde.org/show_bug.cgi?id=337328 --- Comment #21 from Camille Bissuel --- Thanks a lot Anna ! and Happy new year ;) Hopefully this will land successfully into next release ;) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381204] Extract foreground [interactive] result in offset layers with G'mic
https://bugs.kde.org/show_bug.cgi?id=381204 Camille Bissuel changed: What|Removed |Added Summary|Extract foreground |Extract foreground |[interactive] result in |[interactive] result in |offset layers with G'mic|offset layers with G'mic |0.1.7 in Krita 3.1.4| Platform|Archlinux Packages |Appimage Status|RESOLVED|UNCONFIRMED Resolution|UNMAINTAINED|--- Version|3.1.4 |3.2.0-beta.2 --- Comment #4 from Camille Bissuel --- I'm sorry, this is not solved in Krita 3.2 RC3 with the new G'mic-Qt plugin, despite the result is slightly different. See attachment... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381204] Extract foreground [interactive] result in offset layers with G'mic
https://bugs.kde.org/show_bug.cgi?id=381204 --- Comment #5 from Camille Bissuel --- Created attachment 107273 --> https://bugs.kde.org/attachment.cgi?id=107273&action=edit Extract foreground [interactive] offset with Krita 3.2 RC3 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 194268] Kontact crashes at start (Kontact::Plugin::part, K*UniqueAppHandler::newInstance, Kontact::UniqueAppHandler::newInstance)
https://bugs.kde.org/show_bug.cgi?id=194268 Camille Chabot changed: What|Removed |Added CC||camillei...@videotron.ca -- You are receiving this mail because: You are watching all bug changes.
[kcontacts] [Bug 384623] New: unable to operate and/or configurate kontact
https://bugs.kde.org/show_bug.cgi?id=384623 Bug ID: 384623 Summary: unable to operate and/or configurate kontact Product: kcontacts Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: camillei...@videotron.ca Target Milestone: --- Created attachment 107815 --> https://bugs.kde.org/attachment.cgi?id=107815&action=edit Unable to work with total Kontact please see the attachment Great and many thanks Camille Chabot -- You are receiving this mail because: You are watching all bug changes.
[kcontacts] [Bug 384623] unable to operate and/or configurate kontact
https://bugs.kde.org/show_bug.cgi?id=384623 --- Comment #2 from Camille Chabot --- Hi and thank you; version is 5.2.3 Le 2017-09-12 à 10:47, Laurent Montel a écrit : > https://bugs.kde.org/show_bug.cgi?id=384623 > > Laurent Montel changed: > > What|Removed |Added > > CC||mon...@kde.org > > --- Comment #1 from Laurent Montel --- > Which version ? > -- You are receiving this mail because: You are watching all bug changes.
[kdepimlibs] [Bug 199530] Closing Kontact (and other situations) causes a crash [QCoreApplication::notifyInternal, ..., KMessageBox::createKMessageBox, ..., KABC::GuiErrorHandler::error]
https://bugs.kde.org/show_bug.cgi?id=199530 Camille Chabot changed: What|Removed |Added CC||camillei...@videotron.ca -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 385057] New: unable to operate and/or configurate kadress book; as soon as click to open, it's krash...
https://bugs.kde.org/show_bug.cgi?id=385057 Bug ID: 385057 Summary: unable to operate and/or configurate kadress book; as soon as click to open, it's krash... Product: kdebugsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: camillei...@videotron.ca Target Milestone: --- Created attachment 108012 --> https://bugs.kde.org/attachment.cgi?id=108012&action=edit unable to config adress book Unable to config. KDEadress book; ( see file ...I am working with Linux MInt sarah and KDE 5.6 i AM ALSO TRYING TO config and OPERATE kmail AND Kadresse book Many thanks to allow us to have ''free internet'' Camille Chabot -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 382635] kaddressbook crashes when I start it
https://bugs.kde.org/show_bug.cgi?id=382635 --- Comment #13 from Camille Chabot --- Thank you M. Feck Crashing conditions still exist. As i open Kadress book at tool menu with Kmail open it still crash Les paquets contenant les informations de débogage pour l'application et les bibliothèques suivantes sont absentes : * /usr/bin/kaddressbook * /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5 * /usr/lib/i386-linux-gnu/libQt5XcbQpa.so.5 * /usr/lib/i386-linux-gnu/libQt5Widgets.so.5 * /usr/lib/i386-linux-gnu/libKF5AkonadiCore.so.5 * /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 * /usr/lib/i386-linux-gnu/libkaddressbookprivate.so.5 Application: KAddressBook (kaddressbook), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xacf20840 (LWP 7077))] Thread 9 (Thread 0xa38b2b40 (LWP 7092)): #0 0xb77bcc31 in __kernel_vsyscall () #1 0xb429ca6c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187 #2 0xb5cad7bd in __pthread_cond_wait (cond=0x8f6b748, mutex=0x8f6b730) at forward.c:149 #3 0xa6b6cbba in ?? () from /usr/lib/i386-linux-gnu/dri/r600_dri.so #4 0xa6b6c185 in ?? () from /usr/lib/i386-linux-gnu/dri/r600_dri.so #5 0xb4297295 in start_thread (arg=0xa38b2b40) at pthread_create.c:333 #6 0xb5ca105e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 8 (Thread 0xa78b5b40 (LWP 7090)): #0 0xb419645d in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb414faec in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb41500b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb4150254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb61bb234 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb61612b6 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb61616ea in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb5f9282d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb5f92908 in QThread::run() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #9 0xb5f97ad2 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #10 0xb4297295 in start_thread (arg=0xa78b5b40) at pthread_create.c:333 #11 0xb5ca105e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 7 (Thread 0xa80b6b40 (LWP 7088)): #0 0xb4196488 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb414facf in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb41500b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb4150254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb61bb234 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb61612b6 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb61616ea in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb5f9282d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb5f92908 in QThread::run() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #9 0xb5f97ad2 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #10 0xb4297295 in start_thread (arg=0xa80b6b40) at pthread_create.c:333 #11 0xb5ca105e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 6 (Thread 0xa8a44b40 (LWP 7086)): #0 0xb4196480 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb414facf in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb41500b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb4150254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb61bb234 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb61612b6 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb61616ea in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb5f9282d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb5f92908 in QThread::run() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #9 0xb5f97ad2 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #10 0xb4297295 in start_thread (arg=0xa8a44b40) at pthread_create.c:333 #11 0xb5ca105e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 5 (Thread 0xa92feb40 (LWP 7084)): #0 0xb414fff0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb4150254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb61bb234 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #3 0xb61612b6
[korganizer] [Bug 156503] korganiser crashes when creating a new event
https://bugs.kde.org/show_bug.cgi?id=156503 Camille Chabot changed: What|Removed |Added CC||camillei...@videotron.ca -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 298334] Korganiser crash or close at each adding task
https://bugs.kde.org/show_bug.cgi?id=298334 Camille Chabot changed: What|Removed |Added CC||camillei...@videotron.ca -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 375080] Crash when trying tu use every to-do action and New-Event or New-Journal
https://bugs.kde.org/show_bug.cgi?id=375080 Camille Chabot changed: What|Removed |Added CC||camillei...@videotron.ca -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 385361] New: KOrganiser crashed when asked setting for journal, task and event
https://bugs.kde.org/show_bug.cgi?id=385361 Bug ID: 385361 Summary: KOrganiser crashed when asked setting for journal, task and event Product: korganizer Version: 5.2.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: todoview Assignee: kdepim-b...@kde.org Reporter: camillei...@videotron.ca Target Milestone: --- Created attachment 108163 --> https://bugs.kde.org/attachment.cgi?id=108163&action=edit crashing report on KOrganizer I am at the beginnig and i want to ''config'' KOrganizer my platform is -linux mint sarah 18 KDE with no particulars setting, KOrganizer is crashing each and every time I ask to open -new event; new task and new journal with ''action'' It's also crashing when i go to setting and ask to set korganizer. Many thanks to all of you making us free... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382944] krita-3.1.4-x86_64.appimage fails to run with 'could not find or load the Qt platform plugin "xcb"'
https://bugs.kde.org/show_bug.cgi?id=382944 Camille Scholtz changed: What|Removed |Added CC||cami...@airmail.cc --- Comment #1 from Camille Scholtz --- I'm running into the same issue, and I can confirm that libpng.so is the offending library. By downgrading my system libpng from 1.16.31 to 1.16.27 I am able to launch the Krita AppImage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381204] New: Extract foreground [interactive] result in offest layers with G'mic 0.1.7 in Krita 3.1.4
https://bugs.kde.org/show_bug.cgi?id=381204 Bug ID: 381204 Summary: Extract foreground [interactive] result in offest layers with G'mic 0.1.7 in Krita 3.1.4 Product: krita Version: 3.1.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: G'Mic for Krita Assignee: krita-bugs-n...@kde.org Reporter: welc...@nylnook.com Target Milestone: --- Created attachment 106094 --> https://bugs.kde.org/attachment.cgi?id=106094&action=edit Extract foreground [interactive] offest 1 This may be solved with Gmic 2, but for some pictures (including this one: https://commons.wikimedia.org/wiki/Earth#/media/File:BlueMarble-2001-2002.jpg), using the extract foreground [interactive] filter of G'mic in Krita may result in offest layers. Using the background dots (red ones) instead of the foreground dots (green ones) for the foreground usually workaround the issue. Please see the attached screenshots for a clearer explanation ;) Depending on the ratio of the picture, the bug seem to occur or not. It doesn't occur in Gimp. Initially reported here : https://github.com/dtschump/gmic-community/issues/82#issuecomment-308412717 Tested on Antergos Linux 64 bits Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381204] Extract foreground [interactive] result in offest layers with G'mic 0.1.7 in Krita 3.1.4
https://bugs.kde.org/show_bug.cgi?id=381204 --- Comment #1 from Camille Bissuel --- Created attachment 106095 --> https://bugs.kde.org/attachment.cgi?id=106095&action=edit Extract foreground [interactive] offest 2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381204] Extract foreground [interactive] result in offset layers with G'mic 0.1.7 in Krita 3.1.4
https://bugs.kde.org/show_bug.cgi?id=381204 Camille Bissuel changed: What|Removed |Added Summary|Extract foreground |Extract foreground |[interactive] result in |[interactive] result in |offest layers with G'mic|offset layers with G'mic |0.1.7 in Krita 3.1.4|0.1.7 in Krita 3.1.4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381204] Extract foreground [interactive] result in offset layers with G'mic 0.1.7 in Krita 3.1.4
https://bugs.kde.org/show_bug.cgi?id=381204 --- Comment #2 from Camille Bissuel --- Created attachment 106096 --> https://bugs.kde.org/attachment.cgi?id=106096&action=edit Extract foreground [interactive] offset 3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 283475] KDE Dolphin seems not to manage properly .desktop files with URL's
https://bugs.kde.org/show_bug.cgi?id=283475 Camille Chabot changed: What|Removed |Added CC||camillei...@videotron.ca -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 381230] New: manage scanned file with Dolphin
https://bugs.kde.org/show_bug.cgi?id=381230 Bug ID: 381230 Summary: manage scanned file with Dolphin Product: kdebugsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: camillei...@videotron.ca Target Milestone: --- There are two actions (Couper, Supprimer) that want to use the same shortcut (Maj+Suppr). This is most probably a bug. Please report it in bugs.kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland
https://bugs.kde.org/show_bug.cgi?id=379174 Camille Bissuel changed: What|Removed |Added CC||welc...@nylnook.com --- Comment #7 from Camille Bissuel --- If I can humbly add my voice, for me Wayland is the way to go to finally have a correct touch support in Krita under Linux, and that's useful in term of user interaction. But I fully understand that's not a priority right now. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 495627] New: NeoChat: Typo in "Welcome"
https://bugs.kde.org/show_bug.cgi?id=495627 Bug ID: 495627 Summary: NeoChat: Typo in "Welcome" Classification: Translations Product: i18n Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: fr Assignee: kde-francoph...@kde.org Reporter: nevermille@icloud.com Target Milestone: --- Created attachment 175399 --> https://bugs.kde.org/attachment.cgi?id=175399&action=edit Screenshot of NeoChat's login screen NeoChat says "Bienvenu" in French on the login screen while it should be "Bienvenue" -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 419108] New: Latte dock is not displaying correctly the main menu
https://bugs.kde.org/show_bug.cgi?id=419108 Bug ID: 419108 Summary: Latte dock is not displaying correctly the main menu Product: lattedock Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: m...@tournierjc.fr Target Milestone: --- Created attachment 126942 --> https://bugs.kde.org/attachment.cgi?id=126942&action=edit start menu wrongly displayed SUMMARY STEPS TO REPRODUCE 1. Set up latte dock in Unity layer 2. Launch session in Plasma Wayland 3. Click on launch menu OBSERVED RESULT The lateral menu is hiding part of the main menu EXPECTED RESULT Main menu should be offset to be not be hidden SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 5.5.8 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 419108] Latte dock is not displaying correctly the main menu
https://bugs.kde.org/show_bug.cgi?id=419108 --- Comment #2 from Jean-Camille Tournier --- I have set Latte to "Always on top" and it fixed all other windows -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358223] Rotoscoping effect crashes kdenlive when played
https://bugs.kde.org/show_bug.cgi?id=358223 Camille changed: What|Removed |Added CC||camille.mou...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358223] Rotoscoping effect crashes kdenlive when played
https://bugs.kde.org/show_bug.cgi?id=358223 --- Comment #5 from Camille --- (In reply to farid from comment #4) > just tested with today's build and it crashes. Considering JBM has not reported any progress here yet (see https://bugs.kde.org/show_bug.cgi?id=358223#c1 ), it is quite expected that the situation hasn't changed. > maybe a solution is to temporary disable all the unported effects to prevent > the crash in case this can't be fixed in time for release. Sounds like a good idea -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357233] New: Crash when inserting new track
https://bugs.kde.org/show_bug.cgi?id=357233 Bug ID: 357233 Summary: Crash when inserting new track Product: kdenlive Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: camille.mou...@free.fr Inserting a new track in a project crashes the application. Reproducible: Always Steps to Reproduce: 1. Launch Kdenlive 2. Project > Tracks > Insert Track 3. Validate Actual Results: The application crashes, with "Erreur de segmentation (core dumped)" Expected Results: New track inserted The same problem happens with right click > Insert Track Kdenlive version is 15.12.0 installed from http://ppa.launchpad.net/vpinon/kdenlive-testing/ubuntu -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357233] Crash when inserting new track
https://bugs.kde.org/show_bug.cgi?id=357233 Camille changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Camille --- It seems to have been resolved by the last update (4:15.12.0+65-0ubuntu1~vpinon~wily1) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 359232] Crash if I use the "Rotoscoping effect"
https://bugs.kde.org/show_bug.cgi?id=359232 Camille changed: What|Removed |Added CC||camille.mou...@free.fr --- Comment #1 from Camille --- This is a duplicate of https://bugs.kde.org/show_bug.cgi?id=358223 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 359808] Rotoscoping
https://bugs.kde.org/show_bug.cgi?id=359808 Camille changed: What|Removed |Added CC||camille.mou...@free.fr --- Comment #2 from Camille --- Duplicate of https://bugs.kde.org/show_bug.cgi?id=358223 (which has confirmed status) -- 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 #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 work), I wiped and reinstalled my Linux distribution (Antergos) entirely, reinstalling only the Gnome desktop environment and Krita and Scribus dependencies on the Qt side (attica-qt5, libdbusmenu-qt5, phonon-qt5, phonon-qt5-vlc, polkit-qt5, qt5-base, qt5-declarative, qt5-script, qt5-svg, qt5-tools, qt5-x11extras, qt5-xmlpatterns, sonnet). Interestingly, touch events aren't detected in Krita now (I can't pinch to zoom for example), but they are on the Gnome side. I suppose there is one (Qt) lib missing, I don't know which one. Any idea ? And after a week of daily work I can say the bug is not occurring without touch events. If something similar happen, any new click will "unlock" the clicking state. So this is happening, but no need to restart X to stop it. So this is really an upstream bug, do we close here ? At least it should be marked as confirmed (I can't do it)... Thanks again ! -- 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 #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'm not really wanting to try… to be able to continue using Krita 3 ... But, if you can say to me which package or setting I should install or enabled, I'll try... ! In the meanwhile, I noticed a little note in the Input-wacom 0.32 release : https://sourceforge.net/p/linuxwacom/mailman/message/35257555/ " Fix a Cintiq 27QHD touch issue" So maybe it's fixed, I'm waiting for the package (linux kernel) to land stable on archlinux... -- You are receiving this mail because: You are watching all bug changes.
[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 Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: welc...@nylnook.com I am trying to create a new clone brush with a texture for a new brush pack... And I can't ;) Every time I check an option in the "painting mode" tab of the Clone engine like "source point move" or "healing", it's immediately unchecked... So I can't modify or create a new clone brush. Thanks ! (Tested under Antergos Linux) -- You are receiving this mail because: You are watching all bug changes.
[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 reproduce the bug. Since I reinstalled my system (see comment 19), I lose touch events support, but the bug is not occuring. So my guess is that there is a library or setting missing to enable touch events in Qt or Krita, because they work in Gnome, but I don't know which one despite my blind tentatives with various packages to enable it again. Said in another way : before I was able to zoom in and out smoothly into Krita 3 with my fingers, now I can't (touch event are really rarely detected, and are really lagging), and I don't now how to enable it again, so I can't reproduce my own bug anymore. -- You are receiving this mail because: You are watching all bug changes.
[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 everything run as expected for me, and I can't reproduce your bug… -- You are receiving this mail because: You are watching all bug changes.
[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 Camille Bissuel --- I'm interested to use rotation gesture on a Wacom Cintiq 27 Touch… Zoom is already working nicely. As there is Krita users with a touch interface in this bug list, can I ask you to try to reproduce Bug 363225 ? especially as described in comment 7 : https://bugs.kde.org/show_bug.cgi?id=363225#c7 Thanks a lot in advance ! -- 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 #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 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 #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 |events are locked in|in "clicking" state, and |"clicking" state on the |Krita become unusable |Krita interface, and the| |interface become unusable | -- 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 #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 interface. This bug is driving me crazy, and basically I'll need to abandon Krita if this is not fixed a way or another… : I can't spend several hours a day rebooting because of this. I understand this is linked to some upstream bug, but can you PLEASE give me some advice on how to report this correctly and where in the QT/KDE maze ? -- 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 #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 confirmed it's probably a Qt bug. I just started a Qt bug report here : https://bugreports.qt.io/browse/QTBUG-54085 Any confirmation from others Krita users would be welcome though ;) -- 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 Version|3.0 Beta|3.0 -- 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 #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 once the pen comes in proximity, and doesn't always properly clean up their state by releasing any buttons that may have been pressed." Is Krita dropping events from other devices when the pen enter detection ? Thanks again for your hard work ! -- 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 #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 Krita, but I don't do pixel art, so I can't say if it's linked to resolution or memory. Tyson, can you please test to reproduce comment 7 or 8 in Bug 363225 ? I don't know if it's linked or not… Boudewijn was thinking this is similar but I'm not convinced… I suppose there is something wrong happening on the input side when Krita is losing and gaining the window or screen focus again. -- 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 #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: 3.0 Beta Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: welc...@nylnook.com Sorry warning : I probably don't have enough info to correctly fill this bug report, but the buggy behaviour is so annoying and I can't continue debugging without some guidance… I use Krita 3 Beta on Archlinux (Antergos distrib) build from AUR (git 8ff1a4c) on a new shiny (since a few months) Wacom Cintiq 27 Touch tablet, with Gnome 3.20, libwacom 0.18 and xf86-input-wacom 0.32 on an AMD gpu and OpenGL enabled… When Krita start, everything is fine : mouse events are correctly separated from pen events and touch events. Sometimes, and I can't figure out right now what is triggering the bug, the pen events are locked in a sort of "drag and drop" (or continuously clicking) with every interface element of Krita (dockers, popup palette, and so on…), but not the Canvas. So basically the interface become barely usable, and I must stop drawing. Please see the attached video. Additionally, changing window focus and coming back to Krita (see video at 1:14) directly on the canvas result in the system cursor not hiding. I can't figure out if it's linked or not to the continuous clicking behavior. Sometimes simply triggering a touch event resolve the issue. Sometimes I have to close an reopen Krita. Sometimes I even have to log off my session and log again. There is probably some upstream issue related, but this bug occur only in Krita 3 (not 2.9), and not in Gimp or Mypaint (opening both software at the same time prove it). This happen quite often, and I won't be able to use Krita 3 for long if this issue is not solved one way or another… This is happening since I'm testing Krita 3 from several weeks. I waited to know more, but I can't find out where to dig to be more precise. Is there some command line tool I can use to give you a better bug report ? what do you need me to provide ? Thanks again for you great work ! Reproducible: Sometimes -- 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 #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 provide a better log later… -- 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 #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 the paste.kde.org I followed the Krita Faq advice : https://docs.krita.org/KritaFAQ logs before are published for one year, if needed I attach them back here. -- 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 #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 Severity: grave Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: welc...@nylnook.com I work on a large file (8192x8192 pixel), as I use to when I want to do some illustration for an A2 poster. it work well in Krita 2.9 if I took care of not filling my RAM with too much layers. It worked starting from scratch in Krita 3 (recompiled this morning)… but I stopped my work, I closed Krita, and now I want to work again on it … But now brush strokes display and computation is so slow I can't even paint. Switching on and off layer visibility seem to allow computation and display to solve. But I can't do that between each brush stroke ! See this video : https://drive.google.com/open?id=0B-5J--XsvWh-YXBMZ1RXbVVQc0U You can download the kra file here : https://drive.google.com/open?id=0B-5J--XsvWh-azJ0V2NOai1xU00 Might be related to Bug 363225 : https://bugs.kde.org/show_bug.cgi?id=363225 (same config : I use Krita 3 Beta on Archlinux (Antergos distrib) build from AUR on a new shiny (since a few months) Wacom Cintiq 27 Touch tablet, with Gnome 3.20, libwacom 0.18 and xf86-input-wacom 0.32 on an AMD gpu and OpenGL enabled on a Radeon R9 290…) Disabling OpenGl doesn't change anything, no more than disabling Instant preview. If it's not my config, you should be able to reproduce by simply opening the file and try to draw. Reproducible: Always -- 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 #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 your time to test, I'm back to Krita 2.9 to finish this work. But IMHO, not being a part of the Krita team, I think we should investigate this before Krita 3 release. Please give me guidance on how I can give you more infos. -- 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 #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'm under Gnome 3 ? I don't know where to look at to be honest. -- 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 #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 the RC1 appimage in case it change something. -- 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 #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 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 #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 with Krita 2.9 or Krita 2.8 are not.
But the bigger one I found ("radical-dreaming.kra" made with Krita 2.9) crashed
Krita 3 when my pen was close enough to be detected. Reopening once again it
worked.
I'm uploading big files here (upload will take two or three hours), so you can
test :
https://drive.google.com/open?id=0B-5J--XsvWh-Z3lWVksyVlJwMzA
"D12.kra" and "radical-dreaming.kra" are 2.9 files
"illustration-mlle-solangel.kra" and "illustration-mlle-solange-final.kra" are
new files created a few days ago and finished today with Krita 3.
Are there any change in the file format between 2.9 and 3 ?
--
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 #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. I tried to remove it with Krita 2.9 and open it again in Krita 3, but it doesn't fix the bug. -- You are receiving this mail because: You are watching all bug changes.
[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't meant to use it ;p -- You are receiving this mail because: You are watching all bug changes.
[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 anything else (I tried with 72, 90 and 300 ppi), with "Scale Image To New Size", and checking "Adjust print size separately", or if I downscale the definition a little, performance are way better : It's not perfectly smooth as usual, but I can draw easily. So maybe scaling is involved, or scaling unlock something in the file properties or in the file structure ? or there is some miscalculation happening depending on the resolution ? Any way, that's a first workaround… -- You are receiving this mail because: You are watching all bug changes.
[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 watching all bug changes.
[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 Camille Bissuel --- I can reproduce, the steps are : 1/ Create a new Fill layer with a color 2/ Select it and Erase the color with the Del keyboard shortcut 3/ Draw something on the layer… and nothing appear I think Caetano intent is to use this layer as a mask with a locked color : drawing should modify alpha only if I understand rightly ;) -- You are receiving this mail because: You are watching all bug changes.
[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 OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: welc...@nylnook.com Hi Krita team, the new "Mix -> Greater" blending mode in Krita 3 look great for creating new brushes, but at the moment, if I draw with a brush set up with this blending mode, there is no preview while I'm drawing in the right area of the brush editor. It's working on the canvas as far as I can test. It's not working with Pixel, Sketch, Bristle, Spray, Hatchting, Grid, Curve, Dyna, Particle, Clone, Deform (although maybe not useful), Tangent Normal and Filter engines. But it's working with Color Smudge and Shape engines. Painting Mode (Wash or Build Up) doesn't seem to affect this bug. Tested on git master build today. -- You are receiving this mail because: You are watching all bug changes.
[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 Camille Bissuel --- Is this fixed ? -- 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 #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 detection HOVER THE INTERFACE (not the canvas) 3/ Most of the time the touch event is stopped, but the pen is left in this "drag and drog" state, clicking everywhere. Some times it doesn't happen... may be dependant on the exact input when the pen detection start or where the cursor appear on the interface, I can't define it more precisely now. -- 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 #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 panning" state until I trigger a right click or middle click with the pen So… my guess is that an extremely unusual behaviour with mouse and pen (pan with mouse + the pen enter detection on the interface), is now common with touch events now Krita use them on the canvas : for example it's easy to accidentally trigger a touch event with left hand while removing the pen from detection to grab the mouse, do some click, and come back to the tablet over the interface (because it's on borders) so pen enter detection while the canvas is slightly panning or zooming with left hand. Is it possible to stop any "hold" event (pan, zoom, drag) when the pen enter detection ? -- You are receiving this mail because: You are watching all bug changes.
[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 Camille Bissuel --- I can reproduce it always on my linux station with open source amdgpu drivers, specially at bigger zoom level, and with Wash mode. Quite unresponsive also. -- You are receiving this mail because: You are watching all bug changes.
[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 Camille Bissuel --- Sorry, the video is corrupted for me too, also with Firefox… -- You are receiving this mail because: You are watching all bug changes.
[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 Camille Bissuel --- I can reproduce always under Antergos and Krita3 compiled today from Git -- You are receiving this mail because: You are watching all bug changes.
[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.
