Jump to content
  • The game stopped starting on linux


    marksisma_deliri

    Summary: The game stopped starting

    Game Version: A20 b238
    Platform: PC
    OS/Version: Linux
    CPU Model: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
    System Memory: 16 GB
    GPU Model and VRAM: GeForce GTX 750 Ti 2048 MB
    Screen Resolution: 1920x1200
    Video Settings: Custom. A19 worked without problems with these settings, A20, before b238 also ran.
    Game mode: SP

    Did you wipe old saves? Yes & No
    Did you start a new game? Yes & No
    Did you validate your files? Yes
    Are you using any mods? No
    EAC on or off? Off

    Status: NEW

    Bug Description: After starting the game the game cursor appears, output of game overlap desktop, but nothing is drawn. Game seems to get a SIGSTOP signal (but in fact its process is running normally)

    Link to log: https://pastebin.com/9Fz6m41U

    Detailed steps to reproduce the bug: hmm idont know...

    1)Install Debian

    2)Install Steam

    3)Install 7dtd

    4)Run 7dtd

    ???
     


    User Feedback

    Recommended Comments

    6 hours ago, Jugginator said:

    What version debian

    cat /etc/os-release 
    PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
    NAME="Debian GNU/Linux"
    VERSION_ID="11"
    VERSION="11 (bullseye)"
    VERSION_CODENAME=bullseye
    ID=debian
    HOME_URL="https://www.debian.org/"
    SUPPORT_URL="https://www.debian.org/support"
    BUG_REPORT_URL="https://bugs.debian.org/"
     

    Link to comment
    Share on other sites

    14 hours ago, Liesel Weppen said:

    @marksisma_deliri

     

    System specs or it didn't happen.

     

    It DOES run fine on linux. You might have a different problem.

    The 7dtd has been working for me since the A18. Even the experimental A20 worked without problems. The problems started after the release of b238. My computer is certainly far from perfect, but I have no problems with most other games. Even Fallout4 via Proton works relatively stable. Now I've checked everything I had. Discovered a problem running Civilization6, Steam return "corrupted size vs. prev_size". Maybe it all has something to do with the Steam update that came out before the new year. I tried running 7dtd through 7dLauncher.x86_64, same result.

    Link to comment
    Share on other sites

    malloc(): invalid size (unsorted)

    from your log points to some problem with memory allocation. Since your video shows you have 16G RAM it should be sufficient.

    If your installation is corrupted, try verifying your files, or even better download it from scratch. If possible also try installing it to another hdd/ssd just to test if eventually your hdd/sdd is broken.

    Link to comment
    Share on other sites

    On 1/3/2022 at 7:14 PM, Liesel Weppen said:

    malloc(): invalid size (unsorted)

    from your log points to some problem with memory allocation. Since your video shows you have 16G RAM it should be sufficient.

    If your installation is corrupted, try verifying your files, or even better download it from scratch. If possible also try installing it to another hdd/ssd just to test if eventually your hdd/sdd is broken.

    I tried validating the game files through Steam earlier, there were no errors and no positive results either.
    I cleared the directory of the game, then ran the validation Steam, all the files were loaded and the game ran. I was about to write a happy comment, but I decided to go out and run it again. But the game again did not start:( I moved the directory with the game on three different block devices (2 hdd and 1 ssd), creating a symlink in the Steam directory, with no positive result.
    Finally I decided to check my RAM and got some pretty disturbing results:

    # dmidecode 3.3
    Getting SMBIOS data from sysfs.
    SMBIOS 2.7 present.

    Handle 0x0052, DMI type 17, 34 bytes
    Memory Device
        Array Handle: 0x0053
        Error Information Handle: 0x0057
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 8 GB
        Form Factor: DIMM
        Set: None
        Locator: ChannelA-DIMM0
        Bank Locator: BANK 0
        Type: DDR3
        Type Detail: Synchronous
        Speed: 1333 MT/s
        Manufacturer: 029E
        Serial Number: 00000000
        Asset Tag: 9876543210
        Part Number: CMX8GX3M1A1333C9  
        Rank: 2
        Configured Memory Speed: 1333 MT/s

    Handle 0x0053, DMI type 16, 23 bytes
    Physical Memory Array
        Location: System Board Or Motherboard
        Use: System Memory
        Error Correction Type: None
        Maximum Capacity: 16 GB
        Error Information Handle: 0x0054
        Number Of Devices: 2

    Handle 0x0056, DMI type 17, 34 bytes
    Memory Device
        Array Handle: 0x0053
        Error Information Handle: No Error
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 8 GB
        Form Factor: DIMM
        Set: None
        Locator: ChannelB-DIMM0
        Bank Locator: BANK 2
        Type: DDR3
        Type Detail: Synchronous
        Speed: 1333 MT/s
        Manufacturer: 029E
        Serial Number: 00000000
        Asset Tag: 9876543210
        Part Number: CMX8GX3M1A1333C9  
        Rank: 2
        Configured Memory Speed: 1333 MT/s
     

    memtester version 4.5.0 (64-bit)
    Copyright (C) 2001-2020 Charles Cazabon.
    Licensed under the GNU General Public License version 2 (only).

    pagesize is 4096
    pagesizemask is 0xfffffffffffff000
    want 8192MB (8589934592 bytes)
    got  8192MB (8589934592 bytes), trying mlock ...locked.
    Loop 1/5:
      Stuck Address       : ok         
      Random Value        : ok
      Compare XOR         : ok
      Compare SUB         : ok
      Compare MUL         : ok
      Compare DIV         : ok
      Compare OR          : ok
      Compare AND         : ok
      Sequential Increment: ok
      Solid Bits          : ok         
      Block Sequential    : ok         
      Checkerboard        : ok         
      Bit Spread          : ok         
      Bit Flip            : ok         
      Walking Ones        : ok         
      Walking Zeroes      : ok         
      8-bit Writes        : ok
      16-bit Writes       : ok

    Loop 2/5:
      Stuck Address       : ok         
      Random Value        : ok
      Compare XOR         : ok
      Compare SUB         : ok
      Compare MUL         : ok
      Compare DIV         : ok
      Compare OR          : ok
      Compare AND         : ok
      Sequential Increment: ok
      Solid Bits          : ok         
      Block Sequential    : testing 113FAILURE: 0x7171717071717171 != 0x7171717171717171 at offset 0x2d9dd220.
      Checkerboard        : ok         
      Bit Spread          : ok         
      Bit Flip            : ok         
      Walking Ones        : ok         
      Walking Zeroes      : ok         
      8-bit Writes        : ok
      16-bit Writes       : ok

    Loop 3/5:
      Stuck Address       : ok         
      Random Value        : ok
      Compare XOR         : ok
      Compare SUB         : ok
      Compare MUL         : ok
      Compare DIV         : ok
      Compare OR          : ok
      Compare AND         : ok
      Sequential Increment: ok
      Solid Bits          : ok         
      Block Sequential    : ok         
      Checkerboard        : ok         
      Bit Spread          : ok         
      Bit Flip            : ok         
      Walking Ones        : testing  53FAILURE: 0xffdffffeffffffff != 0xffdfffffffffffff at offset 0x2d9dd220.
      Walking Zeroes      : ok         
      8-bit Writes        : ok
      16-bit Writes       : ok

    Loop 4/5:
      Stuck Address       : ok         
      Random Value        : ok
      Compare XOR         : ok
      Compare SUB         : ok
      Compare MUL         : ok
      Compare DIV         : ok
      Compare OR          : ok
      Compare AND         : ok
      Sequential Increment: ok
      Solid Bits          : ok         
      Block Sequential    : ok         
      Checkerboard        : ok         
      Bit Spread          : ok         
      Bit Flip            : ok         
      Walking Ones        : testing  11FAILURE: 0xfffffffefffff7ff != 0xfffffffffffff7ff at offset 0x2d9dd220.
      Walking Zeroes      : ok         
      8-bit Writes        : ok
      16-bit Writes       : ok

    Loop 5/5:
      Stuck Address       : ok         
      Random Value        : ok
      Compare XOR         : ok
      Compare SUB         : ok
      Compare MUL         : ok
      Compare DIV         : ok
      Compare OR          : ok
      Compare AND         : ok
      Sequential Increment: ok
      Solid Bits          : ok         
      Block Sequential    : ok         
      Checkerboard        : ok         
      Bit Spread          : ok         
      Bit Flip            : ok         
      Walking Ones        : testing  71FAILURE: 0xfefffffeffffffff != 0xfeffffffffffffff at offset 0x2d9dd220.
      Walking Zeroes      : ok         
      8-bit Writes        : ok
      16-bit Writes       : ok

    Done.
    I have no idea what these errors mean. But apparently memtester writes some data and reads different data, when accessing a specific memory space, at offset 0x2d9dd220 right?
    But shouldn't programs or operating systems have integrity control mechanisms when reading/writing and handle such cases calmly? Or such mechanisms work only with file system, but not with RAM?

    Link to comment
    Share on other sites

    17 hours ago, marksisma_deliri said:

    But shouldn't programs or operating systems have integrity control mechanisms when reading/writing and handle such cases calmly?

    Nope, they don't have. They assume your hardware works correctly.

     

    17 hours ago, marksisma_deliri said:

    Or such mechanisms work only with file system, but not with RAM?

    Neither harddisks nor RAM have such mechanisms by default.

    For RAM you need at least memory modules and mainboard/cpu that support ECC. And that can only correct certain types of errors but not everything.

    For harddisks you need to put up a raid or similar yourself.

     

    I also don't know the exact meanings of the errors, but if memtest prints such errors, your RAM might be broken.

    Link to comment
    Share on other sites

    I replaced the failed memory module. Also i found that the version of libc6 did not match the stable branch, while nvidia-driver, x-server and everything else was from the stable branch. Maybe it was because of some external repository. Anyway, i disabled all external repositories and updated my distribution to testing branch. 4 or 5 days i have no problem running 7dtd.
    How do i close this thread now?

    Link to comment
    Share on other sites



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...