mart added a comment.

  right now, the xdgv6 branch (xdgv6popup actually) for me causes a crash in 
kwin at startup, with the following BT:
  #0  _int_malloc (av=av@entry=0x7ffff556ab20 <main_arena>, 
bytes=bytes@entry=72) at malloc.c:3414
  #1  0x00007ffff522a5d4 in __GI___libc_malloc (bytes=72) at malloc.c:2911
  #2  0x00007ffff55fde78 in operator new(unsigned long) ()
  
    from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  
  #3  0x00007ffff5dcc32e in QObjectPrivate::connectImpl 
(sender=sender@entry=0x69d950,
  
    signal_index=5, receiver=receiver@entry=0x69c600, slot=slot@entry=0x0, 
    slotObj=slotObj@entry=0x69c860, type=Qt::AutoConnection, types=0x0, 
    senderMetaObject=0x7ffff720c220 
<KWayland::Server::Display::staticMetaObject>)
    at kernel/qobject.cpp:4829
  
  #4  0x00007ffff5dcc69b in QObject::connectImpl (sender=0x69d950, 
signal=<optimized out>,
  
    receiver=0x69c600, slot=0x0, slotObj=0x69c860, type=Qt::AutoConnection, 
types=0x0, 
    senderMetaObject=0x7ffff720c220 
<KWayland::Server::Display::staticMetaObject>)
    at kernel/qobject.cpp:4784
  
  #5  0x00007ffff6f1f249 in QObject::connect<void 
(KWayland::Server::Display::*)(), 
KWayland::Server::Display::createXdgShell(const 
KWayland::Server::XdgShellInterfaceVersion&, QObject*)::<lambda()> >(const 
QtPrivate::FunctionPointer<void (KWayland::Server::Display::*)()>::Object *, 
void (KWayland::Server::Display::*)(KWayland::Server::Display * const), const 
QObject *, KWayland::Server::Display::<lambda()>, Qt::ConnectionType) 
(sender=0x69d950,
  
    signal=(void (KWayland::Server::Display::*)(KWayland::Server::Display * 
const)) 0x7ffff6fa67de <KWayland::Server::Display::aboutToTerminate()>, 
context=0x69c600, slot=..., 
    type=Qt::AutoConnection) at /opt/kde5/include/QtCore/qobject.h:338

REPOSITORY
  R127 KWayland

REVISION DETAIL
  https://phabricator.kde.org/D6047

To: davidedmundson, #plasma
Cc: graesslin, mart, plasma-devel, #frameworks, ZrenBot, progwolff, lesliezhai, 
ali-mohamed, jensreuterberg, abetts, sebas, apol, lukas

Reply via email to