[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-05-11 Thread Rui Salvaterra
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
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1835660

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1844422] Re: WPA3-support

2019-09-28 Thread Rui Salvaterra
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 my connections are downgraded to WPA2.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1844422

Title:
  WPA3-support

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2018-11-02 Thread Rui Salvaterra
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 this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1801325

Title:
  User processes/sessions lingering after logoff

Status in ubuntu-mate:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  Logoff doesn't terminate all user processes/sessions, which means
  after mutiple logon/logoff operations lots of sessions and processes
  are leaking (you can see them with systemctl status). Verified with
  redshift(-gtk), at least. This can be worked around with
  KillUserProcesses=yes on /etc/systemd/logind.conf, but it breaks GNU
  Screen, for example. Tested on 18.04 and 18.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1801325/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp