Jump to content

eggbertx

Community Newbie
  • Posts

    4
  • Joined

  • Last visited

Posts posted by eggbertx

  1. Alright, so after running gdb (since the 0ad provided in the Arch package is stripped), in addition to the text in the OP, I get this

    Thread 1 "pyrogenesis" received signal SIGABRT, Aborted.
    0x00007f6b53c988c0 in raise () from /usr/lib/libc.so.6
    (gdb) backtrace
    #0  0x00007f6b53c988c0 in raise () from /usr/lib/libc.so.6
    #1  0x00007f6b53c99f72 in abort () from /usr/lib/libc.so.6
    #2  0x00007f6b035e78a7 in ?? () from /usr/lib/libdbus-1.so.3
    #3  0x00007f6b035de3e7 in _dbus_warn_check_failed () from /usr/lib/libdbus-1.so.3
    #4  0x00007f6b035ce79f in dbus_message_new_method_call () from /usr/lib/libdbus-1.so.3
    #5  0x00007f6b54f0dcd8 in ?? () from /usr/lib/libSDL2-2.0.so.0
    #6  0x00007f6b54f0e020 in ?? () from /usr/lib/libSDL2-2.0.so.0
    #7  0x00007f6b54ef477e in ?? () from /usr/lib/libSDL2-2.0.so.0
    #8  0x00000001002c0605 in InitSDL () at ../../../source/ps/GameSetup/GameSetup.cpp:689
    #9  InitGraphics (args=..., flags=0) at ../../../source/ps/GameSetup/GameSetup.cpp:1012
    #10 0x000000010005c53c in RunGameOrAtlas (argc=<optimized out>, argv=<optimized out>) at ../../../source/main.cpp:578
    #11 0x000000010004d197 in main (argc=1, argv=0x7fffffffe518) at ../../../source/main.cpp:623

    I followed the backtrace, and the last function in 0 AD's source that it calls before the backtrace goes to libSDL2 is SDL_StopTextInput(). I'm not sure how much help that is.

  2. I'm not sure why I didn't think to try this before, but I decided to create a new user to try to run it there, and it works.

     

    Also, on a hunch I logged out of XFCE, stopped the lightdm service, and started the X server with "startxfce4" in my ~/.xinitrc, and it worked, so it might have something to do with lightdm.

     

    Update: Ok, so I tried it with SDDM, and it still won't start. I'm going to try to build it from source and use gdm to see if I can find some useful information.

    • Like 1
  3. I tried to start 0 AD, but nothing showed up. When I ran it in the terminal, I got this:

    Cache: 400 (total: 15978) MiB
    TIMER| InitVfs: 1.08514 ms
    TIMER| CONFIG_Init: 961.83 us
    Sound: AlcInit success, using OpenAL Soft
    TIMER| shutdown ConfigDB: 1.54 us
    TIMER| resource modules: 1.69955 ms
    TIMER TOTALS (9 clients)
    -----------------------------------------------------
      tc_png_decode: 0 c (0x)
      tc_dds_transform: 0 c (0x)
      tc_pool_alloc: 71.143 kc (3x)
      tc_transform: 0 c (0x)
      tc_plain_transform: 0 c (0x)
      tc_ShaderGLSLLink: 0 c (0x)
      tc_ShaderGLSLCompile: 0 c (0x)
      tc_ShaderValidation: 0 c (0x)
      xml_validation: 0 c (0x)
    -----------------------------------------------------
    TIMER| shutdown misc: 299.19 us
    Cache: 400 (total: 15978) MiB
    TIMER| InitVfs: 88.8623 ms
    TIMER| CONFIG_Init: 999.77 us
    Sound: AlcInit success, using OpenAL Soft
    process 17349: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1371.
    This is normally a bug in some application using the D-Bus library.
      D-Bus not built with -rdynamic so unable to print a backtrace
    /usr/bin/0ad: line 9: 17349 Aborted                 (core dumped) "$pyrogenesis" "$@"

    This happened when I used the 0ad package in the official repository, so I decided to download and built the source myself, but I had the same issue there. Has anyone else had this issue? Should I just file a bug report?

×
×
  • Create New...