ngPost_v1.6-x86_64.AppImage: core dump when X display not present (aka: via a ssh session)

[sanderjo]

When I connect via ssh (so: no X settings), and start ngPost_v1.6-x86_64.AppImage without parameters, it gives a coredump.
I find that quite a hefty effect.
I would prefer ngPost_v1.6-x86_64.AppImage so say something nicely about missing X / GUI.

sander@brixit:~$ ./ngPost_v1.6-x86_64.AppImage 
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.

Aborted (core dumped)

FWIW:

sander@brixit:~$ ./ngPost_v1.6-x86_64.AppImage --help
ngPost_v1.6 is a NNTP poster that can:
  - use multiple connections on multiple servers. (for multiple server, you've to use a config file)
  - spread those connections on several threads (by default the number of cores available)
  - post several files or directory (you can put several times the option -i)
  - generate the nzb
  - use SSL encryption if desired

Syntax: ngPost_v1.6-x86_64.AppImage (options)? (-i <file or directory to upload>)+
        --help             : Help: display syntax
        -v or --version    : app version
        -c or --conf       : use configuration file (if not provided, we try to load $HOME/.ngPost)

[mbruel]

Well, I'm not sure how to help with that...
It's kind of the desired behaviour.
I first developed ngPost to be pure CMD thus you wouldn't have this issue.
Then upon request and to get more visibility I've developed a simple GUI.
I was first maintaining a macro USE_HMI to be able to compile in pure non GUI version but I removed it as I was finding it a bit useless.

So basically, if you launch ngPost without any arguments (or just double click on it from a desktop environment) then it opens the app in graphical mode (creating a QAppilcation and a MainWidow)
However, if you launch it with at least one argument (--help, -v...) it would then be a pure non GUI application so it can run on servers without any server X.

As there is no point to launch it on server without arguments, I'm not sure this is really an issue.
I get you, it's not clean, but it's have one executable that would both run pure CMD and graphically ;)

Let me know what you think, please close the issue if your cool with that.

[sanderjo]

With the self-compiled version, the output is cleaner and no core dump:

sander@brixit:~/git/ngPost/src$ ./ngPost 
qt.qpa.screen: QXcbConnection: Could not connect to display 
Could not connect to any X display.

... that's looks quite nice.