[kwin] [Bug 487833] Graphical Glitches in plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=487833 --- Comment #4 from Lucas Lima --- So my hardware is the following: ~ lspci -nnk | grep VGA 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:249c] (rev a1) 06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c4) --- I have a setup to change the main renderer using KWIN_DRM_DEVICES as the following line in /etc/enviroment (please note that there are udev rules to setup those paths mentioned here) 1. KWIN_DRM_DEVICES=/dev/dri/fixed-reference/amd-card:/dev/dri/fixed-reference/nvidia-card Or when I want when I want to use the nvidia card: 2. KWIN_DRM_DEVICES=/dev/dri/fixed-reference/nvidia-card:/dev/dri/fixed-reference/amd-card Surprisingly enough, the issue seems to happen only when I'm using the amd-card as the primary renderer. When using 2., the issue doens't seem to happen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487833] Graphical Glitches in plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=487833 Lucas Lima changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Lucas Lima --- No, it happens around many applications. I'm not using any transparency in Konsole. As mentioned, it also happens when displaying a YouTube video in full-screen. Here's an example of it happening in Firefox: https://youtu.be/xUSUyo_cfNo -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487833] New: Graphical Glitches in plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=487833 Bug ID: 487833 Summary: Graphical Glitches in plasma 6.1 Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: lima.lucas...@gmail.com Target Milestone: --- SUMMARY Windows and other screen components seem to be glitching in kwin 6.1 beta in wayland The issue can be seeing happening here: https://youtu.be/3SYpui4vV-Q STEPS TO REPRODUCE 1. Move windows around, or enter full-screen in a video in Firefox. 2. 3. OBSERVED RESULT The screen should glitch with what appears to be content from the windows behind it. EXPECTED RESULT Only the contents of the current screen should be shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, Kernel 6.9.2-arch1-1 KDE Plasma Version: 6.1 Beta KDE Frameworks Version: 6.2 Qt Version: 6.7.1 Mesa Version: 24.1.0-1 ADDITIONAL INFORMATION This is in a Hybrid Graphics system with AMD Integrated graphics and Nvidia Discrete graphics, using the AMD graphics as the main renderer. The issues doesn't seem to happen if I use the Nvidia graphics as the primary renderer using KWIN_DRM_DEVICES -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487622] New: Significant performance regressions on Plasma 6.1 on AMD integrated graphics when using wayland
https://bugs.kde.org/show_bug.cgi?id=487622 Bug ID: 487622 Summary: Significant performance regressions on Plasma 6.1 on AMD integrated graphics when using wayland Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: performance Assignee: kwin-bugs-n...@kde.org Reporter: lima.lucas...@gmail.com Target Milestone: --- When using Plasma 6.1, the general performance of Plasma is having various framerate issues. My laptop is equipped with a 165hz screen and when using testufo.com the framerate appears to fluctuate between 100, 90, or even something like 60 fps. Sometimes it stabilizes for a short time at the correct 165 fps, only to fall back to the inconsistent FPS again. This happens on the internal laptop screen without any external screen connected. STEPS TO REPRODUCE 1. Open testufo.com in Kwin 6.0.90.1 using Firefox (using it's wayland backend) 2. 3. OBSERVED RESULT Framerates should vary below the monitor refresh rate. EXPECTED RESULT The Framerate should be the same as the monitor refresh rate SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.9.2-arch1-1 (available in About System) KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0-1 Qt Version: 6.7.1 ADDITIONAL INFORMATION I've tested against Mesa 24.0.7 and 24.1.0, and both show the same behavior. Using kwin-explicit-sync from AUR (https://aur.archlinux.org/packages/kwin-explicit-sync) also doesn't cause this issues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #79 from Lucas Lima --- Chiming in since I'm still very invested in this. I'm also using the Nvidia 555 driver, and I believe the issue mentieoned here: > On KDE6 (kwin 6.0.4.1), wayland session with AMD radeon 780m IGPU and > NVIDIA GeForce RTX 4060 Mobile DGPU and nvidia-open 555 driver on my external > monitor connected to nvidia HDMI port I have low fps equal to half of screen > refresh rate. Is caused by the usage of the new firmware. Kinda off topic, but to fix it add nvidia.NVreg_EnableGpuFirmware=0 to the boot command line options. Now back to the issue, since it was mentioned that it would be fixed in a future driver release, even with the new driver things have not improved. After adding the mentioned command line above, I'm back to the same performance from 550 when using a external monitor in the port attached to the Nvidia card. I'm currently using the kwin-explicit-sync package from Arch even: https://aur.archlinux.org/packages/kwin-explicit-sync, and also setting the OGL_DEDICATED_HW_STATE_PER_CONTEXT=ENABLE_ROBUST to /etc/environment, but that also does nothing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #56 from Lucas Lima --- (In reply to Dmitrii Chermnykh from comment #55) > NVIDIA 550, `OGL_DEDICATED_HW_STATE_PER_CONTEXT=ENABLE_ROBUST` envvar fixes > the issue I tried setting the envvar in /etc/environment to no effect. My Specs are: Asus Zephyrus G15 AMD Ryzen 9 5900HS with Radeon Graphics RTX 3080 Monitor plugged in the nvidia card outputs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #53 from Lucas Lima --- (In reply to Zamundaaa from comment #52) > NVidia driver 550 has been released as a beta and should fix this properly > with Plasma 6.0 Just tested the driver in plasma 6 in Arch, while the performance did improve a bit while testing on testufo.com still pretty bad. I noticed that placing the window in both screens (being shown on both the laptop screen and external monitor), it does make the framerate increase. I can make a video later to properly demonstrate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 Lucas Lima changed: What|Removed |Added CC||lima.lucas...@gmail.com --- Comment #51 from Lucas Lima --- Hello all, I wanted to share a small discovery related to this, a bit related to a post I made a while back on reddit: https://www.reddit.com/r/kde/comments/11detap/psa_on_nvidia_optimushybrid_laptops_using/ I've found that If I disable my integrated graphics from boot with the following configuration under /etc/modprobe.d/10-blacklist-amdgpu.conf: blacklist amdgpu The performance on the external display is fine but my laptop screen doesn't work, only the external monitor. However, if I add the module **after** I got into plasma with: sudo modprobe -a amdgpu I get video on both the external display and my laptop screen, and the framedrops are gone! The CPU utilization is still high though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409040] Framerate decreases rapidly in Wayland on nVidia with proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=409040 Lucas Lima changed: What|Removed |Added CC||lima.lucas...@gmail.com --- Comment #7 from Lucas Lima --- I'm also facing the same behavior. I've noticed this happens when moving any windows to the monitor connected to the Nvidia GPU. I've made a simple video to show the behavior: https://www.youtube.com/shorts/somseC1x1zQ. Notice how the CPU usage of kwin increases when there's a window in the external monitor. This is on a Zephyrus G15 (GA503QS), with a RTX 3080 and a Ryzen 9 5900HS with a integrated GPU also. However, I found that if I disable the amd GPU (using "blacklist amdgpu" on "/etc/modprobe.d/10-blacklist.conf"), the frame drops do not happen (If you want to use this as an workaround, please keep in mind that only the external monitor outputs an image and the laptop screen will be blank), so maybe this is related to the sync between them? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423319] kWin crashed when using hot corner to Present Windows
https://bugs.kde.org/show_bug.cgi?id=423319 --- Comment #19 from Lucas Lima --- I made a video the demonstrate the crash a bit better: https://www.youtube.com/watch?v=7U66sUR6918 Surprisingly, as shown on the video, if you just keep moving the mouse up indefinitely it still happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423319] kWin crashed when using hot corner to Present Windows
https://bugs.kde.org/show_bug.cgi?id=423319 Lucas Lima changed: What|Removed |Added CC||lima.lucas...@gmail.com --- Comment #13 from Lucas Lima --- So I'm on KDE Neon 5.19.5 just to send debugging information on this crash, and found out all this duplicates. If it's useful, I noticed the crash happens mostly if you trigger the corner, and upon triggering again, move the mouse quickly immediately after that. I can reproduce it reliably that way. Hope this helps! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371731] Present Windows lags/stutters when window close buttons are enabled
https://bugs.kde.org/show_bug.cgi?id=371731 Lucas Lima <lima.lucas...@gmail.com> changed: What|Removed |Added CC||lima.lucas...@gmail.com --- Comment #6 from Lucas Lima <lima.lucas...@gmail.com> --- I also have the same problems. However, I noticed that I only happens on Intel drivers when DRI 3 is enabled. On intel modesettings, the problem is always present. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371979] New: Clementine visualizer causes performance drops on Effects
https://bugs.kde.org/show_bug.cgi?id=371979 Bug ID: 371979 Summary: Clementine visualizer causes performance drops on Effects Product: kwin Version: 5.8.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: lima.lucas...@gmail.com Target Milestone: --- Created attachment 101966 --> https://bugs.kde.org/attachment.cgi?id=101966=edit Video of Slowdown When using The Accurate Scale Method, simply enabling the visualizer on clementine causes performance drops on Kwin Effects such as Expose. I've attached a video described the behavior. This is my kwinrc configuration as used. [Compositing] AnimationSpeed=3 Backend=OpenGL Enabled=true GLColorCorrection=false GLCore=true GLPlatformInterface=glx GLPreferBufferSwap=a GLTextureFilter=2 HiddenPreviews=6 OpenGLIsUnsafe=false UnredirectFullscreen=false WindowsBlockCompositing=true XRenderSmoothScale=false [Desktops] Number=3 Rows=1 [Effect-CoverSwitch] TabBox=false TabBoxAlternative=false [Effect-Cube] BorderActivate=9 BorderActivateCylinder=9 BorderActivateSphere=9 [Effect-DesktopGrid] BorderActivate=9 [Effect-FlipSwitch] TabBox=false TabBoxAlternative=false [Effect-PresentWindows] BorderActivate=7 BorderActivateAll=9 BorderActivateClass=9 FillGaps=false LayoutMode=1 LeftButtonDesktop=3 RightButtonWindow=0 ShowPanel=true [Effect-Zoom] InitialZoom=1 [ElectricBorders] Bottom=None BottomLeft=None BottomRight=None Left=None Right=None Top=None TopLeft=None TopRight=None [MouseBindings] CommandActiveTitlebar1=Raise CommandActiveTitlebar2=Start window tab drag CommandActiveTitlebar3=Operations menu CommandAll1=Move CommandAll2=Toggle raise and lower CommandAll3=Resize CommandAllKey=Alt CommandAllWheel=Nothing CommandInactiveTitlebar1=Activate and raise CommandInactiveTitlebar2=Start window tab drag CommandInactiveTitlebar3=Operations menu CommandTitlebarWheel=Switch to Window Tab to the Left/Right CommandWindow1=Activate, raise and pass click CommandWindow2=Activate and pass click CommandWindow3=Activate and pass click CommandWindowWheel=Scroll [Plugins] TIL3REnabled=false cubeslideEnabled=false desktopchangeosdEnabled=true dimscreenEnabled=true enforcedecoEnabled=true highlightwindowEnabled=true kwin-script-tilingEnabled=false kwin4_effect_fadedesktopEnabled=false magiclampEnabled=true minimizeallEnabled=false minimizeanimationEnabled=false showfpsEnabled=true slideEnabled=true synchronizeskipswitcherEnabled=false videowallEnabled=false windowgeometryEnabled=false [Script-desktopchangeosd] PopupHideDelay=300 TextOnly=false [SubSession: 2a86237b-ae5d-4ba2-908d-e293ec6b35a4] active=-1 count=0 [TabBox] ActivitiesMode=1 ApplicationsMode=0 BorderActivate=9 BorderAlternativeActivate=9 DesktopLayout=org.kde.breeze.desktop DesktopListLayout=org.kde.breeze.desktop DesktopMode=1 HighlightWindows=true LayoutName=org.kde.breeze.desktop MinimizedMode=0 MultiScreenMode=0 ShowDesktopMode=0 ShowTabBox=true SwitchingMode=0 [TabBoxAlternative] ActivitiesMode=1 ApplicationsMode=0 DesktopMode=1 HighlightWindows=true LayoutName=org.kde.breeze.desktop MinimizedMode=0 MultiScreenMode=0 ShowDesktopMode=0 ShowTabBox=true SwitchingMode=0 [Windows] ActiveMouseScreen=false AutoRaise=false AutoRaiseInterval=750 AutogroupInForeground=true AutogroupSimilarWindows=false BorderSnapZone=10 CenterSnapZone=0 ClickRaise=true DelayFocusInterval=300 ElectricBorderCooldown=350 ElectricBorderCornerRatio=0.25 ElectricBorderDelay=150 ElectricBorderMaximize=true ElectricBorderTiling=true ElectricBorders=0 FocusPolicy=ClickToFocus FocusStealingPreventionLevel=1 GeometryTip=false HideUtilityWindowsForInactive=true InactiveTabsSkipTaskbar=false MaximizeButtonLeftClickCommand=Maximize MaximizeButtonMiddleClickCommand=Maximize (vertical only) MaximizeButtonRightClickCommand=Maximize (horizontal only) NextFocusPrefersMouse=false Placement=Smart RollOverDesktops=true SeparateScreenFocus=false ShadeHover=false ShadeHoverInterval=250 SnapOnlyWhenOverlapping=false TitlebarDoubleClickCommand=Maximize WindowSnapZone=10 [org.kde.kdecoration2] BorderSize=Tiny ButtonsOnLeft=MSF ButtonsOnRight=IAX CloseOnDoubleClickOnMenu=false library=org.kde.breeze -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371215] Plasma Crashes when trying to end application with kquiapp5
https://bugs.kde.org/show_bug.cgi?id=371215 --- Comment #2 from Lucas Lima <lima.lucas...@gmail.com> --- Also noticed on ksysguard that a plasmashell process stays as 'stopped', and a new one is spawned. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371215] New: Plasma Crashes when trying to end application with kquiapp5
https://bugs.kde.org/show_bug.cgi?id=371215 Bug ID: 371215 Summary: Plasma Crashes when trying to end application with kquiapp5 Product: plasmashell Version: 5.8.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: lima.lucas...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.8.2) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.2-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Trying to quit the plasmashell with kquitapp5 resullted in a crash, and restarted the aplication. - Unusual behavior I noticed: The reason I wanted to quit plasmashell was incorrect wallpapper placing in my monitors. The restart of the plasmashell due to the crash (As the process detects the crash and restarts automatically) did not solve the issue. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9d8ada4800 (LWP 1951))] Thread 10 (Thread 0x7f9c8f75c700 (LWP 10235)): #0 0x7f9d84dece50 in () at /usr/lib/libQt5Core.so.5 #1 0x7f9d7f792c89 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f9d7f7936ab in () at /usr/lib/libglib-2.0.so.0 #3 0x7f9d7f79389c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f9d84ded72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f9d84d9723a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f9d84bba0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f9d84bbed78 in () at /usr/lib/libQt5Core.so.5 #8 0x7f9d83cce454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f9d844d47df in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f9c8abf5700 (LWP 10234)): #0 0x7f9d7f7d8dd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f9d7f792c7c in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f9d7f7936ab in () at /usr/lib/libglib-2.0.so.0 #3 0x7f9d7f79389c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f9d84ded72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f9d84d9723a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f9d84bba0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f9d84bbed78 in () at /usr/lib/libQt5Core.so.5 #8 0x7f9d83cce454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f9d844d47df in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f9c9ec2d700 (LWP 2414)): #0 0x7f9d844cb48d in poll () at /usr/lib/libc.so.6 #1 0x7f9d7f793786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f9d7f79389c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f9d84ded72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f9d84d9723a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f9d84bba0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f9ca92940a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7f9d84bbed78 in () at /usr/lib/libQt5Core.so.5 #8 0x7f9d83cce454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f9d844d47df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f9cd57f6700 (LWP 2333)): #0 0x7ffe967b8a8b in clock_gettime () #1 0x7f9d844e16b6 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f9d84c641a1 in () at /usr/lib/libQt5Core.so.5 #3 0x7f9d84deb3a9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f9d84decc55 in () at /usr/lib/libQt5Core.so.5 #5 0x7f9d7f793179 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #6 0x7f9d7f793724 in () at /usr/lib/libglib-2.0.so.0 #7 0x7f9d7f79389c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #8 0x7f9d84ded72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #9 0x7f9d84d9723a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #10 0x7f9d84bba0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #11 0x7f9d88abc856 in () at /usr/lib/libQt5Quick.so.5 #12 0x7f9d84bbed78 in () at /usr/lib/libQt5Core.so.5 #13 0x7f9d83cce454 in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f9d844d47df in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f9d5b367700 (LWP 2323)): #0 0x7f9d83cd410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9d8a54cac4 in () at
