{"id":168845,"date":"2026-06-15T17:19:29","date_gmt":"2026-06-15T14:19:29","guid":{"rendered":"https:\/\/computingforgeeks.com\/?p=168845"},"modified":"2026-06-15T17:19:29","modified_gmt":"2026-06-15T14:19:29","slug":"things-to-do-after-installing-opensuse-leap","status":"publish","type":"post","link":"https:\/\/computingforgeeks.com\/things-to-do-after-installing-opensuse-leap\/","title":{"rendered":"Things to Do After Installing openSUSE Leap 16"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">You just finished the <a href=\"https:\/\/computingforgeeks.com\/install-opensuse-leap-16\/\">openSUSE Leap 16 install<\/a> and you are staring at a clean GNOME desktop. Before it becomes your daily driver, a handful of things to do after installing openSUSE Leap 16 turn the stock install into something that plays your media, keeps you safe when an update goes sideways, and gives you the new Leap 16 tools worth knowing. None of this is hard, and you can do most of it from one terminal session.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The steps below are ordered the way you would actually do them on a fresh machine: update first, then media and software, then the safety and admin pieces. <em>Everything here was run on a fresh openSUSE Leap 16 install with GNOME in June 2026.<\/em><\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1280\" height=\"800\" src=\"https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-gnome-desktop.png\" alt=\"openSUSE Leap 16 GNOME 48 desktop activities overview after install\" class=\"wp-image-168842\" title=\"\" srcset=\"https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-gnome-desktop.png 1280w, https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-gnome-desktop-300x188.png 300w, https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-gnome-desktop-1024x640.png 1024w, https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-gnome-desktop-768x480.png 768w\" sizes=\"auto, (max-width: 1280px) 100vw, 1280px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Update your system first<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Always start here. The install media is a snapshot in time, so there are already patches waiting. Refresh the repositories and apply every available update:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo zypper refresh\nsudo zypper update<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">On Leap you use <code>zypper update<\/code> (or <code>zypper patch<\/code>) for day-to-day updates within the release. Save <code>zypper dup<\/code> for moving to the next Leap version, not for routine patching. If a kernel update lands, reboot before moving on.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Turn on the non-OSS repository<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Leap ships the non-OSS repository defined but disabled. It holds freely-redistributable but non-open packages a lot of people want, such as certain firmware and browser bits. Enable it and refresh:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo zypper modifyrepo --enable openSUSE:repo-non-oss\nsudo zypper refresh<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">That is the part that trips people up later when a package &#8220;isn&#8217;t found&#8221;; it was sitting in non-OSS the whole time.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Add the Packman repository and install codecs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Out of a fresh install, Leap cannot play many common formats like H.264 video or MP3 because of patent and licensing restrictions. The community Packman repository fills that gap. Add it for Leap 16:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo zypper addrepo -cfp 90 https:\/\/ftp.gwdg.de\/pub\/linux\/misc\/packman\/suse\/openSUSE_Leap_16.0\/ packman\nsudo zypper refresh<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Now switch your installed multimedia packages over to the Packman versions, which carry the full codec support. The vendor change is expected here, so accept it:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo zypper dist-upgrade --from packman --allow-downgrade --allow-vendor-change<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">From here, VLC, the GNOME video player, and browsers will play the formats that were silent before.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Set up Flatpak and Flathub<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Flatpak is already installed on a GNOME Leap 16 system, but the Flathub remote is what gives you the large catalog of desktop apps. Add it:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>flatpak remote-add --if-not-exists flathub https:\/\/dl.flathub.org\/repo\/flathub.flatpakrepo<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Log out and back in once so GNOME Software picks up the new remote, then you can <a href=\"https:\/\/computingforgeeks.com\/install-and-manage-flatpak-applications-on-linux\/\">install and manage Flatpak apps<\/a> from the store or the command line. This is the easy way to get apps that are not packaged in the openSUSE repositories. If you are weighing it against other formats, the <a href=\"https:\/\/computingforgeeks.com\/snap-vs-flatpak-vs-appimage\/\">Snap vs Flatpak vs AppImage<\/a> comparison breaks down when each one makes sense.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Install your everyday applications<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">With Packman and Flathub in place, pull in the basics. From the repositories:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo zypper install vlc fastfetch htop git<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pick whatever fits your workflow. The point is that codecs are sorted, so media apps like VLC just work.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Confirm your Snapper safety net<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This is the openSUSE feature that saves you. On the default Btrfs root, Snapper takes a snapshot before and after every change you make with zypper, so a broken update is one reboot away from being undone. Confirm it is active:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo snapper list<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You will see the snapshots zypper has already created, including a pre\/post pair for every operation you have run:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>  # | Type   | Pre # | Date                        | User | Cleanup | Description\n----+--------+-------+-----------------------------+------+---------+-----------------------\n 0  | single |       |                             | root |         | current\n 1* | single |       | Mon 15 Jun 2026 01:14:23 AM | root |         | first root filesystem\n 2  | pre    |       | Mon 15 Jun 2026 03:25:44 PM | root | number  | zypp(zypper)\n 3  | post   |     2 | Mon 15 Jun 2026 03:34:56 PM | root | number  |<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If an update ever breaks the system, reboot, and in the GRUB menu pick <strong>Start bootloader from a read-only snapshot<\/strong> to boot a working state. You don&#8217;t have to set anything up; on the default install this is already running. The companion guide on <a href=\"https:\/\/computingforgeeks.com\/btrfs-snapshots-snapper-automatic-rollback-fedora-opensuse\/\">automatic rollback with Snapper<\/a> covers managing snapshots day to day.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Open only the ports you need<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">firewalld runs by default on Leap 16. If this is a desktop you probably want it closed to the world; if it is a server, open just the services you actually run. To allow SSH, for example:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo firewall-cmd --add-service=ssh --permanent\nsudo firewall-cmd --reload\nsudo firewall-cmd --list-all<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The zone listing confirms what is open. On this machine only SSH and Cockpit are allowed in:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>public (default, active)\n  target: default\n  interfaces: enp6s18\n  services: cockpit dhcpv6-client ssh\n  ports:\n  forward: yes<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Add a service per app you expose (<code>http<\/code>, <code>https<\/code>, and so on) rather than opening the firewall wide. SELinux is already enforcing on Leap 16, so between the two you start with sane defaults.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Install Cockpit for web-based administration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cockpit is the browser-based admin console openSUSE leans on now that YaST is retired. It gives you a graphical view of services, storage, logs, networking, and updates without leaving the browser. Install and enable it:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo zypper install cockpit\nsudo systemctl enable --now cockpit.socket\nsudo firewall-cmd --add-service=cockpit --permanent\nsudo firewall-cmd --reload<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Open <code>https:\/\/localhost:9090<\/code> (or the machine&#8217;s IP from another computer) and log in with your system user. Accept the self-signed certificate warning on first visit.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1280\" height=\"800\" src=\"https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-cockpit-web-console.png\" alt=\"Cockpit web console overview running on openSUSE Leap 16\" class=\"wp-image-168844\" title=\"\" srcset=\"https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-cockpit-web-console.png 1280w, https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-cockpit-web-console-300x188.png 300w, https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-cockpit-web-console-1024x640.png 1024w, https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-cockpit-web-console-768x480.png 768w\" sizes=\"auto, (max-width: 1280px) 100vw, 1280px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Meet Myrlyn, the new package manager<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Leap 16 retired the YaST software module and replaced it with Myrlyn, a graphical package manager built on the same libzypp backend zypper uses. If you liked clicking through packages in YaST, this is its replacement. Install it:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo zypper install myrlyn<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Launch it from the application grid or with <code>sudo myrlyn<\/code>. You get the familiar package list, patterns, and repository views for installing and removing software graphically.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1280\" height=\"800\" src=\"https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-myrlyn-package-manager.png\" alt=\"Myrlyn graphical package manager on openSUSE Leap 16 showing VLC packages\" class=\"wp-image-168843\" title=\"\" srcset=\"https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-myrlyn-package-manager.png 1280w, https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-myrlyn-package-manager-300x188.png 300w, https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-myrlyn-package-manager-1024x640.png 1024w, https:\/\/computingforgeeks.com\/wp-content\/uploads\/2026\/06\/wm-opensuse-leap-16-myrlyn-package-manager-768x480.png 768w\" sizes=\"auto, (max-width: 1280px) 100vw, 1280px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Add GNOME Tweaks and extensions<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The stock GNOME desktop is deliberately minimal. GNOME Tweaks unlocks fonts, window-button layout, and startup options, and the Extensions app lets you add features like a dock or system tray:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo zypper install gnome-tweaks<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Open Tweaks to set your fonts and titlebar buttons. The GNOME browser connector already ships with the desktop, so head to extensions.gnome.org in Firefox and toggle extensions on directly, or pull curated ones from the repository such as <code>gnome-shell-extension-user-theme<\/code>. This is where a fresh GNOME starts feeling like yours.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Install the NVIDIA driver if you have an NVIDIA GPU<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If your machine has an NVIDIA card, the proprietary driver gives you proper acceleration. openSUSE ships a repository definition for it, so you do not have to add URLs by hand:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo zypper install openSUSE-repos-Leap-NVIDIA\nsudo zypper refresh\nsudo zypper install-new-recommends --repo repo-non-free<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The first command installs the repository definition, which openSUSE registers under the alias <code>repo-non-free<\/code>, and the last pulls the matching driver for your card. On a Secure Boot system the driver creates and enrolls a signing key during install, so follow the blue MOK enrollment screen on the next reboot. If you are on Intel or AMD graphics, skip this entirely; those drivers are already in the kernel.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Set your hostname and time<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Two small things that are easy to forget. Give the machine a real name and confirm time sync is on:<\/p>\n\n\n\n<pre class=\"wp-block-code code\"><code>sudo hostnamectl set-hostname leap-desktop\ntimedatectl<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">With updates applied, codecs in place, your safety net confirmed, and Cockpit and Myrlyn ready, Leap 16 is set up the way it should have shipped for your machine. From here it stays out of your way, which is the whole point of running Leap. If you are coming from an older release, the <a href=\"https:\/\/computingforgeeks.com\/upgrade-opensuse-leap-15-to-16\/\">upgrade from Leap 15 guide<\/a> walks through moving an existing system across.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>You just finished the openSUSE Leap 16 install and you are staring at a clean GNOME desktop. Before it becomes your daily driver, a handful of things to do after installing openSUSE Leap 16 turn the stock install into something that plays your media, keeps you safe when an update goes sideways, and gives you &#8230; <a title=\"Things to Do After Installing openSUSE Leap 16\" class=\"read-more\" href=\"https:\/\/computingforgeeks.com\/things-to-do-after-installing-opensuse-leap\/\" aria-label=\"Read more about Things to Do After Installing openSUSE Leap 16\">Read more<\/a><\/p>\n","protected":false},"author":15,"featured_media":168846,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[299,47,50],"tags":[781,282,9986],"cfg_series":[39887],"class_list":["post-168845","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-how-to","category-linux","category-linux-tutorials","tag-desktop","tag-linux","tag-opensuse","cfg_series-opensuse-leap-16"],"_links":{"self":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/168845","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/comments?post=168845"}],"version-history":[{"count":1,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/168845\/revisions"}],"predecessor-version":[{"id":168847,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/168845\/revisions\/168847"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/media\/168846"}],"wp:attachment":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/media?parent=168845"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/categories?post=168845"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/tags?post=168845"},{"taxonomy":"cfg_series","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/cfg_series?post=168845"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}