hi,
Am Dienstag, den 22.09.2015, 09:10 +0200 schrieb Mr. Kraus:
> I tried to run it in wine (1.4 and later 1.6), and it has a problem
> loading qwindows.dll (from QT5), although as far as I can tell, the
> library is where it should be in the installation folder.
did you install the i386 version
On Tue, 22 Sep 2015 09:10:23 +0200, Mr. Kraus wrote:
>http://tascam.com/content/downloads/products/859/us-16x08_driver_v103_win.zip).
Is it an application or a drive
Hi, I just bought a TASCAM US-16x08 audio interface, and although said to be unsupported, it performs fine with Jack in my Ubuntu Studio 12.04. There is a minor issue at startup (probably with the usb hardware recognition at alsa startup time). However, if the us-16x08 doesn't show in QJackCtrl rig
Thank you Tom for taking the time.
On Tue, 22 Sep 2015 08:36:27 -0400, Tom H wrote:
>systemd-resolved is a service not a package.
Ok, I didn't know it.
[rocketmouse@archlinux ~]$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/sy
On Tue, Sep 22, 2015 at 4:16 AM, Ralf Mardorf
wrote:
> On Mon, 21 Sep 2015 21:51:35 -0400, Tom H wrote:
>> On Sun, Sep 20, 2015 at 1:11 PM, Ralf Mardorf
>> wrote:
>>> by default Wily's /etc/resolv.conf is a link against
>>> ../run/resolvconf/resolv.conf. If you want to maintain Wily from
>>> a
On Tue, 22 Sep 2015 10:19:11 +0200, Ralf Mardorf wrote:
>On Mon, 21 Sep 2015 21:51:35 -0400, Tom H wrote:
>>"systemd-nspawn -bD ...".
>
>I missed this.
>
> -b --boot
>
>I'll test it now ...
[rocketmouse@archlinux ~]$ sudo mv -i /mnt/moonstudio/etc/resolv.conf
/mnt/moonstudio/etc/resolv.conf.fix
On Mon, 21 Sep 2015 21:51:35 -0400, Tom H wrote:
>"systemd-nspawn -bD ...".
I missed this.
-b --boot
I'll test it now ...
--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-disc
On Mon, 21 Sep 2015 21:51:35 -0400, Tom H wrote:
>On Sun, Sep 20, 2015 at 1:11 PM, Ralf Mardorf
> wrote:
>>
>> by default Wily's /etc/resolv.conf is a link against
>> ../run/resolvconf/resolv.conf. If you want to maintain Wily from
>> another install in a systemd-nspawn container, the link needs to
