keyboard speed buttons unusable if there is an opened menu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-input-evdev (Ubuntu) |
New
|
Low
|
Unassigned |
Bug Description
Binary package hint: xserver-
If I use a keyborard shorcut (I mean a key as control the volume or open a calculator, these "predefined" keys), it doesn't work if there is a menu opened (neither if it is the applications menu, the sound menu..... one of this panel's included menu make the keyboard "speed" buttons unusable.
I can't update to Trusty actually because of this bug : https:/
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-
ProcVersionSign
Uname: Linux 2.6.35-23-generic i686
Architecture: i386
DRM.card0.
status: disconnected
enabled: disabled
dpms: On
modes:
edid-base64:
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: On
modes:
edid-base64:
Date: Sun Nov 28 16:54:49 2010
DkmsStatus: virtualbox-ose, 3.2.8, 2.6.35-23-generic, i686: installed
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=fr_FR.utf8
SHELL=/bin/bash
SourcePackage: xserver-
dmi.bios.date: 08/13/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0702
dmi.board.
dmi.board.name: M4A77TD PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-23-generic
Changed in xserver-xorg-input-evdev (Ubuntu): | |
status: | Incomplete → New |
status: | New → Confirmed |
tags: | added: saucy |
description: | updated |
Changed in xserver-xorg-input-evdev (Ubuntu): | |
status: | Incomplete → New |
Hey PEIGNOT,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect <bug-number>
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)