After running for about a week, attempts to open X applications on my work station all result in the same error:
All existing, previously started X-apps continue to work fine.
At any X-app started remotely via ssh works fine.
However, if I open a new ssh session to yet another server and attempt to start an X-app, I get a similar error:
/tmp/.X11-unix/X0 appears to be alive and well (it's there, but I don't know how to poke at it meaningfully).
According to
This has happened before. It takes a week or two to reappear. Rebooting makes the problem go away. ~something~ is dieing; but I haven't been able to suss which.
~/.xsession-errors is ~choked~ with 2500 lines of spurious noise from KDE; so while I imagine the answer is buried in there, it may be no help until I replace KDE with something less vociferous (WindowMaker?).
I find this very weird and very disturbing.
I am running: 10.1-RELEASE-p5 (however, problem first appeared before using
Thank you for your time; but please note that the failure interval is measured in weeks; so I may not respond to suggestions quickly.
Code:
** ericx@milicent ** ~ ** Tue Mar 03 20:44:44
$ xterm
No protocol specified
xterm: Xt error: Can't open display: :0.0
[Exit 1 ]
At any X-app started remotely via ssh works fine.
However, if I open a new ssh session to yet another server and attempt to start an X-app, I get a similar error:
Code:
** ericx@fw ** ~ ** Wed Mar 04 09:29:58
$ xterm
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyxterm: Xt error: Can't open display: localhost.foobar.not:10.0
[Exit 1 ]
According to
sockstat
I appear to be using about 50 streams off the X0 socket (which doesn't seem excessive? Is there a limit?):
Code:
** ericx@milicent ** ~ ** Wed Mar 04 09:35:36
$ netstat -x | grep X0 | wc -l
54
~/.xsession-errors is ~choked~ with 2500 lines of spurious noise from KDE; so while I imagine the answer is buried in there, it may be no help until I replace KDE with something less vociferous (WindowMaker?).
I find this very weird and very disturbing.
I am running: 10.1-RELEASE-p5 (however, problem first appeared before using
freebsd-update
to bump up from 10.0-RELEASE-p[mumble]. Xorg was recompiled at the same time as the OS and is currently:
Code:
** ericx@milicent ** ~ ** Wed Mar 04 10:28:30
$ pkg info | grep xorg
linux-c6-xorg-libs-7.4_1 Xorg libraries (Linux CentOS 6.6)
xorg-7.7_1 X.Org complete distribution metaport
xorg-apps-7.7_2 X.org apps meta-port
xorg-cf-files-1.0.5_1 X.org cf files for use with imake builds
xorg-docs-1.7,1 X.org documentation files
xorg-drivers-7.7_2 X.org drivers meta-port
xorg-fonts-7.7 X.org fonts meta-port
xorg-fonts-100dpi-7.7 X.Org 100dpi bitmap fonts
xorg-fonts-75dpi-7.7 X.Org 75dpi bitmap fonts
xorg-fonts-cyrillic-7.7 X.Org Cyrillic bitmap fonts
xorg-fonts-miscbitmaps-7.7 X.Org miscellaneous bitmap fonts
xorg-fonts-truetype-7.7_1 X.Org TrueType fonts
xorg-fonts-type1-7.7 X.Org Type1 fonts
xorg-libraries-7.7_2 X.org libraries meta-port
xorg-macros-1.19.0 X.Org development aclocal macros
xorg-server-1.14.7_1,1 X.Org X server and related programs