Unplugging and re-plugging keyboard forgets xmodmap

Bug #1609900 reported by Saverio Miroddi
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Expired
Low
Unassigned

Bug Description

[I'm not sure against which package I can report this, so I've preliminary done it against `qemu`]

Since I have a non-standard keyboard (a Kinesis, without Super key), I remapped a key on my system (XUbuntu 16.04).
This is accomplished via:

    ~$ cat ~/.Xmodmap
    keycode 108 = Super_L

This works fine, but after any qemu execution, with passthrough of my USB keyboard, the mapping is lost - more precisely, the system it starts behaving like the key is not mapped.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: qemu 1:2.5+dfsg-5ubuntu10.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Aug 4 19:11:24 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-11 (24 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
KvmCmdLine:
 COMMAND STAT EUID RUID PID PPID %CPU COMMAND
 kvm-irqfd-clean S< 0 0 1261 2 0.0 [kvm-irqfd-clean]
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=7f35da3f-4f3a-40e1-8af0-3f02cfbf9884 ro
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A88XN-WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :
Revision history for this message
Phillip Susi (psusi) wrote :

Doesn't that detach the keyboard from your host system in order to pass it through to the guest? Does physically unplugging and re-plugging the keyboard have the same effect?

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

You are correct; this is not a bug.

Changed in qemu (Ubuntu):
status: New → Invalid
Revision history for this message
Phillip Susi (psusi) wrote :

I'm not so sure about that... if unplugging the keyboard and plugging it back in resets the modmap, that sounds like a bug to me. I was just trying to generalize the reproducer; it doesn't have to involve usb pass through to guest vms.

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

> if unplugging the keyboard and plugging it back in resets the modmap, that sounds like a bug to me.

If that's the case (which is a reasonable expectation), the bug should be (re)opened against a difference package (and with a different title).

Revision history for this message
Phillip Susi (psusi) wrote :

Can you try it and see if that is the case? ;)

Revision history for this message
Saverio Miroddi (64kramsystem) wrote :

Tried it already :-)

If I unplug and re-plug the keyboard (outside the QEMU context) I get the same behavior - the xmodmap configuration is lost.

Phillip Susi (psusi)
summary: - After QEMU execution with keyboard passthrough, key mappings are lost
+ Unplugging and re-plugging keyboard forgets xmodmap
affects: qemu (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: Invalid → New
Changed in xorg (Ubuntu):
importance: Undecided → Low
Revision history for this message
Paul White (paulw2u) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this bug report has any relevance when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg (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.