SDescription of problem: Sort emails by data by clicking on the titel Version-Release number of selected component: trojita-0.7-14.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: trojita crash_function: QSortFilterProxyModelPrivate::proxy_to_source executable: /usr/bin/trojita journald_cursor: s=8bf6ddad9d054d6a8450d20d9e266798;i=71a7;b=93c0cb19eb3b4ed5a8f2faddc4207f7f;m=17bc10e1;t=58d3b68ace9b5;x=70adca1c92536280 kernel: 5.1.12-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QSortFilterProxyModelPrivate::proxy_to_source at itemmodels/qsortfilterproxymodel.cpp:552 #1 QSortFilterProxyModel::mapToSource at itemmodels/qsortfilterproxymodel.cpp:3061 #2 QSortFilterProxyModel::flags at itemmodels/qsortfilterproxymodel.cpp:2487 #3 QModelIndex::flags at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:461 #4 QTreeViewPrivate::isIndexExpanded at ../../include/QtWidgets/5.12.1/QtWidgets/private/../../../../../src/widgets/itemviews/qtreeview_p.h:216 #5 QTreeView::isExpanded at itemviews/qtreeview.cpp:833 #6 QTreeView::verticalScrollbarValueChanged at itemviews/qtreeview.cpp:4018 #7 QAbstractItemView::qt_static_metacall at .moc/moc_qabstractitemview.cpp:423 #8 QMetaObject::activate at kernel/qobject.cpp:3789 #9 QAbstractSlider::valueChanged at .moc/moc_qabstractslider.cpp:308 Find attachment at https://bugzilla.redhat.com/show_bug.cgi?id=1728177
This backtrace looks like a crash somewhere deep in the Qt stack. Yes, we're banging the QAbstractProxyModel quite intensively, but we've got test coverage for this. Unless you can reproduce this with the latest git of Trojita and with assertions enabled, I'm closing this as a "possible bug in Qt".
Will you downstream the latest version to fedora? They claim there has been no upstream for an extensive amount of time
Created attachment 121533 [details] attachment-26974-0.html it crashes trojita. can you take it up with the qt team. On Wed, Jul 10, 2019, 12:06 Jan Kundrát <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=409672 > > Jan Kundrát <jkt@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |UPSTREAM > > --- Comment #1 from Jan Kundrát <jkt@kde.org> --- > This backtrace looks like a crash somewhere deep in the Qt stack. Yes, > we're > banging the QAbstractProxyModel quite intensively, but we've got test > coverage > for this. Unless you can reproduce this with the latest git of Trojita and > with > assertions enabled, I'm closing this as a "possible bug in Qt". > > -- > You are receiving this mail because: > You reported the bug.
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!
Created attachment 121899 [details] attachment-27178-0.html what do you need ? On Tue, 30 Jul 2019 at 06:33, Bug Janitor Service <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=409672 > > --- Comment #4 from Bug Janitor Service <bug-janitor@kde.org> --- > 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! > > -- > You are receiving this mail because: > You reported the bug.
Did you report this with the Qt team?
or how do you want me report this with the Qt team?
Created attachment 122198 [details] attachment-20172-0.html Not sure what additional info is needed. Bug Janitor Service <bugzilla_noreply@kde.org> schrieb am Sa., 17. Aug. 2019, 06:33: > https://bugs.kde.org/show_bug.cgi?id=409672 > > --- Comment #8 from Bug Janitor Service <bug-janitor@kde.org> --- > 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! > > -- > You are receiving this mail because: > You reported the bug.
Changing status.