bugmenot

Ok, what is the status of this bug ? Trying to run the game from a non-writable directory gives me this output: korn@ubuntu:/usr/share/games/0ad/system$ ./pyrogenesis_dbg mkdir failed with errno=13 vfs_lookup.cpp(86): Assertion failed: "0" udbg_bfd_init: loading symbols from /usr/share/games/0ad/system/pyrogenesis_dbg. debug.cpp(216): Unable to open crashlog.txt for writing (please ensure the log directory is writable) Unable to open crashlog.txt for writing (please ensure the log directory is writable) Location: debug.cpp:216 (debug_WriteCrashlog) Call stack: (0x6c5c1e) none:0 std::vector<CacheRelations::SharedCache, std::allocator<CacheRelations::SharedCache> >::_M_insert_aux(__gnu_cxx::__normal_iterator<CacheRelations::SharedCache*, std::vector<CacheRelations::SharedCache, std::allocator<CacheRelations::SharedCache> > >, CacheRelations::SharedCache const&) (0x699afb) none:0 std::list<CInput::SRow, std::allocator<CInput::SRow> >::insert(std::_List_iterator<CInput::SRow>, CInput::SRow const&) (0x69a1ea) none:0 std::list<CInput::SRow, std::allocator<CInput::SRow> >::insert(std::_List_iterator<CInput::SRow>, CInput::SRow const&) (0x69a02b) none:0 std::list<CInput::SRow, std::allocator<CInput::SRow> >::insert(std::_List_iterator<CInput::SRow>, CInput::SRow const&) (0x69a1f5) none:0 std::list<CInput::SRow, std::allocator<CInput::SRow> >::insert(std::_List_iterator<CInput::SRow>, CInput::SRow const&) (0x69a382) none:0 std::list<CInput::SRow, std::allocator<CInput::SRow> >::insert(std::_List_iterator<CInput::SRow>, CInput::SRow const&) (0x6ae4a2) none:0 std::vector<VfsFile const*, std::allocator<VfsFile const*> >::~vector() (0x6a76ca) none:0 FileInfo* std::__uninitialized_copy_a<FileInfo*, FileInfo*, FileInfo>(FileInfo*, FileInfo*, FileInfo*, std::allocator<FileInfo>&) (0x4e6791) none:0 std::_Rb_tree<CStrW, std::pair<CStrW const, long>, std::_Select1st<std::pair<CStrW const, long> >, std::less<CStrW>, std::allocator<std::pair<CStrW const, long> > >::_M_insert_unique_(std::_Rb_tree_const_iterator<std::pair<CStrW const, long> >, std::pair<CStrW const, long> const&) (0x4e7f4a) none:0 std::_Rb_tree<CStrW, std::pair<CStrW const, long>, std::_Select1st<std::pair<CStrW const, long> >, std::less<CStrW>, std::allocator<std::pair<CStrW const, long> > >::_M_insert_unique_(std::_Rb_tree_const_iterator<std::pair<CStrW const, long> >, std::pair<CStrW const, long> const&) (0x43e6ae) none:0 _start (0x7f0d36590abd) /lib/libc.so.6:0 __libc_start_main (0x43d7d9) none:0 _start errno = 0 (?) OS error = ? (C)ontinue, (B)reak, Launch (D)ebugger, or (E)xit? These are my build instructions: cd libraries/fcollada/src && $(MAKE) cd build/workspaces; \ ./update-workspaces.sh; \ cd gcc; \ $(MAKE)

Hello, I have created a debian package for ubuntu and published on playdeb. http://www.playdeb.net/updates/#0 A.D. Before the first start of the game the entire game data and binaries are copied to the user's home directory and the game is then started from there. The usual approach for games (as far as I can tell) is that the game is able to be started from a non-writable directory and all files that have to be written are stored in the $HOME/.config/GAMENAME directory. Also mods can be installed by putting them in this directory.