From: Albin <albin@fripost.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 23286@debbugs.gnu.org
Subject: bug#23286: Unable to unlock xscreensaver in Xfce
Date: Fri, 6 May 2016 20:29:39 +0200 [thread overview]
Message-ID: <572CE293.5080400@fripost.org> (raw)
In-Reply-To: <20160426231752.5355f72b@scratchpost.org>
Sorry about the delay.
Den 2016-04-26 kl. 23:17, skrev Danny Milosavljevic:
> Hi,
>
> On Sun, 24 Apr 2016 16:03:38 +0200
> Albin <albin@fripost.org> wrote:
>
>>> Just to be sure, are you saying that the unlocking works fine with that?
>>
>> Yes, but it doesn't work with Xfce's native screen locking program xflock4.
>
> Ah, then what does
>
> ls -l $(which xflock4)
>
> say?
>
It says:
lrwxrwxrwx 4 root guixbuild 76 1 jan 1970
/run/current-system/profile/bin/xflock4 ->
/gnu/store/[...]-xfce-session-4.12.0/bin/xflock4
Albin
next prev parent reply other threads:[~2016-05-06 18:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 21:16 bug#23286: Unable to unlock xscreensaver in Xfce Albin
2016-04-14 16:50 ` Ludovic Courtès
2016-04-19 19:54 ` Andreas Enge
2016-04-20 16:40 ` Ludovic Courtès
2016-04-23 7:55 ` Danny Milosavljevic
2016-04-23 17:47 ` Albin
2016-04-23 18:22 ` Danny Milosavljevic
2016-04-23 18:28 ` Danny Milosavljevic
2016-04-23 20:15 ` Albin
2016-04-24 1:14 ` Danny Milosavljevic
2016-04-24 14:03 ` Albin
2016-04-26 21:17 ` Danny Milosavljevic
2016-05-06 18:29 ` Albin [this message]
2016-05-18 18:44 ` Danny Milosavljevic
2016-05-20 17:15 ` Albin
2016-05-20 17:48 ` Danny Milosavljevic
2016-05-20 20:22 ` Albin
2016-05-20 18:28 ` Danny Milosavljevic
2016-05-20 18:42 ` Danny Milosavljevic
2016-05-20 22:36 ` Albin
2016-05-21 4:37 ` Danny Milosavljevic
2016-05-21 8:35 ` Albin
2016-05-22 21:43 ` Ludovic Courtès
2016-05-22 21:56 ` Albin
2016-05-23 8:11 ` Ludovic Courtès
2016-05-23 20:18 ` Albin
2016-04-24 13:47 ` Ludovic Courtès
2020-02-18 14:26 ` bug#23286: Hunting #23286: " zimoun
2020-02-18 21:41 ` raingloom
2020-02-18 22:38 ` zimoun
2020-02-25 20:39 ` Albin
2020-02-28 11:53 ` zimoun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=572CE293.5080400@fripost.org \
--to=albin@fripost.org \
--cc=23286@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).