Hide Forgot
Description of problem: I've just a clicked onto inbox folder ... Version-Release number of selected component: trojita-0.7-3.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/trojita crash_function: __cxxabiv1::(anonymous namespace)::adjust_pointer<void> executable: /usr/bin/trojita global_pid: 4440 kernel: 4.8.5-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __cxxabiv1::(anonymous namespace)::adjust_pointer<void> at ../../../../libstdc++-v3/libsupc++/tinfo.h:68 #1 __cxxabiv1::__dynamic_cast at ../../../../libstdc++-v3/libsupc++/dyncast.cc:55 #2 Imap::Mailbox::Model::askForMessagesInMailbox at /usr/src/debug/trojita-0.7/src/Imap/Model/Model.cpp:785 #3 Imap::Mailbox::Model::qt_static_metacall at /usr/src/debug/trojita-0.7/x86_64-redhat-linux-gnu/moc_Model.cpp:325 #4 QObject::event at kernel/qobject.cpp:1263 #5 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3799 #6 QApplication::notify at kernel/qapplication.cpp:3556 #7 QCoreApplication::notifyInternal2 at kernel/qcoreapplication.cpp:988 #8 QCoreApplication::sendEvent at kernel/qcoreapplication.h:231 #9 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1649
Created attachment 1216731 [details] File: backtrace
Created attachment 1216732 [details] File: cgroup
Created attachment 1216733 [details] File: core_backtrace
Created attachment 1216734 [details] File: dso_list
Created attachment 1216735 [details] File: environ
Created attachment 1216736 [details] File: exploitable
Created attachment 1216737 [details] File: limits
Created attachment 1216738 [details] File: maps
Created attachment 1216739 [details] File: mountinfo
Created attachment 1216740 [details] File: namespaces
Created attachment 1216741 [details] File: open_fds
Created attachment 1216742 [details] File: proc_pid_status
Created attachment 1216743 [details] File: var_log_messages
Is this a bug in Qt 5.7 as in Fedora 25? It's not reproducible in F24 (with currently Qt 5.6).
Is it even reproducible on f25/qt-5.7 ?
No crashes here at all in my F24 plasma session. I'm really wondering in general how Karel Volný could produce all the abrt reports, noone else reported such things.
(In reply to Raphael Groner from comment #14) > Is this a bug in Qt 5.7 as in Fedora 25? yes, it's Qt 5.7 and F25, I've been running pre-release since September (In reply to Rex Dieter from comment #15) > Is it even reproducible on f25/qt-5.7 ? it hasn't happened since ... note that in general, the number of times I'm getting abrt popups has dropped significantly around (or slightly before) the F25 GA date (In reply to Raphael Groner from comment #16) > I'm really wondering in general how Karel Volný could produce all the abrt > reports, noone else reported such things. it's karma ... just lend me your machine and I'll crash it :-) well, more seriously - as jkt mentioned on another report, there was some race condition depending on network timeouts, this is the kind of situation that is hard to reproduce ... not sure how relevant it could be here in this report, but let's talk in general, what kinds of errors I'm seeing now as for network timeouts, I have to say that our Zimbra IMAP isn't the most reliable thing on the Earth that I have seen ... however, as I'm the only one in our team that uses Trojitá (and one among a _very few_ Trojitá users in our office), it's quite obvious that there won't be reports from other people suffering the same network problems (they use webinterface or Thunderbird or whatever else) also, not many people use LXQt, and even smaller number of them don't do desktop install but rather minimal install + groupinstall LXQt[*], and of this small number, how many do bother to click through each and every abrt popup, or do even have abrt active? [*] btw I've found many missing dependencies, software relying on fact that something is simply present - that's another contributing factor to experience more problems and I could find a few other patterns that would explain what I am "doing wrong", but I guess the above could be enough to satisfy your curioiusity ;-)
I cannot reproduce the crash with f25/f26 latest with your testcase. So i close this bug as "CURRENTRELEASE". Please feel free to reopen it again if you can reproduce this issue. Thanks for you report.