[kwin] [Bug 482178] Wayland renders the whole desktop in half refresh rate
https://bugs.kde.org/show_bug.cgi?id=482178 --- Comment #9 from Mario Ray Mahardhika --- 6.0.2 arrives to Neon, and I can confirm it's fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482178] Wayland renders the whole desktop in half refresh rate
https://bugs.kde.org/show_bug.cgi?id=482178 --- Comment #7 from Mario Ray Mahardhika --- (In reply to Zane from comment #6) > This seems similar to what I'm seeing in > https://bugs.kde.org/show_bug.cgi?id=482064 > On Wayland, the frame rate is half of the refresh rate. Could be, same Plasma 6 Wayland, despite running on totally different platform. So we know it's not platform specific. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482178] Wayland renders the whole desktop in half refresh rate
https://bugs.kde.org/show_bug.cgi?id=482178 --- Comment #5 from Mario Ray Mahardhika --- > Not sure if this would help the OP as his issue occurs with only one display, > but hopefully this helps someone with a setup similar to mine. Not directly, but should help developers isolating the potential cause. I also happen to have a USB-C to DP cable which I can use to test on my external monitor, which indeed doesn't exhibit the same problem. High refresh rate (170Hz) even works just fine. So maybe the scope can be reduced to HDMI and DSI connector, leaving DisplayPort out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482178] Wayland renders the whole desktop in half refresh rate
https://bugs.kde.org/show_bug.cgi?id=482178 --- Comment #2 from Mario Ray Mahardhika --- `sudo dmesg | i915` is the same for both sessions, however `xrandr --verbose` shows some differences: Wayland === Screen 0: minimum 16 x 16, current 1920 x 1200, maximum 32767 x 32767 DSI-1 connected primary 1920x1200+0+0 (0x23) right (normal left inverted right x axis y axis) 141mm x 226mm Identifier: 0x21 Timestamp: 18133 Subpixel: horizontal rgb Gamma: inf:inf:inf Brightness: 0.40 Clones: CRTC: 0 CRTCs: 0 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: RANDR Emulation: 1 non-desktop: 0 supported: 0, 1 1200x1920 (0x23) 161.250MHz -HSync +VSync *current +preferred h: width 1200 start 1288 end 1416 total 1632 skew0 clock 98.81KHz v: height 1920 start 1923 end 1933 total 1978 clock 49.95Hz X11 === Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 16384 DSI-1 connected primary 1920x1200+0+0 (0x47) right (normal left inverted right x axis y axis) 0mm x 0mm Identifier: 0x41 Timestamp: 173498 Subpixel: horizontal rgb Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 2 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: _KDE_SCREEN_INDEX: 1 panel orientation: Normal supported: Normal, Upside Down, Left Side Up, Right Side Up scaling mode: Full aspect supported: Full, Center, Full aspect link-status: Good supported: Good, Bad CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 CONNECTOR_ID: 185 supported: 185 non-desktop: 0 range: (0, 1) 1200x1920 (0x47) 136.887MHz +HSync +VSync *current +preferred h: width 1200 start 1240 end 1252 total 1268 skew0 clock 107.96KHz v: height 1920 start 2125 end 2127 total 2159 clock 50.00Hz No idea if these matter, though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482178] Wayland renders the whole desktop in half refresh rate
https://bugs.kde.org/show_bug.cgi?id=482178 --- Comment #1 from Mario Ray Mahardhika --- Created attachment 166268 --> https://bugs.kde.org/attachment.cgi?id=166268=edit UFO test on Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482178] New: Wayland renders the whole desktop in half refresh rate
https://bugs.kde.org/show_bug.cgi?id=482178 Bug ID: 482178 Summary: Wayland renders the whole desktop in half refresh rate Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: leledumbo_c...@yahoo.co.id CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 166267 --> https://bugs.kde.org/attachment.cgi?id=166267=edit UFO test on X11 SUMMARY *** Choosing Plasma Wayland session on Plasma 6.0 will present a desktop that has everything rendered in half of what the screen refresh rate is. *** STEPS TO REPRODUCE 1. In SDDM login screen, choose Plasma (Wayland) session 2. Do anything: move mouse, open apps, whatever, it will look choppy OBSERVED RESULT Any changes on the desktop are choppy EXPECTED RESULT Any changes on the desktop are smooth SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0 (available in About System) KDE Plasma Version: 6.0 KDE Frameworks Version: 6.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION $ inxi -F System: Host: LeleChuwi Kernel: 6.6.5-060605-generic x86_64 bits: 64 Desktop: KDE Plasma 6.0.0 Distro: KDE neon 22.04 6.0 Machine: Type: Laptop System: CHUWI Innovation And (ShenZhen) product: MiniBook X v: N/A serial: Mobo: N/A model: N/A serial: UEFI: American Megatrends LLC. v: DNN20A V2.03 date: 12/28/2023 Battery: ID-1: BAT0 charge: 28.9 Wh (100.0%) condition: 28.9/28.9 Wh (100.0%) CPU: Info: quad core model: Intel N100 bits: 64 type: MCP cache: L2: 2 MiB Speed (MHz): avg: 801 min/max: 700/801 cores: 1: 801 2: 801 3: 801 4: 801 Graphics: Device-1: Intel driver: i915 v: kernel Device-2: HYGD-220831-A Hy-Usb2.0-1 MIC type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1200~50Hz OpenGL: renderer: Mesa Intel Graphics (ADL-N) v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2 Audio: Device-1: Intel driver: snd_hda_intel Device-2: HYGD-220831-A Hy-Usb2.0-1 MIC type: USB driver: uvcvideo Sound Server-1: ALSA v: k6.6.5-060605-generic running: yes Sound Server-2: PipeWire v: 0.3.48 running: yes Network: Device-1: Intel driver: iwlwifi IF: wlp0s20f3 state: up mac: c0:a5:e8:40:76:62 Bluetooth: Device-1: Intel AX201 Bluetooth type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: C0:A5:E8:40:76:66 bt-v: 3.0 Drives: Local Storage: total: 476.94 GiB used: 22.99 GiB (4.8%) ID-1: /dev/nvme0n1 model: KPART512GBC2DVT size: 476.94 GiB Partition: ID-1: / size: 455.73 GiB used: 22.99 GiB (5.0%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: /boot/efi size: 299.4 MiB used: 6.1 MiB (2.0%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: partition size: 12.56 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p3 Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 217 Uptime: 26m Memory: 11.43 GiB used: 3.22 GiB (28.2%) Shell: Bash inxi: 3.3.13 Attached is a proof using UFO framerate test (https://www.testufo.com/), named after the corresponding session. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 429408] kde-open5 changes case of argument
https://bugs.kde.org/show_bug.cgi?id=429408 Mario Ray Mahardhika changed: What|Removed |Added CC||leledumbo_c...@yahoo.co.id -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430525] New: Magic Lamp is stuttering when another window is open
https://bugs.kde.org/show_bug.cgi?id=430525 Bug ID: 430525 Summary: Magic Lamp is stuttering when another window is open Product: kwin Version: 5.20.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: leledumbo_c...@yahoo.co.id Target Milestone: --- SUMMARY I think this is better described as a video: https://youtu.be/bDFsksynmKk tl;dr: * standalone window -> effect is smooth * another window behind -> effect is stuttering STEPS TO REPRODUCE 1. Enable Magic Lamp effect, optionally Show FPS as well 2. Open two apps, preferably KDE apps (shouldn't matter, but just in case) 3. Minimize both 4. Start maximizing/minimizing one with the other stay minimized 5. Maximize the other 6. Start maximizing/minimizing again with the same window from step 4 OBSERVED RESULT With Show FPS, at step 4 the fps only goes down by 10 or so and only at the first or second minimize. The subsequent application is stable at highest reachable fps. Visually, the animation is very smooth like there's no frame skipping. At step 6, the fps goes down by up to 30 with 20-ish average and it stays so subsequently. Visually, the animation is like there are skipped frames so the smoothness is much less. EXPECTED RESULT Step 6 should have the same performance as step 4. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro with 5.9.11-3 kernel KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION * CPU/GPU: i7-7700HQ/Intel UHD 620 * KWin MaxFPS: 144 Compositor: * Scale method: Crisp * Rendering backend: OpenGL 3.1 * Vsync: auto * Allow application to block compositing: ✓ Other enabled desktop effects: * Accessibility: Zoom * Appearance: Background contrast, Blur, Desaturate Unresponsive Applications, Fading Popups, Full Screen, Login, Logout, Maximize, Morphing popups, Screen Edge, Sheet, Sliding popups, Translucency, Wobbly Windows * Focus: Dialog Parent, Dim Inactive, Dim Screen for Administrator Mode, Slide Back * Show Desktop Animation: Window Aperture * Virtual Desktop Switching Animation: Desktop Cube Animation * Window Management: Desktop Cube, Present Windows, Resize Window * Window Open/Close Animation: Glide -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425664] Starting docker changes the sensors in CPU Usage monitor
https://bugs.kde.org/show_bug.cgi?id=425664 --- Comment #5 from Mario Ray Mahardhika --- (In reply to David Edmundson from comment #4) > Should be fixed by a7d1b0d95c7ad22e0249e86d5e14092f06ca4299 in ksysguard Has it been tagged to be released in the next version? i.e. 5.19.5 maybe? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425664] Starting docker changes the sensors in CPU Usage monitor
https://bugs.kde.org/show_bug.cgi?id=425664 --- Comment #3 from Mario Ray Mahardhika --- Oh, stopping docker afterwards does not return the sensors back to what it should be. It sticks until reboot (relogin doesn't help). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425664] Starting docker changes the sensors in CPU Usage monitor
https://bugs.kde.org/show_bug.cgi?id=425664 --- Comment #2 from Mario Ray Mahardhika --- Created attachment 131090 --> https://bugs.kde.org/attachment.cgi?id=131090=edit widget condition after docker is started -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425664] Starting docker changes the sensors in CPU Usage monitor
https://bugs.kde.org/show_bug.cgi?id=425664 --- Comment #1 from Mario Ray Mahardhika --- Created attachment 131089 --> https://bugs.kde.org/attachment.cgi?id=131089=edit widget condition before docker is started -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425664] New: Starting docker changes the sensors in CPU Usage monitor
https://bugs.kde.org/show_bug.cgi?id=425664 Bug ID: 425664 Summary: Starting docker changes the sensors in CPU Usage monitor Product: plasmashell Version: 5.19.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: leledumbo_c...@yahoo.co.id CC: plasma-b...@kde.org Target Milestone: 1.0 Initially, CPU Usage monitor widget is working normally, showing usage of each CPU cores. But right after starting docker service, the sensors get changed into docker network sensors. STEPS TO REPRODUCE 1. Start KDE without docker service running 2. Ensure CPU monitor widget shows CPU cores usage 3. Start docker service 4. CPU monitor will show docker ones instead OBSERVED RESULT CPU monitor widget shows docker sensors values EXPECTED RESULT CPU monitor widget still shows CPU cores usage values SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaroi KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405590] Memory leak in CPU monitor widget
https://bugs.kde.org/show_bug.cgi?id=405590 --- Comment #2 from Mario Ray Mahardhika --- I found a new fact that is actually applies to any widget that updates itself every certain period (practically every monitor widget). Only those which are static unaffected (e.g. calendar). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405590] Memory leak in CPU monitor widget
https://bugs.kde.org/show_bug.cgi?id=405590 --- Comment #1 from Mario Ray Mahardhika --- Video uploaded: https://youtu.be/of_3N-rMoXc Sorry for the fan noise and keyboard typing sound. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405590] New: Memory leak in CPU monitor widget
https://bugs.kde.org/show_bug.cgi?id=405590 Bug ID: 405590 Summary: Memory leak in CPU monitor widget Product: plasmashell Version: 5.15.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: leledumbo_c...@yahoo.co.id Target Milestone: 1.0 SUMMARY Putting CPU monitor widget on desktop makes Xorg slowly but sure eating RAM until all RAM is eaten then the whole system freezes. STEPS TO REPRODUCE 1. On a clean desktop, add CPU monitor widget 2. Open something like htop OBSERVED RESULT Xorg slowly eats RAM up to a point where the whole system will freeze. EXPECTED RESULT Xorg only has slight, one time RAM increase to accomodate the widget. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.0.0-rc7/5.15.3 KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION If you then remove the widget, RAM usage will stop raising at the current percentage. Re-adding the widget will make it start raising again. A video demonstrating the leak is being uploaded, coming soon. -- You are receiving this mail because: You are watching all bug changes.
