Page Down button does not work in X.

Bug #261361 reported by psanford
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After upgrading to Intrepid, the page down button on my keyboard doesn't work anymore in X.
It does work in the console. I tried both Evden and Generic 105 layouts.

Revision history for this message
Brian Murray (brian-murray) wrote : Package assigned

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in xorg.

Revision history for this message
Brian Murray (brian-murray) wrote : Need more information

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please add your '/etc/X11/xorg.conf' file and your '/var/log/Xorg.0.log' file as attachments to your bug report? Thanks in advance.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in xorg:
status: Incomplete → Invalid
Revision history for this message
Pander (pander) wrote :

Same problem for me after upgrading from Hardy to Interpid. DOWN and sometimes PAGE UP, PAGE DOWN and END don't work.

Changed in xorg:
status: Invalid → New
Revision history for this message
Pander (pander) wrote :
Download full text (16.8 KiB)

/etc/X11/xorg.conf

# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# Note that some configuration settings that could be done previously
# in this file, now are automatically configured by the server and settings
# here are ignored.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
 DefaultDepth 24
EndSection

Section "Module"
 Load "glx"
EndSection

Section "Device"
 Identifier "Configured Video Device"
 Driver "nvidia"
 Option "NoLogo" "True"
EndSection

/var/log/Xorg.0.log

X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
Current Operating System: Linux katana 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686
Build Date: 24 October 2008 08:00:16AM
xorg-server 2:1.5.2-2ubuntu3 (<email address hidden>)
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 18 16:25:40 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) No Layout section. Using the first Screen section.
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Configured Monitor"
(**) | |-->Device "Configured Video Device"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) No FontPath specified. Using compiled-in default.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
 Entry deleted from font path.
(==) FontPath set to:
 /usr/share/fonts/X11/misc,
 /usr/share/fonts/X11/100dpi/:unscaled,
 /usr/share/fonts/X11/75dpi/:unscaled,
 /usr/share/fonts/X11/Type1,
 /usr/share/fonts/X11/100dpi,
 /usr/share/fonts/X11/75dpi,
 /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
 If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81d9a40
(II) Module ABI versions:
 X.Org ANSI C Emulation: 0.4
 X.Org Video Driver: 4.1
 X.Org XInput driver : 2.1
 X.Org Server Extension : 1.1
 X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 7

(--) PCI:*(0@1:0:...

Revision history for this message
Pander (pander) wrote :

Also .Xmodmap
keycode 115 = Multi_key
keycode 116 = Multi_key
is not being picked up by GNOME, normally GNOME asked one time to load this or not.

Revision history for this message
psanford (pms-mail) wrote :

The some of the keycodes. changed between 8.04 and 8.10. I had the super key and caps lock remapped in my .xmodmap. After the upgrade one of those keybindings went to pagedown. Rewriting my .xmodmap fixed it for me.

Revision history for this message
Pander (pander) wrote :

I was able to map compose wot windows keys via GNOME System / Preferences / Keyboard / Layout / Other Options / Compose key position:
  Left Win-key is Compose.
  Right Win-key is Compose.

What is your .xmodmap, or is it better to remove it and use the above lines?

Also I had to 'Enable support to enter complex characters' in Language settings. This also didn't migrate well in Interpid upgrade. But let's not get too far off topic...

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

Hi pms-mail,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

Changed in xorg:
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in xorg:
status: Incomplete → Invalid
Revision history for this message
Fraser Hanson (fraser-hanson) wrote :

I currently have this bug on two different machines.
Both have had it since upgrading to Intrepid.
Both machines have NVIDIA video cards, and use the proprietary NVIDIA driver. I had always assumed that this was to blame, rather than xorg itself.

The pagedown key stops working at apparently random intervals. Sometimes it stops working after a few seconds, sometimes it might stay working for an hour or so.

I can temporarily restore the pagedown key by running the following command:
    setxkbmap -model evdev

No log messages are generated in /var/log/Xorg.0.log when the problem occurs, nor are any log messages generated by the temporary fix.

I have no .xmodmap file on either of my computers.

Attached is my custom xorg.conf from one of my computers.

Revision history for this message
Fraser Hanson (fraser-hanson) wrote :

Attached is output from lspci -vvnn.

Revision history for this message
Fraser Hanson (fraser-hanson) wrote :

Attached is an Xorg.0.log file.

Changed in xorg:
status: Invalid → New
Bryce Harrington (bryce)
Changed in xorg-server:
status: New → Confirmed
Revision history for this message
Fraser Hanson (fraser-hanson) wrote :
Download full text (3.1 KiB)

It appears that (for today at least) I can trigger the bug at will by starting a new shell. The PgDown command consistently breaks within a few seconds after creating a new tab in gnome-terminal. I don't know if this is a repeatable pattern that I never noticed before, or a change. Today I was playing with my .inputrc and spawning a new shell every 30 seconds or so for testing, when I noticed I was hitting the PgDown bug more often, and spotted the pattern.

Anyway, I took advantage of the repeatability to play with the bug a bit. One revealing bit of information is that xev shows different output for the PgDown key when the bug is in effect. It appears that the PgDown keypress is interpreted as a Control_R.

Here is the normal xev output from working PgUp and PgDown keys (in that order):

KeyPress event, serial 36, synthetic NO, window 0x4400002,
    root 0x32b, subw 0x4400003, time 3031580169, (63,59), root:(68,132),
    state 0x0, keycode 112 (keysym 0xff55, Prior), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 36, synthetic NO, window 0x4400002,
    root 0x32b, subw 0x4400003, time 3031580346, (63,59), root:(68,132),
    state 0x0, keycode 112 (keysym 0xff55, Prior), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 36, synthetic NO, window 0x4400002,
    root 0x32b, subw 0x4400003, time 3031582168, (63,59), root:(68,132),
    state 0x0, keycode 117 (keysym 0xff56, Next), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 36, synthetic NO, window 0x4400002,
    root 0x32b, subw 0x4400003, time 3031582306, (63,59), root:(68,132),
    state 0x0, keycode 117 (keysym 0xff56, Next), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Output when the PgDown bug is in effect:

KeyPress event, serial 30, synthetic NO, window 0x4400002,
    root 0x32b, subw 0x0, time 3031655267, (620,735), root:(625,808),
    state 0x0, keycode 112 (keysym 0xff55, Prior), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x4400002,
    root 0x32b, subw 0x0, time 3031655429, (620,735), root:(625,808),
    state 0x0, keycode 112 (keysym 0xff55, Prior), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 33, synthetic NO, window 0x4400002,
    root 0x32b, subw 0x0, time 3031656307, (620,735), root:(625,808),
    state 0x0, keycode 117 (keysym 0xffe4, Control_R), same_screen YES,
    XKeysymToKeycode returns keycode: 105
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x4400002,
    root 0x32b, subw 0x0, time 3031656403, (620,735), root:(625,808),
    state 0x0, keycode 117 (keysym 0xffe4, Control_R), same_screen YES,
    XKeysymToKeycode returns keycode: 105
    XLookupString gives 0 bytes:
    XFilterEven...

Read more...

Revision history for this message
Fraser Hanson (fraser-hanson) wrote :

I have resolved my issue. It turns out to have been a local configuration issue.

Although I did not have a ~/.xmodmap file, I did have an xmodmap command in my ~/.bashrc which was intended to disable the Menu key in between R_Super and R_Control. Apparently the keycode for Menu must have changed somewhere in all the Xorg reworking, because this used to succesfully remap Menu but now remaps PageDown.

So this one is my fault, and the issue is resolved on both of my boxes. As far as I'm concerned this bug can be closed again.

Bryce Harrington (bryce)
tags: added: intrepid
Revision history for this message
Karl Berg (kalle465) wrote :

I am using jaunty and to me this seems like a bug in the Regional & Language settings page in KDE.
The command created by my settings is:

setxkbmap -model evdev -layout se -variant

which gives the following error when running on command line:

No layout variant specified on the command line
Trailing -variant option ignored

Removing the -variant option solves the problem.

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi psanford,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 261361

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 261361 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/261361

Changed in xorg-server (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.