04-01-2023, 07:50 PM
I seem to be having a few problems with my latest LL conversion from a Windows 7 to LL 6.2 and now 6.4., with some very strange keyboard behaviour.
I’m using the original machine, on which I checked the ram with Memtest86v4, and using a brand new 8TB WD Gold HDD, checked with gsmartcontrol.
I down loaded the LL6.2 from the LL support site, checked the checksum and verified the DVD burn.
And have since upgraded to LL6.4. All seemed to go well, after ignoring the usual update error message, when using the whisker menus LL Update for the first time. A second try produces success, and I ‘m now on LL6.4.
However, by LL6.2 and LL6.4 have the same problem with regard to the keyboard.
LL seems to causing the response of the keyboard output to vary. Sometimes it freezes, and sometimes it has a big delay, resulting in the cursor moving around the screen like ghostly movements, and sometimes missing characters when typing out. As if the process has lost priority, resulting in major lags and lose of response.
I have adjusted keyboard and mouse setting to the same values as a very similar machine that I have, which has been running very successfully on LL4.8 for some time.
Also another strange thing is that the Whisker Menu sometimes pops up by itself, although there might be some loose relationship to the movement of the cursor, but nowhere near the menu area.
Added to which there seems to be a conflict in the setting of the keyboard layout.
During initial installation the option of UK is given, and sure enough when you look at /etc/default/keyboard you do indeed see
XKBMODEL="pc105"
XKBLAYOUT="gb"
But the LL Terminal is set to use the US layout, with no £ and the # in a different place.
However, if you us the
you get a UK layout keyboard on the LL Terminal, but that does not survive a reboot.
The ‘Control Panel/Keyboard/Layout’ is set to ‘Use System Defaults’ as per my other machine, which has a persistent UK layout on both the LL Terminal and in all Apps.
This may or may not have a bearing on the strange keyboard behaviour, but it’s certainly causing me a big headache, in not knowing what to check next.
Can anyone help please.
I’m using the original machine, on which I checked the ram with Memtest86v4, and using a brand new 8TB WD Gold HDD, checked with gsmartcontrol.
I down loaded the LL6.2 from the LL support site, checked the checksum and verified the DVD burn.
And have since upgraded to LL6.4. All seemed to go well, after ignoring the usual update error message, when using the whisker menus LL Update for the first time. A second try produces success, and I ‘m now on LL6.4.
However, by LL6.2 and LL6.4 have the same problem with regard to the keyboard.
LL seems to causing the response of the keyboard output to vary. Sometimes it freezes, and sometimes it has a big delay, resulting in the cursor moving around the screen like ghostly movements, and sometimes missing characters when typing out. As if the process has lost priority, resulting in major lags and lose of response.
I have adjusted keyboard and mouse setting to the same values as a very similar machine that I have, which has been running very successfully on LL4.8 for some time.
Also another strange thing is that the Whisker Menu sometimes pops up by itself, although there might be some loose relationship to the movement of the cursor, but nowhere near the menu area.
Added to which there seems to be a conflict in the setting of the keyboard layout.
During initial installation the option of UK is given, and sure enough when you look at /etc/default/keyboard you do indeed see
XKBMODEL="pc105"
XKBLAYOUT="gb"
But the LL Terminal is set to use the US layout, with no £ and the # in a different place.
However, if you us the
Code:
sudo setxkbmap -layout gb
you get a UK layout keyboard on the LL Terminal, but that does not survive a reboot.
The ‘Control Panel/Keyboard/Layout’ is set to ‘Use System Defaults’ as per my other machine, which has a persistent UK layout on both the LL Terminal and in all Apps.
This may or may not have a bearing on the strange keyboard behaviour, but it’s certainly causing me a big headache, in not knowing what to check next.
Can anyone help please.