I'm using the latest Unofficial Linux Lazy Newb Pack (PyLNP 0.12a). Launching startlnp as sudo gives me an exception in Tkinter callback when i try to play, without sudo simply gives me an "gnome-terminal\n no such file or directory"
I attach the stderr file. Pardon my English.
[Issue created by Former user: 2016-09-29]
[Last updated on bitbucket: 2017-06-10]
[Comment created by Gekokeitaro: 2016-10-09]
Great, thx!!
[Comment created by Pidgeot: 2016-10-09]
Safeguard against a few possible errors when spawning Linux terminals (fixes #132)
→ <<cset 9ada1af51d9b>>
[Comment created by Pidgeot: 2016-10-09]
@Gekokeitaro I am not able to reproduce this on my test machines, but I'm adding a few safeguards which will hopefully make the built-in terminal handling work for you.
If it turns out to not help in 0.12b (once that version is out), then please re-run PyLNP with the command-line option -d and attach both stdout.txt and stderr.txt; it will hopefully provide more information in that case.
[Comment created by Gekokeitaro: 2016-09-30]
Fixed! lot of thanks Michael :D
[Comment created by Gekokeitaro: 2016-09-30]
Sorry, i didn't realize that i wasn't logged after create the issue -.-
I tried to run df throw PyLNP 0.12a without dfhack and it worked, also when using old releases of PyLNP that are still using the xdg-terminal file, is there some way to use that file in new releases?
Thx in advance
[Comment created by Pidgeot: 2016-09-30]
If you want to still use xdg-terminal, you can always copy in the script and then use it as a custom command. You can set this up under File > Configure Terminal.
[Comment created by Pidgeot: 2017-06-10]
@PeridexisErrant I need to look at #138 and #140 first, and time hasn't really allowed that to happen yet. They are probably related, and they should be simple enough to code a fix for, but I still need to actually do it.
The good news is that I've got those on the schedule for tonight, but I may need one more day after that to review a few other things. This means that the release should be happening no later than Monday.
[Comment created by PeridexisErrant: 2017-06-10]
@Pidgeot - I've just spent a while tracking down this problem for a Linux user, because while it's fixed in the repo there's no release with this patch. Can you upload a new release?
Hi!
I'm using the latest Unofficial Linux Lazy Newb Pack (PyLNP 0.12a). Launching startlnp as sudo gives me an exception in Tkinter callback when i try to play, without sudo simply gives me an "gnome-terminal\n no such file or directory"
I attach the stderr file. Pardon my English.
[Issue created by Former user: 2016-09-29] [Last updated on bitbucket: 2017-06-10]
[Comment created by Gekokeitaro: 2016-10-09] Great, thx!!
[Comment created by Pidgeot: 2016-10-09] Safeguard against a few possible errors when spawning Linux terminals (fixes #132)
→ <<cset 9ada1af51d9b>>
[Comment created by Pidgeot: 2016-10-09] @Gekokeitaro I am not able to reproduce this on my test machines, but I'm adding a few safeguards which will hopefully make the built-in terminal handling work for you.
If it turns out to not help in 0.12b (once that version is out), then please re-run PyLNP with the command-line option -d and attach both stdout.txt and stderr.txt; it will hopefully provide more information in that case.
[Comment created by Gekokeitaro: 2016-09-30] Fixed! lot of thanks Michael :D
[Comment created by Gekokeitaro: 2016-09-30] Sorry, i didn't realize that i wasn't logged after create the issue -.-
I tried to run df throw PyLNP 0.12a without dfhack and it worked, also when using old releases of PyLNP that are still using the xdg-terminal file, is there some way to use that file in new releases?
Thx in advance
[Comment created by Pidgeot: 2016-09-30] If you want to still use xdg-terminal, you can always copy in the script and then use it as a custom command. You can set this up under File > Configure Terminal.
[Comment created by Pidgeot: 2017-06-10] @PeridexisErrant I need to look at #138 and #140 first, and time hasn't really allowed that to happen yet. They are probably related, and they should be simple enough to code a fix for, but I still need to actually do it.
The good news is that I've got those on the schedule for tonight, but I may need one more day after that to review a few other things. This means that the release should be happening no later than Monday.
[Comment created by PeridexisErrant: 2017-06-10] @Pidgeot - I've just spent a while tracking down this problem for a Linux user, because while it's fixed in the repo there's no release with this patch. Can you upload a new release?