[kwin] [Bug 488860] New: Massive frame drops with intel iris xe graphics
https://bugs.kde.org/show_bug.cgi?id=488860 Bug ID: 488860 Summary: Massive frame drops with intel iris xe graphics Classification: Plasma Product: kwin Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: performance Assignee: kwin-bugs-n...@kde.org Reporter: moyamat...@crodity.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I have an i5-1235U with onboard Intel Iris Xe graphics. With the latest update to plasma 6.1, there have been massive frame drops (into the 30ish fps) and reduced performance in graphics situations in general. Most of the time the frame rate does stay at 60, but the drops are frequent, about every 15-20 seconds. I am sorry I cannot attach the fps graph since I cannot capture the show fps applet in video. This only used to happen in the x11 session but now it also occurs in the wayland session. I think this has something to do with triple buffering but I am not really sure. STEPS TO REPRODUCE 1. Have Intel Iris Xe graphics 2. Enable the show fps option in kwin 3. See the Current FPS OBSERVED RESULT There should be no frame drops. EXPECTED RESULT Frame drops every 15-20 seconds. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488860] Massive frame drops with intel iris xe graphics
https://bugs.kde.org/show_bug.cgi?id=488860 --- Comment #1 from Yujiro Hanma --- This also spams my journal log, which I think confirms my suspicion that this is related to triple buffering. ``kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)`` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488860] Massive frame drops with intel iris xe graphics
https://bugs.kde.org/show_bug.cgi?id=488860 --- Comment #3 from Yujiro Hanma --- (In reply to Vlad Zahorodnii from comment #2) > The show fps effect is not a proper profiling tool and it can report > sometimes lower refresh rates if the screen is not being repainted actively. > Regarding GL_INVALID_OPERATION, it's a Qt issue. I do not mean to invalidate your point, but it does show lower fps and I can actually feel it as my cursor lags and the animations slow down. Could you please tell me how I can properly give the refresh rate statistics? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488860] Massive frame drops with intel iris xe graphics
https://bugs.kde.org/show_bug.cgi?id=488860 --- Comment #5 from Yujiro Hanma --- (In reply to Vlad Zahorodnii from comment #4) > Is there a lag with KWIN_DRM_DISABLE_TRIPLE_BUFFERING=1 envvar set? I have been using my computer, opening various programs and graphically demanding games, but fps never goes below 55-56 ( and that's only on opening overview ), the weird stuttering I felt in games is also gone. And the desktop and cursor feel much smoother than before. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488860] Massive frame drops with intel iris xe graphics
https://bugs.kde.org/show_bug.cgi?id=488860 --- Comment #6 from Yujiro Hanma --- I should also add that disabling triple buffering also fixed frame time spikes and general stutters in games. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488892] New: Dolphin does not snap when dragged elsewhere once snapped to half of the screen
https://bugs.kde.org/show_bug.cgi?id=488892 Bug ID: 488892 Summary: Dolphin does not snap when dragged elsewhere once snapped to half of the screen Classification: Applications Product: dolphin Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: moyamat...@crodity.com CC: kfm-de...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When opening dolphin maximized, if you snap dolphin to the side and then drag that window and once again try to snap to maximize, it does not do anything. This bug also occurs with kate and gwenview. STEPS TO REPRODUCE 1. Open Dolphin maximized 2. Snap it to the side 3. Try to drag the window and snap to maximize OBSERVED RESULT Nothing happens EXPECTED RESULT Window should maximize SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488892] Dolphin does not snap when dragged elsewhere once snapped to half of the screen
https://bugs.kde.org/show_bug.cgi?id=488892 --- Comment #1 from Yujiro Hanma --- Update: The bug also occurs even when the window is not started as maximized. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488892] Dolphin does not snap when dragged elsewhere once snapped to half of the screen
https://bugs.kde.org/show_bug.cgi?id=488892 --- Comment #2 from Yujiro Hanma --- Created attachment 170752 --> https://bugs.kde.org/attachment.cgi?id=170752&action=edit video depicting the bug -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488896] New: Huge frame drops when recording with spectacle
https://bugs.kde.org/show_bug.cgi?id=488896 Bug ID: 488896 Summary: Huge frame drops when recording with spectacle Classification: Applications Product: Spectacle Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: moyamat...@crodity.com CC: k...@david-redondo.de Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When recording a video with spectacle on my intel i5-1235U laptop with onboard Intel Iris Xe graphics, there are huge frame drops and progressively more and more frames are dropped. STEPS TO REPRODUCE 1. Record a video with spectacle OBSERVED RESULT There are high number of dropped frames EXPECTED RESULT There should be no dropped frames. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Looking at the logs, it seems like spectacle is using vaapi for encoding the video, and the journal is spammed with these messages: kpipewire_vaapi_logging: VAAPI: entrypoint 8 of profile 14 is not supported by the device "/dev/dri/renderD128" kpipewire_vaapi_logging: VAAPI: entrypoint 6 of profile 14 is not supported by the device "/dev/dri/renderD128" kpipewire_record_logging: Filter queue is full, dropping frame 2484... (hundreds of messages of dropping frames) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488896] Huge frame drops when recording with spectacle
https://bugs.kde.org/show_bug.cgi?id=488896 --- Comment #1 from Yujiro Hanma --- I forgot to add this, but I am using the WebM/VP9 codec for encoding. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488896] Huge frame drops when recording with spectacle
https://bugs.kde.org/show_bug.cgi?id=488896 --- Comment #4 from Yujiro Hanma --- (In reply to Noah Davis from comment #3) > What it means is that for some reason, the system cannot encode fast enough > to keep the frames from piling up in memory. When frames start piling up > without being dropped, you may quickly run out of memory and have your whole > system freeze. The reason why this happens could simply be that your > computer is too slow or has too many other things competing for system > resources. I don't think this is the reason. I tested it on a fresh boot and the same thing occurred. Also it used to work perfectly before. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488896] Huge frame drops when recording with spectacle
https://bugs.kde.org/show_bug.cgi?id=488896 --- Comment #7 from Yujiro Hanma --- (In reply to Noah Davis from comment #6) > It is possible for there to be a bug. As you said, this probably is an > upstream issue since Spectacle does not do the frame dropping itself. The > issue is probably in KWin, KPipeWire or in something that either of those > rely on. I did some more testing, and it seems only the libvpx and libvpx-vp9 encoders face this issue. libx264, h264_vaapi and their baseline profiles seem to work fine. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488896] Huge frame drops when recording with spectacle
https://bugs.kde.org/show_bug.cgi?id=488896 --- Comment #8 from Yujiro Hanma --- I think we should perhaps move this to kpipewire, this does not seem like a bug of spectacle. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 489303] kded6 suddenly showing this window after login into my account after updating to Plasma 6.1.1
https://bugs.kde.org/show_bug.cgi?id=489303 Yujiro Hanma changed: What|Removed |Added CC||moyamat...@crodity.com --- Comment #1 from Yujiro Hanma --- Similar situation here. After upgrading to 6.1.1 kdewallet for some reason is not unlocking itself automatically even when login password and wallet password match. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 489303] kded6 suddenly showing this window after login into my account after updating to Plasma 6.1.1
https://bugs.kde.org/show_bug.cgi?id=489303 --- Comment #3 from Yujiro Hanma --- Downgrading kwallet-pam to 6.1.0-1 temporarily resolves the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 489303] kded6 suddenly showing this window after login into my account after updating to Plasma 6.1.1
https://bugs.kde.org/show_bug.cgi?id=489303 --- Comment #4 from Yujiro Hanma --- kwallet 6.1.1-2 has been pushed which fixes this issue -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 488896] Huge frame drops when recording with spectacle
https://bugs.kde.org/show_bug.cgi?id=488896 Yujiro Hanma changed: What|Removed |Added CC||aleix...@kde.org Assignee|noaha...@gmail.com |plasma-b...@kde.org Version|24.05.1 |unspecified Product|Spectacle |KPipeWire Component|General |general -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 488896] Huge frame drops when recording with spectacle
https://bugs.kde.org/show_bug.cgi?id=488896 Yujiro Hanma changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 489434] New: Spectacle crashes on finishing recording with pipewire 1.2.0
https://bugs.kde.org/show_bug.cgi?id=489434 Bug ID: 489434 Summary: Spectacle crashes on finishing recording with pipewire 1.2.0 Classification: Applications Product: Spectacle Version: 24.05.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: moyamat...@crodity.com CC: k...@david-redondo.de Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY With pipewire 1.2.0, spectacle crashes on trying to save a video file. STEPS TO REPRODUCE 1. Record your screen 2. Try to finish the recording OBSERVED RESULT Spectacle stops responding and does not finish the recording. EXPECTED RESULT It should finish the recording. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION This is not related to the bug https://bugs.kde.org/show_bug.cgi?id=488896 which causes kpipewire to keep dropping frames on encoding with webm/vp9, since it would work when you switched the encoder to libx264. -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 488896] Huge frame drops when recording with spectacle
https://bugs.kde.org/show_bug.cgi?id=488896 --- Comment #10 from Yujiro Hanma --- I can confirm the issue still persists with pipewire 1.2.0 -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 488896] Huge frame drops when recording with spectacle
https://bugs.kde.org/show_bug.cgi?id=488896 --- Comment #11 from Yujiro Hanma --- I do not know if this is relevant, but kpipewire always seems to drop frames starting around the 3200th frame number. It also drops every 16th or 17th frame. For example look at this ideapad spectacle[3957]: kpipewire_record_logging: Filter queue is full, dropping frame 6633 ideapad spectacle[3957]: kpipewire_record_logging: Filter queue is full, dropping frame 6650 ideapad spectacle[3957]: kpipewire_record_logging: Filter queue is full, dropping frame ideapad spectacle[3957]: kpipewire_record_logging: Filter queue is full, dropping frame 6683 ideapad spectacle[3957]: kpipewire_record_logging: Filter queue is full, dropping frame 6700 Also please note that this only happens on webm/vp9 codec. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 493863] New: plasma-nm shows connected to many "ghost" networks
https://bugs.kde.org/show_bug.cgi?id=493863 Bug ID: 493863 Summary: plasma-nm shows connected to many "ghost" networks Classification: Plasma Product: plasma-nm Version: 6.1.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: moyamat...@crodity.com Target Milestone: --- Created attachment 174221 --> https://bugs.kde.org/attachment.cgi?id=174221&action=edit Multiple ghost disconnects *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY plasma-nm applet shows connected to ghost networks, clicking disconnect on them do anything. STEPS TO REPRODUCE 1. Click on the plasma-nm applet on the panel OBSERVED RESULT Shows redundant disconnect buttons EXPECTED RESULT They should not be there. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.3 ADDITIONAL INFORMATION I personally think this is because of Arch's update from qt6 from 6.7.2-2 to 6.7.3-1. I have been seeing this issue since the last two days. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480412] "Remote control requested" dialog from KDE Connect doesn't show source of the request when kdeconnect was started via DBus
https://bugs.kde.org/show_bug.cgi?id=480412 Yujiro Hanma changed: What|Removed |Added CC||moyamat...@crodity.com --- Comment #9 from Yujiro Hanma --- I should add that I have another weird consequence of xdg-desktop-portal-kde misbehaving with vmware-workstation, it seems to permanently enable the control key when remote access is enabled to a windows 10 vm. like anything I do on the host the ctrl key is always pressed. If I go to a terminal and press d it immediately closes itself, like I pressed ctrl+d. -- You are receiving this mail because: You are watching all bug changes.
