Ubuntu 18.04: apt hangs during build of FWTS driver, Secure Boot enabled

[Paul English]

I know - I'm breaking threading for everyone. :-/

Continuing to use the devel repo - 18.06.03, leaving Secure Boot enabled.

I tried typing in a password blindly and double-enter. I also tried password, enter, re-type password, enter just in case - no luck.

FWIW force-closing the terminal leaves the apt process orphaned, so a kill -9 is really needed.

I'm a little less familiar with the GUI tools (which isn't saying much!), but "Software & Updates" - on Ubuntu Mate edition, at least, didn't readily show me fwts as something I could install. 

However - Synaptic did! Huzzah!

I got a nice GUI dialog asking me for the password, and explaining that it will be used for Secure Boot and asked after a reboot. It also corrected me when I attempted to use a passphrase (limit 16 characters!). Oops. 

After reboot, I was not at any point prompted for the Secure Boot password I set.

fwts -b works as it should

================

Hi Fisher,

DKMS will be auto signed on 18.04 when secureboot is enabled. I believe 
the problem is a dialogue requesting to set a password never be popped 
up. A workaround given was when the installation gets stuck, type a 
password in the terminal blindly and press return twice. Or if you force 
close the terminal, you could try to run "Software & updates", the 
dialogue should pop up.


Cheers,
Ivan


On 07/10/2018 07:15 AM, Blibbet wrote:
> Hi,
> 
> A friend was just trying to install FWTS on a Ubuntu 18.04 system. They said that apt hangs when trying to install FWTS.
> 
> It hangs during the build of the kernel module.
> 
> Output from 'ps -eaf' includes:
> 
> root      4541  4512  0 11:56 pts/1    00:00:00 whiptail --backtitle Package configuration --title Configuring Secure Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot enabled.  UEFI Secure Boot requires additional configuration to work with third-party drive
> 
> When Secure Boot was disabled, then FWTS was able to successfully install.
> 
> Should there not be some dialog that hints to user that they need to disable Secure Boot?
> 
> Is this a new change in Ubuntu Secure Boot policy that is causing this?
> 
> Thanks for any additional information.
> 
> Thanks,
> Lee Fisher
> 
>