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
#!python
Note: Failed to read JSON from PyLNP.user, ignoring data - error details follow
Traceback (most recent call last):
File "/home/michael/Desktop/df/python_lnp/build/lnp/out00-PYZ.pyz/core.json_config", line 26, in __init__
IOError: [Errno 2] No such file or directory: u'PyLNP.user'
"The path in the stack trace simply comes from the directory the build took place in; it has nothing to do with the file being accessed.
This particular file stores user settings; if this is your first time running the launcher, the message is expected, since you don't have any such settings. (In the event that you did have settings, this message would let you know they couldn't be read, and therefore they weren't applied.)
The message is completely harmless and the program will work just fine without the file. I'll likely change the error message in the near future to give a better message in the case where the file doesn't exist, though."-- Pidgeot
Thanks again.
The text was updated successfully, but these errors were encountered:
Issue is noted here: Lazy-Newb-Pack/Lazy-Newb-Pack-Linux#6
Found running on Fedora 20.
[Issue created by beaubouchard: 2014-11-12]
[Comment created by beaubouchard: 2014-11-12]
explained Lazy-Newb-Pack/Lazy-Newb-Pack-Linux#6 (comment)
"The path in the stack trace simply comes from the directory the build took place in; it has nothing to do with the file being accessed.
This particular file stores user settings; if this is your first time running the launcher, the message is expected, since you don't have any such settings. (In the event that you did have settings, this message would let you know they couldn't be read, and therefore they weren't applied.)
The message is completely harmless and the program will work just fine without the file. I'll likely change the error message in the near future to give a better message in the case where the file doesn't exist, though."-- Pidgeot
Thanks again.
The text was updated successfully, but these errors were encountered: