# Slicer not starting on Linux (Qt plugin issue)

**URL:** https://discourse.slicer.org/t/slicer-not-starting-on-linux-qt-plugin-issue/18856
**Category:** Support
**Created:** [July 21, 2021, 12:44pm UTC](https://discourse.slicer.org/t/slicer-not-starting-on-linux-qt-plugin-issue/18856 "2021-07-21T12:44:40Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![perecanals](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/perecanals/32/9006_2.png) [@perecanals](https://discourse.slicer.org/u/perecanals)
#### Post date: [July 21, 2021, 12:44pm UTC](https://discourse.slicer.org/t/slicer-not-starting-on-linux-qt-plugin-issue/18856/1 "2021-07-21T12:44:41Z")

</div>

Hi,

OS: Linux (Ubuntu 20.04)  
Slicer version (current stable release): Slicer-4.11.20210226-linux-amd64

I am trying to start Slicer after the usual download and extraction process and this error appears:

```auto
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.

```

I found this topic [https://discourse.slicer.org/t/error-executing-version-slicer-4-11-0-2020-06-01-linux-amd64-tar-gz-on-ubuntu-16-04/11834](https://discourse.slicer.org/t/error-executing-version-slicer-4-11-0-2020-06-01-linux-amd64-tar-gz-on-ubuntu-16-04/11834) in the forums, and installing that version works well, but I am using a more recent version of the VMTK module that is not compatible tith that version of Slicer and my Python scripts do not work. I tried installing the Nightly build (Slicer-4.13.0-2021-07-17-linux-amd64) and I run into the same error as the current stable version. Any help?

---

<div class="post-metadata">

### Author: ![perecanals](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/perecanals/32/9006_2.png) [@perecanals](https://discourse.slicer.org/u/perecanals)
#### Post date: [July 21, 2021, 12:56pm UTC](https://discourse.slicer.org/t/slicer-not-starting-on-linux-qt-plugin-issue/18856/2 "2021-07-21T12:56:03Z")

</div>

To add more info, I tried running the `./Slicer` command (stable release) with `export QT_DEBUG_PLUGINS=1`, and this was output:

```auto
QFactoryLoader::QFactoryLoader() ignoring "com.nokia.qt.QGuiPlatformPluginInterface" since plugins are disabled in static builds 
QFactoryLoader::QFactoryLoader() ignoring "com.trolltech.Qt.QStyleFactoryInterface" since plugins are disabled in static builds 
QFactoryLoader::QFactoryLoader() ignoring "com.trolltech.Qt.QInputContextFactoryInterface" since plugins are disabled in static builds 
QFactoryLoader::QFactoryLoader() ignoring "com.trolltech.Qt.QImageIOHandlerFactoryInterface" since plugins are disabled in static builds 
QFactoryLoader::QFactoryLoader() checking directory path "/home/perecanals/Applications/Slicer-4.11.20210226-linux-amd64/lib/QtPlugins/platforms" ...
QFactoryLoader::QFactoryLoader() looking at "/home/perecanals/Applications/Slicer-4.11.20210226-linux-amd64/lib/QtPlugins/platforms/libqxcb.so"
Found metadata in lib /home/perecanals/Applications/Slicer-4.11.20210226-linux-amd64/lib/QtPlugins/platforms/libqxcb.so, metadata=
{
    "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
    "MetaData": {
        "Keys": [
            "xcb"
        ]
    },
    "archreq": 0,
    "className": "QXcbIntegrationPlugin",
    "debug": false,
    "version": 331520
}

Got keys from plugin meta data ("xcb")
QFactoryLoader::QFactoryLoader() checking directory path "/home/perecanals/Applications/Slicer-4.11.20210226-linux-amd64/bin/platforms" ...
Cannot load library /home/perecanals/Applications/Slicer-4.11.20210226-linux-amd64/lib/QtPlugins/platforms/libqxcb.so: (libxcb-xinerama.so.0: cannot open shared object file: No such file or directory)
QLibraryPrivate::loadPlugin failed on "/home/perecanals/Applications/Slicer-4.11.20210226-linux-amd64/lib/QtPlugins/platforms/libqxcb.so" : "Cannot load library /home/perecanals/Applications/Slicer-4.11.20210226-linux-amd64/lib/QtPlugins/platforms/libqxcb.so: (libxcb-xinerama.so.0: cannot open shared object file: No such file or directory)"
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.

```

From this, together with what I gathered online, it seems that the problem has to do with that `libxcb-xinerama.so.0` file, but I don’t know how to fix it.

---

<div class="post-metadata">

### Author: ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)
#### Post date: [July 21, 2021, 1:20pm UTC](https://discourse.slicer.org/t/slicer-not-starting-on-linux-qt-plugin-issue/18856/3 "2021-07-21T13:20:30Z")

</div>

Did you find this thread? That solution should work.

> [@Can't start latest stable on ubuntu 20.04](https://discourse.slicer.org/t/cant-start-latest-stable-on-ubuntu-20-04/14029):
>
> Due to the issues we had with Centos 7 and latest stable, I just recently installed Ubuntu 20.04 on a spare machine. This is just a default install, and nothing more (or less). Latest stable doesn’t start with this error: \> maga@magalab-ubuntu:~/Downloads/Slicer-4.11.20200930-linux-amd64$ ./Slicer \> qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. \> This application failed to start because no Qt platform plugin could be initialized. Reinstalling the a…

---

<div class="post-metadata">

### Author: ![perecanals](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/perecanals/32/9006_2.png) [@perecanals](https://discourse.slicer.org/u/perecanals)
#### Post date: [July 21, 2021, 1:31pm UTC](https://discourse.slicer.org/t/slicer-not-starting-on-linux-qt-plugin-issue/18856/4 "2021-07-21T13:31:00Z")

</div>

Just found it a minute before you posted the response! Gonna try to follow it, thanks and sorry! Maybe I wasn’t specific enough but I could not find it before posting the issue. Thank you!
