Re: locating blocked port
On Tue, Jan 31, 2023 at 03:51:20PM -0500, Haines Brown wrote:
> On Tue, Jan 31, 2023 at 12:13:03PM -0500, Henning Follmann wrote:
>
> > I think this is just futile. Why would you do all this painful stuff,
> > which might not get you close to what you really want - running that app.
>
> Are you implying the problem should not occur?
No, apparently the problem occurs. However (and this might sound harsh)
someone who seems to just run a command she/he found somewhere (on the
internet?). You clearly did not understand what that command was doing,
because I do not believe you think the number of text strings in a program
in any way relates to an port that program listens to.
So I am saying base on that I made the judgement that you will not get
anywhere by running strace, and the advise given to you was not a good one.
Also I do not understand why you are so focused on finding that port.
I would go to the documentation of this Project and start looking at that.
https://docs.jabref.org/
And it even has a faq section for linux.
That might be a good start.
>
> > For now I just assume you installed jabref via the debian packaging system?
> > Please just try to start jabref through the system menu.
>
> Yes, I did a normal # aptitude install of jabref. I don't have a
> desktop manager but my window manager has an applications menu. I've
> never used it but I look for jabref and its not in the mentu. The
> jabref command is in my path and so I simply do:
well, what you say you did differs from the original post. There you called
java with a path to the jar.
You will find also in the faq section an answer why that might be a bad
idea.
BTW. The offical debian package of this application is quite old (I think
it is 3.8). You might download the newest version from that project site.
That versin comes with a embedded jre. Maybe try that.
--
Henning Follmann | hfollmann@itcfollmann.com
Reply to: