Bug 1161111

Summary: YaST Caller: /usr/share/YaST2/modules/Keyboard.rb:306:in `current_kbd'
Product: [openSUSE] openSUSE Distribution Reporter: Axel Braun <axel.braun>
Component: YaST2Assignee: E-mail List <yast2-maintainers>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: ancor
Version: Leap 15.2   
Target Milestone: ---   
Hardware: aarch64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: screenshot of error message
y2logs

Description Axel Braun 2020-01-16 15:15:47 UTC
Created attachment 827676 [details]
screenshot of error message

Having zypper dupped the LXQT Raspi Image from 15.1 to 15.2, and trying to start yast2 language results in the above error message.
y2 logs and screenshot attached

gnuhealth-raspi:/home/test # rpm -qa | grep yast2
yast2-online-update-4.2.2-lp152.1.1.noarch
yast2-transfer-4.1.0-lp152.2.2.aarch64
yast2-users-4.2.6-lp152.1.1.aarch64
yast2-scanner-4.2.0-lp152.1.2.aarch64
patterns-yast-yast2_basis-20190411-lp152.1.2.aarch64
yast2-4.2.47-lp152.1.1.aarch64
yast2-installation-4.2.25-lp152.1.1.noarch
yast2-online-update-frontend-4.2.2-lp152.1.1.noarch
yast2-theme-oxygen-4.2.5-lp152.1.1.noarch
yast2-tftp-server-4.2.0-lp152.1.1.noarch
yast2-auth-server-4.2.3-lp152.1.1.noarch
yast2-configuration-management-4.2.2-lp152.1.1.noarch
yast2-slp-4.1.1-lp152.1.1.aarch64
yast2-ruby-bindings-4.2.5-lp152.1.1.aarch64
yast2-ntp-client-4.2.6-lp152.1.1.noarch
yast2-sudo-4.2.1-lp152.1.1.noarch
yast2-perl-bindings-4.1.0-lp152.2.2.aarch64
yast2-firstboot-4.2.4-lp152.1.1.noarch
yast2-qt-branding-openSUSE-15.2-lp152.1.2.noarch
yast2-support-4.2.3-lp152.1.1.noarch
yast2-nis-client-4.2.1-lp152.1.1.aarch64
yast2-theme-breeze-4.2.5-lp152.1.1.noarch
yast2-apparmor-4.2.1-lp152.1.1.noarch
yast2-pam-4.2.4-lp152.1.1.noarch
yast2-security-4.2.7-lp152.1.1.noarch
yast2-vm-4.2.3-lp152.1.1.aarch64
yast2-snapper-4.2.0-lp152.1.1.aarch64
autoyast2-installation-4.2.23-lp152.1.1.noarch
yast2-trans-en_GB-84.87.20190511.bc4a9329cc-lp152.2.2.noarch
yast2-mail-4.2.2-lp152.1.1.noarch
yast2-alternatives-4.2.2-lp152.1.1.aarch64
yast2-packager-4.2.37-lp152.1.1.aarch64
yast2-country-data-4.2.10-lp152.1.1.aarch64
yast2-logs-4.2.47-lp152.1.1.aarch64
yast2-sound-4.2.2-lp152.1.2.aarch64
yast2-python3-bindings-4.1.1-lp152.1.1.aarch64
yast2-metapackage-handler-4.1.0-lp152.2.2.noarch
yast2-x11-4.1.0-lp152.2.2.aarch64
yast2-trans-en-84.87.20190511.bc4a9329cc-lp152.2.2.noarch
yast2-proxy-4.2.2-lp152.1.1.noarch
yast2-network-4.2.35-lp152.1.1.noarch
yast2-ldap-4.1.0-lp152.2.2.aarch64
yast2-vpn-4.2.3-lp152.1.1.noarch
yast2-add-on-4.2.13-lp152.1.1.noarch
yast2-theme-4.2.5-lp152.1.1.noarch
yast2-journal-4.2.2-lp152.1.1.noarch
yast2-tune-4.2.2-lp152.1.1.aarch64
yast2-xml-4.1.1-lp152.1.1.aarch64
yast2-pkg-bindings-4.2.3-lp152.1.1.aarch64
yast2-storage-ng-4.2.60-lp152.1.1.aarch64
yast2-country-4.2.10-lp152.1.1.aarch64
yast2-firewall-4.2.2-lp152.1.1.noarch
yast2-samba-client-4.2.2-lp152.1.1.noarch
yast2-control-center-qt-4.2.2-lp152.1.2.aarch64
yast2-samba-server-4.2.2-lp152.1.1.noarch
yast2-services-manager-4.2.5-lp152.1.1.noarch
yast2-update-4.2.12-lp152.1.1.aarch64
yast2-iscsi-client-4.2.2-lp152.1.1.noarch
yast2-core-4.1.0-lp152.2.2.aarch64
yast2-trans-stats-2.19.0-lp152.3.2.noarch
yast2-sysconfig-4.2.1-lp152.1.1.noarch
yast2-auth-client-4.2.2-lp152.1.1.noarch
yast2-bootloader-4.2.13-lp152.1.1.aarch64
yast2-printer-4.2.0-lp152.1.2.aarch64
yast2-control-center-4.2.2-lp152.1.2.aarch64
yast2-hardware-detection-4.1.1-lp152.1.2.aarch64
yast2-ycp-ui-bindings-4.2.3-lp152.1.1.aarch64
yast2-nfs-client-4.2.3-lp152.1.1.noarch
yast2-nfs-common-4.2.2-lp152.1.1.noarch
Comment 1 Axel Braun 2020-01-16 15:17:50 UTC
Created attachment 827677 [details]
y2logs
Comment 2 Ancor Gonzalez Sosa 2020-01-16 21:16:53 UTC
This is a duplicate (see bug#1159286 for details). The bug is already fixed in yast2-country 4.2.14

*** This bug has been marked as a duplicate of bug 1159286 ***