Comment 28 for bug 421261

On Sat, 9 Jan 2010, Bryce Harrington wrote:

> On Sat, Jan 09, 2010 at 02:09:14AM -0000, Thomas Dickey wrote:
>> On Sat, 9 Jan 2010, Bryce Harrington wrote:
>>> Well, I'm out of clue. I don't see where we have anything different
>>> from debian for the Xresources for this. I don't have a ~/.Xdefaults,
>>> and the x11-common resource file is the same as from debian.
>> If I had something like that where I could test it, I'd see if I could use
>> strace to show which files were opened on startup. iirc, a setting from
>> xrdb wouldn't show up in this way, but resource settings would.
>> (For this purpose, xterm runs fine without setgid, in case that
>> interferes).
>> something like
>> strace -tfo foo.out xterm
>> would show that. (I expect it to be large - compressed attachments are
>> nice ;-). Tweaking uxterm to get the same information can be done by
>> editing the last line of the script.
> Here is strace from xterm and uxterm.

ok (nothing unexpected there - based on the report). On my machine,
running fvwm2, "xrdb -q" gives

*customization: -color
Kinput2*CcWnn.ccdef: ccdef.kinput2.egg
XLock*logoutButton: -1

(I checked also that none of my files would be setting the resource).

My /etc/X11/Xresources/x11-common file has this:

! $Id$

! load color-specific resources for clients that have them
#ifdef COLOR
*customization: -color

! make Xaw (Athena widget set) clients understand the delete key
! this causes problems with some non-Xaw apps, use with care
! *Text.translations: #override ~Shift ~Meta <Key>Delete: delete-next-character()

The resources for xterm assume that "*customization:color" is set, while
uxterm - because it borrows the XTerm resource file also is including
XTerm-color (to resolve some long-ago problem in getting the color

If your "xrdb -q" doesn't show the resource, then the session manager (or
whatever) is not loading it. (In a quick read of the bug report, I don't
see which window manager is being used - KDE or GNOME, I suppose).

Thomas E. Dickey