From owner-freebsd-xfce@freebsd.org Wed Sep 25 10:19:22 2019 Return-Path: Delivered-To: freebsd-xfce@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 5505F122466 for ; Wed, 25 Sep 2019 10:19:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46dYvG1bn6z3C3T for ; Wed, 25 Sep 2019 10:19:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 34F2D122465; Wed, 25 Sep 2019 10:19:22 +0000 (UTC) Delivered-To: xfce@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 34B4E122464 for ; Wed, 25 Sep 2019 10:19:22 +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 46dYvG0hS9z3C3S for ; Wed, 25 Sep 2019 10:19:22 +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 EB2B1E349 for ; Wed, 25 Sep 2019 10:19:21 +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 x8PAJLWv027439 for ; Wed, 25 Sep 2019 10:19:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x8PAJLRi027438 for xfce@FreeBSD.org; Wed, 25 Sep 2019 10:19:21 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: xfce@FreeBSD.org Subject: [Bug 240804] x11/xfce4-screensaver: Newly Installed via pkg upgrade Does Not Allow Password Input and xscreensaver No Longer Function Forcing User to Reboot Frequently and/or Data Loss Date: Wed, 25 Sep 2019 10:19:22 +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: jlmales@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: xfce@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-xfce@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XFCE for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Sep 2019 10:19:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240804 --- Comment #5 from John --- (In reply to Guido Falsi from comment #4) Agree having two identical "Screensaver (Launch screensaver and locker program)." entries is likely not good. Is there a file, obviously text file, that kee= ps this XFCE autostart configuration in it? If so maybe best to find that file and attach its contents before making any XFCE4 startup configuration chang= es.=20 I have looked in the various directories of /home/keypunch/.config/xfce4 and cannot find any autostart relate files, let alone if text based. As to the issue with the xfce4-screensaver not taking control of keyboard I assume you have not had that challenge in your testing. 2019-09-25 10:15:45+0000 UTC 1569406545 h440nndytpo3mqsdvcmtoeu3tppdnchwt85snd.h440nndytpo3mqsdvcmtoeu3tppdnchwt85s= nd 2 ~ $ ps -Alf | grep screen 1001 34725 12927 0 20 0 9444 3368 select S v0 0:11.55 xscreensaver -no-splash 1001 40578 12927 0 20 0 42696 16816 select S v0 0:01.05 xfce4-screensaver 2019-09-25 10:15:52+0000 UTC 1569406552 h440nndytpo3mqsdvcmtoeu3tppdnchwt85snd.h440nndytpo3mqsdvcmtoeu3tppdnchwt85s= nd 2 ~ $=20 It appears both screensavers are running. Is it possible this may have s= ome root cause for who and when gets the screensaver keyboard? Perhaps this me= ans either one of the startup screensaver entries is for each or only one for b= oth entries? Were you using xcreensaver before you installed xfce4-screensaver for testi= ng? --=20 You are receiving this mail because: You are the assignee for the bug.=