[plasmashell] [Bug 483128] vertical floating panel bleeds into adjacent monitor when window maximized.
https://bugs.kde.org/show_bug.cgi?id=483128 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #3 from Aleksey Zagorodnikov --- Created attachment 166905 --> https://bugs.kde.org/attachment.cgi?id=166905=edit Horizontal panel bleeds on second monitor Hi, I assume there is the same problem with my panels' arrangement. Maximized or not - it doesn't matter. Floating or fixed too. If I have a vertical panel on the left, then the horizontal panel on top or bottom will shift to another monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #8 from Aleksey Zagorodnikov --- Before 5.27 it wasn't happening, noticed it right after update. During tests, I've realized that firefox and chrome somehow related to this behavior. When I close their windows - mouse seems to hover smoothly. But instantly laggy after running the browser again. Disabling hover previews doesn't instantly solve the issue, it needs to restart plasmashell, otherwise, it is laggy even without previews. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #6 from Aleksey Zagorodnikov --- Noticed in journal kwin_wayland[1819]: kwin_screencast: Dropping a screencast frame because the compositor is slow And it seems disabling "Show small windows previews when hovering over Tasks" option in Task Manager settings solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #5 from Aleksey Zagorodnikov --- Got the same issue, but it does not consistently reproduce, at least several minutes it works okay after boot, or after plasmashell --replace. I've noticed that video in Firefox stutters too when hovering over the task manager. I enable FPS counter inside firefox and it drops from 120/60 to <30fps when this happens. It reproduces on built-in display and on an external monitor too. My hardware: Operating System: Manjaro Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 38,9 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LENOVO Product Name: 21DJ System Version: ThinkBook 15 G4 IAP -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #4 from Aleksey Zagorodnikov --- Created attachment 157080 --> https://bugs.kde.org/attachment.cgi?id=157080=edit firefox drops fps -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455638] New: Captured bouncing launch icon of itself
https://bugs.kde.org/show_bug.cgi?id=455638 Bug ID: 455638 Summary: Captured bouncing launch icon of itself Product: Spectacle Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: xglo...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 149942 --> https://bugs.kde.org/attachment.cgi?id=149942=edit bouncing icon SUMMARY After recent update Plasma 5.25 spectacle starts capturing the self icon. STEPS TO REPRODUCE 1. Update manjaro unstable 2. Capture fullscreen or rectangular OBSERVED RESULT There is a Spectacle icon on a screenshot EXPECTED RESULT No Spectacle icon on a screenshot as it was before. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.5-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Genuine Intel® CPU @ 2.40GHz Memory: 31,1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449251] New: Global Menu Applet incorrectly handle multiple activities and show menu items from another app.
https://bugs.kde.org/show_bug.cgi?id=449251 Bug ID: 449251 Summary: Global Menu Applet incorrectly handle multiple activities and show menu items from another app. Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: xglo...@gmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 145989 --> https://bugs.kde.org/attachment.cgi?id=145989=edit reproduced on chrome as well SUMMARY In some cases Global Menu Applet still show menu items from previously focused app, when current focused app hasn't global menu. STEPS TO REPRODUCE 1. Place on panel Global Menu Applet 2. Switch to second activity 3. Open for example Dolphin 4. On a 1st activity open for example maximized Firefox, and sure that is in focus. 5. Open Dolphin in 1st activity 6. Close Dolphin in 1st activity OBSERVED RESULT After closed Dolphin focus brings back to Firefox, but global menu applet still show menu from Dolphin from another activity. EXPECTED RESULT Global Menu Applet should be empty as Firefox not expose menu. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Genuine Intel® CPU @ 3.20GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449160] Wrong sticky window behavior when moving in multi-monitor setup on Wayland
https://bugs.kde.org/show_bug.cgi?id=449160 --- Comment #3 from Aleksey Zagorodnikov --- Nope, only reproduces when grab title. And found that this bug can be reproduced only if window title was below the threshold. If title initially above threshold it can moved smoothly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449160] Wrong sticky window behavior when moving in multi-monitor setup on Wayland
https://bugs.kde.org/show_bug.cgi?id=449160 --- Comment #1 from Aleksey Zagorodnikov --- Created attachment 145925 --> https://bugs.kde.org/attachment.cgi?id=145925=edit arrangement of monitors -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449160] New: Wrong sticky window behavior when moving in multi-monitor setup on Wayland
https://bugs.kde.org/show_bug.cgi?id=449160 Bug ID: 449160 Summary: Wrong sticky window behavior when moving in multi-monitor setup on Wayland Product: kwin Version: git master Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: xglo...@gmail.com Target Milestone: --- Created attachment 145924 --> https://bugs.kde.org/attachment.cgi?id=145924=edit video demonstration SUMMARY My main monitor with 1440 vertical resolution and second monitor with 1024 on vertical. Second monitor placed in right-hand of primary monitor and centered on vertical. So second monitor has position +2560+208. On second monitor there is a plasma panel on top. When I move window on primary monitor by vertical axis from bottom to top it sticks/snap/hangs around +208+24 position and can move further only after mouse pass +208 position. Despite some weird recording artifacts I show it on this video https://youtu.be/SZSH1JiTtFg STEPS TO REPRODUCE 1. Setup second monitor on side of primary and offset it by vertical. 2. Place plasma panel on top of second monitor 3. Drag window on main monitor from bottom to top OBSERVED RESULT Window snaps at some point on main monitor, right when pass height where placed panel on second monitor. It also snaps when moved from top to bottom. EXPECTED RESULT Window should be moved smoothly from bottom to top and top to bottom on this monitor. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Genuine Intel® CPU @ 3.20GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449099] Hot-plugging Primary Monitor not handled correctly for XWayland
https://bugs.kde.org/show_bug.cgi?id=449099 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449099] New: Hot-plugging Primary Monitor not handled correctly for XWayland
https://bugs.kde.org/show_bug.cgi?id=449099 Bug ID: 449099 Summary: Hot-plugging Primary Monitor not handled correctly for XWayland Product: kwin Version: git-stable-Plasma/5.24 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: xrandr Assignee: kwin-bugs-n...@kde.org Reporter: xglo...@gmail.com Target Milestone: --- SUMMARY If I unplug and plug again primary monitor it was incorrectly showed in xrandr' output as not primary, and Xwayland apps starts on wrong monitor. STEPS TO REPRODUCE 1. Login in wayland session 2. Run xrandr 3. Unplug Primary monitor 4. Plug Primary monitor again 5. Run xrandr again and compare output OBSERVED RESULT Xrandr output in 5th step: XWAYLAND1 connected primary 1280x1024+2560+208 (normal left inverted right x axis y axis) 380mm x 300mm XWAYLAND2 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 600mm x 340mm EXPECTED RESULT Xrandr output in 5th step should be the same as in 2nd step: XWAYLAND0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 600mm x 340mm XWAYLAND1 connected 1280x1024+2560+208 (normal left inverted right x axis y axis) 380mm x 300mm SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Genuine Intel® CPU @ 3.20GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION My primary 2560*1440 monitor is connected via DP, and secondary 1280*1024 monitor connected via HDMI and placed on right-hand side. After login in logs: kwin_wayland_drm: Reading output configuration for KWin::DrmOutput(0x564ced0892c0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1) kwin_wayland_drm: Reading output configuration for KWin::DrmOutput(0x564cecf318c0, name="HDMI-A-2", geometry=QRect(0,0 1280x1024), scale=1) kwin_xwl: Setting primary KWin::DrmOutput(0x564ced0892c0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1) 33 After unplug monitor: kwin_wayland_drm: Removing output KWin::DrmOutput(0x564ced0892c0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1) kwin_xwl: Setting primary KWin::DrmOutput(0x564cecf318c0, name="HDMI-A-2", geometry=QRect(2560,208 1280x1024), scale=1) 35 kwin_wayland_drm: Reading output configuration for KWin::DrmOutput(0x564cecf318c0, name="HDMI-A-2", geometry=QRect(2560,208 1280x1024), scale=1) After plug monitor again: kwin_wayland_drm: Reading output configuration for KWin::DrmOutput(0x564cedebd5e0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1) kwin_wayland_drm: Reading output configuration for KWin::DrmOutput(0x564cecf318c0, name="HDMI-A-2", geometry=QRect(0,0 1280x1024), scale=1) kwin_xwl: Setting primary KWin::DrmOutput(0x564cedebd5e0, name="DP-1", geometry=QRect(0,0 2560x1440), scale=1) 35 Aside from this issue I've also experiencing #371717 after reconnect primary monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #33 from Aleksey Zagorodnikov --- Hi folks, I don't know is it make sense for investigation, but for my curiosity I was tried to research it myself. I've using desktop Intel UHD630 with two monitors, primary on DP and secondary on HDMI. And on my setup I need often to effectively unplug-plug DP monitor via KVM switch, while HDMI connected permanently, so I experiencing this kind of bugs a lot during work. Maybe this bug related to "Primary Monitor" feature? If I remove Q_EMIT primaryOutputChanged(primary); in Platform::setPrimaryOutput I can switch monitor back and forth and plasmashell doesn't loose containment on secondary monitor. I've spot another strange behavior with Primary Monitor feature and commented this https://invent.kde.org/plasma/kwin/-/commit/f91ae3e97584767d273479c4013a43e279d77f40#note_383499 but not really sure is it related or not. PS: A bit off-topic, but can we introduce settings for ignoring hot-plug events from monitors? I actually can use wayland only after removing updateOutputs from DrmBackend::handleUdevEvent, otherwise after switching KVM back and forth some windows on desktop changes their positions, a bit annoying. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448963] Panel disappears after turning monitors off/on
https://bugs.kde.org/show_bug.cgi?id=448963 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #2 from Aleksey Zagorodnikov --- In my case not only panel is gone, but background goes black and right click on it not work anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440380] Maximized windows are temporarily unresponsive when hiding titlebar for maximized windows in wayland
https://bugs.kde.org/show_bug.cgi?id=440380 --- Comment #5 from Aleksey Zagorodnikov --- I'm so sorry, didn't realized that fix is not released yet in 5.23.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440380] Maximized windows are temporarily unresponsive when hiding titlebar for maximized windows in wayland
https://bugs.kde.org/show_bug.cgi?id=440380 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #4 from Aleksey Zagorodnikov --- Hi, I've recently switched to wayland and now experiencing this problem. It is marked as resolved, but in my case it is definitely here. I'm using dual monitor setup if it matter. Operating System: Manjaro Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.13-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Genuine Intel® CPU @ 3.20GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
