[Bug 1895912] Re: grub2 does not boot kernels built without CONFIG_EFI_STUB

Is this bug going to be fixed at all? It's been almost two years. It's extremely annoying having to bloat custom kernel builds with EFI stub support just to be able to boot them. ubuntu-Make-the-linux-command-in- EFI-grub-always-try.patch is broken, as this problem does NOT happen on pure Debian.

[Bug 1835660] Re: initramfs unpacking failed

Running 20.04 here, and I've also noticed the same message. Maybe a useful data point: I only see this on UEFI machines, my traditional BIOS machines seem unaffected. Could it be something related to GRUB on UEFI? -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1844422] Re: WPA3-support

Indeed. 19.04 shipped with wpasupplicant 2.6, which had no support at all for WPA3, although network-manager 1.16 already started to support it. With 19.10 shipping wpasupplicant 2.9 and network-manager 1.20, there's just no excuse. I have WPA2+WPA3 mixed-mode deployed on my home network and all

[Bug 1637988] Re: Enable the nfs backend

Hi again, Łukasz I dist-upgraded the cosmic-proposed packages, tried browsing a couple of nfs shares and it worked perfectly on caja. I suppose nautilus will work fine too. Thanks, Rui -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1637988] Re: Enable the nfs backend

Hi, Łukasz I will gladly help testing it when the packages hit cosmic-proposed. By the way, I'm not using nautilus anymore (I migrated to MATE), but I'm assuming caja will work just fine. Thanks, Rui -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1801325] Re: User processes/sessions lingering after logoff

Note that I filed this under ubuntu-mate because I only verified this behaviour under MATE, so I assumed it could be a mate-session-manager issue. Of course, I suspect it's really a systemd-logind problem, but I thought it might be wise to give it the benefit of the doubt… ;) -- You received

[Bug 1637988] Re: gvfsd-nfs not present in gvfs-backends, why?

Ok, according to the changelog at http://changelogs.ubuntu.com/changelogs/pool/main/g/gvfs/gvfs_1.30.3-1ubuntu1/changelog, the problem is libnfs being in universe. Why is it not available in main? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1637988] Re: gvfsd-nfs not present in gvfs-backends, why?

The fact that the requirements are met is exactly what made me file the bug in the first place. It's a huge usability failure, and dismissing it as "wishlist" without any further explanation is quite perplexing. :/ -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1637988] [NEW] gvfsd-nfs not present in gvfs-backends, why?

Public bug reported: We're at the end of 2016 and it's still impossible to browse nfs shares through nautilus, even though this is supported since version 1.23 of gvfs. What's keeping gvfsd-nfs out of the gvfs-backends package? ** Affects: gvfs (Ubuntu) Importance: Undecided

[Bug 1299499]

I'd love to see this one fixed, I also have an Arrandale/Ironlake (Core-i3 380M) laptop stuck at Linux 3.13 because of this bug... :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299499 Title: