[plasmashell] [Bug 492634] plasmashell freezes
https://bugs.kde.org/show_bug.cgi?id=492634 Ondřej Niesner changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492634] plasmashell freezes
https://bugs.kde.org/show_bug.cgi?id=492634 --- Comment #5 from Ondřej Niesner --- Created attachment 173379 --> https://bugs.kde.org/attachment.cgi?id=173379&action=edit media player freezing plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492634] plasmashell freezes
https://bugs.kde.org/show_bug.cgi?id=492634 --- Comment #4 from Ondřej Niesner --- I managed to reproduce the issue. It has to do something with media player that I am using on my panel. Playing some specific songs on spotify freezes the plasmashell. I listen to spotify a lot so that why it happened randomly. I managed to reproduce it with this exact song https://open.spotify.com/track/4GFpaMQrDhrrOQ7CUzNTiU?si=2d576fdadb4043c8 It only happens when the media player is on the panel. On desktop it's fine. I recorded a video of that happening. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492634] plasmashell freezes
https://bugs.kde.org/show_bug.cgi?id=492634 Ondřej Niesner changed: What|Removed |Added CC||ondra.nies...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492634] plasmashell freezes
https://bugs.kde.org/show_bug.cgi?id=492634 --- Comment #3 from Ondřej Niesner --- Created attachment 173347 --> https://bugs.kde.org/attachment.cgi?id=173347&action=edit drkonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492634] plasmashell freezes
https://bugs.kde.org/show_bug.cgi?id=492634 --- Comment #2 from Ondřej Niesner --- Created attachment 173346 --> https://bugs.kde.org/attachment.cgi?id=173346&action=edit gdb -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492634] New: plasmashell freezes
https://bugs.kde.org/show_bug.cgi?id=492634 Bug ID: 492634 Summary: plasmashell freezes Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ondra.nies...@seznam.cz CC: k...@davidedmundson.co.uk Target Milestone: 1.0 I got a issue that my desktop freezes randomly. I don’t know how to reproduce it but it’s really annoying. I am not able click on anything, all completly frozen. Both monitors are affected. Right click, left on desktop doesn't work, panel, all widgets on desktop or on panel are frozen. It’s really annoying when you realize your clock widget is frozen. Alt tabbing, krunner works normally. Restarting plasmashell using systemctl --user restart plasma-plasmashell.service, takes few minutes. Quicker is just to kill the process. Also when that happens the plasmashell process is using 100% one core of my cpu. There's noting in logs at the time when it happens. I can tell by time of my clock widget when it's frozen. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.7-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449105] Dragging a window that was opened maximized moves the mouse cursor to the top left corner of the window
https://bugs.kde.org/show_bug.cgi?id=449105 --- Comment #22 from Ondřej Niesner --- Created attachment 159586 --> https://bugs.kde.org/attachment.cgi?id=159586&action=edit dragging window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449105] Dragging a window that was opened maximized moves the mouse cursor to the top left corner of the window
https://bugs.kde.org/show_bug.cgi?id=449105 Ondřej Niesner changed: What|Removed |Added CC||ondra.nies...@seznam.cz --- Comment #21 from Ondřej Niesner --- Same was also happening on GNOME. It doesn't matter how many screens you have. I have this issue on my laptop which has just one builtin display. This is really annoying bug especially with touchpad when you always need to grab the window from wrong position. Also the window is totally messing it's position when you try to resize it. In mutter it was fixed https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2942?commit_id=7eb01304259b5977feaee3b2d0a2073b70312d89 Is it possible to use in in kwin? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451639] Chromium stuck at 60 fps
https://bugs.kde.org/show_bug.cgi?id=451639 Ondřej Niesner changed: What|Removed |Added Component|compositing |wayland-generic -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451639] New: Chromium stuck at 60 fps
https://bugs.kde.org/show_bug.cgi?id=451639 Bug ID: 451639 Summary: Chromium stuck at 60 fps Product: kwin Version: 5.24.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: ondra.nies...@seznam.cz Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Run "chromium --ozone-platform=wayland" with high refresh rate monitor. OBSERVED RESULT FPS are going down when using Chromium with higher refresh rate. Even with like 75 hz scrolling is not smooth. I tried to set my monitor to different refresh rate and this what I measured. It's really weird. FPS were measured from testufo.com Chromium with 60 hz = 60 fps. 75 hz = 75 fps 100 hz = 100 fps 120 hz = 58 fps 144 hz = 58 fps I tested Chromium on GNOME and Sway and I have no issues at all. It was running smoothly. I have this problem only on KDE. I personally don't use Chromium browser but this affects all programs that are running on Chromium. EXPECTED RESULT Run Chromium smoothly on Wayland with higher refresh rate. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.16.14-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439986] Maximized windows does not follow cursor.
https://bugs.kde.org/show_bug.cgi?id=439986 --- Comment #2 from Ondřej Niesner --- It's checked. It works fine until I close for example dolphin as maximized. Than it will open maximized but on my left monitor even cursor is on right. Unmaximizing dolphin will switch from maximized mode to "normal" window but it's still maximized because it does not remember unmaximized state. I think this is related to https://bugs.kde.org/show_bug.cgi?id=437089 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439987] Chromium bad performance on Wayland
https://bugs.kde.org/show_bug.cgi?id=439987 --- Comment #4 from Ondřej Niesner --- (In reply to Vlad Zahorodnii from comment #1) > Can you please check if changing the latency policy (in system settings) to > "prefer smoothest animations" fixes the issue? Running Firefox on Wayland will match my monitor refresh rate (144 hz) on GNOME 40 and KDE Plasma 5.22.3. https://webglsamples.org/aquarium/aquarium.html I get stable 144 fps. Running Chrome on Wayland will not match my monitor refresh rate and I got around 55 fps on https://webglsamples.org/aquarium/aquarium.html not even stable 60 This does not happen on GNOME 40. Log from Chrome: [27275:27275:0728/020403.343050:ERROR:cursor_loader.cc(107)] Failed to load a platform cursor of type kNull [27316:27316:0728/020403.368223:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is egl [27316:27316:0728/020403.371236:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [27316:27316:0728/020436.766161:ERROR:gles2_cmd_decoder.cc(8216)] [.WebGL-0xe023ba22100]GL ERROR :GL_INVALID_OPERATION : glClear: can't be called on integer buffers [27316:27316:0728/020437.059872:ERROR:gles2_cmd_decoder.cc(10718)] [.WebGL-0xe023ba22100]RENDER WARNING: there is no texture bound to the unit 1 [27316:27316:0728/020437.104605:ERROR:gles2_cmd_decoder.cc(8216)] [.WebGL-0xe023ba22100]GL ERROR :GL_INVALID_OPERATION : glClear: can't be called on integer buffers [27316:27316:0728/020437.106266:ERROR:gles2_cmd_decoder.cc(10738)] [.WebGL-0xe023ba22100]GL ERROR :GL_INVALID_OPERATION : glDrawArrays: Texture bound to texture unit 1 with internal format GL_RG32UI is not compatible with sampler type GL_SAMPLER_2D Can I provide some additional information? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Ondřej Niesner changed: What|Removed |Added CC||ondra.nies...@seznam.cz --- Comment #8 from Ondřej Niesner --- I have two monitors and if I close application as maximized and open it than the application opens always on my left monitor. Totally ignores where is my cursor located. For example System Monitor will open on left monitor as maximized but not in maximized state. But Firefox opens in maximized state but if I click restore down than it will be still maximized but it switeches from maximized state to restore down state. Overall applications does not remember their positions and sizes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439987] Chromium bad performance on Wayland
https://bugs.kde.org/show_bug.cgi?id=439987 --- Comment #3 from Ondřej Niesner --- (In reply to Vlad Zahorodnii from comment #1) > Can you please check if changing the latency policy (in system settings) to > "prefer smoothest animations" fixes the issue? Nothing changed. Also I got some SIGBUS errors in Chromium. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439987] Chromium bad performance on Wayland
https://bugs.kde.org/show_bug.cgi?id=439987 --- Comment #2 from Ondřej Niesner --- Created attachment 140187 --> https://bugs.kde.org/attachment.cgi?id=140187&action=edit Chromium SIGBUS error -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439987] New: Chromium bad performance on Wayland
https://bugs.kde.org/show_bug.cgi?id=439987 Bug ID: 439987 Summary: Chromium bad performance on Wayland Product: kwin Version: 5.22.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ondra.nies...@seznam.cz Target Milestone: --- SUMMARY Launching chromium or any chromium based application with "--enable-features=UseOzonePlatform --ozone-platform=wayland" I got very poor performance on KDE Wayland. Chromium does not match monitors refresh rate and FPS is very low around 48-58 fps. On GNOME Chromium is beautifully smooth. I tried run Chromium both on KDE, GNOME on OpenSUSE, Manjaro. Chromium was always laggy on KDE, smooth on GNOME. STEPS TO REPRODUCE 1. Launch chromium with native Wayland support "--enable-features=UseOzonePlatform --ozone-platform=wayland" EXPECTED RESULT Gain performance by running Chromium on native Wayland support. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439986] New: Maximized windows does not follow cursor.
https://bugs.kde.org/show_bug.cgi?id=439986 Bug ID: 439986 Summary: Maximized windows does not follow cursor. Product: kwin Version: 5.22.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ondra.nies...@seznam.cz Target Milestone: --- SUMMARY Windows that were closed as maximized does not open on monitor where cursor is located. Window opens on most left monitor. STEPS TO REPRODUCE 1. Maximize window SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438208] New: Task manager minimize animation goes to wrong screen
https://bugs.kde.org/show_bug.cgi?id=438208 Bug ID: 438208 Summary: Task manager minimize animation goes to wrong screen Product: plasmashell Version: 5.21.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: ondra.nies...@seznam.cz CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 139075 --> https://bugs.kde.org/attachment.cgi?id=139075&action=edit task manager minimize animation STEPS TO REPRODUCE 1. Use two monitors on X11 session OBSERVED RESULT Minimize animation goes to wrong screen. If I add a second (icons only) task manager to my left monitor than all animation goes to the left monitor. My right monitor is primary display. This affects only X11 session and checked these options "From current desktop" and "From current activity" in task manger settings. EXPECTED RESULT Minimize animation should go to task manager where is the window located. Window is on left screen than minimize to left screen. Window is on right screen than minimize to right screen. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.8-1-MANJARO OS Type: 64-bit Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15,6 GiB of RAM Graphics Processor: Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
