Bug 893162
| Summary: | /usr/bin/gnome-keyring-daemon coredumps at startup | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Karsten Hopp <karsten> | ||||||
| Component: | gnome-keyring | Assignee: | Tomáš Bžatek <tbzatek> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 18 | CC: | debarshir, gustavold, stefw, tbzatek, tsmetana, walters | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | ppc64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 894157 (view as bug list) | Environment: | |||||||
| Last Closed: | 2013-01-20 15:43:19 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 894157 | ||||||||
| Attachments: |
|
||||||||
Created attachment 676525 [details]
Fix memrchr() call with negative string length
Please add the attached patch to the gnome-keyring package. This patch should fix this issue. It fixes an invalid call to memrchr() in libegg.
I could not reproduce this issue reliably as is, but Karsten pointed me to a variant of this bug that could be reproduced easily:
gnome-keyring import ~/.ssh/id_rsa
Although both gkr tool and gkr-daemon crash similarly, they have to be fixed in different places because they use different copies of the faulty libegg. While gkr-daemon uses its own copy of libegg linked statically, the gkr tool ends up using libegg through gcr, which also has libegg linked statically.
I will clone this bug and assign to gcr to get it fixed too.
Turned into "git format-patch" style against https://live.gnome.org/GnomeLove/SubmittingPatches and submitted upstream. Should be reviewed by Stef. gcr-3.6.2-2.fc18,gnome-keyring-3.6.2-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gcr-3.6.2-2.fc18,gnome-keyring-3.6.2-3.fc18 Package gcr-3.6.2-2.fc18, gnome-keyring-3.6.2-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gcr-3.6.2-2.fc18 gnome-keyring-3.6.2-3.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-0884/gcr-3.6.2-2.fc18,gnome-keyring-3.6.2-3.fc18 then log in and leave karma (feedback). gcr-3.6.2-2.fc18, gnome-keyring-3.6.2-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 675001 [details] tarball of abrt files Description of problem: /usr/bin/gnome-keyring-daemon coredumps at startup on PPC64, abrt files attached in a tarball Version-Release number of selected component (if applicable): gnome-keyring-3.6.2-2.fc18