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.

Description of problem:
dialog asking what to do with new message should pop up over window that received ctrl+q/File-Quit, not over concept window, and it should be highlighted

This is similar to bug 810460 - evo seems to do noop instead of requested action.

Version-Release number of selected component (if applicable):
evolution-2.32.3-1.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. have a main window and a New Message window opened, each on separated desktop and have main window focused
2. tell main window to quit the whole application (ctrl+q or file - quit)
3.

Actual results:
* a pop-up is issued:
  * over the New Message window
  * without any highlight
* main window gives no indication of what's going on whatsoever

Expected results:
* the best thing: just save the messages quietly and quit, restore the messages quietly on the new startup
* the next best things:
  * highlight the pop-up window in WM
  * bring the pop-up on top of the window that requested evo to quit

Additional info:

Created attachment 758064 [details]
hanging evo bt

The issue is somewhat worse if you issue another ctrl-q/File-Quit while the pop-up is waiting elsewhere - evo then shows all window widgets as disabled and it does not respond to any input anymore. The attached backtrace is of window in such state.

Upstream patch available (for master (3.9.4+) and 3.8.4+):
https://git.gnome.org/browse/evolution/commit/?h=gnome-3-8&id=69976cc

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1540.html