Paraview failing to start inside singularity container

ParaView Support
1

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

2

It looks like Qt is expecting some desktop infrastructure to be present. Try this:

$ 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.

3

Thank you Ben. It worked better. But now the buttons are not displayed. (see fig below)
Do you know what might be the problem?

image.png
image.png1056×381 18.9 KB

4

Looks like an icon theme is missing? Or not being found?

5

Yes… I installed with “apt install paraview”. Any dependence might be missing?

6

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.