SUMMARY Krita version 4.3.1-alpha (git 90110be), however this has been occurring for me since the base 4.3 update at least, that I've noticed. When I have more than one canvas open at a time, if I close the canvas that I am currently viewing, the program will automatically have me view another open canvas. This part is normal. However, if I attempt to interact with the canvas in any way, instead of displaying the changes I make to the image, it will tile the brush cursor, or any objects I attempt to paste and transform. I can still interact with the canvas by drawing or editing layers, but I cannot see what I have done, and it does not save changes post-error. I am also still able to save the canvas, close and open it and other files, and switch to other canvases. Switching canvases also happens to make the error stop. The error does not occur if I close a canvas tab that I am not currently viewing. STEPS TO REPRODUCE 1. Have more than one canvas open 2. Close the canvas that you are currently viewing 3. Attempt to draw on or otherwise interact with your canvas OBSERVED RESULT If you attempt to draw on the canvas, the brush cursor will tile and trail instead of displaying any changes to the file. If you attempt to paste an image from your clipboard it will appear on a new layer as normal, and attempting to transform it will create a similar tiling/traling effect. EXPECTED RESULT I'm not entirely sure what this section means, but if it's referring to what SHOULD be occurring when I input the actions, I should simply be able to view and continue working on the newly displayed canvas. Pardon me if how I've filled this section in is not useful; I've never submitted a bug report before. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I have not attempted this on another system or OS, so I want to apologize if this is somehow an individual issue. My current canvas display settings under the Display > Canvas Acceleration tab is set to enable canvas graphics acceleration, with the current renderer set as Direct3D 11 via ANGLE, with high quality filtering and texture buffer enabled.
I cannot reproduce it on an appimage on Linux Mint with Cinnamon. @yggdrasilincar can you please check if it happens also with (1) OpenGL instead of ANGLE, and (2) disabled Canvas Graphics Acceleration? Also to make it easier for other people triaging this issue: do I understand correctly that Krita 4.3.0 has the same issue? Please also attach the output from Help -> Show system information for bug reports. > I've never submitted a bug report before. You did quite well for the first time :) And that section meant exactly what you thought. Thanks for submitting.
Created attachment 130445 [details] attachment-17232-0.html Here's the output info from the settings I had when I first noticed the bug: Krita Version: 4.3.1-alpha (git 90110be) Languages: en_GB, en, en_US, en Hidpi: true Qt Version (compiled): 5.12.8 Version (loaded): 5.12.8 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19041 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (AMD Radeon HD 8670D 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<QSurfaceFormat::FormatOption>(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<QSurfaceFormat::FormatOption>(), 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 QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true Hardware Information GPU Acceleration: auto Memory: 7368 Mb Number of Cores: 4 Swap Location: C:/Users/parafinch2/AppData/Local/Temp Current Settings Current Swap Location: C:/Users/parafinch2/AppData/Local/Temp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 150 Use OpenGL: true Use OpenGL Texture Buffer: true Use AMD Vectorization Workaround: false Canvas State: OPENGL_SUCCESS Autosave Interval: 300 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: \\.\DISPLAY1 Depth: 32 Scale: 1 Resolution in pixels: 1600x900 Manufacturer: Model: Refresh Rate: 60 It *was* indeed happening in the base update of 4.3.0 , that's why I switched to the nightly versions to see if perhaps that would help. With graphics acceleration the bug doesn't occur, however it does have a similar result with OpenGL. The only difference in that case is the canvas does not show the tiling issue with the cursor, however I still can't interact with the canvas. I should also note that attempting to pan with the overview navigator doesn't work either. Apologies, I forgot to mention that part in the original report. On Mon, Jul 27, 2020 at 11:56 AM Tymond <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=424665 > > Tymond <tamtamy.tymona@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC| |tamtamy.tymona@gmail.com > > --- Comment #1 from Tymond <tamtamy.tymona@gmail.com> --- > I cannot reproduce it on an appimage on Linux Mint with Cinnamon. > > @yggdrasilincar can you please check if it happens also with (1) OpenGL > instead > of ANGLE, and (2) disabled Canvas Graphics Acceleration? Also to make it > easier > for other people triaging this issue: do I understand correctly that Krita > 4.3.0 has the same issue? > > Please also attach the output from Help -> Show system information for bug > reports. > > > I've never submitted a bug report before. > > You did quite well for the first time :) And that section meant exactly > what > you thought. Thanks for submitting. > > -- > You are receiving this mail because: > You reported the bug.
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
Can you please download and check Krita Next from the website? It's possible that it was fixed in https://invent.kde.org/graphics/krita/-/commit/e02b5afcb26af7cf6b136c0f6859fdc192ada4d4
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Created attachment 131098 [details] attachment-11296-0.html Oh dear, please pardon the very late response! I only just now saw the emails in my inbox, entirely my bad. I downloaded the most recent version of Krita Next, 5.0.0-prealpha (git 3ad4d2e), and the issue seems to be resolved now. Thank you for your time, and again I'm so sorry for taking like 2 weeks to respond. I appreciate all your help! On Wed, Aug 19, 2020 at 12:33 AM Bug Janitor Service < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=424665 > > --- Comment #5 from Bug Janitor Service <bug-janitor@kde.org> --- > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! > > -- > You are receiving this mail because: > You reported the bug.