Hi,
I'm using Acer Aspire 5672WLMi laptop , I'm trying to get my $ and euro keys to work [both euro and $ keys are on either side of the Up arrow key ]
Now, the weird thing is the $ key triggers a ","
- earlier it did *not* trigger *anything* , previously the $ key just did not work[no output]
I ran $ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p'
it returns:
$ > keycode 129 = (keysym 0xffac, KP_Separator), state = 0x0
euro > keycode 128 = (keysym 0x0, NoSymbol), state = 0x0
something seems to have changed but assigned wrongly, unfortunately i dont know the keycodes/keysym before i tried the wiki
seems my keycodes are *not* outside the keycode range but are not assigned properly...
this is not probably the same bug ! or maybe it is , since i dont know the previous keycodes :(
should i file a separate bug or does anyone know how to fix this?
Hi,
I'm using Acer Aspire 5672WLMi laptop , I'm trying to get my $ and euro keys to work [both euro and $ keys are on either side of the Up arrow key ]
I tired to follow this wiki given on this bug report> /wiki.ubuntu. com/LaptopTesti ngTeam/ AcerAspire5610# %E2%82% AC%20and% 20$%20Keys
https:/
But stopped at the xkeycaps section , since *none* of the keyboard layouts did not match my laptop keyboards , and i didnt want to mess the layout , and didnt do anything further.
Now, the weird thing is the $ key triggers a ","
- earlier it did *not* trigger *anything* , previously the $ key just did not work[no output]
I ran $ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p'
it returns:
$ > keycode 129 = (keysym 0xffac, KP_Separator), state = 0x0
euro > keycode 128 = (keysym 0x0, NoSymbol), state = 0x0
something seems to have changed but assigned wrongly, unfortunately i dont know the keycodes/keysym before i tried the wiki
seems my keycodes are *not* outside the keycode range but are not assigned properly...
this is not probably the same bug ! or maybe it is , since i dont know the previous keycodes :(
should i file a separate bug or does anyone know how to fix this?