Bug 829324
| Summary: | Error on boot: "Could not create ICE listening socket: Cannot establish any listening sockets" | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dave Allan <dallan> | ||||||
| Component: | libICE | Assignee: | Søren Sandmann Pedersen <sandmann> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 17 | CC: | bjgindia, codeslayer2010, cpanceac, kem, sandmann | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-08-01 10:39:57 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Dave Allan
2012-06-06 13:15:22 UTC
Created attachment 589883 [details]
screenshot
Created attachment 589887 [details]
additional debug info, logs, etc
this still can be reproduced in f17 + latest updates. it does happen maybe once at every few logins. My Fedora 17 i686 XFCE spin has started showing this problem from today. It was working flawlessley for the past couple of months. Even after repeated tries, I am unable to login through the graphical login screen. I even cleared the sockets created under /tmp/.X11-unix /tmp/.ICE-unix and /tmp-.X0-lock, but the problem remains. This is consistently reproducible everytime on my home pc. Are there any workarounds available? Please let me know if some logs and dumps from my machine may be helpful. This info about my experience today may prove useful to the community. I can't SSH on Fedora 17 and have been troubleshooting the issue. One of the steps I performed was to edit the /etc/ssh/sshd_config file. I uncommented "# Port 22". After reboot I received the error: "Could not create ICE listening socket: Cannot establish any listening sockets" I'm a newbie as a linux admin, so I can provide more info if requested. What I know about my sysem is: Fedora 17 (fresh install) OpenSSH daemon is installed and running GPU: Nvida (Linus says Nvidia support is lacking: http://linux.slashdot.org/story/12/06/17/1415250/torvalds-slams-nvidias-linux-support) If I can help with any other info please let me know. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. |