From owner-freebsd-gnome@freebsd.org Mon Aug 26 05:57:37 2019 Return-Path: Delivered-To: freebsd-gnome@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 225F9D0BA2 for ; Mon, 26 Aug 2019 05:57:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46H1W5070Sz3R8G for ; Mon, 26 Aug 2019 05:57:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 024B6D0BA1; Mon, 26 Aug 2019 05:57:37 +0000 (UTC) Delivered-To: gnome@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 020EFD0B9F for ; Mon, 26 Aug 2019 05:57:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46H1W46Gdkz3R8F for ; Mon, 26 Aug 2019 05:57:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B643D177D for ; Mon, 26 Aug 2019 05:57:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x7Q5vaxX009664 for ; Mon, 26 Aug 2019 05:57:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7Q5vaBh009663 for gnome@FreeBSD.org; Mon, 26 Aug 2019 05:57:36 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 239832] security/secpanel hard-coding of "gnome-terminal" fails under mate-only installation Date: Mon, 26 Aug 2019 05:57:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: radicleparticles@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: gnome@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 05:57:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239832 --- Comment #15 from Jim D. --- There is still something "wrong" about the implementation of secpanel. Once installed, it uses a default user configuration file that has only two line= s in it which do not define any terminal or browser application. When attempting= to execute "secpanel" from icon - nothing appears to happen. When executing the "/usr/local/bin/secpanel" script manually, it fails: Error in startup script: can't read "configs(browserbin)": no such element = in array while executing "$widget([set f]ent) insert 0 "$configs([set f]bin)"" (procedure "main" line 11) invoked from within "main $argc $argv" (file "/usr/local/bin/secpanel" line 2567) The element being searched for does not exist within the application "default.config" file. Yet, when I copy over my previous user "config" file (see attachment 206912= ), everything works just fine. So SOMEthing, SOMEwhere, created the modified u= ser config file. I know that _I_ didn't create the entire thing on my own. I have looked long at the Secpanel TCL scripts and can't find any resolutio= n to this issue. I also don't understand one TCL "foreach" statement that has an= odd number of values used to assign to two loop variables, manages to work. Something within TCL/TK-land must have generated the user config file that I have, but I cannot see what or where. It may be simplest just to supply two "sample" config files, without the "w= ins" statements, for the two major terminal emulators: gnome-terminal and mate-terminal. I will test some variations on this and report back. --=20 You are receiving this mail because: You are the assignee for the bug.=