From debbugs-submit-bounces@debbugs.gnu.org Sat May 21 02:36:11 2016 Received: (at 23286) by debbugs.gnu.org; 21 May 2016 06:36:11 +0000 Received: from localhost ([127.0.0.1]:59483 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b40WB-0007ka-LK for submit@debbugs.gnu.org; Sat, 21 May 2016 02:36:11 -0400 Received: from giraff.fripost.org ([178.16.208.44]:47232 helo=outgoing.fripost.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b40WA-0007kO-7D for 23286@debbugs.gnu.org; Sat, 21 May 2016 02:36:10 -0400 Received: from localhost (localhost [127.0.0.1]) by outgoing.fripost.org (Postfix) with ESMTP id 20EB35916CD; Sat, 21 May 2016 08:36:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fripost.org; h= content-transfer-encoding:content-type:content-type:mime-version :x-mailer:references:in-reply-to:message-id:subject:subject:from :from:date:date; s=20140703; t=1463812562; x=1465626963; bh=NNGe dSVmHWGNbrPWMNA9dV3xRgvHLh1cyDUVAjmjnv8=; b=A4LSNd/80O58Bovv//42 W7cWV6TDufJ11Uqwiuq0NuIYslTtAbhg3KCf7VKbOw8yQwR8AGj5A7KYMszKVhvo ruOLIspEsCaKijTFA6w5XzShAA4WcZGx/WP0I0zhzaQvIjpNU1UUM2KxrmHdM712 p1maVRJlqhVZv0jFPu2mtyU= X-Virus-Scanned: Debian amavisd-new at fripost.org Received: from outgoing.fripost.org ([127.0.0.1]) by localhost (giraff.fripost.org [127.0.0.1]) (amavisd-new, port 10040) with LMTP id RL5tiPcEsVjY; Sat, 21 May 2016 08:36:02 +0200 (CEST) Received: from smtp.fripost.org (mistral.fripost.org [178.16.208.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mistral.fripost.org", Issuer "mistral.fripost.org" (not verified)) by outgoing.fripost.org (Postfix) with ESMTPS id E20215916CA; Sat, 21 May 2016 08:36:02 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) by smtp.fripost.org (Postfix) with ESMTPSA id 645CB1983160; Sat, 21 May 2016 08:36:02 +0200 (CEST) Date: Sat, 21 May 2016 10:35:59 +0200 From: Albin To: Danny Milosavljevic Subject: Re: bug#23286: Unable to unlock xscreensaver in Xfce Message-ID: <20160521103559.4c4d11ff@fripost.org> In-Reply-To: <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> <20160521063749.4bfd1a4d@scratchpost.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: -3.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: -3.7 (---) Den Sat, 21 May 2016 06:37:49 +0200 skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce: > 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? 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 Unable to unlock. > $ gnome-screensaver-command --lock Command not found. > $ xlock -mode blank Worked. ('xlock' also worked.) > $ slock Worked. > > Which one was it? > > (It will probably still be unable to unlock) Now what? :) Albin