fixing Zesty to use Apple boot selector

Zesty 17.04 x86_64 beta 2, while producing a bootable installation when installed on a MacPro, fails to appear in the Apple boot selector like a Fedora 24/25 installation does. It is trivial to emulate the Fedora approach by installing the mactel-boot-logo_1.0-1~xenial_all.deb and mactel-boot_0

Re: fixing Zesty to use Apple boot selector

On Sat, Apr 1, 2017 at 9:04 AM, Daniel Llewellyn wrote: > > > On 1 April 2017 at 01:10, Jack Howarth > wrote: >> >> sudo mkdir -p /boot/efi/System/Library/CoreServices >> sudo install -m 644 /usr/share/mactel-boot/SystemVersion.plist >> /boot/efi/System/Lib

Re: fixing Zesty to use Apple boot selector

On Sat, Apr 1, 2017 at 11:25 AM, Jack Howarth wrote: > On Sat, Apr 1, 2017 at 9:04 AM, Daniel Llewellyn wrote: >> >> >> On 1 April 2017 at 01:10, Jack Howarth >> wrote: >>> >>> sudo mkdir -p /boot/efi/System/Library/CoreServices >>> sudo ins

Re: fixing Zesty to use Apple boot selector

On Sat, Apr 1, 2017 at 11:31 AM, Jack Howarth wrote: > On Sat, Apr 1, 2017 at 11:25 AM, Jack Howarth > wrote: >> On Sat, Apr 1, 2017 at 9:04 AM, Daniel Llewellyn wrote: >>> >>> >>> On 1 April 2017 at 01:10, Jack Howarth >>> wrote: >>>&

Re: fixing Zesty to use Apple boot selector

On Sat, Apr 1, 2017 at 9:04 AM, Daniel Llewellyn wrote: > > > On 1 April 2017 at 01:10, Jack Howarth > wrote: >> >> sudo mkdir -p /boot/efi/System/Library/CoreServices >> sudo install -m 644 /usr/share/mactel-boot/SystemVersion.plist >> /boot/efi/System/Lib

RE: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

Is there any official word from the Ubuntu kernel maintainers about their response to this issue just announced on the Debian mailing lists? https://lists.debian.org/debian-devel/2017/06/msg00308.html My understanding from System76 was that they expected this issue to be fixed with a kernel updat

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

. Jack On Mon, Jun 26, 2017 at 6:20 PM, C de-Avillez wrote: > On Mon, 26 Jun 2017 17:48:26 -0400 > Jack Howarth wrote: > >> Is there any official word from the Ubuntu kernel maintainers about >> their response to this issue just announced on the Debian mailing

default gcc in artful

Are there any plans to switch the default gcc in artful to gcc-7? Or is there some fix in the upcoming gcc 7.2 release that is required for that change? Jack -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https:/

Dropbox menu bar entry vs Artful

Does anyone know why under Artful Aardvark, the current 2015.10.28-1ubuntu2 release of nautilus-Dropbox doesn't produce the Dropbox menu bar entry? Is that that feature limited to the deprecated Ubuntu Desktop menu bar? Otherwise, Dropbox functionality appears to be fully functional with the Files

8.0.32-1ubuntu1.3~ppa2 patches not in tomcat8 8.0.32-1ubuntu1.4

Is there a reason that the patches present in the test tomcat8 8.0.32-1ubuntu1.3~ppa2 were dropped from tomcat8 8.0.32-1ubuntu1.4? I ask because the Metaboanalyst server war has been broken under the ubuntu tomcat7 and tomcat8 for quire some time and this is widely reported by end users... http

Re: 8.0.32-1ubuntu1.3~ppa2 patches not in tomcat8 8.0.32-1ubuntu1.4

alyst war application properly. Jack On Thu, Jul 27, 2017 at 4:23 PM, Nish Aravamudan < nish.aravamu...@canonical.com> wrote: > On Thu, Jul 27, 2017 at 12:00 PM, Robie Basak > wrote: > > On Thu, Jul 27, 2017 at 09:48:06AM -0400, Jack Howarth wrote: > >&g

Re: 8.0.32-1ubuntu1.3~ppa2 patches not in tomcat8 8.0.32-1ubuntu1.4

er tomcat8 as its user work fine on MacOS so this failure on ubuntu is all very confusing. Also note that Rutter's R and cran's have to be used since current Bioconductor requires R 3.4. On Thu, Jul 27, 2017 at 8:14 PM, Nish Aravamudan < nish.aravamu...@canonical.com> wrote: &

Re: 8.0.32-1ubuntu1.3~ppa2 patches not in tomcat8 8.0.32-1ubuntu1.4

Rserve) > Rserve() and finally deploy the MetaboAnalyst.war in glassfish4 that the URL http://localhost:8080/MetaboAnalyst/ works fine under glassfish4. On Thu, Jul 27, 2017 at 8:14 PM, Nish Aravamudan < nish.aravamu...@canonical.com> wrote: > On Thu, Jul 27, 2017 at 5:04 PM, Jack Ho

Re: Proposal: Let's drop i386

I am not sure of the status of the following issue as I no longer have access to hardware to test the issue against current ubuntu. https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1647184 however supporting mixed-mode systems, 64-bit system with 32-bit UEFI, like Debian Jessie 8.0's multi-a

nvidia-340 incapable of single user mode in 20.04

I am finding on a 2008 MacPro with GTX680 that the installation of the nvidia-340 package under Ubuntu 20.04 prevents single user mode boots from working. While the nvidia-340 driver works fine from a normal boot, when 'single' is added before 'quiet' in the grub kernel arguments, the boot pr

booting into recovery mode hangs under 20.04

On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery mode from grub hangs on loading of the ramdisk with the Recovery Menu dialog never appearing. This problem doesn't exist for a fresh install of Ubuntu 18.04 updated to the current package updates. In that case, the Recovery Men

Re: nvidia-340 incapable of single user mode in 20.04

reading this right: > https://www.nvidia.com/Download/driverResults.aspx/159360/en-us > - Dan > > On Fri, Apr 24, 2020 at 4:30 PM Dimitri John Ledkov > wrote: > >> On Mon, 20 Apr 2020 at 20:53, Jack Howarth >> wrote: >> > >> > I am finding

23.10 Help window blank

I have found that, from either a dist-upgrade from 23.04 to 23.10 or a clean install of 23.10, the Help application produces a blank window. Oddly, if you run Help from the 23.10 from the installer image, the Help application properly populates its window with expected content. A comparison of the