[krfb] [Bug 413476] Wayland/Pipewire segfault on connection

2025-07-24 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=413476 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINF

[krfb] [Bug 413476] Wayland/Pipewire segfault on connection

2025-07-09 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=413476 --- Comment #4 from Bug Janitor Service --- ๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it wi

[krfb] [Bug 413476] Wayland/Pipewire segfault on connection

2025-06-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=413476 postix changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC|

[krfb] [Bug 413476] Wayland/Pipewire segfault on connection

2022-03-04 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=413476 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail

[krfb] [Bug 413476] Wayland/Pipewire segfault on connection

2020-01-26 Thread Tom B
https://bugs.kde.org/show_bug.cgi?id=413476 --- Comment #2 from Tom B --- what is the best way to get a backtrace? Trying it again a few months later with the most recent versions of each package, I am still getting the same problem. dmesg shows the following: [315423.305190] krfb[2750682]: se

[krfb] [Bug 413476] Wayland/Pipewire segfault on connection

2019-12-16 Thread Alexey Min
https://bugs.kde.org/show_bug.cgi?id=413476 Alexey Min changed: What|Removed |Added CC||alexey@gmail.com --- Comment #1 from Alexey Mi