<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wayland on Linux Café</title>
    <link>https://mrtomlinux.org/tags/wayland/</link>
    <description>Recent content in Wayland on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 11 Sep 2026 10:21:07 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/wayland/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Quick Fix to Stop a Flatpak App From Updating on My Wayland Desktop</title>
      <link>https://mrtomlinux.org/post/2026-09-11-the-quick-fix-to-stop-a-flatpak-app-from-upda/</link>
      <pubDate>Fri, 11 Sep 2026 10:21:07 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-09-11-the-quick-fix-to-stop-a-flatpak-app-from-upda/</guid>
      <description>&lt;h2 id=&#34;pin-a-flatpak-app-to-a-fixed-version-on-wayland&#34;&gt;Pin a Flatpak App to a Fixed Version on Wayland&lt;/h2&gt;&#xA;&lt;p&gt;Flatpak apps are great for sandboxing, but the automatic update loop can be a nuisance when a new release breaks a workflow or introduces a regression. On a Wayland‑based desktop (GNOME, KDE, etc.) the update mechanism is the same as on X11, so the steps below work everywhere.&lt;/p&gt;&#xA;&lt;h3 id=&#34;1-inspect-the-current-version&#34;&gt;1. Inspect the current version&lt;/h3&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;flatpak info com.spotify.Client&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The output shows the installed commit hash and the remote’s latest commit. If you’re running a version that you want to keep, note the commit hash:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
