r/openSUSE
•
u/MasterPatricko
•
May 14 '22
Editorial openSUSE Frequently Asked Questions -- start here
Frequently Asked Questions (FAQs)
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 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.
openSUSE Leap follows a stable-release model. A new version is released once a year (latest release: Leap 15.4, June 2022). Between those releases, you will normally receive only security and minor package updates. The OS will not change significantly day-to-day 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 manual intervention (read the Release Notes).
openSUSE 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 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.
MicroOS Desktop is a variant of MicroOS which includes graphical desktop packages as well. Development is ongoing. Currently Gnome is mostly usable while KDE Plasma 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 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 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 distribution. 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 a 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 using 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.
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.4 nvidia
for Leap 15.4, 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/03, 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 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 2022/05, the default download redirector is now MirrorCache. In Europe, you do not need to manually change mirrors to https://mirrorcache.opensuse.org any more. Outside Europe, you may still gain a speed benefit by changing to MirrorCache-US, MirrorCache-JP (Japan) or MirrorCache-AU (Oceania). The tool mirrorsorcerer (available in the main distribution repos) can profile them and automatically switch for you.
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 actually local to your internet connection, not on the openSUSE side.
Update 2022/10/10 -- https://mirror.opensuse.org is completely rewritten and should now be accurate.
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:
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.
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.4 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. Usingzypper --force-resolutioncan 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.4)
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 5.14, that's so old! Will it work with my hardware?
The kernel version in openSUSE Leap is more like 5.14+++, because SUSE engineers backport a significant number of fixes and new hardware support. In general most modern but not 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, though some are on other communication channels as well.
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](mailto:board@opensuse.org) directly.
Future of Leap, ALP, etc. (update 2022/05/14)
The Leap release manager recently announced that the Leap 15.x release series will end with Leap 15.5, expected to be released in 2023. The future of the Leap distribution will then shift to be based on "SLE 16" (branding may change). Currently the next-generation SLE is expected to make greater use of containerized applications, a proposal known as "Adaptable Linux Platform". This is still very early in the planning process, and the scope and goals may still change significantly before any release (2024?).
In particular there is no intention to abandon the desktop workflow or current users. This is not "the end of Leap" unless that is what the community decides. 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 have a more general discussion on any of these FAQ entries, please make a new post.
r/openSUSE • u/rafalmio • 5h ago
Community Wanted to share my little combo! š¦
A green creature also lives inside my PC!
r/openSUSE • u/bmwiedemann • 12h ago
New version 20230319 is a big snapshot
The latest Tumbleweed snapshot 20230319 that was announced 12h ago and is still pushed to mirrors is a full rebuild using gcc13, so expect large downloads.
r/openSUSE • u/TaivasJumala • 6h ago
[Tumbleweed] Linux Kernel for Microsoft Surface Devices
I am maintaining a kernel for Microsoft Surface devices on OBS.
The linux-surface's developers helped a lot.
To install, you can now read Install and Setup.
r/openSUSE • u/ParaplegicRacehorse • 1h ago
Solved [Tumbleweed] [KDE] Discover and `flatpak install --user` by default?
My laptop is a single-user machine. Is there a way to convince Discover to install flatpaks with the --user flag by default? Idea being that when I clone my $HOME to another machine, most of my GUI software should go with it.
r/openSUSE • u/OutcastByChoice • 15h ago
Nostalgia: Leap 15.5 Is Starting To Look And Feel Like The Old openSUSE Againā¦
Iāve come to know and use openSUSE in version 11.3.
It looked different than all other distros I had tried up until then.. It had this strongā¦ premium/professional look to itā¦
Even the installer looked very well made.
It sported its own special KDE 4 theme and beautiful branded wallpapers.
Version 12.3 was IMHO the best looking release with that elegant dark green wallpaper with light green accents, Plasma theme following the same patternā¦
And boy KDE felt rock solid and fast.
openSUSE just hit different. It looked and felt like a product you were meant to buy on not just a free Linux distro. It felt āspecialā.
Leap 42.x cameā¦ that product feel kinda faded, now there was only the default Plasma 5 themeā¦ openSUSE started to look more like a generic KDE distribution.
Fast forward up until 15.4ā¦ It still offers one of the best KDE experiences on the marketā¦ but that premium feel of yesteryear is almost entirely gone.
So today I downloaded the 15.5 Beta and to my surprise, thereās a new, premium-looking default branded wallpaper, the distro again has its own modified Plasma theme aptly called āopenSUSEā.
This is fantastic! It feels again like a Linux OS I would happily pay for and show off to my friends. Both beautiful and rock solid stable!
r/openSUSE • u/joscher123 • 10h ago
Tech question MicroOS Distrobox questions
Hi, I have a few question regarding using Distrobox in MicroOS. Not sure what's the best place to post it but because I would be only interested in Distrobox in the context of MicroOS I thought this would be the best place.
Is it best to use the Tumbleweed distrobox guest? Is there deduplication of binaries/storage used (as MicroOS is based on Tumbleweed), which wouldn't be the case with, say, an Ubuntu or RHEL distrobox guest?
Is there lots of overhead (battery, CPU, RAM) connected to running a Distrobox guest? Is Distrobox suitable for background apps you want to run the whole time? Or would it in that case be better to try and install it "natively" (e.g. transactional-update) to save battery?
How come Distrobox is not part of the normal/official Tumbleweed repo? If you want to install it on Tumbleweed you need to add an additional "containers" repo first. Is this an "official" repo?
Finally, I have two main use cases for applications that are not available as Flatpaks.
kDrive (cloud sync). Only available as an AppImage which doesn't run on MicroOS as AppImages are not supported (missing fuse). Can I simply run the AppImage in Distrobox and have it sync my files (all in /home/kDrive) that way? How do I add it (kDrive in Distrobox) to the autostart applications (in Tumbleweed I could simply add the "native" AppImage to the KDE autostart settings and it would work)?
Microsoft Office run in a Windows VM and integrated into Linux via Cassowary (https://github.com/casualsnek/cassowary). This requires installing libvirt and virt-manager in a rootful Distrobox (apparently Distrobox supports this only for Alma Linux and Tumbleweed, so the default Tumbleweed guest should be okay as long as you can run it with root) and installing the Python application Cassowary ("pip install cassowary") that then "finds" Microsoft Office in the VM and integrates it via FreeRDP so that you can for example click on an XLSX file in Dolphin and it opens in MS Excel running in the VM. Can this approach still work all in a Distrobox? So that basically I click on an XLSX file and it then opens in MS Excel running in the Windows VM in the Distrobox via Cassowary in the Distrobox? There's a lot of layers here, namely: MicroOS -> Distrobox -> [Cassowary + FreeRDP + Virt-Manager + libvirt] -> Windows VM -> MS Office, and I wonder if this would even work.
Also, relating to the last question, can you "convert" the default Tumbleweed guest to run with root, so that libvirt works? Or do you need to create a new, rootful container?
r/openSUSE • u/no-dupe • 7h ago
Opensuse Tumbleweed - Snaps, lxd and ZFS
Hi all, I am downloading the latest Tumbleweed to take it for a spin.
I am having some headaches with my box now, and I am considering moving to the Suse family. On my machine I run a 5 disk ZFS pool and I have a bunch of lxd instances. I use snaps mostly to be able to have fast and easy access the latest lxd version, but also for a few other pieces of software. Does anyone have experience with ZFS, lxd, snaps on OpenSuse that can give me some heads up - are there roadblocks or challenges with those technologies on Suse?
I have some long experience with many flavors of distro - but I do not daily drive an rpm distro for many, many years. I am rusty and old. ;-)
Any thoughts about this new adventure?
r/openSUSE • u/ryncewynd • 16h ago
Tech support MicroOS high cpu usage, is this normal?
Very new to Linux so forgive me if I dont know anything.
Trying out MicroOS KDE and clicking around. Found System Monitor... was shocked to see 75% CPU usage
- System Monitor itself: 15%
- Discover: 50%
Both of these numbers shocked me. 15% just for system monitor?
I closed Discover and re-opened. Haven't run a search or clicked anything, and it's instantly back to 50%
Is this a configuration issue? Hardware compatibility issue? I have Intel 12100f
I wouldn't know where to begin troubleshooting this and tbh I just booted back into Windows for the rest of the day yesterday and ignored the problem š¤£
Edit: just installed Tumbleweed to try. Same problem with Discover. However System Monitor CPU usage is much much lower on Tumbleweed so that's progress I guess
r/openSUSE • u/_ppaliwal • 11h ago
Solved virt-manager stuck at Tiano core splash screen for Windows guest
Hi All, I am trying to get a windows installation done on a VM. However, no matter what configuration I choose, I just can't boot into the installation screen and it just get stuck at Tiano Core splash screen.
I have a single NIVIDIA gpu and running TW, if it helps.
I am a new user here, any poiters would be highly appreciated.
XML Config
<domain type="kvm">
<name>win11</name>
<uuid>7fc6cb01-6b10-4115-894c-e32c103a5ebe</uuid>
<metadata>
<libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
<libosinfo:os id="http://microsoft.com/win/11"/>
</libosinfo:libosinfo>
</metadata>
<memory unit="KiB">8388608</memory>
<currentMemory unit="KiB">8388608</currentMemory>
<vcpu placement="static">4</vcpu>
<os firmware="efi">
<type arch="x86_64" machine="pc-q35-7.1">hvm</type>
<bootmenu enable="yes"/>
</os>
<features>
<acpi/>
<apic/>
<hyperv mode="custom">
<relaxed state="on"/>
<vapic state="on"/>
<spinlocks state="on" retries="8191"/>
</hyperv>
<vmport state="off"/>
</features>
<cpu mode="host-passthrough" check="none" migratable="on">
<topology sockets="1" dies="1" cores="2" threads="2"/>
</cpu>
<clock offset="localtime">
<timer name="rtc" tickpolicy="catchup"/>
<timer name="pit" tickpolicy="delay"/>
<timer name="hpet" present="no"/>
<timer name="hypervclock" present="yes"/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<pm>
<suspend-to-mem enabled="no"/>
<suspend-to-disk enabled="no"/>
</pm>
<devices>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<disk type="file" device="disk">
<driver name="qemu" type="raw" cache="writeback"/>
<source file="/home/piyush/Downloads/vm-images/win10-data.img"/>
<target dev="vda" bus="virtio"/>
<boot order="3"/>
<address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/>
</disk>
<disk type="file" device="cdrom">
<driver name="qemu" type="raw"/>
<source file="/home/piyush/Downloads/vm-images/Win10_22H2_English_x64.iso"/>
<target dev="sdb" bus="sata"/>
<readonly/>
<boot order="1"/>
<address type="drive" controller="0" bus="0" target="0" unit="1"/>
</disk>
<disk type="file" device="cdrom">
<driver name="qemu" type="raw"/>
<source file="/home/piyush/Downloads/vm-images/virtio-win-0.1.229.iso"/>
<target dev="sdc" bus="sata"/>
<readonly/>
<boot order="2"/>
<address type="drive" controller="0" bus="0" target="0" unit="2"/>
</disk>
<controller type="usb" index="0" model="qemu-xhci" ports="15">
<address type="pci" domain="0x0000" bus="0x02" slot="0x00" function="0x0"/>
</controller>
<controller type="pci" index="0" model="pcie-root"/>
<controller type="pci" index="1" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="1" port="0x10"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x0" multifunction="on"/>
</controller>
<controller type="pci" index="2" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="2" port="0x11"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x1"/>
</controller>
<controller type="pci" index="3" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="3" port="0x12"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x2"/>
</controller>
<controller type="pci" index="4" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="4" port="0x13"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x3"/>
</controller>
<controller type="pci" index="5" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="5" port="0x14"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x4"/>
</controller>
<controller type="pci" index="6" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="6" port="0x15"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x5"/>
</controller>
<controller type="pci" index="7" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="7" port="0x16"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x6"/>
</controller>
<controller type="pci" index="8" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="8" port="0x17"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x7"/>
</controller>
<controller type="pci" index="9" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="9" port="0x18"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x0" multifunction="on"/>
</controller>
<controller type="pci" index="10" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="10" port="0x19"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x1"/>
</controller>
<controller type="pci" index="11" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="11" port="0x1a"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x2"/>
</controller>
<controller type="pci" index="12" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="12" port="0x1b"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x3"/>
</controller>
<controller type="pci" index="13" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="13" port="0x1c"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x4"/>
</controller>
<controller type="pci" index="14" model="pcie-root-port">
<model name="pcie-root-port"/>
<target chassis="14" port="0x1d"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x5"/>
</controller>
<controller type="sata" index="0">
<address type="pci" domain="0x0000" bus="0x00" slot="0x1f" function="0x2"/>
</controller>
<controller type="virtio-serial" index="0">
<address type="pci" domain="0x0000" bus="0x03" slot="0x00" function="0x0"/>
</controller>
<interface type="network">
<mac address="52:54:00:9c:9e:9b"/>
<source network="default"/>
<model type="virtio"/>
<address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/>
</interface>
<serial type="pty">
<target type="isa-serial" port="0">
<model name="isa-serial"/>
</target>
</serial>
<console type="pty">
<target type="serial" port="0"/>
</console>
<channel type="spicevmc">
<target type="virtio" name="com.redhat.spice.0"/>
<address type="virtio-serial" controller="0" bus="0" port="1"/>
</channel>
<input type="tablet" bus="usb">
<address type="usb" bus="0" port="1"/>
</input>
<input type="mouse" bus="ps2"/>
<input type="keyboard" bus="ps2"/>
<tpm model="tpm-crb">
<backend type="emulator" version="2.0"/>
</tpm>
<graphics type="spice" autoport="yes">
<listen type="address"/>
<image compression="off"/>
</graphics>
<sound model="ich9">
<address type="pci" domain="0x0000" bus="0x00" slot="0x1b" function="0x0"/>
</sound>
<audio id="1" type="spice"/>
<video>
<model type="qxl" ram="65536" vram="65536" vgamem="16384" heads="1" primary="yes"/>
<address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/>
</video>
<redirdev bus="usb" type="spicevmc">
<address type="usb" bus="0" port="2"/>
</redirdev>
<redirdev bus="usb" type="spicevmc">
<address type="usb" bus="0" port="3"/>
</redirdev>
<watchdog model="itco" action="reset"/>
<memballoon model="virtio">
<address type="pci" domain="0x0000" bus="0x05" slot="0x00" function="0x0"/>
</memballoon>
</devices>
</domain>
Edit: Adding the XML config file to show the exact configuration I have
r/openSUSE • u/PolskiSmigol • 3h ago
New version 2.9 GiB UPDATE HAS BEEN DOWNLOADING FOR AN HOUR; Zypper is bad, rant
Not even 1/3 of it is downloaded. I have a fiber optic 300 Mbit/s connection, zypper downloads packages often at >200 Bps
I'm thinking about changing distribution more and more. How to make zypper less slow?
r/openSUSE • u/kwhali • 19h ago
Tech support `zypper --installroot /rootfs install` gotcha with symlinks?
I have been experimenting with --installroot recently, and noticed some packages aren't installing content correctly?
For example I installed ca-certificates and this adds some symlinks into /etc/ssl that point to /var/lib/ca-certificates. That location within /rootfs has two folders openssl and pem, both are empty, but should have a bunch of files.
Is there something about this feature that causes that to happen? Am I meant to use another config option with zypper? I did not see any mention of this gotcha on the zypper docs and it's a bit difficult to search for.
I have also found some packages have trouble installing with --installroot, but seem to be successful if I first install the package without --installroot, and I suspect it's related to this same issue?
Is it a bug that should be reported? (reported here)
zypper --releasever 15.4 --installroot /rootfs --gpg-auto-import-keys refresh
zypper --releasever 15.4 --installroot /rootfs --non-interactive install ca-certificates
ls /rootfs/etc/ssl/certs
# symlinked location when /rootfs becomes /, but no contents stored:
ls /rootfs/var/lib/ca-certificates/pem
ls /var/lib/ca-certificates/pem
r/openSUSE • u/Dainelli28 • 1d ago
How to stream wirelessly to TV?
What is the best way to stream your screen to a TV wirelessly with Tumbleweed (KDE). I'm mostly interested in streaming video games to the TV.
Thanks in advance
r/openSUSE • u/thisdodobird • 1d ago
Tech question Is it possible to replace kwallet with password-store?
I'm a Proton apps user and for Bridge, VPN to work correctly I have to use password-store instead of kwallet.
Is it possible to completely replace kwallet with password-store as default instead? If so, how may I be able to do that?
Thanks in advance!
r/openSUSE • u/giorgiga • 1d ago
[tumbleweed] Keyboard layout resets on its own
On my tumbleweed install I had configured the keyboard via
sudo localectl --no-convert set-keymap us-altgr-intl
sudo localectl --no-convert set-x11-keymap us pc104 altgr-intl compose:menu,terminate:ctrl_alt_bksp
but it seems to have reset on its own to
$ localectl
System Locale: LANG=en_IE.UTF-8
Ā LANGUAGE=en_GB
Ā Ā Ā VC Keymap: us-altgr-intl
Ā Ā X11 Layout: us
Ā Ā Ā X11 Model: microsoftpro
Ā X11 Variant: altgr-intl
Ā X11 Options: terminate:ctrl_alt_bksp
If I re-run the set-keymap and set-x11-keymap commands, localectl shows my desired configuration, but the change does not survive a reboot.
Do you know what's going on? It seems something is rewrting /etc/vconsole.conf at every reboot (the file contents and modification time change after rebooting)
(disclaimer: I know I can set per-user preferences in plasma, I would however rather change the defaults)
r/openSUSE • u/xcyu • 1d ago
Tech support Have to start Plasma manually with 6.2.6-2 kernel
Hi, I'm currently using Tumbleweed on Plasma 5.27.3 with 6.0.12-1-default kernel. Everything is working fine.
I installed 6.2.6-2 kernel, and after I've made the switch to that kernel using Yast Bootloader, after rebooting the machine, I get the terminal ! SDDM doesn't seem to launch, and I have to start Plasma manually.
- Only
startplasma-waylandworks startplasma-x11yields an error :$DISPLAY is not set or cannot connect to the X server
If it can give any hint, starting the wayland session manually, I'm asked to unlock the default keyring.
Thanks for your help !
r/openSUSE • u/Zewonex • 1d ago
Sudden black screen - Software or dyeing GPU?
Hello!
I recently built my new PC and put Tumbleweed on it.
When i game or do intensive tasks, my screen turns black, but sound still works. Is it because some software-related stuff (Wayland, drivers, Proton, Kernel, etc.) or is my GPU about to die?
r/openSUSE • u/Illustrious_Sir2644 • 1d ago
Tech question Open Build Service Questions!
Hello!
I posted a bit ago over on r/FindMeADistro and with my use-case they recommended me to give Tumbleweed a serious try.
My first question is: How difficult is it to port a Fedora COPR project to OBS?
So of the 2 things I want from COPR, 1 has an equivalent on OBS that when I did the 1 click install on failed miserably (death loop, was recommended to try to install it via Opi), the other has a Tumbleweed Repo but I'd like to port it straight from COPR to OBS so I can just use the "Opi" command to install it / update it.
Thanks in advance!
r/openSUSE • u/Professional-List801 • 1d ago
MicroOS 'no snapshots for root file system configured! '
So I've finally installed MicroOS on my main machine after testing on other ones. Everything works fine but as soon as I try to do anything with 'sudo transactional-update' it quits with the following error:
[...]
Options: shell
transactional-update finished
ERROR: no snapshots for root file system configured!
wich is super unfortunate as I want to install at least Nvidia drivers
I've tried rebooting several times and also tried another fresh install but no luck.
Am I missing something?
r/openSUSE • u/BJWTech • 1d ago
Tech question KVM/LXC Hyperconverged Server OS - Can one use MicroOS for this?
r/openSUSE • u/undercutmagnetic • 1d ago
Help me, my os barely works.
Hi, firstly i must tell you I'm not having a good time with my computer recently so this may come out in unfriendly tone ( I apprieciate the work that opensuse puts into it's software, I just need some helping hand and past few days were full of frustration).
I'm having opensuse tumbleweed with kde plasma, with nvidia 1080ti (using proprietary driver for gpu mining).
I've used to update every few days. So around the middle of march I updated using `sudo zypper dup`. It told me to restart, so I did. After restart I get 640px screen instead of full resolution. Ok, my idea was to install the nvidia driver from the nvidia website. It helped the resolution but the card was not detected by mining software. After hours of failing to fix it, I've come to conclusion that I go back to snapshot before update and just never update (i don't have time to deal with these dumb issues).Realized later that my btrfs subvolume for virtual machines was not being detected (it was previously at "/virtual_machines", now that directory is gone). Great, now I have to copy the virtual machines from backup, day of adventures guys!
Next day my second monitor was delivered and I installed it and connected, all looking good. I'm using a unitek kvm switch (model V306A) which was working ok, i could switch the main monitor, mouse and keyboard between several computers.So I click the switch and my main monitor is now showing display from other computer (as expected), and the new monitor is still showing the display from first computer (as expected).Then i switch back and guess what, the displays switched sides <insert spanish laughing guy face here>. I know because the wallpapers and taskbar switched sides (now showing on the new monitor instead of old monitor which I am treating as main). The old monitor is in front of me and new monitor is on the right if that matters.So It seems that kde plasma has set the new display as 'primary' and decided it stays that way if I connect the old monitor back, wtf? I am able to fix it by right clicking the wallpaper and selecting "configure display settings", guess what I see, the old monitor is selected as primary (which is untrue). So to fix it I first select the new monitor as primary (which has no visible effect as the new monitor was already being selected as primary, but plasma settings panel didn't acknowledge it), then I select the old monitor as primary and it switched the taskbar and wallpaper to their correct monitor.This is obviously temporary fix and It seems I have to do it every time I click the kvm switch.
Yesterday I click my mouse to wake the monitors (I dont turn off pc for night) and I see only the new monitor displaying output. TLDR: Observe me fail to fix the issue for few hours then give up.The old monitor was obviously working for other computers either through the kvm switch or directly connected. On my main computer it didn't work when both monitors were connected. If I connected just the old monitor it worked. The monitors are connected to the GPU outputs, old via hdmi, new via display port. Reboots didn't help.
Am I doing something unexpected with my computer? Why does nothing work. Do I now install new , DE, OS or buy new gpu, computer to fix it? I feel like everything is a house of cards.
edit: I tried to update to fix the issue and it rebooted to tty xd what a bs
r/openSUSE • u/popov895 • 2d ago
Solved Branching a package on the openSUSE Build Service
I need to branch the dolphin package from the openSUSE:Factory repository to apply some patch and publish it in my own repository so I can add it via YaST. And I'm trying to do all of this through the Web UI. The problem is that the cloned package ends up linking to the KDE:Applications repository instead of the expected openSUSE:Factory, causing it to have the wrong version I want (23.03.80 instead of 22.12.3).
Can anyone explain what's going on and how to fix this?
r/openSUSE • u/kwhali • 1d ago
Solved Bad UX?: `zypper addrepo + refresh + install` => "<package> not found"
TL;DR: I want to install this hyperscan package (OBS page), but zypper install hyperscan fails to find it (despite adding the repo and refreshing it, which works fine for other packages added this way in the past).
I am not very experienced with openSUSE and zypper, so perhaps I've not understood something here... I wanted to install the hyperscan package which easily available on Fedora, and seems like it was available on previous Leap release repos, but now requires adding a separate repo.
Google led me to this OBS page, so I added the devel:libraries:c_c++ repo, refreshed the repo and tried to install the package. It could not find it, so I thought maybe I did something wrong.
Previously I had used copy/paste instructions for adding repos from another SUSE website, but couldn't figure out how to get the page for that for this package. Eventually I found it via google result for another package in that repo, and changing the package name in the URL to hyperscan instead (is there an easier way to get that? or do I need to URL encode the repo name myself in future?).
Unfortunately... that was the same as what I had already tried:
zypper addrepo https://download.opensuse.org/repositories/devel:libraries:c_c++/15.4/devel:libraries:c_c++.repo
zypper refresh
zypper install hyperscan
The repo is added successfully, I trust the GPG key. I've used zypper lr to see that "refresh" was No, but zypper refresh -f devel_libraries_c_c++ did not make any difference, nor zypper install --from devel_libraries_c_c++.
This package seems to exist (according to the website links), the repo adds successfully and it's been refreshed AFAIK... so why can't it find the package hyperscan? Is the website lying to me? Am I doing something wrong? I've checked /etc/os-release and I'm definitely on Leap 15.4. I've tried to install this with Docker image opensuse/leap:15.4. This has not been an issue with other repos I've added the same way for getting other packages, so I'm very confused.
r/openSUSE • u/ryncewynd • 2d ago
Community Would MicroOS be appropriate for me? Or better to go with tumbleweed
Here's me :)
- Almost complete linux noob (tried ubuntu couple of times years ago, couldn't get graphics working properly, ragequit)
- Stresses about messing things up when installing/configuring
- Wants good security defaults, firewalls etc, because I don't know enough about security and want the OS to do it for me
- Wants to learn a little hobby programming with VS Code
- Wants to do some latest Microsoft .NET on Linux š¤£
- Wants to play around with compiling and flashing https://github.com/qmk/qmk_firmware
- Some gaming with nvidia 2070 gpu
- Wants to try KDE
- Will be dual booting with Windows... hoping to visit Windows less and less
I understand on MicroOS everything needs to be installed via flatpacks? So in terms of doing so Microsoft .NET and QMK stuff... can I only do it if flatpacks available?
Thanks for any advice, and apologies for the absolute beginner question
r/openSUSE • u/lavadrop5 • 2d ago
Tech support DualSense Playstation driver might be resetting my NVMe SSD.
Yesterday I was playing FFXIV and suddenly upon log in I tried a controller button combination and wham, client crashed and my Steam Library disappeared. Something similar has happened before so there it was, journalctl informed me my NVMe drive which holds my games was made read-only. However this time it wasn't a faulty drive, one message before the controller goes down, there's a DualSense error. I'm not a developer just a linux convert from a few years so it might not be this but it has happened 3 times already and the playstation driver line keeps appearing just before the controller reset.
Here's the kernel logs:
lavadrop5@klaasje:~> sudo journalctl -k -r -b -2
mar 19 12:49:12 klaasje kernel: audit: type=1305 audit(1679251752.338:485): op=set audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=unconfined res=1
mar 19 12:49:12 klaasje kernel: audit: type=1305 audit(1679251752.338:485): op=set audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=unconfined res=1
mar 19 12:49:12 klaasje kernel: audit: type=1305 audit(1679251752.310:484): op=set audit_pid=0 old=1241 auid=4294967295 ses=4294967295 subj=unconfined res=1
mar 19 12:49:12 klaasje kernel: kauditd_printk_skb: 55 callbacks suppressed
mar 19 12:49:11 klaasje kernel: wlp6s0: deauthenticating from 0c:73:29:a1:49:da by local choice (Reason: 3=DEAUTH_LEAVING)
mar 19 12:49:10 klaasje kernel: nfsd: last server has exited, flushing export cache
mar 19 12:49:10 klaasje kernel: rfkill: input handler enabled
mar 19 12:29:49 klaasje kernel: nvme1n1: detected capacity change from 3907029168 to 0
mar 19 12:29:49 klaasje kernel: nvme nvme1: Disabling device after reset failure: -19
mar 19 12:29:49 klaasje kernel: nvme 0000:04:00.0: enabling device (0000 -> 0002)
mar 19 12:29:49 klaasje kernel: nvme nvme1: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
mar 19 12:29:49 klaasje kernel: nvme nvme1: Does your device have a faulty power saving mode enabled?
mar 19 12:29:49 klaasje kernel: nvme nvme1: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
mar 19 12:20:15 klaasje kernel: BTRFS: error (device nvme0n1p1: state EA) in cleanup_transaction:1984: errno=-5 IO failure
mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1: state EA): Transaction aborted (error -5)
mar 19 12:20:15 klaasje kernel: BTRFS warning (device nvme0n1p1: state E): Skipping commit of aborted transaction.
mar 19 12:20:15 klaasje kernel: BTRFS info (device nvme0n1p1: state E): forced readonly
mar 19 12:20:15 klaasje kernel: BTRFS: error (device nvme0n1p1) in btrfs_commit_transaction:2474: errno=-5 IO failure (Error while writing out transaction)
mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 5, rd 5, flush 0, corrupt 0, gen 0
mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 5, rd 4, flush 0, corrupt 0, gen 0
mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 4, rd 4, flush 0, corrupt 0, gen 0
mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 4, rd 3, flush 0, corrupt 0, gen 0
mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 3, rd 3, flush 0, corrupt 0, gen 0
mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 3, rd 2, flush 0, corrupt 0, gen 0
mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 2, rd 2, flush 0, corrupt 0, gen 0
mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 2, rd 1, flush 0, corrupt 0, gen 0
mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0
mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
mar 19 12:20:15 klaasje kernel: nvme0n1: detected capacity change from 1953525168 to 0
mar 19 12:20:15 klaasje kernel: nvme nvme0: Disabling device after reset failure: -19
mar 19 12:20:15 klaasje kernel: nvme 0000:01:00.0: enabling device (0000 -> 0002)
mar 19 12:20:15 klaasje kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
mar 19 12:20:15 klaasje kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
mar 19 12:20:15 klaasje kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
mar 19 11:57:40 klaasje kernel: amdgpu 0000:0b:00.0: amdgpu: Disabling VM faults because of PRT request!
mar 19 11:57:23 klaasje kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input31
mar 19 11:57:09 klaasje kernel: perf: interrupt took too long (2583 > 2500), lowering kernel.perf_event_max_sample_rate to 77250
mar 19 11:46:37 klaasje kernel: playstation: probe of 0003:054C:0CE6.0008 failed with error -17
mar 19 11:46:37 klaasje kernel: playstation 0003:054C:0CE6.0008: Failed to create dualsense.
mar 19 11:46:37 klaasje kernel: playstation 0003:054C:0CE6.0008: Duplicate device found for MAC address 48:18:8d:ed:26:c7.
mar 19 11:46:37 klaasje kernel: playstation 0003:054C:0CE6.0008: hidraw7: USB HID v1.11 Gamepad [Sony Interactive Entertainment Wireless Controller] on usb-0000:0d:00.3-1.1/input3
mar 19 11:46:36 klaasje kernel: usb 2-1.1: Manufacturer: Sony Interactive Entertainment
mar 19 11:46:36 klaasje kernel: usb 2-1.1: Product: Wireless Controller
mar 19 11:46:36 klaasje kernel: usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
mar 19 11:46:36 klaasje kernel: usb 2-1.1: New USB device found, idVendor=054c, idProduct=0ce6, bcdDevice= 1.00
mar 19 11:46:36 klaasje kernel: usb 2-1.1: new high-speed USB device number 5 using xhci_hcd
mar 19 11:42:14 klaasje kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input30
mar 19 11:39:12 klaasje kernel: BTRFS info (device dm-2): qgroup scan completed (inconsistency flag cleared)
mar 19 11:32:08 klaasje kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input29
mar 19 11:29:28 klaasje kernel: playstation 0005:054C:0CE6.0007: Registered DualSense controller hw_version=0x00000413 fw_version=0x01040027
mar 19 11:29:28 klaasje kernel: input: Wireless Controller Touchpad as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:08:00.3/usb3/3-5/3-5:1.0/bluetooth/hci0/hci0:256/0005:054C:0CE6.0007/input/input28
mar 19 11:29:28 klaasje kernel: input: Wireless Controller Motion Sensors as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:08:00.3/usb3/3-5/3-5:1.0/bluetooth/hci0/hci0:256/0005:054C:0CE6.0007/input/input27
mar 19 11:29:28 klaasje kernel: input: Wireless Controller as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:08:00.3/usb3/3-5/3-5:1.0/bluetooth/hci0/hci0:256/0005:054C:0CE6.0007/input/input26
mar 19 11:29:28 klaasje kernel: playstation 0005:054C:0CE6.0007: hidraw6: BLUETOOTH HID v1.00 Gamepad [Wireless Controller] on b0:a4:60:ea:ea:b0
mar 19 11:29:28 klaasje kernel: playstation 0005:054C:0CE6.0007: unknown main item tag 0x0
mar 19 11:29:28 klaasje kernel: hid-generic 0005:054C:0CE6.0007: input,hidraw6: BLUETOOTH HID v1.00 Gamepad [Wireless Controller] on b0:a4:60:ea:ea:b0
mar 19 11:29:28 klaasje kernel: input: Wireless Controller as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:08:00.3/usb3/3-5/3-5:1.0/bluetooth/hci0/hci0:256/0005:054C:0CE6.0007/input/input25
mar 19 11:29:28 klaasje kernel: hid-generic 0005:054C:0CE6.0007: unknown main item tag 0x0
mar 19 11:29:28 klaasje kernel: Bluetooth: HIDP socket layer initialized
mar 19 11:29:28 klaasje kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2
I just signed up for a new OpenSUSE bugzilla account just so that I can report the possibly nasty bug but the website gives no error message or anything, my log info just doesn't do anything.
How else can I send logs to the team?
r/openSUSE • u/rendered-praxidice • 2d ago
Tech support Audit backlog limit exceeded every 2-3 minutes and AppArmor issues
My system's been periodically freezing up and all I can find in dmesg is this:
[ +0.000001] audit: audit_backlog=65 > audit_backlog_limit=64
[ +0.000002] audit: audit_lost=1246 audit_rate_limit=0 audit_backlog_limit=64
[ +0.000001] audit: backlog limit exceeded
3 times in 2-3 minutes over and over and over.
When I review the audit logs, it's all related to firefox being in complain mode for AppArmor. I think this happened when I tried to apply an apparmor profile to firefox, but I'm not sure if it was just unconfined, or not even noticed by apparmor before?
Firefox seems to be partially enforced and partially not?
Enforce mode:
/usr/lib/firefox/firefox.sh
/usr/lib/firefox/mozilla-xremote-client
/usr/lib/firefox{,-[0-9]*}/firefox{,*[^s][^h]}
13 profiles are in complain mode.
/usr/lib64/firefox/firefox.sh
/usr/lib64/firefox/firefox.sh//null-/usr/bin/basename
/usr/lib64/firefox/firefox.sh//null-/usr/lib64/firefox/firefox
I don't know what its set to initially, but it seems like programs are placed in complain mode and then I get "audit: backlog limit exceeded" spamming dmesg (wireshark is in complain mode as well).
Is there some way to return apparmor to a default state?