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.
Bug 1104555 - GS freeze when opening compose window in evolution
Summary: GS freeze when opening compose window in evolution
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 7.1
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-04 08:28 UTC by Vladimir Benes
Modified: 2015-11-19 07:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 07:13:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
gs backtrace (17.34 KB, text/plain)
2014-06-04 08:28 UTC, Vladimir Benes
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2216 0 normal SHIPPED_LIVE gnome compositor stack bug fix and enhancement update 2015-11-19 08:26:34 UTC

Description Vladimir Benes 2014-06-04 08:28:24 UTC
Description of problem:
I see a freeze of GS when opening compose window in evolution. BT attached. As we've discussed similar freezes in Evolution it may be caused by dconf/GSettings false change notifications.

Version-Release number of selected component (if applicable):
gnome-shell-3.8.4-31.el7.x86_64

How reproducible:
once a day

Steps to Reproduce:
1.open evolution with several unread emails
2.read some of them
3.press ctrl+shift+r to reply on any

Actual results:
sometimes GS freeze occurs

Expected results:
no freeze at all

Additional info:

Comment 1 Vladimir Benes 2014-06-04 08:28:58 UTC
Created attachment 902040 [details]
gs backtrace

Comment 2 Milan Crha 2014-06-05 15:48:25 UTC
Just a note from evolution's side:

GSettings' "change" signal and GObject's "notify" signal are invoked unconditionally, without checking whether the value of the property or the key changed at all. GObject does it despite the property setter properly checks for the change, GSettings does it when dconf sends a "path-changed" event with
path "/", which means "everything changed".

The solution is to check whether the values really changed in the user's callback. Upstream bug (rejected by upstream) can be found here, together with more details:
https://bugzilla.gnome.org/show_bug.cgi?id=730886

I believe that evolution's presence is just a coincidence, probably caused by its heavy use of GSettings bindings. The attached backtrace shows that the gome-shell was also notified about the path change in GSettings, while the exact path is optimized out, I believe it is "/".

Comment 5 Vladimir Benes 2015-05-14 15:53:04 UTC
cannot see this in the newest 3.14 versions.

Comment 8 errata-xmlrpc 2015-11-19 07:13:06 UTC
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.

https://rhn.redhat.com/errata/RHBA-2015-2216.html


Note You need to log in before you can comment on or make changes to this bug.