On 10/02/2023 03:04, stepore wrote:
> On 2/9/23 00:33, Rob H wrote:
> <nothing at all about features needed - so I'll say again>:
>
>>> I don't know this scanner's feature set or what you need
>>> specifically, but i can't imagine how it's any better than nmap. It
>>> may even be using nmap for scanning. There are some GUI interfaces
>>> for nmap available. And no java dependencies.
>
>
> try nmap. no java dependencies!
>

I tried the said cmd, but got this:

rob@rob-Z97:~$ nmap. no java dependencies!
Command 'nmap.' not found, did you mean:
command 'nmap' from deb nmap (7.91+dfsg1+really7.80+dfsg1-2build1)
Try: sudo apt install <deb name>

I did then install nmap, but still the same error.

Thanks

On 2/10/2023 3:31 AM, Rob H wrote:
> On 10/02/2023 03:07, stepore wrote:
>> On 2/9/23 17:47, Mike Easter wrote:
>>> Paul wrote:
>>>> What sets $JAVA_HOME ?
>>>>
>>>> What if the variable isn't even set ?
>>>>
>>>> Is this a variable that every installer sets ?
>>>
>>> In my experimental live LM 21.1 Cinn, none of the instructions I've
>>> found for 'finding' $JAVA_HOME are giving me any answers; but I know it
>>> must be set/working because when I install the angryip .deb from its
>>> site, then it works properly.
>>>
>>> In the live LM 21.1, there is no 'need' to install or configure the
>>> openjdk first because it is installed by default as indicated earlier.
>>>
>>
>>
>> I'm sure a bunch of stuff can set vars like $JAVA_HOME.
>> But you can check out current environment variable with commands like:
>>
>> env | less
>> set | less
>
> env | less gives my jave path;
>
> JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/jre/
>
> set | less  doesn't show me anything regarding to java, unless I didn't look closely enough
>
> What I can't understand is why I seem to have different java  / jdk version on my mint desktop. Synaptic says I have open JDK11 , but when I use: java -version, it says I have
>
> rob@rob-Z97:~$ java -version
> openjdk version "1.8.0_352"
> OpenJDK Runtime Environment (build 1.8.0_352-8u352-ga-1~22.04-b08)
> OpenJDK 64-Bit Server VM (build 25.352-b08, mixed mode)
>
> Then the JAVA_HOME says I have java 8-openjdk
>
> Confused I  will be!!

Isn't a light bulb coming on yet ?

And remember, I'm just a spectator here. I didn't even
try to reproduce this, because I figured there would
be no way I would get my setup to exactly match yours.

It appears you can install more than one version of Java,
without the others being changed in any way.

However, now, it's up to applications to decide how to
wrap/protect their code against the runtime environment.

You could for example, just hard code the path for openjdk-11
in that script I showed. Then, if that path did not exist,
the program would print the message about needing JDK11.

Alternately, you could define JAVA_HOME in one of your
environment files in ~ that sets up your shell. It should
be obvious now, that the "Java People" did not define this
variable on purpose, because they know to do so, will break
stuff left and right. As in your example, in fact!

This is an example of passing in an environment change.

JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64 angryip

It should be obvious to you by now, that the tiny script
in that package, is the part that sucks. The desired result
for the user, is that the stupid software finds and uses 11.

To repair it at the script level, this line needs to be changed.

java=$JAVA_HOME/bin/java

to something like

java=/usr/lib/jvm/java-11-openjdk-amd64/bin/java

Make a note in your notes file, that you made edits to that file.
The script file will likely be owned by root, so you will
need to elevate the text editor in order to save out
the changed line in the script.

There are several ways to fix this, once you understand
what the "java ecosystem" thinks is a clever idea for
a runtime environment (multiple versions).

Which is the least-disgusting change ? I vote for this approach
(assuming I didn't screw it up). This at least, does not rely on
..profile or rely on making custom changes to the AngryIP package
itself.

JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64 angryip

Paul

On 09-02-2023 04:58, Paul wrote:
> On 2/8/2023 11:40 AM, Rob H wrote:
>> I have been using Angry IP scanner for a number of years with any
>> problems.
>> Very recently I upgraded my Linux Mint to 21.1, and now when I try to
>> run the said program et a popup message saying I need to have
>> Java/OpenJDK11+ to run the program.
>>
>
> Usually, stuff like this is protected with wrappers.
>
> #!/bin/sh
> java=$JAVA_HOME/bin/java
> [ ! -e $java ] && java=java
> $java --add-opens java.base/java.net=ALL-UNNAMED -jar
> /usr/lib*/ipscan/ipscan*.jar "$@"
> [ $? != 0 ] && notify-send "You need Java/OpenJDK 11+ to run ipscan"
>

So, I assume on your system /bin is a soft link to /usr/bin.
Therefore, if you find the place where $JAVA_HOME is defined, DELETE THE
DEFINITION, so $JAVA_HOME does not exist anymore. Hereafter, the
wrapper will work.

stepore wrote:
> I'm sure a bunch of stuff can set vars like $JAVA_HOME.

There are plenty of instructions for /setting/ it, but I'm talking about
/seeing/ it already set, since it is working for angryip.

> But you can check out current environment variable with commands like:
>
> env | less
> set | less

Nope; no JAVA_HOME appears in either of those (in my live Mint 21.1 Cinn
which works w/ angryip). The set result was quite extensive so I used
the /JAVA to see if there was anything JAVA in there.

--
Mike Easter

On 10/02/2023 09:15, Paul wrote:
> On 2/10/2023 3:31 AM, Rob H wrote:
>> On 10/02/2023 03:07, stepore wrote:
>>> On 2/9/23 17:47, Mike Easter wrote:
>>>> Paul wrote:
>>>>> What sets $JAVA_HOME ?
>>>>>
>>>>> What if the variable isn't even set ?
>>>>>
>>>>> Is this a variable that every installer sets ?
>>>>
>>>> In my experimental live LM 21.1 Cinn, none of the instructions I've
>>>> found for 'finding' $JAVA_HOME are giving me any answers; but I know it
>>>> must be set/working because when I install the angryip .deb from its
>>>> site, then it works properly.
>>>>
>>>> In the live LM 21.1, there is no 'need' to install or configure the
>>>> openjdk first because it is installed by default as indicated earlier.
>>>>
>>>
>>>
>>> I'm sure a bunch of stuff can set vars like $JAVA_HOME.
>>> But you can check out current environment variable with commands like:
>>>
>>> env | less
>>> set | less
>>
>> env | less gives my jave path;
>>
>> JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/jre/
>>
>> set | less  doesn't show me anything regarding to java, unless I
>> didn't look closely enough
>>
>> What I can't understand is why I seem to have different java  / jdk
>> version on my mint desktop. Synaptic says I have open JDK11 , but when
>> I use: java -version, it says I have
>>
>> rob@rob-Z97:~$ java -version
>> openjdk version "1.8.0_352"
>> OpenJDK Runtime Environment (build 1.8.0_352-8u352-ga-1~22.04-b08)
>> OpenJDK 64-Bit Server VM (build 25.352-b08, mixed mode)
>>
>> Then the JAVA_HOME says I have java 8-openjdk
>>
>> Confused I  will be!!
>
> Isn't a light bulb coming on yet ?
>
> And remember, I'm just a spectator here. I didn't even
> try to reproduce this, because I figured there would
> be no way I would get my setup to exactly match yours.
>
> It appears you can install more than one version of Java,
> without the others being changed in any way.
>
> However, now, it's up to applications to decide how to
> wrap/protect their code against the runtime environment.
>
> You could for example, just hard code the path for openjdk-11
> in that script I showed. Then, if that path did not exist,
> the program would print the message about needing JDK11.
>
> Alternately, you could define JAVA_HOME in one of your
> environment files in ~ that sets up your shell. It should
> be obvious now, that the "Java People" did not define this
> variable on purpose, because they know to do so, will break
> stuff left and right. As in your example, in fact!
>
> This is an example of passing in an environment change.
>
>    JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64  angryip
>
> It should be obvious to you by now, that the tiny script
> in that package, is the part that sucks. The desired result
> for the user, is that the stupid software finds and uses 11.
>
> To repair it at the script level, this line needs to be changed.
>
>    java=$JAVA_HOME/bin/java
>
> to something like
>
>    java=/usr/lib/jvm/java-11-openjdk-amd64/bin/java
>
> Make a note in your notes file, that you made edits to that file.
> The script file will likely be owned by root, so you will
> need to elevate the text editor in order to save out
> the changed line in the script.
>
> There are several ways to fix this, once you understand
> what the "java ecosystem" thinks is a clever idea for
> a runtime environment (multiple versions).
>
> Which is the least-disgusting change ? I vote for this approach
> (assuming I didn't screw it up). This at least, does not rely on
> .profile or rely on making custom changes to the AngryIP package
> itself.
>
>    JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64  angryip
>
>   Paul

Ok then light bulb was eventually fixed, I think!

In my java path:

rob@rob-Z97:~$ java=/usr/lib/jvm/java-11-openjdk-amd64/bin/java

when I navigate to the said directory, there are 5 entries
java-1.8.0-openjdj-amd64
java-1.11.0-openjdk-amd64
java--8-openjdk-amd64
java-11-openjdk-amd64
openjdk-11

Can I safely remove any of those which are producing the error message
from angry ip

When I do java -version , it still doesn't show openjdk11

I did this as well:
JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64

Thanks

On 10/02/2023 10:10, jjb wrote:
> On 09-02-2023 04:58, Paul wrote:
>> On 2/8/2023 11:40 AM, Rob H wrote:
>>> I have been using Angry IP scanner for a number of years with any
>>> problems.
>>> Very recently I upgraded my Linux Mint to 21.1, and now when I try to
>>> run the said program et a popup message saying I need to have
>>> Java/OpenJDK11+ to run the program.
>>>
>>
>> Usually, stuff like this is protected with wrappers.
>>
>> #!/bin/sh
>> java=$JAVA_HOME/bin/java
>> [ ! -e $java ] && java=java
>> $java --add-opens java.base/java.net=ALL-UNNAMED -jar
>> /usr/lib*/ipscan/ipscan*.jar "$@"
>> [ $? != 0 ] && notify-send "You need Java/OpenJDK 11+ to run ipscan"
>>
>
> So, I assume on your system /bin is a soft link to /usr/bin.
> Therefore, if you find the place where $JAVA_HOME is defined, DELETE THE
> DEFINITION, so $JAVA_HOME does not exist anymore.  Hereafter, the
> wrapper will work.
>
>
I changed the java path to this

java=/usr/lib/jvm/java-11-openjdk-amd64/bin/java

But I still get this

java -version
openjdk version "1.8.0_352"
OpenJDK Runtime Environment (build 1.8.0_352-8u352-ga-1~22.04-b08)
OpenJDK 64-Bit Server VM (build 25.352-b08, mixed mode)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-02-10, Mike Easter wrote:
> stepore wrote:
>> I'm sure a bunch of stuff can set vars like $JAVA_HOME.
>
> There are plenty of instructions for /setting/ it, but I'm talking about
> /seeing/ it already set, since it is working for angryip.

If the full JDK is installed:
echo "$JAVA_HOME"
env | grep JAVA

If only the JRE is installed:
echo "$JRE_HOME"
env | grep JRE

Note, that it is my understanding that these envvars are UNSET by
default; and are mainly used by tools external to Java itself (e.g.
tomcat) so that they can find the java compiler, etc. May or may not
actually come into play for this IP scanner.

Also, as Linux Mint is a derivative of Debian, /usr/bin/java will be a
symlink to /etc/alternatives/java (which in turn is a symlink to
/usr/.../java_x.x.x/bin/java).

A mismatched "alternative" is a very good candidate for why this is
being seen -- easiest fix is the command
sudo update-alternatives java

and choosing version 11 instead of 1.8

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPmRD4ACgkQbWVw5Uzn
KGBG2g//WPg3h3M2nKWDWDcTxrd+srNGI50Y6/Xr5i1OnDGji5mgIgpF7mRzDm5T
2GkyO/L33ERHU+cNPInyrxb/0DaUNsfsp8aF/Zlk3eQHzz6tgVmzQi6onscuZOuO
lVroWSVo+Z19lSajQ1plMSihgmNAQ2U8SBLsH9ZPtHHlchdJ54x4j8K/rrqTZ3hj
/cB9mPOW2EvvQ1D39fjPDifXQmfhnEx+MdGJmUiai9q2EnoK6XCZOVQI9GGh+//6
Yd0KdavDo6o1P7j5TNlR7ApgNVzZvHG3WX0h9QnuqNUOWNgLVrwUpSoO6zQbjuGR
fMQeQXLvMEZAW0DFQN0DMBlxn7RXgTLIJtoNcImzOZ/TDgYYJC+4dwX/Ochx1+cC
SjECjFrX43KWyJDZuQ1qoPLMTBY0i6tsALo+eClwWmz624yvBcq/EhWc5aqlP2S6
V5jlTa6P4nfxoElHiT2xZa44pTwLAXEntKE0mjfgEy3/JhDteM0HO1FpJli4d85F
+/3YVB3Ozfv1btGYiks5C/tyW9ihO63u6nmFp0TFK7JLqReP6N+KqoRMwwRGXm/Z
UyLI5QSzLJCYXzj3ixYx0Pshy+k1YgRnPyNxwajjme/952mOn/RU3C3Apy1SmmPS
d8Cu8c5XNhEOomExICA3t1+uOrUF9/yQDbglGXYhB1VmqNhrzQM=
=oz/m
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-02-10, Rob H wrote:
> On 10/02/2023 03:04, stepore wrote:
>> On 2/9/23 00:33, Rob H wrote:
>> <nothing at all about features needed - so I'll say again>:
>>
>>>> I don't know this scanner's feature set or what you need
>>>> specifically, but i can't imagine how it's any better than nmap. It
>>>> may even be using nmap for scanning. There are some GUI interfaces
>>>> for nmap available. And no java dependencies.
>>
>>
>> try nmap. no java dependencies!
>>
>
> I tried the said cmd, but got this:
>
> rob@rob-Z97:~$ nmap. no java dependencies!
> Command 'nmap.' not found, did you mean:
> command 'nmap' from deb nmap (7.91+dfsg1+really7.80+dfsg1-2build1)
> Try: sudo apt install <deb name>
>
>
> I did then install nmap, but still the same error.
>
> Thanks

the command is 'nmap'; not 'nmap. no java dependencies!'

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPmRG8ACgkQbWVw5Uzn
KGDn6A//dELjy3h+yWb870GY8CHAc2c7Qtuh1G6QKtRYYb1qLjV4W2URCacs8gn+
DnN3pc9TgKiYyjrdwIVca3NeuY8OB64M1lt+rKF7r5whRe8q0Waivu042/5OgUAv
JAele5xRtEEw2j9RdOfGYj7ubqVBi0RsJ1y3U6uxsA9v6tw6Cvc5OLE+R1v+ER1h
/wXwwS0bVyhogVhO3Y6MBd/UfmhrcXtWwx+oH6VaFjVm78Iqqc4oqYePtBtyW9u9
gtriMSX1ZCUYd46VAS35MeDpTv4cUIKg1sfEiFCezazDTpk7NNoNQEWNzoK2kTmt
KQ/UBxsfLjuWd0fzPmxcEPfHDFotk7c8nk9c4VZpYMlKk6l57nMNJz9wKS5okqWS
/YSDPY5TRc46LQjibjhaVRDIBMcIgaBgbMsMnmQcPNuw4sy8htEzQZtOKqzomaoC
wSsedIwIBNrjuNNhtwN36WazAXp571ak6150qBmnhYK7HXDvDmC8HCtCqENvVYJ4
MMij7/ExHr7xmH71AK/K7iYNLleyBzhjEkwolHsLPvN94Wa7dlu8tji96DAHF/qX
ilUAKKrgjGWf2ZqruIOrBtGWL7MrlL7ozSmTP4j4hPcHET7zH+Ll0pkZwLlBrKJI
EMVk5iGT9EnTX0nRyUmFwRmGMYaeqz5tw/7mQm6y6Kor8ta311U=
=pOws
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

Dan Purgert wrote:
> Note, that it is my understanding that these envvars are UNSET by
> default; and are mainly used by tools external to Java itself (e.g.
> tomcat) so that they can find the java compiler, etc. May or may not
> actually come into play for this IP scanner.
>
Ah, so. I see. Maybe I can theorize that while the scanner may have
code that *looks for* JAVA_HOME, it doesn't /have to/ have that set...
BUT, (if so) the environment CAN NOT include /misleading/ (such as for
old java) info about java, which is apparently RH's case.
>
> Also, as Linux Mint is a derivative of Debian, /usr/bin/java will be a
> symlink to /etc/alternatives/java (which in turn is a symlink to
> /usr/.../java_x.x.x/bin/java).

Yes; I chased around a lot of symlinks trying to find something that
held JAVA_HOME because of what people had said in web forums about
finding that.

Again, in live LM 21.1 Cinn default mode before or after angryip is
installed:

$ java -version
openjdk version "11.0.17" 2022-10-18
OpenJDK Runtime Environment (build 11.0.17+8-post-Ubuntu-1ubuntu222.04)
OpenJDK 64-Bit Server VM (build 11.0.17+8-post-Ubuntu-1ubuntu222.04,
mixed mode, sharing)

Nowhere to be found in that live is JAVA_HOME.

--
Mike Easter

On 10/02/2023 13:17, Dan Purgert wrote:
> On 2023-02-10, Mike Easter wrote:
>> stepore wrote:
>>> I'm sure a bunch of stuff can set vars like $JAVA_HOME.
>
>> There are plenty of instructions for /setting/ it, but I'm talking about
>> /seeing/ it already set, since it is working for angryip.
>
> If the full JDK is installed:
> echo "$JAVA_HOME"
> env | grep JAVA
>
> If only the JRE is installed:
> echo "$JRE_HOME"
> env | grep JRE
>
> Note, that it is my understanding that these envvars are UNSET by
> default; and are mainly used by tools external to Java itself (e.g.
> tomcat) so that they can find the java compiler, etc. May or may not
> actually come into play for this IP scanner.
>
>
> Also, as Linux Mint is a derivative of Debian, /usr/bin/java will be a
> symlink to /etc/alternatives/java (which in turn is a symlink to
> /usr/.../java_x.x.x/bin/java).
>
> A mismatched "alternative" is a very good candidate for why this is
> being seen -- easiest fix is the command
> sudo update-alternatives java
>
> and choosing version 11 instead of 1.8
>
>
>

rob@rob-Z97:~$ echo "$JAVA_HOME"
/usr/lib/jvm/java-8-openjdk-amd64/jre/
rob@rob-Z97:~$ env | grep JAVA
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/jre/
rob@rob-Z97:~$

rob@rob-Z97:~$ sudo update-alternatives java
[sudo] password for rob:
update-alternatives: error: unknown argument 'java'

rob@rob-Z97:~$ sudo update-alternatives --display java
java - manual mode
link best version is /usr/lib/jvm/java-11-openjdk-amd64/bin/java
link currently points to /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
link java is /usr/bin/java
slave java.1.gz is /usr/share/man/man1/java.1.gz
/usr/lib/jvm/java-11-openjdk-amd64/bin/java - priority 1111
slave java.1.gz: /usr/lib/jvm/java-11-openjdk-amd64/man/man1/java.1.gz
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java - priority 1081
slave java.1.gz: /usr/lib/jvm/java-8-openjdk-amd64/jre/man/man1/java.1.gz

As the current link points to java-8-openjdk-amd64
how do I change it so it points java-11-openjdk-amd64

Thanks

Rob H wrote:
> rob@rob-Z97:~$ sudo update-alternatives java

I think that is supposed to be

sudo update-alternatives --config java

and then you get a list displayed to choose.

--
Mike Easter

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-02-10, Mike Easter wrote:
> Dan Purgert wrote:
>> Note, that it is my understanding that these envvars are UNSET by
>> default; and are mainly used by tools external to Java itself (e.g.
>> tomcat) so that they can find the java compiler, etc. May or may not
>> actually come into play for this IP scanner.
>>
> Ah, so. I see. Maybe I can theorize that while the scanner may have
> code that *looks for* JAVA_HOME, it doesn't /have to/ have that set...
> BUT, (if so) the environment CAN NOT include /misleading/ (such as for
> old java) info about java, which is apparently RH's case.

No, the issue here is that there are multiple versions of Java installed
(inclusive of 1.8) and when invoking "java" from the terminal, "java
1.8" is the binary that is executed.

The corrective action is running "sudo update-alternatives java" and
ensuring that the system is linking the correct binary (i.e. java11 or
better) when the user invokes "java" from the command line.

>>
>> Also, as Linux Mint is a derivative of Debian, /usr/bin/java will be a
>> symlink to /etc/alternatives/java (which in turn is a symlink to
>> /usr/.../java_x.x.x/bin/java).
>
> Yes; I chased around a lot of symlinks trying to find something that
> held JAVA_HOME because of what people had said in web forums about
> finding that.

You seem to have misinterpreted what I was actually saying here. No
symbolic link on the filesystem will contain any information about the
environment variable $JAVA_HOME (or $JRE_HOME). If necessary, those
environment variables will be set (and exported by) either the global
/etc/profile ; or a user's personalized ~/.profile and or shell-specific
dotfiles (such as ~/.bashrc).

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPmfXkACgkQbWVw5Uzn
KGCnyQ//bMpW0gyXLY1X2cmRYEdBnmPayS9mScL4em/8LfXck5AuqLGtqqF3n5DI
6K+dP6v64YAfnjkEio3Jij61alDGC7plEoQU3EC7kSj/dlEcF0rhaTjf56a4dskT
KpfuDURyEId0oIVm4qAFe3Elas/sQV1cOPwU8qOdA7jBw4JkCx10hEn/rv6Ht2E9
uHpueW/xxiJRUmdxoH+RdH8GpbT4FoJZ67ZnJd/NLi8veKjKjJy2XJkAchZev8/t
3bvkGrs3KdDiYTGrhl3sN+DGNewbzvwsZU7R033f7V67jH2arK2jSJg2rlcnzlw2
dzHomhrrCsPEo7UA+PD5RFalrmHLVIosIlj9vbq9PbR1jFKjMd2GS5AsyUf34ehQ
Y+5D4fYKKStviWQzlEBJzj+c598epfAqIlPmUoV8xfv3qXhdKndFsCd/VGhROVI9
hTAyk98qTkIpZPrcd6uht6C/cWFInLpOg7PjucUup6nlfaKHPRR2gDaoG8iQGI/o
T5hQ0l/O2aS/5d/CtbgT6hcPMU9miRA85PBLVj2eMJB7NvqjpOrcmP6W9V4e+1wC
DcNToM5z/FiZECDgNNGvHhZE9vJvyKy8l0j6FhxY9F2ye6D0m7GzwUzrZVLrTN0N
hsVGPjFrDR5bz8L3YGrMOtfaGdgA2eFYjDE9F1rK3CuJwCRQHGw=
=oheF
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-02-10, Rob H wrote:
> On 10/02/2023 13:17, Dan Purgert wrote:
>> [...]
>> A mismatched "alternative" is a very good candidate for why this is
>> being seen -- easiest fix is the command
>> sudo update-alternatives java
>>
>> and choosing version 11 instead of 1.8
>>
>>
>>
>
> [...]
>
> rob@rob-Z97:~$ sudo update-alternatives java
> [sudo] password for rob:
> update-alternatives: error: unknown argument 'java'

Oops, it's
sudo update-alternatives --config java

Sorry about that :/

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPmffgACgkQbWVw5Uzn
KGAXaA//cpxZeq5ZAGD5oZM49mf7KEqJ6/y/9TxllIO5dpDqy5MfgBJfgDcUuLzg
6q9r2yT0t6FsHK0bxM6Jn3zJY0VoIuLYDpFyQg4K+ukFwPb5usWNkPMOeBqVP9gt
MxANV4B7NkzpAvnwcajH6khGtnQ+W/gSmvsmGYN1H66/fHUsbdECTkt+yFwt56Jp
Ntq/IcHsB479rLyCJJWYMZGfp/qJAO411HG+MPQrxYbIw3deGy/ZwF5wmn3dKZAY
ao8UqFQmLxkdXpHYLquosOurRlQKerSNWKPVKEQuVg09L4eYyUVqOpTElhMDpCPy
WDu/WLsP1QuplxxM3f4lj+P+BaSydaHBv9uoAv58RxQVjuQ0B6qGXhGRIEc8bRfh
qPh9PXddwDstHHQHyKnycCkpNDeKU0dCf5HEnLXl4IOo8DvP6FRdGoWIVN4rdbb5
K0cuP7duS4q2Gzxu9gj19swFwz33FUJ/xYlavcQU52Iz0KYql7ydJv25yGzDlzxY
rs8uiTFCYzzSOAVqlKAYNUUOO1+ZP9thCO7idUeqBHZEeZoLQPcT2shqGKf59yww
Ek4uLN2wnEhKKGd7FwKPK0MRjlFGV/tRak3RdBBpYh+1LSRyKHUfjZ1pS9z6RFir
OUMPrNhRvjWT3AnPqtJfbKZoUGgHcG/SVw7PvXPjlL6Y/eTruHY=
=xlrC
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

Dan Purgert wrote:
> If necessary, those
> environment variables will be set (and exported by) either the global
> /etc/profile ; or a user's personalized ~/.profile and or shell-specific
> dotfiles (such as ~/.bashrc).

I chased the symlinks because there was no profile or anything java in
the bashrc.

But you are correct that the chase led me nowhere except a LOT of
symlinks referring to other symlinks.

--
Mike Easter

On 10/02/2023 17:24, Dan Purgert wrote:
> On 2023-02-10, Rob H wrote:
>> On 10/02/2023 13:17, Dan Purgert wrote:
>>> [...]
>>> A mismatched "alternative" is a very good candidate for why this is
>>> being seen -- easiest fix is the command
>>> sudo update-alternatives java
>>>
>>> and choosing version 11 instead of 1.8
>>>
>>>
>>>
>
>> [...]
>
>> rob@rob-Z97:~$ sudo update-alternatives java
>> [sudo] password for rob:
>> update-alternatives: error: unknown argument 'java'
>
> Oops, it's
> sudo update-alternatives --config java
>
> Sorry about that :/
>
>

I hav ejust used the gui version of alternaives, and I have changed the
java version from java-8-openjdk-amd64 to java-11-openjdk.amd64 and now:

ob@rob-Z97:~$ java -version
openjdk version "11.0.17" 2022-10-18
OpenJDK Runtime Environment (build 11.0.17+8-post-Ubuntu-1ubuntu222.04)
OpenJDK 64-Bit Server VM (build 11.0.17+8-post-Ubuntu-1ubuntu222.04,
mixed mode, sharing)
Java/openJDK11+
But Angry IP scanner is STILL saying it needs Java/openJDK11+ to run

Anyone know why this is now.

Thanks

Rob H wrote:
> ob@rob-Z97:~$ java -version
> openjdk version "11.0.17" 2022-10-18
> OpenJDK Runtime Environment (build 11.0.17+8-post-Ubuntu-1ubuntu222.04)
> OpenJDK 64-Bit Server VM (build 11.0.17+8-post-Ubuntu-1ubuntu222.04,
> mixed mode, sharing)
> Java/openJDK11+

Yay!

> But Angry IP scanner is STILL saying it needs Java/openJDK11+ to run
>
Maybe when you installed angryip it 'took' the info available to it
which was 'bad'/misleading; so if you would uninstall it and then
reinstall it your better openjdk situation would be taken up by the
fresh angryip install.

> Anyone know why this is now.

Actually no I don't; I'm just shooting in the dark :-)

--
Mike Easter

Mike Easter wrote:
> Maybe when you installed angryip it 'took' the info available to it
> which was 'bad'/misleading; so if you would uninstall it and then
> reinstall it your better openjdk situation would be taken up by the
> fresh angryip install.

Or maybe you could get away w/ just a logout/login or a reboot before
trying the uninstall/reinstall of angryip.

--
Mike Easter

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2023-02-10, Rob H wrote:
> On 10/02/2023 17:24, Dan Purgert wrote:
>> On 2023-02-10, Rob H wrote:
>>> On 10/02/2023 13:17, Dan Purgert wrote:
>>>> [...]
>>>> A mismatched "alternative" is a very good candidate for why this is
>>>> being seen -- easiest fix is the command
>>>> sudo update-alternatives java
>>>>
>>>> and choosing version 11 instead of 1.8
>>>>
>>>>
>>>>
>>
>>> [...]
>>
>>> rob@rob-Z97:~$ sudo update-alternatives java
>>> [sudo] password for rob:
>>> update-alternatives: error: unknown argument 'java'
>>
>> Oops, it's
>> sudo update-alternatives --config java
>>
>> Sorry about that :/
>>
>>
>
> I hav ejust used the gui version of alternaives, and I have changed the
> java version from java-8-openjdk-amd64 to java-11-openjdk.amd64 and now:
>
> ob@rob-Z97:~$ java -version
> openjdk version "11.0.17" 2022-10-18
> OpenJDK Runtime Environment (build 11.0.17+8-post-Ubuntu-1ubuntu222.04)
> OpenJDK 64-Bit Server VM (build 11.0.17+8-post-Ubuntu-1ubuntu222.04,
> mixed mode, sharing)
> Java/openJDK11+
> But Angry IP scanner is STILL saying it needs Java/openJDK11+ to run

What is the _exact_ error you're getting? Also are you launching it
from terminal or from the GUI?

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmPmiCEACgkQbWVw5Uzn
KGDVExAAkG6wwfKrxGJOXUqMr1tdHXPM+2Vn7bX+Uxs1OPD4yldwIUPx5v/rNSzT
1iHd+VvFPlVkLHlrgS1d1pxNcPR4xFcBir0yKTZlgVtnNbBfSdB3uVAVYY9NZJHr
/VeUP//BXCh5u8hEeXu5nVlRA5ffR4lioerioQIvUAtyOdJaqQJOKmBNUoWzMy8H
p7z8KmLdehW3FHUp4GfFw9oqVwk8Coxb8f9KiINNMGQ+Ar0lQ/VpYfGoGVddfd0/
3Vyhb13q2Rm4XxKG0lnR1VAv5kGxLLkMSxyI539g7eQu1U1mF6YdGTh88Fy4vcAX
d6AkV9Y0XXVQlxxf/feAQuKgNajQ+eS8QNDVg60EdLzXhbCcvkIy1wt+Agqwb1BL
etWwbJ/jSMqFq7Ux+wxH2SbEBwMOqH8IS8TY6ubQwTummVH7K7nwKE5CSaOM0GwN
DGjYBNMFijf61wqP5BmC5KvsxKDqP8XCaeOOHtaF1bhLLU5JM7oX0pwAvI/Vi3yN
Fi65jU4IeMcp7nnDmcViOAlT5LTHcX/UJpNRFDMkasYfhGAQ8E7tbMVhowvYx0jE
KcLwiRtER1L18DYP8BnnevyKh4nsXJqzXyYZqrtGyq7CH6R8B6Buzy8RDpwv6qs9
SdsghMzKMzTKpZBNOrZMCPB0VllJZ5pR0/YLuYrnx89K8xaCtSE=
=0cvV
-----END PGP SIGNATURE-----

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

On 10/02/2023 18:07, Dan Purgert wrote:
> On 2023-02-10, Rob H wrote:
>> On 10/02/2023 17:24, Dan Purgert wrote:
>>> On 2023-02-10, Rob H wrote:
>>>> On 10/02/2023 13:17, Dan Purgert wrote:
>>>>> [...]
>>>>> A mismatched "alternative" is a very good candidate for why this is
>>>>> being seen -- easiest fix is the command
>>>>> sudo update-alternatives java
>>>>>
>>>>> and choosing version 11 instead of 1.8
>>>>>
>>>>>
>>>>>
>>>
>>>> [...]
>>>
>>>> rob@rob-Z97:~$ sudo update-alternatives java
>>>> [sudo] password for rob:
>>>> update-alternatives: error: unknown argument 'java'
>>>
>>> Oops, it's
>>> sudo update-alternatives --config java
>>>
>>> Sorry about that :/
>>>
>>>
>
>> I hav ejust used the gui version of alternaives, and I have changed the
>> java version from java-8-openjdk-amd64 to java-11-openjdk.amd64 and now:
>
>> ob@rob-Z97:~$ java -version
>> openjdk version "11.0.17" 2022-10-18
>> OpenJDK Runtime Environment (build 11.0.17+8-post-Ubuntu-1ubuntu222.04)
>> OpenJDK 64-Bit Server VM (build 11.0.17+8-post-Ubuntu-1ubuntu222.04,
>> mixed mode, sharing)
>> Java/openJDK11+
>> But Angry IP scanner is STILL saying it needs Java/openJDK11+ to run
>
> What is the _exact_ error you're getting? Also are you launching it
> from terminal or from the GUI?
>
>

I am running Angry IP scan from a menu item, so it could be from GUI.
the popup error message says: You need Java/OpenJDK11+ to run ipscan.

Nothing else , just that

On 10/02/2023 18:07, Mike Easter wrote:
> Mike Easter wrote:
>> Maybe when you installed angryip it 'took' the info available to it
>> which was 'bad'/misleading; so if you would uninstall it and then
>> reinstall it your better openjdk situation would be taken up by the
>> fresh angryip install.
>
> Or maybe you could get away w/ just a logout/login or a reboot before
> trying the uninstall/reinstall of angryip.
>

No such luck. I restarted my desktop, tried to run the program, same
error, then un installed the said program, restarted again , then
installed Angry IP scan yet again, same problem!!

Rob H wrote:
> No such luck. I restarted my desktop, tried  to run the program, same
> error, then un installed the said program, restarted again , then
> installed Angry IP scan yet again, same problem!!

Is your java -version still ok?

--
Mike Easter

On 2/10/2023 1:07 PM, Dan Purgert wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 2023-02-10, Rob H wrote:
>> On 10/02/2023 17:24, Dan Purgert wrote:
>>> On 2023-02-10, Rob H wrote:
>>>> On 10/02/2023 13:17, Dan Purgert wrote:
>>>>> [...]
>>>>> A mismatched "alternative" is a very good candidate for why this is
>>>>> being seen -- easiest fix is the command
>>>>> sudo update-alternatives java
>>>>>
>>>>> and choosing version 11 instead of 1.8
>>>>>
>>>>>
>>>>>
>>>
>>>> [...]
>>>
>>>> rob@rob-Z97:~$ sudo update-alternatives java
>>>> [sudo] password for rob:
>>>> update-alternatives: error: unknown argument 'java'
>>>
>>> Oops, it's
>>> sudo update-alternatives --config java
>>>
>>> Sorry about that :/
>>>
>>>
>>
>> I hav ejust used the gui version of alternaives, and I have changed the
>> java version from java-8-openjdk-amd64 to java-11-openjdk.amd64 and now:
>>
>> ob@rob-Z97:~$ java -version
>> openjdk version "11.0.17" 2022-10-18
>> OpenJDK Runtime Environment (build 11.0.17+8-post-Ubuntu-1ubuntu222.04)
>> OpenJDK 64-Bit Server VM (build 11.0.17+8-post-Ubuntu-1ubuntu222.04,
>> mixed mode, sharing)
>> Java/openJDK11+
>> But Angry IP scanner is STILL saying it needs Java/openJDK11+ to run
>
> What is the _exact_ error you're getting? Also are you launching it
> from terminal or from the GUI?
>

ipscan_3.9.0_amd64.deb

ipscan_3.9.0_amd64.deb\data.tar\.\usr\bin\ipscan

#!/bin/sh
java=$JAVA_HOME/bin/java
[ ! -e $java ] && java=java
$java --add-opens java.base/java.net=ALL-UNNAMED -jar /usr/lib*/ipscan/ipscan*.jar "$@"
[ $? != 0 ] && notify-send "You need Java/OpenJDK 11+ to run ipscan"

It's not an error message. If the script
does not run properly for any reason, it prints

"You need Java/OpenJDK 11+ to run ipscan"

Debug as you see fit!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Paul

Rob H wrote:
> On 09/02/2023 20:35, Mark Bourne wrote:
>> apt list --installed 'openjdk*'
>
> Thanks , yes my Mint version gives roughly the same as you:
>
> ob@rob-Z97:~$ which java
> /usr/bin/java
>
> rob@rob-Z97:~$ update-alternatives --display java
> java - manual mode
>   link best version is /usr/lib/jvm/java-11-openjdk-amd64/bin/java
>   link currently points to /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java

It looks like this is your problem - /usr/bin/java is pointed at the
Java 8 installation.

>   link java is /usr/bin/java
>   slave java.1.gz is /usr/share/man/man1/java.1.gz
> /usr/lib/jvm/java-11-openjdk-amd64/bin/java - priority 1111
>   slave java.1.gz: /usr/lib/jvm/java-11-openjdk-amd64/man/man1/java.1.gz
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java - priority 1081
>   slave java.1.gz:
> /usr/lib/jvm/java-8-openjdk-amd64/jre/man/man1/java.1.gz
>
>
> And
>
> ob@rob-Z97:~$ apt list --installed 'openjdk*'
> Listing... Done
> openjdk-11-jdk-headless/jammy-updates,jammy-security,now
> 11.0.17+8-1ubuntu2~22.04 amd64 [installed,automatic]
> openjdk-11-jdk/jammy-updates,jammy-security,now 11.0.17+8-1ubuntu2~22.04
> amd64 [installed]
> openjdk-11-jre-headless/jammy-updates,jammy-security,now
> 11.0.17+8-1ubuntu2~22.04 amd64 [installed]
> openjdk-11-jre/jammy-updates,jammy-security,now 11.0.17+8-1ubuntu2~22.04
> amd64 [installed]
> openjdk-8-jre-headless/jammy-updates,jammy-security,now 8u352-ga-1~22.04
> amd64 [installed]
>
> rob@rob-Z97:~$ apt list --installed 'openjdk*'
> Listing... Done
> openjdk-11-jdk-headless/jammy-updates,jammy-security,now
> 11.0.17+8-1ubuntu2~22.04 amd64 [installed,automatic]
> openjdk-11-jdk/jammy-updates,jammy-security,now 11.0.17+8-1ubuntu2~22.04
> amd64 [installed]
>
> So all should be good but Angry IP Scanner doesn't think so., as it is
> still saying I need openJDK11 .
> Why though

It's probably trying to use the default Java installation, and that's
currently OpenJDK8 installation - which isn't OpenJDK11. There might be
a way to configure your Angry IP Scanner to specifically use the version
installed at /usr/lib/jvm/java-11-openjdk-amd64/bin/java

Otherwise, the "update-alternatives" system can be configured to make
OpenJDK11 the default Java. Run:

sudo update-alternatives --config java

and when prompted, select the Java 11 version.

--
Mark.

Rob H wrote:
> then installed Angry IP scan yet again, same problem!!

Maybe you should uninstall the Oracle/ old java/ stuff. Personally I
would use synaptic, but your call.

--
Mike Easter

Mike Easter wrote:
> Rob H wrote:
>> then installed Angry IP scan yet again, same problem!!
>
> Maybe you should uninstall the Oracle/ old java/ stuff.  Personally I
> would use synaptic, but your call.
>
I would use synaptic to 'watch out for' any tendency to 'disrupt'
important dependencies. I don't know how to do all that w/ the command
line.

--
Mike Easter