[krita] [Bug 476304] Wiggle at start of line with 2-point-perspective assistant
https://bugs.kde.org/show_bug.cgi?id=476304 --- Comment #5 from Rebecca Breu --- Yeah, the wiggles are gone now. I tested with the file I had attached to this bug report, and also another file where I tried out my most frequent use cases. Overall, it works well for me now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410807] Python Debugger throws exception when ran
https://bugs.kde.org/show_bug.cgi?id=410807 Rebecca Breu changed: What|Removed |Added Status|ASSIGNED|CONFIRMED --- Comment #11 from Rebecca Breu --- I just checked that on Linux, the Debugger still works. BUG 478341 has a slightly different traceback than the original one here, possibly since our current Python version is trying to deal with the forking issue a bit differently, but I think the underlying cause is still the same. Since I failed to find a solution and am not currently working on it, I'm unassigning myself. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410807] Python Debugger throws exception when ran
https://bugs.kde.org/show_bug.cgi?id=410807 Rebecca Breu changed: What|Removed |Added CC||gecko...@gmx.de --- Comment #10 from Rebecca Breu --- *** Bug 478341 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478341] Errors trying to run "Hello World" in Scripter Debugger
https://bugs.kde.org/show_bug.cgi?id=478341 Rebecca Breu changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||rebe...@rbreu.de --- Comment #3 from Rebecca Breu --- *** This bug has been marked as a duplicate of bug 410807 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478010] Scripter will not open
https://bugs.kde.org/show_bug.cgi?id=478010 Rebecca Breu changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478010] Scripter will not open
https://bugs.kde.org/show_bug.cgi?id=478010 Rebecca Breu changed: What|Removed |Added Resolution|--- |FIXED CC||rebe...@rbreu.de Status|REPORTED|NEEDSINFO --- Comment #1 from Rebecca Breu --- Are there any Python tracebacks or other relevant output in Help -> Show Krita log? (And btw, the issue you linked is only relevant for a self-compiled Krita. Krita comes with its own embedded Python and doesn't use your installation.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476304] Wiggle at start of line with 2-point-perspective assistant
https://bugs.kde.org/show_bug.cgi?id=476304 Rebecca Breu changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477731] New: Editing Gamut Mask: Canvas not initialised properly
https://bugs.kde.org/show_bug.cgi?id=477731 Bug ID: 477731 Summary: Editing Gamut Mask: Canvas not initialised properly Classification: Applications Product: krita Version: 5.2.0 Platform: Other OS: Linux Status: REPORTED Keywords: regression Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: rebe...@rbreu.de Target Milestone: --- This happens from 5.2.0 onwards up to current master, but was fine in 5.1.5 STEPS TO REPRODUCE 1. Go to the gamut masks docker 2. Select a Gamut mask, click edit 3. The canvas now turns into the Gamut Mask Editor, but it stays completely grey. It should show the color wheel and the current mask instead. If you know where the mask is supposed to be, you can still for example drag the shape, then Krita will start to update the canvas properly. See video: https://www.youtube.com/watch?v=uc84Hyd_dGs Krita Version: 5.2.0 and also 5.3.0-prealpha (git 7058e47) Hidpi: false 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.10.0-26-amd64 Pretty Productname: Debian GNU/Linux 11 (bullseye) Product Type: debian Product Version: 11 Desktop: GNOME Appimage build: Yes Locale Languages: en_US, en, en_Latn_US, en, en_US, en_Latn_US C locale: en_GB.UTF-8 QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Intel" Renderer: "Mesa Intel(R) HD Graphics 630 (KBL GT2)" Driver version: "4.6 (Core Profile) Mesa 20.3.5" 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 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476304] Wiggle at start of line with 2-point-perspective assistant
https://bugs.kde.org/show_bug.cgi?id=476304 --- Comment #3 from Rebecca Breu --- Another user has reported the same behaviour on KA: https://krita-artists.org/t/problem-with-combining-2-points-perspective-vanishing-point-assistants-in-version-5-2-1/77984/2 I've further found it's not only the 2-point perspective assistant that's causing this, just the one most likely/frequent to behave like this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476849] python error on popup
https://bugs.kde.org/show_bug.cgi?id=476849 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Rebecca Breu --- That's an error happening in the Pigment-O plugin, which is not part of Krita. You'll have to ask the Pigmento-O developer. My guess is you are using a version of the plugin that's not compatible with the latest version of Krita. Check if Pigment-O has a new version out that fixes the problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468082] Vanishing Point assistant doesn't follow canvas rotation
https://bugs.kde.org/show_bug.cgi?id=468082 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #4 from Rebecca Breu --- Yeah, I also just stumbled upon this behaviour with the 5.2 appimage. All other assistants draw their lines according to the coordinate system of the canvas, while the single vanishing point seems to use the screen coordinate system for its radial lines instead. This is not very intuitive, imo, and it gets pretty confusing when the VP's center is way off to the canvas rotation origin, since the VP's center itself of course does rotate with the canvas. It gives the optical illusion of the VP's radial lines rotating the opposite direction. https://youtu.be/M3NkDaK-wK8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476304] Wiggle at start of line with 2-point-perspective assistant
https://bugs.kde.org/show_bug.cgi?id=476304 --- Comment #2 from Rebecca Breu --- Playing around with it further, I think the line wants to snap to the single vanishing point first before it decides to latch onto the 2-point assistant. Only that I have "Snap to single line" enabled where it should stick with the line first snapped onto. The less precise I am with my line, the bigger the wiggle. For some lines, it's almost impossible to be precise enough to not get a wiggle at all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476304] Wiggle at start of line with 2-point-perspective assistant
https://bugs.kde.org/show_bug.cgi?id=476304 --- Comment #1 from Rebecca Breu --- Created attachment 162705 --> https://bugs.kde.org/attachment.cgi?id=162705=edit Example kra file with assistants set up -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476304] New: Wiggle at start of line with 2-point-perspective assistant
https://bugs.kde.org/show_bug.cgi?id=476304 Bug ID: 476304 Summary: Wiggle at start of line with 2-point-perspective assistant Classification: Applications Product: krita Version: 5.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: rebe...@rbreu.de Target Milestone: --- Created attachment 162704 --> https://bugs.kde.org/attachment.cgi?id=162704=edit Screenshot of wiggles I've set up a 2-point-assistant and a vanishing point. If I draw a line with snap to assistant that's supposed to snap to the 2-point assistant, the start of the line often has a small wiggle. "Snap to single line" is activated. See screenshot. Drawing the same line in the reverse direction usually doesn't get a wiggle. Snapping to the single vanishing point doesn't produce any wiggles. If I remove the single vanishing point, no wiggles either. If I go back to Krita 5.1.5, no wiggles either with the same setup of assistants. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475261] when i used dock(comic manager) and create a new page, krita crashed.
https://bugs.kde.org/show_bug.cgi?id=475261 Rebecca Breu changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475261] when i used dock(comic manager) and create a new page, krita crashed.
https://bugs.kde.org/show_bug.cgi?id=475261 Rebecca Breu changed: What|Removed |Added Resolution|--- |FIXED CC||rebe...@rbreu.de Status|REPORTED|NEEDSINFO --- Comment #1 from Rebecca Breu --- It looks like you are using the Krita version from your distribution's package manager? Please try the appimage directly from krita.org instead. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475183] Switching between files performance issue
https://bugs.kde.org/show_bug.cgi?id=475183 --- Comment #3 from Rebecca Breu --- GMail refuses the mail (too big with two files, too spammy with one file). :( If've put up a file here for the moment: http://rbreu.de/comic033.kra You can save the file twice under different names and use those for switching, that should do the trick. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475183] Switching between files performance issue
https://bugs.kde.org/show_bug.cgi?id=475183 Rebecca Breu changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Rebecca Breu --- Sorry for the delay. The files were to big for attaching directly and dropbox TFA mails are failing to reach me at the moment. :( I sent you a mail. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473064] Boot with no dockers and Plugins ( Comic Book Manager and Log Viewer )
https://bugs.kde.org/show_bug.cgi?id=473064 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473429] New start screen in 5.2 Beta adds extra steps to docker plugins that create a new project
https://bugs.kde.org/show_bug.cgi?id=473429 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475183] New: Switching between files performance issue
https://bugs.kde.org/show_bug.cgi?id=475183 Bug ID: 475183 Summary: Switching between files performance issue Classification: Applications Product: krita Version: 5.2.0-rc1 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: rebe...@rbreu.de Target Milestone: --- Created attachment 162057 --> https://bugs.kde.org/attachment.cgi?id=162057=edit Screenshot of popup On 5.2 rc1, subwindows enabled, all files in fullscreen. I noticed that when having multiple files open, switching to another image sometimes takes a couple of seconds and I get a “Waiting for image operation to complete” popup. (See screenshot.) It seems to have to do with the complexity of the files (vs my older laptop, I guess). With the files I'm currently working on, I can reliably reproduce this with: 1. Have two files open 2. Paint on file 1 3. Switch to file 2 (instantaneous) 4. Switch back to file 1: slow and and you get the popup 5. Further switching will be instantaneous again until you do other stuff If I do the same thing on 5.1 with the same files, switching as always instantaneous. I don't remember even having this issue on 5.1, and I've been working working on this project and frequently switching for a while now. I'll be attaching two test files that seem just about complex enough to trigger this issue on my system, though they might not on a different computer? Memory usage in the bottom bar is always reporting fine, with the attached test images it's still in the blue range. Krita Version: 5.2.0-rc1 (git 3323e4e) Hidpi: false 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.10.0-25-amd64 Pretty Productname: Debian GNU/Linux 11 (bullseye) Product Type: debian Product Version: 11 Desktop: GNOME Appimage build: Yes Locale Languages: en_US, en, en_Latn_US, en, en_US, en_Latn_US C locale: en_GB.UTF-8 QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Intel" Renderer: "Mesa Intel(R) HD Graphics 630 (KBL GT2)" Driver version: "4.6 (Core Profile) Mesa 20.3.5" 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_AMD_depth_clamp_separate GL_EXT_framebuffer_multisample_blit_scaled GL_ARB_shading_language_include GL_KHR_context_flush_control GL_NV_packed_depth_stencil GL_ARB_clear_buffer_object GL_ARB_draw_buffers GL_AMD_vertex_shader_layer GL_EXT_texture_shadow_lod GL_ARB_texture_query_levels GL_ARB_robust_buffer_access_behavior GL_ARB_copy_buffer GL_ARB_ES3_compatibility GL_AMD_texture_texture4 GL_ARB_vertex_array_bgra GL_NV_depth_clamp GL_ARB_robustness GL_OES_EGL_image GL_KHR_texture_compression_astc_ldr GL_ARB_polygon_offset_clamp GL_ARB_shader_viewport_layer_array GL_ARB_sample_shading GL_EXT_EGL_sync GL_ARB_base_instance GL_AMD_shader_trinary_minmax GL_MESA_shader_integer_functions GL_ARB_framebuffer_no_attachments GL_ARB_invalidate_subdata GL_ARB_arrays_of_arrays GL_ARB_direct_state_access GL_KHR_debug GL_ARB_conservative_depth GL_AMD_query_buffer_object GL_ARB_shader_stencil_export GL_NV_fragment_shader_interlock GL_ARB_shader_ballot GL_ARB_texture_non_power_of_two GL_KHR_no_error GL_ARB_shader_atomic_counter_ops GL_ARB_texture_storage_multisample GL_EXT_texture_compression_rgtc GL_ARB_shader_texture_lod GL_ARB_fragment_shader GL_ARB_get_program_binary GL_ARB_shader_texture_image_samples GL_ARB_shader_draw_parameters GL_EXT_draw_instanced GL_ARB_parallel_shader_compile GL_EXT_texture_shared_exponent GL_ANGLE_texture_compression_dxt5 GL_NV_conditional_render GL_ARB_shader_clock
[krita] [Bug 475172] New: Wrong file name in title bar
https://bugs.kde.org/show_bug.cgi?id=475172 Bug ID: 475172 Summary: Wrong file name in title bar Classification: Applications Product: krita Version: 5.2.0-rc1 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: rebe...@rbreu.de Target Milestone: --- Created attachment 162051 --> https://bugs.kde.org/attachment.cgi?id=162051=edit Screenshots of all three steps On 5.2 rc1, subwindows enabled, all files in fullscreen. I’m noticing a weirdness with the title bar that I don’t understand. I start Krita and open my first file called comic031.kra. The title bar looks as it did in previous versions, see also attached screenshots: (1.4 GiB) - [comic031.kra] — Krita I open a second file called comic033.kra while the first file is still open, now I get the filename displayed twice. comic033.kra (714.5 MiB) - [comic033.kra] — Krita If I reproduce this step in 5.1, I still only have the name in brackets, not the name at the beginning of the line. Now if I switch back to the first image, I get two *different* file names displayed, plus what seems like the file size of the other image: comic033.kra (714.5 MiB) - [comic031.kra] — Krita Again, in 5.1 I only get the second filename and the correct size. Both documents have document titles set, comic031 and comic033 respectively. If I keep opening more files, they all get comic033 as second file name, and that image’s size. Trying out other orders of opening the files, I think Krita just really likes the alphabetically last one. Why is it trying to display two file names in the first place? I can’t see what use that would be. I can imagine displaying the document title could be useful, which my files have set but those don’t have the .kra ending. This is a somewhat scary problem, because I feared for a moment that I was overwriting files I didn't want to overwrite. Krita Version: 5.2.0-rc1 (git 3323e4e) Hidpi: false 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.10.0-25-amd64 Pretty Productname: Debian GNU/Linux 11 (bullseye) Product Type: debian Product Version: 11 Desktop: GNOME Appimage build: Yes Locale Languages: en_US, en, en_Latn_US, en, en_US, en_Latn_US C locale: en_GB.UTF-8 QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Intel" Renderer: "Mesa Intel(R) HD Graphics 630 (KBL GT2)" Driver version: "4.6 (Core Profile) Mesa 20.3.5" 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_get_texture_sub_image GL_ARB_texture_multisample GL_ARB_shader_group_vote GL_ARB_shader_draw_parameters GL_ATI_texture_float GL_AMD_conservative_depth GL_ARB_texture_non_power_of_two GL_ARB_ES3_compatibility GL_ARB_occlusion_query2 GL_ARB_texture_compression_rgtc GL_EXT_texture_swizzle GL_AMD_texture_texture4 GL_ARB_vertex_shader GL_KHR_robust_buffer_access_behavior GL_ARB_depth_buffer_float GL_KHR_no_error GL_ARB_shading_language_packing GL_ARB_framebuffer_no_attachments GL_ARB_shader_clock GL_ARB_half_float_pixel GL_ARB_vertex_array_object GL_ARB_gpu_shader_int64 GL_ARB_robustness GL_NV_conditional_render GL_ARB_shader_texture_image_samples GL_ARB_shader_precision GL_ARB_shader_atomic_counter_ops GL_ARB_texture_storage_multisample GL_ARB_transform_feedback3 GL_ARB_ES3_1_compatibility GL_ARB_texture_swizzle GL_ARB_draw_buffers_blend GL_S3_s3tc GL_ARB_texture_buffer_range GL_ARB_draw_buffers GL_ARB_draw_indirect GL_ARB_fragment_shader_interlock GL_ARB_shader_storage_buffer_object GL_INTEL_shader_atomic_float_minmax
[digikam] [Bug 464354] When typing in the Face Tag Box whilst in "Preview", esc should just exit the type box
https://bugs.kde.org/show_bug.cgi?id=464354 --- Comment #2 from Rebecca Wardle --- I think there should be shortcut options for the buttons under the text box: "Ok", "Remove" and "Ignore". After typing a name into the box "Ok" can be triggered with enter and I think there should be keybinds so you don't have to use the mouse to click on "Remove" or "Ignore" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464359] New: Shortcut for the Face tagging box options
https://bugs.kde.org/show_bug.cgi?id=464359 Bug ID: 464359 Summary: Shortcut for the Face tagging box options Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: beccamwar...@gmail.com Target Milestone: --- There should exist shortcut options for the confirm, remove and ignore options of the face tagging system. "Enter" functions as a confirm, but I can find no reference to other shortcuts for this. Shortcuts here would rapidly increase efficiency when first setting up or inporting large numbers of photos -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464354] New: When typing in the Face Tag Box whilst in "Preview", esc should just exit the type box
https://bugs.kde.org/show_bug.cgi?id=464354 Bug ID: 464354 Summary: When typing in the Face Tag Box whilst in "Preview", esc should just exit the type box Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: beccamwar...@gmail.com Target Milestone: --- Experienced on Windows 11 This is a usability feature. When typing into the Face Tag Box whilst in "Preview" mode, esc should just exit the type box instead of exiting preview mode back to "Thumbnails" view. A second esc could then escape "Preview" mode, but I (and I suspect most users) would expect "Esc" to initially escape/exit any active text boxes before changing the display -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429265] Import Python Plugin doesn't activate the plugin
https://bugs.kde.org/show_bug.cgi?id=429265 Rebecca Breu changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/3d010f44a ||1686d2e1bf350903345b0d91350 ||32f2 Status|ASSIGNED|RESOLVED --- Comment #6 from Rebecca Breu --- Git commit 3d010f44a1686d2e1bf350903345b0d9135032f2 by Rebecca Breu. Committed on 24/11/2020 at 17:31. Pushed by rempt into branch 'master'. Let users choose to enable imported plugins The final MessageBox informing the user about the successfully imported plugins now lets the user choose to enable them immediately. The user still needs to restart Krita, but at least now you only need to restart once, and you don't have to search through the Plugin Manager yourself. M +21 -11 plugins/python/plugin_importer/plugin_importer_extension.py https://invent.kde.org/graphics/krita/commit/3d010f44a1686d2e1bf350903345b0d9135032f2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429265] Import Python Plugin doesn't activate the plugin
https://bugs.kde.org/show_bug.cgi?id=429265 Rebecca Breu changed: What|Removed |Added Status|REPORTED|ASSIGNED CC||rebe...@rbreu.de Assignee|krita-bugs-n...@kde.org |rebe...@rbreu.de Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429262] Import Python Plugins doesn't import all action files
https://bugs.kde.org/show_bug.cgi?id=429262 --- Comment #2 from Rebecca Breu --- Sure! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 428299] New: the "battery and brightness" widget display only 1st battery
https://bugs.kde.org/show_bug.cgi?id=428299 Bug ID: 428299 Summary: the "battery and brightness" widget display only 1st battery Product: Powerdevil Version: 5.20.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rebecca.b.9...@gmail.com Target Milestone: --- SUMMARY At the moment the "battery and brightness" widget currently allows to see as icon only the first battery status when placed on a panel, and the user must click on the plasmoid to see all of other batteries installed on the computer as context menu, and seemingly there are not an option to select which one the user wants to display in the plasmoid setup. STEPS TO REPRODUCE 1. Place the "battery and brightness" widget on a panel, you see the status of the 1st battery. 2. Click on the "battery and brightness" plasmoid, you see on the context menu any other battery installed on the system. 3. Right click on the plasmoid, press on "configure battery and brightness" to open the widget configurator menu: there is only one option, which is the possibility to show the percentage or not, nor other. OBSERVED RESULT Absence in the configuration menu of an option that allows you to choose which battery to display the status of as a widget icon. EXPECTED RESULT Presence in the configuration menu of an option that allows you to choose which battery to display the status of as a widget icon. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416922] Full screen and canvas mode switching issues on secondary monitor
https://bugs.kde.org/show_bug.cgi?id=416922 Rebecca Breu changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Rebecca Breu --- I can't reproduce it anymore either. Closing this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419153] Wacom pen AND computer mouse are not recognized by Krita canvas
https://bugs.kde.org/show_bug.cgi?id=419153 Rebecca Breu changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||rebe...@rbreu.de --- Comment #3 from Rebecca Breu --- Audrey, does it help when you go to Settings -> Configure Krita -> Display -> Canvas Acceleration and there set the Renderer from OpenGL to Angle (or vice versa) and restart Krita? Tricia, this sounds like a different problem. If something suddenly stops working it's likely you got an operating system update that messed up your tablet driver. Try reinstalling the driver. If you have any more issues, ask in krita-artists.org first, since this is not a user support platform. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419758] Using transform tool on a vector layer causes the layer to appear invisible.
https://bugs.kde.org/show_bug.cgi?id=419758 --- Comment #4 from Rebecca Breu --- Related bug: https://bugs.kde.org/show_bug.cgi?id=420919 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420919] Transormation tool should not allow to be used over vector layers, and inform to use transform mask instead
https://bugs.kde.org/show_bug.cgi?id=420919 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #3 from Rebecca Breu --- Related bug: https://bugs.kde.org/show_bug.cgi?id=419758 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420609] When i select a colour in the colour selector tool, it doesnt give me that colour it only gives me black, grey or white
https://bugs.kde.org/show_bug.cgi?id=420609 Rebecca Breu changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- Can you please attach a screenshot of your whole Krita window with the layers docker visible? It's important to know what colours space you are using and what kind of layer you are on (a pixel layer vs a mask for example). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420532] Using Cut at Point doesn't break a Vector into two parts
https://bugs.kde.org/show_bug.cgi?id=420532 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- I'm pretty sure this is intended behaviour, maybe someone else can confirm? It's at least what I'd expect, and I just checked and it works the same in Inkscape, for example. You can also use the "break at point" button for "opening" a closed path (like a closed polygon) and in that case the shape is still connected and can't be split into two vector shapes anyway. So if anything, splitting vector shapes should be a new feature that probably needs a bit of design discussion first. Inkscape has a dedicated "Break apart" action for this in the "Path" menu which splits a vector shape into all its unconnected parts. But then, Inkscape has plenty of other path options as well: different ways of combining shapes, converting them etc etc. Krita doesn't have any of that at the moment. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420531] Copy & Pasting Vector Shape from one layer to another doesn't preserve node type.
https://bugs.kde.org/show_bug.cgi?id=420531 Rebecca Breu changed: What|Removed |Added Summary|Moving Vector from one |Copy & Pasting Vector Shape |layer to another doesn't|from one layer to another |preserve node type. |doesn't preserve node type. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420531] Moving Vector from one layer to another doesn't preserve node type.
https://bugs.kde.org/show_bug.cgi?id=420531 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Rebecca Breu --- I can confirm this on the 4.2.9 appimage. You don't even have to paste it do a different layer--pasting to the same layer has the same effect. Pasting to Inkscape too. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420476] Krita canvas wont let me draw or use any tools but after clicking outside of canvas the drawings will appear
https://bugs.kde.org/show_bug.cgi?id=420476 Rebecca Breu changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||rebe...@rbreu.de Resolution|--- |WAITINGFORINFO --- Comment #1 from Rebecca Breu --- Does it help if you go to Settings -> Configure Krita -> Display -> Canvas Acceleration and there set the Renderer from OpenGL to Angle (or vice versa) and then restart Krita? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420342] Transparency colour not saved
https://bugs.kde.org/show_bug.cgi?id=420342 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #6 from Rebecca Breu --- I still don't know what exactly you are doing, and I can't reproduce any bugs regarding transparency. "Therefor I started to change the background to 'white-transparent'." What do you mean by this? The transparency checkerboard of the canvas? Your layers? Your png export? "This figure should have a transparent background and had it through the whole procedure of making but once saved, the background is white, transparency gone." You should save your images as kra files and only export them to other file formats once you are done. If you don't export the png with "Store alpha channel" enabled, then (and only then) you get to pick a colour at the bottom of the export dialog with which your transparency is going to be replaced and then, yes, the transparency will be gone in the exported png. Even if you open that png up again in Krita. "And in some occasions a soft grey or white shade appears on the saved picture which is invisible in Krita." My guess is that it's there but not very visible on the white-and-grey transparency checkerboard, and just a bit that you wanted to erase but didn't erase completely with the soft eraser because you couldn't see it. If you are working on black and white pictures, it's probably best to either change the colour of the transparency checkerboard (Settings -> Configure Krita -> Display -> Grid Settings -> Transparency Checkerboard), or to add a solid bright colour layer at the bottom of your layer stack and toggle the vibisility of that on and off for checking. And of course toggle visibility off for export. ;) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410807] Python Debugger throws exception when ran
https://bugs.kde.org/show_bug.cgi?id=410807 --- Comment #9 from Rebecca Breu --- "Do not open an SQLite database connection, then fork(), then try to use that database connection in the child process. All kinds of locking problems will result and you can easily end up with a corrupt database." https://www.sqlite.org/howtocorrupt.html#_carrying_an_open_database_connection_across_a_fork_ When does Krita try to access the DB? Can it potentially happen from within a Python script? What about threading? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420159] Advanced Colour Selector has a very slow response to dragging
https://bugs.kde.org/show_bug.cgi?id=420159 Rebecca Breu changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||rebe...@rbreu.de Ever confirmed|0 |1 --- Comment #1 from Rebecca Breu --- I can confirm this with a current master build in docker. It's fine with the 4.2.9 appimage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410807] Python Debugger throws exception when ran
https://bugs.kde.org/show_bug.cgi?id=410807 --- Comment #8 from Rebecca Breu --- Note to self: Try if spawning subprocesses actually still works on Linux, or whether we run into the same sqlite db access issues as https://bugs.kde.org/show_bug.cgi?id=420078 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410807] Python Debugger throws exception when ran
https://bugs.kde.org/show_bug.cgi?id=410807 --- Comment #7 from Rebecca Breu --- Unfortunately, this is a very tricky issue. The debugger wants to spawn a subprocess for debugging the script. On Linux and (I assume) MacOS, this works by forking the current process. On Windows, there's no way to fork/clone the current process, so as a workaround, Python's multiprocessing library starts a new process from scratch and gives it the parent process's argv to provide such things as the Python executable, Python script etc. However, since we are running an embedded Python, the parent process has no argv and trying to access that attribute fails with the error posted by the bug reporter. It's possible to set argv manually before spawning the subprocess, but that way, we could only provide a system Python executable (if it even exists), not Krita's embedded Python since that's not an executable. See for example here: https://stackoverflow.com/questions/15636266/embedded-python-multiprocessing-not-working Here's the same issue with a user script in Blender: https://blender.stackexchange.com/questions/8530/how-to-get-python-multiprocessing-module-working-on-windows The only fix that I can think of is rewriting the debugger to use threads instead of subprocesses, but that could potentially cause other issues, like thread-safety and issues with Python's GIL. Not sure if Blender has a debugger like this—might be worth looking into? If we can't solve it, we could at least deactivate the debugger on Windows, or catch the error with a meaningful popup for the user. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419976] c)_Pencil-3_Large_4B brush glitches on second picture
https://bugs.kde.org/show_bug.cgi?id=419976 --- Comment #3 from Rebecca Breu --- On second thought, I'm not so sure about the chalk brushes anymore, or my ability to press down on the tablet at equal pressure. Fact is that the "Accessing uninitialized random source!" message only happens for a couple of brushes (I found a couple of pencils in addition to the 4b pencil) and it's not happening for the chalk brushes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419976] c)_Pencil-3_Large_4B brush glitches on second picture
https://bugs.kde.org/show_bug.cgi?id=419976 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #2 from Rebecca Breu --- Ah, boud replied already while I was typing. Still, here are my observations: What a weird bug, but I can confirm it on the 4.2.9 and 4.1.7 appimages on Debian. I was trying a couple of other brushes as well: The "h) Chalk Grainy" and "h) Chalk Soft" seem to have it as well — I can't paint as lightly on the second image as I can on the first one — and more brushes might be affected as well, but it's hard to tell with some of them. It happens regardless of whether I have "Temporarily Save Tweaks to Presets" enabled or not, or if the images are displayed in windowed or tabbed mode, or whether I keep the first image open or not before I create the second one. From the second image onward that I create, I have the darker pencil. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419758] Using transform tool on a vector layer causes the layer to appear invisible.
https://bugs.kde.org/show_bug.cgi?id=419758 --- Comment #3 from Rebecca Breu --- Huh, I get it all the time with the 4.2.9 appimage and the recent master build in docker, no matter what I try. I'm attaching my system info in case that helps (this one is for the master/docker build). Krita Version: 5.0.0-prealpha (git 90d05a3) Languages: en_US, en, en_US, en Hidpi: false Qt Version (compiled): 5.12.7 Version (loaded): 5.12.7 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.9.0-11-amd64 Pretty Productname: Ubuntu 16.04.6 LTS Product Type: ubuntu Product Version: 16.04 Desktop: OpenGL Info Vendor: "Intel Open Source Technology Center" Renderer: "Mesa DRI Intel(R) HD Graphics 630 (Kaby Lake GT2) " Version: "3.0 Mesa 18.0.5" Shading language: "1.30" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 15796 Mb Number of Cores: 4 Swap Location: /tmp Current Settings Current Swap Location: /tmp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 30 Use OpenGL: true Use OpenGL Texture Buffer: true Use AMD Vectorization Workaround: false Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 1 Screen: 0 Name: eDP-1 Depth: 24 Scale: 1 Resolution in pixels: 2560x1440 Manufacturer: AU Optronics Model: Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419758] Using transform tool on a vector layer causes the layer to appear invisible.
https://bugs.kde.org/show_bug.cgi?id=419758 Rebecca Breu changed: What|Removed |Added Ever confirmed|0 |1 CC||rebe...@rbreu.de Status|REPORTED|CONFIRMED --- Comment #1 from Rebecca Breu --- I can confirm this. It happens with all transform modes except the regular "Free" transform. After applying the transformation, the layer turns invisible without being marked invisible. You can turn visibility off and on again to get the layer back, though you will see that the transformation hasn't applied and the layer is back in its original state. Which of the other transformation modes can we expect to work on vector layers anyway? Maybe some of them need to be disabled? Playing some more with it, I also found the following: Once I've transformed a vector layer with the "Free" transform and applied it, and activate the transform tool again, I can't switch to the other transform modes because get a "can't transform on an empty layer" popup, even though the layer isn't empty and I can still use the "Free" transform. So if that's already an attempt to block some of the transform tools on vector layers, it's the wrong error message and should probably also disallow other transform modes from the start? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419769] i have save a short animation ; quitte krita and want i want to open my document i can't find it
https://bugs.kde.org/show_bug.cgi?id=419769 Rebecca Breu changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- In which folder did you save your work? Did you save it in a temporary folder, or an external drive that's now unplugged, or a network service that's now unavailable? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419587] The Popup Palette Shortcut also affects canvas context menu
https://bugs.kde.org/show_bug.cgi?id=419587 --- Comment #2 from Rebecca Breu --- OK. I guess I'll find another key to rebind it to that doesn't get in the way as much. "Open Popup Palette and Canvas Context Menu", maybe? People will be searching for Popup Palette since I don't think it's clear to a lot of people that it's a context menu, and "Canvas" should be in there because it doesn't affect context menues in other parts of the GUI. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419587] New: The Popup Palette Shortcut also affects canvas context menu
https://bugs.kde.org/show_bug.cgi?id=419587 Bug ID: 419587 Summary: The Popup Palette Shortcut also affects canvas context menu Product: krita Version: 4.2.9 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: rebe...@rbreu.de Target Milestone: --- This has been happening at least since 4.2.8, probably longer. I just didn't connect things until now. STEPS TO REPRODUCE 1. Observe how right-click on vector layer or with the reference image tool enabled gives you the vector context menu 2. Go to Settings -> Configure Krita -> Canvas Input Settings -> Show Popup Palette 3. There's an existing keyboard shortcut there. Edit "Mouse Button" to "Keyboard Shortcut" and leave "Input" at "None", then save the settings. 4. This will disable the popup palette on paint layers. However, it will also disable the right-click vector context menu. (Right-click context menus on other parts of the GUI than the canvas, e.g. in dockers, still work.) Code-wise I can see why this happens—I guess that the popup palette *is* the context menu on paint layers. However, the settings option lead me to believe the shortcut was only for the popup palette and that I could disable the popup palette and only the popup palette. Which is a feature I very much like to have. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391241] Esc key to exit selection
https://bugs.kde.org/show_bug.cgi?id=391241 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #3 from Rebecca Breu --- I agree. Esc is used to cancel ongoing actions, but when you have a selection the action is already done. The selection is a thing that exists in the undo stack and gets saved in the kra file. Shift + Ctrl + A for deselecting is a pretty common shortcut as well. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419379] Issues with screen dissapering when i load a new canvas.
https://bugs.kde.org/show_bug.cgi?id=419379 Rebecca Breu changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- Go to Settings -> Configure Krita -> Display -> Canvas Acceleration and there set the Renderer from OpenGL to Angle (or vice versa). Then restart Krita. Does that help? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419368] Line Tool: Lines jagged/wiggly on pixel layers
https://bugs.kde.org/show_bug.cgi?id=419368 Rebecca Breu changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419368] New: Line Tool: Lines jagged/wiggly on pixel layers
https://bugs.kde.org/show_bug.cgi?id=419368 Bug ID: 419368 Summary: Line Tool: Lines jagged/wiggly on pixel layers Product: krita Version: 4.2.9 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: rebe...@rbreu.de Target Milestone: --- Created attachment 127080 --> https://bugs.kde.org/attachment.cgi?id=127080=edit Wiggly lines in 4.2.9 SUMMARY When the straight line tool is used on a pixel layer, the lines aren't quite straight, but a little jagged/wiggly. STEPS TO REPRODUCE 1. Create a new image with a pixel layer 2. Select a thin line art brush 3. Select the line tool 4. Draw lines OBSERVED RESULT Lines are a little jagged / wiggly. See screenshots. EXPECTED RESULT Straight lines. This happens only with 4.2.9, not with 4.2.8. A user reported this on reddit first: https://www.reddit.com/r/krita/comments/fqnjnw/straight_line_tool_bug/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419368] Line Tool: Lines jagged/wiggly on pixel layers
https://bugs.kde.org/show_bug.cgi?id=419368 --- Comment #1 from Rebecca Breu --- Created attachment 127081 --> https://bugs.kde.org/attachment.cgi?id=127081=edit Straight lines in 4.2.8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414576] Zoom failure in 4.2.8 but not in 4.2.7.
https://bugs.kde.org/show_bug.cgi?id=414576 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #46 from Rebecca Breu --- (In reply to Ahab Greybeard from comment #7) > I seem to have fixed this for the appimages on my PC. > > In kritadisplayrc, I had the line OpenGLRenderer=none > > [I must have previously been turning Canvas Graphics Acceleration on and off > to test another bug I'd been looking at. I assume I'd forgotten that a > restart is needed to implement this. > Note that the advisory statement "needs restart" looks like it only applies > to the Preferred Renderer but it applies to any change in those settings.] > > Setting the kritadisplayrc line OpenGLRenderer to be 'auto' or 'desktop' > clears the problem for me. > > Can you go to Settings -> Configure Krita -> Display , make sure Canvas > Graphics Acceleration is ticked and then press OK then restart krita? > > This setting does not cause any zoom-lag problems for version 4.2.6 or > 4.2.7.1 appimages. It affects 4.2.8 and the Dec09 4.3.0 prealpha appimages. I just ran into this problem (Debian, appimage) — suddenly zooming was super laggy on both 4.2.8 and 4.2.9 when it never had been before. Looking in "Settings -> Configure Krita -> Display", it said the renderer was "Auto (OpenGL)", but looking at my kritadisplayrc, OpenGLRenderer was set no none. Editing the file as Ahab said fixed the problem. I have no idea what caused the issue all of a sudden since I've never touched the display settings. The only setting that I changed recently was to allow several instances of Krita, and for the first time ever I was running two intances of Krita at the same time, and that's when I noticed the issue. So *maybe* accessing configs concurrently screwed something up, but I haven't been able to reproduce it so far. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419189] Krita crashes when undo a clear Assistants
https://bugs.kde.org/show_bug.cgi?id=419189 Rebecca Breu changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- I can confirm this on 4.2.8, the 4.2.9 beta. My compiled master build gives me an assert: ASSERT (krita): "curAssistants.size() == assistants.size() + 1" in file /home/appimage/persistent/krita/plugins/assistants/Assistants/EditAssistantsCommand.cpp, line 62 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419121] Crash on selecting certain color profiles
https://bugs.kde.org/show_bug.cgi?id=419121 --- Comment #3 from Rebecca Breu --- Ah, it seems that colour profiles are system-wide, the same as fonts are. Apparently, AnimePalette is one that comes with PhotoShop. Could you get a backtrace for your crash? See here: https://docs.krita.org/en/reference_manual/dr_minw_debugger.html -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419121] Crash on selecting certain color profiles
https://bugs.kde.org/show_bug.cgi?id=419121 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- Huh, I neither have AnimePalette nor ColorMatch RGB. Where did you get them from? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419093] call to Node.mergeDown() exits krita
https://bugs.kde.org/show_bug.cgi?id=419093
Rebecca Breu changed:
What|Removed |Added
CC||rebe...@rbreu.de
Status|REPORTED|CONFIRMED
Ever confirmed|0 |1
--- Comment #2 from Rebecca Breu ---
I can confirm this. It's only happening with the current 4.3. master, not with
4.2.8 and 4.2.9 beta. I'm getting two safe asserts and a segfault:
SAFE ASSERT (krita): "!m_d->waitingOnImages.contains(image)" in file
/home/appimage/persistent/krita/libs/image/KisBusyWaitBroker.cpp, line 64
SAFE ASSERT (krita): "m_d->waitingOnImages.contains(image)" in file
/home/appimage/persistent/krita/libs/image/KisBusyWaitBroker.cpp, line 80
Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
Node::createNode (image=..., node=..., parent=parent@entry=0x0) at
/home/appimage/persistent/krita/libs/libkis/Node.cpp:87
87 if (node->inherits("KisGroupLayer")) {
(gdb) backtrace
#0 Node::createNode (image=..., node=..., parent=parent@entry=0x0) at
/home/appimage/persistent/krita/libs/libkis/Node.cpp:87
#1 0x7fffc4632bc7 in Node::mergeDown (this=0xe999090) at
/home/appimage/persistent/krita/libs/libkis/Node.cpp:608
#2 0x7fffbbd9fae3 in meth_Node_mergeDown (sipSelf=0x7fffb66650d0,
sipArgs=)
at
/home/appimage/appimage-workspace/krita-build/plugins/extensions/pykrita/sip/./krita/sipkritapart0.cpp:20073
#3 0x7fffc49016fa in cfunction_call_varargs (kwargs=,
args=0x7fffcc06d040, func=0x7fffb71d9b80)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Objects/call.c:757
#4 PyCFunction_Call (func=0x7fffb71d9b80, args=0x7fffcc06d040,
kwargs=)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Objects/call.c:772
#5 0x7fffc48ff311 in _PyObject_MakeTpCall (callable=0x7fffb71d9b80,
args=, nargs=, keywords=0x0)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Objects/call.c:159
#6 0x7fffc48d5827 in _PyObject_Vectorcall (kwnames=,
nargsf=, args=,
callable=)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Include/cpython/abstract.h:125
#7 call_function (kwnames=0x0, oparg=, pp_stack=, tstate=0x6cdc000)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Python/ceval.c:4987
#8 _PyEval_EvalFrameDefault (f=, throwflag=)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Python/ceval.c:3469
#9 0x7fffc49efeaa in _PyEval_EvalCodeWithName
(_co=_co@entry=0x7fffb6655240, globals=globals@entry=0x7fffb6634180,
locals=locals@entry=0x7fffb6634180, args=args@entry=0x0,
argcount=argcount@entry=0, kwnames=kwnames@entry=0x0, kwargs=0x0, kwcount=0,
kwstep=2, defs=0x0, defcount=0, kwdefs=0x0, closure=0x0, name=0x0,
qualname=0x0)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Python/ceval.c:4298
#10 0x7fffc49f005e in PyEval_EvalCodeEx (_co=_co@entry=0x7fffb6655240,
globals=globals@entry=0x7fffb6634180,
locals=locals@entry=0x7fffb6634180, args=args@entry=0x0,
argcount=argcount@entry=0, kws=kws@entry=0x0, kwcount=0, defs=0x0,
defcount=0, kwdefs=0x0, closure=0x0)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Python/ceval.c:4327
#11 0x7fffc49f008b in PyEval_EvalCode (co=co@entry=0x7fffb6655240,
globals=globals@entry=0x7fffb6634180,
locals=locals@entry=0x7fffb6634180)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Python/ceval.c:718
#12 0x7fffc49ecaa9 in builtin_exec_impl (module=,
locals=0x7fffb6634180, globals=0x7fffb6634180, source=0x7fffb6655240)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Python/bltinmodule.c:1033
#13 builtin_exec (module=, args=,
nargs=)
--Type for more, q to quit, c to continue without paging--
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Python/clinic/bltinmodule.c.h:396
#14 0x7fffc4949380 in cfunction_vectorcall_FASTCALL
(func=func@entry=0x7fffcc03c590, args=, nargsf=nargsf@entry=2,
kwnames=)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Objects/methodobject.c:421
#15 0x7fffc490125f in PyVectorcall_Call (callable=0x7fffcc03c590,
tuple=, kwargs=)
at
/home/appimage/appimage-workspace/deps-build/ext_python/ext_python-prefix/src/ext_python/Objects/call.c:199
#16 0x7fffc48d6308 in do_call_core (kwdict=0x7fffb6652e80,
callargs=0x7fffb6653640, func=0x7fffcc03c590, tstate=0x6cdc000)
at
/home/appimage/appimage-
[krita] [Bug 392343] Text editor's Font-Style droplist and Bold button are broken
https://bugs.kde.org/show_bug.cgi?id=392343 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #8 from Rebecca Breu --- Bold is already broken in 4.2.8, see 419081. (I can confirm that as well). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419081] Bold text doesn't work
https://bugs.kde.org/show_bug.cgi?id=419081 Rebecca Breu changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- Yes, this is a know issue. *** This bug has been marked as a duplicate of bug 392343 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392343] Text editor's Font-Style droplist and Bold button are broken
https://bugs.kde.org/show_bug.cgi?id=392343 Rebecca Breu changed: What|Removed |Added CC||danielpet...@outlook.com --- Comment #7 from Rebecca Breu --- *** Bug 419081 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418606] Local selection mask is not marked by the selection tool
https://bugs.kde.org/show_bug.cgi?id=418606 --- Comment #5 from Rebecca Breu --- The 4.2.9 beta just came out Monday. The plan is to have a two week testing period and release soon after. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418606] Local selection mask is not marked by the selection tool
https://bugs.kde.org/show_bug.cgi?id=418606 Rebecca Breu changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Rebecca Breu --- Testing further with the krita-4.2.9-beta1-8e62bc9-x86_64 appimage, the issue seems to be fixed, so I'm closing this bug. Ants work as expected there. Kirill, you can try this with the Krita Plus version from the download section of the krita.org website. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418606] Local selection mask is not marked by the selection tool
https://bugs.kde.org/show_bug.cgi?id=418606 Rebecca Breu changed: What|Removed |Added Ever confirmed|0 |1 CC||rebe...@rbreu.de Status|REPORTED|CONFIRMED --- Comment #1 from Rebecca Breu --- I can confirm this: you get no ants when you create a local selection mask that way and activate the selection mask. The selection mask works, however, even if you can't see its outline. Once you close the document and re-open it, the ants show up as they should. This reminds me of the first version of the "split to local selection masks" feature, which also had the issue of no ants showing up. My guess is that whatever confifu did to fix that should also work here? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418494] Document.exportImage doesn't export from the current state of the document
https://bugs.kde.org/show_bug.cgi?id=418494 Rebecca Breu changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Rebecca Breu --- Disregard what I said above—I got confused. I do in fact get the issue every time, and neither calling doc.waitForDone() nor time.sleep(3) before the export solves the problem, nor does disabling batch mode. So it doesn't seem to be a timing issue as far as I can tell. Saving and re-opening does seem to be the only "fix". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418494] Document.exportImage doesn't export from the current state of the document
https://bugs.kde.org/show_bug.cgi?id=418494 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- I have this problem intermittently. Does calling "doc.waitForDone()" before the export reliably save the issue? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418406] A Rotation Transform around the 'x' or 'y' axis (not 'z' axis) caused loss of off-canvas content
https://bugs.kde.org/show_bug.cgi?id=418406 Rebecca Breu changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||rebe...@rbreu.de --- Comment #2 from Rebecca Breu --- I can confirm this for both the 4.2.8 version and today's nightly appimage 4c27cab. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418343] Krita Contiguous Selection Tool Bug ( Inconsistent selected Lines )
https://bugs.kde.org/show_bug.cgi?id=418343 Rebecca Breu changed: What|Removed |Added Resolution|--- |DUPLICATE CC||rebe...@rbreu.de Status|REPORTED|RESOLVED --- Comment #1 from Rebecca Breu --- This will be fixed in the next release. You can already try it in the Krita Plus from the krita.org website. *** This bug has been marked as a duplicate of bug 414647 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414647] Grow / Shrink Selection only change the width of a selection
https://bugs.kde.org/show_bug.cgi?id=414647 Rebecca Breu changed: What|Removed |Added CC||ilovestrawberries2001@gmail ||.com --- Comment #6 from Rebecca Breu --- *** Bug 418343 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418147] GUI major problem
https://bugs.kde.org/show_bug.cgi?id=418147 Rebecca Breu changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418147] GUI major problem
https://bugs.kde.org/show_bug.cgi?id=418147 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #1 from Rebecca Breu --- Re-installing doesn't remove your configuration files. Can you try resetting your configuration and see if that helps? https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418089] Blend mode "Addition" replaced by "Normal" after save/load to Krita (`kra`) file.
https://bugs.kde.org/show_bug.cgi?id=418089 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Rebecca Breu --- I can confirm this with the 4.2.8 appimage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418071] Moving layers that has any area made with select>fill is slow to move with move tool
https://bugs.kde.org/show_bug.cgi?id=418071 Rebecca Breu changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- I can confirm this on the 4.2.8 appimage. If I look at the little layer previews, what seems to be happening is that the stored section of a layer with brush strokes on it is cropped down to the area that has actual paint on it, whereas the layer where I bucket filled a selection is the size of the whole image but with a lot of transparent space. There's something that recalculates stored area when I paint with a brush, but for some reason it won't do that if I started with a bucked filled selection — even if I add brush strokes afterwards. I can only make the stored section larger by painting outside of the canvas border. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418012] Can't align circles or any other objects
https://bugs.kde.org/show_bug.cgi?id=418012 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- Arrange only works for vector layers. Seems like you have a pixel layer. In the layers docker, next to the plus icon to create a new layer, there's a dropdown from where you can choose to create a new vector layer. Draw your circle on that and try again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417404] Zoom tool behaves unpredictably when free rotation is active
https://bugs.kde.org/show_bug.cgi?id=417404 Rebecca Breu changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||rebe...@rbreu.de Ever confirmed|0 |1 --- Comment #1 from Rebecca Breu --- I can confirm this with current master (f303fa7) as well. The zoom tool works fine on a non-rotated canvas, but acts weird once there's a rotation. I think the amount of zoom looks fine, but the offset is wrong. And yes, it's strange to have the zoom selection box rotate with the canvas instead of keeping in alignment with the screen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417305] Crash when try to edit fill layer
https://bugs.kde.org/show_bug.cgi?id=417305 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #2 from Rebecca Breu --- I can't reproduce it on Debian either, neither with my current docker build nor with the most recent appimage (both version c4ce32e). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416922] New: Full screen and canvas mode switching issues on secondary monitor
https://bugs.kde.org/show_bug.cgi?id=416922 Bug ID: 416922 Summary: Full screen and canvas mode switching issues on secondary monitor Product: krita Version: git master Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: rebe...@rbreu.de Target Milestone: --- This only happens when I have Krita open on my secondary monitor, and only with the current nightly appimage. The 4.2.8 appimage works fine on either monitor. STEPS TO REPRODUCE 1. Put Krita on your secondary monitor not in full screen mode 2. Create or open an image 3. Hit "tab" to switch to canvas only mode. Works fine! 4. Hit "tab" to switch out of canvas only mode. OBSERVED RESULT Krita now displays in full screen mode. Though when you open the "View" window, you see that Krita thinks it's not full screen (no ckeckmark next to Full Screen Mode). So when you click "Full Screen Mode", nothing seems to happen except that Krita sets the checkmark. Now you can click "Full Screen Mode" again to switch back to normal mode, and everything is fine again. I also noticed that on the nightly, Full Screen Mode doesn't quite cover the entire secondary screen, though Canvas Mode does. Again, with 4.2.8 it works on either monitor as it should. There's a different full screen issue in bug 416894 on Windows, which I can't reproduce, not sure if there's any relation. Krita Version: 4.3.0-prealpha (git 0657457) Languages: en_US, en Hidpi: false Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.9.0-9-amd64 Pretty Productname: Debian GNU/Linux 9 (stretch) Product Type: debian Product Version: 9 OpenGL Info Vendor: "Intel Open Source Technology Center" Renderer: "Mesa DRI Intel(R) Kabylake GT2 " Version: "3.0 Mesa 13.0.6" Shading language: "1.30" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 15796 Mb Number of Cores: 4 Swap Location: /tmp Current Settings Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 100 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 300 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 1 Use Zip64: 0 Display Information Number of screens: 2 Screen: 0 Name: eDP-1 Depth: 24 Scale: 1 Resolution in pixels: 2560x1440 Manufacturer: AU Optronics Model: Refresh Rate: 60 Screen: 1 Name: HDMI-1 Depth: 24 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: Eizo Nanao Corporation Model: EV2450- Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416894] krita full screen in wrong monitor
https://bugs.kde.org/show_bug.cgi?id=416894 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- I can't reproduce it on Debian, neither with the 4.2.8 appimage nor the recent nightly appimage. Might be a Windows-specific issue? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416627] New: Swap FG-BG-Colour icon missing in current master
https://bugs.kde.org/show_bug.cgi?id=416627 Bug ID: 416627 Summary: Swap FG-BG-Colour icon missing in current master Product: krita Version: git master Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: rebe...@rbreu.de Target Milestone: --- Created attachment 125311 --> https://bugs.kde.org/attachment.cgi?id=125311=edit Colour swap icon: difference in 4.2.8 and master In the current master (my build from just now or the nightly appimage 21fb8e2), the little arrow icon next to the foreground/background icons in the toolbar is missing. You can still click the area to swap colours. In the 4.2.8 appimage, the arrow icon is present. See attached image. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416431] The new mixer slider docker causes freeze of the entire system.
https://bugs.kde.org/show_bug.cgi?id=416431 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- On Linux I cannot reproduce it, neither in my docker build with current master (07888a2e90827605cbc46f25e2124f3b4b1cdb14), nor with the latest nightly appimage (21fb8e2). The Mixer Slider works fine. Docker build system info: Krita Version: 4.3.0-prealpha (git 07888a2) Languages: en_US, en, en_US, en Hidpi: false Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.9.0-9-amd64 Pretty Productname: Ubuntu 16.04.6 LTS Product Type: ubuntu Product Version: 16.04 OpenGL Info Vendor: "Intel Open Source Technology Center" Renderer: "Mesa DRI Intel(R) HD Graphics 630 (Kaby Lake GT2) " Version: "3.0 Mesa 18.0.5" Shading language: "1.30" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 15796 Mb Number of Cores: 4 Swap Location: /tmp Current Settings Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 30 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 0 Use Zip64: 0 Display Information Number of screens: 1 Screen: 0 Name: eDP-1 Depth: 24 Scale: 1 Resolution in pixels: 2560x1440 Manufacturer: AU Optronics Model: Refresh Rate: 60 Current Settings Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 30 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 0 Use Zip64: 0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416172] Rendering issues/crashes when opening files with vector layer
https://bugs.kde.org/show_bug.cgi?id=416172 --- Comment #12 from Rebecca Breu --- Created attachment 125123 --> https://bugs.kde.org/attachment.cgi?id=125123=edit kritadisplayrc that causes the issue -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416172] Rendering issues/crashes when opening files with vector layer
https://bugs.kde.org/show_bug.cgi?id=416172 --- Comment #11 from Rebecca Breu --- Created attachment 125122 --> https://bugs.kde.org/attachment.cgi?id=125122=edit kritarc that causes the issue -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416172] Rendering issues/crashes when opening files with vector layer
https://bugs.kde.org/show_bug.cgi?id=416172 --- Comment #10 from Rebecca Breu --- Could test with my current kritarc and kritadisplayrc from when I reported the bug. The rendering issue again is 100% reproducible. Copying the rc files over to my docker, I can now reproduce the rendering issue 100% with my current master docker build as well. The good news: the intermittent crashes I get with the 4.2.8 appimage with those rc files, I couldn't reproduce with the nightly appimage nor the docker build at all despite A LOT of tries. That seems to be fixed. I'm going to attach the rc files. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416172] Rendering issues/crashes when opening files with vector layer
https://bugs.kde.org/show_bug.cgi?id=416172 --- Comment #8 from Rebecca Breu --- Ah, sorry, I cut off the copy At the end is the whole system info. Playing around with the settings, I found out: When I remove my kritarc and kritadisplayrc, the rendering issue almost doesn't occur at all. Out of at least 50 tries, probably more, I had it happen twice. (So maybe the Krita versions I listed in my initial report as "working" for me also just have this issue super rarely instead of not at all? I always loaded several times, but not THAT often.) Unfortunately, during testing I accidentally overwrote my config files as of yesterday, but with an older version, I get the rendering issue as well, but only sometimes. It can go well for 20 times or more, and then fail for 20 times. I can't find anything that influences it. This is the kritadisplayrc: [General] EnableHiDPI=false EnableSingleApplication=true LogUsage=true OpenGLRenderer=auto canvasState=OPENGL_SUCCESS rootSurfaceFormat=bt709-g22 And the according Current Settings: Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 100 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 300 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 1 Use Zip64: 0 Once I have access to my backup, I can retrieve the latest Krita configs. Not today though. - The complete system info with the settings used when I reported the bug: Krita Version: 4.2.8 Languages: en_US Hidpi: false Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.9.0-9-amd64 Pretty Productname: Debian GNU/Linux 9 (stretch) Product Type: debian Product Version: 9 OpenGL Info Vendor: "Intel Open Source Technology Center" Renderer: "Mesa DRI Intel(R) Kabylake GT2 " Version: "3.0 Mesa 13.0.6" Shading language: "1.30" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 15796 Mb Number of Cores: 4 Swap Location: /tmp Current Settings Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 100 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 300 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 1 Use Zip64: 0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416172] Rendering issues/crashes when opening files with vector layer
https://bugs.kde.org/show_bug.cgi?id=416172 --- Comment #5 from Rebecca Breu --- I just found out that it doesn't seem happen in the 4.1.7 appimage with the same file, so it seems to be a regression. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416172] Rendering issues/crashes when opening files with vector layer
https://bugs.kde.org/show_bug.cgi?id=416172 --- Comment #4 from Rebecca Breu --- Sorry, file was too big. Here is the Krita document which has the rendering issue for me: https://www.dropbox.com/s/aliupae079thuv8/test_bug_416172.kra?dl=0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416172] Rendering issues/crashes when opening files with vector layer
https://bugs.kde.org/show_bug.cgi?id=416172 --- Comment #3 from Rebecca Breu --- Created attachment 125063 --> https://bugs.kde.org/attachment.cgi?id=125063=edit How the image exports wrong -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416172] Rendering issues/crashes when opening files with vector layer
https://bugs.kde.org/show_bug.cgi?id=416172 --- Comment #2 from Rebecca Breu --- Created attachment 125062 --> https://bugs.kde.org/attachment.cgi?id=125062=edit How the image should look like -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416172] Rendering issues/crashes when opening files with vector layer
https://bugs.kde.org/show_bug.cgi?id=416172 --- Comment #1 from Rebecca Breu --- Created attachment 125061 --> https://bugs.kde.org/attachment.cgi?id=125061=edit Screenshot of rendering issue -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416172] New: Rendering issues/crashes when opening files with vector layer
https://bugs.kde.org/show_bug.cgi?id=416172 Bug ID: 416172 Summary: Rendering issues/crashes when opening files with vector layer Product: krita Version: 4.2.8 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: rebe...@rbreu.de Target Milestone: --- I'm not sure if it's maybe the same issue as https://bugs.kde.org/show_bug.cgi?id=404681 I can only reproduce this with the appimages (4.2.8 and the current nightly krita-4.3.0-prealpha-0a0738b). I can't reproduce it in a current docker build for some reason. It also only happens if the Krita document is of a certain size/complexity. With the attached file I can reproduce the rendering issues 100% on my machine, the crashes happen now and then. With smaller files the rendering issues happen sometimes, with very simple files not at all. test_exported_correctly.png shows what the image is supposed to look like: every "speech bubble" has a text inside and a rectangle around. test_opened_weird.png shows what I get when I open the file in Krita: lots of the vetor objects are invisible (but still selectable), some weird artefact shows up an the bottom half. test_exported_wrong.png shows what happens if I export it in that state—the vectors are still invisible but the artifact doesn't show up. I can "fix" the artifact by hiding/unhiding layers. The only way to "fix" the vectors is by grabbing them, knowing where they are supposed to be. Krita Version: 4.2.8 Languages: en_US Hidpi: false Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.9.0-9-amd64 Pretty Productname: Debian GNU/Linux 9 (stretch) Product Type: debian Product Version: 9 OpenGL Info Vendor: "Intel Open Source Technology Center" Renderer: "Mesa DRI Intel(R) Kabylake GT2 " Version: "3.0 Mesa 13.0.6" Shading language: "1.30" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415935] New: Colorize Mask: Cursor disappears when there's no colorize mask layer
https://bugs.kde.org/show_bug.cgi?id=415935 Bug ID: 415935 Summary: Colorize Mask: Cursor disappears when there's no colorize mask layer Product: krita Version: 4.2.8 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Colorize Assignee: krita-bugs-n...@kde.org Reporter: rebe...@rbreu.de Target Milestone: --- SUMMARY When activating the Colorize Mask Tool and there's no colorize mask layer yet, the cursor disappears while over the canvas. This happens in the 4.2.8 appimage and the current master built in docker. STEPS TO REPRODUCE 1. In a document that doesn't have a colorize mask yet, click on the colorize mask tool 2. Move your pointer over the canvas 3. No cursor 4. Press shift or alt 5. The "pointy finger"/"click" cursor appears as it should be from the start Switch to a different tool and back to the colorize mask, and the cursor will be gone again. Once you've created a colorize mask and the cursor is a brush, it will always appear correctly. Krita Version: 4.2.8 Languages: en_US Hidpi: false Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.9.0-9-amd64 Pretty Productname: Debian GNU/Linux 9 (stretch) Product Type: debian Product Version: 9 OpenGL Info Vendor: "Intel Open Source Technology Center" Renderer: "Mesa DRI Intel(R) Kabylake GT2 " Version: "3.0 Mesa 13.0.6" Shading language: "1.30" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 15796 Mb Number of Cores: 4 Swap Location: /tmp Current Settings Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 100 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 300 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 1 Use Zip64: 0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410871] Reorder Touch Docker (simple!)
https://bugs.kde.org/show_bug.cgi?id=410871 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- This is a Junior Job -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415794] Krita crashes when opening a file 3 times without krita already open
https://bugs.kde.org/show_bug.cgi?id=415794 Rebecca Breu changed: What|Removed |Added Ever confirmed|0 |1 CC||rebe...@rbreu.de Status|REPORTED|CONFIRMED --- Comment #2 from Rebecca Breu --- I can confirm this with the 4.2.8 appimage. I can reproduce it in command line by typing krita-4.2.8-x86_64.appimage & krita-4.2.8-x86_64.appimage Results in a segfault. I guess it would also happen if you put an icon to Krita on the desktop, and maybe more often on a slow system where Krita takes a while to start up and you get impatient and click again... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415747] Phantom off-canvas content with vector objects
https://bugs.kde.org/show_bug.cgi?id=415747 --- Comment #2 from Rebecca Breu --- Created attachment 124815 --> https://bugs.kde.org/attachment.cgi?id=124815=edit Screenshots of moving and trimming -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415747] Phantom off-canvas content with vector objects
https://bugs.kde.org/show_bug.cgi?id=415747 Rebecca Breu changed: What|Removed |Added Ever confirmed|0 |1 CC||rebe...@rbreu.de Status|REPORTED|CONFIRMED --- Comment #1 from Rebecca Breu --- I can confirm this. I also noticed: 1. Undoing the move operation doesn't remove the artifacts 2. When I initially move one object outside the canvas, it only gets shown partly in the preview, and trimming the image to the layer at that stage only includes that part of my object too. After this trimming, my preview has this image duplicated, and trimming again (without doing anything else in between) makes the image bigger again in accordance with the preview but without any new content showing up. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415695] 403 Forbidden when trying to download krita-appimage-deps.tar
https://bugs.kde.org/show_bug.cgi?id=415695 Rebecca Breu changed: What|Removed |Added CC||rebe...@rbreu.de --- Comment #1 from Rebecca Breu --- There's a workaround for this so that you continue—edit the URL in bootstrap-deps.sh to this one: https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Dependency_Build/69/artifact/krita-appimage-deps.tar -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415669] Vanishing Point assistant, angle density slider has not-working up/down controls.
https://bugs.kde.org/show_bug.cgi?id=415669 Rebecca Breu changed: What|Removed |Added Ever confirmed|0 |1 CC||rebe...@rbreu.de Status|REPORTED|CONFIRMED --- Comment #1 from Rebecca Breu --- I can confirm this, both that the arrows aren't working on the angle input, and that the cursor stays in slider mode over the arrows for both angle and opacity input. The arrow buttons should work, but also, the cursor should change back to regular over the arrows. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415651] New: Multi-brush tool: Copy Translate "Add" button should disable when I choose other type
https://bugs.kde.org/show_bug.cgi?id=415651 Bug ID: 415651 Summary: Multi-brush tool: Copy Translate "Add" button should disable when I choose other type Product: krita Version: 4.2.8 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: rebe...@rbreu.de Target Milestone: --- SUMMARY In the multi brush tool for the type "Copy Translate", the "Add" button should disable when I switch to other types. STEPS TO REPRODUCE 1. Enable the multi brush tool 2. Select the type "Copy Translate" in the tool options 3. Press the "Add" button in the tool options for adding brushes 4. Select a different type than "Copy Translate" 5. Try to draw OBSERVED RESULT Won't draw. That's because it's still in the "Add brush" mode that only the Copy Translate type has. You have to go back to "Copy Translate" and push the "Add" button again to be able to draw again in any other type. EXPECTED RESULT It's probably best if the "Add brush" mode gets disabled as soon as I choose another type. I'm on the 4.2.8 appimage. -- You are receiving this mail because: You are watching all bug changes.
