From debbugs-submit-bounces@debbugs.gnu.org Sat May 21 00:37:56 2016 Received: (at 23286) by debbugs.gnu.org; 21 May 2016 04:37:56 +0000 Received: from localhost ([127.0.0.1]:59450 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b3yfk-0004xz-G1 for submit@debbugs.gnu.org; Sat, 21 May 2016 00:37:56 -0400 Received: from dd1012.kasserver.com ([85.13.128.8]:55380) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b3yfi-0004xq-9n for 23286@debbugs.gnu.org; Sat, 21 May 2016 00:37:54 -0400 Received: from localhost (178.165.131.159.wireless.dyn.drei.com [178.165.131.159]) by dd1012.kasserver.com (Postfix) with ESMTPSA id 8A57B1CA0852; Sat, 21 May 2016 06:37:51 +0200 (CEST) Date: Sat, 21 May 2016 06:37:49 +0200 From: Danny Milosavljevic To: Albin Subject: Re: bug#23286: Unable to unlock xscreensaver in Xfce Message-ID: <20160521063749.4bfd1a4d@scratchpost.org> In-Reply-To: <20160521003629.0796482e@fripost.org> References: <570EB72F.9060101@fripost.org> <87lh4gm8x3.fsf@gnu.org> <20160423095509.46afe0e7@scratchpost.org> <571BB528.7090801@fripost.org> <20160423202252.4802df28@scratchpost.org> <20160423202816.1412a0cc@scratchpost.org> <571BD7DB.7060606@fripost.org> <20160424031423.22ef23ad@scratchpost.org> <571CD23A.1070208@fripost.org> <20160426231752.5355f72b@scratchpost.org> <572CE293.5080400@fripost.org> <20160518204439.31571a4c@scratchpost.org> <573F461A.9010904@fripost.org> <20160520194849.4bae25b7@scratchpost.org> <20160520222201.7b52e715@fripost.org> <20160520202848.460abd5d@scratchpost.org> <20160520204209.75bbfb60@scratchpost.org> <20160521003629.0796482e@fripost.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.28; x86_64-unknown-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 23286 Cc: Ludovic =?UTF-8?B?Q291cnTDqHM=?= , 23286@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.7 (/) On Sat, 21 May 2016 00:36:29 +0200 Albin wrote: Ok, then let's try to find out which locker xflock4 actually uses (from the file you attached). To recap, when you call $ xflock4 manually it locks but doesn't allow you to unlock, right? Please try to call these manually (in that order) and stop at the first one that doesn't throw an error: $ xscreensaver-command -lock $ gnome-screensaver-command --lock $ xlock -mode blank $ slock Which one was it? (It will probably still be unable to unlock)