https://bugs.kde.org/show_bug.cgi?id=501073
Alexandre ZANNI <alexandre.za...@europe.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexandre.za...@europe.com
--- Comment #35 from Alexandre ZANNI <alexandre.za...@europe.com> ---
Some interesting behavior I'd like to share.
Like mentioned by others earlier, my system video signal was freezing as soon
as I started to play a video (not just firefox and youtube, but also vivaldi
and any website). So I tried to launch a local video with different players.
Freezing also occurred with SMPlayer and VLC but interestingly not with mpv.
There must be something to dig on that path (common library, similar system
call, etc.) that triggers the bug with most web browser integrated video
players and dedicated video players that mpv is not using. What's even more
surprising, is that my SMPlayer is configured to used system mpv as video
backend.
It's not just the first time the video is launched that the bug is happening
but also frequently while the video is still playing.
systemctl --user restart plasma-powerdevil workaround prevents freeze from
happening.
I'm not sure that "kwin_wayland[1000]: kwin_wayland_drm: The main thread was
hanging temporarily!" error is related to the cause of the issue but rather is
a consequence. Because I don't see this error happening at each freeze.
When I was playing a video in Vivaldi, for example, I also saw this error,
which seems related to the powerdevil workaround:
avril 10 20:17:34 archpowa vivaldi-stable[2414]:
[2410:2435:0410/201734.673470:ERROR:object_proxy.cc(576)] Failed to call
method: org.freedesktop.PowerManagement.Inhibit.Inhibit: object_path=
/org/freedesktop/Powe
rManagement/Inhibit: org.freedesktop.DBus.Error.NoReply: Did not receive a
reply. Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.
It doesn't seems to be related to a computer having been running for a long
time because it arrived to me soon after booting up.
This should not be related to a specific kernel version because it's happening
on a kernel I haven't updated for months and the bug was not present before. So
it suggests it must rather be related to a library that was recently updated.
Operating System: Arch Linux
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.6.77-1-lts66 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 1600X Six-Core Processor
Memory: 31.3 Gio of RAM
Graphics Processor: AMD Radeon RX 480 Graphics
Motherboard Name: AB350 Pro4
--
You are receiving this mail because:
You are watching all bug changes.
