[Bug 50807] X processes do not always start properly after resume

[Mary Gardiner]

*** This bug is a duplicate of bug 49221 ***

Public bug reported:

About 80% of suspend/resumes on this machine (a Fujitsu Lifebook S6120
for what it's worth) work fine. However, the rest of the time upon
resuming I successfully put my password into gnome-screensaveer and
while I can use existing programs opened prior to the suspend, I cannot
start new programs.

According to strace, it's blocking on a socket read, here's the relevant
output when I try and open an xterm:

connect(4, {sa_family=AF_FILE, path="/tmp/.ICE-unix/15504"}, 22) = 0
fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0
write(4, "\0\1\0\0\0\0\0\0", 8)         = 8
read(4,

There appears to be no way to reset the state of this satisfactorily,
other than completely logging out of and logging back into X.

** Affects: xorg (Ubuntu)
     Importance: Untriaged
         Status: Unconfirmed

-- 
X processes do not always start properly after resume
https://launchpad.net/bugs/50807