Red Hat Bugzilla – Bug 75666
PgUp/PgDn keys not working in xterm
Last modified: 2014-03-16 22:31:37 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830
Description of problem:
When the num lock key is off I can't get the PgDn and PgUp keys to work properly
in xterm. In joe and such they don't work, except as said, if num lock is on.
For root, as by default his .Xresources defines PgDn and PgUp as prior/next, I
can't get them to work even if num lock is on. The workaround is of course
obvious but nevertheless it is rather annoying.
Steps to Reproduce:
2.Open joe with some text file
3.Try to scroll down using PgDn
4.Turn on num lock
5.Try to scroll down again
Actual Results: After 3 nothing happens. After 5 it works.
With the default config this only happens to root because of the
<KeyPress>Prior/Next lines in .Xresources not with other users (was happening to
me because I had pasted some of root's .Xresources definitions to
/etc/X11/Xresources). Anyway with this config root isn't able to use PgUp/PgDn
except to scroll back and forth between xterm's pages themselves.
I guess this belongs to rootfiles then.
All xterm bug reports should be filed directly to XFree86.org, as Red Hat
does not support xterm. xterm is provided only for end user convenience.
The preferred terminals are gnome-term and konsole.
You can report your bug to xterm developers by emailing firstname.lastname@example.org
Since this turned out to be (IMHO) merely a config file problem with the
.Xresources from redhat's rootfiles package I think there is nothing to report
to XFree86.org then.
As I mentioned previously, I think the problem is in the .Xresources file that
Red Hat distributes in the rootfiles package not xterm, so and also because it
is so easily fixed with no loss of functionality (scroll in xterm with
Shift-PgUp/Dn instead of only PgUp/Dn) I'm reopening the bug.
Reassigning to package owner.
Same problem in Red Hat 9.
Same problem in Fedora Core 2.
Removing .Xresources; there's no reason for it to be different for
root than for other users.