Bug 418731
| Summary: | "couldn't read 4 bytes from client" in /var/log/messages | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christoph Wickert <christoph.wickert> |
| Component: | gnome-keyring | Assignee: | Tomáš Bžatek <tbzatek> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 9 | CC: | jburgess777, mail, poc, spacecat42, tsmetana, utmue |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://forums.fedoraforum.org/forum/showthread.php?p=914467 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-07-14 16:33:58 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: | |||
|
Description
Christoph Wickert
2007-12-10 20:22:50 UTC
This is apparently a duplicate of bug 354041 Not sure, because I don't see high CPU usage here at all. Also deleting and recreating the key rings did not solve the problem. I see this as well. Fully updated F8, Evolution user. Ping. I still see this on F9, fresh install but $HOME kept. Obviously it's not only limited to evolution, the message also appears when evo is not started and network-manager is the only client using the keyring daemon. This should be fixed by the patch applied for the upstream bug http://bugzilla.gnome.org/show_bug.cgi?id=511285 I'm getting this same behaviour in F9 using gnome-keyring-2.22.3-1.fc9.x86_64 and gnome-keyring-pam-2.22.3-1.fc9.x86_64. I use Evolution 2.22.3.1 under KDE 4.1.2 and the log messages appear in spurts every 10 minutes. I tried removing ~/.gnome2/keyrings/login.keyring and restarting the session, but to no avail (the keyring file was recreated though). Tomáš, any plans to fix this or just wait for the bugzappers to close it? I haven't been checking this, but I took a look just now and apparently it's no longer happening. I'm now on F10 (fully updated), with gnome-keyring-2.24.1-1.fc10.x86_64 and gnome-keyring-pam-2.24.1-1.fc10.x86_64. There is one message in the logs saying: /var/log/messages:Jan 11 22:32:26 bree gnome-keyring-daemon[3356]: couldn't write 146 bytes to client: Broken pipe but that may be something else. Ping! Another ping, or just wait for the bug-zappers to close this? I'm now on F11-pre and it's still not happening: gnome-keyring-2.26.1-1.fc11.x86_64. I can confirm that it no longer happens on F-10 and F-11, nevertheless I think this should be fixed, especially since the fix was already mentioned in comment #5. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. A sad day for Fedora. Obviously maintainers don't care about their bugs and don't even bother to write a single comment into a bug report - not even if the solution is already mentioned in the report and if the bug is flagged NEEDINFO. For better tracking I now close this bug duplicate of bug 354041. *** This bug has been marked as a duplicate of bug 354041 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |