discomfitor pushed a commit to branch enlightenment-0.20.
http://git.enlightenment.org/core/enlightenment.git/commit/?id=1f0e9fb0ab7c409aaebc15651a2ec4994dd67439
commit 1f0e9fb0ab7c409aaebc15651a2ec4994dd67439
Author: Carsten Haitzler (Rasterman) <ras...@rasterman.com>
Date: Mon May 16 18:09:12 2016 +0900
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. :)
---
README.wayland | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.wayland b/README.wayland
index 1d49e7f..15de1f3 100644
--- a/README.wayland
+++ b/README.wayland
@@ -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
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,
you can tell Enlightenment to use that when you start it:
--
