Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 936972[details]
backtrace
Description of problem:
evolution freezed after sending of an email. During writing of the email, I switched to another folder in the main window and I invoked a search
Version-Release number of selected component (if applicable):
evolution-3.8.5-22.el7_0.1.1.x86_64
evolution-data-server-3.8.5-24.el7_0.x86_64
How reproducible:
random
...
Additional info:
thread 1 bt:
#0 0x00007fd079d80a4d in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007fd07a09edd4 in g_main_context_poll (priority=2147483647, n_fds=5, fds=0x39bff40, timeout=243, context=0x2201d30) at gmain.c:3999
#2 g_main_context_iterate (context=0x2201d30, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3700
#3 0x00007fd07a09f25a in g_main_loop_run (loop=0x24b67e0) at gmain.c:3899
#4 0x00007fd07c5740ed in gtk_main () at gtkmain.c:1156
#5 0x0000000000403933 in main (argc=1, argv=0x7fff31324f68) at main.c:707
Thanks for a bug report. The background processes are idle, except of the evolution-addressbook-factory, which is doing couple requests through libgdata, I suppose with your Google addressbook. The evolution process backtrace doesn't show any UI freeze, according to the backtrace the evolution was responsive, but could show couple ongoing IMAP-related operations. At least, I see in the backtrace that there are four imapx_parser_thread() threads, waiting for data from the server and two imapx_idle_thread() threads.
Am I right with the UI of evolution being responsive? Could you explain what the UI does in this "freeze", please?
Maybe it is related to bug #1214659, I wouldn't be surprised if it is. Could you retest with evolution which will have the fix for that bug included, please?
Created attachment 936972 [details] backtrace Description of problem: evolution freezed after sending of an email. During writing of the email, I switched to another folder in the main window and I invoked a search Version-Release number of selected component (if applicable): evolution-3.8.5-22.el7_0.1.1.x86_64 evolution-data-server-3.8.5-24.el7_0.x86_64 How reproducible: random ... Additional info: thread 1 bt: #0 0x00007fd079d80a4d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007fd07a09edd4 in g_main_context_poll (priority=2147483647, n_fds=5, fds=0x39bff40, timeout=243, context=0x2201d30) at gmain.c:3999 #2 g_main_context_iterate (context=0x2201d30, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3700 #3 0x00007fd07a09f25a in g_main_loop_run (loop=0x24b67e0) at gmain.c:3899 #4 0x00007fd07c5740ed in gtk_main () at gtkmain.c:1156 #5 0x0000000000403933 in main (argc=1, argv=0x7fff31324f68) at main.c:707