SOLVED: Problem with X resources on upgrade to RH-7.3/KDE-3.0.0-5

James Richard Tyrer tyrerj at acm.org
Sat May 18 10:33:48 BST 2002


"Steven W. Orr" wrote:
> 
> On Fri, 17 May 2002, Steven W. Orr wrote:
> 
> =>This is complicated to explain, but please bear with me.
> =>
> =>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

Are you starting X from the command line in the console with: "startx"?

Because "~/.xinitrc" only gets run when X is started with: "startx".  If
you start with the GUI login, it won't work.

> =>
> =>xrdb -load ~/.Xresources 2> /dev/null &
> =>
> =>My .Xresources simply sez:
> =>*customization: -color
> =>*StringConversionWarnings: on
> =>
> =>* In my XTerm-color I have (among other things)
> =>*VT100*backarrowKey: true
> =>*VT100.geometry:     80x72
> =>
> =>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.  

<SNIP>

> =>Can someone please tell me what I'm doing wrong here?

> Turns out to be a bug in the startkde script. 

Sorry, this isn't a bug in the: "startkde" script.

> Make your own personal 
> copy of the script and add the following line *after* the call to 
> kdeinit:
> 
>     xrdb -merge "$HOME/.Xresources"
> 
> A bug has been submitted to bugzilla #65137 and can be viewed at
> 
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=65137

But, IMHO, this may be an issue.  When you start an X session with KDM
or XDM -- that is, after you login, it runs a script: "Xsession" this
script should include the following:

----------------------------------------------------------------

if [ -f /etc/X11/Xmodmap ]; then
    xmodmap /usr/etc/X11/Xmodmap
fi

if [ -f ~/.Xmodmap ]; then
    xmodmap ~/.Xmodmap
fi

if [ -f /etc/X11/xdm/Xdefaults ]; then
    xrdb -merge /etc/X11/xdm/Xdefaults
fi

if [ -f ~/.Xdefaults ]; then
    xrdb -merge ~/.Xdefaults
fi

if [ -f /etc/X11/xdm/Xresources ]; then
    xrdb -merge /etc/X11/xdm/Xresources
fi

if [ -f ~/.Xresources ]; then
    xrdb -merge ~/.Xresources
fi

----------------------------------------------------------------

This is where your various parameters should be read in.

> Red Hat: Please fix this. Lots of things depend on X resources working
> properly. This bug broke all of the resources that I set in my resource
> files including xterm, emacs, xmris, xload, xlogo, xdvi, and bitmap. It 
> is unacceptable to have to do an xrdb -load on a resource file at 
> startup.
> 
So, you can check your file: "Xsession" and see if that is the actual
problem.

--
JRT
___________________________________________________
This message is from the kde mailing list.
Account management:  http://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.




More information about the kde mailing list