From owner-freebsd-xfce@freebsd.org Thu Sep 26 05:33:15 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 4343CF974E for ; Thu, 26 Sep 2019 05:33:15 +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 46f3Vf70F4z3KK7 for ; Thu, 26 Sep 2019 05:33:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id F00B9F974D; Thu, 26 Sep 2019 05:33:14 +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 EFCF9F974C for ; Thu, 26 Sep 2019 05:33:14 +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 46f3Vf640bz3KK6 for ; Thu, 26 Sep 2019 05:33:14 +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 B481D236F2 for ; Thu, 26 Sep 2019 05:33:14 +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 x8Q5XEDp055138 for ; Thu, 26 Sep 2019 05:33:14 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x8Q5XEAA055137 for xfce@FreeBSD.org; Thu, 26 Sep 2019 05:33:14 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: Thu, 26 Sep 2019 05:33:14 +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: In Progress 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: Thu, 26 Sep 2019 05:33:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240804 --- Comment #10 from John --- (In reply to Guido Falsi from comment #8) It was a very unexpected long day as result of multiple FreeBSD bugs. I st= ill have few to open unrelated to this issue. I was not up again until late to= day and have a number of eMail I needed to do and updates related bug #240801 a= nd bug # 240811. I was so tired I really made a mess of what was to be two si= mple updates to bug #240810. Before I was to bed I made the changes to the XFCE .desktop files for autos= tart as per bug #240810 and but #240810. The tests are time consuming as there = are reboots and waiting time for the screensaver to activate. I then enabled xscreensaver and disabled xfce4-screensaver. xscreensaver a= s I=20 have been used to since installing FreeBSD mid July 2019 as had been since = the FreeBSD install. Then I flipped to enabling xfce4-screensaver and disabling xscreensaver.=20 xfce4-screensaver worked which means it accepted keyboard input. I went to sleep, way too tired to do anything else. A short time ago I was able to clear/save what I was working on at time to = do the next test of both xscreensaver and xfce4-screensaver active at same tim= e.=20 The bug issue as reported and first experienced after the FreeBSD pkg upgra= de occurred. I changed the XFCE4 startup to enabled for xfce4-screensaver and disabled f= or xscreensaver on purpose rahter than xscreensaver I have used for years on purpose. Something odd I think is occurring with xfce4-screensaver, but I = am not sure so it will take a few days on using xfce4-screensaver before I kno= w it this odd behaviour I think occurred occurs again. If the od behaviour occu= rs again it will be a new bug report as it will be a very different issue. When xscreensaver and xfce-screensaver are enabled xfce4-screensaver takes presendance in displaying ove xscreensaver on system when some mouse or keyboard action wakes up the screensaver. As you suspected (an made sense = to me) with xscreensaver and xfce4-screensaver enabled is preventing keyboard input reaching xfce4-screensaver and appears does not reach the hidden from display xscreensaver that xfce4-screensaver os layered overtop on system. The question now is how should xfce handle two or more different screensave= rs on the system? In my opinion there are different pros and cons for any of = the possible solutions. One aspect to take into consideration is xscreensaver works on multiple DEs where as xfce4-screensaver likely only works with XFC= E4.=20 For those that have multiple DEs they can and do use it would seem likely, = but not a sure thing, that xscreensaver should take precedence as the screensav= er enabled for the DE, ergo precedence for XFCE4. This is just one thought of= a few approaches that I think merits some discussion to see what seems the be= st approach to take. I suspect this may be difficult discussion in that I can= see many approaches that may makes sense as well. I suggested the rational for xscreensaver based on xscreensaver most likely works in most, if not all DE= s.=20 That said discussion should occur to see what other thoughts are and the pros/cons of those before deciding what approach will be taken. --=20 You are receiving this mail because: You are the assignee for the bug.=