https://bugs.kde.org/show_bug.cgi?id=365242

--- Comment #4 from Fabian Vogt <fab...@ritter-vogt.de> ---
(In reply to Martin Gräßlin from comment #3)
> Possible patch for the crash: https://phabricator.kde.org/D2135 - untested
> as I don't have a VM setup for it (need to fix that).

Looks like it's working: FATAL ERROR: backend failed to initialize, exiting now

However, it crashes with a segfault after that, in a global destructor:

Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault.            
0x00007ffff5e815a3 in QSocketNotifier::setEnabled(bool) () from
/usr/lib64/libQt5Core.so.5                                      
(gdb) bt                                                                        
#0  0x00007ffff5e815a3 in QSocketNotifier::setEnabled(bool) () from
/usr/lib64/libQt5Core.so.5                                  
#1  0x00007ffff5e81629 in QSocketNotifier::~QSocketNotifier() () from
/usr/lib64/libQt5Core.so.5                                
#2  0x00007ffff5e81649 in QSocketNotifier::~QSocketNotifier() () from
/usr/lib64/libQt5Core.so.5                                
#3  0x00007ffff5e738f1 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5                                   
#4  0x00007ffff5e7cc8f in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5                                                
#5  0x00007fffde79ade9 in KWin::DrmBackend::~DrmBackend() ()                    
   from
/usr/lib64/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so    
#6  0x00007ffff5e3e279 in ?? () from /usr/lib64/libQt5Core.so.5                 
#7  0x00007ffff5e3f66f in ?? () from /usr/lib64/libQt5Core.so.5                 
#8  0x00007ffff52a85df in __cxa_finalize () from /lib64/libc.so.6               
#9  0x00007ffff5c49763 in ?? () from /usr/lib64/libQt5Core.so.5                 
#10 0x00007fffffffcfb0 in ?? ()                                                 
#11 0x00007ffff7de7c5a in _dl_fini () from /lib64/ld-linux-x86-64.so.2

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to