Created attachment 666551 [details] xterm.strace Description of problem: sassmann@t530:~> xterm ICE default IO error handler doing an exit(), pid = 7773, errno = 2 Version-Release number of selected component (if applicable): gnome-session-3.6.2-3.fc18.x86_64 Not sure if I got the right component, please reassign if I got this wrong. How reproducible: only happens after a few hours, but then every time. Steps to Reproduce: 1. launch xterm Additional info: I'm reusing my old home directory from F17. Moving away ~/.ICEauthority allows xterm to start again, but that's probably not a good idea.
I'm seeing the exact same problem periodically as well. I thought it was related to suspending my laptop while on one network (work) then going home and connecting to a different network (home) but that's not reproducible either. It just occurred and roughly coincided with me connecting to our juniper connect vpn, so I logged out of my gnome session and back in and reconnected to my work vpn and the problem is not occurring. So it's not at least directly triggered by network changes.
I've the same issue and the following workaround it was ok ... restarting session (logout,logon). I didn't reproduce it but was happened few times. FC18 x86_64
I have the same issue with F18 x86_64 whenever I resume from hibernate or suspend. Logging out, then back in fixes the issue until the next hibernation/suspend, but that is not an acceptable workaround. It defeats the purpose of hibernation and suspend in the first place. Removing ~/.ICEauthority also works, but as the OP stated, that's not a good idea. When running a strace on an application that won't start, I see an attempt to read: unix:/tmp/.ICE-unix/<gnome-session PID>. This is followed by: Refusing new client connection I'm not sure why it is refused. The permissions look correct on the files and directories involved. I'm not sure what else to check. Any help would be greatly appreciated.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.