Closed atolosadelgado closed 1 year ago
Update: there is a different error in lxplus9 (alma9) when the same steps are followed, :
PhysicsList +++ Transportation flag: 0
PhysicsList +++ Program decays: 0
PhysicsList +++ RangeCut: 0.700000
Geant4UI INFO +++ GlobalRangeCut> Install Geant4 control directory:/ddg4/GlobalRangeCut/
FieldSetup INFO Geant4 magnetic field tracking configured.
FieldSetup INFO G4MagIntegratorStepper:ClassicalRK4 G4Mag_EqRhs:Mag_UsualEqRhs
FieldSetup INFO Epsilon:[min:0.000050 mm max:0.001000 mm]
FieldSetup INFO Delta:[chord:0.250000 1-step:0.010000 intersect:0.001000] LargestStep 10000.000000 mm
**************************************************************
Geant4 version Name: geant4-11-01-patch-02 [MT] (15-June-2023)
Copyright : Geant4 Collaboration
References : NIM A 506 (2003), 250-303
: IEEE-TNS 53 (2006), 270-278
: NIM A 835 (2016), 186-225
WWW : http://geant4.org/
**************************************************************
Geant4UI INFO +++ Geant4RunManager> Install Geant4 control directory:/ddg4/Geant4RunManager/
Geant4RunManager WARN +++ Configured run manager of type: G4RunManager.
Geant4Kernel WARN +++ Multi-threaded mode requested, but not supported by this compilation of Geant4.
Geant4Kernel WARN +++ Falling back to single threaded mode.
Geant4Exec WARN +++ Only 1 subdetectors present. You sure you loaded the geometry properly?
G4PhysListFactory::GetReferencePhysList <FTFP_BERT> EMoption= 0
<<< Geant4 Physics List simulation engine: FTFP_BERT
Myphysics INFO Registered Geant4 physics constructor G4StepLimiterPhysics to physics list
UserInitialization INFO +++ Executing Geant4UserActionInitialization::Build. Context:0x1a0bd520 Kernel:0x1999efe0 [-1]
UI INFO +++ Starting G4UIExecutive 'DDG4' of type qt....
Available UI session types: [ Qt, tcsh, csh ]
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: linuxfb, minimal, offscreen, vnc, webgl, xcb.
*** Break *** abort
Hi,
@dkonst13 and I tried to dig a bit more in this issue. We tried the following points in Alma9 (lxplus9)
LCG view4 release provide DD4hep, and the initial code I posted works and the detector can be visualized using the Geant4 Qt interface.
However if Key4hep stack (nightlies*) is used instead, an error appears in the terminal saying that openGL and EGL are disabled (same error message as in the original post)
QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
and the Geant4 Qt interface window opens but it does not display the detector.
We found that the configuration summary of Qt in key4hep show this options:
X11 specific:
XLib ................................. no
XCB Xlib ............................. no
EGL on X11 ........................... no
xkbcommon-x11 ........................ yes
but the LCG view4 release show this other one
X11 specific:
XLib ................................. yes
XCB Xlib ............................. yes
EGL on X11 ........................... no
xkbcommon-x11 ........................ yes
and these flags were used for compiling Qt: -xcb -opengl
Could this be the source of the problem?
Thank you for your time.
*/cvmfs/sw-nightlies.hsf.org/key4hep/releases/latest/x86_64-almalinux9-gcc11.3.1-opt/key4hep-stack/2023-07-06-vkxwxh/setup.sh
Thanks for the information, I could reproduce. Potentially fixed in https://github.com/spack/spack/pull/39718 but won't be fixed in the stack until I make another complete build. I'll close the issue once the fixed build is in cvmfs.
The latest nightly should have fixed this, can you give it a try @atolosadelgado ?
Hurra!!! Both geoDisplay and Geant4-Qt visualization work now!! Thank you for fixing this!
Unrelated note: while configuring k4geo repository with the nightlies in my laptop (Alma9), I got this message, probably not important
CMake Warning (dev) at /cvmfs/sw-nightlies.hsf.org/key4hep/releases/2023-09-03/x86_64-almalinux9-gcc11.3.1-opt/cmake/3.27.4-qc4pvz/share/cmake-3.27/Modules/CMakeFindDependencyMacro.cmake:76 (find_package):
Policy CMP0144 is not set: find_package uses upper-case <PACKAGENAME>_ROOT
variables. Run "cmake --help-policy CMP0144" for policy details. Use the
cmake_policy command to set the policy and suppress this warning.
Environment variable BOOST_ROOT is set to:
/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2023-09-03/x86_64-almalinux9-gcc11.3.1-opt/boost/1.83.0-vt5zkb
For compatibility, find_package is ignoring the variable, but code in a
.cmake module might still use it.
Call Stack (most recent call first):
/cvmfs/sw-nightlies.hsf.org/key4hep/releases/2023-09-03/x86_64-almalinux9-gcc11.3.1-opt/dd4hep/ce7bfea294a4daa5bfeb590852fabe3ca87353c4=develop-k2ojli/cmake/DD4hepConfig.cmake:49 (FIND_DEPENDENCY)
CMakeLists.txt:40 (find_package)
This warning is for project developers. Use -Wno-dev to suppress it.
Unrelated note: while configuring k4geo repository with the nightlies in my laptop (Alma9), I got this message, probably not important
That's a harmless and unrelated warning, you can ignore it
Closing since this is now working (https://github.com/spack/spack/pull/39718 plus possibly changing -system-xcb
to xcb
), the releases won't be fixed but the next one will have the fix.
Geant4 Qt visualization do not work properly. The code below shows the steps for building a dummy detector, and opening via ddsim the Geant4-Qt interface, but the detector is not displayed (just a black window instead). When LCG view release is used instead of key4hep, the steps lead to the correct display of the detector.
Some error messages appear in the terminal when ddsim is launched, maybe related to Qt?
Thank you for your time :) Alvaro