[kwin] [Bug 451301] Kate crashes when opening a file while save file dialog is open
https://bugs.kde.org/show_bug.cgi?id=451301 --- Comment #12 from tux --- (In reply to David Edmundson from comment #11) > This bug is a crash report that is over a year old without any activity, as > our software is always changing, the information in this ticket is unlikely > to still be useful. > > If this issue is still reproducible in a newer version of kwin (5.27.5 or > 6.0) please reopen this ticket with a bumped version number or it will be > closed in 30 days. The crash does not seem to happen anymore with kwin 6.0 (wayland) on my system. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447498] Minor issue, Android app says battery information not available
https://bugs.kde.org/show_bug.cgi?id=447498 Tux changed: What|Removed |Added CC||not-a-peng...@tutanota.com --- Comment #1 from Tux --- Created attachment 147941 --> https://bugs.kde.org/attachment.cgi?id=147941&action=edit connect indicator screenshot (no data, -1% reported) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447498] Minor issue, Android app says battery information not available
https://bugs.kde.org/show_bug.cgi?id=447498 --- Comment #2 from Tux --- Comment on attachment 147941 --> https://bugs.kde.org/attachment.cgi?id=147941 connect indicator screenshot (no data, -1% reported) Same thing here with Android 10 (Oppo Color OS flavour, unsure if that is the cause or not, I can't change or try any other phone OS right now) and KDEConnect on Arch on the other side. So far the same notification appears on the phone and and no battery usage % is displayed at all on the computer side, neither on the qt app, kde cli or Gconnect (which doesn't really matter here, but I tested it too). https://i.imgur.com/s4qFxO6.png d’abr. 03 20:45:31 honk-a-tron kdeconnectd[1827]: no pair requests to accept! d’abr. 03 20:46:06 honk-a-tron kdeconnectd[1827]: kdeconnect.plugin.contacts: handleResponseVCards: Unable to open "/home/tux/.local/share/kpeoplevcard/kdeconnect-009186294aa5a9f4/3047i55a861> d’abr. 03 20:46:28 honk-a-tron kdeconnectd[1827]: kdeconnect.plugin.battery: No Primary Battery detected on this system. This may be a bug. d’abr. 03 20:46:28 honk-a-tron kdeconnectd[1827]: kdeconnect.plugin.battery: Total quantity of batteries found: 0 d’abr. 03 20:46:28 honk-a-tron kdeconnectd[1827]: kdeconnect.plugin.contacts: handleResponseVCards: Unable to open "/home/tux/.local/share/kpeoplevcard/kdeconnect-009186294aa5a9f4/3047i55a861> d’abr. 03 20:46:36 honk-a-tron kcmshell5[197882]: qt.svg: Cannot open file ':/icons/kdeconnect/kdeconnect.svg', because: No such file or directory d’abr. 03 20:46:36 honk-a-tron kcmshell5[197882]: qt.svg: Cannot open file ':/icons/kdeconnect/kdeconnect.svg', because: No such file or directory d’abr. 03 20:46:54 honk-a-tron drkonqi[197949]: QSystemTrayIcon::setVisible: No Icon set -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447498] Minor issue, Android app says battery information not available
https://bugs.kde.org/show_bug.cgi?id=447498 --- Comment #3 from Tux --- Comment on attachment 147941 --> https://bugs.kde.org/attachment.cgi?id=147941 connect indicator screenshot (no data, -1% reported) Operating System: Arch KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-1-lts (64-bit) Graphics Platform: X11 Processors: 4 × AMD Ryzen 3 2200G with Radeon Vega Graphics Memory: 19,5 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490526] Touchpad settings are unaccessible, blank screen
https://bugs.kde.org/show_bug.cgi?id=490526 tux changed: What|Removed |Added CC||t...@nijstekje.nl --- Comment #19 from tux --- Workaround command: kcmshell6 kcm_touchpad -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488326] Opening System Settings to Mouse or Networks KCM breaks other pages afterwards: InlineMessage.qml:123 Cannot assign object of type "TP.IconPropertiesGroup" to property of
https://bugs.kde.org/show_bug.cgi?id=488326 tux changed: What|Removed |Added CC||t...@nijstekje.nl --- Comment #93 from tux --- Workaround command for missing touchpad settings: kcmshell6 kcm_touchpad -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370206] KScreenlocker not unlockable after switching to new session
https://bugs.kde.org/show_bug.cgi?id=370206 Tux changed: What|Removed |Added CC||tuxg...@gmail.com --- Comment #3 from Tux --- I have the same problem on multiple computers running kubuntu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497658] New: Clipboard doesn't load
https://bugs.kde.org/show_bug.cgi?id=497658 Bug ID: 497658 Summary: Clipboard doesn't load Classification: Plasma Product: plasmashell Version: 6.2.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard widget & pop-up Assignee: plasma-b...@kde.org Reporter: t...@nijstekje.nl Target Milestone: 1.0 SUMMARY Clipboard doesn't load after update on Arch Linux. STEPS TO REPRODUCE 1. Click clipboard widget 2. Observe error message OBSERVED RESULT "Sorry! There was an error loading Clipboard." "file:///usr/share/plasma/plasmoids/org.kde.plasma.clipboard/contents/ui/main.qml:122:26: Type Private.ClipboardMenu unavailable qrc:/qt/qml/org/kde/plasma/private/clipboard/ClipboardMenu.qml:209:9: QtLabsModel.DelegateChoice is not a type" EXPECTED RESULT Clipboard loading/working as normal. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.0 Qt Version: 6.9.0 Kernel Version: 6.12.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600 6-Core Processor Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 6650 XT -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 500903] DdeLink bookmarks are created in LibreOffice Writer when copying text to the clipboard
https://bugs.kde.org/show_bug.cgi?id=500903 tux changed: What|Removed |Added CC||t...@nijstekje.nl --- Comment #1 from tux --- I've been affected with this too on KDE 6.3.2 A fresh/new LibreOffice profile doesn't help. A way to make it less annoying is to disable "Field Shadings" in the "View" menu, so you at least don't see the marks. And before saving or sharing a file, you can go to "Insert" -> "Bookmark..." and delete everything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500903] In LibreOffice Writer, DdeLink bookmarks are created in the document when copying text to the clipboard
https://bugs.kde.org/show_bug.cgi?id=500903 --- Comment #6 from tux --- (In reply to Fushan Wen from comment #5) > I am not sure if this is a bug: > https://ask.libreoffice.org/t/libreoffice-writer-automatic-bookmark-creation- > while-keyboard-maestro-engine-is-running/97599/2 That's on MacOS when running the MacOS program "Keyboard Maestro", so not relevant here on Linux. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 502331] New: Ark cannot load Zstandard (zstd) archives compressed with --long=28 or higher
https://bugs.kde.org/show_bug.cgi?id=502331 Bug ID: 502331 Summary: Ark cannot load Zstandard (zstd) archives compressed with --long=28 or higher Classification: Applications Product: ark Version: 25.03.90 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: t...@nijstekje.nl CC: rthoms...@gmail.com Target Milestone: --- SUMMARY Ark cannot load Zstandard (zstd) archives that are compressed with `--long=28` (or higher). The command line tool `zstd` also throws an error that "Frame requires too much memory for decoding" when just doing `zstd -d file.tar.zst`, but passing `--long=...` to the decompression command works fine (e.g. `zstd --long=28 -d file.tar.zst`). The `--long=28` (or higher) option is useful for most desktop/laptop users, because it can significantly enhance compression on folders/file whose size is over 100 MB at the cost of some (trivial amount of) memory and a very small increase in compression time. I also think that `--long` should be enabled by default in Ark when compressing to zstd, because it can significantly enhance compression at almost no speed cost. For example, compressing the 1326 MiB GE-Proton9-27 folder at level 15 yields an archive of 385 MiB in 14 seconds, but just 283 MiB in 15 seconds when `--long=29` is used. That's 102 MiB less for just one extra second. To achieve a similar compression without using `--long`, the compression level needs to be increased to level 21 which takes 84 seconds (and even then the archive is still larger at 288 MiB). As `--long` is the same as `--long=27` and corresponds to 128M of memory it would be the safest default, but `--long=28` at 256M or `--long=29` at 512M are good defaults too, considering that most desktop/laptop users have at least 8 GB of system memory. STEPS TO REPRODUCE 1. Create zstd archive with `--long=28` (or higher, up to 31). 2. Try to open archive with Ark. OBSERVED RESULT The following error is shown: `Loading the archive ‘file.tar.zst’ failed with the following error: Archive corrupted or insufficient permissions.` EXPECTED RESULT The archive gets loaded and can be used/extracted. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.9.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 371689] New: If "main display" is not set to monitor 1, pen pressure breaks
https://bugs.kde.org/show_bug.cgi?id=371689 Bug ID: 371689 Summary: If "main display" is not set to monitor 1, pen pressure breaks Product: krita Version: 3.1 Beta Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: tuxedonrangerprow...@gmail.com Target Milestone: --- Created attachment 101787 --> https://bugs.kde.org/attachment.cgi?id=101787&action=edit Shows the display numbers, what the main display is set to, and the pen pressure problem. Also current with 3.0.11 If your main display is set to anything except the first monitor detected by the graphics driver, then Krita will not detect pen pressure properly and will lag as if it's working with the mouse. This is not the fault of the tablet driver itself. Using the pen pressure test program reveals that pen pressure is fine with non-primary main displays. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408645] Look and Feel workspace theme not showing installed themes
https://bugs.kde.org/show_bug.cgi?id=408645 Killer Tux changed: What|Removed |Added CC||killer...@outlook.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432606] New: Installing new look and feel/mouse themes didn't work
https://bugs.kde.org/show_bug.cgi?id=432606 Bug ID: 432606 Summary: Installing new look and feel/mouse themes didn't work Product: systemsettings Version: 5.19.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: killer...@outlook.de Target Milestone: --- Created attachment 135481 --> https://bugs.kde.org/attachment.cgi?id=135481&action=edit Two screenshots of the problem Installing new look and feel/mouse themes didn't work STEPS TO REPRODUCE 1. Install new cursors 2. After five or so no new cursors will be shown No new cursors will be shown All cursors would be in the overview, not only in "install new cursors" SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-41-generic OS Type: 64-bit Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 7.3 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 432606] Installing new look and feel/mouse themes didn't work
https://bugs.kde.org/show_bug.cgi?id=432606 --- Comment #2 from Killer Tux --- (In reply to Nate Graham from comment #1) > Very likely fixed by a newer version. Any chance you can test again with > Frameworks 5.78 or a more recent version? Thanks! Actually I could, but sadly I don't know how to force an update to the newest version of KDE-Frameworks. Could You please explain it to me in a few steps (if not, I'm going to search the internet, but I don't know whether it's true or false and I don't want to destroy my system...) Thanks in advance! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471532] New: Unable to drag anything from Project Bin
https://bugs.kde.org/show_bug.cgi?id=471532 Bug ID: 471532 Summary: Unable to drag anything from Project Bin Classification: Applications Product: kdenlive Version: 23.04.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ruffian_...@hotmail.com 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. Add any file to Project Bin 2. Attempt to click and drag any file from Project Bin to Timeline. 3. OBSERVED RESULT Feature does not function. File will not move and, instead, shows a circle with a line through it on the cursor. EXPECTED RESULT File will move from Project Bin to Timeline SOFTWARE/OS VERSIONS Windows: 10 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.
[kdenlive] [Bug 471532] Unable to drag anything from Project Bin
https://bugs.kde.org/show_bug.cgi?id=471532 --- Comment #1 from Ruffian Tux --- I have attempted to reinstall the software, have tried the standalone version, and have tried to remove the kdenliverc file but found that it did not exist. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363627] New: Drop-down menu from access bar is invisible in full-screen mode when a document is loaded/present.
https://bugs.kde.org/show_bug.cgi?id=363627 Bug ID: 363627 Summary: Drop-down menu from access bar is invisible in full-screen mode when a document is loaded/present. Product: krita Version: 3.0 Release Candidate Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: tuxedonrangerprow...@gmail.com If you're in full screen mode and you try to access the drop-down menu. You can still interact with them, but they won't be visible. This appears to be an OpenGL mode only problem from how I tested. Reproducible: Sometimes Steps to Reproduce: 1. Make sure OpenGL is active. 2. New/Load document 3. Go full screen 4. Click any option in the menu bar at the top of the program. Actual Results: No drop down menu visible. Can still interact with drop-down menu. Expected Results: Show the drop-down menu. OS: Windows 10 GPU: nVidia GeForce GTX 750 Ti -- You are receiving this mail because: You are watching all bug changes.