[krita] [Bug 457470] (5.1.0-RC1 git 0640c07) - System crash on selecting older custom brush preset
https://bugs.kde.org/show_bug.cgi?id=457470 --- Comment #3 from mvowada --- Thanks Halla, didn't know that. Link to Tiar's script: https://krita-artists.org/t/brush-fixer-for-brushes-created-in-krita-5-1-beta-1/44075/4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457470] (5.1.0-RC1 git 0640c07) - System crash on selecting older custom brush preset
https://bugs.kde.org/show_bug.cgi?id=457470 mvowada changed: What|Removed |Added Summary|(5.1.0-RC1 git 0640c07) - |(5.1.0-RC1 git 0640c07) - |SYSTEM CRASH ON SELECTING |System crash on selecting |OLDER CUSTOM BRUSH PRESET |older custom brush preset -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457470] (5.1.0-RC1 git 0640c07) - SYSTEM CRASH ON SELECTING OLDER CUSTOM BRUSH PRESET
https://bugs.kde.org/show_bug.cgi?id=457470 mvowada changed: What|Removed |Added Severity|critical|crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457470] (5.1.0-RC1 git 0640c07) - SYSTEM CRASH ON SELECTING OLDER CUSTOM BRUSH PRESET
https://bugs.kde.org/show_bug.cgi?id=457470 --- Comment #1 from mvowada --- Created attachment 151103 --> https://bugs.kde.org/attachment.cgi?id=151103=edit Video example -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457470] New: (5.1.0-RC1 git 0640c07) - SYSTEM CRASH ON SELECTING OLDER CUSTOM BRUSH PRESET
https://bugs.kde.org/show_bug.cgi?id=457470 Bug ID: 457470 Summary: (5.1.0-RC1 git 0640c07) - SYSTEM CRASH ON SELECTING OLDER CUSTOM BRUSH PRESET Product: krita Version: git master (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: freebo...@tiscali.it Target Milestone: --- Created attachment 151102 --> https://bugs.kde.org/attachment.cgi?id=151102=edit Custom brush preset SUMMARY Latest stable appimage, fresh configs, just copied an older custom brush preset (see attachment) to the painttopresets folder before launching krita (the custom preset was created using previous krita-5.1.0-beta2-ff115ccb7b-x86_64.appimage - june 2022). When trying to select the custom preset from the choose brush preset window I get a sigsegv and an hard system reboot is needed in order to continue to use the system. Can't provide backtrace but I managed to record a video example. STEPS TO REPRODUCE 1. fresh configs and copy the attached custom preset to the share/krita/painttopresets folder 2. start krita 3. click the "Choose brush preset" button on the toolbar and try to select the custom preset (it's the first one in the list) OBSERVED RESULT System crash, hard shutdown needed EXPECTED RESULT Select the preset and paint SOFTWARE/OS VERSIONS Krita Version: 5.1.0-RC1 (git 0640c07) Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 Kernel Type: linux Kernel Version: 5.4.0-122-generic Pretty Productname: Ubuntu 18.04.6 LTS Locale Languages: C, it_IT, it ADDITIONAL INFORMATION 1. custom preset attached 2. video example attached -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445922] when I try to use layers styles, espetialy the one that give a shadow ( called ''ombre porté'' in french), krita crash. I tried it on nightly and beta builds using all the most re
https://bugs.kde.org/show_bug.cgi?id=445922 mvowada changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #13 from mvowada --- Hi Sara, does the crash happen again without having imported your previously saved resources? (you wrote "I backed all the things Iwanted to keep in an other folder and made a bundle of my stuff befor deleting everything") (There are some compatibility issues between version 4 and 5 https://krita.org/en/krita-5-0-release-notes/) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447878] Opacity of the Eraser mode swaps with opacity of the brush after certain actions
https://bugs.kde.org/show_bug.cgi?id=447878 --- Comment #2 from mvowada --- Maybe related to bug 389022 ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447878] Opacity of the Eraser mode swaps with opacity of the brush after certain actions
https://bugs.kde.org/show_bug.cgi?id=447878 mvowada changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||freebo...@tiscali.it Ever confirmed|0 |1 --- Comment #1 from mvowada --- Hi, I can reproduce this on Linux with Krita 5 appimage as well. After a bit of testing I guess that these three behaviours eventually cause the swap between the Selection and Brush tools opacity and eraser modes: - selection tools (Rectangular|Elliptical|Polygonal) -DO NOT- allow to press the "Set eraser mode" button -WHILE- selection tools (Freehand|Similar-color|Bezier|Magnetic) -DO-; - selection tools (all) once selected, switch to their own opacity settings -BUT- the "Set eraser mode" button doesn't change its status accordingly; - selection tools (all) allow to access the "E" shorcut to enable/disable eraser mode -BUT- the "Set eraser mode" button doesn't change its status accordingly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447805] File picker previews don't properly render small images
https://bugs.kde.org/show_bug.cgi?id=447805 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Hi, I can reproduce this on Ubuntu 18.04.6 LTS with appimage Version: 5.0.1-alpha (git 603a2f6) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445922] when I try to use layers styles, espetialy the one that give a shadow ( called ''ombre porté'' in french), krita crash. I tried it on nightly and beta builds using all the most re
https://bugs.kde.org/show_bug.cgi?id=445922 mvowada changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||freebo...@tiscali.it --- Comment #11 from mvowada --- Hi Sara, glad the issue has been fixed by devs. I'm going to close this report as "fixed" for now, feel free to reopen it in case, ok? Thanks for reporting -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447685] After I flatten my layers and click on canvas Krita freezes then crashes. This happens with any canvas size.
https://bugs.kde.org/show_bug.cgi?id=447685 mvowada changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447685] After I flatten my layers and click on canvas Krita freezes then crashes. This happens with any canvas size.
https://bugs.kde.org/show_bug.cgi?id=447685 mvowada changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||freebo...@tiscali.it Resolution|--- |FIXED --- Comment #1 from mvowada --- Hi, I'm not a developer and I'm a Linux user but: - does this happen also with newly created documents? - are all "Paint" layers (the default layer type in Krita) -AND- - are all the layers visible when flattening? Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447599] Crash with: trim to selection > and then switch to a previous snapshot which had an hidden Fill Pattern Layer below a visible layer
https://bugs.kde.org/show_bug.cgi?id=447599 --- Comment #4 from mvowada --- (changed the title a bit) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447599] Crash with: trim to selection > and then switch to a previous snapshot which had an hidden Fill Pattern Layer below a visible layer
https://bugs.kde.org/show_bug.cgi?id=447599 mvowada changed: What|Removed |Added Summary|Crash with: trim to |Crash with: trim to |selection > and then switch |selection > and then switch |to a previous snapshot |to a previous snapshot |which had an hidden Fill|which had an hidden Fill |Pattern Layer below a |Pattern Layer below a |visible Layer |visible layer -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447599] Crash with: trim to selection > and then switch to a previous snapshot which had an hidden Fill Pattern Layer below a visible Layer
https://bugs.kde.org/show_bug.cgi?id=447599 mvowada changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Summary|Crash with: trim to |Crash with: trim to |selection > and then switch |selection > and then switch |to a previous snapshot |to a previous snapshot |which had an hidden Fill|which had an hidden Fill |Pattern Layer right below a |Pattern Layer below a |visible Fill Color Layer|visible Layer Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447599] Crash with: trim to selection > and then switch to a previous snapshot which had an hidden Fill Pattern Layer right below a visible Fill Color Layer
https://bugs.kde.org/show_bug.cgi?id=447599 --- Comment #3 from mvowada --- Hi Dmitry, thanks for helping with bug 447462 yesterday.:) Yes, here I can reproduce the crash consistently with Build #1346 (27-Dec-2021 6:34:00 PM): 1. create a hidden pattern layer 2. add a paint layer 3. take a snapshot 4. select and trim to selection 5. switch to sbapshot Please, let me know if you need further informations. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447599] Crash with: trim to selection > and then switch to a previous snapshot which had an hidden Fill Pattern Layer right below a visible Fill Color Layer
https://bugs.kde.org/show_bug.cgi?id=447599 --- Comment #1 from mvowada --- GDB report (not sure it will help): SAFE ASSERT (krita): "currentLeaf->node()" in file /home/appimage/workspace/Krita_Stable_Appimage_Build/krita/libs/image/kis_async_merger.cpp, line 221 Thread 1 "AppRun" received signal SIGSEGV, Segmentation fault. 0x750a3484 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 (gdb) k Kill the program being debugged? (y or n) n Not confirmed. (gdb) thread apply all bt Thread 42 (Thread 0x7fffa7fff700 (LWP 6902)): #0 0x7fffee993fb9 in futex_reltimed_wait_cancelable ( private=, reltime=0x7fffa7ffeae0, expected=0, futex_word=0xa95ad30) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fffa7ffeba0, mutex=0xa95ace0, cond=0xa95ad08) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0xa95ad08, mutex=0xa95ace0, abstime=0x7fffa7ffeba0) at pthread_cond_wait.c:667 #3 0x74ecbd64 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #4 0x74ecc0f6 in QWaitCondition::wait(QMutex*, unsigned long) () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #5 0x74ec8b28 in ?? () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #6 0x74ec442e in ?? () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #7 0x7fffee98d6db in start_thread (arg=0x7fffa7fff700) at pthread_create.c:463 #8 0x745ab71f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 41 (Thread 0x7fffa77fe700 (LWP 6901)): ---Type to continue, or q to quit--- #0 0x7fffee993fb9 in futex_reltimed_wait_cancelable ( private=, reltime=0x7fffa77fdae0, expected=0, futex_word=0xdcd65f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fffa77fdba0, mutex=0xdcd65a0, cond=0xdcd65c8) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0xdcd65c8, mutex=0xdcd65a0, abstime=0x7fffa77fdba0) at pthread_cond_wait.c:667 #3 0x74ecbd64 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #4 0x74ecc0f6 in QWaitCondition::wait(QMutex*, unsigned long) () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #5 0x74ec8b28 in ?? () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #6 0x74ec442e in ?? () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #7 0x7fffee98d6db in start_thread (arg=0x7fffa77fe700) at pthread_create.c:463 #8 0x745ab71f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 40 (Thread 0x7fffc691e700 (LWP 6900)): #0 0x7fffee993fb9 in futex_reltimed_wait_cancelable ( private=, reltime=0x7fffc691dae0, expected=0, ---Type to continue, or q to quit--- futex_word=0x7fff988d3430) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fffc691dba0, mutex=0x7fff988d33e0, cond=0x7fff988d3408) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fff988d3408, mutex=0x7fff988d33e0, abstime=0x7fffc691dba0) at pthread_cond_wait.c:667 #3 0x74ecbd64 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #4 0x74ecc0f6 in QWaitCondition::wait(QMutex*, unsigned long) () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #5 0x74ec8b28 in ?? () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #6 0x74ec442e in ?? () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #7 0x7fffee98d6db in start_thread (arg=0x7fffc691e700) at pthread_create.c:463 #8 0x745ab71f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 39 (Thread 0x7fffa6ffd700 (LWP 6899)): #0 0x7fffee993fb9 in futex_reltimed_wait_cancelable ( private=, reltime=0x7fffa6ffcae0, expected=0, futex_word=0x7fff9508bea0) ---Type to continue, or q to quit--- at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fffa6ffcba0, mutex=0x7fff9508be50, cond=0x7fff9508be78) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fff9508be78, mutex=0x7fff9508be50, abstime=0x7fffa6ffcba0) at pthread_cond_wait.c:667 #3 0x74ecbd64 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #4 0x74ecc0f6 in QWaitCondition::wait(QMutex*, unsigned long) () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #5 0x74ec8b28 in ?? () from /tmp/.mount_kritaQyMff9/usr/bin/../lib/libQt5Core.so.5 #6 0x74ec442e in ?? () from /tmp/.mo
[krita] [Bug 447599] New: Crash with: trim to selection > and then switch to a previous snapshot which had an hidden Fill Pattern Layer right below a visible Fill Color Layer
https://bugs.kde.org/show_bug.cgi?id=447599 Bug ID: 447599 Summary: Crash with: trim to selection > and then switch to a previous snapshot which had an hidden Fill Pattern Layer right below a visible Fill Color Layer Product: krita Version: 5.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: freebo...@tiscali.it Target Milestone: --- Created attachment 144907 --> https://bugs.kde.org/attachment.cgi?id=144907=edit Video example. SUMMARY (See also attached video example.) trim to selection > and then switch to a previous snapshot which had an hidden Fill Pattern Layer right below a visible Fill Color Layer STEPS TO REPRODUCE 1. File > New... 2. Add Fill Layer... > Pattern > OK 3. hide the pattern layer 4. Add Fill Layer... > Color > OK 5. Create snapshot 6. J (Elliptical Selection Tool) > drag on canvas to make a selection 7. Image > Trim to Selection 8. Snapshot docker > select the snapshot created in point 5. > Switch to selected snapshot OBSERVED RESULT Crash EXPECTED RESULT Switch to snapshot SOFTWARE/OS VERSIONS Krita Version: 5.0.1-alpha (git 603a2f6) Qt Version (compiled): 5.12.12 - Version (loaded): 5.12.12 OS Information: Ubuntu 18.04.6 LTS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447462] Crash with: New... + Flatten image + Elliptical selection + Trim to selection + ("Undo History" docker) click on ""
https://bugs.kde.org/show_bug.cgi?id=447462 --- Comment #1 from mvowada --- Created attachment 144826 --> https://bugs.kde.org/attachment.cgi?id=144826=edit Video example. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447462] New: Crash with: New... + Flatten image + Elliptical selection + Trim to selection + ("Undo History" docker) click on ""
https://bugs.kde.org/show_bug.cgi?id=447462
Bug ID: 447462
Summary: Crash with: New... + Flatten image + Elliptical
selection + Trim to selection + ("Undo History"
docker) click on ""
Product: krita
Version: 5.0.0
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: General
Assignee: krita-bugs-n...@kde.org
Reporter: freebo...@tiscali.it
Target Milestone: ---
Created attachment 144824
--> https://bugs.kde.org/attachment.cgi?id=144824=edit
GDB report
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
See also attached GDB report and video example.
STEPS TO REPRODUCE
1. CTRL+N (File > New...)
2. Layer > Flatten image
3. J (Elliptical selection tool) > Ctrl+Shift+Drag on canvas
4. Image > Trim to selection
5. "Undo History" docker > click on ""
OBSERVED RESULT
Crash
EXPECTED RESULT
Undo?
SOFTWARE/OS VERSIONS
Krita Version: 5.0.1-alpha (git 37d49dc)
Qt Version (compiled): 5.12.12 - Version (loaded): 5.12.12
OS Information:
Pretty Productname: Ubuntu 18.04.6 LTS
Product Type: ubuntu
Product Version: 18.04
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 381537] Zoom fit with margins?
https://bugs.kde.org/show_bug.cgi?id=381537 --- Comment #3 from mvowada --- (In reply to Tymond from comment #1) > Add margins settings in the Configure Krita so one can adjust it to their > own preference. Those settings would be global and always applicable when > the user calls "Fix to X". Hi Tymond, thanks, I agree with your suggestion. It would solve the issue for me. (In reply to vanyossi from comment #2) > In the same nature of "knowing if we are zommed in" I could suggest a > "toggle zoom" that while the button is pressed is shows the full image, when > the button is unpressed zoom goes back to previous state. Thanks vanyossi. I think it would be a nice feature to have. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373837] Last used brush won't be remembered at next start (Krita 3.1.1 - Ubuntu 14.04)
https://bugs.kde.org/show_bug.cgi?id=373837 mvowada changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #10 from mvowada --- Hi, closing since I can't reproduce this with latest krita 4 and 5 versions. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370611] merging a multi-selection of layers with layer below merges with the bottom-most selected layer, not the layer beneath the selection.
https://bugs.kde.org/show_bug.cgi?id=370611 --- Comment #7 from mvowada --- Hi, in my case I've tried with Version: 4.2.0-pre-alpha (git c2fbec1) and I can't reproduce the bug. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401656] "Arrange" docker not working in nightly Krita?
https://bugs.kde.org/show_bug.cgi?id=401656 --- Comment #11 from mvowada --- (In reply to Anna Medonosova from comment #9) > With latest git master/appimage I cannot reproduce this bug anymore. Please, > mvowada, can you confirm that it is indeed working now? Hi Anna, I'm sorry but I'm not able to try with a more recent version of Krita since the appimage now uses Qt 5.12 and it won't start on my old OS. If the bug is fixed now, please, feel free to close this ticket. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361012] Guides: Undo only actions, not user settings?
https://bugs.kde.org/show_bug.cgi?id=361012 --- Comment #11 from mvowada --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391113] Color selector triangle spins a bit when changing vector colors (Krita 4 beta appimage)
https://bugs.kde.org/show_bug.cgi?id=391113 --- Comment #5 from mvowada --- (In reply to Scott Petrovic from comment #4) > Marking as needs info. This might be fixed now if you check out the latest > version of Krita (4.2.1) Hi Scott, thanks for the commit. I'm sorry but I'm not able to try with a more recent version of Krita since the appimage now uses Qt 5.12 and it won't start on my old OS. If the bug is fixed now, please, feel free to close this ticket. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405209] Wrong preset at restart
https://bugs.kde.org/show_bug.cgi?id=405209 mvowada changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from mvowada --- (In reply to Boudewijn Rempt from comment #1) > I don't see that happen here. Does that still happen for you? Hi, I'm able to reproduce this with Krita Version: 4.2.0-pre-alpha (git c2fbec1) which I think dates back to 2019-03-07. I don't know with a more recent version of Krita since the appimage now uses Qt 5.12 and it won't start on my old OS. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398509] Request for Outline Tool
https://bugs.kde.org/show_bug.cgi?id=398509 --- Comment #12 from mvowada --- Just one note: it would be nice to have the "Freehand Path Tool > Pencil" changes remembered when restarting. Example: 1. set "Exactness" to "0.10" (default is 0.50) 2. restart Actual Results: "Exactness" will reset to "0.50" (it was set to "0.10"). Expected Results: keep options changes through sessions (like brush smoothing). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405310] Layer renaming after painting
https://bugs.kde.org/show_bug.cgi?id=405310 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Created attachment 118715 --> https://bugs.kde.org/attachment.cgi?id=118715=edit Video example Thanks, I can confirm the problem (see video). It sounds like an effect of Bug 400357. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405334] Layer Rename Text Selection
https://bugs.kde.org/show_bug.cgi?id=405334 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #3 from mvowada --- Created attachment 118714 --> https://bugs.kde.org/attachment.cgi?id=118714=edit Video Hi. I can confirm the issue with a recent nightly (git c2fbec1) (see video). Likely that is the same issue of Bug 400357 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400357] [layer-stack] Renaming layers has not a consistent usability
https://bugs.kde.org/show_bug.cgi?id=400357 --- Comment #9 from mvowada --- Created attachment 118713 --> https://bugs.kde.org/attachment.cgi?id=118713=edit Video example 2 (timing) (Checked with Krita 4.2.0-pre-alpha (git c2fbec1) Hi, could be a timing issue (see video)? If I do click the layer and quickly hit F2, then the text will lose its selection/highlighting. Where if I click the layer, wait a few seconds and hit F2, then the text will remain highlighted/selected. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398509] Request for Outline Tool
https://bugs.kde.org/show_bug.cgi?id=398509 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #11 from mvowada --- (In reply to wolthera from comment #10) > > This allows the freehand path tool to be used as an outline fill tool. It works beautifully. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405209] New: Wrong preset at restart
https://bugs.kde.org/show_bug.cgi?id=405209 Bug ID: 405209 Summary: Wrong preset at restart Product: krita Version: git master Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: freebo...@tiscali.it Target Milestone: --- Created attachment 118643 --> https://bugs.kde.org/attachment.cgi?id=118643=edit Video Krita 4.2.0-pre-alpha (git c2fbec1) on Ubuntu. Choose a preset, paint, quit, restart, new document and a different brush preset will be activated (see video example). STEPS TO REPRODUCE 1. fresh configs + start + new 2. choose a different brush preset 3. paint 4. quit (do not save) 5. restart 6. new OBSERVED RESULT At restart and new, the last used preset won't be the active one. EXPECTED RESULT Remember the last used preset at restart. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399796] "Last saved" template highlighted instead of the "last used" (user templates only)
https://bugs.kde.org/show_bug.cgi?id=399796 --- Comment #2 from mvowada --- Thanks wolthera -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404181] coloured text has dark borders
https://bugs.kde.org/show_bug.cgi?id=404181 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Sounds like a duplicate of Bug 399830? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382876] Copy/Paste Layer Styles
https://bugs.kde.org/show_bug.cgi?id=382876 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Having to set layer styles from scratch more than once is draining when the preview lags behind. It would help if it were possible to copy and paste styles by doing right-click over the layer "FX" indicator. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404047] "Move tool" slowness comparing to "Transform tool"
https://bugs.kde.org/show_bug.cgi?id=404047 mvowada changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from mvowada --- I'm going to confirm this bug. Please, feel free to change the status of this report if you think it is an expected behaviour. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404047] "Move tool" slowness comparing to "Transform tool"
https://bugs.kde.org/show_bug.cgi?id=404047 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Created attachment 117908 --> https://bugs.kde.org/attachment.cgi?id=117908=edit Video (Tested with 4.2.0-pre-alpha (git 86c58a3) - Ubuntu 14.04 - RAM 8GB - GeForce 9800 GT/PCIe/SSE2) I think it's because the "Move Tool (T)" moves the whole layer not just a part of it as the Transform Tool does. (See video) 1. fresh configs 2. start Krita 3. create a new document: 1920 x 1080 px / 72 ppi / 8-bit 4. paint some strokes 5. use the Move Tool (T) to move the layer Actual Results: refreshing of the canvas doesn't catch up when moving the layer with the "Move Tool". Expected: no lags when moving a layer? Note: with more complex layer set-ups it gets worse. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403836] git 0858d79 Colour Selector (Shift + I) Has limited hue range between Cyan and Violet-Blue
https://bugs.kde.org/show_bug.cgi?id=403836 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #2 from mvowada --- Same working profile, same display profile but two different results when picking colours in Krita and PS? Krita colour selector can't pick the same blues as in PS? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403854] Timeline doesn't highlight current frame when loading document
https://bugs.kde.org/show_bug.cgi?id=403854 mvowada changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Thanks. Yes, easily reproducible here (tested with krita 4.2.0-pre-alpha (git 86c58a3 appimage on Ubuntu 14.04). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403974] Reference Images: z-position/order not saved
https://bugs.kde.org/show_bug.cgi?id=403974 mvowada changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||freebo...@tiscali.it --- Comment #2 from mvowada --- Hi. I can confirm with Krita 4.2.0-pre-alpha (git 86c58a3) appimage on Ubuntu 14.04: 1. CTRL+N (new) 2. Tools > "Reference Images Tool" 3. "Tool Options" > click [+] and add 2 reference images 4. with the last added reference image selected > "CTRL+ALT+[" (lower it) 5. save 6. reopen Actual Results: the lowered ref. image will show up on top of the other. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403876] Gradient for the outline change the color of the fill of the shape
https://bugs.kde.org/show_bug.cgi?id=403876 mvowada changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||freebo...@tiscali.it Resolution|--- |FIXED --- Comment #1 from mvowada --- Hi Tymond, it sounds like Bug 399127. Is it the same issue? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403846] Confirming a manipulation with the transform tool and clicking on the canvas with a different tool freezes Krita
https://bugs.kde.org/show_bug.cgi?id=403846 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from mvowada --- Hi Kyelle Bantog, Thanks for the report and the video. I've checked and I can't reproduce the crash on Linux Ubuntu 14.04 with Krita 4.2.0 and 4.1.7. So it might be specific to Krita for Windows. Please, could you try by closing Krita, renaming the "%LOCALAPPDATA%\kritarc" file to something different like "kritarc.BAK" and then restart? -- 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 #8 from mvowada --- :) Thanks -- 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 #6 from mvowada --- I'd prefer case 2: "with last mergedimage.png", as long as png suits the needs. At least one doesn't have to open the .kra document and export, which can be tedious in particular if it's a large file. -- 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 #3 from mvowada --- I think it is for Bug 325686? "Nesting .kra files is dangerous, since a .kra file can contain file layers itself, which is not supported" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403816] .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 --- Comment #1 from mvowada --- Hi. Yes, in both 4.2.0-pre-alpha (git 0285643) and 4.1.7 Krita versions (appimages). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403816] .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 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403676] 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 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from mvowada --- Thanks. Assuming it is unwanted (i.e. size limits) I can confirm with 4.2.0 on Ubuntu 14.04. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403771] (Brush presets) Can't reload C saved from A which was used to save B
https://bugs.kde.org/show_bug.cgi?id=403771 mvowada changed: What|Removed |Added Summary|(Brush presets) Cannot |(Brush presets) Can't |reload C saved from A which |reload C saved from A which |was used to save B |was used to save B -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403771] New: (Brush presets) Cannot reload C saved from A which was used to save B
https://bugs.kde.org/show_bug.cgi?id=403771 Bug ID: 403771 Summary: (Brush presets) Cannot reload C saved from A which was used to save B Product: krita Version: git master Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: freebo...@tiscali.it Target Milestone: --- Created attachment 117735 --> https://bugs.kde.org/attachment.cgi?id=117735=edit (Video) Steps (see video): 1. pick preset A + Edit + Save new B (use the proposed name) 2. pick preset A + Edit + Save new C (use the proposed name) (note that B is gone) 3. restart 4. pick preset C + Edit 5. try to reload C Actual Results: impossible to reload C, it needs restarting Expected Results: reset C to its default settings (Tested with Krita 4.2.0 - Ubuntu 14.04) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403758] Shift+Click-and-drag will move all the layers when using the "Move Tool" set to "Move current layer"
https://bugs.kde.org/show_bug.cgi?id=403758 mvowada changed: What|Removed |Added Attachment #117726|0 |1 is obsolete|| --- Comment #6 from mvowada --- Created attachment 117727 --> https://bugs.kde.org/attachment.cgi?id=117727=edit "Move Tool" current behaviour (4.2.0). I have put suggestions between parentheses. (Text file) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403758] Shift+Click-and-drag will move all the layers when using the "Move Tool" set to "Move current layer"
https://bugs.kde.org/show_bug.cgi?id=403758 --- Comment #5 from mvowada --- Created attachment 117726 --> https://bugs.kde.org/attachment.cgi?id=117726=edit "Move Tool" current behaviour (4.2.0). I have put suggestions between parentheses. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403758] New: Shift+Click-and-drag will move all the layers when using the "Move Tool" set to "Move current layer"
https://bugs.kde.org/show_bug.cgi?id=403758 Bug ID: 403758 Summary: Shift+Click-and-drag will move all the layers when using the "Move Tool" set to "Move current layer" Product: krita Version: git master Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: freebo...@tiscali.it Target Milestone: --- SUMMARY When using the "SHIFT" key constraint the "Move Tool" set to "Move current layer", will move all the layers. STEPS TO REPRODUCE 1. "CTRL+N" (New) 1. add 2 layers + paint something on them 2. "T" (Move Tool) 3. "Tool Options > Selection Mode > Move current layer" checked 4. "SHIFT+Click-and-drag" over a painted area OBSERVED RESULT All the layers will move (apart from the default white layer which is limitless) EXPECTED RESULT Move just the current layer, along the X/Y axes. SOFTWARE/OS VERSIONS Krita 4.1.7-4.2.0 on Ubuntu 14.04 ADDITIONAL INFORMATION On Krita 3.3.3 it works well, apparently. Forum thread for reference: https://forum.kde.org/viewtopic.php?f=139=156896 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403687] Using color picker while using Multibrush in Copy Translate mode causes Krita to freeze
https://bugs.kde.org/show_bug.cgi?id=403687 mvowada changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||freebo...@tiscali.it --- Comment #1 from mvowada --- I can confirm this on Linux Ubuntu 14.04 too. Thanks for reporting -- 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 #7 from mvowada --- To recap, the =/- keys do not zoom relative to cursor and do not appear in "Settings > Configure Krita... > Keyboard shortcuts" yet in Krita 4.2.0. -- 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 #6 from mvowada --- Yes. I've just realized that I missed the point of this report by confusing the zoom in/out shortcuts with the zoom input setting. Please, forget what I've said before. And it's already possible to set the zoom to cursor from the pen buttons by going to "Settings" > "Configure Krita..." > "Canvas Input Settings" > "Zoom Canvas". -- 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 #4 from mvowada --- (In reply to Raghavendra kamath from comment #3) > for those who want both types of zoom behaviour Keyboard shortcuts for zooming relative to the mouse cursor would let users to zoom relative to cursor directly from their pen buttons. Why not to add two new shortcuts, let's say "CTRL+SHIFT++" and "CTRL+SHIFT+-" for zooming to cursor? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403639] Window_newView //unable to access new view drop down menu//
https://bugs.kde.org/show_bug.cgi?id=403639 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #2 from mvowada --- Hi daniel, do the "tile" and "cascade" commands work? -- 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 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #2 from mvowada --- I second the request: it would be consistent behaviour having both the mouse and shortcuts zooming to cursor. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403535] Canvas isn't cleared when adding a new blank frame.
https://bugs.kde.org/show_bug.cgi?id=403535 mvowada changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Hi, I can easily reproduce this on Ubuntu 14.04 with Krita 4.2.0-pre-alpha (git 0c1da95). Thanks for the clear report and the video. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403288] Skips animation key frame when using shortcuts
https://bugs.kde.org/show_bug.cgi?id=403288 mvowada changed: What|Removed |Added Summary|Skips animation frame |Skips animation key frame ||when using shortcuts -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403288] Skips animation frame
https://bugs.kde.org/show_bug.cgi?id=403288 mvowada changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from mvowada --- (confirming) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403288] Skips animation frame
https://bugs.kde.org/show_bug.cgi?id=403288 --- Comment #3 from mvowada --- Created attachment 117610 --> https://bugs.kde.org/attachment.cgi?id=117610=edit (Video testing the bug) Hi Elyse, I can confirm the issue on linux too with 4.1.7 and 4.2.0 Krita versions, thanks. For me the exact steps to reproduce the bug are (see video testing): 1. map the "Next Key Frame" action to the "Right" key 2. map the "Previous Key Frame" action to the "Left" key 3. "CTRL+N" (new) 4. click on frame 0 5. click "Add blank frame" 6. repeat with frame 1,2,3 7. click "First Frame" (on the play bar!) 8. use the "Right" and "Left" keys Actual Results: the timeline cursor will alternately skip keyframes. NOTE A: point 7: directly clicking on the timeline would make it impossible to reproduce the bug. NOTE B: here the issue disappears soon after the first playback. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403085] Bug fix for 402841 seems to have introduced loss of animation playback and sometimes crashing
https://bugs.kde.org/show_bug.cgi?id=403085 --- Comment #2 from mvowada --- (Just added the word "animation" to the title for an easier search by summaries) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403085] Bug fix for 402841 seems to have introduced loss of animation playback and sometimes crashing
https://bugs.kde.org/show_bug.cgi?id=403085 mvowada changed: What|Removed |Added Summary|Bug fix for 402841 seems to |Bug fix for 402841 seems to |have introduced loss of |have introduced loss of |playback and sometimes |animation playback and |crashing|sometimes crashing -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400484] Weird thing where the selection, instant preview and the move tool don't play nice.
https://bugs.kde.org/show_bug.cgi?id=400484 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #2 from mvowada --- *** Bug 403371 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403371] "Move Tool (T)" > "Tool Options" docker > "Selection Modes" unpredictable
https://bugs.kde.org/show_bug.cgi?id=403371 mvowada changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from mvowada --- (In reply to Ahab Greybeard from comment #5) > The X:Y: position boxes also work Yes, I had deleted that part in the forum thread :) However, the "Move Tool (T) > Tool Options > Selection Modes", 2nd and 3rd options (radio group) are not reliable in Krita version 4.2.0 and partially in 4.1.7. They seem to work in version 3.3.3. In my opinion their labels should also be more clear, like i.e.: option 1: "move current layer" option 2: "center layer at pointer click" option 3: "move all (nested) layers" I think that the main issue is: BUG 400484. I'm going to mark this as a duplicate of it. *** This bug has been marked as a duplicate of bug 400484 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403371] "Move Tool (T)" > "Tool Options" docker > "Selection Modes" unpredictable
https://bugs.kde.org/show_bug.cgi?id=403371 --- Comment #4 from mvowada --- (Link to the forum thread: https://forum.kde.org/viewtopic.php?f=139=156759) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403371] "Move Tool (T)" > "Tool Options" docker > "Selection Modes" unpredictable
https://bugs.kde.org/show_bug.cgi?id=403371 --- Comment #3 from mvowada --- Created attachment 117556 --> https://bugs.kde.org/attachment.cgi?id=117556=edit Test Files (In reply to Ahab Greybeard from comment #2) > Can you attach or somehow make available your saved .kra file which shows > these problems? Please, see the attached zip file, it contains 2 kra files created with v4.1.7 and v4.2.0. (In reply to Ahab Greybeard from comment #2) > Were you using a mouse or a pen to carry out the operations? It was using the pen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403371] "Move Tool (T)" > "Tool Options" docker > "Selection Modes" unpredictable
https://bugs.kde.org/show_bug.cgi?id=403371 --- Comment #1 from mvowada --- (checked with Instant Preview OFF, same results here) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403371] New: "Move Tool (T)" > "Tool Options" docker > "Selection Modes" unpredictable
https://bugs.kde.org/show_bug.cgi?id=403371 Bug ID: 403371 Summary: "Move Tool (T)" > "Tool Options" docker > "Selection Modes" unpredictable Product: krita Version: git master Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Move Assignee: krita-bugs-n...@kde.org Reporter: freebo...@tiscali.it Target Milestone: --- Created attachment 117547 --> https://bugs.kde.org/attachment.cgi?id=117547=edit Video example (tested using Krita 4.2.0-pre-alpha (git 0c1da95) It seems that the "Move Tool (T)" > "Tool Options" docker > "Selection Modes" section, options 2 and 3, do not work as they should (see video). Possibly related: Bug 400484, Bug 392557 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403288] Skips animation frame
https://bugs.kde.org/show_bug.cgi?id=403288 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Created attachment 117506 --> https://bugs.kde.org/attachment.cgi?id=117506=edit Test file (unzip to see the kra file) Hi, It seems I'm not able to reproduce the bug on Ubuntu 14.04. I've checked with both 4.1.7 and 4.2.0 versions (see test file): 1. created shortcuts for "Previous Key Frame"/"Next Key Frame" (left/right keys) 2. created multiple keyframes 3. kept tapping the left and right keys Actual Results: the timeline cursor jumps across the key frames without skipping -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401911] Krita crashes after grouping masks converted from layers
https://bugs.kde.org/show_bug.cgi?id=401911 mvowada changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #7 from mvowada --- Hi Andras, thanks for reporting back. I'm going to close the report for now: in case feel free to reopen it. Thanks for the wishes and happy new year you too. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401911] Krita crashes after grouping masks converted from layers
https://bugs.kde.org/show_bug.cgi?id=401911 --- Comment #4 from mvowada --- Same results with Krita 1.4.7 (converted layers do not group and no crash). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401911] Krita crashes after grouping masks converted from layers
https://bugs.kde.org/show_bug.cgi?id=401911 --- Comment #3 from mvowada --- (Tested with Krita 4.2.0-pre-alpha (git 0c1da95) on Ubuntu 14.04) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401911] Krita crashes after grouping masks converted from layers
https://bugs.kde.org/show_bug.cgi?id=401911 mvowada changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||freebo...@tiscali.it Status|REPORTED|NEEDSINFO --- Comment #2 from mvowada --- Hi Andras, I'm sorry but I'm not able to reproduce the bug using 4.2.0. Here are my steps, please tell if they are wrong and how to exactly reproduce the crash: 1. fresh configs 2. "CTRL+N" (new) 3. change top layer opacity 4. "INS" x4 (four times) 5. change layers opacity and casually paint on them 6. group the top 5 layers 7. click the group layer once 8. add a transparency mask and paint on it 9. INS x2 (two times: it creates two layers inside the group at the top) 10. convert them two to "Filter Mask" 11. group them Actual Results: no crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403140] New: Vector shapes "Pattern fill" not working?
https://bugs.kde.org/show_bug.cgi?id=403140 Bug ID: 403140 Summary: Vector shapes "Pattern fill" not working? Product: krita Version: git master Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: freebo...@tiscali.it Target Milestone: --- Created attachment 117418 --> https://bugs.kde.org/attachment.cgi?id=117418=edit Video example (Tested using "Krita 4.2.0-pre-alpha (git 0c1da95)" Appimage - "Ubuntu 14.04") I'm not sure if it's known but "Pattern fill" (vector shapes) is not working here. Steps (see video): 1. fresh configs 2. add a "Vector Layer" 3. add a rectangle shape on it (no fill) 4. "Select Shapes Tool" > click the rectangle 5. "Tool Options" > Fill > click the "Pattern fill" button Actual Results: the rectangle won't get filled with pattern Expected: fill the selected rectangle with pattern -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403085] Bug fix for 402841 seems to have introduced loss of playback and sometimes crashing
https://bugs.kde.org/show_bug.cgi?id=403085 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from mvowada --- Hi Ahab G., I've opened the test file https://bugs.kde.org/attachment.cgi?id=117391 with the latest nightly "krita-4.2.0-pre-alpha-95773b5-x86_64.appimage" and I can easily reproduce the playback stop bug. I've then checked with the (a few days) older "krita-4.2.0-pre-alpha-0c1da95-x86_64.appimage" and it works well without any playback stops. Thanks for reporting this. Confirming. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402841] Animation curve opacity doesn't display correctly during playback and sometimes during timeline scrolling
https://bugs.kde.org/show_bug.cgi?id=402841 mvowada changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||freebo...@tiscali.it Resolution|--- |WAITINGFORINFO --- Comment #1 from mvowada --- Hi Tristan, I'm sorry but the attached image is really small (200px) and it's difficult to see the problem. Please, could you upload another example (4MB limit) or provide details on what happens and what you would expect? Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402749] "My Favorites" brush group doesn't load on startup
https://bugs.kde.org/show_bug.cgi?id=402749 --- Comment #8 from mvowada --- Created attachment 117262 --> https://bugs.kde.org/attachment.cgi?id=117262=edit Video Hi Boudewijn, I've made a video showing the issue, hope it helps. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402749] "My Favorites" brush group doesn't load on startup
https://bugs.kde.org/show_bug.cgi?id=402749 --- Comment #4 from mvowada --- (Appimage) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402749] "My Favorites" brush group doesn't load on startup
https://bugs.kde.org/show_bug.cgi?id=402749 mvowada changed: What|Removed |Added Ever confirmed|0 |1 CC||freebo...@tiscali.it Status|REPORTED|CONFIRMED --- Comment #3 from mvowada --- Hi, I can reproduce this as well (Krita 4.2.0-pre-alpha (git ea51095) - Ubuntu 14.04 - Gnome Compiz): 1. "Brush presets" docker > select "My favorites" item from the dropdown list 2. restart Krita Actual Results: brush presets docker "My favorites" list will display as empty. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402806] The Brush HUD configuration window is to small
https://bugs.kde.org/show_bug.cgi?id=402806 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from mvowada --- Hi Alexander, this has been fixed recently I think. *** This bug has been marked as a duplicate of bug 402296 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402296] 4.1.7 onwards, pop up palette has malformed brush properties sub-window
https://bugs.kde.org/show_bug.cgi?id=402296 mvowada changed: What|Removed |Added CC||a.nolt...@almano.de --- Comment #6 from mvowada --- *** Bug 402806 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402679] SIGSEGV with fresh start, when choosing a brush preset and no document open
https://bugs.kde.org/show_bug.cgi?id=402679 --- Comment #3 from mvowada --- Hi Wolthera, (In reply to wolthera from comment #2) > Next time, see if you can get the full backtrace with 'thread apply all > backtrace' if you're running in GDB. I'm sorry, the OS freezes as soon as I try to choose a preset (point 4) and I always have to shutdown through the power button (tested using the Appimage with both "i3wm" and "Unity/Compiz" as window managers). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402679] SIGSEGV with fresh start, when choosing a brush preset and no document open
https://bugs.kde.org/show_bug.cgi?id=402679 --- Comment #1 from mvowada --- (Tested with Krita 4.2.0-pre-alpha (git ea51095) on Ubuntu 14.04 - i3 window manager) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402679] New: SIGSEGV with fresh start, when choosing a brush preset and no document open
https://bugs.kde.org/show_bug.cgi?id=402679 Bug ID: 402679 Summary: SIGSEGV with fresh start, when choosing a brush preset and no document open Product: krita Version: git master Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: freebo...@tiscali.it Target Milestone: --- Created attachment 117167 --> https://bugs.kde.org/attachment.cgi?id=117167=edit (Video of the steps) (Krita - Ubuntu 14.04 - i3 window manager) I'm having a crash by doing (see video): 1. fresh configs + start (no documents) 2. "Settings" > "Configure Toolbars..." > edit and click "OK" 3. (toolbar >) "Choose brush preset" > new "Tag" > type in a name > "Enter" key 4. Left-click on any brush preset in the window. Actual Results: SIGSEGV and freezing of the OS. Terminal says something like: Thread 1 "AppRun" received signal SIGSEGV, Segmentation fault. 0x746fadc0 in QObject::blackSignals(bool) () from /tmp/.mount_KritairlyBm/usr/bin/../lib/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402633] Wrong layer numeration after deleting middle one.
https://bugs.kde.org/show_bug.cgi?id=402633 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from mvowada --- Hi. I think it might be useful to know the reasons for changing how layers are named by default. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402443] Enlarging a canvas paint added sections instead of keeping them transparent
https://bugs.kde.org/show_bug.cgi?id=402443 mvowada changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #5 from mvowada --- Sky, thanks for reporting back. I'm going to close this report. Feel free to reopen it in case. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402443] Enlarging a canvas paint added sections instead of keeping them transparent
https://bugs.kde.org/show_bug.cgi?id=402443 mvowada changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from mvowada --- (In reply to SkyDiver from comment #2) > I'd just like to emphasize that doing this will make all the pixels on that > layer become transparent, including the ones that I'd like to keep visible. I see the point. It's always possible to change the default canvas transparency by going to "CTRL+N" > "Create new document" > "Content" tab. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402508] starts and then appears black screen and stops working
https://bugs.kde.org/show_bug.cgi?id=402508 mvowada changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||freebo...@tiscali.it Status|REPORTED|NEEDSINFO --- Comment #1 from mvowada --- Hi Paolaw. Please, see if these informations can be useful for you: - Bug 360601 - https://phabricator.kde.org/T5883 - (might be outdated) https://userbase.kde.org/Krita/Manual/FAQ#Krita_start_with_a_black_canvas_and_nothing_changes_when_you_try_to_draw.2Fshows_a_black_screen_on_my_Windows_system_with_an_Intel_GPU If you have doubts please, paste here also the (Krita main menu >) "Help > Show system information for bug reports..." text, or ask the Forum (https://forum.kde.org/viewforum.php?f=139). Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402443] Enlarging a canvas paint added sections instead of keeping them transparent
https://bugs.kde.org/show_bug.cgi?id=402443 mvowada changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402443] Enlarging a canvas paint added sections instead of keeping them transparent
https://bugs.kde.org/show_bug.cgi?id=402443 mvowada changed: What|Removed |Added Resolution|--- |FIXED CC||freebo...@tiscali.it Status|REPORTED|NEEDSINFO --- Comment #1 from mvowada --- Hi Sky, can you say what happens if you do right-click over the layer > select "Properties..." and low the layer opacity down to 0%? Example: 1. fresh configs 2. "CTRL+N" (default settings) 3. click select the bottom layer 4. "CTRL+A" (select all) 5. "CTRL+X" (cut) 6. Image > Resize Canvas... (enlarging) 7. right-click over the layer > "Properties..." > Opacity: 0%. Actual Results: transparent margins. Is it the same for you? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402418] Krita 4.1.5 crash wen wacom intuos pen enter in drawing area
https://bugs.kde.org/show_bug.cgi?id=402418 mvowada changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Hello Avelino, can you check with the latest release 4.1.7? It could be the same bug of https://bugs.kde.org/show_bug.cgi?id=402155 Let we know if it'll work for you (with fresh configs :) Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402329] The vector shape's repeat type of gradient is not saved.
https://bugs.kde.org/show_bug.cgi?id=402329 mvowada changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from mvowada --- Let's keep the report confirmed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402329] The vector shape's repeat type of gradient is not saved.
https://bugs.kde.org/show_bug.cgi?id=402329
--- Comment #3 from mvowada ---
Created attachment 117017
--> https://bugs.kde.org/attachment.cgi?id=117017=edit
(Video example)
Video example of the "repeat" gradient ignored at reopening ("Fill" and
"Stroke").
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 402329] The vector shape's repeat type of gradient is not saved.
https://bugs.kde.org/show_bug.cgi?id=402329 mvowada changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Thanks for the report (confirming with Krita 4.2.0-pre-alpha (git 95b09ea) - Ubuntu 14.04). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402292] A Krita crach if I want to select color spase (AnimePalett,TealMagentaGold,ColorNegative,RedBleuYellow,Smokey)
https://bugs.kde.org/show_bug.cgi?id=402292 mvowada changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||freebo...@tiscali.it --- Comment #1 from mvowada --- Hi there. Do you mean when picking colours from the "Palette" docker? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402263] Undoing doesn't always set document back to "not modified"
https://bugs.kde.org/show_bug.cgi?id=402263 mvowada changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||freebo...@tiscali.it --- Comment #2 from mvowada --- Confirming (Krita 4.2.0-pre-alpha (git 95b09ea) - Ubuntu 14.04). (See also Bug 386488) -- You are receiving this mail because: You are watching all bug changes.
