[kdenlive] [Bug 434179] Kdenlive is missing translation for all its dialogues/sub-windows (Windows version only)
https://bugs.kde.org/show_bug.cgi?id=434179 --- Comment #29 from Tyson Tan --- I think this issue has been resolved by itself. All translations are showing under Windows. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422006] [Dolphin] Emptying trash does not trigger view refresh
https://bugs.kde.org/show_bug.cgi?id=422006 --- Comment #37 from Tyson Tan --- The bug hasn't been affecting me for quite some time now. I didn't change anything other than the regular system updates. Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488478] Restore Defaults in Canvas Input Settings defaults to Clip Studio Paint Compatible profile
https://bugs.kde.org/show_bug.cgi?id=488478 --- Comment #5 from Tyson Tan --- Thank you, Halla! :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488606] After Krita launches and you first open a file, the canvas will not show up until you rotate the screen orientation
https://bugs.kde.org/show_bug.cgi?id=488606 --- Comment #9 from Tyson Tan --- Thank you, Halla! :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 491962] Workflow Buttons Docker doesn't display a translated title/name
https://bugs.kde.org/show_bug.cgi?id=491962 --- Comment #3 from Tyson Tan --- Thank you, Freya! :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 491962] New: Workflow Buttons Docker doesn't display a translated title/name
https://bugs.kde.org/show_bug.cgi?id=491962 Bug ID: 491962 Summary: Workflow Buttons Docker doesn't display a translated title/name Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- Created attachment 172797 --> https://bugs.kde.org/attachment.cgi?id=172797&action=edit Workflow Buttons Docker doesn't display a translated title/name I have finished translating everything about the newly added Workflow Buttons docker. But the name in Main Menu -> Settings -> Dockers is still English, so is the title of the docker. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 490843] No layer is active after switching between views, except for the last opened view
https://bugs.kde.org/show_bug.cgi?id=490843 --- Comment #9 from Tyson Tan --- Thank you, Dmitry! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 490843] No layer is active after switching between views, except for the last opened view
https://bugs.kde.org/show_bug.cgi?id=490843 Tyson Tan changed: What|Removed |Added Summary|No layer is active after|No layer is active after |switching between views |switching between views, |with multiple layers, |except for the last opened |except for the last view|view -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 490843] No layer is active after switching between views with multiple layers, except for the last view
https://bugs.kde.org/show_bug.cgi?id=490843 --- Comment #4 from Tyson Tan --- When drag-and-dropping multiple single layer PNGs into Krita's window, the original report is still valid. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 490843] No layer is active after switching between views with multiple layers, except for the last view
https://bugs.kde.org/show_bug.cgi?id=490843 Tyson Tan changed: What|Removed |Added Summary|No layer is active when |No layer is active after |opening multiple images all |switching between views |at once, except for the |with multiple layers, |last one|except for the last view -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 490843] No layer is active when opening multiple images all at once, except for the last one
https://bugs.kde.org/show_bug.cgi?id=490843 --- Comment #3 from Tyson Tan --- I have done some more testing today, and there were new findings. This bug has nothing to do with "opening files". It happens when "switching between views that has multiple layers". Procedure to reproduce: 1) Open 2 images with multiple layers, let's call the first image A, and the last image B; 2) Switch to image A, select a layer; 3) Switch to image B, then back to A; Result: Image A now has no active layer. Expected result: Image A should retain its active layer. Exception: If Image A has only 1 layer, that layer will still be active after switching views. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 490843] No layer is active when opening multiple images all at once, except for the last one
https://bugs.kde.org/show_bug.cgi?id=490843 --- Comment #2 from Tyson Tan --- Also happens to Main Menu -> File -> Open dialogue with multiple files selected. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 490843] New: No layer is active when opening multiple images all at once, except for the last one
https://bugs.kde.org/show_bug.cgi?id=490843 Bug ID: 490843 Summary: No layer is active when opening multiple images all at once, except for the last one Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- When opening multiple images all at once, no layer is active except for the last image. The user can't do anything until they select one layer. Tested with latest nightlies. Noticed since 2024-07-25. Procedure to reproduce: 1) Prepare 2 images, let's call them A/B for now; 2) Drag these 2 images together into Krita's window; 3) Let's presume image A is opened first, and B opened last; Result: 1) Only Image B (the last one opened) has an active layer by default. 2) Switch to Image A -- it has no active layer -- and thus cannot be edited. Expected: Every image that opened together should have an active layer. I consider this a bug, because Krita would normally make sure one layer is active for us. This is an inconsistent and confusing behavior. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 490505] New: [Android] Unable to display canvas for the first document after a cold start, unless switching away from Krita for once
https://bugs.kde.org/show_bug.cgi?id=490505 Bug ID: 490505 Summary: [Android] Unable to display canvas for the first document after a cold start, unless switching away from Krita for once Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 14.x Status: REPORTED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- Somewhere after version 5.2.2, Krita Android became unable to display canvas after a cold start of the app. Opening an existing document or creating a new document for the first time after a cold start does nothing -- everything greys out after that. It can be solved by switching away from the Krita app -- by either going to the device's Home Screen or the Task Switcher. Tested on Samsung Galaxy Tab S8 with OneUI 5.1 (Android 14) using both 5.2.3 and the latest nightly APK (d9195f26b1, 2024-07-19). Multiple cases on different devices and older Android versions were reported to me by the local community. Procedure to reproduce: 1) Exit Krita from its File menu; 2) Cold start Krita; 3) Create a new document; 4) Nothing happens, Krita doesn't display its canvas, everything greys out; 5) Switch away from the Krita app to Home Screen of the device and then back to Krita; 6) Krita can now display its canvas; 7) Any later document behaves normally until exiting Krita; -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] Canvas shortcuts break when other application steals focus or holds down global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 Tyson Tan changed: What|Removed |Added CC||zimin2093354...@163.com --- Comment #19 from Tyson Tan --- *** Bug 470354 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470354] When Windows opens Krita and WeChat at the same time, Krita canvas zooming in and out, moving canvas and other canvas controls unable to use (Google translate,I don't speak Englis
https://bugs.kde.org/show_bug.cgi?id=470354 Tyson Tan changed: What|Removed |Added CC||tysont...@gmail.com Resolution|NOT A BUG |DUPLICATE --- Comment #2 from Tyson Tan --- *** This bug has been marked as a duplicate of bug 483687 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] Canvas shortcuts break when other application steals focus or holds down global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 Tyson Tan changed: What|Removed |Added Summary|[Windows] Canvas shortcuts |[Windows] Canvas shortcuts |break when other|break when other |applications try steal |application steals focus or |focus or listen to global |holds down global shortcuts |shortcuts | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462848] [Android] Touch Docker's File buttons open a white screen and lock up
https://bugs.kde.org/show_bug.cgi?id=462848 --- Comment #11 from Tyson Tan --- Hi Dmitry, Yes, I can confirm this bug has been fixed. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463118] [Android] Unable to close an opened main menu by clicking it again
https://bugs.kde.org/show_bug.cgi?id=463118 --- Comment #2 from Tyson Tan --- Hi Dmitry, This bug still exists. I'm now using Samsung Galaxy Tab S8 with OneUI 5.1 (Android 14). I have just tested with both 5.2.3 and the latest nightly APK. The behavior was the same as stated in the original report. In case you misunderstood what I meant, I can trigger this bug by doing the following: 1) In Krita's menu bar; 2) Click "File"; 3) The "File" menu opens; 4) Click "File" again; 5) The "File" menu closed for a split second, but it was re-opened immediately after; Workaround: 6) Click the empty space on the right side of Krita's main menu bar; 7) The "File" menu was able to close for good. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486322] Export document dialogue doesn't have the original file name in Filename input field
https://bugs.kde.org/show_bug.cgi?id=486322 Tyson Tan changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #5 from Tyson Tan --- Looks like the bug has been fixed for real in recent builds. Must be dependency related. Close this as fixed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488479] New: Quickly lifting the pen away from the screen while pressing down a pen button breaks touch gesture actions
https://bugs.kde.org/show_bug.cgi?id=488479 Bug ID: 488479 Summary: Quickly lifting the pen away from the screen while pressing down a pen button breaks touch gesture actions Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Tablets (tablet issues are only very rarely bugs in Krita!) Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- SUMMARY On a Pen Display or an Android tablet, lifting the pen away from the screen while pressing down a pen button breaks the screen's touch gesture actions. For example, if I pressed down Middle Button to pan the canvas, and accidentally moved my pen too high and the digitizer lost the pen input, I was unable to rotate the canvas with two-finger gestures afterward. STEPS TO REPRODUCE 1. On a Pen Display or an Android tablet 2. Press down Middle Mouse button to pan canvas 3. Quickly lift the pen up, away from the range of the screen's digitizer 4. Do not put the pen back in range 5. Use two finger gestures to rotate the canvas OBSERVED RESULT I could not use two finger gestures to rotate the canvas. EXPECTED RESULT I should be able to use two finger gestures to rotate the canvas. SOFTWARE/OS VERSIONS 5.2.3 beta 1 and the latest nightly versions. It seems that if I lifted my pen slowly away from the range, it's less likely to break the touch gestures. But I could not reliably reproduce the phenomenon. During my test, there was one occasion under Android which I lost the Middle Button input afterward. I wonder if this has something to do with the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437241] If Canvas Input Settings are 'Paint Tool Sai Compatible', there is loss of functionality
https://bugs.kde.org/show_bug.cgi?id=437241 Tyson Tan changed: What|Removed |Added CC||tysont...@gmail.com --- Comment #6 from Tyson Tan --- Created attachment 170489 --> https://bugs.kde.org/attachment.cgi?id=170489&action=edit Restore Defaults to CSP Compatible profile conflicts with existing actions Restore Defaults in Canvas Input Settings resets the Input Profile to Clip Studio Paint Compatible, which has been reported as bug 488478. And after restoring to defaults, the Clip Studio Paint Compatible profile immediately has a conflict in "Alternate Invocation" section, with: Ctrl + Left Button Alternate Invocation -> Primary Mode Alternate Invocation -> Sample Foreground Color From Current Layer It's not good when a default profile doesn't work out of the box. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488478] New: Restore Defaults in Canvas Input Settings defaults to Clip Studio Paint Compatible profile
https://bugs.kde.org/show_bug.cgi?id=488478 Bug ID: 488478 Summary: Restore Defaults in Canvas Input Settings defaults to Clip Studio Paint Compatible profile Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- In Canvas Input Settings, if I click the "Restore Defaults" button, it resets the Input Profile to "Clip Studio Paint Compatible". We should reset it to "Krita Default". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488477] New: Resets All Settings is broken
https://bugs.kde.org/show_bug.cgi?id=488477 Bug ID: 488477 Summary: Resets All Settings is broken Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- The "Reset All Settings" action in Main Menu > Settings seems to be broken. It doesn't seem to reset the Keyboard Shortcuts, Canvas Input Settings, Toolbars and such. Doesn't seem to do anything, really. This is causing difficulties when helping people to troubleshoot their Krita installs. Tested under Windows/Linux/Android 5.2.3 beta1 and the latest nightly versions. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488452] The "Edit" toolbar is hidden by default, which is causing confusion
https://bugs.kde.org/show_bug.cgi?id=488452 Tyson Tan changed: What|Removed |Added Summary|Edit toolbar is hidden by |The "Edit" toolbar is |default, which is causing |hidden by default, which is |confusion |causing confusion -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488452] New: Edit toolbar is hidden by default, which is causing confusion
https://bugs.kde.org/show_bug.cgi?id=488452 Bug ID: 488452 Summary: Edit toolbar is hidden by default, which is causing confusion Classification: Applications Product: krita Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- Krita has 3 toolbars. They are "File", "Edit", "Brushes and Stuff". The "Edit" toolbar is hidden by default. It holds two very frequently used actions: Undo & Redo. Because the toggling of toolbar visibility is hidden away in an obscure place, people often got confused by why the Undo/Redo buttons cannot be shown, even though "they have already been added to a toolbar". I, for one, got confused by this issue before. And today, a moderator of our local community also got confused, and they reported this to me as a "suspected bug". We both ran into this under the Android version, because we really needed those buttons on a touchscreen. Given how experienced we both were, and yet still fell for it, I think it's safe to assume more people would have been confused by this, as well. I suggest we show the "Edit" toolbar by default, and we should move it next to the "File" toolbar. I think that is where it is supposed to be. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442227] Liquify Transform's Mode buttons and options are arranged in a confusing way
https://bugs.kde.org/show_bug.cgi?id=442227 --- Comment #3 from Tyson Tan --- Created attachment 170468 --> https://bugs.kde.org/attachment.cgi?id=170468&action=edit Confusing Liquify Transform Modes Icons No, the screenshot you uploaded in Comment 1 is the options for Free Transformation. The options for Liquify Transformation today look exactly like what I reported back then. In this screenshot, I highlighted the issues. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487724] Krita.org PAGES.POT has multiple broken links, wrong dates, missing and duplicate items
https://bugs.kde.org/show_bug.cgi?id=487724 Tyson Tan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Tyson Tan --- Fixed: https://invent.kde.org/websites/krita-org/-/issues/22#note_958542 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487724] New: Krita.org PAGES.POT has multiple broken links, wrong dates, missing and duplicate items
https://bugs.kde.org/show_bug.cgi?id=487724 Bug ID: 487724 Summary: Krita.org PAGES.POT has multiple broken links, wrong dates, missing and duplicate items Classification: Applications Product: krita Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- Sorry for reporting website issues as Unknown component, because I could not find this project in bugs.kde.org under Krita. I've also file an issue on invent.kde.org, but I'm not sure that's the place for it: https://invent.kde.org/websites/krita-org/-/issues/22 All errors I've found for PAGES.POT: #: content/en/release-history.md:175 3.0.0: 31-05-2016, [release announcement](en/posts/2016/krita-3-0-released/), [release notes](en/krita-3-0-release-notes/) Missing page: (en/krita-3-0-release-notes/) #: content/en/release-history.md:179 3.1.2: 01-02-2017, [release announcement](en/posts/2017/krita-3-1-2-released/), [release notes](en/release-notes-for-3-1-2/) Missing page: (en/release-notes-for-3-1-2/) #: content/en/release-history.md:180 3.1.3: 01-05-2017, [release announcement](en/posts/2017/krita-3-1-3/), [release notes](en/release-notes-for-3-1-3/) Missing page: (en/release-notes-for-3-1-3/) #: content/en/release-history.md:182 3.2.0: 17-08-2017, [release announcement](en/posts/2017/krita-3-2-0-released/), [release notes](en/release-notes-for-krita-3-2/) Missing page: (en/release-notes-for-krita-3-2/) #: content/en/release-history.md:193 4.0.0: 22-03-2018, [release announcement](en/posts/2018/krita-4-0-0-released/), [release notes](en/krita-4-0-release-notes/), [dot.kde.org story](https://dot.kde.org/2018/03/22/5-things-look-forward-krita-40) Missing page: (en/krita-4-0-release-notes/) #: content/en/release-history.md:203 4.1.0: 27-06-2018, [release announcement](en/posts/2018/krita-4-1-0-released/), [release notes](en/posts/2018/krita-4-1-release-notes/), [dot story](https://dot.kde.org/2018/03/22/5-things-look-forward-krita-40). Missing page: (en/posts/2018/krita-4-1-release-notes/) #: content/en/release-history.md:214 4.2.0: 29-05-2019, [release announcement](en/posts/2019/krita-4-2-0-is-out/), [release notes](en/krita-4-2-release-notes/) Missing page: (en/krita-4-2-release-notes/) #: content/en/release-history.md:235 4.4.0: 13-10-2020, [release announcement](en/posts/2020/krita-4-4-0-released/), [release notes](en/posts/2020/krita-4-4-0-release-notes/) Missing page: (en/posts/2020/krita-4-4-0-release-notes/) #: content/en/release-history.md:237 4.4.2: 19-01-2021, [release announcement](https://invent.kde.org/graphics/krita/-/merge_requests/668): a sneaky feature release with mesh gradients, mesh transforms, more fill layer types and new brush presets. Wrong link: (https://invent.kde.org/graphics/krita/-/merge_requests/668) Correct link: (en/posts/2021/krita-4-4-2-released/) #: content/en/release-history.md:256 5.0.2: 13-06-2018, [release announcement](). There was no 5.0.1. Wrong date: 13-06-2018 Correct date: 2022-01-07 Missing link: (https://krita.org/en/posts/2022/krita-5-0-2/) #: content/en/release-history.md:257 5.0.5: 13-06-2018, [release announcement](https://krita.org/en/item/krita-5-0-5-released/). There no 5.0.3 and 5.0.4 releases. Wrong date: 13-06-2018 Correct date: 2022-04-14 #: content/en/release-history.md:260 5.0.5: 13-06-2018, [release announcement]() Duplicate of the previous entry. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486322] Export document dialogue doesn't have the original file name in Filename input field
https://bugs.kde.org/show_bug.cgi?id=486322 --- Comment #4 from Tyson Tan --- It appears that this bug only affects the first export attempt of a Krita session. Once the user successfully exported anything (the image was saved), all export coming after that (even with other documents) will have their original file name provided in the input box. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486322] Export document dialogue doesn't have the original file name in Filename input field
https://bugs.kde.org/show_bug.cgi?id=486322 Tyson Tan changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Tyson Tan --- Sorry, I think the bug still exists. I probably have mistaken it with Save As... in Comment 2. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486322] Export document dialogue doesn't have the original file name in Filename input field
https://bugs.kde.org/show_bug.cgi?id=486322 Tyson Tan changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Tyson Tan --- Seemed to have been fixed now. Although I don't know which commit or what building environment change fixed it. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486322] New: Export document dialogue doesn't have the original file name in Filename input field
https://bugs.kde.org/show_bug.cgi?id=486322 Bug ID: 486322 Summary: Export document dialogue doesn't have the original file name in Filename input field Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- Somewhere between 2024/04/20 - 2024/04/30, Krita Nightly Unstable build's Export Document dialogue doesn't supply the original file name in its Filename input field anymore. It is always empty by default. I don't think this change is desirable. It makes the exporting process so much more cumbersome, and which acts against effective file management and document versioning. Tested with krita-5.3.0-prealpha-cd30414277-x86_64.appimage (2024/04/30) I suspect the following commits that were merged on 2024/04/24: Fix resetting document title on File->Export cancel https://invent.kde.org/graphics/krita/-/tree/07293e87b3ab329a0adcb9d4efb52ad5093b73d9 Added option to fix file type when exporting https://invent.kde.org/graphics/krita/-/tree/5ba1cb38760f6bf7d0e12be840ebef8db8062bc8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 Tyson Tan changed: What|Removed |Added CC||15503134...@163.com --- Comment #18 from Tyson Tan --- *** Bug 449000 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449000] Mouse wheel rotates canvas and stops working after importing image
https://bugs.kde.org/show_bug.cgi?id=449000 Tyson Tan changed: What|Removed |Added CC||tysont...@gmail.com Resolution|WORKSFORME |DUPLICATE --- Comment #4 from Tyson Tan --- *** This bug has been marked as a duplicate of bug 483687 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 Tyson Tan changed: What|Removed |Added Summary|[Windows] [Since|[Windows] Canvas shortcuts |4.3.0beta1] Canvas |break when other |shortcuts break when other |applications try steal |applications try steal |focus or listen to global |focus or listen to global |shortcuts |shortcuts | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #17 from Tyson Tan --- Created attachment 168055 --> https://bugs.kde.org/attachment.cgi?id=168055&action=edit Video of Krita's canvas shortcut issue -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #16 from Tyson Tan --- Created attachment 168054 --> https://bugs.kde.org/attachment.cgi?id=168054&action=edit Krita tablet event log during the issue This tablet event log ended with a suspicious message: WARNING: modifiers state became inconsistent! Trying to fix that... inputEvent->modifiers() = QFlags(NoModifier) d->matcher.debugPressedKeys() = QVector(Qt::Key_Shift, Qt::Key_Control, Qt::Key_T, Qt::Key_F22) It has "modifiers state inconsistant" and the repeatedly reported "F22" key like many other users reported. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #15 from Tyson Tan --- Maybe this bug is related to: https://bugs.kde.org/show_bug.cgi?id=462768 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 Tyson Tan changed: What|Removed |Added Component|General |Shortcuts and Canvas Input ||Settings -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #14 from Tyson Tan --- I don't think I have the knowledge to do that. Maybe a Krita dev knows how. I will first try to investigate this with the Krita devs, and get back to you if what we found was indeed a Qt bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #12 from Tyson Tan --- I can try to record a video with Key stroke visualization, if that's what you mean. I will do it later tonight. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #10 from Tyson Tan --- To sum the important new findings up: 1) Something happened between Krita 4.2.9 and 4.3.0beta1 caused this issue. 2) Or maybe something happened between Qt 5.12.7 and 5.12.8 caused it. 3) This is not China specific. 4) Changing Krita's workspace restores Canvas Shortcuts temporarily. Therefore, I think this is indeed a Krita problem. Maybe since 4.3.0beta1, Krita 's canvas focus restore mechanism has been broken. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #9 from Tyson Tan --- I also traced back this issue to a Krita-Artist forum post: https://krita-artists.org/t/4-3-beta-1-certain-keyboard-shortcuts-not-working/7027/9 This user is not Chinese, so this issue is not China specific. And the post is 4.3.0beta1 related. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #8 from Tyson Tan --- Additionally, when Krita's Canvas Shortcuts are broken: Mouse wheel Up/Down to Zoom is also broken. Possibly because it's also a Canvas Shortcut? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #7 from Tyson Tan --- On another note, I've also discovered a workaround inside Krita. Whenever Krita lost its Canvas Shortcuts: 1) Click "Choose Workspace" button on the right of Krita's toolbar. 2) Change to another Workspace and back. 3) Krita's Canvas shortcuts is restored temporarily. However, if the upper mentioned 3rd party apps trigger the issue again, Krita will lose its Canvas Shortcuts again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #6 from Tyson Tan --- Weixin PC Client (微信 PC 客户端): https://weixin.qq.com/ https://pc.weixin.qq.com/ Weixin PC Client appears to be Electron based. The following behaviors break Krita's canvas shortcuts: 1) The Login of Weixin PC Client bringing up its main window above other apps. 2) The chat dialogue has an "Emotion" button. Clicking this icon to open the Emotion GIF list. 3) Clicking "Mini Programs (小程序)" icon on its Left sidebar opens a special dialogue window. 4) Clicking "Channels (视频号)" icon on its Left sidebar opens a special dialogue window. There is no known workaround for Weixin except avoiding the actions above. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #5 from Tyson Tan --- Dingtalk (钉钉): https://www.dingtalk.com/ https://page.dingtalk.com/wow/z/dingtalk/simple/ddhomedownload#/ This app seems to be Qt based. It has Qt 5.15.11 libraries in its installation directory. The Starting up, Login Sequence, New Message Notifications seemed to break Krita's canvas shortcuts. After turning off all of Dingtalk's global hotkeys, I was unable to reproduce this issue anymore. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #4 from Tyson Tan --- Tencent QQ (Old branch): https://im.qq.com/ https://im.qq.com/pcqq/index.shtml https://dldir1.qq.com/qqfile/qq/PCQQ9.7.22/QQ9.7.22.240318_01.exe Only the old 9.7.x branch was affected. The recently rewritten 9.9.x branch is unaffected. The old branch was written in C. The new branch is Electron based. The Startup and Login sequence of this old QQ will break Krita's canvas shortcuts. Nothing else. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #3 from Tyson Tan --- To add to my discovery in Comment 3: In my initial report Description and Comment 1 I said I was only able to reproduce the issue with Sogou Pinyin Input Method. This turned out to be inaccurate. In reality, almost every popular Instant Messaging app in China was affected. This includes: 1) QQ (the old 9.7.x branch) 2) Dingtalk 3) Weixin These apps require Chinese ID to register an account, so it's not practical for the Krita team to test them. I will include what triggered the issue in these apps below. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #2 from Tyson Tan --- After more investigation, I discovered some important clues that point to Krita/Qt. 1) Krita 4.2.9 was unaffected by this bug. 2) The problem started to happen since 4.3.0beta1. 3) I tested this personally, using binaries from KDE Attic: https://download.kde.org/Attic/krita/ Krita 4.3 Release Notes: https://krita.org/en/release-notes/krita-4-3-release-notes/ Qt version difference: Krita 4.2.9 uses Qt 5.12.7. Krita 4.3.0beta1 uses Qt 5.12.8 Qt 5.12.8 Release Notes: https://www.qt.io/blog/qt-5.12.8-released Fixed bugs in Qt 5.12.8: https://bugreports.qt.io/browse/QTBUG-79192?filter=21875 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] [Since 4.3.0beta1] Canvas shortcuts break when other applications try steal focus or listen to global shortcuts
https://bugs.kde.org/show_bug.cgi?id=483687 Tyson Tan changed: What|Removed |Added Summary|[Windows] Krita loses |[Windows] [Since |modifier and mouse click|4.3.0beta1] Canvas |canvas input due to certain |shortcuts break when other |apps aggressively stealing |applications try steal |focus |focus or listen to global ||shortcuts -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] [Windows] Krita loses modifier and mouse click canvas input due to certain apps aggressively stealing focus
https://bugs.kde.org/show_bug.cgi?id=483687 --- Comment #1 from Tyson Tan --- Here I will repeat the important points in Chinese, so people can find this bug report easier. Krita 在 Windows 下面会因为某些其他程序使用激进的手段抢夺窗口焦点而导致 Krita 的画布输入失去修饰键 (Ctrl/Shift/Alt) 和鼠标中键/右键。没有经验的用户体验到的表象是“快捷键失效”、“Ctrl键按下不能拾色”、“无法打开右键弹出面板”、“无法用中键移动画布”等。然而实际上这和快捷键没有关系——单键的快捷键 (如B/E/R/V 等)，带修饰键的非画布快捷键 (Ctrl+S 等) 的工作依然是正常的。 以搜狗拼音输入法为例，我的测试发现在以下的任意情况下它会积极地抢夺 Krita 的焦点： 1. 从其他输入法切换到搜狗拼音 2. 显示推广气泡 (在搜狗输入法工具栏上方偶尔出现的单行文字提示，例如推广语音输入、AI写作等功能) 3. 搜狗拼音的语音输入 (麦克风按钮) 点击后打开了语音输入框在实时监听用户输入时 必须将这些气泡、弹窗、对话框全部关闭 (不需要关闭搜狗输入法本身)，然后重启 Krita，这样 Krita 的画布快捷键输入才会恢复正常。 我已经将这个问题通过搜狗输入法内建的反馈功能提交给他们了，虽然他们大概率不会做任何事情。 我记得这个问题并不是一直存在的，好象是从 2022 年左右搜狗拼音被重写时才开始陆续发现有人报告这个问题，而且当时貌似很多其他绘画软件也遇到不少奇怪的丢输入的情况。不知道是不是一回事。 虽然有人说微信可能也会导致问题，但是我测试的时候同时打开了QQ、微信、钉钉、B站、网易云音乐、百度网盘、360浏览器等这些常见软件，全部默认设置直接用，它们各自都有推送消息弹窗等，但我并没有遇到任何问题——只有搜狗拼音才会发生问题。 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483687] New: [Windows] Krita loses modifier and mouse click canvas input due to certain apps aggressively stealing focus
https://bugs.kde.org/show_bug.cgi?id=483687 Bug ID: 483687 Summary: [Windows] Krita loses modifier and mouse click canvas input due to certain apps aggressively stealing focus Classification: Applications Product: krita Version: 5.2.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- SUMMARY *** Under Windows, Krita loses modifier and mouse click canvas input due to certain apps aggressively stealing focus. User would experience symptoms like "broken shortcuts" and "unable to pick color by pressing down Ctrl", "unable to call popup palette", "unable to move canvas view by middle button". But in fact, this has nothing to do with shortcuts. For example, single key shortcuts like B, E, etc are not affected. Non canvas input shortcuts with modifier (like Ctrl+S for saving document) are not affected. I found out that this problem has something to do with certain apps aggressively stealing focus -- by them either showing persistent popups, or showing a high priority dialogue that listens to user input in real time, all time. If Krita's focus got stolen, I must first close those popups/dialogues, then restart Krita to get the modifiers and mouse clicks working again. *** STEPS TO REPRODUCE Here I will use Sogou Pinyin (搜狗拼音输入法) ( https://shurufa.sogou.com/) as example. Sogou Pinyin is a popular Chinese input app. Almost every PC in China have this app as the default input method -- meaning it will always have a toolbar on screen. Sogou Pinyin steals focus at EITHER of the following situations: 1. Switching from other Input method to Sogou Pinyin; 2. Sogou Pinyin showing a persistent advertisement popup above its toolbar, you must click the X button to close it; 3. Sogou Pinyin's Voice Input dialogue in open (press the "microphone" button on its toolbar). OBSERVED RESULT If ANY of the situations above happened, Krita immediately loses its modifier key input and middle/right button input. Restarting Krita alone won't solve the issue. Sogou Pinyin's AD Popups/Voice Input dialogues must be closed before restarting Krita to solve this issue. SOFTWARE/OS VERSIONS Windows: Windows 11 23H2 ADDITIONAL INFORMATION There is a KA forum discussion thread about this issue: https://krita-artists.org/t/if-i-click-away-from-krita-my-shortcuts-break-5-1-1/51977/10 Although I think their understanding was inaccurate. I was unable to reproduce any of their claims about WeChat PC client causing issues. This issue is a very serious threat to our userbase in China, given how popular Sogou Pinyin is in this region. I began to hear about this around 2022 when Sogou Pinyin was rewritten. Many users were forced away from Krita because of this issue making them unable to use Krita, and no one seemed to know what caused it. I have reported this issue to Sogou Pinyin. But I doubt they will do anything. It is worth mention that every other art apps aren't being affected like Krita. Maybe they have implemented specific workarounds for this issue. Maybe if Krita can steal focus more aggressively, we can solve this problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481548] After switching to new Hugo based website, Welcome Page News section is not fetching non-English news properly
https://bugs.kde.org/show_bug.cgi?id=481548 --- Comment #3 from Tyson Tan --- Created attachment 165946 --> https://bugs.kde.org/attachment.cgi?id=165946&action=edit English/Japanse/Chinese becomes English/English/English -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481548] After switching to new Hugo based website, Welcome Page News section is not fetching non-English news properly
https://bugs.kde.org/show_bug.cgi?id=481548 --- Comment #2 from Tyson Tan --- No, it's not like I'm against always showing English, but currently for example if you set to show English, Chinese and Japanese, you get English, English, English. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481548] New: After switching to new Hugo based website, Welcome Page News section is not fetching non-English news properly
https://bugs.kde.org/show_bug.cgi?id=481548 Bug ID: 481548 Summary: After switching to new Hugo based website, Welcome Page News section is not fetching non-English news properly Classification: Applications Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- Since Krita.org switching to Hugo platform, the News section on Krita's Welcome page has broken. It doesn't fetch non-English language news properly. Every alternative language is showing English content. Maybe it has something to do with the new languages tags (which is correct on the new website). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481418] New: Krita's Fisheye Assistant is using the wrong kind of curves
https://bugs.kde.org/show_bug.cgi?id=481418 Bug ID: 481418 Summary: Krita's Fisheye Assistant is using the wrong kind of curves Classification: Applications Product: krita Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- Created attachment 165861 --> https://bugs.kde.org/attachment.cgi?id=165861&action=edit Fisheye Perspective Curves are segments of Perfect Circles Krita's Fisheye Assistant is using the wrong kind of curves. The Fisheye Assistant is currently using ellipses for its curves. However, a proper Fisheye Perspective can only be achieved by using segments of perfect circle. In fact, Krita's Curvlinear Perspective Rulers is doing this the correct way -- it makes sense too -- Fisheye perspective is just an application of Curvlinear Perspective. Although the effects of using ellipses and perfect circles might look similar, ellipses only works for projecting spherical objects on a flat screen -- for example, a photo of a globe. As such, it can only loosely mimic 1-point dead-center Fisheye Perspective. If we increase the center points for more complicated Fisheye Perspectives, this misuse of curves will prevent people to understand how things works, and things fall apart. A will attach a proper Fisheye Perspective guideline for reference. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 480818] New: kcm-wacomtablet does not work with the Wacom One Pen Dispaly 2023 models
https://bugs.kde.org/show_bug.cgi?id=480818 Bug ID: 480818 Summary: kcm-wacomtablet does not work with the Wacom One Pen Dispaly 2023 models Classification: Plasma Product: wacomtablet Version: 3.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: tysont...@gmail.com Target Milestone: --- kcm-wacomtablet does not work with the Wacom One Pen Dispaly 2023 models. The device is correctly detected and operational, but none of the settings on kcm-wacomtablet has any effect. I can still use xsetwacom to change the settings. Older device like Cintiq Pro 24 are not affected. Installing xorg-xinput did not help. xsetwacom list devices Wacom One 13 Touch (DTH134): Wacom One pen display 13.3" with touch Pen stylus id: 21 type: STYLUS Wacom One pen display 13.3" with touch Finger touch id: 22 type: TOUCH Wacom One pen display 13.3" with touch Pen eraser id: 32 type: ERASER Wacom One 12 (DTC121): Wacom One pen display 11.6" Pen stylus id: 21 type: STYLUS Wacom One pen display 11.6" Pen eraser id: 22 type: ERASER Operating System: Manjaro Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 Kernel Version: 6.7.0-0-MANJARO (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480677] Canvas-only mode and Normal mode remember dockers layout separately, unless restarting Krita
https://bugs.kde.org/show_bug.cgi?id=480677 Tyson Tan changed: What|Removed |Added Summary|Canvas-only mode and Normal |Canvas-only mode and Normal |mode remembers dockers |mode remember dockers |layout separately, unless |layout separately, unless |restarting Krita|restarting Krita -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480677] New: Canvas-only mode and Normal mode remembers dockers layout separately, unless restarting Krita
https://bugs.kde.org/show_bug.cgi?id=480677 Bug ID: 480677 Summary: Canvas-only mode and Normal mode remembers dockers layout separately, unless restarting Krita Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- If Toolbox and dockers are set to not hidden in Canvas-only mode, dockers layout (positions and their show/hide states) are remembered separately in Canvas-only mode for the current session. Upon exiting Canvas-only mode, every docker layout change will be reverted to what they were in Normal mode. This is an unwanted behavior. It leads to confusion to those who use Canvas-only mode with some dockers shown. How to reproduce: 1. Configure Krita > Canvas-only settings > uncheck "Toolbox and dockers" 2. Press Tab to enter Canvas-only mode 3. Close a docker, or move its position 4. Press Tab again to exit Canvas-only mode 5. Dockers are reverted to what they were in Normal mode. Workaround: 1. Only change dockers in normal mode 2. After changing the dockers, restart Krita 3. The changed dockers layout now works in Canvas-only mode Tested with krita-5.3.0-prealpha-a8f6ca21b0-x86_64.appimage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480444] New: Krita should disable Touch Painting and One Finger gestures by default
https://bugs.kde.org/show_bug.cgi?id=480444 Bug ID: 480444 Summary: Krita should disable Touch Painting and One Finger gestures by default Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- Krita currently enables Touch Painting by default: Configure Krita > General > Tools > Enables Touch Painting Krita currently assigns One Finger Tap gesture to Show Popup Widget by default: Configure Krita > Canvas Input Settings > Show Popup Widget Krita currently assigns One Finger Drag gesture to Pan Canvas by default: Configure Krita > Canvas Input Settings > Pan Canvas In practice, these default settings make no sense. They work against any tablet or pen display with touch sensibility. We either disable them, or we have to disable the touch on the device. We just can't work with all the mistakes they cause. With more and more devices becoming touch-sensitive, they have become the first thing to get in the way for our new users. And that's not a good first impression. I suggest we disable Touch Painting by default. No sane artist would ever draw with Touch instead of a stylus. Those who do, are more suitable to play with something like MS Paint or Kolorpaint instead. Touch Painting is not pressure sensitive, not accurate, and thus has no place in a professional art app. Touch Painting is prone to leave unwanted stroke marks on the canvas that ruins the artwork. It also blocks all Touch Gestures, which is the primary reason for any artist to use a touch sensitive device in the first place. I suggest we don't assign any Canvas Input to One Finger Tap gesture by default. One Finger Tap gesture is currently assigned to Show Popup Widget by default. We don't need that, because we have a right button on our canvas. In fact, we shouldn't assign anything to One Finger Tap -- it causes way too many unwanted activations that it is impossible to draw under such condition. I suggest we don't assign any Canvas Input to One Finger Drag gesture by default. One Finger Drag gesture is currently assigned to Pan Canvas by default. We don't need that, because we already have a more natural, more powerful default gesture -- Two Finger Draw to Zoom and Rotate Canvas (it can pan the canvas, too). In fact, we shouldn't assign anything to One Finger Drag -- it causes way too many unwanted activations that cause the canvas to jump around. It is impossible to draw reliably under such condition. I think One Finger gestures are just too error-prone to be used. They are only good for scrolling / selecting items. It's wise to just leave them unused on Krita's canvas. Lastly, I think we might want to default Two Finger Drag gesture to Zoom Canvas, instead of Zoom and Rotate Canvas. It causes way too many unwanted rotations. It is annoying to correct the canvas orientation every time after zooming. But I can understand why people would want a two-finger rotation gesture. If we can make snapping to 0 degree happens more aggressively, it can help us to recover from unwanted rotations. By changing these default settings, I believe we can create a much better out-of-box user experience for artists who have a touch-sensitive tablet or pen display. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480440] [Windows] Krita should use OpenGL as the default renderer for AMD GPUs
https://bugs.kde.org/show_bug.cgi?id=480440 --- Comment #2 from Tyson Tan --- ANGLE currently has a warning message about Texture buffers being explicitly disabled. I wonder if that's related. Also I think it's quite scary to have a default settings to display a warning like that. It's not very reassuring. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480440] New: [Windows] Krita should use OpenGL as the default renderer for AMD GPUs
https://bugs.kde.org/show_bug.cgi?id=480440 Bug ID: 480440 Summary: [Windows] Krita should use OpenGL as the default renderer for AMD GPUs Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- Currently under Windows, Krita's default "Auto" setting for renderer is using Direct 3D 11 via ANGLE. However, AMD GPUs performs poorly under ANGLE. Everything on the canvas appears to have a slow frame rate. Brush strokes have visible stuttering. It's nearly unusable. Change the renderer to OpenGL, then everything works smoothly. Maybe we should default to OpenGL for AMD GPUs instead. Tested under Windows 11 (23H2), with AMD Radeon RX7600 or AMD Radeon 780M (Ryzen 7840U). The system is freshly installed, with everything up-to-date including the latest driver (Adrenalin 24.1.1). The performance is the same for Krita 5.2.2 and krita-nightly-x64-5.3.0-prealpha-9a64eec01e (2024-01-28). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435185] Add shortcuts and sliders for Fade and Scatter in Auto brush mode
https://bugs.kde.org/show_bug.cgi?id=435185 --- Comment #7 from Tyson Tan --- Nothing really at this point. I thought about requesting optional sliders for Fade and Scatter in Krita's toolbar. But on second thought, we need to rely on Brush Editor's preview to control the effect. Toolbar sliders alone wouldn't be enough. It'd be nice if the toolbar sliders have built-in brush previews ... But let's not get too ahead of ourselves. :P -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438702] Missing translations for a few common buttons like OK and Cancel (Kdenlive official builds only)
https://bugs.kde.org/show_bug.cgi?id=438702 --- Comment #3 from Tyson Tan --- Yes, I think the translation issue has been fixed. Also check bug 434179, I think it has been fixed too. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472381] Simplified Chinese (zh_CN) translation of docs.krita.org is broken
https://bugs.kde.org/show_bug.cgi?id=472381 Tyson Tan changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Tyson Tan --- It seemed to have fixed itself now. I thought it was out of sync, because after updating the translation SVN, I didn't see dev.krita.org using the new translations for days. Do we usually need a few days before dev.krita.org loads the new translations? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 474674] Text Tool doesn't recognize any white spaces in front of the first line
https://bugs.kde.org/show_bug.cgi?id=474674 --- Comment #3 from Tyson Tan --- Thanks for the explanation! :D -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 474674] Text Tool doesn't recognize any white spaces in front of the first line
https://bugs.kde.org/show_bug.cgi?id=474674 --- Comment #1 from Tyson Tan --- Created attachment 161710 --> https://bugs.kde.org/attachment.cgi?id=161710&action=edit Krita Text Tool can't recognize white spaces in front of the first line KRA -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 474674] New: Text Tool doesn't recognize any white spaces in front of the first line
https://bugs.kde.org/show_bug.cgi?id=474674 Bug ID: 474674 Summary: Text Tool doesn't recognize any white spaces in front of the first line Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- Created attachment 161709 --> https://bugs.kde.org/attachment.cgi?id=161709&action=edit Krita New Text Engine doesn't recognize the first white spaces in the first line After upgrading to the new text engine, Krita now fails to recognize the first white spaces in the first line of a text shape. All white spaces in front of the first line is now ignored. But they work fine starting from the second line. I used full-width white spaces in the sample, which is widely used in CJK countries. But it is the same for half-width white spaces used in western countries. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429665] Touchpad Tap-to-click should be enabled by default in System Settings
https://bugs.kde.org/show_bug.cgi?id=429665 --- Comment #10 from Tyson Tan --- (In reply to Kevin Kofler from comment #9) I've already said it in Comment 2, I suppose I should expand the details: > If there is really no other way to click on a given touchpad Even though most button-less trackpads can press-to-click, but in reality, such interaction is not a practical way to use those devices. They are clearly not engineered to be used as such. The natural interaction on those device is self-explained: 1) Who knows to press down for a button, when there is NO BUTTON to be seen? -- newer generations GREW UP WITH TOUCHSCREENS, -- they will never have guessed the trackpad can be pressed down for a button. 2) You often need to press really hard to initiate a click. -- because unlike a physical button, you don't know where the switch is under the surface. -- as such, precise clicks and dragging are nearly impossible, -- and mistakes are rampant because there is no clear divide between the trackpad and the "buttons". If there is anything the trackpad designers are trying to imply, they are encouraging people to use tap-to-click, while discouraging people from using press-to-click. Press-to-click on a trackpad is more like a fail-safe, fallback, last-resort kind of feature. According to my observation, NOBODY in ANY organization I worked in EVER used press-to-click on their button-less trackpads. EVERY people I EVER recommended KDE Plasma to, the FIRST difficulty they ran into on a laptop has ALWAYS been the "tap-to-click" feature being disabled by default. > For everyone else, defaulting to tap to click is a bad idea because it is > redundant with the physical clicks and because it is prone to misclicks. Maybe it only with old trackpads. Not so much for modern devices. I never had any misclicks on my tiny 10-inch mini-laptop with tap-to-click. > disabling that misfeature was one of the first things I changed. Now enabling that feature becomes one of the first things I changed, and the same for many more other people... Disabling tap-and-click by default is a misfeature that turns first time users away. Really bad first impression when you can't even click anything unless educated before-hand. EVERY OTHER OSes are doing the opposite, KDE Plasma's default behavior stands out like a sore-thumb. The situation has changed, and the world has moved on. We need to adapt. I really don't think dwelling on the past experience is going to help us in the long run. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473023] New: [Android] Missing translations in Wide Gamut Color Selector's configuration dialogue and Tablet Settings page
https://bugs.kde.org/show_bug.cgi?id=473023 Bug ID: 473023 Summary: [Android] Missing translations in Wide Gamut Color Selector's configuration dialogue and Tablet Settings page Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: Translation Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- Krita's Android version has been missing some translations for Wide Gamut Color Selector's configuration dialogue and the Tablet Settings page. Wide Gamut Color Selector docker's Configuration dialogue has been missing the translations for the common buttons. Those are placed at the bottom of the dialogue: OK Cancel Restore Defaults Tablet Settings page in Configure Krita dialogue has been missing 2 translations for the sliders. Those had been missing for other reasons for years, but Dmitry fixed them about 1-2 months ago. They are: Maximum brush speed Brush speed smoothing The Appimage is showing the upper mentioned translations properly. Tested on Samsung Galaxy Tab S8, OneUI 5.1 (Android 13). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473021] New: [Android] Toolbar‘s Expansion Spacer is broken and now only shows its label text
https://bugs.kde.org/show_bug.cgi?id=473021 Bug ID: 473021 Summary: [Android] Toolbar‘s Expansion Spacer is broken and now only shows its label text Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- Some time between the latest 2 Android nightly builds (#1167, #1168, 2023-08-03, 2023-08-04), the toolbar's Expansion Spacer went broken. It now only shows its text label (literally "Expansion Spacer") instead of doing what it is supposed to do. Appimage version is not affected. But I noticed there is a new "edit" toolbar now, and it's not showing its name in Toolbar menu. Maybe something has been changed in the toolbars that caused this? Tested on Samsung Galaxy Tab S8, OneUI 5.1 (Android 13). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465886] Text tool font options are broken in Krita Next after the merging of the new text part
https://bugs.kde.org/show_bug.cgi?id=465886 --- Comment #13 from Tyson Tan --- Thank you, Alvin. I need this function in my job. Now I can finally use the Nighties again! :D -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 472747] squashfuse 0.3.0-1 causes kioslave5 to crash upon appimage thumbnail creation
https://bugs.kde.org/show_bug.cgi?id=472747 --- Comment #3 from Tyson Tan --- The upstream has already fixed the bug. They released squashfuse 0.4.0 which has already been pushed by Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 472747] squashfuse 0.3.0-1 causes kioslave5 to crash upon appimage thumbnail creation
https://bugs.kde.org/show_bug.cgi?id=472747 Tyson Tan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Tyson Tan --- https://github.com/vasi/squashfuse/issues/105 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 472747] New: squashfuse 0.3.0-1 causes kioslave5 to crash upon appimage thumbnail creation
https://bugs.kde.org/show_bug.cgi?id=472747 Bug ID: 472747 Summary: squashfuse 0.3.0-1 causes kioslave5 to crash upon appimage thumbnail creation Classification: Frameworks and Libraries Product: kio-extras Version: 23.04.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Thumbnails and previews Assignee: plasma-b...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- After the my ArchLinux installation updated to squashfuse 0.3.0-1, kioslave5 began to crash when kio is trying to create thumbnails for appimage files. Could be an upstream/packaging issue, but I'm not familiar with this, so I reported the issue here, just in case. I will report the same issue to squashfuse, if no one did it already. Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 squashfuse: 0.3.0-1 kio-extras: 23.04.3-1 libappimage: 1.0.4.5-4 Application: kioslave5 (kioslave5), signal: Segmentation fault [KCrash Handler] #4 0x7f13f004fdbf in sqfs_init () at /usr/lib/libsquashfuse.so.0 #5 0x7f13f004ff0b in sqfs_open_image () at /usr/lib/libsquashfuse.so.0 #6 0x7f13dc70480c in appimage::core::impl::TraversalType2::TraversalType2(std::__cxx11::basic_string, std::allocator >) () at /usr/lib/libappimage.so.1.0 #7 0x7f13dc704ada in () at /usr/lib/libappimage.so.1.0 #8 0x7f13dc704c69 in appimage::core::PayloadIterator::PayloadIterator(appimage::core::AppImage const&) () at /usr/lib/libappimage.so.1.0 #9 0x7f13dc704cce in appimage::core::AppImage::files() const () at /usr/lib/libappimage.so.1.0 #10 0x7f13dc70c0a3 in appimage::utils::PayloadEntriesCache::readAllEntries() () at /usr/lib/libappimage.so.1.0 #11 0x7f13dc70de9e in appimage::utils::PayloadEntriesCache::buildCache() () at /usr/lib/libappimage.so.1.0 #12 0x7f13dc70e2a2 in appimage::utils::PayloadEntriesCache::PayloadEntriesCache(appimage::core::AppImage const&) () at /usr/lib/libappimage.so.1.0 #13 0x7f13dc70e2fe in appimage::utils::ResourcesExtractor::ResourcesExtractor(appimage::core::AppImage const&) () at /usr/lib/libappimage.so.1.0 #14 0x7f13dc7054cf in appimage_read_file_into_buffer_following_symlinks () at /usr/lib/libappimage.so.1.0 #15 0x7f13f0057530 in () at /usr/lib/qt/plugins/kf5/thumbcreator/appimagethumbnail.so #16 0x7f13f97108c9 in () at /usr/lib/qt/plugins/kf5/kio/thumbnail.so #17 0x7f13f97165d5 in () at /usr/lib/qt/plugins/kf5/kio/thumbnail.so #18 0x7f13f960da14 in () at /usr/lib/libKF5KIOCore.so.5 #19 0x7f13f960a106 in KIO::SlaveBase::dispatch(int, QByteArray const&) () at /usr/lib/libKF5KIOCore.so.5 #20 0x7f13f960225e in KIO::SlaveBase::dispatchLoop() () at /usr/lib/libKF5KIOCore.so.5 #21 0x7f13f97122c2 in kdemain () at /usr/lib/qt/plugins/kf5/kio/thumbnail.so #22 0x5613ecf2d1fd in () #23 0x7f13f8e83850 in () at /usr/lib/libc.so.6 #24 0x7f13f8e8390a in __libc_start_main () at /usr/lib/libc.so.6 #25 0x5613ecf2d455 in () [Inferior 1 (process 3113) detached] -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472381] Simplified Chinese (zh_CN) translation of docs.krita.org is broken
https://bugs.kde.org/show_bug.cgi?id=472381 Tyson Tan changed: What|Removed |Added CC||tyson...@tysontan.com --- Comment #2 from Tyson Tan --- Yeah, I figured it was a branch switch related issue too. People freak out when things suddenly go back in time. XD Definitely delete the old translations. Those were 4 years old. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462921] Main Menu -> View -> Canvas has become untranslatable in Krita Next
https://bugs.kde.org/show_bug.cgi?id=462921 Tyson Tan changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Tyson Tan --- Yeah, it has been fixed in Krita Plus and replaced in Krita Next. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469945] Krita Nightly crashed by any action after started for a while
https://bugs.kde.org/show_bug.cgi?id=469945 --- Comment #8 from Tyson Tan --- Thanks, Dmitry! :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470969] Krita Android nighties crashed on most actions
https://bugs.kde.org/show_bug.cgi?id=470969 --- Comment #7 from Tyson Tan --- Thanks, Sharaf! :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470969] Krita Android nighties crashed on most actions
https://bugs.kde.org/show_bug.cgi?id=470969 --- Comment #5 from Tyson Tan --- When I reported bug 469945, this bug didn't occur. So the last known good date is 2023-05-18, and it has nothing to do with that bug either, since Dmitry has already fixed it before build pipeline #1116. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470969] Krita Android nighties crashed on most actions
https://bugs.kde.org/show_bug.cgi?id=470969 --- Comment #4 from Tyson Tan --- Created attachment 159630 --> https://bugs.kde.org/attachment.cgi?id=159630&action=edit Krita crash log -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470969] Krita Android nighties crashed on most actions
https://bugs.kde.org/show_bug.cgi?id=470969 --- Comment #3 from Tyson Tan --- Created attachment 159629 --> https://bugs.kde.org/attachment.cgi?id=159629&action=edit Krita Android log -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470969] Krita Android nighties crashed on most actions
https://bugs.kde.org/show_bug.cgi?id=470969 --- Comment #2 from Tyson Tan --- Created attachment 159628 --> https://bugs.kde.org/attachment.cgi?id=159628&action=edit Krita system info -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470969] Krita Android nighties crashed on most actions
https://bugs.kde.org/show_bug.cgi?id=470969 --- Comment #1 from Tyson Tan --- Created attachment 159627 --> https://bugs.kde.org/attachment.cgi?id=159627&action=edit Krita usage log -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470969] New: Krita Android nighties crashed on most actions
https://bugs.kde.org/show_bug.cgi?id=470969 Bug ID: 470969 Summary: Krita Android nighties crashed on most actions Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 13.x Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- Krita Android nighties are crashing on most actions lately. I wasn't able to create a new document, nor open existing ones. It even crashed on calling the bug report. Tested on Samsung Tab S8 with OneUI 5.1 (Android 13) with pipeline #1116 (2023-06-13). I will attach the logs on following posts. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470871] Krita lacks the ability to extract text from image and then paste them as text object
https://bugs.kde.org/show_bug.cgi?id=470871 --- Comment #3 from Tyson Tan --- The original bug reporter contacted me using email. It turned out to be a feature request rather than a valid bug report. The reporter wanted to request the feature of automatically extracting flattened text from an image, along with the font style, the user can then paste into a real text object. >From the description in their email, I think the reporter also wanted to request the feature of creating fonts by mimicking the flattened text. The reporter said "Photoshop already has this", and "I would like you to improve your tutorials and other places as well" without saying anything specific. I could not find any information about Photoshop being able to do what they mentioned. I'm speculating that they might have glanced some Photoshop tutorials which they misunderstood the content and thought it was all automation feature of the app. I had a light stroke reading their email. The writing could use much coaching. I would categorize this as "Report Under Influence (RUI)". :P -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470871] Krita lacks the ability to extract text from image and then paste them as text object
https://bugs.kde.org/show_bug.cgi?id=470871 Tyson Tan changed: What|Removed |Added Severity|normal |wishlist Summary|图片不能把字体提取出来，也不能粘贴新文本|Krita lacks the ability to ||extract text from image and ||then paste them as text ||object -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470871] 图片不能把字体提取出来，也不能粘贴新文本
https://bugs.kde.org/show_bug.cgi?id=470871 --- Comment #2 from Tyson Tan --- 你好，你想报告什么问题？你的报告的标题是“图片不能把字体提取出来，也不能粘贴新文本”。你应该描述的是： 你打算在 Krita 中做什么，为此进行了什么操作，遇到了什么问题。要具体说明。 你现在附带上来的日志对你标题中描述的问题是没有价值的，因为日志只能用来排查程序崩溃。 如果你不懂英语，可以直接写中文。我会帮你翻译成英语。 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469945] Krita Nightly crashed by any action after started for a while
https://bugs.kde.org/show_bug.cgi?id=469945 --- Comment #5 from Tyson Tan --- Tested with today's appimage: krita-5.2.0-prealpha-e6c66a0bd4-x86_64.appimage It appeared that the crash has nothing to do with brush action specifically. Krita would just crash by doing anything, after started for a while. It wouldn't crash on its own. It'd crash by doing any action or by just closing the document. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469945] Krita Nightly crashed by any action after started for a while
https://bugs.kde.org/show_bug.cgi?id=469945 Tyson Tan changed: What|Removed |Added Summary|Krita Nightly crashed after |Krita Nightly crashed by |a few brush strokes |any action after started ||for a while -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469945] Krita Nightly crashed after a few brush strokes
https://bugs.kde.org/show_bug.cgi?id=469945 --- Comment #4 from Tyson Tan --- I attached the KRA file which I experienced the crash below: https://www.dropbox.com/s/14h2405l8glhs4n/fanart_20230331A_20190211_celeste.zip?dl=0 I was using a custom brush. Engine: Pixel Brush tip: Image -- chisel_soft Size: 92.46px General: Size -> Pressure (Exponential upward curve) Rotation -> Direction (Linear) Texture: Strength -> Pressure (Linear) 100% I was drawing on the Layer named "Maddy". It's a normal layer. I was drawing slowly for the long black lines along the character's boots. Krita would not handle more than 10 strokes before it froze, and then crashed immediately afterward without any message. I also received a libwacom package update on Archlinux today before using Krita. I wonder if that could be related. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469945] Krita Nightly crashed after a few brush strokes
https://bugs.kde.org/show_bug.cgi?id=469945 --- Comment #1 from Tyson Tan --- Created attachment 159074 --> https://bugs.kde.org/attachment.cgi?id=159074&action=edit Krita system information I have encountered the same kind of crash on two different machines. I'm attaching one of the system information here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469945] New: Krita Nightly crashed after a few brush strokes
https://bugs.kde.org/show_bug.cgi?id=469945 Bug ID: 469945 Summary: Krita Nightly crashed after a few brush strokes Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- Created attachment 159072 --> https://bugs.kde.org/attachment.cgi?id=159072&action=edit Krita usage log Krita Nightly crashed after a few brush strokes. I'm using appimage on Archlinux. I noticed this crash in the latest build (cdb36cb4f0, 2023-05-17). I was unable to reproduce this in the prior build (a92c1c611a, 2023-05-16). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441978] Empties Trash to create free space string in navigation bar's Empty Trash button's tooltip is untranslatable
https://bugs.kde.org/show_bug.cgi?id=441978 Tyson Tan changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467310] Many translations are missing in digikam 7.9 and 7.10
https://bugs.kde.org/show_bug.cgi?id=467310 --- Comment #12 from Tyson Tan --- Thank you, they were indeed fixed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432100] Unable to rename a album with subfolders under Windows
https://bugs.kde.org/show_bug.cgi?id=432100 --- Comment #8 from Tyson Tan --- Hi Gilles, I reported this bug as an agent of the community, but I don't use Windows myself. I have forgotten everything after so many years. I'm sorry. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422006] [Dolphin] Emptying trash does not trigger view refresh
https://bugs.kde.org/show_bug.cgi?id=422006 --- Comment #22 from Tyson Tan --- It's still happening for me too. Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.10-arch1-1 (64-bit) Dolphin: 22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 465897] Potential problem in passing AppData translations to appstream-data
https://bugs.kde.org/show_bug.cgi?id=465897 --- Comment #20 from Tyson Tan --- (In reply to Aleix Pol from comment #18) > Thank you very much for such a thorough bug report! > > I think I've found the problem. The xml:lang field is getting generated as > "zh-CN" instead of "zh_CN". I'll see if I can find where this is generated. Thank you Aleix! :D -- You are receiving this mail because: You are watching all bug changes.
