I am using xterm 223. Attempting to access xterm main settings with ctrl+left_click will cause xterm to hang for a few seconds and no settings menu will appear. Doing ctrl+left_click again will bring up the main settings menu. Bug 113592 states that this is fixed but the problem is still happening for me. Problem has started happening after switching to unicode locale.
We really can't do anything about this, not a Gentoo issue, and not much of an xterm issue as well... Also it doesn't really freeze, just press Ctrl and *hold* the mouse button until the menu actually appears, it takes some time. It would need to be fixed in x11-libs/libXaw, so this should be marked UPSTREAM.
(In reply to comment #1) > We really can't do anything about this, not a Gentoo issue, and not much of an > xterm issue as well... Also it doesn't really freeze, just press Ctrl and > *hold* the mouse button until the menu actually appears, it takes some time. > > It would need to be fixed in x11-libs/libXaw, so this should be marked > UPSTREAM. > It does freeze for me. In fact, all of X seems to freeze. I can't change virtual desktops, open new programs, or perform any basic operations. CPU usage spikes to 100%. Holding the mouse button doesn't seem to make a difference.
Someone suggested that I force the menus to initialize in a POSIX locale. It's on my to-do list to implement as an optional feature.
(In reply to comment #3) > Someone suggested that I force the menus to initialize in > a POSIX locale. It's on my to-do list to implement as > an optional feature. > It's not clear to me whether that would fix the issue above. Would it?
It might fix it (something in that area - I would have thought it was the choice of fonts, but some comments I've seen indicate it may be up a level, in how the characters are laid out with respect to the locale setting). It wouldn't fix it for cases where the menu labels are localized, but assuming no bad side effects crop up, would be useful for people who use the default menu labels which are all in 7-bit ASCII.
I added that (menuLocale resource) in #224. This is not a performance issue on my boxes, but tracing through the X code, I can see that in a UTF-8 locale, the Xaw code (because of some side-effect of the pixmap support!) is loading a font-set which covers all of the "useful" fonts for the given locale. That is done once - so setting the locale during the menu loading to "C" eliminates the font-sets.
Seems to work fine for me with version #243, closing as TEST-REQ.. reopen if it's still an issue.
