Bug 1340078
Summary: | libXfixes-5.0.2 is available | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
Component: | libXfixes | Assignee: | Benjamin Tissoires <btissoir> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rawhide | CC: | btissoir, fedora, sandmann | ||||
Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | libXfixes-5.0.2-2.fc24 | Doc Type: | Enhancement | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-05-28 18:33:44 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
Upstream Release Monitoring
2016-05-26 12:15:08 UTC
Patching or scratch build for libXfixes-5.0.1 failed. Created attachment 1161963 [details] Rebase-helper rebase-helper-debug.log log file. See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues. Patches were not touched. All were applied properly bentiss's libXfixes-5.0.2-2.fc25 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=768749 libXfixes-5.0.2-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-88baa4e5ce libXfixes-5.0.2-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-88baa4e5ce This update seems to break at-spi on wayland: Successfully activated service 'org.a11y.atspi.Registry' SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry ** (at-spi2-registryd:26015): WARNING **: AT-SPI: Cannot open default display ** (yumex-dnf-updatechecker:16295): WARNING **: AT-SPI: Could not obtain desktop path or name ** (gnome-settings-daemon:16158): WARNING **: AT-SPI: Could not obtain desktop path or name ** (evolution-alarm-notify:16251): WARNING **: AT-SPI: Could not obtain desktop path or name ** (transmission-gtk:16274): WARNING **: AT-SPI: Could not obtain desktop path or name ** (gnome-calendar:22924): WARNING **: AT-SPI: Could not obtain desktop path or name ** (gnome-terminal-server:22404): WARNING **: AT-SPI: Could not obtain desktop path or name Activating service name='org.a11y.atspi.Registry ** (at-spi2-registryd:26017): WARNING **: Could not open X display It seems like every single Gtk+ application starting in a gnome+wayland session is printing 10…20 of those messages. Please don't spam my syslog ;) (In reply to Christian Stadelmann from comment #7) > It seems like every single Gtk+ application starting in a gnome+wayland > session is printing 10…20 of those messages. Please don't spam my syslog ;) I am very surprised this to be the case. The difference between 5.0.1-6 and 5.0.2-2 is basically just a tag upstream of the new release after a removal of a compatibility function that was here to fix a CVE in libX11 < 1.6. Could you downgrade just libXfixes to 5.0.1-6 and see if the problem persists? (In reply to Benjamin Tissoires from comment #8) > (In reply to Christian Stadelmann from comment #7) > > It seems like every single Gtk+ application starting in a gnome+wayland > > session is printing 10…20 of those messages. Please don't spam my syslog ;) > > I am very surprised this to be the case. The difference between 5.0.1-6 and > 5.0.2-2 is basically just a tag upstream of the new release after a removal > of a compatibility function that was here to fix a CVE in libX11 < 1.6. > > Could you downgrade just libXfixes to 5.0.1-6 and see if the problem > persists? I did, and the problem went away. This is why I left this comment. Now I upgraded again and the issue isn't coming back, so probably this was a false alert. Sorry for the noise. libXfixes-5.0.2-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report. |