Salome wayland session not opening debian/ubuntu based system

1

Hello,
I am facing the same issue as mentioned here:

having the same error message when I run ./salome (or ./mesa_salome)

X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 3 (X_GetWindowAttributes)
Resource id in failed request: 0xe
Serial number of failed request: 10
Current serial number in output stream: 11

is there any solution that does not involve fall back to X11 for the hole system?
(also for extra info, my sat output is OK for everything)
this is happening with the ubuntu specific. I just tested with the universal, in this case it works with the exception of the explode function in GEOM
regards

2

Hello Franco,

to make Explode work, try to add these extra libraries extra_libs.tgz (1,2 Mo) for the universal binaries.

Extract them in SALOME-9.12.0/BINARIES-CO7 and add in salome after system_dep:

    context.addToLdLibraryPath(out_dir_Path + r"/BINARIES-CO7/extra_libs")

Christophe

3

Hello christophe,
thanks for your help, this solved the problems with explode function, just a small detail for others that might have the same issue there is a missing “/” in the line of code to add the correct line is:
context.addToLdLibraryPath(out_dir_Path + r"/BINARIES-CO7/extra_libs")
and to insert directly in the correct location (for new users out there)

salome_folder=SALOME-9.12.0
cd $salome_folder
sed -i 's|# context.addToLdLibraryPath(out_dir_Path + r"/BINARIES-CO7/system_dep/gl")|# context.addToLdLibraryPath(out_dir_Path + r"/BINARIES-CO7/system_dep/gl")\n    context.addToLdLibraryPath(out_dir_Path + r"/BINARIES-CO7/extra_libs")|' "./mesa_salome"

regards

4

Thank you Franco for the feedback. I have added the missing / to my message.

Christophe

1 Like
5

Hello christophe,
with the universal version, if I do some manipulations (go to geom-> create a primitive → go to mesh → create mesh of primitive), when I go to close the program and select not save. I am getting several errors of ‘SIGSEGV ‘segmentation violation’ detected. address X’ with X values being [0, 0, 30, 8].
I don’t care a lot about the errors themselves, as I can hit okey but the issue is that (sometimes yes sometimes no) the next time I open salome , ALL my toolbars in geom and mesh (disappear and I need to re activate them one by one).
if you don’t have clues on how to solve this, what is the file that saves the setup of the toolbars in salome? if necessary I could delate it (so it goes back to default) or make a copy and overwrite after each close of salome…

6

Hello Franco,

to retrieve the original position of the toolbars, you can delete the files SalomeApprc.* in $HOME/.config/salome but you will use other preferences. If you want to keep other preferences, you can edit the last file and only remove the windows_geometry section.

Christophe

7

Concerning the Wayland issue, maybe someone could test the following to see whether it resolves the reported issue.

   export QT_OPENGL_NO_SANITY_CHECK=1
   ./salome

Thanks

8

Hello @NabilG
I can confirm that stills same behavior,
I am getting the following error after trying to open any module (with ./salome and ./mesa_salome) over wayland session.
my complete OS info:

kde plasma version 6.0.4
kde frameworks version 6.1.0
qt version 6.7.0
kernel version 6.5.0-10036-tuxedo (64 bit)
session wayland

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  3 (X_GetWindowAttributes)
  Resource id in failed request:  0xe
  Serial number of failed request:  10
  Current serial number in output stream:  11

from sat tool, it looks like I have all the dependencies

1 Like
9

I am using Ubuntu 24.04 and the SALOME-9.13.0-native-UB24.04-SRC binaries - I keep getting the same X error when I want to switch to “Geometry” or any other mode.

The presented workaround does not work for me - is there any other fix that could work for me?

1 Like
10

only I have found myself to be able to use salome in wayland, is to use the universal linux distribution. the one for ubuntu you need to log in a Xserver session, with xwayland it does not work. or at least couldn’t make it work myself.

11

I have the same problem with the same configuration as you (salome 9.13 on ubuntu 24.04). Did you manage to make Salome work?

I’m now using Salome from the command line. I hope my Python code is correct, but I cannot monitor it.

12

you can use the universal linux distribution that one works with wayland

1 Like
13

Hi there,

Is there any news about this Wayland issue? I am facing exactly the same issue and I cannot switch to X11 session in my system anymore and I only have wayland. And, is it possible to compile the universal version by myself? Because I cannot download it from Salome site due to the reCAPCHA test. I have difficulty to access any Google service here. I can git the source code from github and compile it myself.

14

Hello,

For those who has problem with Wayland session, there is a workaround.

QT_QPA_PLATFORM=xcb salome

works for me. It forces salome to run under X11 even when you are in a wayland session. Some explanation: when

QT_DEBUG_PLUGINS=1 QT_DEBUG_PLATFORMM=1 QT_LOGGING_RULES=qt.qpa.*=true" WAYLAND_DEBUG=1 SALOME_VERBOSE=1 salome -V2 > salome.log 2>&1

I got some information in salome.log:

SALOME_Session_Server.cxx [140] : Warning: Wayland does not support QWindow::requestActivate()

………..

X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 3 (X_GetWindowAttributes) Resource id in failed request: 0x10 Serial number of failed request: 28 Current serial number in output stream: 29

It looks like that when you try to activate some modules (SHAPER, GEOM, SMESH, HEXABLOCK), SALOME calls function QWidget::activateWindow() which calls QWindow::requestActivate() underlyingly. But Wayland doesn’t support QWindow::requestActivate() intendedly.

Wayland’s design philosophy prioritizes security and user control, preventing applications from disrupting the user’s workflow by forcefully activating or focusing windows. This behavior contrasts with X11, where such actions are permitted.

It’s quite difficult to trace which process exactly calls Qwidget::activateWindow() or QWindow::requestActivate() which causes the crash so I just use QT_QPA_PLATFORM=xcb as a workaround at this moment.

1 Like