[go: nahoru, domu]

Skip to main content

Reddit and its partners use cookies and similar technologies to provide you with a better experience.

By accepting all cookies, you agree to our use of cookies to deliver and maintain our services and site, improve the quality of Reddit, personalize Reddit content and advertising, and measure the effectiveness of advertising.

By rejecting non-essential cookies, Reddit may still use certain cookies to ensure the proper functionality of our platform.

For more information, please see our Cookie Notice and our Privacy Policy.

Get the Reddit app

Scan this QR code to download the app now
Or check it out in the app stores
r/openSUSE icon
r/openSUSE icon

r/openSUSE

members
online

openSUSE Frequently Asked Questions -- start here

Frequently Asked Questions (FAQs)

Please also look at the official FAQ on the openSUSE Wiki.

This post is intended to answer frequently asked questions about all openSUSE distributions and the openSUSE community and help keep the quality of the subreddit high by avoiding repeat questions. If you have specific contributions or improvements to FAQ entries, please message the post author or comment here. If you would like to ask your own question, or have a more general discussion on any of these FAQ topics, please make a new post.

What's the difference between Leap, Tumbleweed, and MicroOS? Which should I choose?

The openSUSE community maintains several Linux-based distributions (distros) -- collections of useful software and configuration to make them all work together as a useable computer OS.

Leap follows a stable-release model. A new version is released once a year (latest release: Leap 15.6, June 2024). Between those releases, you will normally receive only security and minor package updates. The user experience will not change significantly during the release lifetime and you might have to wait till the next release to get major new features. Upgrading to the next release while keeping your programs, settings and files is completely supported but may involve some minor manual intervention (read the Release Notes first).

Tumbleweed follows a rolling-release model. A new "version" is automatically tested (with openQA) and released every few days. Security updates are distributed as part of these regular package updates (except in emergencies). Any package can be updated at any time, and new features are introduced as soon as the distro maintainers think they are ready. The user experience can change due to these updates, though we try to avoid breaking things without providing an upgrade path and some notice (usually on the Factory mailing list).

Both Leap and Tumbleweed can work on laptops, desktops, servers, embedded hardware, as an everyday OS or as a production OS. It depends on what update style you prefer.

MicroOS is a distribution aimed at providing an immutable base OS for containerized applications. It is based on Tumbleweed package versions, but uses a btrfs snapshot-based system so that updates only apply on reboot. This avoids any chance of an update breaking a running system, and allows for easy automated rollback. References to "MicroOS" by itself typically point to its use as a server or container-host OS, with no graphical environment.

Aeon/Kalpa (formerly MicroOS Desktop) are variants of MicroOS which include graphical desktop packages as well. Development is ongoing. Currently Gnome (Aeon) is usable while KDE Plasma (Kalpa) is in an early alpha stage. End-user applications are usually installed via Flatpak rather than through distribution RPMs.

Leap Micro is the Leap-based version of an immutable OS, similar to how MicroOS is the immutable version of Tumbleweed. It is currently in the "release candidate" stage of development. It is also primarily recommended for server and container-host use, as there is no graphical desktop included.

JeOS (Just-Enough OS) is not a separate distribution, but a label for absolutely minimal installation images of Leap or Tumbleweed. These are useful for containers, embedded hardware, or virtualized environments.

How do I test or install an openSUSE distribution?

In general, download an image from https://get.opensuse.org and write (not copy as a file!) it directly to a USB stick, DVD, or SD card. Then reboot your computer and use the boot settings/boot menu to select the appropriate disk.

Full DVD or NetInstall images are recommended for installation on actual hardware. The Full DVD can install a working OS completely offline (important if your network card requires additional drivers to work on Linux), while the NetInstall is a minimal image which then downloads the rest of the OS during the install process.

Live images can be used for testing the full graphical desktop without making any changes to your computer. The Live image includes an installer but has reduced hardware support compared to the DVD image, and will likely require further packages to be downloaded during the install process.

In either case be sure to choose the image architecture which matches your hardware (if you're not sure, it's probably x86_64). Both BIOS and UEFI modes are supported. You do not have to disable UEFI Secure Boot to install openSUSE Leap or Tumbleweed. All installers offer you a choice of desktop environment, and the package selection can be completely customized. You can also upgrade in-place from a previous release of an openSUSE distro, or start a rescue environment if your openSUSE distro installation is not bootable.

All installers will offer you a choice of either removing your previous OS, or install alongside it. The partition layout is completely customizable. If you do not understand the proposed partition layout, do not accept or click next! Ask for help or you will lose data.

Any recommended settings for install?

In general the default settings of the installer are sensible. Stick with a BTRFS filesystem if you want to use filesystem snapshots and rollbacks, and do not separate /boot if you want to use boot-to-snapshot functionality. In this case we recommend allocating at least 40 GB of disk space to / (the root partition).

What is the Open Build Service (OBS)?

The Open Build Service is a tool to build and distribute packages and distribution images from sources for all Linux distributions. All openSUSE distributions and packages are built in public on an openSUSE instance of OBS at https://build.opensuse.org; this instance is usually what is meant by OBS.

Many people and development teams use their own OBS projects to distribute packages not in the main distribution or newer versions of packages. Any link containing https://download.opensuse.org/repositories/ refers to an OBS download repository.

Anyone can create use their openSUSE account to start building and distributing packages. In this sense, the OBS is similar to the Arch User Repository (AUR), Fedora COPR, or Ubuntu PPAs. Personal repositories including 'home:' in their name/URL have no guarantee of safety or quality, or association with the official openSUSE distributions. Repositories used for testing and development by official openSUSE packagers do not have 'home:' in their name, and are generally safe, but you should still check with the development team whether the repository is intended for end users before relying on it.

How can I search for software?

When looking for a particular software application, first check the default repositories with YaST Software, zypper search, KDE Discover, or GNOME Software.

If you don't find it, the website https://software.opensuse.org and the command-line tool opi can search the entire openSUSE OBS for anyone who has packaged it, and give you a link or instructions to install it. However be careful with who you trust -- home: repositories have absolutely no guarantees attached, and other OBS repositories may be intended for testing, not for end-users. If in doubt, ask the maintainers or the community (in forums like this) first.

The software.opensuse.org website currently has some issues listing software for Leap, so you may prefer opi in that case. In general we do not recommend regular use of the 1-click installers as they tend to introduce unnecessary repos to your system.

How do I open this multimedia file / my web browser won't play videos / how do I install codecs?

Certain proprietary or patented codecs (software to encode and decode multimedia formats) are not allowed to be distributed officially by openSUSE, by US and German law. For those who are legally allowed to use them, community members have put together an external repository, Packman, with many of these packages.

The easiest way to add and install codecs from packman is to use the opi software search tool.

zypper install opi
opi codecs

We can't offer any legal advice on using possibly patented software in your country, particularly if you are using it commercially.

Alternatively, most applications distributed through Flathub, the Flatpak repository, include any necessary codecs. Consider installing from there via Gnome Software or KDE Discover, instead of the distribution RPM.

Update 2022/10/10: opi codecs will also take care of installing VA-API H264 hardware decode-enabled Mesa packages on Tumbleweed, useful for those with AMD GPUs.

How do I install NVIDIA graphics drivers?

NVIDIA graphics drivers are proprietary and can only be distributed by NVIDIA themselves, not openSUSE. SUSE engineers cooperate with NVIDIA to build RPM packages specifically for openSUSE.

First add the official NVIDIA RPM repository

zypper addrepo -f https://download.nvidia.com/opensuse/leap/15.6 nvidia

for Leap 15.6, or

zypper addrepo -f https://download.nvidia.com/opensuse/tumbleweed nvidia

for Tumbleweed.

To auto-detect and install the right driver for your hardware, run

zypper install-new-recommends --repo nvidia

When the installation is done, you have to reboot for the drivers to be loaded. If you have UEFI Secure Boot enabled, you will be prompted on the next bootup by a blue text screen to add a Secure Boot key. Select 'Enroll MOK' and use the 'root' user password if requested. If this process fails, the NVIDIA driver will not load, so pay attention (or disable Secure Boot). As of 2023/06, this applies to Tumbleweed as well.

NVIDIA graphics drivers are automatically rebuilt every time you install a new kernel. However if NVIDIA have not yet updated their drivers to be compatible with the new kernel, this process can fail, and there's not much openSUSE can do about it. In this case, you may be left with no graphics display after rebooting into the new kernel. On a default install setup, you can then use the GRUB menu or snapper rollback to revert to the previous kernel version (by default, two versions are kept) and afterwards should wait to update the kernel (other packages can be updated) until it is confirmed NVIDIA have updated their drivers.

Why is downloading packages slow / giving errors?

openSUSE distros download package updates from a network of mirrors around the world. By default, you are automatically directed to the geographically closest one (determined by your IP). In the immediate few hours after a new distribution release or major Tumbleweed update, the mirror network can be overloaded or mirrors can be out-of-sync. Please just wait a few hours or a day and retry.

As of 2023/08, openSUSE now uses a global CDN with bandwidth donated by Fastly.com.

If the errors or very slow download speeds persist more than a few days, try manually accessing a different mirror from the mirror list by editing the URLs in the files in /etc/zypp/repos.d/. If this fixes your issues, please make a post here or in the forums so we can identify the problem mirror. If you still have problems even after switching mirrors, it is likely the issue is local to your internet connection, not on the openSUSE side.

Do not just choose to ignore if YaST, zypper or RPM reports checksum or verification errors during installation! openSUSE package signing is robust and you should never have to manually bypass it -- it opens up your system to considerable security and integrity risks.

What do I do with package conflict errors / zypper is asking too many questions?

In general a package conflict means one of two things:

  1. The repository you are updating from has not finished rebuilding and so some package versions are out-of-sync. Cancel the update, wait for a day or two and retry. If the problems persist there is likely a packaging bug, please check with the maintainer.

  2. You have enabled too many repositories or incompatible repositories on your local system. Some combinations of packages from third-party sources or unofficial OBS repositories simply cannot work together. This can also happen if you accidentally mix packages from different distributions -- e.g. Leap 15.6 and Tumbleweed or different architectures (x86 and x86_64). If you make a post here or in the forums with your full repository list (zypper repos --details) and the text of any conflict message, we can advise. Using zypper --force-resolution can provide more information on which packages are in conflict.

Do not ignore package conflicts or missing dependencies without being sure of what you are doing! You can easily render your system unusable.

How do I "rollback" my system after a failed or buggy update?

If you chose to use the default btrfs layout for the root file system, you should have previous snapshots of your installation available via snapper. In general, the easiest way to rollback is to use the Boot from Snapshot menu on system startup and then, once booted into a previous snapshot, execute snapper rollback. See the official documentation on snapper for detailed instructions.

Tumbleweed

How should I keep my system up-to-date?

Running zypper dist-upgrade (zypper dup) from the command-line is the most reliable. If you want to avoid installing any new packages that are newly considered part of the base distribution, you can run zypper dup --no-recommends instead, but you may miss some functionality.

I ran a distro update and the number of packages is huge, why?

When core components of the distro are updated (gcc, glibc) the entire distribution is rebuilt. This usually only happens once every few (3+) months. This also stresses the download mirrors as everyone tries to update at the same time, so please be patient -- retry the next day if you experience download issues.

Leap (current version: 15.6)

How should I keep my system up-to-date?

Use YaST Online Update or zypper update from the command line for maintenance updates and security patches. Only if you have added extra repositories and wish to allow for packages to be removed and replaced by them, use zypper dup instead.

The Leap kernel version is 6.4, that's so old! Will it work with my hardware?

The kernel version in openSUSE Leap is more like 6.4+++, because SUSE engineers backport a significant number of fixes and new hardware support. In general most modern but not absolutely brand-new stuff will just work. There is no comprehensive list of supported hardware -- the best recommendation is to try it any see. LiveCDs/LiveUSBs are an option for this.

Can I upgrade my kernel / desktop environment / a specific application while staying on Leap?

Usually, yes. The OBS allows developers to backport new package versions (usually from Tumbleweed) to other distros like Leap. However these backports usually have not undergone extensive testing, so it may affect the stability of your system; be prepared to undo the changes if it doesn't work. Find the correct OBS repository for the upgrade you want to make, add it, and switch packages to that repository using YaST or zypper.

Examples include an updated kernel from obs://Kernel:stable:backport (warning: need to install a new key if UEFI Secure Boot is enabled) or updated KDE Plasma environment.

See Package Repositories for more.

openSUSE community

What's the connection between openSUSE and SUSE / SLE?

SUSE is an international company (HQ in Germany) that develops and sells Linux products and services. One of those is a Linux distribution, SUSE Linux Enterprise (SLE). If you have questions about SUSE products, we recommend you contact SUSE Support directly or use their communication channels, e.g. r/suse.

openSUSE is an open community of developers and users who maintain and distribute a variety of Linux tools, including the distributions openSUSE Leap, openSUSE Tumbleweed, and openSUSE MicroOS. SUSE is the major sponsor of openSUSE and many SUSE employees are openSUSE contributors. openSUSE Leap directly includes packages from SLE and it is possible to in-place convert one distro into the other, while openSUSE Tumbleweed feeds changes into the next release of SLE and openSUSE Leap.

How can I contribute?

The openSUSE community is a do-ocracy. Those who do, decide. If you have an idea for a contribution, whether it is documentation, code, bugfixing, new packages, or anything else, just get started, you don't have to ask for permission or wait for direction first (unless it directly conflicts with another persons contribution, or you are claiming to speak for the entire openSUSE project). If you want feedback or help with your idea, the best place to engage with other developers is on the mailing lists, or on IRC/Matrix (https://chat.opensuse.org/). See the full list of communication channels in the subreddit sidebar or here.

Can I donate money?

The openSUSE project does not have independent legal status and so does not directly accept donations. There is a small amount of merchandise available. In general, other vendors even if using the openSUSE branding or logo are not affiliated and no money comes back to the project from them. If you have a significant monetary or hardware contribution to make, please contact the openSUSE Board directly.

Future of Leap, ALP, etc. (update 2024/01/15)

The Leap release manager originally announced that the Leap 15.x release series will end with Leap 15.5, but this has now been extended to 15.6. The future of the Leap distribution will then shift to be based on "SLE 16" (branding may change). Currently the next release, Leap 16.0, is expected to optionally make greater use of containerized applications, a proposal known as "Adaptable Linux Platform". This is still early in the planning and development process, and the scope and goals may still change before any release. If Leap 16.0 is significantly delayed, there may also be a Leap 15.7 release.

In particular there is no intention to abandon the desktop workflow or current users. The current intention is to support both classic and immutable desktops under the "Leap 16.0" branding, including a path to upgrade from current installations. If you have strong opinions, you are highly encouraged to join the weekly openSUSE Community meetings and the Desktop workgroups in particular.


If you have specific contributions or improvements to FAQ entries, please message the post author or comment here. If you would like to ask your own question or have a more general discussion on any of these FAQ entries, please make a new post.

The text contents of this post are licensed by the author under the GNU Free Documentation License 1.2 or (at your option) any later version.

I have personally stopped posting on reddit due to ongoing anti-user and anti-moderator actions by Reddit Inc. but this FAQ will continue to be updated.




Snapshots /home setup issue Snapshots /home setup issue

Having some issues getting snapshots setup on my home directory. When I installed Leap 15.6 I put /home on a separate drive, and it is formatted as btrfs.

Following the official guide here.
https://doc.opensuse.org/documentation/leap/reference/html/book-reference/cha-snapper.html#sec-snapper-homedirs

Getting pam_snapper installed is no problem

sudo zypper in pam_snapper

But when I go to actually create the config I get this error:

sudo snapper -c home_username create-config /home/myuser
IO Error (subvolume is not a btrfs subvolume)

However, it is definitely btrfs. Was setup this way initially, and confirmed here as well by running:

findmnt -no FSTYPE /home
btrfs

Here's also a snapshot of my Yast partition:

https://preview.redd.it/snapshots-home-setup-issue-v0-a57yk2hs2h9d1.png

Feel like I'm missing something simple here. Any help would be great.




Black artifacts in Max Payne 3 Black artifacts in Max Payne 3
How to… ?
https://preview.redd.it/black-artifacts-in-max-payne-3-v0-p8d25ymshf9d1.png

I'm seeing these black artifacts on blood, smoke and some other places. I've tried changing the WINE versions, changing Wayland to X11 and nothing fixed this issue. I tried using RAV=DEBUG and it also didn't fix anything. I pirated this game from FitGirl.

[System]
Operating System: openSUSE Tumbleweed 20240624
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.5-1-default (64-bit)
Graphics Platform: Wayland
[CPU]
Vendor: GenuineIntel
Model: Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz
Physical cores: 2
Logical cores: 4
[Memory]
RAM: 7.5 GB
Swap: 7.5 GB
[Graphics]
Vendor: Intel
OpenGL Renderer: Mesa Intel(R) HD Graphics 620 (KBL GT2F)
OpenGL Version: 4.6 (Compatibility Profile) Mesa 24.1.1 (git-6c377358a5)
OpenGL Core: 4.6 (Core Profile) Mesa 24.1.1 (git-6c377358a5)
OpenGL ES: OpenGL ES 3.2 Mesa 24.1.1 (git-6c377358a5)
Vulkan Version: 1.3.261
Vulkan Drivers: Intel(R) HD Graphics 620 (KBL GT2F) (1.3.278)
upvotes · comments

Nvidia open drivers. Nvidia open drivers.
Tech support

Hello all.

After 12 years my trusty old HP laptop has finally given up completely. Couldn't be bothered to diagnose further so I dunno what was up, and it is also not the point of this post.

I have bought a replacement laptop which should be here on Wednesday. It has an RTX 4060, so I've been reading up on the Nvidia drivers article on the OpenSUSE website.

It has to be said, as much as I love OpenSUSE, the documentation is lacking sometimes compared to things like the mighty Arch wiki. I know it needs community updates, but the point stands.

Anyway, my questions are:

From my understanding, a 4060 should work with the new open kernel modules, yes? But the article then also says to install proprietary stuff from the Nvidia repository.

Once I have installed the open kernel modules, will a simple

'zypper inr --repo NVIDIA'

suffice to install all the rest of the required bits and will it overwrite the open modules? Also, the laptop has an i7 14650HX, will I need to install SUSE prime too to offload GPU intensive tasks such as gaming? The wiki page makes out it is only for Optimus laptops.

Thanks a lot.

Edit: also, I've ignored a lot of the old Wayland Nvidia threads as they never applied to me. I'm deciding whether to remain with trusty ol' Xfce or install Plasma when my laptop arrives. Does Nvidia play nice with Wayland now? If I still need to run an X11 session, I'll just stick with Xfce.


Switched to SlowRoll : plasma-systemmonitor infinite loading Switched to SlowRoll : plasma-systemmonitor infinite loading
Tech support

Hey everyone !

Yesterday I decided to give SlowRoll a try since I was having issues with standard Tumbleweed. So I switched the repos to SlowRoll, and did a full system update.

It's all hunky-dory, it actually resolved some issues I had with KDE, except for the System Monitor that just loads infinitely now. When I try launching it from Konsole, here is what I get :

qt.svg: link #path2410 is undefined!
file:///usr/lib64/qt6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth"
file:///usr/lib64/qt6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding: Binding loop detected for property "target"

Any ideas about what could be the source of the issue ? I saw there was a bug report about binding loops and tried to reproduce these changes on my system without any luck...

[ETA] I found out it freezes inside KSysGuard::SensorFaceControllerPrivate::createGui, infinitely waiting for QWaitCondition::wait

[ETA2] I have no idea what was wrong but I finally fixed this by following these steps :

  • Download Tumbleweed's install media and boot from it

  • Select Upgrade and follow the process

  • Reboot to your system, login and open a console

  • Remove every repositories from past install using zypper rr

  • Re-add the default Tumbleweed repo : sudo zypper ar http://download.opensuse.org/tumbleweed/repo/oss/ temp

  • Reinstall the default repos (for good measure) using: sudo zypper in openSUSE-repos-Tumbleweed

  • Install Slowroll following these steps

  • Switch to TTY1 using Ctrl + Alt + F1 (to avoid crashes during update), login, and perform distrib update sudo zypper dup

  • Reboot using systemctl reboot

  • Make sure everything works, if not, do a full reinstall I guess ?


Fullscreening games on a second virtual desktop has started to cause issues, not sure how to properly diagnose. Fullscreening games on a second virtual desktop has started to cause issues, not sure how to properly diagnose.
Tech support

Like the title says, at some point over the past couple of days I've started to experience a bug. I'm thinking it's related to the update to KDE Plasma 6.1, and I may need to take this question over to the KDE sub but I figured I would start here. I usually have a Youtube video or Spotify running on my main virtual desktop while playing EU4 on my second. Now when I try to do so, I get a weird flickering and the content of my desktops just merges into one desktop, then it switches back and forth between the content sets (the game coming to the forefront, then the browser window, then the game, back and forth). It seems similar to this issue but I'm not certain that they're describing the exact same behavior, and the report itself is pretty old now. I'm happy to snapper rollback if I can figure out where exactly the problem started happening, I just want to make sure I'm taking the proper troubleshooting steps.

I've confirmed this isn't EU4 specific, and it only happens when a game is full-screened. Doesn't happen when a video is full-screened.

System info if it helps





TLauncher (Minecraft) not starting up TLauncher (Minecraft) not starting up

Hey guys, sorry for posting this here, I already posted this under r/TLAUNCHER but got no answers from there ( https://www.reddit.com/r/TLAUNCHER/comments/1dp6ub6/tlauncher_is_not_starting_up_on_opensuse/ )

So I got a Tumbleweed installment, and this TLauncher doesn't start up, I'm stuck at the popup loading screen. I checked all my java things, they seem to be installed:

$ java --version
openjdk 21.0.3 2024-04-16
OpenJDK Runtime Environment (build 21.0.3+9-suse-1.1-x8664)
OpenJDK 64-Bit Server VM (build 21.0.3+9-suse-1.1-x8664, mixed mode, sharing)

The terminal output is here: https://pastebin.com/nCxXWvjx

This keeps loading forever

And the oddest thing is that I can get this same launcher to work, on my MX Linux, so its something with OSTW I think. I was thinking if maybe apparmor is blocking something, so I disabled it but still nothing. Could it be the yast-alternatives? I'm in a bit confusion, but please any help is appreciated.

I'm on latest snapshot of TW 2024.06.25:

Operating System: openSUSE Tumbleweed 20240625
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.6-1-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
Manufacturer: MSI
Product Name: MS-7972
System Version: 2.0


Stuttering in Wayland Stuttering in Wayland

On my laptop after Wayland has been running for a while (I can't figure out how long as sometimes it starts very soon) I get stuttering when doing anything. Even after closing every program every few seconds the entire system pauses for a half second. I can't find any indication of a problem in logs (but I'm awful at reading logs and I'm not sure I'm looking at the right ones) but loading up the fps meter shows that framerate is dropping coinciding with the pauses and framerate is smooth when its not stuttering. Relogging does nothing, closing all programs does nothing, different account does nothing... Only restarting fixes it and that's for a short period of time (although I've had it run a few hours with no problem or it starts after a minute other times). CPU is not overheating, I don't think the swap is being used at all.... X11 runs fine, windows runs fine but I wanna run Wayland for improved animations and when its running well it also seems snappier.

I'm at a loss for how to start diagnosing this. Please help. Also wish I knew how to paste a codeblock on here but here are my system specs.

System:
Kernel: 6.9.5-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc
Console: pty pts/2 DM: SDDM Distro: openSUSE Tumbleweed 20240622
Machine:
Type: Laptop System: Dell product: Latitude E6540 v: 00 serial: Chassis: type: 9
serial:
Mobo: Dell model: 0VPH0Y v: A03 serial: part-nu: 05BE
uuid: 4c4c4544-0034-5010-8030-cac04f503133 UEFI: Dell v: A27 date: 06/13/2019
Battery:
ID-1: BAT0 charge: 42.0 Wh (100.0%) condition: 42.0/48.8 Wh (85.9%) volts: 12.5 min: 11.1
model: Samsung SDI DELL 5CGM4A7 type: Li-ion serial: status: full
CPU:
Info: quad core model: Intel Core i7-4800MQ bits: 64 type: MT MCP smt: enabled arch: Haswell
rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 2676 high: 2755 min/max: 800/3700 volts: 1.2 V ext-clock: 100 MHz cores:
1: 2684 2: 2618 3: 2666 4: 2703 5: 2735 6: 2581 7: 2755 8: 2672 bogomips: 43116
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Dell driver: i915 v: kernel
arch: Gen-7.5 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, HDMI-A-3, VGA-1
bus-ID: 00:02.0 chip-ID: 8086:0416 class-ID: 0300
Device-2: AMD Mars XTX [Radeon HD 8790M] vendor: Dell driver: radeon v: kernel arch: GCN-1
pcie: speed: 8 GT/s lanes: 8 ports: active: none empty: VGA-2 bus-ID: 01:00.0 chip-ID: 1002:6606
class-ID: 0300 temp: 55.0 C
Device-3: Microdia Integrated Webcam driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
lanes: 1 bus-ID: 1-1.5:3 chip-ID: 0c45:64d0 class-ID: 0e02
Display: server: X.org v: 1.21.1.12 with: Xwayland v: 24.1.0 compositor: kwin_wayland driver:
X: loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: crocus,radeonsi gpu: i915
tty: 110x28
Monitor-1: eDP-1 model: Samsung 0x4c48 res: 1920x1080 dpi: 142 size: 344x194mm (13.54x7.64")
diag: 395mm (15.5") modes: 1920x1080
API: EGL v: 1.5 hw: drv: intel crocus drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: crocus device: 2 drv: swrast surfaceless: drv: radeonsi inactive: gbm,wayland,x11
API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 24.1.2 note: console (EGL sourced)
renderer: OLAND (radeonsi LLVM 18.1.6 DRM 2.50 6.9.5-1-default), Mesa Intel HD Graphics 4600
(HSW GT2), llvmpipe (LLVM 18.1.6 256 bits)
API: Vulkan v: 1.3.283 layers: 1 surfaces: N/A device: 0 type: integrated-gpu driver: N/A
device-ID: 8086:0416
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Dell
driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403
Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
API: ALSA v: k6.9.5-1-default status: kernel-api with: aoss type: oss-emulator
Server-1: PipeWire v: 1.0.7 status: n/a (root, process) with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
Device-1: Intel Ethernet I217-LM vendor: Dell driver: e1000e v: kernel port: f080
bus-ID: 00:19.0 chip-ID: 8086:153a class-ID: 0200
IF: em1 state: down mac:
Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1
bus-ID: 03:00.0 chip-ID: 8086:08b1 class-ID: 0280
IF: wlp3s0 state: up mac:
Bluetooth:
Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 2-1.5:3 chip-ID: 8087:07dc class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running rfk-block:
hardware: no software: yes address: bt-v: 4.0 lmp-v: 6
Drives:
Local Storage: total: 756.4 GiB used: 61.03 GiB (8.1%)
ID-1: /dev/sda vendor: Intel model: SSDSA2CW300G3 size: 279.46 GiB speed: 3.0 Gb/s tech: SSD
serial: fw-rev: 0362 scheme: GPT
ID-2: /dev/sdb vendor: TeamGroup model: T253512GB size: 476.94 GiB speed: 6.0 Gb/s tech: SSD
serial: fw-rev: 4A0 scheme: GPT
Partition:
ID-1: / size: 460.91 GiB used: 61.02 GiB (13.2%) fs: btrfs dev: /dev/sdb2
ID-2: /boot/efi size: 511 MiB used: 5.8 MiB (1.1%) fs: vfat dev: /dev/sdb1
ID-3: /home size: 460.91 GiB used: 61.02 GiB (13.2%) fs: btrfs dev: /dev/sdb2
ID-4: /opt size: 460.91 GiB used: 61.02 GiB (13.2%) fs: btrfs dev: /dev/sdb2
ID-5: /var size: 460.91 GiB used: 61.02 GiB (13.2%) fs: btrfs dev: /dev/sdb2
Swap:
ID-1: swap-1 type: partition size: 15.53 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb3
Sensors:
System Temperatures: cpu: 59.0 C mobo: 56.0 C sodimm: SODIMM C gpu: radeon temp: 55.0 C
Fan Speeds (rpm): cpu: 3975
Info:
Memory: total: 16 GiB available: 15.53 GiB used: 3.84 GiB (24.7%) igpu: 32 MiB
Processes: 272 Power: uptime: 0h 6m states: freeze,mem,disk suspend: deep wakeups: 0
hibernate: platform Init: systemd v: 255 default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 52 Compilers: gcc: 13.3.0
Shell: Sudo (sudo) v: 1.9.15p5 default: Bash v: 5.2.26 running-in: pty pts/2 inxi: 3.3.35



Thorium Web Browser does not exist in OpenSUSE Thorium Web Browser does not exist in OpenSUSE
Web Browser

Thorium is an excellent web browser based on Chromium project. I love it a lot. Works like a charm. It is very resource efficient web browser. This helps me a lot on my office computer where the next best web browser in terms of efficiency is just Edge. I want to be able to sync my data between my office computer and home computer.

I just can't find find Thorium in OpenSUSE repository. Thorium website also prefers Debian based Linux distributions. I do not want to leave OpenSUSE as I have grown to like it a lot especially compared to all Debian based Linux distros and Fedora. I also don't want to use third party repo as I don't want to nuke my system.



How do I fix dependency conflicts during an update (Tumbleweed) How do I fix dependency conflicts during an update (Tumbleweed)

Hey folks,
so I haven't updated my system in 3 weeks or so (which I don't feel is too long of a timeframe).
When running zypper dup some conflicts came up, which I first tried solving by reinstalling the codecs through opi.
This didn't help though, because I still get this output.
Is it fine to go with the provided solution? I fear that this will somehow cause a chain reaction of conflicts down the line.
I'd be grateful for any help!

thank you in advance







DHCP server module for YAST? DHCP server module for YAST?

Does anyone know what the status is of the DHCP server module for the YAST control panel?

I remember there used to be one some time ago, and I would like to use it to configure a local DHCP server,

I know it can be done by manually editing config files and such, but the module for doing so with YAST was really nice and easy to use, I see that there is a community provided package in the software section of the OpenSUSE website, but after installing it and trying to launch it gives an error regarding importing namespace DnsServerAPI. Does anyone have any suggestions with how to get the YAST module to work?

Thank you.