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

Jan Bidler <janbidle...@protonmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WAITINGFORINFO              |---
             Status|NEEDSINFO                   |REPORTED

--- Comment #11 from Jan Bidler <janbidle...@protonmail.com> ---
Used the nightly Flatpak version, still get a crash, although I think this one
is different?
Terminal shows this:
> /usr/include/c++/11.3.0/optional:446: constexpr const _Tp& 
> std::_Optional_base_impl<_Tp, _Dp>::_M_get() const [with _Tp = 
> Quotient::MemberEventContent; _Dp = 
> std::_Optional_base<Quotient::MemberEventContent, false, false>]: Assertion 
> 'this->_M_is_engaged()' failed.


GDB bt full:
```
Thread 1 "neochat" received signal SIGABRT, Aborted.
0x00007ffff4e5949b in raise () from /usr/lib/x86_64-linux-gnu/libc.so.6
(gdb) bt full
#0  0x00007ffff4e5949b in raise () at /usr/lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff4e42857 in abort () at /usr/lib/x86_64-linux-gnu/libc.so.6
#2  0x0000555555670376 in  ()
#3  0x0000555555686845 in  ()
#4  0x000055555566cd89 in  ()
#5  0x00007ffff5697491 in QSortFilterProxyModel::data(QModelIndex const&, int)
const ()
    at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00005555556aa6de in  ()
#7  0x00005555556ab1f5 in  ()
#8  0x00007ffff61b540f in  () at /usr/lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#9  0x00007ffff73a98d6 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x00007ffff73aa562 in
QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*,
QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*,
QQmlPropertyData**) ()
    at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x00007ffff7386065 in
QV4::QQmlContextWrapper::lookupInParentContextHierarchy(QV4::Lookup*,
QV4::ExecutionEngine*, QV4::Value*) () at
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x00007fff89fe36a4 in  ()
#13 0x0000000000000000 in  ()

```

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

Reply via email to