Dr. Werner Fink writes:
On Tue, Mar 06, 2012 at 02:33:27PM +0100, Joachim Schrod wrote:
Dr. Werner Fink wrote:
Btw: using standard login should use dbus-launch ... for my personal ~/.xsession I'm using
killall -u werner -q dbus-daemon exec -a dbus-launch dbus-launch --sh-syntax --exit-with-session fvwm2
as very last line.
No ck-launch-session?
My personal dbus daemon runs without dbus-launch. (I don't use standard KDM/gdm startup scripts.) You've got intel when an explicite dbus-launch is needed?
I call kdeinit4 in .xsession for some KDE programs that I use, though. Maybe that starts my dbus daemon.
I try to avoid kde as well as gnome tools due to the fact that the system is flooded with a huge number of daemons I do not need. Those daemons are eating system resources as well as producing a lot of messages I do not want in my ~/.xsession-errors.
The messages problem I understand, I handle that with specific stderr redirections. Avoiding KDE programs is difficult: k3b, digikam, and others are best what's available in Linux, IMHO. Luckily I don't care for the additional daemons, our workstations are powerful enough. But that you don't use ck-launch-session was a bit of surprise. For me, handling access to sound/DVD/USB/etc. via {Console,Policy}Kit has been much better than group rights management; after one got over the almost non-existing documentation. Anyhow, have a nice day. Joachim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org