Cuda installer strange behaviour

[wildtruc]

This is already partly said in last zenvidia changelog, but who reads that kind of log :)
So, I repeat it here and also because I finally found one of the reasons.

Since kernel 7 and Fedora 44 (maybe other recent distros), Cuda self extraction run package open an xterm window no matter what during extraction process then failed on its own --tmpdir option and send a term signal. Strange.

The work-around sounds to extract the package and execute the Cuda-installer in a temp dir separately. It looks easy, but not really in the facts.
There an extraction option in self-extrating package marked as --extract=xxx that .... didn't extract the whole package content. Strange, again.
But well, this is not the last.

So, the problem is that cuda self extracting run package doesn't have a real extraction tool, the installer is very minimalistic and the work-arround is to make it failed to preserve the package content. I won't tell how: I'm not really hurry that devs fix it.
All this is functional, but it didn't resolve the Xterm window pop up.

One of the reason (and for an unknown reason except a bug) comes with Yad usage which must use subshells to get a clean log window with pulse and one of them need to be run in background with & at the end to capture pid and display pulsing object. And .... Cuda -installer doesn't like that.
The process believe it is a external command line and start the Xterm to execute itself and ...... crash on its own tempdir option.
If the Xterm window shows up during primary extraction, don't close it, never.

The issue seem to not affect Nvidia drivers self extraction package at the moment. Hoping it wont.