[kwin] [Bug 472959] kwin_wayland crashed in "KWin::Workspace::setActiveWindow(KWin::Window*)"? after closing an app
https://bugs.kde.org/show_bug.cgi?id=472959 --- Comment #5 from Andrej Halveland --- I don't believe I have gotten this kind of crash again since I reported it here. I guess this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481058] Recording windows or screens with OBS or spectacle is broken in Plasma 6 RC2 on Wayland: Failed to start pipewire screencast
https://bugs.kde.org/show_bug.cgi?id=481058 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479743] Apply/discard dialog from widget settings has unnecessary scroll bar
https://bugs.kde.org/show_bug.cgi?id=479743 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 479304] No way to scroll in the "Screen Sharing" portal window
https://bugs.kde.org/show_bug.cgi?id=479304 --- Comment #6 from Andrej Halveland --- haha, I accidentally mixed up Plasma and Qt versions together... sorry! Yes, I meant Plasma 6.0 RC1, not Plasma 6.7 RC1. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 479304] No way to scroll in the "Screen Sharing" portal window
https://bugs.kde.org/show_bug.cgi?id=479304 --- Comment #4 from Andrej Halveland --- Plasma 6.7 RC1 built against Qt6.7 beta1 made no difference. Plasma 6.7 RC1 built against Qt6.6 also made no difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478083] The transparency of the panel changes abruptly when playing the "overview" or "desktop grid" effect
https://bugs.kde.org/show_bug.cgi?id=478083 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 479568] Screen Sharing dialog is not scrollable
https://bugs.kde.org/show_bug.cgi?id=479568 Andrej Halveland changed: What|Removed |Added Status|REPORTED|RESOLVED CC||andrej.h...@gmail.com Resolution|--- |DUPLICATE --- Comment #2 from Andrej Halveland --- *** This bug has been marked as a duplicate of bug 479304 *** -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 479304] No way to scroll in the "Screen Sharing" portal window
https://bugs.kde.org/show_bug.cgi?id=479304 Andrej Halveland changed: What|Removed |Added CC||o...@geek.co.il --- Comment #1 from Andrej Halveland --- *** Bug 479568 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 479306] Screen Sharing portal freezes the screen for several seconds with large amount of windows open. Presumably due to this, if there's another screenshare running, th
https://bugs.kde.org/show_bug.cgi?id=479306 Andrej Halveland changed: What|Removed |Added Summary|Screen Sharing portal |Screen Sharing portal |freezes the screen for |freezes the screen for |several seconds with large |several seconds with large |amount of windows open. |amount of windows open. |Presumably due to this, if |Presumably due to this, if |another app is already |there's another screenshare |screensharing, that app's |running, that screenshare |screenshare will freeze.|will freeze. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 479306] New: Screen Sharing portal freezes the screen for several seconds with large amount of windows open. Presumably due to this, if another app is already screenshari
https://bugs.kde.org/show_bug.cgi?id=479306 Bug ID: 479306 Summary: Screen Sharing portal freezes the screen for several seconds with large amount of windows open. Presumably due to this, if another app is already screensharing, that app's screenshare will freeze. Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.91.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andrej.h...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- 1. Issue: When I have many apps/windows open, and then I try to screen share a window in Discord/OBS, the entire screen will freeze for several seconds (in extreme cases even for 10 seconds). 2. Issue And I believe that because of this freeze, it causes my other screenshares (be it a whole screen or just a window) to freeze indefinitely (until I manually re-share the same screen/window again). Here's a video demonstration: https://www.youtube.com/watch?v=_azZ6AMHhGc I used OBS in the steps to reproduce but it's the exact same with Discord in chromium. So it's not OBS specific. STEPS TO REPRODUCE (1st issue) 1. Have many apps/windows open 2. Try to screenshare a window in OBS OBSERVED RESULT The screen will freeze for several seconds. EXPECTED RESULT The screen should not freeze. STEPS TO REPRODUCE (2nd issue) 1. Have many apps/windows open 2. In OBS create the first screenshare and select any screen/window 3. In OBS create a second screenshare of a *window* OBSERVED RESULT The screen will freeze for several seconds AND the first screenshare will freeze indefinitely. EXPECTED RESULT The screen and other screenshares should not freeze. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0 beta1 Kernel Version: 6.7.0-rc6 Graphics Platform: Wayland Graphics Drivers: mesa 23.3.2 Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 479304] New: No way to scroll in the "Screen Sharing" portal window
https://bugs.kde.org/show_bug.cgi?id=479304 Bug ID: 479304 Summary: No way to scroll in the "Screen Sharing" portal window Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.91.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andrej.h...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- Created attachment 164628 --> https://bugs.kde.org/attachment.cgi?id=164628=edit Video demonstration. STEPS TO REPRODUCE 1. Open many apps 2. Try to screen share a window in discord for example OBSERVED RESULT In the "Screen Sharing" portal the right side items are cut-off and also there is no way to scroll down to other windows, the solution is to resize the "Screen Sharing" portal window EXPECTED RESULT Items should not be cut-off / clipped and we should be able to scroll down the list of windows. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0 beta1 Kernel Version: 6.7.0-rc6 Graphics Platform: Wayland Graphics Drivers: mesa 23.3.2 Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 476647] xdg-portal-desktop-kde start after xdg-portal-desktop, if it even starts
https://bugs.kde.org/show_bug.cgi?id=476647 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479126] Wayland: High CPU on mouse move
https://bugs.kde.org/show_bug.cgi?id=479126 --- Comment #2 from Andrej Halveland --- Here is a more extensive software/hardware info: Plasma 6 Beta 2 (installed through Arch Linux's kde-unstable repo) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7 (beta1) Kernel Version: 6.7.0-rc6 Graphics Platform: Wayland Graphics Drivers: mesa 23.3.1-2 Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479126] Wayland: High CPU on mouse move
https://bugs.kde.org/show_bug.cgi?id=479126 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #1 from Andrej Halveland --- Just for comparison. While looking at htop, without moving my mouse the kwin_wayland process jumps between 0 and 1% CPU usage and when I move my mouse (on the desktop) it jumps to about 12-15% CPU usage. This is on a Zephyrus G15 GA502IV laptop with Ryzen 9 4900HS and Vega 8. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab
https://bugs.kde.org/show_bug.cgi?id=479094 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #5 from Andrej Halveland --- Created attachment 164508 --> https://bugs.kde.org/attachment.cgi?id=164508=edit journalctl of plasma-kwin_wayland I just experienced something pretty similar and with the same errors in logs. I was in the new overview, I closed a desktop and then quickly with the four-finger swipe down when to the desktop, but before it could get to the desktop, the screen started flickering, and when I tried going to another virtual desktop by using the gestures, the screen went black. I reproduced it twice in a row, but as soon as I pulled out my camera I can't reproduce it... will try my best. This is on Plasma 6 Beta 2. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0 (beta) Kernel Version: 6.7.0-rc6 Graphics Platform: Wayland Graphics Drivers: mesa 23.3.1 Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Per-screen virtual desktops
https://bugs.kde.org/show_bug.cgi?id=107302 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448420] When screen configuration changes, hidden Panel in "Auto-hide" or "Dodge Windows" mode inappropriately becomes shown until clicked again
https://bugs.kde.org/show_bug.cgi?id=448420 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #10 from Andrej Halveland --- This has been bugging me for some time now. It is especially annoying when you setup automatic switching between refresh rates when on a battery and when plugged in. Can be easily reproduced via simply changing the refresh rate either through System Settings or through kscreen-doctor. This is on Plasma 6 Beta 2. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0 (beta) Kernel Version: 6.7.0-rc6 Graphics Platform: Wayland Graphics Drivers: mesa 23.3.1 Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479023] Autohide panel not popping up in plasma 6 beta.
https://bugs.kde.org/show_bug.cgi?id=479023 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #3 from Andrej Halveland --- I kinda like this behavior to be honest. It's at least useful when you have a button or something really close to the bottom where the auto-hiding panel also is, and with this change/bug/whatever you are less likely to accidentally open the panel when you didn't want to. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478838] Plasmashell sometimes crashes in QPlatformWindow::hasPendingUpdateRequest() after or during screen being turned off
https://bugs.kde.org/show_bug.cgi?id=478838 --- Comment #7 from Andrej Halveland --- Created attachment 164435 --> https://bugs.kde.org/attachment.cgi?id=164435=edit plasmashell backtrace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478838] Plasmashell sometimes crashes in QPlatformWindow::hasPendingUpdateRequest() after or during screen being turned off
https://bugs.kde.org/show_bug.cgi?id=478838 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #6 from Andrej Halveland --- I basically get the exact same backtrace from plasmashell when I disconnect my external HDMI monitor. If it makes any difference the external monitor is connected via a VGA to HDMI adapter to my laptop. This is on Arch with the kde-unstable repo enabled. Plasma 6 Beta 2 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0 (beta) Kernel Version: 6.7.0-rc6 Graphics Platform: Wayland Graphics Drivers: mesa 23.3.1-1 Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478811] "Error loading QML file." System settings on Plasma 6.0 Beta 2
https://bugs.kde.org/show_bug.cgi?id=478811 --- Comment #9 from Andrej Halveland --- That MR also breaks the "Shortcuts" settings page. That page now shows: ``` Error loading QML file. qrc:/kcm/kcm_keys/main.qml:66 Type Kirigami.InlineMessage unavailable file:///usr/lib/qt6/qml/org/kde/kirigami/InlineMessage.qml:63 Type KT.InlineMessage unavailable qrc:/qt/qml/org/kde/kirigami/templates/InlineMessage.qml:102 Cannot assign object of type "TP.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_117*" as the former is neither the same as the latter nor a sub-class of it. ``` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478811] "Error loading QML file." System settings on Plasma 6.0 Beta 2
https://bugs.kde.org/show_bug.cgi?id=478811 --- Comment #8 from Andrej Halveland --- >https://invent.kde.org/plasma/systemsettings/-/merge_requests/280 also is a >viable fix Yes, this does seem to work. But, the "Mouse" and "Touchpad" settings in "Mouse & Touchpad" still seem to be broken, and those pages only work with `QML_DISABLE_DISK_CACHE=1`. And also stuff still goes under the header (like the one that shows the "Quick Settings" text on the landing page when launching System Settings). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478811] "Error loading QML file." System settings on Plasma 6.0 Beta 2
https://bugs.kde.org/show_bug.cgi?id=478811 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #6 from Andrej Halveland --- Until this gets fixed you can workaround this issue by putting >QML_DISABLE_DISK_CACHE=1 into your >/etc/environment file and then just reboot your system -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 478815] kscreenlocker_greet fails to display UI after upgrade to beta 2, blocks screen forcing intervention / reboot
https://bugs.kde.org/show_bug.cgi?id=478815 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478029] Window Recording freezes when resizing the window
https://bugs.kde.org/show_bug.cgi?id=478029 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 477816] Neochat crashing after login
https://bugs.kde.org/show_bug.cgi?id=477816 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434877] High CPU usage
https://bugs.kde.org/show_bug.cgi?id=434877 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #18 from Andrej Halveland --- This is still an issue. It's because of this specific issue where the plasma-systemmonitor app always uses 50% CPU of one core that I always used the older "systemmonitor" app. It's a real bummer that the older "systemmonitor" app got removed in favor of this new one, even though the new one is still really flawed. https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3471 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.7.0-rc5-1-mainline Graphics Platform: Wayland Graphics Drivers: mesa 23.3.1 Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477486] Ark not built with Qt6
https://bugs.kde.org/show_bug.cgi?id=477486 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 477902] Breeze themed cursor changes to a generic one when hovering over Qt5 apps, and also some other apps.
https://bugs.kde.org/show_bug.cgi?id=477902 Andrej Halveland changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 477902] New: Breeze themed cursor changes to a generic one when hovering over Qt5 apps, and also some other apps.
https://bugs.kde.org/show_bug.cgi?id=477902 Bug ID: 477902 Summary: Breeze themed cursor changes to a generic one when hovering over Qt5 apps, and also some other apps. Classification: Plasma Product: Breeze Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andrej.h...@gmail.com CC: uhh...@gmail.com Target Milestone: --- Created attachment 163752 --> https://bugs.kde.org/attachment.cgi?id=163752=edit Video demonstration. When hovering over Qt5 apps (and also some other apps) the cursor theme is suddenly changed to a what I think is a fallback one. STEPS TO REPRODUCE 1. Open Ark for example (Because it is a Qt5 app... Carla also does this because it is a Qt5 app, and Supersonic also does this, which is an app written in Go using the Fyne toolkit) 2. Hover your mouse cursor over Ark OBSERVED RESULT Mouse theme suddenly changes to a non-breeze one. EXPECTED RESULT The mouse theme shouldn't change. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.3-arch1-1 Graphics Platform: Wayland Graphics Drivers: mesa 23.2.1-2 Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) ADDITIONAL INFORMATION: I have both breeze and breeze5 packages installed. I am not sure if I am just missing something or of it's a genuine bug. I have also added a video attachment. Also I don't know if this is a Carla issue or not, but Carla (which is a Qt5 app) is not being themed at all after upgrading to Plasma 6. It was being themed properly when I was using Plasma 5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 464727] Dolphin and Ark start having graphical bugs after the "Choose Application" Portal opens (after double clicking on an "Unknown" file type.)
https://bugs.kde.org/show_bug.cgi?id=464727 Andrej Halveland changed: What|Removed |Added Version|5.27.2 |5.90.0 Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 464727] Dolphin and Ark start having graphical bugs after the "Choose Application" Portal opens (after double clicking on an "Unknown" file type.)
https://bugs.kde.org/show_bug.cgi?id=464727 --- Comment #5 from Andrej Halveland --- This is still an issue in Plasma 5.90.0 I am guessing this was implemented once again in Plasma 6? But sadly it is still causing issues. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.3-arch1-1 Graphics Platform: Wayland Graphics Drivers: mesa 23.2.1-2 Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477359] Add Vlad Zahorodnii's Sliding Notifications desktop effect into Plasma.
https://bugs.kde.org/show_bug.cgi?id=477359 Andrej Halveland changed: What|Removed |Added OS|Linux |Unspecified Platform|Arch Linux |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477359] New: Add Vlad Zahorodnii's Sliding Notifications desktop effect into Plasma.
https://bugs.kde.org/show_bug.cgi?id=477359 Bug ID: 477359 Summary: Add Vlad Zahorodnii's Sliding Notifications desktop effect into Plasma. Classification: Plasma Product: kwin Version: 5.27.80 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: andrej.h...@gmail.com Target Milestone: --- It would be nice to add Vlad Zahorodnii's Sliding Notifications desktop effect into Plasma 6 as an alternative effect to the currently used fading one. Maybe even enable it by default in Plasma 6? https://github.com/zzag/kwin-effects-sliding-notifications -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384782] Allow manually re-ordering tray icons
https://bugs.kde.org/show_bug.cgi?id=384782 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468916] Plasma Panel Visually Freezes
https://bugs.kde.org/show_bug.cgi?id=468916 --- Comment #13 from Andrej Halveland --- I meant to say "hangs" instead of "crashes", as that's what was probably happening to me back then. Sorry! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468916] Plasma Panel Visually Freezes
https://bugs.kde.org/show_bug.cgi?id=468916 --- Comment #12 from Andrej Halveland --- I kind of forgot about this bug report. I just want to say that I have not experienced these crashes for some time now... i am not sure if it was because of some downloaded plasmoids or whatever but I am not getting these crashes anymore. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454206] Slow performance with RAW files on big folders
https://bugs.kde.org/show_bug.cgi?id=454206 Andrej Halveland changed: What|Removed |Added Ever confirmed|0 |1 Version|22.04.1 |23.04.3 CC||andrej.h...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Andrej Halveland --- I have the same issue... loading folders with few hundred RAW photos, or even a single (1) RAW photo takes ages to load. Loading just one RAW image takes about 7 seconds to load, and while it's loading, the Gwenview process has CPU usage of 300%. On the other hand, something like Geeqie loads RAW images (even hundreds of images) basically INSTANTLY. Gwenview is just unusable for RAW image viewing. Even digiKam is significantly faster than Gwenview, but not as fast as Geeqie. The RAW photos in question are Canon's .CR2 Loading JPEG images is fine. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.5-rc5 Graphics Platform: Wayland Graphics Drivers: mesa-git (23.3.0_devel.176075.8c62b3938a8.d41d8cd-1) Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 460388] Opening then closing widget does not remove created node from Pipewire, leading to multiple "Plasma PA" dangling nodes
https://bugs.kde.org/show_bug.cgi?id=460388 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #2 from Andrej Halveland --- I believe this is the same behavior as in my own bug report? https://bugs.kde.org/show_bug.cgi?id=467117 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472959] kwin_wayland crashed in "KWin::Workspace::setActiveWindow(KWin::Window*)"? after closing an app
https://bugs.kde.org/show_bug.cgi?id=472959 --- Comment #2 from Andrej Halveland --- Created attachment 160705 --> https://bugs.kde.org/attachment.cgi?id=160705=edit Coredump right after crash (no kwin-debug package) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472959] kwin_wayland crashed in "KWin::Workspace::setActiveWindow(KWin::Window*)"? after closing an app
https://bugs.kde.org/show_bug.cgi?id=472959 --- Comment #1 from Andrej Halveland --- Text from kwin_crash_closing_supersonic-desktop-more-debug-symbols.gdb Thread 11 (LWP 1633): #0 0x7fb349226c0f in __strncasecmp_l_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:547 #1 0x7fb3180013f0 in () #2 0x7fb3180013f0 in () #3 0x0002 in () #4 0x in () #5 0x0002 in () #6 0x7fb347b6cc2f in () at /usr/lib/libglib-2.0.so.0 #7 0x7fb347b0d0e2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #8 0x7fb34a2eb4cc in QTypedArrayData::allocate(unsigned long, QFlags) (options=..., capacity=0) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:221 #9 QTypedArrayData::unsharableEmpty() () at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:274 #10 QVector::detach() (this=0x7fb318001301) at ../../include/QtCore/../../src/corelib/tools/qvector.h:402 #11 QVector::detach() (this=0x7fb318001301) at ../../include/QtCore/../../src/corelib/tools/qvector.h:397 #12 QVector::removeLast() (this=0x7fb318001301) at ../../include/QtCore/../../src/corelib/tools/qvector.h:821 #13 QVector::takeLast() (this=0x7fb318001301) at ../../include/QtCore/../../src/corelib/tools/qvector.h:156 #14 QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:509 #15 0x5627e4e5f968 in () #16 0x5627e4e5f910 in () #17 0x5627e4d6bd50 in () #18 0x7fb32e7fbcc0 in () #19 0x7ffcea804710 in () #20 0x7fb32dffc000 in () #21 0x7fb34a0f72d6 in (anonymous namespace)::(anonymous namespace)::Q_QGS_freelist::innerFunction () at thread/qreadwritelock.cpp:618 #22 (anonymous namespace)::(anonymous namespace)::Q_QGS_freelist::innerFunction () at thread/qreadwritelock.cpp:618 #23 QGlobalStatic, (anonymous namespace)::(anonymous namespace)::Q_QGS_freelist::innerFunction, (anonymous namespace)::(anonymous namespace)::Q_QGS_freelist::guard>::operator* (this=) at ../../include/QtCore/../../src/corelib/global/qglobalstatic.h:147 #24 QReadWriteLockPrivate::allocate() () at thread/qreadwritelock.cpp:624 #25 0x9dc100adb148d800 in () #26 0x in () --Type for more, q to quit, c to continue without paging--c Thread 10 (LWP 1682): #0 __glob (pattern=, flags=, errfunc=, pglob=0x5627e4dfac68) at ../posix/glob.c:845 Thread 9 (LWP 1686): #0 __glob (pattern=, flags=, errfunc=, pglob=0x5627e4dfac6c) at ../posix/glob.c:845 Thread 8 (LWP 1660): #0 0x7fb349226c0f in __strncasecmp_l_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:547 #1 0x7fb3040013d0 in () #2 0x7fb3040013d0 in () #3 0x0001 in () #4 0x in () #5 0x0001 in () #6 0x7fb347b6cc2f in () at /usr/lib/libglib-2.0.so.0 #7 0x7fb347b0d0e2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #8 0x7fb34a2eb4cc in QTypedArrayData::allocate(unsigned long, QFlags) (options=..., capacity=0) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:221 #9 QTypedArrayData::unsharableEmpty() () at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:274 #10 QVector::detach() (this=0x7fb304001301) at ../../include/QtCore/../../src/corelib/tools/qvector.h:402 #11 QVector::detach() (this=0x7fb304001301) at ../../include/QtCore/../../src/corelib/tools/qvector.h:397 #12 QVector::removeLast() (this=0x7fb304001301) at ../../include/QtCore/../../src/corelib/tools/qvector.h:821 #13 QVector::takeLast() (this=0x7fb304001301) at ../../include/QtCore/../../src/corelib/tools/qvector.h:156 #14 QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:509 #15 0x5627e5541348 in () #16 0x5627e55412f0 in () #17 0x5627e554af70 in () #18 0x7fb3173feca0 in () #19 0x7ffcea803f80 in () #20 0x7fb316bff000 in () #21 0x7fb34a0f72d6 in (anonymous namespace)::(anonymous namespace)::Q_QGS_freelist::innerFunction () at thread/qreadwritelock.cpp:618 #22 (anonymous namespace)::(anonymous namespace)::Q_QGS_freelist::innerFunction () at thread/qreadwritelock.cpp:618 #23 QGlobalStatic, (anonymous namespace)::(anonymous namespace)::Q_QGS_freelist::innerFunction, (anonymous namespace)::(anonymous namespace)::Q_QGS_freelist::guard>::operator* (this=) at ../../include/QtCore/../../src/corelib/global/qglobalstatic.h:147 #24 QReadWriteLockPrivate::allocate() () at thread/qreadwritelock.cpp:624 #25 0x7fb34a0f34fa in QHash::freeData(QHashData*) (x=0x10012, this=0x5627e554af70) at ../../include/QtCore/../../src/corelib/tools/qhash.h:617 #26 QHash::detach_helper() (this=0x5627e554af70) at ../../include/QtCore/../../src/corelib/tools/qhash.h:633 #27 QHash::detach() (this=0x5627e554af70) at ../../include/QtCore/../../src/corelib/tools/qhash.h:291 #28 0x9dc100adb148d800 in () #29 0x in () Thread 7 (LWP 1648): #0 __glob (pattern=, flags=, errfunc=, pglob=0x7fb34314e5d0) at ../posix/glob
[kwin] [Bug 472959] New: kwin_wayland crashed in "KWin::Workspace::setActiveWindow(KWin::Window*)"? after closing an app
https://bugs.kde.org/show_bug.cgi?id=472959 Bug ID: 472959 Summary: kwin_wayland crashed in "KWin::Workspace::setActiveWindow(KWin::Window*)"? after closing an app Classification: Plasma Product: kwin Version: 5.27.7 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andrej.h...@gmail.com Target Milestone: --- Created attachment 160704 --> https://bugs.kde.org/attachment.cgi?id=160704=edit Coredump with more symbols I had Supersonic (the Subsonic compatible music client) compiled with Wayland support running fine... but after I closed it via the "Close" button in the Window Frame suddenly KWin crashed and restarted. Btw I have closed the Supersonic app before multiple times just fine, but this time it for some reason made KWin crash. I also don't know if anything changes if the application is running via XWayland. I don't know how to reproduce this reliably, this is the first time KWin crashed like this. STEPS TO REPRODUCE 1. Compile supersonic-desktop from the AUR with wayland support (add the "-tags=wayland" option to the "go build" line when compiling) 2. Close the application via the "Close" button on the window frame. OBSERVED RESULT KWin crashes and restarts. EXPECTED RESULT KWin should not crash. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.5-rc4 Graphics Platform: Wayland Graphics Drivers: mesa-git (23.3.0_devel.174810.9709ae4cc66.d41d8cd-1) Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) ADDITIONAL INFORMATION The kwin_crash_closing_supersonic-desktop-more-debug-symbols.gdb coredump was rerun after I rebooted my machine and then installed the kwin-debug package. The kwin_crash_closing_supersonic-desktop.gdb coredump was ran right after I got the crash (without the kwin-debug package). -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 472805] Neochat crash on start
https://bugs.kde.org/show_bug.cgi?id=472805 --- Comment #3 from Andrej Halveland --- Yeah, I submitted a bug report a moment ago. https://bugs.archlinux.org/task/79261 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 472805] Neochat crash on start
https://bugs.kde.org/show_bug.cgi?id=472805 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #1 from Andrej Halveland --- I had the same issue today where Neochat started fine, but sometimes it would crash outright, or sometimes I would have to switch channels a bunch of times and then it would crash. So just this moment I locally compiled Arch's neochat from PKGBUILD and now it seems to work fine. To try and compile neochat yourself do this: Install base-devel and devtools via `sudo pacman -Syu base-devel devtools` Then clone the neochat PKGBUILD with `pkgctl repo clone neochat` Now go into that directory with `cd neochat` And now compile and install neochat with `makepkg -s -i --skipinteg` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459082] Wayland - Notification on primary monitor in wrong place
https://bugs.kde.org/show_bug.cgi?id=459082
Andrej Halveland changed:
What|Removed |Added
CC||andrej.h...@gmail.com
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
--- Comment #4 from Andrej Halveland ---
I can reproduce this by simply plugging in my external monitor to my laptop
after Plasma is started.
This can be fixed by simply opening "Display Configuration" from my system tray
and then switching to or between different modes ("Extend to left" or "Extend
to right"). Or it can also be fixed by re-arranging any screen in System
Settings.
Here's a video of it:
https://youtu.be/YXzPtj2QO9E
--
You are receiving this mail because:
You are watching all bug changes.
[kio-extras] [Bug 296526] Dolphin is too slow when upload a file on a SSH server
https://bugs.kde.org/show_bug.cgi?id=296526 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468916] Plasma Panel Visually Freezes
https://bugs.kde.org/show_bug.cgi?id=468916 --- Comment #10 from Andrej Halveland --- Created attachment 160097 --> https://bugs.kde.org/attachment.cgi?id=160097=edit Plasmashell hang backtraces Here are my latest 4 hangs. In the last two hangs (05-07-2023 and 01-07-2023) I have noticed a lot of "ThreadWeaver" related stuff that didn't appear in the older backtraces. I want to say that this ThreadWeaver stuff started appearing after removing the "Media Player" widget from my panel, but I am not entirely sure... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468916] Plasma Panel Visually Freezes
https://bugs.kde.org/show_bug.cgi?id=468916 --- Comment #9 from Andrej Halveland --- Here's my latest hang on Plasma 5.27.6 Attaching to process 3926368 [New LWP 3926381] [New LWP 3926382] [New LWP 3926383] [New LWP 3926388] [New LWP 3926389] [New LWP 3926390] [New LWP 3926391] [New LWP 3926399] [New LWP 3926400] [New LWP 3926401] [New LWP 3926402] [New LWP 3926411] [New LWP 3926436] [New LWP 3926483] [New LWP 3926484] [New LWP 3926485] [New LWP 3926486] [New LWP 3926487] [New LWP 3926488] [New LWP 3926617] [New LWP 3926665] [New LWP 3926678] [New LWP 3926841] [New LWP 3926842] [New LWP 3926844] [New LWP 3926845] --Type for more, q to quit, c to continue without paging--c [New LWP 3926847] [New LWP 3926857] [New LWP 3926858] [New LWP 3926860] [New LWP 3926861] [New LWP 3926862] [New LWP 3956015] [New LWP 3956016] [New LWP 3956018] [New LWP 3956019] [New LWP 3956020] [New LWP 3978981] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". 0x7f3281899f0e in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x7f32780e9480) at futex-internal.c:57 57 return INTERNAL_SYSCALL_CANCEL (futex_time64, futex_word, op, expected, (gdb) thread apply all bt Thread 39 (Thread 0x7f319dbfc6c0 (LWP 3978981) "KIO::WorkerThre"): #0 0x7f3281913d06 in __GI_ppoll (fds=fds@entry=0x7f319dbfba88, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42 #1 0x7f32820e356f in ppoll (__ss=, __timeout=, __nfds=, __fds=) at kernel/qcore_unix.cpp:129 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f319dbfba88) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f319dbfba88) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll(pollfd*, unsigned long, timespec const*) (timeout_ts=, nfds=, fds=) at kernel/qcore_unix.cpp:155 #5 qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=fds@entry=0x7f319dbfba88, nfds=nfds@entry=1, timeout_ts=) at kernel/qcore_unix.cpp:150 #6 0x7f3281d63094 in qt_poll_msecs (nfds=1, timeout=, fds=0x7f319dbfba88) at ../../include/QtCore/5.15.10/QtCore/private/../../../../../src/corelib/kernel/qcore_unix_p.h:381 #7 QNativeSocketEnginePrivate::nativeSelect(int, bool, bool, bool*, bool*) const (this=this@entry=0x7f31cc007760, timeout=, checkRead=checkRead@entry=true, checkWrite=checkWrite@entry=false, selectForRead=selectForRead@entry=0x7f319dbfbb67, selectForWrite=0x7f319dbfbb66) at socket/qnativesocketengine_unix.cpp:1436 #8 0x7f3281d64ab6 in QNativeSocketEngine::waitForReadOrWrite(bool*, bool*, bool, bool, int, bool*) (this=0x7f31cc001410, readyToRead=0x7f319dbfbb67, readyToWrite=, checkRead=true, checkWrite=false, msecs=, timedOut=0x0) at socket/qnativesocketengine.cpp:1120 #9 0x7f3281d51407 in QAbstractSocket::waitForReadyRead(int) (this=0x7f31cc006700, msecs=-1) at socket/qabstractsocket.cpp:2293 #10 0x7f32816eeeaa in () at /usr/lib/libKF5KIOCore.so.5 #11 0x7f328172303a in KIO::SlaveBase::dispatchLoop() () at /usr/lib/libKF5KIOCore.so.5 #12 0x7f32817a2077 in () at /usr/lib/libKF5KIOCore.so.5 #13 0x7f3281ef34da in operator() (__closure=) at thread/qthread_unix.cpp:350 #14 (anonymous namespace)::terminate_on_exception > (t=) at thread/qthread_unix.cpp:287 #15 QThreadPrivate::start(void*) (arg=0x5638be2a7920) at thread/qthread_unix.cpp:310 #16 0x7f328189d44b in start_thread (arg=) at pthread_create.c:444 #17 0x7f3281920e40 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 38 (Thread 0x7f320a8856c0 (LWP 3956020) "QSGRenderThread"): #0 0x7f3281899f0e in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x5638bed43100) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x5638bed43100, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7f3281899f8f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5638bed43100, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7f328189c7a0 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5638bed430b0, cond=0x5638bed430d8) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x5638bed430d8, mutex=0x5638bed430b0) at pthread_cond_wait.c:618 #5 0x7f3281efb264 in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5638bed430b0) at thread/qwaitcondition_unix.cpp:146 #6 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x5638be474908, mutex=mutex@entry=0x5638be474900, deadline=...) at thread/qwaitcondition_unix.cpp:225 #7 0x7f3283bfd712 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x5638be4748f8) at /usr/src/debug/
[plasmashell] [Bug 469227] When switching screens on in specific order, tooltips and dashboard may appear at wrong positions/screen
https://bugs.kde.org/show_bug.cgi?id=469227 --- Comment #13 from Andrej Halveland --- Yeah, sure. The Application Dashboard seems to open on the wrong (external) monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469227] When switching screens on in specific order, tooltips and dashboard may appear at wrong positions/screen
https://bugs.kde.org/show_bug.cgi?id=469227 Andrej Halveland changed: What|Removed |Added Ever confirmed|0 |1 CC||andrej.h...@gmail.com Status|REPORTED|CONFIRMED --- Comment #11 from Andrej Halveland --- I have a very similar behavior on my laptop. https://i.imgur.com/hzyWISu.mp4 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 Kernel Version: 6.3.4-arch1-1 Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468916] Plasma Panel Visually Freezes
https://bugs.kde.org/show_bug.cgi?id=468916 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #8 from Andrej Halveland --- I have the same behavior, just that I don't know how to reproduce it on demand, it always seems pretty random when the hang happens. These are without debug symbols, for now. I will install the related debug packages and will send another backtrace when it eventually hangs again. Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.4.0-rc2 Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS 8-Core Processor Memory: 24GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) Attaching to process 3306240 [New LWP 3306241] [New LWP 3306242] [New LWP 3306243] [New LWP 3306244] [New LWP 3306245] [New LWP 3306246] [New LWP 3306247] [New LWP 3306250] [New LWP 3306251] [New LWP 3306252] [New LWP 3306257] [New LWP 3306274] [New LWP 3306275] [New LWP 3306276] [New LWP 3306277] [New LWP 3306320] [New LWP 3306321] [New LWP 3306322] [New LWP 3306323] [New LWP 3306325] [New LWP 3306356] [New LWP 3306406] [New LWP 3306407] [New LWP 3306408] [New LWP 3306411] [New LWP 3306414] [New LWP 3306415] [New LWP 3306416] [New LWP 3306419] [New LWP 3306420] [New LWP 3306421] [New LWP 3306422] [New LWP 3306423] [New LWP 3306424] [New LWP 3312371] [New LWP 3312372] [New LWP 3312373] [New LWP 3336077] [New LWP 3336078] [New LWP 3336079] [New LWP 3395474] [New LWP 3395475] --Type for more, q to quit, c to continue without paging--c [New LWP 3395476] [New LWP 52931] [New LWP 52932] [New LWP 52933] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". 0x7fca2d899f0e in ?? () from /usr/lib/libc.so.6 (gdb) bt #0 0x7fca2d899f0e in () at /usr/lib/libc.so.6 #1 0x7fca2d89c7a0 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fca2deeb6f4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7fca2fc0002a in () at /usr/lib/libQt5Quick.so.5 #4 0x7fca2e556927 in QWindow::event(QEvent*) () at /usr/lib/libQt5Gui.so.5 #5 0x7fca2ed78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #6 0x7fca2e08e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #7 0x7fca2e54aa34 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/libQt5Gui.so.5 #8 0x7fca2e5298c5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #9 0x7fca2f9408d5 in () at /usr/lib/libQt5WaylandClient.so.5 #10 0x7fca2ccd753b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #11 0x7fca2cd34219 in () at /usr/lib/libglib-2.0.so.0 #12 0x7fca2ccd61a2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #13 0x7fca2e0d8d3c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #14 0x7fca2e08668c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #15 0x7fca2e0912f9 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #16 0x55b90131f16c in () #17 0x7fca2d839850 in () at /usr/lib/libc.so.6 #18 0x7fca2d83990a in __libc_start_main () at /usr/lib/libc.so.6 #19 0x55b90131f515 in () (gdb) thread apply all bt Thread 47 (Thread 0x7fc9015fa6c0 (LWP 52933) "QSGRenderThread"): #0 0x7fca2d899f0e in () at /usr/lib/libc.so.6 #1 0x7fca2d89c7a0 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fca2deeb6f4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7fca2fbfcfc2 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fca2dee424a in () at /usr/lib/libQt5Core.so.5 #5 0x7fca2d89d44b in () at /usr/lib/libc.so.6 #6 0x7fca2d920e40 in () at /usr/lib/libc.so.6 Thread 46 (Thread 0x7fc901dfb6c0 (LWP 52932) "plasmash:gdrv0"): #0 0x7fca2d899f0e in () at /usr/lib/libc.so.6 #1 0x7fca2d89c7a0 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fca20ec256c in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fca20f0b98c in () at /usr/lib/dri/radeonsi_dri.so #4 0x7fca2d89d44b in () at /usr/lib/libc.so.6 #5 0x7fca2d920e40 in () at /usr/lib/libc.so.6 Thread 45 (Thread 0x7fc9025fc6c0 (LWP 52931) "plasmash:gdrv0"): #0 0x7fca2d899f0e in () at /usr/lib/libc.so.6 #1 0x7fca2d89c7a0 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fca20ec256c in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fca20f0b98c in () at /usr/lib/dri/radeonsi_dri.so #4 0x7fca2d89d44b in () at /usr/lib/libc.so.6 #5 0x7fca2d920e40 in () at /usr/lib/libc.so.6 Threa
[kwin] [Bug 469818] Games unable to render properly at 150% scaling
https://bugs.kde.org/show_bug.cgi?id=469818 Andrej Halveland changed: What|Removed |Added Keywords||wayland Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org CC||andrej.h...@gmail.com Version|unspecified |5.27.4 Component|general |wayland-generic Product|kde |kwin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468235] Screen refresh rate stuck at 60hz even when set to 144hz in the display settings
https://bugs.kde.org/show_bug.cgi?id=468235 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #5 from Andrej Halveland --- I have bisected this bug to this https://invent.kde.org/plasma/kwin/-/commit/dc95392b982ac9ae95a72e5f38e5ecc499f0bc19 commit -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 467117] While the audio is suspended, "Plasma PA" does not disappear after opening and closing the audio widget from tray.
https://bugs.kde.org/show_bug.cgi?id=467117 Andrej Halveland changed: What|Removed |Added Summary|Connections between apps|While the audio is |with suspended audio and|suspended, "Plasma PA" does |"Plasma PA" do not |not disappear after opening |disconnect after closing|and closing the audio |the widget from tray. |widget from tray. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 467117] New: Connections between apps with suspended audio and "Plasma PA" do not disconnect after closing the widget from tray.
https://bugs.kde.org/show_bug.cgi?id=467117 Bug ID: 467117 Summary: Connections between apps with suspended audio and "Plasma PA" do not disconnect after closing the widget from tray. Classification: Plasma Product: plasma-pa Version: 5.27.2 Platform: Archlinux OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andrej.h...@gmail.com CC: isma...@gmail.com, m...@ratijas.tk, now...@gmail.com Target Milestone: --- Created attachment 157148 --> https://bugs.kde.org/attachment.cgi?id=157148=edit Video demonstration. When viewing "pw-top" or Carla, I can see new audio connections made each time when opening the "Plasma PA" widget (with the Applications tab open) from tray when an app like Firefox or Spotify are paused. The connections immediately disappear when an audio starts playing from the specific apps. This is when using PipeWire, I don't know how (or if) it behaves the same on PulseAudio. STEPS TO REPRODUCE 1. Open an app like Firefox, open a YouTube video and then pause it. 2. Or open Spotify, play something for a second and then pause it. 3. Open "pw-top" in terminal 4. Start opening and closing the Audio Volume (with the Applications shown, not the devices) widget located in the system tray. OBSERVED RESULT "Plasma PA" clients start appearing in pw-top, and only disappear when playing audio from the apps that had their audio paused. EXPECTED RESULT The "Plasma PA" clients should disappear regardless if the audio client has their audio suspended/paused or not. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2 Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS Memory: 16GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 272539] WISH: Instant preview like OSX Snow Leopard
https://bugs.kde.org/show_bug.cgi?id=272539 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 464727] Dolphin and Ark start having graphical bugs after the "Choose Application" Portal opens (after double clicking on an "Unknown" file type.)
https://bugs.kde.org/show_bug.cgi?id=464727 Andrej Halveland changed: What|Removed |Added Summary|Dolphin and Ark start |Dolphin and Ark start |having graphical bugs after |having graphical bugs after |the "Choose Application"|the "Choose Application" |Portal opens (after double |Portal opens (after double |clicking on "Unknown" Type |clicking on an "Unknown" |file.) |file type.) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464727] Dolphin starts having graphical bugs after the "Choose Application" Portal opens (after double clicking on "Unknown" Type file.)
https://bugs.kde.org/show_bug.cgi?id=464727 --- Comment #3 from Andrej Halveland --- It's also 100% reproducible in Ark by right clicking on a text file (for example) and choosing "Open With...". This is on Plasma 5.27.2, KF 5.103.0, Qt 5.15.8. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 465248] Show GPU/VRAM usage for processes
https://bugs.kde.org/show_bug.cgi?id=465248 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455526] Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 --- Comment #20 from Andrej Halveland --- (In reply to Andrej Halveland from comment #18) > I have not yet tested reverting the patch (but I don't think it will be > straight forward after so many code changes) as it's already 4 in the > morning and I want to go to bed :). I have not yet tested reverting the patch on the latest Plasma release as I don't think it will be a straight forward code revert after so many code changes -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455526] Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 --- Comment #19 from Andrej Halveland --- (In reply to Andrej Halveland from comment #18) > archive repo from 2020/06/21 so I could install Plasma 5.25.0. I meant 2022/06/21 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455526] Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 --- Comment #18 from Andrej Halveland --- After many hours of bisecting (and wasting my time on bisecting whatever was already bisected, and fixed... sigh), I have come to this (https://invent.kde.org/plasma/kwin/-/commit/aac0609bb99d76d54a4861458b0859356f76c5ca) commit that is causing these issues, the commit before that (https://invent.kde.org/plasma/kwin/-/commit/d4c44220b455d91578c588277393def30325f6b2) is all fine without those blur glitches. This has been tested on Plasma 5.25.0 in Wayland on Arch Linux using the archive repo from 2020/06/21 so I could install Plasma 5.25.0. I have not yet tested reverting the patch (but I don't think it will be straight forward after so many code changes) as it's already 4 in the morning and I want to go to bed :). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464727] Dolphin starts having graphical bugs after the "Choose Application" Portal opens (after double clicking on "Unknown" Type file.)
https://bugs.kde.org/show_bug.cgi?id=464727 Andrej Halveland changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464727] Dolphin starts having graphical bugs after the "Choose Application" Portal opens (after double clicking on "Unknown" Type file.)
https://bugs.kde.org/show_bug.cgi?id=464727 --- Comment #2 from Andrej Halveland --- I can also reproduce this in a Garuda "KDE Git" Linux VM with VirtioGPU acceleration, with the latest git master. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kguiaddons] [Bug 463199] "After taking screenshot: Copy to clipboard" does not work anymore on Wayland
https://bugs.kde.org/show_bug.cgi?id=463199 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464727] Dolphin starts having graphical bugs after the "Choose Application" Portal opens (after double clicking on "Unknown" Type file.)
https://bugs.kde.org/show_bug.cgi?id=464727 --- Comment #1 from Andrej Halveland --- Downgrading `plasma-integration` to version 5.26.5, which changes the "Show Application" from the Portal one to the "old" one fixes my issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464727] New: Dolphin starts having graphical bugs after the "Choose Application" Portal opens (after double clicking on "Unknown" Type file.)
https://bugs.kde.org/show_bug.cgi?id=464727 Bug ID: 464727 Summary: Dolphin starts having graphical bugs after the "Choose Application" Portal opens (after double clicking on "Unknown" Type file.) Classification: Applications Product: dolphin Version: 22.12.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: andrej.h...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 13 --> https://bugs.kde.org/attachment.cgi?id=13=edit Video Since I upgraded to Plasma 5.26.90 (from the kde-unstable repository on Arch) I noticed that after I double-click on a file that has the "Unknown" type, which causes the new "Choose Application" Portal to appear, Dolphin stops updating half it's GUI (well the part where you can browse your folders). This does not happen when I right-click on a file and choose "Other Application", only when I double-click on a file with "Unknown" file type. STEPS TO REPRODUCE 1. Upgrade to Plasma 5.26.90 2. Open Dolphin 3. Open a file with "Unknown" file type. OBSERVED RESULT Half the GUI stops updating. Although resizing the windows updates it. EXPECTED RESULT No GUI glitches should appear. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-rc3 Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS 8-Core Processor Memory: 16GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455526] Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463891] Popups appear in their own window when activated while the app is inactive.
https://bugs.kde.org/show_bug.cgi?id=463891 --- Comment #2 from Andrej Halveland --- Ok, Filelight seems to be fixed in git master, but Dolphin still exhibits this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463891] New: Popups appear in their own window when activated while the app is inactive.
https://bugs.kde.org/show_bug.cgi?id=463891 Bug ID: 463891 Summary: Popups appear in their own window when activated while the app is inactive. Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andrej.h...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 155059 --> https://bugs.kde.org/attachment.cgi?id=155059=edit Video demonstration. I am not entirely sure in which category this belongs to, so please correct it if it's wrong... sorry! STEPS TO REPRODUCE 1. Open (for example) Filelight and scan anything you want 2. Make the Filelight app inactive by clicking on any other open app (or the desktop) 3. Hover over Filelight's pie chart with your cursor so a popup appears OBSERVED RESULT Popup appears in it's own window in the middle of the screen. EXPECTED RESULT Popup should appear the same as when the app is active. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.2-arch1-1-snipex (Includes ACS Override patch and redisabled freesync) Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS 8-Core Processor Memory: 16GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463661] New: Auto-hiding panel won't show while dragging a file.
https://bugs.kde.org/show_bug.cgi?id=463661 Bug ID: 463661 Summary: Auto-hiding panel won't show while dragging a file. Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: andrej.h...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 154924 --> https://bugs.kde.org/attachment.cgi?id=154924=edit Video demonstration. SUMMARY When trying to drag a file to an application that is hidden, the hidden panel won't un-hide (so that I could point to the application on the "Icons-only task manager" and then drag-and-drop the file in that application). STEPS TO REPRODUCE 1. Enable auto-hide on a panel. 2. Drag a file from a file manager and point it at the hidden panel. OBSERVED RESULT Panel doesn't do anything. EXPECTED RESULT Panel should show up when dragging a file to the panel. SOFTWARE/OS VERSIONS Linux kernel: 6.1.0-arch1 CPU: Ryzen 9 4900HS GPU: Vega 8 RAM: 16GB KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460902] The screen flickers while dimming when turning off the screen.
https://bugs.kde.org/show_bug.cgi?id=460902 --- Comment #5 from Andrej Halveland --- I believe this wasn't pushed into the "Plasma/5.26" branch? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461707] KWin crashes when approaching really small app menu bar that auto-hides from under
https://bugs.kde.org/show_bug.cgi?id=461707 --- Comment #3 from Andrej Halveland --- Created attachment 153780 --> https://bugs.kde.org/attachment.cgi?id=153780=edit "coredumpctl gdb 1314" (kwin_wayland) backtrace Here you go. I hope this is a good backtrace (fingers crossed). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461707] KWin crashes when approaching really small app menu bar that auto-hides from under
https://bugs.kde.org/show_bug.cgi?id=461707 --- Comment #1 from Andrej Halveland --- **CORRECTION** OBSERVED RESULT KWin crashes (if mesa_glthread is enabled on plasmashell it restarts and becomes kinda functional, if mesa_glthread is disabled on plasmashell then plasmashell crashes which results in black screen, and trying to open krunner makes it freeze alltogether). I am using mesa-git 23.0.0_devel.162480.c987a727a76.d41d8cd98f00b204e9800998ecf8427e-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461707] New: KWin crashes when approaching really small app menu bar that auto-hides from under
https://bugs.kde.org/show_bug.cgi?id=461707 Bug ID: 461707 Summary: KWin crashes when approaching really small app menu bar that auto-hides from under Classification: Plasma Product: kwin Version: 5.26.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andrej.h...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Right click on desktop --> "Add Panel" --> "Application Menu Bar" 2. Make it the smallest you can 3. Enable auto-hide 4. Try to "un-hide" it with mouse from under (trying to un-hide it from sideways does not trigger the crash) OBSERVED RESULT KWin crashes (and restarts when mesa_glthread is on, if mesa_glthread is disabled on plasmashell then only plasmashell crashes). EXPECTED RESULT KWin shouldn't crash. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.7-zen1-1-zen Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS 8-Core Processor Memory: 16GB of RAM Graphics Processor: Integrated: Vega 8 Dedicated: NVIDIA GeForce RTX 2060 Max-Q Manufacturer: ASUS (Zephyrus G15 GA502IV) ADDITIONAL INFORMATION Making the panel a little bigger stops KWin from crashing. Video on how to trigger the crash: https://youtu.be/Mv5tBGjNP-4 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 456310] Keyboard volume control keys don't change the volume of the default sink
https://bugs.kde.org/show_bug.cgi?id=456310 --- Comment #3 from Andrej Halveland --- Created attachment 153299 --> https://bugs.kde.org/attachment.cgi?id=153299=edit Bug showcase Also forgot to mention... If I close the audio source (mpv in the video), I once again can't adjust the volume by using volume keys, as seen at the end of the video. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 456310] Keyboard volume control keys don't change the volume of the default sink
https://bugs.kde.org/show_bug.cgi?id=456310 Andrej Halveland changed: What|Removed |Added Ever confirmed|0 |1 CC||andrej.h...@gmail.com Status|REPORTED|CONFIRMED --- Comment #2 from Andrej Halveland --- I have the exact same behaviour, although I noticed that when the virtual sinks are not connected to anything the volume seems to adjust just fine, but If I load my Carla project with several EQs and things like that, then it starts to misbehave... I experience this bug on multiple of my computers. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: Plasma 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460905] Blur effects briefly becomes transparent when apps go to/from maximized state.
https://bugs.kde.org/show_bug.cgi?id=460905 --- Comment #1 from Andrej Halveland --- Created attachment 153152 --> https://bugs.kde.org/attachment.cgi?id=153152=edit Video (X11) Also, I am not sure how old this bug is, as I noticed this bug when I started using the transparency/blur effect in Konsole just recently. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460905] New: Blur effects briefly becomes transparent when apps go to/from maximized state.
https://bugs.kde.org/show_bug.cgi?id=460905 Bug ID: 460905 Summary: Blur effects briefly becomes transparent when apps go to/from maximized state. Classification: Plasma Product: kwin Version: 5.26.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: andrej.h...@gmail.com Target Milestone: --- Created attachment 153151 --> https://bugs.kde.org/attachment.cgi?id=153151=edit Video (wayland) When having blur enabled in Konsole or in for example Dolphin (when using the "Lightly" Application Style) the blur briefly becomes transparent when the animation for maximizing begins and ends. When disabling the Maximize/Restore desktop effect it still happens, but it's much, much less noticeable (it's like only a frame or so). (Also, sorry if I chose the wrong "Component") STEPS TO REPRODUCE 1. In Konsole enable the transparency and blur effect. 2. Maximize/Restore Konsole. OBSERVED RESULT Blur becomes transparent on the start and end of the maximize/restore animation. EXPECTED RESULT Blur should not get transparent while Maximizing/Restoring. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-zen1-1-zen Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS 8-Core Processor Memory: 16GB of RAM Graphics Processor: Integrated: Vega 8 Dedicated: NVIDIA GeForce RTX 2060 Max-Q Manufacturer: ASUS (Zephyrus G15 GA502IV) ADDITIONAL INFORMATION I have also tried this in X11 but it's even worse... The blur does not resize when maximizing Konsole, and so there is a box in the top left that is blurred, and the rest in transparent. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460902] The screen flickers while dimming when turning off the screen.
https://bugs.kde.org/show_bug.cgi?id=460902 --- Comment #1 from Andrej Halveland --- Created attachment 153150 --> https://bugs.kde.org/attachment.cgi?id=153150=edit Video demonstration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460902] New: The screen flickers while dimming when turning off the screen.
https://bugs.kde.org/show_bug.cgi?id=460902 Bug ID: 460902 Summary: The screen flickers while dimming when turning off the screen. Classification: Plasma Product: kwin Version: 5.26.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andrej.h...@gmail.com Target Milestone: --- There is like 70% chance when turning the screen off by either using the "Turn off screen" shortcut or when using > kscreen-doctor --dpms off (and probably also when letting the screen turn itself off after some time) causes the screen to flicker while the screen is dimming. STEPS TO REPRODUCE 1. Use "kscreen-doctor --dpms off" to turn the screen off. OBSERVED RESULT While dimming the screen flickers. EXPECTED RESULT Smooth transition from the screen being on to completely turning off. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-zen1-1-zen Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS 8-Core Processor Memory: 16GB of RAM Graphics Processor: Integrated: Vega 8 Dedicated: NVIDIA GeForce RTX 2060 Max-Q Manufacturer: ASUS (Zephyrus G15 GA502IV) ADDITIONAL INFORMATION This is not a new regression, this is at least a few releases old. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460382] Blurred windows get transparent when using gestures / when sliding between virtual desktops
https://bugs.kde.org/show_bug.cgi?id=460382 --- Comment #3 from Andrej Halveland --- >I saw 5.26.0 and thought we might have broken it, but it was probably broken >for a while already Yes, I should've mentioned that too... When applying this patch to the Plasma/5.26 branch it does fix the sliding blur on windows, but does not fix it on the Application Bar/Default Panel (I forgot to mention to enable "Slide docks" in Virtual Desktop settings). But then I also noticed when I compiled KWin with the "work/zzag/slide-effect-blur" branch (with some janky hack to make it compile with Plasma 5.26 and Wayland 1.20, idk if it broke something) the "Slide Docks" feature disappeared from the settings? Is it because I am using stable Plasma 5.26 with the "way too new" KWin? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460382] Blurred windows get transparent when using gestures / when sliding between virtual desktops
https://bugs.kde.org/show_bug.cgi?id=460382 --- Comment #1 from Andrej Halveland --- Created attachment 152781 --> https://bugs.kde.org/attachment.cgi?id=152781=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460382] New: Blurred windows get transparent when using gestures / when sliding between virtual desktops
https://bugs.kde.org/show_bug.cgi?id=460382 Bug ID: 460382 Summary: Blurred windows get transparent when using gestures / when sliding between virtual desktops Classification: Plasma Product: kwin Version: git-stable-Plasma/5.26 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: andrej.h...@gmail.com Target Milestone: --- Created attachment 152780 --> https://bugs.kde.org/attachment.cgi?id=152780=edit Screenshot 1 When the blur effects are enabled and you use the three-finger swipe to smoothly slide into the next virtual desktop you can see that the blur effect also somehow slides, which results in the blur to become transparent. This is not limited to the three-finger swipe action though... If you set the animation to be really slow and change your desktop by using the Pager you can also see it. STEPS TO REPRODUCE 1. Create multiple desktops/workspaces 2. Use the "Slide" desktop effect 3. Switch between virtual desktops OBSERVED RESULT Blur disappears/reappears as the transition from one desktop to another happens. EXPECTED RESULT Blur should not become transparent. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.1-arch1-1 Graphics Platform: Wayland and X11 Processors: AMD Ryzen 9 4900HS 8-Core Processor Memory: 16GB of RAM Graphics Processor: Integrated: Vega 8 Dedicated: NVIDIA GeForce RTX 2060 Max-Q Manufacturer: ASUS (Zephyrus G15 GA502IV) ADDITIONAL INFORMATION This is also happens when using any of the gestures on Wayland (all windows with blur become transparent, see screenshots). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460322] New: Desktop becomes unresponsive when trying to type or use the mouse after using "Turn Off Screen" shortcut.
https://bugs.kde.org/show_bug.cgi?id=460322 Bug ID: 460322 Summary: Desktop becomes unresponsive when trying to type or use the mouse after using "Turn Off Screen" shortcut. Classification: Plasma Product: kwin Version: git-stable-Plasma/5.26 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andrej.h...@gmail.com Target Milestone: --- When attempting to use the Screen Off shortcut it works just fine (when executing it multiple times it seems to get visually buggy, no big deal) but when If I for example press the shortcut for turning Off the Screen and accidentally press another button or move the mouse after pressing the shortcut for turning off the screen, it seems to "wake up" but doing practically anything is not possible anymore, and only way to fix it is to actually suspend the system, afterwards it's fine. STEPS TO REPRODUCE 1. Bind a keybind to the "Turn Off Screen" shortcut. 2. Try typing on the keyboard or move the mouse while or right after activating the shortcut. OBSERVED RESULT Screen wakes up and the desktop becomes unusable. EXPECTED RESULT Screen should wake up and the desktop remain fully functional. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.90 / 5.26 KDE Frameworks Version: 5.98.0 / 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.19.13-arch1-g14-1 Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS 8-Core Processor Memory: 16GB of RAM Graphics Processor: Integrated: Vega 8 Dedicated: NVIDIA GeForce RTX 2060 Max-Q Manufacturer: ASUS (Zephyrus G15 GA502IV) ADDITIONAL INFORMATION I believe I first noticed this on Plasma 5.24.x around when I got a new laptop, of course this could be much, much older bug. Video demonstration: https://www.youtube.com/watch?v=kU-yMYr72e8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459286] [Regression, Bisected] Screen garbles/freezes when changing resolution/refresh rate respectively.
https://bugs.kde.org/show_bug.cgi?id=459286 --- Comment #4 from Andrej Halveland --- Here's the report: https://gitlab.freedesktop.org/drm/amd/-/issues/2162 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459286] [Regression, Bisected] Screen garbles/freezes when changing resolution/refresh rate respectively.
https://bugs.kde.org/show_bug.cgi?id=459286 --- Comment #2 from Andrej Halveland --- Created attachment 152159 --> https://bugs.kde.org/attachment.cgi?id=152159=edit output of journalctl --boot 0 | grep kwin_wayland_drm -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459286] [Regression, Bisected] Screen garbles/freezes when changing resolution/refresh rate respectively.
https://bugs.kde.org/show_bug.cgi?id=459286 --- Comment #1 from Andrej Halveland --- Created attachment 152158 --> https://bugs.kde.org/attachment.cgi?id=152158=edit dmesg output with drm debugging -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459286] New: [Regression, Bisected] Screen garbles/freezes when changing resolution/refresh rate respectively.
https://bugs.kde.org/show_bug.cgi?id=459286 Bug ID: 459286 Summary: [Regression, Bisected] Screen garbles/freezes when changing resolution/refresh rate respectively. Classification: Unclassified Product: kwin Version: 5.25.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andrej.h...@gmail.com Target Milestone: --- Updating to Plasma 5.25.90 I noticed that whenever my screen refresh rate changes (e.g. disconnecting/connecting the charger by a script) the screen completely freezes (and if let sitting for a few minutes, then it also starts to garble) and requires a reboot afterwards. Changing the screen resolution garbles/corrupts the screen but returning to the previous resolution gets the screen un-garbled. STEPS TO REPRODUCE 1. Be on latest beta KWin release (5.25.90) 2. Change screen refresh-rate/resolution OBSERVED RESULT Screen freezes after changing refresh rate, requiring a reboot. Screen garbles/corrupts after changing resolution, reverting the change "fixes" it. EXPECTED RESULT Screen shouldn't freeze and/or garble. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS 8-Core Processor Memory: 16GB of RAM Graphics Processor: Integrated: Vega 8 Dedicated: NVIDIA GeForce RTX 2060 Max-Q Manufacturer: ASUS (Zephyrus G15 GA502IV) ADDITIONAL INFORMATION Downgrading to KWin 5.25.5 fixes the issue, therefore I started to bisect and I came to commit 4be81e01761d4f541c3b34bbf02f28d635fd to be causing the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 456702] Increasing/Decreasing volume also adjusts some non-default sinks (pipewire/easyeffects)
https://bugs.kde.org/show_bug.cgi?id=456702 Andrej Halveland changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 456702] Increasing/Decreasing volume also adjusts some non-default sinks (pipewire/easyeffects)
https://bugs.kde.org/show_bug.cgi?id=456702 Andrej Halveland changed: What|Removed |Added CC||andrej.h...@gmail.com --- Comment #1 from Andrej Halveland --- Do you have KMix installed/running by any chance? I had similar behavior when KMix was running. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455814] Display will not wake from DPMS since 5.25 (Wayland Nvidia)
https://bugs.kde.org/show_bug.cgi?id=455814 --- Comment #18 from Andrej Halveland --- This time it works! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455814] Display will not wake from DPMS since 5.25 (Wayland Nvidia)
https://bugs.kde.org/show_bug.cgi?id=455814 --- Comment #16 from Andrej Halveland --- Sadly, it's the same -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455814] Display will not wake from DPMS since 5.25 (Wayland Nvidia)
https://bugs.kde.org/show_bug.cgi?id=455814 --- Comment #14 from Andrej Halveland --- Oh, ok. Anyways, https://invent.kde.org/plasma/kwin/-/merge_requests/2602 does not work/improve anything, screen stays black and keyboard is unresponsive like on the "stock" build -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455814] Display will not wake from DPMS since 5.25 (Wayland Nvidia)
https://bugs.kde.org/show_bug.cgi?id=455814 Andrej Halveland changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/merge_requests/25 ||99/diffs?commit_id=ad7b90ef ||437c621dff993ea9bc6120ba64d ||bccd5 --- Comment #12 from Andrej Halveland --- The merge request @ https://invent.kde.org/plasma/kwin/-/merge_requests/2599 did indeed fix the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455814] Display will not wake from DPMS since 5.25 (Wayland Nvidia)
https://bugs.kde.org/show_bug.cgi?id=455814 --- Comment #9 from Andrej Halveland --- Created attachment 150274 --> https://bugs.kde.org/attachment.cgi?id=150274=edit dmesg output with drm debugging > So I started the logging > turned off dpms > closed the lid to put the system > to sleep > resumed from suspend by opening the lid > SSH'd to my laptop from > another computer > killed kwin with "sudo pkill -9 kwin" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455814] Display will not wake from DPMS since 5.25 (Wayland Nvidia)
https://bugs.kde.org/show_bug.cgi?id=455814 --- Comment #7 from Andrej Halveland --- Created attachment 150244 --> https://bugs.kde.org/attachment.cgi?id=150244=edit output of journalctl --boot 0 | grep kwin_wayland_drm Yeah, I think the >Atomic test for (0) failed! Invalid argument is the main culprit here, I hope... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455814] Display will not wake from DPMS since 5.25 (Wayland Nvidia)
https://bugs.kde.org/show_bug.cgi?id=455814 --- Comment #5 from Andrej Halveland --- I have updated to Plasma 5.25.2 but the issue still persists. But as I previously said, this error doesn't appear anymore. >kwin_wayland_drm: Setting dpms mode failed! But this one still does: >kwin_wayland_drm: Couldn't parse EDID for connector DrmConnector(id=78, >gpu=KWin::DrmGpu(0x55d5c9178250), name="eDP-1-unknown", >connection="Connected"```, countMode=14) For now I use a really hacky workaround where I basically enable the dpms back on with "kscreen-doctor --dpms on" by using systemd to execute it before suspending. After that resuming works perfectly. And btw how can I make sure that Xaver Hugl has been CC'd or "pinged" again? I am not sure how all of this works exactly. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455814] Display will not wake from DPMS since 5.25 (Wayland Nvidia)
https://bugs.kde.org/show_bug.cgi?id=455814 --- Comment #4 from Andrej Halveland --- (In reply to Nate Graham from comment #3) > Bug 455795 was just fixed yesterday; are you sure you have > https://invent.kde.org/plasma/kwin/-/commit/ > ea8b0d962be15fbf5c4c29ac4dd657ff34344e17? Yes, I can assure you that I had that commit when compiling kwin. I have used the Plasma/5.25 branch and I have checked that those changes were actually there. The steps I have made: 1. (in kwin git folder) mkdir build && cd build 2. cmake .. 3. make -j8 4. sudo pacman -R kwin (to uninstall my current kwin package) 5. sudo make install (to install newly compiled kwin) 6. restarted my machine -- You are receiving this mail because: You are watching all bug changes.
