Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1748003
Summary: | Epiphany does not render anything when X server is launched by lightdm | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | František Zatloukal <fzatlouk> | ||||
Component: | webkit2gtk3 | Assignee: | Eike Rathke <erack> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 31 | CC: | awilliam, erack, fzatlouk, gecko-bugs-nobody, gmarr, gnome-sig, jhorak, john.j5live, kevin, klember, mcatanzaro+wrong-account-do-not-cc, mclasen, phatina, pwhalen, rhughes, robatino, rstrode, sandmann, tingping, tpopela | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | AcceptedBlocker | ||||||
Fixed In Version: | webkit2gtk3-2.25.92-2.fc31 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-09-10 01:21:05 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1644937 | ||||||
Attachments: |
|
Description
František Zatloukal
2019-09-02 12:43:01 UTC
Proposed as a Blocker for 31-beta by Fedora user frantisekz using the blocker tracking app because: "It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments." After reboot, I've started getting something to stdout. Also, launching with "WEBKIT_DISABLE_COMPOSITING_MODE=1" didn't help. $ WEBKIT_DISABLE_COMPOSITING_MODE=1 epiphany google.cz Unable to init server: Could not connect: Connection refused (WebKitWebProcess:2): Gtk-WARNING **: 08:51:56.033: cannot open display: :0.0 Unable to init server: Could not connect: Connection refused (WebKitWebProcess:2): Gtk-WARNING **: 08:51:56.466: cannot open display: :0.0 ** (epiphany:19753): WARNING **: 08:51:57.139: Web process crashed Unable to init server: Could not connect: Connection refused ... and this is spammed forever. (In reply to František Zatloukal from comment #2) > After reboot, I've started getting something to stdout. Also, launching with > "WEBKIT_DISABLE_COMPOSITING_MODE=1" didn't help. > > $ WEBKIT_DISABLE_COMPOSITING_MODE=1 epiphany google.cz > Unable to init server: Could not connect: Connection refused > > (WebKitWebProcess:2): Gtk-WARNING **: 08:51:56.033: cannot open display: :0.0 > Unable to init server: Could not connect: Connection refused > > (WebKitWebProcess:2): Gtk-WARNING **: 08:51:56.466: cannot open display: :0.0 > > ** (epiphany:19753): WARNING **: 08:51:57.139: Web process crashed > Unable to init server: Could not connect: Connection refused > > ... and this is spammed forever. Look for the backtrace of the WebKitWebProcess crash in coredumpctl.. Guess: web process sandbox might be blocking X11 connections. We've probably only tested it under Wayland. Created attachment 1610806 [details]
Archive containing output files of strace
This isn't arch specific and reproducible on x86_64 with the xfce spin. (In reply to Paul Whalen from comment #6) > This isn't arch specific and reproducible on x86_64 with the xfce spin. That's interesting, I've tried it on GNOME (Xorg) on x86_64 where it worked just fine, didn't try Xfce on x86_64 though :/ So, this means it's broken on all (blocking) arm desktops. Discussed during the 2019-09-03 blocker review meeting: [1] The decision to delay the classification of this as a blocker bug was made as while this and other bugs frantisekz has encountered on his Raspberry Pi 2 worry us, we'd like to delay the decision on them for a bit while we do more triage with other testers and other systems to determine exactly what's going on. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2019-09-03/f31-blocker-review.2019-09-03-16.01.txt So... WebKit web process can't connect to X server... but only if you use Xfce? That's a strange one. Can you confirm that Flatpak'd X11 applications work fine? WebKit should be using X11 identically. Incoming: https://src.fedoraproject.org/rpms/webkit2gtk3/c/51412210ff4717e910fb8147bbd45e8d8a84dc9f?branch=master Thanks Patrick! FEDORA-2019-14d9d650ca has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-14d9d650ca I'm +1 blocker on this now that we seem to have confirmed it'll affect all installs. Any other votes? +1 blocker +1 blocker OK, that's +3. Marking accepted. webkit2gtk3-2.25.92-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-14d9d650ca webkit2gtk3-2.25.92-2.fc31 fixes the issue. Thanks! webkit2gtk3-2.25.92-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. |