aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCarsten Haitzler (Rasterman) <raster@rasterman.com>2016-05-16 18:09:12 +0900
committerCarsten Haitzler (Rasterman) <raster@rasterman.com>2016-05-16 18:09:12 +0900
commitb4e1e6cbf06838c1b1e424cc44ca1b4de7ec0370 (patch)
treeca89a499d0a38fcb896024d3528ef1278933ed10
parentstop filling logs with buffer transform/scale spam (diff)
downloadenlightenment-b4e1e6cbf06838c1b1e424cc44ca1b4de7ec0370.tar.gz
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. :)
-rw-r--r--README.wayland2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.wayland b/README.wayland
index 23e69a245..b69ab1361 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: