[kwin] [Bug 459389] Copy and paste do not work in Wayland when using some text editors in konsole and some applications
https://bugs.kde.org/show_bug.cgi?id=459389 --- Comment #11 from Zesko --- (In reply to Zesko from comment #1) > Copy & paste (Shared Clipboard) does not work from KDE Wayland in my host to > KDE Wayland in Virtualbox. > It does not work from Virtualbox to my host too. But Gnome Wayland has no > issue with shared clipboard. I noticed that some shared-clipboard works, some shared-clipboard does not work: Shared-clipboard does not work if: - Kate in KDE Wayland in VirtualBox ---> any applications in same KDE Wayland in Host. - Any applications in KDE Wayland in VirtualBox <--- Kate in same KDE Wayland in Host. Shared-clipboard works if: - Copy any URL in Firefox in KDE Wayland in VirtualBox > any applications in KDE Wayland in Host, it appears in Klipper too. - Any applications in KDE Wayland in VirtualBox < Copy any URL in Firefox in KDE Wayland in Host. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 446840] Link to https://www.manjarocomputer.eu on https://kde.org/hardware
https://bugs.kde.org/show_bug.cgi?id=446840 --- Comment #3 from Albert Astals Cid --- I'm relatively sure i raised the same concern when the SteamDeck was added :) (or maybe not seeing how this one was being ignored) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459714] Media controller widget with "song name" uses too much horizontal space
https://bugs.kde.org/show_bug.cgi?id=459714 Antonio Rojas changed: What|Removed |Added CC|aro...@archlinux.org| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459714] Media controller widget with "song name" uses too much horizontal space
https://bugs.kde.org/show_bug.cgi?id=459714 Antonio Rojas changed: What|Removed |Added Target Milestone|--- |1.0 Assignee|ksi...@gmail.com|plasma-b...@kde.org CC||aro...@archlinux.org, ||k...@privat.broulik.de Product|plasma-mediacenter |plasmashell Version|unspecified |git-stable-Plasma/5.26 Component|MediaController |Media Player -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 Reuben changed: What|Removed |Added CC||reube...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457910] Desktop grid arrow keys navigate between windows not desktops
https://bugs.kde.org/show_bug.cgi?id=457910 --- Comment #5 from Vlad Zahorodnii --- Git commit 893d58eba7800f2fa6f05c6e630ed419ed4ce083 by Vlad Zahorodnii, on behalf of David Edmundson. Committed on 27/09/2022 at 06:28. Pushed by vladz into branch 'Plasma/5.26'. Don't accept space and enter key events in empty WindowHeaps This fixes being able to select an empty desktop. (cherry picked from commit 105af544c9069f2ccbcb80fc460e7c9dba2a26f5) M +1-1src/effects/private/qml/WindowHeap.qml https://invent.kde.org/plasma/kwin/commit/893d58eba7800f2fa6f05c6e630ed419ed4ce083 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459726] New: bezier line tool doesn't respond to [ and ] to change brush size
https://bugs.kde.org/show_bug.cgi?id=459726 Bug ID: 459726 Summary: bezier line tool doesn't respond to [ and ] to change brush size Classification: Applications Product: krita Version: git master (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: tapatilore...@gmail.com Target Milestone: --- On master branch, git commit hash: 6f95172f6146c696d60a0af94b00d817e4c69117 Also tested on stable public release 5.1.0 STEPS TO REPRODUCE 1. open any document, new or old, in krita 2. switch to the bezier line tool 3. press either [ or ] to increase or decrease brush size (assuming default shortcuts) OBSERVED RESULT No change in brush size EXPECTED RESULT Brush size changes. Why is this expected? Because the size of the brush is used by the tool to determine the line thickness, so these shortcuts are relevant. The straight line tool handles these shortcuts as well. This is a discrepancy that creates functional friction, i.e. the user needs to use the mouse or switch tools temporarily to change brush size, then switch back. SOFTWARE/OS VERSIONS Windows: Windows 10 Home (10.0.19042) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457910] Desktop grid arrow keys navigate between windows not desktops
https://bugs.kde.org/show_bug.cgi?id=457910 --- Comment #4 from Vlad Zahorodnii --- Git commit 105af544c9069f2ccbcb80fc460e7c9dba2a26f5 by Vlad Zahorodnii, on behalf of David Edmundson. Committed on 27/09/2022 at 06:26. Pushed by vladz into branch 'master'. Don't accept space and enter key events in empty WindowHeaps This fixes being able to select an empty desktop. M +1-1src/effects/private/qml/WindowHeap.qml https://invent.kde.org/plasma/kwin/commit/105af544c9069f2ccbcb80fc460e7c9dba2a26f5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459389] Copy and paste do not work in Wayland when using some text editors in konsole and some applications
https://bugs.kde.org/show_bug.cgi?id=459389 --- Comment #10 from Zesko --- > wl-clipboard was already installed. > I have no xsel and uninstalled xclip today, then Micro can not be opened > after reboot, but it only shows black and blank (No text) in Konsole. Update: Micro appears with text and works fine with wl-clipboard when Klipper (System Tray Clipboard) is not empty! If Klipper (System Tray Clipboard) is EMPTY, then Micro can not be opened. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459389] Copy and paste do not work in Wayland when using some text editors in konsole and some applications
https://bugs.kde.org/show_bug.cgi?id=459389 --- Comment #9 from Zesko --- (In reply to Vlad Zahorodnii from comment #8) > If you uninstall both xclip and xsel and leave only wl-clipboard installed, > does clipboard work in micro? wl-clipboard was already installed. I have no xsel and uninstalled xclip today, then Micro can not be opened after reboot, but it only shows black and blank (No text) in Konsole. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459725] New: allow switching desktop when present all windows
https://bugs.kde.org/show_bug.cgi?id=459725 Bug ID: 459725 Summary: allow switching desktop when present all windows Classification: Plasma Product: kwin Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: xgd...@gmail.com Target Milestone: --- SUMMARY allow switching desktop when present all windows. 1. allow keyboard shortcuts of switching desktop when present all windows. 2. allow moving window to other desktop by dragging when present all windows. STEPS TO REPRODUCE 1. present all windows 2. press the keyboard shortcuts of switching desktop OBSERVED RESULT the keyboard shortcuts of switching desktop don' t work EXPECTED RESULT keyboard shortcut work SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04.1 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: Version 5.92.0 Qt Version: 5.15.3 (built against 5.15.3) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459066] Problems with the vertical mirror mode of the multibrush tool
https://bugs.kde.org/show_bug.cgi?id=459066 --- Comment #5 from Deif Lou --- My intuition tells me that the top-right and bottom-right dabs should have the same x coordinate, so even if the coords are subpixel and the dabs pixels may not be exactly the same, the dabs should align on the left and right. Same with the bottom-left and bottom right dabs but in the y coordinate. When I checked the code I couldn't see anything wrong with the transformations in the tool to be honest, so I don't know were else to look. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459276] Batch Queue Manager, Base tool (Convert tool): crash for some selected formats
https://bugs.kde.org/show_bug.cgi?id=459276 --- Comment #13 from caulier.gil...@gmail.com --- Git commit d6110157d24421dd51635cb16b2ccbbd8b82b0ae by Gilles Caulier. Committed on 27/09/2022 at 06:01. Pushed by cgilles into branch 'qt5-maintenance'. cleanup previous intall under Windows M +14 -0project/bundles/mxe/03-build-digikam.sh https://invent.kde.org/graphics/digikam/commit/d6110157d24421dd51635cb16b2ccbbd8b82b0ae -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420595] Blown up view (Intel Graphic Card issue on Windows)
https://bugs.kde.org/show_bug.cgi?id=420595 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459724] New: Black Desktop / Desktop Reset (Mutiple Monitor Setup)
https://bugs.kde.org/show_bug.cgi?id=459724 Bug ID: 459724 Summary: Black Desktop / Desktop Reset (Mutiple Monitor Setup) Classification: Plasma Product: plasmashell Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: abys...@yahoo.com CC: notm...@gmail.com Target Milestone: 1.0 Can someone have a look at this thread? Please don't mark this thread as a duplicate and toss it aside. https://bugs.kde.org/show_bug.cgi?id=427861 It has been sprawling forever and the black desktop/desktop reset (background resets, notes, widgets, etc..) with multiple monitor setups. It is almost impossible to use your desktop for anything as it will either randomly be completely reset (a new container is created in plasma-org.kde.plasma.desktop-appletsrc). Literally just get an extra monitor and use KDE with it for a few days/weeks, I'm sure you'll experience the issues many of us are. I'm at a loss as I love KDE, but constantly fighting this issue is slowly driving many away from using KDE. This bug is still present in 5.25 and though I haven't had a chance to try 5.26, I would think it is also present there as well. Any help is appreciated as it is driving us all nuts to not be able to actually utilize a major components of this desktop environment, along with having to redo things it desides to randomly reset our desktops. Easy to reproduce the black desktop: 1. Leave your computer idle 2. Let your monitors go to sleep 3. Wake up the system and login 4. You should have now a black desktop on one of your monitors Desktop reset is random, and can happen either using the steps above, or just randomly on a login to the system. Many many posts in the linked thread should be beneficial to eradicating these issues going forward. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414736] Needs creation date in Clip Properties.
https://bugs.kde.org/show_bug.cgi?id=414736 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[kdenlive] [Bug 404844] GUI resize unstable
https://bugs.kde.org/show_bug.cgi?id=404844 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.
[kdenlive] [Bug 419985] Crash when changing the project resolution on a busy project
https://bugs.kde.org/show_bug.cgi?id=419985 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #11 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 451673] No puedo apreciar los menús, no puedo editar videos.
https://bugs.kde.org/show_bug.cgi?id=451673 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.
[kate] [Bug 381024] Autocomplete back-searches word
https://bugs.kde.org/show_bug.cgi?id=381024 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 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 457541] Night Color Non-operational
https://bugs.kde.org/show_bug.cgi?id=457541 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[kup] [Bug 458326] Add manual trigger for backup
https://bugs.kde.org/show_bug.cgi?id=458326 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.
[kdenlive] [Bug 425495] Value on Audio Mixer graph does not correspond with Slider Value
https://bugs.kde.org/show_bug.cgi?id=425495 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |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 423053] Extract frame cause blank png
https://bugs.kde.org/show_bug.cgi?id=423053 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |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 426933] Extracted clips start is slighty different from the marked zone
https://bugs.kde.org/show_bug.cgi?id=426933 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.
[kdenlive] [Bug 452141] "Places" Panel in kfilewidget should be able to be toggled off.
https://bugs.kde.org/show_bug.cgi?id=452141 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[kdenlive] [Bug 452509] Kdenlive (Appimage) crashes when I click onto a video clip in the timeline
https://bugs.kde.org/show_bug.cgi?id=452509 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.
[kdenlive] [Bug 440999] Low resolution color filter icons
https://bugs.kde.org/show_bug.cgi?id=440999 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.
[kate] [Bug 459023] Kate error message: The specified folder does not exist or was not readable.
https://bugs.kde.org/show_bug.cgi?id=459023 --- Comment #2 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.
[krita] [Bug 458081] Krita 5.1.0 will not allow me to pull up art via search.
https://bugs.kde.org/show_bug.cgi?id=458081 --- 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.
[kdenlive] [Bug 395701] Keyframes are not recalculated for all clips when rendering the final video which produces frozen images at the beginning of transitions (input clip format is h264)
https://bugs.kde.org/show_bug.cgi?id=395701 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #21 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 420595] Blown up view (Intel Graphic Card issue on Windows)
https://bugs.kde.org/show_bug.cgi?id=420595 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #16 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.
[kmymoney] [Bug 457640] Allow KmyMoney to stay on selected transaction even when switching between Virtual Desktops
https://bugs.kde.org/show_bug.cgi?id=457640 --- 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 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #4 from Alexander Reinholdt --- If you need some more information, please let me know. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451681] Scan and refresh of album don't rotate HEIC files correctly.
https://bugs.kde.org/show_bug.cgi?id=451681 --- Comment #14 from Maik Qualmann --- openSUSE Tumbleweed is still on libheif-1.12. Since libheif-1.13 was released recently, the bug will not be fixed until the current version. Maik -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 imagame...@msn.com changed: What|Removed |Added CC||imagame...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459697] Regional Settings -> Formats messes up something and causes warnings in Perl and other command-line tools
https://bugs.kde.org/show_bug.cgi?id=459697 hanyo...@protonmail.com changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #3 from hanyo...@protonmail.com --- > Auto locale generation has been added in the new KCM_RegionAndLang. Which > will ship with plasma 5.26 I already said this feature has been added in plasma 5.26 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459276] Batch Queue Manager, Base tool (Convert tool): crash for some selected formats
https://bugs.kde.org/show_bug.cgi?id=459276 --- Comment #12 from caulier.gil...@gmail.com --- Git commit 8c86f33952258bc5174a61cb4bdd3ac8db5326ae by Gilles Caulier. Committed on 27/09/2022 at 02:56. Pushed by cgilles into branch 'qt5-maintenance'. clean up previous install under MacOS M +14 -0project/bundles/macports/03-build-digikam.sh https://invent.kde.org/graphics/digikam/commit/8c86f33952258bc5174a61cb4bdd3ac8db5326ae -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445361] MacOS - Animation Playback Lag
https://bugs.kde.org/show_bug.cgi?id=445361 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #5 from vanyossi --- Is the black canvas not related to bug 459134? I could reproduce that one on the mac mini with M1. As for this report: I cannot reproduce it with the files I've made yet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459609] KWin switches the discrete GPU on every time a new Wayland window is opened in a switchable graphics setup
https://bugs.kde.org/show_bug.cgi?id=459609 Nate Graham changed: What|Removed |Added Resolution|NOT A BUG |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446506] Onion Skin Artifacts
https://bugs.kde.org/show_bug.cgi?id=446506 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com --- Comment #3 from vanyossi --- This is probably related to other tiling canvas artifacts. Setting to confirmed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459134] Animation Cache displays black frame when "limit cached frame size" is active.
https://bugs.kde.org/show_bug.cgi?id=459134 vanyossi changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||ghe...@gmail.com --- Comment #2 from vanyossi --- Setting to confirmed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459455] [request] please add multiple frames when multiple frame-slots are selected
https://bugs.kde.org/show_bug.cgi?id=459455 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1597 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459723] Using transform/move tool on empty columns doesn't apply a new autokey
https://bugs.kde.org/show_bug.cgi?id=459723 tomtomtomreportin...@gmail.com changed: What|Removed |Added Keywords||regression --- Comment #1 from tomtomtomreportin...@gmail.com --- Since this issue starts occurring as of 5.1.0, marking as a regression. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459723] New: Using transform/move tool on empty columns doesn't apply a new autokey
https://bugs.kde.org/show_bug.cgi?id=459723 Bug ID: 459723 Summary: Using transform/move tool on empty columns doesn't apply a new autokey Classification: Applications Product: krita Version: 5.1.1 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- Per https://krita-artists.org/t/auto-frame-mode-no-longer-exists/48439/5 SUMMARY As of 5.1.0, using the transform/move tool on content from a previous frame onto a selected empty column doesn't automatically add a new frame. STEPS TO REPRODUCE 1. Add the first frame. 2. Draw something. 3. Select the drawn content. 4. Select a new empty column. 5. Translate the content with move/transform tool. OBSERVED RESULT A new frame isn't automatically made. EXPECTED RESULT A new frame should be automatically made. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.12.12 (appimage) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459066] Problems with the vertical mirror mode of the multibrush tool
https://bugs.kde.org/show_bug.cgi?id=459066 --- Comment #4 from vanyossi --- Created attachment 152453 --> https://bugs.kde.org/attachment.cgi?id=152453&action=edit Multibrush with pixel brushes Differences probably come at the subpixel level. To check this I did this: Used a pixel "perfect" brush (Pixel Art Fill) at 1px size the pixel filled is correctly mirrored in all modes. However "Basic-5 Pixel" at 1px gives little variations. To me this is expected as each dab is a different brush. However I will look at the code tomorrow. Attached video shows coordinates are the same at the pixel coordinate level. Doing the same test without sharpness (using subpixel) will produce little differences. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 459722] New: Konsole crashed during resize
https://bugs.kde.org/show_bug.cgi?id=459722 Bug ID: 459722 Summary: Konsole crashed during resize Classification: Applications Product: konsole Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: arca...@ivanov.biz Target Milestone: --- Application: konsole (22.04.1) Qt Version: 5.15.5 Frameworks Version: 5.98.0 Operating System: Linux 5.19.10-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Attempted to resize the konsole window going from 3-screen to a single primary on laptop. Konsole crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 0x7fd8a428ec4c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7fd8a423e9c6 in raise () from /lib64/libc.so.6 #6 0x7fd8a42287f4 in abort () from /lib64/libc.so.6 #7 0x7fd8a46a2b57 in __gnu_cxx::__verbose_terminate_handler() [clone .cold] () from /lib64/libstdc++.so.6 #8 0x7fd8a46ae3dc in __cxxabiv1::__terminate(void (*)()) () from /lib64/libstdc++.so.6 #9 0x7fd8a46ae447 in std::terminate() () from /lib64/libstdc++.so.6 #10 0x7fd8a46ae6a8 in __cxa_throw () from /lib64/libstdc++.so.6 #11 0x7fd8a46a557f in std::__throw_out_of_range_fmt(char const*, ...) [clone .cold] () from /lib64/libstdc++.so.6 #12 0x7fd8a631ce4e in Konsole::Screen::fastAddHistLine() () from /lib64/libkonsoleprivate.so.1 #13 0x7fd8a6318cec in Konsole::Screen::resizeImage(int, int) () from /lib64/libkonsoleprivate.so.1 #14 0x7fd8a63108cd in Konsole::Emulation::setImageSize(int, int) [clone .part.0] () from /lib64/libkonsoleprivate.so.1 #15 0x7fd8a4cdb8b6 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #16 0x7fd8a62ff3fc in Konsole::TerminalDisplay::changedContentSizeSignal(int, int) () from /lib64/libkonsoleprivate.so.1 #17 0x7fd8a636b8d4 in Konsole::TerminalDisplay::updateImageSize() () from /lib64/libkonsoleprivate.so.1 #18 0x7fd8a636cad8 in Konsole::TerminalDisplay::resizeEvent(QResizeEvent*) () from /lib64/libkonsoleprivate.so.1 #19 0x7fd8a59f2323 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7fd8a59aed22 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #21 0x7fd8a4ca8218 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #22 0x7fd8a59e85a8 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /lib64/libQt5Widgets.so.5 #23 0x7fd8a59e95a1 in QWidget::setGeometry(QRect const&) () from /lib64/libQt5Widgets.so.5 #24 0x7fd8a5b65947 in QSplitterPrivate::setGeo(QSplitterLayoutStruct*, int, int, bool) () from /lib64/libQt5Widgets.so.5 #25 0x7fd8a5b681d1 in QSplitterPrivate::doResize() () from /lib64/libQt5Widgets.so.5 #26 0x7fd8a59f2323 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #27 0x7fd8a5a9e512 in QFrame::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #28 0x7fd8a59aed22 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #29 0x7fd8a4ca8218 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #30 0x7fd8a59e85a8 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /lib64/libQt5Widgets.so.5 #31 0x7fd8a59e95a1 in QWidget::setGeometry(QRect const&) () from /lib64/libQt5Widgets.so.5 #32 0x7fd8a59ce908 in QLayoutPrivate::doResize() () from /lib64/libQt5Widgets.so.5 #33 0x7fd8a59aed07 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #34 0x7fd8a4ca8218 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #35 0x7fd8a59e85a8 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /lib64/libQt5Widgets.so.5 #36 0x7fd8a59e95a1 in QWidget::setGeometry(QRect const&) () from /lib64/libQt5Widgets.so.5 #37 0x7fd8a5b8e596 in QTabWidget::setUpLayout(bool) () from /lib64/libQt5Widgets.so.5 #38 0x7fd8a59f2323 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #39 0x7fd8a59aed22 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #40 0x7fd8a4ca8218 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #41 0x7fd8a59e85a8 in QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /lib64/libQt5Widgets.so.5 #42 0x7fd8a59e95a1 in QWidget::setGeometry(QRect const&) () from /lib64/libQt5Widgets.so.5 #43 0x7fd8a5aa2c85 in QWidgetAnimator::animate(QWidget*, QRect const&, bo
[digikam] [Bug 459306] 'Ambiguous Shortcuts' Message is displayed every time digiKam is launched.
https://bugs.kde.org/show_bug.cgi?id=459306 caulier.gil...@gmail.com changed: What|Removed |Added Summary|'Ambiguous Shortcuts' |'Ambiguous Shortcuts' |Message is displayed every |Message is displayed every |time Digikam is launched|time digiKam is launched. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459306] 'Ambiguous Shortcuts' Message is displayed every time Digikam is launched
https://bugs.kde.org/show_bug.cgi?id=459306 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||7.9.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 362986] Application Dashboard needs an option for the name to have two lines
https://bugs.kde.org/show_bug.cgi?id=362986 --- Comment #15 from tomash...@gmail.com --- I think this should fix this: https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1180 Not much idea why exactly :-). This does not provide an option as OP requested but sets default to two lines. That seems reasonable at least on my system, as I applications names in general fit to two lines and there are many applications where two lines are needed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459609] KWin switches the discrete GPU on every time a new Wayland window is opened in a switchable graphics setup
https://bugs.kde.org/show_bug.cgi?id=459609 Prajna Sariputra changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Prajna Sariputra --- (In reply to Zamundaaa from comment #2) > KWin doesn't touch a GPU unless it's used for compositing or an output is > attached. Most likely, something is probing all the GPUs on application > startup (and eglinfo is doing that as well, but there it's intentional), > instead of only picking the primary one. > Do you have nvidia-utils installed? It caused this behavior for someone else > before: > https://www.reddit.com/r/kde/comments/u5qtjy/ > when_using_qt_programs_in_wayland_they_have_to/ Ah, yes I do have nvidia-utils installed, however in my case I do actually need it there (occasionally if I need to use the dGPU properly I will switch to a Plasma X11 session running on said dGPU plus the proprietary driver, used to use bbswitch instead of nouveau for but that causes other issues I need to work around). Fortunately, it appears that the thing with `/usr/bin/nvidia-modprobe` in that post is just a symptom, the true cause is that libglvnd when using EGL will load all installed ICDs[1], including the NVIDIA one in my case, which is what was poking the dGPU. So, aside from just getting rid of nvidia-utils another way to solve the issue is to set the `__EGL_VENDOR_LIBRARY_FILENAMES` environment variable to only have the Mesa ICD like so: `__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json`. Anyway, thanks for pointing me in the right direction! Also, I am setting the resolution to "not a bug" since it's clearly not a KDE issue, but maybe "upstream" could be a better fit since it's the proprietary driver messing about when it shouldn't? [1]: https://gitlab.freedesktop.org/glvnd/libglvnd/-/blob/master/src/EGL/icd_enumeration.md -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459455] [request] please add multiple frames when multiple frame-slots are selected
https://bugs.kde.org/show_bug.cgi?id=459455 vanyossi changed: What|Removed |Added Keywords||triaged CC||ghe...@gmail.com --- Comment #1 from vanyossi --- To insert multiple keyframes: right click frame -> Keyframe -> Insert Multiple Keyframes. This adds a given number of frames with a step value. However I do see why it feels akward that "add blank keyframe" does not act over the selection. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456142] Display scale is reset on logout
https://bugs.kde.org/show_bug.cgi?id=456142 --- Comment #10 from poperi...@mailbox.org --- Created attachment 152452 --> https://bugs.kde.org/attachment.cgi?id=152452&action=edit Contents of ~/.local/share/kscreen I've uploaded the contents of ~/.local/share/kscreen, like you said. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459161] Inconsistent cursor size
https://bugs.kde.org/show_bug.cgi?id=459161 --- Comment #5 from nocturne --- Now after a gtk3 upgrade (possibly from https://gitlab.gnome.org/GNOME/gtk/-/commit/75d3095a6bb0001682be37c6bb4d42e9bb115d39 ). The cursor is 3 times as big on gtk windows compared to rest of the desktop. Using 24 cursor size and 250% global scaling. Following warnings are printed by gtk apps. (firefox:7952): Gdk-WARNING **: 05:56:17.970: ../gtk/gdk/wayland/gdkcursor-wayland.c:242 cursor image size (64x64) not an integermultiple of scale (3) Any idea how this can be fixed. It is now hard to use gtk apps with the massive cursor -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458530] Crash when trying to open certificate database
https://bugs.kde.org/show_bug.cgi?id=458530 --- Comment #5 from apaul...@gmail.com --- The command line output is just the following: Unable to open QuickAnnotatingTools XML definition QWidget::repaint: Recursive repaint detected KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = okular path = /usr/bin pid = 48724 KCrash: Arguments: /usr/bin/okular KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Stopped okular It looks like maybe something is calling repaint() when it shouldn't be? But it doesn't seem to be anything in the trace, so maybe a repaint is getting triggered accidentally somewhere else, and it just isn't causing a crash until later. Here's a dump with a bit more information, but okularGenerator_ghostview.so doesn't seem to have any debug symbols included in the package, and the other missing frame is unclear what's missing: Application: Okular (okular), signal: Segmentation fault [New LWP 49309] [New LWP 49313] [New LWP 49314] [New LWP 49315] [New LWP 49316] [New LWP 49317] [New LWP 49318] [New LWP 49319] [New LWP 49320] [New LWP 49321] [New LWP 49322] [New LWP 49323] [New LWP 49324] [New LWP 49325] [New LWP 49326] [New LWP 49327] [New LWP 49328] [New LWP 49330] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f0adcc9499f in __GI___poll (fds=0x7fff530bddf8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f0ad910a000 (LWP 49308))] Thread 19 (Thread 0x7f0a811c5700 (LWP 49330)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f0add0266f1 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:133 #2 QtLinuxFutex::futexWait > (expectedValue=, futex=...) at thread/qfutex_p.h:135 #3 futexSemaphoreTryAcquire_loop (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:219 #4 futexSemaphoreTryAcquire (timeout=-1, n=, u=...) at thread/qsemaphore.cpp:262 #5 QSemaphore::acquire (this=0x555f00799480, n=) at thread/qsemaphore.cpp:326 #6 0x7f0acde78e06 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_ghostview.so #7 0x7f0add024543 in QThreadPrivate::start (arg=0x555f00799470) at thread/qthread_unix.cpp:330 #8 0x7f0adc194609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f0adcca1133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f0aa0ff9700 (LWP 49328)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f0aa0ff8b50, clockid=, expected=0, futex_word=0x555f00490df0) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f0aa0ff8b50, clockid=, mutex=0x555f00490da0, cond=0x555f00490dc8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x555f00490dc8, mutex=0x555f00490da0, abstime=0x7f0aa0ff8b50) at pthread_cond_wait.c:665 #3 0x7f0add02a578 in QWaitConditionPrivate::wait_relative (this=0x555f00490da0, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x555f00490da0) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x555f0048bb60, mutex=mutex@entry=0x555effc4d3c8, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7f0add027a91 in QThreadPoolThread::run (this=0x555f0048bb50) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7f0add024543 in QThreadPrivate::start (arg=0x555f0048bb50) at thread/qthread_unix.cpp:330 #8 0x7f0adc194609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f0adcca1133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f0aa17fa700 (LWP 49327)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f0aa17f9b50, clockid=, expected=0, futex_word=0x555f00490904) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f0aa17f9b50, clockid=, mutex=0x555f004908b0, cond=0x555f004908d8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x555f004908d8, mutex=0x555f004908b0, abstime=0x7f0aa17f9b50) at pthread_cond_wait.c:665 #3 0x7f0add02a578 in QWaitConditionPrivate::wait_relative (this=0x555f004908b0, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x555f004908b0) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x555f0048bb00, mutex=mutex@entry=0x555effc4d3c8, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7f0add027a91 in QThreadPoolThread::run (this=0x555f0048baf0) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7f0add024543 in QThreadPrivate::start (arg=0x555f0048baf0) at thread/qthread_unix.cpp:330 #8 0x7f0adc194609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f0adcca1133 in clone () at ../sysdeps/unix/sysv/linux/
[kaffeine] [Bug 459721] Kaffeine (ver 2.0.18) stopped working (no video, no audio, no onscreen errors) when the Fedora software was updated from the 5.18.xx kernel to the 5.19.xx kernel.
https://bugs.kde.org/show_bug.cgi?id=459721 --- Comment #1 from smoeller...@gmail.com --- See all comments & details below. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 459721] New: Kaffeine (ver 2.0.18) stopped working (no video, no audio, no onscreen errors) when the Fedora software was updated from the 5.18.xx kernel to the 5.19.xx kernel.
https://bugs.kde.org/show_bug.cgi?id=459721 Bug ID: 459721 Summary: Kaffeine (ver 2.0.18) stopped working (no video, no audio, no onscreen errors) when the Fedora software was updated from the 5.18.xx kernel to the 5.19.xx kernel. Classification: Applications Product: kaffeine Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mche...@kernel.org Reporter: smoeller...@gmail.com Target Milestone: --- SUMMARY *** Kaffeine (ver 2.0.18) stopped working (no video, no audio, no onscreen errors) when my Fedora software was updated from the 5.18.xx kernel to the 5.19.xx kernel. It does not work on any version of the 5.19 kernel. It continues to work normally on the 5.18.xx kernel. This forces me to reboot into the 5.18.19 kernel to watch over the air broadcast tv. I have used this same PC for years running Fedora and have always used Kaffeine to watch tv. It was just when the 5.19.xx kernel was installed that it stopped working. It does not work under ANY version of the 5.19 kernel. My system is running - Fedora Release 36 (MATE-Compiz) 64-bit Kernel Linux 5.19.11-200.fc36.x86_64 x86_64 MATE 1.26.0 *** STEPS TO REPRODUCE 1. Boot system using the 5.18.xx kernel, Kaffeine works fine. 2. Boot system using any version of the 5.19 kernel, Kaffeine does not work. No audio, no video, no onscreen errors. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux - Fedora Release 36 (MATE-Compiz) 64-bit Kernel Linux 5.19.11-200.fc36.x86_64 x86_64 MATE 1.26.0 KDE platform 5.98 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459720] Regression in 5.26 where Plasma falsely detects new display and checks for "unexisting screen", resetting the display's config
https://bugs.kde.org/show_bug.cgi?id=459720 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459720] Regression in 5.26 where Plasma falsely detects new display and checks for "unexisting screen", resetting the display's config
https://bugs.kde.org/show_bug.cgi?id=459720 --- Comment #2 from mira...@mirandastreeter.com --- Created attachment 152451 --> https://bugs.kde.org/attachment.cgi?id=152451&action=edit Fixed display settings -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459720] Regression in 5.26 where Plasma falsely detects new display and checks for "unexisting screen", resetting the display's config
https://bugs.kde.org/show_bug.cgi?id=459720 --- Comment #1 from mira...@mirandastreeter.com --- Created attachment 152450 --> https://bugs.kde.org/attachment.cgi?id=152450&action=edit Messed up display settings after reboot -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459720] New: Regression in 5.26 where Plasma falsely detects new display and checks for "unexisting screen", resetting the display's config
https://bugs.kde.org/show_bug.cgi?id=459720 Bug ID: 459720 Summary: Regression in 5.26 where Plasma falsely detects new display and checks for "unexisting screen", resetting the display's config Classification: Plasma Product: KScreen Version: 5.25.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: mira...@mirandastreeter.com Target Milestone: --- Created attachment 152449 --> https://bugs.kde.org/attachment.cgi?id=152449&action=edit Journal logs while issue occurs, see "ADDITIONAL INFORMATION" SUMMARY *** I have three displays. A UHD TV, and two FHD desktop monitors. I'd like for the KDE to remember the TVs display configuration, but after every reboot, or after every login/logout, or after every time the TV is turned on (even if the TV is set to a different output), KDE forgets the configuration of that display. This is new to the 5.26 beta, rolling back to 5.25 resolves the issue. *** STEPS TO REPRODUCE 1. Disable a display and save settings 2. Reboot the PC, or login/logout of KDE, or power on the disabled screen OBSERVED RESULT KDE forgets the config that I've set for that display, and places it at 0,0 overlayed on my monitors EXPECTED RESULT KDE should remember to keep the display disabled, and not reset its coordinates SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel: 5.19.11-arch1-1 (64-bit) Mesa Version: 22.1.7 Operating System: Arch Linux 64-bit Graphics Processor: Radeon RX 6600 XT Graphics Server: X11 ADDITIONAL INFORMATION This used to work on 5.25. This started happening on the 5.26 beta, so this is a regression in behavior and separate from previous display related bugs. I can reliably roll back to 5.25 and the issue goes away. The TV does not need to be powered on for this to happen, just rebooting the PC while the TV's HDMI is plugged in breaks it. When KDE forgets the TV display's config, it puts the TV's display at coordinates 0,0 and re-enables the display, meaning it's overlayed on my monitors. At my desktop I see a blown up wallpaper and windows that maximize both across and below both my monitors, so I'm stuck looking at a duplicated corner of a bigger display until I reset settings. I'll attach a couple screenshots so you can get an idea of what I'm talking about. You'll want to zoom in and focus on the display settings window to see what's happened. The second, smaller screenshot shows what I keep having to flip it back to. I've attached journal output of what occurs when this happens. When observing these logs keep in mind this was tested on the latest main git of plasma-workspace as of yesterday. At 23:10:54, I powered on the television to view a different HDMI input (though, again, there are other ways to reproduce this, the TV could have been powered off and we just reboot the PC). We see a lot of xrandr output (it should be clear which screen is which, the TV is in 4K and there's two 1080p screens, the primary one set to coordinate 0,0 on the left). Eventually we're seeing some amdgpu blanking interval shenanigans (?), likely from the monitors input flipping off and back on, which is how I visually know everything's about to mess up. Then there's some more attempts at changing the config and a whole heap of spamming "requesting unexisting screen 4" and "requesting unexisting screen 3" and some warnings it couldn't read some null configuration properties? That's when the issue occurs, and it re-enables the TV. I then wait a minute and change the settings back in the "Display Configuration" window. The only thing I did was click the TV from the dropdown and uncheck "enabled". I hit "apply" and "keep settings" starting at 23:12:27. We get more "unexisting screen" spam and then this fun when it attempts to apply the config: ``` ASSERT: "view->containment()->lastScreen() == id || view->containment()->lastScreen() == -1" in file /home//Git/plasma-workspace-git/src/plasma-workspace/shell/shellcorona.cpp, line 801 ``` Followed by a coredump and what's clearly the shell crashing. Everything but my windows goes blank black and unresponsive for a few seconds (no wallpaper, no panels) before it recovers and puts everything back where it aught to. Importantly, this particular behavior with the crash is specific to latest git main (5.26.80)! On the regular beta (5.25.90) instead of crashing it just loses the settings of my primary display. Both these issues are besides what I'm primarily concerned about, which is the TV continually getting re-enabled even when it's powered off. I thought this looked similar to #459448, but they're referring to the "location" settings, rather than the location itself. Still, some awfully similar triggers. I do n
[www.kde.org] [Bug 424333] Mention more hardware (or maybe companies rather than models?) at kde.org
https://bugs.kde.org/show_bug.cgi?id=424333 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- It's a lot bigger now! -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 459719] New: Link to https://store.minisforum.com/products/deskmini-um700-manjaro-linux on https://kde.org/hardware
https://bugs.kde.org/show_bug.cgi?id=459719 Bug ID: 459719 Summary: Link to https://store.minisforum.com/products/deskmini-um700-m anjaro-linux on https://kde.org/hardware Classification: Websites Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: n...@kde.org Target Milestone: --- This device runs Manjaro Plasma by default and is prominently featured on https://manjaro.org. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 459718] New: Move the Tuxedo section higher on https://kde.org/hardware
https://bugs.kde.org/show_bug.cgi?id=459718 Bug ID: 459718 Summary: Move the Tuxedo section higher on https://kde.org/hardware Classification: Websites Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: n...@kde.org Target Milestone: --- Tuxedo ships their devices with TuxedoOS by default, which now uses KDE Plasma! Accordingly, that makes Tuxedo a vendor ship ships Plasma by default, so we should move the Tuxedo section higher up and mention that all their devices have Plasma by default -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 459717] New: cli7zplugin: not working with latest upstream 7-zip
https://bugs.kde.org/show_bug.cgi?id=459717 Bug ID: 459717 Summary: cli7zplugin: not working with latest upstream 7-zip Classification: Applications Product: ark Version: 22.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugins Assignee: elvis.angelac...@kde.org Reporter: youlko...@gmail.com CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- SUMMARY cli7zplugin(kerfuffle_cli7z) won't work with upstream 7-zip-full(22.01-3 from AUR) due to "7z l -slt" returning data that is not delimited by any of the currently implemented delimiters(see https://github.com/KDE/ark/blob/master/plugins/cli7zplugin/cliplugin.cpp#L125-L127) and delimited by \n instead. STEPS TO REPRODUCE 1. Open any .7z file(password protection doesn't matter) 2. Ark reports "The archive is empty or Ark could not open its content." in GUI and "ark.part: No entry listed by the plugin" in stdout. EXPECTED RESULT Ark displays the contents of the archive. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux x86_64 (Linux 5.19.11-arch1-1) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Full logs(7z l -slt & ark) and test file upon request. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 446840] Link to https://www.manjarocomputer.eu on https://kde.org/hardware
https://bugs.kde.org/show_bug.cgi?id=446840 --- Comment #2 from Nate Graham --- Oops, sorry I missed your comment. My understanding is that we: 1. List hardware with Plasma by default on top, irrespective of if KDE has a relationship with the vendor 2. List hardware with Plasma as an option below that, irrespective of if KDE has a relationship with the vendor This is based on the fact that, as far as I know, KDE has no relationship with Valve or KFocus, yet they're listed prominently. The https://www.manjarocomputer.eu stuff could probably be in the bottom section, given how Plasma isn't the default choice for the hardware listed there--just one option of several. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 456782] "Save tab layout to file" makes meaningless file
https://bugs.kde.org/show_bug.cgi?id=456782 --- Comment #1 from Kurt Hindenburg --- This is not for tabs but for "splits" inside one tab. Create a split, save it and then look at the json file. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 459558] Cursor jumps while moving
https://bugs.kde.org/show_bug.cgi?id=459558 temptem...@gmail.com changed: What|Removed |Added URL||https://gitlab.freedesktop. ||org/mesa/mesa/-/issues/7351 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459510] [master] Krita segfaults a couple seconds after undoing group creation in certain cases
https://bugs.kde.org/show_bug.cgi?id=459510 --- Comment #3 from tomtomtomreportin...@gmail.com --- You get the same backtrace if you create a group on an empty layer and then close the document. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 459217] resizing when a bash prompt is too long produces lots of garbled text
https://bugs.kde.org/show_bug.cgi?id=459217 Kurt Hindenburg changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Kurt Hindenburg --- Yes, I think there are other BR about this or at least I recall seeing this issue before. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456857] Drawing Tablet and Multi Monitor: Turning off the "Target Display" resets setting to "Follow the active screen", which is also not reflected in the KCM
https://bugs.kde.org/show_bug.cgi?id=456857 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/3004 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455674] Unmoving cursor continually reselects the menu item it's hovering over
https://bugs.kde.org/show_bug.cgi?id=455674 --- Comment #27 from Iyán Méndez Veiga --- These are the versions I have: $ pacman -Q | grep qt5-quick qt5-quick3d 5.15.6+kde+r1-1 qt5-quickcontrols 5.15.6+kde+r0-1 qt5-quickcontrols2 5.15.6+kde+r5-1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 457641] fragment image viewer
https://bugs.kde.org/show_bug.cgi?id=457641 --- Comment #1 from Kurt Hindenburg --- This looks like an OS distribution issue. I would suggest updating your system and trying again. If same issue, ask in your distribution's site. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455674] Unmoving cursor continually reselects the menu item it's hovering over
https://bugs.kde.org/show_bug.cgi?id=455674 --- Comment #26 from Iyán Méndez Veiga --- Can it be that onPositionChanged got broken/changed with recent changes on qt5? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459306] 'Ambiguous Shortcuts' Message is displayed every time Digikam is launched
https://bugs.kde.org/show_bug.cgi?id=459306 --- Comment #3 from PeterJ --- Yes the problem has been solved. Thank you Maik for following up with me. Regards Peter Johnson Maik Qualmann wrote on 26/09/2022 01:47:00: > https://bugs.kde.org/show_bug.cgi?id=459306 > > --- Comment #2 from Maik Qualmann --- > Could the problem be solved? > > Maik > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 459616] DesktopExecParser: Some terminals require "-e " while others just take the command directly
https://bugs.kde.org/show_bug.cgi?id=459616 --- Comment #3 from Andrew Gunnerson --- I went through Arch Wiki's list of terminal emulators and tested most of them: https://wiki.archlinux.org/title/List_of_applications#Terminal_emulators Looks like there are many different ways with how they accept the commands :( Requires `-e` where `-e` signals the end of argument parsing and all further arguments specify the command to run: - alacritty - konsole - lxterminal - mlterm - putty (documented in the help output, but the argument parser fails to handle -e) - qterminal (fails to run command if it contains arguments starting with dash. Eg. `-c` in `qterminal -e bash -c 'sleep 5'`) - roxterm - tilix - urxvt - xterm Requires `-e`, but requires the command to be specified as a single string: - guake - mate-terminal - pantheon-terminal (does not exit after command completion) - terminator - xfce4-terminal Requires no flag after the Exec= command in the .desktop file: - gnome-terminal - kitty - wezterm Requires no flag, but also supports `-e` optionally: - st Don't support running a command at all: - liri-terminal - yakuake -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 459705] Connecting to a remote host via a SSH jump host changes custom profile back to the Konsole default profile
https://bugs.kde.org/show_bug.cgi?id=459705 Einar Aleksejev changed: What|Removed |Added Summary|Connecting to a remote |Connecting to a remote host |server via a SSH jump host |via a SSH jump host changes |changes custom profile back |custom profile back to the |to the Konsole default |Konsole default profile |profile | -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 459705] Connecting to a remote server via a SSH jump host changes custom profile back to the Konsole default profile
https://bugs.kde.org/show_bug.cgi?id=459705 Einar Aleksejev changed: What|Removed |Added Summary|Connecting to a target |Connecting to a remote |server via a SSH jump host |server via a SSH jump host |changes custom profile back |changes custom profile back |to the Konsole default |to the Konsole default |profile |profile -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458608] Defaults button does not reset all settings
https://bugs.kde.org/show_bug.cgi?id=458608 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1179 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-karchive] [Bug 459716] New: Failing test for zstd
https://bugs.kde.org/show_bug.cgi?id=459716 Bug ID: 459716 Summary: Failing test for zstd Classification: Frameworks and Libraries Product: frameworks-karchive Version: 5.98.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: phod...@protonmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY *** Hi, I'm trying to build karchive with zstd support and the test fails. Could you help? *** STEPS TO REPRODUCE 1. guix build karchive OBSERVED RESULT Test project /tmp/guix-build-karchive-5.98.0.drv-0/build Start 1: karchivetest ^[[B1/5 Test #1: karchivetest .Subprocess aborted***Exception: 3.06 sec * Start testing of KArchiveTest * Config: Using QtTest library 5.15.5, Qt 5.15.5 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 10.3.0), unknown unknown PASS : KArchiveTest::initTestCase() PASS : KArchiveTest::testEmptyFilename() PASS : KArchiveTest::testNullDevice() PASS : KArchiveTest::testNonExistentFile() PASS : KArchiveTest::testCreateTar(.tar) RESULT : KArchiveTest::testCreateTar():".tar": 0.24 msecs per iteration (total: 62, iterations: 256) PASS : KArchiveTest::testCreateTarXXX(.tar.gz) RESULT : KArchiveTest::testCreateTarXXX():".tar.gz": 0.41 msecs per iteration (total: 53, iterations: 128) PASS : KArchiveTest::testCreateTarXXX(.tar.bz2) RESULT : KArchiveTest::testCreateTarXXX():".tar.bz2": 0.60 msecs per iteration (total: 78, iterations: 128) PASS : KArchiveTest::testCreateTarXXX(.tar.lzma) RESULT : KArchiveTest::testCreateTarXXX():".tar.lzma": 2.1 msecs per iteration (total: 70, iterations: 32) PASS : KArchiveTest::testCreateTarXXX(.tar.xz) RESULT : KArchiveTest::testCreateTarXXX():".tar.xz": 2.1 msecs per iteration (total: 69, iterations: 32) PASS : KArchiveTest::testCreateTarXXX(.tar.zst) RESULT : KArchiveTest::testCreateTarXXX():".tar.zst": 0.23 msecs per iteration (total: 61, iterations: 256) PASS : KArchiveTest::testReadTar(.tar.gz) RESULT : KArchiveTest::testReadTar():".tar.gz": 0.53 msecs per iteration (total: 68, iterations: 128) PASS : KArchiveTest::testReadTar(.tar.bz2) RESULT : KArchiveTest::testReadTar():".tar.bz2": 0.58 msecs per iteration (total: 75, iterations: 128) PASS : KArchiveTest::testReadTar(.tar.lzma) RESULT : KArchiveTest::testReadTar():".tar.lzma": 0.53 msecs per iteration (total: 68, iterations: 128) PASS : KArchiveTest::testReadTar(.tar.xz) RESULT : KArchiveTest::testReadTar():".tar.xz": 0.53 msecs per iteration (total: 68, iterations: 128) PASS : KArchiveTest::testReadTar(.tar.zst) RESULT : KArchiveTest::testReadTar():".tar.zst": 0.49 msecs per iteration (total: 63, iterations: 128) PASS : KArchiveTest::testUncompress(.tar.gz) PASS : KArchiveTest::testUncompress(.tar.bz2) PASS : KArchiveTest::testUncompress(.tar.lzma) PASS : KArchiveTest::testUncompress(.tar.xz) QWARN : KArchiveTest::testUncompress(.tar.zst) kf.archive: ZSTD_decompressStream returned 18446744073709551606 Unknown frame descriptor FAIL! : KArchiveTest::testUncompress(.tar.zst) 'totalSize > 26000' returned FALSE. () Loc: [/tmp/guix-build-karchive-5.98.0.drv-0/karchive-5.98.0/autotests/karchivetest.cpp(586)] PASS : KArchiveTest::testTarFileData(.tar.gz) PASS : KArchiveTest::testTarFileData(.tar.bz2) PASS : KArchiveTest::testTarFileData(.tar.lzma) PASS : KArchiveTest::testTarFileData(.tar.xz) PASS : KArchiveTest::testTarFileData(.tar.zst) PASS : KArchiveTest::testTarCopyTo(.tar.gz) PASS : KArchiveTest::testTarCopyTo(.tar.bz2) PASS : KArchiveTest::testTarCopyTo(.tar.lzma) PASS : KArchiveTest::testTarCopyTo(.tar.xz) PASS : KArchiveTest::testTarCopyTo(.tar.zst) PASS : KArchiveTest::testTarReadWrite(.tar.gz) PASS : KArchiveTest::testTarReadWrite(.tar.bz2) PASS : KArchiveTest::testTarReadWrite(.tar.lzma) PASS : KArchiveTest::testTarReadWrite(.tar.xz) === Received signal at function time: 9ms, total time: 3054ms, dumping stack === === End of stack trace === QFATAL : KArchiveTest::testTarReadWrite(.tar.zst) Received signal 11 Function time: 9ms Total time: 3054ms FAIL! : KArchiveTest::testTarReadWrite(.tar.zst) Received a fatal error. Loc: [Unknown file(0)] Totals: 33 passed, 2 failed, 0 skipped, 0 blacklisted, 3055ms * Finished testing of KArchiveTest * EXPECTED RESULT KArchiveTest::testUncompress and KArchiveTest::testTarReadWrite succeed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Guix -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459715] Wallpaper "crashes" and only black background shown when external display connected (wayland)
https://bugs.kde.org/show_bug.cgi?id=459715 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 458591] OSC 7 stopped working to preserve path when creating a new tab
https://bugs.kde.org/show_bug.cgi?id=458591 --- Comment #2 from Kurt Hindenburg --- bisect says it is this https://invent.kde.org/utilities/konsole/-/commit/5b5fdb0e32793f5888e3fb915501b07fa80f739a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459715] New: Wallpaper "crashes" and only black background shown when external display connected (wayland)
https://bugs.kde.org/show_bug.cgi?id=459715 Bug ID: 459715 Summary: Wallpaper "crashes" and only black background shown when external display connected (wayland) Classification: Plasma Product: plasmashell Version: 5.25.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: plasma-b...@kde.org Reporter: nortex...@gmail.com CC: notm...@gmail.com, qydwhotm...@gmail.com Target Milestone: 1.0 On wayland, when I connect an external display, often the wallpaper "crashes" and only a black background is shown. The panel and other plasmashell components work just fine. I cannot right-click the desktop to bring up the menu. Restarting plasma brings it back, but sometimes you need to click on the black to show the image, and then unfocusing the desktop makes it show black again. Eventually it goes back to normal. Layout: Folder View Wallpaper type: Image Positioning: Scaled and cropped Image: in home folder -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 459714] Media controller widget with "song name" uses too much horizontal space
https://bugs.kde.org/show_bug.cgi?id=459714 Lucas changed: What|Removed |Added Summary|Media controller widget |Media controller widget |"song name" uses too much |with "song name" uses too |horizontal space|much horizontal space -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 459714] New: Media controller widget "song name" uses too much horizontal space
https://bugs.kde.org/show_bug.cgi?id=459714 Bug ID: 459714 Summary: Media controller widget "song name" uses too much horizontal space Classification: Plasma Product: plasma-mediacenter Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: MediaController Assignee: ksi...@gmail.com Reporter: lcs...@hotmail.com Target Milestone: --- Created attachment 152448 --> https://bugs.kde.org/attachment.cgi?id=152448&action=edit Media widget shows the media title. SUMMARY This is an undesired change in behavior I noticed in Plasma 5.25.90. The new media controller widget has completely changed its appearance and uses too much horizontal space after [this change](https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1892) was introduced. STEPS TO REPRODUCE 1. Add a Media Player widget. 2. Play a song/video. OBSERVED RESULT Media widget shows the title of the media being played (attached). EXPECTED RESULT Expected the old compact clickable button without text, or at least an option to change the introduced behavior. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 145346] Add a shortcut to enable/disable "display categories in thumbnail view"
https://bugs.kde.org/show_bug.cgi?id=145346 Johannes Zarl-Zierl changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/commit/f3b ||12cc595d0a292de1d0d8345bda5 ||8dfb1f4504 --- Comment #3 from Johannes Zarl-Zierl --- Git commit f3b12cc595d0a292de1d0d8345bda58dfb1f4504 by Johannes Zarl-Zierl. Committed on 26/09/2022 at 22:09. Pushed by johanneszarl into branch 'master'. Make "display labels/categories" accessible via "view" menu. Until now, the two settings "display labels in thumbnail view" and "display categories in thumbnail view" were only changeable via the settings dialog. This commit adds them to the "view" menu to be easier to reach. As a side affect, this change also allows both actions to be assigned a keyboard shortcut. M +3-0CHANGELOG.md M +20 -0MainWindow/Window.cpp M +8-3Settings/ThumbnailsPage.cpp M +3-1kphotoalbumui.rc M +24 -2lib/kpabase/SettingsData.cpp M +3-0lib/kpabase/SettingsData.h https://invent.kde.org/graphics/kphotoalbum/commit/f3b12cc595d0a292de1d0d8345bda58dfb1f4504 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 458591] OSC 7 stopped working to preserve path when creating a new tab
https://bugs.kde.org/show_bug.cgi?id=458591 Kurt Hindenburg changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Kurt Hindenburg --- used to work in 22.04 - doesn't in 22.08 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451681] Scan and refresh of album don't rotate HEIC files correctly.
https://bugs.kde.org/show_bug.cgi?id=451681 Hans changed: What|Removed |Added CC||kde-bugs.mail.postfach144@n ||everbox.com --- Comment #13 from Hans --- It seems to me this bug still exists. I'm using digiKam 7.8.0 on openSUSE Tumbleweed. HEIC files in portrait orientation are displayed in landscape orientation, no matter if as thumbnail, as preview or in the editor. They open correctly in Gwenview and GIMP. Reopen? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #19 from Philippe Waroquiers --- I took a look at the attached logs. A first observation: * We have 2 groups of 3 threads that get the 0xe8 syscall return. * For each of these 2 groups, we see a little bit before these 0xe8 return that there is a connection to the embedded gdbserver of Valgrind. Here are the line number and occurrences of the 0xe8 syscall return: 6 matches for "0xe8" in buffer: valgrind 26734:SYSCALL[61639,20](232) ... [async] --> Success(0xe8) 26774:SYSCALL[61639,17](232) ... [async] --> Success(0xe8) 26789:SYSCALL[61639,15](232) ... [async] --> Success(0xe8) 31141:SYSCALL[61639,14](232) ... [async] --> Success(0xe8) 31176:SYSCALL[61639,16](232) ... [async] --> Success(0xe8) 31206:SYSCALL[61639,13](232) ... [async] --> Success(0xe8) And here are the 3 matches for the gdbserver: 3 matches for "TO DEBUG" in buffer: valgrind 286:==61639== TO DEBUG THIS PROCESS USING GDB: start GDB like this 26668:==61639== TO DEBUG THIS PROCESS USING GDB: start GDB like this 31121:==61639== TO DEBUG THIS PROCESS USING GDB: start GDB like this where the first one is the message produced at startup. Maybe this is a modified executable that triggers a call to vgdb/gdb when it encounters this syscall problem ? Or is there something that attaches to the valgrind gdbserver or sends a command to it ? Because in this last case, we could possibly have an interaction between vgdb and many threads blocked in syscalls. We see in the stderr trace the following: --61639:2: gdbsrv stored register 0 size 8 name rax value 0007 tid 1 status VgTs_WaitSys --61639:2: gdbsrv stored register 0 size 8 name rax value 00e8 tid 15 status VgTs_WaitSys --61639:2: gdbsrv stored register 0 size 8 name rax value 00e8 tid 17 status VgTs_WaitSys --61639:2: gdbsrv stored register 0 size 8 name rax value 00e8 tid 20 status VgTs_WaitSys --61639:1: gdbsrv stop_pc 0x4CAC04E changed to be resume_pc 0x4C9CD7F: poll (poll.c:29) --61639:2: gdbsrv stored register 0 size 8 name rax value 0007 tid 1 status VgTs_WaitSys --61639:2: gdbsrv stored register 0 size 8 name rax value 00e8 tid 13 status VgTs_WaitSys --61639:2: gdbsrv stored register 0 size 8 name rax value 00e8 tid 14 status VgTs_WaitSys --61639:2: gdbsrv stored register 0 size 8 name rax value 00e8 tid 16 status VgTs_WaitSys --61639:1: gdbsrv VG core calling VG_(gdbserver_report_signal) vki_nr 15 SIGTERM gdb_nr 15 SIGTERM tid 1 - So, for the 2 groups of 3 threads that got 0xe8 syscall return, we see that the valgrind gdbserver was instructed to put 0xe8 in the rax register. It is however difficult to relate the stderr output with the valgrind output. If you could redo the trace with the none tool, but keep together the stderr and the valgrind output (i.e. let valgrind do its output to stderr together with its debug log) + add --time-stamp=yes that might help to see what happens in which order. I have to say that at this state, I have not much idea what other things to look at. To further investigate and possibly find the bug, likely we will need an (easy to run) reproducer. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 459713] New: Plasma-nm should do a better job at displaying errors regrading your network.
https://bugs.kde.org/show_bug.cgi?id=459713 Bug ID: 459713 Summary: Plasma-nm should do a better job at displaying errors regrading your network. Classification: Plasma Product: plasma-nm Version: 5.25.5 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: linus...@gmail.com CC: jgrul...@redhat.com Target Milestone: --- SUMMARY *** When trying to set up my school wireless via plasma-nm, no matter what I did, I couldn't connect to my school's wireless. It turns out that I had gotten the network domain incorrect. I wasn't able to figure this out however, until I tried to connect while journalctl was running and shot out an error, as plasma-nm would not present errors to me that would actually be able to aid me in resolving my network issue. So it would be great if plasma-nm would either have the capability to show more errors than just whether your password was wrong, or a more generic error saying that it couldn't connect. Instead, I think it should also be able to tell you whether your domain is wrong when connecting to a WPA2 enterprise network for example, or that you are using the incorrect type of WPA2 security for your enterprise connection. I am pretty sure these are all things that would most likely show errors in journalctl if you got them incorrect, so it would be great if plasma-nm's gui could display them as well. And if it can't, at least get plasma-nm to display all the errors regarding your network in a nice list, so you can at least get a hint at what is wrong. *** ISSUE: Plasma-nm's errors are not good enough to be helpful for more than just an incorrect network password. EXPECTED RESULT For plasma-nm to have the ability to display a wide range of errors for most connection issues that arise. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 459616] DesktopExecParser: Some terminals require "-e " while others just take the command directly
https://bugs.kde.org/show_bug.cgi?id=459616 --- Comment #2 from Andrew Gunnerson --- Unfortunately, yes. With xterm, it fails when parsing the arguments without `-e`. With Konsole, konsole -e bash -c 'echo abc' runs `bash -c 'echo abc'` as expected, but: konsole -- bash -c 'echo abc' seems to just ignore the extra arguments. (And arguments cannot be parsed without the `--`.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #1 from Aleix Pol --- It would be useful to get some details as to what could be special to your system. Would you be able to see what's special about it? This is not something we (I?) have seen before. Some ideas: Can you reproduce this on 22.04? How about on another distro like Fedora? Note that to test them you can generally just boot into their live images on USB, no need to go all the way. What graphics card and drivers are you using? Do you get any outstanding error messages in ~/.local/share/sddm/wayland-session.log? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 431300] Equity records
https://bugs.kde.org/show_bug.cgi?id=431300 --- Comment #2 from Jack --- Reading my reply now, I realize it wasn't complete accurate in describing things. I apologize for that. Part of the issue is a potential confusion with terminology. Any ownership of a stock (or mutual fund) requires a SECURITY to exist. That contains the basic information about the stock, such as trading symbol, exchange, and source of online quotes. Then, for each Investment Account which owns any of that Security, there does need to be an EQUITY account. That is used to keep the shares owned in that Investment Account separate from shares owned in any other Investment account. One example of the need for this is that the two investment accounts may have different currencies, even if that is not a common occurrence. As you point out, there are some problems with this specific implementation - there is a danger of creating a new SECURITY when adding an EQUITY to an Investment account. Bug 443566 is specifically about making this easier, and less prone to error. The current way also duplicates some information about the stock, which can lead to confusion. The development team is about to start reviewing all open bugs about Investments, and hopefully some of them will be addressed in the coming months. As developer resources are scarce, there is no timetable for this. The process of adding a Security to an Investment Account will certainly be considered, as will whether a separate Equity Account per Investment Account is really necessary. I think it's fair to say that the goals are increased functionality with decreased chances for errors and confusion, but anything which requires major changes to the underlying data structures may end up further deferred. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #4 from Jason Straight --- (In reply to Nate Graham from comment #3) > That will be because of another bug (monitor information stored in a > different way on Wayland vs X11). If you correct those things, reboot, and > then try to reproduce the issue, does it happen again? Still happens. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 458858] "Open File Manager" does not work as expected when using tmux
https://bugs.kde.org/show_bug.cgi?id=458858 Kurt Hindenburg changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455674] Unmoving cursor continually reselects the menu item it's hovering over
https://bugs.kde.org/show_bug.cgi?id=455674 Nate Graham changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #25 from Nate Graham --- I'm at a loss to explain how this issue could possibly still be happening for you. Can anyone else using the beta reproduce it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455674] Unmoving cursor continually reselects the menu item it's hovering over
https://bugs.kde.org/show_bug.cgi?id=455674 Nate Graham changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #24 from Nate Graham --- Hmm, then you have the change. Re-opening. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 459712] New: Profile Does Not Save Changes
https://bugs.kde.org/show_bug.cgi?id=459712 Bug ID: 459712 Summary: Profile Does Not Save Changes Classification: Applications Product: konsole Version: 22.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: wulfwine.ceolm...@gmail.com Target Milestone: --- SUMMARY After closing konsole, any changes made to a profile are not saved. Additionally, any newly created profiles are not saved. STEPS TO REPRODUCE 1. Open Konsole 2. Make a change to a profile/ make a new profile 3. Close Konsole 4. Open Konsole OBSERVED RESULT Edits to Konsole profiles have not been saved EXPECTED RESULT Edits to Konsole profiles to be saved SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 5.15.65-1 MANJARO (64- KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459253] External screen mode is set to "clone" after every login or screen locking
https://bugs.kde.org/show_bug.cgi?id=459253 Nate Graham changed: What|Removed |Added Version Fixed In||5.26 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459404] Crash in KWin::Window::isDesktop()
https://bugs.kde.org/show_bug.cgi?id=459404 Nate Graham changed: What|Removed |Added Version Fixed In||5.26 -- You are receiving this mail because: You are watching all bug changes.
