visit icon indicating copy to clipboard operation
visit copied to clipboard

QT plugins directories not copied to VisIt install plugins directory

Open griffin28 opened this issue 2 years ago • 5 comments

Describe the bug

I did a make install -j 2 after building VisIt and when I tried to run VisIt, I received an error Qt: Warning: Could not find the Qt platform plugin "xcb" in "" . I did an export QT_DEBUG_PLUGINS=1 to get more information and discovered the QFactoryLoader was looking specifically in the VisIt install plugins directory (and I believe 1 or 2 others) for the xcb stuff. Once I copied the directories in the QT plugins directory to the VisIt plugins directory that was created after doing the make install everything worked.

I don't remember this being an issue with earlier VisIt releases. I checked an old VisIt install and don't see anything QT related in the plugins directory.

TP library build command:

build_visit --build-mode Debug --makeflags -j16 --no-thirdparty --no-visit --cmake --python --vtk --qt --qwt --boost --mpich --adios --adios2 --advio --boxlib --cfitsio --conduit --gdal --h5part --hdf5 --cgns --netcdf --mfem --silo --szip --icet --zlib --xdmf --tbb --thirdparty-path /home/kgriffin/VisIt/third_party/3.3.0

VisIt build command:

cmake -DCMAKE_BUILD_TYPE=Debug -DVISIT_INSTALL_THIRD_PARTY=ON -DVISIT_BUILD_ALL_PLUGINS=ON -DCMAKE_INSTALL_PREFIX=/usr/local/visit ../src

Desktop

  • OS and version: Ubuntu 20.04.5
  • VisIt Version: 3.3.0 and 3.3.1

griffin28 avatar Sep 29 '22 18:09 griffin28

Additional Info: The QT plugins directories (platforms and xcbglintegrations) get copied to linux-x86_64/lib/qtplugins during make install. The QFactoryLoader is expecting them in linux-x86_64/plugins.

griffin28 avatar Oct 11 '22 17:10 griffin28

@griffin28 what it the contents of qt.conf in linux-x86_64/bin?

biagas avatar Oct 11 '22 22:10 biagas

Here's what's in the qt.conf file:

[Paths]
Plugins=../lib/qtplugins

griffin28 avatar Oct 12 '22 00:10 griffin28

I think the issue is on my end. This was working correctly in 3.1.4 the same setup for QT. Not sure what got messed up.

griffin28 avatar Oct 12 '22 00:10 griffin28

Another thing to check would be any environment variables related to QT.

biagas avatar Oct 12 '22 14:10 biagas