Bug 174669

Summary: [WPE] WPE doesn't work on Fedora (Fedora 26)
Product: WebKit Reporter: Carlos Alberto Lopez Perez <clopez>
Component: WPE WebKitAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: bugs-noreply, jaragunde, mcatanzaro, zan
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=178896

Carlos Alberto Lopez Perez
Reported 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.
Attachments
Michael Catanzaro
Comment 1 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
Michael Catanzaro
Comment 2 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.
Michael Catanzaro
Comment 3 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 ***
Note You need to log in before you can comment on or make changes to this bug.