Bug 1281331

Summary: [abrt] [IMAPx] Incorrect unref of message info on message copy
Product: [Fedora] Fedora Reporter: rh <r>
Component: evolution-data-serverAssignee: Milan Crha <mcrha>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: bojan, fedora, ifoolb, lucilanga, mbarnes, mcrha, philip, tpopela, tuksgig
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/780a6cbe9a18ac099ec0757269a53db072880c18
Whiteboard: abrt_hash:3fe88447f7dfccc92b44e18f308641576a6a451f;VARIANT_ID=workstation;
Fixed In Version: evolution-data-server-3.18.3-1 evolution-data-server-3.18.2-2.fc23 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 21:51:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
'Details' from ABRT none

Description rh 2015-11-12 10:27:52 UTC
Version-Release number of selected component:
evolution-3.18.1-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        evolution
crash_function: camel_message_info_unref
executable:     /usr/bin/evolution
global_pid:     11209
kernel:         4.2.5-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
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

Comment 1 rh 2015-11-12 10:27:59 UTC
Created attachment 1093116 [details]
File: backtrace

Comment 2 rh 2015-11-12 10:28:00 UTC
Created attachment 1093117 [details]
File: cgroup

Comment 3 rh 2015-11-12 10:28:03 UTC
Created attachment 1093118 [details]
File: core_backtrace

Comment 4 rh 2015-11-12 10:28:05 UTC
Created attachment 1093119 [details]
File: dso_list

Comment 5 rh 2015-11-12 10:28:07 UTC
Created attachment 1093120 [details]
File: environ

Comment 6 rh 2015-11-12 10:28:08 UTC
Created attachment 1093121 [details]
File: exploitable

Comment 7 rh 2015-11-12 10:28:10 UTC
Created attachment 1093122 [details]
File: limits

Comment 8 rh 2015-11-12 10:28:15 UTC
Created attachment 1093123 [details]
File: maps

Comment 9 rh 2015-11-12 10:28:16 UTC
Created attachment 1093124 [details]
File: mountinfo

Comment 10 rh 2015-11-12 10:28:18 UTC
Created attachment 1093125 [details]
File: open_fds

Comment 11 rh 2015-11-12 10:28:19 UTC
Created attachment 1093126 [details]
File: proc_pid_status

Comment 12 rh 2015-11-12 10:28:21 UTC
Created attachment 1093127 [details]
File: var_log_messages

Comment 13 Milan Crha 2015-11-16 08:31:49 UTC
Thanks for a bug report. This had been fixed recently in an upstream bug [1]. See it for more details how to workaround the issue until the 3.18.3 is out.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=757789

Comment 14 Milan Crha 2015-11-16 08:33:04 UTC
*** Bug 1281341 has been marked as a duplicate of this bug. ***

Comment 15 Milan Crha 2015-11-18 09:11:23 UTC
*** Bug 1282840 has been marked as a duplicate of this bug. ***

Comment 16 Milan Crha 2015-11-18 09:25:14 UTC
*** Bug 1282509 has been marked as a duplicate of this bug. ***

Comment 17 Fedora Update System 2015-11-18 10:18:12 UTC
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

Comment 18 Fedora Update System 2015-11-19 15:27:05 UTC
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

Comment 19 Fedora Update System 2015-11-19 16:55:40 UTC
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

Comment 20 Milan Crha 2015-11-25 07:34:52 UTC
*** Bug 1285160 has been marked as a duplicate of this bug. ***

Comment 21 Fedora Update System 2015-12-02 21:51:22 UTC
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.

Comment 22 汪明衡 2016-08-19 02:42:52 UTC
I may still get this problem. I'm not sure. On fedora 23 evolution version 3.18.5.2-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.

Comment 23 汪明衡 2016-08-19 02:46:26 UTC
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.

Comment 24 Milan Crha 2016-08-19 08:43:09 UTC
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 \
       --enablerepo=updates-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
   just confirm.

Then include the information in the new bug report. Thanks in advance.

Comment 25 汪明衡 2016-08-20 00:54:50 UTC
Not exactly a starter, but I've never used this sort of gdb command ;) Here is the new bug report link
https://bugzilla.redhat.com/show_bug.cgi?id=1368612