Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#4690 - Shift+pageup/pagedown not scrolling text in xterm if pointer outside window

Attached to Project: Arch Linux
Opened by Janne Paalijarvi (usv) - Wednesday, 24 May 2006, 00:07 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 29 May 2006, 13:51 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

It is impossible to scroll text in xterm window using shift+pageup/pagedown if mouse pointer is outside the window. If mouse pointer is inside xterm text area, scrolling works ok with the aforementioned keys. It seems to be independent on window manager (happens in KDE and fluxbox, also some people report having this issue with xfce and icewm, but I haven't tested those). This behaviour happens regardless of the focus model, even if "focus follows mouse" and alike is disabled and the window has focus constantly. Shif+pageup/pagedown works flawlessly on konsole, rxvt, urxvt, aterm and mlterm. It was also interesting to notice that what comes to scrolling, xterm binary from Debian Etch works flawlessly straight out-of-the-box :) People reported that the scrolling bug appeared after switching to xorg 7. I cannot confirm this, because I haven't used xorg 6 with Arch Linux.

Specs:
Arch Linux 0.7.2
xorg-11R7.0-1
kdebase-3.5.2-2
fluxbox-0.9.15.1-1
xterm-207-1
bash-3.1.17-1

More info available on request.
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 29 October 2006, 16:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  latest xterm fixes this.
Comment by Jan de Groot (JGC) - Wednesday, 24 May 2006, 06:08 GMT
This is caused by enabling LUIT support in xterm. Disable LUIT and it should be fine. This bug has been reported upstream at Freedesktop AFAIK.

Loading...