Trying to edit something and using the Move Tool to move something around, but it's slow at updating, and then it fails to autosave because it's stuck trying to update. It gives me popup saying unable to save. I've tried giving Krita more memory but it still acts so slow for updating. I increased its memory limit to 80% and increased the other memory settings accordingly too, but it's still not enough to make it update fast enough. Reproducible: Always Steps to Reproduce: 1. Increase pool memory to max allowed. 2. create something and use the move tool, text, or imported image layer 3. try scale and move the object around. Actual Results: it lags, hangs in place and doesn't properly update fast enough. Expected Results: expected results is that the scaled image or text should be able to move around fluidly without lagging or hanging in place with slow updates. OS: Linux Mint 18 (Cinnamon) 64-bit Memory: 8GB Graphics: Intel HD Graphics 4000 + Nvidia GeForce GT 630M
I'm sorry, but generic "it's too slow" reports are not very helpful for us. But more importantly, Krita 2.9.7 as shipped by Ubuntu and Mint is very old, and we've been working really hard to improve performance since then. Please update to the lates version (3.0.1.1) or the latest beta (3.0.91). You can use either the snap image or the appimage: we no longer manage to provide a ppa as well.
(In reply to Boudewijn Rempt from comment #1) > I'm sorry, but generic "it's too slow" reports are not very helpful for us. > But more importantly, Krita 2.9.7 as shipped by Ubuntu and Mint is very old, > and we've been working really hard to improve performance since then. Please > update to the lates version (3.0.1.1) or the latest beta (3.0.91). You can > use either the snap image or the appimage: we no longer manage to provide a > ppa as well. I'd grab a log file of what's going on if I knew where to find the log file. I turned on debugger logging and I can't find it.
Please do not change the status of bug reports: the bug tracker is a tool for developers to work with. We decide the status of a bug report. You reported this bug for 2.9.7 which is an old and unmaintained version of Krita. We do not accept reports for that version anymore. Please use the most recent version and if you find a specific issue, report it. "Doesn't update fast enough" is not a bug report.
(In reply to Boudewijn Rempt from comment #3) > Please do not change the status of bug reports: the bug tracker is a tool > for developers to work with. We decide the status of a bug report. > > You reported this bug for 2.9.7 which is an old and unmaintained version of > Krita. We do not accept reports for that version anymore. Please use the > most recent version and if you find a specific issue, report it. "Doesn't > update fast enough" is not a bug report. This is rather pathetic… old version or not, it's still a bug to me, I could still provide more details if I could find the log files. This still remains unresolved for me regardless.
I don't know what you mean with "the log files". Krita doesn't write log files. And if it did, I wouldn't want to see them because 2.9.7 is no longer being maintained. We can't help it that your distribution cannot keep up with us, after 2.9.7 we released 2.9.8, 2.9.9, 2.9.10 and 2.9.11. You issues might have been fixed in any of those releases. Or they might have been fixed in 3.0.0, 3.0.1 or 3.0.1.1. And the reason we release new versions is because we fix bugs; and that's the reason you should upgrade to a new version. That's not pathetic, that's normal.