<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>compiz &amp;mdash; alan</title>
    <link>https://www.franzoni.eu/alan/tag:compiz</link>
    <description>Alan&#39;s musings</description>
    <language>en</language>
    <pubDate>Tue, 17 Nov 2026 00:49:46 +0000</pubDate>
    <item>
      <title>Unfreezing your desktop: when Compiz goes wrong</title>
      <link>https://www.franzoni.eu/alan/unfreezing-your-desktop-when-compiz-goes-wrong</link>
      <description>&lt;![CDATA[A desktop freeze is something that&#39;s not so rare nowadays - that&#39;s not good, but we shouldn&#39;t get desperate about that.&#xA;&#xA;I like Compiz with Unity Desktop on my Ubuntu Trusty very much; I feel it&#39;s a step forward compared to traditional desktops. The only major nuisance I had on the previous versions was the inability to disable the global menu (which I like by itself, but I don&#39;t like the global menu disappearing when the mouse is not over it), but you can now disable it and have the menu on the window - even though you can&#39;t still enable an always-visible behaviour.&#xA;&#xA;The problem is: compiz sometimes gets buggy. Running a different window manager, like metacity and/or xcompmgr just doesn&#39;t seem good, you can experience other issues and you&#39;re using the stack in a way it wasn&#39;t designed for. I don&#39;t like that approach.&#xA;&#xA;So, what can you do when your desktop freezes? The symptoms are usually very clear: you can move your mouse, but you can&#39;t click nor type anything.&#xA;&#xA;You don&#39;t need to reboot nor to restart X. You can fix this without losing your work.&#xA;&#xA;Get a raw tty&#xA;&#xA;Press Ctrl+Alt+F1 and get to a raw linux console, and login with your credentials. Make sure you use the same user you&#39;re logged into X with.&#xA;&#xA;Find and kill your stuck process&#xA;&#xA;pgrep compiz&#xA;&#xA;This will print the PID of our stuck window manager.&#xA;&#xA;Let&#39;s kill it&#xA;&#xA;pkill compiz&#xA;&#xA;This won&#39;t usually be enough because the process is really stuck: if you repeat the pgrep command above, you&#39;ll find it still running - i.e. pgrep will return the very same PID as above.&#xA;&#xA;So let&#39;s kill it, really this time!&#xA;&#xA;pkill -9 compiz&#xA;&#xA;Then wait some 15-20 seconds.&#xA;&#xA;Now, if you repeat the pgrep , you&#39;ll either see a) no result or b) a different PID.&#xA;&#xA;If you see a different PID, it&#39;s Ubuntu that noticed the crashed process and relaunched it; press Ctrl+Alt+F7, and you should just get back a working desktop!&#xA;&#xA;Relaunching&#xA;&#xA;If you see nothing with pgrep, you&#39;ll need to relaunch Compiz manually.&#xA;&#xA;You cannot simply relaunch compiz on the console, because it must connect to X: the proper way to do it is:&#xA;&#xA;DISPLAY=:0 compiz&#xA;&#xA;Now switch back to your X instance with Ctrl+Alt+F7 and enjoy!&#xA;&#xA;#MostlyUnixish #linux #ancientwisdom #community #ubuntu #compiz&#xA;]]&gt;</description>
      <content:encoded><![CDATA[<p>A desktop freeze is something that&#39;s not so rare nowadays – that&#39;s not good, but we shouldn&#39;t get desperate about that.</p>

<p>I like <a href="http://www.compiz.org" rel="nofollow">Compiz</a> with <a href="https://unity.ubuntu.com/" rel="nofollow">Unity Desktop</a> on my <a href="https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes" rel="nofollow">Ubuntu Trusty</a> very much; <strong>I feel it&#39;s a step forward compared to traditional desktops</strong>. The only major nuisance I had on the previous versions was the inability to disable the global menu (which I like by itself, but I don&#39;t like the global menu disappearing when the mouse is not over it), but you can now disable it and have the menu on the window – even though you can&#39;t still enable an always-visible behaviour.</p>

<p>The problem is: compiz sometimes gets buggy. Running a different window manager, like <a href="https://help.ubuntu.com/community/Metacity" rel="nofollow">metacity</a> and/or <a href="http://cgit.freedesktop.org/xorg/app/xcompmgr/" rel="nofollow">xcompmgr</a> just doesn&#39;t seem good, you can experience other issues and you&#39;re using the stack in a way it wasn&#39;t designed for. I don&#39;t like that approach.</p>

<p>So, what can you do when your desktop freezes? The symptoms are usually very clear: you can move your mouse, but you can&#39;t click nor type anything.</p>

<p><strong>You don&#39;t need to reboot nor to restart X.</strong> You can fix this without losing your work.</p>

<h2 id="get-a-raw-tty">Get a raw tty</h2>

<p>Press <em>Ctrl+Alt+F1</em> and get to a raw linux console, and login with your credentials. Make sure you use the same user you&#39;re logged into X with.</p>

<h2 id="find-and-kill-your-stuck-process">Find and kill your stuck process</h2>

<pre><code>pgrep compiz
</code></pre>

<p>This will print the PID of our stuck window manager.</p>

<p>Let&#39;s kill it</p>

<pre><code>pkill compiz
</code></pre>

<p>This <strong>won&#39;t usually be enough</strong> because the process is really stuck: if you repeat the <em>pgrep</em> command above, you&#39;ll find it still running – i.e. pgrep will return the very same PID as above.</p>

<p>So let&#39;s kill it, really this time!</p>

<pre><code>pkill -9 compiz
</code></pre>

<p>Then wait some 15-20 seconds.</p>

<p>Now, if you repeat the <em>pgrep</em> , you&#39;ll either see a) no result or b) a different PID.</p>

<p>If you see a different PID, it&#39;s Ubuntu that noticed the crashed process and relaunched it; press <em>Ctrl+Alt+F7</em>, and you should just get back a working desktop!</p>

<h2 id="relaunching">Relaunching</h2>

<p>If you see nothing with pgrep, you&#39;ll need to relaunch Compiz manually.</p>

<p>You cannot simply relaunch compiz on the console, because it must connect to X: the proper way to do it is:</p>

<pre><code>DISPLAY=:0 compiz
</code></pre>

<p>Now switch back to your X instance with <em>Ctrl+Alt+F7</em> and enjoy!</p>

<p><a href="/alan/tag:MostlyUnixish" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">MostlyUnixish</span></a> <a href="/alan/tag:linux" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">linux</span></a> <a href="/alan/tag:ancientwisdom" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">ancientwisdom</span></a> <a href="/alan/tag:community" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">community</span></a> <a href="/alan/tag:ubuntu" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">ubuntu</span></a> <a href="/alan/tag:compiz" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">compiz</span></a></p>
]]></content:encoded>
      <guid>https://www.franzoni.eu/alan/unfreezing-your-desktop-when-compiz-goes-wrong</guid>
      <pubDate>Fri, 12 Dec 2014 22:28:00 +0000</pubDate>
    </item>
  </channel>
</rss>