Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

[KNOWN] hung graphics driver

Discussion in 'Critical Issues (Blockers, Performance, Crashes)' started by Alley Oop, Mar 19, 2019.

Thread Status:
Not open for further replies.
  1. Alley Oop

    Alley Oop Bug Hunter Bug Moderator

    Messages:
    15,679
    Likes Received:
    19,463
    Trophy Points:
    153
    i am still having the xid 16 completely hung graphics driver crashes that started in r62 patch 900. this requires a full reboot, i can't even switch to a tty. it is not a multi-player issue, though that does make it MUCH more likely. on my end, i have done a full reinstall, bumped the driver from 415.27 to 418.43, tried dropping back to kernel 4.14, tried downgrading cuda to version 9, and paid close attention to system temps (they're fine) but given it started with a specific patch i don't think the trouble is on my end.

    03/19/2019 14:51
    Title:
    Reproduction Rate:
    Blocker?
    Details:
    Steps to Reproduce:
    User Specs:
    OS: Linux 4.20 ManjaroLinux 18.0.4 64bit
    CPU: Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz (4) System RAM: 24053
    GPU: GeForce GTX 970/PCIe/SSE2 GPU RAM: 4096
    SotA.QA.Linux.64.818.Date.03.19.19
    Area: Novia_R9_Forest01_01
    Area Display Name: South Boundless Forest
    Loc: (332.3, 21.9, -302.8)
    Debug: Tm92aWFfUjlfRm9yZXN0MDFfMDF8fCgzMzIuMjk4LCAyMS44ODgsIC0zMDIuNzU4KXwoMCwgMC45ODcsIDAsIC0wLjE2Mil8MTQzLjQ2MjJ8MTYuOTg1NDV8MTg=
     
  2. Chris

    Chris Tech Lord Moderator Ambassador SOTA Developer

    Messages:
    2,470
    Likes Received:
    27,551
    Trophy Points:
    190
    Gender:
    Male
    If you're linux OS is crashing to the point of requiring a full reboot, that does sound like a driver specific problem. No program should be able to make Linux crash unless there is a driver problem. This is almost certainly a side effect of us switching to 2018.3. Hopefully we'll get some more linux people in to test it so we can see if it is specific to your card or OS flavor or if it something more global. Might have some work around for you by forcing a different render pipeline on the command line but waiting for more info first.

    SOTA-64305
     
    Feeyo likes this.
  3. Undone

    Undone Trap Master Moderator SOTA Developer

    Messages:
    346
    Likes Received:
    848
    Trophy Points:
    43
    I am not encountering any issues on on Ubuntu 18.04 with nvidia 390 drivers on OpenGL. Vulkan crashes on startup but that is a known issue. Does this happen immediately? Only in a specific location? etc...
     
    Feeyo likes this.
  4. Feeyo

    Feeyo Avatar

    Messages:
    1,716
    Likes Received:
    2,520
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    When removing my QA client, extracting it and starting the QA patcher for the first time. My whole desktop crashes. Could be the same issue.

    Some output:
    Code:
    Mar 20 18:35:01 DevRig org.gnome.Shell.desktop[6741]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a00005 (Shroud of )
    
    Mar 20 18:35:26 DevRig org.gnome.Nautilus[6661]: Found path: /home/feeyo/SHROUD/SOTAQA/Shroud of the Avatar - Launcher.x86_64
    Mar 20 18:35:26 DevRig org.gnome.Nautilus[6661]: Mono path[0] = '/home/feeyo/SHROUD/SOTAQA/Shroud of the Avatar - Launcher_Data/Managed'
    Mar 20 18:35:26 DevRig org.gnome.Nautilus[6661]: Mono path[1] = '/home/feeyo/SHROUD/SOTAQA/Shroud of the Avatar - Launcher_Data/Mono'
    Mar 20 18:35:26 DevRig org.gnome.Nautilus[6661]: Mono config path = '/home/feeyo/SHROUD/SOTAQA/Shroud of the Avatar - Launcher_Data/Mono/etc'
    Mar 20 18:35:26 DevRig org.gnome.Nautilus[6661]: displaymanager : xrandr version warning. 1.6
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-0: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-1: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): Samsung U28E590 (DFP-2): connected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): Samsung U28E590 (DFP-2): Internal DisplayPort
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): Samsung U28E590 (DFP-2): 1440.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-3: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-4: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-5: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-6: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-6: 1440.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-7: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig org.gnome.Nautilus[6661]: client has 4 screens
    Mar 20 18:35:26 DevRig org.gnome.Nautilus[6661]: displaymanager screen (0)(DP-0): 2880 x 1620
    Mar 20 18:35:26 DevRig org.gnome.Nautilus[6661]: Using libudev for joystick management
    Mar 20 18:35:26 DevRig org.gnome.Nautilus[6661]: Importing game controller configs
    
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-0: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-1: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): Samsung U28E590 (DFP-2): connected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): Samsung U28E590 (DFP-2): Internal DisplayPort
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): Samsung U28E590 (DFP-2): 1440.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-3: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-4: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-5: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-6: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-6: 1440.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-7: disconnected
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
    Mar 20 18:35:26 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    
    
    Mar 20 18:35:26 DevRig gnome-shell[6741]: Native children wider or taller than 65535 pixels are not supported
    Mar 20 18:35:26 DevRig gnome-shell[6741]: The program 'gnome-shell' received an X Window System error.
                                              This probably reflects a bug in the program.
                                              The error was 'BadAlloc (insufficient resources for operation)'.
                                                (Details: serial 30584 error_code 11 request_code 12 (core protocol) minor_code 0)
                                                (Note to programmers: normally, X errors are reported asynchronously;
                                                 that is, you will receive the error a while after causing it.
                                                 To debug your program, run it with the GDK_SYNCHRONIZE environment
                                                 variable to change this behavior. You can then get a meaningful
                                                 backtrace from your debugger if you break on the gdk_x_error() function.)
    Mar 20 18:35:26 DevRig org.gnome.Shell.desktop[6741]: == Stack trace for context 0x559de8136340 ==
    Mar 20 18:35:26 DevRig systemd[1]: Started Process Core Dump (PID 7897/UID 0).
    Mar 20 18:35:27 DevRig polkitd[5415]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.102, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.utf8) (disconnected from bus)
    Mar 20 18:35:27 DevRig gnome-session[6686]: gnome-session-binary[6686]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
    Mar 20 18:35:27 DevRig gnome-session-binary[6686]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-0: disconnected
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-1: disconnected
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): Samsung U28E590 (DFP-2): connected
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): Samsung U28E590 (DFP-2): Internal DisplayPort
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): Samsung U28E590 (DFP-2): 1440.0 MHz maximum pixel clock
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-3: disconnected
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-4: disconnected
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-5: disconnected
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-6: disconnected
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-6: 1440.0 MHz maximum pixel clock
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-7: disconnected
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
    Mar 20 18:35:27 DevRig /usr/libexec/gdm-x-session[6680]: (--) NVIDIA(GPU-0):
    Mar 20 18:35:28 DevRig gsd-media-keys[6881]: g_variant_get_va: assertion 'value != NULL' failed
    Mar 20 18:35:28 DevRig gsd-media-keys[6881]: g_variant_unref: assertion 'value != NULL' failed
    Mar 20 18:35:28 DevRig systemd-coredump[7898]: Failed to get ACL: Operation not supported
    Mar 20 18:35:28 DevRig systemd-coredump[7898]: Process 6741 (gnome-shell) of user 1000 dumped core.
    
    
     
  5. Feeyo

    Feeyo Avatar

    Messages:
    1,716
    Likes Received:
    2,520
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    will try to patch up and see if I can reproduce the in game crash.
     
  6. Undone

    Undone Trap Master Moderator SOTA Developer

    Messages:
    346
    Likes Received:
    848
    Trophy Points:
    43
    was this trying vulkan or opengl?
     
  7. Alley Oop

    Alley Oop Bug Hunter Bug Moderator

    Messages:
    15,679
    Likes Received:
    19,463
    Trophy Points:
    153
    @Feeyo, if your crash is the same thing, then it's not nvidia, as i recall you use an amd card? are you able to switch to a tty when it happens to you?

    @Chris, i was under the impression that bumping up to 2018.3 was qa this release? this dates back to live patch 900. which version was that on, was it different from 899?

    @Undone, more-than-onces: i've had it happen three times in one run of upper tears, i've had it happen when first loading to the overworld, i've had it happen when first loading to the ardoris docks. this sort of thing is what made me think for a bit that it was a multiplayer issue. but then there are one-offs: for instance just walking through stinging tree when nobody else is there (and not when it's doing something that'd be an obvious clue like loading a house full of deco). the one on qa yesterday was simply moving after killing a lowbie archer by the grannus statue in south boundless forest.

    this was with opengl, i have not tried vulkan in a few releases.

    the problem with troubleshooting is that i can't get it to do it reliably. even upper tears, which makes it pretty darn likely, and can sometimes get through a whole attenuation.
     
  8. Feeyo

    Feeyo Avatar

    Messages:
    1,716
    Likes Received:
    2,520
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    OpenGL.

    I use an nvidia GTX1080. (nvidia-drivers-418.43-) How long can you play before it crashes? I just patched up and played for about 10 minutes without a crash.

    My gnome-shell got destroyed by the patcher, also tried running the patcher on my LXDE desktop and the same behavior happened. Yes I could do a ctrl+alt F4 to change TTY and pull out the dmesg output.
     
  9. Alley Oop

    Alley Oop Bug Hunter Bug Moderator

    Messages:
    15,679
    Likes Received:
    19,463
    Trophy Points:
    153
    sometimes for hours, as long as i'm solo. crashes in solo instances are very rare.

    ah, i cannot. even the tty is a solid white screen. did you have this problem previous to this qa? ...because mine dates back to live 900.
     
  10. Feeyo

    Feeyo Avatar

    Messages:
    1,716
    Likes Received:
    2,520
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    I did not have that issue in the previous QA. But I had not played a lot really.
     
  11. Feeyo

    Feeyo Avatar

    Messages:
    1,716
    Likes Received:
    2,520
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    Still getting these random errors:
    Code:
    Mar 20 19:32:15 DevRig org.gnome.Nautilus[9488]: Player data archive not found at `/home/feeyo/SHROUD/SOTAQA/Shroud of the Avatar - Launcher_Data/data.unity3d`, using local filesystem
     
  12. Undone

    Undone Trap Master Moderator SOTA Developer

    Messages:
    346
    Likes Received:
    848
    Trophy Points:
    43
    the patcher remains on an older version of unity and has not been updated in quite some time - so I'm not sure why it would just now begin causing problems? I hate to ask, but can either of you try ubuntu and see if the crashes persist? In principle it shouldn't matter but with unity you never know.

    Also can you start sharing your unity crash logs from these?
     
  13. Alley Oop

    Alley Oop Bug Hunter Bug Moderator

    Messages:
    15,679
    Likes Received:
    19,463
    Trophy Points:
    153
    i am not going to do that, i have dsl. also, i am not having patcher problems.

    i thought these were auto-uploaded by the patcher? where are they?
     
  14. Undone

    Undone Trap Master Moderator SOTA Developer

    Messages:
    346
    Likes Received:
    848
    Trophy Points:
    43
    Some are, some are not. But out of the ones that are I still do not know for sure which crashes are the ones that caused your entire desktop to lock up in this situation.
     
  15. Alley Oop

    Alley Oop Bug Hunter Bug Moderator

    Messages:
    15,679
    Likes Received:
    19,463
    Trophy Points:
    153
    okay, what's the path?
     
  16. Feeyo

    Feeyo Avatar

    Messages:
    1,716
    Likes Received:
    2,520
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    Sorry I am not offering support on trying it on Ubuntu. Re-compiling my desktop with Gentoo takes too much time to just try to reproduce it on Ubuntu.
    @Alley Oop I will be trying to reproduce it with playing tonight. Will post an update if any news.
    Also if you crash again, try your system joural: journalctl --since=2019-03-20
    Or change the date to when it crashed, it should be in there.
     
  17. Alley Oop

    Alley Oop Bug Hunter Bug Moderator

    Messages:
    15,679
    Likes Received:
    19,463
    Trophy Points:
    153
    i do not think the unity crash logs are in the system journal.
     
  18. Feeyo

    Feeyo Avatar

    Messages:
    1,716
    Likes Received:
    2,520
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    Your system crashed, they should show you what happened.
     
  19. Alley Oop

    Alley Oop Bug Hunter Bug Moderator

    Messages:
    15,679
    Likes Received:
    19,463
    Trophy Points:
    153
    they do, but it is not helpful. from my previous post:

    17:56:15 kernel: NVRM: GPU at PCI:0000:01:00: GPU-2eb63bff-eefd-13e0-0fd0-506f74521a06
    17:56:15 kernel: NVRM: Xid (PCI:0000:01:00): 16, Head 00000000 Count 0001e045
    17:56:15 kernel: NVRM: Xid (PCI:0000:01:00): 16, Head 00000000 Count 0001e045

    there are no oddities in the log before that. xid 16 is simply "Display engine hung"
     
  20. Undone

    Undone Trap Master Moderator SOTA Developer

    Messages:
    346
    Likes Received:
    848
    Trophy Points:
    43
    look in
    Code:
    ~/.config/unity3d/Portalarium/Shroud of the Avatar/sota_log.txt
    before you launch the game again (as this file will be overwritten)
     
Thread Status:
Not open for further replies.