Description of problem: I copied neochat folder to different computer. Then left one group I were member of. Then started neochat on the other computer and started neochat. Left the same group I left already. It crashed immediately. Version-Release number of selected component: neochat-22.04-1.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-100616.slice/user/app.slice/app-glib-org.kde.neochat-115140.scope cmdline: neochat crash_function: QVector<QQuickItemPrivate::ChangeListener>::realloc executable: /usr/bin/neochat journald_cursor: s=71cca600c70144fea48d6574e35780c9;i=77d5f;b=9c75f692f4b546829c83ac38d1abb154;m=249710c409;t=5deaa038b68b2;x=71578dce1da684c7 kernel: 5.17.4-200.fc35.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 100616 Truncated backtrace: Thread no. 1 (2 frames) #0 QVector<QQuickItemPrivate::ChangeListener>::realloc at /usr/include/qt5/QtCore/qvector.h:736 #1 QVector<QQuickItemPrivate::ChangeListener>::detach at /usr/include/qt5/QtCore/qvector.h:405
Created attachment 1878613 [details] File: backtrace
Created attachment 1878614 [details] File: core_backtrace
Created attachment 1878615 [details] File: cpuinfo
Created attachment 1878616 [details] File: dso_list
Created attachment 1878617 [details] File: environ
Created attachment 1878618 [details] File: exploitable
Created attachment 1878619 [details] File: limits
Created attachment 1878620 [details] File: maps
Created attachment 1878621 [details] File: mountinfo
Created attachment 1878622 [details] File: open_fds
Created attachment 1878623 [details] File: proc_pid_status
Created attachment 1878624 [details] File: var_log_messages
Crash related to Qt internals. Switching component to qt5-qtbase.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.