all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Albin <albin@fripost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 23286@debbugs.gnu.org
Subject: bug#23286: Unable to unlock xscreensaver in Xfce
Date: Sun, 22 May 2016 23:56:45 +0200	[thread overview]
Message-ID: <20160522235645.6896525f@fripost.org> (raw)
In-Reply-To: <87zirhojkd.fsf@gnu.org>

Den Sun, 22 May 2016 23:43:14 +0200
skrev Re: bug#23286: Unable to unlock xscreensaver in Xfce:

> Albin <albin@fripost.org> skribis:
> 
> > Den Sat, 21 May 2016 06:37:49 +0200  
> 
> [...]
> 
> >> 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.  
> 
> IIUC, xfce-lock uses one of the above lockers.  For them to work, and
> if you want to be able to unlock your screen ;-), you need to make
> sure you use ‘screen-locker-service’  for each of them.
> 
> So:
> 
>   (operating-system
>     ;; …
>     (services (cons (screen-locker-service xscreensaver)
>                     %desktop-services)))
> 

This was my original configuration which didn't let me unlock if I had
locked with xflock4. Any other ideas?

> since ‘%desktop-services’ already takes care of slock and xlock.
> 
> Could you try and report back?  We’re getting there! :-)

I hope so! :)

> 
> Ludo’.

Albin

  reply	other threads:[~2016-05-22 21:58 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160522235645.6896525f@fripost.org \
    --to=albin@fripost.org \
    --cc=23286@debbugs.gnu.org \
    --cc=ludo@gnu.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.