# Paraview failing to start inside singularity container
**URL:** https://discourse.paraview.org/t/paraview-failing-to-start-inside-singularity-container/14891
**Category:** ParaView Support
**Created:** [June 19, 2024, 11:27pm UTC](https://discourse.paraview.org/t/paraview-failing-to-start-inside-singularity-container/14891 "2024-06-19T23:27:20Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Renato\_E\_Poli](https://discourse.paraview.org/u/Renato_E_Poli)
#### Post date: [June 19, 2024, 11:27pm UTC](https://discourse.paraview.org/t/paraview-failing-to-start-inside-singularity-container/14891/1 "2024-06-19T23:27:20Z")
I am using a full environment inside a singularity container. From the container bash, I call paraview and it crashes (output below). Paraview was installed through “apt install paraview” (Ubuntu 22).
Any clue of what might be wrong?
This is the output:
$ paraview
QStandardPaths: error creating runtime directory ‘/run/user/1000’ (No such file or directory)
QStandardPaths: error creating runtime directory ‘/run/user/1000’ (No such file or directory)
dbus[4830]: D-Bus library appears to be incorrectly set up: see the manual page for dbus-uuidgen to correct this issue. (Failed to open “/var/lib/dbus/machine-id”: No such file or directory; UUID file ‘/etc/machine-id’ should contain a hex string of length 32, not length 0, with no other text)
D-Bus not built with -rdynamic so unable to print a backtrace
Aborted (core dumped)
Thank you,
Renato
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [June 21, 2024, 11:08am UTC](https://discourse.paraview.org/t/paraview-failing-to-start-inside-singularity-container/14891/2 "2024-06-21T11:08:36Z")
It looks like Qt is expecting some desktop infrastructure to be present. Try this:
```commands
$ echo "create a new machine id"
$ uuidgen | tr -d '-' | sudo cat > /etc/machine-id
$ echo "run ParaView under a D-Bus session"
$ dbus-launch paraview
```
That `uuidgen` pipeline may need some editing…the redirect might not happen under `sudo` permissions.
---
### Author:  [@Renato\_E\_Poli](https://discourse.paraview.org/u/Renato_E_Poli)
#### Post date: [June 21, 2024, 1:41pm UTC](https://discourse.paraview.org/t/paraview-failing-to-start-inside-singularity-container/14891/3 "2024-06-21T13:41:25Z")
Thank you Ben. It worked better. But now the buttons are not displayed. (see fig below)
Do you know what might be the problem?
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [June 23, 2024, 4:09am UTC](https://discourse.paraview.org/t/paraview-failing-to-start-inside-singularity-container/14891/4 "2024-06-23T04:09:00Z")
Looks like an icon theme is missing? Or not being found?
---
### Author:  [@Renato\_E\_Poli](https://discourse.paraview.org/u/Renato_E_Poli)
#### Post date: [June 24, 2024, 1:38pm UTC](https://discourse.paraview.org/t/paraview-failing-to-start-inside-singularity-container/14891/5 "2024-06-24T13:38:34Z")
Yes… I installed with “apt install paraview”. Any dependence might be missing?
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [June 26, 2024, 10:45am UTC](https://discourse.paraview.org/t/paraview-failing-to-start-inside-singularity-container/14891/6 "2024-06-26T10:45:51Z")
Could be…if you try to install another Qt or GTK application, do any icon packages want to get installed as a dependency?
Oh, or the SVG support plugin for Qt could be missing; I think a number of these icons are SVGs now.