unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Attila Lendvai <attila@lendvai.name>,
	Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: disable suspend without user login
Date: Fri, 28 Jan 2022 09:11:09 -0800	[thread overview]
Message-ID: <87k0ejn5ua.fsf@yucca> (raw)
In-Reply-To: <lJ-HukmLsvrQ8g2HOV1Fj9Dh1ZEkP-UwFhynoLsV_M6rpYNMHbxrgvv6dQQjpXKoLBYR7gS1gCLjhaFUj1z7oqKue4wMZmWmH7k8md61f2o=@lendvai.name>

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

On 2022-01-28, Attila Lendvai wrote:
>> The first reply already says what you have to do, i.e. set those two
>
> my problem was that i didn't know how to run dbus-launch on Guix.
>
> the proper incantation on Guix is:
>
> $ guix install glib:bin xhost
> $ xhost +
> $ ll `which gsettings`
> $ su -
> # su --login gdm --shell `which bash`
> -bash-5.1$ dbus-launch /gnu/store/567jgb5q1cr7xmqsd5kairrdj66ihhy9-glib-2.70.0-bin/bin/gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'

Be very careful with "xhost +", from the xhost manpage:

  +       Access is granted to everyone, even if they aren't on the list (i.e., access control is turned off).

X is also a network-transparent protocol, so read-write access to your
display from any user on your system or potentially on the network opens
the door wide for keyloggers or other ways to steal passphrases, data on
disk, etc.


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      reply	other threads:[~2022-01-28 17:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  9:28 disable suspend without user login Attila Lendvai
2022-01-27 19:45 ` Simon Streit
2022-01-27 19:57 ` Liliana Marie Prikler
2022-01-28  9:36   ` Attila Lendvai
2022-01-28 17:11     ` Vagrant Cascadian [this message]

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=87k0ejn5ua.fsf@yucca \
    --to=vagrant@debian.org \
    --cc=attila@lendvai.name \
    --cc=guix-devel@gnu.org \
    --cc=liliana.prikler@gmail.com \
    /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).