yeah that issue is fixed in the bzr branch. Try debuild -us -uc , which
should disable signing (why you had the failure)
On Sat, Jan 18, 2014 at 4:34 PM, ianorlin <email address hidden> wrote:
> starting testdrive gtk from a terminal did give me an error saying not
> supported version of virtualbox which mine is currently 4.3 while
> testdrive currently only supports 4.0 4.1 and 4.2
>
> --
> You received this bug notification because you are subscribed to
> TestDrive.
> https://bugs.launchpad.net/bugs/1270331
>
> Title:
> In trusty testdrive will not create a virtualbox virtual machine of
> lubntu i386 guest from trusty amd 64 host
>
> Status in Test Drive an Ubuntu ISO in a Virtual Machine:
> New
> Status in “testdrive” package in Ubuntu:
> New
>
> Bug description:
> lsb_release
> Distributor ID: Ubuntu
> Description: Ubuntu Trusty Tahr (development branch)
> Release: 14.04
> Codename: trusty
> 2. apt-cache policy testdrive
> installed 3.24-0ubuntu1
> canidate 3.24-0ubuntu1
> apt-cache policy virtualbox
> Installed: 4.3.2-dfsg-1ubuntu1
> Candidate: 4.3.2-dfsg-1ubuntu1
> 3. I expected test drive to start a virtualbox vm of the trusty lubuntu
> i386 dialy. Steps to reproduce are sync an i386 lubuntu trusty iso and then
> try to try to launch the vm. I wanted the virtual machine to be created.
> 4. Instead testdrive said configuring virtual machine but never
> completes.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: testdrive 3.24-0ubuntu1
> ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
> Uname: Linux 3.12.0-7-generic x86_64
> NonfreeKernelModules: wl
> ApportVersion: 2.13.1-0ubuntu1
> Architecture: amd64
> CurrentDesktop: LXDE
> Date: Fri Jan 17 16:08:37 2014
> InstallationDate: Installed on 2014-01-02 (15 days ago)
> InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha amd64 (20140101)
> PackageArchitecture: all
> SourcePackage: testdrive
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/testdrive/+bug/1270331/+subscriptions
>
yeah that issue is fixed in the bzr branch. Try debuild -us -uc , which
should disable signing (why you had the failure)
On Sat, Jan 18, 2014 at 4:34 PM, ianorlin <email address hidden> wrote:
> starting testdrive gtk from a terminal did give me an error saying not /bugs.launchpad .net/bugs/ 1270331 ature: Ubuntu 3.12.0-7.15-generic 3.12.4 dules: wl ture: all /bugs.launchpad .net/testdrive/ +bug/1270331/ +subscriptions
> supported version of virtualbox which mine is currently 4.3 while
> testdrive currently only supports 4.0 4.1 and 4.2
>
> --
> You received this bug notification because you are subscribed to
> TestDrive.
> https:/
>
> Title:
> In trusty testdrive will not create a virtualbox virtual machine of
> lubntu i386 guest from trusty amd 64 host
>
> Status in Test Drive an Ubuntu ISO in a Virtual Machine:
> New
> Status in “testdrive” package in Ubuntu:
> New
>
> Bug description:
> lsb_release
> Distributor ID: Ubuntu
> Description: Ubuntu Trusty Tahr (development branch)
> Release: 14.04
> Codename: trusty
> 2. apt-cache policy testdrive
> installed 3.24-0ubuntu1
> canidate 3.24-0ubuntu1
> apt-cache policy virtualbox
> Installed: 4.3.2-dfsg-1ubuntu1
> Candidate: 4.3.2-dfsg-1ubuntu1
> 3. I expected test drive to start a virtualbox vm of the trusty lubuntu
> i386 dialy. Steps to reproduce are sync an i386 lubuntu trusty iso and then
> try to try to launch the vm. I wanted the virtual machine to be created.
> 4. Instead testdrive said configuring virtual machine but never
> completes.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: testdrive 3.24-0ubuntu1
> ProcVersionSign
> Uname: Linux 3.12.0-7-generic x86_64
> NonfreeKernelMo
> ApportVersion: 2.13.1-0ubuntu1
> Architecture: amd64
> CurrentDesktop: LXDE
> Date: Fri Jan 17 16:08:37 2014
> InstallationDate: Installed on 2014-01-02 (15 days ago)
> InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha amd64 (20140101)
> PackageArchitec
> SourcePackage: testdrive
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https:/
>