[raiguard][2.1.8] Blueprint file drag and drop fails for Linux Steam version.

[Chindraba]

Using the Linux version on Steam, not some PlayOnSteam thing.
With the Steam version set to 2.1.8 I open a new game and attempt to drag in a blueprint file and nothing happens.

To ensure everything was correct with new versions and potential changes I launced a new game, switched to editor, placed 4 storage tanks and made a blueprint. I exported the generated string, standard and JSON, to files. I also minified the JSON into a third file. The drag and drop for all three files failed silently. No error messages, no sounds, and no new blueprint in the cursor.
Performing the same action, with the same files, in the stand-alone version of 2.1.8 works as it has ever since the feature was introduced in 2.0.25.

What I expected is for the file to be imported as a blueprint to either place or save in the library.
(This actually failed in 2.1.7 but I was too slow to report it.)

Using the Linux version on Steam for 2.0.77 it still works as normal. (Attempting to rule out a change in Steam's interface.)
While there seems to be nothing helpful in the log file, it is attached anyway.
No save file is included as none was made or needed to be used. Stating with a new game.

[raiguard]

Could you please test it with SDL_EVENT_LOGGING=1 and post that log, as well as test X11 vs. Wayland? I suspect this is an SDL bug.

Wild shot in the dark: are you using xwayland-satellite? If you are, and the game is running on X11, then drag-and-drop won't work.

[Chindraba]

Unless Steam is doing something in the background there should be no Wayland involvement. I tried it a while back and found it was not ready for primetime on my system and reinstalled.
The SDL flag, however, has been set and the the test re-run.
Results are the same, but the log may help.

If you need any other setting changed, I'll be happy to give them a try.

[raiguard]

Ah, SDL is logging to stdout/stderr instead of the log file, so you will need to run it from the terminal in order to get the sdl event log output.

What I am looking for is to check whether or not it is receiving SDL drag-and-drop events.

[Chindraba]

I'm not sure how to capture stdout/stderr when Steam forces a relaunch when using CLI.
However, it has to be receiving the drag/drop events because the string import works, except the non-minified JSON.
Different report on that. viewtopic.php?t=134510

[Chindraba]

Using the command

Code: Select all

steam steam://rungameid/427520

to launch Steam and the game from CLI I do get what looks like the same thing as is generated in the log file.
I attempted to drag/drop a file, and failed. Then I drag/drop the text of that file from Kate and had success.
This is what the console gave me.

[Prommah]

0.000 Program arguments: "/home/chindraba/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio" "SDL_EVENT_LOGGING=1"

From this it looks like you're passing SDL_EVENT_LOGGING=1 as an argument, rather than setting it as an environment variable.

I'm assuming you're using the launch options in Steam. If you are, by default that just appends what you put in there as arguments to the game. You need to make it put the env variable before the executable, and you can also make it a bit easier & cleaner to log the output using launch options as well. So, for example, use this as the launch options for Factorio to set the env variable & log the console output to /home/chindraba/factorio-console.log

SDL_EVENT_LOGGING=1 %command% > ~/factorio-console.log 2>&1

Then you should get a bunch of lines starting with SDL EVENT: SDL_EVENT_ in that log file.

[Chindraba]

Paydirt
Complete raft of lines.
Same process: filed drag on file, success on drag of string.
All mods off this time as well.

[Chindraba]

If it helps, here is the same log file when using 2.0.77 in Steam.

[raiguard]

Thanks for the log. This might be because you're running plasma 6 on X11, which unfortunately I cannot easily test. I need to figure out a better system for testing various desktop environments and distros before I can look at this. For now, just copy/paste or drag the text.

[Chindraba]

Thanks for the log. This might be because you're running plasma 6 on X11, which unfortunately I cannot easily test. I need to figure out a better system for testing various desktop environments and distros before I can look at this. For now, just copy/paste or drag the text.

Understood. Linux is still a distro-hell scene. For my use-case Wayland isn't ready for prime-time so it's X11 for now.
Unlikely, but if you need me to do something 'odd' as a test, always willing. I'm even brave enough to drop in the random binary if need. You and WUBE have earned that trust.

Edit: For the record, unlike what I'd hoped after the JSON fix, this still remains in 2.1.12