Skip to content

Latest commit

 

History

History
122 lines (74 loc) · 4.39 KB

install-non-debian.md

File metadata and controls

122 lines (74 loc) · 4.39 KB

Install StudioDisplay on non-Debian-based Linuxes (Manjaro, Arch, …)

Table of Contents

Will it work?

The good news: It will work. But you’re a little on your own. Read on.

What will not work (except on a Raspberry Pi)

  • SignalPi (mqtt-signalpi.py) — Requires a Raspberry Pi with Raspbian or Raspbian Lite.
  • UnicornLight (mqtt-unicornlight.py) — Requires a Raspberry Pi with Raspbian or Raspbian Lite.

What might need a little extra work

  • SignalBox (mqtt-signalbox.py) — Requires a driver for the SignalBox hardware. This might have to be manually compiled for your system.
  • Stream silence detection — Requires silentJACK, which might have to be manually compiled for your system.

What will work

Everything else should (almost) work right out-of-the-box. Read on.

Different package managers (i.e., pacman instead of apt)

Quite easy. Take Manjaro or Arch as example: These use pacman instead of apt for package management.

So whenever I talk about something like

sudo apt-get install python3 python-pip python3-pip

you simply substitute something like:

sudo pacman -S python3 python-pip python3-pip

My system has Python 3.x as default, not Python 2.x

Also quite easy. Just remember whenever we talk about python3-something, you’ll probably have that under the name python-something. And whenever we use python-something in the docs, you’ll probably need python2-something instead.

Let’s assume you run on Manjaro 17.1.10, which uses pacman instead of apt for package management and also has Python3 as default.

For the example

sudo apt-get install python3 python-pip python3-pip

we would now simply use

sudo pacman -S python2 python2-pip python-pip

and thus install Python2 instead of Python3 (which we already have), and install Python’s pip for Python2 under the name pip2 and for Python3 under the name pip. (For systems with Python2 as default, these would be pip for Python2 pip and pip3 for Python3 pip.)

From now on, when the docs say you should use pip, use pip2 instead; for pip3, substitute pip.

Thus, installing the Python MQTT client software in the docs says:

sudo pip install paho-mqtt
sudo pip3 install paho-mqtt

But we just do it »the other way round«:

sudo pip2 install paho-mqtt
sudo pip install paho-mqtt

Not so hard, ain’t it? :-)

On my testing machine, startall.sh doesn’t work correctly

Possible reasons are …

Missing software

  • You might not have both Python2 and Python3 installed. Both are required for full functionality.

  • Maybe you haven’t installed paho-mqtt system-wide. It must be available to all users and thus be installed as superuser (or with sudo).

  • Have you installed paho-mqtt for both Python2 and Python3? This is neccessary so all modules can function correctly.

Different X terminal emulator

  • Your system might not have the x-terminal-emulator. Use nano to edit startall.sh and simply substitute your system’s X terminal emulator for all occurrences of x-terminal-emulator.

    Hint: On Arch-based systems like Manjaro, this is typically xfce4-terminal.

You started it from a desktop file manager

In general, one shouldn’t start shell scripts from a desktop file manager (like Nemo, Thunar, …). This can lead to lots of unwanted side effects.

  • Always open a terminal and start startall.sh or stopall.sh from there.