Exporting Character problem in 5.0.0 in Linux

[ffujita]

While I originally had this problem using the Draw Steel ruleset, I've replicated the problem in the Sample 5e Campaign. When I try to export a character, FG just dies. The FG window disappears. I'm thrown back to the desktop. I'm using Fedora Linux, and will provide additional information if it will help you to nail down the problem.

I don't have access to a windows machine right now, and I hadn't tried to export a character on previous versions of FG in Linux -- sorry.

Frank

[superteddy57]

I'm on Ubuntu and also tested with Debian and haven't run into this issue. The supported distro is Ubuntu and might require more troubleshooting on your end to see why it's failing. You could try running it through the terminal and seeing what kind of errors that might be produced when you try to export.

[Moon Wizard]

Responded in the original thread.

https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/1997012993/Linux+Starting+FGU+with+Wayland+Instead+of+x11+Com positor

JPG

[Speculi]

With Wayland becoming more and more the mainstream and X11 getting faded out, is there anything you can do to fix this?
Maybe an update to the file browser plugin you are using? Not sure which version you are on...

Starting with X11 backend works as a workaround.

Relevant log for open/save file dialog crashes on Wayland:



Caught fatal signal - signo:11 code:1 errno:0 addr:0x1323b36210
Obtained 20 stack frames.
#0 0x007f4b94e01b98 in getWindowFromPid
#1 0x007f4b94e01c7b in getUnityWindow
#2 0x007f4b94e01efd in GTKOpenPanel
#3 0x007f4b94e01e2a in DialogOpenFilePanelAsync
#4 0x0000004220ff53 in (wrapper managed-to-native) Crosstales.FB.Wrapper.Linux.NativeMethods:DialogOp enFilePanelAsync (string,string,string,bool,Crosstales.FB.Wrapper.L inux.NativeMethods/AsyncCallback)
#5 0x0000004220fc2f in Crosstales.FB.Wrapper.FileBrowserLinux:OpenFilesAs ync (string,string,string,bool,Crosstales.FB.Extension Filter[],System.Action`1<string[]>)
#6 0x0000004220f6ba in Crosstales.FB.FileBrowser:OpenFilesAsync (string,string,string,bool,Crosstales.FB.Extension Filter[])
#7 0x000000421fe59f in FEJEDEPIKDL:ADIHDHOJKEF (int,bool,string,System.Collections.Generic.List`1<System.ValueTuple`2<string, string>>)
#8 0x0000004220e66b in LLEJHGCHBDD:DDDBLEEFJPF (intptr)
#9 0x0000004200ea57 in (wrapper native-to-managed) LLEJHGCHBDD:DDDBLEEFJPF (intptr)
#10 0x00000041ffe0ce in (wrapper managed-to-native) KeraLua51.NativeMethods:lua_pcall (intptr,int,int,int)
#11 0x00000041ffe043 in KeraLua51.Lua:PCall (int,int,int)
#12 0x00000041ffdf8f in JEAPNOMMHMC:IFOEMGIHOML (int,int,bool)
#13 0x000000420b8d27 in BGKNOHPJLAI:BCGDIPADBCG (int,int)
#14 0x0000004220d447 in DEKMCGAGBCB:MGFPBANEPEJ ()
#15 0x0000004220d1df in DEKMCGAGBCB:ReceiveClickUp (int,UnityEngine.Vector2Int modreq(System.Runtime.InteropServices.InAttribute)&)
#16 0x0000004220d015 in NNODHJOADMC:KIFJPOAEFGA (int)
#17 0x000000421fc7e3 in NNODHJOADMC:FDENFOEBLBE ()
#18 0x000000421fc14f in FG.FGDesktop:BBGABPMFMKH ()
#19 0x00000041ff5263 in FG.FGDesktop:Update ()
#20 0x00000041d3bc15 in (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr)




Caught fatal signal - signo:11 code:1 errno:0 addr:0xbffa8d818
Obtained 21 stack frames.
#0 0x007ff88e401b98 in getWindowFromPid
#1 0x007ff88e401c7b in getUnityWindow
#2 0x007ff88e4021c6 in GTKSavePanel
#3 0x007ff88e401eb8 in DialogSaveFilePanelAsync
#4 0x0000004187883e in (wrapper managed-to-native) Crosstales.FB.Wrapper.Linux.NativeMethods:DialogSa veFilePanelAsync (string,string,string,string,Crosstales.FB.Wrapper .Linux.NativeMethods/AsyncCallback)
#5 0x0000004187854f in Crosstales.FB.Wrapper.FileBrowserLinux:SaveFileAsy nc (string,string,string,Crosstales.FB.ExtensionFilte r[],System.Action`1<string>)
#6 0x00000041878149 in Crosstales.FB.FileBrowser:SaveFileAsync (string,string,string,Crosstales.FB.ExtensionFilte r[])
#7 0x00000041875c07 in FEJEDEPIKDL:PPMDMNHDLKI (FEJEDEPIKDL/AJOJDFIMLNC,string,string)
#8 0x0000004187523f in FG.ImageDataModeToolbar:ExportImage ()
#9 0x000000413f1b2a in UnityEngine.Events.InvokableCall:Invoke ()
#10 0x0000004155d2d7 in UnityEngine.Events.UnityEvent:Invoke ()
#11 0x0000004155d207 in UnityEngine.UI.Button:Press ()
#12 0x0000004155d19b in UnityEngine.UI.Button:OnPointerClick (UnityEngine.EventSystems.PointerEventData)
#13 0x00000041542d11 in UnityEngine.EventSystems.ExecuteEvents:Execute (UnityEngine.EventSystems.IPointerClickHandler,Uni tyEngine.EventSystems.BaseEventData)
#14 0x00000041542a7b in UnityEngine.EventSystems.StandaloneInputModule:Rel easeMouse (UnityEngine.EventSystems.PointerEventData,UnityEn gine.GameObject)
#15 0x0000004151a41f in UnityEngine.EventSystems.StandaloneInputModule:Pro cessMousePress (UnityEngine.EventSystems.PointerInputModule/MouseButtonEventData)
#16 0x000000414f2603 in UnityEngine.EventSystems.StandaloneInputModule:Pro cessMouseEvent (int)
#17 0x000000414f24ef in UnityEngine.EventSystems.StandaloneInputModule:Pro cessMouseEvent ()
#18 0x000000414f20bb in UnityEngine.EventSystems.StandaloneInputModule:Pro cess ()
#19 0x0000004130dbcb in UnityEngine.EventSystems.EventSystem:Update ()
#20 0x000000412f8175 in (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr)

[slaapliedje]

Here's your fix;

vim .local/share/applications/FantasyGrounds.desktop
And add to the Exec= line the GDK_BACKEND=x11 bit.
Should look like this;

Exec=env GDK_BACKEND=x11 $HOME/.smiteworks/fantasygrounds/FantasyGrounds.x86_64

I tried to add it to the wiki, but I do not have edit access, apparently.

Edit: This worked on KDE under Arch and Gnome under Arch as well, but it should be pretty universal.

[ffujita]

I'm sure I'm on the road to getting this fixed, but as of now, things are worse.

While before, FG would run until I tried to export a character, now it will not open at all.

I've tried adding the x11 code to my FantasyGrounds.desktop file and I've tried launching from Terminal. I get the Updater showing up, but when I try to launch FG, it kicks me back to the updater.

from the terminal here is my output:

frank@fedora:~$ GDK_BACKEND=x11 ./.smiteworks/fantasygrounds/FantasyGrounds.x86_64
FGUpdaterEngine path is /home/frank/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
Looking for update in /home/frank/.smiteworks/fantasygrounds/FantasyGroundsUpdater_NEW
/home/frank/.smiteworks/fantasygrounds/FantasyGroundsUpdater_NEW not found
Changing directory to /home/frank/.smiteworks/fantasygrounds/FGUpdaterEngine
Launching FGUpdaterEngine: /home/frank/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
[UnityMemory] Configuration Parameters - Can be set up in boot.config
"memorysetup-bucket-allocator-granularity=16"
"memorysetup-bucket-allocator-bucket-count=8"
"memorysetup-bucket-allocator-block-size=4194304"
"memorysetup-bucket-allocator-block-count=1"
"memorysetup-main-allocator-block-size=16777216"
"memorysetup-thread-allocator-block-size=16777216"
"memorysetup-gfx-main-allocator-block-size=16777216"
"memorysetup-gfx-thread-allocator-block-size=16777216"
"memorysetup-cache-allocator-block-size=4194304"
"memorysetup-typetree-allocator-block-size=2097152"
"memorysetup-profiler-bucket-allocator-granularity=16"
"memorysetup-profiler-bucket-allocator-bucket-count=8"
"memorysetup-profiler-bucket-allocator-block-size=4194304"
"memorysetup-profiler-bucket-allocator-block-count=1"
"memorysetup-profiler-allocator-block-size=16777216"
"memorysetup-profiler-editor-allocator-block-size=1048576"
"memorysetup-temp-allocator-size-main=4194304"
"memorysetup-job-temp-allocator-block-size=2097152"
"memorysetup-job-temp-allocator-block-size-background=1048576"
"memorysetup-job-temp-allocator-reduction-small-platforms=262144"
"memorysetup-allocator-temp-initial-block-size-main=262144"
"memorysetup-allocator-temp-initial-block-size-worker=262144"
"memorysetup-temp-allocator-size-background-worker=32768"
"memorysetup-temp-allocator-size-job-worker=262144"
"memorysetup-temp-allocator-size-preload-manager=262144"
"memorysetup-temp-allocator-size-nav-mesh-worker=65536"
"memorysetup-temp-allocator-size-audio-worker=65536"
"memorysetup-temp-allocator-size-cloud-worker=32768"
"memorysetup-temp-allocator-size-gfx=262144"
Loading in SingleInstance mode

I'm sorry I'm not a linux veteran, I just switched from Windows a month ago, but I'm pretty good at following directions. TiA for any help here.

Frank

[AlterZwerg]

Encountered a similar problem with exporting a map while running FG on Ubuntu 24.04.
FG would crash instantly, same with trying to export a character.
Starting FG via the Terminal command from the Wiki (x11 instead of Wayland) solved the problem.

But as Speculi pointed out, Wayland will be the way to go in the long term.

[slaapliedje]

Encountered a similar problem with exporting a map while running FG on Ubuntu 24.04.
FG would crash instantly, same with trying to export a character.
Starting FG via the Terminal command from the Wiki (x11 instead of Wayland) solved the problem.

But as Speculi pointed out, Wayland will be the way to go in the long term.

Yeah, there is currently some sort of culture war going on with the x11 vs Wayland thing. I usually use this program to show people that Wayland is simply not ready (there's also some funkiness with Wine and clipboards, etc.
The issue seems to specifically be about opening the save/open dialog box from the program. Though I was having luck with loading tokens sometimes, on Wayland so I thought the issue may have been fixed, but it doesn't appear to be so.

[slaapliedje]

I'm sure I'm on the road to getting this fixed, but as of now, things are worse.

While before, FG would run until I tried to export a character, now it will not open at all.

I've tried adding the x11 code to my FantasyGrounds.desktop file and I've tried launching from Terminal. I get the Updater showing up, but when I try to launch FG, it kicks me back to the updater.

from the terminal here is my output:

frank@fedora:~$ GDK_BACKEND=x11 ./.smiteworks/fantasygrounds/FantasyGrounds.x86_64
FGUpdaterEngine path is /home/frank/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
Looking for update in /home/frank/.smiteworks/fantasygrounds/FantasyGroundsUpdater_NEW
/home/frank/.smiteworks/fantasygrounds/FantasyGroundsUpdater_NEW not found
Changing directory to /home/frank/.smiteworks/fantasygrounds/FGUpdaterEngine
Launching FGUpdaterEngine: /home/frank/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
[UnityMemory] Configuration Parameters - Can be set up in boot.config
"memorysetup-bucket-allocator-granularity=16"
"memorysetup-bucket-allocator-bucket-count=8"
"memorysetup-bucket-allocator-block-size=4194304"
"memorysetup-bucket-allocator-block-count=1"
"memorysetup-main-allocator-block-size=16777216"
"memorysetup-thread-allocator-block-size=16777216"
"memorysetup-gfx-main-allocator-block-size=16777216"
"memorysetup-gfx-thread-allocator-block-size=16777216"
"memorysetup-cache-allocator-block-size=4194304"
"memorysetup-typetree-allocator-block-size=2097152"
"memorysetup-profiler-bucket-allocator-granularity=16"
"memorysetup-profiler-bucket-allocator-bucket-count=8"
"memorysetup-profiler-bucket-allocator-block-size=4194304"
"memorysetup-profiler-bucket-allocator-block-count=1"
"memorysetup-profiler-allocator-block-size=16777216"
"memorysetup-profiler-editor-allocator-block-size=1048576"
"memorysetup-temp-allocator-size-main=4194304"
"memorysetup-job-temp-allocator-block-size=2097152"
"memorysetup-job-temp-allocator-block-size-background=1048576"
"memorysetup-job-temp-allocator-reduction-small-platforms=262144"
"memorysetup-allocator-temp-initial-block-size-main=262144"
"memorysetup-allocator-temp-initial-block-size-worker=262144"
"memorysetup-temp-allocator-size-background-worker=32768"
"memorysetup-temp-allocator-size-job-worker=262144"
"memorysetup-temp-allocator-size-preload-manager=262144"
"memorysetup-temp-allocator-size-nav-mesh-worker=65536"
"memorysetup-temp-allocator-size-audio-worker=65536"
"memorysetup-temp-allocator-size-cloud-worker=32768"
"memorysetup-temp-allocator-size-gfx=262144"
Loading in SingleInstance mode

I'm sorry I'm not a linux veteran, I just switched from Windows a month ago, but I'm pretty good at following directions. TiA for any help here.

Frank

Welcome to the land of Linux!
Hmm, I'm not getting the updater error.

GDK_BACKEND=x11 $HOME/.smiteworks/fantasygrounds/FantasyGrounds.x86_64

[UnityMemory] Configuration Parameters - Can be set up in boot.config
"memorysetup-bucket-allocator-granularity=16"
"memorysetup-bucket-allocator-bucket-count=8"
"memorysetup-bucket-allocator-block-size=4194304"
"memorysetup-bucket-allocator-block-count=1"
"memorysetup-main-allocator-block-size=16777216"
"memorysetup-thread-allocator-block-size=16777216"
"memorysetup-gfx-main-allocator-block-size=16777216"
"memorysetup-gfx-thread-allocator-block-size=16777216"
"memorysetup-cache-allocator-block-size=4194304"
"memorysetup-typetree-allocator-block-size=2097152"
"memorysetup-profiler-bucket-allocator-granularity=16"
"memorysetup-profiler-bucket-allocator-bucket-count=8"
"memorysetup-profiler-bucket-allocator-block-size=4194304"
"memorysetup-profiler-bucket-allocator-block-count=1"
"memorysetup-profiler-allocator-block-size=16777216"
"memorysetup-profiler-editor-allocator-block-size=1048576"
"memorysetup-temp-allocator-size-main=4194304"
"memorysetup-job-temp-allocator-block-size=2097152"
"memorysetup-job-temp-allocator-block-size-background=1048576"
"memorysetup-job-temp-allocator-reduction-small-platforms=262144"
"memorysetup-allocator-temp-initial-block-size-main=262144"
"memorysetup-allocator-temp-initial-block-size-worker=262144"
"memorysetup-temp-allocator-size-background-worker=32768"
"memorysetup-temp-allocator-size-job-worker=262144"
"memorysetup-temp-allocator-size-preload-manager=262144"
"memorysetup-temp-allocator-size-nav-mesh-worker=65536"
"memorysetup-temp-allocator-size-audio-worker=65536"
"memorysetup-temp-allocator-size-cloud-worker=32768"
"memorysetup-temp-allocator-size-gfx=262144"


might be a path issue, though $HOME should be the equivalent of /home/frank/, try it like that?

[ffujita]

Thanks for the suggestion. This will bring up the FGUpdater, but a window doesn't appear, and if I launch, once again it boots me out to the updater.

frank@fedora:~$ GDK_BACKEND=x11 $HOME/.smiteworks/fantasygrounds/FantasyGrounds.x86_64
FGUpdaterEngine path is /home/frank/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
Looking for update in /home/frank/.smiteworks/fantasygrounds/FantasyGroundsUpdater_NEW
/home/frank/.smiteworks/fantasygrounds/FantasyGroundsUpdater_NEW not found
Changing directory to /home/frank/.smiteworks/fantasygrounds/FGUpdaterEngine
Launching FGUpdaterEngine: /home/frank/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
[UnityMemory] Configuration Parameters - Can be set up in boot.config
"memorysetup-bucket-allocator-granularity=16"
"memorysetup-bucket-allocator-bucket-count=8"
"memorysetup-bucket-allocator-block-size=4194304"
"memorysetup-bucket-allocator-block-count=1"
"memorysetup-main-allocator-block-size=16777216"
"memorysetup-thread-allocator-block-size=16777216"
"memorysetup-gfx-main-allocator-block-size=16777216"
"memorysetup-gfx-thread-allocator-block-size=16777216"
"memorysetup-cache-allocator-block-size=4194304"
"memorysetup-typetree-allocator-block-size=2097152"
"memorysetup-profiler-bucket-allocator-granularity=16"
"memorysetup-profiler-bucket-allocator-bucket-count=8"
"memorysetup-profiler-bucket-allocator-block-size=4194304"
"memorysetup-profiler-bucket-allocator-block-count=1"
"memorysetup-profiler-allocator-block-size=16777216"
"memorysetup-profiler-editor-allocator-block-size=1048576"
"memorysetup-temp-allocator-size-main=4194304"
"memorysetup-job-temp-allocator-block-size=2097152"
"memorysetup-job-temp-allocator-block-size-background=1048576"
"memorysetup-job-temp-allocator-reduction-small-platforms=262144"
"memorysetup-allocator-temp-initial-block-size-main=262144"
"memorysetup-allocator-temp-initial-block-size-worker=262144"
"memorysetup-temp-allocator-size-background-worker=32768"
"memorysetup-temp-allocator-size-job-worker=262144"
"memorysetup-temp-allocator-size-preload-manager=262144"
"memorysetup-temp-allocator-size-nav-mesh-worker=65536"
"memorysetup-temp-allocator-size-audio-worker=65536"
"memorysetup-temp-allocator-size-cloud-worker=32768"
"memorysetup-temp-allocator-size-gfx=262144"
Loading in SingleInstance mode

[slaapliedje]

There is something funky going on there. When I launch it like that, and click the 'check for updates' it forks off the updater into another process, does it's updates, then flips back to the FGU app. It does that on three different computers, though I have not tested it on Fedora.

Two of the computers have Fantasy Grounds installed via Steam, and one is installed via their installer script downloaded directly from the fantasygrounds.com website. Is your install from Steam or the Script?

[ffujita]

I installed from the script.

[slaapliedje]

I installed from the script.
Hmm, are you using Fedora 43? I wonder if they broke something, they definitely seem to be very proud of breaking x11 compatibility in that version. Either way, it sounds like Xwayland / X11 support will be completely removed in GTK5 when that comes out, so Smiteworks really should fix this bug.

[ffujita]

Actually, I'm using Fedora 42. I was afraid of upgrading to 43.0, not because of the 43, but because of the .0 -- I figured I'd upgrade when it got to 43.1.

[Nylanfs]

Yeah, there is currently some sort of culture war going on ...

Once you've been in the 'nix universe enough you will find there's culture wars over damn near everything. :D

[slaapliedje]

Once you've been in the 'nix universe enough you will find there's culture wars over damn near everything. :D
Ha, pretty much.

Okay, I just tested it on an old/low spec laptop that I happen to still have Fedora 42 on, and it seemed to work correctly, so I'm not sure why it's forking off anything for the updater.

[lesliev]

I am on Ubuntu (22.04) with Wayland, running FGU under Steam - and I was able to export characters yesterday but today the game crashes as soon as I hit the save button after choosing the location.
The save dialogue shows and works fine.

FG data and programs are in these location on my system:
/home/leslie/.steam/debian-installation/steamapps/compatdata/1196310/pfx/drive_c/Program Files/SmiteWorks/Fantasy Grounds
/home/leslie/.steam/debian-installation/steamapps/compatdata/1196310/pfx/drive_c/users/steamuser/AppData/Roaming/SmiteWorks/Fantasy Grounds

The exports directory I was picking (where yesterday's file was):
/home/leslie/.steam/debian-installation/steamapps/compatdata/1196310/pfx/drive_c/Program Files/SmiteWorks/Fantasy Grounds/Exports

This Exports directory was owned by my user and other users had no write access to it.
Changing "Others Access" to "Create and delete files" fixed the issue, and FG could export after that.

Not sure what changed the permission, or if the user running FG changed, or if this will change again, but that was the problem.

[slaapliedje]

I am on Ubuntu (22.04) with Wayland, running FGU under Steam - and I was able to export characters yesterday but today the game crashes as soon as I hit the save button after choosing the location.
The save dialogue shows and works fine.

FG data and programs are in these location on my system:
/home/leslie/.steam/debian-installation/steamapps/compatdata/1196310/pfx/drive_c/Program Files/SmiteWorks/Fantasy Grounds
/home/leslie/.steam/debian-installation/steamapps/compatdata/1196310/pfx/drive_c/users/steamuser/AppData/Roaming/SmiteWorks/Fantasy Grounds

The exports directory I was picking (where yesterday's file was):
/home/leslie/.steam/debian-installation/steamapps/compatdata/1196310/pfx/drive_c/Program Files/SmiteWorks/Fantasy Grounds/Exports

This Exports directory was owned by my user and other users had no write access to it.
Changing "Others Access" to "Create and delete files" fixed the issue, and FG could export after that.

Not sure what changed the permission, or if the user running FG changed, or if this will change again, but that was the problem.
Odd. Can you post the results of this while Fantasy Grounds is running? It should show which user it is running as.

ps aux | grep -i Fantasy

[Moon Wizard]

You'll need to add the commands to force FG to run with X11 compositor:
https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/1997012993/Linux+Starting+FGU+with+Wayland+Instead+of+x11+Com positor

Regards,
JPG

[ffujita]

And that worked to get my FG running instead of closing out when I try to launch. It doesn't fix the exit from FG when I try to export a character problem.

Thanks for the partial solution.

Frank

[Moon Wizard]

The X11 compositor issue is what affects the export dialog as it's a limitation of the file dialog library we have to use.

Make sure you are running directly against the FG program and not against the FG Updater or FG Steam shortcut.

Regards,
JPG

[lesliev]

The X11 compositor issue is what affects the export dialog as it's a limitation of the file dialog library we have to use.

Make sure you are running directly against the FG program and not against the FG Updater or FG Steam shortcut.

Regards,
JPG

This is the file dialog, and it works for me, on Wayland:
65812

```
╰─➤ echo $XDG_SESSION_TYPE
wayland
```

I'm not sure why the permission change made a difference - but I tried 5 times before I made the permission change and it crashed every time, then I changed the permission of the Export directory with `chmod o+w Exports` and right after that I could export without error.

I guess I am seeing something different to everyone else? I am on Ubuntu 22.04.5 LTS.

I have `ps aux | grep -i Fantasy` and all the processes are running as me (leslie), so no idea on why this made a difference.

I just tested now again and the permissions for Exports are still `drwxrwxrwx` and I can still export to there.

HOWEVER, I can also export to the directory above that, with permissions `drwxrwxr-x`!

So I really don't understand what's going on!

[ffujita]

Okay, I'm not using Steam. So how do I know whether I'm "running directly against the FG program and not against the FG Updater"

Frank

[Moon Wizard]

What's the exact command line you are using?

Just as an aside, I'm not an expert at Linux by any means.
I only know that the file dialog libraries only work with X11, not Wayland. (According to all my previous information I've received.)
We just use Unity game engine and libraries to get FG running under Linux.
And, as most Linux users know, there is a lot of uniqueness in every distro, that can create unique scenarios.

Hopefully, someone more versed with Linux can chime in to help.
Regards,
JPG

[slaapliedje]

Okay, I'm not using Steam. So how do I know whether I'm "running directly against the FG program and not against the FG Updater"

Frank
In your ~/.smiteworks/fantasygrounds/ directory you should have FantasyGroundsUpdater and FantasyGrounds.x86_64. The latter is the actual app, that's what you want to launch with the GDK_BACKEND=x11 parameter.
This works perfectly fine whether I'm using Steam or not. It'd probably be easier to troubleshoot on the Discord for FGU or something.

@ Moon Wizard
Ha, I do Linux professionally, I still wouldn't see myself as an expert, though usually people pass the really hard to figure out mysteries to me, because I speak 'computer'. :P

[ffujita]

I'm in my second month of using Linux. I'm the person non-it people go to with Windows problems. But I'm just beginning to learn linux, and so:

I'm using Fedora 24 Gnome. I launch Fantasy Grounds from the Icon in my "Show Apps" window.

I modified the FantasyGrounds.desktop file, as described in: https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/1997012993/Linux+Starting+FGU+with+Wayland+Instead+of+x11+Com positor

Here is the contents of my FantasyGrounds.desktop file:
[Desktop Entry]
Version=1.0
Name=Fantasy Grounds
GenericName=Fantasy Grounds
Comment=Fantasy Grounds
Exec=env GDK_BACKEND=x11 $HOME/.smiteworks/fantasygrounds/FantasyGrounds.x86_64
Exec=/home/frank/.smiteworks/fantasygrounds/FantasyGrounds.x86_64
Path=/home/frank/.smiteworks/fantasygrounds
Icon=/home/frank/.smiteworks/fantasygrounds/FantasyGroundsIcon.png
Terminal=false
Type=Application
Categories=Game

TiA for any help (any of) you provide,

Frank

[slaapliedje]

I'm in my second month of using Linux. I'm the person non-it people go to with Windows problems. But I'm just beginning to learn linux, and so:

I'm using Fedora 24 Gnome. I launch Fantasy Grounds from the Icon in my "Show Apps" window.

I modified the FantasyGrounds.desktop file, as described in: https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/1997012993/Linux+Starting+FGU+with+Wayland+Instead+of+x11+Com positor

Here is the contents of my FantasyGrounds.desktop file:
[Desktop Entry]
Version=1.0
Name=Fantasy Grounds
GenericName=Fantasy Grounds
Comment=Fantasy Grounds
Exec=env GDK_BACKEND=x11 $HOME/.smiteworks/fantasygrounds/FantasyGrounds.x86_64
Exec=/home/frank/.smiteworks/fantasygrounds/FantasyGrounds.x86_64
Path=/home/frank/.smiteworks/fantasygrounds
Icon=/home/frank/.smiteworks/fantasygrounds/FantasyGroundsIcon.png
Terminal=false
Type=Application
Categories=Game

TiA for any help (any of) you provide,

Frank
Looks correct.
if you 'echo $HOME' it should give you '/home/frank/
Ha, the beauty of running Linux, when people ask you to fix their Windows, you just say "I'm sorry, I'm a Linux guy now." :)

[Speculi]

FG data and programs are in these location on my system:
/home/leslie/.steam/debian-installation/steamapps/compatdata/1196310/pfx/drive_c/Program Files/SmiteWorks/Fantasy Grounds
/home/leslie/.steam/debian-installation/steamapps/compatdata/1196310/pfx/drive_c/users/steamuser/AppData/Roaming/SmiteWorks/Fantasy Grounds


Looks like you are running the Windows version of FG through Steams Proton compatibility layer. That would indeed change how it behaves in regards to X11/Wayland, because now Proton/Wine would do the translation to open file dialogs instead of the library used in the Linux version.

[ffujita]

Looks like you are running the Windows version of FG through Steams Proton compatibility layer. That would indeed change how it behaves in regards to X11/Wayland, because now Proton/Wine would do the translation to open file dialogs instead of the library used in the Linux version.

I'm pretty sure that I downloaded and installed the linux version of FG. I have not installed Wine. I guess my Steam installation (I did not buy FG through Steam, but I have other games that I play via Steam) installed some version of Proton.

[Speculi]

I'm pretty sure that I downloaded and installed the linux version of FG.
Just to be clear, my post was an answer for "lesliev" not "ffujita". They seem to be using the Windows version of Fantasy Grounds through Steam Proton, judging by the given paths (".../pfx/drive_c/..." is a pretty clear indicator for that). That's why their experience is different from other Linux users, most likely.


I only know that the file dialog libraries only work with X11, not Wayland. (According to all my previous information I've received.)
And there are no updates for the library and they don't provide any support on this topic? As I mentioned, Wayland seems to be the future for basically every Linux distro... Should be in their interest to support going forward.

And, as most Linux users know, there is a lot of uniqueness in every distro, that can create unique scenarios.
Seems pretty universally related to Wayland...
Not sure if that's possible, but if I had access to the File Browser library and maybe the code snipped for how you invoke it from Unity, I would take a look at it. Of course no promises. Especially if the Linux library is only provided as a binary.

[slaapliedje]

Just to be clear, my post was an answer for "lesliev" not "ffujita". They seem to be using the Windows version of Fantasy Grounds through Steam Proton, judging by the given paths (".../pfx/drive_c/..." is a pretty clear indicator for that). That's why their experience is different from other Linux users, most likely.


And there are no updates for the library and they don't provide any support on this topic? As I mentioned, Wayland seems to be the future for basically every Linux distro... Should be in their interest to support going forward.

Seems pretty universally related to Wayland...
Not sure if that's possible, but if I had access to the File Browser library and maybe the code snipped for how you invoke it from Unity, I would take a look at it. Of course no promises. Especially if the Linux library is only provided as a binary.
If I were a betting man, it is likely making a call to the xdg file dialog box, or whatever it is called (I would need to look this up), as it does pull up the correct file dialog based on the desktop environment that you use. For example, dolphin in KDE and Nautilus under Gnome.
https://wayland.app/protocols/xdg-dialog-v1
https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/24

[nephranka]

Actually, I'm using Fedora 42. I was afraid of upgrading to 43.0, not because of the 43, but because of the .0 -- I figured I'd upgrade when it got to 43.1.

I am on Fedora 43 with no issues using the x11 hack. I run FG from a script:

#!/bin/sh
GDK_BACKEND=x11 /home/userx/.smiteworks/fantasygrounds/FantasyGrounds.x86_64

[ffujita]

I just wanted to mention that I'm no longer having a problem with exporting characters in FGU in Linux. My solution was to install via Steam. Back when I bought my FGU license, iirc the Steam version had its own separate license. But now it doesn't, the VTT is free, and when I installed via Steam, it just asked for my FG account sign in, and it worked just fine. So, while I was frustrated when the fix suggested here didn't work, I'm very pleased that Smiteworks makes the choice to use Steam or not painless.

Thanks!
Frank

[Speculi]

My solution was to install via Steam.



Here is the contents of my FantasyGrounds.desktop file:
[Desktop Entry]
Version=1.0
Name=Fantasy Grounds
GenericName=Fantasy Grounds
Comment=Fantasy Grounds
Exec=env GDK_BACKEND=x11 $HOME/.smiteworks/fantasygrounds/FantasyGrounds.x86_64
Exec=/home/frank/.smiteworks/fantasygrounds/FantasyGrounds.x86_64
Path=/home/frank/.smiteworks/fantasygrounds
Icon=/home/frank/.smiteworks/fantasygrounds/FantasyGroundsIcon.png
Terminal=false
Type=Application
Categories=Game


Most likely too late for you and you already found a solution that's working for you:
One reason why the "fix" didn't work for you might be the case, that you have two "Exec" lines in your .desktop file. One with the fix, one without.

[slaapliedje]

Most likely too late for you and you already found a solution that's working for you:
One reason why the "fix" didn't work for you might be the case, that you have two "Exec" lines in your .desktop file. One with the fix, one without.

Haha, I don't even know how I missed that! Yeah, that secondary exec line needs to be removed...

[Desktop Entry]
Version=1.0
Name=Fantasy Grounds
GenericName=Fantasy Grounds
Comment=Fantasy Grounds
Exec=env GDK_BACKEND=x11 /home/frank/.smiteworks/fantasygrounds/FantasyGrounds.x86_64
Path=/home/frank/.smiteworks/fantasygrounds
Icon=/home/frank/.smiteworks/fantasygrounds/FantasyGroundsIcon.png
Terminal=false
Type=Application
Categories=Game