[krita] [Bug 491276] New: Instant Preview Artifacting and Stuck On In Parts of Canvas After Zooming
https://bugs.kde.org/show_bug.cgi?id=491276 Bug ID: 491276 Summary: Instant Preview Artifacting and Stuck On In Parts of Canvas After Zooming Classification: Applications Product: krita Version: 5.2.3 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Instant Preview Assignee: krita-bugs-n...@kde.org Reporter: michel.r.berge...@gmail.com Target Milestone: --- Created attachment 172282 --> https://bugs.kde.org/attachment.cgi?id=172282&action=edit instant preview canvas glitch after move SUMMARY On a large canvas, tools that use Instant Preview cause artifacting and glitchy canvas rendering when returning to a non-Instant Preview state, after the zoom level has changed significantly during the operation, and the tool/operation is not "properly" committed/ended. It's most noticeable near bottom of canvas, but applies elsewhere too. STEPS TO REPRODUCE 1. Ensure "Force Instant Preview for Move Tool" is enabled under Configure Krita > Performance > Instant Preview. 2. Create a larger document: A3 300ppi (3508 x 4960). 3. Zoom out so the canvas is small (< 10%). 4. Fill the background color with a light grey. 5. Make a new Paint Layer and draw some black squiggles along the bottom edge of the canvas. 6. Make another new Paint Layer and draw a horizontal line in the center of the canvas, crossing the whole width. The line is better off not perfectly straight -- use a regular brush. 7. Select the Move tool on the horizontal line's layer. 8. Click and drag to move the layer towards the bottom of the canvas, then back up to the center near where it was originally. **This is necessary.** 9. A green box should appear around the layer to signify the Move tool is still active. 10. Zoom in towards the bottom of the canvas (>40%). Notice that Paint Layer 1 (squiggles) appears very fuzzy from the Instant Preview, and a white line is showing along the entire bottom edge of the canvas (despite the background being grey). **Sometimes the white line shows up on the side of the canvas instead. I don't make the rules...** 11. Without pressing Enter or Escape, either: 11a. Select another tool (e.g. brush tool); or 11b. Select another Paint Layer. OBSERVED RESULT The area around the bottom of the canvas (where the horizontal line was moved to, then moved away from) will be stuck in a low-detail Instant Preview state, while only the area near where the horizontal line layer was moved back to will be reverted back to normal. The bottom of the canvas will remain this way until something happens to update it. Drawing a line will only fix the area immediately around the brushstroke. The solution seems to be to toggle the background layer(s). EXPECTED RESULT The entire canvas should be reset back to a fully-rendered, not Instant-Preview state. SOFTWARE/OS VERSIONS Windows: 10 & 11 Linux/KDE Plasma: Linux Mint 21.3 Cinnamon Krita: 5.2.2 & 5.2.3 (Windows installer, Linux AppImage) ADDITIONAL INFORMATION I've attached a gallery of screenshots showing what it looks like. I've tested and observed this behavior on multiple computers (desktop/laptop), between multiple OS' (Windows/Linux), dedicated/integrated graphics, drawing tablet/mouse/trackpad, and every Krita 5.2.x build I've tried. This happens on new installs of Krita, as well as on my main system. It seems mostly related to the Move Tool and the Transform Tool, so long as Force Instant Preview is toggled on for that tool; the regular Instant Preview Mode (View > Instant Preview Mode) being toggled on/off during normal use seems irrelevant. This might be related to bug 480973 but I think that one might be specific to the Transform Tool and its "Preview" mode Tool Options. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 491264] New: Initial kritarc File Incomplete and Sets Wrong Defaults For New (and possibly upgrading) Users
https://bugs.kde.org/show_bug.cgi?id=491264 Bug ID: 491264 Summary: Initial kritarc File Incomplete and Sets Wrong Defaults For New (and possibly upgrading) Users Classification: Applications Product: krita Version: 5.2.3 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: michel.r.berge...@gmail.com Target Milestone: --- Created attachment 172273 --> https://bugs.kde.org/attachment.cgi?id=172273&action=edit kritarc file diff - after opening Settings window SUMMARY On new installations of Krita 5.2.x, the kritarc file generated is missing config entries, leading to incorrect defaults. It's most apparent on brand new deployments, but somehow occurred for me when upgrading from 5.2.2 to 5.2.3 on Windows 11 as well. Opening the Configure Krita window & clicking OK (without changing any settings) results in missing default flags being added to the kritarc file. Clicking Cancel does nothing as expected. Exacerbating this, it seems like some tools' default behaviors (if the config flag is not present in kritarc) are different from the intended defaults as shown to the user in Configure Krita. This leads to some settings behaving differently for brand new users vs those who've gone in and played around with unrelated options. Most noticeably, on a brand new installation of Krita, Force Instant Preview is toggled on for the Move tool; but after clicking OK (without changing any settings), it is toggled off. "Off" is clearly the intended default, as that's what is shown to the user when they check that setting. This behavior was observed in Windows 10, Windows 11, as well as the Linux AppImage. STEPS TO REPRODUCE 1. Delete or move the kritarc file. Optionally you can delete/move the ~/.local/share/krita folder to simulate a new install. 2. Open Krita. 3. Make a new large document where you can observe Instant Preview in action: 3a. Create an A3 300ppi document (3508 x 4960) 3b. Draw something on a new layer 3c. Zoom out to about 10% 3d. Select the Move tool, and begin moving the layer (a green box will appear) 3e. Zoom in (50+%) while the tool is still active, and notice that the preview quality is extremely low while Instant Preview is active for the Move Tool 4. Cancel the Move operation by pressing Esc (the layer should return to normal quality) 5. Open Settings > Configure Krita 6. Click OK without doing or changing anything 7. Retry the Move tool from step 3 and notice that Instant Preview is no longer active for the Move tool OBSERVED RESULT Before clicking OK in the Configure Krita window, Force Instant Preview is enabled for the Move tool, despite the default selection in Performance > Instant Preview > Force Instant Preview for Move Tool being unchecked. EXPECTED RESULT Force Instant Preview should be off for the Move tool, unless a user explicitly toggles it on. Opening and confirming the Settings window, without changing any settings, should not result in any changed settings. SOFTWARE/OS VERSIONS Windows: 10 and 11 Linux/KDE Plasma: Linux Mint 21.3 Cinnamon ADDITIONAL INFORMATION I attached a full diff of my kritarc file from testing on Linux (easier). The "before" is from opening Krita for the first time, where all I did was create and save a document (simulating a new user). The "after" represents me opening the Configure Krita window and immediately clicking OK to close it. Doing this adds a lot of entries to the file, and changes some tools' behaviors. I was not able to reproduce the 5.2.2 > 5.2.3 upgrade re-enabling the Force Instant Preview for Move Tool issue on Linux, but upgrading about a month ago on Windows 11 is what led me down this rabbit hole in the first place. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 flash changed: What|Removed |Added CC||devesh.genius...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459087] New: The default panel is slow and laggy under Wayland
https://bugs.kde.org/show_bug.cgi?id=459087 Bug ID: 459087 Summary: The default panel is slow and laggy under Wayland Product: plasmashell Version: 5.25.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: devesh.genius...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Switch virtual desktops 2. Click on hidden systray icon 3. Click on launcher OBSERVED RESULT 1. Notice that the panel takes longer time to update itself to show the running and closed apps 2. It takes longer for the blue "line" above the systray icon to come and go 3. It takes longer for the blue "line" above the launcher icon to come and go EXPECTED RESULT 1. It should reflect the changes faster SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456211] New: Plasma crashing while opening application menu in Wayland
https://bugs.kde.org/show_bug.cgi?id=456211 Bug ID: 456211 Summary: Plasma crashing while opening application menu in Wayland Product: plasmashell Version: 5.24.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: devesh.genius...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.5) Qt Version: 5.15.3 Frameworks Version: 5.95.0 Operating System: Linux 5.15.0-39-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 22.04 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was making some recordings in audacity and doing nothing more I use Kubuntu The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fa1a730ea66 in QQuickItemPrivate::itemToWindowTransform() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fa1a730ec29 in QQuickItemPrivate::windowToItemTransform() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fa1a731246d in QQuickItem::mapFromScene(QPointF const&) const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fa1a738c821 in QQuickMouseArea::mouseMoveEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fa1a731ebd8 in QQuickItem::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fa1a65ba713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7fa1a58c0e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fa1a733cf75 in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7fa1a733e65f in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7fa1a5cb55a5 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7fa1a65ba713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fa1a58c0e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fa1a5ca9307 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7fa1a5c7ea2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #18 0x7fa1a3892174 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #19 0x7fa1a3c8ed1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fa1a3ce36f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fa1a3c8c3c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fa1a591a0a8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fa1a58bf74b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fa1a58c7ce4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x555bb5c04dce in ?? () #26 0x7fa1a51dcd90 in __libc_start_call_main (main=main@entry=0x555bb5c03f70, argc=argc@entry=1, argv=argv@entry=0x7ffe242f7028) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7fa1a51dce40 in __libc_start_main_impl (main=0x555bb5c03f70, argc=1, argv=0x7ffe242f7028, init=, fini=, rtld_fini=, stack_end=0x7ffe242f7018) at ../csu/libc-start.c:392 #28 0x555bb5c04ef5 in ?? () [Inferior 1 (process 1690) detached] Possible duplicates by query: bug 450215, bug 391926, bug 376941, bug 371272, bug 334870. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
