From: Bone Baboon <bone.baboon@disroot.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: help-guix@gnu.org
Subject: Re: Starting Sway a Wayland window manager
Date: Sun, 28 Mar 2021 23:14:55 -0400 [thread overview]
Message-ID: <87o8f2fy6o.fsf@disroot.org> (raw)
In-Reply-To: <87blb4ysii.fsf@yucca>
Vagrant Cascadian writes:
> Is the elogind service running? I *think* that is what I needed to get
> sway working from the console...
I have added the `elogind` service. Here is the services section of my
systems configuration:
```
(services
(append
(list
(service elogind-service-type)
(service accountsservice-service-type)
(service inputattach-service-type)
x11-socket-directory-service
polkit-wheel-service)
%base-services))
```
When I run `sudo herd status` the output shows that `elogind` is
started.
When I run `sway` on virtual terminal 1 sway does not start and I get
this output:
```
localhost dbus-daemon[380]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.24" (uid=1000 pid=26112 comm="sway ") interface="org.freedesktop.login1.Session" member="SetType" error name="(unset)" requested_reply="0" destination="org.freedesktop.login1" (uid=0 pid=381 comm="/gnu/store/jdk3r1gs4d36n3aj9fscsvwwc9prnrzp-elogin")
[backend/backend.c:303] Failed to open any DRM device
[sway/server.c:49] Unable to create backend
```
When I run `sudo sway` it outputs "XDG_RUNTIME_DIR is not set in the
environment. Aborting.".
next prev parent reply other threads:[~2021-03-29 3:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 0:43 Starting Sway a Wayland window manager Bone Baboon
2021-03-28 1:05 ` jbranso
2021-03-28 1:30 ` Vagrant Cascadian
2021-03-28 2:27 ` Joshua Branson
2021-03-28 16:45 ` Joshua Branson
2021-03-29 13:53 ` Bone Baboon
2021-03-29 15:07 ` Joshua Branson
2021-03-29 3:19 ` Bone Baboon
2021-03-29 3:55 ` Joshua Branson
2021-03-29 13:45 ` Bone Baboon
2021-03-29 18:23 ` Vagrant Cascadian
2021-03-31 21:12 ` Bone Baboon
2021-03-31 22:41 ` Vagrant Cascadian
2021-03-29 3:14 ` Bone Baboon [this message]
2021-03-29 3:54 ` Joshua Branson
2021-03-29 15:37 ` raingloom
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=87o8f2fy6o.fsf@disroot.org \
--to=bone.baboon@disroot.org \
--cc=help-guix@gnu.org \
--cc=vagrant@debian.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).