Skip to content
0
  • Recent
  • Tags
  • Popular
  • SAMSON Connect
  • Get SAMSON
  • Recent
  • Tags
  • Popular
  • SAMSON Connect
  • Get SAMSON
Collapse
SAMSON Forum
  1. Home
  2. SAMSON
  3. Getting started
  4. Problem of graphics card after SAMSON installation on Ubuntu 18.04 (Intel processors)

Problem of graphics card after SAMSON installation on Ubuntu 18.04 (Intel processors)

Scheduled Pinned Locked Moved Solved Getting started
43 Posts 2 Posters 62.5k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • DmitriyMarinD
    DmitriyMarinD
    DmitriyMarin
    wrote on last edited by DmitriyMarin
    #15

    Sorry, I should have added:

    cd ~/NANO-D/SAMSON/0.7.0/Binaries
    export LD_LIBRARY_PATH=.:./SAMSONQtLibs:$LD_LIBRARY_PATH
    

    So, all these "not found" you posted are ok, since these libraries are actually provided with SAMSON and are placed in the same folder.
    If you redo the ldd check it should not find any "not found" libraries.

    Or you can do this ldd check from the SAMSON-Core.sh launching script after exporting all the libraries (already done in the script) instead of launching ./SAMSON-Core

    We will see what might cause the issue, but might be it smth more general since you said the VMD does not work as well.

    Dmitriy,
    The SAMSON Team, https://s-c.io

    1 Reply Last reply
    0
    • R
      R
      Robert
      wrote on last edited by
      #16

      No problem. Indeed, I don't find any "not found" library anymore with the two ldd checks above :
      ldd ./SAMSON-Core | grep "not found" | grep -v "Qt5"
      ldd ./libSBGRender.so | grep "not found" | grep -v "Qt5"

      When I launch SAMSON (./SAMSON-Core.sh or ./SAMSON-Core), I get the following message in the terminal :

      "
      saving context
      launching SAMSON-Core
      Python found in the system:
      Python executable: /home/rbenda/anaconda3/bin/python3
      Python library has not been loaded: Cannot load library libpython3.6m: (libpython3.6m: cannot open shared object file: No such file or directory)
      "

      I don't know if the problem can be due to this Python library but I don't think so (there might be a problem for SAMSON Apps using Python but it is not yet my case ...).

      I have modified the SAMSON-Core.sh script with vi. I uncommented the two lines
      ldd SAMSON-Core
      echo $LD_LIBRARY_PATH

      and added

      ldd ./SAMSON-Core | grep "not found" | grep -v "Qt5"
      ldd ./libSBGRender.so | grep "not found" | grep -v "Qt5"

      just before the last line echo "restoring context".

      SAMSON windows opens (as usual, but with the usual problem of no molecule appearing when loading a molecule, or the window not following the 'mouse' movement as you could see in the first screen shot I posted). I obtain this message in the terminal :

      saving context
      launching SAMSON-Core
      Python found in the system:
      Python executable: /home/rbenda/anaconda3/bin/python3
      linux-vdso.so.1 (0x00007ffed5fd5000)
      libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fab6811d000)
      libOpenGL.so.0 => /usr/lib/x86_64-linux-gnu/libOpenGL.so.0 (0x00007fab67eef000)
      libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0 (0x00007fab67cbe000)
      libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1 (0x00007fab67a4f000)
      libSAMSON.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSAMSON.so (0x00007fab67647000)
      libSBGCommand.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGCommand.so (0x00007fab6732e000)
      libGUI.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libGUI.so (0x00007fab67000000)
      libSBGUser.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGUser.so (0x00007fab66de2000)
      libSBSNeighborSearch.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBSNeighborSearch.so (0x00007fab66bba000)
      libSBGMain.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGMain.so (0x00007fab66912000)
      libSBGProperty.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGProperty.so (0x00007fab666ff000)
      libSBGToolBar.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGToolBar.so (0x00007fab664e3000)
      libSBGElement.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGElement.so (0x00007fab662ce000)
      libSBGInspector.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGInspector.so (0x00007fab65cfb000)
      libSBIFile.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBIFile.so (0x00007fab65af0000)
      libSBGRender.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGRender.so (0x00007fab65830000)
      libSBGDocument.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGDocument.so (0x00007fab655ce000)
      libSBGUndo.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGUndo.so (0x00007fab653b9000)
      libSBGWidget.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGWidget.so (0x00007fab65162000)
      libSBIElement.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBIElement.so (0x00007fab64f13000)
      libSBGNotification.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGNotification.so (0x00007fab64d06000)
      libSBGLog.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGLog.so (0x00007fab64af4000)
      libIO.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libIO.so (0x00007fab648f1000)
      libSBIPackage.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBIPackage.so (0x00007fab646d1000)
      libSBIWebService.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBIWebService.so (0x00007fab644b3000)
      libSBGVisualModel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGVisualModel.so (0x00007fab642a3000)
      libSBGStructuralModel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGStructuralModel.so (0x00007fab64037000)
      libSBGPropertyModel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGPropertyModel.so (0x00007fab63e27000)
      libSBGInteractionModel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGInteractionModel.so (0x00007fab63c16000)
      libSBGDynamicalModel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGDynamicalModel.so (0x00007fab63a05000)
      libSBGSimulator.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGSimulator.so (0x00007fab637f5000)
      libSBGStateUpdater.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGStateUpdater.so (0x00007fab635e8000)
      libSBGDataGraph.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGDataGraph.so (0x00007fab6331c000)
      libSBGMenu.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGMenu.so (0x00007fab6310e000)
      libSBGAction.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGAction.so (0x00007fab62ee8000)
      libSBGApp.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGApp.so (0x00007fab62cdd000)
      libSBGEditor.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGEditor.so (0x00007fab62ac0000)
      libSBGWindow.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGWindow.so (0x00007fab6286b000)
      libSBGSettings.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGSettings.so (0x00007fab62652000)
      libData.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libData.so (0x00007fab61b9e000)
      libSBDColor.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBDColor.so (0x00007fab61854000)
      libSBDDocument.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBDDocument.so (0x00007fab6130b000)
      libSBMVisualModel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBMVisualModel.so (0x00007fab610fa000)
      libSBDController.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBDController.so (0x00007fab60d80000)
      libSBMPropertyModel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBMPropertyModel.so (0x00007fab60b6f000)
      libSBSSimulator.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBSSimulator.so (0x00007fab60957000)
      libSBDApp.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBDApp.so (0x00007fab60743000)
      libSBGPath.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBGPath.so (0x00007fab6052b000)
      libQt5MultimediaWidgets.so.5 => ./SAMSONQtLibs/libQt5MultimediaWidgets.so.5 (0x00007fab6030d000)
      libQt5Multimedia.so.5 => ./SAMSONQtLibs/libQt5Multimedia.so.5 (0x00007fab60002000)
      libQt5Network.so.5 => ./SAMSONQtLibs/libQt5Network.so.5 (0x00007fab5fc6e000)
      libQt5OpenGL.so.5 => ./SAMSONQtLibs/libQt5OpenGL.so.5 (0x00007fab5fa17000)
      libQt5PrintSupport.so.5 => ./SAMSONQtLibs/libQt5PrintSupport.so.5 (0x00007fab5f7a9000)
      libQt5Sql.so.5 => ./SAMSONQtLibs/libQt5Sql.so.5 (0x00007fab5f562000)
      libQt5Widgets.so.5 => ./SAMSONQtLibs/libQt5Widgets.so.5 (0x00007fab5ed2d000)
      libQt5Gui.so.5 => ./SAMSONQtLibs/libQt5Gui.so.5 (0x00007fab5e57d000)
      libQt5Xml.so.5 => ./SAMSONQtLibs/libQt5Xml.so.5 (0x00007fab5e342000)
      libQt5Core.so.5 => ./SAMSONQtLibs/libQt5Core.so.5 (0x00007fab5dc02000)
      libSBSStateUpdater.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBSStateUpdater.so (0x00007fab5d9ee000)
      libSBMInteractionModel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBMInteractionModel.so (0x00007fab5d7d6000)
      libSBMDynamicalModel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBMDynamicalModel.so (0x00007fab5d58e000)
      libSBMStructuralModel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBMStructuralModel.so (0x00007fab5cc31000)
      libSBDType.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBDType.so (0x00007fab5ca0f000)
      libSBMElement.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBMElement.so (0x00007fab5c7ed000)
      libSBDQuantity.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBDQuantity.so (0x00007fab5c5eb000)
      libSBMModel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBMModel.so (0x00007fab5c3dc000)
      libSBDDataGraph.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBDDataGraph.so (0x00007fab5c00b000)
      libSBCFunctor.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBCFunctor.so (0x00007fab5bdff000)
      libCore.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libCore.so (0x00007fab5bbfb000)
      libSBCKernel.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBCKernel.so (0x00007fab5b9da000)
      libSBCUndo.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBCUndo.so (0x00007fab5b7c6000)
      libSBCClass.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBCClass.so (0x00007fab5b5a2000)
      libSBCSignal.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBCSignal.so (0x00007fab5b396000)
      libSBCReference.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBCReference.so (0x00007fab5b169000)
      libSBCLog.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBCLog.so (0x00007fab5af5b000)
      libSBCMeta.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBCMeta.so (0x00007fab5ad4a000)
      libSBCContainer.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBCContainer.so (0x00007fab5ab28000)
      libSBCHeap.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBCHeap.so (0x00007fab5a7e1000)
      libSBCSerializer.so => /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries/libSBCSerializer.so (0x00007fab5a477000)
      libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fab5a0d9000)
      libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fab59ce8000)
      /lib64/ld-linux-x86-64.so.2 (0x00007fab68321000)
      libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x00007fab59a32000)
      libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007fab596fa000)
      libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fab594db000)
      libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x00007fab5924f000)
      libstdc++.so.6 => /home/rbenda/anaconda3/lib/libstdc++.so.6 (0x00007fab683ce000)
      libgcc_s.so.1 => /home/rbenda/anaconda3/lib/libgcc_s.so.1 (0x00007fab683b9000)
      libpulse-mainloop-glib.so.0 => /usr/lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0 (0x00007fab5904a000)
      libpulse.so.0 => /usr/lib/x86_64-linux-gnu/libpulse.so.0 (0x00007fab58dfa000)
      libglib-2.0.so.0 => /home/rbenda/anaconda3/lib/libglib-2.0.so.0 (0x00007fab58cdd000)
      libz.so.1 => /home/rbenda/anaconda3/lib/libz.so.1 (0x00007fab6838f000)
      libicui18n.so.56 => ./SAMSONQtLibs/libicui18n.so.56 (0x00007fab58844000)
      libicuuc.so.56 => ./SAMSONQtLibs/libicuuc.so.56 (0x00007fab5848c000)
      libicudata.so.56 => ./SAMSONQtLibs/libicudata.so.56 (0x00007fab56aa9000)
      libgthread-2.0.so.0 => /home/rbenda/anaconda3/lib/libgthread-2.0.so.0 (0x00007fab6838a000)
      libxcb.so.1 => /home/rbenda/anaconda3/lib/libxcb.so.1 (0x00007fab56880000)
      libpulsecommon-11.1.so => /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so (0x00007fab56602000)
      libdbus-1.so.3 => /home/rbenda/anaconda3/lib/libdbus-1.so.3 (0x00007fab565ae000)
      libpcre.so.1 => /home/rbenda/anaconda3/lib/./libpcre.so.1 (0x00007fab56566000)
      librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fab5635e000)
      libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007fab5615a000)
      libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007fab55ed6000)
      libwrap.so.0 => /lib/x86_64-linux-gnu/libwrap.so.0 (0x00007fab55ccc000)
      libsndfile.so.1 => /usr/lib/x86_64-linux-gnu/libsndfile.so.1 (0x00007fab55a53000)
      libasyncns.so.0 => /usr/lib/x86_64-linux-gnu/libasyncns.so.0 (0x00007fab5584d000)
      liblzma.so.5 => /home/rbenda/anaconda3/lib/liblzma.so.5 (0x00007fab55627000)
      liblz4.so.1 => /home/rbenda/anaconda3/lib/liblz4.so.1 (0x00007fab55403000)
      libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007fab550e8000)
      libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x00007fab54ece000)
      libFLAC.so.8 => /usr/lib/x86_64-linux-gnu/libFLAC.so.8 (0x00007fab54c57000)
      libogg.so.0 => /usr/lib/x86_64-linux-gnu/libogg.so.0 (0x00007fab54a4e000)
      libvorbis.so.0 => /usr/lib/x86_64-linux-gnu/libvorbis.so.0 (0x00007fab54823000)
      libvorbisenc.so.2 => /usr/lib/x86_64-linux-gnu/libvorbisenc.so.2 (0x00007fab5457a000)
      libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007fab5435f000)
      libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007fab5414a000)
      /home/rbenda/NANO-D/SAMSON/0.7.0/Binaries:.:./SAMSONQtLibs:/home/rbenda/anaconda3/lib:
      Python library has not been loaded: Cannot load library libpython3.6m: (libpython3.6m: cannot open shared object file: No such file or directory)

      Do you think it is only due to this "libpython3.6m" library problem ?

      Thank you very much for your help, sorry for all theses problems and disturbance...
      Have a nice evening
      Robert

      1 Reply Last reply
      0
      • DmitriyMarinD
        DmitriyMarinD
        DmitriyMarin
        wrote on last edited by
        #17

        Thank you for posting the log, @Robert !

        The fact that it cannot find Python:

        Python found in the system:
        Python executable: /home/rbenda/anaconda3/bin/python3
        Python library has not been loaded: Cannot load library libpython3.6m: (libpython3.6m: cannot open shared object file: No such file or directory)
        

        should not cause any problem when launching SAMSON, it is only used in the Python Scripting Element in SAMSON.

        But there are other lines which might indicate an issue, e.g.:

        libxcb.so.1 => /home/rbenda/anaconda3/lib/libxcb.so.1
        

        Could you, please, try launching SAMSON with the following line commented in the ./SAMSON-Core.sh script:

        export LD_LIBRARY_PATH=${PYTHON_LIBRARY_PATH}:${LD_LIBRARY_PATH}
        

        such that libxcb.so and other libraries won't be used from the anaconda3 installation. If they are still used from there you might want to check your environment variables (see ~/.bashrc) and excluding the path to anaconda3 from there just for the try.

        But, I do not think that might be causing an issue since I am using anaconda3 under Ubuntu 16.04 (I use Python in SAMSON) and I have the same linking.

        Dmitriy,
        The SAMSON Team, https://s-c.io

        1 Reply Last reply
        0
        • R
          R
          Robert
          wrote on last edited by
          #18

          Thanks Dmitriy !

          Indeed, commenting this line in the SAMSON-Core.sh script yields :

          libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f5750b03000)

          instead in the terminal.

          DmitriyMarinD 1 Reply Last reply
          0
          • R Robert

            Thanks Dmitriy !

            Indeed, commenting this line in the SAMSON-Core.sh script yields :

            libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f5750b03000)

            instead in the terminal.

            DmitriyMarinD
            DmitriyMarinD
            DmitriyMarin
            wrote on last edited by
            #19

            @Robert

            Does it help with the problem you have?

            Dmitriy,
            The SAMSON Team, https://s-c.io

            1 Reply Last reply
            0
            • DmitriyMarinD
              DmitriyMarinD
              DmitriyMarin
              wrote on last edited by
              #20

              @Robert

              When you executed the glxinfo | grep OpenGL command in the terminal you got:

              ...
              OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.8
              ...
              OpenGL version string: 3.0 Mesa 18.2.8
              

              Whilst your system supports OpenGL 4.5 and SAMSON asks for OpenGL 3.2+ during the installation, in some cases, the Mesa driver might provide OpenGL 3.0 for better compatibility. You can specify the version you want using the MESA_GL_VERSION_OVERRIDE environment variable. This should force the correct version of OpenGL to be used. To check how it works, you might do in the terminal smth like this:

              MESA_GL_VERSION_OVERRIDE=4.5 glxinfo | grep OpenGL
              

              Could you, please, try setting this variable in the script that launches SAMSON-Core (please, try versions 3.2, 4.2, and 4.5):

              MESA_GL_VERSION_OVERRIDE=4.5 ./SAMSON-Core
              

              Dmitriy,
              The SAMSON Team, https://s-c.io

              1 Reply Last reply
              0
              • R
                R
                Robert
                wrote on last edited by
                #21

                Hello Dmitryi, thanks for your help.

                Having:
                libxcb.so.1 => /usr/ lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f5750b03000)

                (i.e. the fact that libxcb.so and other libraries are not used from the anaconda3 installation, when commenting the line
                export LD_LIBRARY_PATH=${PYTHON_LIBRARY_PATH}:${LD_LIBRARY_PATH}
                in SAMSON-Core.sh script)

                didn't solve the graphical problem when launching ./SAMSON-Core.sh.

                I have a strange problem since this morning, when I try to launch ./SAMSON-Core directly, instead of ./SAMSON-Core.sh (which "works", i.e. open the SAMSON window but with the graphical problem you know), I obtain an error message :

                ./SAMSON-Core: error while loading shared libraries: libSAMSON.so: cannot open shared object file: No such file or directory.

                I did the two commands:
                MESA_GL_VERSION_OVERRIDE=4.5 glxinfo | grep OpenGL

                MESA_GL_VERSION_OVERRIDE=4.5 ./SAMSON-Core

                but for the second one, I obtain an error message (be it for 4.5, 3.2 or 4.2) ; the same error message as when launching ./SAMSON-Core :

                ./SAMSON-Core: error while loading shared libraries: libSAMSON.so: cannot open shared object file: No such file or directory

                Sorry for so much trouble, hoping to solve it today !( but I have access to another fixed computer where SAMSON works today, so I can also work while trying to solve this problem on my laptop).
                Regards,
                Robert

                1 Reply Last reply
                0
                • R
                  R
                  Robert
                  wrote on last edited by
                  #22

                  Concerning libSAMSON.so, it is strange because I have it in my directory /NANO-D/SAMSON/0.7.0/Binaries . (and I checked but I think I didn't change the SAMSON-Core.sh script after re-commenting all the lines, so ./SAMSON-Core should open the interface as before...)

                  1 Reply Last reply
                  0
                  • DmitriyMarinD
                    DmitriyMarinD
                    DmitriyMarin
                    wrote on last edited by
                    #23

                    On Linux, the SAMSON-Core.sh script is necessary for launching the SAMSON-Core executable since it sets up paths to necessary libraries. That's why when launching just the SAMSON-Core executable you may have an error about missing libraries.

                    Could you, please, try modifying the SAMSON-Core.sh script as follows (with different OpenGL versions: 3.2, 4.2, and 4.5):

                    MESA_GL_VERSION_OVERRIDE=4.5 ./SAMSON-Core
                    

                    Dmitriy,
                    The SAMSON Team, https://s-c.io

                    1 Reply Last reply
                    0
                    • R
                      R
                      Robert
                      wrote on last edited by
                      #24

                      Thank you, I tried with the three versions 3.2, 4.2 and 4.5 but it didn't work ...

                      I inserted the line
                      MESA_GL_VERSION_OVERRIDE=4.5 ./SAMSON-Core

                      just before the final line of ./SAMSON-Core.sh :
                      echo "restoring context"

                      (I don't know if it is the right place...)

                      1 Reply Last reply
                      0
                      • DmitriyMarinD
                        DmitriyMarinD
                        DmitriyMarin
                        wrote on last edited by
                        #25

                        Does the following command in the terminal:

                        MESA_GL_VERSION_OVERRIDE=4.5 glxinfo | grep OpenGL
                        

                        among other output show you (for your version of Mesa):

                        OpenGL version string: 4.5 Mesa 18.2.8
                        

                        Basically, it should specify the version of OpenGL provided by Mesa.

                        In the SAMSON-Core.sh script you can try modifying it as follow (see the line with ./SAMSON-Core):

                        ...
                        export LD_LIBRARY_PATH=$script_dir:.:./SAMSONQtLibs:$LD_LIBRARY_PATH
                        
                        #ldd SAMSON-Core	#uncomment to have more information if SAMSON crashes
                        #echo $LD_LIBRARY_PATH	#uncomment to have more information if SAMSON crashes
                        MESA_GL_VERSION_OVERRIDE=4.5 ./SAMSON-Core --logconsole			#available flags --disablenetwork /--import /--logconsole /--logfile "file" /--logdefaultfile
                        
                        export LD_LIBRARY_PATH=$SAVED_LD_LIBRARY_PATH
                        export LC_ALL=$SAVED_LC_ALL
                        echo "restoring context"
                        

                        You can try modifying the OpenGL version to 3.2, 4.2, 4.5. Does it launch SAMSON and do you still have the same problem?

                        Dmitriy,
                        The SAMSON Team, https://s-c.io

                        1 Reply Last reply
                        0
                        • R
                          R
                          Robert
                          wrote on last edited by
                          #26

                          Yes, with :
                          MESA_GL_VERSION_OVERRIDE=4.5 glxinfo | grep OpenGL

                          I obtain :
                          OpenGL version string: 4.5 (Compatibility Profile) Mesa 18.2.8

                          I tried this modification you proposed in the ./SAMSON-Core.sh, at the right place, SAMSON launches but I have the same graphical problem be it for 3.2, 4.2 and 4.5 versions ... I get a lot of information in the terminal while SAMSON is launching, do you want me to paste it ? (it is a bit long ...)

                          1 Reply Last reply
                          0
                          • R
                            R
                            Robert
                            wrote on last edited by
                            #27

                            In the end of the message when launching SAMSON, I obtain :
                            ....

                              -  "elementName" "Graphene Sheet Creator"
                              -  "elementDeveloperID" "C682B30F-0D21-4CDB-B968-B72E225DDC8F"
                              -  "elementID" "FF9BE415-C812-1C1A-CDBE-78896176B067"
                              -  "elementVersion" "0.7.0"
                              -  "checksumDebug" 0
                              -  "checksumRelease" 0
                              -  "elementDescription" ""
                              -  "elementOS" ""
                              -  "samsonVersion" "0.7.0"
                              -  "forceUpdate" false
                              -----------------------------------------------------------------------
                            

                            =============================================================================

                            QPixmap::scaled: Pixmap is a null pixmap
                            libpng warning: iCCP: known incorrect sRGB profile
                            libpng warning: iCCP: known incorrect sRGB profile
                            "File"
                            "File"
                            "Edit"
                            "Edit"
                            "App"
                            QLayout: Attempting to add QLayout "" to SBGWidgetOnExit "", which already has a layout
                            restoring context

                            DmitriyMarinD 1 Reply Last reply
                            0
                            • DmitriyMarinD
                              DmitriyMarinD
                              DmitriyMarin
                              wrote on last edited by DmitriyMarin
                              #28

                              No, there is no need to post the output, it has a lot of information because of the --logconsole flag.

                              We will try to see what we can do about this issue.

                              Dmitriy,
                              The SAMSON Team, https://s-c.io

                              1 Reply Last reply
                              0
                              • R Robert

                                In the end of the message when launching SAMSON, I obtain :
                                ....

                                  -  "elementName" "Graphene Sheet Creator"
                                  -  "elementDeveloperID" "C682B30F-0D21-4CDB-B968-B72E225DDC8F"
                                  -  "elementID" "FF9BE415-C812-1C1A-CDBE-78896176B067"
                                  -  "elementVersion" "0.7.0"
                                  -  "checksumDebug" 0
                                  -  "checksumRelease" 0
                                  -  "elementDescription" ""
                                  -  "elementOS" ""
                                  -  "samsonVersion" "0.7.0"
                                  -  "forceUpdate" false
                                  -----------------------------------------------------------------------
                                

                                =============================================================================

                                QPixmap::scaled: Pixmap is a null pixmap
                                libpng warning: iCCP: known incorrect sRGB profile
                                libpng warning: iCCP: known incorrect sRGB profile
                                "File"
                                "File"
                                "Edit"
                                "Edit"
                                "App"
                                QLayout: Attempting to add QLayout "" to SBGWidgetOnExit "", which already has a layout
                                restoring context

                                DmitriyMarinD
                                DmitriyMarinD
                                DmitriyMarin
                                wrote on last edited by
                                #29

                                @robert

                                This output is totally ok.

                                Dmitriy,
                                The SAMSON Team, https://s-c.io

                                1 Reply Last reply
                                0
                                • DmitriyMarinD
                                  DmitriyMarinD
                                  DmitriyMarin
                                  wrote on last edited by
                                  #30

                                  @Robert

                                  What you can also do, if you want to try, is to add a PPA with newer drivers (see this launchpad page) - it provides recently updated X and Mesa free graphics drivers for Intel, etc:

                                  sudo add-apt-repository ppa:oibaf/graphics-drivers
                                  sudo apt-get update
                                  

                                  Update with it and may try installing the following package:

                                  sudo apt-get install xserver-xorg-video-intel
                                  

                                  P.s.: if you install packages from this PPA and later want to update Ubuntu to a newer version it is recommended to remove these packages and PPA before upgrading (see this launchpad page).

                                  Dmitriy,
                                  The SAMSON Team, https://s-c.io

                                  1 Reply Last reply
                                  0
                                  • R
                                    R
                                    Robert
                                    wrote on last edited by
                                    #31

                                    Thanks for these ideas. I tried but it didn't work.
                                    I still have the same problem.

                                    I will maybe focus on my problem for VMD, as you say it is maybe more general than SAMSON, it is a global graphics problem maybe.
                                    Or maybe I could try a complete new installation of SAMSON , don't know if it could rearrange things thanks to the last installed packages...

                                    Thanks again, Robert

                                    DmitriyMarinD 1 Reply Last reply
                                    0
                                    • R Robert

                                      Thanks for these ideas. I tried but it didn't work.
                                      I still have the same problem.

                                      I will maybe focus on my problem for VMD, as you say it is maybe more general than SAMSON, it is a global graphics problem maybe.
                                      Or maybe I could try a complete new installation of SAMSON , don't know if it could rearrange things thanks to the last installed packages...

                                      Thanks again, Robert

                                      DmitriyMarinD
                                      DmitriyMarinD
                                      DmitriyMarin
                                      wrote on last edited by
                                      #32

                                      @robert
                                      You can try re-installing, but I do not think it will resolve the issue.

                                      Dmitriy,
                                      The SAMSON Team, https://s-c.io

                                      1 Reply Last reply
                                      0
                                      • R
                                        R
                                        Robert
                                        wrote on last edited by
                                        #33

                                        Hi Dmitryi, hope you are doing well. I tried reinstalling SAMSON but it didn't solve the problem indeed...
                                        I don't want you of course to solve my problem for VMD ^^, (I have also written to VMD for assistance) but I can share you this info , maybe it is linked to the problem I have with SAMSON : when I open vmd (which seems, as SAMSON, perfectly installed), I get the following message in the terminal :

                                        Info) VMD for LINUXAMD64, version 1.9.3 (December 1, 2016)
                                        Info) http://www.ks.uiuc.edu/Research/vmd/
                                        Info) Email questions and bug reports to vmd@ks.uiuc.edu
                                        Info) Please include this reference in published work using VMD:
                                        Info) Humphrey, W., Dalke, A. and Schulten, K., `VMD - Visual
                                        Info) Molecular Dynamics', J. Molec. Graphics 1996, 14.1, 33-38.
                                        Info) -------------------------------------------------------------
                                        Info) Multithreading available, 8 CPUs detected.
                                        Info) Free system memory: 28GB (90%)
                                        Info) Dynamically loaded 2 plugins in directory:
                                        Info) /usr/local/lib/vmd/plugins/LINUXAMD64/molfile
                                        vmd >

                                        bot nothing opens (no VMD interface).

                                        Moreover, if I type "menu main status", I get "off", anf if I type "menu main on" (to activate the menu), and again "menu main status", I still get "off". If I type "menu list", I get nothing (meaning that there is no available menu, which is why I don't even get the main menu window opening).

                                        What is really strange is that VMD seems to have been perfectly installed, as I can analyse a pdb file as follows :

                                        vmd CF_OX_monomer_11_SAMSON.pdb

                                        in the terminal gives :

                                        Info) VMD for LINUXAMD64, version 1.9.3 (December 1, 2016)
                                        Info) http://www.ks.uiuc.edu/Research/vmd/
                                        Info) Email questions and bug reports to vmd@ks.uiuc.edu
                                        Info) Please include this reference in published work using VMD:
                                        Info) Humphrey, W., Dalke, A. and Schulten, K., `VMD - Visual
                                        Info) Molecular Dynamics', J. Molec. Graphics 1996, 14.1, 33-38.
                                        Info) -------------------------------------------------------------
                                        Info) Multithreading available, 8 CPUs detected.
                                        Info) Free system memory: 28GB (90%)
                                        Info) Dynamically loaded 2 plugins in directory:
                                        Info) /usr/local/lib/vmd/plugins/LINUXAMD64/molfile
                                        Info) File loading in progress, please wait.
                                        Info) Using plugin pdb for structure file CF_OX_monomer_11_SAMSON.pdb
                                        Info) Using plugin pdb for coordinates from file CF_OX_monomer_11_SAMSON.pdb
                                        Info) Determining bond structure from distance search ...
                                        Info) Eliminating bonds duplicated from existing structure...
                                        Info) Finished with coordinate file CF_OX_monomer_11_SAMSON.pdb.
                                        Info) Analyzing structure ...
                                        Info) Atoms: 93
                                        Info) Bonds: 99
                                        Info) Angles: 0 Dihedrals: 0 Impropers: 0 Cross-terms: 0
                                        Info) Bondtypes: 0 Angletypes: 0 Dihedraltypes: 0 Impropertypes: 0
                                        Info) Residues: 1
                                        Info) Waters: 0
                                        Info) Segments: 1
                                        Info) Fragments: 1 Protein: 2 Nucleic: 0
                                        vmd > exit
                                        Info) VMD for LINUXAMD64, version 1.9.3 (December 1, 2016)
                                        Info) Exiting normally.

                                        In another computer where VMD works perfectly, I get the following message in the terminal when opening VMD :

                                        /usr/local/lib/vmd/vmd_LINUXAMD64: /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1: no version information available (required by /usr/local/lib/vmd/vmd_LINUXAMD64)
                                        Info) VMD for LINUXAMD64, version 1.9.3 (November 30, 2016)
                                        Info) http://www.ks.uiuc.edu/Research/vmd/
                                        Info) Email questions and bug reports to vmd@ks.uiuc.edu
                                        Info) Please include this reference in published work using VMD:
                                        Info) Humphrey, W., Dalke, A. and Schulten, K., `VMD - Visual
                                        Info) Molecular Dynamics', J. Molec. Graphics 1996, 14.1, 33-38.
                                        Info) -------------------------------------------------------------
                                        Info) Multithreading available, 4 CPUs detected.
                                        Info) CPU features: SSE2 AVX AVX2 FMA
                                        Info) Free system memory: 681MB (35%)
                                        Info) No CUDA accelerator devices available.
                                        Warning) Detected X11 'Composite' extension: if incorrect display occurs
                                        Warning) try disabling this X server option. Most OpenGL drivers
                                        Warning) disable stereoscopic display when 'Composite' is enabled.
                                        Info) OpenGL renderer: SVGA3D; build: RELEASE; LLVM;
                                        Info) Features: STENCIL MDE CVA MTX NPOT PP PS GLSL(OVF)
                                        Info) Full GLSL rendering mode is available.
                                        Info) Textures: 2-D (4096x4096), 3-D (256x256x256), Multitexture (8)
                                        Info) Dynamically loaded 2 plugins in directory:
                                        Info) /usr/local/lib/vmd/plugins/LINUXAMD64/molfile
                                        vmd >

                                        => so OpenGL seems also to be what lacks (at least in the messages in the terminal) for me for VMD to open its menu and graphics, so maybe, concerning SAMSON, it is due to a bad installation of OpenGL, I don't know...

                                        Thank you.
                                        Regards,
                                        Robert

                                        1 Reply Last reply
                                        0
                                        • DmitriyMarinD
                                          DmitriyMarinD
                                          DmitriyMarin
                                          wrote on last edited by DmitriyMarin
                                          #34

                                          @Robert

                                          I think, it might be connected to the Wayland display being used instead of Xorg (see: https://forum.samson-connect.net/topic/37/installing-or-running-samson-on-ubuntu-17-04-and-later-versions). I would suggest you to try installing Xorg and disabling Wayland display.

                                          See, e.g.: https://linuxconfig.org/how-to-disable-wayland-and-enable-xorg-display-server-on-ubuntu-18-04-bionic-beaver-linux

                                          Dmitriy,
                                          The SAMSON Team, https://s-c.io

                                          1 Reply Last reply
                                          0

                                          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                          With your input, this post could be even better 💗

                                          Register Login
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post