|
Post by escuelaslinux on Oct 23, 2023 0:03:37 GMT
I think you'll need to go to Menu → Settings → Modules and unload "Keyboard", then go to Menu → Applications → System → Commit Desktop Changes.
Then paste the gsettings command, and finally apply the ibus method you already know. If it works, remember to assign a new shortcut to switch between keyboards.
|
|
|
Post by maxheadroom on Oct 23, 2023 9:49:48 GMT
|
|
|
Post by escuelaslinux on Oct 23, 2023 10:22:07 GMT
I'm not quite sure what's going on here either, but you mentioned that you removed the Spanish keyboard from the ibus method. Maybe if you did that, the Moksha method would work fine now? (go to Menu → Settings → Modules and load "Keyboard").
If the Moksha method still fails, I would suggest going to Menu → Applications → System → Reinstate User - to have the default user account back and also remove any leftover configuration - and then try the ibus method again.
|
|
|
Post by maxheadroom on Oct 23, 2023 10:32:59 GMT
Regarding the problem about the accented letters with the incorporated keyboard, I'm pretty sure it's a bug: I did some troubleshooting and found that to fix it, all you have to do is open the settings and press Apply WITHOUT need to make any changes. The problem is that it reoccurs after reboot, even when Commit changes has been applied. I also tried different computers and keyboards, but they all behave the same.
|
|
|
Post by maxheadroom on Oct 23, 2023 11:16:01 GMT
I'm not quite sure what's going on here either, but you mentioned that you removed the Spanish keyboard from the ibus method. Maybe if you did that, the Moksha method would work fine now? (go to Menu → Settings → Modules and load "Keyboard"). If the Moksha method still fails, I would suggest going to Menu → Applications → System → Reinstate User - to have the default user account back and also remove any leftover configuration - and then try the ibus method again. The Moksha method still fails. The Reinstate user command starts, show the message "Please wait some seconds" and stays that way. I rebooted and tried again, but still the same... Could this do with the fact that I have done the original installation in Greek?
|
|
|
Post by escuelaslinux on Oct 23, 2023 11:30:25 GMT
The accented characters are á é í ó ú? If so, they are Spanish language characters, indeed. Can you open Terminology and type 'cat .Xmodmap' to check what contains that file? if it contains:
keycode 133 = Mode_switch keycode 134 = Mode_switch keysym a = a A aacute Aacute a A keysym e = e E eacute Eacute e E keysym i = i I iacute Iacute i I keysym o = o O oacute Oacute o O keysym u = u U uacute Uacute u U keysym n = n N ntilde Ntilde n N then type 'cp .XmodmapEN .Xmodmap'. It's a long shot, but that file could have been messing somehow with a Greek keyboard layout.
Check if this procedure fixes the issue.
|
|
|
Post by escuelaslinux on Oct 23, 2023 11:40:55 GMT
You should wait until the message goes away. Remember that your computers are a bit old and the seconds may sum some minutes
Indeed, "Please wait some seconds" gives the idea of waiting like some 10 seconds. I'll rephrase that text string for our next version.
|
|
|
Post by maxheadroom on Oct 23, 2023 12:37:55 GMT
The accented characters are á é í ó ú? If so, they are Spanish language characters, indeed. Can you open Terminology and type 'cat .Xmodmap' to check what contains that file? if it contains:
keycode 133 = Mode_switch keycode 134 = Mode_switch keysym a = a A aacute Aacute a A keysym e = e E eacute Eacute e E keysym i = i I iacute Iacute i I keysym o = o O oacute Oacute o O keysym u = u U uacute Uacute u U keysym n = n N ntilde Ntilde n N then type 'cp .XmodmapEN .Xmodmap'. It's a long shot, but that file could have been messing somehow with a Greek keyboard layout.
Check if this procedure fixes the issue.
Believe it or not, this fixes the problem!
|
|
|
Post by escuelaslinux on Oct 23, 2023 12:46:47 GMT
I can't believe it! The accented characters should only appear when the Windows key is pressed, so Win + a = á, Win + e = é...
This is a shortcut meant for our Spanish-speaking users, and I still have no idea how it messes with Greek keyboards, but at least the problem is solved.
|
|
|
Post by maxheadroom on Oct 23, 2023 16:14:27 GMT
You should wait until the message goes away. Remember that your computers are a bit old and the seconds may sum some minutes
Indeed, "Please wait some seconds" gives the idea of waiting like some 10 seconds. I'll rephrase that text string for our next version.
It isn't a too old one actually (Core 2 Duo), but it didn't complete the process within half an hour (tried twice). I then tried on another (i3) and it completed successfully in 2-3 minutes, so it must be something specific to the first one. Can't wait to apply the keyboard fix to all the machines tomorrow, so that we start using them! :-)
|
|
|
Post by escuelaslinux on Oct 23, 2023 20:39:32 GMT
You can use the command line version of ReinstateUser to see possible error messages and troubleshoot what's going on with your Core 2 Duo. On Terminology type:
sudo commandReinstate [enter]
|
|
|
Post by maxheadroom on Oct 24, 2023 9:28:09 GMT
I ran it and it completed in a couple of minutes.
The lab is set and running, as of today. Next step is to set up Veyon to manage the class. Thank you all people for supporting this project!
|
|
|
Post by escuelaslinux on Oct 24, 2023 12:03:29 GMT
Awesome!!!
Remember that an easy way to set up Veyon is documented in the Escuelas Linux installation manual.
|
|
|
Post by escuelaslinux on Oct 24, 2023 17:31:05 GMT
|
|
|
Post by maxheadroom on Oct 25, 2023 10:21:34 GMT
Awesome!!! Remember that an easy way to set up Veyon is documented in the Escuelas Linux installation manual. I need to use Veyon cross-platform. I have two computers on my desk: one running Windows 11 Pro 64-bit and one Windows 7 Pro 64-bit. Can I use them to manage the clients who all run Escuelas 32-bit?
|
|