All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] xorg with nodm/xdm init.d script conflicts causes blank screen
Date: Sun, 17 Nov 2019 20:28:28 +0100	[thread overview]
Message-ID: <1f4aee0a-074a-dbfc-2d53-908b091501a5@mind.be> (raw)
In-Reply-To: <348ab096ff9aeb8f448af5c8bddf15fdac9a61ed.camel@collabora.com>



On 13/09/2019 23:08, Ezequiel Garcia wrote:
> Hello everyone,
> 
> On Fri, 2019-09-13 at 19:41 +0200, Thomas Petazzoni wrote:
[snip]
>> So it means that starting /usr/bin/nodm in fact starts another X.org
>> server. I would have expected S40xorg to start the X.org server, and
>> then S90nodm to start the display manager inside the X.org server
>> started by S40xorg, but apparently it's not the case.
>>
> 
> Normally, display managers start X. E.g.:
> 
> gdm:
> https://github.com/GNOME/gdm/blob/master/daemon/gdm-server.c#L710
> 
> nodm:
> https://github.com/spanezz/nodm/blob/master/xserver.c#L159
[snip]
>> So if all display manager all start their own X.org server instance, it
>> means that perhaps S40xorg should only be installed if there's no
>> display manager enabled ?
[snip]
> When nodm was introduced, xorg-server didn't have the sysv init script.
> I assume it was added because Bernd needed to launch X without any session,
> but I don't truly understand the reasons for that route, as opposed to
> using a display manager. Or nodm, in case a fixed user login, no security
> is needed, as in a e.g. kiosk thing.
> 
> I haven't checked if it's possible, but I guess we can make some hidden
> config symbol PROVIDES_X_DISPLAY_MANAGER for display managers to select,
> and then use it to restrict the xorg server sysv init so it's available
> only if no display manager was selected.

 Indeed, the proper way is probably to create a virtual package for display
managers, make the different display managers implementations of that virtual
package, and install the xorg init script only when there is no display manager.

 The virtual package will also make sure that there is only 1 display manager.

 Regards,
 Arnout

> 
> Curious about the unfolding,
> Ezequiel
> 
>>> P.S. (As an aside, why don't more buildroot init scripts use 
>>> /etc/default config files?)
>>
>> Because we need more contributions to make our init scripts consistent
>> and use /etc/default config files! :-)
>>
>> Best regards,
>>
>> Thomas
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

      parent reply	other threads:[~2019-11-17 19:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13  6:24 [Buildroot] xorg with nodm/xdm init.d script conflicts causes blank screen Tudor Holton
2019-09-13 17:41 ` Thomas Petazzoni
2019-09-13 21:08   ` Ezequiel Garcia
2019-11-09 16:11     ` Ezequiel Garcia
2019-11-17 19:28     ` Arnout Vandecappelle [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1f4aee0a-074a-dbfc-2d53-908b091501a5@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.