error while loading shared libraries: libGLX.so.0

[Benjin454]

Hello,
Iv tried this container on both windows and osx. Getting this

/Slic3r/slic3r-dist/bin/prusa-slicer: error while loading shared libraries: libGLX.so.0: cannot open shared object file: No such file or directory

Any suggestions?

[Benjin454]

Iv tried adding package xserver-xorg-core to the docker file with no success. Also tried libglx-dev, libglx0 which it could not locate those packages.

[davidk]

Hello,

Thank you for the report. It looks like the container is failing similarly under Debian/Ubuntu as well. I've added some changes under the i8 branch.

The latest github actions run has pushed up a new image with these changes; please test with the following and let me know if it helps (--net=host seems to be necessary, otherwise PrusaSlicer exits silently during startup):

docker run --net=host \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-v "$PWD":/Slic3r/3d \
-v slic3rSettings:/home/slic3r \
-e DISPLAY="$DISPLAY" \
--rm keyglitch/docker-slic3r-prusa3d

[Benjin454]

Hi,

Thank you for the reply. Started fresh and pulled the container on Catalina macOS. The first attempt it opens a small blank window(picture below). Closed the window then. Executing the Docker run command Anytime after, the blank window does not show unless docker engine is restarted. It will show the CLI options then quit immediately. Its says the display is not set.

`ben@Bens-MacBook-Pro ~ % docker run --net=host
-v /tmp/.X11-unix:/tmp/.X11-unix
-v "$PWD":/Slic3r/3d
-v slic3rSettings:/home/slic3r
-e DISPLAY="$DISPLAY"
--rm keyglitch/docker-slic3r-prusa3d
[2022-01-05 18:20:29.031637] [0x00007f4d5d29d8c0] [trace] Initializing StaticPrintConfigs
PrusaSlicer-2.4.0+linux-x64-202112211614 based on Slic3r (with GUI support)
https://github.com/prusa3d/PrusaSlicer

Usage: prusa-slicer [ ACTIONS ] [ TRANSFORM ] [ OPTIONS ] [ file.stl ... ]

Actions:
--export-3mf Export the model(s) as 3MF.
--export-amf Export the model(s) as AMF.
--export-gcode, --gcode, -g
Slice the model and export toolpaths as G-code.
DISPLAY not set, GUI mode not available.

--export-obj Export the model(s) as OBJ.
--export-sla, --sla Slice the model and export SLA printing layers as PNG.
--export-stl Export the model(s) as STL.
--gcodeviewer Visualize an already sliced and saved G-code
--help, -h Show this help.
--help-fff Show the full list of print/G-code configuration options.
--help-sla Show the full list of SLA print configuration options.
--info Write information about the model to the console.
--save ABCD Save configuration to the specified file.
--slice, -s Slice the model as FFF or SLA based on the printer_technology configuration
value.

Transform options:
--align-xy X,Y Align the model to the given point.
--center X,Y Center the print around the given center.
--cut N Cut model at the given Z.
--dont-arrange Do not rearrange the given models before merging and keep their original XY
coordinates.
--duplicate N Multiply copies by this factor.
--duplicate-grid X,Y
Multiply copies by creating a grid.
--ensure-on-bed Lift the object above the bed when it is partially below. Enabled by default,
use --no-ensure-on-bed to disable.
--merge, -m Arrange the supplied models in a plate and merge them in a single model in order
to perform actions once.
--repair Try to repair any non-manifold meshes (this option is implicitly added whenever
we need to slice the model to perform the requested action).
--rotate N Rotation angle around the Z axis in degrees.
--rotate-x N Rotation angle around the X axis in degrees.
--rotate-y N Rotation angle around the Y axis in degrees.
--scale N Scaling factor or percentage.
--scale-to-fit X,Y,Z
Scale to fit the given volume.
--split Detect unconnected parts in the given model(s) and split them into separate
objects.

Other options:
--config-compatibility
This version of PrusaSlicer may not understand configurations produced by the
newest PrusaSlicer versions. For example, newer PrusaSlicer may extend the list
of supported firmware flavors. One may decide to bail out or to substitute an
unknown value with a default silently or verbosely. (disable, enable,
enable_silent; default: enable)
--datadir ABCD Load and store settings at the given directory. This is useful for maintaining
different profiles or including configurations from a network storage.
--ignore-nonexistent-config
Do not fail if a file supplied to --load does not exist.
--load ABCD Load configuration from the specified file. It can be used more than once to
load options from multiple files.
--loglevel N Sets logging sensitivity. 0:fatal, 1:error, 2:warning, 3:info, 4:debug, 5:trace
For example. loglevel=2 logs fatal, error and warning level messages.
--output ABCD, -o ABCD
The file where the output will be written (if not specified, it will be based on
the input file).
--single-instance If enabled, the command line arguments are sent to an existing instance of GUI
PrusaSlicer, or an existing PrusaSlicer window is activated. Overrides the
"single_instance" configuration value from application preferences.

Print options are processed in the following order:
1) Config keys from the command line, for example --fill-pattern=stars
(highest priority, overwrites everything below)
2) Config files loaded with --load
3) Config values loaded from amf or 3mf files

Run --help-fff / --help-sla to see the full listing of print options.
ben@Bens-MacBook-Pro ~ %
`

I also installed ubuntu on my intel based MacBook. Tried the docker container on ubuntu. Other than some complaints about some drivers not loading, it seems to work correctly. So that may rule out a hardware incompatibility.

[davidk]

If the CLI options show without any arguments passed, it usually indicates that PrusaSlicer did not find a compatible X server. I am not sure how Dockerized X11 apps are run on macOS these days (so I am unable to debug and test myself). Is something like XQuartz still required?