Monthly Archives: October 2013

Setting up schroot for Python multiprocessing

When using Arch Linux, its sometimes required to run something in a older/stable releaes of a Linux distribution. For this purpose I have a Ubuntu 12.04 LTS installation in a schroot environment. However, using Bitbake (a heavily multithreded and Python based build utility) The build aborted with the error:

  File "/usr/lib/python2.7/multiprocessing/", line 63, in __init__
    self._rlock = Lock()
  File "/usr/lib/python2.7/multiprocessing/", line 147, in __init__
    SemLock.__init__(self, SEMAPHORE, 1, 1)
OSError: [Errno 13] Permission denied

Read more »

Graphical boot splash screen with Nvidia binary drivers

Recently I had a hard time to bring graphical boot splash screen (Plymouth) to work on a Ubuntu 13.10 Saucy Salamander installation. I use the Nvidia binary¬†driver and activated uvesafb therefor (see this blog post how to do this). However, it didn’t work. In the end two pieces were missing: Read more »

Arch Linux: Gnome 3.10 on Wayland

Gnome 3.10 on Wayland

Gnome 3.10 on Wayland

Gnome 3.10 has initial Wayland support and hit the Arch Linux repositories lately, time to give it a try! The gnome packages are available with Wayland support, namely gnome-shell (which includes the gnome-shell-wayland binary) and mutter-wayland.

But I soon realized, that running Gnome on Wayland using Arch is not possible without some work: Firing up mutter-launch with the gnome-shell-wayland, lead to this error:

$ CLUTTER_BACKEND=wayland mutter-launch --verbose -- gnome-shell-wayland --wayland
(gnome-shell-wayland:18781): mutter-ERROR **: Spurious exit of X Wayland server

Gnome (or more specific, mutter, the Gnome window manager/compositor) needs a working XWayland version. XWayland is a X-Server running as a Wayland client. Its only used for non Wayland compatible clients, but is a mandatory requirement for mutter right now. The X-Server in the Arch repositories does not support this mode, hence another package is necessary. Read more »