#2914 closed defect (invalid)
OS stop suddently after a few minutes
| Reported by: | Nicolas Lefebvre | Owned by: | |
|---|---|---|---|
| Priority: | Should Have | Milestone: | |
| Component: | Core engine | Keywords: | |
| Cc: | Patch: |
Description
I'm on ubuntu 14.10
I launch 0ad (version alpha 17) and start a solo/match game with 2 players (me and AI:petra bot level sandbox)
After at least 10 minutes the ubuntu stop screen appear and my computer stops. There is no message before the crash.
I have tried to change graphical parameters but the problem is still here. I can do other tests if it needed.
Attachments (5)
Change History (11)
by , 10 years ago
| Attachment: | system_info.txt added |
|---|
by , 10 years ago
| Attachment: | crashlog.txt added |
|---|
by , 10 years ago
| Attachment: | interestinglog.html added |
|---|
by , 10 years ago
| Attachment: | mainlog.html added |
|---|
by , 10 years ago
| Attachment: | commands.txt added |
|---|
comment:1 by , 9 years ago
| Keywords: | unanswered added |
|---|
comment:2 by , 9 years ago
| Keywords: | unanswered removed |
|---|
comment:3 by , 9 years ago
The "Ubuntu stop screen" is the image shown normally when stopping ubuntu (after cliking on shutdown this screen is shown a few seconds before power down). There is absolutly no message (nothing in logs) as if the stop action was asked in a normal way. I think that it's probably a driver issue but as I never had the problem when 0 A.D. is not running it might be the way that 0 A.D. use the driver. As I have just reinstalled my computer last week I will reinstall 0 A.D. and try to reproduce the bug. I will post a new comment with the result as soon as the test is done.
comment:4 by , 9 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
After a clean reinstal of ubuntu I don't have seen the problem. It's probably a driver issue not related to 0.A.D. I change the resolution of the trac to invalid. Sorry for the error.
What is the "Ubuntu stop screen"? Is there a message, maybe you can take a photo or find it in the logs? If it's actually crashing the OS, that doesn't sound like a 0 A.D. problem, but more likely hardware (overheating?) or driver issues.