From owner-freebsd-current@freebsd.org Mon Sep 21 22:36:48 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1E28F3FF657 for ; Mon, 21 Sep 2020 22:36:48 +0000 (UTC) (envelope-from doctorwhoguy@gmail.com) Received: from mail-ej1-x642.google.com (mail-ej1-x642.google.com [IPv6:2a00:1450:4864:20::642]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BwK732Y4Gz43V2 for ; Mon, 21 Sep 2020 22:36:47 +0000 (UTC) (envelope-from doctorwhoguy@gmail.com) Received: by mail-ej1-x642.google.com with SMTP id q13so20013629ejo.9 for ; Mon, 21 Sep 2020 15:36:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=YDV+ZXBN3TAmLITFa5iVYLSxA8RZVNzPoOK3x+qN1SM=; b=hypV91VretvZhYnC4QKDGF1DC0eeYVZM8X2pIAoSeqpoCflFdgUiAVHSNRSGHBDLZH 1qb5iCu71JRXoW5r/ZMYlNVK451L1iEFSmYeZzTbE+ATMFQYEuzvC55q30Qv8cYwh9Ur ObHBHHQEWcTMLLse0FUUNar37+zJ7tUe7pB9f0KpL4gTLdnde9x1gqvSMHY5nEWQ1dPz /0TWmlARUUUwRy7C/X4q7kMa+bB9r0A34r/Kh/e9EThLOvMGwoqTYCmOSwtC1Zz2MhJQ ztT92iE8LFlvlFVgSEVUbKqXsIKbPZ61J3MXq3RVD2q+xa8NUG/L0hDsezOjUfvMGwyY EMkA== X-Gm-Message-State: AOAM533aZkguO/oH0gHaHVSKAdk3hz73O7y94PLkOuw4FZDBMBWEdZVO 19flCKls7OjGKccwtsoT0M4hplTitrdGTjLAkrj5aZC3plY= X-Google-Smtp-Source: ABdhPJxpI5CiITqSLPHeU/jijkZj3MYw0v1m+HQS4jlQW+HMZqPBlZPy9hITYhbQ4dbTOoYP8njx8XGnIfqcSbvBel4= X-Received: by 2002:a17:906:6411:: with SMTP id d17mr1707367ejm.93.1600727805125; Mon, 21 Sep 2020 15:36:45 -0700 (PDT) MIME-Version: 1.0 From: Patrick McMunn Date: Mon, 21 Sep 2020 17:36:33 -0500 Message-ID: Subject: Can't forward X11 apps over ssh since migrating to 13-CURRENT To: freebsd-current@freebsd.org X-Rspamd-Queue-Id: 4BwK732Y4Gz43V2 X-Spamd-Bar: / X-Spamd-Result: default: False [-0.96 / 15.00]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; TO_DN_NONE(0.00)[]; URI_COUNT_ODD(1.00)[1]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.01)[-0.008]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.94)[-0.943]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.01)[-1.005]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::642:from]; HTTP_TO_IP(1.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2020 22:36:48 -0000 I don't know if it's just coincidental or if it's because of some change in 13-CURRENT, but I recently migrated from 12.1-STABLE, and now I am unable to forward X11 apps over ssh. The only app I was accustomed to running this way was Handbrake. It worked fine before, but now i get this: $ ghb Unable to init server: Could not connect to 127.0.0.1: Connection refused (ghb:87219): Gtk-WARNING **: 13:12:41.281: cannot open display: I have tried other apps like Wireshark and even xclock just to see, but they won't work either. Has anyone else had problems with X11 forwarding on 13-CURRENT? If it's working for everyone else, at least I can know it's probably not 13-CURRENT's fault, and I need to look elsewhere for the cause. And yes, my sshd_config has it enabled. It worked fine before, and I made sure to keep the same config.