[krita] [Bug 412860] New: Mouse pointer randomly appearing when pop up shows up
https://bugs.kde.org/show_bug.cgi?id=412860 Bug ID: 412860 Summary: Mouse pointer randomly appearing when pop up shows up Product: krita Version: 4.2.7-beta1 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- SUMMARY Mouse pointer randomly appearing on the brush outline after popup appears. STEPS TO REPRODUCE 1. Set cursor shape to no cursor in preferences. Now when using the brush you shouldn't see the mouse cursor 2. While still using the brush tool, for example cmd+O to display the open... pop up reproduces quite well the problem 3. Close the pop up. Sometimes you still have the cursor stuck on your brush shape (doesn't always work so you need to repeat a few times if it doesn't) OBSERVED RESULT You have a mouse cursor stuck in the middle of your brush shape. To get rid of it I need to get the cursor out of the canvas and back. EXPECTED RESULT No cursor stuck in the middle of the brush shape SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412860] Mouse pointer randomly appearing when pop up shows up
https://bugs.kde.org/show_bug.cgi?id=412860 --- Comment #1 from Manga Tengu --- in case this doesn't show in the ticket (I fill the form though...) This is on macOS mojave latest + Krita 4.2.7.1 but the problem is not new at all. Just had a hard time to pin point it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412860] Mouse pointer randomly appearing when pop up shows up
https://bugs.kde.org/show_bug.cgi?id=412860 --- Comment #3 from Manga Tengu --- (In reply to Boudewijn Rempt from comment #2) > Yes, I've been able to reproduce this. I'm not sure where the bug is, > though... It seems to happen in random softwares. So maybe it's mac specific... For example I'm working in Eclipse and some slack popup appears. My caret becomes a mouse cursor and I have to do similar tricks to get it back to normal. In Krita my work around is to either get out and in the canvas or invoke a quick tool like the eye dropper. Makes me think we need to be able to make the layer docker popable like the color and paint preset selectors ! That would be so cool. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407224] New: ColorSpace wrong option with P3 screens
https://bugs.kde.org/show_bug.cgi?id=407224 Bug ID: 407224 Summary: ColorSpace wrong option with P3 screens Product: krita Version: 4.1.7 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- As discussed with Wolthera, the following option may need to be hidden on new macbooks: Color Management > Display > Use system monitor profile. After switching all the color space options to display P3 and seeing no change, I just unchecked this box and the oversaturation is gone. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407598] Freezing at first stroke - git 7bc375b
https://bugs.kde.org/show_bug.cgi?id=407598 --- Comment #5 from Manga Tengu --- (In reply to wolthera from comment #4) > Hey MangaTengu, does this still happen with 4.2.6? It doesn't happen anymore. I even forgot about it 0_o -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410959] New: Full screen mode disappearing when invoking popup palette and color history
https://bugs.kde.org/show_bug.cgi?id=410959 Bug ID: 410959 Summary: Full screen mode disappearing when invoking popup palette and color history Product: krita Version: 4.2.4 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- When invoking a popup docker (color selector, color history) in full screen, the os switches back to the desktop and displays the pop up there, alone (over all the other applications but without the krita window). STEPS TO REPRODUCE 1. go full screen: it works fine 2. go desktop screen 3. go full screen: krita hides and shows only the popup palette over the desktop OBSERVED RESULT So macOS has this disgusting sliding desktop effect when you open a fullscreen app. The whole desktop will disappear sliding to the left. Then if you get back to it, your full screen app will disappear sliding to the right...this is what happens when I open a pop up palette. It opens alone on top of the desktop while the krita fullscreen window has slid to the right and is invisible EXPECTED RESULT Krita still be visible under the popup palette even if I switch back and forth fullscreen and windowed mode... MacOS Latest/Krita 4.2.X, actually tested on 4.2.4, 4.2.5 ADDITIONAL INFORMATION You definitely need a popup layers, that would be so cool.. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410959] Full screen mode disappearing when invoking popup palette and color history
https://bugs.kde.org/show_bug.cgi?id=410959 --- Comment #1 from Manga Tengu --- Step 2 I mean leave full screen mode -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422357] New: command stays pressed when alt tabing back in krita
https://bugs.kde.org/show_bug.cgi?id=422357 Bug ID: 422357 Summary: command stays pressed when alt tabing back in krita Product: krita Version: 4.3.0-beta1 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- ### This is for 4.3.0-beta2 (not available yet) ### When going back to the krita window under certain circumstances, Krita thinks command is pressed while it's not. You need to press it again to unlock command. STEPS TO REPRODUCE 1. Set Krita in full view 2. Command tab outside of it (in a non full view application) When you press command tab, you need to be slow enough for the color picker to show before you change window 3. Command tab back in Krita OBSERVED RESULT In krita, the color picker stays activated until you press command again EXPECTED RESULT Krita is happy you are back and doesn't lock the command key SOFTWARE/OS VERSIONS macOS: Catalina 10.15.4 ADDITIONAL INFORMATION Still on that 2018 macbook pro 15' -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422357] command stays pressed when alt tabbing back in krita
https://bugs.kde.org/show_bug.cgi?id=422357 Manga Tengu changed: What|Removed |Added Version|4.3.0-beta1 |4.3.0-beta2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419000] Canvas input navigation shortcuts not working when going to full screen mode
https://bugs.kde.org/show_bug.cgi?id=419000 --- Comment #2 from Manga Tengu --- yest this is macOS specific -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419000] Canvas input navigation shortcuts not working when going to full screen mode
https://bugs.kde.org/show_bug.cgi?id=419000 --- Comment #5 from Manga Tengu --- Reproduced again with 78d8377. And it happens even when I go from full screen to windowed. Is there a way I can give more info about that ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418999] Krita with wrong zip headers cannot be viewed in scribus
https://bugs.kde.org/show_bug.cgi?id=418999 --- Comment #3 from Manga Tengu --- The base file I use (duplicate it x times to make my pages, was created a few years ago. Maybe that's the issue.) I'll make a new file and try with that -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421030] New: Reload original preset not working
https://bugs.kde.org/show_bug.cgi?id=421030 Bug ID: 421030 Summary: Reload original preset not working Product: krita Version: nightly build (please specify the git hash!) Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- SUMMARY click on the button or use a shortcut to reload original preset doesn't work STEPS TO REPRODUCE 1. change the brush settings (rotation, spacing for example) 2. click the reload button 3. cry OBSERVED RESULT The preview brush stroke is updated, (the fuzzy side of it). Settings are not reloaded EXPECTED RESULT Brush gets back to its default position SOFTWARE/OS VERSION macOS: catalina 10.15.4 krita 78d8377 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419000] Canvas input navigation shortcuts not working when going to full screen mode
https://bugs.kde.org/show_bug.cgi?id=419000 --- Comment #7 from Manga Tengu --- I have an french azerty keyboard (native) and I use it as such. I use the the keyboard shortcut I customized to the F key. I Hope this help ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417312] New: Krita nightly terminated after splash
https://bugs.kde.org/show_bug.cgi?id=417312 Bug ID: 417312 Summary: Krita nightly terminated after splash Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: macOS Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Launching krita ba4e484 fails. After the splash screen, krita is terminated without prompt. Before that I was using e383c2a STEPS TO REPRODUCE Launch krita OBSERVED RESULT Krita window never shows, the process is killed after splash screen EXPECTED RESULT Krita launches and informs me I have won 1 million dollars (US)... SOFTWARE/OS VERSIONS macOS: latest ADDITIONAL INFORMATION I have an early 2019 15' macbook pro -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417312] Krita nightly terminated after splash
https://bugs.kde.org/show_bug.cgi?id=417312 --- Comment #2 from Manga Tengu --- My mac has Catalina 10.15.3 (19D76) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417312] Krita nightly terminated after splash
https://bugs.kde.org/show_bug.cgi?id=417312 --- Comment #4 from Manga Tengu --- I did as you said (moved my krita to krita-old) still not working Launched from terminal the way you described, then it works (but only that way). Here is the output: macbook "pro" have 2 graphics cards, one dedicated and one integrated. And I have disabled the automatic switch a year ago so I always use the dedicated gpu = No "breeze" available. Set style "fusion" WARNING: configured swap location is not writable, using a fall-back location "/Users/nour/Library/Application Support/krita/swap" -> "/private/var/folders/4t/xdmnfpwn7sn97qp1ygb9cwkwgn/T" WARNING: configured swap location is not writable, using a fall-back location "/Users/nour/Library/Application Support/krita/swap" -> "/private/var/folders/4t/xdmnfpwn7sn97qp1ygb9cwkwgn/T" Invalid profile : "/Library/ColorSync/Profiles//WebSafeColors.icc" "Web Safe Colors" QObject::startTimer: Timers cannot have negative intervals WARNING: configured swap location is not writable, using a fall-back location "/Users/nour/Library/Application Support/krita/swap" -> "/private/var/folders/4t/xdmnfpwn7sn97qp1ygb9cwkwgn/T" /Applications/krita.app/Contents/Frameworks/krita-python-libs/krita added to PYTHONPATH QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout Shortcut for action "wrap_around_mode" "&Wrap Around Mode" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "view_ruler" "Show &Rulers" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "view_show_guides" "Show Guides" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "view_lock_guides" "Lock Guides" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "new_from_visible" "&New Layer From Visible" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "add_new_transparency_mask" "&Transparency Mask" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "toggle_layer_visibility" "Toggle layer &visibility" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "toggle_layer_inherit_alpha" "Toggle layer alpha &inheritance" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "toggle_layer_alpha_lock" "Toggle layer &alpha" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "view_toggle_painting_assistants" "S&how Painting Assistants" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "view_toggle_assistant_previews" "Show &Assistant Previews" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "reload_preset_action" "Reload Original Preset" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "selectopaque" "Select &Opaque (Replace)" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "file_export_file" "E&xport..." set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Shortcut for action "view_toggledockers" "&Show Dockers" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. = -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417312] Krita nightly terminated after splash
https://bugs.kde.org/show_bug.cgi?id=417312 --- Comment #7 from Manga Tengu --- (In reply to Boudewijn Rempt from comment #6) > Hm, no that log doesn't show anything special, I'm afraid. Does this still > happen now we've got updated dependencies for macOS as well? Does it also > happen if you run Krita as another user? Yes it still happens, even with a new session. The workaround for me is to launch krita through terminal: open -n -a /Applications/krita.app -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417312] Krita nightly terminated after splash
https://bugs.kde.org/show_bug.cgi?id=417312 --- Comment #13 from Manga Tengu --- Deeper into weirdness :) Indeed reselecting the language solves opening krita BUT if I open a kra file while krita is closed, it will fail and propose to relaunch. Then when I click "reopen", it will work. I can redo it as much as I want, the first open will fail if I click a kra file rather than the krita.app -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419000] Canvas input navigation shortcuts not working when going to full screen mode
https://bugs.kde.org/show_bug.cgi?id=419000 --- Comment #9 from Manga Tengu --- Maybe it happens in a random fashion depending on setups ? In my case, it is systematic (happens everytime) and I'm using the stylus -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421485] New: daily builds not only for krita next
https://bugs.kde.org/show_bug.cgi?id=421485 Bug ID: 421485 Summary: daily builds not only for krita next Product: krita Version: 4.3.0-beta1 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Unittests Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Actually, we have only krita next available as a daily build. Krita plus and Krita beta are not available. Realized this here: https://krita-artists.org/t/krita-4-3-0-beta-is-out-you-too-can-help-with-beta-testing/6611/28?u=mangatengu https://krita-artists.org/t/krita-4-3-0-beta-is-out-you-too-can-help-with-beta-testing/6611/29?u=mangatengu https://krita-artists.org/t/krita-4-3-0-beta-is-out-you-too-can-help-with-beta-testing/6611/31?u=mangatengu https://krita-artists.org/t/krita-4-3-0-beta-is-out-you-too-can-help-with-beta-testing/6611/33?u=mangatengu -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421485] daily builds not only for krita next
https://bugs.kde.org/show_bug.cgi?id=421485 --- Comment #3 from Manga Tengu --- Actual Nightly uses the new resources. Actually it's not workable for me as I have many bugs (I lose brushes in my presets and I can't reset brush parameters for example). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421485] daily builds not only for krita next
https://bugs.kde.org/show_bug.cgi?id=421485 --- Comment #5 from Manga Tengu --- Yay ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421584] New: File Saving is getting extremely slow
https://bugs.kde.org/show_bug.cgi?id=421584 Bug ID: 421584 Summary: File Saving is getting extremely slow Product: krita Version: 4.3.0-beta1 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Saving a 65 mb file takes up 40 seconds in average. Recently Krita has gotten really slower in file saving, but with 4.3.0-beta1 I'm dreading the file saving moment. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421584] File Saving is getting extremely slow
https://bugs.kde.org/show_bug.cgi?id=421584 --- Comment #1 from Manga Tengu --- forgot to say I have a 2018 macbook pro 15` with a good cpu. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421584] File Saving is getting extremely slow
https://bugs.kde.org/show_bug.cgi?id=421584 --- Comment #2 from Manga Tengu --- The saved file is 3508x6905px and has 16 layers -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421584] File Saving is getting extremely slow
https://bugs.kde.org/show_bug.cgi?id=421584 --- Comment #4 from Manga Tengu --- Sadly I don't have a linux with a comparable CPU. I wish I could mail the original it but it's too big. So I made a few slimming operations and tested the performance along the way which led me to interesting infos: I flattened the image -> still as slow I made the image 2/3 of the size, it got from 45 to 35 seconds I filled the layer with solid white -> saves in 1 or 2 seconds. This is proportional to the size of the file btw. So My guess is the more the final image is complex and fragmented, the slower it gets. The more solid color zones there are, the faster it is... I'm mailing you the flattened reduced file so it's a tad lower than 20 mb and fits gmail. (still the image is slow and complex -> 35 sec per save). Fill it with white, it will save fast. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421584] File Saving is getting extremely slow
https://bugs.kde.org/show_bug.cgi?id=421584 --- Comment #7 from Manga Tengu --- No I didn't, but I also tried manually trimming the file before saving as It was bleeding a lot -> no noticeable change. I can send you the sample file if your email can handle a 20mb file attachement. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421584] File Saving is getting extremely slow
https://bugs.kde.org/show_bug.cgi?id=421584 --- Comment #9 from Manga Tengu --- Here you go https://drive.google.com/open?id=18jiDSzE27-DYcMwfmTf2rksXzZOT2zHb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421584] File Saving is getting extremely slow
https://bugs.kde.org/show_bug.cgi?id=421584 --- Comment #11 from Manga Tengu --- yes originally it was bigger and had lots of layers but it was too big to share via email or here. (didn't think of drive). So I simplified it and realized it was still very slow. 43 seconds seconds to be exact on my configuration: 2018 macbook pro 15` with a good cpu. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421584] File Saving is getting extremely slow
https://bugs.kde.org/show_bug.cgi?id=421584 --- Comment #13 from Manga Tengu --- This is very interesting indeed. Leads me to think the following: In my comics workflow I have LOTS of files and I do save a lot. Since the compression difference is not significant, can we configure krita through ui settings to compression to 0 ? Can we even save files without mergedimage.png embeded files ? Then being able to command line krita to generate those mergedimage.png on demand would be very welcome. Would that affect thumbnails btw ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421584] File Saving is getting extremely slow
https://bugs.kde.org/show_bug.cgi?id=421584 --- Comment #15 from Manga Tengu --- Yes but what I understood is default level is 6, and "compress more" is 9. But as an extrem saver I'd like to know if we could set the level with a slider rahter than a checkbox so we can chose from 0 to 9 ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421844] New: setResolution, setXRes, setYRes, scaleImage not working
https://bugs.kde.org/show_bug.cgi?id=421844 Bug ID: 421844 Summary: setResolution, setXRes, setYRes, scaleImage not working Product: krita Version: 4.3.0-beta1 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Make a new image via the scripting tool, the image resolution should be 288 ppi no matter how you try to change it: I tried scaleImage, setResolutionn setXRes and seYRes without success. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417312] Krita nightly terminated after splash
https://bugs.kde.org/show_bug.cgi?id=417312 --- Comment #16 from Manga Tengu --- When opening a kra file with krita NOT launched, krita fails to start and needs to be reopened. build 9dffafb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418937] New: When krita is not opened, double clicking a kra file crashes
https://bugs.kde.org/show_bug.cgi?id=418937 Bug ID: 418937 Summary: When krita is not opened, double clicking a kra file crashes Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- When Krita is not running, go in finder and double click a kra file. Krita will crash on splash screen and the os will propose to reopen. Click reopen, krita opens correctly This has appeared with https://bugs.kde.org/show_bug.cgi?id=417312#add_comment git hash: 9dffafb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417312] Krita nightly terminated after splash
https://bugs.kde.org/show_bug.cgi?id=417312 --- Comment #18 from Manga Tengu --- Sure ! https://bugs.kde.org/show_bug.cgi?id=418937 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418999] New: Krita with wrong zip headers cannot be viewed in scribus
https://bugs.kde.org/show_bug.cgi?id=418999 Bug ID: 418999 Summary: Krita with wrong zip headers cannot be viewed in scribus Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Some kra files can't be viewed in scribus when inserted there. drag and drop the following kra file in scribus: https://filebin.net/blnehkvmndquf7ee/Lineage_c005_p13.kra?t=52r8dsgz The file doesn't show in scribus which says "image not found" I talked to the guys over scribus and opened a ticket where they mentioned the malformed zip header: https://bugs.scribus.net/view.php?id=16067 EXPECTED RESULT The mergedImage should show in scribus SOFTWARE/OS VERSIONS krita 4.3.0-prealpha git 9dffafb macOS: Catalina 10.15.3 (19D76) ADDITIONAL INFORMATION At first I thought it was a size issue and resizing the canvas to a smaller size did help. But I had inconsistent results. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418999] Krita with wrong zip headers cannot be viewed in scribus
https://bugs.kde.org/show_bug.cgi?id=418999 Manga Tengu changed: What|Removed |Added Platform|Other |macOS Disk Images OS|Linux |macOS -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419000] New: Canvas input navigation shortcuts not working when going to full screen mode
https://bugs.kde.org/show_bug.cgi?id=419000 Bug ID: 419000 Summary: Canvas input navigation shortcuts not working when going to full screen mode Product: krita Version: nightly build (please specify the git hash!) Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- SUMMARY When I go to full screen mode, I can't pan, zoom, rotate with shortcuts involving the mouse. I can ctrl + + or ctrl + - to zoom in or out but using the shortcut involving the mouse will not do. STEPS TO REPRODUCE 1. Be in windowed mode 2. Go in full screen mode and don't switch to another application (this is actually the workaround to unlock the situation) 3. Try to use your mouse involving shortcut to pan or zoom OBSERVED RESULT Nothing happens EXPECTED RESULT Panning, zooming, rotating... SOFTWARE/OS VERSIONS Krita 4.0.3-prealpha git 9dffafb macOS: Catalina 10.15.3 (19D76) ADDITIONAL INFORMATION This happened after fixing the issue with popup dockers quitting the full screen mode on macOS -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419093] New: call to Node.mergeDown() exits krita
https://bugs.kde.org/show_bug.cgi?id=419093 Bug ID: 419093 Summary: call to Node.mergeDown() exits krita Product: krita Version: nightly build (please specify the git hash!) Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Created attachment 126936 --> https://bugs.kde.org/attachment.cgi?id=126936&action=edit a script that loads a file, creates a view on it. Adds an extra solid layer at the bottom and merges When I call mergeDown() on a Node with the scripting console, krita shuts down abruptly STEPS Load a file (tried with jpg and png) edit the (attached) script to load it run the script OBSERVED RESULT krita shuts down. If you comment the mergeDown call, krita won't shut down EXPECTED RESULT The layer is merged SOFTWARE/OS VERSIONS Krita 4.3.0-prealpha git 9dffafb macOS: Catalina 10.15.3 (19D76) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419093] call to Node.mergeDown() exits krita
https://bugs.kde.org/show_bug.cgi?id=419093
Manga Tengu changed:
What|Removed |Added
Attachment #126936|a script that loads a file, |a script that tries to
description|creates a view on it. Adds |mergeDown a layer
|an extra solid layer at the |
|bottom and merges |
--- Comment #1 from Manga Tengu ---
Comment on attachment 126936
--> https://bugs.kde.org/attachment.cgi?id=126936
a script that tries to mergeDown a layer
>from krita import *
>
>doc = Application.openDocument("PathToImage")
>window = Application.activeWindow()
>view = window.addView(doc)
>window.showView(view)
>paintLayer = doc.createNode("Background1", "paintLayer")
>i = InfoObject()
>i.setProperty("color", "white")
>s = Selection()
>s.select(0, 0, doc.width(), doc.height(), 255)
>fillLayer = doc.createFillLayer("Background2", "color", i, s)
>root = doc.rootNode()
>children = root.childNodes()
>root.setChildNodes([fillLayer, paintLayer, children[0]])
>children = root.childNodes()
>children[1].mergeDown()
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 412740] Krita leaks memory on exporting multiple pages from the comics manager
https://bugs.kde.org/show_bug.cgi?id=412740 Manga Tengu changed: What|Removed |Added CC||mangate...@gmail.com --- Comment #12 from Manga Tengu --- subscribing! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419111] New: krita crashes whith looping calls to setPixelData
https://bugs.kde.org/show_bug.cgi?id=419111 Bug ID: 419111 Summary: krita crashes whith looping calls to setPixelData Product: krita Version: nightly build (please specify the git hash!) Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Created attachment 126943 --> https://bugs.kde.org/attachment.cgi?id=126943&action=edit A very nice script I made a script batch some png in a folder and output corresponding kra files with a white background and a disabled desaturation filter on top Opening a lot of those png files at once works fine. Opening 2 or 3 of those files with a loop call to Node.setPixelData to fill a paint layer crashes krita. STEPS TO REPRODUCE 1. Have a root folder with png subfolder containing 5 A3 300dpi png files and a kra destination like so: testFoler/ |_png/ |_kra/ 2. Adapt the paths in the script (3 of them line 3, 4, 38) 3. Run the script OBSERVED RESULT Krita crashes EXPECTED RESULT 1. Corona virus is destroyed... 2. All png files have an equivalent kra file with a white background and a disabled desaturate 3rd mode desaturation filter and the drawing layer active. SOFTWARE/OS VERSIONS Krita 4.3.0-prealpha git 9dffafb but also krita 4.2.8 macOS: Catalina 10.15.3 (19D76) ADDITIONAL INFORMATION The script is attached -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419112] New: Ten scripts not working on macOS
https://bugs.kde.org/show_bug.cgi?id=419112
Bug ID: 419112
Summary: Ten scripts not working on macOS
Product: krita
Version: nightly build (please specify the git hash!)
Platform: macOS Disk Images
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: Scripting
Assignee: krita-bugs-n...@kde.org
Reporter: mangate...@gmail.com
Target Milestone: ---
using {cmd|ctrl} + shift + 1, 2 ... on my (azerty) keyboard doesn't launch
script.
And loading scripts in the tenscript dialog only shows after restarting krita
STEPS TO REPRODUCE
1. Add a script to Ten scripts
2. Reopen the dialog and see it's not there
3. Restart and see it is there
4. Try to use it with the shortcut
OBSERVED RESULT
Nothing happens
EXPECTED RESULT
Script is launched. Best of all would be to have an option for the stdout to
popup
SOFTWARE/OS VERSIONS
Krita 4.3.0-prealpha git 9dffafb
macOS: Catalina 10.15.3 (19D76)
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 376559] New: Still not working: Cumulative undo
https://bugs.kde.org/show_bug.cgi?id=376559 Bug ID: 376559 Summary: Still not working: Cumulative undo Product: krita Version: 3.1.2 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Yes now you can check cumulative undo, but it won't have any effect at all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376744] New: Krita file layer not found
https://bugs.kde.org/show_bug.cgi?id=376744 Bug ID: 376744 Summary: Krita file layer not found Product: krita Version: 3.1.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- File layers are not found when you open or command-line export a kra file. This is a bug that was supposed to be fixed by changing the path of the appImage or something (see Boud for more detail, I gave him a kra file with a file layer as a sample at the time). But it's still not working. And also, now everytime you want to save or load a file, the dialog box that shows up doesn't remember the last location you entered but the temp directory in which the appImage is working or so... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375070] Cumulative undo not working
https://bugs.kde.org/show_bug.cgi?id=375070 Manga Tengu changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #5 from Manga Tengu --- In V3.1.2 the bug is not fixed yet -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375070] Cumulative undo not working
https://bugs.kde.org/show_bug.cgi?id=375070 --- Comment #6 from Manga Tengu --- The checkbox is saved, but the effect is not there -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375070] Cumulative undo not working
https://bugs.kde.org/show_bug.cgi?id=375070 --- Comment #7 from Manga Tengu --- *** Bug 376559 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376559] Still not working: Cumulative undo
https://bugs.kde.org/show_bug.cgi?id=376559 Manga Tengu changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Manga Tengu --- *** This bug has been marked as a duplicate of bug 375070 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376774] New: Translating layer nested in a group layer only refresh if transparency mask is disabled
https://bugs.kde.org/show_bug.cgi?id=376774 Bug ID: 376774 Summary: Translating layer nested in a group layer only refresh if transparency mask is disabled Product: krita Version: 3.1.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Translation Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Created attachment 104153 --> https://bugs.kde.org/attachment.cgi?id=104153&action=edit a kra setup for quick test Translation of layers nested inside group layers is not refreshing when there is a Transparency layer activated inside the group layer. I attached a kra file with such setup. Layers have explicit names. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376777] New: Magic Wand not working on big files
https://bugs.kde.org/show_bug.cgi?id=376777 Bug ID: 376777 Summary: Magic Wand not working on big files Product: krita Version: 3.1.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Created attachment 104155 --> https://bugs.kde.org/attachment.cgi?id=104155&action=edit Kra file already set up and consistently bugging on my machine. !! BEFORE YOU TEST THE SAMPLE FILE !! You need to resize the image as I shrunk it down to attach it here. The real hight is 4960px and consequently the width is 3508px. !! THEN YOU CAN GO ON !! When using the magic wand and clicking to select, sometimes nothing happens with "big" files like A3 300dpi : So here I am, with my proud Frame layer delimiting my panels. I click inside each hole (limit selection to current layer) and transform the selection into transparency masks for each panel (which are group layers) to make sure my strokes don't overlap between panels (the thickness of the frame is not enough to cover my strokes). I realized recently the magic wand was working kind of randomly. Sometimes I use the wand and it's fine sometimes not. So I took my actual file where it is consistently bugging and marked down where it works and where it doesn't: I can only select the first hole I checked in green in my attachment sample kra file. The others won't work (unless I resize down the file so it can be attached). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376993] New: File layer convert
https://bugs.kde.org/show_bug.cgi?id=376993 Bug ID: 376993 Summary: File layer convert Product: krita Version: 3.1.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Created attachment 104251 --> https://bugs.kde.org/attachment.cgi?id=104251&action=edit Terminal's output during a crash When I convert a file layer to paint layer, then paint without closing the file between conversion and painting, after 50-60 strokes (brush around 110px wide on an A3 300dpi), krita crashes systematically (it closes in the blink of an eye). If I paint over a file where I did the conversion but closed krita between conversion and painting, it will work fine. I tried to get a hint (maybe it's my machine ?...) so I launched via terminal and logged krita's output in a txt file I attached. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374218] New: krita [command] from appImage not working
https://bugs.kde.org/show_bug.cgi?id=374218 Bug ID: 374218 Summary: krita [command] from appImage not working Product: krita Version: 3.1.1 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- I have some scripts to batch export & resize my kra files as I draw my manga. This is a very convenient tool as I have lots of pages to proceed. Works fine with krita from apt-get since a long while now. However with krita appImage it doesn't work. it gives me: "File /tmp/.mount_VWclcQ/usr/waste_c7_p10.kra does not exist" with "waste_c7_p10.kra" being the name of the file proceeded. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374222] New: file layer export bug
https://bugs.kde.org/show_bug.cgi?id=374222 Bug ID: 374222 Summary: file layer export bug Product: krita Version: 3.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- When exporting a .kra containing a file layer which displays correctly the krita app will ask you to relocate the file because it doesn't find it at "X" while X is actually the right path. Then I need to specify the file by hand for each file in my batch everytime. This happens to me with krita 2.9.7 and the 3.1.1 appImage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374223] creating new file layer
https://bugs.kde.org/show_bug.cgi?id=374223 Manga Tengu changed: What|Removed |Added Summary|creatingnew file layer |creating new file layer -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374223] New: creatingnew file layer
https://bugs.kde.org/show_bug.cgi?id=374223 Bug ID: 374223 Summary: creatingnew file layer Product: krita Version: 3.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Importing a file as a new file layer will result in an empty layer systematically. It works fine with 2.9.7 though. So as a workaround I import with 2.9.7 and then work in 3.1.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374222] file layer export bug
https://bugs.kde.org/show_bug.cgi?id=374222 --- Comment #2 from Manga Tengu --- Created attachment 103034 --> https://bugs.kde.org/attachment.cgi?id=103034&action=edit my script my lovely script -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374222] file layer export bug
https://bugs.kde.org/show_bug.cgi?id=374222 --- Comment #5 from Manga Tengu --- (In reply to Boudewijn Rempt from comment #3) > What is the full path to the place from where you run the script? Added an attachement, lost my comment :(... So I was saying: I'm doing it in the commandLine via my trusty shell script that usually works fine as long as there is no file layer in the kra file. The real path to the kra: /media/b/3A6C7A2A6C79E155/Images WASTE/Manga/chapitre_7/pages/kra The real path to the file layer: /media/b/3A6C7A2A6C79E155/Images WASTE/Manga/chapitre_7/pages/svg/png I place myself in the real path and launch my script (the attachement) and get: The file associated to a file layer with the name "Cache" is not found. Expected path: /../svg/png/waste_c7_p10.png Do you want to locate it manually? if I concat the kra path and this relative path I get: /media/b/3A6C7A2A6C79E155/Images WASTE/Manga/chapitre_7/pages/kra/../svg/png/waste_c7_p10.png which is right (file name included). Please note 3A6C7A2A6C79E155 is the name of my hard drive I mount. I get the same issue with 2.9.7 and 3.1.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374222] file layer export bug
https://bugs.kde.org/show_bug.cgi?id=374222 --- Comment #6 from Manga Tengu --- (In reply to Boudewijn Rempt from comment #4) > (Oh, and btw -- why don't you just get the mergedimage.png from the .kra > file?) You mean pixelate the file layer into a regular paint layer ? If I need to modify it later I lose the advantage of file layer. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374218] working dir of appimage is not the dir from which the appimage is started
https://bugs.kde.org/show_bug.cgi?id=374218 --- Comment #2 from Manga Tengu --- (In reply to Boudewijn Rempt from comment #1) > That's because the working dir of krita running from the appimage is > different; the export command will work if you specify the path to the > image, like > > bin/krita-3.1.1-x86_64.appimage ~/bla.kra --export --export-filename > ~/bla.jpg If I have to hardcode the location of the file it works but it means for every location I put files in for transformation I need to input the location by hand. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374222] file layer export bug
https://bugs.kde.org/show_bug.cgi?id=374222 --- Comment #8 from Manga Tengu --- (In reply to Boudewijn Rempt from comment #7) > Hm... I'd also like to see one of the kra files. If there's a path in there > that really starts with a /, then that's obviously one of the problems. At > that point it's no longer relative but absolute. It might also be a problem > that there's a space in the path. > > The other thing is that a .kra file is a zip file; inside the zip file is a > full-size preview of your image in png format. Getting that instead of > asking krita to convert the image to png is more efficient. The / I'm writing is to give you the absolute path. In the script it's not present as I execute the script right aside from the files. The script actually just calls a file name with no directories before. There are no spaces in the kra files names. Btw Yes I'll gladly use that ready to use png, but how do I access it ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374222] file layer export bug
https://bugs.kde.org/show_bug.cgi?id=374222 --- Comment #10 from Manga Tengu --- (In reply to Boudewijn Rempt from comment #9) > Use the "unzip" utility to extract the file -- it's always called the same > thing. But I'd still like to have access to one of your files to see what's > up... I managed to get it under 4mb (60 originally) so here you go -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374222] file layer export bug
https://bugs.kde.org/show_bug.cgi?id=374222 --- Comment #11 from Manga Tengu --- Created attachment 103036 --> https://bugs.kde.org/attachment.cgi?id=103036&action=edit kra sample file the kra file. I'll set the file layer which is called Cache in another attachement -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374222] file layer export bug
https://bugs.kde.org/show_bug.cgi?id=374222 --- Comment #12 from Manga Tengu --- Created attachment 103037 --> https://bugs.kde.org/attachment.cgi?id=103037&action=edit file layer Cache is the file layer for the sample kra file it is the same size and resolution -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374222] file layer export bug
https://bugs.kde.org/show_bug.cgi?id=374222 --- Comment #13 from Manga Tengu --- Please not that this time adding a file layer worked...maybe because I reduced the size of the kra file ? (In another bug report (374223) I reported it didn't work with the 3.1.1 appImage but it seems more tricky than that. I'll continue this in the other report) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374223] creating new file layer
https://bugs.kde.org/show_bug.cgi?id=374223
--- Comment #2 from Manga Tengu ---
I got it:
the kra file is on a mounted hard drive and I can access it several ways :
1---
If I access it via its physical path
/media/user/blabla/**/*.kra
I can add new file layers.
2---
If I access it via my symbolic link
/home/user/Pictures/{ln}/**/*.kra
It will add an empty file layer
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 375070] New: Cumulative undo not working
https://bugs.kde.org/show_bug.cgi?id=375070 Bug ID: 375070 Summary: Cumulative undo not working Product: krita Version: 3.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- using AppImage. Checking cumulative undo will not be taken into account. Cumulative undo won't work. Opening the undo settings again, you can see it is unchecked as before. BTW this feature is really useful, I think it should be easier to spot. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 493912] The dmg for 5.2.6 doesn't open
https://bugs.kde.org/show_bug.cgi?id=493912 --- Comment #4 from Manga Tengu --- Yes indeed now it works, but I entered the suffix by hand as it seems the link is cached and not updating on my local machine. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 493912] New: The dmg for 5.2.6 doesn't open
https://bugs.kde.org/show_bug.cgi?id=493912 Bug ID: 493912 Summary: The dmg for 5.2.6 doesn't open Classification: Applications Product: krita Version: 5.2.6 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- I set this as critical, supposing it was not specific to my configuration. I hope you don't hold a grudge on me if it IS just me in the end :') The diskimage is unmountable on my M1 disk image: The disk image couldn't be opened Disk image operation failed with error code 3840 I'm actually using 5.2.2 on sonoma 14.5 (23F79) on a M1 macbook pro 16" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 493982] Shortuct customization not taken into account
https://bugs.kde.org/show_bug.cgi?id=493982 Manga Tengu changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|FIXED |--- --- Comment #2 from Manga Tengu --- Even after that, in my current state, trying to assign shift + ; doesn't seem to work (for toggle layer alpha inheritence, nor freehand selection tool) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 493982] Shortuct customization not taken into account
https://bugs.kde.org/show_bug.cgi?id=493982 Manga Tengu changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #1 from Manga Tengu --- Wiping my resource folder unlocked assigning shortcuts again, I'll try to see if things degrade again or if I had something dirty lurking in my resource folder -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 493982] New: Shortuct customization not taken into account
https://bugs.kde.org/show_bug.cgi?id=493982 Bug ID: 493982 Summary: Shortuct customization not taken into account Classification: Applications Product: krita Version: 5.2.2 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- On macOS sonoma 14.5 (23F79) TL;DR: the more I assign shortcuts, the less they are effective, until they don't change anymore. The long story: I've noticed I sometimes needed to repeat shortcuts' assignment several times. Then as I kept customizing over the days I realized it wasn't working anymore. I reset everything, thinking I may have set something really wrong. I redid all the config in less than an hour. First shortcuts work flawlessly At a certain point I need to assign the shortcuts several time for them to be effective. Then at another threshold, I can repeat assignments as much as I want without it being effective. To reproduce: - customize dozens of shortcuts in main or alternative + canvas inputs Observed: - sometimes when going back to the shortcut assignment, you can see the old shortcut - sometimes you see the right shortcut, but it doesn't work Disclaimer: I use Karabiner, a key remapper for macOS, but quitting it doesn't make the shortcuts work -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366116] New: Tag assignment fails in the paint to preset dropdown list
https://bugs.kde.org/show_bug.cgi?id=366116 Bug ID: 366116 Summary: Tag assignment fails in the paint to preset dropdown list Product: krita Version: 3.0 Platform: Windows CE OS: Windows CE Status: UNCONFIRMED Severity: minor Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com In the toolbar brushes and co there is a dropdown to chose a paint preset just right to the brush parameters. In this dropdown, if you right click on a brush and try to add a new tag or assign one, it will disappear and not work. I have to use the the brush preset panel to make it work. btw the search field in that panel is so efficient that if you prefix your brushes correctly, it will act like tags. It's very useful since when I import a preset, the tag assignment is not imported so I have to reassign the brushes to their tags every time (can't use bundles, they have other issues that make merging them together to update them quite painfull) Reproducible: Always Steps to Reproduce: 1.Open the paintToPreset dropdown in the brush and co 2. right click a brush 3. try to assign a new or existing tag to it Actual Results: the dialog disappears and nothing happens Expected Results: tags are happily assigned windows 10 krita 3.0 portable -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363096] New: Free transform after a perspective transform
https://bugs.kde.org/show_bug.cgi?id=363096 Bug ID: 363096 Summary: Free transform after a perspective transform Product: krita Version: 2.9.11 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Application: krita (2.9.11) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 3.19.0-32-generic x86_64 Distribution: Linux Mint 17.3 Rosa -- Information about the crash: - What I was doing when the application crashed: begun a free transform after a perspective deformation of a transform mask -- Backtrace: Application: Krita (krita), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd2edb5d7c0 (LWP 3227))] Thread 15 (Thread 0x7fd2b8b85700 (LWP 3242)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd2eb70f816 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7fd2eb70b95b in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7fd2e98dd5f0 in waitForWork (this=0x22076a0) at /build/krita-2.9-INmjI7/krita-2.9-2+git20160202+r46/krita/image/tiles3/kis_tile_data_pooler.cc:165 #4 KisTileDataPooler::run (this=0x22076a0) at /build/krita-2.9-INmjI7/krita-2.9-2+git20160202+r46/krita/image/tiles3/kis_tile_data_pooler.cc:187 #5 0x7fd2eb70f32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fd2e57a9182 in start_thread (arg=0x7fd2b8b85700) at pthread_create.c:312 #7 0x7fd2eaeaf47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 14 (Thread 0x7fd2b27fc700 (LWP 3243)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd2eb70f816 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7fd2eb70bd63 in QSemaphore::tryAcquire(int, int) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7fd2e99063a3 in KisTileDataSwapper::waitForWork (this=) at /build/krita-2.9-INmjI7/krita-2.9-2+git20160202+r46/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #4 0x7fd2e99065da in KisTileDataSwapper::run (this=0x22076e0) at /build/krita-2.9-INmjI7/krita-2.9-2+git20160202+r46/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #5 0x7fd2eb70f32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fd2e57a9182 in start_thread (arg=0x7fd2b27fc700) at pthread_create.c:312 #7 0x7fd2eaeaf47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 13 (Thread 0x7fd2c7e2a700 (LWP 3244)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd2eb70f816 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7fd2ec6dbe16 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #3 0x7fd2eb70f32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7fd2e57a9182 in start_thread (arg=0x7fd2c7e2a700) at pthread_create.c:312 #5 0x7fd2eaeaf47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 12 (Thread 0x7fd2b2ffd700 (LWP 3245)): #0 0x7fd2e57ac7ee in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7fd2aa2afbf0) at pthread_mutex_unlock.c:57 #1 __GI___pthread_mutex_unlock (mutex=0x7fd2aa2afbf0) at pthread_mutex_unlock.c:310 #2 0x7fd2e530b9b1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd2e52c98f9 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd2e52c9f52 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd2e52ca0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fd2eb83e7be in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7fd2eb8100af in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7fd2eb8103a5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7fd2eb70cc5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7fd2eb7f1823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7fd2eb70f32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x7fd2e57a9182 in start_thread (arg=0x7fd2b2ffd700) at pthread_create.c:312 #13 0x7fd2eaeaf47d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 11 (Thread 0x7fd2b37fe700 (LWP 3248)): #0 0x7fd2e530b613 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd2e530b9a9 in g_mutex_unlock () from /li
[krita] [Bug 363096] Free transform after a perspective transform
https://bugs.kde.org/show_bug.cgi?id=363096 --- Comment #3 from Manga Tengu --- Ok so the problem happens with a file which has a Transform layer on a folder which contain 2 layers having each one a transform layer. That's a complex set up that allows me to draw orthogonal faces of a volume, then transform them separately into perspective, then transforming the total into perspective. Then rework orthogonally if needed. To illustrate it, i took a few screenshots I ordered and described in the file names: http://filebin.net/8z5r9338z2/shots.7z -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363096] Free transform after a perspective transform
https://bugs.kde.org/show_bug.cgi?id=363096 --- Comment #4 from Manga Tengu --- Also please note, when imported as a file layer, krita crashes -- You are receiving this mail because: You are watching all bug changes.
