Red Hat Bugzilla – Bug 65137
KDE does not honor standard X resources.
Last modified: 2007-04-18 12:42:39 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513
Description of problem:
I just upgraded from RH-7.2 to 7.3. My problem is that, for some reason,
my backspace key no longer works in pine (as well as other problems).
Here's my setup:
I have a correct value set for my XFILESEARCHPATH and my
XUSERFILESEARCHPATH variables. In my $XUSERFILESEARCHPATH I have a file
called XTerm-color and in my .xinitrc I have this one line
xrdb -load ~/.Xresources 2> /dev/null &
My .Xresources simply sez:
* In my XTerm-color I have (among other things)
For some reason, now when I start an xterm, it comes up with 24 lines
instead of the desired 80 and the backarrow key no longer works in pine.
Instead I have to use the ^H key. In fact all of the resource setting I
specify no longer seem to work. The odd thing is that the resources seem
to work fine in gnome. Under KDE, the behavior seems to be broken. I know
there used to be a setting someplace that said something about how
resources should be controlled by kde for non-kde apps.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.xrdb -load ~/.Xresources
This adds the -color value to *customization
2.Make sure that X*FILESEARCHPATH is set to contain %N%C for each directory
3.Result is that X resource files are not honored.
Please note that the value of my directories in XFILESEARCHPATH and
XUSERFILESEARCHPATH all correctly end in /%N%C and that my customization
resource (as specified above) is set to -color
I was able to fix the problem by adding the following lines to startkde after
the call to kdeinit. Here's the associated fragment:
# We set LD_BIND_NOW to increase the efficiency of kdeinit.
# kdeinit unsets this variable before loading applications.
LD_BIND_NOW=true kdeinit +kcminit +knotify || \
xmessage -geometry 500x100 "Couldn't start kdeinit. Check your installation."
# Added by me
if [ -f "$HOME/.Xresources" ]; then
xrdb -merge "$HOME/.Xresources"
# End of Added by me
*** This bug has been marked as a duplicate of 65098 ***