Funny that it doesn't happen again. Perhaps there was some other process
running that confused openttd in some way, or something else was
different in your environment? If you manage to reproduce it again, let
us know. If not, I'll probably close this report soon.
The debug output generated by openttd -d 4 is generated on stderr (not
stdout), so use 2> log.txt to redirect.
** Changed in: openttd (Ubuntu)
Status: New => Incomplete
--
openttd eats all my cpu
https://bugs.launchpad.net/bugs/467179
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
