[krita] [Bug 410838] New: [regression] Using move tool with lab 16 bit float is slow, and hangs krita when enabling instant preview
https://bugs.kde.org/show_bug.cgi?id=410838 Bug ID: 410838 Summary: [regression] Using move tool with lab 16 bit float is slow, and hangs krita when enabling instant preview Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Move Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY When testing the HDR machine at sprint, I selected a part of character and started to move it, the machine although powerful started to slow things. I then tried to enable instant preview and the programm hung with the window going transparent. The canvas size was A4 300ppi the color model was LAB 16 bit float. the monitor was HDR enabled. STEPS TO REPRODUCE we weren't able to reproduce the hang but, the slowness in move tool was reproduced. SOFTWARE/OS VERSIONS Windows: windows 10 This might be probably related to this bug - https://bugs.kde.org/show_bug.cgi?id=400484 Also Dmitry said he had implemented something that might trigger this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410759] New: Add ability to restore last krita session (like the autosave restore)
https://bugs.kde.org/show_bug.cgi?id=410759 Bug ID: 410759 Summary: Add ability to restore last krita session (like the autosave restore) Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY We have a dialog box which, at the event of crash, presents the user with autosaved files. It would be nice if we extend this feature and make it load last autosaved session to restore. This would bring back the files restore dockers etc. This would be helpful for people working on animation etc. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408555] Retangular Selection Tool page informs wrong shortcut (J rather than Ctrl + R)
https://bugs.kde.org/show_bug.cgi?id=408555 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #1 from Raghavendra kamath --- Thanks for the report, we will update it soon. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407605] Add an option to zoom to a location
https://bugs.kde.org/show_bug.cgi?id=407605 Raghavendra kamath changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG --- Comment #4 from Raghavendra kamath --- Lets close this bug report then :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407605] Add an option to zoom to a location
https://bugs.kde.org/show_bug.cgi?id=407605 Raghavendra kamath changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||ra...@raghukamath.com --- Comment #1 from Raghavendra kamath --- Have you tried the zoom tool in the tool bar ? it does exactly what you want. The zoom tool is z magnifying glass icon in the toolbar on the left side besides the hand icon (pan tool) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407269] Alow deselection by clicking with a selection tool stopped working
https://bugs.kde.org/show_bug.cgi?id=407269 --- Comment #2 from Raghavendra kamath --- (In reply to Boudewijn Rempt from comment #1) > Um, this still works for me? Yes I checked only the rectangle and elliptical selection tool deselect on click , but now the outline select and polygon select tool. So this bug report can either be closed or renamed into the following wishbug- "Make the click to deselect feature available to polygon and outline select tool". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407269] New: [regression] Allow deselection by clicking with a selection tool stopped working
https://bugs.kde.org/show_bug.cgi?id=407269 Bug ID: 407269 Summary: [regression] Allow deselection by clicking with a selection tool stopped working Product: krita Version: 4.1.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY We had a new feature which allowed a user to deselect an existing selection just by clicking on the canvas by any selection tool. This was implemented in the following commit -https://invent.kde.org/kde/krita/commit/2eab134abb0d7031cba5b65ee04bf306b1b47af But in recent master it has stopped working. Iwill try to bisect and see where this got broken. STEPS TO REPRODUCE 1. Open krita built from master 2. make a selection with any selection tool 3. click anywhere in the canvas to deselect the selection OBSERVED RESULT selection doesn't get deselected. EXPECTED RESULT selection should get deselected on left click SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406049] Add option to force crop within image boundary
https://bugs.kde.org/show_bug.cgi?id=406049 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #1 from Raghavendra kamath --- I think If grow is not enable, the crop area won't go beyond the canvas boundary so this is expected. Since the area can't go beyond the boundary, it gets clipped and remainder of the area is reflected in the locked input boxes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407160] Unexpected hiding and offsetting behaviour of active selection after performing a move action on layer with move tool
https://bugs.kde.org/show_bug.cgi?id=407160 --- Comment #2 from Raghavendra kamath --- To add more, the bug is just that selection gets hidden and has offset after move action on the layer. regardless of paste or copy. Paste is working correctly and it is not related. To reproduce, - draw something on a new layer - draw a selection - move the layer with move tool The selection will be hidden until you select the selection tool again and also will have offset. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407160] Unexpected hiding and offsetting behaviour of active selection after performing a move action on layer with move tool
https://bugs.kde.org/show_bug.cgi?id=407160 Raghavendra kamath changed: What|Removed |Added Summary|Unexpected selection offset |Unexpected hiding and |after Select -> Copy, paste |offsetting behaviour of |-> Move -> Paste -> Move|active selection after ||performing a move action on ||layer with move tool -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407160] Unexpected selection offset after Select -> Copy, paste -> Move -> Paste -> Move
https://bugs.kde.org/show_bug.cgi?id=407160 Raghavendra kamath changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||ra...@raghukamath.com --- Comment #1 from Raghavendra kamath --- I can confirm this in master. In addition to the above data, i would like to add that selection that appears after moving has an offset to it. And after the second move you can get the selection to appear again if you re- activate any one of the selection tools. The problem here seems like - Using move tool offsets the selection a bit - After the move action with the move tool, selection hides itself until you activate another tool. My opinion on the questions and suggestion in comment1 - Paste content inside the selection. (New coordinates). No , since I had copied the object when it was in the previous location I would expect the copy to pasted in it's original location. - don't paste anything This is also a No. Since one would not expect paste to not work. - Should we destroy the selection if it goes outside the canvas? This is also a No, since it is inconsistent with the behaviour that we have selection outside of the canvas, and in previous discussion on IRC (if i remember correctly) we had agreed to allow selection outside the canvas. Possible solutions from my opinion - Don't hide selection after move action is completed, and also don't offset the selection after move(i think this is different problem along with hiding). If the selection is not hidden then it doesn't matter if it goes beyond canvas boundary, user will see it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407205] You can no longer drag and drop using tab mode
https://bugs.kde.org/show_bug.cgi?id=407205 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #2 from Raghavendra kamath --- I confirm this in master. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404597] Jumpy, unpredictable zoom behavior right after canvas rotation
https://bugs.kde.org/show_bug.cgi?id=404597 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395724] Kmail doesn't add signatures to reply automatically
https://bugs.kde.org/show_bug.cgi?id=395724 Raghavendra kamath changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Raghavendra kamath --- This is not reproducible now, so I am closing this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384370] Resizing canvas to bigger size with offset anchor set to center doesn't work.
https://bugs.kde.org/show_bug.cgi?id=384370 --- Comment #2 from Raghavendra kamath --- Yes thanks Kuntal, This is not reproducible now. So we can close this -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 404275] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=404275 --- Comment #13 from Raghavendra kamath --- Yes this is fixed in 5.12.3 , just got an update to qt on arch and it is fixed there -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 338470] Support Photoshop/Adobe TIFF extensions.
https://bugs.kde.org/show_bug.cgi?id=338470 --- Comment #10 from Raghavendra kamath --- The darktable dev has added layered tiff support for GIMP, can we take a look at it for our reference - https://twitter.com/GIMP_Official/status/1118811319036252160 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 404275] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=404275 --- Comment #7 from Raghavendra kamath --- In my case time zone is IST -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403674] [regression] Undo select polygon points with shift + z is not working in master
https://bugs.kde.org/show_bug.cgi?id=403674 Raghavendra kamath changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Raghavendra kamath --- I am not encountering this bug now in master on kubuntu -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405119] Flatten image with a layer stack containing apha inheritance results in all layers dissapearing.
https://bugs.kde.org/show_bug.cgi?id=405119 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404416] Sliders and Colour pickers with Pen in Windows 10
https://bugs.kde.org/show_bug.cgi?id=404416 Raghavendra kamath changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #12 from Raghavendra kamath --- This is clearly not a Krita issue, since Carson said that this is reproducible with other software as well, you should really follow this up with microsoft or QT(may be) for this, Please don't re-open the issue unless it is specifically a bug in Krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403579] [UI] There is a greyed out warning sign in blend mode list
https://bugs.kde.org/show_bug.cgi?id=403579 --- Comment #3 from Raghavendra kamath --- I am on kubuntu with backports now, and it is not reproducible in this system, might be a glitch in arch due to newer versions. I think we can close this, if I encounter it again, I'll re-open -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404553] New: Crash while changing image color profile from grayscale 8 bit to rgb 8 bit
https://bugs.kde.org/show_bug.cgi?id=404553 Bug ID: 404553 Summary: Crash while changing image color profile from grayscale 8 bit to rgb 8 bit Product: krita Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Application: krita (4.2.0-pre-alpha (git eb4d2d0)) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.18.0-15-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: I was changing the color profile of an image from gray scale -D50 elle V2 to rgb The crash can be reproduced sometimes. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x55cb573f9354) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 [Current thread is 1 (Thread 0x7f9ac55f9800 (LWP 5444))] Thread 15 (Thread 0x7f9a627fb700 (LWP 5538)): #0 futex_reltimed_wait_cancelable (private=, reltime=0x7f9a627fac50, expected=0, futex_word=0x55cb6cc98400) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f9a627fad10, mutex=0x55cb6cc983b0, cond=0x55cb6cc983d8) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x55cb6cc983d8, mutex=0x55cb6cc983b0, abstime=0x7f9a627fad10) at pthread_cond_wait.c:667 #3 0x7f9acd2b431c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9acd2ac182 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9acd2b3c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9acade6164 in start_thread (arg=) at pthread_create.c:486 #7 0x7f9accf7ddef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f9a913fd700 (LWP 5537)): #0 futex_reltimed_wait_cancelable (private=, reltime=0x7f9a913fcc50, expected=0, futex_word=0x55cb6cc97f50) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f9a913fcd10, mutex=0x55cb6cc97f00, cond=0x55cb6cc97f28) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x55cb6cc97f28, mutex=0x55cb6cc97f00, abstime=0x7f9a913fcd10) at pthread_cond_wait.c:667 #3 0x7f9acd2b431c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9acd2ac182 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9acd2b3c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9acade6164 in start_thread (arg=) at pthread_create.c:486 #7 0x7f9accf7ddef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f9a91bfe700 (LWP 5536)): #0 futex_reltimed_wait_cancelable (private=, reltime=0x7f9a91bfdc50, expected=0, futex_word=0x55cb6cc97b30) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f9a91bfdd10, mutex=0x55cb6cc97ae0, cond=0x55cb6cc97b08) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x55cb6cc97b08, mutex=0x55cb6cc97ae0, abstime=0x7f9a91bfdd10) at pthread_cond_wait.c:667 #3 0x7f9acd2b431c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9acd2ac182 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9acd2b3c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9acade6164 in start_thread (arg=) at pthread_create.c:486 #7 0x7f9accf7ddef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f9a923ff700 (LWP 5535)): #0 futex_reltimed_wait_cancelable (private=, reltime=0x7f9a923fec50, expected=0, futex_word=0x55cb6cc977c0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f9a923fed10, mutex=0x55cb6cc97770, cond=0x55cb6cc97798) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x55cb6cc97798, mutex=0x55cb6cc97770, abstime=0x7f9a923fed10) at pthread_cond_wait.c:667 #3 0x7f9acd2b431c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9acd2ac182 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9acd2b3c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9acade6164 in start_thread (arg=) at pthread_create.c:486 #7 0x7f9accf7ddef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f9a6cdfe700 (LWP 5534)): [KCrash Handler] #6 std::__atomic_base, DefaultValueTraits > >::Table*>::load (__m=std::memory_order_consume, this=) at
[krita] [Bug 393113] Crop Tool: crop image without cropping the layers data
https://bugs.kde.org/show_bug.cgi?id=393113 --- Comment #7 from Raghavendra kamath --- Hi Victor, To get rid of the content beyond the canvas boundary there is always Image > Trim to Image Size menu. you can also add a keyboard shortcut for that, it seems better for your use case. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404416] Sliders and Colour pickers with Pen in Windows 10
https://bugs.kde.org/show_bug.cgi?id=404416 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #6 from Raghavendra kamath --- Hi Carson, Can you check if the slider behaves similarly in other programs, if it does like you show in the video , then it is an issue with Microsoft's implementation, I would suggest following up with them. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-karchive] [Bug 403899] KArchive should support Zip64
https://bugs.kde.org/show_bug.cgi?id=403899 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403816] it is possible to add a kra file as a file layer with D
https://bugs.kde.org/show_bug.cgi?id=403816 --- Comment #10 from Raghavendra kamath --- thanks for the fix boud -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403816] it is possible to add a kra file as a file layer with D
https://bugs.kde.org/show_bug.cgi?id=403816 --- Comment #5 from Raghavendra kamath --- I think we should either remove ability to drag and drop kra files as file layers or implement having kra file as file layer but with last mergedimage.png of the file layer, (sorry for sounding silly) or some other way to tackle this issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403817] New: On canvas color selector triggers a taskbar entry in plasma
https://bugs.kde.org/show_bug.cgi?id=403817 Bug ID: 403817 Summary: On canvas color selector triggers a taskbar entry in plasma Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Created attachment 117767 --> https://bugs.kde.org/attachment.cgi?id=117767=edit video demonstrating the duplicate entry in taskbar SUMMARY When using krita with plasma desktop environment, the on canvas color selector triggers the taskbar entry. I have attached a video demonstrating the duplicate taskbar entry being popping up and going when the color selector disappears. On IRC wolthera and deevad also confirmed this. STEPS TO REPRODUCE 1. Open latest krita under plasma desktop, open a new file 2. press shift + I to get on canvas color selector popup. 3. you'll notice the task bar gets a duplicate krita entry, which will disappear as the color selector will go. OBSERVED RESULT color selectoir behaves as if it is a window of its own EXPECTED RESULT color selector should be contained withing the application SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.14.5 Qt Version: 5.12.0 KDE Frameworks Version: 5.54.0 Kernel Version: 4.20.5-arch1-1-ARCH OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403816] New: .kra file is not shown or listed in file selector dialog when inserting a file layer
https://bugs.kde.org/show_bug.cgi?id=403816 Bug ID: 403816 Summary: .kra file is not shown or listed in file selector dialog when inserting a file layer Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY It is possible to add a Kra file as a file layer, you can already add it now by drag and drop operation and selecting insert as file layer from the context menu. But when you try to insert a .kra file through the file layer menu from the layer stack + button, even though the resulting file dialog has all supported file format selected, kra file is not shown in there. so users think that kra file is not supported to be added as a file layer, unless they add it by drag and drop. STEPS TO REPRODUCE 1. Create a test kra file save it in some location 2. create a new file and try to add the test kra file as a file layer through the layer stack menu OBSERVED RESULT the file selector hides kra file EXPECTED RESULT kra file should be displayed with other supported format -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380001] Mouse Wheel Up/Down zooms relative to cursor, +/- zooms to middle of canvas
https://bugs.kde.org/show_bug.cgi?id=380001 --- Comment #5 from Raghavendra kamath --- In the phabricator review, Ashwin (dev) said that "The ctrl + +/ ctrl + - will zoom with respect to centre while =/- keys will zoom with repect to cursor position." I guess this solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380001] Mouse Wheel Up/Down zooms relative to cursor, +/- zooms to middle of canvas
https://bugs.kde.org/show_bug.cgi?id=380001 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #3 from Raghavendra kamath --- I don't know if this correct, while zooming from the mouse, I would like it to zoom with respect to my mouse cursor, but while zooming with the keyboard shortcut I would prefer it to be zoom in with respect to canvas center. I can't find the earlier discussion but we had a discussion about zoom actions. A user would require to position his cursor before zooming in with keyboard for it to zoom towards the cursor position, in which case he would most like be zooming with the mouse shortcut itself. So move cursor then zoom with shortcut becomes a bit cumbersome. there is also ctrl + space + (middle mouse) left click shortcut which can satisfy zoom to cursor position request too. Having the distinction of two different type of zoom action would help and be useful for those who want both types of zoom behavior -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403676] New: Converting vector layer to paint layer crops the content of the vector layer beyond canvas boundaries
https://bugs.kde.org/show_bug.cgi?id=403676 Bug ID: 403676 Summary: Converting vector layer to paint layer crops the content of the vector layer beyond canvas boundaries Product: krita Version: 4.1.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY If there is a vector object which spans beyond the canvas boundary , and a user converts it to raster (paint layer) the content that is beyond the canvas boundary gets trimmed or cropped. STEPS TO REPRODUCE 1. Open krita add a new vector layer, draw a rectangle such that half of it is beyond canvas boundary 2. right click on the layer in layer stack and go to convert > to paint layer 3. check the resulting layer by moving it, it must be now trimmed, discarding the portion that was out of canvas OBSERVED RESULT the vector objects beyond the canvas get trimmed when converting to paint layer EXPECTED RESULT the data should be preserved even when converting to paint layer -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401988] Crash on touching graphic tablet pen on canvas
https://bugs.kde.org/show_bug.cgi?id=401988 Raghavendra kamath changed: What|Removed |Added CC||jindel...@gmail.com --- Comment #21 from Raghavendra kamath --- *** Bug 403672 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403672] Crash when Krita registered tablet pen
https://bugs.kde.org/show_bug.cgi?id=403672 Raghavendra kamath changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||ra...@raghukamath.com --- Comment #1 from Raghavendra kamath --- *** This bug has been marked as a duplicate of bug 401988 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403674] New: [regression] Undo select polygon points with shift + z is not working in master
https://bugs.kde.org/show_bug.cgi?id=403674 Bug ID: 403674 Summary: [regression] Undo select polygon points with shift + z is not working in master Product: krita Version: 4.1.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY In the recent master branch, undoing select polygon points with shift +z is not working. this was along with the election shortcuts not working, but i forgot to mention it in the bug report earlier. STEPS TO REPRODUCE 1. open krita built from master and select the polygon selection tool 2. start to select with polygon selection tool 3. Try to undo the points with shift + z (as noted in the keyboard shortcuts) OBSERVED RESULT the shortcut doesn't work EXPECTED RESULT the last made polygon point should be undone by the shortcut -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403591] New: [UI] there is an unwanted space between flip icons in transform tool options.
https://bugs.kde.org/show_bug.cgi?id=403591 Bug ID: 403591 Summary: [UI] there is an unwanted space between flip icons in transform tool options. Product: krita Version: 4.1.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Created attachment 117655 --> https://bugs.kde.org/attachment.cgi?id=117655=edit space in the transform tool option docker. SUMMARY In Krita built from git master, there is unwanted space between the flip tool icons in the tool option docker for the transform tool. I believe this is a regression from the recent transform tool option tweaks. Just adding a bug report to keep this in the list. Also attached is the screenshot showing the space. I believe this commit introduced this space - https://cgit.kde.org/krita.git/commit/?id=cf276a7086f459cdf902c10ac883795f3d039b7a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403587] New: Add replace and subtract shortcuts for selection tools - A R and S are not working in master
https://bugs.kde.org/show_bug.cgi?id=403587 Bug ID: 403587 Summary: Add replace and subtract shortcuts for selection tools - A R and S are not working in master Product: krita Version: 4.1.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY The shortcuts for adding replacing and subtracting selection are not working in git master. STEPS TO REPRODUCE 1. Open krita built from git master 2. draw a selection with selection tool like bezier 3. press A R or S, check the tool option icon, they don't change, check by drawing a selection too OBSERVED RESULT shortcut have no change in the mode of selection EXPECTED RESULT selection mode should be changed according to shortcuts SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.14.5 Qt Version: 5.12.0 KDE Frameworks Version: 5.54.0 Kernel Version: 4.20.3-arch1-1-ARCH OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION the modifiers combination are working as usual. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403579] New: [UI] There is a greyed out warning sign in blend mode list
https://bugs.kde.org/show_bug.cgi?id=403579 Bug ID: 403579 Summary: [UI] There is a greyed out warning sign in blend mode list Product: krita Version: 4.1.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Created attachment 117650 --> https://bugs.kde.org/attachment.cgi?id=117650=edit screenshot showing the icon SUMMARY There is a grayed out warning (square speech bubble) icon in the favorites section of the blend mode list. This is in master as well as latest appimage STEPS TO REPRODUCE 1. open krita and go to any blend mode list either in layers panel or brush blend mode. you'll find the icon.. ADDITIONAL INFORMATION Attaching the screenshot showing the unnecessary icon -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402834] Add dithering to gradients
https://bugs.kde.org/show_bug.cgi?id=402834 --- Comment #3 from Raghavendra kamath --- Sorry for taking this different tangent. I think dithering should be in how colors are mixed and shown on screen and not just in gradients. for example there will be banding when you convert from 16 bit to 8 bit and sometime the look of the image will change drastically due to this. So i think dithering should be added to converting images , and if possible everyplace where there is a possibility of seeing a banding. A work around for this situation is to add noise spread filter from gmic -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 402958] New: Korganizer crashes on startup
https://bugs.kde.org/show_bug.cgi?id=402958 Bug ID: 402958 Summary: Korganizer crashes on startup Product: korganizer Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY On arch linux with korganizer version 5.10, crashes on startup. STEPS TO REPRODUCE 1. Open Korganizer 5.10 in arch linux OBSERVED RESULT Crash on opening SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.14.4 Qt Version: 5.12.0 KDE Frameworks Version: 5.53.0 Kernel Version: 4.20.0-arch1-1-ARCH ADDITIONAL INFORMATION -- Backtrace -- Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe5cb370840 (LWP 2511))] Thread 5 (Thread 0x7fe5c2dee700 (LWP 2516)): #0 0x7fe5d3a1cc21 in poll () from /usr/lib/libc.so.6 #1 0x7fe5d102f540 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fe5d102f62e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fe5d3f695c4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fe5d3f1258c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fe5d3d565c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fe5d3d579cc in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fe5d1c28a9d in start_thread () from /usr/lib/libpthread.so.0 #8 0x7fe5d3a27b23 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fe5c35ef700 (LWP 2514)): #0 0x7fe5d0fdd424 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7fe5d102f639 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #2 0x7fe5d3f695c4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #3 0x7fe5d3f1258c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fe5d3d565c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #5 0x7fe5d3d579cc in ?? () from /usr/lib/libQt5Core.so.5 #6 0x7fe5d1c28a9d in start_thread () from /usr/lib/libpthread.so.0 #7 0x7fe5d3a27b23 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fe5c893e700 (LWP 2513)): #0 0x7fe5d3a1cc21 in poll () from /usr/lib/libc.so.6 #1 0x7fe5d102f540 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fe5d102f62e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fe5d3f695c4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fe5d3f1258c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fe5d3d565c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fe5d3690ba6 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7fe5d3d579cc in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fe5d1c28a9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fe5d3a27b23 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fe5c9f60700 (LWP 2512)): #0 0x7fe5d3a1cc21 in poll () from /usr/lib/libc.so.6 #1 0x7fe5d0fa4630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fe5d0fa62db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fe5caf3496b in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fe5d3d579cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fe5d1c28a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fe5d3a27b23 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fe5cb370840 (LWP 2511)): [KCrash Handler] #6 0x7fe5d3dfacba in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fe5d3df45d9 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fe5d3d9d0ef in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7fe5d3d9d56d in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7fe5d3d9db04 in QDateTime::QDateTime(QDate const&, QTime const&, QTimeZone const&) () from /usr/lib/libQt5Core.so.5 #11 0x7fe5d51375d0 in KCalCore::MemoryCalendar::rawEvents(QDate const&, QDate const&, QTimeZone const&, bool) const () from /usr/lib/libKF5CalendarCore.so.5 #12 0x7fe5d50ea259 in KCalCore::Calendar::events(QDate const&, QDate const&, QTimeZone const&, bool) const () from /usr/lib/libKF5CalendarCore.so.5 #13 0x7fe5d5488dde in ?? () from /usr/lib/libkorganizerprivate.so.5 #14 0x7fe5d548a608 in ?? () from /usr/lib/libkorganizerprivate.so.5 #15 0x7fe5d5484265 in ?? () from /usr/lib/libkorganizerprivate.so.5 #16 0x7fe5d547e010 in ?? () from /usr/lib/libkorganizerprivate.so.5 #17 0x7fe5d5472260 in CalendarView::CalendarView(QWidget*) () from /usr/lib/libkorganizerprivate.so.5 #18 0x55cddd3da7fc in ?? () #19 0x55cddd3dbc7d in ?? () #20 0x55cddd3dc84f in ?? () #21 0x7fe5d552c605 in KontactInterface::PimUniqueApplication::start(QStringList const&, bool) ()
[krita] [Bug 402831] Resizing Brush with shift +lmb drag is lagging, and not smooth for various complex brush tips
https://bugs.kde.org/show_bug.cgi?id=402831 --- Comment #3 from Raghavendra kamath --- Yes, I don't have issue in older appimages, I'll try to see where exactly this started -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402909] My drawing will not finish rendering. It will not let me draw or save. please help.
https://bugs.kde.org/show_bug.cgi?id=402909 Raghavendra kamath changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||ra...@raghukamath.com Status|REPORTED|NEEDSINFO --- Comment #1 from Raghavendra kamath --- Does it say waiting for operation with a progress bar? you need to provide us with more information, to solve this -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402892] New: Krita crashed when exiting without saving from a big file
https://bugs.kde.org/show_bug.cgi?id=402892 Bug ID: 402892 Summary: Krita crashed when exiting without saving from a big file Product: krita Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Application: krita (4.2.0-pre-alpha (git 91c359e)) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.20.0-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was working on a 5k x 5k file, the file had cpu intensive layer fx, on multiple layer, there were a dozen of layers. i closed krita and hit dont save, krita crashed. I don't know if i can reproduce this crash, but i think the backtrace will be helpful -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb41857dcc0 (LWP 12059))] Thread 23 (Thread 0x7fb2f37e9700 (LWP 12495)): #0 0x7fb41c8bfef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb41d9d1a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7fb41d9d1b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7fb41d9cfbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fb41d9cb9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fb41c8b9a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fb41d516b23 in clone () from /usr/lib/libc.so.6 Thread 22 (Thread 0x7fb3087f4700 (LWP 12494)): #0 0x7fb41c8bfef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb41d9d1a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7fb41d9d1b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7fb41d9cfbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fb41d9cb9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fb41c8b9a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fb41d516b23 in clone () from /usr/lib/libc.so.6 Thread 21 (Thread 0x7fb308ff5700 (LWP 12493)): #0 0x7fb41c8bfef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb41d9d1a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7fb41d9d1b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7fb41d9cfbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fb41d9cb9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fb41c8b9a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fb41d516b23 in clone () from /usr/lib/libc.so.6 Thread 20 (Thread 0x7fb3097f6700 (LWP 12492)): #0 0x7fb41c8bfef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb41d9d1a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7fb41d9d1b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7fb41d9cfbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fb41d9cb9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fb41c8b9a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fb41d516b23 in clone () from /usr/lib/libc.so.6 Thread 19 (Thread 0x7fb309ff7700 (LWP 12491)): #0 0x7fb41c8bfef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb41d9d1a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7fb41d9d1b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7fb41d9cfbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fb41d9cb9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fb41c8b9a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fb41d516b23 in clone () from /usr/lib/libc.so.6 Thread 18 (Thread 0x7fb341ffc700 (LWP 12490)): #0 0x7fb41c8bfef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb41d9d1a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7fb41d9d1b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7fb41d9cfbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fb41d9cb9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fb41c8b9a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fb41d516b23 in clone () from /usr/lib/libc.so.6 Thread 17 (Thread 0x7fb3427fd700 (LWP 12489)): #0 0x7fb41c8bfef6 in
[krita] [Bug 402834] New: Multiple successive gradients drawn one above other produce undesired banding and color variations
https://bugs.kde.org/show_bug.cgi?id=402834 Bug ID: 402834 Summary: Multiple successive gradients drawn one above other produce undesired banding and color variations Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Created attachment 117268 --> https://bugs.kde.org/attachment.cgi?id=117268=edit gradient banding SUMMARY When applying multiple successive gradients (foreground to transparency) one above other, we get bandings and undesired color variations. According to discussion on IRC this is due to dithering problem. the bug is seen prominently when working with colors close to black and you draw it on a new layer. Drawing on an opaque white layer reduces the banding a bit. I have attached a png file with multiple gradients you can see banding in the middle, and if you zoom in you can see reds and greens in the colors. this becomes a hassle when color picking and painting too. STEPS TO REPRODUCE 1. Open a New document in Krita, switch color to close to black near red spectrum. 2. Choose the gradient tool and go and adding radial gradient successively one above another OBSERVED RESULT Bandings appear when applying successive gradients EXPECTED RESULT gradients should be dithered and smooth gradation should be produces SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.14.4 Qt Version: 5.12.0 KDE Frameworks Version: 5.53.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402831] New: Resizing Brush with shift +lmb drag is lagging, and not smooth for various complex brush tips
https://bugs.kde.org/show_bug.cgi?id=402831 Bug ID: 402831 Summary: Resizing Brush with shift +lmb drag is lagging, and not smooth for various complex brush tips Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY Shift plus left mouse button drag to resize brush size gets jittery and laggy for complex brush tips like stamp_leaves etc, sometimes it happens with relatively simple brushes as well. STEPS TO REPRODUCE 1. Open new krita document, select stamp_leaves brush from default brush set 2. try to resize brush with shift + left mouse button drag OBSERVED RESULT brush resize is not smooth and often the brush size jumps after a big pause EXPECTED RESULT brush resize should be smooth SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.4 Qt Version: 5.12.0 KDE Frameworks Version: 5.53.0 Distro : Arch ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402745] New: Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=402745 Bug ID: 402745 Summary: Discover crashes at start Product: Discover Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Application: plasma-discover (5.14.4) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.20.0-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I just opened discover and it crashes immediately. Earlier it would hang but now it crashes The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f31cf07bf80 (LWP 4664))] Thread 34 (Thread 0x7f315dffb700 (LWP 4721)): #0 0x7f31d3ba14ed in syscall () at /usr/lib/libc.so.6 #1 0x7f31d233c151 in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f31d23ba2c3 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f31d235f5fb in () at /usr/lib/libglib-2.0.so.0 #4 0x7f31d236867b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f31d2e53a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f31d3ba6b23 in clone () at /usr/lib/libc.so.6 Thread 33 (Thread 0x7f3186ffd700 (LWP 4719)): #0 0x7f31d3b9bc21 in poll () at /usr/lib/libc.so.6 #1 0x7f31d238d540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f31d238d62e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f31bc40af5f in () at /usr/lib/libostree-1.so.1 #4 0x7f31d236867b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f31d2e53a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f31d3ba6b23 in clone () at /usr/lib/libc.so.6 Thread 32 (Thread 0x7f315effd700 (LWP 4718)): #0 0x7f31d3ba14ed in syscall () at /usr/lib/libc.so.6 #1 0x7f31d233c151 in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f31d23ba2c3 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f31d235f5fb in () at /usr/lib/libglib-2.0.so.0 #4 0x7f31d236867b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f31d2e53a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f31d3ba6b23 in clone () at /usr/lib/libc.so.6 Thread 31 (Thread 0x7f315f7fe700 (LWP 4717)): #0 0x7f31d3ba14ed in syscall () at /usr/lib/libc.so.6 #1 0x7f31d233c151 in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f31d23ba2c3 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f31d235f5fb in () at /usr/lib/libglib-2.0.so.0 #4 0x7f31d236867b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f31d2e53a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f31d3ba6b23 in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7f315700 (LWP 4716)): #0 0x7f31d3ba14ed in syscall () at /usr/lib/libc.so.6 #1 0x7f31d233c151 in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f31d23ba2c3 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f31d235f5fb in () at /usr/lib/libglib-2.0.so.0 #4 0x7f31d236867b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f31d2e53a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f31d3ba6b23 in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7f3164ff9700 (LWP 4715)): #0 0x7f31d3ba14ed in syscall () at /usr/lib/libc.so.6 #1 0x7f31d233c151 in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f31d23ba2c3 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f31d235f5fb in () at /usr/lib/libglib-2.0.so.0 #4 0x7f31d236867b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f31d2e53a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f31d3ba6b23 in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7f31657fa700 (LWP 4714)): #0 0x7f31d3ba14ed in syscall () at /usr/lib/libc.so.6 #1 0x7f31d233c151 in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x7f31d23ba2c3 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f31d235f5fb in () at /usr/lib/libglib-2.0.so.0 #4 0x7f31d236867b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f31d2e53a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f31d3ba6b23 in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7f31cdc5f700 (LWP 4713)): #0 0x7f31d3b9bc21 in poll () at /usr/lib/libc.so.6 #1 0x7f31d238d540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f31d238d62e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f31bc40af5f in () at /usr/lib/libostree-1.so.1 #4 0x7f31d236867b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f31d2e53a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f31d3ba6b23 in clone () at /usr/lib/libc.so.6 Thread 26 (Thread
[krita] [Bug 401988] Crash on touching graphic tablet pen on canvas
https://bugs.kde.org/show_bug.cgi?id=401988 Raghavendra kamath changed: What|Removed |Added Summary|Crash on opening any kra|Crash on touching graphic |file|tablet pen on canvas -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401988] Crash on opening any kra file
https://bugs.kde.org/show_bug.cgi?id=401988 --- Comment #1 from Raghavendra kamath --- On further inspection, this only happens when I use pen and not with mouse -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401988] New: Crash on opening any kra file
https://bugs.kde.org/show_bug.cgi?id=401988 Bug ID: 401988 Summary: Crash on opening any kra file Product: krita Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Application: krita (4.2.0-pre-alpha (git dab1e85)) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.19.8-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I tried to open some kra files which were saved earlier from same krita version The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9318a48cc0 (LWP 862))] Thread 24 (Thread 0x7f92a13f4700 (LWP 900)): #0 0x7f931cd6fef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f931de81a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f931de81b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f931de7fbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f931de7b9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f931cd69a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f931d9c6b23 in clone () from /usr/lib/libc.so.6 Thread 23 (Thread 0x7f92a1bf5700 (LWP 899)): #0 0x7f931cd6fef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f931de81a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f931de81b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f931de7fbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f931de7b9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f931cd69a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f931d9c6b23 in clone () from /usr/lib/libc.so.6 Thread 22 (Thread 0x7f92a23f6700 (LWP 898)): #0 0x7f931cd6fef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f931de81a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f931de81b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f931de7fbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f931de7b9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f931cd69a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f931d9c6b23 in clone () from /usr/lib/libc.so.6 Thread 21 (Thread 0x7f92a2bf7700 (LWP 897)): #0 0x7f931cd6fef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f931de81a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f931de81b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f931de7fbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f931de7b9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f931cd69a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f931d9c6b23 in clone () from /usr/lib/libc.so.6 Thread 20 (Thread 0x7f92a33f8700 (LWP 896)): #0 0x7f931cd6fef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f931de81a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f931de81b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f931de7fbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f931de7b9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f931cd69a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f931d9c6b23 in clone () from /usr/lib/libc.so.6 Thread 19 (Thread 0x7f929b3f8700 (LWP 895)): #0 0x7f931cd6fef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f931de81a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f931de81b97 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f931de7fbb4 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f931de7b9cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f931cd69a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f931d9c6b23 in clone () from /usr/lib/libc.so.6 Thread 18 (Thread 0x7f92a3bf9700 (LWP 894)): #0 0x7f931cd6fef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f931de81a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f931de81b97 in QWaitCondition::wait(QMutex*,
[krita] [Bug 399627] [Freehand brush] Crash while painting, backtrace ★★★
https://bugs.kde.org/show_bug.cgi?id=399627 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399969] New: Krita Crashes when adding selection masks to group layer
https://bugs.kde.org/show_bug.cgi?id=399969 Bug ID: 399969 Summary: Krita Crashes when adding selection masks to group layer Product: krita Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Application: krita (4.2.0-pre-alpha (git e35700e)) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.14-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I added a selection to a new document Then enable displaying global selection mask then select the selection mask in the layer panel and press ctrl G to make krita crash A user can have multiple selection masks so it would be great to make it possible to add selection masks to a group to keep them organised. And krita shouldn't crash when grouping them The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbde9203840 (LWP 11875))] Thread 16 (Thread 0x7fbd8dffc700 (LWP 11949)): #0 0x7fbdee4deef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fbdef5f25fd in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7fbdef5ea024 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7fbdef5f1f65 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fbdee4d8a9d in start_thread () from /usr/lib/libpthread.so.0 #5 0x7fbdef135b23 in clone () from /usr/lib/libc.so.6 Thread 15 (Thread 0x7fbdb6bf2700 (LWP 11898)): #0 0x7fbdef12ac21 in poll () from /usr/lib/libc.so.6 #1 0x7fbdecc3dee0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fbdecc3dfce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fbdef7f2fe4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fbdef79e8cc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fbdef5e7eb9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fbdef5f1f65 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fbdee4d8a9d in start_thread () from /usr/lib/libpthread.so.0 #8 0x7fbdef135b23 in clone () from /usr/lib/libc.so.6 Thread 14 (Thread 0x7fbdb73fe700 (LWP 11891)): #0 0x7fbdecbec414 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7fbdecc3d741 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7fbdecc3de06 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7fbdecc3dfce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fbdef7f2fe4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fbdef79e8cc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fbdef5e7eb9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7fbde6ae35bb in ?? () from /usr/lib/libQt5Quick.so.5 #8 0x7fbdef5f1f65 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7fbdee4d8a9d in start_thread () from /usr/lib/libpthread.so.0 #10 0x7fbdef135b23 in clone () from /usr/lib/libc.so.6 Thread 13 (Thread 0x7fbdbcf2e700 (LWP 11890)): #0 0x7fbdef12ac21 in poll () from /usr/lib/libc.so.6 #1 0x7fbdecc3dee0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fbdecc3dfce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fbdef7f2fe4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fbdef79e8cc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fbdef5e7eb9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fbde6864859 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7fbdef5f1f65 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fbdee4d8a9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fbdef135b23 in clone () from /usr/lib/libc.so.6 Thread 12 (Thread 0x7fbdbeffd700 (LWP 11889)): #0 0x7fbdee4deef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fbdef5f25fd in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7fbdef5ea024 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7fbdef5f1f65 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fbdee4d8a9d in start_thread () from /usr/lib/libpthread.so.0 #5 0x7fbdef135b23 in clone () from /usr/lib/libc.so.6 Thread 11 (Thread 0x7fbdbf7fe700 (LWP 11888)): #0 0x7fbdee4deef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fbdef5f25fd in QWaitCondition::wait(QMutex*, unsigned long) () from
[krita] [Bug 363598] More fluent export
https://bugs.kde.org/show_bug.cgi?id=363598 --- Comment #6 from Raghavendra kamath --- Ctrl E is for merging layers, I have kept shift + E for export that is available. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398477] Cursor disappears in Layerbox
https://bugs.kde.org/show_bug.cgi?id=398477 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398285] New: [wish bug] Allow transform for multiple selected layer
https://bugs.kde.org/show_bug.cgi?id=398285 Bug ID: 398285 Summary: [wish bug] Allow transform for multiple selected layer Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- With R select and ability to select multiple layers with control key, it would be great if we had ability to transform those multiple selected layer, Now we group those layer and do transformation on the group, but it becomes cumbersome if the layer order matters. We already have the ability to move multiple selected layers, allowing transform would allow greater flexibility. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397932] Cannot hold shift and make add selection while drawing a selection with bezier curve tool
https://bugs.kde.org/show_bug.cgi?id=397932 --- Comment #6 from Raghavendra kamath --- @ scott currently we have shift + left click to complete shape for only shape tools and not selection, so we can retain the behavior with the shape tools but remove it from selection tools. Example is how polygon tool and polygon selection tool works now. we need to follow this same thing for bezier selection and bezier curve tool. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397932] Cannot hold shift and make add selection while drawing a selection with bezier curve tool
https://bugs.kde.org/show_bug.cgi?id=397932 --- Comment #4 from Raghavendra kamath --- Currently you can check the polygon selection tool and polygon tool, if it is a selection tool the polygon selection tool ignore the shift left click to complete and uses shift to activate add to selection. while if it is a polygon tool, it uses shift to complete the shape. I think bezier selection tool also should follow this paradigm, shift left click complete can be limited to bezier curve tool (where it shows this in tool tip too) but can be left out of the bezier curve selection tool, in the selection tool it can behave like all selection tool to add to selection when shift is held. So to summarise properly Remove shift + left click to complete from selection tool but keep it in normal bezier curve tool. this is the same behavior as polygon tool and polygon selection tool -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395222] transform tool on layer while mirror tools are active, makes preview fully white.
https://bugs.kde.org/show_bug.cgi?id=395222 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397932] New: Cannot hold shift and make add selection while drawing a selection with bezier curve tool
https://bugs.kde.org/show_bug.cgi?id=397932 Bug ID: 397932 Summary: Cannot hold shift and make add selection while drawing a selection with bezier curve tool Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- While drawing a selection with bezier selection, it is not possible to hold the shift key and add to the selection like other selection tools. While Holding shift and drawing a bezier curve the tool gets deactivated when you click the second node. To reproduce : 1. Open a new document 2. Draw a selection with bezier selection tool 3. Now hold shift and try to draw a new selection to add to the previous selection The result is when you click to add the second node, the tool gets deactivated and the first node is gone. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397929] New: Duplicating local selection mask by ctrl + left click drag crashes Krita
https://bugs.kde.org/show_bug.cgi?id=397929 Bug ID: 397929 Summary: Duplicating local selection mask by ctrl + left click drag crashes Krita Product: krita Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Application: krita (4.2.0-pre-alpha (git 95e1b63)) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.18.4-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was duplicating a local selection mask from one layer to another layer by holding ctrl and dragging while holding left mouse button. The crash can be reproduced sometimes. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0f18678840 (LWP 11974))] Thread 13 (Thread 0x7f0ea9ff8700 (LWP 12435)): #0 0x7f0f1e4beef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f0f1f5d069d in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f0f1f5c80c4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f0f1f5d0005 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f0f1e4b8a9d in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f0f1f113a43 in clone () from /usr/lib/libc.so.6 Thread 12 (Thread 0x7f0eaa7f9700 (LWP 12434)): #0 0x7f0f1e4beef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f0f1f5d069d in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f0f1f5c80c4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f0f1f5d0005 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f0f1e4b8a9d in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f0f1f113a43 in clone () from /usr/lib/libc.so.6 Thread 11 (Thread 0x7f0eaaffa700 (LWP 12433)): #0 0x7f0f1e4beef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f0f1f5d069d in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f0f1f5c80c4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f0f1f5d0005 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f0f1e4b8a9d in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f0f1f113a43 in clone () from /usr/lib/libc.so.6 Thread 10 (Thread 0x7f0eabffc700 (LWP 12432)): #0 0x7f0f1e4beef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f0f1f5d069d in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f0f1f5c80c4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f0f1f5d0005 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f0f1e4b8a9d in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f0f1f113a43 in clone () from /usr/lib/libc.so.6 Thread 9 (Thread 0x7f0eab7fb700 (LWP 12431)): #0 0x7f0f1e4beef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f0f1f5d069d in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f0f1f5c80c4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f0f1f5d0005 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f0f1e4b8a9d in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f0f1f113a43 in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f0ea97f7700 (LWP 12430)): #0 0x7f0f1e4beef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f0f1f5d069d in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f0f1f5c80c4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f0f1f5d0005 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f0f1e4b8a9d in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f0f1f113a43 in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f0ea8ff6700 (LWP 12429)): #0 0x7f0f1e4beef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f0f1f5d069d in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f0f1f5c80c4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f0f1f5d0005 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f0f1e4b8a9d in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f0f1f113a43 in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f0ea87f5700 (LWP 12428)): #0 0x7f0f1e4beef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f0f1f5d069d in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f0f1f5c80c4 in ?? () from
[kfontview] [Bug 367650] ~/.fonts deprecation ; please install new fonts to $XDG_DATA_HOME/fonts ; ~/.local/share/fonts
https://bugs.kde.org/show_bug.cgi?id=367650 --- Comment #3 from Raghavendra kamath --- Ok, I didn't notice the same email. Should I create a new bug or let this bug be open? -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 367650] ~/.fonts deprecation ; please install new fonts to $XDG_DATA_HOME/fonts ; ~/.local/share/fonts
https://bugs.kde.org/show_bug.cgi?id=367650 Raghavendra kamath changed: What|Removed |Added Resolution|FIXED |--- CC||ra...@raghukamath.com Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #1 from Raghavendra kamath --- This is still happening on latest arch linux so this is not yet fixed. there is not explaination about how this bug got fixed or any commit message showing that this is fixed. I am reopening this bug report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374240] Krita crashes when creating a filter layer
https://bugs.kde.org/show_bug.cgi?id=374240 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 from Raghavendra kamath --- Thanks for checking, I think we can close this bug :) If you encounter anything in future please report a bug here, until then enjoy Krita. P.S. thanks to developers for fixing bugs :D -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391292] Shape Selection tool cannot edit shapes on a selection mask.
https://bugs.kde.org/show_bug.cgi?id=391292 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Raghavendra kamath --- +1 Earlier i could edit the selection (resize and move) with the shape selection tool now the functionality is not there incidentally if I double click the selection I can enter in to node editing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374240] Krita crashes when creating a filter layer
https://bugs.kde.org/show_bug.cgi?id=374240 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #8 from Raghavendra kamath --- Hi Pablo, Can you please check the latest version of krita and see if the bug is still present in it. As Jeff mentioned it seems to work in the latest version. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373869] Unable to move docker
https://bugs.kde.org/show_bug.cgi?id=373869 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com Status|NEEDSINFO |RESOLVED --- Comment #3 from Raghavendra kamath --- Hi Jade, can you please check if this is reproducible in the latest version of Krita and also can you please check if doing what boud mentioned in comment 2 helps to resolve this. Also please don't attach dropbox links as they expire. For now I am going to close this bug report, if you think you can still reproduce this bug report in the latest version of Krita please feel free to re-open this bug report with the relevant information thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373801] why won't it work
https://bugs.kde.org/show_bug.cgi?id=373801 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||ra...@raghukamath.com --- Comment #2 from Raghavendra kamath --- Due to lack of information, reply and activity on this bug report I am going to close it for now. @solar, if you can reproduce the bug that you had with the latest Krita version then please file a new bug report with accurate information to reproduce it and also describing it accurately For your information please read our bug reporting guide -> https://docs.krita.org/en/untranslatable_pages/reporting_bugs.html -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 347959] Gaussian blur broken with 32-bit float images
https://bugs.kde.org/show_bug.cgi?id=347959 Raghavendra kamath changed: What|Removed |Added Resolution|--- |WORKSFORME CC||ra...@raghukamath.com Status|CONFIRMED |RESOLVED --- Comment #2 from Raghavendra kamath --- Hi Jonathan, Can you please check if this bug is still reproducible in the latest version of Krita. The files that you have linked have expired so i couldn't check it with your test file. I tried to do a gaussian blur on a 32 bit float image but all seemed okay for me. For now i am going to close this bug report due to lack of reply and activity, if you think this bug is still present please feel free to re-open the bug report and also please attached the kra file here it self. thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362533] Tremulous lines when drawing with pencil (hidpi related?)
https://bugs.kde.org/show_bug.cgi?id=362533 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||ra...@raghukamath.com --- Comment #11 from Raghavendra kamath --- Hi Ilya Can you please check if this is still reproducible in the latest version of Krita, for now I am going to close this bug report due to lack of activity and reply, if you think this bug is still present in the latest version of krita , please feel free to re-open this bug report thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352842] [WACOM] The disableTouchOnCanvas option doesn't disable touch for touch screens
https://bugs.kde.org/show_bug.cgi?id=352842 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||ra...@raghukamath.com --- Comment #4 from Raghavendra kamath --- Hi dodongobo...@yahoo.com Is this bug still reproducible in the latest version of Krita? For now I am closing this bug report as there is no reply or activity here, if you think this bug is still present in the latest version of Krita then please feel free to reopen this bug report Thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363598] More fluent export
https://bugs.kde.org/show_bug.cgi?id=363598 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #1 from Raghavendra kamath --- If you export the document once in some format, it will save it in the same format net time you export a document in that session. I think this solves the problem, you just have to select a format for the first time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373451] Krita 3.0.1.1 Language do not change from english
https://bugs.kde.org/show_bug.cgi?id=373451 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #3 from Raghavendra kamath --- Hi Carlos, Is this bug still reproducible in the latest version of Krita, can you please check and confirm. Thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373239] Selecting a layer makes Krita an inactive window
https://bugs.kde.org/show_bug.cgi?id=373239 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #2 from Raghavendra kamath --- HI Ismael, Can you please check if this is still reproducible in the latest version of Krita and also please give more information about the bug as requested by boud in comment 1 Thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372117] hand shortcut issue
https://bugs.kde.org/show_bug.cgi?id=372117 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||ra...@raghukamath.com --- Comment #2 from Raghavendra kamath --- Hi kspcoo...@gmail.com, Can you please test the latest version of Krita and see if this bug is still reproducible, For now since there is no activity or reply on this bug report I am closing this bug report, If you can still reproduce the bug in Latest version of krita please feel free to re-open this bug report thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364813] Selection tools create a big black blob on the canvas before crashing.
https://bugs.kde.org/show_bug.cgi?id=364813 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #13 from Raghavendra kamath --- I could not reproduce this bug on my system and there is no reply from the bug reporter for almost a year now. So due to inactivity I think we can close this bug for now. @Joe if you can still reproduce this bug in the latest version of Krita then feel free to reopen this bug thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 344418] Splash is not centered after switching to another screen with different resolution
https://bugs.kde.org/show_bug.cgi?id=344418 --- Comment #5 from Raghavendra kamath --- Misunderstood the bug sorry reopened now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 344418] Splash is not centered after switching to another screen with different resolution
https://bugs.kde.org/show_bug.cgi?id=344418 Raghavendra kamath changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 344418] Splash is not centered after switching to another screen with different resolution
https://bugs.kde.org/show_bug.cgi?id=344418 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Raghavendra kamath --- In the recent version of Krita the splash is removed and a new welcome screen is shown in the empty area when you start Krita here is the commit -> https://cgit.kde.org/krita.git/commit/?id=2325bd70e41e0a17ae727df877a2b9e8e1765a87 Here is the discussion for the design which was merged in master -> https://phabricator.kde.org/D13861 So I think This bug can be closed. If there is any problem with the new design i think we can open a new bug report for it . Thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397261] New: While undoing a stroke, the tiles don't refresh and messup the drawing
https://bugs.kde.org/show_bug.cgi?id=397261 Bug ID: 397261 Summary: While undoing a stroke, the tiles don't refresh and messup the drawing Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- When a user does undo a stroke krita sometimes randomly stops updating the titles, making it seem like undo is not working, however if we try to draw over these strokes (which are still visible) we get new stroke and artifacts the portion your new pixels are laid out get cleared. There is also a problem of redo not working, so you are left in state of broken undo and new strokes. This is making git master unusable and the bug is random and really not consistent so it is hard to pinpoint anything. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396704] Using Transform Tool (ctrl+t) on a selection, when applied, the contents of the selection disappears.
https://bugs.kde.org/show_bug.cgi?id=396704 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396445] New: Shortcut for Invert color is missing
https://bugs.kde.org/show_bug.cgi?id=396445 Bug ID: 396445 Summary: Shortcut for Invert color is missing Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- There was a shortcut for inverting colors of the image. This can be found in filter > adjust > invert. The old shortcut was Ctrl + I but in my build of Krita, I cannot find the shortcut displayed in the menu nor does it work when I press it. We should have the shortcut as it was in 3.0 and pre 3.0 days P.S. I would suggest keeping the name of the filter as "invert colors" to make it more clear. thank you -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395724] New: Kmail doesn't add signatures to reply automatically
https://bugs.kde.org/show_bug.cgi?id=395724 Bug ID: 395724 Summary: Kmail doesn't add signatures to reply automatically Product: kmail2 Version: 5.8.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- I have all the checkboxes checked in the configure kmail > composer > general and signature section. But when replying or replying all, Kmail doesn't add my signature to the message automatically. The work arround is to add %SIGNATURE in the standard reply template. Kmail should add signature when replying/replying all, when the option for adding signature automatically is checked, without the need to edit standard template. I am using kmail 5.8.2 on arch linux plasma version is 5.13.1 kde framework version is 5.47.0 Qt version is 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395480] Resizing two or more objects at once scales the stroke, but tool option is not updated and then changing stroke is incorrect
https://bugs.kde.org/show_bug.cgi?id=395480 --- Comment #2 from Raghavendra kamath --- Hi Dmitry, It is okay if we have scale style by default, the problem here is once you scale the objects the tool option docker width of stroke becomes irrelevant. it should show correct (scaled) width of stroke and one should be able to change it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 360666] over write dialog is not shown when saving a file with preexisting file name. the file gets overwritten without alerting and data of existing file is los
https://bugs.kde.org/show_bug.cgi?id=360666 Raghavendra kamath changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #16 from Raghavendra kamath --- this seems to have been fixed in recent updates. thank you closing this now -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395484] New: Preview checkbox for layer style dialog doesn't function
https://bugs.kde.org/show_bug.cgi?id=395484 Bug ID: 395484 Summary: Preview checkbox for layer style dialog doesn't function Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- The preview checkbox for the layer style window, doesn't function. The preview is always on. Un checking the preview doesn't switch preview off. To reproduce 1) Open Krita and create a new document 2) add a shape in a new layer 3) open layer style window and add some layerstyles example outerglow or stroke. 4) try to switch off preview by unchecking the radio button on the right side. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395483] New: Adding 1 px stroke layer style generates artefacts
https://bugs.kde.org/show_bug.cgi?id=395483 Bug ID: 395483 Summary: Adding 1 px stroke layer style generates artefacts Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Created attachment 113371 --> https://bugs.kde.org/attachment.cgi?id=113371=edit artefact when using stroke layerstyle of 1 px size When you add a 1 px stroke to a layer it generates extended artefact instead of proper stroke. The stroke position inside or outside doesn't matter. To reproduce : 1) Open krita and create a new document 2) Add medium rectangle or any shape in this document 3) Add stroke layer style and change the size to 1 px. You'll notice artefacts i.e. the stroke extending to the right side as shown in the attachment -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381925] Booleans give too many new nodes.
https://bugs.kde.org/show_bug.cgi?id=381925 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395481] New: Vector stroke miter, and cap options should be in tool option rather than inside a dropdown
https://bugs.kde.org/show_bug.cgi?id=395481 Bug ID: 395481 Summary: Vector stroke miter, and cap options should be in tool option rather than inside a dropdown Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Created attachment 113370 --> https://bugs.kde.org/attachment.cgi?id=113370=edit tool option for miter and cap hidden inside the three dots dropdown Currently when you select a vector shape, the options for Miter, Cap and lenght of the miter are shown inside a dropdown besides the stroke thickness input box in tool options. It makes it hard to discover and one may think that this is related to stroke thickness, while it is related to stroke but not it.s thickness. These options should be shown in the tool option itself along with thickness and other options in the stroke tab. Adding an attachment showing the options. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395480] New: Resizing two or more objects at once scales the stroke, but tool option is not updated and then changing stroke is incorrect
https://bugs.kde.org/show_bug.cgi?id=395480 Bug ID: 395480 Summary: Resizing two or more objects at once scales the stroke, but tool option is not updated and then changing stroke is incorrect Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- If A user resizes two or more vector objects through shape selection tool. The stroke is scaled as well, The problem arises when resizing the stroke width via tool width is incorrect. The tool option doesn't update at first, and then inserting any number gives wrong stroke (as if it is being resized and then applied). To reproduce 1) Open Krita and insert a new vector layer 2) Draw two shapes in it, then with shape selection tool select both and then scale them down 3) You'll notice that the stroke is resized but the tool option shows same number in stroke tab. 4) If you try to insert a number there, the stroke width is resized however, it is not the correct width. The stroke should be resized not relative to the scale size and ideally there should be an option (in future may be ) to enable stroke and pattern resize on scaling objects. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 376584] Action menu missing in addressbook
https://bugs.kde.org/show_bug.cgi?id=376584 Raghavendra kamath changed: What|Removed |Added Ever confirmed|0 |1 CC||ra...@raghukamath.com Status|UNCONFIRMED |CONFIRMED --- Comment #6 from Raghavendra kamath --- I can confirm this on arch linux with kaddressbook Version 5.8.2 not only action menu, tools menu is also missing. be it standalone or with kontact. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373174] Cannot enter HTML hex values
https://bugs.kde.org/show_bug.cgi?id=373174 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||ra...@raghukamath.com --- Comment #3 from Raghavendra kamath --- Hi martin.jeffrey Can you please check if this bug is reproducible in the latest version of krita. Since there is a lack of response, I am closing this bug report for now. If you are still facing this issue, please feel free to re-open the bug report thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367774] csv format doesn't export
https://bugs.kde.org/show_bug.cgi?id=367774 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com Status|NEEDSINFO |RESOLVED --- Comment #5 from Raghavendra kamath --- Hi stepan Can you please check if this bug is reproducible in the latest version of krita. Since there is a lack of response, I am closing this bug report for now. If you are still facing this issue, please feel free to re-open the bug report thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363799] Krita's brush strokes delay mouse/cursor at the end of each stroke
https://bugs.kde.org/show_bug.cgi?id=363799 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||ra...@raghukamath.com --- Comment #2 from Raghavendra kamath --- Hi Akiko Can you please check if this bug is reproducible in the latest version of krita. Since there is a lack of response, I am closing this bug report for now. If you are still facing this issue, please feel free to re-open the bug report thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 345282] [WACOM CINTIQ] Cursor offset problem
https://bugs.kde.org/show_bug.cgi?id=345282 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #16 from Raghavendra kamath --- Thanks for the confirmation Joshua Grubbs, Closing this now. thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370519] Only opening once during a computer session
https://bugs.kde.org/show_bug.cgi?id=370519 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com Status|NEEDSINFO |RESOLVED --- Comment #3 from Raghavendra kamath --- Hi gameboy.alex123 Can you please check if this bug is reproducible in the latest version of krita. Since there is a lack of response, I am closing this bug report for now. If you are still facing this issue, please feel free to re-open the bug report thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370572] Crashing after applying transform mask to a cloned layer
https://bugs.kde.org/show_bug.cgi?id=370572 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #7 from Raghavendra kamath --- Hi guys, can you please check if this issue is still reproduced in the latest version of Krita. thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370026] Pop-up Palette shows Favorite Presets instead of last-used tag
https://bugs.kde.org/show_bug.cgi?id=370026 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com Status|NEEDSINFO |RESOLVED --- Comment #4 from Raghavendra kamath --- Hi Phoenix Enero Can you please check if this bug is reproducible in the latest version of krita. Since there is a lack of response, I am closing this bug report for now. If you are still facing this issue, please feel free to re-open the bug report thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366770] Can't see my marks on the canvas until I click outside of the canvas.
https://bugs.kde.org/show_bug.cgi?id=366770 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com Status|NEEDSINFO |RESOLVED --- Comment #5 from Raghavendra kamath --- Hi aearelsp, If turning off opengl worked, that means the problem is in the graphic card drivers, Can you please update them and check if this issue still persists in the latest version of Krita. For now I am going to close this bug report, if you are still facing this issue, please feel free to re-open this bug report thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366560] Krita crashes on creating an image
https://bugs.kde.org/show_bug.cgi?id=366560 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com Status|NEEDSINFO |RESOLVED --- Comment #2 from Raghavendra kamath --- Hi George, Can you please check if this bug is reproducible in the latest version of krita. Since there is a lack of response, I am closing this bug report for now. If you are still facing this issue, please feel free to re-open the bug report thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365862] the sensitivity of tablet stop working
https://bugs.kde.org/show_bug.cgi?id=365862 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||ra...@raghukamath.com --- Comment #2 from Raghavendra kamath --- Hi lichu Can you please check if this bug is reproducible in the latest version of krita. Since there is a lack of response, I am closing this bug report for now. If you are still facing this issue, please feel free to re-open the bug report thank you -- You are receiving this mail because: You are watching all bug changes.
