xmodmap doesn't recognise dead_belowdot

Bug #414784 reported by Matthias-Christian Ott on 2009-08-17
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xkeyboard-config (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: x11-xserver-utils

xmodmap doesn't recognise dead_belowdot (0xfe60):

$ cat .xmodmaprc
keycode dead_belowdot = emdash
$ xmodmap .xmodmaprc
xmodmap: .xmodmaprc:1: bad keysym target keysym 'dead_belowdot', no corresponding keycodes
xmodmap: 1 error encountered, aborting.

xev does so.

Bryce Harrington (bryce) wrote :

Hi matthias-christian,

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

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-xorglog
tags: added: needs-lspci-vvnn
Changed in x11-xserver-utils (Ubuntu):
status: New → Incomplete
Download full text (13.7 KiB)

$ lspci -vvnn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
 Subsystem: Hewlett-Packard Company Device [103c:0934]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
 Latency: 0
 Capabilities: <access denied>
 Kernel modules: intel-agp

00:01.0 PCI bridge [0604]: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port [8086:2591] (rev 03)
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
 I/O behind bridge: 00002000-00002fff
 Memory behind bridge: c8800000-c8bfffff
 Prefetchable memory behind bridge: c0000000-c7ffffff
 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
 BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
  PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
 Capabilities: <access denied>
 Kernel driver in use: pcieport-driver
 Kernel modules: shpchp

00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [8086:2660] (rev 03)
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Bus: primary=00, secondary=10, subordinate=10, sec-latency=0
 Memory behind bridge: c8000000-c83fffff
 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
 BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
  PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
 Capabilities: <access denied>
 Kernel driver in use: pcieport-driver
 Kernel modules: shpchp

00:1c.1 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 [8086:2662] (rev 03)
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Bus: primary=00, secondary=20, subordinate=20, sec-latency=0
 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
 BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
  PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
 Capabilities: <access denied>
 Kernel driver in use: pcieport-driver
 Kernel modules: shpchp

00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 03)
 Subsystem: Hewlett-Packard Company Device [103c:0934]
 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MA...

Download full text (36.1 KiB)

$ cat /var/log/Xorg.0.log

X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server i686 Ubuntu
Current Operating System: Linux marix 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 00:28:35 UTC 2009 i686
Build Date: 09 April 2009 02:10:02AM
xorg-server 2:1.6.0-0ubuntu14 (<email address hidden>)
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
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: Sun Aug 23 11:30:12 2009
(II) Loader magic: 0x3bc0
(II) Module ABI versions:
 X.Org ANSI C Emulation: 0.4
 X.Org Video Driver: 5.0
 X.Org XInput driver : 4.0
 X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 7

(--) PCI:*(0@1:0:0) ATI Technologies Inc M24 1P [Radeon Mobility X600] rev 0, Mem @ 0xc0000000/134217728, 0xc8800000/65536, I/O @ 0x00002000/256, BIOS @ 0x????????/131072
(II) Scanning /usr/share/xserver-xorg/pci directory for additional PCI ID's supported by the drivers
(II) Matched radeon from file name radeon.ids
(==) Using default built-in configuration (39 lines)
(==) --- Start of built-in configuration ---
 Section "Device"
  Identifier "Builtin Default radeon Device 0"
  Driver "radeon"
 EndSection
 Section "Screen"
  Identifier "Builtin Default radeon Screen 0"
  Device "Builtin Default radeon Device 0"
 EndSection
 Section "Device"
  Identifier "Builtin Default ati Device 0"
  Driver "ati"
 EndSection
 Section "Screen"
  Identifier "Builtin Default ati Screen 0"
  Device "Builtin Default ati Device 0"
 EndSection
 Section "Device"
  Identifier "Builtin Default vesa Device 0"
  Driver "vesa"
 EndSection
 Section "Screen"
  Identifier "Builtin Default vesa Screen 0"
  Device "Builtin Default vesa Device 0"
 EndSection
 Section "Device"
  Identifier "Builtin Default fbdev Device 0"
  Driver "fbdev"
 EndSection
 Section "Screen"
  Identifier "Builtin Default fbdev Screen 0"
  Device "Builtin Default fbdev Device 0"
 EndSection
 Section "ServerLayout"
  Identifier "Builtin Default Layout"
  Screen "Builtin Default radeon Screen 0"
  Screen "Builtin Default ati Screen 0"
  Screen "Builtin Default vesa Screen 0"
  Screen "Builtin Default fbdev Screen 0"
 EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default radeon Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default radeon Device 0"
(==) No monitor specified for screen "Builtin Default radeon Screen 0".
 Using a default monitor configuration.
(**) |-->Screen "Builtin Default ati Screen 0" (1)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default ati Device 0"
(==) No monitor specified for screen "Builtin Default ati Screen 0".
 Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (2)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified fo...

Bryce Harrington (bryce) on 2009-11-03
affects: x11-xserver-utils (Ubuntu) → xkeyboard-config (Ubuntu)

@Matthias-Christian Ott: I've setup bug #512622 which in general matters strange xmodmap keymapping.
If You think this affects You, or maybe could solve Your Problem then please strike the apropriate handle ;o))

Maybe many keybord related problems can be solved that way.

Simos Xenitellis  (simosx) wrote :

This is not an xkeyboard-config issue. dead_belowdot was added a few years back to XOrg, however I think the problem is due to the use of xmodmap.

xmodmap lines look like

keycode 176 = XF86AudioRaiseVolume
keycode 174 = XF86AudioLowerVolume

which means you map keycodes to actions. The way you use dead_belowdot I think it not correct.
I am marking this as closed. I might be wrong; in this case reopen.

For more on xmodmap, see http://cweiske.de/howto/xmodmap/allinone.html
In general, you set up hotkeys according to https://wiki.ubuntu.com/Hotkeys/Troubleshooting

Changed in xkeyboard-config (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers