forked from enlightenment/enlightenment
e start - no it doesny need dbus-launch
no. perhaps you should see the execvp("dbus-launch", dbus_argv); code that auto re-launches using dbus-launch if a dbus session bus etc. is not "found" (env vars). if your issue is that its mis-detecting the fix the detection, but this coe went into e_start like a decade ago or so... and it's worked every since in x11 mode and gave us a dbus session. it SHOULD work for wayland too. don't make instructions change and become more complex if not absoultely needed. :)
This commit is contained in:
parent
b5e47665bb
commit
b4e1e6cbf0
|
@ -70,7 +70,7 @@ Enlightenment, when compiled with Wayland support and started from a tty,
|
||||||
will automatically attempt to load the wl_drm output module and start
|
will automatically attempt to load the wl_drm output module and start
|
||||||
a Wayland session. Simply start as usual:
|
a Wayland session. Simply start as usual:
|
||||||
|
|
||||||
dbus-launch enlightenment_start
|
enlightenment_start
|
||||||
|
|
||||||
If you have a separate configuration profile that you would like to use,
|
If you have a separate configuration profile that you would like to use,
|
||||||
you can tell Enlightenment to use that when you start it:
|
you can tell Enlightenment to use that when you start it:
|
||||||
|
|
Loading…
Reference in New Issue