From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: "André A. Gomes" <andremegafone@gmail.com>
Cc: 55391@debbugs.gnu.org, dev@jpoiret.xyz
Subject: bug#55391: Multiple slim services
Date: Tue, 17 May 2022 09:29:43 +1000 [thread overview]
Message-ID: <87h75pavec.fsf@zancanaro.id.au> (raw)
In-Reply-To: <87fsl9ma1g.fsf@gmail.com>
Hi André,
On Mon, May 16 2022, André A. Gomes wrote:
> Here it goes. The manual states that you can have two slim
> services on different ttys. Am I misinterpreting something?
> Thank you!
I don't think you're misinterpreting anything, but Josselin is
correct when they say
On Fri, May 13 2022, Josselin Poiret wrote:
> If I understand the relevant code properly, this should happen
> only when you try to extend a service type (eg.
> slim-service-type) with another service
In your case, you're using set-xorg-configuration which tries to
extend your slim-service-type service. Unfortunately, you want to
define two of them, which causes the extension mechanism to fail
complaining about the ambiguity.
You should be able to fix this by adding the xorg-configuration
directly into the slim service that you're defining, something
like this:
(cons* (service slim-service-type (slim-configuration
(display ":0")
(vt "vt7")
(xorg-configuration
(xorg-configuration
(modules (list
xf86-input-libinput
xf86-input-evdev
xf86-input-wacom))
(keyboard-layout
keyboard-layout)
(server-arguments
;; disable screen-saver
timeout
(append (list "-s" "0")
%default-xorg-server-arguments))
(extra-config (list
xorg-touchpad
xorg-monitor))))))
(service slim-service-type (slim-configuration
(display ":0")
(vt "vt8")
;; I wasn't sure if you
wanted the same
;; xorg-configuration here,
so I left it out.
))
(modify-services %desktop-services
(delete gdm-service-type)
(delete (screen-locker-service xlockmore "xlock"))))
I hope that helps,
Carlo
next prev parent reply other threads:[~2022-05-16 23:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 21:56 bug#55391: Multiple slim services André A. Gomes
2022-05-13 6:38 ` Josselin Poiret via Bug reports for GNU Guix
2022-05-16 21:39 ` André A. Gomes
2022-05-16 23:29 ` Carlo Zancanaro [this message]
2022-05-17 15:31 ` André A. Gomes
2022-05-17 15:38 ` André A. Gomes
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=87h75pavec.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=55391@debbugs.gnu.org \
--cc=andremegafone@gmail.com \
--cc=dev@jpoiret.xyz \
/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).