Per eccerr0r's post, this may not actually gain you anything that you care about. This will give those processes access to a common DBUS session. The requested change runs a DBUS session, with your window manager and all the children thereof under it. Since it seems that you were "forced" to use elogind, then I'd say you should rebuild everything with USE=-elogind to revert to previous behavior and all is better - no need to set up a session through dbus. With the legacy windowmanagers out there which do not provide services to simplify access to console attached devices, there probably is no need for elogind/systemd support anyway, unless you run something that uses the support beyond the windowmanager, perhaps like one of the file managers from a full desktop environment. You should have been able to disable elogind support if you don't want it, though I'm not sure about the consequences of doing such from your setup. How is the above different to just running "exec bspwm"? Which one is "better"? What will I gain? It says I should put "exec dbus-launch -exit-with-session " in my. Since elogind was required to emerge x11-base/xorg-server I've read the Wiki page about elogind. xinitrc file to start my window manager with startx. ![]() ![]() On Debian I always had "exec bspwm" in my. Posted: Sat 11:44 pm Post subject: start window manager with "dbus-launch"? Gentoo Forums Forum Index Desktop Environments Gentoo Forums :: View topic - start window manager with "dbus-launch"?
0 Comments
Leave a Reply. |