FS#58863 - [qmmp] terminated by signal SIGSEGV (Address boundary error)
Attached to Project:
Community Packages
Opened by Juan Simón (j1simon) - Monday, 04 June 2018, 12:16 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Sunday, 05 August 2018, 19:01 GMT
Opened by Juan Simón (j1simon) - Monday, 04 June 2018, 12:16 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Sunday, 05 August 2018, 19:01 GMT
|
Details
Description:
I have tested qmmp v1.2.1 (in official repositories) and qmmp v1.2.2 (with Arch oficial PKGBUILD modified) GNOME Shell 3.28.2 on Wayland When I execute this application it shows an error: "'qmmp' terminated by signal SIGSEGV (Address boundary error)" When I execute it with gdb: Starting program: /usr/bin/qmmp [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". QMMPStarter: removed invalid socket file QmmpPluginCache: loaded plugin libpulseaudio.so QmmpUiPluginCache: loaded plugin libfileops.so QmmpUiPluginCache: loaded plugin libgnomehotkey.so [New Thread 0x7fffea10d700 (LWP 11769)] MediaKeys: gnome settings daemon is not running QmmpUiPluginCache: loaded plugin libmpris.so QmmpUiPluginCache: loaded plugin libskinned.so Thread 1 "qmmp" received signal SIGSEGV, Segmentation fault. 0x00007fffe942cae5 in ?? () from /usr/lib/qmmp/Ui/libskinned.so With both versions the error is the same. |
This task depends upon
Closed by Jaroslav Lichtblau (Dragonlord)
Sunday, 05 August 2018, 19:01 GMT
Reason for closing: Upstream
Sunday, 05 August 2018, 19:01 GMT
Reason for closing: Upstream
Comment by David Roth (V1del) -
Thursday, 07 June 2018, 11:28 GMT
Comment by Juan Simón (j1simon) -
Thursday, 07 June 2018, 11:36 GMT
Comment by Juan Simón (j1simon) -
Monday, 11 June 2018, 07:51 GMT
Comment by Juan Simón (j1simon) -
Monday, 11 June 2018, 07:53 GMT
Likely an issue with Wayland and X specific UI functionality, does
it work if you start it with QT_QPA_PLATFORM=xcb qmmp ?
Yes, it is a issue with Wayland. With 'QT_QPA_PLATFORM=xcb qmmp'
it works.
I've tried to report this error to qmmp bug tracker
(https://sourceforge.net/p/qmmp-dev/tickets/) but only authorized
users can report errors.
Stack trace with more details.