PMP crash on fedora35 with gnome and wayland
hfdem opened this issue · 3 comments
~ gdb plexmediaplayer
Reading symbols from plexmediaplayer...
Reading symbols from /usr/lib/debug/usr/bin/plexmediaplayer-2.58.1-3.fc35.x86_64.debug...
(gdb) r
Starting program: /usr/bin/plexmediaplayer
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffd2a8b640 (LWP 15965)]
[New Thread 0x7fffd228a640 (LWP 15966)]
[New Thread 0x7fffd1a89640 (LWP 15967)]
[New Thread 0x7fffd1288640 (LWP 15968)]
[New Thread 0x7fffd0a87640 (LWP 15969)]
[Thread 0x7fffd0a87640 (LWP 15969) exited]
[Thread 0x7fffd1288640 (LWP 15968) exited]
[Thread 0x7fffd1a89640 (LWP 15967) exited]
[Thread 0x7fffd228a640 (LWP 15966) exited]
[Thread 0x7fffd2a8b640 (LWP 15965) exited]
[New Thread 0x7fffd2a8b640 (LWP 15970)]
QSocketNotifier: Can only be used with threads started with QThread
[New Thread 0x7fffd1a89640 (LWP 15972)]
[New Thread 0x7fffd228a640 (LWP 15973)]
[New Thread 0x7fffd1288640 (LWP 15977)]
[New Thread 0x7fffbbae0640 (LWP 15978)]
libpng warning: iCCP: known incorrect sRGB profile
[New Thread 0x7fffbad94640 (LWP 15979)]
[New Thread 0x7fffba593640 (LWP 15980)]
[New Thread 0x7fffb9d92640 (LWP 15981)]
[New Thread 0x7fffb9591640 (LWP 15982)]
[New Thread 0x7fffb8d90640 (LWP 15983)]
[New Thread 0x7fffa3fff640 (LWP 15984)]
[New Thread 0x7fffa37fe640 (LWP 15985)]
[New Thread 0x7fff9bfff640 (LWP 15986)]
[New Thread 0x7fffa2ffd640 (LWP 15987)]
[New Thread 0x7fffa27fc640 (LWP 15988)]
[Thread 0x7fffa27fc640 (LWP 15988) exited]
[Thread 0x7fff9bfff640 (LWP 15986) exited]
[Thread 0x7fffa2ffd640 (LWP 15987) exited]
[Thread 0x7fffa37fe640 (LWP 15985) exited]
[Thread 0x7fffa3fff640 (LWP 15984) exited]
[New Thread 0x7fffa2ffd640 (LWP 15989)]
[New Thread 0x7fffa3fff640 (LWP 15990)]
[New Thread 0x7fff9bfff640 (LWP 15991)]
[New Thread 0x7fffa37fe640 (LWP 15992)]
[New Thread 0x7fffa27fc640 (LWP 15993)]
[New Thread 0x7fffa1ffb640 (LWP 15994)]
[New Thread 0x7fffa17fa640 (LWP 15995)]
[New Thread 0x7fffa0ff9640 (LWP 15996)]
[New Thread 0x7fff9b7fe640 (LWP 15997)]
[New Thread 0x7fff9affd640 (LWP 15998)]
[Thread 0x7fff9b7fe640 (LWP 15997) exited]
[New Thread 0x7fff9b7fe640 (LWP 15999)]
[New Thread 0x7fff98c7c640 (LWP 16000)]
[New Thread 0x7fff61f9f640 (LWP 16001)]
[New Thread 0x7fff69f9f640 (LWP 16002)]
[New Thread 0x7fff6979e640 (LWP 16003)]
[New Thread 0x7fff68f9d640 (LWP 16004)]
[New Thread 0x7fff63fff640 (LWP 16005)]
[New Thread 0x7fff637fe640 (LWP 16006)]
[New Thread 0x7fff62ffd640 (LWP 16007)]
[New Thread 0x7fff627fc640 (LWP 16008)]
[New Thread 0x7fff6179e640 (LWP 16009)]
[New Thread 0x7fff60f9d640 (LWP 16010)]
[New Thread 0x7fff3bfff640 (LWP 16011)]
[New Thread 0x7fff3b7fe640 (LWP 16012)]
[New Thread 0x7fff3affd640 (LWP 16013)]
[New Thread 0x7fff3a7fc640 (LWP 16014)]
[New Thread 0x7fff39ffb640 (LWP 16015)]
[New Thread 0x7fff397fa640 (LWP 16016)]
[New Thread 0x7fff38ff9640 (LWP 16017)]
[New Thread 0x7fff1bfff640 (LWP 16018)]
[New Thread 0x7fff1b7fe640 (LWP 16019)]
[New Thread 0x7fff1affd640 (LWP 16020)]
[New Thread 0x7fff1a7fc640 (LWP 16021)]
[New Thread 0x7fff19ffb640 (LWP 16022)]
[Thread 0x7fff19ffb640 (LWP 16022) exited]
[New Thread 0x7fff19ffb640 (LWP 16023)]
[Detaching after fork from child process 16024]
[Detaching after fork from child process 16025]
[Detaching after fork from child process 16026]
[New Thread 0x7fff197fa640 (LWP 16029)]
[New Thread 0x7fff18ff9640 (LWP 16030)]
[New Thread 0x7ffef7fff640 (LWP 16031)]
[New Thread 0x7ffef77fe640 (LWP 16032)]
[New Thread 0x7ffef6ffd640 (LWP 16033)]
[New Thread 0x7ffef67fc640 (LWP 16034)]
[New Thread 0x7ffef57fa640 (LWP 16035)]
[New Thread 0x7ffef5ffb640 (LWP 16036)]
[New Thread 0x7ffef4ff9640 (LWP 16037)]
[New Thread 0x7ffedbfff640 (LWP 16038)]
[New Thread 0x7ffedb7fe640 (LWP 16039)]
[New Thread 0x7ffedaffd640 (LWP 16040)]
[Detaching after fork from child process 16041]
[New Thread 0x7ffeda7fc640 (LWP 16043)]
[New Thread 0x7ffed9ffb640 (LWP 16047)]
[New Thread 0x7ffed97fa640 (LWP 16050)]
[New Thread 0x7ffed8ff9640 (LWP 16062)]
Thread 71 "QSGRenderThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffed97fa640 (LWP 16050)]
0x00007ffff7159ba3 in XQueryExtension (dpy=0x55555578b550, name=0x7ffff2646000 <va_dri2ExtensionName> "DRI2", major_opcode=0x7ffed97f8804, first_event=0x7ffed97f8808, first_error=0x7ffed97f880c) at /usr/src/debug/libX11-1.7.3.1-1.fc35.x86_64/src/QuExt.c:48
48 LockDisplay(dpy);
I have the same exact crash when trying to launch PMP on KDE on Wayland. If I launch using KDE on X11, I do not have the issue.
PMP does not work with Wayland. It may be possible to make it work by building against a newer Qt. It's is likely better to switch to X11 because Wayland obliterates some useful features in a playback application (like refresh rate matching).
PMP does not work with Wayland. It may be possible to make it work by building against a newer Qt. It's is likely better to switch to X11 because Wayland obliterates some useful features in a playback application (like refresh rate matching).
I understand that this is now probably a "resolved wontfix" situation, but I really think discarding Wayland wholesale is the wrong approach, especially since X11 is slowly being phased out. It would be nice if the app could run without crashing under XWayland in the meantime.
Wayland is by no means perfect at this point but it is a constantly maturing technology, and having this stance will become increasingly difficult as distros such as as Ubuntu move to making Wayland the default.
If Wayland support is off the table, making the app work with XWayland is much better than having a segfault-on-launch default situation.