SUMMARY *** Occasionally I will get all of these bugs at once, and it lasts for a random amount of time (what I mean is, the bugs are persistent throughout restarts). Then it just goes away for some reason before coming back randomly. These bugs are: 1: The UNDO function will refuse to work until the tablet pen is far away from my tablet. The pen is not touching, just about 1 inch above it. 2: The UNDOs become cumulative, UNDOing anywhere from 3 - 12 brushstrokes at once, even though **cumulative undo is not activated, NOT activated**. 3: The REDO function also randomly no longer remembers anything I have UNDOne, and refuses to re-apply strokes I have previously UNDOne. All three of these bugs always **and only** appear altogether at once, and persist through restarts, before randomly disappearing after an unknown amount of time. *** STEPS TO REPRODUCE I have not correlated the bugs to anything yet; no Windows updates, no Java updates. Whatever it is, UNDO/REDO just works one day, then not the next, regardless of any changes to my system. SOFTWARE/OS VERSIONS Windows: 10
Why would you think java updates make any difference... Please provide the contents of help->system information for bug reports and help->krita log for bug reports. Also, tell us about the make and type of your tablet, and whether you have the latest version installed.
(In reply to Halla Rempt from comment #1) The bugs are gone again now for some reason, I'll see if I can spot any causes next time it comes back :o > Why would you think java updates make any difference... No idea, I was looking for any possible correlation. > Also, tell us about the make and type of your tablet, and whether you have the latest version installed. Wacom Intuos S CTL-4100/K0-CX. Version 6.3.41-1 (Latest version). > Please provide the contents of help system information for bug reports and help krita log for bug reports. Hmm, I'm not sure what this is referring to, if the information provided below is incorrect please let me know! OS Name Microsoft Windows 10 Home Version 10.0.19043 Build 19043 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name DESKTOP-828Q759 System Manufacturer Gigabyte Technology Co., Ltd. System Model B450M S2H V2 System Type x64-based PC System SKU Default string Processor AMD Ryzen 3 3100 4-Core Processor, 3593 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date American Megatrends Inc. F1, 8/28/2020 SMBIOS Version 3.2 Embedded Controller Version 255.255 BIOS Mode Legacy BaseBoard Manufacturer Gigabyte Technology Co., Ltd. BaseBoard Product B450M S2H V2 BaseBoard Version x.x Platform Role Desktop Secure Boot State Unsupported PCR7 Configuration Binding Not Possible Windows Directory C:\Windows System Directory C:\Windows\system32 Boot Device \Device\HarddiskVolume7 Locale United States Hardware Abstraction Layer Version = "10.0.19041.1741" User Name DESKTOP-828Q759\Markovich Time Zone China Standard Time Installed Physical Memory (RAM) 16.0 GB Total Physical Memory 15.9 GB Available Physical Memory 7.28 GB Total Virtual Memory 21.2 GB Available Virtual Memory 7.33 GB Page File Space 5.25 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware No Hyper-V - Data Execution Protection Yes Thanks for your time! This bug is only temporary and occasional, and if you haven't heard of such a problem before and/or have been unable to replicate such an issue, then please don't bother, it's probably something wonky on my end.
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.
If you go to the Help menu in Krita you will find two entries that provide different information that can be useful when investigating a bug. Please save that to files (or access the files directly from %APPDATA% in the file manager) and attach to this bug report.
In any case, if the problems are gone, I'll close the report :-)