SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I got a e16 desktop up and running, it is set up to call a script to do this
Code:
# Start DBUS session bus:
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
{
eval `dbus-launch --sh-syntax --exit-with-session`
echo "setting: $DBUS_SESSION_BUS_ADDRESS"
export DBUS_SESSION_BUS_ADDRESS
}
else
echo "alldone $DBUS_SESSION_BUS_ADDRESS"
fi
then call to exec e16 next, it was working, but now it looks to be a sporadic in nature. so if I slap that into rc.local and call it during start up, will that even work or cause any issues if it is to work?
or other ideas to make sure this is working. It is a pain if i am already doing something that prevents be from logging out and in again in the hope that the second time will be the charm so I will have automount working.
How are you starting your e16?
If you are booting to run level 3, and then using 'startx', then the DBUS_SESSION_BUS_ADDRESS variable needs to set in ~/.xinitrc. (Note that the startx script specifically unsets that variable, so setting it in rc.local will not work.)
If you are booting to run level 4 and using the kdm display manager, then the DBUS_SESSION_BUS_ADDRESS variable needs to set by a script called by the session desktop file /usr/share/apps/kdm/sessions/enlightenment.desktop. By default, that file has
Code:
Exec=enlightenment_start
You may need to adjust the name of the script, or add the code to set the variable in that script.
How are you starting your e16?
If you are booting to run level 3, and then using 'startx', then the DBUS_SESSION_BUS_ADDRESS variable needs to set in ~/.xinitrc. (Note that the startx script specifically unsets that variable, so setting it in rc.local will not work.)
If you are booting to run level 4 and using the kdm display manager, then the DBUS_SESSION_BUS_ADDRESS variable needs to set by a script called by the session desktop file /usr/share/apps/kdm/sessions/enlightenment.desktop. By default, that file has
Code:
Exec=enlightenment_start
You may need to adjust the name of the script, or add the code to set the variable in that script.
I'm using run level 4 and have a script in local/bin/e16start it runs that dbus then exec starte16 remember this is e16 before they changed everything to what people are seeing is todays enlightenment.
it is exacty like you're saying it is. kdm/e16.desktop -> /usr/local/bin/e16start -> /usr/share/e16/staerte16
I even put an echo in the script to created a file in my home dir with the dbus info and it is getting it,but still it is not working completely. it was working without a hitch after i set it up like this, then I redid my system partitions re-installed and now it is not cooperating.
I am using my other laptop - when i get back to that one I'll refresh my memory on this issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.