XF86Mail and XF86WWW buttons not launch mail client and web browser
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kubuntu-default-settings (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xorg
XF86Mail and XF86WWW buttons not launch mail client and web browser.
Tested on Kubuntu Maverick and Natty.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSign
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelMo
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 256.53 Fri Aug 27 20:27:48 PDT 2010
GCC version: gcc version 4.4.5 20100909 (prerelease) (Ubuntu/Linaro 4.4.4-14ubuntu1)
Architecture: amd64
Date: Tue Sep 14 08:19:05 2010
DkmsStatus:
virtualbox-ose, 3.2.8, 2.6.35-20-generic, x86_64: installed
nvidia-current, 256.53, 2.6.35-20-generic, x86_64: installed
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
MachineType: Acer, inc. Aspire 5920G
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANGUAGE=
LANG=ru_RU.UTF-8
SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 06/18/2008
dmi.bios.vendor: Acer
dmi.bios.version: v1.3813
dmi.board.name: Chapala
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer, Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Aspire 5920G
dmi.product.
dmi.sys.vendor: Acer, inc.
peripherals:
system:
distro: Ubuntu
codename: maverick
architecture: x86_64
kernel: 2.6.35-20-generic
affects: | xorg (Ubuntu) → nvidia-graphics-drivers (Ubuntu) |
affects: | nvidia-graphics-drivers (Ubuntu) → kubuntu-default-settings (Ubuntu) |
Hey RussianNeuroMancer,
Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?
If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.
If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.
If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.