Jump to content

Kyle Stemen

Very supportive Vintarian
  • Posts

    33
  • Joined

  • Last visited

Everything posted by Kyle Stemen

  1. I'm trying to use VSHUD v2.0.12 with VS 1.15.1 to connect to the RabbitTech server (with all the other required RabbitTech mods). I'm running Fedora 34. I was able to login once, but then when I started holding something, VS crashed. Since then, every time I login, it crashes. If I remove VSHUD, I can login. I've tried disabling everything in vshud.json, but it didn't help. The debug info printed to the console isn't very helpful. I included part of it below. The rest of it doesn't appear to be relevant. ================================================================= Native Crash Reporting ================================================================= Got a UNKNOWN while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= ... Thread 1 (Thread 0x7f3d77355740 (LWP 622017) "mono"): #0 0x00007f3d7708cb0f in __GI___wait4 (pid=pid@entry=622165, stat_loc=stat_loc@entry=0x7ffdf41e9ce4, options=options@entry=0, usage=usage@entry=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:30 #1 0x00007f3d7708ca8b in __GI___waitpid (pid=pid@entry=622165, stat_loc=stat_loc@entry=0x7ffdf41e9ce4, options=options@entry=0) at waitpid.c:38 #2 0x000055792c20893b in dump_native_stacktrace (signal=0x55792c4eaeb6 "UNKNOWN", mctx=0x7ffdf41ea840) at /usr/src/debug/mono-6.12.0-4.fc34.x86_64/mono/mini/mini-posix.c:1112 #3 0x000055792c1d1bbe in mono_dump_native_crash_info (info=<optimized out>, mctx=0x7ffdf41ea840, signal=0x55792c4eaeb6 "UNKNOWN") at /usr/src/debug/mono-6.12.0-4.fc34.x86_64/mono/mini/mini-posix.c:1154 #4 mono_handle_native_crash (signal=0x55792c4eaeb6 "UNKNOWN", mctx=0x7ffdf41ea840, info=<optimized out>) at /usr/src/debug/mono-6.12.0-4.fc34.x86_64/mono/mini/mini-exceptions.c:3423 #5 0x000055792c18b4ea in mono_crashing_signal_handler (_dummy=4, _info=0x7ffdf41eab30, context=0x7ffdf41eaa00) at ../utils/mono-signal-handler.c:77 #6 <signal handler called> () at ../sysdeps/unix/sysv/linux/sigaction.c #7 0x00000000420f0980 in () #8 0x00007f3cbbe8ab78 in () #9 0x00007f3c1a3ed580 in () #10 0x00007f3c1f924660 in () #11 0x0000000042376135 in () #12 0x0000000000001010 in () #13 0x000055792c49f588 in mono_threads_enter_gc_safe_region_unbalanced_internal (stackdata=0x7ffdf41eafc0) at ../utils/mono-threads-coop.c:290 #14 mono_threads_enter_gc_safe_region_unbalanced (stackpointer=<optimized out>) at ../utils/mono-threads-coop.c:298 #15 0x00007f3d6969b270 in () #16 0x00007ffdf41eb1b0 in () #17 0x00007f3d65b35a80 in () #18 0x0000000100000000 in () #19 0x0000000000000000 in () AL lib: (EE) ALCplaybackAlsa_mixerProc: Wait timeout... buffer size too low? [Inferior 1 (process 622017) detached] ================================================================= Basic Fault Address Reporting ================================================================= Memory around native instruction pointer (0x420f0980):0x420f0970 ff 25 00 00 00 00 c0 a1 d5 65 3d 7f 00 00 08 58 .%.......e=....X 0x420f0980 27 8e 38 79 55 00 00 00 00 00 00 00 00 00 00 00 '.8yU........... 0x420f0990 ff 25 00 00 00 00 c0 a2 d5 65 3d 7f 00 00 89 54 .%.......e=....T 0x420f09a0 24 10 48 b8 88 15 62 2c 79 55 00 00 f7 00 01 00 $.H...b,yU...... ================================================================= Managed Stacktrace: ================================================================= ================================================================= If I use gdb to attach to the process before it crashes, I can get it to report that the crash occurs in Vintagestory.API.Common.CollectibleObject:Vintagestory.API.Common.CollectibleObject.OnHeldIdle_Patch1. (gdb) bt #0 0x0000000040ea8a78 in () #1 0x00007fdc732be213 in () #2 0x00007fdbcd6f3098 in () #3 0x00007fdb23898360 in () #4 0x00007fdb2a05fa40 in () #5 0x0000000041124645 in () #6 0x0000000000001010 in () #7 0x0000557649ce2588 in mono_threads_enter_gc_safe_region_unbalanced_internal (stackdata=0x7ffd49534290) at ../utils/mono-threads-coop.c:290 #8 mono_threads_enter_gc_safe_region_unbalanced (stackpointer=<optimized out>) at ../utils/mono-threads-coop.c:298 #9 0x00007fdc7a81fa58 in () #10 0x00007ffd49534480 in () #11 0x00007fdc63bb9ad0 in () #12 0x0000000100000000 in () #13 0x0000000000000000 in () (gdb) p mono_pmip (0x00007fdc732be213) $7 = 0x5576510570d0 " (wrapper dynamic-method) Vintagestory.API.Common.CollectibleObject:Vintagestory.API.Common.CollectibleObject.OnHeldIdle_Patch1 (Vintagestory.API.Common.CollectibleObject,Vintagestory.API.Common.ItemS"... (gdb) p mono_pmip (0x0000000040ea8a78) $8 = 0x0 (gdb) up #1 0x00007fdc732be213 in ?? () (gdb) call mono_debug_print_vars ($rip, 1) Thread 1 "mono" received signal SIGSEGV, Segmentation fault. mono_method_get_param_names ( method="Vintagestory.API.Common.CollectibleObject:Vintagestory.API.Common.CollectibleObject.OnHeldIdle_Patch1 ()", names=0x0) at ../metadata/loader.c:1454 1454 names [i] = "";
  2. I installed VSHUD version v2.0.51 (non-compat), and my client hangs when I try to connect to the RabbitTech server. The message on the screen says "Data received, launching client instance." If I edit the vshud.json file and set "FDShow" to false, then I can join the server without problems. There are no problems in single player mode (with the same mods installed). I'm running Fedora Linux 33.
  3. Does anyone know how to get the clock GUI to work? I tried a lot of different variants of the .clockconfig command, with no luck. If I run .clockconfig without any arguments, the game crashes: Version: v1.13.0 (Stable)8/22/2020 9:39:28 PM: Critical error occurred System.NullReferenceException: Object reference not set to an instance of an object at VSHUD.ClockDialogSystem+<>c__DisplayClass6_0.<StartClientSide>b__2 (System.Int32 id, Vintagestory.API.Common.CmdArgs args) [0x00007] in <4653ab348fa043359047af2b3c5ff576>:0 at Vintagestory.API.Common.ClientChatCommand.CallHandler (Vintagestory.API.Common.IPlayer player, System.Int32 groupId, Vintagestory.API.Common.CmdArgs args) [0x00000] in <1535f56ebd604f7fa7b622e2b7e019b5>:0 at Vintagestory.Client.NoObf.HudDialogChat.HandleClientCommand (System.Int32 groupid, System.String command, Vintagestory.API.Common.CmdArgs arguments) [0x00036] in <baa2a5b2e6e247eb9851c6b55aad8342>:0 at Vintagestory.Client.NoObf.HudDialogChat.HandleClientCommand (System.String message, System.Int32 groupid) [0x0003f] in <baa2a5b2e6e247eb9851c6b55aad8342>:0 at Vintagestory.Client.NoObf.HudDialogChat.HandleClientMessage (System.Int32 groupid, System.String message) [0x0001e] in <baa2a5b2e6e247eb9851c6b55aad8342>:0 at Vintagestory.Client.NoObf.HudDialogChat.OnNewClientToServerChatLine (System.Int32 groupId, System.String message, Vintagestory.API.Common.EnumChatType chattype, System.String data) [0x00000] in <baa2a5b2e6e247eb9851c6b55aad8342>:0 at Vintagestory.Client.NoObf.ClientEventManager.TriggerNewClientChatLine (System.Int32 groupid, System.String message, Vintagestory.API.Common.EnumChatType chattype, System.String data) [0x00015] in <baa2a5b2e6e247eb9851c6b55aad8342>:0 at Vintagestory.Client.NoObf.HudDialogChat.OnKeyDown (Vintagestory.API.Client.KeyEvent args) [0x0008e] in <baa2a5b2e6e247eb9851c6b55aad8342>:0
  4. Distro / Kernel release : Fedora 28 Mono / .NET package version : mono-core-4.8.0-14.fc28.x86_64 Graphics driver version : akmod-nvidia-396.45-1.fc28.x86_64 Works for client, mp server or both : only tested client Installation method used : install.sh Hacks (if needed) : The Vintagestory.desktop file doesn't work. Have to run `mono Vintagestory.exe` directly Had to run `sudo cert-sync /etc/pki/tls/certs/ca-bundle.crt` to fix an "unable to connect to auth server" error. After closing the window or hitting the quit button, the program doesn't actually exit. Have to ctrl-Z it, then kill %1.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.