Version-Release number of selected component: trojita-0.5-7.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: trojita crash_function: Imap::Mailbox::ImapTask::log executable: /usr/bin/trojita global_pid: 29883 kernel: 4.2.0-0.rc6.git0.2.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 Imap::Mailbox::ImapTask::log at /usr/src/debug/trojita-0.5/src/Imap/Tasks/ImapTask.cpp:304 #1 Imap::Mailbox::ImapTask::_failed at /usr/src/debug/trojita-0.5/src/Imap/Tasks/ImapTask.cpp:239 #2 Imap::Mailbox::Model::killParser at /usr/src/debug/trojita-0.5/src/Imap/Model/Model.cpp:1471 #3 Imap::Mailbox::Model::handleSocketDisconnectedResponse at /usr/src/debug/trojita-0.5/src/Imap/Model/Model.cpp:1134 #4 Imap::Mailbox::Model::responseReceived at /usr/src/debug/trojita-0.5/src/Imap/Model/Model.cpp:245 #6 Imap::Mailbox::Model::qt_static_metacall at /usr/src/debug/trojita-0.5/build/moc_Model.cpp:322 #7 QObject::event at kernel/qobject.cpp:1246 #8 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3717 #9 QApplication::notify at kernel/qapplication.cpp:3500 #10 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:965
Created attachment 1066513 [details] File: backtrace
Created attachment 1066514 [details] File: cgroup
Created attachment 1066515 [details] File: core_backtrace
Created attachment 1066516 [details] File: dso_list
Created attachment 1066517 [details] File: environ
Created attachment 1066518 [details] File: limits
Created attachment 1066519 [details] File: maps
Created attachment 1066520 [details] File: mountinfo
Created attachment 1066521 [details] File: namespaces
Created attachment 1066522 [details] File: open_fds
Created attachment 1066523 [details] File: proc_pid_status
Created attachment 1066524 [details] File: var_log_messages
Hi Karel, thanks for your report. Can you reproduce this crash, what were you doing for it? Especially as you reported against f23, I wonder if it can be duplicated in Fedora 22.
(In reply to Raphael Groner from comment #13) > Can you reproduce this crash, what were you doing for it? unfortunately not; or at least I wasn't able to figure out any sequence of actions leading to crash, and while I'm getting crashes quite often after the upgrade, it seems it hits different code each time > Especially as you reported against f23, I wonder if it can be duplicated in > Fedora 22. I'd think so, so far I haven't seen anything fixed (as I hoped when updating to pre-release version) :-/
(In reply to Karel Volný from comment #14) > ... after the upgrade ... oops, I've mixed the versions I mean that my system started to exhibit crashes after upgrade to Fedora 22 as it included 'fresh' KDE 5, I was hoping that upgrading again to F23 will bring me newer (and more mature) version with less crashes, but it did not happen
As far as I can understand the provided backtrace and available source, Trojita lost network connection for any strange reason and then tried to log it and crashed. Due to the fact that it is obviously difficult to reproduce the original situation, I'll close this. Please feel free to reopen if problem still exists, then I try to poke upstream.
trojita-0.5a-2.20151216gitefa30f3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update trojita' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-afb9844b79
trojita-0.5a-2.20151216gitefa30f3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.