Date: Tue, 21 Jan 2014 15:20:08 -0800 From: David Wolfskill <david@catwhisker.org> To: x11@freebsd.org Subject: xterm: Xt error: Can't open display: :0.0 Message-ID: <20140121232008.GM1789@albert.catwhisker.org>
next in thread | raw e-mail | index | archive | help
--QPZaqi6af6gbSrAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I noticed something a bit odd today: I tend to connect to everything =66rom my laptop, which has historically Just Worked. Today, around mid-day, I tried starting an xterm... and (apparently) nothing happened. So I tried issuing "xterm &" from an existing xterm, and saw: d130(9.2-S)[13] Maximum number of clients reachedxterm: Xt error: Can't ope= n display: :0.0 Well... that's kinda ... rude.... (I subsequently found similar messages in ~/.xsession-errors.) Some salient information about the environment: The machine is running: FreeBSD g1-251.catwhisker.org 9.2-STABLE FreeBSD 9.2-STABLE #649 r260981M/= 260982:902506: Tue Jan 21 04:53:17 PST 2014 root@g1-251.catwhisker.org:= /usr/obj/usr/src/sys/CANARY i386 today. (I generally update it daily; see <http://www.catwhisker.org/~david/FreeBSD/history/laptop_i386_9.txt>; for a history of updates to the machine since last May; <http://www.catwhisker.org/~david/FreeBSD/history/>; has an explanation of what I've done to the version string output by uname and "sysctl kern.version".) As you might gather from the above, I use xdm. I haven't yet had the courage to try the "new X.org" yet; I'm using xorg-7.7. I see by my records that I updated xterm from xterm-300 to xterm-301 yesterday morning. I didn't exercise the machine as much then as I am doing today -- yesterday was a work holiday; I'm at work today. While xorg-7.7 has dependencies of dbus & hal, I don't run either of those (as I had some bad experiences with hal apparently going into 100% CPU loops); rather, I added the stanza: Section "ServerFlags" Option "AutoAddDevices" "False" EndSection to xorg.conf some years ago, and never looked back. I'm using nvidia-driver, and have been for about as long as I've had this laptop (which is almost 4 years now). Is this result ... expected now? Is there some configuration-thing I can/should change to avoid running into whatever limit this is? Is there more information I can/should provide? Thanks in advance; please include me in the recipient list of messages on this topic, as I'm not subscribed to x11@. (I've set Reply-To in an attempt to make this less inconvenient.) Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --QPZaqi6af6gbSrAE Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQJ8BAEBCgBmBQJS3wCmXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RThEMDY4QTIxMjc1MDZFRDIzODYzRTc4 QTY3RjlDOERFRjQxOTNCAAoJEIpn+cje9Bk7qmwQAI3HlHkn8MsxOTlaUsD7pdZR eqi+FQ2u0asrn0ewor+if5uhbcLC2wrAyCvzLr4LkUVNBjl2OQIZmunGP4uQKNJk /UEdg5vSFrJ6/VOrtAInqZLMSCoY1566zAh0aVmQbQ7aesucNJTWnn44Rge3Z6VT 2fLAJ4Tk1OJnf1EeO7HD3zVdj6erSRK6rDAHOxK8aoirn7Y+FolipxtcmW0oCbQH vgnfD64Bs+NLcl6TC2EZFdS7egd/8mUmZJkX27+JjtpmtRz+DsabjCZ+GEkZXwHo SPD6KyCKFzzDKcfzLDDgYgWG/DCjKnpfquSSXuRLXSLHqvkL8YtAi6c0XT7Tfmzr JCcmc7fm/7XLAFM9HgY1x/cwWSB8xXKExxBSaxc4s7VWwqDSrHyIEWdDGEhoYK3F +EPkndQayNHHsUGo6T/g0R/SV5EkgOAMAdCf/3O4Kj7el5sz1u7gCVJwFsJyfdIt CIDOMt+4mnVEgAzgqRzZOTh1Pe1dC5SbZzKcB44cP48Vstdgs8ypelXXvA7pbWQf GEJ216WQw4X5cS+MOOJjqwYGRYtBOqJJoy9J1YoSw7EkCVJmRk8JFbBI/WL2fLT4 egjkhEhajLTo01ZR8cb2l6s9EXzgym98v2pJn5Y0iqeM1KDMhTt3qQYz0r9XOqbH BHiXNQIcfSv+x/U81z/2 =GQzz -----END PGP SIGNATURE----- --QPZaqi6af6gbSrAE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140121232008.GM1789>