Another crash in Rime of Frostmaiden / 5E. I posted player side logs over in Windows crash thread. I did not get server side logs. However, attached is my syslog.
Printable View
nothing happens when trying to run, if I try often enough I see a brief outline of a box popup and go away. No error, only thing I can find is in syslog
Apr 10 21:27:04 1USER-HP-G72 org.mate.panel.applet.BriskMenuFactory[26336]: FGUpdaterEngine path is /home/1USER/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
Apr 10 21:27:04 1USER-HP-G72 org.mate.panel.applet.BriskMenuFactory[26336]: Looking for update in /home/1USER/.smiteworks/fantasygrounds/FantasyGroundsUpdater_NEW
Apr 10 21:27:04 1USER-HP-G72 org.mate.panel.applet.BriskMenuFactory[26336]: /home/1USER/.smiteworks/fantasygrounds/FantasyGroundsUpdater_NEW not found
Apr 10 21:27:04 1USER-HP-G72 org.mate.panel.applet.BriskMenuFactory[26336]: Changing directory to /home/1USER/.smiteworks/fantasygrounds/FGUpdaterEngine
Apr 10 21:27:04 1USER-HP-G72 org.mate.panel.applet.BriskMenuFactory[26336]: Launching FGUpdaterEngine: /home/1USER/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
Apr 10 21:27:04 1USER-HP-G72 org.mate.panel.applet.BriskMenuFactory[26336]: Found path: /home/1USER/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
Apr 10 21:27:04 1USER-HP-G72 org.mate.panel.applet.BriskMenuFactory[26336]: Loading in SingleInstance mode
Using Ubuntu Mate
DISTRIB_DESCRIPTION="Ubuntu 18.04.5 LTS"
Linux 1USER-HP-G72 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
I've checked permissions of things and they all look right to me. No error message or window or anything running in background. Running via icon or term same effect.
1USER@1USER-HP-G72:~/.smiteworks/fantasygrounds$ ./FantasyGroundsUpdater
FGUpdaterEngine path is /home/1USER/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
Looking for update in /home/1USER/.smiteworks/fantasygrounds/FantasyGroundsUpdater_NEW
/home/1USER/.smiteworks/fantasygrounds/FantasyGroundsUpdater_NEW not found
Changing directory to /home/1USER/.smiteworks/fantasygrounds/FGUpdaterEngine
Launching FGUpdaterEngine: /home/1USER/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
Found path: /home/1USER/.smiteworks/fantasygrounds/FGUpdaterEngine/FGUpdaterEngine.x86_64
Loading in SingleInstance mode
And then nothing. When i run it with strace, I do se some mention of not finding files....
openat(AT_FDCWD, "/etc/xdg/xdg-mate/vulkan/explicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/xdg/vulkan/explicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/vulkan/explicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/mate/vulkan/explicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/local/share/vulkan/explicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/vulkan/explicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/var/lib/snapd/desktop/vulkan/explicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/1USER/.local/share/vulkan/explicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/xdg/xdg-mate/vulkan/implicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/xdg/vulkan/implicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/vulkan/implicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/mate/vulkan/implicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/local/share/vulkan/implicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/vulkan/implicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/var/lib/snapd/desktop/vulkan/implicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/1USER/.local/share/vulkan/implicit_layer.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
geteuid() = 1000
getuid() = 1000
getegid() = 1000
getgid() = 1000
openat(AT_FDCWD, "/etc/xdg/xdg-mate/vulkan/icd.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/xdg/vulkan/icd.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/vulkan/icd.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/mate/vulkan/icd.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/local/share/vulkan/icd.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/vulkan/icd.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/var/lib/snapd/desktop/vulkan/icd.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/home/1USER/.local/share/vulkan/icd.d", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
write(8, "Vulkan detection: 0\n", 20) = 20
write(8, "No supported renderers found, ex"..., 63) = 63
munmap(0x7f98fc42d000, 2417288) = 0
getpid() = 3980
unlink("/dev/shm/mono.3980") = 0
futex(0x161b1a8, FUTEX_WAKE_PRIVATE, 2147483647) = 4
futex(0x161b158, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7f990df399d0, FUTEX_WAIT, 3982, NULL) = 0
futex(0x7f990cf379d0, FUTEX_WAIT, 3984, NULL) = 0
madvise(0x7f9920000000, 4194304, MADV_DONTNEED) = 0
mprotect(0x7f9920000000, 4194304, PROT_NONE) = 0
munmap(0x7f9920000000, 268435456) = 0
getpid() = 3980
exit_group(1) = ?
+++ exited with 1 +++
This line here looks like your issue:
write(8, "No supported renderers found, ex"..., 63) = 63
Try checking your video drivers (glxinfo | grep "OpenGL version") and update them if necessary
Thanks for the suggestion, I'm not seeing an issue...
$ glxinfo | grep -i opengl
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (ILK)
OpenGL version string: 2.1 Mesa 20.0.8
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 20.0.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:
$ lspci |grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
Dunno if this is Linux or just general but here are logs from games where the game just stopped responding to any input and had to be shut down. Both times with an image open (game map).
Attachment 46456
Attachment 46457
Attachment 46458
There's nothing in the log files. If the program appears to "stop responding" vs. crash, that's usually indicative of a ruleset/extension loop issue. There's nothing I saw in the log files; so I would suggest removing all non-official extensions when trying again.
Regards,
JPG
I just started having connection issues to the cloud systems this evening, which I reported via:
https://www.fantasygrounds.com/forum...l=1#post600004
I'm not sure this is Linux specific.
It is unlikely to be Linux specific. However, as I posted there, we need logs from both the GM and the player right after the connection is attempted.
Thanks,
JPG
If the issue was image performance related, then v4.1 is probably going to help.
If the issue was memory related, then we're still looking at Unity 2020 LTS migration after v4.1 initial release settles.
Regards,
JPG