[RESOLVED?] Game cannot start (Ubuntu 12.04 LTS)

[buro9]

Experienced with the Ubuntu repo version, also experienced with the Wildfire repo version.

Error message:

Cache: 500 (total: 196096) MiB
TIMER| InitVfs: 341.944 us
Sound: AlcInit success, using PulseAudio Default
dir_watch_inotify.cpp(210): Function call failed: return value was -1 (Function failed (no details available))
Function call failed: return value was -1 (Function failed (no details available))
Location: dir_watch_inotify.cpp:210 (dir_watch_Add)
Call stack:
(0x85ccda) /usr/games/pyrogenesis() [0x85ccda]
(0x816001) /usr/games/pyrogenesis() [0x816001]
(0x816cde) /usr/games/pyrogenesis() [0x816cde]
(0x8164d9) /usr/games/pyrogenesis() [0x8164d9]
(0x85ec64) /usr/games/pyrogenesis() [0x85ec64]
(0x87bb3d) /usr/games/pyrogenesis() [0x87bb3d]
(0x877120) /usr/games/pyrogenesis() [0x877120]
(0x82f548) /usr/games/pyrogenesis() [0x82f548]
(0x56b9a9) /usr/games/pyrogenesis() [0x56b9a9]
(0x5d4ad4) /usr/games/pyrogenesis() [0x5d4ad4]
(0x5c73de) /usr/games/pyrogenesis() [0x5c73de]
(0x41ea6e) /usr/games/pyrogenesis() [0x41ea6e]
(0x414317) /usr/games/pyrogenesis() [0x414317]
(0x7fbb994f076d) /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7fbb994f076d]
(0x41da35) /usr/games/pyrogenesis() [0x41da35]
errno = 0 (?)
OS error = ?

This occurs without ever launching the menu screen, as soon as the "0ad" command is entered.

[Yves]

How do you start the game exactly? Do you use the launcher in Unity or do you run it from the terminal?

I remember an issue with relative paths if you start it the wrong way (don't remember how exactly).

[buro9]

I normally use the launcher in Unity. But I tried the command line `0ad` as per the /usr/share/applications/0ad.desktop file with the same result.

The game hadn't updated in a while, but the Linux kernel and Java both had on the last system update... which are the only updates that I guess could have affected it.

The error screen I get looks like a raw GUI toolkit screen, it's not dressed in the Ubuntu windowing style if that helps at all (I doubt it).

Edited July 28, 2013 by buro9

[historic_bruno]

Can you install the 0ad-debug package to get debug symbols, then try again? That call stack doesn't tell us much yet.

[buro9]

0ad-dbg installed.

Though... it now works. Game launched first time and then on subsequent occasions without issue.

The output is:

Cache: 500 (total: 196096) MiB
TIMER| InitVfs: 326.695 us
Sound: AlcInit success, using PulseAudio Default
TIMER| CONFIG_Init: 64.7512 ms
TIMER| InitScripting: 2.14487 ms
TIMER| RunHardwareDetection: 19.4294 ms
TIMER| write_sys_info: 16.5027 ms
TIMER| InitRenderer: 4.6841 ms
TIMER| ps_console: 1.33423 ms
TIMER| ps_lang_hotkeys: 567.257 us
TIMER| common/setup.xml: 776.837 us
TIMER| common/styles.xml: 52.42 us
TIMER| common/sprite1.xml: 1.73274 ms
TIMER| common/init.xml: 1.46559 ms
TIMER| common/common_sprites.xml: 1.98637 ms
TIMER| common/common_styles.xml: 248.196 us
TIMER| pregame/sprites.xml: 416.573 us
TIMER| pregame/styles.xml: 46.723 us
TIMER| pregame/mainmenu.xml: 5.21289 ms
TIMER| common/global.xml: 385.227 us
Using Xcursor to sys_cursor_create 32 x 32 cursor
TIMER| common/setup.xml: 1.00695 ms
TIMER| common/styles.xml: 42.97 us
TIMER| common/sprite1.xml: 2.63902 ms
TIMER| common/common_sprites.xml: 2.79679 ms
TIMER| common/common_styles.xml: 183.863 us
TIMER| msgbox/msgbox.xml: 719.92 us
TIMER| shutdown TexMan: 7.094 us
TIMER| shutdown Renderer: 15.6559 ms
TIMER| shutdown SDL: 55.7464 ms
TIMER| shutdown UserReporter: 316.31 us
TIMER| shutdown ScriptingHost: 994.49 us
TIMER| shutdown ConfigDB: 0.233 us
TIMER| resource modules: 527.57 ms
TIMER TOTALS (9 clients)
-----------------------------------------------------
  tc_png_decode: 19.4409 Mc (8x)
  tc_pool_alloc: 1191.37 kc (123x)
  tc_dds_transform: 28.311 kc (10x)
  tc_transform: 62.556 kc (4x)
  tc_plain_transform: 23.001 kc (4x)
  tc_ShaderGLSLLink: 0 c (0x)
  tc_ShaderGLSLCompile: 0 c (0x)
  tc_ShaderValidation: 1141.47 kc (1x)
  xml_validation: 1053.83 kc (1x)
-----------------------------------------------------
TIMER| shutdown misc: 522.234 us

Removing 0ad-dbg does not make the original issue appear again.

I'll consider it resolved... because it's no longer happening. But I'll also leave the 0ad-dbg symbols installed and should it occur again I'll re-open this conversation and will post whatever the output is at that time.