You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the notification that an update was available, I accepted and this is what showed up in the terminal.
"Cannot open assembly '/mnt/bc1/Program': No such file or directory."
The full path should be:
"/mnt/bc1/Program Files/steam_linux/steamapps/common/Kerbal Space Program"
I waited for a moment, then freaked out and decided to hit ctrl+c in case any shenanigans may have been happening related to sub folders and recursion (to minimize potential damage).
A quick glance at my drive shows all appears to be well.
I ran ckan again, and it just loaded normally, and seems to be updated - 1.10.0-0gb447380
If that was just some debug-style output and the software resolved the problem, I think it should say so.
4.0.4-2-ARCH #1 SMP PREEMPT Fri May 22 03:05:23 UTC 2015 x86_64 GNU/Linux
Mono JIT compiler version 4.0.1
The mount in question is an NTFS partition.
The text was updated successfully, but these errors were encountered:
At the notification that an update was available, I accepted and this is what showed up in the terminal.
"Cannot open assembly '/mnt/bc1/Program': No such file or directory."
The full path should be:
"/mnt/bc1/Program Files/steam_linux/steamapps/common/Kerbal Space Program"
I waited for a moment, then freaked out and decided to hit ctrl+c in case any shenanigans may have been happening related to sub folders and recursion (to minimize potential damage).
A quick glance at my drive shows all appears to be well.
I ran ckan again, and it just loaded normally, and seems to be updated - 1.10.0-0gb447380
If that was just some debug-style output and the software resolved the problem, I think it should say so.
4.0.4-2-ARCH #1 SMP PREEMPT Fri May 22 03:05:23 UTC 2015 x86_64 GNU/Linux
Mono JIT compiler version 4.0.1
The mount in question is an NTFS partition.
The text was updated successfully, but these errors were encountered: