From mboxrd@z Thu Jan  1 00:00:00 1970
From: Danny Milosavljevic <dannym@scratchpost.org>
Subject: bug#23286: Unable to unlock xscreensaver in Xfce
Date: Sat, 21 May 2016 06:37:49 +0200
Message-ID: <20160521063749.4bfd1a4d@scratchpost.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>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39701)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1b3yfu-0008Sa-Aw
	for bug-guix@gnu.org; Sat, 21 May 2016 00:38:07 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1b3yfq-00066H-8O
	for bug-guix@gnu.org; Sat, 21 May 2016 00:38:05 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:47113)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1b3yfq-00066D-5I
	for bug-guix@gnu.org; Sat, 21 May 2016 00:38:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1b3yfp-0004yI-Up
	for bug-guix@gnu.org; Sat, 21 May 2016 00:38:01 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.23286.B23286.146380547619099@debbugs.gnu.org>
In-Reply-To: <20160521003629.0796482e@fripost.org>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Albin <albin@fripost.org>
Cc: 23286@debbugs.gnu.org

On Sat, 21 May 2016 00:36:29 +0200
Albin <albin@fripost.org> 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)