From: Vladimir Sedach <vas@oneofus.la>
To: bone.baboon@disroot.org
Cc: help-guix@gnu.org
Subject: Re: Start Xorg server using xinit manually
Date: Sun, 21 Mar 2021 20:29:41 -0700 [thread overview]
Message-ID: <87wntz50ii.fsf@t510.orion.oneofus.la> (raw)
In-Reply-To: <87sg4ob1sb.fsf@disroot.org>
Bone Baboon <bone.baboon@disroot.org> writes:
> The command also fails with a similar log when prefixed with sudo.
Well, that rules out the setuid issue. Do you get graphics with a
login manager service? I tried getting xinit running as you have, but
gave up at the same step: no /dev/dri/card0 device node.
Looking at my configuration now, I think the problem might be dbus.
Do you have dbus-service enabled? I suspect there might be an
implicit dependence between X and udev (which is probably what is
responsible for creating /dev/dri/card0) on dbus, that might not be
producing any log messages.
The minimal X configuration I have is:
(dbus-service) (service slim-service-type)
> [ 95.135] _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
…
> [ 95.427] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
This part indicates that you might need to figure out the setuid
issue anyway (or run as root) if you make further progress. Debian
has a setuid wrapper executable (at /usr/lib/xorg/Xorg.wrap) that
could be a starting point. I think something like that might need to
go to xinit upstream. See https://issues.guix.gnu.org/25865
If dbus-service does indeed get you farther along, can you please
report that back to the list? In that case, it would seem that
dbus-service is a necessary dependency for running X and should
become part of the provided login manager services.
--
Vladimir Sedach
Software engineering services in Los Angeles https://oneofus.la
next prev parent reply other threads:[~2021-03-22 3:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 22:05 Start Xorg server using xinit manually Bone Baboon
2021-03-21 23:05 ` jbranso
2021-03-21 23:21 ` nylxs
2021-03-22 17:14 ` Leo Famulari
[not found] ` <a03873e7-122d-fa50-21df-295112a5ede5@optonline.net>
2021-03-23 2:39 ` Leo Famulari
2021-03-21 23:58 ` Bone Baboon
2021-03-22 2:55 ` Joshua Branson
2021-03-22 16:49 ` Gary Johnson
2021-03-22 18:34 ` Vincent Legoll
2021-03-22 18:42 ` Leo Famulari
2021-03-23 3:22 ` Bone Baboon
2021-03-23 8:02 ` Sergiu Ivanov
2021-03-24 21:42 ` Bone Baboon
2021-03-23 18:37 ` Gary Johnson
2021-03-26 20:41 ` Bone Baboon
2021-03-28 17:30 ` Gary Johnson
2021-03-24 21:48 ` Bone Baboon
2021-03-22 3:29 ` Vladimir Sedach [this message]
2021-03-24 22:18 ` Bone Baboon
2021-03-25 15:20 ` Gary Johnson
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=87wntz50ii.fsf@t510.orion.oneofus.la \
--to=vas@oneofus.la \
--cc=bone.baboon@disroot.org \
--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).