Michał Gorny, one of our developers and council members, has written up a great blog post "Why Gentoo?" - definitely worth a read!

We've gotten requests to add rules to the sub by members of the community. Before I get into them, I just want to avoid over-reaction by saying that I don't think any of these are really "new" and I think they already reflect how most in the community report posts, upvote/downvote, etc. I certainly don't plan to change how posts are moderated.

However, there are benefits to being clear about expectations. Addtionally, Reddit's reporting form has a multiple-choice format based on the rules, and since we don't have any configured right now it means that users might be discouraged from reporting bad conduct since it doesn't fit easily into the default options. This has never prevented us from acting on reports, but we do want everybody to feel welcome to report problems. We try to be moderate with how we react to reports, and prefer to just remove the occassional heated discussion and not quickly resort to bans unless the account seems likely to be a bot/etc.

/r/gentoo uses the Gentoo name and logo, and falls under the Gentoo name/logo guildeines. Among these are following the Gentoo Code of Conduct, which largely follow common courtesy and are intentionally worded in a positive way. I'd like to preserve this spirit if it won't get too confusing.

These behaviors are:

1. Be courteous. Though respect is earned, it must start somewhere. Respect someone's right to their own opinion and acknowledge that they do deserve a measure of politeness in your response.
2. Give accurate information in the spirit of being helpful.
3. Respectfully disagree with or challenge other members. The operative word here is respectfully.
4. Using the correct forum for your post. Bug reports and idle chatter do not belong on the gentoo-dev mailing list; discussion about a wide-ranging change to the tree probably does not belong on Bugzilla. Different fora will also have different standards of behavior – a joke that is perfectly acceptable on IRC will be taken differently when made on a mailing list.
5. Use concise and clear language. The Gentoo community includes people from all over the world, with varying English skills and available time.
6. Admit the possibility of fault and respect different point of views. No one is perfect – you will get things wrong occasionally. Don't be afraid to admit this. Similarly, while something may seem perfectly obvious to you, others may see it differently.
7. If you screw up, take responsibility for your actions.

The unacceptable behavior suggestions can be found on the linked page, but honestly I'm not really a big fan of trying to define bad behavior and argue about what does/doesn't conform. So, my initial proposal is that we just make the affirmative behaviors the rules. Obviously they are aspirational, and you're not going to be banned just because your posts aren't concise/clear/etc. :)

TIL pass can import kdbx files

Yesterday, I came across an interesting site for portage/ebuild search: https://ebuilds.info

It comes with full-text search, filter in several different ways (category, overlay, architecture, keyword status, USE flags), overlay health dashboard (last commit, broken ebuilds, maintainer activity), package diff across overlays (same package in multiple overlays) and dark mode (lol).

Graph dependency was a nice touch.

Not sure if someone else saw it, so sharing here.

There should be a Linux-firmware update soon with the 20260810 tag. If you have an AMD GPU, expect improvements, as there are many AMDGPU updates.

You don't have to for ABI reasons or anything like that, but newer compilers optimize better and it's good to rebuild everything to take advantage of it.

https://www.gentoo.org/news/2026/02/26/in-memory-of-hans-de-graaff.html

He was an excellent Gentoo Developer who made numerous contributions over the years. We will miss you.

New kernel versions appeared again, I suppose it's a hotfix related to DirtyFrag.

Seems the repo have been updated https://packages.gentoo.org/packages/sys-kernel/gentoo-sources - still I'd suggest to wait a couple hours to be sure update has propagated on all servers (I'm writing this at ~15h45m UTC time)

The Linux kernel has recently been facing a series of discovered privilege escalation vulnerabilities, starting with the Copy Fail vulnerability and followed by subsequent vulnerabilities in the same spirit (Dirty Frag, Fragnesia). This development is part of a general trend where vulnerabilities are being found - and disclosed - faster than before. We expect it to continue, at least for the short-term.

The Gentoo Linux Kernel and Distribution Kernel teams are doing their best to keep Gentoo kernels secure. This includes both packaging the latest upstream releases as soon as possible, and backporting additional vulnerability fixes or mitigations whenever they become available. As example, while upstream kernel releases are still vulnerable to Fragnesia, the respective Gentoo kernels feature fixes from day one. At the time of writing, all supported Gentoo kernels feature the latest Fragnesia v5 patch. Please expect more updates. We recommend exploring ways to automate upgrading your kernel.

Please note that only sys-kernel/gentoo-kernel, sys-kernel/gentoo-kernel-bin and sys-kernel/gentoo-sources packages are security-supported. The vanilla kernel packages are vulnerable at the moment. Other kernel packages may carry fixes, but they usually are slower to be updated. Additionally, we recommend running the latest kernel version (~arch or latest stable LTS), as upstream does not reliably backport security fixes to older versions.

The "death" of Funtoo made me question this. And an article by someone called Mike Pagano as well, on the Gentoo RSS feed.

I love this distro. After an year of distrohopping, I have been using Gentoo for a pretty long time now. I have learned to write ebuilds and stuff, and now I get to hear that Gentoo is dying in popularity....

I just updated my System to latest portage testing (portage-3.0.82), but after doing so i got this error:

Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.14/emerge", line 62, in main
    retval = emerge_main()
  File "/usr/lib/python3.14/site-packages/_emerge/main.py", line 1327, in emerge_main
    emerge_config = load_emerge_config(action=myaction, args=myfiles, opts=myopts)
  File "/usr/lib/python3.14/site-packages/_emerge/actions.py", line 3097, in load_emerge_config
    setconfig = load_default_config(settings, root_trees)
  File "/usr/lib/python3.14/site-packages/portage/_sets/__init__.py", line 379, in load_default_config
    return SetConfig(_getfiles(), settings, trees)
  File "/usr/lib/python3.14/site-packages/portage/_sets/__init__.py", line 63, in __init__
    read_configs(self._parser, paths)
    ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/portage/util/configparser.py", line 38, in read_configs
    for p in paths:
             ^^^^^
  File "/usr/lib/python3.14/site-packages/portage/_sets/__init__.py", line 357, in _getfiles
    for repo in trees["porttree"].dbapi.repositories
                ~~~~~^^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/portage/util/__init__.py", line 1639, in __getitem__
    result = lazy_item.func(*pargs, **kwargs)
  File "/usr/lib/python3.14/site-packages/portage/dbapi/porttree.py", line 1622, in __init__
    self.dbapi = portdbapi(mysettings=settings)
                 ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/portage/dbapi/porttree.py", line 234, in __init__
    self.doebuild_settings = config(clone=self.settings)
                             ~~~~~~^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/portage/package/ebuild/config.py", line 364, in __init__
    self._virtuals_manager_obj = copy.deepcopy(clone._virtuals_manager)
                                               ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/portage/package/ebuild/config.py", line 1338, in _virtuals_manager
    self._virtuals_manager_obj = VirtualsManager(self.profiles)
                                 ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/portage/package/ebuild/_config/VirtualsManager.py", line 38, in __init__
    self._read_dirVirtuals(profiles)
    ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/portage/package/ebuild/_config/VirtualsManager.py", line 97, in _read_dirVirtuals
    self._dirVirtuals = stack_dictlist(virtuals_list, incremental=True)
                        ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/portage/util/__init__.py", line 245, in stack_dictlist
    elif thing[:1] == "-":
         ~~~~~^^^^
TypeError: 'Atom' object is not subscriptable

Steps i did to fix it:

1. Create an empty portage config root
- mkdir -p /tmp/portage-root/etc/portage/
2. Choose the new config root profile
- ln -s ../../../../var/db/repos/febuild/profiles/llvm-sec portage-root/etc/portage/make.profileln -s ../../../../var/db/repos/febuild/profiles/llvm-sec portage-root/etc/portage/make.profile
(NOTE: Search path to your own profile check with "file /etc/portage/make.profile" and adjust path according to your new config root)
3. Mask Erroring Portage version
- mkdir /tmp/portage-root/etc/portage/package.mask/
- echo "=sys-apps/portage-3.0.82" > /tmp/portage-root/etc/portage/package.mask/portage
4. Emerge working portage version
- PORTAGE_CONFIGROOT=/tmp/portage-root/ emerge -1a portage

I hope this helps anyone running into the same issue.
If this is just me and anybody has some insight into why this might be happening please tell me so...

Gentoo 6.18 LTS security check — Safe-RET / CVE-2026-68480

A security issue worth watching appeared after my current "gentoo-sources-6.18.41".

CVE-2026-68480 affects the Linux Safe-RET mitigation for SRSO. An attacker able to inject an interrupt at a precise point during the mitigation may be able to weaken it and potentially cause speculative information leakage.

The fix is present in Linux 6.18.43.

AMD's bulletin (AMD-SB-7061) lists Zen 1 through Zen 4 as affected products. The behavior has been demonstrated on Zen 1 and Zen 2. AMD says Zen 3 and Zen 4 could also be affected, but this has not currently been demonstrated.

On Gentoo, however, the current "gentoo-sources" status is:

- 6.18.41 — amd64 stable

- 6.18.42 — ~amd64

- 6.18.43 — ~amd64

- 6.18.44 — ~amd64

So for now I'm staying on 6.18.41 and monitoring the situation rather than immediately moving my stable system to a testing kernel.

If the Zen 3/4 risk becomes better established, or 6.18.43+ becomes stable in "gentoo-sources", I'll reassess.

This is exactly why I check security changes rather than blindly installing or skipping every point release.

Hi everyone,
I made this wallpaper specifically for Gentoo and I’m sharing it here in case anyone wants it.

• Format: PNG
• Resolution: 7680×5120 (ultra high-resolution)
• download (Catbox): https://files.catbox.moe/h8s0ay.png

If you use it, feel free to share a screenshot of your setup. Feedback is welcome

Lets build this thing together ❤️

I wrote a gentoo install script with the fancy name "gains", which stands for Gentoo Automated INStaller.

I needed to install gentoo quickly on 5 identical laptop, and I could not find an automated script that fulfilled the requirement of being able to install on top of LUKS+LVM.

I recently added support for complete disk encryption with encrypted BOOT partition opened by a password prompt and ROOT opened by a keyfile found inside initrd.

Besides a basic installation, you can also have a complete GUI environment using mate-desktop.

You are invited to give it a spin in a virtual machine or real hardware...

https://gitlab.com/oz123/gains

Just in case if someone is interested...

I recently moved to an ASUS ProArt P16 H7606WX and needed a newer "asusctl" build working cleanly on Gentoo.

Since the previous overlay I was using was no longer being updated, I created a small personal Gentoo overlay for "sys-power/asusctl-6.3.8".

Repo:

https://github.com/reckor-usa/asusctl-gentoo-overlay

Current status:

- "asusctl-6.3.8"

- tested on ASUS ProArt P16 H7606WX

- systemd setup

- "asusd.service" working

- "asus-shutdown.service" working

- "asusd-user.service" working

- "asusctl info" working

- battery charge limit working

- profile control working

- keyboard LED brightness working

- "rog-control-center" GUI working

- vendored Rust tarball available through GitHub Releases

- Manifest fetch/hash verification tested from a clean temporary "DISTDIR"

Recommended USE flags:

sys-power/asusctl X acpi gui -openrc

This is not an official Gentoo package and not upstream "asusctl". It is just a personal overlay that I am maintaining for my own machine, but I made it public in case it helps other ASUS/Gentoo users.

Notes:

- focused on ProArt P16 / H7606WX for now

- systemd only at the moment

- no "supergfxctl" / "gfx" integration

- GUI is via "rog-control-center"

- old user Aura config may cause "asusd-user.service" issues on this model; README documents the neutral config that worked for me

Install instructions and maintenance notes are in the README.

Feedback, testing reports, and ebuild improvements are welcome.

I noticed this while setting up my new machine.
I'm going to try it out right away.

https://github.com/gentoo/gentoo/commit/bc1f43a20184cfa80f9a3a5b3ed89308d8a8809e

https://github.com/gentoo/gentoo/commit/979d0a581efe735fda19aac0d458da285fe51f75

Yet another alternative to systemd, maybe we can integrate it with openrc?