On Mon, Jul 28, 2025 at 09:03:30AM +0500, Alex Volkov wrote:
Package: pulseview
Version: 0.4.2-3+b1
Severity: normal
Dear Maintainer,
an attempt to lauch pulseview in KDE with QtCurve application style in use leads to a segfault
with the followinfg diagnostic in dmesg:
[83596.494848] pulseview[16636]: segfault at 29aa1440317a ip 00007f6870429080 sp 00007ffdf8c72310 error 4 in qtcurve.so[1d080,7f687041d000+62000] likely on CPU 0 (core 0, socket 0)
[83596.494853] Code: 58 01 00 00 4c 89 e7 e8 9e 47 ff ff 48 8b 44 24 40 8b 10 83 fa 01 0f 87 ae 03 00 00 48 8b 44 24 40 48 63 50 08 4c 8b 74 d0 10 <41> 8b 06 83 c0 01 83 f8 01 0f 87 a1 03 00 00 4c 89 e7 e8 09 25 01
As a workaround, launching it by the command `XDG_CURRENT_DESKTOP=Gnome pulseview` (with
the environment variable) works. Also, launching it from a ssh session (where X-related
variables has never been set) by `DISPLAY=:0 pulseview` works too.
Is this a pulseview issue, or a QtCurve issue? It's not clear to me that pulseview is paying any attention to the desktop type, rather than it
being one of the underlying libraries.
J.
--
101 things you can't have too much of : 40 - Star Wars toys.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)