Search
Welcome to the monthly update for openSUSE Tumbleweed for July 2024. Last month was busy with events like the Community Summit in Berlin and the openSUSE Con...
![Tumbleweed Monthly Update - July 2024](https://lemmy.ml/pictrs/image/058a5f23-9d3d-4f59-9339-0347b74f082a.png?format=webp&thumbnail=256)
Welcome to the monthly update for openSUSE Tumbleweed for July 2024. Last month was busy with events like the Community Summit in Berlin and the openSUSE Conference. Both events were productive and well-received. Despite the busy schedule and follow on discussion from the conference about the Rebranding of the Project, a number of snapshots continued to roll out to users this month.
Stay tuned and tumble on!
Should readers desire more frequent information about snapshot updates, they are encouraged to subscribe to the openSUSE Factory mailing list.
New Features and Enhancements
- Linux Kernel 6.9.9: This kernel introduces several important fixes and enhancements across various subsystems. Key updates include the introduction of
devm_mutex_init()
for mutex initialization in multiple components, addressing issues in the Hisilicon debugfs uninit process, and resolving shared IRQ handling in DRM Lima drivers. Fixes in the PowerPC architecture avoidnmi_enter/nmi_exit
in real mode interrupts, while networking improvements prevent unnecessaryBUG()
calls innet/dql
. Enhancements in WiFi drivers such as RTW89 include improved handling for 6 GHz channels. Updates in DRM/AMD drivers address multiple issues, from uninitialized variable warnings to ensuring proper timestamp initialization and memory management. The RISC-V architecture receives a fix for initial sample period values, and several BPF selftests see adjustments for better error detection. These updates collectively enhance system stability, performance, and security. - KDE Plasma 6.1.3: Discover now auto-handles Flatpak rebases from runtimes and properly uninstalls EOL refs without replacements. In Kglobalacceld, invalid keycodes are explicitly processed. Kpipewire introduces proper cleanup on deactivate and fixes thread handling for PipeWireSourceStream. KScreen now uses ContextualHelpButton from Kirigami, and Kscreenlocker adds a property to track past prompts. KWin sees numerous improvements: relaxed nightlight constraints, simplified Wayland popup handling, better input method windows, and enhanced screencast plugins. Plasma Mobile enhancements improve home screen interactions, translation issues, and swipe detection. Plasma Networkmanager and Plasma Workspace benefit from shared QQmlEngine and various bug fixes, including avatar image decoding and pointer warping on Wayland.
- Frameworks 6.4.0: Attica updates its gitignore to include VS Code directories. Baloo reverts a QCoreApplication change and ports QML modules. Breeze Icons introduces a ColorScheme-Accent and fixes data-warning icons. KArchive now rejects tar files with negative sizes and fixes crashes with malformed files. KAuth and KBookmarks add VS Code directories to gitignore. KCalendarCore adds missing QtCore dependencies and QML bindings for calendar models. KIO improves systemd process handling and deprecates unused features. Kirigami enhances navigation and dialog components. KTextEditor adds a tool for testing JavaScript scripts and ensures even indent sizes, fixing multiple bugs.
- KDE Gear 24.05.2: Akonadi-calendar adds missing change notifications. Dolphin updates Meta-Object Compiler generation. Filelight enables appx building and ensures hicolor icon presence while Itinerary fixes calendar permissions, corrupted notes, and the package introduces new extractors. Kdenlive addresses timeline, aspect ratio, and compilation issues. Okular fixes a crash with certain PDF actions.
- Supermin 5.3.4: This update introduces several key enhancements, including support for OCaml 5 and kylinsecos. It improves package management by detecting dnf5 and omitting missing options. The update also refines OCaml compilation by using
-output-complete-exe
instead of-custom
that fixes kernel filtering for the aarch64 architecture, and enables kernel uncompression on RISC-V. The update removes previously applied patches now included in the new tarball, helping to streamline the codebase and improve maintainability. - Checkpolicy 3.7: The latest update brings support for Classless Inter-Domain Routing notation in nodecon statements, enhancing SELinux policy definition capabilities. Error messages are now more descriptive, and error handling has been improved. Key bug fixes include handling unprintable tokens, avoiding garbage value assignments, freeing temporary bounds types and performing contiguous checks in host byte order.
Key Package Updates
- NetworkManager 1.48.4: This update introduces support for matching Open vSwitch (OVS) system interfaces by MAC address, enhancing network interface management. Additionally, NetworkManager now considers the contents of
/etc/hosts
when determining the system hostname from reverse DNS lookups of configured interface addresses, improving hostname resolution accuracy. Subpackages updated include NetworkManager-bluetooth, NetworkManager-lang, NetworkManager-tui, NetworkManager-wwan, libnm0, and typelib-1\_0-NM-1\_0. These enhancements contribute to more robust and precise network configuration handling in Linux environments. - libguestfs 1.53.5: This update includes significant enhancements and fixes. The
--chown
parameter is now correctly split on the ':' character, and a new checksum command is supported. Detection for Circle Linux and support for the LoongArch architecture have been added, including file architecture translation fixes. The update allows nbd+unix:// URIs and reimplements GPT partition functions usingsfdisk
. DHCP configuration improvements and a newvirt-customize --inject-blnsvr
operation enhance usability. Deprecated features include the removal of gluster, sheepdog, and tftp drive support. New APIs such asfindfs_partuuid
andfindfs_partlabel
improve functionality, while inspection tools now resolve PARTUUID and PARTLABEL in/etc/fstab
. These updates enhance compatibility, performance, and functionality across various environments. - glib2 2.80.4: The latest update backports key patches: mapping
EADDRNOTAVAIL
toG_IO_ERROR_CONNECTION_REFUSED
, handling files larger than 4GB ing_file_load_contents()
, and correcting GIR install locations and build race conditions. Additionally, improvements ingthreadedresolver
ensure returned records are properly reference-counted inlookup_records()
. - ruby3.3 3.3.4: This release addresses a regression where dependencies were missing in the gemspec for some bundled gems such as net-pop, net-ftp, net-imap, and prime. Other fixes include preventing
Warning.warn
calls for disabled warnings, correcting memory allocation sizes inString.new(:capacity)
and resolving string corruption issues. - libgcrypt 1.11.0: The latest update introduces several new interfaces and performance enhancements. New features include an API for Key Encapsulation Mechanism (KEM), support for algorithms like Streamlined NTRU Prime sntrup761, Kyber, and Classic McEliece, and various Key Derivation Functions (KDFs) including HKDF and X963KDF. Performance improvements feature optimized implementations for SM3, SM4, and other cryptographic operations on ARMv8/AArch64, PowerPC, and AVX2/AVX512 architectures. Other changes include various enhancements for constant time operations and deprecates the
GCRYCTL_ENABLE_M_GUARD
control code.
Bug Fixes
-
orc 0.4.39:
- CVE-2024-40897 was solved with versions before 0.4.39, which had a buffer overflow vulnerability in
orcparse.c
.
- CVE-2024-40897 was solved with versions before 0.4.39, which had a buffer overflow vulnerability in
-
java-21-openjdk 21.0.4.0:
- CVE-2024-21131 was a difficult-to-exploit vulnerability allowing unauthorized data modifications.
- CVE-2024-21138 was a vulnerability causing partial denial of service.
- CVE-2024-21140 was a vulnerability allowing unauthorized data access and modification;
- CVE-2024-21145 was similar.
- CVE-2024-21147 was the same, but for more critical data.
-
ovmf 202402 had three months of CVE patches in its quarterly update.
-
Mozilla Firefox 128.0: This release fixes 16 CVEs. The most severe was CVE-2024-6604; this was a memory safety bug in Firefox 128, Firefox ESR 115.13, Thunderbird 128 and Thunderbird 115.13. These bugs showed evidence of memory corruption that potentially allowed arbitrary code execution.
-
ghostscript 10.03.1)
- CVE-2024-33869 allowed bypassing restrictions via crafted PostScript documents.
- CVE-2023-52722
- CVE-2024-33870 allows access to arbitrary files via crafted PostScript documents.
- CVE-2024-33871 allowed arbitrary code execution via crafted PostScript documents using custom Driver libraries in
contrib/opvp/gdevopvp.c
. - CVE-2024-29510 allowed memory corruption and SAFER sandbox bypass via format string injection in a uniprint device.
-
xwayland 24.1.1 3:
- CVE-2024-31080 had a vulnerability that could allow attackers to trigger the X server to read and transmit heap memory values, leading to a crash.
- CVE-2024-31081 could cause memory leakage and segmentation faults, leading to a crash.
- CVE-2024-31083 allowed arbitrary code execution by authenticated attackers through specially crafted requests.
-
libreoffice 24.2.5.2:
- CVE-2024-5261 allows fetching remote resources without proper security checks.
-
GTK3 3.24.43:
- CVE-2024-6655 allowed a library injection into a GTK application from the current working directory under certain conditions.
-
netpbm 11.7.0:
- CVE-2024-38526: doc, which provides API documentation for Python projects, had a vulnerability where pdoc --math linked to malicious JavaScript files from polyfill.io.
Conclusion
The month of July 2024 was marked by significant updates, security fixes and enhancements. The Linux Kernel 6.9.9 update introduced several key fixes and improvements across various subsystems, enhancing overall stability and performance. KDE Plasma 6.1.3 brought numerous UI improvements and better handling of Flatpak rebases. The updates to Frameworks 6.4.0 and KDE Gear 24.05.2 provided additional enhancements and bug fixes, improving user experience and system reliability. Critical security vulnerabilities were addressed in various packages, including Firefox, ghostscript, and xwayland, ensuring Tumbleweed remains secure, efficient, and feature-rich for all users. Additionally, the Aeon team announced the release of Aeon Desktop to Release Candidate 3 status that came from the release of a Tumbleweed snapshot last week.
For those Tumbleweed users who want to contribute or want to engage with detailed technological discussions, subscribe to the openSUSE Factory mailing list . The openSUSE team encourages users to continue participating through bug reports, feature suggestions and discussions.
Contributing to openSUSE Tumbleweed
Your contributions and feedback make openSUSE Tumbleweed better with every update. Whether reporting bugs, suggesting features, or participating in community discussions, your involvement is highly valued.
More Information about openSUSE:
Official
Fediverse
(Image made with DALL-E)
Understanding Linux and choosing your first Linux distro, v2.0
You're about to take your first steps in the wonderful world of Linux, but you're overwhelmed by the amount of choices? Welcome to this (I hope) very simple guide :)
The aim of this guide is to provide simple, clear information to ease your transition as a beginner. This is not a be-all-end-all guide nor an advanced guide. Because there is a lot of info and explanations everywhere, I will often (over-)simplify so as to keep the information accessible and digestible. Please refrain from asking to add your favorite distro/DE in the comments, I feel there is too much choice already ;)
Preamble
Make sure your hardware is compatible
Nowadays most relatively recent hardware works perfectly fine on Linux, but there are some edge cases still. If you don't use niche hardware and your wifi card is supported, chances are you're golden. Please note that nVidia is a bad faith player in the Linux world, so if you have a GeForce GPU, expect some trouble.
Make sure your favourite apps are either available or have a good replacement on Linux
If some proprietary app is essential to your workflow and is irreplaceable, consider running it in a VM, keeping a Windows partition for it or try and run it through Wine (this is advanced stuff though).
Be aware that Linux is not Windows/MacOS
Things work differently, and this is normal. You will probably struggle at the beginning while adjusting to a new paradigm. You may have to troubleshoot some things. You may break some things in the process. You will probably get frustrated at some point or another. It's okay. You're learning something new, and it can be hard to shed old habits forged by years on another system.
When in doubt, search for documentation
Arch Wiki is one of the greatest knowledge bases about Linux. Despite being heavily tied to Arch, most of its content is readily usable to troubleshoot most modern distros, as the building blocks (Kernel, systemd, core system apps, XOrg/Wayland, your DE of choice etc.) are the same. Most distros also maintain their own knowledge base.
Understanding the Linux world
What is Linux?
Linux, in the strictest definition, is the kernel, ie. the core component that, among other things, orchestrates and handles all interactions between hardware and software, of a large family of operating systems that, by metonymy, are called "Linux". In general understanding, Linux is any one of these operating systems, called distros.
What is a distro?
A distro, short for "Software Distribution", is a cohesive ensemble of software, providing a full operating system, maintained by a single team. Generally, all of them tend to provide almost the same software and work in a very similar way, but there are major philosophical differences that may influence your choice.
What are the main differences between distros?
As said above, there are a lot of philosophical differences between distros that lead to practical differences. There are a lot of very different ways the same software can be distributed.
- "Point Release" (OpenSUSE Leap) vs. "Rolling Release" (OpenSUSE Tumbleweed): Point release distros are like traditional software. They have numbered releases, and between each one no feature updates take place, only security updates and bug fixes. Rolling Release distros package and distribute software as soon as it's available upstream (the software developer's repos), meaning that there are no versions and no specific schedule.
- "Stable" (Debian Stable) vs. "Bleeding edge" (Arch): Stable distros are generally point release, and focus on fixing bugs and security flaws at the expense of new features. Each version goes through a lenghty period of feature freeze, testing and bug fixing before release. Stability here not only means trouble-free operation, but more importantly consistent behavior over time. Things won't evolve, but things won't break. At least until the next release. Bleeding edge distros, which often follow the rolling release model (there are outliers like Fedora which are mostly bleeding edge yet have point releases), on the other hand, are permanently evolving. By constantly pushing the latest version of each software package, new features, new bugs, bug fixes, security updates and sometimes breaking changes are released continuously. Note that this is not a binary, there is a very large continuum between the stablest and the most bleeding edge distro.
- "Community" (Fedora) vs. "Commercial" (RHEL): Despite the name, Community distros are not only maintained by volunteers, but can also be developed by some company's employees and can be sponsored by commercial entities. However, the main difference with Commercial distros is that they're not a product destined to be sold. Commercial distros like Red Hat's RHEL, SuSE Linux Enterprise or Ubuntu Pro are (supposed to be) fully maintained by their company's employees and target businesses with paid support, maintenance, fixes, deployment, training etc.
- "x package manager" vs. "y package manager", "x package format" vs. "y package format": It doesn't matter. Seriously.
apt
,dnf
orpacman
, to name a few, all have the exact same purpose: install and update software on your system and manage dependencies. - "general purpose" (Linux Mint) vs. "niche" (Kali Linux): General purpose distros are just that: distros that can do pretty much anything. Some are truly general purpose (like Debian), and have no bias towards any potential use, be it for a server, a desktop/laptop PC, some IOT or embedded devices, containers etc., some have various flavors depending on intended use (like Fedora Workstation for desktops and Fedora Server for, you guessed it, servers) but are still considered general purpose. They aim for maximum hardware compatibility and broad use cases. At the opposite end, niche distros are created for very specific and unique use cases, like pentesting (Kali), gaming (Nobara), music production (AV Linux) etc. They tend to have a lot of specific tools preinstalled, nonstandard defaults or modified kernels that may or may not work properly outside of their inteded use case.
- "team" (Any major distro) vs. "single maintainer" (Nobara): Pretty self explanatory. Some distros are maintained by a single person or a very small group of people. These distros do not usually last very long.
- "traditional" (Fedora Workstation) vs. "atomic" (Fedora Silverblue): In traditional distros, everything comes from a package. Every single component is individually installable, upgradeable, and deletable. Updating a package means deleting its previous version and replacing it with a new one. A power failure during an update lead to a partial upgrade and can make a system unbootable. Maybe a new package was bad and breaks something. Almost nothing prevents an unsuspecting user from destroying a core component. To mitigate risks and ensure a coherent system at each boot, atomic (also called transactional or immutable) distros, pioneered by Fedora Silverblue and Valve's SteamOS, were born. Like mobile phone OSes, the base system is a single image, that gets installed, alongside the current running version and without modifying it, and becomes active at the next reboot. As updates are isolated from one another, if the new version doesn't work the user can easily revert to a previous, functional version. Users are expected to install Flatpaks or use Distrobox, as installing (layering) packages is not as straightforward as with standard distros.
- "OG" (Debian) vs. "derivative" (Ubuntu): Original distros are directly downstream of their components' source code repositories, and do most of the heavy lifting. Because of the tremendous amount of work it represents, only a few distros like Debian, Arch, Slackware or Fedora have the history, massive community and sometimes corporate financial backing to do this. Other distros reuse most packages from those original distros and add, replace or modify some of them for differenciation. For example, Debian is the parent of almost all deb-based distros like Ubuntu, which itself is the parent of distros like Mint or Pop!_OS.
What are the main components of a distro, ie. a Linux-based operating system?
All distros provide, install and maintain, among other things, the following components:
- Boot and core system components (these are generally out-of-scope for beginners, unless you need to fix something, but you should at least know they exist):
- A boot manager (GRUB, systemd_init, etc.): Boots the computer after the motherboard POSTs, lets you choose what to start
- An init system (systemd, etc.): Starts everything needed to run the computer, including the kernel
- A kernel (Linux): Has control over everything, main interface for software to discuss with hardware
- Command-line environment, to interact with he computer in text mode:
- A shell (bash, zsh, fish etc.): The main interface for command-line stuff
- Command-line tools (GNU, etc.): Standard suite of command-line tools + default tools chosen by the distro maintainers
- User-installable command-line tools and shells
- Graphical stack for desktop/laptop computers:
- Display servers (X11, Wayland compositors): Handle drawing stuff on screens
- A Desktop environment (Plasma, Gnome, XFCE etc.): The main graphical interface you'll interact with everyday.
- User-facing applications (browsers, text processors, drawing software etc.): Some are generally installed by default and/or are part of a desktop environment's suite of software, most are user-installable.
- A package manager (apt, dnf, pacman, yast etc.): Installs, deletes, updates and manages dependencies of all software installed on the machine.
Which are the main Desktop Environments and which one should I choose?
As a new user, this is basically the only thing you should concern yourself about: choosing a first Desktop environment. After all, it will be your main interface for the weeks/years to come. It's almost as important as choosing your first distro. These are a few common choices that cater to different tastes:
- Gnome: Full featured yet very minimalist, Gnome is a great DE that eschews the traditional Desktop metaphor. Like MacOS, out of the box, it provides its strongly opinionated developers' vision of a user experience. Fortunately, unlike MacOS, there are thousands of extensions to tweak and extend the looks and behaviour of the DE. Dash-to-dock or Dash-to-panel are great if you want a more MacOS-like or Windows-like experience, Blur My Shell is great if you love blurry transparent things, Appindicator is a must, and everything else is up to you. Gnome's development cycle is highly regular and all core components and apps follow the same release schedule, which explains why a lot of distros choose it as their default DE.
- KDE Plasma: Full featured and maximalist, Plasma does not cater to a single design philosophy, is very flexible and can be tweaked almost ad infinitum. This may be an advantage for people who like to spend hours making the perfect environment, or a disadvantage as the possibilities can be overwhelming, and the added complexity may compromise stability, bugginess or completeness. There is not yet a single development cycle for core components and apps, which makes it a bit more difficult for distro maintainers and explains why there are so few distros with Plasma as the flagship DE. The KDE team is however evolving towards a more regular update cycle.
- Cinnamon: Forked from Gnome 3 by the Linux Mint team who disliked the extreme change of user experience it introduced, Cinammon provides a very traditional, "windows-like", desktop-metaphor experience in a more modern software stack than the older DEs it takes inspiration from. Cinnamon still keeps a lot in common with Gnome by being simple and easy to use, yet heavily modifiable with themes, applets and extensions.
- Lightweight DEs for old or underpowered machines: The likes of XFCE, LXDE, LXQt are great if you want to ressurect an old machine, but lack the bells and whistles of the aforementioned DEs. If your machine is super old, extremely underpowered and has less than a few Gb of RAM, don't expect miracles though. A single browser tab can easily dwarf the RAM usage and processing power of your entire system.
As for which one you should choose, this is entirely up to you, and depends on your preferences. FYI, you are not married to your distro's default desktop environment. It's just what comes preinstalled. You can install alternative DEs on any distro, no need to reinstall and/or distro-hop.
How do I install stuff on Linux?
Forget what you're used to do on Windows of MacOS: searching for your software in a seach engine, finding a big "Download" button on a random website and running an installer with administator privileges. Your package manager not only keeps you system up to date, but also lets you install any software that's available in your distro's repositories. You don't even need to know the command line, Gnome's Software or Plasma's Discover are nice graphical "App Stores" that let you find and install new software.
Flatpak are a great and more recent recent alternative to distro packages that's gaining a lot of traction, and is increasingly integrated by default to the aforementioned App Stores. It's basically a "universal" package manager system thet sits next to your system, that lets software developers directly distribute their own apps instead of offloading the packaging and distribution to distro maintainers.
Choosing a first distro
As discussed before, there is a metric fuckload (or 1.112 imperial fucktons) of distros out there. I advise you to keep it as mainstream as possible for your first steps. A distro with a large user base, backed by a decently large community of maintainers and contributors and aimed at being as fuss-free as possible is always better than a one-person effort tailored to a specific use-case. Choose a distro that implements well the DE of your choice.
What are great distros for beginners?
The following are great distros for beginners as well as more advanced users who just want to have a system that needs almost no configuration out of the box, just works and stays out of the way. Always read the installation documentation thoroughly before attempting anything, and follow any post-install requirements (for example, installing restricted-licence drivers on Fedora).
- Fedora Workstation: Clean, sensible, modern and very up to date and should work out of the box for most hardware. Despite being sponsored by Red Hat (who are getting a lot of justified hate for moving RHEL away from open-source), this is a great community distro for both beginners and very advanced users (including the Linus Torvalds). Fedora is the flagship distro for the Gnome Desktop Environment, but also has a fantastic Plasma version. Keywords: Point Release, close to Bleeding Edge, Community, dnf/rpm, large maintainer team, traditional, original.
- Linux Mint: Mint is an Ubuntu (or Debian for the LMDE variant) derivative for beginners and advanced users alike, that keeps Ubuntu's hardware support and ease of use while reverting its shenanigans and is Cinammon's flagship distro. Its main goal is to be a "just works" distro. Keywords: Point Release, halfway between Stable and Bleeding Edge, Community, apt/deb, smallish maintainer team but lots of contributors, traditional, derivative (Ubuntu or Debian).
- Pop!_OS: Backed by hardware Linux vendor System76, this is another Ubuntu derivative that removes Snaps in favor or Flatpaks. Its heavily modified Gnome DE looks and feels nice. In a few months/years, it will be the flagship distro for the -promising but still in development- Cosmic DE. Keywords: Point Release, halfway between Stable and Bleeding Edge, commercially-backed Community, apt/deb, employee's maintainer team, traditional, derivative (Ubuntu).
- If you want something (advertised as) zero-maintenance, why not go the Atomic way? They are still very new and there isn't a lot of support yet because they do things very differently than regular distros, but if they wort OOTB on your system, they should work reliably forever. Sensible choices are uBlue's Aurora (Plasma), Bluefin (Gnome) or Bazzite (gaming-ready), which are basically identical to Fedora's atomic variants but include (among other things) restricted-licence codecs and QOL improvements by default, or OpenSUSE's Aeon (Gnome). Keywords: Point Release, Bleeding Edge, Community, rpm-ostree, large maintainer team, Atomic, sub-project (Fedora/OpenSUSE).
Which power-user distros should I avoid as a beginner, unless I reaaaally need to understand everything instead of being productive day one?
These are amongst the very best but should not be installed as your first distro, unless you like extremely steep learning curves and being overwhelmed.
- Debian Stable: as one of the oldest, still maintained distros and the granddaddy of probably half of the distros out there, Debian is built like a tank. A very stringent policy of focusing on bug and security fixes over new features makes Debian extremely stable and predictable, but it can also feel quite outdated. Still a rock-solid experience, with a lot to tinker with despite very sensible defaults. It is an incredible learning tool and is as "Standard Linux" as can be. Debian almost made the cut to "beginner" distros because of its incredible reliability and massive amount of documentation available, but it might be a bit too involved for an absolute beginner to configure to perfection. Keywords: Point Release, Stable as fuck, Community, apt/deb, large maintainer team, traditional, original.
- Arch: The opposite of Debian in philosophy, packages often come to Arch almost as soon as the source code is released. Expect a lot of manual installation and configuration, daily updates, and regularly fixing stuff. An incredible learning tool too, that will make you intimate with the inner workings of Linux. The "Arch btw" meme of having to perform every single install step by hand has taken a hit since Arch has had a basic but functional installer for a few years now, which is honestly a good thing. I work in sofware. A software engineer who does every single tedious task manually instead of automating it is a shit software engineer. A software engineer who prides themself from doing every single tedious task manually should seriously reconsider their career choices. Arch's other main appeal is the Arch User Repository or AUR, a massive collection of user-created, automated install scripts for pretty much anything. Keywords: Rolling Release, Bleeding-edge, Community, pacman/pkg, large maintainer team, traditional, original.
Which distro should I avoid, period?
- Ubuntu: despite having a huge mind-share as the beginner distro, Ubuntu suffers from it's parent company's policy to make Ubuntu kinda-Linux-but-not-really and a second-rate citizen compared to their Ubuntu Pro commercial product. Some of the worst takes in recent years have been pushing Snaps super agressively in order to get some "vendor-lock-in", proprietary walled-garden ecosystem with exclusive commercial apps, forcibly installing snaps even when explicitely asking for a .deb package through
apt
, baking ads and nags into major software or only delivering critical security patches to Pro customers. Fortunately, there are some great derivatives like Mint or Pop!_OS cited above that work equally well but revert some of the most controversial decisions made by Canonical. - Manjaro: Manjaro might seem appealing as a "user-friendlier" Arch derivative and some of its tools are fantastic to remove some configuration burden, but ongoing mismanagement issues and the fact that it needs Arch-style regular maintenance as updates often break stuff prevent it from being a truly beginner distro. Manjaro also has a highly irregular update schedule that's weeks behind Arch, making using the AUR extremely dangerous, as it always expects a fully up-to-date Arch system.
- Any single-maintainer or tiny team distros like Nobara or CachyOS. They might be fantastic distros made by exceptional people (I have mad respect for Nobara's maintainer Glorious Eggroll and his work on Proton-GE), they are most often derivatives so the heavy lifting is already done by their parent distro's maitainers, but there is too much risk involved. Sometimes life happens, sometimes people move on to other projects, and dozens of small distros get abandonned every year, leaving their users dead in the water. Trusting larger teams is a much safer bet in the long term.
- Anything that refuse to use standards for ideological reasons like Alpine Linux, Devuan or Artix. Don't get me wrong, not using any GNU tools or systemd is a cool technological feat and developing alternatives to the current consensus is how things evolve. However, these standard tools have a long history, hundreds if not thousands of maintainers and are used by millions, meaning there's a huge chance your specific issue is already solved. Refusing to use them should be reserved to very advanced users who perfectly understand what they're gaining and losing. As a beginner to intermediate level, it will at best make most of the documentation out there irrelevant, at worst make your life a miserable hell if you need to troubleshoot anything.
Philosophical questions, or "I've seen people arguing over the Internet and now I'm scared"
You've done your research, you're almost ready to take the plunge, you even read a lot of stuff on this very community or on the other website that starts with a "R", but people seem very passionately for or against stuff. What should you do?
Shoud I learn the command line?
Yes, eventually. To be honest, nowadays a lot of things can be configured on the fly graphically, through your DE's settings. But sometimes, it's much more efficient to work on the command line, and sometimes it's the only way to fix something. It's not that difficult, and you can be reasonably productive by understanding just about a dozen very simple commands.
I have a very old laptop/desktop, should I use a distro from its era?
Noooo!. Contrary to Windows and MacOS which only work correctly on period-correct computers, Linux runs perfectly well on any hardware from the last 20 to 30 years. You will not gain performance by using an old distro, but you will gain hundreds of critical security flaws that have been since corrected. If you need to squeeze performance out of an old computer, use a lightweight graphical environment or repurpose it as a headless home server. If it's possible, one of the best ways to breathe new life into an old machine is to add some RAM, as even lightweight modern sofware will struggle with less than a few Gb.
Should I be concerned about systemd?
No. In short, systemd is fine and all major distros have switched to systemd years ago. Even the extremely cautious people behind Debian have used systemd as default since 2015. Not wanting to use systemd is a niche more rooted in philosophical and ideological rather than practical or technical reasons, and leads to much deeper issues than you should concern yourself with as a beginner.
Should I be concerned about XOrg/Wayland?
Yes and No, but mostly No. First off, most distros install both Wayland and XOrg by default, so if one is not satisfying to you, try the other. Remember in the preamble when I said nVidia was a bad actor? Well, most of people's complaints about Wayland are because of nVidia and their shitty drivers, so GTX/RTX users should stay on XOrg for now. But like it or not, XOrg is dead and unmaintained, and Wayland is the present and future. XOrg did too many things, carried too many features from the 80's and 90's and its codebase is a barely maintainable mess. X11 was born in a time when mainframes did most of the heavy lifting and windows were forwarded over a local network to dumb clients. X11 predates the Internet and has basically no security model. Wayland solves that by being a much simpler display protocol with a much smaller feature set adapted to modern computing and security. The only downside is that some very specific functionalities based on decades of X11 hacking and absolute lack of security can be lost.
I want to play some games, should I look for a gaming distro?
No. General purpose distros are perfectly fine for gaming. You can install Steam, Lutris, Heroic, Itch etc. and use Proton just fine on almost anything. Even Debian. In short, yes, you can game on Linux, there are great tutorials on the internet.
Should I be concerned about Flatpaks and/or Snaps vs. native packages?
Not really. Flatpaks are great, and more and more developers package their apps directly in Flatpak format. As a rule of thumb, for user facing applications, if your app store gives you the choice between Flatpak and your native package manager version, choose the most recent stable version and/or the one packaged by the developer themselves (which should often be the Flatpak anyway). Snaps however are kinda bad. They are a Canonical/Ubuntu thing, so as long as you avoid Ubuntu, its spins and its derivatives that still include Snaps, you should be fine. They tend to take a lot longer to startup than regular apps or Flatpaks, the snap store is proprietary, centralized and Canonical controls every part of it. Also, Canonical is very aggressive in pushing snaps to their users, even forcing them even when they want to install an apt
package. If you don't care, have fun.
I need/want program "x", but it is only available on distro "y" and not on mine. I've been told to ditch my beloved distro and install the other one, should I?
No. Generally, most software is intallable from your distro's package manager and/or Flatpak. But sometimes, your distro doesn't package this program you need, or an inconsiderate developer only distributes a random .deb on their Github release page. Enter Distrobox. It is a very simple, easy to use command line tool that automates the creation of other Linux distros containers using Docker or Podman (basically, tiny, semi-independant Linuxes that live inside your regular Linux), and lets you "export" programs installed inside these containers to you main system so you can run them as easily and with almost the same performance as native programs. Some atomic distros like uBlue's variants even include it by default. That .deb we've talked about before? Spin a Debian container and dpkg install
the shit out of it. Absolutely need the AUR? Spin an Arch container and go to town.
Acknowledgements
Thanks to everyone who helped improve this guide: @[email protected], @[email protected], @[email protected], @[email protected], @[email protected], @[email protected], @[email protected], @[email protected], @[email protected], @[email protected] ...and many others who chimed in in the comments <3
Link to version 1: https://lemm.ee/post/15895051
Welcome to the monthly update for openSUSE Tumbleweed for June 2024. This month was busy with events like the Community Summit in Berlin and the openSUSE Con...
![Tumbleweed Monthly Update - June 2024](https://lemmy.ml/pictrs/image/5476e278-0404-47b7-8a71-cee0f1fa983b.png?format=webp&thumbnail=256)
Welcome to the monthly update for openSUSE Tumbleweed for June 2024. This month was busy with events like the Community Summit in Berlin and the openSUSE Conference, but a number of snapshots continued to roll out to users. Developers, system administrators and users receive updates designed to enhance your experience and ensure high levels of security and performance.
Should readers desire a more frequent amount of information about snapshot updates, readers are encouraged to subscribe to the openSUSE Factory mailing list.
Let’s go!
New Features and Enhancements
- Linux Kernel 6.9.7: This kernel introduces several important fixes and enhancements across various subsystems. Key updates include addressing undefined references in netfilter when
CONFIG_SYSCTL
is disabled, correcting TCP Fast Open handling, and resolving a conflicting quirk in Advanced Linux Sound Architecture for Realtek devices. Improvements in file system writeback operations, multi-threaded path handling and memory management for Hisilicon crypto drivers enhance stability. Networking updates include fixes for race conditions in netpoll, enhancements for specific SFP modules, and improvements in WiFi drivers such as RTW89, Ath9k, Ath12k, and MT76. Additional platform-specific updates address issues in ACPI, ARM64 configurations, HID device handling, and Bluetooth driver fixes. - PipeWire 1.2.0 and WirePlumber 0.5.4: PipeWire 1.2.0 introduces asynchronous processing, node.sync-group for synchronized scheduling, and improved config parsing error reporting. It also adds mandatory metadata support for buffer parameters, multiple data-loops with CPU affinity, and dynamic log level adjustments. Key fixes include RTP-SAP module enhancements, ROC 0.3 support, and improved Bluetooth BAP broadcast code parsing. WirePlumber 0.5.4 refines the role-based linking policy, allowing role-based sinks alongside standard audio operations and enabling regular filters to act as best targets. It addresses startup crashes due to empty config files, improves Bluetooth profile auto-switching, and fixes issues with DSP filters and infinite loop scenarios in autoswitching scripts. Together, these updates enhance the flexibility, reliability, and overall performance of audio management in Linux environments. Both also received updates in snapshot 20240627
- Mesa and Mesa-drivers 24.1.2: Both packages underwent a specfile cleanup, involving the relocation of Rust crate sources into subprojects folders and updates to
baselibs.conf
. Due to the maintenance burden associated with Rust crates as system dependencies, these crates are now downloaded as vendored dependencies, as detailed in the README-suse-maintenance.md. The update adds support for building libvulkan\_nouveau, including necessary Rust crates such as paste-1.0.14, proc-macro2-1.0.70, quote-1.0.33, syn-2.0.39, and unicode-ident-1.0.12. However, building libvulkan\_nouveau on Leap is not possible due to the requirement for rust-cbindgen \>= 0.25. For more details, refer to the release notes at https://docs.mesa3d.org/relnotes/24.1.2. - KDE Plasma 6.1.1: Discover improves UI elements and Packagekit support, while Dr Konqi corrects the Sentry dbus interface usage. Plasma Addons addresses reference issues in Effects/cube, and krdp ensures version compatibility and resolves session controller bugs. Kscreenlocker improves greeter functionality, and KWin introduces multiple fixes for shaders, tiling, and input panels. Libkscreen and libplasma update protocol versions and fix plugin loading issues. Plasma Desktop enhances task icon sizing, panel opacity and file dragging across screens. Plasma Audio Volume Control removes unnecessary symlinks, and Plasma Systemmonitor correctly positions loading overlays. Powerdevil improves battery protection UI and limits backlighthelper calls.
- Python-setuptools 70.0: Key features in this new major version include emitting warnings for ignored [tools.setuptools] entries in
pyproject.toml
, improved error messaging forpkg_resources.EntryPoint.require
and handlingNone
location distributions more gracefully. The update also refreshes unpinned vendored dependencies, supports PEP 625 by standardizing package name and version in filenames and ensures encoding consistency for.pth
files. Obsolete Python \< 3.8 code has been removed, andpkg_resources
now usesstdlib
importlib.machinery
. Bug fixes address race conditions in the install command, improve handling of nested namespaces withpackage_dir
and correct variouspkg_resources
method behaviors. The patch for reproducibility has also been refreshed. - Xen 4.18.2\_06: This version resolves intermittent system hangs when Power Control Mode is set to Minimum Power. Patches also improve CPU mask handling and interrupt movement in various scenarios. Upstream bug fixes include improvements in scheduler resource data management and include fixes for building with GNU Compiler Collection 14.
Key Package Updates
- NetworkManager 1.48.2: This package updates support for matching OVS system interfaces by MAC address and fixes port reactivation and VPN secrets handling for 2-factor authentication. It saves connection timestamps during shutdown for proper autoactivation after restart. Key changes in 1.48.0 deprecate autotools building, add support for changing OpenSSL ciphers for 802.1X authentication, and set unmanaged device reasons in the
StateReason
property visible in nmcli. Additionally, it replaces themac-address-blacklist
property withmac-address-denylist
, improves WiFi 6 GHz band detection and optimizes performance to avoid high CPU usage during route updates. Previous version 1.46 adds brought dynamic SSID-based stable IDs, randomized MAC addresses and several enhancements for handling IPv6, D-Bus and cloud setup. - ibus-table 1.17.6: This update drops Python2 support, transitioning all scripts to Python3 using pyupgrade. It now allows the use of keys with Unicode keysyms in keybindings, enhancing customization and flexibility. Additionally, the
frames_per_buffer=chunk_size
option is now utilized inself._paudio.open()
for improved audio handling. The update also includes translation enhancements from Weblate, with Czech translations reaching 36.6 percent, Japanese at 45.3 percent, and Chinese (Simplified) at 92.0 percent. - btrfsprogs 6.9: The
mkfs
utility now halts if the mount status cannot be determined when using the--force
option and corrects the minimum size calculation for zoned devices. The check command removes the--clear-ino-cache
option, shifting its functionality to therescue
command group, and adds detection and repair for incorrect file extent itemram_bytes
values. The qgroup commands now sync the filesystem before searching for stale entries, handle uncleaned subvolumes andsquota
enabled scenarios, and display the cleaning status of subvolumes. Thereceive
command fixes stream parsing for strict alignment hosts, andtune change-csum
anddump-tree
commands include updates for handlingdev-replace
status items. Theconvert
command improves extent iteration for preallocated/unwritten extents. The build process now ensures compatibility with e2fsprogs 1.47.1 and improves header file dependency tracking. Documentation was also updated. - GNU’s Emacs 29.4: An emergency bugfix took place in this release. In this update, arbitrary shell commands are no longer executed when enabling Org mode, significantly enhancing security by preventing the execution of potentially malicious commands.
Bug Fixes
-
Python-dnspython 2.6.1:
- CVE-2023-29483 - Eventlet before 0.35.2 in dnspython allows remote "TuDoor" DNS attack interference.
-
php8 8.3.8:
- CVE-2012-1823 involved a vulnerability where attackers could inject arguments into PHP-CGI, leading to potential security issues. The new vulnerability, CVE-2024-4577, was discovered to bypass this original fix, allowing the same or similar types of argument injection attacks. The update ensures that this bypass is no longer possible, reinforcing the security measures originally put in place for CVE-2012-1823.
- Similarly, the bypass of CVE-2024-1874 was made with the fix to CVE-2024-5585.
-
kernel-firmware-nvidia-gspx-G06 (NVIDIA GPU driver)
- CVE-2024-0090 was a vulnerability where a user can cause an out-of-bounds write.
- CVE-2024-0091 was a vulnerability where a user can cause an untrusted pointer dereference. A successful exploit of this vulnerability might lead to denial of service.
- CVE-2024-0092 was an improper check or improper handling of exception conditions might lead to denial of service.
-
XZ 5.6.2:
- CVE-2024-3094 Through a series of complex obfuscations, the liblzma build process extracts a prebuilt object file from a disguised test file existing in the source code, which is then used to modify specific functions in the liblzma code. This results in a modified liblzma library that can be used by any software linked against this library, intercepting and modifying the data interaction with this library. More details in snapshot 20240605
-
cJSON v1.7.17:
- CVE-2024-31755 - A segmentation violation, which can trigger through the second parameter.
Conclusion
The month of June 2024 saw a range of significant updates, security fixes and enhancements. The Linux Kernel 6.9.7 update improved stability and performance. Mesa and Mesa-drivers 24.1.2 introduced Rust crate dependencies and improved Vulkan support. KDE Plasma 6.1.1 brought UI improvements and a major version of Python-setuptools 70.0 arrived for rolling release users. A few critical security vulnerabilities were taken care of and fixes related to the XZ backdoor continued, so that Tumbleweed remains secure, efficient and feature-rich for all users.
For those Tumbleweed users who want to contribute or want to engage with detailed technological discussions, subscribe to the openSUSE Factory mailing list . The openSUSE team encourages users to continue participating through bug reports, feature suggestions and discussions.
Contributing to openSUSE Tumbleweed
Your contributions and feedback make openSUSE Tumbleweed better with every update. Whether reporting bugs, suggesting features, or participating in community discussions, your involvement is highly valued.
More Information about openSUSE:
Official
Fediverse
(Image made with DALL-E)
Welcome to the monthly update for openSUSE Tumbleweed for May 2024. This month has seen a significant number of updates, enhancements, and crucial security f...
![openSUSE Tumbleweed Monthly Update - May 2024](https://lemmy.world/pictrs/image/18096fe9-2f71-48f8-ad97-0f3c90bd90f2.png?format=webp&thumbnail=256)
Welcome to the monthly update for openSUSE Tumbleweed for May 2024. This month has seen a significant number of updates, enhancements, and crucial security fixes. Whether you are a developer, a system administrator, or a casual user, these updates are designed to enhance your experience and ensure the highest level of security and performance.
Should readers desire a more frequent amount of information about snapshot updates, readers are encouraged to subscribe to the openSUSE Factory mailing list.
Let’s go!
New Features and Enhancements
- Linux Kernel 6.9.1: The month of May had a couple updates for the Kernel, but so far remains at version 6.9.1, which addresses various issues and enhancing overall stability. The mt76 driver for wifi saw improvements with the addition of missing chanctx operations for the mt7915 wifi card, enhancing functionality. A critical fix was made to the keys subsystem to prevent overwriting key expiration during instantiation, improving security. Support for system suspend/hibernation was enhanced for the Modem Host Interface subsystem with the addition of the
mhi_power_down_keep_dev()
Application Programming Interfaces, which is beneficial for maintaining device states during power management operations. - LLVM 18.1.6: Subpackages that were updated were clang-tools, clang18, libLLVM18, libclang-cpp18, libclang13, llvm18-gold. Fixed issues with generating incorrect thunks for functions with aligned parameters or incorrect return value passing when StructRet was used.
-Xclang
-target-feature
-Xclang +unaligned-scalar-mem
for enabling unaligned scalar memory accesses on CPUs without unaligned vector access support were introduced. Build failures when compiling AVX512 code with-march=native
on machines without AVX512 were addressed. Crashes in the AArch64 backend related tofcmp
instruction operands being true or false at the IR level were fixed and there was a fix to compiler crashes. - KDE Frameworks 5.116.0: Breeze Icons received new icons for
audio/ogg
andaudio/x-vorbis+ogg
file types, as well as theaudio/vnd.wave
MIME type, enhancing support for audio file formats. Extra CMake Modules had notable updates including the dropping of attempts to set IMPORTED on targets with installed configurations inecm_add_qch
. KFileMetaData saw a fix with the handling of attribute namespacing and improved metadata accuracy and processing. KService addressed a warning related to the "mimeTypex-scheme-handler/file
not found" issue. - udisks2 2.10.1: This update features updated Ukrainian and German translations, improvements to testing for LVM2 RAID by wiping used devices, settling down before checking properties and rescanning vdevs after tests. Offline and online filesystem grow tests were added, and documentation for the Filesystem.Size property was clarified. A fix was implemented for Python class invocation in nvme tests, and a --no-partition-scan option was added for the loop-setup command in udisksctl. A
--no-partition-scan
option for theloop-setup
command in udisksctl was added. - firewalld 2.1.2: The update to 2.1.2 includes several fixes: the policy now allows forwarding ports with the
to-addr
foregress-zone=HOST
, the range check for large rule limits in rich rules has been corrected, and skip detection in thefw-in-container
environment has been fixed during testing. - snapper 0.11.0: The update introduces asynchronous cleanup of stale btrfs qgroups and reverts some parts to fix the build in the Open Build Service. The cleanup service is now set to run every hour and qgroups are disabled if they do not exist to avoid failure when creating snapshots. Support for quarterly snapshots has been added, and a table-style selection is now based on codeset.
- GTK3 3.24.42: Printing is improved by avoiding access to freed printers. Wayland fixes include correct monitor sizes, a crash related to tablet removal, inferred resizable edges for tiled windows, and ensuring commits occur soon after acknowledging a configure.
GTK4 4.14.4: A crash issue when there is no child was resolved and efficiency improvements were made in loading symbolic SVGs and handling color-free symbolics. Accessibility updates include making the gtk-demo sidebar search more accessible and stopping the emission of focus events. GDK introduced support for
XDG_ACTIVATION_TOKEN
and made defensive improvements for dmabuf. These improvements include handling unknown formats more carefully and using a narrower range for YUV formats. - Mozilla Firefox 126.0. The browser brought had a major update and fixed 16 Common Vulnerabilities and Exposures. There was arbitrary JavaScript execution in PDF.js fixed with CVE-2024-4367. A potential permissions request bypass via clickjacking was fixed for CVE-2024-4764. There were memory safety bug fixes addressing CVE-2024-4778 and CVE-2024-4777; the latter helps with those for Firefox ESR 115.11 and Thunderbird 115.11.
sssd 2.9.5: The update introduces a new configuration option called
failover_primary_timeout
. This option allows users to configure how often SSSD tries to reconnect to a primary server after successfully connecting to a backup server. Previously, this interval was hardcoded to 31 seconds, which remains the default value. - openldap2 2.6.7: The liblber library fixes a missing newline on long messages and libldap addresses exit handling issues with OpenSSL3, TLS usage with multiple LDAP URIs OpenSSL cipher suite handling and handling of Diffie-Hellman parameter files with OpenSSL 3.0. The slapd service now honors the disclose option in matchedDN handling, improves regex testing in ACLs, and fixes sync replication with glued databases.
- iproute2 6.9: The update introduces several new features and improvements: The
m_mirred
module now allows mirroring to block and thetc
command addsNLM_F_ECHO
support for actions and filters. Theip
command has been enhanced with coupled\_control support for bonding and a new monitor command for IOAM6. - xwayland 24.1.0: The feature release addresses several regressions introduced in previous release candidate versions. The
eglstreams
support has been dropped. - AppStream 1.0.3: Key features include enhanced validator checks to ensure description lists aren't translated, improved translation checks for descriptions and the ability to propagate selected custom entries to catalog output via the CLI compose command. Many other features were added.
Key Package Updates
- tpm2-0-tss 4.1.0: This updated provided a major security fix for CVE-2024-29040. Various bug fixes were implemented, including correcting the length check on FAPI auth callbacks, fixing the deviation from the CEL specification and resolving json syntax errors in FAPI profiles that were previously ignored by json-c. The update also adds support for new features and enables the usage of external keys for Fapi\_Encrypt.
- postgresql16 16.3: A fix was made for CVE-2024-4317, which could allow for an unprivileged database user to read most common values and other statistics from
CREATE STATISTICS
commands of other users. - Python 3.x versions had a fix for CVE-2023-6597 A vulnerability was discovered in the CPython. It affected versions 3.12.1, 3.11.7, 3.10.13, 3.9.18, 3.8.18, and earlier. This class would incorrectly follow symlinks during cleanup when there were permission errors. As a result, users with the ability to run privileged programs could potentially change the permissions of files pointed to by symlinks under certain conditions.
Bug Fixes
-
glib2 2.80.2:
- CVE-2024-34397 - An issue in GNOME GLib allows spoofed D-Bus signals, affecting client behavior
-
- CVE-2024-33861 - QStringConverter's invalid pointer callback can modify the stack, risking vulnerabilities in applications using QStringDecoder.
-
libxml2 2.12.7
- CVE-2024-34459 - Buffer over-read in xmllint --htmlout can cause vulnerabilities in libxml2 before 2.12.7.
-
libarchive 3.7.4:
- CVE-2024-26256 - Remote Code Execution Vulnerability.
-
krb5 added some patches to fix memory leaks related to:
-
ovmf
- CVE-2022-36763 -
EDK2
vulnerability inTcg2MeasureGptTable()
allows heap buffer overflow via local network
- CVE-2022-36763 -
-
python-Jinja2 3.1.4:
- CVE-2024-34064 - Jinja's
xmlattr
filter vulnerability allows non-attribute characters in keys, risking XSS attacks.
- CVE-2024-34064 - Jinja's
-
tpm2-0-tss 4.1.0:
- CVE-2024-29040 is a flaw that allows an attacker to generate arbitrary quote data, which may not be detected by Fapi\_VerifyQuote.
Conclusion
The month of May 2024 had a steady flow of crucial security fixes, important updates, and notable enhancements across various packages for openSUSE Tumbleweed. The updates to the Linux Kernel, LLVM, KDE Frameworks and numerous other components ensure that Tumbleweed systems remain feature-rich and keep rolling. Developers and users alike benefit from the improvements, enhancements and new features.
For those Tumbleweed users who want to contribute or want to engage with detailed technological discussions, subscribe to the openSUSE Factory mailing list . The openSUSE team encourages users to continue participating through bug reports, feature suggestions and discussions.
Contributing to openSUSE Tumbleweed
Your contributions and feedback make openSUSE Tumbleweed better with every update. Whether reporting bugs, suggesting features, or participating in community discussions, your involvement is highly valued.
What is the community's opinion of Pop!_OS?
It’s an Ubuntu downstream maintained by Linux box maker System76 which is targeted for both general usability and design/media applications. They will soon be debuting their own home-spun desktop environment, Cosmic DE, which is highly anticipated by the Linux community.
How does the community here feel about this distribution and the company that has brought it to us? How do you feel about the projects that they’re working on, and their goals for the distribution moving forward?
Unable to install updates on Nobara 38 b/c the operation would result in removing the following protected packages: nobara-amdgpu-config
I'm trying to install system updates on my gaming PC, which runs on Nobara 38. Typically I'd accomplish this in the command line by issuing dnf upgrade
, but it refuses to update because doing so would remove the protected package nobara-amdgpu-config
. Trying --skip-broken
produces the same result.
How do I get past this issue or work around it so that I can install updates?
Command line output:
``` [yo_scottie_oh@nobara ~]$ sudo dnf upgrade Last metadata expiration check: 0:33:19 ago on Sat 06 Apr 2024 05:57:10 PM EDT. Error: Problem: The operation would result in removing the following protected packages: nobara-amdgpu-config (try to add '--skip-broken' to skip uninstallable packages) [yo_scottie_oh@nobara ~]$ sudo dnf upgrade --skip-broken Last metadata expiration check: 0:33:42 ago on Sat 06 Apr 2024 05:57:10 PM EDT. Error: Problem: The operation would result in removing the following protected packages: nobara-amdgpu-config [yo_scottie_oh@nobara ~]$ sudo dnf update nobara-login [sudo] password for scott: Last metadata expiration check: 0:43:46 ago on Sat 06 Apr 2024 05:57:10 PM EDT. Error: Problem: The operation would result in removing the following protected packages: nobara-amdgpu-config (try to add '--skip-broken' to skip uninstallable packages) [yo_scottie_oh@nobara ~]$ nobara-sync
Option “-x” is deprecated and might be removed in a later version of gnome-terminal.
Use “-- ” to terminate the options and put the command line to execute after it.
[yo_scottie_oh@nobara ~]$ ```
EDIT: I'm still attempting to solve this on my own. Trying solutions found in this Super User thread and this Reddit thread, which points to this documentation on the Nobara project site.
EDIT 2: Issuing nobara-sync
seems to have done the trick. The Nobara project documentation that I linked to above explains why they recommend nobara-sync
instead of dnf upgrade
.
Cycle through windows | apps
Following is very subjective and probably varies from distro to distro, de to de, app to app, user to user.
For the longest time, I believed Ctrl+Tab and Ctrl+Shift+Tab was the only way of navigation through apps and windows. Many years ago, some editor introduced me to the behavior that Ctrl+Tab switches to the last used tab. I hated that behavior. I didn't understand it and it was annoying. Luckily you could switch to the old way (in my experience) which I did.
How do you guys cycle through windows?
What is the best way for switching? Is there a standard or at least an attempt for a standard? Or at least a name for different styles?
App / Window switching
I switch and highlight apps by pressing Meta+Tab, or Meta+Shift+Tab. This works very good. I use PaperWM, a window tiling feature in GNOME such that I have no overlapping windows and don't need to care about the position of the windows anymore for the most part. When I press Ctrl+i, the window to the right of the highlighted window moves below the current window and both adjust in size to half the screen.
Cycle right isn't the proper way of going forward doesn't apply here anymore unless I define it as a zig zag movement.
Luckily, we have arrow keys. With, Meta+[Up,Down,Left,Right] I can move to any window. The shortcoming is that I need two hands because Meta is on the left and the arrow are on the right side of the keyboard. Having to use two hands is a big no-go for a fundamental command in my opinion. What's the solution to this? Ctrl+[W,S,A,D]? Does it clash with other main fundamental keybindings?
Kate uses Alt+Arrow to cycle through tabs. It uses Ctrl+Tab to cycle through time.
If you use Ctrl+Arrow to cycle through the windows, you can use Ctrl+(Shift+)Tab for cycling through time, i.e. last used tab/window.
In the browser, I navigate via Ctrl+Tab. There are no tabs below the current tab. btw, why not, mozilla? Kate and Pulsar (Atom successor) have Ctrl+N as the default for a new document (and hence tab).
For consistency, I want to use either Ctrl+T or Ctrl+N for a new document/window. Which standard do you guys use and prefer? Other apps with other keybindings?
Ctrl+Tab is good for a linear movement but Ctrl+Arrow is more logical.
I used to use Alt+F4 to quit apps. Recently, I discovered that you can use Ctrl+w to quit a tab and Ctrl+q to close a window. Wouldn't it be better to use Ctrl+q to close a tab and Meta+q to close the window?
Currently, I default to
- Ctrl+Arrow is for tab bidimensional motion.
- Meta+Arrow is for window bidimensional motion.
- Ctrl+Tab is for tab time-dimensional motion.
- Meta+Tab is for window time-dimensional motion.
- Which is better Ctrl+T or Ctrl+N for a new tab/document? Is it good that there is a distinction?
- Shift always reverses the action
I can't find a way to customize the keybindings in firefox, does that mean that I have to default to [Ctrl,Meta]+Tab to cycle through tabs/windows?
Working instructions for OpenRazer on Fedora Silverblue?
Probably a longshot, but hoping anyone here might have working instructions on getting OpenRazer running under Fedora Silverblue. I recently picked up some Huntsman V2s and while OpenRGB works for basic control, I'd like to see what other options are available.
Apparently there is a known incompatibility between Silverblue and how OpenRazer implements kernel modules (link). I've seen elsewhere that some users have tweaked the build files to work around this, but I couldn't find any detailed info. Any help would be appreciated.
EDIT:
I got it working, but it wasn't worth the trouble compared to simply running OpenRGB in a flatpak. For Razer keyboard users, you'll gain one or two RGB presets over OpenRGB, such as Reactive, and the ability to adjust the polling rate (the merits of which are highly debatable). You'll lose secure boot and kernel verification unless you also add the ublue repo and signing key rpm (ublue-os-akmods-addons
).
If anyone wants to do it anyway, I had success by downloading and installing the following ublue-os akmod rpms from here:
- akmod-openrazer-100.0.0.git.530.886f986d-1.fc39.x86_64.rpm
- kmod-openrazer-100.0.0.git.530.886f986d-1.fc39.x86_64.rpm
- openrazer-kmod-common-100.0.0.git.530.886f986d-1.fc39.x86_64.rpm
(Note: you might need to layer the kernel-devel
package first; I had it layered already so I can't confirm.)
Add the openrazer repo, then install the daemon and frontend app:
curl -o - https://download.opensuse.org/repositories/hardware:/razer/Fedora_$(rpm -E %fedora)/hardware:razer.repo | sudo tee /etc/yum.repos.d/razer.repo rpm-ostree install openrazer-meta razergenie
Add the plugdev group to /etc/group, then add your user to it:
sudo bash -c 'grep "plugdev" /lib/group >> /etc/group' sudo gpasswd -a $USER plugdev
Finally, launch RazerGenie...
[!](https://lemmy.ca/pictrs/image/b6036739-8980-48a7-abdb-956f3622eb4f.png)
"Help me choose my first distro" and other questions for beginners
You're about to take your first steps in the wonderful world of Linux, but you're overwhelmed by the amount of choices? Welcome to this (I hope) very simple guide :)
The aim of this guide is to provide simple, clear information to ease your transition as a beginner. This is not a be-all-end-all guide nor an advanced guide.
Preamble
Make sure your hardware is compatible
Nowadays most relatively recent hardware works perfectly fine on Linux, but there are some edge cases still. If you don't use niche hardware and your wifi card is supported, chances are you're golden. Please note that nVidia is a bad faith player in the Linux world, so if you have a GeForce GPU, expect some trouble.
Make sure your favourite apps are either available or have a good replacement on Linux
If some proprietary app is essential to your workflow and is irreplaceable, consider running it in a VM, keeping a Windows partition for it or try and run it through Wine (this is advanced stuff though).
Be aware that Linux is not Windows/MacOS
Things work differently, and this is normal. You will probably struggle at the beginning while adjusting to a new paradigm. You may have to troubleshoot some things. You may break some things in the process. You will probably get frustrated at some point or another. It's okay. You're learning something new, and it can be hard to shed old habits forged by years on another system.
What are the best resources out there?
Arch Wiki without a doubt. Despite being heavily tied to Arch, most of its content is readily usable to troubleshoot most modern distros, as the building blocks (Kernel, systemd, core system apps, XOrg/Wayland, your DE of choice etc.) are the same.
Okay, now to the most important questions
Which distro should I use?
There are a metric fuckload (or 1.112 imperial fucktons) of distros out there, but these can be broadly put into two main categories: general-purpose distros and niche-distros. I advise you to keep it as mainstream as possible for your first steps. A distro with a large user base, backed by a large community of maintainers and aimed at being as fuss-free as possible is always better than a one-person effort tailored to a specific use-case.
Beginner distros
These are great distros for beginners as well as more advanced users who just want to have a system that needs almost no configuration out of the box, just works and stays out of the way.
- Fedora Workstation: Clean, sensible, modern and very up to date and should work out of the box for most hardware. Despite the community's rightful backlash against Red Hat, this is still a great distro for beginners and advanced users. Even Linus Torvalds himself favors Fedora as a daily driver. Fedora is the flagship distro for the Gnome Desktop Environment.
- Linux Mint: While I haven't used it myself, there is a lot of praise here for this Ubuntu derivative from beginners and advanced users alike. Its main goals are ease of use and being the flagship distro for the Cinnamon DE, which is very similar to Windows and may ease the transition for new users.
- Pop!_OS: Backed by hardware Linux vendor System76, this Ubuntu derivative shares some of the issues with its infamous parent, but its heavily modified Gnome DE looks and feels nice.
- I do not recommend Ubuntu nor Manjaro: despite being marketed as "beginner friendly distros", and despite often running perfectly fine, these two have major issues in management, packaging policies or philosophy that might make your life as a beginner difficult. Ubuntu suffers from it's parent company's goal to make Ubuntu kinda-Linux-but-not-really, and there are some great derivatives like the ones cited above that work equally well but revert some of the most controversial decisions made by Canonical. Manjaro might seem appealing as a "beginner-friendly" Arch derivative and some of its tools are fantastic to remove some configuration burden, but ongoing mismanagement issues and the fact that it needs regular maintenance as updates often break stuff prevent it from being a truly beginner distro.
Advanced distros
So you've taken your first steps, you're starting to be really comfortable with Linux, and you want to get your hands dirty and really learn what's happening under the surface? These should not be installed as your first distro, unless you like extremely steep learning curves and being overwhelmed.
- Debian: as one of the oldest, still maintained distros and the granddaddy of probably half of the distros out there, Debian is built like a tank. A very stringent policy of focusing on bug and security fixes over new features makes Debian extremely stable and predictable, but it can also feel a bit outdated. Still a rock-solid experience, with a lot to tinker with despite very sensible defaults. It is an incredible learning tool and is as "Standard Linux" as can be.
- Arch: The opposite of Debian in philosophy, packages often come to Arch almost as soon as the source code is released. Expect a lot of manual installation and configuration, daily updates, and regularly fixing stuff. An incredible learning tool too, that will make you intimate with the inner workings of Linux.
Which Desktop Environment should I use?
This is entirely up to you, and depends on your preferences.
- Gnome: Full featured yet very minimalist, Gnome is a great DE that eschews the traditional Desktop metaphor. Like MacOS, out of the box, it provides the strongly opinionated developers' vision of a user experience. Fortunately, unlike MacOS, there are thousands of extensions to tweak and extend the looks and behaviour of the DE. Dash-to-dock or Dash-to-panel are great if you want a more MacOS-like or Windows-like experience, Blur My Shell is great if you love blurry transparent things, Appindicator is a must, and everything else is up to you. Gnome's development cycle is highly regular and all core components and apps follow the same release schedule, which explains why a lot of distros choose it as their default DE.
- KDE Plasma: Full featured and maximalist, Plasma does not cater to a single design philosophy, is very flexible and can be tweaked almost ad infinitum. This may be an advantage for people who like to spend hours making the perfect environment, or a disadvantage as the possibilities can be overwhelming, and the added complexity may compromise stability, bugginess or completeness. There is no single development cycle for core components and apps, which makes it a bit more difficult for distro maintainers.
- Cinnamon: If you want the most "windows-like" experience out of the box, Cinnamon is great. As I have no experience with it, I'll let the Mint users praise it in the comments :D
- Lightweight DEs for old or underpowered machines: The likes of XFCE, LXDE, LXQt are great if you want to ressurect an old machine, but lack the bells and whistles of the aforementioned DEs.
Philosophical questions, or "I heard conflicting stuff over the Internet and now I'm scared"
You've done your research, you're almost ready to take the plunge, you even read a lot of stuff on this very community, but people seem very passionately for or against stuff. What should you do?
Shoud I learn the command line?
Yes, eventually. To be honest, nowadays a lot of things can be configured on the fly graphically, through your DE's settings. But sometimes, it's much more efficient to work on the command line, and sometimes it's the only way to fix something. It's not that difficult, and you can be reasonably productive by understanding just about a dozen very simple commands.
I have a very old laptop/desktop, should I use a distro from this era?
Noooo!. Contrary to Windows and MacOS which only work correctly on period-correct computers, Linux runs perfectly well on any hardware from the last 20 to 30 years. You will not gain performance by using an old distro, but you will gain hundreds of critical security flaws that have been since corrected. If you need to squeeze performance out of an old computer, use a lightweight graphical environment or repurpose it as a headless home server.
Should I be concerned about systemd?
No. In short, systemd is fine and all major distros have switched to systemd years ago. Even the extremely cautious people behind Debian have used systemd as default since 2015. Not wanting to use systemd is a niche more rooted in philosophical rather than practical or technical reasons, and leads to much deeper issues than you should concern yourself with as a beginner. (Thanks @[email protected] for the precisions)
Should I be concerned about XOrg/Wayland?
Yes and No, but mostly No. First off, most distros install both Wayland and XOrg by default, so if one is not satisfying to you, try the other. Remember in the preamble when I said nVidia was a bad actor? Well, most of people's complaints about Wayland are because of nVidia and their shitty drivers, so GeForce users should stay on XOrg for now. But like it or not, XOrg is dead and unmaintained, and Wayland is the present and future. XOrg did too many things, carried too many features from the 80's and 90's and its codebase is a barely maintainable mess. Wayland solves that by being just a simple display protocol with a much smaller codebase, and offloading feature development to the compositors.
Should I look for a gaming-focused distro?
No. General purpose distros are perfectly fine for gaming. You can install Steam, Lutris, Heroic, Itch etc. and use Proton just fine on almost anything. Even Debian. In short, yes, you can game on Linux, there are great tutorials on the internet.
Should I be concerned about Flatpaks and/or Snaps?
Not really. Flatpaks are great, and more and more developers package their apps directly in Flatpak format. As a rule of thumb, for user facing applications, if your app store gives you the choice between Flatpak and your native package manager version, choose the most recent version. Snaps however are a Canonical/Ubuntu thing, so as long as you avoid Ubuntu, its spins and its derivatives that still include Snaps, you should be fine. They tend to take a lot longer to startup than regular apps or Flatpaks, the snap store is proprietary, centralized and Canonical controls every part of it. If you're fine with that, have fun. (Thanks @[email protected] for the precisions)
Should I follow The Way?
Yes. One does not speak unless one knows. You can take your helmet off in public tho.
Feel free to help correct, expand, or simplify this guide :)
Any multiline zsh compatible shells?
Some time ago I found xonsh which is a python-based shell. It had really good multiline support, and I am searching for a shell with sameish multiline support as xonsh. Fish shell also has good multiline support, it is around the same level, but it is not posix compatible. I want a shell that has that kind of level of multiline, but zsh (bash is also fine) compatible.
Does anyone know of one?
edit: based on the replies, I get this is unclear. My problem with zsh is that if i press enter and it starts a new line, I can't get back to the prevous line, because a new prompt is started. In fish this is possible, all lines are one prompt. But, fish is not posix compatible. So, I guess I want a posix-compatible shell with fish-like lines (multiple line) editing. I wanted zsh support to keep using my custom oh-my-zsh prompt, but remaking it for a new shell is not a big problem. Sorry for being unclear.
edit 2:
solution is here!
Thanks to @[email protected] I started thinking and made the following:
When on the first line, enter accepts and alt-enter inserts a newline. When not on the first line, enter inserts a newline and alt-enter accepts.
Here is the code to put in your .zshrc
:
```shell
MULTILINE!!!
bindkey '^[e' push-line-or-edit
enter accepts when only one line found, else creates newline
function _zle_ml_enter { if ! [[ $BUFFER == $'\n' ]]; then zle accept-line else zle self-insert-unmeta fi } zle -N _zle_ml_enter bindkey '^M' _zle_ml_enter
alt-enter accepts when more than one line found, else creates newline
function _zle_ml_meta_enter { if [[ $BUFFER == $'\n' ]]; then zle accept-line else zle self-insert-unmeta fi } zle -N _zle_ml_meta_enter bindkey '[M' _zle_ml_meta_enter
```
edit:
changed if [[ "$BUFFERLINES" -le 1 ]]; then
to if ! [[ $BUFFER == *$'\n'* ]]; then
and if [[ "$BUFFERLINES" -gt 1 ]]; then
to if [[ $BUFFER == *$'\n'* ]]; then
for improving detection. Also added alt-e shortcut because I had that configured myself but forgot to add here.