Tiny Core Linux
Tiny Core Extensions => TCE Bugs => Topic started by: tcFan on June 21, 2017, 04:40:14 PM
-
hello,
trying to follow the wiki instructions for loading PulseAudio, it seems I can't get dbus to start.
Everything else is working, if I load pulseaudio by sudo and with the --system flag it can even play video music from within Firefox, and get controls through pavucontrol, etc.
I'd like to run it "properly" though. I place the "dbus-launch" script on .X.d/dbus but nothing happens (status returns negative), chmod the file into an executable, also nothing. I do make sure to back it up. Placed dbus.tcz onboot.lst, at the top, as well. Any ideas please?
Edit: Do I have to place something at bootlocal.sh?
-
okay, so it was conflicting information between the wiki and the extension info.
The proper command is "sudo /usr/local/etc/init.d/dbus start" and the dbus file on .X.d/ doesn`t seem to be necessary.
Moreover, a post here suggested loading expat2 before dbus would start it auto but that didn`t work.
I did place the command on bootlocal.sh however and everything works now but, please advise if there is a better way. Thanks.
-
For almost any extension to work with dbus, the dbus daemon either needs to be started manually or via bootlocal.sh
There are a few extensions - avahi, bluez, cups - whose daemons will start the dbus daemon if it is not already started.
The gnome-session extension will autostart many (but not all) daemons and other processes, but requires the dbus daemon to be started before it will run via "startx".
-
> There are a few extensions
Cool. Something like a (pseudo code) "dbus status"?"dbus start":null;
why not add this kind of script to the pulseaudio extension? it clearly requires dbus, right?
-
Once dbus is started several applications like gnome-session and pavucontrol will start pulseaudio automatically.