[12.10] Won´t start [false alarm, sorry]

[Goury]

Code: Select all

~/proprietary/factorio 12.10/bin/x64$ ./factorio 
   0.000 2015-10-04 02:03:24; Factorio 0.12.10 (Build 17003, linux64)
   0.000 Operating system: Linux
   0.000 Program arguments: "./factorio" 
   0.000 Read data path: /home/goury/proprietary/factorio/data
   0.000 Write data path: /home/goury/proprietary/factorio
   0.000 Binaries path: /home/goury/proprietary/factorio/bin
   0.029 Available display adapters: 1
   0.030  [0]: resolution 1920x1080px at [0,0]
   0.030 Create display on adapter 0. Size 1280x720 at position [310, 162]. Monitor 0
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  154 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  23
  Current serial number in output stream:  24

Code: Select all

~/proprietary/factorio 12.10/bin/x64$ cat ../../factorio-current.log 
   0.000 2015-10-04 02:10:09; Factorio 0.12.10 (Build 17003, linux64)
   0.000 Operating system: Linux
   0.000 Program arguments: "./factorio" 
   0.000 Read data path: /home/goury/proprietary/factorio 12.10/data
   0.000 Write data path: /home/goury/proprietary/factorio 12.10
   0.000 Binaries path: /home/goury/proprietary/factorio 12.10/bin
   0.029 Available display adapters: 1
   0.029  [0]: resolution 1920x1080px at [0,0]
   0.029 Create display on adapter 0. Size 1280x720 at position [310, 162]. Monitor 0
 140.256 Received SIGINT, shutting down

Clean 12.10 tarball
WIndow is created but nothing happens in that window
Evening is almost ruined but all is not lost thanks to my cute wife

UPD: resetted Nvidia driver config and restarted window server and everything seems fine now.

[Oxyd]

Well, that's certainly interesting. What graphics card and what drivers do you have?

[Goury]

Well, that's certainly interesting. What graphics card and what drivers do you have?

GTX 770 with proprietary 346.96
It appears so it was Nvidia driver bug, resetting its config and restarting window server fixed the problem