[Bug 1814403] Re: Latest update causes 30 sec. menu delay timeout

2019-02-08 Thread Michael Shannon
Verification-done for bionic using grub2/2.02-2ubuntu8.12 and grub2-signed/1.93.13+2.02-2ubuntu8.12: This fixes this issue for UEFI with /boot/grub on ZFS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1815105] [NEW] 2.02-2ubuntu8.10 breaks booting from ZFS

2019-02-07 Thread Michael Shannon
Public bug reported: Upon upgrading to grub 2.02-2ubuntu8.10 from 2.02-2ubuntu8.9 all of my machines with /boot/grub on ZFS display a long list of the following sort at boot, before reaching the GRUB menu. Handle 0x49cb9b98   /ACPI (a0341d0,0)/PCI (0,14)/USB(9.1)/EndEntire   USB I/O   device

[Bug 1790349] [NEW] package chirp (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/chirpw', which is also in package chirp-daily 20180815~xenial~1

2018-09-02 Thread Michael Shannon
Public bug reported: I upgraded to 18.04 from 16 - and upon attempting to update to the latest version of chirp, I was presented with this bug report. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: chirp (not installed) ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname:

[Bug 1685754] Re: gnome-terminal unduly forces umask=0022

2018-07-05 Thread Michael Shannon
Correction, I believe this is actually a bug in dbus. gnome-terminal, and others are not setting as it should, but as far as I know, dbus cannot support in a systemd environment due to the limitations mentioned in #21. ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New

[Bug 1685754] Re: gnome-terminal unduly forces umask=0022

2018-07-05 Thread Michael Shannon
This is a bug in every GNOME application that uses systemctl --user to start itself. There is currently no sane fix because systemd is missing a feature of upstart, umask inheritance. GNOME could abuse systemd's instantiated services feature to pass the umask through this but this would be far

[Bug 1779736] [NEW] umask ignored on NFSv4.2 mounts

2018-07-02 Thread Michael Shannon
Public bug reported: After upgrading to kernel 4.15.0-24-generic (on Ubuntu 18.04 LTS) NFSv4.2 mounts ignore the umask when creating files and directories. Files get permissions 666 and directories get 777. Therefore, a umask of 000 is seemingly being forced when creating files/directories in