<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Desktop on Linux Café</title>
    <link>https://mrtomlinux.org/tags/desktop/</link>
    <description>Recent content in Desktop on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 15 Nov 2026 09:59:47 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/desktop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fixing GNOME Terminal Freezes on Wayland</title>
      <link>https://mrtomlinux.org/post/2026-11-15-how-to-stop-gnome-terminal-freezing-when-runn/</link>
      <pubDate>Sun, 15 Nov 2026 09:59:47 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-11-15-how-to-stop-gnome-terminal-freezing-when-runn/</guid>
      <description>&lt;h2 id=&#34;why-gnome-terminal-can-freeze-on-a-4k-wayland-display&#34;&gt;Why GNOME Terminal can freeze on a 4K Wayland display&lt;/h2&gt;&#xA;&lt;p&gt;When you fire up a heavy background job—think &lt;code&gt;dd&lt;/code&gt;, &lt;code&gt;fio&lt;/code&gt;, or a long‑running &lt;code&gt;rsync&lt;/code&gt;—the terminal can suddenly stop answering. On a 4K laptop running Wayland the culprit is usually the compositor trying to keep the terminal’s output fresh while the CPU is busy elsewhere. The rendering loop stalls, and the window looks frozen even though the shell is still alive. The cure is to separate the terminal’s repainting from the job’s I/O, or to give the compositor a lighter load.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
