16 Sep
2012
16 Sep
'12
6:39 p.m.
Is there any way (--nodbus?) of getting jackd2 with dbus built in to start
in a no X11 system?
I get this:
Failed to connect to session bus for device reservation Unable to
autolaunch a dbus-daemon without a $DISPLAY for X11
from this:
jackd -v -dalsa -dhw:0 -p2048 -n3
I have an old box with minimal memory, speed, drive space, that I want to
experiment with (using old internal junk sound IF) with cli audio stuff as
well as netjack. (netjack is jackd2)
Or a way of setting up a dbus instance jackd can use. I have seen a script
called jackstart that does this, but the program it uses dbus-launch wants
X11 depends :P
Dbus use should be possible without X11 sessions anyway. I just don't know
how.
I would prefer not to have to use a roll my own version of Jackd so that I
have easy access to updates.
BTW, it would seem that with netjack, MIDI ports can be on a different
machine from Audio IF using a2j (a2j may be needed on more than one
machine if using apps that are alsa midi only on more than one machine).
Any holes in that logic? So two MIDI IFs on two machines should be usable
at the same time. Sync would not be an issue at the speeds MIDI runs at.
In fact it would give better response when using external synths as the
MIDI baud rate would be less of an issue.
Len
--
Len Ovens
www.OvenWerks.net
17 Sep
17 Sep
1:56 a.m.
On Sun, September 16, 2012 9:51 am, Brendan Jones wrote:
I moved both the jack file and the a2j file out of that directory but get
the same message.
--
Len Ovens
www.OvenWerks.net
6:07 a.m.
On Sun, September 16, 2012 9:51 am, Brendan Jones wrote:
Turns out the jackd2 package already pulls in any x11 stuff dbus-x11 needs
and the 130kb it takes on my disk is not a problem. So I can fake an X11
session without having one.
--
Len Ovens
www.OvenWerks.net
11:27 p.m.
On Mon, September 17, 2012 9:07 am, S. Massy wrote:
I'm still working on it. I have a solution that does get jackd running by
using this script:
--------------------------------8<----------------
#! /bin/bash
# file: /home/user/data/script/jackstart
#
# This is ridiculous:
export DISPLAY=:0
# dbus-launch started, DBUS_SESSION_BUS_ADDRESS exported:
export `dbus-launch | grep ADDRESS`
# dbus-launch started, DBUS_SESSION_BUS_PID exported
export `dbus-launch | grep PID`
jackd -dalsa -dhw:0 -r44100 > ~/.log/jack.log 2>&1
-------------------------------8<------------------
I don't like it ... it runs /bin/dbus-daemon twice and both instances keep
running. There should be a way to get both ADDRESS and PID from one
instance.
The second problem is more complex. In an X session situation, all
processes running in that session have the same environment values because
those values are passed to them by the session. In a console or terminal
situation, something like this could be used as part of .profile or
.bashrc for somewhat of the same effect.... but, I would likely have more
than one login that I may be using. I have (so far with just playing with
ALSA) found it handy to have one terminal (out of the 6 VTs) just to run
alsamixer. I think it may be nice to have one for making and breaking jack
connections as well as whatever audio apps I want to play with. So far
that would be 6 instances of dbus-daemon... and I am not sure if something
started in one terminal would be able to talk to one in another... So, I
think I need to have a file that has the three exportable values in it:
DISPLAY, PID and ADDRESS. At a new login bashrc checks for this file and
if it is not there, starts dbus and creates the file. If the file is
there, then the PID is checked to see if it belongs to dbus and if so
exports the file contents... or if not recreates the file.
Another way (I am thinking these up as I go BTW) might be to have
/etc/rc.local run a script that:
su $jackuser
starts dbus as $jackuser
creates file in /home/$jackuser/.config/fakedbus (or something)
This file would have the three lines to export at boot time.
exits
This assumes only one user will be using the machine in this way or that
the same script will be run for all users who might. It would get sourced
as part of .bashrc as the user logs in. The advantage of this is that
jackdbus could be run using jack_control for example. a2j would be able to
use dbus. Session software would be able to run for persistent jack/midi
connections. The system could be run remotely via ssh logins as well.
Comment: Linux and linux distros have become X11 centric or server use
only. There have become a rather narrow set of ways it is meant to be
used. Using Linux as a desktop CLI OS is now quite difficult and takes
some thought and knowledge on the part of the installer.
My test box is a PII (I think) 300Mhz with 191M ram and a 2.6G drive
(include swap). It is amazing what can be fit in here when there is no GUI
to worry about and how much spare CPU there is to play with.
Len
--
Len Ovens
www.OvenWerks.net
19 Sep
19 Sep
8:54 a.m.
On Mon, September 17, 2012 2:27 pm, Len Ovens wrote:
OK, here is what I have done:
/etc/rc.local gets this line added:
su - len -c /home/len/.bin/startfake.sh
startfake.sh looks like this:
------------------------
#! /bin/bash
# Len's try at creating a dbus session on a no X system
# September 18 2012
rm /home/len/.bin/setsession
# Pretend we are X
echo "DISPLAY=:0" >/home/len/.bin/setsession
dbus-launch | grep ADDRESS >>/home/len/.bin/setsession
dbus-launch | grep PID >>/home/len/.bin/setsession
-------------------------------
~/.profile gets this bit added:
-------------------------------
if [ -f "$HOME/.bin/setsession" ]; then
. "$HOME/.bin/setsession"
fi
export DISPLAY
export DBUS_SESSION_BUS_ADDRESS
export DBUS_SESSION_BUS_PID
-------------------------------
here's whats running after boot:
Last login: Tue Sep 18 23:37:06 2012 from len-netbook.cbbs.org
len@mini:~$ ps x
PID TTY STAT TIME COMMAND
821 ? Ss 0:00 //bin/dbus-daemon --fork --print-pid 4
--print-addres
827 ? Ss 0:00 //bin/dbus-daemon --fork --print-pid 4
--print-addres
1136 ? SLsl 0:09 /usr/bin/jackdbus auto
1566 ? S 0:00 sshd: len@pts/1
1567 pts/1 Ss+ 0:05 -bash
2054 ? S 0:00 sshd: len@pts/0
2055 pts/0 Ss 0:05 -bash
2153 pts/0 R+ 0:00 ps x
len@mini:~$ jack_control status
--- status
started
len@mini:~$
Hmm, jackdbus isn't running till I ran jack_control start on the other
login. jackd can also be run ok instead of jackdbus.
--
Len Ovens
www.OvenWerks.net
4580
days inactive
4583
days old
linux-audio-user@lists.linuxaudio.org
6 comments
3 participants
participants (3)
-
Brendan Jones -
Len Ovens -
S. Massy