unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jeff Bauer <jeffrubic@gmail.com>
To: help-guix@gnu.org
Subject: i3lock: problem and solution
Date: Sun, 16 Jun 2019 09:29:15 -0500	[thread overview]
Message-ID: <20190616142915.GC12459@serpent> (raw)

Thanks to support on #guix irc, I was able to get i3lock
working.  After installing the package, i3lock would not
accept my login password.  It was suggested that I add
to my config.scm:

(screen-locker-service i3lock "i3lock")

However, I still wasn't able to unlock my screen.  Next
suggestion was to add i3lock to config.scm packages,
but that also didn't work.  Finally xavierm02_ suggested
that I uninstall i3lock as a user package which fixed
the problem.  Per kmicu: "my guess is that your i3lock
from specification->packages shadows i3lock from the
service which has setuid set."

Changes to my config.scm below.  Posting here on the
mail list in case anyone else experiences similar issues.
Thanks to everyone for their advice.

-Jeff


 (use-modules (gnu))
 (use-service-modules desktop networking ssh xorg)
+(use-package-modules wm)

 (operating-system
   (locale "en_US.utf8")
@@ -35,6 +36,7 @@
   (packages
     (append
       (list (specification->package "i3-wm")
+            (specification->package "i3lock")
             (specification->package "nss-certs"))
       %base-packages))
@@ -42,6 +44,7 @@
     (append
       (list (service xfce-desktop-service-type)
             (service openssh-service-type)
+            (screen-locker-service i3lock "i3lock")
             (set-xorg-configuration
               (xorg-configuration
                 (keyboard-layout keyboard-layout))))

             reply	other threads:[~2019-06-16 14:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-16 14:29 Jeff Bauer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-16 13:54 i3lock: problem and solution Jeff Bauer

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=20190616142915.GC12459@serpent \
    --to=jeffrubic@gmail.com \
    --cc=help-guix@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.
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).