Hi Sary, thanks for the prompt response. The first thing I notice is the kernel version you just used is different to the original dmesg:
Original: [ 0.000000] Linux version 3.2.0-23-generic (buildd@crested) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu4) ) #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 (Ubuntu 3.2.0-23.36-generic 3.2.14) [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=daeaa295-5990-4302-a175-fe2559526049 ro quiet splash vt.handoff=7 Now: [ 0.000000] Linux version 3.0.0-19-generic (buildd@vernadsky) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #33-Ubuntu SMP Thu Apr 19 19:05:57 UTC 2012 (Ubuntu 3.0.0-19.33-generic 3.0.27) [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-19-generic root=UUID=710b9731-f503-4f39-8891-b8292e060a73 ro quiet splash vt.handoff=7 This looks to be a two different installations. The original one was using 12.04 Precise, this later one looks to be using 11.10 Oneiric. Is the PC set up for multiple boots into different releases? Second thought regarding dmesg. dmesg used to only capture the initial boot messages which were switched to /var/log/kern.log once the system got going. That has changed with 12.04 so that might explain why - if you're using 11.10 Oneiric now - you don't see the key-scan codes reported in dmesg. To find all occurrences try this: grep -n 'setkeycodes' /var/log/* You may need to prefix that command with 'sudo' if some files aren't accessible to your user account. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/995185 Title: Multimedia keys are disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/995185/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
