Ubuntu Studio Bug Updates

[Scott Lavender]

Hello all,

I'd like to inform you about some significant bugs in Ubuntu Studio and
their import.

** Ardour Mute Bug **
The first one I wanted to discuss is the "mute will not work in Ardor" bug -
https://bugs.launchpad.net/bugs/581786

This manifests as disabled mute buttons and I suspect that this has existed
throughout the Ardour 2.8.x series.  This bug results from a build
configuration file that mixes settings of '1' and 'yes' for affirmative.  It
appears that when Ardour is built the 'yes' option is not parsed as an
affirmative and the local config file in the user's home directory therefore
contains settings of '0' for the various mute options.

Those affected will notice this bug when a recording a track and then
attempting to mute the track on playback.  The track will not be muted
although the mute button will lit up.

To fix this in existing projects within Ardour:  right click on the mute
button, four options will be presented, left click on the desired mute
options.  However, I believe this will fix this track ONLY and all new
tracks added will still have a disabled mute button.

To fix this for future project and new tracks in existing projects:  open
the ~/.ardour2/ardour.rc file (notice: the directory is hidden) with your
favorite editor and make sure the to mute options look like this below:

<Option name="mute-affects-pre-fader" value="1"/>
<Option name="mute-affects-post-fader" value="1"/>
<Option name="mute-affects-controls-outs" value="1"/>
<Option name="mute-affects-main-outs" value="1"/>

Ardour-2.8.7 has been built for Maverick with the 120_mute.patch and users
who do a clean, fresh full install with Maverick should not notice this bug.


** gnome-network-admin Bug **
The other bug I wanted to mention is the "can't configure network" bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/570828

This manifests itself on a new install of Ubuntu Studio by a grayed out
configuration options in the gnome-network-admin application for configuring
the network.  This effectively prevents users from configuring a working
network connection, most noticeably after a fresh install of Ubuntu Studio.

When network-manager was chosen to be the default application to configure
networks in vanilla Ubuntu, a patch was applied to gnome-network-admin to
disable the interface resulting in one place to configure the network.  This
works well for vanilla Ubuntu desktop users as they had network-manager
installed by default, however network-manager is not installed by default in
Ubuntu Studio, we have the crippled gnome-network-admin installed by
default.

The choice to use gnome-network-admin should be explained.  network-manager
was discovered to cause additional latency when recording audio, therefore
gnome-network-admin was chosen because it doesn't cause the same latency
issues.  However, it was unknown that the 10_disable_interface.patch was
applied to neuter it's configuration capabilities at that time.

What we are attempting to effect is have the patch removed.  Considering
that gnome-network-admin isn't installed by default in a vanilla Ubuntu
desktop install, we are not expect that this will be considered a
regression.

So until the patch is removed there is still a work around.  I believe that
both network-manager and network-manager-applet are installed on the Ubuntu
Studio DVD.  You can find them on the DVD at:

network-manager:
/pool/main/n/network-manager/network-manager_0.8-0ubuntu3_i386.deb

network-manager-applet:
/pool/main/n/network-manager-applet/network-manager-gnome_0.8-0ubuntu3_i386.deb

You can choose to moderate your sources in Synaptic (System ->
Administration -> Synaptic Package Manger) and add the DVD as a source
(Setting -> Repositories -> Cdrom with Ubuntu 10.04 'Lucid Lynx').  After
reloading package information (RELOADING IS AN IMPORTANT STEP) you should be
able to find and install either network-manager or network-manager-applet,
which would allow you to properly configure your network.

Another options, if you can't use the DVD as a repository, is to copy either
.deb file and install it by copying the .deb file to your desktop and a)
double click on it or b) use the terminal and 'dpkg -i filename.deb'.  NB:
don't type filename in the dpkg command, use the *actual* file name of the
.deb file.

As mentioned before, our goal is to correct this issue and hopefully in time
for Maverick and the rebuilding of 10.04.1.


I hope you find this email helpful.  Please let us know if you have any
questions or comments.

Regards,
ScottL
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-studio-users/attachments/20100527/9a4131cb/attachment-0001.htm