Brandon Williams, thank you for reporting this and helping make Ubuntu better. Jaunty reached EOL on October 23, 2010. Please see this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases
We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux <replace-with-bug-number> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag: needs-upstream-testing This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text: needs-upstream-testing If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: kernel-unable-to-test-upstream kernel-unable-to-test-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. Please let us know your results. Thank you for your understanding. Helpful Bug Reporting Tips: https://help.ubuntu.com/community/ReportingBugs ** This bug is no longer a duplicate of bug 295216 Dell Mini 9 & Mini 12 Wireless toggle function key not connected ** Package changed: gnome-control-center (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Low => Medium ** Tags added: needs-kernel-logs needs-upstream-tesing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/367097 Title: custom keyboard shortcut inactive on login Status in “linux” package in Ubuntu: Incomplete Bug description: Binary package hint: gnome-control-center On the Dell mini, the wireless key (Fn+2) issues keycode 171, XF86AudioNext. I have configured a 'Custom Shortcut' with the 'Keyboard Shortcuts' capplet that should run a command to toggle the WLAN state when I press the wireless key. This shortcut is inactive after I log in. If I open the 'Keyboard Shortcuts' capplet, change the short key, and then change it back to XF86AudioNext, the wireless key functions as expected in this session. However, if I log out and log back in, the shortcut key no longer functions and I have to re-enable again in the capplet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/367097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
