After upgrading from ubuntu-14.04LTS to 15.04 I get this error:
$./bin/x64/factorio
0.017 2015-10-25 16:21:04; Factorio 0.12.13 (Build 17141, linux64)
0.017 Operating system: Linux
0.017 Program arguments: "./bin/x64/factorio"
0.017 Read data path: /home/hedin/Downloads/factorio/factorio-12.6/data
0.017 Write data path: /home/hedin/Downloads/factorio/factorio-12.6
0.017 Binaries path: /home/hedin/Downloads/factorio/factorio-12.6/bin
0.118 Available display adapters: 2
0.118 [0]: resolution 1920x1200px at [1920,0]
0.118 [1]: resolution 1920x1200px at [0,0]
0.118 Create display on adapter 0. Size 1280x720 at position [310, 222]. Monitor 0
*** Error in `./bin/x64/factorio': free(): invalid pointer: 0x00007f916eedaf00 ***
Factorio crashed. Generating symbolized stacktrace, please wait ...
#0 0x7f9172c8c2f0 in ?? at ??:0
#1 0x7f9172c8c267 in ?? at ??:0
#2 0x7f9172c8deca in ?? at ??:0
#3 0x7f9172ccfc53 in ?? at ??:0
#4 0x7f9172cd7c69 in ?? at ??:0
#5 0x7f9172cdb89c in ?? at ??:0
#6 0x7f916ec3df42 in ?? at ??:0
#7 0x7f916ec3e3a3 in ?? at ??:0
#8 0x7f916ec3f315 in ?? at ??:0
#9 0x7f91747a236b in ?? at ??:0
#10 0x7f916ec3f361 in ?? at ??:0
#11 0x7f916ec3f3a3 in ?? at ??:0
#12 0x7f916ec3c1a4 in ?? at ??:0
#13 0x7f9170e76b14 in ?? at ??:0
#14 0x7f9170e9dac2 in ?? at ??:0
0.622 Error Util.cpp:61: Unexpected error occurred. You can help us to solve the problem by posting the contents of the log file on the Factorio forums.
ubuntu-15.04 error
-
- Manual Inserter
- Posts: 2
- Joined: Sun Oct 25, 2015 4:25 pm
- Contact:
Re: ubuntu-15.04 error
https://forums.factorio.com/forum/vie ... =7&t=17261Ejdesgaard wrote:After upgrading from ubuntu-14.04LTS to 15.04 I get this error:
Automatic Belt (and pipe) Planner—Automate yet another aspect of constructing your factory!
Re: ubuntu-15.04 error
Moved from Technical Help to Bug Reports ‹ Duplicates.
For more details see the thread prg linked. As this error only occurs in the current 0.12.13, a workaround is to revert back to 0.12.12 for now.
For more details see the thread prg linked. As this error only occurs in the current 0.12.13, a workaround is to revert back to 0.12.12 for now.