tag 794110 moreinfo thanks Hi everyone! With my Qt maintainer hat on, I would like you to give me some info. First: We have only one backtrace coming from the original submitter. Can the rest of you check if when a crash happens the current thread's (the crashing one) backtrace says something like: Thread 1 (Thread 0x7f5376449940 (LWP 18333)): [KCrash Handler] #6 0x00007f5373d1d1b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x00007f5373f860c8 in QQmlDelegateModel::_q_itemsChanged(int, int, QVector<int> const&) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x00007f5373fadd2c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x00007f5373fae46f in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x00007f53718d723a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 or is it different? Second: as this seems to be QML-related I would like to know which video card and drivers (proprietary or not) are you using. This might or not be a Qt bug, but as long as we can't reproduce it with a minimal example or get some more information it is difficult to say. Qt 5.6.0 has been released today, but we are not going to push it to unstable until 5.6.1 comes out (between 4 to 8 weeks more) due to the need of a transition. Kinds regards, Lisandro. -- Super cow powers | bbq > /dev/stomach Traveler1, seen on #debian-ar, irc.oftc.net Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Attachment:
signature.asc
Description: This is a digitally signed message part.