SUMMARY *** The first time I opened Neochat today, it launched, but when I clicked on a chat to open it, it crashed. Since then it directly crashes after launch (chats are visible for a brief moment). When I launched it from the command line with `flatpak run org.kde.neochat`, I got the following output: ``` quotient.main: The library is built with end-to-end encryption (E2EE) quotient.e2ee: Successfully loaded pickling key from keychain quotient.e2ee: 65536 bytes of secure heap initialised quotient.e2ee: Allocated 128 bytes of secure heap (requested 128 bytes), 128 / 65536 bytes of secure heap used in total quotient.e2ee: The fixed buffer source is shared; assuming that the caller is responsible for securely clearing other copies quotient.e2ee: Allocated 256 bytes of secure heap (requested 160 bytes), 384 / 65536 bytes of secure heap used in total quotient.e2ee: Deallocated 256 bytes, 128 / 65536 bytes of secure heap used quotient.e2ee: Allocated 256 bytes of secure heap (requested 160 bytes), 384 / 65536 bytes of secure heap used in total quotient.e2ee: Deallocated 256 bytes, 128 / 65536 bytes of secure heap used quotient.e2ee: Allocated 256 bytes of secure heap (requested 160 bytes), 384 / 65536 bytes of secure heap used in total quotient.e2ee: Deallocated 256 bytes, 128 / 65536 bytes of secure heap used quotient.e2ee: Allocated 256 bytes of secure heap (requested 160 bytes), 384 / 65536 bytes of secure heap used in total quotient.e2ee: Deallocated 256 bytes, 128 / 65536 bytes of secure heap used quotient.e2ee: Allocated 256 bytes of secure heap (requested 160 bytes), 384 / 65536 bytes of secure heap used in total quotient.e2ee: Deallocated 256 bytes, 128 / 65536 bytes of secure heap used quotient.main: Malformed userId: "@.m.rule.contains_user_name" quotient.main: Malformed userId: "@.org.matrix.msc3933.rule.extensible.encrypted_room_one_to_one" quotient.main: Malformed userId: "@.org.matrix.msc3933.rule.extensible.message.room_one_to_one" quotient.main: Malformed userId: "@.org.matrix.msc3933.rule.extensible.file.room_one_to_one" quotient.main: Malformed userId: "@.org.matrix.msc3933.rule.extensible.image.room_one_to_one" quotient.main: Malformed userId: "@.org.matrix.msc3933.rule.extensible.video.room_one_to_one" quotient.main: Malformed userId: "@.org.matrix.msc3933.rule.extensible.audio.room_one_to_one" quotient.e2ee: Successfully loaded pickling key from keychain quotient.e2ee: Allocated 128 bytes of secure heap (requested 128 bytes), 256 / 65536 bytes of secure heap used in total quotient.e2ee: The fixed buffer source is shared; assuming that the caller is responsible for securely clearing other copies Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. QQmlComponent: Cannot create new component instance before completing the previous qrc:/EmojiDialog.qml:57: TypeError: Cannot read property 'width' of null qrc:/EmojiPicker.qml:25: TypeError: Cannot read property 'category' of undefined ASSERT: "isValidFor(room, oldMarker)" in file /run/build/libquotient/Quotient/eventstats.cpp, line 60 ``` (I didn't include the first two lines to hide my matrix ID's) *** STEPS TO REPRODUCE 1. launch Neochat OBSERVED RESULT Neochat crashes EXPECTED RESULT neochat works SOFTWARE/OS VERSIONS Operating System: Crystal Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: TUXEDO Product Name: TUXEDO Aura 15 Gen1 System Version: Not Applicable
We'll need a backtrace to figure this out; could you try providing one?
I would love to, but I don't know how I get it. Since it lives in a flatpak, I guessed that the [arch wiki guide](https://wiki.archlinux.org/title/Debugging/Getting_traces) won't work (and also I found it a bit long and didn't wan't to dive into it if it probably does not work anyways). So I tried to I tried to follow [this documentation](https://develop.kde.org/docs/packaging/flatpak/integration/), installed the `.Debug` package, entered some kind of shell inside the flatpak with `flatpak run --command=bash --devel org.kde.neochat` and then ran `gdb /app/bin/neochat`. This gave me ```GNU gdb (GDB) 12.1t ~]$ Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /app/bin/neochat... Reading symbols from /usr/lib/debug//app/bin/neochat.debug... (gdb) ``` and exited after a couple of seconds without a backtrace. It also didn't open neochat, so I opened it from the panel entry and made the crash happen, but still nothing was shown. Can you tell me what I did wrong or piont me to a better guide?
By the way, now it does not crash after launch anymore, but only when I click on specific chats. Which chats trigger it, is not persistent.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I *think* I have solved this by granting permission to run in the background. Seems weird that it crashed on specific chats due to that, but the insta crash is fixed now. So I will close this for now and hopefully forever