Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1712515[details]
simple webkit/python browser
Description of problem: In bug 1841104 we got a report that cockpit-desktop does not work properly on RHEL 8.3: The login page still works, but as soon as it connects to the websocket, page hangs or even stays blank.
Version-Release number of selected component (if applicable):
webkit2gtk3-2.28.4-1.el8.x86_64
How reproducible: Always
Steps to Reproduce:
1. /usr/libexec/cockpit-desktop /
Or alternatively, use the attached script:
1. sudo systemctl start cockpit.socket
2. ./pywebkit http://localhost:9090
3. Log in as your user
Actual results:
- In the pywebkit reproducer, the login page works. The login page does not appear with cockpit-desktop (deliberately).
- Webkit window opens and stays empty.
Expected results: webkit window renders cockpit.
Additional info:
* As the login page works, I suspect this is somehow related to cockpit's websocket -- the "main" pages all require that, but the login page doesn't.
* ./pywebkit works fine for other pages like https://google.com or https://redhat.com
* This works fine on Fedora 32, both with epiphany and cockpit-desktop and ./pywebkit. Fedora 32 has the same webkit2gtk3 upstream version.
* I can't test epiphany on RHEL 8.3, as it's not in RHEL nor EPEL, and installing the Fedora 32 package fails due to dependencies.
* Firefox works fine with cockpit. But cockpit-desktop prefers webkit to avoid all the browser chrome (it sets up a little network namespace sandbox, so that cockpit is the *only* thing that the page can access -- it's supposed to feel like a desktop app).
* There are on console messages related to this.
Do you have any hint how to debug that further? Without error messages or console logs I don't know how to proceed here.
Thanks!
Comment 1Michael Catanzaro
2020-08-26 18:48:33 UTC
(In reply to Martin Pitt from comment #0)
> The login page still works, but as soon
> as it connects to the websocket, page hangs or even stays blank.
It's a good thing you mentioned websocket, otherwise this would have been hard. Here's what I did:
* Tested your pywebkit script on RHEL 8.2 and verifies it works fine.
* Installed webkit2gtk3 from RHEL 8.3 on my RHEL 8.2 system and verified it breaks cockpit
* Installed a hacked up scratch build of libsoup 2.70.0 and verified it fixes cockpit
* Breathed sigh of relief. Thank goodness!
The problem is likely caused by https://trac.webkit.org/changeset/248099/webkit. We switched from WebKit's cross-platform WebSockets implementation to libsoup's implementation. And our libsoup in RHEL is old and missing a couple dozen WebSocket fixes. So we could either revert that change in WebKit, or figure out what commit in libsoup we need to fix this. Fixing libsoup is almost surely going to be a smaller, easier, and safer change, so next I'll try to figure out which commit in libsoup is needed. So far, I know that the issue was fixed somewhere between 2.62.3 (RHEL 8) and 2.70.0 (latest stable).
Shame we missed blocker/exception deadline, but late-breaking problems like this are what the exception process is for....
Comment 3Michael Catanzaro
2020-08-26 21:57:35 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: GNOME security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:4451