[Bug 1937110] Re: dhcp option 121 & 249

2022-05-19 Thread Mathew Binkley
I just wanted to say that we are also hitting the same problem (lack of dhcp option 121/249). So Subiquity connects to the network, but can't get a default route and thus fails. Couple this with the removal of debian-installer support from Ubuntu, and we can no longer install Ubuntu Jammy LTS.

[Bug 1973654] [NEW] Using debian-installer on a server with a Let's Encrypt cert dies

2022-05-16 Thread Mathew Binkley
Public bug reported: While using debian-installer to install Ubuntu Focal, I get the following error: May 16 22:02:41 base-installer: Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the

[Bug 1798162] Re: VLC failed after attempt to open a video file

2018-11-17 Thread Mathew Binkley
Tagging this as I'm seeing the same. Running Cosmic 18.10 64-bit in a VirtualBox 5.2.22r126460 (latest stable). It complains about "Failed to open VDPAU backend libvdpau_nvidia.so" even though I don't have any nvidia drivers or Ubuntu packages installed (it's using the VirtualBox video

[Bug 400750] Re: Building ATLAS on Intel Xeon E5520 crashes machine

2009-07-28 Thread Mathew Binkley
In addition to ATLAS, I have found the machine crashes occasionally (not nearly as predictably though) while compiling a kernel or running ACML- GPU demos. Jaunty latest kernel and CentOS 5.3 kernel both have the vulnerabilty, while Fedora Core 11 does not. I've done further testing, and the

[Bug 400750] Re: Building ATLAS on Intel Xeon E5520 crashes machine

2009-07-28 Thread Mathew Binkley
I forgot to add this before, but the xprobe error messages I mentioned in the initial bug report are red herrings. The kernel crashes some time after those error messages are generated. -- Building ATLAS on Intel Xeon E5520 crashes machine https://bugs.launchpad.net/bugs/400750 You received