Bug 174669 - [WPE] WPE doesn't work on Fedora (Fedora 26)
Summary: [WPE] WPE doesn't work on Fedora (Fedora 26)
Status: RESOLVED DUPLICATE of bug 178896
Alias: None
Product: WebKit
Classification: Unclassified
Component: WPE WebKit (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-20 03:19 PDT by Carlos Alberto Lopez Perez
Modified: 2017-10-30 07:10 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Alberto Lopez Perez 2017-07-20 03:19:33 PDT
It seems some users (at least Jacobo and Michael) are having trouble using the WPE minibrowser (dyz) on Fedora.

The error is:

PlatformDisplayWPE: could not create the EGL display.


Some quick instructions about how to test WPE are at: https://trac.webkit.org/wiki/WPE


This is using Mesa graphics.
Comment 1 Michael Catanzaro 2017-07-20 05:34:03 PDT
Well there are two errors. That is the first one. The next one is:

/home/mcatanzaro/Projects/WebKit/WebKitBuild/Release/bin/WPENetworkProcess: symbol lookup error: /home/mcatanzaro/Projects/WebKit/WebKitBuild/Release/lib/libWPEWebKit.so.0: undefined symbol: soup_auth_negotiate_supported
Comment 2 Michael Catanzaro 2017-07-20 05:35:25 PDT
Note: all dependencies of WebKit that themselves depend on libsoup need to be added to the JHBuild environment. Probably one is missing.
Comment 3 Michael Catanzaro 2017-10-30 07:10:54 PDT
I think this is a duplicate, and the other bug has comments with some debugging, so let's move discussion there even though this one is a lot older.

(In reply to Michael Catanzaro from comment #1)
> Well there are two errors. That is the first one. The next one is:
> 
> /home/mcatanzaro/Projects/WebKit/WebKitBuild/Release/bin/WPENetworkProcess:
> symbol lookup error:
> /home/mcatanzaro/Projects/WebKit/WebKitBuild/Release/lib/libWPEWebKit.so.0:
> undefined symbol: soup_auth_negotiate_supported

I'm not seeing that myself, using our JHBuild environment. Perhaps we fixed that in the past several months.

*** This bug has been marked as a duplicate of bug 178896 ***