When adding a specific routing instructions via the Yast network configuration tool how to find a different subnet, the information did not show up when calling the "ip route" command. Specifically, the machine has two network devices (eth0, eth1) with specific addresses 192.168.1.10 on eth0 and 192.168.2.20 on eth1 with the 192.168.1.0/24 being the default route. I want to declare a path to a third network 192.168.3.0/24 through the interface 192.168.2.0/24 on eth1 device. I added a line in the Yast configuration tool in the System->Network Settings -> Routing tab for the routing table, with the content: Default route (disabled) Destination: 192.168.3.0/24 Gateway: 192.168.2.1 Device: eth1 Options: (no entry) This information did not show up when issueing the ip route command. Response was: default via 192.168.1.10 dev eth0 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.10 192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.20 Is there a particular trick to ensure that routing information (target address range, gateway, device, options) entered in Yast gets recognized? Rebooting did not seem to do the job. When adding the routing information manually via ip route add 192.168.3.0/24 via 192.168.2.1 dev eth1 where 192.168.2.1 is a router serving the eth1 device, things worked nicely, but it would be great if this does not need to be done after every reboot... Is there a particular place to look for documentation ofh yast on such issues? Thanks!!

I'm running openSUSE Leap 15.5 on a Dell laptop connected to my broadband router by both Ethernet over power line and Wi-Fi. When I power up my laptop and log in, Internet access is very slow for a while. Investigation reveals that some program is using all the available download bandwidth. Since the Internet speeds up as soon as YaST tells me how many updates I have available, I suspect that the culprit is YaST checking for updates. Is there a way to limit the amount of Internet bandwidth that a particular program (YaST in this case) is allowed to use so that other activities are not slowed down? I could presumably disable YaST's automatic check for updates, but then I would not get informed when important security updates are available.

I receive the following error message from the Software Updates function in Open Suse Leap:

There is no update candidate for kernel-default-devel-5.14.21-150500.55.68.1.x86_64

This happens if I try to apply all available updates, which always (probably since I updated to 15.5) include updates for `kernel-devel and kernel-default-devel, both to version 5.14.21-150500.53.2`. However YasT package management, under Multiversion packages, tells me that I only have 55.65 and 55.68 installed; these are also the only versions explicitly mentioned in my boot menu. I have to manually exclude these two packages for the rest of the updates to succeed. What can I do to: * avoid these messages, * ensure that my updates work normally, * (avoid messing up my bootloader), and * if desirable, clean up any detritus from my system? I forget why I installed these `-devel` packages, but I think it may have been because they provided files needed to build some software — or even out of simple curiosity. ## Listings (I am sorry about the German in some of these listings; I have several languages installed, and for some reason it often uses German instead of English!) `pjtraill@PatrickLaptopLinux:~> zypper search /^kernel/`

S  | Name                                 | Summary                                                       | Type
---+--------------------------------------+---------------------------------------------------------------+-----------
   | kernel-64kb                          | Kernel with 64kb PAGE_SIZE                                    | Quellpaket
   | kernel-azure                         | Kernel for MS Azure cloud                                     | Paket
   | kernel-azure                         | Kernel for MS Azure cloud                                     | Quellpaket
   | kernel-azure-devel                   | Development files necessary for building kernel modules       | Paket
   | kernel-azure-extra                   | Kernel for MS Azure cloud - Unsupported kernel modules        | Paket
   | kernel-azure-livepatch-devel         | Kernel symbols file used during kGraft patch development      | Paket
   | kernel-azure-optional                | Kernel for MS Azure cloud - Optional kernel modules           | Paket
   | kernel-azure-vdso                    | vdso binaries for debugging purposes                          | Paket
   | kernel-debug                         | A Debug Version of the Kernel                                 | Paket
   | kernel-debug                         | A Debug Version of the Kernel                                 | Quellpaket
   | kernel-debug-devel                   | Development files necessary for building kernel modules       | Paket
   | kernel-debug-livepatch-devel         | Kernel symbols file used during kGraft patch development      | Paket
   | kernel-debug-vdso                    | vdso binaries for debugging purposes                          | Paket
i+ | kernel-default                       | The Standard Kernel                                           | Paket
   | kernel-default                       | The Standard Kernel                                           | Quellpaket
   | kernel-default-base                  | The Standard Kernel - base modules                            | Paket
   | kernel-default-base                  | The Standard Kernel - base modules                            | Quellpaket
   | kernel-default-base-rebuild          | Empty package to ensure rebuilding kernel-default-base in OBS | Paket
i+ | kernel-default-devel                 | Development files necessary for building kernel modules       | Paket
i+ | kernel-default-extra                 | The Standard Kernel - Unsupported kernel modules              | Paket
   | kernel-default-livepatch             | Metapackage to pull in matching kernel-livepatch package      | Paket
   | kernel-default-livepatch-devel       | Kernel symbols file used during kGraft patch development      | Paket
i+ | kernel-default-optional              | The Standard Kernel - Optional kernel modules                 | Paket
   | kernel-default-vdso                  | vdso binaries for debugging purposes                          | Paket
i+ | kernel-devel                         | Development files needed for building kernel modules          | Paket
   | kernel-devel-azure                   | Development files needed for building kernel modules          | Paket
   | kernel-devel-rt                      | Development files needed for building kernel modules          | Paket
   | kernel-docs                          | Kernel Documentation                                          | Paket
   | kernel-docs                          | Kernel Documentation                                          | Quellpaket
   | kernel-docs-html                     | Kernel Documentation (HTML)                                   | Paket
   | kernel-firmware                      | Linux kernel firmware files                                   | Paket
   | kernel-firmware                      | Linux kernel firmware files                                   | Quellpaket
i+ | kernel-firmware-all                  | Compatibility metapackage for kernel firmware files           | Paket
i+ | kernel-firmware-amdgpu               | Kernel firmware files for AMDGPU graphics driver              | Paket
i+ | kernel-firmware-ath10k               | Kernel firmware files for Atheros QCA988x WiFi drivers        | Paket
i+ | kernel-firmware-ath11k               | Kernel firmware files for Atheros Qualcomm WiFi drivers       | Paket
i+ | kernel-firmware-atheros              | Kernel firmware files for Atheros wireless drivers            | Paket
i+ | kernel-firmware-bluetooth            | Kernel firmware files for various Bluetooth drivers           | Paket
i+ | kernel-firmware-bnx2                 | Kernel firmware files for Broadcom network drivers            | Paket
i+ | kernel-firmware-brcm                 | Kernel firmware files for Broadcom wireless drivers           | Paket
i+ | kernel-firmware-chelsio              | Kernel firmware files for Chelsio network drivers             | Paket
i+ | kernel-firmware-dpaa2                | Kernel firmware files for NXP Management Complex bus driver   | Paket
i+ | kernel-firmware-i915                 | Kernel firmware files for Intel i915 graphics driver          | Paket
i+ | kernel-firmware-intel                | Kernel firmware files for Intel-platform device drivers       | Paket
i+ | kernel-firmware-iwlwifi              | Kernel firmware files for Intel wireless drivers              | Paket
i+ | kernel-firmware-liquidio             | Kernel firmware files for Cavium LiquidIO driver              | Paket
i+ | kernel-firmware-marvell              | Kernel firmware files for Marvell network drivers             | Paket
i+ | kernel-firmware-media                | Kernel firmware files for various Video4Linux drivers         | Paket
i+ | kernel-firmware-mediatek             | Kernel firmware files for Mediatek network drivers            | Paket
i+ | kernel-firmware-mellanox             | Kernel firmware files for Mellanox Spectrum switch driver     | Paket
i+ | kernel-firmware-mwifiex              | Kernel firmware files for Marvell WiFi fullmac drivers        | Paket
i+ | kernel-firmware-network              | Kernel firmware files for various network drivers             | Paket
i+ | kernel-firmware-nfp                  | Kernel firmware files for Netronome Flow Processor driver     | Paket
i+ | kernel-firmware-nvidia               | Kernel firmware files for Nvidia Tegra and graphics drivers   | Paket
   | kernel-firmware-nvidia-gsp-G06       | Kernel firmware file for open NVIDIA kernel module driver G06 | Paket
   | kernel-firmware-nvidia-gspx-G06      | Kernel firmware file for open NVIDIA kernel module driver G06 | Quellpaket
   | kernel-firmware-nvidia-gspx-G06      | Kernel firmware file for open NVIDIA kernel module driver G06 | Paket
   | kernel-firmware-nvidia-gspx-G06-cuda | Kernel firmware file for open NVIDIA kernel module driver G06 | Quellpaket
   | kernel-firmware-nvidia-gspx-G06-cuda | Kernel firmware file for open NVIDIA kernel module driver G06 | Paket
i+ | kernel-firmware-platform             | Kernel firmware files for various platform drivers            | Paket
i+ | kernel-firmware-prestera             | Kernel firmware files for Marvell Prestera ASIC driver        | Paket
i  | kernel-firmware-qcom                 | Kernel firmware files for Qualcomm device drivers             | Paket
i+ | kernel-firmware-qlogic               | Kernel firmware files for QLogic network drivers              | Paket
i+ | kernel-firmware-radeon               | Kernel firmware files for Radeon graphics driver              | Paket
i+ | kernel-firmware-realtek              | Kernel firmware files for Realtek wireless drivers            | Paket
i+ | kernel-firmware-serial               | Kernel firmware files for various serial drivers              | Paket
i+ | kernel-firmware-sound                | Kernel firmware files for various sound drivers               | Paket
i+ | kernel-firmware-ti                   | Kernel firmware files for Texas Instruments wireless drivers  | Paket
i+ | kernel-firmware-ueagle               | Kernel firmware files for Eagle IV USB ADSL modem driver      | Paket
i+ | kernel-firmware-usb-network          | Kernel firmware files for various USB WiFi / Ethernet drivers | Paket
i  | kernel-install-tools                 | Useful tools for installing self-built kernels                | Paket
   | kernel-kvmsmall                      | The Small Developer Kernel for KVM                            | Paket
   | kernel-kvmsmall                      | The Small Developer Kernel for KVM                            | Quellpaket
   | kernel-kvmsmall-devel                | Development files necessary for building kernel modules       | Paket
   | kernel-kvmsmall-livepatch-devel      | Kernel symbols file used during kGraft patch development      | Paket
   | kernel-kvmsmall-vdso                 | vdso binaries for debugging purposes                          | Paket
i+ | kernel-macros                        | RPM macros for building Kernel Module Packages                | Paket
   | kernel-obs-build                     | package kernel and initrd for OBS VM builds                   | Paket
   | kernel-obs-build                     | package kernel and initrd for OBS VM builds                   | Quellpaket
   | kernel-obs-qa                        | Basic QA tests for the kernel                                 | Paket
   | kernel-obs-qa                        | Basic QA tests for the kernel                                 | Quellpaket
   | kernel-rt                            | The Linux Kernel                                              | Paket
   | kernel-rt                            | The Linux Kernel                                              | Quellpaket
   | kernel-rt-devel                      | Development files necessary for building kernel modules       | Paket
   | kernel-rt-extra                      | The Linux Kernel - Unsupported kernel modules                 | Paket
   | kernel-rt-livepatch                  | Metapackage to pull in matching kernel-livepatch package      | Paket
   | kernel-rt-livepatch-devel            | Kernel symbols file used during kGraft patch development      | Paket
   | kernel-rt-optional                   | The Linux Kernel - Optional kernel modules                    | Paket
   | kernel-rt-vdso                       | vdso binaries for debugging purposes                          | Paket
   | kernel-rt_debug                      | The Linux Kernel                                              | Paket
   | kernel-rt_debug                      | The Linux Kernel                                              | Quellpaket
   | kernel-rt_debug-devel                | Development files necessary for building kernel modules       | Paket
   | kernel-rt_debug-livepatch-devel      | Kernel symbols file used during kGraft patch development      | Paket
   | kernel-rt_debug-vdso                 | vdso binaries for debugging purposes                          | Paket
i+ | kernel-source                        | The Linux Kernel Sources                                      | Paket
   | kernel-source                        | The Linux Kernel Sources                                      | Quellpaket
   | kernel-source-azure                  | The Linux Kernel Sources                                      | Paket
   | kernel-source-azure                  | The Linux Kernel Sources                                      | Quellpaket
   | kernel-source-rt                     | The Linux Kernel Sources                                      | Paket
   | kernel-source-rt                     | The Linux Kernel Sources                                      | Quellpaket
   | kernel-source-vanilla                | Vanilla Linux kernel sources with minor build fixes           | Paket
   | kernel-syms                          | Kernel Symbol Versions (modversions)                          | Paket
   | kernel-syms                          | Kernel Symbol Versions (modversions)                          | Quellpaket
   | kernel-syms-azure                    | Kernel Symbol Versions (modversions)                          | Paket
   | kernel-syms-azure                    | Kernel Symbol Versions (modversions)                          | Quellpaket
   | kernel-syms-rt                       | Kernel Symbol Versions (modversions)                          | Paket
   | kernel-syms-rt                       | Kernel Symbol Versions (modversions)                          | Quellpaket
   | kernel-vanilla                       | The Standard Kernel - without any SUSE patches                | Quellpaket
   | kernel-vanilla                       | The Standard Kernel - without any SUSE patches                | Paket
   | kernel-vanilla-base                  | The Standard Kernel - without any SUSE patches - base modules | Paket
   | kernel-vanilla-devel                 | Development files necessary for building kernel modules       | Paket
   | kernel-vanilla-livepatch-devel       | Kernel symbols file used during kGraft patch development      | Paket
   | kernel-zfcpdump                      | The IBM System Z zfcpdump Kernel                              | Quellpaket
   | kernelshark                          | GUI for trace-cmd                                             | Paket

`zypper info kernel-devel`:

Information for Paket kernel-devel:
-----------------------------------
Repository     : update-sle (15.5)
Name           : kernel-devel
Version        : 5.14.21-150500.55.68.1
Arch           : noarch
Anbieter       : SUSE LLC 
Installed Size : 59.1 MiB
Installed      : Yes
Status         : up-to-date
Quellpaket     : kernel-source-5.14.21-150500.55.68.1.src
Upstream-URL   : https://www.kernel.org/ 
Summary        : Development files needed for building kernel modules
Description    : 
    Kernel-level headers and Makefiles required for development of
    external kernel modules.


    Source Timestamp: 2024-06-05 21:39:05 +0000
    GIT Revision: 40e256a4a88f37d43c8f973ffe5bee78c5b1c679
    GIT Branch: SLE15-SP5

`zypper repos`

Repository-Prioritäten treten in Kraft:                                                                                                                                                                                                     (Siehe 'zypper lr -P' für Details)
      20 (erhöhte Priorität)  :  1 Repository
      99 (Standard-Priorität) : 12 Repositorys

#  | Alias                                | Name                                                         | Enabled | GPG Check | Refresh
---+--------------------------------------+--------------------------------------------------------------+---------+-----------+--------
 1 | NVIDIA:repo-non-free                 | repo-non-free (15.5)                                         | Yes     | (r ) Yes  | Yes
 2 | download.nvidia.com-$releasever      | nVidia Graphics Drivers                                      | Yes     | (r ) Yes  | Yes
 3 | http-download.opensuse.org-08194b20  | openSUSE:Leap:15.5:Update                                    | No      | ----      | ----
 4 | https-download.opensuse.org-1a3b4b18 | SUSE:SLE-15-SP2:GA                                           | No      | ----      | ----
 5 | https-download.opensuse.org-1df5925c | SUSE:SLE-15:GA                                               | No      | ----      | ----
 8 | https-download.opensuse.org-4e7c4183 | devel:languages:rust                                         | No      | ----      | ----
11 | https-download.opensuse.org-7c0c5e5f | SUSE:SLE-15-SP1:GA                                           | No      | ----      | ----
 7 | https-download.opensuse.org-31c9479b | home:kimi                                                    | No      | ----      | ----
 9 | https-download.opensuse.org-75a45d34 | server:database                                              | No      | ----      | ----
10 | https-download.opensuse.org-75f4f64c | home:bespokesynth:libs                                       | No      | ----      | ----
 6 | https-download.opensuse.org-2312c850 | SUSE:SLE-15-SP1:Update                                       | No      | ----      | ----
12 | https-download.opensuse.org-a01803b3 | network:im:signal                                            | No      | ----      | ----
13 | https-download.opensuse.org-b4a26c73 | home:hibby50                                                 | No      | ----      | ----
14 | https-download.opensuse.org-b695c6af | SUSE:SLE-15:Update                                           | No      | ----      | ----
15 | https-download.opensuse.org-b800ad06 | SUSE:SLE-15-SP3:GA                                           | No      | ----      | ----
16 | https-download.opensuse.org-e33eb299 | openSUSE:Backports:SLE-15-SP3                                | No      | ----      | ----
17 | https-download.opensuse.org-eb8758bc | openSUSE:Backports:SLE-15-SP3:Checks                         | No      | ----      | ----
18 | https-download.opensuse.org-fb44bba0 | SUSE:SLE-15-SP2:Update                                       | No      | ----      | ----
19 | openSUSE-Leap-${releasever}-1        | openSUSE-Leap-15.5-1                                         | No      | ----      | ----
20 | openSUSE:repo-non-oss                | repo-non-oss (15.5)                                          | Yes     | (r ) Yes  | Yes
21 | openSUSE:repo-non-oss-debug          | repo-non-oss-debug (15.5)                                    | No      | ----      | ----
22 | openSUSE:repo-openh264               | repo-openh264 (15.5)                                         | Yes     | (r ) Yes  | Yes
23 | openSUSE:repo-oss                    | repo-oss (15.5)                                              | Yes     | (r ) Yes  | Yes
24 | openSUSE:repo-oss-debug              | repo-oss-debug (15.5)                                        | No      | ----      | ----
25 | openSUSE:repo-oss-source             | repo-oss-source (15.5)                                       | No      | ----      | ----
26 | openSUSE:update-backports            | update-backports (15.5)                                      | Yes     | (r ) Yes  | Yes
27 | openSUSE:update-backports-debug      | update-backports-debug (15.5)                                | No      | ----      | ----
28 | openSUSE:update-non-oss              | update-non-oss (15.5)                                        | Yes     | (r ) Yes  | Yes
29 | openSUSE:update-non-oss-debug        | update-non-oss-debug (15.5)                                  | No      | ----      | ----
30 | openSUSE:update-oss                  | update-oss (15.5)                                            | Yes     | (r ) Yes  | Yes
31 | openSUSE:update-oss-debug            | update-oss-debug (15.5)                                      | No      | ----      | ----
32 | openSUSE:update-sle                  | update-sle (15.5)                                            | Yes     | (r ) Yes  | Yes
33 | openSUSE:update-sle-debug            | update-sle-debug (15.5)                                      | No      | ----      | ----
34 | openSUSE_Leap_${releasever}          | Mozilla for Leap 15.5                                        | Yes     | (r ) Yes  | Yes
35 | openSUSE_Leap_${releasever}_1        | Packman (full) for Leap 15.5                                 | Yes     | (r ) Yes  | Yes
36 | repo-backports-update                | Update repository of openSUSE Backports                      | Yes     | (r ) Yes  | Yes
37 | repo-sle-update                      | Update repository with updates from SUSE Linux Enterprise 15 | Yes     | (r ) Yes  | Yes

`sudo zypper purge-kernels --dry-run`:

Installierte Pakete werden gelesen...

Säuberung von veralteten Kerneln wird vorbereitet...
Konfiguration: latest,latest-1,running
Kernel Release läuft: 5.14.21-150500.55.68-default
Kernel arch läuft: x86_64

Paketabhängigkeiten werden aufgelöst...
Nothing to do.

Version data from Info Centre:

Operating System: openSUSE Leap 15.5
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.14.21-150500.55.68-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4702MQ CPU @ 2.20GHz
Memory: 11.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4600
Manufacturer: Acer
Product Name: Aspire V3-772G
System Version: V1.15

I would like the help of someone with more experience to understand the differences and how those 5 things are connected: libzypp, YaST, Zypper, PackageKit and Gnome Software Center. Here is my take away from a day of research: - libzypp: the backend package management library that powers applications like YaST, zypper and the openSUSE implementation of PackageKit - YaST: it's a system configuration tool that happens to allow the management of dependencies through libzypp. It provides both a graphical interface (GTK) and an interface through the terminal (not sure what it's used here) - Zypp: the official command-line package manager of Open SUSE - PackageKit: that's where things get a little fuzzy for me. This seems to be a package manager abstraction - its supposed to abstract all the differences between apt, zypper, yum, etc - Gnome Software Center: it's a graphical interface (GTK) to install dependencies through package kit - so it's supposed to work with all distros, regardless of the underline package manager used If I understood this correct: - Why don't I see the apps installed through YaST in the Gnome Software Center and vice-versa? - Why would I want to keep Gnome Software Center installed if the previous point (^) doesn't happen? To me this thing just seems cluttered

I just upgraded to OpenSUSE 12.2 from OpenSUSE 12.1 by changing all of my repositories to target 12.2 (instead of 12.1). Now that I've upgraded, I've found a bunch of packages that have no repository*, which the **YaST Software Manager** marks with red text in the version column. I can scroll through these and remove every single one, but I'm wondering if the **zypper** search (zypper se) or the **Software Manager** has any way to target/select all of these at once. *- These packages had a repository (OpenSUSE 12.1 something), but since I replaced those repositories with the 12.2 repositories, they no longer have a repository association. This doesn't create a problem, because the 12.2 repositories should contain everything I need to run my system.

I have an installation of openSUSE 11.4 which was installed in German. I started Yast2 (which displayed in German, like "Netzwerkdienste") and switched the language to English under "System" -> "Sprache". Yast2 downloaded some files, installed something and remained German ("Netzwerkdienste" can still be seen instead of, presumably, "Network Services"). I rebooted the machine, same result. I un-installed the German Yast language pack. Yast2 persists in displaying in German. I don't know how many of Yast2's screens are supposed to be translated, but I think it might only be the main screen that is in German. However, it is annoying. How can I change it? Update: I checked environment variables (for the root user). There are several variables that refer to language settings and all remain set to German. declare -x LANG="de_DE.utf8" declare -x LANGUAGE="de_DE.utf8" declare -x LC_ALL="de_DE.utf8" Shouldn't Yast2 have modified them? Update: I just started vi and it's also in German... does the language setting in Yast2 do anything at all?

I installed OpenSuse Tumbleweed instead of Debian, with which I have a 25 years familiarity, on my new PC. Now, I have problems with UTF-8, e.g., when I cat some_file containing UTF-8 encoded Unicode characters I see some garbage, also input methods don't work properly. To fix the problems, e.g., I can start an XTerm like LANG=C.utf8 xterm and in the new XTerm everything is fine. What I want to do is to set my LANG to C.utf8 globally, but every (EVERY) guide I've found just explains how to use Yast to perform the task, and Yast lists tens of different languages but no C. The configuration file /etc/sysconfig/language is over 100 lines and I find it confusing, and I'm not particularly confident that it's the right place to modify. How must I LANG=C.utf8 permanently, using Yast or without using Yast?

A 32-bit server with openSUSE Tumbleweed: While logging in, I received this warning: > /usr/bin/manpath: can't set the locale; make sure $LC_* and $LANG are correct To fix the above error, I run these commands to modify the system language and time, but I get errors:

> sudo yast2 language
[sudo] password for root: 
Failed to set locale. Fix your system.
Failed to set locale. Fix your system.

Also:

> sudo yast2 timezone
[sudo] password for root: 
Failed to set locale. Fix your system.
Failed to set locale. Fix your system.

I couldn't figure out the cause. Does anyone have a suggestion? Update -- Locale output:

> locale 
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=
LC_CTYPE=UTF-8
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=

Another output:

> locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
C
C.utf8
POSIX
aa_DJ
aa_DJ.utf8
aa_ER
aa_ER@saaho
aa_ET
af_ZA
af_ZA.utf8
agr_PE
ak_GH
am_ET
an_ES
an_ES.utf8

# ... it' a long list

Update -- Adding these lines to ~/.profile didn't fix the problem, even after logging out or even reboot:

export LANG="en_US.UTF-8"
export LC_CTYPE="en_US.UTF-8"
export LC_ALL="en_US.UTF-8"

### New observation 1. Log in to the server directly/physically: no warning is thrown 1. Log in to the server by SSH from a Linux laptop (openSUSE Leap 15.1): no warning is thrown 1. Log in to the server by SSH from MacBook laptop: this warning is thrown: > /usr/bin/manpath: can't set the locale; make sure $LC_* and $LANG are correct

I run these commands to install DNS server dependencies on openSUSE Tumbleweed:

sudo zypper in -t pattern dhcp_dns_server
sudo systemctl enable named.service
sudo systemctl start named.service

To configure the DNS server, I'm trying YAST2 following [this documentation](https://doc.opensuse.org/documentation/leap/reference/html/book-opensuse-reference/cha-dns.html) :

sudo yast2 dns-server

I intend to configure example.com domain zone with IP address 1.2.3.4. ### What I did I have a DNS zone of *master* type: My *NS Records* tab is: My *Records* tab is: ### Problem However, saving the configuration runs into a problem: I couldn't figure it out. Can anyone help?

I have a Virtual Machine with a clean installation of SUSE Linux For SAP Applications 15. I configured the network with YaST Network (IP address assigned, file /etc/sysconfig/network/ifcfg-eth0 automatically created, everything looked good). When OS is rebooted, file ifcfg-eth0 is missing and I have to configure the network again. Does anybody know why file ifcfg-eth0 is deleted after reboot? Does OS do it on purpose? Do I need SUSE License?

I ran into a kind of bigger problem. In my company we have an In-house ERP-server (SUSE ENTERPRISE). I wanted to write a bash script that adds users automatically. However, I needed the signs "\" (=ALT+"\") and {} (=ALT + "{" or "}" respectively) in order to write that script. The enterprise linux did not support ANY SIGN that require ALT + sign combinations. So I was pretty sure, if I changed the keyboard settings from "de_de@EURO" to "de_DE.UTF-8" I would be able to solve this issue. By entering yast2(graphical settings manager) in the command line and changing the keyboard system setting this way, I did not fully solve the issue with the missing characters that come with ALT key combinations but I got half way there because it gave me the option to use ALT+NUMBER combinations inside the VIM editor at least. This way I could at least finish my bash script. I left the system keyboard settings like this because I thought I made an improvement anyway. But today, the company we purchased the ERP system from claimed that all GERMAN UMLAUTE were corrupt or failed to be parsed correctly, all UMLAUTE WERE MISSING they said. So they decided (without letting us know) that there was an error in our ERP linux server (because I changed something) and changed everything back to work again and claimed they needed an entire working day for fixing it (8 hours). 8 hours - 135 Euros each. Now my boss asked me who did the change and I admitted that it was me and this is why I am here. I offered him that I would pay the full price so the company does not need to pay for my mistake if it was. And that I would never touch this system again. However, I am pretty confident with Linux and I cannot seem to understand how someone needs 8 hours to fix a system keyboard setting that should 1. be found in a change log file 2. be fixed by entering yast2 to open the suse manager and change back the keyboard settings to the original settings and 3. I don't even believe that de_DE.UTF-8 should have any problems with recognizing GERMAN UMLAUTE. What is your opinion about this? Is it really possible that changing this keyboard setting messes up an entire ERP (the forms and the output)? Or are they trying to charge us a service that was fixed in like half an hour and make 8 hours out of it? And is it normal that a company that sells a Linux SUSE enterprise server is incapable of making sure that ALT+CHARACTERS are recognized OUT OF THE BOX? Don't get me wrong. I realize that I should not have touched and changed a running/productive server without asking anyone but I believe that the deal/problem/issue is not that big to charge that big of an amount for this service. I have a 3 years experience with Linux Debian. So SUSE is nothing too new for me. I would like to know your expertise opinion about this. I would also like to know how I should act in this situation as an advice because possibly - even if I pay the full price - I might still get fired for that action. I am very open to criticism and I am not afraid of indoctrinations - on the contrary - I ask for them.

I've read the official YaST module development documetations and I've implemented my YaST module successfully. Now I would like to create a myModule menu entry in YaST, i.e., when I type yast, to have a menu like System or Network Settings, instead of needing to type /sbin/yast2 myModule.ycp every time I want to access my tool. How can I achieve this? I have not found any documentation about this online.

I'm installing a fresh openSUSE 13.1 with an autoyast xml file. I can't find the correct way to enable ssh and open the port in the firewall; the "Confirmation" screen shows that SSH service will be disabled, SSH port will be blocked. I already tried: sshd enable without success...

Linux distro: SLES 11 SP4 I have on hand SLES 11 ISO's: SP1, SP2, & SP3 I need to locate and install older programs located on older ISO's. For example: I have gcc 4.7 on SP4, but I need to install gcc 4.3.4 on SP1. When I insert the disc(s) into the DVD-ROM, I open YaST > Software Management > Search: gcc > The only thing I see is the SP4 catologue list, but I'm fairly certain that the gcc versions are located on those ISO's. What am I doing wrong and how can I install older programs from previous SP packages?

When installing openSUSE Tumbleweed, I get a red warning before the last confirmation: Boot from MBR does not work together with btrfs filesystem and GPT disk label without bios_grub partition. To fix this issue, create bios_grub partition or use any ext filesystem for boot partition or do not install stage 1 to MBR. The warning is right, installed like that openSUSE can't boot. As far as I understand my machine is probably in EFI mode, because YaST creates something that looks like GPT to me (at least in the graph visualization of the expert partitioning I can see GPT under both /dev/sda and /dev/sdb). What may be relevant is that automatic partitioning creates a BIOS boot partition as /dev/sda1. Apparently this is not enough, neither is setting /dev/sda1 as the custom boot partition instead of MBR on at the boot loader settings, so how do I turn this one into a "bios_grub partition" (whatever that is)?

While trying to run a module from within yast in Tumbleweed openSUSE, the module crashed and it says in terminal Run command: /sbin/yast2 sw_single & terminate called after throwing an instance of 'YUIPluginException' what(): Couldn't load plug-in qt YaST got signal 6 at file /usr/share/YaST2/modules/Wizard.rb:782 sender PID: 7211 /sbin/yast2: line 440: 7211 中止 (core dumped) $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS What this could　be ? zypper search libyui*　 is: S | 名前 | 概要 | 種類 --+--------------------------+--------------------------------------+----------- | libyui-devel | Libyui header files | パッケージ i | libyui-doc | Libyui documentation | パッケージ | libyui-ncurses-devel | Libyui-ncurses header files | パッケージ i | libyui-ncurses-doc | Libyui-ncurses documentation | パッケージ | libyui-ncurses-pkg-devel | Libyui-ncurses-pkg header files | パッケージ i | libyui-ncurses-pkg-doc | Libyui-ncurses-pkg documentation | パッケージ i | libyui-ncurses-pkg7 | Libyui - yast2 package selector wi-> | パッケージ i | libyui-ncurses7 | Libyui - Character Based User Inte-> | パッケージ | libyui-qt-devel | Libyui-qt header files | パッケージ i | libyui-qt-doc | Libyui-qt documentation | パッケージ | libyui-qt-graph-devel | Libyui-qt-graph header files | パッケージ i | libyui-qt-graph-doc | Libyui-qt-graph documentation | パッケージ | libyui-qt-graph7 | Libyui - Qt Graph Widget | パッケージ | libyui-qt-pkg-devel | Libyui-qt-pkg header files | パッケージ i | libyui-qt-pkg-doc | Libyui-qt-pkg documentation | パッケージ i | libyui-qt-pkg7 | Libyui - Qt Package Selector | パッケージ i | libyui-qt7 | Libyui - Qt User Interface | パッケージ i | libyui7 | Libyui - GUI-abstraction library | パッケージ Update, it seems to be related to a specific package/ パッケージ as cited here but making the process listed I still dont get the UI up. Despite the page speaks about novell linux, and Im open Suse, there is no xorg-x11-libXrender-7.4-1.23.1 but instead is libXrender1-0.9.10-1.1.x86_64 So what would be needed? Thanks in advance

How do I get the above message right after starting an ssh session. The reason I opened the ssh session was that I came across a 500 internal server error on the plesk panel. I tried to look around for similar problems, but all answers I find seem very specific toward variations on this problem. I guess it is a very generic message, if I should provide more info, please let me know what to run. free -m total used free shared buffers cached Mem: 5020 202 4817 0 0 0 -/+ buffers/cache: 202 4817 Swap: 0 0 0 ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited pending signals (-i) 16375 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 16375 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited cat /proc/user_beancounters Version: 2.5 uid resource held maxheld barrier limit failcnt 1231234: kmemsize 6061008 6064704 17024866 19647330 0 lockedpages 0 0 3800 4096 0 privvmpages 138119 138227 138256 202568 755228 shmpages 60296 60296 131072 131072 0 dummy 0 0 2147483647 2147483647 0 numproc 64 64 232 232 0 physpages 30682 30671 0 2147483647 0 vmguarpages 0 0 66400 2147483647 0 oomguarpages 50128 50117 2147483647 2147483647 0 numtcpsock 28 28 500 500 0 numflock 14 14 200 232 0 numpty 1 1 64 64 0 numsiginfo 0 0 512 512 0 tcpsndbuf 275520 275520 4683256 6102456 0 tcprcvbuf 458752 458752 4683256 6102456 0 othersockbuf 48576 49280 1503232 4063232 0 dgramrcvbuf 0 0 240000 262144 0 numothersock 38 38 382 382 1 dcachesize 773048 774892 2194304 2317184 0 numfile 2874 2874 5432 5432 6308 dummy 0 0 0 0 0 dummy 0 0 0 0 0 dummy 0 0 0 0 0 numiptent 64 64 128 128 0

I am currently using openSUSE 13.1 KDE. The big reason why I like openSUSE is YaST. YaST does so much and makes many parts of life easier. YaST not only graphically allows me to add/remove/manage repositories, and packages. It allows me to manage my firewall, kernel, services, groups, sudo and a lot more from a GUI. My favorite is that YaST allows me to set up Apache Virtual Hosts with a few clicks of the mouse on my local desktop (I am a web developer). Now I can and know how to manage most of these things in terminal, but sometimes I like the GUI. Are there any alternatives to YaST out there? Either distro agnostic or specific to a distro (any linux distro). I just want to see what else is out there.

I am looking to disable my root account for security purposes only in witch I use sudo for anything I use on my system that I need the root account for. Witch works fine for if I need to do anything within the terminal. But when I open YaST2 it ask me for the root password and not mine. And I am wondering if I can set YaST up to use my password sense the root password wont work scene it will be disabled. **Update** I use opensuse tumbleweed along with MATE desktop environment

I have OpenSuse Leap 42.2. YaST2 software manager fails to autofresh and the error message is: > Cannot access installation media http://download.opensuse.org/distribution/leap/42.2/repo/non-oss/ (Medium 1). Check whether the server is accessible" This problem has persisted for over a month now. Any ideas how to get past this issue?