function key events takes time to respond

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Hi,
same bug exists in 9.04

9.04 amd64 on DualCore 4200+ 4 GB ram with load of 20% cpu cores, takes 3.0 - 4.0 seconds to respond to VolumeDown key. Fresh system, Gnome.

I guess desktop should first react to the request (volume down right NOW), and then spend 3 seconds loading fancy GUI...

LimCore, is it applying while your are listening music (in rythmbox for example) ? Is it long too when your computer does nothing (just after booting) ?

assigning to linux
limcore, can you please answer the last question?

It takes 1.0 - 2.0 sec even when not listening to music

Just for first time though, I think the solution would be:
1. to keep this app "in memory" / preloaded if possible
2. to have it first do the volume change, and then display UI
3. to have some locking, what happens if I press the button 5 times, are 5 this apps started, or is just 1?

darx, thank you for reporting this and helping make Ubuntu better. Gutsy reached EOL on April 18th, 2009.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try 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 run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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