[kdenlive] [Bug 430734] New: Increasing preview resolution glitches out preview when GPU processing is enabled
https://bugs.kde.org/show_bug.cgi?id=430734 Bug ID: 430734 Summary: Increasing preview resolution glitches out preview when GPU processing is enabled Product: kdenlive Version: 20.12.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- I'm using the latest kdenlive 20.12 flatpak. I was playing around with GPU processing. My preview resolution was set to 540p (I was also using proxys, but disabling them made no difference). When I changed the preview resolution to 1:1 (1080p), the preview window looked zoomed in with weird artifacts. Using an AMD RX580 with Mesa 20.2.3 btw. STEPS TO REPRODUCE 1. Set the playback resolution to less than 1:1 (in my case 540p) 2. Enable Movit GPU processing 3. After that, change the playback resolution to something bigger (1:1) OBSERVED RESULT Preview glitches out with artifacts until Kdenlive is restarted EXPECTED RESULT Playback resolution changes like normal -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430573] New: Plasma on Wayland crashes when dragging an application out of the menu
https://bugs.kde.org/show_bug.cgi?id=430573 Bug ID: 430573 Summary: Plasma on Wayland crashes when dragging an application out of the menu Product: plasmashell Version: 5.20.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: firlaevhans.fi...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Flags: Wayland+ When I tried to drag an application from the application menu or from KRunner into Latte-Dock, the screen froze as soon as the mouse cursor left the menu, then I got back to SDDM. STEPS TO REPRODUCE 1. Start Plasma on Wayland 2. Open the application menu or Krunner 3. Try to drag the application out of the menu OBSERVED RESULT The Plasma Wayland session crashes. On X11, it does not. EXPECTED RESULT Applications can be dragged from the menu to the likes of Latte Dock etc. SOFTWARE/OS VERSIONS OS: Manjaro KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430573] Plasma on Wayland crashes when dragging an application out of the menu
https://bugs.kde.org/show_bug.cgi?id=430573 Firlaev-Hans changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org Component|general |general Target Milestone|1.0 |--- Product|plasmashell |kwin --- Comment #2 from Firlaev-Hans --- (In reply to Nate Graham from comment #1) > Can you add a backtrace? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl Looks like it is kwin_wayland, not plasmashell that crashed. Whoops. Also, the same crash can happen when dragging around items in the dock. Unfortunately the coredump for kwin_wayland is "truncated" so I'm afraid this might not be very useful: #0 0x7ff96a2162b8 in ?? () Backtrace stopped: Cannot access memory at address 0x7ffe871b54c0 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #5 from Firlaev-Hans --- I also noticed this problem, Yakuake doesn't retract when it loses focus on Wayland, but it works fine on X11. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430624] Terminal Crashes in Dolphin everytime dolphin is opened
https://bugs.kde.org/show_bug.cgi?id=430624 Firlaev-Hans changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||firlaevhans.fiete@protonmai ||l.com --- Comment #1 from Firlaev-Hans --- I've also seen this happen. I usually have a terminal open in Dolphin at all times. I used to use zsh, now I use fish. zsh often crashed upon starting Dolphin, and fish sometimes either crashes completely as well or shows error messages which I would gladly post here but of course right now I can't get it to fail. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430573] Plasma on Wayland crashes when dragging an application out of the menu
https://bugs.kde.org/show_bug.cgi?id=430573 Firlaev-Hans changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |FIXED --- Comment #3 from Firlaev-Hans --- I tried the latest KDE Neon Unstable in a VM and didn't run into this issue on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 428476] When ripping an audio CD and the artist has a / in the name (AC/DC), unwanted subfolders are created
https://bugs.kde.org/show_bug.cgi?id=428476 --- Comment #1 from Firlaev-Hans --- Note: The target directory was on an NTFS drive which allows '/' in filenames, manually renaming the folder to "AC⁄DC - Rock or Bust" worked fine. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 428476] New: When ripping an audio CD and the artist has a / in the name (AC/DC), unwanted subfolders are created
https://bugs.kde.org/show_bug.cgi?id=428476 Bug ID: 428476 Summary: When ripping an audio CD and the artist has a / in the name (AC/DC), unwanted subfolders are created Product: k3b Version: 20.08 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Copying Assignee: k...@kde.org Reporter: firlaevhans.fi...@protonmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- I was ripping an AC/DC CD to flac files with default settings and instead of making a folder called "AC⁄DC - Rock or Bust" in my Music folder K3b made a folder called "AC" with a sub folder "DC - Rock or Bust" STEPS TO REPRODUCE 1. Try to Rip a CD where either the Artist (%A) or the Title (%T) includes a / 2. Look at the output directory OBSERVED RESULT A '/' in the name creates a subfolder (Music/AC/'DC - Rock or Bust') EXPECTED RESULT A directory with a / in it's name (Music/'AC/DC - Rock or Bust') SOFTWARE/OS VERSIONS OS: Manjaro testing KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 K3b Version: 20.08.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439209] New: Panels with adaptive transparency don't become transparent when "show desktop" keyboard shortcut is used
https://bugs.kde.org/show_bug.cgi?id=439209 Bug ID: 439209 Summary: Panels with adaptive transparency don't become transparent when "show desktop" keyboard shortcut is used Product: plasmashell Version: 5.22.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: 1.0 SUMMARY When you have a "minimize all windows" widget in the panel with adaptive transparency and click it, the panel will become translucent as expected. However, when using a global keyboard shortcut for showing the desktop, the panel stays opaque. STEPS TO REPRODUCE 1. Have a panel with adaptive transparency enabled 2. Have a Kwin keyboard shortcut for "show desktop" 3. Open and maximize a window so the panel becomes opaque 4. Press the key combination for "show desktop" OBSERVED RESULT The panel stays opaque, even though no maximized windows are shown EXPECTED RESULT The panel should become translucent when the desktop is shown, just like when using the widget. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.13-zen1-1-zen (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416690] Why move to deleted folder? on mount directory.
https://bugs.kde.org/show_bug.cgi?id=416690 --- Comment #3 from Firlaev-Hans --- (In reply to Nate Graham from comment #2) > Sorry, I'm having a hard time understanding the problem. Could you attach a > screenshot--or even better, a screen recording--that shows the issue? Thanks! Unfortunately it's kind of difficult to get a screen capture of a bug that you can't reproduce on purpose. I just tried to make the bug happen again with OBS running but... I couldn't... But in short, sometimes when you delete a folder in dolphin, and press enter in the confirmation dialog, dolphin will enter the deleted directory (and complain that the path no longer exists). I haven't figured out if there's a specific reason why this would occur, because, again, this bug never happens when I WANT it to happen, but it happens rather often in normal use. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416690] Why move to deleted folder? on mount directory.
https://bugs.kde.org/show_bug.cgi?id=416690 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #1 from Firlaev-Hans --- I'm not quite sure if what I'm experiencing is exactly what you are describing but I'm regularly encountering a similar bug: The folder doesn't need to be on an external drive. Select a folder and hit shift+delete to delete it without moving it to the trash first. In the confirmation dialog, just hit the enter key. The dialog window will close, the folder will be deleted, but then dolphin will enter the (deleted) directory and show a warning that the folder doesn't exist. This bug doesn't always occur, and I have not been able to find out how exactly you can reproduce this bug. I just had that bug happen again, but after that I created and deleted a bunch more test folders and couldn't reproduce it again. First I thought maybe the main dolphin window still registers the press of the enter key after the dialog closes and moves into the directory right as it is being deleted, but when I purposely keep the enter key pressed a bit longer, that doesn't make the bug occur. I'm on Dolphin 20.12.3 on Arch Linux right now but I've encountered that bug every so often for months if not years. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416690] Why move to deleted folder? on mount directory.
https://bugs.kde.org/show_bug.cgi?id=416690 --- Comment #5 from Firlaev-Hans --- (In reply to Nate Graham from comment #4) > I see, that helps. Probably what happens is that the return key gets > forwarded to the view after the dialog closes, and there' a brief second in > which the folder is still visible, so Dolphin tries to enter it, but this > fails because a micro-second after that, it gets deleted. > > That said, I cannot reproduce the issue with the current git master version. > Could you please try again with the version of Dolphin in Kubuntu 21.04, > which is due to be released in a few days? I just tried it on the Ubuntu 21.04 Beta as well as git master and couldn't reproduce it either, but then again, I can't even reproduce it with the version on which I just experienced that bug a few days ago (also 20.12.3 on Arch). So even if you couldn't reproduce it the bug may very well still exist, I just have no idea how to trigger it (probably the timing and perhaps the size of the folder have to be just right?) But then considering that this bug only happens every once in a while and is barely annoying I don't know whether it is worth spending too much time trying to hunt it down. But the enter key being forwarded to the main dolphin window in the split second where the folder is still there would be my best guess too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441354] New: Touchscreens: Tapping and holding on a panel should show a context menu or enter panel edit mode
https://bugs.kde.org/show_bug.cgi?id=441354 Bug ID: 441354 Summary: Touchscreens: Tapping and holding on a panel should show a context menu or enter panel edit mode Product: plasmashell Version: 5.22.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: 1.0 SUMMARY Nothing happens when you tap and hold on a panel STEPS TO REPRODUCE 1. Be on a device with a touchscreen (such as a 2in1 laptop) 2. Tap and hold on the panel OBSERVED RESULT Nothing happens EXPECTED RESULT When you touch (and hold) an empty area on the panel, you should either get into panel edit mode or show the right click context menu. Touching and holding on an applet or system tray icon should show its right-click context menu (this seems to work some of the time but it is very inconsistent) SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83 Qt Version: 5.15.2 Both Wayland and X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441533] New: Dolphin's terminal panel is partially transparent on Wayland even though it shouldn't be with Breeze
https://bugs.kde.org/show_bug.cgi?id=441533 Bug ID: 441533 Summary: Dolphin's terminal panel is partially transparent on Wayland even though it shouldn't be with Breeze Product: dolphin Version: 21.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY In Konsole, I set the background to be 10% transparent and blurred. On X11 with Breeze, this setting does not affect Dolphins terminal panel which always stays opaque. On Wayland, however, it does become transparent (except for a glitchy looking opaque bar at the top). Also, the background is only transparent, not blurred. It looks rather broken. STEPS TO REPRODUCE 1. Enable background transparency in Konsole. Also enable blur. 2. Use the default Breeze application style (I used the Breeze Dark color scheme) 3. Open Dolphin on Wayland 4. Show the built-in terminal with F4. OBSERVED RESULT The terminal panel is transparent, but not blurred. A flickering bar at the top of the terminal panel is not transparent and seems to show parts of older frames of the terminal some of the time. EXPECTED RESULT The terminal inside Dolphin should either a) ignore the transparency setting and stay opaque like it does on X11, or b) it should be transparent AND BLURRED, without a weird glitchy bar at the top (like on X11 with some third party Application styles). SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 441033] New: With a global menu bar, the layout indicator/switcher is not shown
https://bugs.kde.org/show_bug.cgi?id=441033 Bug ID: 441033 Summary: With a global menu bar, the layout indicator/switcher is not shown Product: kdenlive Version: 21.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY The layout switcher that lets you switch between Logging, Editing, Audio, Effects and Color resides in the top right corner in the menu bar. But because I use a global menu in Plasma, the menu bar is not shown inside the kdenlive window, thus the layout indicator is nowhere to be found. STEPS TO REPRODUCE 1. Add a global menu widget to your Panel in KDE Plasma 2. Open Kdenlive OBSERVED RESULT The layout switcher is gone, as it is not shown in the global menu. EXPECTED RESULT The layout switcher is still shown somewhere, even though there's no menu bar inside the kdenlive window. ADDITIONAL INFORMATION I know that you can switch between layouts using keyboard shortcuts or the "View" menu, but that is not as convenient and most importantly there's no visual indication what layout you are currently in. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 441960] New: Several unnecessary horizontal scroll bars in Elisa
https://bugs.kde.org/show_bug.cgi?id=441960
Bug ID: 441960
Summary: Several unnecessary horizontal scroll bars in Elisa
Product: Elisa
Version: 21.08.1
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: general
Assignee: matthieu_gall...@yahoo.fr
Reporter: firlaevhans.fi...@protonmail.com
Target Milestone: ---
Created attachment 141274
--> https://bugs.kde.org/attachment.cgi?id=141274=edit
Screenshot of the scroll bar
SUMMARY
Look at the screenshot: There are multiple horizontal scroll bars that can't
actually scroll. Am I missing something? What are they for?
STEPS TO REPRODUCE
1. Just... look at Elisa
OBSERVED RESULT
A horizontal scrollbar is drawn
- at the bottom of the playlist view
- at the bottom of the left sidebar
- at the bottom of whatever is in the middle, except for "Aktuelle Wiedergabe"
("Current Playback")
- at the bottom of the playlist in party mode
but it doesn't go anywhere, it just... exists and changes color when your mouse
hovers over it, but it doesn't do anything. It just makes the interface look
more busy, which is the opposite of what Elisa needs.
EXPECTED RESULT
The scroll bars should not exist unless they have a purpose (such as showing
longer song titles that are cut off, which currently they currently can't)
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 442662] New: KWindowSystem on Wayland is missing many signals, some of which are needed by Yakuake
https://bugs.kde.org/show_bug.cgi?id=442662 Bug ID: 442662 Summary: KWindowSystem on Wayland is missing many signals, some of which are needed by Yakuake Product: frameworks-kwindowsystem Version: 5.86.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- Yakuake, the drop-down terminal, uses signals in KWindowSystem (https://api.kde.org/frameworks/kwindowsystem/html/classKWindowSystem.html) for some functionality, such as activeWindowChanged() to check if it has lost focus. The needed signals are not implemented in the Wayland version of KWindowSystem, which causes lots of issues with Yakuake's behavior (e. g. it can't retract automatically upon loosing focus (See Bug 380497), it can't stay on top of other Windows and more) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 --- Comment #14 from Firlaev-Hans --- I opened a bug report for KWindowSystem: Bug 442662 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 443519] New: Elisa can't read Ogg/Opus files if the extension is .ogg
https://bugs.kde.org/show_bug.cgi?id=443519 Bug ID: 443519 Summary: Elisa can't read Ogg/Opus files if the extension is .ogg Product: Elisa Version: 21.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY Opus is the successor to the Vorbis audio codec. Both are usually stored in a OGG container, however for Opus the extension is typically .opus and not .ogg, but I have run into several cases where a .ogg file contained an Opus stream. However, unlike any other media player I tried, Elisa will only play Opus if the extension is .opus, and it will only play .ogg if the codec is vorbis. STEPS TO REPRODUCE 1. Encode some audio with libopus with ffmpeg, give it the file extension .ogg 2. Open it in Elisa 3. Rename it to .opus 4. Try again OBSERVED RESULT Elisa will only play the file once it has been renamed to .opus, not .ogg, and seemingly assumes that .ogg files always contain a Vorbis stream. EXPECTED RESULT Elisa should detect that the OGG container contains an Opus stream and play it, regardless of the file extension SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444175] New: Wayland: After rotating the screen twice and then opening the system tray, the wallpaper is cut off
https://bugs.kde.org/show_bug.cgi?id=444175 Bug ID: 444175 Summary: Wayland: After rotating the screen twice and then opening the system tray, the wallpaper is cut off Product: plasmashell Version: 5.22.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: firlaevhans.fi...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 142709 --> https://bugs.kde.org/attachment.cgi?id=142709=edit Screenshot of incorrectly rendered wallpaper SUMMARY Not sure if this is the right place to file this bug but: After rotating the screen of my 2in1 laptop from horizontal to vertical and back, the wallpaper looks normal at first, but after opening the system tray, the right half of the screen is black. STEPS TO REPRODUCE 1. Enable auto-rotation on a supported device on Wayland 2. Rotate your screen from horizontal to vertical and then back to horizontal 3. Open the system tray OBSERVED RESULT The wallpaper is rendered like in vertical mode, thus appears cut off (see screenshot) EXPECTED RESULT The wallpaper should look normal SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.12-200.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx Memory: 6.7 GiB of RAM Graphics Processor: AMD Radeon™ Vega 3 Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443699] New: Video DVDs don't show up in "Disks & Devices" Widget, but they do in Dolphin
https://bugs.kde.org/show_bug.cgi?id=443699 Bug ID: 443699 Summary: Video DVDs don't show up in "Disks & Devices" Widget, but they do in Dolphin Product: plasmashell Version: 5.22.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Disks & Devices Assignee: plasma-b...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: 1.0 SUMMARY I noticed that when I insert a DVD movie, it shows up as removable media in Dolphin, but the "Disks & Devices" Widget in the system tray shows nothing 95% of the time STEPS TO REPRODUCE 1. Have a DVD reader 2. Insert a movie DVD 3. Look at "Disks & Devices" OBSERVED RESULT Nothing shows up most of the time EXPECTED RESULT The DVD should show up in "Disks & Devices" with the option to mount it, play it, rip it with K3b, eject it etc. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.11-zen1-1-zen (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 --- Comment #15 from Firlaev-Hans --- (In reply to Firlaev-Hans from comment #14) > I opened a bug report for KWindowSystem: Bug 442662 So basically, they're not going to implement those signals in KWindowSystem on Wayland, and Yakuake will have to find another way to get this functionality on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 443019] New: Some Mails are displayed as HTML by default even though it is not set as preferred
https://bugs.kde.org/show_bug.cgi?id=443019 Bug ID: 443019 Summary: Some Mails are displayed as HTML by default even though it is not set as preferred Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY In KMail's settings under "security" I have NOT checked "Prefer HTML view over plain text". I even went into the folder preferences for my inbox and specifically set it to prefer plain text over HTML, yet many e-mails are displayed as HTML by default. After opening the mail I can manually (and only temporarily) switch to plain text view, but I'd like to force that as the default for all mails. STEPS TO REPRODUCE 1. Make sure that HTML view is NOT preferred in the global security setings 2. Optionally, also set the inbox to prefer plain text view. 3. Open some mails from various sources, some of them will still open in HTML view OBSERVED RESULT Some mails open in HTML view even though plain text view is preferred EXPECTED RESULT When HTML view is not preferred (when plain text is preferred), ALL mails should be forced into plain text view by default when opening them. Also, it might be less confusing if in KMail's security settings there were radio buttons for selecting either "prefer plain text" or "prefer HTML" like in the folder settings, instead of just a check box for "prefer HTML view" SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444172] [Wayland] Ghost window left behind when moving wayland windows to other VD/Activity using key bindings or pager widget
https://bugs.kde.org/show_bug.cgi?id=444172 Firlaev-Hans changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #9 from Firlaev-Hans --- Can confirm on Neon unstable, though only if more than one monitor is active. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445436] [Wayland] On multi screen setups, moving a window to a different workspace makes it flicker and also stay visible on the current workspace
https://bugs.kde.org/show_bug.cgi?id=445436 Firlaev-Hans changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Firlaev-Hans --- Indeed, that seems to be the same issue. *** This bug has been marked as a duplicate of bug 444172 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444172] [Wayland] Ghost window left behind when moving wayland windows to other VD/Activity using key bindings or pager widget
https://bugs.kde.org/show_bug.cgi?id=444172 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #8 from Firlaev-Hans --- *** Bug 445436 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444172] [Wayland] Ghost window left behind when moving wayland windows to other VD/Activity using key bindings or pager widget
https://bugs.kde.org/show_bug.cgi?id=444172 --- Comment #10 from Firlaev-Hans --- (In reply to Firlaev-Hans from comment #9) > Can confirm on Neon unstable, though only if more than one monitor is active. Never mind the "only with more than one monitor" thing. I can reproduce it with only one monitor on the latest Neon unstable as well, but only some of the time, whereas it happens every single time with two monitors. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 --- Comment #24 from Firlaev-Hans --- (In reply to Nate Graham from comment #23) > OK, KeepOpen=false seems to work for me, but KeepOpen=true doesn't. Is that > what you're seeing too? If so that's a separate issue. This is indeed just a fix for KeepOpen=false. But KeepOpen=true already works, it always has. All it's supposed to do AFAIK is to not retract Yakuake when it looses focus, so it just goes behind the currently focused window (like any other normal window would). And that's what it does, on both X11 and Wayland. What still doesn't work on Wayland is "KeepAbove=true", which is a separate option that, when combined with KeepOpen=true, makes Yakuake always stay in the foreground / as the top most window even when it's not focused. This can be worked around by the user with a KWin rule to keep Yakuake in the foreground. I'm not sure if that issue can be fixed without direct cooperation with KWin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399763] Window-Specific Overrides rule using the window-class does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=399763 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #5 from Firlaev-Hans --- (In reply to Philipp Reichmuth from comment #4) > It seems unlikely that this will ever work though, because window class is > an X11 property. It is possible to set KWin Window rules (under System Settings > Window Management) on Wayland, defined by the window class. Even "Detect Window Properties" works there. I don't see why it couldn't work the same way for Breeze decoration window specific overrides. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399763] Window-Specific Overrides rule using the window-class does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=399763 --- Comment #7 from Firlaev-Hans --- Isn't this technically a bug in "Breeze" > "window decoration", and not in "KWin" > "wayland-generic"? At least the relevant code seems to reside at https://invent.kde.org/plasma/breeze/-/tree/master/kdecoration -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445230] Kdenlive crashes when trying to add a video to the timeline that has more audio tracks than the project currently has
https://bugs.kde.org/show_bug.cgi?id=445230 --- Comment #2 from Firlaev-Hans --- (In reply to emohr from comment #1) > Thank you for reporting. Please try with the AppImage. It should appear a > massage to create more audio tracks. It does indeed work with the AppImage of 21.08.3, the message about adding an audio track appears as soon once the video file is imported and dragging it to the timeline creates a warning, without that constant warning sound and without crashing. Something must be wrong with the build on Arch Linux then. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445992] New: Can't switch from "only internal display" directly to "only external display" or vice versa on Wayland
https://bugs.kde.org/show_bug.cgi?id=445992 Bug ID: 445992 Summary: Can't switch from "only internal display" directly to "only external display" or vice versa on Wayland Product: KScreen Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasma Applet Assignee: kscreen-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY On Wayland when you connect an external screen to a laptop and, using the quick display configuration widget or popup, first select "Switch to external display" (leftmost option), then to "Switch to internal display" (or vice versa), nothing happens. In order to switch to the external display, a different option (either extend to the left/right or have them both in sync) As my system is set to German I'm not sure exactly what the options are called in English. STEPS TO REPRODUCE 1. Be on Wayland on a laptop with an external display 2. Using the quick display configuration applet or the Meta+P popup, select "Switch to external display" 3. After that, select "Switch to external display" (won't work) 4. Select "Extend to the right" 5. Try "Switch to external display" again (now it works) OBSERVED RESULT "Switch to external display" does not work while only the internal display is active, only if both are active (same for "Switch to internal display") EXPECTED RESULT The option should do what it says it does SOFTWARE/OS VERSIONS Operating System: KDE Neon Unstable KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445993] New: After switching between the options in Quick Display Configuration applet several times in a row, the session completely freezes (Wayland)
https://bugs.kde.org/show_bug.cgi?id=445993 Bug ID: 445993 Summary: After switching between the options in Quick Display Configuration applet several times in a row, the session completely freezes (Wayland) Product: KScreen Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasma Applet Assignee: kscreen-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY Switching between the various options in the Quick Display Configuration applet or Meta+P popup a couple of times in a row on Wayland causes the session to completely freeze (except for the mouse cursor). At that point I can only switch to a tty or hard reset the computer. The following line is printed to the journal several times (36 times in fact): plasmashell[3887]: requesting unexisting screen 1 TO REPRODUCE just play with the Quick Display Configuration widget on Wayland a little bit until this happens. SOFTWARE/OS VERSIONS Operating System: KDE Neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 445158] Yakuake does not open on the screen where the mouse pointer is
https://bugs.kde.org/show_bug.cgi?id=445158 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Firlaev-Hans --- Can confirm on KDE Neon unstable. Oddly enough when I tried it yesterday on my main (Arch Linux) PC on Wayland I could NOT confirm this, Yakuake actually DID open on the screen with the mouse. However, it was not resized correctly for the secondary monitor which has a lower resolution, thus it was cut off to the right. I have not found any configuration difference between the two machines that would explain the different behavior (both were also running the master build of Yakuake) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445438] New: If plasmashell has been restarted in a session, the widget explorer does not open at all
https://bugs.kde.org/show_bug.cgi?id=445438 Bug ID: 445438 Summary: If plasmashell has been restarted in a session, the widget explorer does not open at all Product: plasmashell Version: 5.23.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: 1.0 SUMMARY The widget explorer sidebar simply will not open if you have restarted plasmashell with plasmashell --replace. Clicking "Add widgets" in a panel's or desktop's right click menu or using the keyboard shortcut does nothing at all in that case. You have to log out and log back in again to be able to open it again. STEPS TO REPRODUCE 1. In a fresh Plasma session, open the widget explorer sidebar: It works as expected 2. Now run "plasmashell --replace" in KRunner or the terminal 3. Try to open the widget explorer again OBSERVED RESULT The widget explorer won't open after restarting plasmashell until you log out and log back in again or reboot EXPECTED RESULT The widget explorer should open normally even after plasmashell has been restarted SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-zen1-1-zen (64-bit) Graphics Platform: Both X11 and Wayland -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 445157] KRunner always opens on a particular screen in Wayland (unlike X11, where it opens where the mouse is)
https://bugs.kde.org/show_bug.cgi?id=445157 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Firlaev-Hans --- Can confirm on Arch Linux (Plasma 5.23.3) as well as KDE Neon unstable, Krunner always opens on the left screen even if the cursor is on the right screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445436] New: [Wayland] On multi screen setups, moving a window to a different workspace makes it flicker and also stay visible on the current workspace
https://bugs.kde.org/show_bug.cgi?id=445436 Bug ID: 445436 Summary: [Wayland] On multi screen setups, moving a window to a different workspace makes it flicker and also stay visible on the current workspace Product: kwin Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY On Wayland, when I use a keyboard shortcut to move a window to a different workspace / virtual desktop on a system with two monitors, the window flickers a lot, but stays visible on the current workspace. Clicking it makes it disappear, though while it is still visible you can use a keyboard shortcut again to move it to yet another workspace (or back to the current one). This issue does NOT occur with just one monitor (but I think it used to). It also does NOT occur if instead of a keyboard shortcut, the Alt+F3 menu is used to move the window to a different workspace STEPS TO REPRODUCE 1. Be on Wayland and have more than one monitor 2. Have >1 workspace and set KWin keyboard shortcuts for moving a window to a specific workspace 3. Use the shortcut to move a window to a different workspace OBSERVED RESULT The window flickers and stays visible on the current workspace even though it was moved to a different one EXPECTED RESULT The window should simply disappear since it is no longer supposed to be on that workspace. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-zen1-1-zen (64-bit) Graphics Platform: Wayland ... and also on KDE Neon unstable -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445443] New: Wayland: Issues with the display switcher widget or popup (Meta+P) - I dare you to play with it until it breaks
https://bugs.kde.org/show_bug.cgi?id=445443 Bug ID: 445443 Summary: Wayland: Issues with the display switcher widget or popup (Meta+P) - I dare you to play with it until it breaks Product: KScreen Version: git Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasma Applet Assignee: kscreen-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY On Wayland I'm experiencing issues with the quick display switcher thingy that pops up with Meta+P, as well as its system tray applet counterpart. If you have a laptop and an external display I encourage you to try switching between all the options for a minute (on Wayland), you are guaranteed to run into various bugs. Among the issues I personally found are: - If you first set only the internal display to be active and then switch to only the external display or vice versa, nothing happens. You have to choose "extend to the left/right" first and then choose to switch to the external (/internal) display only in order for it to work - Sometimes when switching to the internal display, the wallpaper is cut off (likely because the external screen has a different aspect ratio) - Sometimes when switching around, one of the monitors will have a black background (no wallpaper) - When choosing any option at all from the quick display switcher, there seems to be a ~25% chance that it will freeze the session completely except for the mouse cursor, and you can't do anything but restart the PC or switch to a TTY SOFTWARE/OS VERSIONS Operating System: KDE Neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445080] New: [Wayland] Tooltips of panel applets sometimes have a broken background
https://bugs.kde.org/show_bug.cgi?id=445080 Bug ID: 445080 Summary: [Wayland] Tooltips of panel applets sometimes have a broken background Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: 1.0 Created attachment 143281 --> https://bugs.kde.org/attachment.cgi?id=143281=edit Screenshot of broken tooltip SUMMARY When hovering over applets or system tray icons with the mouse, sometimes the background of the tooltip is rendered incorrectly as seen in the attached screenshot STEPS TO REPRODUCE 1. Hover over plasmoids with tooltips with the mouse cursor 2. ... continue hovering over several plasmoids until you see the glitch OBSERVED RESULT See screenshot EXPECTED RESULT Normal looking tooltip SOFTWARE/OS VERSIONS KDE Neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 And also on: Fedora Linux 35 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445230] New: Kdenlive crashes when trying to add a video to the timeline that has more audio tracks than the project currently has
https://bugs.kde.org/show_bug.cgi?id=445230 Bug ID: 445230 Summary: Kdenlive crashes when trying to add a video to the timeline that has more audio tracks than the project currently has Product: kdenlive Version: 21.08.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY I tried to add a video file with 3 audio tracks to a blank kdenlive project (which came only with two audio tracks) and the KDE warning sound played constantly before kdenlive crashed after a few seconds STEPS TO REPRODUCE 1. Add a video file with more audio tracks than the project currently has 2. Drag it onto the timeline OBSERVED RESULT Warning sound with no message followed by a crash EXPECTED RESULT A popup window asking if more audio track should be added to the project to accommodate those of the video file SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-zen1-1-zen (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441533] Dolphin's terminal panel is partially transparent on Wayland even though it shouldn't be with Breeze
https://bugs.kde.org/show_bug.cgi?id=441533 Firlaev-Hans changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Firlaev-Hans --- This appears to be fixed as I cannot reproduce it on KDE Neon unstable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444175] Wayland: After rotating the screen twice and then opening the system tray, the wallpaper is cut off
https://bugs.kde.org/show_bug.cgi?id=444175 Firlaev-Hans changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Firlaev-Hans --- After the upgrade to Fedora 35 the issue no longer appears even though the Plasma version is still the same (but Frameworks have been upgraded to 5.87) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437928] After Touchscreen Edge Gesture, Grid doesn't respond to Touchscreen Input
https://bugs.kde.org/show_bug.cgi?id=437928 Firlaev-Hans changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||firlaevhans.fiete@protonmai ||l.com Ever confirmed|0 |1 --- Comment #4 from Firlaev-Hans --- Can confirm this issue on: Operating System: Fedora 34 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.15-300.fc34.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 --- Comment #11 from Firlaev-Hans --- I admit that I have very little understanding about how all this works but after digging in the source code a bit it appears that the problem may not be in Yakuake itself, but in KDE Frameworks, specifically in KWindowSystem. To detect a focus loss, Yakuake connects to the activeWindowChanged signal in KWindowSystem, which exists in platforms/xcb but not platforms/wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449962] After upgrading to 5.24.0 the Maliit Keyboard no longer appears as an on-screen keyboard when the Virtual Keyboard is activated and set to be Maliit
https://bugs.kde.org/show_bug.cgi?id=449962 Firlaev-Hans changed: What|Removed |Added Ever confirmed|0 |1 CC||firlaevhans.fiete@protonmai ||l.com Status|REPORTED|CONFIRMED --- Comment #1 from Firlaev-Hans --- Can confirm on KDE Neon. Even in tablet mode, the OSK never appears. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 451470] New: EXIF Metadata included in AVIF images is not shown in Gwenview, Dolphin etc.
https://bugs.kde.org/show_bug.cgi?id=451470 Bug ID: 451470 Summary: EXIF Metadata included in AVIF images is not shown in Gwenview, Dolphin etc. Product: frameworks-kimageformats Version: 5.91.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alex.me...@kde.org Reporter: firlaevhans.fi...@protonmail.com CC: aa...@kde.org, kdelibs-b...@kde.org Target Milestone: --- SUMMARY I converted some photos from JPEG to AVIF and made sure to include the EXIF metadata (e. g. camera model, focal length etc), but in Gwenview and Dolphin this metadata is not displayed. However, exiftool can read the data from the AVIF file. Btw after I converted the AVIF back to a JPEG, metadata was shown for the new JPEG again STEPS TO REPRODUCE 1. Find a JPEG photo with EXIF data, and look at the data displayed in Dolphins preview panel 2. Convert it to AVIF: avifenc PHOTO.jpg PHOTO.avif 3. Include the EXIF data in the AVIF: exiftool -tagsfromfile PHOTO.jpg PHOTO.avif 4. Confirm that the EXIF data is included in the AVIF by looking at the output of: exiftool PHOTO.avif 5. Look at the file in Dolphins preview panel or in Gwenview OBSERVED RESULT Metadata is displayed for the JPEG, but not for the AVIF EXPECTED RESULT Metadata for the AVIF file should be displayed SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.16.13-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451500] New: Current timestamp for some media players (e. g. Spotify) is wrong / starts at 0:00 when opening the applet
https://bugs.kde.org/show_bug.cgi?id=451500 Bug ID: 451500 Summary: Current timestamp for some media players (e. g. Spotify) is wrong / starts at 0:00 when opening the applet Product: plasmashell Version: 5.24.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Media Player Assignee: plasma-b...@kde.org Reporter: firlaevhans.fi...@protonmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY If you play a song in Spotify and let it play for a few seconds, then open the media player applet, it will display the timestamp as 0:00 and count up from there, rather than displaying the correct timestamp. If you then close the applet and open it again a few seconds later, it will continue at the timestamp at which you closed it. STEPS TO REPRODUCE 1. Play a song in Spotify (some other players might be affected too) 2. A few seconds later, open the media control applet and compare the timestamp displayed in there with the one in Spotify itself 3. Close the applet and open it again a few seconds later OBSERVED RESULT The time code displayed in the media control applet is different from the actual time code (starts at 0:00 instead of the actual time code). E. g. the current song is at 0:23 of 3:53, you open the applet, it says 0:00 of 3:53, 5 seconds later the song is at 0:27 but the applet either says 0:05 of 3:53 instead of 0:27, or it's simply frozen at 0:00. EXPECTED RESULT The media control applet should get the correct timestamp from Spotify, or, if that's not possible, just don't display a (wrong) time code at all as it's rather confusing to the user. SOFTWARE/OS VERSIONS Betriebssystem: Arch Linux KDE-Plasma-Version: 5.24.3 KDE-Frameworks-Version: 5.92.0 Qt-Version: 5.15.3 Kernel-Version: 5.16.14-zen1-1-zen (64-bit) Grafik-Plattform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451631] New: [Wayland] Plasmashell freezes briefly after switching the virtual desktop
https://bugs.kde.org/show_bug.cgi?id=451631 Bug ID: 451631 Summary: [Wayland] Plasmashell freezes briefly after switching the virtual desktop Product: plasmashell Version: 5.24.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: firlaevhans.fi...@protonmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY When you switch to a different VD, the panel (and other plasmashell components) will visually freeze for about two seconds or so. It doesn't happen all the time, but when it does happen, it happens throughout the entire session (or until the session is suspended and resumed). plasmashell --replace does NOT fix this when it happens It's not terribly rare, it happens about 50% of the time for me. I've seen this on multiple different systems on Wayland now (not confirmed on X11). STEPS TO REPRODUCE 1. Be on Wayland with multiple virtual desktops 2. ??? (If it doesn't happen on the first try, restart your session until it does 3. Switch to a different VD (doesn't matter which method) 4. Look at the panel (e. g. the VD pager or a clock showing seconds to see it freeze) OBSERVED RESULT The panel won't update for a second or two / will appear visually frozen EXPECTED RESULT The panel should just update normally SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.16.14-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451631] [Wayland] Plasmashell freezes briefly after focussing the desktop / switching to an empty virtual desktop
https://bugs.kde.org/show_bug.cgi?id=451631 Firlaev-Hans changed: What|Removed |Added Summary|[Wayland] Plasmashell |[Wayland] Plasmashell |freezes briefly after |freezes briefly after |switching the virtual |focussing the desktop / |desktop |switching to an empty ||virtual desktop -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450405] New: After moving a native Wayland window to a different virtual desktop it is still considered focused
https://bugs.kde.org/show_bug.cgi?id=450405 Bug ID: 450405 Summary: After moving a native Wayland window to a different virtual desktop it is still considered focused Product: kwin Version: 5.24.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY On wayland if you move any native window to a different workspace it still appears focused in the pager applet (though not in the 3rd party "Window title" applet), still responds to keyboard input, and can still be moved with KWin shortcuts, even though it's now on a different workspace, until you focus something else. XWayland apps are not affected. STEPS TO REPRODUCE 1. Have keyboard shortcuts set for moving windows to specific virtual desktops 2. Open a native Wayland window (not XWayland). I suggest something like Kate or Konsole will let you type something. 3. Move it to a different VD. Take a look at the desktop pager widget. 4. Type something. 5. Without clicking on anything, press the according keyboard shortcut to move the active window to the desktop you are currently on OBSERVED RESULT 3. The window will be displayed in the pager applet on the new VD, but it will still be colored as if it was the active window 5. The previously moved window will come back to the current workspace. If you did step 4. then you'll notice that the window accepted keyboard input while it wasn't even on the active workspace. EXPECTED RESULT After a window is moved to a different VD, it should not have focus anymore. Thus, it should also no longer accept keyboard input, and KWin shortcuts shouldn't affect it anymore either. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.9-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444172] [Wayland] Ghost window left behind when moving wayland windows to other VD/Activity using key bindings or pager widget
https://bugs.kde.org/show_bug.cgi?id=444172 --- Comment #17 from Firlaev-Hans --- It appears that Bug 450405 might have been the root cause for this ghost window glitch, and while the workspace repaint fixes this symptom, the bug that caused it is still present. Take a look at that bug report for details, but TL;DR KWin apparently still considers a (non-XWayland) window to be the currently focused window even after it leaves the current workspace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450405] After moving a native Wayland window to a different virtual desktop it is still considered focused
https://bugs.kde.org/show_bug.cgi?id=450405 --- Comment #2 from Firlaev-Hans --- I do not believe this is a duplicate of the bug you linked, at least not exactly. At the very least, the fix for the ghost window bug in 5.24.1 did not fix this bug. It seems likely that this bug was the root cause for the ghost windows bug; Since the native Wayland window is still "focused" after leaving the workspace it would still be drawn, or at least its area would not be repainted, until you actively focus something else. But the ghost window bug ended up getting fixed by repainting the workspace after a window leaves the VD, which only fixed the symptom and not the root cause. So while we no longer get the visual artifact, the window is still considered the focused window by KWin and receives keyboard input while on a different workspace, even in the latest Plasma version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450078] New: New overview doesn't allow moving windows between screens
https://bugs.kde.org/show_bug.cgi?id=450078 Bug ID: 450078 Summary: New overview doesn't allow moving windows between screens Product: kwin Version: 5.24.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY I have two screens. In the overview effect, when I drag a window to a different monitor, it doesn't show up there at all and as soon as I let go of the mouse button it returns to where it was. In Parachute, it was possible to move windows to other screens directly, or even to other workspaces on those other screens. Only tested on Wayland. Was going to include a screen capture but the overview doesn't show up on it, oddly enough. STEPS TO REPRODUCE 1. Have at least two monitors, and open any window 2. Activate the new overview 3. Try to drag a window to a different monitor OBSERVED RESULT When dragging the window and moving the cursor to the other monitor, the window just disappears / isn't visible on the other monitor. When letting go, the window snaps back to the monitor it was previously on. EXPECTED RESULT The overview effect should allow dragging windows to other monitors. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.8-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451631] [Wayland] Plasmashell freezes briefly after focussing the desktop / switching to an empty virtual desktop
https://bugs.kde.org/show_bug.cgi?id=451631 --- Comment #3 from Firlaev-Hans --- (In reply to Nate Graham from comment #2) > Does just the panel freeze, or does everything > freeze? Are apps also frozen? Or just the Plasma panel and other Plasma > components? During this freeze, can you open KRunner with Alt+Space? Just the Panels and other Plasma components, such as visible notifications. Application windows don't freeze, nor does KRunner. I can't test if Plasmoids on the desktop are affected too because while I get this bug right now I can't add widgets right now because of Bug 439159. > "it happens throughout the entire session". Can you clarify? By that I meant that when I do encounter this bug, I can consistently reproduce it until the session ends or is suspended. However I just realized that this isn't entirely true, I was able to consistently reproduce just a moment ago but now it's been a few minutes and even though I'm still in the same session and did nothing special it suddenly stopped happening. So it doesn't surprise me that you couldn't reproduce it on first try, since it only happens some of the time. Frustratingly I don't know how to reproduce this reliably, it just randomly seems to happen some of the time. But I have encountered this bug many times on multiple different computers, so I'd be surprised if nobody else besides me (and Bug 451840 ?) is ever able to reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448673] Cannot move panels to a different side and the dragged panel has a titlebar
https://bugs.kde.org/show_bug.cgi?id=448673 Firlaev-Hans changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448673] Cannot move panels to a different side and the dragged panel has a titlebar
https://bugs.kde.org/show_bug.cgi?id=448673 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #1 from Firlaev-Hans --- Created attachment 147782 --> https://bugs.kde.org/attachment.cgi?id=147782=edit Screen Capture of described bug Can confirm on 5.24.3 Wayland on Arch. I added a video of the bug, too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451840] Plasmashell sluggish after waking from sleep on Wayland
https://bugs.kde.org/show_bug.cgi?id=451840 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #4 from Firlaev-Hans --- (In reply to Simon Vogl from comment #3) > Created attachment 147832 [details] > Journal log during slowdowns > > I managed to capture a journal log of the slowdowns happening. > It also seems somewhat linked to plasmashellrc as getting rid of the > [Updates] section inside of plasmashellrc fixes the bug temporarily for > me > Again, it is very hard to reproduce for me, I only managed to sporadically > reproduce on NVIDIA so far, still no luck on Intel Iris Xe. That journal log is interesting, because >plasmashell[17830]: QWaylandDataOffer: timeout reading from pipe >plasmashell[17830]: QWaylandDataOffer: error reading data for mimeType >application/x-kde-cutselection is exactly the same as what I saw in my likely related issue (Bug 451631) that Matt linked. It sure seems suspicious and sounds like it's related to the clipboard somehow (???) If you search for QWaylandDataOffer on Bugzilla you find several other bugs that are in some way related to plasmashell hanging or crashing as well. No idea what this error means specifically but it's worth investigating IMO. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442379] When using Natural Scrolling, scrolling direction to change volume is inverted
https://bugs.kde.org/show_bug.cgi?id=442379 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #5 from Firlaev-Hans --- (In reply to David Edmundson from comment #4) > Qt does have a property on the wheel event to signify if it's inverted or not I just had a look at that, I figured this would be an easy fix with something like > if (wheel.inverted) wheelDelta = -wheelDelta but as it turns out the "inverted" property of the WheelEvent always returns false even if the scrolling direction is actually inverted, both on X11 and Wayland, and both with a touchpad and with a mouse. The Qt docs themselves even say > Note: Many platforms provide no such information. On such platforms inverted > always returns false. https://doc.qt.io/qt-5/qml-qtquick-wheelevent.html#inverted-prop So I guess it's not as easy to fix as it seemed. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 448461] New: Can't scroll in playlist using touch screen as it drags around the tracks instead
https://bugs.kde.org/show_bug.cgi?id=448461 Bug ID: 448461 Summary: Can't scroll in playlist using touch screen as it drags around the tracks instead Product: Elisa Version: 21.12.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY On my 2in1 laptop when I try to scroll the playlist in Elisa I end up changing the order of the tracks instead. STEPS TO REPRODUCE 1. Have a touch screen 2. Have enough tracks in Elisa's playlist so that it can be scrolled 3. Try to scroll the playlist using the touch screen (in the normal playlist view, not in party mode) OBSERVED RESULT Unless you start scrolling from the album banner, you end up dragging the tracks around and changing their order in the playlist instead of scrolling. EXPECTED RESULT Dragging on a touch screen in the playlist area should make it scroll. Dragging the tracks around should require touching and holding them for a short moment. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.13-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland (not tested on X11) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469989] Screen recording doesn't work
https://bugs.kde.org/show_bug.cgi?id=469989 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #5 from Firlaev-Hans --- Cannot confirm anymore on current Neon Unstable on Wayland with Spectacle built against Qt 6.6. Fixed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442159] Adaptive transparency / floating reacts to windows on wrong screen after screen configuration changes
https://bugs.kde.org/show_bug.cgi?id=442159 Firlaev-Hans changed: What|Removed |Added Summary|Adaptive transparency works |Adaptive transparency / |with windows on wrong |floating reacts to windows |screen |on wrong screen after ||screen configuration ||changes --- Comment #3 from Firlaev-Hans --- Floating panels are affected in the same way as transparency: When plasmashell was started with only my internal display active and then I plug in the external monitor (which then becomes my primary monitor, thus my panel moves there), the panel defloats and becomes opaque when a window on my laptop display "touches" it even though it's located on the external display, and it stays floating and transparent when only a window on that display touches it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442159] Adaptive transparency works with windows on wrong screen
https://bugs.kde.org/show_bug.cgi?id=442159 Firlaev-Hans changed: What|Removed |Added Version|5.22.5 |5.27.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474223] Pinned apps in a Wayland session are not remembered
https://bugs.kde.org/show_bug.cgi?id=474223 Firlaev-Hans changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||firlaevhans.fiete@protonmai ||l.com --- Comment #1 from Firlaev-Hans --- Looks like while changes like adding and removing widgets are immediately written to .config/plasma-org.kde.plasma.desktop-appletsrc, changes to the pinned launchers in the task manager are now only written when plasmashell exits, and does so "gracefully"? When I run plasmashell --replace, the changes are saved and kept, but if I not-so-gently kill either plasmashell or KWin, the changes are not saved. When shutting down / logging out, plasmashell behaves as if KWin died, according to the journal (this is the case on 5.27 too): plasmashell[3262]: The Wayland connection broke. Did the Wayland compositor die? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474223] Changes to pinned apps are only saved at quit, so changes can be lost if there's a power outage or plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=474223 --- Comment #3 from Firlaev-Hans --- > However let's broaden the topic of this bug report a bit to request that > configs get saved > before quit so we can harden Plasmashell a bit against crashes, power loss, > etc. That's how it already worked in Plasma 5 (on 5.27.7 at least); any changes would be written to disk immediately. It was apparently changed in Plasma 6, either intentionally or not, but curiously *only for pinned task manager items and nothing else* as far as I can tell, which seems quite odd. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463533] Dolphin, file not getting sorted correctly
https://bugs.kde.org/show_bug.cgi?id=463533 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 473599] XWaylandVideoBridge only shares white screen
https://bugs.kde.org/show_bug.cgi?id=473599 Firlaev-Hans changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Firlaev-Hans --- (In reply to David Edmundson from comment #2) > Something changed, and I believe this was fixed in master, but I can't know > for sure. > > Do you know what version xwaylandvideoridge has the Fedora repositories? Ah, seems to be a rather old version from May: xwaylandvideobridge-0:0~git20230504.3445aff-2.fc38.x86_64 A more recent Flatpak build from gitlab CI works fine. I guess Fedora just needs to update their package. -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 473599] XWaylandVideoBridge only shares white screen
https://bugs.kde.org/show_bug.cgi?id=473599 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Firlaev-Hans --- I'm having the same issue. I'm using xwaylandvideoridge from the Fedora Repositories, and before that I used a nightly Flatpak build. Neither of them work. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475161] The night color at current location doesn't work properly as manual location
https://bugs.kde.org/show_bug.cgi?id=475161 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com Keywords||regression --- Comment #1 from Firlaev-Hans --- Interestingly it's the exact opposite for me. Current location, which worked previously (before Frameworks 5.100), now keeps my screen in day mode. Manual location with the same coordinates works just fine. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 469137] MKV is a dinosaur format from the 1990's.
https://bugs.kde.org/show_bug.cgi?id=469137
Firlaev-Hans changed:
What|Removed |Added
CC||firlaevhans.fiete@protonmai
||l.com
--- Comment #1 from Firlaev-Hans ---
Are you confusing mkv with something else? It is NOT some abandoned "dinosaur"
format from the 90s, it came out in 2002 more than a year AFTER mp4 and it had
its latest release last october, whereas mp4 hasn't had a new release in 3
years.
Mkv ("Matroska") is actually a very popular, very flexible container format
that supports almost any codec imaginable (including H264 and H265 video and
mp3 or AAC audio). It is a completely free and open standard (unlike mp4) and
doesn't have anything to do with Microsoft or proprietary formats.
It also holds a significant advantage over mp4 for recording scenarios like
this, which is that it can recover better from sudden interruptions during
recording (like crashes or power outages) as unlike mp4 it doesn't result in
broken files. It is the preferred container format in OBS Studio for a reason.
I also don't understand your complaint about editing and modifying mkv files.
FFMPEG and handbrake can work with them just fine, and so can most video
editors. I don't know which software you usually use to manipulate your MP4
files of course.
Now, the actual codecs used by kamoso are a different story. It records theora
video and vorbis audio, the latter is okay but theora *is* a dinosaur codec and
not very good. But again, that has nothing to do with mkv. Kamoso could easily
switch to H264 / H265 video and mp3 (or rather AAC which is much more popular
for videos) audio, while keeping the Matroska container format.
Although I'm not sure how that would work with the licensing of these codecs,
so it might be better to switch to VP8/VP9 video and Opus audio instead which
are good modern free formats and also widely supported (YouTube uses them).
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 416690] Why move to deleted folder? on mount directory.
https://bugs.kde.org/show_bug.cgi?id=416690 Firlaev-Hans changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #8 from Firlaev-Hans --- (In reply to Alexander Kowalski from comment #7) > Created attachment 148270 [details] > Screen recording > > I just noticed the recent activity here (compared to my comment on bug > 391380 at least) and while I am still not absolutely sure that this is a > duplicate of that one, the description in the new comments sounds very much > like that to me, I can still reproduce this issue reliably using the latest > version and I also found out what the cause was back then, just no easy and > reliable fix (see comment there). I made a recording of encountering the > issue, the only time-critical step is changing between the views fast enough > that the terminal does not keep up (this does not require split views, > happens with other navigation too). Interesting, so this issue does definitely look like a sub-issue of the one you reported (which I've definitely encountered before as well). So at least we finally know how to reproduce this reliably, the steps are: 1. Open Dolphin and open the F4 terminal panel 2. Create a folder and enter it 3. Quickly press Alt+left arrow and Alt+right arrow repeatedly to go back and forth until the terminal can't keep up any more and thinks you're still inside the new folder when you aren't 4. Delete the folder while the terminal panel is still inside it -> Dolphin enters the folder after deleting it and then complains that the folder doesn't exist (I reopened this issue for now but maybe it should be marked as a duplicate of your bug instead, I don't know) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451631] [Wayland] Plasmashell freezes briefly after focussing the desktop / switching to an empty virtual desktop
https://bugs.kde.org/show_bug.cgi?id=451631 --- Comment #1 from Firlaev-Hans --- One important detail I forgot to mention in my original report is that this only happens when switching from a desktop with a focused window to an empty desktop, not when switching between empty desktops or between desktops that both have windows on them. In fact, it doesn't seem to be related to switching desktops directly at all. The same thing happens when you have a window focused and then click on the desktop to un-focus the window. I updated the title accordingly. So in general, it happens when switching from having a window focused to having no window focused. But still, it's inconsistent / doesn't happen in every session, so that's always fun to debug. Here's some possibly (but maybe not at all) related info from journalctl: QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454049] Folder icon for folder with image thumbnail is not updated when accent color changes until Dolphin is restarted
https://bugs.kde.org/show_bug.cgi?id=454049 --- Comment #1 from Firlaev-Hans --- Created attachment 149002 --> https://bugs.kde.org/attachment.cgi?id=149002=edit Initial appearance before changing accent color, everything looks normal -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454045] New blend effect causes all windows to briefly appear while in "Show Desktop" mode when accent color changes
https://bugs.kde.org/show_bug.cgi?id=454045 Firlaev-Hans changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 454047] New: With tinted color scheme, title bar color doesn't update when accent color changes automatically
https://bugs.kde.org/show_bug.cgi?id=454047 Bug ID: 454047 Summary: With tinted color scheme, title bar color doesn't update when accent color changes automatically Product: Breeze Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: firlaevhans.fi...@protonmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY If you set your color scheme to be accent color tinted and your accent color to "From active Wallpaper", the window decoration won't update it's tinted color when the wallpaper and thus accent color changes. It will only change correctly after manually applying any setting in the System Settings Colors page. STEPS TO REPRODUCE 1. Check "Tint all colors with accent color" in your color scheme's settings 2. Specifically DON'T check the option to apply color effects to window title bars 3. Set your accent color to "From current wallpaper" 4. Make sure to apply all these settings 5. Change the wallpaper, so that the accent color changes 6. Change the wallpaper once more, accent color changes again 7. Change anything at all in the Color settings and apply OBSERVED RESULT 5. The window contents update their tint color but the title bars don't 6. The window contents update normally again, but the title bars now take on the color that they should have taken after step 5 7. The tint for both the title bars and the window contents is updated uniformly and correctly again EXPECTED RESULT The title bar colors should always be updated correctly if the accent color changes, even if it was not changed by the user from system settings but rather by changing the wallpaper SOFTWARE/OS VERSIONS KDE Neon Unstable KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454049] New: Folder icon for folder with image thumbnail is not updated when accent color changes until Dolphin is restarted
https://bugs.kde.org/show_bug.cgi?id=454049 Bug ID: 454049 Summary: Folder icon for folder with image thumbnail is not updated when accent color changes until Dolphin is restarted Product: dolphin Version: 22.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 149001 --> https://bugs.kde.org/attachment.cgi?id=149001=edit Appearance after the accent color is changed but before Dolphin is restarted. Folder on the left still has old accent color SUMMARY When using an icon theme whose folder icons respect the accent color (such as default Breeze nowadays), the color of folder icons in an open dolphin window is immediately updated when the accent color changes, but not if said folder icon has a thumbnail preview for the files inside it on it. See screenshot. STEPS TO REPRODUCE 1. Use Breeze icons. 2. Have one folder that contains an image and thus generates a thumbnail, and one that does not. 3. Change the accent color and be disappointed 4. Restart Dolphin OBSERVED RESULT The color of "normal" folder icons (like the one on the right in my screenshot) updates as expected. The color of folder icons featuring thumbnails for the pictures inside the folder (like the one on the left in my screenshot) is not updated until Dolphin is restarted. EXPECTED RESULT When the accent color changes, the folders with thumbnails need to be updated too. That likely means regenerating the thumbnail for that folder on the fly. SOFTWARE/OS VERSIONS KDE Neon Unstable KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454045] New: New blend effect causes all windows to briefly appear while in "Show Desktop" mode when accent color changes
https://bugs.kde.org/show_bug.cgi?id=454045 Bug ID: 454045 Summary: New blend effect causes all windows to briefly appear while in "Show Desktop" mode when accent color changes Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY Basically, what the title says. STEPS TO REPRODUCE 1. Set the accent color to "From current wallpaper" 2. Enter "Show Desktop" mode (Meta+D) to hide all windows 3. Change the wallpaper so that the accent color changes OBSERVED RESULT While still in "Show Desktop" mode, all open but currently hidden windows briefly pop up with their old colors and then fade away. EXPECTED RESULT Windows that are not currently shown should be ignored by the blend effect. However, the desktop settings window may be visible even during show desktop mode, so not all windows can be ignored. SOFTWARE/OS VERSIONS KDE Neon Unstable KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445992] Can't switch from "only internal display" directly to "only external display" or vice versa on Wayland
https://bugs.kde.org/show_bug.cgi?id=445992 Firlaev-Hans changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Firlaev-Hans --- Can no longer reproduce on Neon unstable / 5.24.80 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445993] After switching between the options in Quick Display Configuration applet several times in a row, the session completely freezes (Wayland)
https://bugs.kde.org/show_bug.cgi?id=445993 Firlaev-Hans changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Firlaev-Hans --- Seems to be fixed (?) -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 454273] New: Selecting a different song in the playlist with the touch screen requires tapping it three (!) times
https://bugs.kde.org/show_bug.cgi?id=454273 Bug ID: 454273 Summary: Selecting a different song in the playlist with the touch screen requires tapping it three (!) times Product: Elisa Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY Not a serious problem, but irritating for sure. To start playing a specific song in the current playlist using the touch screen you need to 1. Tap on the song once to select it and show the buttons that normally appear on mouse hover 2. Tap on the play button that just appeared, **but doing so will only select the button and not press it** (this is the irritating part) 3. Tap it again to actually start playing the song The same goes for the other buttons in there, like "show in folder" and "Remove", as well of course. EXPECTED RESULT First of all, in step 2 above, tapping any of the buttons should just activate it, you know, like buttons usually do when you touch them, instead of only being selected and requiring another tap. That way you would only need to tap a song twice to play or remove it. But the following gestures could make this even faster and easier (should I create separate tickets for these?): - Quickly double tapping a song should immediately start it even if you didn't actually touch its play button. After all, so does double clicking with the mouse - Swiping a song to the side should remove it from the playlist SOFTWARE/OS VERSIONS Elisa 22.07.70 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 454032] When using a language other than English, inline buttons of initial view don't work until you switch views once
https://bugs.kde.org/show_bug.cgi?id=454032 Firlaev-Hans changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||firlaevhans.fiete@protonmai ||l.com --- Comment #13 from Firlaev-Hans --- Can confirm on multiple german systems with both 22.04 and master. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440456] Dolphin become slow/unresponsive after playing a video or audio from the information panel
https://bugs.kde.org/show_bug.cgi?id=440456 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com Keywords||wayland --- Comment #3 from Firlaev-Hans --- Can confirm on Arch and Dolphin 22.04 when using Wayland at least (haven't used X11 in a while but I'm pretty sure it was fine there). >(even for video file only the audio will play) In some cases the video will actually at least show some frames (but won't play properly). And in general, besides becoming "unresponsive and slow", the whole UI suddenly gets graphical glitches all over the place, with parts of the screen not updating properly. Only after restarting Dolphin it goes back to normal. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 442251] Elisa setting for Initial View on Startup
https://bugs.kde.org/show_bug.cgi?id=442251 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #17 from Firlaev-Hans --- I cannot reproduce this with the latest Elisa version (either 22.04 or master) on a german system. What I am seeing instead is that while the correct page is displayed on startup, nothing can be played / added to the playlist from that page. For example, if I set the start page to album view, then I cannot hit play on any album (nothing happens, no terminal output). Elisa also gets somewhat sluggish at that point. Even switching to a different view and back doesn't fix this, however, if I click a play button in a different view (e. g. artists), THEN go back to album view, the album play buttons work again. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 454343] Tapping a song in the playlist view with the touchscreen should play it
https://bugs.kde.org/show_bug.cgi?id=454343 --- Comment #2 from Firlaev-Hans --- (In reply to Nate Graham from comment #1) > Double tap is generally not a great UX on touch. I think single-tap enough > should do it. That's *probably* what the user wanted. But then how do you use the other buttons (remove, show details, ...) on touch screens? Currently they are only shown when tapping on a song once. One might want to use these buttons without playing that song. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451631] [Wayland] Plasmashell freezes briefly after focusing the desktop if it was started with a non-empty clipboard history
https://bugs.kde.org/show_bug.cgi?id=451631 Firlaev-Hans changed: What|Removed |Added Summary|[Wayland] Plasmashell |[Wayland] Plasmashell |freezes briefly after |freezes briefly after |focusing the desktop if it |focusing the desktop if it |was started with a full |was started with a |clipboard history |non-empty clipboard history --- Comment #6 from Firlaev-Hans --- Minor correction, the clipboard doesn't need to be full, it just needs to be *not* empty when plasmashell (re)starts for this bug to trigger -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451840] Plasmashell sluggish after waking from sleep on Wayland
https://bugs.kde.org/show_bug.cgi?id=451840 --- Comment #6 from Firlaev-Hans --- If you still get this issue, can you test if it happens specifically when Plasma was started with a full clipboard history and stops happening when the clipboard is cleared? Because that turned out to be the cause of my issue (read the latest comments on Bug 451631), and it would be interesting to see if these are indeed two symptoms of the same root cause. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451631] [Wayland] Plasmashell freezes briefly after focusing the desktop if it was started with a non-empty clipboard history
https://bugs.kde.org/show_bug.cgi?id=451631 Firlaev-Hans changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #8 from Firlaev-Hans --- (In reply to Yannick from comment #7) > Same issue here, on Archlinux and Plasma 5.25.2 on wayland (no issue on X11). > I've got the same messages in the journal log when the freeze happens. > > However on my end it only seems to happen when there's a document in the > clipboard, it doesn't happen with text selection in the clipboard. Yes, you're right. It only happens when your clipboard contains files rather than just text. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 455089] New: Certain characters (like ü,ö,ä,ß but also ' ) in CD Metadata replaced with ## in ripped .flac files
https://bugs.kde.org/show_bug.cgi?id=455089 Bug ID: 455089 Summary: Certain characters (like ü,ö,ä,ß but also ' ) in CD Metadata replaced with ## in ripped .flac files Product: k3b Version: 22.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Copying Assignee: k...@kde.org Reporter: firlaevhans.fi...@protonmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY I ripped a bunch of audio CDs to flac and noticed that while the filenames of the resulting files where normal, their Metadata had all sorts of characters replaced, e. g. "Don't Stop Me Now" became "Don##t stop me now". I was able to correct these mistakes by editing the metadata in other software, so clearly this is not a limitation of Flac's Metadata format. STEPS TO REPRODUCE 1. Find an audio CD that has characters such as ' or üöäß in its album title, artist name or track names 2. Rip it with K3b 3. Take a look at the metadata of the resulting files using e. g. VLC OBSERVED RESULT The characters are replaced with ## in the metadata but the filename is usually fine. EXPECTED RESULT The metadata should look normal SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.18.2-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 455497] New: After touchscreen-scrolling to the bottom of the playlist panel and overshooting, the playlist jitters indefinitely
https://bugs.kde.org/show_bug.cgi?id=455497 Bug ID: 455497 Summary: After touchscreen-scrolling to the bottom of the playlist panel and overshooting, the playlist jitters indefinitely Product: Elisa Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- Created attachment 149863 --> https://bugs.kde.org/attachment.cgi?id=149863=edit Screen recording SUMMARY Bug currently in Elisa master branch, see attached video STEPS TO REPRODUCE 1. Use Elisa on a touch screen, add enough songs to playlist that it becomes scollable 2. Scroll to the very bottom of the playlist, overshooting a bit to trigger the rubber band effect 3. Profit OBSERVED RESULT The playlist view doesn't stop jittering by itself, only after scrolling again manually EXPECTED RESULT After the rubber band animation the playlist should remain still SOFTWARE/OS VERSIONS Elisa git build from master (1c55dcef) Operating System: Fedora Linux 36 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.13-300.fc36.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 455089] Certain characters (like ü,ö,ä,ß but also ' ) in CD Metadata replaced with ## in ripped .flac files
https://bugs.kde.org/show_bug.cgi?id=455089 --- Comment #2 from Firlaev-Hans --- (In reply to Albert Astals Cid from comment #1) > Can't seem to reproduce :/ Weird. I wonder what's going wrong on my system then, because it happens literally every time there is a special character in the metadata. I do seem to recall that this hasn't always been the case on my system either though, as I'm sure I have ripped CDs with '-characters before without problems. Maybe it has something to do with the tools / libraries used in the background? Or maybe it is in some way related to the locale? My system is set to german. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451631] [Wayland] Plasmashell freezes briefly after focusing the desktop if it was started with a full clipboard history
https://bugs.kde.org/show_bug.cgi?id=451631 Firlaev-Hans changed: What|Removed |Added Summary|[Wayland] Plasmashell |[Wayland] Plasmashell |freezes briefly after |freezes briefly after |focussing the desktop / |focusing the desktop if it |switching to an empty |was started with a full |virtual desktop |clipboard history --- Comment #5 from Firlaev-Hans --- I have now found a reliable way to reproduce this issue: 1. Completely fill up your Klipper history with anything 2. Either restart plasmashell yourself or reboot / log out and back in 3. Focus a window, then focus the desktop 4. Clear the clipboard history, then repeat step 3 After step 3 you will notice this brief freeze. After step 4, you won't. This is still reproducible on Plasma 5.25.0 / Frameworks 5.95.0 on Arch. This journal log is definitely related as it is printed every time the freeze happens: >plasmashell[5515]: QWaylandDataOffer: timeout reading from pipe >plasmashell[5515]: QWaylandDataOffer: error reading data for mimeType >application/x-kde-cutselection -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 454343] New: Double tapping a song in the playlist view with the touchscreen should play it
https://bugs.kde.org/show_bug.cgi?id=454343 Bug ID: 454343 Summary: Double tapping a song in the playlist view with the touchscreen should play it Product: Elisa Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY If you double click on a song in the Playlist view with the mouse it starts playing, but not if you use a touch screen. It would be a nice enhancement for touch users if double tapping a song made it play, particularly because the inline play button for a song is not shown until it is selected. SOFTWARE/OS VERSIONS Elisa 22.07.70 (built today) Operating System: Fedora Linux 36 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.8-300.fc36.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 454273] Selecting a different song in the playlist with the touch screen requires tapping it three (!) times
https://bugs.kde.org/show_bug.cgi?id=454273 --- Comment #2 from Firlaev-Hans --- (In reply to Nate Graham from comment #1) > The first tap on the play button works for me. Are you using X11 or Wayland? > > We could probably play on single tap, but I'd like a second bug report for > that. Likewise for "swipe to remove". > > *** This bug has been marked as a duplicate of bug 438644 *** I *had* this issue on Wayland, didn't try on X11. But my Elisa build was a couple of days old. Now I can indeed no longer reproduce this either. Anyways, I still went ahead and opened a ticket for "double tap to play": Bug 454343 (Didn't create one for "swipe to remove" as I figured that might lead to accidental removals of songs and now that this issue is solved, removing a song is easy enough on touch) P. S. Did you mean to mark this as a duplicate of 438644? To me it doesn't look like it's related at all. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458063] New: KDE Connect clipboard sharing syncs passwords copied from password managers
https://bugs.kde.org/show_bug.cgi?id=458063 Bug ID: 458063 Summary: KDE Connect clipboard sharing syncs passwords copied from password managers Product: kdeconnect Version: 22.04.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: firlaevhans.fi...@protonmail.com Target Milestone: --- SUMMARY Also see https://www.reddit.com/r/kde/comments/ws99fn/can_i_make_kde_connect_ignore_copied_passwords/ Basically, I want to keep using the clipboard sync feature of KDE Connect, but unfortunately it means that passwords copied from my password manager will also be synced to the connected devices and, unlike on the machine they were copied from, won't be automatically deleted from their clipboards after 10 seconds. This is a pretty big security issue for anyone using both a PM and a synced clipboard. If there's a way KDE Connect could know where a clipboard item came from, it would be great if one could blacklist specific sources (like my Password manager KeepassXC) from being synced to other devices. STEPS TO REPRODUCE 1. Have a connected device via KDE Connect, with clipboard sharing enabled 2. Let your password manager copy something to the clipboard 3. Check the clipboard on the connected device OBSERVED RESULT The copied content (password) is synced to all other devices. On the "host" machine, password managers like KeepassXC will usually automatically delete the copied password from the clipboard after a few seconds. Also, even within those few seconds, the password doesn't show up in the Klipper history. But on all devices that KDE Connect syncs the clipboard to, the password is permanently added to the clipboard. EXPECTED RESULT If possible, KDE Connect should be able to have a blacklist of applications whose clipboard items will not be synced. Otherwise, it might be possible to get away with only syncing the actual Klipper history and not copied items that aren't added to the history (because KeepassXC passwords aren't, but manually copied stuff would be) SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.17-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458063] KDE Connect clipboard sharing syncs passwords copied from password managers
https://bugs.kde.org/show_bug.cgi?id=458063 --- Comment #4 from Firlaev-Hans --- (In reply to Nicolas Fella from comment #3) > I did implement that a while ago, but ironically people complained that they > *do* want to sync their passwords :) > > https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/39 Could it be made into an option then? Looking at the MR it seems like that was were the discussion was leading but nothing happened after that. I can definitely see valid points for both sides of the argument, but personally I don't like it when my passwords are visible in plain text in some other device's clipboard history (the thing is that I often have not only my phone, but also my other Linux PC connected via KDE Connect) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458063] KDE Connect clipboard sharing syncs passwords copied from password managers
https://bugs.kde.org/show_bug.cgi?id=458063 --- Comment #2 from Firlaev-Hans --- (In reply to David Edmundson from comment #1) > klipper does have a mechanism supported by some password managers were we > filter out any selection which contains a mimetype key > application/x-kde-passwordManagerHint Is that something that KDE Connect already filters out, that just isn't supported on the KeePassXC side? Or does KDE Connect still need to implement the filtering? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 458848] New: Lock screen timer ignores pen input / screen is locked after writing with stylus and giving no other input for 5 minutes.
https://bugs.kde.org/show_bug.cgi?id=458848 Bug ID: 458848 Summary: Lock screen timer ignores pen input / screen is locked after writing with stylus and giving no other input for 5 minutes. Product: kscreenlocker Version: 5.25.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: firlaevhans.fi...@protonmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY I was writing something in Xournal++ with my stylus on my 2in1 laptop. While using the stylus, touchscreen input is rightfully ignored (so my hand resting on the screen does not count as touch input). When I didn't pan around or anything using the touchscreen for a little while, thus giving no other input besides the stylus, the screen locker suddenly came on. The five-second-rule for unlocking without a password also only worked when I touched the screen and not when tapping it with the stylus. This has happened twice today and it's getting a bit annoying. STEPS TO REPRODUCE 1. Be on a 2in1 with a stylus (a wacom tablet may work too) 2. (Optional, but recommended for testing): Set the lock screen timeout to the lowest possible value (1 minute) 3. Just use the stylus for a minute without giving any other input (i. e. don't touch the screen (with fingers), keyboard or mouse) (4. When the lock screen appears, tap it with the stylus, then with your fingers, within five seconds) OBSERVED RESULT The lock screen appears despite actively using the computer with a stylus. Once it appears, using the stylus also won't unlock it within the short no-password-period. EXPECTED RESULT Stylus input should be considered input by kscreenlocker, just like keyboard, mouse and touchscreen. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.6-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland System Version: Lenovo IdeaPad C340-14API -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460248] plasmashell with high CPU usage in Wayland session
https://bugs.kde.org/show_bug.cgi?id=460248 Firlaev-Hans changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #6 from Firlaev-Hans --- Could you test if the issue is gone after fully updating your Arch system now (specifically, kimageformats-5.99.0-2)? If so, it was probably the same as Bug 460085 and is now fixed. If the issue persists then Bug 460085 probably isn't related. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454379] plasmashell starts lagging after any file is copied from dolphin and dolphin is closed
https://bugs.kde.org/show_bug.cgi?id=454379 --- Comment #17 from Firlaev-Hans --- (In reply to Nate Graham from comment #15) > I could reproduce this issue last month, but I can't anymore with the > current state of git master. Can anyone else? It might have been fixed > recently. Still reproducible latest Neon Unstable, so if it was in fact fixed it must have been VERY recently (i. e. ~ this week) if the fix hasn't even made it to Neon unstable yet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460085] Plasmashell constantly uses ~20% of my CPU (and GPU?) and significantly tanks game performance
https://bugs.kde.org/show_bug.cgi?id=460085 --- Comment #3 from Firlaev-Hans --- Perhaps this is useful (this is the output without specifying the PID): >37.99% QSGRenderThread libc.so.6 >24.36% plasmashell libQt5Core.so.5.15.6 > 8.28% plasmashell libglib-2.0.so.0.7400.0 > 5.96% plasmashell libQt5Gui.so.5.15.6 > 5.58% plasmashell libc.so.6 > 5.50% plasmashell libQt5Quick.so.5.15.6 > 3.88% plasmashell [vdso] > 1.13% perf perf > 0.66% plasmashell ld-linux-x86-64.so.2 > 0.53% plasmashell libQt5Widgets.so.5.15.6 > 0.49% swapper [unknown] > 0.49% kwin_wayland radeonsi_dri.so > 0.45% plasmashell kimg_avif.so > 0.41% Isolated Web Co libxul.so > 0.29% plasmashell libstdc++.so.6.0.30 > 0.27% perf libc.so.6 > 0.24% plasmashell libwayland-client.so.0.21.0 > 0.22% plasmashell breeze.so > 0.22% plasmashell libQt5WaylandClient.so.5.15.6 > 0.18% plasmashell libKF5XmlGui.so.5.98.0 > 0.17% kwin_wayland libkwin.so.5.25.90 > 0.15% QSGRenderThread radeonsi_dri.so > 0.15% kwin_wayland libc.so.6 > 0.14% kwin_wayland [unknown] > 0.11% kwin_wayland libQt5Gui.so.5.15.6 > 0.10% plasmashell libQt5Qml.so.5.15.6 > 0.09% kwin_wayland libQt5Core.so.5.15.6 > 0.08% plasmashell libKirigamiPlugin.so > 0.07% plasmashell libpulse-mainloop-glib.so.0.0.6 > 0.06% plasmashell libKF5PlasmaQuick.so.5.98.0 > 0.06% QSGRenderThread libQt5Quick.so.5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460085] Plasmashell constantly uses ~20% of my CPU (and GPU?) and significantly tanks game performance
https://bugs.kde.org/show_bug.cgi?id=460085 --- Comment #2 from Firlaev-Hans --- (In reply to Fushan Wen from comment #1) > Could you run > > perf top -p $(pidof plasmashell) -K > > to see what's hogging the CPU? Unfortunately that command does not appear to work for me: >Error: >Failed to mmap with 22 (Invalid argument) -- You are receiving this mail because: You are watching all bug changes.
