In message <[EMAIL PROTECTED]>, Joh n Mills writes: >'startx' still proceeds until it fills all available memory. In >particular, 'top' shows the size of 'xclock' growing while other processes >seem OK. ... >2) Does this [mis]behavior sound familiar to anyone?
I've seen this before when the "fontconfig" system got confused. Try running fc-cache -fv as root. If that doesn't fix it, try: echo "*clock.render: false" >> /usr/X11R6/lib/X11/app-defaults/XClock This second command disables the Xrender extensions in xclock, which I have found necessary on some systems to make xclock work at all. Ian _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"