[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 Juan Méndez changed: What|Removed |Added Version|23.08.5 |24.02.0 Platform|Manjaro |unspecified --- Comment #15 from Juan Méndez --- Yeah, I can confirm this is a problem as of the latest Plasma (6.0.1). I don't think krfb was ever touched in the Qt migration, so I guess it's okay to assume krfb is still broken. On Plasma 6.x krfb even manages to crash the desktop bringing everything down (except for Qt apps) with it. --- krfb --version krfb 24.02.0 plasma-desktop 6.0.1-1 -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 --- Comment #2 from Juan Méndez --- Forgot to mention this is happening under KDE Wayland. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 --- Comment #1 from Juan Méndez --- gdb backtrace: kpipewire_dmabuf_logging: eglChooseConfig returned this many configs: 1 [New Thread 0x7fff937fe6c0 (LWP 4568)] [New Thread 0x7fff92ffd6c0 (LWP 4569)] kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" Thread 1 "krfb-virtualmon" received signal SIGSEGV, Segmentation fault. __memcpy_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:706 706 VMOVU %VMM(0), (%rdi) (gdb) backtrace #0 __memcpy_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:706 #1 0x7fff7fea6255 in memcpy (__len=8294400, __src=, __dest=) at /usr/include/bits/string_fortified.h:29 #2 PWFrameBuffer::Private::handleFrame (frame=..., this=0x5583fde0) at /usr/src/debug/krfb/krfb-23.04.2/framebuffers/pipewire/pw_framebuffer.cpp:392 #3 operator() (frame=..., __closure=) at /usr/src/debug/krfb/krfb-23.04.2/framebuffers/pipewire/pw_framebuffer.cpp:156 #4 QtPrivate::FunctorCall, QtPrivate::List, void, PWFrameBuffer::Private::Private(PWFrameBuffer*):: >::call (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146 #5 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256 #6 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443 #7 0x76be9fe7 in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x5597b4e0, signal_index=7, argv=0x7fffd760) at kernel/qobject.cpp:3923 #9 0x7fff7fa466aa in PipeWireSourceStream::frameReceived (this=this@entry=0x5597b4e0, _t1=...) at /usr/src/debug/kpipewire/build/src/KPipeWire_autogen/EWIEGA46WW/moc_pipewiresourcestream.cpp:219 #10 0x7fff7fa521fe in PipeWireSourceStream::handleFrame (this=this@entry=0x5597b4e0, buffer=buffer@entry=0x55c2f0a8) at /usr/src/debug/kpipewire/kpipewire-5.27.5/src/pipewiresourcestream.cpp:533 #11 0x7fff7fa52b4d in PipeWireSourceStream::process (this=0x5597b4e0) at /usr/src/debug/kpipewire/kpipewire-5.27.5/src/pipewiresourcestream.cpp:551 #12 0x7fff7f8a4108 in do_call_process (loop=, async=, seq=, data=, size=, user_data=0x55c2ec90) at ../pipewire/src/pipewire/stream.c:420 #13 0x7fff7f8148e1 in flush_items (impl=0x55c11138) at ../pipewire/spa/plugins/support/loop.c:171 #14 0x7fff7f813a09 in source_event_func (source=0x555b08e0) at ../pipewire/spa/plugins/support/loop.c:650 #15 0x7fff7f8155b6 in loop_iterate (object=0x55c11138, timeout=) at ../pipewire/spa/plugins/support/loop.c:483 #16 0x7fff7fa485d0 in operator() (__closure=) at /usr/src/debug/kpipewire/kpipewire-5.27.5/src/pipewirecore.cpp:78 #17 QtPrivate::FunctorCall, QtPrivate::List<>, void, PipeWireCore::init(int):: >::call (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146 #18 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256 #19 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443 #20 0x76be9fe7 in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate (sender=0x5558aba0, signal_index=3, argv=0x7fffde00) at kernel/qobject.cpp:3923 #22 0x76beb7e4 in QSocketNotifier::activated (this=this@entry=0x5558aba0, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #23 0x76beb928 in QSocketNotifier::event (this=0x5558aba0, e=) at kernel/qsocketnotifier.cpp:302 #24 0x776ae93f in QApplicationPrivate::notify_helper (this=, receiver=0x5558aba0, e=0x7fffdf20) at kernel/qapplication.cpp:3640 #25 0x76bb4b18 in QCoreApplication::notifyInternal2
[krfb] [Bug 470996] New: krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 Bug ID: 470996 Summary: krfb-virtualmonitor 23.x crashes Classification: Applications Product: krfb Version: 23.04.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: vps...@gmail.com Target Milestone: --- SUMMARY krfb-virtualmonitor simply crashes when trying to use it STEPS TO REPRODUCE 1. Try to use krfb-virtualmonitor 23.x OBSERVED RESULT krfb-virtualmonitor segfaults for no apparent reason EXPECTED RESULT - the program shouldn't segfault - downgrading to krfb-virtualmonitor 22.x solves the issue (specifically, this version works just fine: https://archive.archlinux.org/packages/k/krfb/krfb-22.12.3-1-x86_64.pkg.tar.zst) SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.5-1 KDE Frameworks Version: 5.107.0-1 Qt Version: 5.15.9 (latest as of today) ADDITIONAL INFORMATION - CPU: 12th Gen Intel(R) Core(TM) i7-1280P (20) @ 4.7 GHz GPU: Intel Alder Lake-P Integrated Graphics Controller - krfb-virtualmonitor also crashes even after deleting the default config file in ~/.config - Some logs: QT_LOGGING_RULES="krfb.krfb=true" krfb-virtualmonitor --name test --resolution 2400x1080 --password test --port 5900 krfb.krfb: Loaded plugin with name "pw" krfb.krfb: Using FrameBuffer: "pw" krfb.krfb: Starting server. Listen port: 5900 Listen Address: "0.0.0.0" Password enabled: true 13/06/2023 04:55:26 PM Listening for VNC connections on TCP port 5900 13/06/2023 04:55:26 PM Listening for VNC connections on TCP6 port 5900 kpipewire_dmabuf_logging: eglChooseConfig returned this many configs: 1 kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" Segmentation fault -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456300] Screen sharing broken when using non-standard screen resolutions
https://bugs.kde.org/show_bug.cgi?id=456300 --- Comment #6 from Juan Méndez --- (In reply to Aleix Pol from comment #4) > Seems to be a bug in webrtc that recently , which is shared by both firefox > and chromium: https://webrtc-review.googlesource.com/c/src/+/265384 > > Can you test if you also have this problem with OBS? (In reply to Aleix Pol from comment #4) > Seems to be a bug in webrtc that recently , which is shared by both firefox > and chromium: https://webrtc-review.googlesource.com/c/src/+/265384 > > Can you test if you also have this problem with OBS? I just tested with OBS and everything works just fine (yay!). However, this bug is kinda weird because I was unable to replicate the same issue on GNOME (with all the latest updates as of yesterday). All these bug reports seem to indicate this issue only happens on KDE, though there's one comment about someone using NixOS + GNOME having the same issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456300] Screen sharing broken when using non-standard screen resolutions
https://bugs.kde.org/show_bug.cgi?id=456300 --- Comment #3 from Juan Méndez --- A couple of things worth noting: 1. None of what I mentioned above of below happens on Xorg (lol) 2. Firefox does seem to be broken as well, but not as badly as Chromium. This might deserve a bug report on its own, but here's a TL;DR of what happens when I try to test screen sharing using https://mozilla.github.io/webrtc-landing/gum_test.html : - The portal dialog shows up as usual asking me to pick a screen - I can see my screen in the miniature preview, but the preview remains frozen shortly after clicking the OK button in the portal dialog - Clicking the Pause/Play button will unfreeze the preview and things will work as expected - CPU usage goes br, with Firefox using about 60% of a CPU core and kwin_wayland using an entire CPU core. This doesn't happen with Chromium - My display's refresh rate drops to ~24 FPS with Firefox (it's a 75Hz display). I tried lowering the resolution but I still see a massive FPS drop on Wayland. This doesn't happen on Chromium, though - None of this happens on Xorg as well. CPU usage remains consistently low (no more than 20% core usage on both Chromium and FF), and no FPS drops either. 3. This also happens when using either DP or HDMI. Please let me know which logs you need, and/or the instructions to get you all the info needed to sort this out. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456300] Screen sharing broken when using non-standard screen resolutions
https://bugs.kde.org/show_bug.cgi?id=456300 --- Comment #2 from Juan Méndez --- Created attachment 150377 --> https://bugs.kde.org/attachment.cgi?id=150377&action=edit smaller resolution, everything works just fine -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456300] Screen sharing broken when using non-standard screen resolutions
https://bugs.kde.org/show_bug.cgi?id=456300 --- Comment #1 from Juan Méndez --- Created attachment 150376 --> https://bugs.kde.org/attachment.cgi?id=150376&action=edit native resolution, no VAAPI/hw accel hacks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456300] New: Screen sharing broken when using non-standard screen resolutions
https://bugs.kde.org/show_bug.cgi?id=456300 Bug ID: 456300 Summary: Screen sharing broken when using non-standard screen resolutions Product: kwin Version: 5.25.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: vps...@gmail.com Target Milestone: --- Created attachment 150375 --> https://bugs.kde.org/attachment.cgi?id=150375&action=edit native resolution SUMMARY When using a screen with an arguably _non-standard_ (or should I say _not-so-common_) resolution, screen sharing is pretty much broken on Chromium-based browsers. The "recording stream" looks glitchy and borked, for some reason. This didn't happen in Plasma 5.24.x, though. Please see pictures attached. Strangely enough, things work great on Firefox and OBS, but this wasn't broken in Plasma 5.24. Things also work if I scale back to a rather more common resolution, i.e. 2560x1080, 1920x1080, etc. In fact, I'm only able to reproduce the bug using my monitor's native resolution (3440x1440). STEPS TO REPRODUCE 1. Use any website that allows you to record your screen (zoom, jitsi, screenapp.io, etc). OBSERVED RESULT The captured stream looks glitchy, with lots of artifacts. Almost as if the computer were having GPU issues. EXPECTED RESULT No glitches or screen artifacts in the recorded stream. SOFTWARE/OS VERSIONS Linux Version: 5.15.2 Note: This doesn't seem to be a kernel issue, since I am able to reproduce the same behavior in kernel versions 5.15.x - 5.18.x. --- KDE Plasma Version: 5.25.2-1 --- KDE Frameworks Version: 5.95.0-2 --- Qt Version: 5.15.5+kde+r166-1 ADDITIONAL INFORMATION - I'm using my laptop's integrated graphics (Intel 8th gen U-series CPU). It has no issue driving the 2k screen - I'm pretty sure this is not a driver/mesa issue since I was unable to reproduce the same issue on GNOME 42 + same chromium release - I tried using older chromium releases (pre 103.x) to no avail - I did enable pipewire support in chrome://flags - I'm able to reproduce the same behavior using Flathub's Chromium, Brave, Arch's Chromium and ungoogled-chromium as well - I tried forcing Chromium's VAAPI support to see if it was a hardware-accel related issue, but that doesn't seem to be the case. - It looks like Chromium fails to call GetVSyncParametersIfAvailable() but ONLY when I use my display's native resolution. No such thing happens when I use smaller display resolutions. Maybe kwin is failing to provide some necessary info? -- You are receiving this mail because: You are watching all bug changes.
