[Qtwebengine] Re： How do I run web engine on a sever without a display?

[Kevin Truong]

(note that you now have to run the program in sudo, or it won't be able to
connect to the X server)

On Thu, Dec 10, 2015 at 4:17 PM, Kevin Truong <knt261 at gmail.com> wrote:

> FYI, in case it helps anyone in the future, what I ended up using is a
> xdummy. I set up an xorg server with a dummy video driver:
>
> sudo apt-get install xauth xorg openbox
>
> Then followed the xdummy configuration here:
>
>
> http://askubuntu.com/questions/453109/ubuntu-14-04-add-fake-display-when-no-monitor-is-plugged-in
>
> Then, when I ssh into the headless server, I do:
> export DISPLAY=:0
> sudo startx&
>
> That code starts the X server in the background. Then whenever I need to
> run a program that calls qt web engine, I just have to make sure "echo
> $DISPLAY" prints out ":0" (if not, I just export DISPLAY=:0 again), then I
> run the program. It should run smoothly.
>
> Using xdummy this way, the program feels slightly faster than xvfb --
> might be due to xvfb requiring so many file writes to disk. I also notice
> the program hanging less often too.
>
>
>
>
> On Wed, Dec 9, 2015 at 4:22 PM, Kevin Truong <knt261 at gmail.com> wrote:
>
>> Yeah that's what I meant -- the -platform offscreen crashes whether or
>> not you use xvfb.
>>
>> On Wed, Dec 9, 2015 at 12:56 AM, Michael Brüning <
>> michael.bruning at theqtcompany.com> wrote:
>>
>>> Hi Nemo,
>>>
>>> On 12/09/2015 07:43 AM, Nemo wrote:
>>>
>>> xvfb-run --server-args="-screen 0, 1024x868x24" ./myapp_webengine
>>>
>>> This works.
>>>
>>> yes, if you're using xvfb, you shouldn't use -platform offscreen.
>>>
>>> --
>>>
>>> Best regards,
>>> Michael
>>>
>>>
>>> _______________________________________________
>>> QtWebEngine mailing list
>>> QtWebEngine at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/qtwebengine
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20151210/85c37f39/attachment.html>