[Bug 1844422] Re: WPA3-SAE support
@Seb128 Alright, thank you for you guidance, I'll open a new bug for NM-Applet ** No longer affects: network-manager-applet (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844422] Re: WPA3-SAE support
It didn't work before, the password field being 'missing in action' is something that started when I enabled WPA3 on my AP/Router and has persisted. I think WPA3 in general doesn't fully work with NM-Applet as of yet. I am able to connect using WPA3 via via NMTUI, after which NM-Applet, for instance, shows Security as "None". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844422] Re: WPA3-SAE support
So there's a bit more work to this than i stated yesterday: https://gitlab.gnome.org/GNOME/network-manager-applet/commits/master?utf8=%E2%9C%93=sae -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844422] Re: WPA3-SAE support
@Seb128, Sorry to bother you again, but I've noticed some (at least for me) unexpected fallout from this bug. Using Xubuntu Eoan with 20.4-2ubuntu2 from proposed. When connecting to my Wi-Fi network (which is set to WPA2/WPA3 mixed mode) using NM-Applet (the GUI not NMTUI) it will show the authn dialog but the Wi-Fi password field is missing. I've attached a screenshot depicting the Issue. If I'm not mistaken, the following commit fixes this issue: https://gitlab.gnome.org/GNOME/network-manager-applet/commit/1272e7fa2e976ac5db6352302962aba439ce6dd7 ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+attachment/5297059/+files/NM-Applet-fail.png ** Also affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844422] Re: WPA3-SAE support
@seb128 >From a functional point of view, it is working now. I'm able to connect to my AP with WPA3-SAE/WPA3-Personal using 1.20.4-2ubuntu2 from proposed. Although I'm unable to comment on the gnome-shell part of this bug since i'm using XFCE. Thanks for helping out. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844422] Re: WPA3-SAE support
@teunis, The point is NM (when setting WPA3-Personal as the security protocol) will ALWAYS pass "ieee80211w=0" this is NOT configurable on the client even when setting PMF=2 in the config file. The latest commit fixes this problem and thus is kind of important to achieving the goal as set out in this bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844422] Re: WPA3-SAE support
@seb128 The Current version will not connect to WPA3-SAE secured Wi-Fi without that commit (being able to connect to WPA3-personal secured Wi-Fi is the whole point of this bug). This is because 802.11w is mandatory for WPA3-SAE (though it can be disabled for certain configs) and NetworkManager up and until 1.20.4 passes "ieee80211w=0" (which disables 802.11w). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844422] Re: WPA3-SAE support
** Description changed: 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/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 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. + + == + Update 09-10-2019: + So it has come to my attention that NetworkManager needs one additional commit backported from upstream to make WPA3-SAE work: + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08 + + Without this latest commit connecting to WPA3-personal networks will + still fail because of a lack of 802.11w support in the network-manager + settings. ** Changed in: network-manager (Ubuntu) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844422] Re: WPA3-SAE support
Relevant commit made upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Running a Quadro M2000M here. ubuntu-drivers-common ver. 1:0.5.2.1 fixes the issue for me. The dGPU fan is of and -according to powertop the dGPU draws zero power when using Intel iGPU. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783511] [NEW] gvfsd-metadata extreme log spamming
Public bug reported: Hello, I'm Using Ubuntu 18.04 LTS everytime i browse our mounted CIFS / SMB share or open a file Journald fills up with the following messages: jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
