[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint
https://bugs.kde.org/show_bug.cgi?id=353960 --- Comment #36 from Stig Grindland --- (In reply to Andrew from comment #29) > After seeing "any patch welcome"... I spent the morning working on this: > https://invent.kde.org/frameworks/kwallet/-/merge_requests/83 Thank you so much for putting your time into improving this, Andrew -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint
https://bugs.kde.org/show_bug.cgi?id=353960 Stig Grindland changed: What|Removed |Added CC||stig.grindl...@gmail.com --- Comment #24 from Stig Grindland --- Hello, I'm also here regarding this user experience, as I have experienced it myself ever since I switched to linux some months ago and trying different distros. KDE feels unhelpful by telling me to "Please set-up at least an encryption key, then try again.", as if I'm already an expert on this stuff. Which is making me do the job of searching up how to do this the right way. Which again leads me to all kind of info from years back which I'm not sure about. If the error message could include a link to KDE documentation, or some suggestion on how to proceed with setting up GPG, I think it would be a great step forward here. For context, I went through these steps and I hope new users doesn't have to: Ask an AI for help -> reddit -> link to this issue -> understand why I should set up GPG and not escape to blowfish. I am now glad to see that I'm not alone here, and thanks to all you previous commenters for the information collected here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450630] Can't save or create a new Canvas Input Profile when using non-default Resource Folder
https://bugs.kde.org/show_bug.cgi?id=450630 --- Comment #2 from Stig (Rakurri) --- (In reply to amyspark from comment #1) > Looks like another case of bugs 447813 / 447235 ? Ah, it might be, it seems parallell except the crash! I saw that this MR might be relevant https://invent.kde.org/graphics/krita/-/merge_requests/1281 In that case when that is merged I could test it and see if it fixes this problem, and write my results -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450630] New: Can't save or create a new Canvas Input Profile when using non-default Resource Folder
https://bugs.kde.org/show_bug.cgi?id=450630 Bug ID: 450630 Summary: Can't save or create a new Canvas Input Profile when using non-default Resource Folder Product: krita Version: 5.0.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: sti-n...@online.no Target Milestone: --- SUMMARY I have my Resources located here: C:\Users\myusername\OneDrive\2D Art\Krita\Krita Resource Folder It works fantastically, except that I have had to set up my canvas input settings from scratch every time I open Krita, and to my dismay, Krita do not save any of my changes or new profiles. I set the Severity to major as I think spending much time on tweaking and changing the navigation and not have it saved can cause much headache to users using a non-default Resource Folder. Putting Canvas Input Profiles in the input folder does not work either, they won't show up in Krita. STEPS TO REPRODUCE 1. Have your Resources Folder as something else than default. Mine is in my OneDrive 2. Change the Canvas Input Settings or try to create new profiles 3. Closing and restarting Krita will result in no changes or new profiles being present OBSERVED RESULT Canvas Input Settings did not save anything EXPECTED RESULT Canvas Input Settings remembering my changes SOFTWARE/OS VERSIONS Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447045] New: Brushes with kind of low Density has bad visibility on canvas
https://bugs.kde.org/show_bug.cgi?id=447045 Bug ID: 447045 Summary: Brushes with kind of low Density has bad visibility on canvas Product: krita Version: 5.0.0-beta5 Platform: Other OS: Microsoft Windows Status: REPORTED Keywords: regression Severity: minor Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: sti-n...@online.no Target Milestone: --- Created attachment 144586 --> https://bugs.kde.org/attachment.cgi?id=144586=edit Note the black-ish circle SUMMARY Brushes with kind of low Density has bad visibility on canvas and appear as a kind of dark and muddy overlay, this did not happen in Krita 4 STEPS TO REPRODUCE 1. Make an "Auto" brush that has a Density value of around 30% 2. Make it large and hover it over the canvas with preview outline enabled. OBSERVED RESULT It covers most of the surface area and makes it hard to see your results, especially when using Smudge brushes. EXPECTED RESULT Thin outline like other brushes SOFTWARE/OS VERSIONS Krita 5.0.0-beta5 Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446292] Can't change Ten Brushes brushes
https://bugs.kde.org/show_bug.cgi?id=446292 --- Comment #6 from Stig (Rakurri) --- (In reply to Dmitry Kazakov from comment #3) Hi! Yep that worked! Thank you very much. I will soon try bringing the presets and most important settings back as I have wanted to have a christmas cleaning of my Krita folder for Krita 5. I think this is solved, but if I experience the problem again I will send a message! Should I change this bug report to resolved? -- 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 #8 from Stig (Rakurri) --- (In reply to Stig (Rakurri) from comment #7) > (Sorry for the late reply, have been very occupied with exams.) It seems to > work about the same on fast in both versions. I noticed though that my > spacing was very high. And when the spacing is high I notice that the > liquify seems to push the pixels in the wrong way the first dab(s) a lot of > the time. This to me made it look much less performant. Is that effect > visible in the videos I sent? It makes the liquify much less usable on high > spacing, although it is not noticeable on low spacing This happens for both 4.4.8 and 5 beta3 -- 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 #7 from Stig (Rakurri) --- (Sorry for the late reply, have been very occupied with exams.) It seems to work about the same on fast in both versions. I noticed though that my spacing was very high. And when the spacing is high I notice that the liquify seems to push the pixels in the wrong way the first dab(s) a lot of the time. This to me made it look much less performant. Is that effect visible in the videos I sent? It makes the liquify much less usable on high spacing, although it is not noticeable on low spacing -- 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 Stig (Rakurri) changed: What|Removed |Added CC||sti-n...@online.no --- Comment #5 from Stig (Rakurri) --- Can confirm on Krita 5 beta3, it is extremely slow on my Windows 10 PC, it takes a very long time to see results of the liquify, the tool most often push the pixels at random it feels like and do not move the pixels around correctly, Krita might even freeze a bit while using the tool. It worked fine in Krita 4.x. This happen on every file. I have a pretty modern 2019 desktop machine, so I think this is affecting a lot of people, I think the bug reports importance should be set much higher than "wishlist" Here is a video of the problem https://imgur.com/a/iXmBffo System Info System Info Krita Version: 5.0.0-beta2 (git a642eb0) Languages: en_US, en, en_US, en, en_US, en, en_US, en, nn_NO, nn, en_US, en Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19044 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (NVIDIA GeForce RTX 2070 SUPER Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" 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(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false Extensions: "GL_EXT_read_format_bgra" "GL_CHROMIUM_copy_compressed_texture" "GL_ANGLE_program_cache_control" "GL_EXT_discard_framebuffer" "GL_EXT_texture_compression_s3tc_srgb" "GL_EXT_texture_rg" "GL_ANGLE_client_arrays" "GL_ANGLE_request_extension" "GL_OES_texture_npot" "GL_ANGLE_texture_usage" "" "GL_EXT_color_buffer_half_float" "GL_OES_mapbuffer" "GL_OES_EGL_image" "GL_EXT_shader_texture_lod" "GL_EXT_texture_format_BGRA" "GL_OES_packed_depth_stencil" "GL_EXT_color_buffer_float" "GL_OES_EGL_image_external_essl3" "GL_ANGLE_framebuffer_multisample" "GL_CHROMIUM_sync_query" "GL_OES_compressed_ETC1_RGB8_texture" "GL_ANGLE_texture_compression_dxt3" "GL_EXT_debug_marker" "GL_OES_get_program_binary" "GL_OES_rgb8_rgba8" "GL_CHROMIUM_bind_uniform_location" "GL_ANGLE_translated_shader_source" "GL_CHROMIUM_color_buffer_float_rgba" "GL_OES_surfaceless_context" "GL_EXT_texture_norm16" "GL_NV_EGL_stream_consumer_external" "GL_EXT_frag_depth" "GL_OES_texture_half_float" "GL_ANGLE_pack_reverse_row_order" "GL_ANGLE_depth_texture" "GL_NV_fence" "GL_KHR_debug" "GL_NV_pixel_buffer_object" "GL_ANGLE_multiview" "GL_EXT_texture_storage" "GL_ANGLE_texture_compression_dxt5" "GL_OES_EGL_image_external" "GL_EXT_blend_minmax" "GL_EXT_disjoint_timer_query" "GL_ANGLE_robust_client_memory" "GL_OES_depth32" "GL_OES_vertex_array_object" "GL_ANGLE_lossy_etc_decode" "GL_OES_standard_derivatives" "GL_ANGLE_instanced_arrays" "GL_OES_texture_float" "GL_EXT_sRGB" "GL_NV_pack_subimage" "GL_EXT_occlusion_query_boolean" "GL_CHROMIUM_copy_texture" "GL_EXT_map_buffer_range" "GL_OES_texture_fl
[krita] [Bug 446292] Can't change Ten Brushes brushes
https://bugs.kde.org/show_bug.cgi?id=446292 --- Comment #1 from Stig (Rakurri) --- System Info Krita Version: 5.0.0-beta2 (git a642eb0) Languages: en_US, en, en_US, en, en_US, en, en_US, en, nn_NO, nn, en_US, en Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19044 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (NVIDIA GeForce RTX 2070 SUPER Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" 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(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false Extensions: "GL_EXT_read_format_bgra" "GL_CHROMIUM_copy_compressed_texture" "GL_ANGLE_program_cache_control" "GL_EXT_discard_framebuffer" "GL_EXT_texture_compression_s3tc_srgb" "GL_EXT_texture_rg" "GL_ANGLE_client_arrays" "GL_ANGLE_request_extension" "GL_OES_texture_npot" "GL_ANGLE_texture_usage" "" "GL_EXT_color_buffer_half_float" "GL_OES_mapbuffer" "GL_OES_EGL_image" "GL_EXT_shader_texture_lod" "GL_EXT_texture_format_BGRA" "GL_OES_packed_depth_stencil" "GL_EXT_color_buffer_float" "GL_OES_EGL_image_external_essl3" "GL_ANGLE_framebuffer_multisample" "GL_CHROMIUM_sync_query" "GL_OES_compressed_ETC1_RGB8_texture" "GL_ANGLE_texture_compression_dxt3" "GL_EXT_debug_marker" "GL_OES_get_program_binary" "GL_OES_rgb8_rgba8" "GL_CHROMIUM_bind_uniform_location" "GL_ANGLE_translated_shader_source" "GL_CHROMIUM_color_buffer_float_rgba" "GL_OES_surfaceless_context" "GL_EXT_texture_norm16" "GL_NV_EGL_stream_consumer_external" "GL_EXT_frag_depth" "GL_OES_texture_half_float" "GL_ANGLE_pack_reverse_row_order" "GL_ANGLE_depth_texture" "GL_NV_fence" "GL_KHR_debug" "GL_NV_pixel_buffer_object" "GL_ANGLE_multiview" "GL_EXT_texture_storage" "GL_ANGLE_texture_compression_dxt5" "GL_OES_EGL_image_external" "GL_EXT_blend_minmax" "GL_EXT_disjoint_timer_query" "GL_ANGLE_robust_client_memory" "GL_OES_depth32" "GL_OES_vertex_array_object" "GL_ANGLE_lossy_etc_decode" "GL_OES_standard_derivatives" "GL_ANGLE_instanced_arrays" "GL_OES_texture_float" "GL_EXT_sRGB" "GL_NV_pack_subimage" "GL_EXT_occlusion_query_boolean" "GL_CHROMIUM_copy_texture" "GL_EXT_map_buffer_range" "GL_OES_texture_float_linear" "GL_EXT_robustness" "GL_EXT_draw_buffers" "GL_OES_texture_half_float_linear" "GL_CHROMIUM_bind_generates_resource" "GL_CHROMIUM_color_buffer_float_rgb" "GL_EXT_texture_filter_anisotropic" "GL_EXT_texture_compression_dxt1" "GL_EXT_unpack_subimage" "GL_OES_element_index_uint" "GL_ANGLE_framebuffer_blit" QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true useBufferInvalidation (config option): false Hardware Information GPU Acceleration: auto Memory: 40873 Mb Number of Cores: 8 Swap Location: C:/Users/sti-n/AppData/Local/Temp Current Settings Current Swa
[krita] [Bug 446292] New: Can't change Ten Brushes brushes
https://bugs.kde.org/show_bug.cgi?id=446292 Bug ID: 446292 Summary: Can't change Ten Brushes brushes Product: krita Version: 5.0.0-beta2 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Keywords: regression Severity: major Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: sti-n...@online.no Target Milestone: --- SUMMARY Ten Brushes has stopped working as intended for me in the latest versions of Krita 5.0 beta, I can't change the brushes used by the plugin and are stuck with those I had in Krita 4.x STEPS TO REPRODUCE 1. Try to change a the brushes in Ten Brushes (Tools -> Scripts -> Ten Brushes") 2. Try to use the shortcuts to change between them. Or go back in the menu to see there were no changes 3. Changes were not applied. OBSERVED RESULT Can't configure or change the brushes used by Ten Brushes EXPECTED RESULT Being able to configure and change brushes SOFTWARE/OS VERSIONS Windows 10 Krita Plus - 5.0.0-beta2 (git a642eb0) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443548] This file crashes when saving incrementaly
https://bugs.kde.org/show_bug.cgi?id=443548 --- Comment #3 from Stig (Rakurri) --- Thank you! I tested the 5.1.0 prealpha build and it worked like a charm there! I hope this fix makes it into the full release of 5.0.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443548] This file crashes when saving incrementaly
https://bugs.kde.org/show_bug.cgi?id=443548 --- Comment #1 from Stig (Rakurri) --- Crash Log SESSION: 09 Oct 2021 00:16:59 +0200. Executing C:\Program Files\Krita (x64)\bin\krita.exe Krita Version: 5.0.0-beta2, Qt version compiled: 5.12.11, loaded: 5.12.11. Process ID: 53352 09 Oct 2021 00:16:59 +0200: Style: fusion. Available styles: windowsvista, Windows, Fusion 09 Oct 2021 00:17:01 +0200: Database is up to date. Version: 0.0.13, created by Krita 5.0.0-beta1, at on. aug 18 21:15:13 2021 09 Oct 2021 00:17:04 +0200: Non-store package - creating updater 09 Oct 2021 00:17:15 +0200: Importing application/x-krita to application/x-krita. Location: C:/Users/sti-n/OneDrive/2D Art/2D Prosjektfilar/2021/Amethyst/Amethyst14_013.kra. Real location: C:/Users/sti-n/OneDrive/2D Art/2D Prosjektfilar/2021/Amethyst/Amethyst14_013.kra. Batchmode: 0 09 Oct 2021 00:17:15 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:17:15 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:17:15 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:17:17 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:17:17 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:17:17 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:17:18 +0200: Loaded image from application/x-krita. Size: 3733 * 5327 pixels, 4.16665 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB built-in). Layers: 21 09 Oct 2021 00:18:35 +0200: Saving Document C:/Users/sti-n/OneDrive/2D Art/2D Prosjektfilar/2021/Amethyst/Amethyst14_013.kra as C:/Users/sti-n/OneDrive/2D Art/2D Prosjektfilar/2021/Amethyst/Amethyst14_014.kra (mime: application/x-krita). 3733 * 5327 pixels, 22 layers. 101 frames, 24 framerate. Export configuration: No configuration SESSION: 09 Oct 2021 00:18:41 +0200. Executing C:\Program Files\Krita (x64)\bin\krita.exe Krita Version: 5.0.0-beta2, Qt version compiled: 5.12.11, loaded: 5.12.11. Process ID: 42496 09 Oct 2021 00:18:41 +0200: Style: fusion. Available styles: windowsvista, Windows, Fusion 09 Oct 2021 00:18:43 +0200: Database is up to date. Version: 0.0.13, created by Krita 5.0.0-beta1, at on. aug 18 21:15:13 2021 09 Oct 2021 00:18:46 +0200: Non-store package - creating updater 09 Oct 2021 00:19:10 +0200: Importing application/x-krita to application/x-krita. Location: C:/Users/sti-n/OneDrive/2D Art/2D Prosjektfilar/2021/Amethyst/Amethyst14_013.kra. Real location: C:/Users/sti-n/OneDrive/2D Art/2D Prosjektfilar/2021/Amethyst/Amethyst14_013.kra. Batchmode: 0 09 Oct 2021 00:19:10 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:19:10 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:19:10 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:19:11 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:19:12 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:19:12 +0200: SAFE ASSERT (krita): “!localResources.contains(KoResourceSP())” in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\resources\KisLocalStrokeResources.cpp, line 80 09 Oct 2021 00:19:13 +0200: Loaded image from application/x-krita. Size: 3733 * 5327 pixels, 4.16665 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB built-in). Layers: 21 09 Oct 2021 00:20:05 +0200: Saving Document C:/Users/sti-n/OneDrive
[krita] [Bug 443548] New: This file crashes when saving incrementaly
https://bugs.kde.org/show_bug.cgi?id=443548 Bug ID: 443548 Summary: This file crashes when saving incrementaly Product: krita Version: 5.0.0-beta2 Platform: Other OS: Microsoft Windows Status: REPORTED Keywords: regression, release_blocker Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: sti-n...@online.no Target Milestone: --- SUMMARY The file was started in Krita 5.0 Beta 1 or earlier but when I updated to Krita 5.0 Beta 2 I crash whenever I incrementally save it. File: https://drive.google.com/file/d/14t28upXQcrBpK4ho3dLyuqL7rgAWyCIp/view?usp=sharing STEPS TO REPRODUCE 1. Open file 2. Increment save, Krita crashes on my Windows 10 PC with Krita 5.0 Beta 2 3. If it does not crash, paint on the "Transparency Mask 1" layer and then incremental save. OBSERVED RESULT Crash EXPECTED RESULT Saving an incremental version SOFTWARE/OS VERSIONS Windows 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441886] Crash when using Filter Engine brush with Gradient Map
https://bugs.kde.org/show_bug.cgi?id=441886 --- Comment #2 from Stig (Rakurri) --- Sorry I forgot, here is the crash log: https://pastebin.com/cRfkRAsj -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441886] New: Crash when using Filter Engine brush with Gradient Map
https://bugs.kde.org/show_bug.cgi?id=441886 Bug ID: 441886 Summary: Crash when using Filter Engine brush with Gradient Map Product: krita Version: 5.0.0-beta1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: sti-n...@online.no Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Change a Filter Engine Brush's filter to Gradient Map 2. Paint with it 3. Interact with the layers. For instance create a new layer. OBSERVED RESULT Krita crashes EXPECTED RESULT Krita should not crash, and the user should be able to make new layers etc SOFTWARE/OS VERSIONS Windows 10 Krita 5.0 Beta1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438096] Color Smudge brush with Overlay Mode turned on crashes Krita when painting in the "Paint in this area"
https://bugs.kde.org/show_bug.cgi?id=438096 --- Comment #2 from Stig (Rakurri) --- I think this is it: https://pastebin.com/MBRjmbaE -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438096] New: Color Smudge brush with Overlay Mode turned on crashes Krita when painting in the "Paint in this area"
https://bugs.kde.org/show_bug.cgi?id=438096 Bug ID: 438096 Summary: Color Smudge brush with Overlay Mode turned on crashes Krita when painting in the "Paint in this area" Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Keywords: regression, release_blocker Severity: crash Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: sti-n...@online.no Target Milestone: --- Color Smudge brush with Overlay Mode turned on crashes Krita when painting in the "Paint in this area" section when creating a new Brush Preset. STEPS TO REPRODUCE 1. Have a Smudge Engine Brush with “Overlay Mode” turned on 2. “Save New Brush Preset…” 3. Paint in the “Paint in this area” with the brush, Krita will hang, and then crash OBSERVED RESULT Krita freezes, then crashes. EXPECTED RESULT Smudging of the thumbnail, if a custom one is added, it would smudge the thumbnail, just like a normal smudge brush without Overlay Mode turned on would. SOFTWARE/OS VERSIONS 5.0.0-prealpha (git 9bad11e) Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423950] Unable to render to mp4 in kdenlive with ffmpeg 4.3
https://bugs.kde.org/show_bug.cgi?id=423950 Stig-Ørjan Smelror changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Stig-Ørjan Smelror --- Found the culprit. mlt needed to be rebuilt with ffmpeg 4.3. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423950] New: Unable to render to mp4 in kdenlive with ffmpeg 4.3
https://bugs.kde.org/show_bug.cgi?id=423950 Bug ID: 423950 Summary: Unable to render to mp4 in kdenlive with ffmpeg 4.3 Product: kdenlive Version: 20.04.2 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: smel...@gmail.com Target Milestone: --- Created attachment 129948 --> https://bugs.kde.org/attachment.cgi?id=129948=edit Unable to render to mp4 SUMMARY Unable to render mp4/aac with ffmpeg 4.3 STEPS TO REPRODUCE 1. Install Mageia Cauldron 2. Launch kdenlive 3. Create a video project 4. Try to render to mp4 OBSERVED RESULT The mp4 option is greyed out and unavailable EXPECTED RESULT Being able to render to mp4 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Mageia Cauldron (available in About System) KDE Plasma Version: 20.04.2 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION ffmpeg, gpac and x264 tainted are installed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409613] "Reset Canvas Rotation" set to "Space + R" breaks color picking after pan action
https://bugs.kde.org/show_bug.cgi?id=409613 --- Comment #13 from Stig --- I didn't experience the bug while testing in the new package, seems to work for me too! :) Thank you! Dmitry -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404133] Artifacts when painting in RGB 32-bit float/channel
https://bugs.kde.org/show_bug.cgi?id=404133 Stig changed: What|Removed |Added CC||sti-n...@online.no --- Comment #13 from Stig --- Can confirm, this also happens on Windows 10 with both the 16-bit float/channel and 32-bit float/channel, using the 4.2.9-beta. one of the brushes this happens with is j)_Waterpaint_Soft_Edges -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399190] Instant Preview causes severe canvas slowdown with non-painting tools on large documents
https://bugs.kde.org/show_bug.cgi?id=399190 Stig changed: What|Removed |Added CC||sti-n...@online.no --- Comment #4 from Stig --- This happens to me too. Zooming is extremely slow when I am working on an animation with Instant Preview Mode turned on, while zooming is buttery smooth when it is turned off. Using Krita 4.2.8 on Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409613] Color picker shortcut doesn't work after moving canvas with spacebar(pan tool shortcut)
https://bugs.kde.org/show_bug.cgi?id=409613 Stig changed: What|Removed |Added CC||sti-n...@online.no --- Comment #5 from Stig --- I also had the same problem. On all of my 3 Windows 10 computers the "Zoom Canvas" and "Alternate Invocation" did not work when I expected them to, and often were unresponsive for many seconds. It seemed to stop working at seemingly random times. Which was extremely frustrating. But now I know thanks to Hector, that this was caused by my keyboard shortcut for "Reset Canvas Rotation" being set to "Space + R" in my shortcut scheme which I used on all of my computers. I also propose that Krita should disable the appointment of shortcuts with a space. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379039] syscall wrapper for prctl(PR_SET_NAME) must not check more than 16 bytes
https://bugs.kde.org/show_bug.cgi?id=379039 --- Comment #7 from Peter (Stig) Edwards <thatsafunnyname.ra...@mailnull.com> --- Thank you very much for the patch, I built and tested and it works as expected. For the changes in coregrind/m_syswrap/syswrap-linux.c, I was thinking it might be better to use VKI_TASK_COMM_LEN ( as defined in include/vki/vki-linux.h ) and not 16. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379039] syscall wrapper for prctl(PR_SET_NAME) must not check more than 16 bytes
https://bugs.kde.org/show_bug.cgi?id=379039 --- Comment #4 from Peter (Stig) Edwards <thatsafunnyname.ra...@mailnull.com> --- Created attachment 105142 --> https://bugs.kde.org/attachment.cgi?id=105142=edit A hack of a patch that just duplicates the asciiz func with a _limit_len version. A hack of a patch that just duplicates the asciiz func with a _limit_len version. A proper fix would avoid the duplication of code. Probably not that useful. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379039] False positive when passing non null terminated char* name (len 16 >= bytes) to prctl(PR_SET_NAME
https://bugs.kde.org/show_bug.cgi?id=379039 --- Comment #2 from Peter (Stig) Edwards <thatsafunnyname.ra...@mailnull.com> --- (In reply to Ivo Raisr from comment #1) > Yes, indeed. Kernel takes care to copy TASK_COMM_LEN at max. > Please could you supply a patch with the fix? Thank you for the quick response. I did look to see if I could find a quick fix. I was looking for a *asciiz function in memcheck/mc_main.c that could take a length limit so that I could pass TASK_COMM_LEN to it. I did not find one. I thought it might be possible in coregrind/m_syswrap/syswrap-linux.c::PRE(sys_prctl) VKI_PR_SET_NAME case to change PRE_MEM_RASCIIZ to a strnlen call with TASK_COMM_LEN and then call PRE_MEM_READ with size. I am not familiar with the valgrind codebase and I do not currently have time to work on a patch for this. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379039] New: False positive when passing non null terminated char* name (len 16 >= bytes) to prctl(PR_SET_NAME
https://bugs.kde.org/show_bug.cgi?id=379039
Bug ID: 379039
Summary: False positive when passing non null terminated char*
name (len 16 >= bytes) to prctl(PR_SET_NAME
Product: valgrind
Version: 3.12.0
Platform: RedHat RPMs
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: thatsafunnyname.ra...@mailnull.com
Target Milestone: ---
Hello and thank you for valgrind,
This is a minor edge case.
I noticed that with a non null terminated array of 16 chars passed to prctl
with PR_SET_NAME, valgrind 3.12.0 ( and 3.11.0 , 3.10.0 , 3.8.1 and 3.5.0 )
memcheck ends up calling mc_is_defined_asciiz which checks a zero-terminated
ascii string and reports the memory error "Syscall param prctl(set-name) points
to uninitialised byte(s)". I don't think the name *has* to be null terminated
if it is 16 bytes (or more).
>From the linux man page:
"The name can be up to 16 bytes long,
including the terminating null byte.
(If the length of the string, including the terminating null byte,
exceeds 16 bytes, the string is silently truncated.)"
Reproducer:
# cat valgrind_memcheck_prctl.c
#include
int main(int argc, char *argv[]){
char buf[16] = "1234567890123456";
int ret = prctl(PR_SET_NAME, buf, 0, 0, 0);
return ret;
}
# gcc -g valgrind_memcheck_prctl.c
# valgrind --track-origins=yes ./a.out
==143257== Memcheck, a memory error detector
==143257== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==143257== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==143257== Command: ./a.out
==143257==
==143257== Syscall param prctl(set-name) points to uninitialised byte(s)
==143257==at 0x4F2AF8A: prctl (in /usr/lib64/libc-2.17.so)
==143257==by 0x400580: main (valgrind_memcheck_prctl.c:4)
==143257== Address 0xfff000260 is on thread 1's stack
==143257== in frame #1, created by main (valgrind_memcheck_prctl.c:2)
==143257== Uninitialised value was created by a stack allocation
==143257==at 0x400530: main (valgrind_memcheck_prctl.c:2)
==143257==
==143257==
==143257== HEAP SUMMARY:
==143257== in use at exit: 0 bytes in 0 blocks
==143257== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==143257==
==143257== All heap blocks were freed -- no leaks are possible
==143257==
==143257== For counts of detected and suppressed errors, rerun with: -v
==143257== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Above is on a RHEL7 x86_64 host, using the valgrind-3.10.0-16.el7 RPM and
gcc-4.8.5-4.el7.
Cheers,
Peter (Stig) Edwards
--
You are receiving this mail because:
You are watching all bug changes.
