Bug 1497483

Summary: 0ad crashes on launch in fedora 27
Product: [Fedora] Fedora Reporter: Bill <thetaeridanus>
Component: 0adAssignee: Paulo Andrade <paulo.cesar.pereira.de.andrade>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 27CC: bioinfornatics, cheese, ignatenko, paulo.cesar.pereira.de.andrade, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-01 07:47:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bill 2017-09-30 22:59:28 UTC
Description of problem: 0ad fails on launch.


Version-Release number of selected component (if applicable): 0.0.22-2.fc27


How reproducible: Attempt to launch 0ad from either gui or command line.


Steps to Reproduce:

1. After upgrade from F26 to F27 (pre beta). 0ad crashes on launch. 


Actual results:


0ad
Cache: 400 (total: 15950) MiB
TIMER| InitVfs: 3.33281 ms
TIMER| CONFIG_Init: 1.62114 ms
Sound: AlcInit success, using OpenAL Soft
TIMER| shutdown ConfigDB: 0.411 us
AL lib: (WW) FreeContext: (0x24fdec0) Deleting 64 Sources
TIMER| resource modules: 501.241 ms
TIMER TOTALS (9 clients)
-----------------------------------------------------
  tc_dds_transform: 0 c (0x)
  tc_png_decode: 0 c (0x)
  tc_pool_alloc: 54.384 kc (3x)
  tc_transform: 0 c (0x)
  tc_plain_transform: 0 c (0x)
  tc_ShaderValidation: 0 c (0x)
  tc_ShaderGLSLLink: 0 c (0x)
  tc_ShaderGLSLCompile: 0 c (0x)
  xml_validation: 0 c (0x)
-----------------------------------------------------
TIMER| shutdown misc: 423.583 us
Cache: 400 (total: 15950) MiB
TIMER| InitVfs: 91.9652 ms
TIMER| CONFIG_Init: 912.456 us
Sound: AlcInit success, using OpenAL Soft
dbus[4990]: arguments to dbus_type_is_basic() were incorrect, assertion "dbus_type_is_valid (typecode) || typecode == DBUS_TYPE_INVALID" failed in file ../../dbus/dbus-signature.c line 323.
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 4:  4990 Aborted                 (core dumped) LD_LIBRARY_PATH=/usr/lib64/0ad /usr/bin/pyrogenesis "$@"

Comment 1 Igor Gnatenko 2017-10-01 07:47:05 UTC
Unfortunately, we've got latest SDL2 and it seems to break things.. Hopefully upstream resolves issue ASAP.

*** This bug has been marked as a duplicate of bug 1496895 ***