Comment # 14 on bug 1008760 from Karl Cheng

(In reply to Michal Suchanek from comment #13)
> This still does not work for me on SLE12 (SP2 , it does not build on earlier
> due to lack of QT5)
> 
> # phantomjs
> QXcbConnection: Could not connect to display 
> PhantomJS has crashed. Please read the bug reporting guide at
> <http://phantomjs.org/bug-reporting.html> and file a bug report.
> Aborted (core dumped)
> 
> 
> Often connecting to a display gives a DISPLAY* pointer which is not checked
> for non-null leading to a crash.
> 
> However, *NOT* connecting to a display is supposed feature of phantomjs so
> trying to connect in the first place is in itself broken.

Is this the version in devel:languages:nodejs?(In reply to Michal Suchanek from
comment #13)
> This still does not work for me on SLE12 (SP2 , it does not build on earlier
> due to lack of QT5)
> 
> # phantomjs
> QXcbConnection: Could not connect to display 
> PhantomJS has crashed. Please read the bug reporting guide at
> <http://phantomjs.org/bug-reporting.html> and file a bug report.
> Aborted (core dumped)
> 
> 
> Often connecting to a display gives a DISPLAY* pointer which is not checked
> for non-null leading to a crash.
> 
> However, *NOT* connecting to a display is supposed feature of phantomjs so
> trying to connect in the first place is in itself broken.

Indeed, thanks for testing. (Didn't check this in headless environment.)

I tried using the "offscreen" Qt plugin but the images produced seemed to be
broken (no images or text rendered, just layout).

I'll submit 2.1.1 instead given the Git snapshot doesn't exactly seem ready to
use/test yet.