On Tue, May 11, 2021 at 10:59:16AM +0200, Philipp Marek wrote: > > It's possible that you have some font resource (such as a proportional > > font) which confuses it, causing it to write outside its window. > > XTerm*faceName: DejaVu Sans Mono actually Xaw uses only bitmap fonts (though some versions of fontconfig can be told to offer those fonts...) Thinking that locale might be a clue, I tried setting it to de_AT.UTF-8, without seeing any problems. > > But that would be apparent in xterm (thinking that a wildcard font > > resource which affects one would affect both). > > > > Given that, I'm expecting that the answer is that the X server > > (for some less-used device) is not handling the window properly. > > Hmmm.... > > 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev > 07) I can't tell :-( That gets into hardware dependencies. In your first comment, you mentioned "the few existing pixels blink". That makes it sound like the X server (since the contents of the window from xterm's point of view are generally static, unless programmed to blink using an escape sequence). If this had been simply a missing border, I'd ask about the window manager (noting that on a couple of machines, I see the gnome stuff overriding the resource-settings, while most window managers leave that alone). Then again (one of those was Fedora34, whose effect was apparent because it took about a second to _redraw_ the menu border), you might be using some version of gnome-session/-shell/-whatever, which has bugs in its attempt to redraw the border. If that's the case, trying a different window manager (xfce4 for instance) would show if the window manager is the appropriate place to go. (xterm has had its own problems with drawing, but so far this doesn't match any of the situations where I would assume xterm's at fault) -- Thomas E. Dickey <dickey@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net
Attachment:
signature.asc
Description: PGP signature