Closed RossComputerGuy closed 5 years ago
Executing from openstego (not within the /lib folder) worked fine for me:
java -jar lib/openstego.jar
or
java -jar <absolute path>/openstego/lib/openstego.jar
I'm using the AUR package.
@SpaceboyRoss01 not sure what is AUR package, but looks like that the package is incorrectly built. Can you check if openstego.jar file is there, and if so extract the contents using any zip utility and check if following file exists: com/openstego/desktop/resource/openstego.ini
https://aur.archlinux.org/packages/openstego/ this is what I'm using because I'm using Arch and I don't know where the jar is located
@MrCode97 I don't know where the lib directory for openstego is.
I found out openstego is located at /usr/share/java/openstego/openstego.jar but running it still causes a NullPointerException.02.12.2018, 20:39, "SpaceboyRoss01" notifications@github.com:@MrCode97 I don't know where the lib directory for openstego is.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
I saw that in that package the openstego.sh is having following line:
java -jar "/usr/share/java/openstego/openstego.jar" "$@"
It seems to be okay. Did you try running openstego using "openstego.sh" script?
Yes--Sent from Yandex.Mail for mobile08.12.2018, 02:27, "Samir Vaidya" notifications@github.com:I saw that in that package the openstego.sh is having following line: java -jar "/usr/share/java/openstego/openstego.jar" "$@" It seems to be okay. Did you try running openstego using "openstego.sh" script?
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.
Can you try downloading zip version directly from github releases, and try that instead of using ArchLinux package?
it does the same thing.
Thanks, I am able to reproduce it. The issue happens only first time you launch OpenStego. It fails with NPE, but it still creates "openstego.ini" file in the user's home folder, and next launch onwards it works fine. I'll fix this with next release.
Fixed in master branch. Will be part of next release.
I just installed it