[krita] [Bug 487248] Colorspace error
https://bugs.kde.org/show_bug.cgi?id=487248 Tiar changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #1 from Tiar --- That comes either from the Cross-channel Adjustment Curves filter or the Color Adjustment Curves filter. 1. Do you have a filter mask or a filter layer on the image? 2. What is the color space and profile of your current image (should be written on the bottom of Krita) and what is the color space and profile of the layer the filter mask is attached to (right-click -> Properties should show you that information)? 3. Do you do anything special in this file? 4. Does it happen when you create a completely new file? 5. Can you share the file it happens with? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486311] segfault on drag and drop
https://bugs.kde.org/show_bug.cgi?id=486311 Tiar changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Can you please try appimage 5.2.2 from the website to see if it works there or segfaults as well? We've got a few reports about crashes on 5.2.2: bug 485446 , bug 484715 , but they all seem to happen only on the snap version. Snap is not officially supported, we're not the team making them, unlike appimages that are made by Krita team. So maybe something wrong happened with packaging, and for that we need to know whether this crash happens on appimage too. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484936] Selecting an ICCmax profile crashes Krita
https://bugs.kde.org/show_bug.cgi?id=484936 Tiar changed: What|Removed |Added Ever confirmed|0 |1 Severity|normal |crash Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #3 from Tiar --- It has a crash log, so it shouldn't be closed by the Bug Janitor. But still, having the ICC profile would be useful. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484115] krita-5.2.2-185d3bbd - crash when selecting some brushes
https://bugs.kde.org/show_bug.cgi?id=484115 Tiar changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/-/commit/13fe82a ||dbb67fa3234ff9bbfb1ba2a7820 ||b099fe Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Tiar --- Git commit 13fe82adbb67fa3234ff9bbfb1ba2a7820b099fe by Agata Cacko. Committed on 15/04/2024 at 11:47. Pushed by tymond into branch 'master'. Fix assert on selecting RGBA brushes in incorrect format Before this commit, if you had a brush tip saved in PNG file, that has at least one colorful pixel (not all values of R, G and B were equal), and had no semi-transparent pixels, it would assert on importing it or selecting. After this commit, all brushes with colorful pixels or no alpha go through the RGBA route and are converted into ARGB32 format. Note: that means we don't support higher bit depth for RGBA brushes. But we already didn't before this commit. M +3-1libs/brush/kis_png_brush.cpp https://invent.kde.org/graphics/krita/-/commit/13fe82adbb67fa3234ff9bbfb1ba2a7820b099fe -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 485446] Krita snap crash on opening or creating a new file
https://bugs.kde.org/show_bug.cgi?id=485446 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Tiar --- Hi, we don't build Krita's snap package, please make a report to the maintainers of the snap package. Seems like they don't include the PyQt package, maybe. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 485447] Snap install does not have an application icon
https://bugs.kde.org/show_bug.cgi?id=485447 Tiar changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Hi, we don't build Krita's snap package, please make a report to the maintainers of the snap package. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 485305] too big on phone
https://bugs.kde.org/show_bug.cgi?id=485305 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Tiar --- I'm sorry, but we don't support Krita on phones (only on Android tablets, which have bigger screens) for this very reason. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484751] Default line width is set to 100px, which is too large
https://bugs.kde.org/show_bug.cgi?id=484751 Tiar changed: What|Removed |Added Status|REPORTED|RESOLVED CC||tamtamy.tym...@gmail.com Resolution|--- |NOT A BUG --- Comment #1 from Tiar --- The default line width for the tool that you can use on vector layers (like Rectangle Tool) is the current size of the brush. You can choose a different brush or change the size in the widget on top of the canvas to make the line width smaller. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484715] crash upon opening past files
https://bugs.kde.org/show_bug.cgi?id=484715 Tiar changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||tamtamy.tym...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #5 from Tiar --- Maybe try getting a crashlog. Help -> Show Krita log for bug reports might contain it (when you get some kind of Krita that works: appimage, or maybe a flatpak, or figure out how to fix that snap version). And this: > Cannot mix incompatible Qt library (5.15.11) with this library (5.15.12) Sounds like a snap/system configuration problem, not something in Krita at all. You should ask for help someone who knows how snaps operate (I don't) and what's the deal with the mismatched libraries and how to fix that. Most likely, you can just remove the system Qt libraries you installed to install that old Krita version - but why would a snap version require you to remove system libraries to work, I don't know. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484986] Scrollbar Readability suggestion
https://bugs.kde.org/show_bug.cgi?id=484986 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #3 from Tiar --- > how many people will actually update the program if the visuals remain the > same? I think many people do get excited about the new useful features when they see it. Though of course visuals are important too. Anyway, the problem with scrollbars and color-schemes/themes is that there are not two separate colors for the bar and the background of the scrollbar, but just one color that is modified to be lighter and darker for the bar and the background respectively. That color is "BackgroundNormal" in section "[Colors:Normal]". You can set it to "255,0,0" to see the whole bar changing to red. >From what I checked, you can get better contrast (using the standard Krita Dark theme) if you set it to "90,90,90", and basically the lighter it is, the better the contrast. "100,100,100" is mostly usable too, but keep in mind that the higher you go, the less contrast you have with text. It looks a bit uglier but it works better, I guess. The theme that works best is Krita Bright, I believe. The documentation I could find is here: https://docs.kde.org/stable5/en/plasma-workspace/kcontrol/colors/index.html There is a chance that the settings on top: "[ColorEffects:Disabled]" and "[ColorEffects:Inactive]" might have some effect on the scrollbar but I doubt it. There is an option to create a new style (but that would mean forking Fusion, I think? Probably bundling Breeze would be way less invasive and there is a good reason why we don't do that), or apply a stylesheet (but in that case we wouldn't be able to use themes). We could possibly patch Fusion for our own builds, or maybe replace all scrollbars with a custom one with a custom painting process. Not sure if the effort is worth it. I've seen people complaining about this before so it does seem to be at least partially an issue, but whether or what we should do about this is another matter. Maybe we should downgrade it to a wishlist, too. The slider is not unusable, and one can use Krita Bright theme for better contrast. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484936] Selecting an ICCmax profile crashes Krita
https://bugs.kde.org/show_bug.cgi?id=484936 Tiar changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #1 from Tiar --- Could you please attach that ICCMax profile to the bug report? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484114] Brush Lag when using Thunderbolt Cable to connect Huion Tablet
https://bugs.kde.org/show_bug.cgi?id=484114 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Tiar --- That sounds like a tablet driver problem. Try switching in Krita -> Settings -> Configure Krita -> Tablet Settings to Wintab (and restart your PC or at least Krita for a good measure), you can try reinstalling the driver, and if all fails, you can ask on krita-artists.org forum, which is a bit better place for diagnosing and fixing tablet issues. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481184] New: Krita crashes on animation cache on a file without animation
https://bugs.kde.org/show_bug.cgi?id=481184 Bug ID: 481184 Summary: Krita crashes on animation cache on a file without animation Classification: Applications Product: krita Version: git master (please specify the git hash!) Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: tamtamy.tym...@gmail.com Target Milestone: --- Created attachment 165733 --> https://bugs.kde.org/attachment.cgi?id=165733=edit Crash log SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Be on f3bb64bec1 (I was over it with some changes) 2. I was testing MR !636, so my file had at least a paint layer and some references, possibly also a vector layer. Never had any animation, I doubt the Animation Timeline docker was enabled. OBSERVED RESULT Crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS (Krita in a docker) Krita Version: 5.3.0-prealpha (git 7406513) Hidpi: true Qt Version (compiled): 5.15.7 Version (loaded): 5.15.7 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.15.0-76-generic Pretty Productname: Ubuntu 20.04.6 LTS Product Type: ubuntu Product Version: 20.04 Desktop: Appimage build: No Locale Languages: en_US, en, en_Latn_US C locale: en_US.UTF-8 QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Intel" Renderer: "Mesa Intel(R) Iris(R) Plus Graphics (ICL GT2)" Driver version: "4.6 (Core Profile) Mesa 21.2.6" Shading language: "4.60" Requested format: QSurfaceFormat(version 3.3, options QFlags(), 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(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CoreProfile) GL version: 4.6 Supports deprecated functions false Is OpenGL ES: false supportsBufferMapping: true supportsBufferInvalidation: true forceDisableTextureBuffers: false Extensions: GL_ARB_compute_shader GL_ARB_sync GL_ARB_indirect_parameters GL_EXT_texture_compression_rgtc GL_ARB_clip_control GL_AMD_draw_buffers_blend GL_KHR_blend_equation_advanced GL_AMD_depth_clamp_separate GL_INTEL_blackhole_render GL_ARB_framebuffer_sRGB GL_ARB_draw_instanced GL_ARB_texture_query_lod GL_ARB_pipeline_statistics_query GL_EXT_shader_samples_identical GL_MESA_texture_signed_rgba GL_ARB_shader_image_load_store GL_ARB_uniform_buffer_object GL_ARB_clear_buffer_object GL_EXT_shader_integer_mix GL_ARB_timer_query GL_KHR_robustness GL_ARB_depth_clamp GL_ARB_vertex_attrib_64bit GL_EXT_demote_to_helper_invocation GL_ARB_texture_buffer_object GL_ARB_shader_texture_lod GL_EXT_texture_shared_exponent GL_ARB_robust_buffer_access_behavior GL_ARB_shader_image_size GL_3DFX_texture_compression_FXT1 GL_EXT_draw_buffers2 GL_ARB_vertex_type_10f_11f_11f_rev GL_EXT_blend_equation_separate GL_ARB_texture_multisample GL_ARB_gpu_shader_int64 GL_EXT_semaphore_fd GL_AMD_vertex_shader_viewport_index GL_ARB_texture_non_power_of_two GL_ARB_texture_cube_map_array GL_ARB_invalidate_subdata GL_ARB_texture_compression_bptc GL_EXT_transform_feedback GL_ARB_vertex_array_bgra GL_ARB_sampler_objects GL_ARB_texture_stencil8 GL_ARB_transform_feedback3 GL_ARB_map_buffer_alignment GL_ARB_vertex_buffer_object GL_KHR_robust_buffer_access_behavior GL_ARB_gpu_shader5 GL_ARB_buffer_storage GL_ARB_texture_query_levels GL_ARB_internalformat_query2 GL_ARB_shader_precision GL_ARB_texture_view GL_ARB_copy_image GL_ARB_framebuffer_object GL_EXT_polygon_offset_clamp GL_ARB_clear_texture GL_ARB_shader_bit_encoding GL_ARB_vertex_shader GL_EXT_timer_query GL_ARB_derivative_control GL_AMD_conservative_depth GL_ARB_post_depth_coverage GL_EXT_memory_object_fd GL_ARB_vertex_attrib_binding
[krita] [Bug 480915] https://www.reddit.com/r/krita/comments/19epys0/why_isnt_krita_reading_the_pressure_on_my_tablet/
https://bugs.kde.org/show_bug.cgi?id=480915 Tiar changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Have you tried any of the solutions given to you by commenters? Pen pressure is very rarely a bug in Krita, the vast majority is just some kind of misconfiguration. Usually installing a new tablet driver, or swtiching between Windows Ink and Wintab in Krita's Settings -> Configure Krita -> Tablet Settings, is enough to get it work. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480832] Color and layer display abnormalities when opening PSD format file
https://bugs.kde.org/show_bug.cgi?id=480832 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Tiar --- Closing as not a bug. You can subscribe to bug 400643 if you want to be notified when it's implemented. You can also check out https://invent.kde.org/graphics/krita/-/merge_requests/1813 which is the newest attempt at implementing it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480601] Crash when continuous selecting by color label reference includes a transform mask
https://bugs.kde.org/show_bug.cgi?id=480601 Tiar changed: What|Removed |Added Severity|minor |crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480601] Crash when continuous selecting by color label reference includes a transform mask
https://bugs.kde.org/show_bug.cgi?id=480601 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 336731] Saving color information in brush presets
https://bugs.kde.org/show_bug.cgi?id=336731 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #8 from Tiar --- Isn't that resolved thanks to RGBA brush presets? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 318027] Apply inherit alpha layer to itself
https://bugs.kde.org/show_bug.cgi?id=318027 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #4 from Tiar --- It would be an equivalent of making a temporary transparency mask out of all the layers below the one we want to apply the alpha inheritance, then merging with that mask. We need to do it one layer at a time internally due to situations like this: - Group layer -- Layer A, alpha inheritance turned on -- Layer B, -- Layer C, alpha inheritance turned on -- Layer D. (layer A's alpha inheritance masked area is different from layer C's, because layer A's alpha = Layer D + (C) + B's alpha). There are two questions: - do we expose an option to do it one layer at a time (just "apply A.I. to this layer") or to all layers inside the group (then an option for a group layer "apply A.I. to all layers inside/all child layers")? - What do you do with group layers, file layers, clone layers etc.? Maybe we need to add an option "Convert alpha inheritance here to transparency mask" instead for those kinds of layers (then of course the paint layer could have both...)? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375155] Add option to texture each dab instead of stroke
https://bugs.kde.org/show_bug.cgi?id=375155 --- Comment #4 from Tiar --- This is way more complex than it seems so on the surface, considering the work Deif Lou did, plus this picture of comparison: https://krita-artists.org/t/testing-needed-new-brush-texture-modes/23031/11 that seems to conclude that what Krita does is texturing per tip, while it could per stroke. (Btw, maybe the texture options are enough now?) So this wish requires both discussions with artists and some (preferably deep) understanding of the available texturing options in both Krita and other programs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380141] Make it possible to merge masks
https://bugs.kde.org/show_bug.cgi?id=380141 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #2 from Tiar --- It would be good to have an option to merge it not only using AND mode (which I guess should be the default for transparency masks, as this is what happens when you have two transparency masks enabled). Selection masks are a bit more tricky since there is no way to have more than one enabled at once, but we could default to AND as well. But it would be good to have an option to merge them with OR mode in some way. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 173590] Provide visual feedback on loading files
https://bugs.kde.org/show_bug.cgi?id=173590 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #7 from Tiar --- There is a progress bar on the bottom now, and if you open it as the first file, the Welcome Page is greyed out. Maybe it's enough now? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462151] Add an option to center the position of the Transform
https://bugs.kde.org/show_bug.cgi?id=462151 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Just to be sure, are you aware of and using the Snap to Center option? What makes it not suitable for your usecase? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480168] Вылетает
https://bugs.kde.org/show_bug.cgi?id=480168 Tiar changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #1 from Tiar --- Hi, sorry, we can't do anything about your issue (Krita crashing) until you give us more information. Please attach the files/information from Help -> Show Krita log for bug reports, and Help -> Show system information for bug reports. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435185] Add shortcuts and sliders for Fade and Scatter in Auto brush mode
https://bugs.kde.org/show_bug.cgi?id=435185 Tiar changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #8 from Tiar --- Setting to Fixed, then. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443620] Custom Pattern doesn't show Current Layer content until switched from and back
https://bugs.kde.org/show_bug.cgi?id=443620 --- Comment #3 from Tiar --- I think the Update button should just be above the thumbnail (kind of "chronologically") instead of below, and it would already fix most of the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389015] expand selection of N frames
https://bugs.kde.org/show_bug.cgi?id=389015 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #6 from Tiar --- I believe the feature you're looking for is selecting all of those frames, then right-click, then Hold Frames -> Insert Multiple Hold Frames, then choose either 1 (for 2x slower animation) or 2 (for 3x slower animation). It will have the same effect without duplicating data. Can you please check that function and confirm that it works the way you need it? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447761] [FeatureRequest] Highlight selected area while using the Contiguous Selection Tool
https://bugs.kde.org/show_bug.cgi?id=447761 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Can you please elaborate on what you mean by "highlighting"? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376883] Paste on active layer & active keyframe.
https://bugs.kde.org/show_bug.cgi?id=376883 Tiar changed: What|Removed |Added Resolution|--- |FIXED CC||tamtamy.tym...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #5 from Tiar --- Seems to be implemented already. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465272] Add an action to "scalable distance"
https://bugs.kde.org/show_bug.cgi?id=465272 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Component|Usability |Scripting -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369503] Render animation encode resume after error,by looking at folder
https://bugs.kde.org/show_bug.cgi?id=369503 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Related bug 411109 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439759] Fill Rectangle with pattern in Vector Layer loads damaged pattern after reopen
https://bugs.kde.org/show_bug.cgi?id=439759 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #4 from Tiar --- Created attachment 165124 --> https://bugs.kde.org/attachment.cgi?id=165124=edit Example file with pattern fill on a vector shape We no longer can create files with pattern fill (see bug 403140), however we can still load them afaik, and I think they still suffer from this issue. In the attachment, in the original file there was no white cross, and when opening this file in f3bb64bec1 (5.2+, master), a white cross appears in the pattern. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395808] Text shape should support gradient and pattern backgrounds.
https://bugs.kde.org/show_bug.cgi?id=395808 Tiar changed: What|Removed |Added Resolution|--- |FIXED CC||tamtamy.tym...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #12 from Tiar --- Now both normal and mesh gradients are supported in text as well, while pattern is removed from vector shapes altogether. I think we should close this (I set it to Fixed since the gradients are fixed now). (The pattern fill kinda worked in previous versions but it was never fully implemented, according to https://bugs.kde.org/show_bug.cgi?id=403140#c2) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447514] New gradient smoothing is not applied to mesh gradients / Mesh gradients looking really blocky
https://bugs.kde.org/show_bug.cgi?id=447514 Tiar changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Severity|wishlist|normal --- Comment #3 from Tiar --- Because of the above, I'm changing it back to a bug and setting to confirmed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447514] New gradient smoothing is not applied to mesh gradients / Mesh gradients looking really blocky
https://bugs.kde.org/show_bug.cgi?id=447514 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #2 from Tiar --- Created attachment 165118 --> https://bugs.kde.org/attachment.cgi?id=165118=edit Screenshot showing the difference between stop gradient and mesh gradient on a vector shape (600 dpi, the text is 9pt) I don't think this is a wish report, because the vector shapes with mesh gradients don't always - like in this case - need more values or blue noise to be smooth. I think there is an issue with rendering that for some reason doesn't see the true resolution of the file. The text above was 9pt, and the middle-and-upper parts show around 6 values - possibly the mesh gradient is painted in points (so 9 values calculated for 9 points of text) instead of pixels (which on 600 dpi image, as it was, is around, what, 56 pixels? And black-to-white gradient has 255 values, so we should see 56 values in the gradient without any additional smart smoothing). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477561] Pixel brush with size 2 or more does not create the pixels correctly
https://bugs.kde.org/show_bug.cgi?id=477561 Tiar changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||tamtamy.tym...@gmail.com Ever confirmed|0 |1 --- Comment #3 from Tiar --- Hi, if you check "Align the brush preview outline to the pixel grid", it should start to work fine. However, that is, I think, a regression: in 5.1.5 the brush works as expected despite the checkbox not being checked, therefore making the "aligning to the pixel grid" a cosmetic checkbox instead of a functional one (and it was still important as a cosmetic checkbox since many people felt that constricting the brush outline to pixels felt worse, since it was "jumping" from one position to the next. There were many discussions about this). Now the question is whether the change of behaviour was expected or not. I mean it changes the way an already saved brush works, so I would assume it's a regression and not an expected change. Related commits: 4c639ee9bd5c958cce08598ecc3beea0182e7e33 (probable introduction of the wrong logic? Except it was already included in 5.1...) And: 5fdf853a1a1fe21b04c6bf02584762040bd66628 (that is why it works differently in 5.2.0-beta1). Faulty line: https://invent.kde.org/graphics/krita/-/blob/master/plugins/paintops/libpaintop/KisSharpnessOption.cpp#L34 - includes m_alignOutlinePixels, and that function is called in both outline painting and dab painting. Fix: just separate two functions so that the outline is painted according to the checkbox, and the dab is always aligned, as it was before. I will investigate further to understand how that happened, which should give a hint whether it was in any way intentional or just a mistake. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435185] Add shortcuts and sliders for Fade and Scatter in Auto brush mode
https://bugs.kde.org/show_bug.cgi?id=435185 --- Comment #6 from Tiar --- Tyson, can we close this report now or is there something more you want to get done here? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423788] Liquify Tool - Utterly Slow Performance
https://bugs.kde.org/show_bug.cgi?id=423788 --- Comment #9 from Tiar --- So what is the conclusion - when using "Fast" preview in Krita 5., is it much slower than Krita 4., or around the same speed (no mater if very slow on higher spacing)? Asking to be sure whether there has been any regression, or is it just a normal (albeit slow) performance and this report is a wish for Liquify to go faster. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363315] Averaged/Mixed Custom Color Selector
https://bugs.kde.org/show_bug.cgi?id=363315 Tiar changed: What|Removed |Added Summary|Averaged Color Sampler |Averaged/Mixed Custom Color ||Selector -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466583] Artifacts when shapes are not at integer positions
https://bugs.kde.org/show_bug.cgi?id=466583 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- I wonder if the solution wouldn't be a checkbox to restrict the moved vector shapes positions to multiples of 0.5? (Must be multiples of 0.5 instead of integers, because for example having a 3px thick rectangle, you'd want to put it in the center of a pixel). (Note that now bug 466582 is fixed, so it is possible to correct it afterwards in gui). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466582] Vector Shape positions are floats, yet the interface pretends they are integers
https://bugs.kde.org/show_bug.cgi?id=466582 Tiar changed: What|Removed |Added CC||griffin-barr...@outlook.com --- Comment #8 from Tiar --- *** Bug 416833 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416833] Select shapes tool geometry input fields not properly handling decimal values
https://bugs.kde.org/show_bug.cgi?id=416833 --- Comment #4 from Tiar --- *** This bug has been marked as a duplicate of bug 466582 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390950] Support fractions for size and position of vector objects
https://bugs.kde.org/show_bug.cgi?id=390950 Tiar changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||tamtamy.tym...@gmail.com --- Comment #4 from Tiar --- *** This bug has been marked as a duplicate of bug 466582 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466582] Vector Shape positions are floats, yet the interface pretends they are integers
https://bugs.kde.org/show_bug.cgi?id=466582 Tiar changed: What|Removed |Added CC||vladimir.firefly.savic@gmai ||l.com --- Comment #7 from Tiar --- *** Bug 390950 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410533] SHIFT key doesn't change size
https://bugs.kde.org/show_bug.cgi?id=410533 Tiar changed: What|Removed |Added CC||rebuilders...@gmail.com --- Comment #5 from Tiar --- *** Bug 477351 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477351] Wish: Allow drag-resizing of brush when using rectangle, ellipse etc tools
https://bugs.kde.org/show_bug.cgi?id=477351 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Tiar --- *** This bug has been marked as a duplicate of bug 410533 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435876] Shift modifier to crop a perfect square
https://bugs.kde.org/show_bug.cgi?id=435876 Tiar changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Tiar --- There is a way to conserve the ratio by locking it in the Tool Options, but yes, using Shift either for squares or for conserving the ratio (possibly ctrl+Shift for a square?) would be nice. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 479658] Moving with arrow keys breaks if you move viewport
https://bugs.kde.org/show_bug.cgi?id=479658 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #2 from Tiar --- I couldn't reproduce on Linux Mint either. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 479405] voliantsoin at location
https://bugs.kde.org/show_bug.cgi?id=479405 Tiar changed: What|Removed |Added Severity|critical|crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 479405] voliantsoin at location
https://bugs.kde.org/show_bug.cgi?id=479405 Tiar changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Confirming since it contains a crashlog. Can you tell us something about what were you doing when Krita crashed? You were adding some resource (for example a brush, or a bundle) to Krita, what was it? Or did it happen on startup? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 479603] Add a button to move colors generated with color patches into the current palette.
https://bugs.kde.org/show_bug.cgi?id=479603 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Tiar --- Seems like quite a good idea. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478798] Lost progress on a file that was supposed to autosave every 15min, there is no backup or recovery file
https://bugs.kde.org/show_bug.cgi?id=478798 Tiar changed: What|Removed |Added Summary|I lost about 3+ hours worth |Lost progress on a file |of progress on a piece that |that was supposed to |had autosaved every 15 |autosave every 15min, there |minutes. There is no |is no backup or recovery |backup and/or recovery file |file |of the document. Attached | |is all that was saved, but | |it is missing the majority | |of my artwork that I| |completed. | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478798] I lost about 3+ hours worth of progress on a piece that had autosaved every 15 minutes. There is no backup and/or recovery file of the document. Attached is all that was saved,
https://bugs.kde.org/show_bug.cgi?id=478798 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #3 from Tiar --- Please include Help -> Show Krita log for bug reports, and Help -> Show system information for bug reports. Also your file wasn't attached, but we probably don't really need it. Also please tell us your saving habits, how often do you save, which folder (is it some cloud service like Google Drive or Dropbox?), which option do you choose (normal type of saving, from the menu? keyboard shortcut?). And what was the name of the file. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 479593] Smart Patch
https://bugs.kde.org/show_bug.cgi?id=479593 Tiar changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #1 from Tiar --- Hi, please include the text from Help -> Show Krita log for bug reports. You can do that by going to the bugs website and click the "Add an attachment" option. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469645] Krita keeps crashing on a specific piece of artwork
https://bugs.kde.org/show_bug.cgi?id=469645 Tiar changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com --- Comment #4 from Tiar --- There are three ways how you can do it: 1) Easiest, but with size limit: you can visit https://bugs.kde.org/show_bug.cgi?id=469645 (this is the website for the bug report), there will be a list of Attachments. Underneath there is text "Add an attachment". Press it, then you'll see another page. There will be "Browse" button, click it, find the file that causes Krita to crash, add some text in Description field, and press "Submit". 2) You can share it on Google Drive (remember to add the viewing access for people having the link) or Dropbox or similar service. 3) If it's really private (or you can't show it to public because it's a commission for a client etc.), you can send an email from gmail to mentioned email address: vur...@gmail.com with the file as an attachment. It's best to use (1) or (2) so all developers have access to it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470029] Save didnt create folder yet said it work
https://bugs.kde.org/show_bug.cgi?id=470029 Tiar changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #2 from Tiar --- The log seems to think it successfully saved the file. 1) What if you go in Krita -> File -> Open Recent -> and check if the file is there? If so, does it open successfully? 2) What if you open the file manager, and show hidden folders and files? Instruction: https://support.microsoft.com/en-us/windows/view-hidden-files-and-folders-in-windows-97fbc472-c603-9d90-91d0-1166d1d9f4b5#WindowsVersion=Windows_10 Does it appear then? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412943] Use System Monitor Profile checkbox attributes wrong profile to screens, breaking color management
https://bugs.kde.org/show_bug.cgi?id=412943 --- Comment #20 from Tiar --- Git commit 054517cd8f42e0f4215f7eae2628428bc23b3370 by Agata Cacko. Committed on 15/05/2023 at 14:09. Pushed by tymond into branch 'master'. Fix color profiles being assigned to screens by indexes Before this commit, Krita assigned color profiles to screens based on screen indexes, which apparently can change (see the bug report). This commit introduces "screen string identifier" which is a concatenation of multiple screen properties like manufacturer, serial number, resolution etc. (Note that especially on Windows, any of those properties might be empty strings). Related: bug 407498, bug 412608 M +36 -1libs/ui/kis_config.cc M +2-0libs/ui/kis_config.h https://invent.kde.org/graphics/krita/commit/054517cd8f42e0f4215f7eae2628428bc23b3370 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412608] [Color Management] Attributing a monitor profile to multi monitor is difficult.
https://bugs.kde.org/show_bug.cgi?id=412608 --- Comment #4 from Tiar --- Git commit 054517cd8f42e0f4215f7eae2628428bc23b3370 by Agata Cacko. Committed on 15/05/2023 at 14:09. Pushed by tymond into branch 'master'. Fix color profiles being assigned to screens by indexes Before this commit, Krita assigned color profiles to screens based on screen indexes, which apparently can change (see the bug report). This commit introduces "screen string identifier" which is a concatenation of multiple screen properties like manufacturer, serial number, resolution etc. (Note that especially on Windows, any of those properties might be empty strings). Related: bug 407498, bug 412943 M +36 -1libs/ui/kis_config.cc M +2-0libs/ui/kis_config.h https://invent.kde.org/graphics/krita/commit/054517cd8f42e0f4215f7eae2628428bc23b3370 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407498] Color profiles should take into account monitor model and serial number
https://bugs.kde.org/show_bug.cgi?id=407498 Tiar changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/054517cd8 ||f42e0f4215f7eae2628428bc23b ||3370 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #12 from Tiar --- Git commit 054517cd8f42e0f4215f7eae2628428bc23b3370 by Agata Cacko. Committed on 15/05/2023 at 14:09. Pushed by tymond into branch 'master'. Fix color profiles being assigned to screens by indexes Before this commit, Krita assigned color profiles to screens based on screen indexes, which apparently can change (see the bug report). This commit introduces "screen string identifier" which is a concatenation of multiple screen properties like manufacturer, serial number, resolution etc. (Note that especially on Windows, any of those properties might be empty strings). Related: bug 412608, bug 412943 M +36 -1libs/ui/kis_config.cc M +2-0libs/ui/kis_config.h https://invent.kde.org/graphics/krita/commit/054517cd8f42e0f4215f7eae2628428bc23b3370 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457586] when moving the area with transforming tool using arrow keys, the preview doesn't update on the canvas when the option is 'Fast'.
https://bugs.kde.org/show_bug.cgi?id=457586 Tiar changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/aa6c5da0c ||0dd93845e892fff21d2753c6fca ||4e85 Resolution|--- |FIXED --- Comment #5 from Tiar --- Git commit aa6c5da0c0dd93845e892fff21d2753c6fca4e85 by Agata Cacko. Committed on 15/05/2023 at 01:50. Pushed by tymond into branch 'master'. Fix Transform Tool to update on arrow keys on Fast Before this commit, transform tool wouldn't update the canvas when the user used arrow keys to move the content using the Fast preview type. M +2-0plugins/tools/tool_transform2/kis_tool_transform.cc https://invent.kde.org/graphics/krita/commit/aa6c5da0c0dd93845e892fff21d2753c6fca4e85 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469060] bitdefender asked to allow tcp ip what not then just closed.
https://bugs.kde.org/show_bug.cgi?id=469060 Tiar changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- It sounds like it was a Bitdefender related, not Krita related? As in, maybe Bitdefender closed Krita for some reason?... You can attach Help -> Show Krita log for bug reports, but I doubt it will help. Regarding the autosaving, you can change the autosave time in Settings -> Configure Krita -> General -> File Handling -> Autosave Interval. I personally recommend having it at 3 min, but you can choose whatever you want. That will be the max time of lost progress on your painting. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468226] I have an issue where I'll draw and ill get a message saying "waiting for image operation to complete" and then the whole layer gets cleared of it contents..
https://bugs.kde.org/show_bug.cgi?id=468226 Tiar changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #3 from Tiar --- I'm glad you figured it out, then. And thanks for answering. I'm closing the bug in that case. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468226] I have an issue where I'll draw and ill get a message saying "waiting for image operation to complete" and then the whole layer gets cleared of it contents..
https://bugs.kde.org/show_bug.cgi?id=468226 Tiar changed: What|Removed |Added Keywords||triaged -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468226] I have an issue where I'll draw and ill get a message saying "waiting for image operation to complete" and then the whole layer gets cleared of it contents..
https://bugs.kde.org/show_bug.cgi?id=468226 Tiar changed: What|Removed |Added Severity|normal |major CC||tamtamy.tym...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Tiar --- Ouch, that gif looks scary. I set it to "major" since it's a dataloss. Can you please share the content of Help -> Show Krita log for bug reports? Hopefully there is some more information about it. (I personally couldn't reproduce it). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463408] Transparency Masks and Transform Masks are not saved into Compositions
https://bugs.kde.org/show_bug.cgi?id=463408 Tiar changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/6cc18f5a4 ||96751dbb22414cb9f04a946e966 ||7f27 Status|ASSIGNED|RESOLVED --- Comment #4 from Tiar --- Git commit 6cc18f5a496751dbb22414cb9f04a946e9667f27 by Agata Cacko. Committed on 20/04/2023 at 19:54. Pushed by tymond into branch 'master'. Fix compositions to take into account masks visibility Before this commit, masks visibility wasn't taken into account in Compositions. This commit ensures it is. M +4-1libs/image/kis_layer_composition.cpp https://invent.kde.org/graphics/krita/commit/6cc18f5a496751dbb22414cb9f04a946e9667f27 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444070] Advanced color selector history swatches height/width backwards when in horizontal mode.
https://bugs.kde.org/show_bug.cgi?id=444070 Tiar changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/1e6b3e9b7 ||68d27d276be4447b67070f9effe ||5802 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Tiar --- Git commit 1e6b3e9b768d27d276be4447b67070f9effe5802 by Agata Cacko. Committed on 20/04/2023 at 19:54. Pushed by tymond into branch 'master'. Fix height and width mixed up in color history Before this commit, adjusting Height would adjust the width of the color swatch, and adjusting the Width would adjust the height of it. Since it only changes the text on screen (other than that, the code is consistent), it won't change the look of color selector for anyone who already adjusted it to their liking. M +2-2 plugins/dockers/advancedcolorselector/wdg_color_selector_settings.ui https://invent.kde.org/graphics/krita/commit/1e6b3e9b768d27d276be4447b67070f9effe5802 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458593] When scaling brush tipsdown , the average value of the tip is not kept
https://bugs.kde.org/show_bug.cgi?id=458593 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #7 from Tiar --- Created attachment 158219 --> https://bugs.kde.org/attachment.cgi?id=158219=edit Screenshot of the rectangle Auto brush tip test with 3.0 auto spacing and 7% flow The brush tip's average value is actually correct. The brush tip's values variance is not - it gets progressively lower (meaning that all pixels are getting closer and closer to the average, meaning some medium grey/half-transparent). However, the fix for the variance doesn't fix this issue (I checked). The specific issue with this brush is just caused by Auto spacing + very low Flow. If you follow those steps: 1. take the demo brush 2. change the brush tip from "Predefined" to "Auto", then change to black square 3. Paint with it on 5px and 15px. Result: the same bug, despite no brush tip image being scaled. 4. Change the Spacing from 0.02 to 3. You'll see that in case of 15px, the brush tips overlap, but in case of 5px, there are spaces between them. The objective value of the spacing does get smaller, but not small enough. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466438] Some of Krita Layer and Brush Effect are not working properly Like Lumminosity, Multiply, Linear Bun, and some other
https://bugs.kde.org/show_bug.cgi?id=466438 Tiar changed: What|Removed |Added Status|REPORTED|RESOLVED CC||tamtamy.tym...@gmail.com Resolution|--- |INTENTIONAL --- Comment #2 from Tiar --- You are using the LAB color space. For "typical" experience with blending modes, it's recommended to use RGB color space. Many of the blending modes are not possible in non-RGB color spaces, and some might be defined but work differently (for example, Multiply in CMYK color space results in lighter colors due to the characteristics of CMYK color space - instead of 0 being the darkest color, it's the lightest). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 455106] Value (HSV) blend mode changes saturation unexpectedly
https://bugs.kde.org/show_bug.cgi?id=455106 Tiar changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com Status|CONFIRMED |ASSIGNED CC||tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444070] Advanced color selector history swatches height/width backwards when in horizontal mode.
https://bugs.kde.org/show_bug.cgi?id=444070 Tiar changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com Status|CONFIRMED |ASSIGNED CC||tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464257] Layer effects not saved if they're the only thing changed.
https://bugs.kde.org/show_bug.cgi?id=464257 --- Comment #7 from Tiar --- Master bug of the uuid issue (all issues where the layer style of the duplicated layer is the same as the layer style of the original layer) is bug 457553. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457553] Duplicating layers with layer styles, and changing style on new layer results in wrong serialization and both layer have same layer styles after load.
https://bugs.kde.org/show_bug.cgi?id=457553 Tiar changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||9c847ba5c8ec912bf3c4d318ed5 ||c654a89400418 Resolution|--- |FIXED --- Comment #5 from Tiar --- Fixed in 9c847ba5c8ec912bf3c4d318ed5c654a89400418. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457553] Duplicating layers with layer styles, and changing style on new layer results in wrong serialization and both layer have same layer styles after load.
https://bugs.kde.org/show_bug.cgi?id=457553 Tiar changed: What|Removed |Added CC||knowz...@pokemail.net --- Comment #4 from Tiar --- *** Bug 451385 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 451385] Copy and pasting a layer with an existing layerstyle fails to save changes
https://bugs.kde.org/show_bug.cgi?id=451385 Tiar changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||tamtamy.tym...@gmail.com Resolution|--- |DUPLICATE --- Comment #3 from Tiar --- *** This bug has been marked as a duplicate of bug 457553 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467729] Opening Layer Styles editor resets gradient overlay colors if 0. Foreground to Background is selected and document hasn't been saved/closed/reopened.
https://bugs.kde.org/show_bug.cgi?id=467729 --- Comment #1 from Tiar --- Relevant: bug 445135 and commit 46e8344d6fa2deebb9d5e6da59f9b6d9bc7f6f2c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467729] Opening Layer Styles editor resets gradient overlay colors if 0. Foreground to Background is selected and document hasn't been saved/closed/reopened.
https://bugs.kde.org/show_bug.cgi?id=467729 Tiar changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467729] Opening Layer Styles editor resets gradient overlay colors if 0. Foreground to Background is selected and document hasn't been saved/closed/reopened.
https://bugs.kde.org/show_bug.cgi?id=467729 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Keywords||triaged -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466545] Krita not saving layer styles and forgetting layer style parameters
https://bugs.kde.org/show_bug.cgi?id=466545 Tiar changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #6 from Tiar --- I believe it is fixed already. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464218] Bevel and Emboss Highlight Mode color not saved with file
https://bugs.kde.org/show_bug.cgi?id=464218 Tiar changed: What|Removed |Added CC||justinjserr...@hotmail.com --- Comment #3 from Tiar --- *** Bug 457485 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457485] the bevel and embos is not keeping it color
https://bugs.kde.org/show_bug.cgi?id=457485 Tiar changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||tamtamy.tym...@gmail.com --- Comment #3 from Tiar --- It's fixed in the Krita Next already and will be fixed in the next version. *** This bug has been marked as a duplicate of bug 464218 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463408] Transparency Masks and Transform Masks are not saved into Compositions
https://bugs.kde.org/show_bug.cgi?id=463408 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Status|CONFIRMED |ASSIGNED Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464257] Layer effects not saved if they're the only thing changed.
https://bugs.kde.org/show_bug.cgi?id=464257 Tiar changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Tiar --- Setting it to fixed, then :) Thanks for testing! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464257] Layer effects not saved if they're the only thing changed.
https://bugs.kde.org/show_bug.cgi?id=464257 Tiar changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com --- Comment #4 from Tiar --- Related commits: a84179a80bc8e74505455d0589d07b4cf4283b47 - Don't forget 'align with layer' in gradient layer style e8631c562c511d6b33ea05b93e3f7ddca852 - Fix color in Bevel and Emboss being forgotten 27aed51669b54356b132d7b6fa18bba90bd94d35 - Fix Bevel and Emboss - Texture Depth not being read from asl 9c847ba5c8ec912bf3c4d318ed5c654a89400418 - Fix layerstyle creation so they are kept after reload -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466545] Krita not saving layer styles and forgetting layer style parameters
https://bugs.kde.org/show_bug.cgi?id=466545 --- Comment #3 from Tiar --- Related commits: a84179a80bc8e74505455d0589d07b4cf4283b47 - Don't forget 'align with layer' in gradient layer style e8631c562c511d6b33ea05b93e3f7ddca852 - Fix color in Bevel and Emboss being forgotten 27aed51669b54356b132d7b6fa18bba90bd94d35 - Fix Bevel and Emboss - Texture Depth not being read from asl 9c847ba5c8ec912bf3c4d318ed5c654a89400418 - Fix layerstyle creation so they are kept after reload -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466545] Krita not saving layer styles and forgetting layer style parameters
https://bugs.kde.org/show_bug.cgi?id=466545 --- Comment #2 from Tiar --- Note: if it's not resolved for some parameters, please do make a list of which parameters exactly are forgotten, it's pretty difficult otherwise, because of how many of them are there. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466545] Krita not saving layer styles and forgetting layer style parameters
https://bugs.kde.org/show_bug.cgi?id=466545 Tiar changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Could you please check Krita Next and see if this issue is resolved? There has been several commits that solved various issues and there is a high chance it's solved now (I solved some of the Stroke parameters being forgotten, and the Opacity strokes were already working because of some older but still recent commits). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464257] Layer effects not saved if they're the only thing changed.
https://bugs.kde.org/show_bug.cgi?id=464257 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #3 from Tiar --- @Ralek could you please check Krita Next and see if this issue is resolved? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463110] Layer lock does not prevent moving selected parts of layer
https://bugs.kde.org/show_bug.cgi?id=463110 Tiar changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/36573abc8 ||c6ddd22b339d8f8c3da26da5bf5 ||db1a Resolution|--- |FIXED --- Comment #2 from Tiar --- Git commit 36573abc8c6ddd22b339d8f8c3da26da5bf5db1a by Agata Cacko. Committed on 17/03/2023 at 17:00. Pushed by tymond into branch 'master'. Prevent moving selected parts of a locked layer Before this commit, Move Tool could still move selected part on a layer even if it was locked. This commit prevents it from happening. M +10 -1plugins/tools/basictools/kis_tool_move.cc https://invent.kde.org/graphics/krita/commit/36573abc8c6ddd22b339d8f8c3da26da5bf5db1a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459801] Pop-up Palette does not display correct canvas rotation angle.
https://bugs.kde.org/show_bug.cgi?id=459801 Tiar changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/238193411 ||94ba534df3cef09542327d50dec ||d76c Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Tiar --- Git commit 23819341194ba534df3cef09542327d50decd76c by Agata Cacko. Committed on 17/03/2023 at 17:00. Pushed by tymond into branch 'master'. Fix updating rotation indicator in the popup palette Before this commit, the popup palette rotation indicator wouldn't update in some cases. This commit ensures it is up to date every time the popup palette is drawn. Test cases: 1. Rotate with shortcut or touch gesture, show popup palette, close it, rotate some more, show popup palette 2. Show popup palette, rotate with shortcut or touch gesture M +3-0libs/ui/kis_popup_palette.cpp https://invent.kde.org/graphics/krita/commit/23819341194ba534df3cef09542327d50decd76c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456194] Align with Layer checkbox in Gradient Overlay deactivates itself when Layer Style is accessed again
https://bugs.kde.org/show_bug.cgi?id=456194 Tiar changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/a84179a80 ||bc8e74505455d0589d07b4cf428 ||3b47 --- Comment #5 from Tiar --- Git commit a84179a80bc8e74505455d0589d07b4cf4283b47 by Agata Cacko. Committed on 17/03/2023 at 00:39. Pushed by tymond into branch 'master'. Don't forget 'align with layer' in gradient layer style Before this commit, checking "Align with layer" in the gradient overlay layer style would result only in temporary alignment with the layer, and the checkbox would be unchecked next time the user opens the dialog. The same was happening with the gradient in the Stroke layer style. This commit ensures the value of the checkbox will be remembered. There is still potentially a problem with Stroke layer style having only one boolean value for the "Align with layer" values in both Gradient and Pattern, but it shouldn't be much trouble for the user because this commit ensures that the value in the active stroke type will be remembered correctly. M +14 -5libs/ui/dialogs/kis_dlg_layer_style.cpp https://invent.kde.org/graphics/krita/commit/a84179a80bc8e74505455d0589d07b4cf4283b47 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463110] Layer lock does not prevent moving selected parts of layer
https://bugs.kde.org/show_bug.cgi?id=463110 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461309] Fuzzy Dab ignores curves calculation mode, appears to just use multiply.
https://bugs.kde.org/show_bug.cgi?id=461309 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #2 from Tiar --- I would be careful about fixing this bug, because judging from the code in here: "KisCurveOption::ValueComponents KisCurveOption::computeValueComponents(const KisPaintInformation& info) const" (kis_curve_option.cpp, line 389) https://invent.kde.org/graphics/krita/-/blob/master/plugins/paintops/libpaintop/kis_curve_option.cpp#L389 it seems like it was a design choice. There are a few types of sensors and apparently Fuzzy Dab, Fuzzy Stroke, Rotation, Tilt and Drawing Angle are calculated separately from the rest. Whole logic was designed and explained here: https://invent.kde.org/graphics/krita/-/commit/159a61263e6d4f7812ba56e38fa29a1a02dcae11 It seems like it might be necessary for values like Hue etc. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459801] Pop-up Palette does not display correct canvas rotation angle.
https://bugs.kde.org/show_bug.cgi?id=459801 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Status|CONFIRMED |ASSIGNED Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466985] memory leak
https://bugs.kde.org/show_bug.cgi?id=466985 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Tiar --- Could you please attach screenshots of Configure Krita -> Performance -> General, and what shows up when, when you have the issue (it must be happening during taking the screenshot), you click on the small bar on the bottom showing the memory? (It would probably be yellow or red, but can be grey too, and when clicked it should show information like Image size and Memory used). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464218] Bevel and Emboss Highlight Mode color not saved with file
https://bugs.kde.org/show_bug.cgi?id=464218 Tiar changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/e8631c562 ||c511d6b33ea05b93e3f7ddc ||a852 Status|ASSIGNED|RESOLVED --- Comment #2 from Tiar --- Git commit e8631c562c511d6b33ea05b93e3f7ddca852 by Agata Cacko. Committed on 09/03/2023 at 23:07. Pushed by tymond into branch 'master'. Fix color in Bevel and Emboss being forgotten Before this commit, both Highlight Color and Shadow Color in Layer Styles -> Bevel and Emboss would be forgotten after closing the document. This commit ensures that it's properly written to the file and then read from it. M +3-0libs/psdutils/asl/kis_asl_xml_parser.cpp https://invent.kde.org/graphics/krita/commit/e8631c562c511d6b33ea05b93e3f7ddca852 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464218] Bevel and Emboss Highlight Mode color not saved with file
https://bugs.kde.org/show_bug.cgi?id=464218 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Status|CONFIRMED |ASSIGNED Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466794] Unable to edit Basic-1 in Brush Editor
https://bugs.kde.org/show_bug.cgi?id=466794 Tiar changed: What|Removed |Added Resolution|--- |NOT A BUG CC||tamtamy.tym...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Tiar --- It is actually working correctly. Krita's brushes are categorized in so called "engines", every engine has different code and different set of options. Basic-1 brush uses "Quick engine" (you can see the lighting bolt underneath the brush preset name), which has very limited set of options to make super extra fast (you can make it very big and it will still be nearly instant). If you want to have more options, just edit a brush like Basic-2 Opacity, just disable the Opacity being affected by Pressure to have the same effect as on Basic-1. You can also unhide the left panel of the brush editor and press the [+] button underneath all brushes, and choose "Pixel", that will create a new brush preset for you that you can edit and save. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 460058] Cannot Link to Image (grayed out) reference file when inserting it via drag-and-drop
https://bugs.kde.org/show_bug.cgi?id=460058 Tiar changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/485e586f6 ||bdde3afff121d72f93def5327d5 ||1def --- Comment #3 from Tiar --- Git commit 485e586f6bdde3afff121d72f93def5327d51def by Agata Cacko. Committed on 28/02/2023 at 21:49. Pushed by tymond into branch 'master'. Fix disabled Link to Image in Ref Tool after drag-and-drop Before this commit, there was no way to link the new reference image to the original file, because Krita were forgetting the url. This commit fixes that. Notes: - you can only choose Link to Image after adding the new reference image. If you still use the Embed in .kra option and save and reopen, then the location will be forgotten and there won't be a way to Link it to Image again. (possible improvement: don't forget the location). - in theory, the image displayed in Krita might be different before and after saving and reopening, because before it will be loading the file from clipboard, and the code there is pretty complicated (it doesn't always go the same way as loading from url). To prevent issues, just keep it as "Embed as .kra". - removed "d->embed = false" in setFilename() and added ref->setEmbed(false) in the loading visitor instead, because then the responsibilities of parts of the code are more clear. M +0-1libs/ui/KisReferenceImage.cpp M +9-0libs/ui/KisView.cpp M +1-0plugins/impex/libkra/kis_kra_load_visitor.cpp https://invent.kde.org/graphics/krita/commit/485e586f6bdde3afff121d72f93def5327d51def -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 460058] Cannot Link to Image (grayed out) reference file when inserting it via drag-and-drop
https://bugs.kde.org/show_bug.cgi?id=460058 Tiar changed: What|Removed |Added Status|CONFIRMED |ASSIGNED CC||tamtamy.tym...@gmail.com Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465954] Krita fails manual saves silently with no space left in home directory
https://bugs.kde.org/show_bug.cgi?id=465954 Tiar changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com Status|REPORTED|CONFIRMED CC||tamtamy.tym...@gmail.com Ever confirmed|0 |1 Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
