Bug 197418 - Segmentation fault at start up of Qt WPE minibrowser
Summary: Segmentation fault at start up of Qt WPE minibrowser
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: WPE WebKit (show other bugs)
Version: WebKit Nightly Build
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-30 09:30 PDT by Ludovico de Nittis
Modified: 2019-05-07 08:18 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ludovico de Nittis 2019-04-30 09:30:18 PDT
I installed the WPE Qt extension with flatpak and when I try to run the minibrowser it crashes with the following stack trace:

$ ./Tools/Scripts/run-qt-wpe-minibrowser

Setting repo flathub URL from Flathub to https://dl.flathub.org/repo/
Using org.webkit.WPE prefix in /home/ryuzaki/ALocalDev/WebKit/WebKitBuild/WPE/FlatpakTreeRelease
Starting MiniBrowser.
1   0x7f5076b39569 WTFCrash
2   0x7f508cfb3ac5 WPEQtView::createWebView()
3   0x7f5099c2d6f2 QObject::event(QEvent*)
4   0x7f509ad6abab QQuickItem::event(QEvent*)
5   0x7f5099c02e89 QCoreApplication::notifyInternal2(QObject*, QEvent*)
6   0x7f5099c05ed7 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
7   0x7f5099c574d3
8   0x7f5096fa84ae g_main_context_dispatch
9   0x7f5096fa8748
10  0x7f5096fa87e0 g_main_context_iteration
11  0x7f5099c56ae3 QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
12  0x7f5099c01b5b QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
13  0x7f5099c09a72 QCoreApplication::exec()
14  0x5574a5441c88 main
15  0x7f50994910d3 __libc_start_main
16  0x5574a5441dae _start
/run/host//tmp/tmpJIiwHG: line 1:     4 Segmentation fault      (core dumped) "/app/webkit/Tools/Scripts/run-qt-wpe-minibrowser" "--release" "--wpe"
Comment 1 Philippe Normand 2019-05-04 03:42:04 PDT
A -platform wayland-egl argument is needed, iirc.
Comment 2 Philippe Normand 2019-05-07 07:07:05 PDT
(In reply to Philippe Normand from comment #1)
> A -platform wayland-egl argument is needed, iirc.

Confirmed. Use either wayland or wayland-egl if you run a desktop under a Wayland compositor.

I wonder why the assert message isn't displayed... This is  the ASSERT:

RELEASE_ASSERT_WITH_MESSAGE(backend, "EGL initialization failed");
Comment 3 Ludovico de Nittis 2019-05-07 08:00:46 PDT
Yesterday I wrote a comment but probably got lost, strange.

Anyway Philippe I also tested the "--platform wayland-egl" and I can confirm that it works.
Comment 4 Philippe Normand 2019-05-07 08:18:31 PDT
Alright, let's close this then :)