[Bug 18019] New: hotkey-setup gives errors, laptop hotkeys dont function in kde

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=18019
Ubuntu | hotkey-setup

           Summary: hotkey-setup gives errors, laptop hotkeys dont function
                    in kde
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: other
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: hotkey-setup
        AssignedTo: mjg59 at codon.org.uk
        ReportedBy: michael at ralston.id.au
         QAContact: kubuntu-bugs at lists.ubuntu.com


I have a Clevo laptop, http://www.clevo.com.tw/products/M375E.asp  
  
When hotkey-setup starts up it gives me the following errors...  
KDSETKEYCODE: Invalid argument  
failed to set scancode 5d to keycode 256  
KDSETKEYCODE: Invalid argument  
failed to set scancode aa to keycode 256  
KDSETKEYCODE: Invalid argument  
failed to set scancode ef to keycode 256  
 
My dmidecode information is fairly sparse... 
        System Information 
                Manufacturer: 
                Product Name: M375E 
                Version: None 
                Serial Number: 12345678 
                UUID: Not Present 
                Wake-up Type: Unknown 
 
When using gnome, the buttons on the front of the laptop function correctly. One launching firefox and the other  
launching evolution. When using KDE these buttons do nothing, I've tried setting them up in kde's control panel, under  
accessibility, keyboard shortcuts and khotkeys but the buttons don't activate the hotkey widget when I try to assign  
them to a function. Not sure if the kde problem is caused by hotkey-setup not working properly... maybe not as the buttons 
do work in gnome.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.