[dolphin] [Bug 196772] Dolphin tree view needs method to expand and collapse all/selected nodes
https://bugs.kde.org/show_bug.cgi?id=196772 --- Comment #12 from Bill Werrel --- The left/right arrow shortcuts for expand/collapse in 23.04.02 work great. It would good to also get a short cut for "expand all", and to make the keyboard shortcuts configurable. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 469829] PDF file size increases exponentially after typing in text using the Typewriter tool and Highlighter
https://bugs.kde.org/show_bug.cgi?id=469829 --- Comment #6 from alstjr7...@daum.net --- Thank you!! It seems that the font is only embedded once. (Keep in 2MB) I think it has been solved now. After the update, the package version is as follows: ``` poppler 23.06.0-1 poppler-data 0.4.12-1 poppler-glib 23.06.0-1 poppler-qt5 23.06.0-1 ``` -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471058] Tags not shown for all items after export-import
https://bugs.kde.org/show_bug.cgi?id=471058 --- Comment #14 from Jan van Bekkum --- Hi Mike, The ones for which I did a reread on computer A before export, correctly show tags and labels on computer B, but also the 5 stars that appeared on computer A after the reread. Jan -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471100] Google voice typing doesn't work
https://bugs.kde.org/show_bug.cgi?id=471100 --- Comment #1 from Adam --- Just editing step 1 for clarity: STEPS TO REPRODUCE 1. On the android kde connect app, Click remote input and choose the keyboard. Any keyboard (eg swiftkey or gboard or google voice typing) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471100] New: Google voice typing doesn't work
https://bugs.kde.org/show_bug.cgi?id=471100 Bug ID: 471100 Summary: Google voice typing doesn't work Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: a...@adamlove.com.au CC: andrew.g.r.hol...@gmail.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 *** KDE connect remote input won't allow me to send voice typing from my phone to my computer STEPS TO REPRODUCE 1. Click remote input and choose a keyboard 2. Click on a text box in my computer browser or any other section that will allow text input 3. Any keyboard I choose, be it gboard or swift key or Google voice import will redirect me to the same Google voice recording keyboard. It seems like this Google voice recording keyboard isn't sending key strokes, perhaps it's sending whole words which aren't recognised by the computer as text input OBSERVED RESULT Nothing is received EXPECTED RESULT Text input SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 22.04 KDE plasma version 5.2 4.7 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.92.0 Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457370] Task manager causes Plasma to hang with heavy usage
https://bugs.kde.org/show_bug.cgi?id=457370 --- Comment #20 from David Chmelik --- Good: no longer seems to be a problem, and is duplicate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432697] Quick re-login causes ACPI ERRORs and a broken plasma session.
https://bugs.kde.org/show_bug.cgi?id=432697 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468506] Copied content not pasting on newly-opened applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=468506 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 469857] Kasts->Settings reports nothing
https://bugs.kde.org/show_bug.cgi?id=469857 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429826] Plasma/OpenSuse Logout / Login crashing regularly
https://bugs.kde.org/show_bug.cgi?id=429826 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441591] Switching user sometimes results in frozen UI
https://bugs.kde.org/show_bug.cgi?id=441591 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469888] Crash during screensharing
https://bugs.kde.org/show_bug.cgi?id=469888 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469849] Containment missing on login with laptop screen disabled and external screen as the only active one until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=469849 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469869] [regression] KCM_SDDM Crashes Utilizing over 100% CPU
https://bugs.kde.org/show_bug.cgi?id=469869 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468506] Copied content not pasting on newly-opened applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=468506 Joseph DeGarmo changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468506] Copied content not pasting on newly-opened applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=468506 --- Comment #10 from Joseph DeGarmo --- Also happens in Debian 12. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464378] [Recorder] All artworks created from the same template ends into the same recorded directory
https://bugs.kde.org/show_bug.cgi?id=464378 Bug Janitor Service changed: What|Removed |Added Resolution|FIXED |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 465247] Kdenlive (appimage) wont start on Linux Mint 20.3
https://bugs.kde.org/show_bug.cgi?id=465247 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469814] Rectangular region screenshot includes Spectacle window
https://bugs.kde.org/show_bug.cgi?id=469814 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406690] ksmserver crashes when resuming from suspend, if kiosk mode is used
https://bugs.kde.org/show_bug.cgi?id=406690 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424565] Okteta uses dark text color on a dark background
https://bugs.kde.org/show_bug.cgi?id=424565 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376728] Global Menu does not reappear for windows on session restore because appmenu kded module isn't loaded yet by the time the app launches
https://bugs.kde.org/show_bug.cgi?id=376728 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #14 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451702] Various KDE apps lock up with 100% CPU usage when monitor powers off
https://bugs.kde.org/show_bug.cgi?id=451702 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467632] Window appears blank until resize or restart plasmashell
https://bugs.kde.org/show_bug.cgi?id=467632 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466414] Plasmashell and kwin_wayland processes peak in Wayland, but only when no windows are drawn
https://bugs.kde.org/show_bug.cgi?id=466414 --- Comment #13 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466764] 16:10 resolution broken on Wayland with Nvidia
https://bugs.kde.org/show_bug.cgi?id=466764 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450069] Plasma 5.24 freezes/black screen on wake from sleep
https://bugs.kde.org/show_bug.cgi?id=450069 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448310] Cursor sometimes slow after shutting lid
https://bugs.kde.org/show_bug.cgi?id=448310 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 464954] Dictionary search uses the network without any indication of this
https://bugs.kde.org/show_bug.cgi?id=464954 Bacteria changed: What|Removed |Added CC||dev.bacterios...@aleeas.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470927] Plasma panel items all on the left
https://bugs.kde.org/show_bug.cgi?id=470927 --- Comment #6 from Stephen.Gear007 --- Have tried developer edition. This worked normal panel. So this morning I downloaded unstable 1508 iso and it's the same as before the panel is all to the left. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471099] New: Tags can't be renamed nor be deleted
https://bugs.kde.org/show_bug.cgi?id=471099 Bug ID: 471099 Summary: Tags can't be renamed nor be deleted Classification: Applications Product: dolphin Version: 23.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: deanrikrikichsanhakiki+kde...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY My Dolphin now has 2 tags that can't be renamed nor deleted, opening Dolphin through the terminal doesn't show any meaning full log (doesn't show any log at all in the process of renaming or deleting the tags), except `kf.kio.workers.tags: "tags:/Test" stat() invalid url`, when trying to open the "tag folder", `Test` here is what the Tag should be renamed to, not the original/previous name. STEPS TO REPRODUCE - Select a file - Click `Add` on the tag section on the preview/information panel (the panel on the right side of the dolphin) - Add multiple tags in quick succession - Notice that (at least in my case) after a while, the `Tags` section on the left side of the Dolphin shows "All Tags", "Tags 1", and "Tags 2" (in my case) but not the other/rest of the tags I added to the previous file. - Adjust the previous file's tag by removing every tag first, close the tag dialog for the file, then click `Add` again on the file info - Notice that (at least in my case) available tags are only the "Tags 1" and "Tags 2", the previously added tag has gone - Add the remaining tags to the file, close the dialog afterwards - Click the `Edit` on the tag section of the file info again (modify the file tag) - Remove every tag from the file, close the dialog afterwards - Note that (at least in my case) the two tags still remain, even though there's no file in the whole system that uses that tag - Now either try to delete or rename the actual tag (not the Tags section on the left of the dolphin) - Refresh (F5) after doing so - Note that (at least in my case) the tags are neither got renamed nor deleted OBSERVED RESULT - No tag is being renamed or deleted. EXPECTED RESULT - The tag should be renamed or deleted. SOFTWARE/OS VERSIONS Linux/KDE Plasma: - KDE Plasma Version: 5.27.5 - KDE Frameworks Version: 5.106.0 - Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471084] Improve Focus Timecode time input to make it faster.
https://bugs.kde.org/show_bug.cgi?id=471084 --- Comment #1 from Gabriel Gazzán --- Another variants possible I forgot to mention above: [digits typed --> resulting timecode] 1 --> 00:00:00:01 3: --> 00:00:03:00 2:: --> 00:02:00:00 1:15: --> 00:00:01:15:00 115: --> 00:00:01:15:00 etc... or in additive/subtractive form: [current time = 00:05:20:10] +15: --> 00:05:35:10 -15: --> 00:05:05:10 etc... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 429933] "Often played" and "recently played" section do not work correctly when Baloo indexing is disabled
https://bugs.kde.org/show_bug.cgi?id=429933 Nate Graham changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #6 from Nate Graham --- Yeah what was I thinking, this should work fine without Baloo and it does for me. Postix, can you still reproduce the issue? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471098] Crash bei "Iris Box"
https://bugs.kde.org/show_bug.cgi?id=471098 --- Comment #2 from fehler-im-progr...@posteo.de --- Created attachment 159707 --> https://bugs.kde.org/attachment.cgi?id=159707=edit Iris Box (broken Preview, before Crash) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444489] [Wayland] Kickoff launches dragged-and-dropped favorite when I click on any part of it
https://bugs.kde.org/show_bug.cgi?id=89 Nate Graham changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #16 from Nate Graham --- Can confirm, it's fixed in 6! We didn't make any code changes on our side here, which means it must have been an upstream Qt issue all along that we unwittingly exposed ourselves to with the big Kickoff refactor in 5.23. Nice that it's fixed in Qt 6. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471098] Crash bei "Iris Box"
https://bugs.kde.org/show_bug.cgi?id=471098 --- Comment #1 from fehler-im-progr...@posteo.de --- Created attachment 159706 --> https://bugs.kde.org/attachment.cgi?id=159706=edit Example clip for project file "Bug-Crash-Iris Box.kdenlive" -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471098] New: Crash bei "Iris Box"
https://bugs.kde.org/show_bug.cgi?id=471098 Bug ID: 471098 Summary: Crash bei "Iris Box" Classification: Applications Product: kdenlive Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: fehler-im-progr...@posteo.de Target Milestone: --- Created attachment 159705 --> https://bugs.kde.org/attachment.cgi?id=159705=edit Crash at "Iris Box" 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. Insert a Clip 2. Insert "Wipe - Iris Box" 3. Play OBSERVED RESULT Preview "broken" - then crash EXPECTED RESULT Effect "Iris Box" 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.
[systemsettings] [Bug 470629] Unable to configure "ContentType" drm property
https://bugs.kde.org/show_bug.cgi?id=470629 --- Comment #7 from NW --- Hi, Thanks for clarifying the default behavior of KDE Plasma. Is it documented somewhere since when KDE Plasma defaults to this behavior and why this behavior was made the default? The bug report would still be valid, since it is reporting that there is no UI option for users to alter the default behavior. And with Wayland, users would also not be able to alter the behavior via the terminal (please feel free to correct if wrong). (In reply to Zamundaaa from comment #6) > Yes, apps can specify a content type for their window. For that reason I do > not think that a setting for this makes sense, as media players will change > the TV into the "video" mode as appropriate. That would be outside of KDE Plasma's control though? Because not all media player apps are part of KDE Plasma. And as such, KDE Plasma can not ensure that all media players will behave this way, right? Is there a known list of apps which change the content type on their own? Not every user might want the TV to automatically switch from one mode to another mode just because an app decides to do so. Whereas some users might be fine with that. As such, adding a drop-down, which allows users to set the content type, would be preferrable. That said: Perhaps KDE Plasma's current default behavior could be retained and could be named "Automatic" on the new "Content Type" drop-down in "System Settings -> Display and Monitor -> Display Configuration"? That way the "Content Type" drop-down would allow to choose from: * Automatic * None * Graphics * Photo * Cinema * Game Would that work? And would selecting a specific content type from that drop-down (other than Automatic) prevent apps from changing the content type? Or would apps still be able to change the content type on their own, even if the user has selected a specific content type from that drop-down? Regards -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467945] Shapes: converting nodes to corner/smooth/symmetric works only in the last opened document
https://bugs.kde.org/show_bug.cgi?id=467945 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1826 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 471097] New: GPU, VRAM and RAM Usage Most broken (Nvidia)
https://bugs.kde.org/show_bug.cgi?id=471097 Bug ID: 471097 Summary: GPU, VRAM and RAM Usage Most broken (Nvidia) Classification: Applications Product: plasma-systemmonitor Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: theatt...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 159704 --> https://bugs.kde.org/attachment.cgi?id=159704=edit You can see that the usage is zero SUMMARY *** This happened once before. I have a 3060 12 GB. Its VRAM and Usage is not being reported by System Monitor. It is at 0 right now. Ram Usage is also incorrect, as Htop and System Monitor results are not the same. Can't tell much about my Ram, but I am glad to help in anyway *** STEPS TO REPRODUCE 1. Set System Monitor to display GPU Usage and VRAM Usage by editing page 2. Observe the result OBSERVED RESULT VRAM and GPU Usage appears 0% EXPECTED RESULT System Monior should display the correct GPU and VRAM usage. Ram usage is also incorrect if I am to consider Htops result. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Endeavor OS (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471096] Icons on desktop have the selection marker
https://bugs.kde.org/show_bug.cgi?id=471096 Patrick Silva changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471096] New: Icons on desktop have the selection marker
https://bugs.kde.org/show_bug.cgi?id=471096 Bug ID: 471096 Summary: Icons on desktop have the selection marker Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com CC: h...@kde.org Target Milestone: 1.0 Created attachment 159703 --> https://bugs.kde.org/attachment.cgi?id=159703=edit screenshot STEPS TO REPRODUCE 1. hover over any icon on desktop 2. 3. OBSERVED RESULT the selection marker overlaps the icon on desktop. Please see the attached screenshot. EXPECTED RESULT no selection marker SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 471095] "Could not find the program '/qdbus'" error message when trying to take a screenshot via context menu from Spectacle icon
https://bugs.kde.org/show_bug.cgi?id=471095 Patrick Silva changed: What|Removed |Added Summary|Error message when trying |"Could not find the program |to take a screenshot via|'/qdbus'" error message |context menu from Spectacle |when trying to take a |icon|screenshot via context menu ||from Spectacle icon Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 471095] New: Error message when trying to take a screenshot via context menu from Spectacle icon
https://bugs.kde.org/show_bug.cgi?id=471095 Bug ID: 471095 Summary: Error message when trying to take a screenshot via context menu from Spectacle icon Classification: Applications Product: Spectacle Version: git-master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: bugsefor...@gmx.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 159702 --> https://bugs.kde.org/attachment.cgi?id=159702=edit screenshot STEPS TO REPRODUCE 1. add Spectacle icon to desktop 2. right-click on the icon added to desktop and choose some option used to take a screenshot 3. OBSERVED RESULT error message seen in the attached screenshot EXPECTED RESULT no error SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471058] Tags not shown for all items after export-import
https://bugs.kde.org/show_bug.cgi?id=471058 --- Comment #13 from Jan van Bekkum --- The missing metadata is always added. I made an error resetting options after I did some experiments. However, I noticed that when I do a reread 5 stars are added. The stars are not in the metadata (see below). ?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?> http://www.w3.org/1999/02/22-rdf-syntax-ns#;> http://www.video/; xmlns:xmpDM="http://ns.adobe.com/xmp/1.0/DynamicMedia/; xmlns:audio="http://www.audio/; xmlns:exif="http://ns.adobe.com/exif/1.0/; xmlns:tiff="http://ns.adobe.com/tiff/1.0/; xmlns:xmp="http://ns.adobe.com/xap/1.0/; xmlns:acdsee="http://ns.acdsee.com/iptc/1.0/; xmlns:digiKam="http://www.digikam.org/ns/1.0/; xmlns:MicrosoftPhoto="http://ns.microsoft.com/photo/1.0/; xmlns:lr="http://ns.adobe.com/lightroom/1.0/; xmlns:mediapro="http://ns.iview-multimedia.com/mediapro/1.0/; xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/; xmlns:dc="http://purl.org/dc/elements/1.1/; video:duration="22522" video:MaxBitRate="194447326" video:StreamCount="3" video:Codec="hevc" video:CodecDescription="H.265 / HEVC (High Efficiency Video Coding)" video:Format="yuv420p10le" video:ColorMode="bt709" video:ColorSpace="CCIR-709" video:Width="3840" video:FrameWidth="3840" video:SourceImageWidth="3840" video:Height="2160" video:FrameHeight="2160" video:SourceImageHeight="2160" video:FrameSize="w:3840, h:2160, unit:pixels" video:AspectRatio="16/9" video:FrameRate="59.9401" video:BitDepth="24" video:Language="eng" video:TrackCreateDate="3761817978" video:MajorBrand="qt " video:CompatibleBrands="qt pana" video:MinorVersion="537986816" video:DateTimeOriginal="2023-03-16T12:26:18" video:DateUTC="2023-03-16T12:26:18" video:ModificationDate="2023-03-16T12:26:18" video:DateTimeDigitized="2023-03-16T12:26:18" video:FileName="A001C192_230316_DJ0B.MOV" video:FileSize="522" video:FileType="MOV" video:MimeType="video/quicktime" xmpDM:duration="22522" xmpDM:videoColorSpace="CCIR-709" xmpDM:videoFrameSize="w:3840, h:2160, unit:pixels" xmpDM:videoPixelAspectRatio="16/9" xmpDM:videoFrameRate="Other" xmpDM:videoPixelDepth="Other" xmpDM:shotDate="Thu Mar 16 13:26:18 2023" xmpDM:audioSampleRate="48000" xmpDM:audioChannelType="Stereo" xmpDM:audioSampleType="32Int" audio:Codec="pcm_s24be" audio:CodecDescription="PCM signed 24-bit big-endian" audio:SampleRate="48000" audio:ChannelType="Stereo" audio:Format="s32" audio:SampleType="32Int" audio:TrackLang="eng" audio:TrackCreateDate="3761817978" exif:DateTimeOriginal="2023-03-16T12:26:18" exif:DateTimeDigitized="2023-03-16T12:26:18" exif:ExifVersion="0232" exif:FlashpixVersion="0100" exif:ColorSpace="65535" exif:PixelXDimension="3840" exif:PixelYDimension="2160" tiff:DateTime="2023-03-16T12:26:18" tiff:ImageWidth="3840" tiff:ImageLength="2160" tiff:YCbCrPositioning="1" tiff:XResolution="72/1" tiff:YResolution="72/1" tiff:ResolutionUnit="2" tiff:Model="HC-X1500" xmp:MetadataDate="2023-03-16T12:26:18" xmp:Label="Red" xmp:ModifyDate="2023-03-16T12:26:18" xmp:CreateDate="2023-03-16T12:26:18" acdsee:categories="CategoriesCategory Assigned=0ProjectsCategory Assigned=0HCC-ZOB Videogroep HelmondCategory Assigned=12023-01 - Kleine DommelCategory Assigned=1316/CategoryCategory Assigned=1315/CategoryCategory Assigned=1314/Category/Category/Category/CategoryCategory Assigned=0LocatieCategory Assigned=1NederlandCategory Assigned=1Eindhoven/Category/Category/CategoryCategory Assigned=0RivierCategory Assigned=1Dommel/CategoryCategory Assigned=1Kleine Dommel/Category/CategoryCategory Assigned=0CameraCategory Assigned=1Panasonic HC-X1500Category Assigned=1Cine-V/Category/Category/Category/Categories" digiKam:ColorLabel="1" digiKam:PickLabel="1" photoshop:DateCreated="2023-03-16T12:26:18" photoshop:Urgency="1"> 1 2 3 0 Projects/HCC-ZOB Videogroep Helmond/2023-01 - Kleine Dommel/314 Locatie/Nederland/Eindhoven Rivier/Kleine Dommel Projects/HCC-ZOB Videogroep Helmond/2023-01 - Kleine Dommel/315 Rivier/Dommel Camera/Panasonic HC-X1500 Projects/HCC-ZOB Videogroep Helmond/2023-01 - Kleine Dommel Projects/HCC-ZOB Videogroep Helmond/2023-01 - Kleine Dommel/316 Camera/Panasonic HC-X1500/Cine-V Locatie/Nederland Projects/HCC-ZOB Videogroep Helmond/2023-01 - Kleine Dommel/314 Locatie/Nederland/Eindhoven Rivier/Kleine Dommel Projects/HCC-ZOB Videogroep Helmond/2023-01 - Kleine Dommel/315 Rivier/Dommel Camera/Panasonic HC-X1500 Projects/HCC-ZOB Videogroep Helmond/2023-01 - Kleine Dommel Projects/HCC-ZOB Videogroep Helmond/2023-01 - Kleine Dommel/316 Camera/Panasonic HC-X1500/Cine-V Locatie/Nederland
[systemsettings] [Bug 471093] Numpad shortcuts not recognised under Wayland / Regression
https://bugs.kde.org/show_bug.cgi?id=471093 --- Comment #1 from aplatypus --- Created attachment 159701 --> https://bugs.kde.org/attachment.cgi?id=159701=edit Short cut Export (save) failed * Unfortunately the 'Export Scheme' operation did not save a file. * I tried this several times, see second screenshot -- Showing that a find statement did not locate the exported file. * The Export/Save command did not show an error or report a problem. Perhaps the file is save someplace else -- But that should be reported or logged. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471067] Checkboxes have weird blurry look on them
https://bugs.kde.org/show_bug.cgi?id=471067 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #3 from Nate Graham --- Yeah, in the past we've seen that scrollable views can become pixel-misaligned; maybe that's what's happening here. If you do a two-finger touchpad scroll *very slowly* do the checkboxes look better and then worse again as you scroll? If you aren't using a laptop, clicking and dragging on the scrollbar may also work. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471067] Checkboxes have weird blurry look on them
https://bugs.kde.org/show_bug.cgi?id=471067 duha.b...@gmail.com changed: What|Removed |Added CC||duha.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471094] New: Be able to select panels without firing up any action in the process...
https://bugs.kde.org/show_bug.cgi?id=471094 Bug ID: 471094 Summary: Be able to select panels without firing up any action in the process... Classification: Applications Product: kdenlive Version: git-master Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY One thing that often gets in the way of a smooth workflow in Kdenlive is the fact that whenever you make a click to select a panel to make it the active/current one, something always happens right away. This often results in a distraction (caused by the fact that you have to revert the change made, or stop the action being executed without intention and the resume what you went to do initially), so I think it should be avoided whenever technically possible. OBSERVED RESULT Depending on where you make click you get: - Project Bin: the Clip Monitor goes to front, even when you haven't selected any clip in there. - Monitors: start reproducing the shown video. - Timeline empty space [Selection Tool active]: change the time cursor position to where you made the click, clicking on an empty space in any track or even where there's no track at all. - Timeline Clip/Wipes/Track: Effects Stack panel goes to front. (OK, I know this can be switched on/off in Preferences, and it's not a bad thing per se, but just something to take into account when organizing panels in the UI, so not to end up having a messy workflow. EXPECTED RESULT Be able to make click on a panel to making it current, without any action starting to happen immediately. Perhaps there's a way to do it and I don't know it yet, if that's the case my apologies. Thanks for listening! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471093] New: Numpad shortcuts not recognised under Wayland / Regression
https://bugs.kde.org/show_bug.cgi?id=471093 Bug ID: 471093 Summary: Numpad shortcuts not recognised under Wayland / Regression Classification: Applications Product: systemsettings Version: 5.27.4 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: plasma-b...@kde.org Reporter: william.full.m...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 159700 --> https://bugs.kde.org/attachment.cgi?id=159700=edit Screenshot of keyboard shortcuts SUMMARY STEPS TO REPRODUCE 1. I have used the shortcut pattern to switch to a virtual workspace of: Ctrl+Alt+Num+1, Ctrl+Alt+Num+2, etc to respectively switch to virtual workspace: 1, 2, etc for many years. 2. After upgrading to Kubuntu 23.04 I logged on using a Wayland session 3. My workspace change shortcut didn't work for workspace #1 (and other shortcuts). This is/was working under X-11 loging session on this installation. 4. I checked the KWin shortcuts and they are are set correctly. See screenshot for 'Ctrl+Alt+Num+3' example circled. This is how it works with Plasma X-11. 5. I then went to redefine the 'Ctrl+Alt+Num+1' (workspace 1) keystroke BUT they shortcut interface did NOT recognise 'Ctrl+Alt+Num+1' key pattern and instead recorded: 'Ctrl+Alt+1'. That is incorrect. 6. I checked this shortcut combination and 'Ctrl+Alt+1' matches BOTH the QWETY keyboard-1-key scan-code and the numpad-1-key scan-code. Unlike the X-11 session the Wayland session does not distinguish the numpad as a different set of keys (scan-codes). Sometimes the numpad is a completely different piece of hardware, so this is not what is desired. OBSERVED RESULT * The required: 'Ctrl+Alt+Num+1' does not register, and cannot be defined. * The existing (example) 'Ctrl+Alt+Num+3' is defined from the Kubuntu Plasma X-11 login on this PC * None of the currently defined workspace shortcuts work. * Instead the shortcut: 'Ctrl+Alt+Num+1' was recorded and uses the number keys on the QWERTY keyboard or the numpad 1-key -- Which is NOT desired. The keyboard 1-key is used for other things. EXPECTED RESULT * 'Ctrl+Alt+Num+1', 'Ctrl+Alt+Num+2' , 'Ctrl+Alt+Num+3' , ... 'Ctrl+Alt+Num+9' and 'Ctrl+Alt+Num+0', should be defined as distinct scancodes and work as defined with the existing X-11 settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.04 (available in About System) KDE Plasma Version: 5.27.4 (I think; The KDE ABOUT box does not display the Plasma release number) KDE Frameworks Version: No idea, where can I find that? Qt Version: v5 I believe ADDITIONAL INFORMATION * I have saved the shortcut definitions using they 'Export Scheme' button, alas the bug report only seems to permit a single attachmet. I will try to add someting later after filing this bug. * It seems by the list of 'possibly related' issues that came-up when I opened this bug that there are several cases where the numpad is being ignored or collapsed onto keyboard keys. * The thing with keystrokes, is that they match scan-codes, not characters. Often there are custome keypads or alternative controls 'wired' to the system that are do not at all match a keyboard -- Uses include custom terminals, machine control, virtual controls. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471092] Systray icon of apps in general does not appear anymore
https://bugs.kde.org/show_bug.cgi?id=471092 Patrick Silva changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471092] New: Systray icon of apps in general does not appear anymore
https://bugs.kde.org/show_bug.cgi?id=471092 Bug ID: 471092 Summary: Systray icon of apps in general does not appear anymore Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com CC: mate...@gmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. open any app with a systray icon, like Discord, OBS Studio, VLC player and others 2. observe the system tray 3. OBSERVED RESULT the icon of the app used in the step 1 does not appear in the system tray EXPECTED RESULT the systray icon appears in the system tray SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460397] Scale text may not fit into display view
https://bugs.kde.org/show_bug.cgi?id=460397 Nate Graham changed: What|Removed |Added Version|git-stable-Plasma/5.26 |5.26.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460397] Scale text may not fit into display view
https://bugs.kde.org/show_bug.cgi?id=460397 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kscreen/-/commit/5cf490f |ma/kscreen/-/commit/4614c0e |4b2c2532c236a6868a8524996f6 |72889f5e63f5e09a0aebd289630 |2d0328 |ed7634 --- Comment #8 from Nate Graham --- Git commit 4614c0e72889f5e63f5e09a0aebd289630ed7634 by Nate Graham, on behalf of Maxim S. Committed on 15/06/2023 at 21:09. Pushed by ngraham into branch 'Plasma/5.27'. Add boundaries to resolution text The text of the resolution with scale breaks in the middle of the number. I am adding ZWS (U+200B) that acts like word boundary so text can wrap nicely if there's not enough space. FIXED-IN: 5.27.6 (cherry picked from commit 5cf490f4b2c2532c236a6868a8524996f62d0328) M +1-1kcm/package/contents/ui/Output.qml https://invent.kde.org/plasma/kscreen/-/commit/4614c0e72889f5e63f5e09a0aebd289630ed7634 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460397] Scale text may not fit into display view
https://bugs.kde.org/show_bug.cgi?id=460397 Nate Graham changed: What|Removed |Added Version Fixed In|5.26.1 |5.27.6 Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kscreen/commit/fdbf6f8a0 |ma/kscreen/-/commit/5cf490f |06ebb7376927f02013f8c91bcda |4b2c2532c236a6868a8524996f6 |ba35|2d0328 --- Comment #7 from Nate Graham --- Git commit 5cf490f4b2c2532c236a6868a8524996f62d0328 by Nate Graham, on behalf of Maxim S. Committed on 15/06/2023 at 21:08. Pushed by ngraham into branch 'master'. Add boundaries to resolution text The text of the resolution with scale breaks in the middle of the number. I am adding ZWS (U+200B) that acts like word boundary so text can wrap nicely if there's not enough space. FIXED-IN: 5.27.6 M +1-1kcm/ui/Output.qml https://invent.kde.org/plasma/kscreen/-/commit/5cf490f4b2c2532c236a6868a8524996f62d0328 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471058] Tags not shown for all items after export-import
https://bugs.kde.org/show_bug.cgi?id=471058 --- Comment #12 from Maik Qualmann --- Does the missing metadata get added when you re-read the metadata via the Item menu? We already have a bug report from Windows users who report that not all metadata is always read, only after a re-read. The cause is unknown, I could never reproduce it. The cause could be a file locking by certain AntiVirus programs, Explorer or other. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 471061] Installation for /usr/local installs plugins into incorrect path
https://bugs.kde.org/show_bug.cgi?id=471061 --- Comment #4 from Cory F Cohen --- I agree with most of what Jack said. I was in fact trying to get a build that did not interfere with the distro-supplied version of KMyMoney, and I did "modify the build" from the defaults by specifying a non-standard installation prefix to accomplish that. I agree that tracking multiple library versions and so forth can be complicated and often requires some careful thought. Generally, I'm very cautious about building custom software and overwriting the installation in /usr as seems to be the default setting in the KMyMoney build. I implemented a "workaround" to meet my needs, which installed the modified prefix script as /usr/local/bin/kmymoney, and the executable as /usr/local/bin/kmymoney.bin (as some other packages have done). I just noticed that the debugging instructions suggest -DKDE_INSTALL_PREFIX_SCRIPT=ON, which curiously installs prefix.sh into /usr/local, but with permissions that only allow root to read the file, so it's not really a fix in my opinion. It's possible that the behavior requiring a script that is NOT installed (or is installed with restrictive permissions) is fairly standard for KDE applications, and that my expected behavior is somehow made more difficult to implement by aspects of the standard KDE build environment that I'm not familiar with. I am new to KMyMoney and KDE application development in general. If the issue is "common", I too have no idea where to report it to. I was simply remarking that the behavior of a custom prefix build of KMyMoney wasn't consistent with my usual experience with other Linux software. Specifically, that building and installing software into /usr/local usually (in my experience) results in a working application without additional steps that you're supposed to "know". I repeat that this is no longer a problem for me, and I'm only arguing this issue in hopes of presenting an easier "first build" experience for other possible developers. It's not instantly obvious to a new developer why the plugins were not found and why the application does not work in the requested prefix. If this is perceived as intentional or not-a-bug by the broader community, I'll let it go, use my workaround and move on, but I also see an opportunity to make things easier for new developers. I'm willing to propose a change to implement the script installation, but only if the community perceives that the change is valuable (and so far it seems that they do not). -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 471091] New: Filelight analyses home folder, then crashes
https://bugs.kde.org/show_bug.cgi?id=471091 Bug ID: 471091 Summary: Filelight analyses home folder, then crashes Classification: Applications Product: filelight Version: 23.04.2 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: nicolabae...@yahoo.it CC: martin.sandsm...@kde.org Target Milestone: --- Application: filelight (23.04.2) Qt Version: 5.15.9 Frameworks Version: 5.107.0 Operating System: Linux 6.3.7-zen1-1-zen x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: As the title says, Filelight analyses a folder but it crashes afterwards. This happens with every folder (ext4 and ntfs) The crash can be reproduced every time. -- Backtrace: Application: Filelight (filelight), signal: Segmentation fault [KCrash Handler] #4 0x7f779e752e23 in ?? () from /usr/lib/libnvidia-glcore.so.530.41.03 #5 0x7f779e723ac5 in ?? () from /usr/lib/libnvidia-glcore.so.530.41.03 #6 0x7f77ad14cc70 in ?? () from /usr/lib/libQt5Gui.so.5 #7 0x7f77ad0a9d19 in ?? () from /usr/lib/libQt5Gui.so.5 #8 0x7f77ad08772f in QOpenGLShaderProgram::link() () from /usr/lib/libQt5Gui.so.5 #9 0x7f77ae788eb5 in QSGMaterialShader::compile() () from /usr/lib/libQt5Quick.so.5 #10 0x7f77ae795ec0 in ?? () from /usr/lib/libQt5Quick.so.5 #11 0x7f77ae7a4de7 in QSGBatchRenderer::Renderer::renderUnmergedBatch(QSGBatchRenderer::Batch const*) () from /usr/lib/libQt5Quick.so.5 #12 0x7f77ae7a7c84 in QSGBatchRenderer::Renderer::renderBatches() () from /usr/lib/libQt5Quick.so.5 #13 0x7f77ae7ac611 in QSGBatchRenderer::Renderer::render() () from /usr/lib/libQt5Quick.so.5 #14 0x7f77ae794265 in QSGRenderer::renderScene(QSGBindable const&) () from /usr/lib/libQt5Quick.so.5 #15 0x7f77ae7fb4e9 in QSGOpenGLLayer::grab() () from /usr/lib/libQt5Quick.so.5 #16 0x7f77ae7f3396 in QSGOpenGLLayer::updateTexture() () from /usr/lib/libQt5Quick.so.5 #17 0x7f77ae7da3d3 in QSGBasicInternalImageNode::preprocess() () from /usr/lib/libQt5Quick.so.5 #18 0x7f77ae794969 in QSGRenderer::preprocess() () from /usr/lib/libQt5Quick.so.5 #19 0x7f77ae79422c in QSGRenderer::renderScene(QSGBindable const&) () from /usr/lib/libQt5Quick.so.5 #20 0x7f77ae794704 in QSGRenderer::renderScene(unsigned int) () from /usr/lib/libQt5Quick.so.5 #21 0x7f77ae7ed795 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /usr/lib/libQt5Quick.so.5 #22 0x7f77ae849711 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () from /usr/lib/libQt5Quick.so.5 #23 0x7f77ae7f7e26 in ?? () from /usr/lib/libQt5Quick.so.5 #24 0x7f77ae7fcbe4 in ?? () from /usr/lib/libQt5Quick.so.5 #25 0x7f77ac6f30da in ?? () from /usr/lib/libQt5Core.so.5 #26 0x7f77ac09d44b in ?? () from /usr/lib/libc.so.6 #27 0x7f77ac120e40 in ?? () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f77a4dff6c0 (LWP 13552) "QQmlThread"): #1 0x7f77ab110657 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7f77ab16d906 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f77ab10e032 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f77ac8e9f2f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f77ac899824 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f77ac6f6eb6 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f77ae2c2410 in ?? () from /usr/lib/libQt5Qml.so.5 #8 0x7f77ac6f30da in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f77ac09d44b in ?? () from /usr/lib/libc.so.6 #10 0x7f77ac120e40 in ?? () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f77a61666c0 (LWP 13551) "QThread"): #1 0x7f77ab110e47 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7f77ab16d998 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f77ab10e032 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f77ac8e9f2f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f77ac899824 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f77ac6f6eb6 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f77ac6f30da in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f77ac09d44b in ?? () from /usr/lib/libc.so.6 #9 0x7f77ac120e40 in ?? () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f77a7d676c0 (LWP 13549) "QDBusConnection"): #1 0x7f77ab16da9f in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f77ab10e032 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f77ac8e9f2f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4
[plasmashell] [Bug 470901] If the Panel is placed on top of the screen, "More options" menu unexpectedly opens upwards
https://bugs.kde.org/show_bug.cgi?id=470901 Patrick Silva changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Patrick Silva --- The bug persists on neon unstable. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471058] Tags not shown for all items after export-import
https://bugs.kde.org/show_bug.cgi?id=471058 --- Comment #11 from Jan van Bekkum --- Created attachment 159699 --> https://bugs.kde.org/attachment.cgi?id=159699=edit Sidecar that wasn't copied by export -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471058] Tags not shown for all items after export-import
https://bugs.kde.org/show_bug.cgi?id=471058 --- Comment #10 from Jan van Bekkum --- Are you using digiKam's Local Export Tool? Ok, I'll test it with that. ==> Yes, export to local storage Please check whether there really is a sidecar in computer A for the video files in question. ==> there is a sidecar for all files on computer A. I attach the sidecar that wasn't copied. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 470357] "Appearance" section in the settings of System Monitor widgets is empty due to "org.kde.kconfig" not being installed
https://bugs.kde.org/show_bug.cgi?id=470357 Patrick Silva changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Patrick Silva --- Fixed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470935] "Profile:" text is misplaced
https://bugs.kde.org/show_bug.cgi?id=470935 Patrick Silva changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Patrick Silva --- it's no longer happening. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 465269] Plasma mobile session crashes when kscreenlocker is unlocked
https://bugs.kde.org/show_bug.cgi?id=465269 --- Comment #20 from Marco Mattiolo --- (In reply to Devin Lin from comment #19) > > I think we'll close this bug for now then, and open a new one if it is > observed with Plasma 6. Please, during the Plasma6 general rework, do not forget to add as many logging as possible inside the code base. It was already discussed in the past, that lack of debugging logs makes hard to understand who/when/where is breaking. I am now seeing again that "The screen locker is broken and unlocking is not possible anymore. In order to unlock it, switch to a virtual terminal ..." on pmOS on op6: of course this is not a Plasma6 fault, but it confirms the need for better debugging logs. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471067] Checkboxes have weird blurry look on them
https://bugs.kde.org/show_bug.cgi?id=471067 --- Comment #2 from Akseli Lahtinen --- Created attachment 159698 --> https://bugs.kde.org/attachment.cgi?id=159698=edit Changed height in gammaray for comparison Added a new attachment, screenshot after using gammaray. Both elements are on same page, so the image isnt copy pasted twice. I modified the top element checkbox to have height 21.01, the error went away. Bottom one is the default. Seems there's some floating point erroring going on, I encounted something similar with outlines: Drawing a thin line with width of 1.0 would look wrong, but drawing it with width of 1.01 would look right. My problem is that I do not even know where to start fixing this, so any help is welcome. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 471090] New: Elisa's theme only partially changed when changing global theme from Breeze Light to Breeze Dark (until application's restart)
https://bugs.kde.org/show_bug.cgi?id=471090 Bug ID: 471090 Summary: Elisa's theme only partially changed when changing global theme from Breeze Light to Breeze Dark (until application's restart) Classification: Applications Product: Elisa Version: 23.04.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: damik...@gmail.com Target Milestone: --- Created attachment 159697 --> https://bugs.kde.org/attachment.cgi?id=159697=edit Elisa being shown in semi-changed style, with Breeze Dark theme selected. SUMMARY *** Elisa's theme is only partially changed when switching global theme from Breeze Light to Breeze Dark: - toolbar and hamburger menu stay light, together with current playlist view - fonts are dark-on-dark After restart the colors are shown correctly. *** STEPS TO REPRODUCE 1. Open Elisa, Breeze Light as Global Theme 2. Change Global theme to Breeze Dark OBSERVED RESULT Some of Elisa's colors are only partially changed to dark theme, until restart. EXPECTED RESULT All of Elisa's colors should be refreshed instantly after theme is changed. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.6-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-2520M CPU @ 2.50GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 3000 Manufacturer: Hewlett-Packard Product Name: HP EliteBook 8460p System Version: A0001D02 ADDITIONAL INFORMATION Maybe Kirigami issue and not Elisa specific? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458572] Add toggle to show all KWin scripts regardless of X-KWin-Exclude-Listing state
https://bugs.kde.org/show_bug.cgi?id=458572 Alexander Lohnau changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |alexander.loh...@gmx.de --- Comment #3 from Alexander Lohnau --- Maybe we can reconsider this for KF6. I have reached out to the Bismuth people with the suggestion of only hiding the KCM of the script and not the entire script. @Nate, then the "Desktop Change OSD" entry will show in the KCM (though it appears to do so now anyway?). Maybe we can interpret this as a "it is broken now, but nobody seemed to care, so we could keep it as it is". -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469113] KDE doesn't remember display resolution
https://bugs.kde.org/show_bug.cgi?id=469113 fw.smi...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #7 from fw.smi...@gmail.com --- I happened again. I didn't change any configuration, but now my 1440p monitor is outputting at 1080. Below is the kscreen-doctor -o output of the monitor in the wrong resolution. Output: 66 eDP-1 disabled connected priority 0 Panel Modes: 73:1920x1080@60! 74:1920x1080@60 75:1920x1080@60 76:1920x1080@60 77:1920x1080@60 78:1920x1080@40 79:1680x1050@60 80:1680x1050@60 81:1400x1050@60 82:1600x900@60 83:1600x900@60 84:1600x900@60 85:1600x900@60 86:1280x1024@60 87:1400x900@60 88:1400x900@60 89:1280x960@60 90:1440x810@60 91:1440x810@60 92:1368x768@60 93:1368x768@60 94:1280x800@60 95:1280x800@60 96:1280x800@60 97:1280x800@60 98:1280x720@60 99:1280x720@60 100:1280x720@60 101:1280x720@60 102:1024x768@60 103:1024x768@60 104:960x720@60 105:928x696@60 106:896x672@60 107:1024x576@60 108:1024x576@60 109:1024x576@60 110:1024x576@60 111:960x600@60 112:960x600@60 113:960x540@60 114:960x540@60 115:960x540@60 116:960x540@60 117:800x600@60 118:800x600@60 119:800x600@56 120:840x525@60 121:840x525@60 122:864x486@60 123:864x486@60 124:700x525@60 125:800x450@60 126:800x450@60 127:640x512@60 128:700x450@60 129:700x450@60 130:640x480@60 131:640x480@60 132:720x405@60 133:720x405@59 134:684x384@60 135:684x384@60 136:640x400@60 137:640x400@60 138:640x360@60 139:640x360@60 140:640x360@60 141:640x360@59 142:512x384@60 143:512x288@60 144:512x288@60 145:480x270@60 146:480x270@60 147:400x300@60 148:400x300@56 149:432x243@60 150:432x243@60 151:320x240@60 152:360x202@60 153:360x202@59 154:320x180@60 155:320x180@59 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 67 DP-1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 68 HDMI-1 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 69 DP-2 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 70 HDMI-2 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 71 HDMI-3 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 207 eDP-1-2 disabled disconnected priority 0 Panel Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 208 HDMI-1-4 enabled connected priority 1 HDMI Modes: 75:1920x1080@60 76:1920x1080@60 77:1920x1080@60 79:1680x1050@60 80:1680x1050@60 81:1400x1050@60 82:1600x900@60 83:1600x900@60 84:1600x900@60 85:1600x900@60 86:1280x1024@60 87:1400x900@60 88:1400x900@60 89:1280x960@60 90:1440x810@60 91:1440x810@60 92:1368x768@60 93:1368x768@60 94:1280x800@60 95:1280x800@60 96:1280x800@60 97:1280x800@60 98:1280x720@60 99:1280x720@60 100:1280x720@60 101:1280x720@60 102:1024x768@60 103:1024x768@60 104:960x720@60 105:928x696@60 106:896x672@60 107:1024x576@60 108:1024x576@60 109:1024x576@60 110:1024x576@60 111:960x600@60 112:960x600@60 113:960x540@60 114:960x540@60 115:960x540@60 116:960x540@60 117:800x600@60 118:800x600@60 119:800x600@56 120:840x525@60 121:840x525@60 122:864x486@60 123:864x486@60 124:700x525@60 125:800x450@60 126:800x450@60 127:640x512@60 128:700x450@60 129:700x450@60 130:640x480@60 131:640x480@60 132:720x405@60 133:720x405@59 134:684x384@60 135:684x384@60 136:640x400@60 137:640x400@60 138:640x360@60 139:640x360@60 140:640x360@60 141:640x360@59 142:512x384@60 143:512x288@60 144:512x288@60 145:480x270@60 146:480x270@60 147:400x300@60 148:400x300@56 149:432x243@60 150:432x243@60 151:320x240@60 152:360x202@60 153:360x202@59 154:320x180@60 155:320x180@59 2431:1920x1080@60* 2432:1920x1080@50 2433:1920x1080@60 2434:1920x1080@60 2435:1920x1080@50 2436:1920x1080@60 2437:1400x1050@75 2438:1600x900@60 2439:1280x1024@75 2440:1152x864@75 2441:1280x720@60 2442:1280x720@50 2443:1280x720@60 2444:1024x768@75 2445:1024x768@75 2446:1024x768@70 2447:960x720@75 2448:928x696@75 2449:896x672@75 2450:832x624@75 2451:800x600@75 2452:800x600@70 2453:800x600@65 2454:800x600@72 2455:800x600@75 2456:720x576@50 2457:700x525@75 2458:720x480@60 2459:720x480@60 2460:640x512@75 2461:640x480@75 2462:640x480@73 2463:640x480@60 2465:576x432@75 2466:512x384@75 2467:512x384@70 2468:416x312@75 2469:400x300@72 2470:400x300@75 2471:320x240@73 2472:320x240@75 2796:2560x1440@60! 2797:1920x1440@60 2798:2048x1280@60 2799:1856x1392@60 2800:1792x1344@75 2801:1792x1344@60 2802:2048x1152@60
[kmymoney] [Bug 471061] Installation for /usr/local installs plugins into incorrect path
https://bugs.kde.org/show_bug.cgi?id=471061 --- Comment #3 from Jack --- If someone wants to build and install kmymoney in lieu of a distro-supplied version, I'm pretty sure it "just works." It's only if you modify any defaults that issues arise. It might be reasonable to think that if you modify the build from the defaults, then you know what you are doing. If you do alter the install prefix, then it might be specifically because you want it out of the way of standard system installed stuff. Remember that much of where programs look for libraries already depends on environment variables, and is not fully built in to the executable, so it is not currently feasibly to adjust where a program looks for libraries and plugins. Also, none of that is specific to KMyMoney (as far as I know.) I believe it all comes along for using the Qt/KDE/CMake environment and build system. I'm not even sure where such a wishlist would properly be directed. In your case, it might be reasonable to create a script to source prefix.sh and then call the new kmymoney. That is essentially how it is possible to have more than one version of the program installed at the same time, without them stepping all over each other. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 471061] Installation for /usr/local installs plugins into incorrect path
https://bugs.kde.org/show_bug.cgi?id=471061 Cory F Cohen changed: What|Removed |Added Resolution|NOT A BUG |INTENTIONAL --- Comment #2 from Cory F Cohen --- Ok. I was aware that this script existed, but I thought that it was part of the build environment. It seems odd to me that after installing into a custom prefix that the software doesn't actually function without setting half a dozen environment variables. It's not like the plugins are optional in any way, since it's not possible to open a data file without them. In my experience software usually configures itself for the build path that it's installed into. Have you considered installing a version of the prefix script (including an invocation of the kmymoney executable) as $CMAKE_INSTALL_PREFIX/bin/kmymoney ? Regardless, the advice is clear enough once you know what has to be done, so it's not a problem for me anymore, it just seems like an opportunity to make it easier for people to build kmymoney. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 467428] Expired or missing access tokens for account
https://bugs.kde.org/show_bug.cgi?id=467428 emin turker changed: What|Removed |Added CC||turkerem...@gmail.com --- Comment #5 from emin turker --- Issue still present. Operating System: EndeavourOS KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.8-zen1-1-zen (64 bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471053] Copy & paste with "Strg A" from old to new project no longer works
https://bugs.kde.org/show_bug.cgi?id=471053 --- Comment #3 from fehler-im-progr...@posteo.de --- Created attachment 159696 --> https://bugs.kde.org/attachment.cgi?id=159696=edit Bug 'Strg A' (without Wipe).png -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471053] Copy & paste with "Strg A" from old to new project no longer works
https://bugs.kde.org/show_bug.cgi?id=471053
--- Comment #2 from fehler-im-progr...@posteo.de ---
*Hello emohr,*
What does timeline_corruption+ mean. Did you find an error after all?
The problem seems to be the transitions (wipe). Even the transitions
ALONE cause the problem ("not enough tracks to insert the clipboard").
I use Linux.
*Regards Johannes*
Am 15.06.23 um 16:58 schrieb emohr:
> https://bugs.kde.org/show_bug.cgi?id=471053
>
> emohr changed:
>
> What|Removed |Added
>
>Flags||timeline_corruption+
>
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 471089] New: Undocumented gestures/mouse swipe
https://bugs.kde.org/show_bug.cgi?id=471089 Bug ID: 471089 Summary: Undocumented gestures/mouse swipe Classification: Plasma Product: kwin Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Gestures Assignee: kwin-bugs-n...@kde.org Reporter: dc.h...@slowlyboiledfrog.com Target Milestone: --- SUMMARY Some mouse movement causes all of my windows to tile losing focus on the active window. This creates innumerable problems because, whatever the gesture is (and I am not sure) it is AMBIGUOUS and interferes with productivity. There doesn't seem to be a system setting to control the effect. This is a serious problem. It compromises productivity! *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_andSytem_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE Unknown. The issue does not seem to be documented. It MIGHT be a wipe, right to left but it seems dependent upon other things. OBSERVED RESULT Windows tile EXPECTED RESULT This effect should be option and controllable. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: WHAT? (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.017.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Note: Mouse, not touchpad. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 471088] New: No square root function on the calculator
https://bugs.kde.org/show_bug.cgi?id=471088 Bug ID: 471088 Summary: No square root function on the calculator Classification: Applications Product: kcalc Version: 22.04.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: linux...@avoura.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. There is no button for square root 2. Cannot do square root 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 22.04.3 (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.
[okteta] [Bug 471079] okteta show empty HEX-dump area
https://bugs.kde.org/show_bug.cgi?id=471079 --- Comment #3 from Friedrich W. H. Kossebau --- Notes for self/developer: "QPainter::begin: Paint device returned engine == 0, type: 2" here the type 2 seems to be "Pixmap" from QInternal enum PaintDeviceFlags. Okteta uses a QPixmap for caching the cursor (gui/cursor.cpp). Forcing that QPixmap to be an 0x0 QPixmap results in the same log as reported: QPainter::begin: Paint device returned engine == 0, type: 2 QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::setPen: Painter not active QPainter::end: Painter not active, aborted The size of the pixmap is calculated from args PixelX Width, PixelY Height, qreal devicePixelRatio, where the width & height are taken (indirectly from the QFontMetrics of the fixed size font. And devicePixelRatio is taken from the widget (Qt). The latter being 0 would fail elsewhere I assume, so a working theory here would be that either of or both the maxWidth() and height() have a value of 0, perhaps due to broken font metadata. So the font having some (unexpected) 0 values might explain the experienced display. Testing with other fonts for the system fixed size/width font might help to confirm that theory. -- You are receiving this mail because: You are watching all bug changes.
