[krita] [Bug 446757] Appimage update does not work, underlying mechanism is either not present or not executable.
https://bugs.kde.org/show_bug.cgi?id=446757 --- Comment #10 from Anna Medonosova --- Hi, amyspark, > One mo, shouldn't these be > https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/ > lastSuccessfulBuild/artifact/Krita-Plus-x86_64.appimage.zsync and > https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/ > lastSuccessfulBuild/artifact/Krita-Next-x86_64.appimage.zsync? I think the naming gets a little confusing, as there is a mismatch between branding/update channel and binary factory job names. For clarity, I have summarized it in the following table. > +-+-+---+ > | Channel | binary factory job | >zsync url > | > +-+--+---+ > | Next| Krita_Nightly_Appimage_Build | > https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/Krita-Next-x86_64.appimage.zsync > | > | Plus| Krita_Stable_Appimage_Build | > https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/lastSuccessfulBuild/artifact/Krita-Plus-x86_64.appimage.zsync > | > | Beta| Krita_Release_Appimage_Build | the > https://download.kde.org/unstable/krita/updates/Krita-Beta-x86_64.appimage.zsync > | > | Stable | Krita_Release_Appimage_Build | > https://download.kde.org/stable/krita/updates/Krita-Stable-x86_64.appimage.zsync > | > +-+--+---+ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446757] Appimage update does not work, underlying mechanism is either not present or not executable.
https://bugs.kde.org/show_bug.cgi?id=446757 Anna Medonosova changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446757] Appimage update does not work, underlying mechanism is either not present or not executable.
https://bugs.kde.org/show_bug.cgi?id=446757 Anna Medonosova changed: What|Removed |Added Status|ASSIGNED|CONFIRMED CC||anna.medonosova@protonmail. ||com --- Comment #2 from Anna Medonosova --- Hi, Wolthera, I can reproduce the issue in the betas, Plus and 5.0.0 stable version. I have filed a MR that should fix embedding of the AppImageUpdate tool. There is also a second issue that breaks the update process: the zsync files are missing on the download server. The update mechanism expects the zsync files to be available as https://download.kde.org/unstable/krita/updates/Krita-Beta-x86_64.appimage.zsync for stable version and https://download.kde.org/stable/krita/updates/Krita-Stable-x86_64.appimage.zsync for betas. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445179] Krita crashes when opening a file with 16-bit int depth
https://bugs.kde.org/show_bug.cgi?id=445179 --- Comment #6 from Anna Medonosova --- Created attachment 144002 --> https://bugs.kde.org/attachment.cgi?id=144002&action=edit system information for bug reports (android) I'm attaching the system information. The device is a Samsung Galaxy Tab S6, if that's relevant. Thanks for looking into it :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445179] Krita crashes when opening a file with 16-bit int depth
https://bugs.kde.org/show_bug.cgi?id=445179 Anna Medonosova changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445179] Krita crashes when opening a file with 16-bit int depth
https://bugs.kde.org/show_bug.cgi?id=445179 --- Comment #1 from Anna Medonosova --- Created attachment 143352 --> https://bugs.kde.org/attachment.cgi?id=143352&action=edit test file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445179] New: Krita crashes when opening a file with 16-bit int depth
https://bugs.kde.org/show_bug.cgi?id=445179 Bug ID: 445179 Summary: Krita crashes when opening a file with 16-bit int depth Product: krita Version: git master (please specify the git hash!) Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 143351 --> https://bugs.kde.org/attachment.cgi?id=143351&action=edit backtrace of the crash SUMMARY When I try to open a file with 16-bit int depth color profile, Krita crashes upon loading the file. 8-bit documents are opened correctly. I'm attaching a test file triggering the crash and a backtrace. STEPS TO REPRODUCE 1. Open a file with 16-bit depth profile OBSERVED RESULT Krita crashes. EXPECTED RESULT The file is opened. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445127] New: Saving files opened from a file manager silently fails
https://bugs.kde.org/show_bug.cgi?id=445127 Bug ID: 445127 Summary: Saving files opened from a file manager silently fails Product: krita Version: git master (please specify the git hash!) Platform: Android OS: Android 11.x Status: REPORTED Severity: major Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 143314 --> https://bugs.kde.org/attachment.cgi?id=143314&action=edit usage log SUMMARY On Android (Samsung Galaxy Tab S6), when I open a .kra file from within a file manager, make changes and want to save later, the file is not saved and there is no error shown. Also, there is no 'saving document' progress bar down in the status bar (the progress bar shows up for the same file opened from within Krita). The log does not even show a save operation. 'Save as' works normally. Saving documents opened from within Krita works correctly. STEPS TO REPRODUCE 1. open a .kra file from a file manager 2. make a change 3. click the save button OBSERVED RESULT The change is not saved. There is no corresponding save operation in the log file. EXPECTED RESULT Ideally, the file is saved. If that is not possible, there should be an error message shown to the user. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438324] Specific PSD file causes color selector and canvas glitches
https://bugs.kde.org/show_bug.cgi?id=438324 Anna Medonosova changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Anna Medonosova --- (In reply to wolthera from comment #6) > anna, is this still happening with the latest appimage? Amyspark added some > important patches to LCMS. (though, you might need to use the nightly, I > don't recall if they cherry-picked it to 5.0...) Hi, Wolthera, I tried reproducing the issue on git 6a5e83d (AppImage and local builds for Linux and Android). The visual glitches are gone. I'm marking the bug as resolved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438549] Mirror tool handle is not displayed on canvas
https://bugs.kde.org/show_bug.cgi?id=438549 --- Comment #8 from Anna Medonosova --- Created attachment 140408 --> https://bugs.kde.org/attachment.cgi?id=140408&action=edit screenshot with handles missing -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438549] Mirror tool handle is not displayed on canvas
https://bugs.kde.org/show_bug.cgi?id=438549 Anna Medonosova changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #7 from Anna Medonosova --- (In reply to Dmitry Kazakov from comment #5) > Hi, Anna! > > Could you please make a screenshot of the problem? I cannot understand what > is wrong with the handles on your side. I've just retested on Linux and the > handles are painted correctly here :( Hi! yesterday I have retested on git efe590e (nightly appimage on linux, local build for Android). In this version, the handles were displayed correctly on both platforms. In the previous versions, the circle with the arrow was missing, only the dashed lines were present. (I will attach a screenshot.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440211] Crash when selecting some presets in brush editor
https://bugs.kde.org/show_bug.cgi?id=440211 Anna Medonosova changed: What|Removed |Added Attachment #140290|system |system information for bug description||reports -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440211] Crash when selecting some presets in brush editor
https://bugs.kde.org/show_bug.cgi?id=440211 --- Comment #1 from Anna Medonosova --- Created attachment 140290 --> https://bugs.kde.org/attachment.cgi?id=140290&action=edit system -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440211] New: Crash when selecting some presets in brush editor
https://bugs.kde.org/show_bug.cgi?id=440211 Bug ID: 440211 Summary: Crash when selecting some presets in brush editor Product: krita Version: git master (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 140289 --> https://bugs.kde.org/attachment.cgi?id=140289&action=edit backtrace of the crash SUMMARY When some presets are either selected in the brush editor, or they are first selected in other widgets and then the brush editor is opened, Krita crashes. I have reproduced the crash with the "f) Bristles" group of presets, "b) Basic-6 Details" and presets from the "Charcoal KA" and "Digital Atelier" bundles. STEPS TO REPRODUCE A. 1. select the "f) Bristles-1 Details" preset 2. open the brush editor 3. crash B. 1. open the brush editor 2. select the "f) Bristles-1 Details" preset in the list on the left 3. crash OBSERVED RESULT Krita crashes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438549] Mirror tool handle is not displayed on canvas
https://bugs.kde.org/show_bug.cgi?id=438549 Anna Medonosova changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #4 from Anna Medonosova --- (In reply to Dmitry Kazakov from comment #2) > Hi, Anna! > > Could you please check if the bug is still actual? I tested the current > master and it seems like the bug is not here anymore Hi, Dmitry, I can confirm the issue is still there in git b66a85a, both locally built and in the appimage from the Binary Factory. I have tested turning off canvas acceleration in the settings. When acceleration is turned off, the mirror tool handles are displayed correctly. However, with acceleration on, the handles do not appear. I have updated nvidia drivers to 460.91.03 in the meantime (I had 460.80 previously), but that didn't help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438549] Mirror tool handle is not displayed on canvas
https://bugs.kde.org/show_bug.cgi?id=438549 Anna Medonosova changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438549] New: Mirror tool handle is not displayed on canvas
https://bugs.kde.org/show_bug.cgi?id=438549 Bug ID: 438549 Summary: Mirror tool handle is not displayed on canvas Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 139285 --> https://bugs.kde.org/attachment.cgi?id=139285&action=edit system information for bug reports SUMMARY When I turn on either the horizontal or vertical mirror tool, a dashed line appears on the canvas and brush strokes are mirrored. However, the handle is missing and so the line cannot be moved. The "Lock line" checkbox is unchecked. If you check and uncheck the checkbox, the handle does not appear. STEPS TO REPRODUCE 1. Turn on horizontal or vertical mirror (buttons in the toolbar OBSERVED RESULT The handle is missing. EXPECTED RESULT The handle should be displayed on canvas, unless "Lock line" checkbox is checked. ADDITIONAL INFORMATION Version: 5.0.0-prealpha (git 4f029a8) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438324] Specific PSD file causes color selector and canvas glitches
https://bugs.kde.org/show_bug.cgi?id=438324 --- Comment #4 from Anna Medonosova --- Created attachment 139168 --> https://bugs.kde.org/attachment.cgi?id=139168&action=edit system information for bug reports (android) On Android, I can't reproduce the glitches on canvas with 5.0.0-prealpha (git 884a064) I have built today. The triangle in the Advanced color selector is invisible. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438324] Specific PSD file causes color selector and canvas glitches
https://bugs.kde.org/show_bug.cgi?id=438324 --- Comment #3 from Anna Medonosova --- Created attachment 139166 --> https://bugs.kde.org/attachment.cgi?id=139166&action=edit system information for bug reports (appimage) I have retested with AppImage 5.0.0-prealpha (git 607fca8). I can still reproduce the issue. I'm attaching system information for bug reports to this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438324] Specific PSD file causes color selector and canvas glitches
https://bugs.kde.org/show_bug.cgi?id=438324 --- Comment #1 from Anna Medonosova --- Created attachment 139139 --> https://bugs.kde.org/attachment.cgi?id=139139&action=edit selector glitches -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438324] New: Specific PSD file causes color selector and canvas glitches
https://bugs.kde.org/show_bug.cgi?id=438324 Bug ID: 438324 Summary: Specific PSD file causes color selector and canvas glitches Product: krita Version: git master (please specify the git hash!) Platform: Appimage OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 139138 --> https://bugs.kde.org/attachment.cgi?id=139138&action=edit test file SUMMARY When a specific PSD file is open, color selectors (advanced, specific and internal on Linux, on Android also the one in popu palette) and canvas (on Android) become unusable due to various visual glitches. The image also does not work when saved as or exported. On Android I have also seen some kind of storage error. A way to recover the image is to copy the layers to a different document. I suspect it may have something to do with the document color space, but I'm not sure about that. I have observed the issue in latest nightly appimage and on Android git master build. In the 4.4.3 appimage, the glitches are not present. STEPS TO REPRODUCE 1. Open testimage.psd (attached to this report) OBSERVED RESULT The color selectors disappear, are displaced or display other glitches. The canvas shows only portions of the document. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437663] New: Long press does not work in floating dockers
https://bugs.kde.org/show_bug.cgi?id=437663 Bug ID: 437663 Summary: Long press does not work in floating dockers Product: krita Version: git master (please specify the git hash!) Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY When a docker is floating, long press (used instead of right click on Android) is not registered. A tap (left click) is registered instead. When the dockers are docked into the side toolbars, it works correctly. I have tested this issue in the Advanced Color Selector and Layers dockers, with the SPen. STEPS TO REPRODUCE A) 1. Undock the Advanced Color Selector 2. Long-press on the color selector to change background color => background color is unchanged B) 1. Undock the Layers docker 2. Long-press on a layer name => nothing happens (a context menu should appear -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418855] Layer content is invisible after applying transform on a system under load
https://bugs.kde.org/show_bug.cgi?id=418855 Anna Medonosova changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Anna Medonosova --- Hi, Dmitry, with your appimage I couldn't reproduce the issue anymore (while it shows up quite consistently on the 4.4.3 appimage). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437365] New: Numbered value scale in artistic color selector does not show numbers
https://bugs.kde.org/show_bug.cgi?id=437365 Bug ID: 437365 Summary: Numbered value scale in artistic color selector does not show numbers Product: krita Version: git master (please specify the git hash!) Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY When numbered value scale is turned on in the Artistic color selector, a grayscale strip with numbers is shown on the lefy of the selector. On Android, the strip is shown correctly, but the numbers are missing. STEPS TO REPRODUCE 1. Turn on numbered value scale in the selector settings OBSERVED RESULT The gray strip is shown on the left side of the docker, however, the numbers are missing. EXPECTED RESULT The gray strip should have numbers on top. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436858] New: Long press on the brush preset chooser closes the popup
https://bugs.kde.org/show_bug.cgi?id=436858 Bug ID: 436858 Summary: Long press on the brush preset chooser closes the popup Product: krita Version: git master (please specify the git hash!) Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY When I long-press a brush preset in the left half of the preset chooser (the one on the toolbar), a context menu is shown. However, when I do the same on the right half, the popup is closed instead. The preset chooser docker works correctly. STEPS TO REPRODUCE 1. Open the brush preset chooser popup from the toolbar 2. Long-press a brush preset in the right half of the chooser OBSERVED RESULT The popup is closed EXPECTED RESULT The context menu is displayed. ADDITIONAL INFORMATION I tested it on git 87c46be, Samsung Galaxy Tab S6. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432904] App crashes if Layers is selected from 3 bar menu Top right of screen
https://bugs.kde.org/show_bug.cgi?id=432904 Anna Medonosova changed: What|Removed |Added CC||anna.medonosova@protonmail. ||com --- Comment #2 from Anna Medonosova --- Created attachment 135761 --> https://bugs.kde.org/attachment.cgi?id=135761&action=edit backtrace of the crash I can reproduce the crash on current stable branch and master. I'm attaching a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432488] New: Brush presets from user-imported bundles cannot be reloaded
https://bugs.kde.org/show_bug.cgi?id=432488 Bug ID: 432488 Summary: Brush presets from user-imported bundles cannot be reloaded Product: krita Version: 4.4.2 Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY Brush presets from user-imported bundles cannot be reloaded: clicking the "Reload preset" button does nothing. Presets from the default bundles from Krita installation reload correctly. STEPS TO REPRODUCE 1. Select a preset 2. Make changes to the preset (e.g. change size or opacity) 3. Click the "Reload preset" button (in the toolbar, in brush editor or in the popup palette) OBSERVED RESULT The preset is not reloaded. EXPECTED RESULT The preset is reloaded to original state. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432362] New: Crash when creating a new document
https://bugs.kde.org/show_bug.cgi?id=432362 Bug ID: 432362 Summary: Crash when creating a new document Product: krita Version: git master Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY Krita crashes when creating a new document (custom or from a template). Opening an existing document does not trigger the crash. STEPS TO REPRODUCE 1. Open the new document dialog, either from the menu or from the welcome page 2. Click "Create" OBSERVED RESULT Krita crashes. EXPECTED RESULT A new document is created and opened. ADDITIONAL INFORMATION Backtrace: ** Crash dump: ** Build fingerprint: 'samsung/gts6lwifieea/gts6lwifi:10/QP1A.190711.020/T860XXS3BUA1:user/release-keys' #00 0x00133138 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libQt5Core.so (operator==(QString const&, QString const&)) #01 0x001dd740 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libQt5Core.so (QUrl::fileName(QFlags) const+76) #02 0x00f3f758 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (KisDocument::caption() const+76) (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisDocument::caption() const /home/user/persistent/src/libs/ui/KisDocument.cpp:1760:30 #03 0x00f669e8 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (KisMainWindow::updateCaption()+408) (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisMainWindow::updateCaption() /home/user/persistent/src/libs/ui/KisMainWindow.cpp:961:32 #04 0x00f67ae0 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (KisMainWindow::setActiveView(KisView*)+92) (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisMainWindow::setActiveView(KisView*) /home/user/persistent/src/libs/ui/KisMainWindow.cpp:1549:5 #05 0x00f6a810 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (KisMainWindow::setActiveSubWindow(QWidget*)+208) (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisMainWindow::setActiveSubWindow(QWidget*) /home/user/persistent/src/libs/ui/KisMainWindow.cpp:2473:13 #06 0x00f5f198 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (KisMainWindow::subWindowActivated()+260) (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisMainWindow::subWindowActivated() /home/user/persistent/src/libs/ui/KisMainWindow.cpp:2220:5 #07 0x00f76370 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisMainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) /home/user/persistent/src/libs/ui/KisMainWindow.cpp:0:9 #08 0x002b5194 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libQt5Core.so (QMetaObject::activate(QObject*, int, int, void**)+2584) #09 0x002c69c0 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libQt5Widgets.so Crash dump is completed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431611] Transform tool sticks to stylus when attempting to resize
https://bugs.kde.org/show_bug.cgi?id=431611 Anna Medonosova changed: What|Removed |Added CC||anna.medonosova@protonmail. ||com --- Comment #1 from Anna Medonosova --- I can confirm this behavior on my Galaxy Tab S6. It might be related, that when dragging either the handles or a point outside/inside the transformed area, the action (move, scale, shear, ...) Krita performs is not always what I would expect, based on experience from the desktop version (e.g. it shears instead of scaling when dragging the handle). Also, the cursor does not change to reflect the current action. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430314] New: Triangle shape of the Advanced color selector is not clickable
https://bugs.kde.org/show_bug.cgi?id=430314 Bug ID: 430314 Summary: Triangle shape of the Advanced color selector is not clickable Product: krita Version: 4.4.2-beta1 Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY When the Advanced color selector is set to the triangle type, the triangle does not respond to neither touch nor the S Pen. The color blip is not moved to the selected point on the shape and foreground color is unchanged. The ring and the shade selector both work. When the foreground color is changed (from the working parts of the selector, from the color picker, or from other selectors), the blip updates correctly. Other shape types work correctly. STEPS TO REPRODUCE 1. Set the advanced color selector shape to triangle 2. Click the triangle to change foreground color OBSERVED RESULT The blip does not update, foreground color does not change. EXPECTED RESULT The blip moves to the selected position and foreground color is changed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429691] New: Adding a symbol from the Vector Library is very sensitive to timing
https://bugs.kde.org/show_bug.cgi?id=429691 Bug ID: 429691 Summary: Adding a symbol from the Vector Library is very sensitive to timing Product: krita Version: 4.4.1 Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 133669 --> https://bugs.kde.org/attachment.cgi?id=133669&action=edit screen recording of the issue SUMMARY In the desktop version of Krita, symbols from the Vector Library dockers can be drag&dropped onto the canvas. On Android, I can technically double-tap and drag the symbol (though it takes some trial and error). However, I have to be very quick, otherwise the dragged symbol disappears before I reach the canvas and the symbol is not added. STEPS TO REPRODUCE 1. Create a document 2. Enable the Vector Library docker 3. Drag a symbol from the docker onto the canvas OBSERVED RESULT The symbol disappears while dragging and is not added to the canvas. EXPECTED RESULT The symbol remains under cursor until it is dropped onto the canvas. Or a different way to add the symbol (e.g. a button in the docker) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426832] Nighly AppImages do not contain update information
https://bugs.kde.org/show_bug.cgi?id=426832 Anna Medonosova changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/2d04911bd ||ffd581874004a6faade317a6ed8 ||f51f Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Anna Medonosova --- Git commit 2d04911bdffd581874004a6faade317a6ed8f51f by Anna Medonosova. Committed on 16/11/2020 at 11:34. Pushed by amedonosova into branch 'master'. Fix embedding of update information into AppImage M +1-1packaging/linux/appimage/build-image.sh https://invent.kde.org/graphics/krita/commit/2d04911bdffd581874004a6faade317a6ed8f51f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429056] New: Resaving with different mime type does not work on Android
https://bugs.kde.org/show_bug.cgi?id=429056 Bug ID: 429056 Summary: Resaving with different mime type does not work on Android Product: krita Version: 4.4.0 Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY When trying to save a file, which was opened as JPG, to the native KRA format, JPG file is saved instead of KRA. The native file dialog on Android does not allow me to select a mime type; the suffix of the file name I entered is not considered. STEPS TO REPRODUCE 1. Open a JPG file 2. Make a change 3. File -> Save As, rename the file to ‘testfile.kra’ OBSERVED RESULT On disk, there is a file called testfile.kra.jpg, which is a JPG, not KRA. EXPECTED RESULT I would expect either being able to select a mime type in the file dialog or that the saving process selecting a mime type for the file according to the suffix I input. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427402] New: Paste as reference image crashes Krita
https://bugs.kde.org/show_bug.cgi?id=427402 Bug ID: 427402 Summary: Paste as reference image crashes Krita Product: krita Version: 4.4.0-beta2 Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 132179 --> https://bugs.kde.org/attachment.cgi?id=132179&action=edit backtrace of the crash SUMMARY 'Paste as reference image' button in the tool options of the reference image tool causes Krita to crash. STEPS TO REPRODUCE 1. Open a document 2. Select the reference image tool 3. Click the 'Paste as reference image' button in the tool options OBSERVED RESULT A crash. EXPECTED RESULT I would expect it to either work, or not crash and display an error message. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427043] New: Usage log and system information cannot be saved to a file
https://bugs.kde.org/show_bug.cgi?id=427043 Bug ID: 427043 Summary: Usage log and system information cannot be saved to a file Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY In 5.0.0 39f51c6, usage log and system information for bug reports cannot be saved. STEPS TO REPRODUCE 1. Open Help -> Show system information for bug reports, or Show Krita Log for bug reports 2. Click 'Save to file' 3. Select a directory to save to OBSERVED RESULT The operation fails silently. There is a file in the target directory with size of 0B. EXPECTED RESULT The log file is saved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427042] New: Save Incremental Version/Backup does not work
https://bugs.kde.org/show_bug.cgi?id=427042 Bug ID: 427042 Summary: Save Incremental Version/Backup does not work Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY In 5.0.0 39f51c6, if you try to save with 'Save Incremental Version' or 'Save Incremental Backup', the operation does not save and produces an error. It fails both for local storage and Google Drive. A normal document produces a different error than an autosave file open on startup after a crash. STEPS TO REPRODUCE 1. Open a document 2. Make some changes 3. Save with 'File' -> 'Save Incremental Version' or 'Save Incremental Backup' OBSERVED RESULT The document is not saved. Saving a normal document says: "Cannot open file for writing. An unspecified error occured.". Saving an autosave produces either a popup with "Couldn't save incremental version. Alternative names exhausted, try manually saving with a higher number." (for incremental version), or an error in the status bar: "Error during saving: / cannot be written to. Please save under a different name." (incremental backup). EXPECTED RESULT The document is saved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425011] ext_qt for Android does not build
https://bugs.kde.org/show_bug.cgi?id=425011 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Anna Medonosova --- ext_qt from master builds correctly now, thanks to Sharaf Zaman. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426914] New: Crash when dragging global selection mask onto another layer
https://bugs.kde.org/show_bug.cgi?id=426914 Bug ID: 426914 Summary: Crash when dragging global selection mask onto another layer Product: krita Version: 4.4.0-beta1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 131890 --> https://bugs.kde.org/attachment.cgi?id=131890&action=edit backtrace of the crash SUMMARY When the global selection mask is dragged onto another layer in the Layers docker, Krita crashes. In 4.3, the same action converted the global selection into a local selection for the target layer. STEPS TO REPRODUCE 1. Check "Show global selection mask" in the Select menu. 2. Make a selection. 3. In the Layers docker, drag the global selection mask onto another layer. OBSERVED RESULT Segfault. EXPECTED RESULT The global selection is converted into local selection mask. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426832] Nighly AppImages do not contain update information
https://bugs.kde.org/show_bug.cgi?id=426832 --- Comment #2 from Anna Medonosova --- (In reply to wolthera from comment #1) > is this for the plus or Krita next? Because boud mentioned only master has > that information? Next. Last time I did an update was around 19th August, it worked correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426832] New: Nighly AppImages do not contain update information
https://bugs.kde.org/show_bug.cgi?id=426832 Bug ID: 426832 Summary: Nighly AppImages do not contain update information Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY AppImage updating does not work, because the AppImage does not contain update information. (The check fails silently, and the updater dialog does not appear. The unsuccessful check is logged in krita.log. That is by design.) STEPS TO REPRODUCE 1. Download a nightly appimage 2. in the console, run ./ --appimage-updateinformation OBSERVED RESULT Empty string. EXPECTED RESULT The AppImage contains the right update information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426386] New: Fill pattern of vector shapes is not affected by transform
https://bugs.kde.org/show_bug.cgi?id=426386 Bug ID: 426386 Summary: Fill pattern of vector shapes is not affected by transform Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY In the AppImage for 4.4.0-alpha (git c00326b), the 'Tool Options' docker shows controls for transforming pattern fill. However, vector shapes are not affected by these parameters. STEPS TO REPRODUCE 1. Create a document. Create a vector layer. 2. Select the rectangle tool (or any other shape tool) 3. In the 'Tool Options', set Fill to 'Pattern' and tweak 'Pattern Transform' parameters 4. Create a shape on the canvas OBSERVED RESULT The fill of the shape is not affected by the transform parameters. EXPECTED RESULT Either the transform parameters affect the vector shape, or the 'Pattern Transform' section is hidden for vector layers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425344] Pop up palette not showing brushes on android
https://bugs.kde.org/show_bug.cgi?id=425344 Anna Medonosova changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||anna.medonosova@protonmail. ||com --- Comment #1 from Anna Medonosova --- I can reproduce this on my tablet. I have also tried changing the number of palette presets, it does not help. When the configuration is reset, default presets appear on the palette. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425011] New: ext_qt for Android does not build
https://bugs.kde.org/show_bug.cgi?id=425011 Bug ID: 425011 Summary: ext_qt for Android does not build Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 130634 --> https://bugs.kde.org/attachment.cgi?id=130634&action=edit build error SUMMARY When trying to build ext_qt for Android (both git master and 4.3 branch; locally and in docker with the kdeorg/ci-android image), configure fails with "ERROR: Unknown command line option '-with'.", probably due to https://invent.kde.org/graphics/krita/-/commit/3845a10d659aa48603bfb19b737f714177e0f14e. When "-with qtmultimedia" is replaced with "-skip qtmultimedia", the error is gone. STEPS TO REPRODUCE 1. Build dependencies for Android OBSERVED RESULT ext_qt does not build EXPECTED RESULT ext_qt builds without error -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424514] Guaranteed crash when opening 2 G'MIC-qt
https://bugs.kde.org/show_bug.cgi?id=424514 Anna Medonosova changed: What|Removed |Added CC||anna.medonosova@protonmail. ||com --- Comment #3 from Anna Medonosova --- Created attachment 130349 --> https://bugs.kde.org/attachment.cgi?id=130349&action=edit backtrace of the crash, when first gmic window is closed (3-1); Linux, git master -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424347] Android: Flickering square appears where you are currently drawing
https://bugs.kde.org/show_bug.cgi?id=424347 Anna Medonosova changed: What|Removed |Added Keywords||triaged Status|REPORTED|NEEDSINFO CC||anna.medonosova@protonmail. ||com Resolution|--- |WAITINGFORINFO --- Comment #1 from Anna Medonosova --- This might be a matter of fine tuning the configuration to your hardware. Can you reproduce the flickering with different display settings? To change display settings, go to "Settings" -> "Configure Krita" -> "Display". You can try 1, unchecking the "Use texture buffer" option 2, selecting a different "Scaling Mode" 3, turning off "Canvas Graphics Acceleration" For more details about the settings, you can refer to the manual at https://docs.krita.org/en/reference_manual/preferences/display_settings.html -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423752] Crash can be induced with 4.3.0 onwards after copying a vector layer to another open image
https://bugs.kde.org/show_bug.cgi?id=423752 Anna Medonosova changed: What|Removed |Added Attachment #130072|back|backtrace of the crash description|| -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423752] Crash can be induced with 4.3.0 onwards after copying a vector layer to another open image
https://bugs.kde.org/show_bug.cgi?id=423752 --- Comment #2 from Anna Medonosova --- Created attachment 130072 --> https://bugs.kde.org/attachment.cgi?id=130072&action=edit back -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423752] Crash can be induced with 4.3.0 onwards after copying a vector layer to another open image
https://bugs.kde.org/show_bug.cgi?id=423752 Anna Medonosova changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||anna.medonosova@protonmail. ||com --- Comment #1 from Anna Medonosova --- I can reproduce this issue in krita-5.0.0-prealpha-dd8d748-x86_64.appimage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423752] Crash can be induced with 4.3.0 onwards after copying a vector layer to another open image
https://bugs.kde.org/show_bug.cgi?id=423752 Anna Medonosova changed: What|Removed |Added Keywords||triaged -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423959] The ppi of an image affects the pixel size of vector objects copied into it and creates artifacts with layer copying.
https://bugs.kde.org/show_bug.cgi?id=423959 Anna Medonosova changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||anna.medonosova@protonmail. ||com Ever confirmed|0 |1 --- Comment #1 from Anna Medonosova --- I can confirm both issues in 4.3.0 appimage and in locally compiled git master. Krita Version: 4.3.0 Languages: C Hidpi: true Qt Version (compiled): 5.12.8 Version (loaded): 5.12.8 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.4.0-40-generic Pretty Productname: Ubuntu 20.04 LTS Product Type: ubuntu Product Version: 20.04 Desktop: KDE OpenGL Info Vendor: "Intel" Renderer: "Mesa Intel(R) HD Graphics 620 (KBL GT2)" Version: "4.6 (Compatibility Profile) Mesa 20.0.8" Shading language: "4.60" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 7849 Mb Number of Cores: 4 Swap Location: /tmp/user/1000 Current Settings Current Swap Location: /tmp/user/1000 Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 30 Use OpenGL: true Use OpenGL Texture Buffer: true Use AMD Vectorization Workaround: false Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 2 Screen: 0 Name: HDMI-2 Depth: 24 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: NEC Corporation Model: EA224WMi- Refresh Rate: 60 Screen: 1 Name: eDP-1 Depth: 24 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: Chimei Innolux Corporation Model: Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423959] The ppi of an image affects the pixel size of vector objects copied into it and creates artifacts with layer copying.
https://bugs.kde.org/show_bug.cgi?id=423959 Anna Medonosova changed: What|Removed |Added Keywords||triaged -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422843] Unable to save a document with selection
https://bugs.kde.org/show_bug.cgi?id=422843 --- Comment #5 from Anna Medonosova --- Update: raster selection seems to be unaffected, however, I can't save a vector selection. It might be related to bug https://bugs.kde.org/show_bug.cgi?id=422312 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422843] Unable to save a document with selection
https://bugs.kde.org/show_bug.cgi?id=422843 Anna Medonosova changed: What|Removed |Added Summary|"Save As" does not work |Unable to save a document |from documents opened from |with selection |GDrive | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422843] "Save As" does not work from documents opened from GDrive
https://bugs.kde.org/show_bug.cgi?id=422843 --- Comment #3 from Anna Medonosova --- Created attachment 129394 --> https://bugs.kde.org/attachment.cgi?id=129394&action=edit file producing the error -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422843] "Save As" does not work from documents opened from GDrive
https://bugs.kde.org/show_bug.cgi?id=422843 --- Comment #2 from Anna Medonosova --- I have done other tests and I think I have identified this issue wrongly. The problem seems unrelated to file storage, it rather is an issue with saving a file with selections. Scenario A 1. Create a document 2. Make a selection with any of the selection tools 3. Save the document Scenario B 1. Create a document 2. Add local selection mask to a layer 3. Save the document Scenario C 1. Open the document attached to this bug 2. Save the document All those scenarios produce the error on my device. The path I save to is /storage/emulated/0/Pictures. In scenario C, I can save the file after I delete the local selection mask attached to layer "local selection". I'm sorry for the confusion. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422843] New: "Save As" does not work from documents opened from GDrive
https://bugs.kde.org/show_bug.cgi?id=422843 Bug ID: 422843 Summary: "Save As" does not work from documents opened from GDrive Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@gmail.com Target Milestone: --- SUMMARY When I open a document directly from Google Drive, I am unable to use "Save As" to save it to the local storage. (4.3.1-alpha, git f1990fa) STEPS TO REPRODUCE 1. File -> Open. In the native dialog, pick a file from remote Drive. 2. Make a change to the document. 3. File -> "Save As". Pick a local directory, enter a file name and confirm. OBSERVED RESULT The file is not saved and an error dialog appears. If the target file name does not exist on the local storage, it says "Error occurred while writing to the file." If the target file name exists, it says "Unknown error." EXPECTED RESULT The file is saved to local storage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422422] [Insert as Reference Image] Krita *.kra files not allowed
https://bugs.kde.org/show_bug.cgi?id=422422 Anna Medonosova changed: What|Removed |Added Keywords||triaged -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422406] Krita freezes and crashes to desktop when after dragging a lone magnetic anchor.
https://bugs.kde.org/show_bug.cgi?id=422406 Anna Medonosova changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Keywords||triaged -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422406] Krita freezes and crashes to desktop when after dragging a lone magnetic anchor.
https://bugs.kde.org/show_bug.cgi?id=422406 Anna Medonosova changed: What|Removed |Added CC||anna.medonos...@gmail.com --- Comment #1 from Anna Medonosova --- Created attachment 129035 --> https://bugs.kde.org/attachment.cgi?id=129035&action=edit gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422422] [Insert as Reference Image] Krita *.kra files not allowed
https://bugs.kde.org/show_bug.cgi?id=422422 Anna Medonosova changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422422] [Insert as Reference Image] Krita *.kra files not allowed
https://bugs.kde.org/show_bug.cgi?id=422422 Anna Medonosova changed: What|Removed |Added CC||anna.medonos...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Anna Medonosova --- I can confirm this; also in 4.3.0-beta1 and git master. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422412] New: Recent documents on the welcome page do not open
https://bugs.kde.org/show_bug.cgi?id=422412 Bug ID: 422412 Summary: Recent documents on the welcome page do not open Product: krita Version: unspecified Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@gmail.com Target Milestone: --- SUMMARY In my current build from the krita/4.3 branch (4e18814), when I select one of the recent documents on the welcome page, either with touch tap, or stylus tap, nothing happens, the document does not open. In my previous builds this worked. STEPS TO REPRODUCE 1. Tap a document in the Recent list on the Welcome page OBSERVED RESULT The document does not open. EXPECTED RESULT The document opens. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422391] New: Crash when using "Save Layer/Mask" on a transform mask
https://bugs.kde.org/show_bug.cgi?id=422391 Bug ID: 422391 Summary: Crash when using "Save Layer/Mask" on a transform mask Product: krita Version: 4.3.0-beta2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@gmail.com Target Milestone: --- Created attachment 129006 --> https://bugs.kde.org/attachment.cgi?id=129006&action=edit backtrace of the crash SUMMARY When I try to export a transform mask with "Layer -> Import/Export -> Save Layer/Mask", Krita crashes. Exporting a transparency mask, a colorize mask and a filter mask does not crash. STEPS TO REPRODUCE 1. Download the test file: https://cgit.kde.org/others/krita-marketing.git/tree/manualdemofiles/clonelayer-transformmasks_azaleas.kra 2. Open the test file 3. Select a transform mask in the Layers docker 4. Layer -> Import/Export -> Save Layer/Mask OBSERVED RESULT Krita crashes, no file is saved. EXPECTED RESULT I'm not sure if saving a mask like this is actually expected to work. But it should at least display an error message instead of crashing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422312] Krita for Android opens vector layers as empty.
https://bugs.kde.org/show_bug.cgi?id=422312 --- Comment #5 from Anna Medonosova --- Created attachment 128981 --> https://bugs.kde.org/attachment.cgi?id=128981&action=edit test file from android version -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422312] Krita for Android opens vector layers as empty.
https://bugs.kde.org/show_bug.cgi?id=422312 --- Comment #4 from Anna Medonosova --- Created attachment 128980 --> https://bugs.kde.org/attachment.cgi?id=128980&action=edit test file from desktop version -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422312] Krita for Android opens vector layers as empty.
https://bugs.kde.org/show_bug.cgi?id=422312 Anna Medonosova changed: What|Removed |Added CC||anna.medonos...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Anna Medonosova --- I can confirm this bug on krita/4.3 branch, Android 10. I have also observed following behavior, which may be associated with this bug: A. embedded reference images are not shown on android B. data from vector layers created on android are missing from the kra files Ad B. Steps to reproduce: 1. Create a document with a vector layer on android. 2. Draw something on the vector layer. Newly created shapes are visible. 3. Save and close the document. 4. Upon reopening the document, the vector shapes are gone. The resulting kra file lists the vector layer in the maindoc.xml, but the directory with the content.svg is missing completely. The preview, however, shows the vector shapes. I'm attaching example files. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421933] Reopening unnamed autosave produces an error dialog
https://bugs.kde.org/show_bug.cgi?id=421933 --- Comment #4 from Anna Medonosova --- I observed the issue while running the AppImage with isolated config and home directories for testing (https://invent.kde.org/snippets/741). In that case, XDG_PICTURES_DIR is set to system-wide default, which is $HOME/Pictures. However, the Pictures directory does not exist within the home dir. Another option to trigger the error is to temporarily change XDG_PICTURES_DIR (on my Ubuntu it is in ~/.config/user-dirs.dirs). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421933] New: Reopening unnamed autosave produces an error dialog
https://bugs.kde.org/show_bug.cgi?id=421933 Bug ID: 421933 Summary: Reopening unnamed autosave produces an error dialog Product: krita Version: 4.3.0-beta1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@gmail.com Target Milestone: --- SUMMARY When opening an autosave of a previously unsaved document, Krita tries to save the autosave file to the Pictures directory. If the directory does not exist, the save operation fails. STEPS TO REPRODUCE 1. Create a new document, do NOT save 2. Make some marks 3. Wait for autosave 4. Kill Krita 5. Reopen Krita 6. Click OK to recover the autosave OBSERVED RESULT The autosave file is opened, but it produces a dialog with following error: Could not save [...home directory...]/Pictures/.krita-66481-document_0-autosave.kra Reason: Cannot open file for writing. Reason: The file could not be opened. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421792] New: Save Incremental Version fails with specific file paths
https://bugs.kde.org/show_bug.cgi?id=421792 Bug ID: 421792 Summary: Save Incremental Version fails with specific file paths Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@gmail.com Target Milestone: --- SUMMARY When a directory name resembles incremental version naming scheme, 'Save incremental version' fails. The file path is parsed incorrectly - instead of the file name, Krita increments the number in the directory part of the path. Since such directory does not exist, saving fails. The behavior is the same in git master, 4.3beta1 and 4.2.9. STEPS TO REPRODUCE 1. Create a directory test_1.t 2. Create a document, save to test_1.t 3. Make a change 4. Save incremental version with File -> 'Save Incremental Version' OBSERVED RESULT "Could not save [...]/test_2.t/test_increments.kra Reason: Cannot open file for writing. Reason: The file could not be opened." EXPECTED RESULT The file name is correctly incremented and saved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418855] New: Layer content is invisible after applying transform on a system under load
https://bugs.kde.org/show_bug.cgi?id=418855 Bug ID: 418855 Summary: Layer content is invisible after applying transform on a system under load Product: krita Version: 4.2.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@gmail.com Target Milestone: --- Created attachment 126789 --> https://bugs.kde.org/attachment.cgi?id=126789&action=edit Screen capture of the problem SUMMARY When the system is under load, content of both normal and vector layers turns invisible after applying any transform. Usually when an operation takes a long time, there is a progress bar under the layer name in the Layers docker. However, in this case, there is no progress bar and the transformed area does not reappear. Layer content reappears when the canvas is redrawn (e.g. tool change, window focus change). Curiously enough, I have not seen it happen when transforming selections. It seems similar to bug https://bugs.kde.org/show_bug.cgi?id=408057, but it happens on Linux and also I have reproduced it only when the CPUs are overloaded (image size or layer count do not seem to impact this issue). I have reproduced the same behavior on 4.2.8, 4.2.9beta1 and git master. STEPS TO REPRODUCE 1. Open a document in Krita, create a layer, draw something 2. Stress the system (compile Krita in the background on all your cores, or use some synthetic load generator, like stress-ng) 3. Switch back to Krita, select the Transform Tool, do any transformation available 4. Confirm the transformation with the Enter key OBSERVED RESULT The transformed area turns invisible. EXPECTED RESULT The transformed area reappears after some time. There is a progress bar in the Layers docker showing that there is an operation in progress. ADDITIONAL INFORMATION Krita Version: 4.2.8 Languages: en_US, en_US, en_US, en_US, en_US, en_US Hidpi: false Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.3.0-40-generic Pretty Productname: Ubuntu 19.10 Product Type: ubuntu Product Version: 19.10 OpenGL Info Vendor: "Intel Open Source Technology Center" Renderer: "Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) " Version: "3.0 Mesa 19.2.8" Shading language: "1.30" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 7849 Mb Number of Cores: 4 Swap Location: /tmp Current Settings Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 30 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 600 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 0 Use Zip64: 0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418282] New: Palette docker does not refresh correctly after a color is added from color picker
https://bugs.kde.org/show_bug.cgi?id=418282 Bug ID: 418282 Summary: Palette docker does not refresh correctly after a color is added from color picker Product: krita Version: 4.2.8 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@gmail.com Target Milestone: --- Created attachment 126473 --> https://bugs.kde.org/attachment.cgi?id=126473&action=edit Screen capture of the problem SUMMARY When the Color Selector Tool is used to add picked colors to a palette, the palette docker does not refresh correctly after a color is picked from a canvas. The swatch appears on next use of the tool or upon redraw of the palette docker. STEPS TO REPRODUCE 1. Open a document, draw some colorful blobs on the canvas 2. In the palette docker, create a new palette, 'picker_test' 3. Switch the tool to Color Selector Tool 4. In the Tool Options, check the 'Add to palette' checkbox and set the combo box to 'picker_test' 5. With the Color Selector Tool, pick the blobs from the canvas OBSERVED RESULT The swatches in palette docker do not appear when they the color is picked from canvas. They are either appear after the next use of the Color Selector Tool, or after redraw of the docker (different palette selected, or switch to different window and back). EXPECTED RESULT The swatch appears in the palette docker right after it is picked from the canvas. ADDITIONAL INFORMATION Krita Version: 4.2.8 Languages: en_US Hidpi: true Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.3.0-40-generic Pretty Productname: Ubuntu 19.10 Product Type: ubuntu Product Version: 19.10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412365] New: Reset Rotation visible on welcome page, clicking causes sefgault
https://bugs.kde.org/show_bug.cgi?id=412365 Bug ID: 412365 Summary: Reset Rotation visible on welcome page, clicking causes sefgault Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@gmail.com Target Milestone: --- Created attachment 122878 --> https://bugs.kde.org/attachment.cgi?id=122878&action=edit backtrace SUMMARY When Krita is started and the welcome page appears, there is a "Reset Rotation" button visible in the bottom left corner of the status bar. If the button is clicked, Krita crashes. When a file is opened and then closed, the button disappears. STEPS TO REPRODUCE 1. Start Krita 2. While still on the welcome page, click the 3. segfault -- 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 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||4.2.3 Status|REPORTED|RESOLVED --- Comment #13 from Anna Medonosova --- All issues from this bug are fixed now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409395] If Krita is closed while saving, the document is not saved
https://bugs.kde.org/show_bug.cgi?id=409395 Anna Medonosova changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/d3c5a3f613dd50 ||342af5853d331a1e93a24eb9df Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Anna Medonosova --- Git commit b9671ace4fe47e27ebc76a4b584545d1751e5d96 by Anna Medonosova. Committed on 29/07/2019 at 17:27. Pushed by amedonosova into branch 'master'. Disallow closing Krita while it initiates saving Do not close Krita while KisMainWindow has the savingEntryMutex locked (while the background saving process is being initiated). After the background saving job is initiated, KisDocument blocks closing while it saves itself. M +11 -0libs/ui/KisMainWindow.cpp https://invent.kde.org/kde/krita/commit/b9671ace4fe47e27ebc76a4b584545d1751e5d96 --- Comment #2 from Anna Medonosova --- Git commit d3c5a3f613dd50342af5853d331a1e93a24eb9df by Anna Medonosova. Committed on 29/07/2019 at 17:27. Pushed by amedonosova into branch 'master'. Do not process user input during saving operations Fixes a race condition in the saving process, which is caused by processing user input events in multiple places during save. M +2-2libs/ui/KisDocument.cpp M +1-1libs/ui/dialogs/kis_delayed_save_dialog.cpp M +3-3libs/ui/kis_async_action_feedback.cpp https://invent.kde.org/kde/krita/commit/d3c5a3f613dd50342af5853d331a1e93a24eb9df -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409395] If Krita is closed while saving, the document is not saved
https://bugs.kde.org/show_bug.cgi?id=409395 --- Comment #1 from Anna Medonosova --- Git commit b9671ace4fe47e27ebc76a4b584545d1751e5d96 by Anna Medonosova. Committed on 29/07/2019 at 17:27. Pushed by amedonosova into branch 'master'. Disallow closing Krita while it initiates saving Do not close Krita while KisMainWindow has the savingEntryMutex locked (while the background saving process is being initiated). After the background saving job is initiated, KisDocument blocks closing while it saves itself. M +11 -0libs/ui/KisMainWindow.cpp https://invent.kde.org/kde/krita/commit/b9671ace4fe47e27ebc76a4b584545d1751e5d96 -- 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 #9 from Anna Medonosova --- With latest git master/appimage I cannot reproduce this bug anymore. Please, mvowada, can you confirm that it is indeed working now? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409395] New: If Krita is closed while saving, the document is not saved
https://bugs.kde.org/show_bug.cgi?id=409395 Bug ID: 409395 Summary: If Krita is closed while saving, the document is not saved Product: krita Version: git master Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@gmail.com Target Milestone: --- If the user closes Krita while saving is in progress, there is a chance of Krita closing before the saving process is finished, thus leading to data loss. 1, user makes a modification to the document 2, user initiates save; KisMainWindow::saveDocument() locks itself, so it can not be entered twice 3, before the saving is finished, user generates an event to close Krita; this event gets caught by one of QApplication::processEvents() function (several occurences during save) 4, processEvents() reacts to close by triggering closeEvent(), which calls KisView::queryClose() 5, in queryClose(), the code checks if document is still flagged as modified, which it is; KisMainWindow::saveDocument() is called 6, KisMainWindow::saveDocument() is locked, because saving is already in progress and so returns false 7, Krita closes; the document was not saved -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408256] Missing closest color indication in new color palette docker
https://bugs.kde.org/show_bug.cgi?id=408256 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/c06107d673357c ||b9e8cb56771106770b5bc0f75a --- Comment #4 from Anna Medonosova --- Git commit c06107d673357cb9e8cb56771106770b5bc0f75a by Anna Medonosova. Committed on 14/06/2019 at 10:30. Pushed by amedonosova into branch 'master'. Fix 'Enforce palette colors' feature Since the 'Enforce palette colors' is a feature of the internal color selector, this commit moves the functionality from KisPaletteView to KisDlgInternalColorSelector. Also, that way the color change is forced only once upon foreground color change, preventing cycling signals and confusing color changes (KisPaletteView can be used more than once with different color palettes). Removes KisPaletteView::slotFGColorResourceChanged, the function is obsolete: it was meant to solve bug 402072 that is now fixed in a better way. BACKPORT:krita/4.2 Related: bug 402072 M +7-2libs/widgets/KisDlgInternalColorSelector.cpp M +7-13 libs/widgets/kis_palette_view.cpp M +8-6libs/widgets/kis_palette_view.h M +1-1plugins/dockers/palettedocker/palettedocker_dock.cpp https://invent.kde.org/kde/krita/commit/c06107d673357cb9e8cb56771106770b5bc0f75a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402072] Palette Docker: Can't reselect colour easily
https://bugs.kde.org/show_bug.cgi?id=402072 --- Comment #3 from Anna Medonosova --- Git commit c06107d673357cb9e8cb56771106770b5bc0f75a by Anna Medonosova. Committed on 14/06/2019 at 10:30. Pushed by amedonosova into branch 'master'. Fix 'Enforce palette colors' feature Since the 'Enforce palette colors' is a feature of the internal color selector, this commit moves the functionality from KisPaletteView to KisDlgInternalColorSelector. Also, that way the color change is forced only once upon foreground color change, preventing cycling signals and confusing color changes (KisPaletteView can be used more than once with different color palettes). Removes KisPaletteView::slotFGColorResourceChanged, the function is obsolete: it was meant to solve bug 402072 that is now fixed in a better way. BACKPORT:krita/4.2 Related: bug 408256 M +7-2libs/widgets/KisDlgInternalColorSelector.cpp M +7-13 libs/widgets/kis_palette_view.cpp M +8-6libs/widgets/kis_palette_view.h M +1-1plugins/dockers/palettedocker/palettedocker_dock.cpp https://invent.kde.org/kde/krita/commit/c06107d673357cb9e8cb56771106770b5bc0f75a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408256] Missing closest color indication in new color palette docker
https://bugs.kde.org/show_bug.cgi?id=408256 Anna Medonosova changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |anna.medonos...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408256] Missing closest color indication in new color palette docker
https://bugs.kde.org/show_bug.cgi?id=408256 Anna Medonosova changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||anna.medonos...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Anna Medonosova --- Hi, Larpon, in the new palette docker, the selection of closest color needs to be enabled specifically. To do that: 1, in the main menu select "Settings" -> "Configure Krita" -> "Color Management" 2, tick the checkbox labeled "Enforce palette colors: always select the nearest color from the active palette." With that option turned on, does the palette docker function as expected? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407977] Gamut mask status should be saved to Krita file
https://bugs.kde.org/show_bug.cgi?id=407977 Anna Medonosova changed: What|Removed |Added Ever confirmed|0 |1 CC||anna.medonos...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Anna Medonosova --- Hi, Storm Engineer, thanks for the report. There is a plan for similar feature, details are available in Phabricator: https://phabricator.kde.org/T9652. It is not fully designed yet, it needs ideas and UI mockups. If you are interested and have some time to spare, I will be happy to work with you. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407513] Gamut mask selectable area has an offset to visible mask
https://bugs.kde.org/show_bug.cgi?id=407513 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||anna.medonos...@gmail.com --- Comment #2 from Anna Medonosova --- This is fixed in https://commits.kde.org/krita/57ce1ba509ff3d7a83a7d159ce937cbeeb1bbfe6. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374493] Page orientation does not affect previously selected dimension in New Image dialog
https://bugs.kde.org/show_bug.cgi?id=374493 Anna Medonosova changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/6f3ea24f84e2f70b3dbbfd18 ||37fa223d297f4309 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Anna Medonosova --- Git commit 6f3ea24f84e2f70b3dbbfd1837fa223d297f4309 by Anna Medonosova. Committed on 06/04/2019 at 14:44. Pushed by amedonosova into branch 'master'. Fix page orientation switch in new image dialog Summary: KisDoubleParseSpinBox does not update it's state while being edited (to allow for the math formulas to work correctly). If the cursor is in the number field while the user is changing page orientation, the focused spinbox's value does not change. To work around that, this patch clears focus on the width and height spinboxes before switching page orientation. Reviewers: #krita, rempt Reviewed By: #krita, rempt Tags: #krita Differential Revision: https://phabricator.kde.org/D20300 M +3-0libs/ui/widgets/kis_custom_image_widget.cc https://commits.kde.org/krita/6f3ea24f84e2f70b3dbbfd1837fa223d297f4309 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368360] Krita does not remember shortcut save location.
https://bugs.kde.org/show_bug.cgi?id=368360 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/27678b4ca0c4363ee643a473 ||d6d45244a4b316db Status|CONFIRMED |RESOLVED --- Comment #4 from Anna Medonosova --- Git commit 27678b4ca0c4363ee643a473d6d45244a4b316db by Anna Medonosova. Committed on 23/03/2019 at 05:40. Pushed by amedonosova into branch 'master'. Remember last used dirs for shortcut import/export Summary: File dialogs in KShortcutSchemesEditor use KoFileDialog instead of plain QFileDialog. This allows to remember last used directories for load/save/import/export. Load, save and import location now defaults to homedir, instead of the directory where Krita started. Reviewers: #krita, rempt Reviewed By: #krita, rempt Subscribers: rempt Tags: #krita Differential Revision: https://phabricator.kde.org/D19964 M +5-0libs/koplugin/KisMimeDatabase.cpp M +40 -34 libs/widgetutils/xmlgui/kshortcutschemeseditor.cpp https://commits.kde.org/krita/27678b4ca0c4363ee643a473d6d45244a4b316db -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404852] Crash upon saving due something with the mirror config. [gdb backtrace]
https://bugs.kde.org/show_bug.cgi?id=404852 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kri ||ta/8161893484cc31bb417c980e ||978db3a2046b4d4e --- Comment #4 from Anna Medonosova --- Git commit 8161893484cc31bb417c980e978db3a2046b4d4e by Anna Medonosova. Committed on 18/03/2019 at 15:10. Pushed by amedonosova into branch 'master'. Better pointer handling in KisMirrorManager and KisMirrorAxis Summary: BUG:405093,404852 Reviewers: #krita, dkazakov Reviewed By: #krita, dkazakov Subscribers: dkazakov Tags: #krita Differential Revision: https://phabricator.kde.org/D19776 M +3-0libs/image/kis_types.h M +1-2libs/ui/canvas/kis_mirror_axis.cpp M +3-1libs/ui/canvas/kis_mirror_axis.h M +29 -21 libs/ui/kis_mirror_manager.cpp M +3-6libs/ui/kis_mirror_manager.h https://commits.kde.org/krita/8161893484cc31bb417c980e978db3a2046b4d4e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405093] Crash after closing a document.
https://bugs.kde.org/show_bug.cgi?id=405093 Anna Medonosova changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/8161893484cc31bb417c980e ||978db3a2046b4d4e Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Anna Medonosova --- Git commit 8161893484cc31bb417c980e978db3a2046b4d4e by Anna Medonosova. Committed on 18/03/2019 at 15:10. Pushed by amedonosova into branch 'master'. Better pointer handling in KisMirrorManager and KisMirrorAxis Summary: BUG:405093,404852 Reviewers: #krita, dkazakov Reviewed By: #krita, dkazakov Subscribers: dkazakov Tags: #krita Differential Revision: https://phabricator.kde.org/D19776 M +3-0libs/image/kis_types.h M +1-2libs/ui/canvas/kis_mirror_axis.cpp M +3-1libs/ui/canvas/kis_mirror_axis.h M +29 -21 libs/ui/kis_mirror_manager.cpp M +3-6libs/ui/kis_mirror_manager.h https://commits.kde.org/krita/8161893484cc31bb417c980e978db3a2046b4d4e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405093] Crash after closing a document.
https://bugs.kde.org/show_bug.cgi?id=405093 --- Comment #5 from Anna Medonosova --- Git commit f16b1f8b61ad08899a9518577aa6af1e0080eea4 by Anna Medonosova. Committed on 06/03/2019 at 14:57. Pushed by amedonosova into branch 'master'. Fix decoration handling in KisMirrorManager KisMirrorManager did not update d->mirrorAxisDecoration upon view change, instead it used last created decoration. If the document tied to that decoration was closed, Krita crashed. M +3-0libs/ui/canvas/KisMirrorAxisConfig.cpp M +13 -12 libs/ui/kis_mirror_manager.cpp M +0-1libs/ui/kis_mirror_manager.h https://commits.kde.org/krita/f16b1f8b61ad08899a9518577aa6af1e0080eea4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405093] Crash after closing a document.
https://bugs.kde.org/show_bug.cgi?id=405093 --- Comment #3 from Anna Medonosova --- It seems that both crashes are symptoms of one problem: the KisMirrorManager handles it's decorations incorrectly. I can reproduce the crash with following steps: 1, open two documents with mirror configuration 2, close one of the documents 3, click on the mirror tool buttons in paintop box -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405093] Crash after closing a document.
https://bugs.kde.org/show_bug.cgi?id=405093 Anna Medonosova changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||anna.medonos...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405037] New vector shapes are not filled with correctly after pattern change
https://bugs.kde.org/show_bug.cgi?id=405037 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/7b4550bd4600dec9a108737b ||d027693cbe942145 Status|REPORTED|RESOLVED --- Comment #1 from Anna Medonosova --- Git commit 7b4550bd4600dec9a108737bd027693cbe942145 by Anna Medonosova. Committed on 03/03/2019 at 15:14. Pushed by amedonosova into branch 'master'. Fix creating vector shapes with pattern fill M +1-1libs/ui/tool/kis_tool.cc https://commits.kde.org/krita/7b4550bd4600dec9a108737bd027693cbe942145 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405037] New: New vector shapes are not filled with correctly after pattern change
https://bugs.kde.org/show_bug.cgi?id=405037 Bug ID: 405037 Summary: New vector shapes are not filled with correctly after pattern change Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@gmail.com Target Milestone: --- If a vector shape is created with fill set to pattern 1. Select Rectangle Tool (or Ellipse, ...). In the tool options set fill to pattern. 2. Change the pattern in patterns docker. 3. Draw the shape. The shape is filled with a gradient instead of current pattern from resource manager. There is a null pointer KisTool's d->currentPattern. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404852] Crash upon saving due something with the mirror config. [gdb backtrace]
https://bugs.kde.org/show_bug.cgi?id=404852 --- Comment #3 from Anna Medonosova --- Git commit ce50e5ceeb4ab6a3bd5a1a04082d7c82d4d0ca0f by Anna Medonosova. Committed on 27/02/2019 at 14:25. Pushed by amedonosova into branch 'master'. Check for view and document before setting mirror tool config M +1-0libs/ui/canvas/KisMirrorAxisConfig.cpp M +9-6libs/ui/kis_mirror_manager.cpp M +1-1libs/ui/kis_mirror_manager.h https://commits.kde.org/krita/ce50e5ceeb4ab6a3bd5a1a04082d7c82d4d0ca0f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404852] Crash upon saving due something with the mirror config. [gdb backtrace]
https://bugs.kde.org/show_bug.cgi?id=404852 Anna Medonosova changed: What|Removed |Added CC||anna.medonos...@gmail.com --- Comment #1 from Anna Medonosova --- I am sorry, I cannot reproduce it. Are there specific steps to trigger the crash? Can you provide the file that causes it? Do you have a core file? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385521] Selecting "Gradient" in brush editor crashes krita
https://bugs.kde.org/show_bug.cgi?id=385521 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/1117e62d79645ea9931e0f30 |ta/d12bbbe117442f1e0b30ba4d |37e93527a97ca3a2|f8a5703802c5f771 --- Comment #5 from Anna Medonosova --- Git commit d12bbbe117442f1e0b30ba4df8a5703802c5f771 by Anna Medonosova. Committed on 25/02/2019 at 11:31. Pushed by amedonosova into branch 'master'. Use plain color source instead of gradient in KisPresetLivePreviewView Summary: KisPresetLivePreviewView cannot display gradient color source: there is no resource manager for KisResourcesSnapshot, therefore gradient is nullptr. That crashes Krita, when it tries to render the preview. This patch solves the issue by falling back to plain color source for preset preview rendering. Reviewers: #krita, rempt Reviewed By: #krita, rempt Tags: #krita Differential Revision: https://phabricator.kde.org/D19297 M +11 -0libs/ui/widgets/kis_preset_live_preview_view.cpp https://commits.kde.org/krita/d12bbbe117442f1e0b30ba4df8a5703802c5f771 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385521] Selecting "Gradient" in brush editor crashes krita
https://bugs.kde.org/show_bug.cgi?id=385521 --- Comment #4 from Anna Medonosova --- Created attachment 118336 --> https://bugs.kde.org/attachment.cgi?id=118336&action=edit backtrace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385521] Selecting "Gradient" in brush editor crashes krita
https://bugs.kde.org/show_bug.cgi?id=385521 Anna Medonosova changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||anna.medonos...@gmail.com --- Comment #3 from Anna Medonosova --- I have encountered the same behavior in the current git master, just a few lines of code above the old bug. I attach backtrace from the crash. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 339515] mirror-mode center line doesn't save to file.
https://bugs.kde.org/show_bug.cgi?id=339515 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kri ||ta/54d3dc15daa1b2adc8708aa7 ||0ae3726c9301dcf1 --- Comment #2 from Anna Medonosova --- Git commit 54d3dc15daa1b2adc8708aa70ae3726c9301dcf1 by Anna Medonosova. Committed on 22/02/2019 at 05:09. Pushed by amedonosova into branch 'master'. Saving Mirror Tool state to KRA Summary: Saving Mirror Tool state to KRA file, wished for in bug 339515. Test Plan: - Set up mirror lines. Save, close and reopen. Expected result: the mirror lines and options should be automatically set and activated. - Open multiple files, with and without mirror lines. Expected result: Every open document should have separate configuration. Toolbar actions should affect only the currently active view. Reviewers: #krita, rempt Reviewed By: #krita, rempt Subscribers: rempt Tags: #krita Differential Revision: https://phabricator.kde.org/D18254 M +2-1libs/ui/CMakeLists.txt M +21 -0libs/ui/KisDocument.cpp M +6-0libs/ui/KisDocument.h A +246 -0libs/ui/canvas/KisMirrorAxisConfig.cpp [License: LGPL] A +103 -0libs/ui/canvas/KisMirrorAxisConfig.h [License: LGPL] M +137 -74 libs/ui/canvas/kis_mirror_axis.cpp M +6-0libs/ui/canvas/kis_mirror_axis.h M +40 -1libs/ui/kis_mirror_manager.cpp M +8-3libs/ui/kis_mirror_manager.h M +8-0libs/ui/kis_paintop_box.cc M +14 -0plugins/impex/libkra/kis_kra_loader.cpp M +1-0plugins/impex/libkra/kis_kra_loader.h M +15 -0plugins/impex/libkra/kis_kra_saver.cpp M +1-0plugins/impex/libkra/kis_kra_saver.h M +1-0plugins/impex/libkra/kis_kra_tags.h https://commits.kde.org/krita/54d3dc15daa1b2adc8708aa70ae3726c9301dcf1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 337328] Advanced color selector do not allow to show Shade selector only
https://bugs.kde.org/show_bug.cgi?id=337328 Anna Medonosova changed: What|Removed |Added Latest Commit|http://commits.kde.org/call |https://commits.kde.org/kri |igra/cb207e27e7cda184f0901e |ta/52afd0cbfc8e23d1b4c9f519 |4ea5bcb79cb8bcf666 |356dbe847fc2a890 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #20 from Anna Medonosova --- Git commit 52afd0cbfc8e23d1b4c9f519356dbe847fc2a890 by Anna Medonosova. Committed on 01/01/2019 at 12:58. Pushed by amedonosova into branch 'master'. Advanced Color Selector: option to hide color selector Summary: I have resurrected the original patch by Ranveer Aggarwal, which enables the user to hide the color selector part of the docker. There was one issue with the original: the docker settings button is inside the color selector, therefore when you hide the selector, the only way to configure the docker is via the main menu, "Settings" -> "Configure Krita". To solve that I have added a fallback settings button to the docker widget, which appears when the color selector part is hidden. Reviewers: #krita, rempt Reviewed By: #krita, rempt Subscribers: rempt Tags: #krita Differential Revision: https://phabricator.kde.org/D17893 M +15 -8 plugins/dockers/advancedcolorselector/kis_color_selector_container.cpp M +1-0 plugins/dockers/advancedcolorselector/kis_color_selector_container.h M +68 -4 plugins/dockers/advancedcolorselector/kis_color_selector_ng_docker_widget.cpp M +8-0 plugins/dockers/advancedcolorselector/kis_color_selector_ng_docker_widget.h M +3-3 plugins/dockers/advancedcolorselector/kis_color_selector_settings.cpp M +256 -244 plugins/dockers/advancedcolorselector/wdg_color_selector_settings.ui https://commits.kde.org/krita/52afd0cbfc8e23d1b4c9f519356dbe847fc2a890 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402342] --template does not open provided template
https://bugs.kde.org/show_bug.cgi?id=402342 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kri ||ta/3e3f0d0a265df8697630be9d ||1e89bdea4b9bd28a --- Comment #2 from Anna Medonosova --- Git commit 3e3f0d0a265df8697630be9d1e89bdea4b9bd28a by Anna Medonosova. Committed on 22/12/2018 at 20:40. Pushed by amedonosova into branch 'master'. M +3-0libs/ui/KisApplication.cpp https://commits.kde.org/krita/3e3f0d0a265df8697630be9d1e89bdea4b9bd28a -- You are receiving this mail because: You are watching all bug changes.
