Bug 1439798
Summary: | libsoup stuck on infinite loop for kerberized pages | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Michal Odehnal <modehnal> |
Component: | libsoup | Assignee: | Tomas Popela <tpopela> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.4 | CC: | tpelka, tpopela |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libsoup-2.56.0-3.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 19:32:29 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: |
Description
Michal Odehnal
2017-04-06 14:34:14 UTC
Console output upon opening: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess: symbol lookup error: /lib64/libwebkit2gtk-4.0.so.37: undefined symbol: gtk_widget_path_iter_set_object_name (In reply to Michal Odehnal from comment #2) > Console output upon opening: > /usr/libexec/webkit2gtk-4.0/WebKitWebProcess: symbol lookup error: > /lib64/libwebkit2gtk-4.0.so.37: undefined symbol: > gtk_widget_path_iter_set_object_name You don't have gtk3 package from 7.4 installed. The error that I see is: (process:17033): libsoup-WARNING **: SoupMessage 0x5628b94be940 stuck in infinite loop? Console output upon opening in VM: (process:7189): libsoup-WARNING **: gssapi step failed: Unspecified GSS failure. Minor code may provide more information: SPNEGO cannot find mechanisms to negotiate Reproducible with get utility from libsoup: ./get -d -N -c ~/Documents/red_hat_ca_cert.crt https://tcms.engineering.redhat.com I'm moving it to the right component (libsoup) before I will investigate it further. OK, so the tcms is sending the following response to the initial GET: < HTTP/1.1 401 Authorization Required < Soup-Debug-Timestamp: 1491552071 < Soup-Debug: SoupMessage 1 (0x2083bd0) < Date: Fri, 07 Apr 2017 08:01:11 GMT < Server: Apache/2.2.15 (Red Hat) < WWW-Authenticate: Negotiate < WWW-Authenticate: Basic realm="TCMS - Kerberos login (if negotiate unavailable)" < Last-Modified: Thu, 08 Dec 2016 08:15:51 GMT < ETag: "9fb30-0-543213ee8e70f" < Accept-Ranges: bytes < Vary: Accept-Encoding < Content-Encoding: gzip < Content-Length: 20 < Connection: close < Content-Type: text/plain; charset=UTF-8 The problem here is the request to close the connection. This is causing the connection to be closed and the authentication process to be restarted. For example the errata server specifies the connection to be kept alive, which I think is the right thing to do. But I need to confirm it the the kerberos guys. 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, 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/RHEA-2017:2146 |