Red Hat Bugzilla – Bug 1281331
[abrt] [IMAPx] Incorrect unref of message info on message copy
Last modified: 2016-08-19 20:54:50 EDT
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 camel_message_info_unref at camel-folder-summary.c:4538
#1 g_hash_table_remove_all_nodes at ghash.c:548
#3 g_hash_table_remove_all at ghash.c:1428
#4 g_hash_table_destroy at ghash.c:1122
#5 camel_imapx_server_copy_message_sync at camel-imapx-server.c:4310
#6 imapx_conn_manager_copy_message_run_sync at camel-imapx-conn-manager.c:1755
#7 camel_imapx_job_run_sync at camel-imapx-job.c:473
#8 camel_imapx_conn_manager_run_job_sync at camel-imapx-conn-manager.c:986
#9 imapx_conn_manager_copy_message_sync at camel-imapx-conn-manager.c:1805
#10 camel_imapx_conn_manager_copy_message_sync at camel-imapx-conn-manager.c:1838
Created attachment 1093116 [details]
Created attachment 1093117 [details]
Created attachment 1093118 [details]
Created attachment 1093119 [details]
Created attachment 1093120 [details]
Created attachment 1093121 [details]
Created attachment 1093122 [details]
Created attachment 1093123 [details]
Created attachment 1093124 [details]
Created attachment 1093125 [details]
Created attachment 1093126 [details]
Created attachment 1093127 [details]
Thanks for a bug report. This had been fixed recently in an upstream bug . See it for more details how to workaround the issue until the 3.18.3 is out.
*** Bug 1281341 has been marked as a duplicate of this bug. ***
*** Bug 1282840 has been marked as a duplicate of this bug. ***
*** Bug 1282509 has been marked as a duplicate of this bug. ***
evolution-data-server-3.18.2-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-cf51e6b9dc
evolution-data-server-3.18.2-2.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 evolution-data-server'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-cf51e6b9dc
*** Bug 1285160 has been marked as a duplicate of this bug. ***
evolution-data-server-3.18.2-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
I may still get this problem. I'm not sure. On fedora 23 evolution version 188.8.131.52-1.fc23.i686, with evolution-mapi-3.18.4-1.fc23.i686.rpm installed, when trying setting up an exchange account, it crashes on clicking 'ok' button following password prompt by first clicking 'Authenticate' button on the exchange server setup window. But when I was about to report it, ABRT read 'The process had locked memory which usually indicates efforts to protect sensitive data (passwords) from being written to disk.'... I was directed to https://bugzilla.redhat.com/show_bug.cgi?id=1285160 when clicking Bugzilla, which then points me here.
Created attachment 1192019 [details]
'Details' from ABRT
This is the details by clicking 'details'. don't know if it's relevant, hope it will be helpful.
Thanks for the update. I guess the ABRT is wrong. Both bugs were specific to IMAP, while you mention a crash after using evolution-mapi. Those are two unrelated parts. Even the ABRT's Details do not show anything related to evolution-mapi. To be honest, I do not see from it any crashing thread.
Could you open a new bug report against evolution-mapi, where we could investigate this further, please? Ideally if you can reproduce it, though not that Fedora 24 would be better, because samba libraries received many fixes between the version in Fedora 23 and Fedora 24. Anyway, as a starter for the new bug report, please try this:
a) install debuginfo packages for the the evolution-mapi, evolution-data-server,
evolution and openchange, which can be done as root with:
# dnf install openchange-debuginfo evolution-debuginfo \
evolution-data-server-debuginfo evolution-mapi-debuginfo \
(eventually use "*-debuginfo" instead of "updates-debuginfo")
b) run evolution from terminal under gdb as a regular user:
$ gdb evolution --ex r --ex bt --ex "t a a bt" --ex q
This command just runs the evolution and when it breaks, it prints
a backstrace where it stopped and then backtrace for all running threads.
c) Reproduce the issue in the evolution. In case evolution freezes, check
the terminal, whether gdb is not waiting for an input.
d) once reproduced, copy the output of the gdb to a text file, say bt.txt.
Please check the bt.txt for any private information, like passwords, email
address, server addresses,... I usually search for "pass" at least (quotes
for clarity only).
The gdb should ask whether you want to quit at the end, which you can
Then include the information in the new bug report. Thanks in advance.
Not exactly a starter, but I've never used this sort of gdb command ;) Here is the new bug report link