<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gnome on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/gnome/</link>
    <description>Recent content in Gnome on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 11:09:03 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/gnome/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fixing GNOME’s broken audio output after an ALSA upgrade</title>
      <link>https://linuxeries.org/post/2026-10-04-fixing-gnomes-broken-audio-output-after-an-al/</link>
      <pubDate>Sun, 04 Oct 2026 11:09:03 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-10-04-fixing-gnomes-broken-audio-output-after-an-al/</guid>
      <description>&lt;h2 id=&#34;gnome-audio-stops-after-an-alsa-upgrade--how-to-diagnose-and-fix&#34;&gt;GNOME audio stops after an ALSA upgrade – how to diagnose and fix&lt;/h2&gt;&#xA;&lt;p&gt;When a distro bumps the ALSA stack, the first thing that usually goes wrong is the desktop audio. In GNOME you’ll see “no audio” or a muted‑looking volume slider that actually reports a non‑zero level. The root cause is a mismatch between the kernel‑level ALSA driver and the user‑space libraries that PipeWire (the default audio server in GNOME 45+) talks to. Below is a practical, step‑by‑step walk‑through that covers the most common culprits, how to confirm them, and how to fix the issue without rolling back the whole upgrade.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
