[kde] [Bug 488975] The jitter mouse will continue to get bigger.
https://bugs.kde.org/show_bug.cgi?id=488975 --- Comment #2 from lc --- Created attachment 170813 --> https://bugs.kde.org/attachment.cgi?id=170813=edit The size in the settings is fixed, but the mouse is still getting bigger. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488975] The jitter mouse will continue to get bigger.
https://bugs.kde.org/show_bug.cgi?id=488975 --- Comment #1 from lc --- Because after updating the KDE 6.1.0 version, I found that the mouse turns on by default after setting the jitter, so I wanted to try this feature and fixed the size in the settings, but found that the mouse jitter keeps getting bigger. I don't know if anyone else has filed this bug, but I don't think it will affect anything. This passage is translated by a web page and may be incorrect. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7735H with Radeon Graphics Memory: 11.4 GiB of RAM Graphics Processor: AMD Radeon 680M Manufacturer: MECHREVO Product Name: WUJIE 14 System Version: Version 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488975] New: The jitter mouse will continue to get bigger.
https://bugs.kde.org/show_bug.cgi?id=488975 Bug ID: 488975 Summary: The jitter mouse will continue to get bigger. Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: gz18870140...@outlook.com Target Milestone: --- ARRAY(0x555c9397fa40) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479687] New: Mouse cursor doesn't show on primary display (Wayland only)
https://bugs.kde.org/show_bug.cgi?id=479687 Bug ID: 479687 Summary: Mouse cursor doesn't show on primary display (Wayland only) Classification: Plasma Product: kwin Version: 5.92.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: 7hwlyd...@mozmail.com Target Milestone: --- SUMMARY Mouse cursor doesn't show on primary display. Changing cursor themes does not help. Cursor appear on primary monitor after disconnect secondary. STEPS TO REPRODUCE 1. Notebook + External display (HDMI) 2. Plasma 6 RC1 Wayland 3. OBSERVED RESULT Mouse cursor doesn't show on primary display EXPECTED RESULT Mouse cursor is shown on all monitors SOFTWARE/OS VERSIONS KDE Plasma Version: 5.92.0 KDE Frameworks Version: Version 5.248.0 Qt Version: Version 6.7.0 (built against 6.7.0) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 479091] Can't create new swatch in palette (Linux)
https://bugs.kde.org/show_bug.cgi?id=479091 LC Sharkey <9rtq7...@duck.com> changed: What|Removed |Added CC||9rtq7...@duck.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 479091] New: Can't create new swatch in palette (Linux)
https://bugs.kde.org/show_bug.cgi?id=479091 Bug ID: 479091 Summary: Can't create new swatch in palette (Linux) Classification: Applications Product: krita Version: 5.2.1 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: 9rtq7...@duck.com Target Milestone: --- Created attachment 164488 --> https://bugs.kde.org/attachment.cgi?id=164488=edit Text copied from bug report dialog. 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. Open Palette Editor; click button to "Add a swatch group." 2. Enter swatch group name; click "OK." 3. Click "OK" in Palette Editor dialog. 4. Click disk icon to save palette. 5. Close Krita; launch from 5.2.0 appimage and repeat 1-4. 6. Close Krita; launch from 5.1.5 appimage and repeat 1-4. OBSERVED RESULT Using krita-5.2.1-x86_64.appimage, the swatch group is not created. It does not show up in the Palette, and re-opening the Palette Editor shows that the new group does not exist. Using krita-5.2.0-x86_64.appimage gets same result as with 5.2.0. Using krita-5.1.5-x86_64.appimage works as expected; new swatch group is created and saved. EXPECTED RESULT The new swatch created should show up in the palette and should be visible in the Palette editor. SOFTWARE/OS VERSIONS Linux: Pop!_OS 22.04 LTS 64-bit; GNOME v. 42.9; X11 (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: N/A Qt Version: 5.15.7 ADDITIONAL INFORMATION See attached file for text box data from bug submission dialog (tried to paste here but it's too long). -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 462512] [NVIDIA] Missing sensor information after driver update
https://bugs.kde.org/show_bug.cgi?id=462512 LC changed: What|Removed |Added Ever confirmed|1 |0 CC||luochen1...@gmail.com Status|RESOLVED|REPORTED Resolution|FIXED |--- --- Comment #35 from LC --- Still have this issue: - GPU 1 Frequency: 0 HHz - GPU 1 Temperature: 0 - GPU 1 Usage: 0% - GPU 1 Video Memory Used: "" (Nothing displayed) - GPU1 Total Video Memory: 56.0 GiB $ neofetch --stdout OS: NixOS 23.11.20230706.3c74875 (Tapir) x86_64 Host: ASUSTeK COMPUTER INC. TUF GAMING X670E-PLUS Kernel: 6.4.1 Uptime: 52 mins Packages: 3368 (nix-system), 217 (nix-user) Shell: zsh 5.9 Resolution: 3840x2160 DE: Plasma 5.27.6 WM: KWin Icons: Papirus-Dark [GTK2/3] Terminal: .konsole-wrappe CPU: AMD Ryzen 9 7950X (32) @ 4.500GHz GPU: NVIDIA GeForce RTX 4090 Memory: 8596MiB / 64033MiB -- You are receiving this mail because: You are watching all bug changes.
[calligrachart] [Bug 46251] Legend not completely visible
https://bugs.kde.org/show_bug.cgi?id=46251 LC changed: What|Removed |Added CC||luochen1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 469491] https://kde.org/nl/announcements/gear/23.04.0/ Who is responsable for this?
https://bugs.kde.org/show_bug.cgi?id=469491 --- Comment #5 from LC --- Blijkbaar is er geen .po bestand van de tekst op de website beschikbaar. Waar staat de te vertalen tekst of beter nog waar staat de nederlandse vertaling? Wellicht heb je langs deze weg extra hulp gekregen om op zijn minst de tekst op de website nog beter te vertalen. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 469491] https://kde.org/nl/announcements/gear/23.04.0/ Who is responsable for this?
https://bugs.kde.org/show_bug.cgi?id=469491 LC changed: What|Removed |Added CC||luc.casterm...@gmail.com --- Comment #3 from LC --- This bug report cannot be specific about the text to be translated. It states that available translations appear to be automatically generated. If that is the case, then after a first manual correction of a text the subsequent one, automatic again, will contain again errors as the overall process was not changed! If translations are done automatically it might be needed to change the process and install a review/update of the translated text before it is actually published. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 463159] editor screen does not show text or is frozen
https://bugs.kde.org/show_bug.cgi?id=463159 --- Comment #1 from LC --- this is duplicate of 461189; you might close this one -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 461189] content of file to be translated is not shown
https://bugs.kde.org/show_bug.cgi?id=461189 --- Comment #6 from LC --- (In reply to Simon Depiets from comment #5) > (In reply to Luigi Toscano from comment #4) > > But this is not about wayland, I see the issue on X11. > > You are correct... > Does your layout also gets broken when you just open/close > project/translation-memory tabs without opening an actual file? > > The nightly build works fine on Windows with kde FW 5.99/qt 5.15.5 so that > looks system specific. > @LC Which distro are you using? Debian. I have seen this bug since many months (summer 2022). I am on experimental/sid/testing -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 463159] New: editor screen does not show text or is frozen
https://bugs.kde.org/show_bug.cgi?id=463159 Bug ID: 463159 Summary: editor screen does not show text or is frozen Classification: Applications Product: lokalize Version: 22.12.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: editor Assignee: sdepi...@gmail.com Reporter: luc.casterm...@gmail.com CC: sha...@ukr.net Target Milestone: --- 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. open a text 2. open another text OBSERVED RESULT text in window1 can be edited text in window 2 cannot be edited or is not even shown EXPECTED RESULT text should be editable in both windows independently from each other. THis is basic functionality. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.16.6 ADDITIONAL INFORMATION I observed this behaviour on ALL previous versions, from approximately summer 2022 onwards -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 461189] New: content of file to be translated is not shown
https://bugs.kde.org/show_bug.cgi?id=461189 Bug ID: 461189 Summary: content of file to be translated is not shown Classification: Applications Product: lokalize Version: 21.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: sdepi...@gmail.com Reporter: luc.casterm...@gmail.com CC: sha...@ukr.net Target Milestone: --- 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. start Lokalize 2. 3. OBSERVED RESULT Lokalize opens The project overview tab opens The translation memory tab opens The tab in which a to-be-translated-file can be opened, but the content is not shown/drawn EXPECTED RESULT The to-be-translated-file should be visible SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457236] Adaptive in plasma_shell_org.kde.plasma.desktop.pot appears to behave as Automatic
https://bugs.kde.org/show_bug.cgi?id=457236 LC changed: What|Removed |Added CC||luc.casterm...@gmail.com --- Comment #2 from LC --- I'd translate "adaptive" with "aanpasbaar" too. Where I as a user would interpret it that I, as a user, would be able to adapt/change certain settings my self. Latter seems not to be the case. Which to me means that "adaptive" is wrong. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 450909] It takes very long for translated work to get to the user
https://bugs.kde.org/show_bug.cgi?id=450909 LC changed: What|Removed |Added CC||luc.casterm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
