Closed MakaraSok closed 1 year ago
Test specification and instructions
✅ GROUP_BIONIC: Ubuntu 18.04 Bionic with Gnome Shell and X11 ("Ubuntu")
✅ GROUP_FOCAL: Ubuntu 20.04 Focal with Gnome Shell and X11 ("Ubuntu")
✅ GROUP_JAMMY_X11: Ubuntu 22.04 Jammy with Gnome Shell and X11 ("Ubuntu on Xorg")
🟩 GROUP_JAMMY_WAYLAND: Ubuntu 22.04 Jammy with Gnome Shell and Wayland ("Ubuntu") (TEST_OSK currently failing due to #6239)
✅ GROUP_WASTA: Wasta 20.04 with Cinnamon ("Cinnamon (Default)")
✅ GROUP_BIONIC: Ubuntu 18.04 Bionic with Gnome Shell and X11 ("Ubuntu")
✅ GROUP_FOCAL: Ubuntu 20.04 Focal with Gnome Shell and X11 ("Ubuntu")
✅ GROUP_JAMMY_X11: Ubuntu 22.04 Jammy with Gnome Shell and X11 ("Ubuntu on Xorg")
🟩 GROUP_JAMMY_WAYLAND: Ubuntu 22.04 Jammy with Gnome Shell and Wayland ("Ubuntu")
✅ GROUP_WASTA: Wasta 20.04 with Cinnamon ("Cinnamon (Default)")
TEST_INSTALL (PASSED): Successfully installed the Keyman 16.0.39-alpha build as per the instructions.
TEST_START (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_INSTALL (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_ADDED (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_WORKS (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_ICELANDIC (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_INST_PKG (PASSED): Tested this as per the instructions and it is working as expected.
TEST_INSTALL (PASSED): Successfully installed the Keyman 16.0.39-alpha build as per the instructions.
TEST_START (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_INSTALL (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_ADDED (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_WORKS (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_ICELANDIC (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_INST_PKG (PASSED): Tested this as per the instructions and it is working as expected.
TEST_INSTALL (PASSED): Successfully installed the Keyman 16.0.39-alpha build as per the instructions.
TEST_START (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_INSTALL (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_ADDED (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_WORKS (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_ICELANDIC (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KB_INST_PKG (PASSED): Tested this as per the instructions and it is working as expected.
TEST_UI_ABOUT (PASSED): Tested this in Ubuntu Bionic 18.04 Linux OS (Virtual Machine) and it is showing the expected result.
TEST_UI_HELP (PASSED): Tested this in Ubuntu Bionic 18.04 Linux OS (Virtual Machine) and it is showing the expected result.
TEST_UI_OPTIONS (PASSED): Tested this in Ubuntu Bionic 18.04 Linux OS (Virtual Machine) and it is showing the expected result.
TEST_UNINSTALL (FAILED): The removed files are still appears in the mentioned link /usr/lib/python3/dist-packages/keyman_config.
*.kmp files are missing in the subdirectories under ~/.local/share/keyman.
TEST_UNINSTALL (FAILED): The removed files are still appears in the mentioned link /usr/lib/python3/dist-packages/keyman_config.
*.kmp files are missing in the subdirectories under ~/.local/share/keyman.
However, the Keyman_Config folder has been removed from the mentioned link /usr/lib/python3/dist-packages/keyman_config.
*.kmp files are missing in the subdirectories under ~/.local/share/keyman.
TEST_IPA_WRITER (PASSED): Tested this as per the instructions and it is working as expected.
TEST_IPA_GEDIT (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KO_WRITER (FAILED): Tested this as per the instructions and it seems that it is not showing expected output.
TEST_KO_GEDIT (PASSED): Tested this as per the instructions and it is working as expected.
TEST_KM_WRITER (FAILED): Tested this as per the instructions and it seems that it is not showing expected output.
TEST_KM_GEDIT (PASSED): Tested this as per the instructions and it is working as expected.
Ahh, the test instructions were wrong. There are no .kmp files to begin with, so there can't be any after uninstalling :smile: . I updated the instructions to look for .kmx files.
I'm a bit puzzled about the files in /usr/lib/python3/dist-packages/keyman_config
still being there after uninstallation. @bharanidharanj Could you please run the uninstall tests again? You don't have to run it for all groups, you can stop after you get the first failure. Would you please attach the files /var/log/apt/history.log
and /var/log/apt/term.log
from the machine you're getting the failure?
@keymanapp-test-bot retest TEST_UNINSTALL
@ermshiperete Okay. I will run the uninstall test once again and let you know the result. Thanks.
@bharanidharanj Do you still have the Jammy VM in the state where the uninstall failed? If so, could you please run this command and show me the output: apt list python3-keyman-config
@ermshiperete Sure, I will do it.
@ermshiperete Here, is the output for the command apt list python3-keyman-config in Jammy VM,
@bharanidharanj ok, so that's the problem. Somehow pyton3-keyman-config
was not installed as a dependency but explicitly and so it didn't get uninstalled with --autoremove
.
Please uninstall Keyman and then install it again by running these commands:
sudo apt remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0
sudo apt install keyman
then run the test again.
I updated the test instructions and added a sanity check to run before the test.
@keymanapp-test-bot retest SUITE_UNINSTALL GROUP_JAMMY_X11 TEST_UNINSTALL
@bharanidharanj ok, so that's the problem. Somehow
pyton3-keyman-config
was not installed as a dependency but explicitly and so it didn't get uninstalled with--autoremove
.Please uninstall Keyman and then install it again by running these commands:
sudo apt remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0 sudo apt install keyman
then run the test again.
I updated the test instructions and added a sanity check to run before the test.
@keymanapp-test-bot retest SUITE_UNINSTALL GROUP_JAMMY_X11 TEST_UNINSTALL
@ermshiperete
@bharanidharanj ok, so that's the problem. Somehow
pyton3-keyman-config
was not installed as a dependency but explicitly and so it didn't get uninstalled with--autoremove
.Please uninstall Keyman and then install it again by running these commands:
sudo apt remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0 sudo apt install keyman
then run the test again.
I updated the test instructions and added a sanity check to run before the test.
@keymanapp-test-bot retest SUITE_UNINSTALL GROUP_JAMMY_X11 TEST_UNINSTALL
@ermshiperete Okay, I will re-run the test as per your test instructions.
Keyman for Linux Acceptance Test Procedures
>
at the start of a new line under the checkbox to note the result. (For an example, see #3973).General remark to the groups below
The login screen allows you to select different environments by clicking on the cog symbol. Different Ubuntu versions put it in different places and use slightly different icons. In the groups below the menu item to select is put in parenthesis and quotes, e.g. Ubuntu 18.04 Bionic with Gnome Shell and X11 ("Ubuntu").
Gather Assets for Testing
click to expand
Either VM or physical machine will work. - [ ] Ubuntu 18.04 Bionic with Gnome Shell and X11 ("Ubuntu") - [ ] Ubuntu 20.04 Focal with Gnome Shell and X11 ("Ubuntu") - [ ] Ubuntu 22.04 Jammy with Gnome Shell and X11 ("Ubuntu on Xorg")Expand to see how to do and verify this
- when login in, click the cog and select "Ubuntu on Xorg" ![Screenshot from 2022-01-19 18-28-11](https://user-images.githubusercontent.com/181336/150183345-f07c7191-b12b-4739-b4fc-c585148db56c.png) - verify that you're using X11 by running the following command in a terminal: ```bash echo $XDG_SESSION_TYPE ``` This should output `x11`.Expand to see how to do and verify this
- when login in, click the cog and select "Ubuntu" (not "Ubuntu on Xorg") - verify that you're using Wayland by running the following command in a terminal: ```bash echo $XDG_SESSION_TYPE ``` This should output `wayland`.Setup Steps
click to expand
- [ ] Install latest updates on the system: ```bash sudo apt update sudo apt --autoremove upgrade ``` On Ubuntu 18.04 Bionic use the following commands instead: ```bash sudo apt update sudo apt upgrade sudo apt autoremove ``` - [ ] Uninstall previous versions of Keyman for Linux on the system: ```bash sudo apt --autoremove remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0 ``` On Ubuntu 18.04 Bionic use these commands instead: ```bash sudo apt remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0 sudo apt autoremove ``` - [ ] Remove left-over artifacts by running: ```bash rm -rf ~/.local/share/keyman/ sudo rm -rf /usr/local/share/keyman/ ``` - [ ] Remove all keyboards from Input Sources that except "English (US)" - From Ubuntu, start "Settings" --> "Region & Language" (in newer Ubuntu versions: "Settings" --> "Keyboard") - On Wasta Linux, open IBus Keyboards instead --> Input Method tab - [ ] Add the ppa (for pre-beta tests, replace `keyman-beta` with `keyman-alpha`): ```bash sudo add-apt-repository ppa:keymanapp/keyman-beta sudo apt update ``` - [ ] Add a second non-Keyman keyboard so that the language/keyboard dropdown shows (these are the steps for Ubuntu; for Wasta they are similar):Expand to see the steps
- From Ubuntu, start "Settings" --> "Region & Language" (in newer Ubuntu versions: "Settings" --> "Keyboard"; on Wasta Linux open IBus Preferences which can be opened by typing "ibus keyboards"). - Below "Input Sources" click the "+" and then the three dots: ![Screenshot from 2022-02-03 11-46-53](https://user-images.githubusercontent.com/181336/152328230-8c70fe5a-32fb-4090-a50b-272300d82df7.png) - in the search field, type "French" (or any other language), "Other" and then of the French keyboards and finally the "Add" button. ![Screenshot from 2022-02-03 11-50-06](https://user-images.githubusercontent.com/181336/152328628-f578b3b3-250a-45f1-89de-f0bc8e1c43b6.png) - now the language/keyboard dropdown will show. If not, reboot. ![Screenshot from 2022-02-03 11-51-24](https://user-images.githubusercontent.com/181336/152329086-ede2657f-ad4d-4b17-bd1d-b24a8d3e3839.png)Expand to see the steps
- In LO Tools/Options, go to the Language Settings/Languages tab. Under "Default Languages for Documents" check the box for "Asian" and select "Korean (RoK)" as language, and check "Complex text layout" and select "Khmer" as language. ![Screenshot from 2022-06-23 12-13-56](https://user-images.githubusercontent.com/181336/175276071-2fda6202-b2a2-498a-9638-517409e68dcb.png) - You'll also have to change the default style: go to Styles/Manage Styles, right-click on "Default Paragraph Style" and select Modify. Go to the Font tab. For Asian Text Font, select Family "NanumMyeongjo" and Language "Korean (RoK)". For CTL Font, select Family "Khmer Mondulkiri" (or another "Khmer" font) and Language "Khmer". ![Screenshot from 2022-06-23 12-11-35](https://user-images.githubusercontent.com/181336/175275721-d3b282e0-4efc-42b8-89aa-493468981141.png)User Testing
click to expand
## SUITE_INSPECT: Visual Inspection of master/beta branches - **TEST_CI_MASTER**: Verify the master build for Linux reports green on