[Touch-packages] [Bug 2067613] Re: CVE-2024-5290 : Fix loading of arbitrary shared objects
** Also affects: wpa (Debian) Importance: Undecided Status: New ** Changed in: wpa (Debian) Importance: Undecided => High ** Changed in: wpa (Debian) Status: New => Fix Released ** Changed in: wpa (Debian) Assignee: (unassigned) => Andrej Shadura (andrew.sh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2067613 Title: CVE-2024-5290 : Fix loading of arbitrary shared objects Status in wpa package in Ubuntu: Fix Released Status in wpa package in Debian: Fix Released Bug description: Hello team We received a vulnerability report a while back - that lets users load arbitrary shared object files in the context of the wpa_supplicant process running as root in affected Ubuntu systems. TLDR : Upstream released a fix : https://w1.fi/cgit/hostap/commit/?id=c84388ee4c66bcd310db57489eac4a75fc600747 that includes a compile time config for allow-listing a set of shared objects. Details here : `wpa_supplicant` is a binary package of source `wpa` ```sh $ umt search wpa Running search command. Ubuntu packages: Release Version Pocket Component trusty 2.1-0ubuntu1.7 security main trusty/esm 2.1-0ubuntu1.7+esm4 security main xenial 2.4-0ubuntu6.8 security main bionic 2:2.6-15ubuntu2.8 security main focal 2:2.9-1ubuntu4.3security main jammy 2:2.10-6ubuntu2 updates main lunar 2:2.10-12release main mantic 2:2.10-15release main noble 2:2.10-21build4 release main Other packages: Release Version Pocket Component bookworm 2:2.10-12release main bullseye 2:2.9.0-21 release main buster 2:2.7+git20190128+0c1e29f-6+deb10u4 updates main testing 2:2.10-21.1 release main unstable 2:2.10-21.1 release main ``` Upstream - https://w1.fi/cgit upstream examples point to config that lets all users in group `wheel` access the frontend. debian and ubuntu use group membership to control access to D-Bus So in `debian/patches/02_dbus_group_policy.patch` ``` diff --git a/wpa_supplicant/dbus/dbus-wpa_supplicant.conf b/wpa_supplicant/dbus/dbus-wpa_supplicant.conf index e81b495..413c049 100644 --- a/wpa_supplicant/dbus/dbus-wpa_supplicant.conf +++ b/wpa_supplicant/dbus/dbus-wpa_supplicant.conf @@ -9,6 +9,11 @@ + + + + + ``` to allow `netdev` users access to the wpa_supplicant which gets started as a service ``` diff --git a/wpa_supplicant/systemd/wpa_supplicant.service.in b/wpa_supplicant/systemd/wpa_supplicant.service.in index 18cbc11..f02bc15 100644 --- a/wpa_supplicant/systemd/wpa_supplicant.service.in +++ b/wpa_supplicant/systemd/wpa_supplicant.service.in @@ -8,8 +8,11 @@ IgnoreOnIsolate=true [Service] Type=dbus BusName=fi.w1.wpa_supplicant1 -ExecStart=@BINDIR@/wpa_supplicant -u -s -O /run/wpa_supplicant +ExecStart=@BINDIR@/wpa_supplicant -u -s -O "DIR=/run/wpa_supplicant GROUP=netdev" ExecReload=/bin/kill -HUP $MAINPID +Group=netdev +RuntimeDirectory=wpa_supplicant +RuntimeDirectoryMode=0750 [Install] WantedBy=multi-user.target ``` If a user is able to escalate to `netdev` - they will be able to interact with the dbus interface. One of the interface `fi.w1.wpa_supplicant1` lets the user create a network interface via `CreateInterface` - See [`wpas_dbus_handler_create_interface`](http://w1.fi/wpa_supplicant/devel/dbus__new__handlers_8h.html#a4c504285e9504dc5508f35646278f867) `ConfigFile` has configurations for a network interface * for loading an opensc engine with `opensc_engine_path`which is a path to a shared object. See [`opensc_engine_path`](https://w1.fi/wpa_supplicant/devel/structwpa__config.html#a791fade4701a30852dbb2b25866ba359) * for loading a PKCS#11 engine with `pkcs11_engine_path` which is a path to a shared object. See [`pkcs11_engine_path`](https://w1.fi/wpa_supplicant/devel/structwpa__config.html#adf38e52ccfe1b621ef5a18b78b1c3a9e) Both these paths don't check for paths - any arbitrary location - leading to arbitrary code execution. Overall any user within the group `netdev` would be able to load arbitrary shared objects - in the context of a process running as root - granting privilege escalation to `root` The process that loads t
[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
** Bug watch added: Debian Bug tracker #1010603 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010603 ** Also affects: wpa (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010603 Importance: Unknown Status: Unknown ** Changed in: wpa (Debian) Importance: Unknown => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: Unknown Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
** Also affects: wpa (Debian) Importance: Undecided Status: New ** Changed in: wpa (Debian) Importance: Undecided => Wishlist ** Changed in: wpa (Debian) Status: New => Fix Released ** Changed in: wpa (Debian) Assignee: (unassigned) => Andrej Shadura (andrew.sh) -- 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/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Invalid Status in ubiquity source package in Xenial: Confirmed Status in wpa source package in Xenial: Fix Committed Status in wpa package in Debian: Fix Released Bug description: [Impact] Users booting from OEM setup may find that their wireless device is "not ready" as per NetworkManager, because wpasupplicant is not running. This is because the steps taken to start in OEM prepare, before moving to the real system runs systemctl isolate, and wpasupplicant gets caught in the crossfire. [Test case] * Steps to reproduce: 1. Install in OEM mode 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. [Regression potential] The following are examples of possible regression scenarios from this stable update: - Failure to get the wireless device ready at session start - Driver loading issues for the wireless devices - Failure to complete OEM preparation steps, due to the oem user remaining connected while it's being removed by the last steps of the OEM preparation process. [Background information] * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1893563] Re: netplan: can't login to ap mode with psk
Right, my apologies, I was too quick to be angry: I only checked the patch proposed here but not the actual one committed — and apparently I haven’t read the discussion to the end. Having checked the actual package, I see it is in fact a patch from the upstream Git. Still, it’d be great if you could at least notify me, and it would be much better if we could first push such changes into Debian first. -- 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/1893563 Title: netplan: can't login to ap mode with psk Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Committed Status in wpa package in Ubuntu: Fix Released Bug description: I've setup my wifi cards as ap over a bridge using netplan. If I add: auth: key-management: psk password: "testinglang" then my clients are unable to connect. If I remove those lines above in netplan then the clients are able to connect but without a password. If I run wpa_cli -i wlp3s0 status, I get: bssid=4c:1d:96:71:a3:90 freq=2412 ssid=walad2 id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED p2p_device_address=4c:1d:96:71:a3:91 address=4c:1d:96:71:a3:90 uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a I notice that key_mgmt=UNKNOWN. Perhaps that's the problem? Any pointers on how to debug and fix this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.99-0ubuntu3~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 23:11:48 2020 InstallationDate: Installed on 2020-08-16 (14 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1893563] Re: netplan: can't login to ap mode with psk
I’ve just verified and in fact not only this hasn’t been submitted upstream, but the upstream has shipped an alternative implementation of this by Beniamino Galvani (@bengal). I’d really appreciate if Ubuntu didn’t add non-trivial patches without discussion with the upstream and me as the Debian maintainer for this package. -- 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/1893563 Title: netplan: can't login to ap mode with psk Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Committed Status in wpa package in Ubuntu: Fix Released Bug description: I've setup my wifi cards as ap over a bridge using netplan. If I add: auth: key-management: psk password: "testinglang" then my clients are unable to connect. If I remove those lines above in netplan then the clients are able to connect but without a password. If I run wpa_cli -i wlp3s0 status, I get: bssid=4c:1d:96:71:a3:90 freq=2412 ssid=walad2 id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED p2p_device_address=4c:1d:96:71:a3:91 address=4c:1d:96:71:a3:90 uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a I notice that key_mgmt=UNKNOWN. Perhaps that's the problem? Any pointers on how to debug and fix this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.99-0ubuntu3~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 23:11:48 2020 InstallationDate: Installed on 2020-08-16 (14 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1893563] Re: netplan: can't login to ap mode with psk
@seb128, @mhodson, @shemgp, has this patch been submitted to the upstream? -- 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/1893563 Title: netplan: can't login to ap mode with psk Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Committed Status in wpa package in Ubuntu: Fix Released Bug description: I've setup my wifi cards as ap over a bridge using netplan. If I add: auth: key-management: psk password: "testinglang" then my clients are unable to connect. If I remove those lines above in netplan then the clients are able to connect but without a password. If I run wpa_cli -i wlp3s0 status, I get: bssid=4c:1d:96:71:a3:90 freq=2412 ssid=walad2 id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED p2p_device_address=4c:1d:96:71:a3:91 address=4c:1d:96:71:a3:90 uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a I notice that key_mgmt=UNKNOWN. Perhaps that's the problem? Any pointers on how to debug and fix this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.99-0ubuntu3~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 23:11:48 2020 InstallationDate: Installed on 2020-08-16 (14 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
** Bug watch added: Debian Bug tracker #954457 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954457 ** Also affects: wpa (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954457 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Released Status in wpa package in Debian: Unknown Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+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 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
Speaking of which, it would be great if this patch was dropped: - debian/patches/session-ticket.patch: disable the TLS Session Ticket extension to fix auth with 802.1x PEAP on some hardware. This has been superseded by upstream changes a couple of releases ago and is no longer needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Triaged Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+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 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
@racb, it’s been committed to the upstream package in Debian; just a sync is needed. ** Package changed: wpasupplicant (Ubuntu) => wpa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Triaged Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+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 1763611] Re: Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs
I'm also affected by this bug on a normal Ubuntu. Times out the same way in initramfs. Interestingly, this doesn't seem to happen with another installation of Ubuntu here. Cc @vorlon ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1763611 Title: Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs Status in initramfs-tools package in Ubuntu: New Status in ubiquity package in Ubuntu: Fix Released Bug description: See this thread at the Ubuntu Forums: https://ubuntuforums.org/showthread.php?t=2388799 How come the ultra light Lubuntu Bionic needs 40 seconds from the grub menu to the log in screen, while the corresponding Kubuntu and Xubuntu Bionic can do it in 10 seconds in my Toshiba laptop? All the operating systems were installed from the Bionic Beta-2 desktop 64-bit iso files and made up to date today (and reside in a new SSD connected via the internal SATA bay). -o- and to summarize the conclusion https://ubuntuforums.org/showthread.php?t=2388799&page=2&p=13756324#post13756324 This supports the assumption, that there are problems for Lubuntu to manage SSDs with 4096 byte size physical sectors. But the other flavours of Ubuntu can manage it. Let us hope that this can help the Lubuntu developer to find and squash the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lubuntu-desktop 0.93 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Apr 13 09:59:42 2018 InstallationDate: Installed on 2018-04-06 (7 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180405) SourcePackage: lubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1763611/+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 1644975] Re: Resume from disk (swapfile) fails
@superm1, your fix makes the boot process very slow on one of the machines, it takes a minute or more for it to time out waiting for the resume device. People also complain here: https://askubuntu.com/questions/1013830/slow- boot-long-kernel-load-time-due-to-wrong-resume-device -- 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/1644975 Title: Resume from disk (swapfile) fails Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Debian: Incomplete Bug description: Well, hibernation with swap file doesn't work while hibernation with swap partition works perfectly fine with the exactly same configuration and hardware. The reason is that when resuming from swap file, initramfs script can't correctly detect the machine are hibernated from the last shut down. And I investigated the issue and found this patch solved https://bugs.launchpad.net/ubuntu/+source/initramfs- tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the hibernate to work. And it isn't applied to the package. I'd like to help this is really applied to the official package. In short, my setup is swapfile inside the system filesystem (LUKS + LVM2 + ext4). Also, I roughly followed this tutorial to prepare this configurartion that: https://ubuntuforums.org/showthread.php?t=1042946 I've opening this bug because the original bug report is closed and getting no response... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
@cyphermox, has there been any proper solution of this since then? Is the patch still needed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Invalid Status in ubiquity source package in Xenial: Confirmed Status in wpa source package in Xenial: Fix Committed Bug description: [Impact] Users booting from OEM setup may find that their wireless device is "not ready" as per NetworkManager, because wpasupplicant is not running. This is because the steps taken to start in OEM prepare, before moving to the real system runs systemctl isolate, and wpasupplicant gets caught in the crossfire. [Test case] * Steps to reproduce: 1. Install in OEM mode 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. [Regression potential] The following are examples of possible regression scenarios from this stable update: - Failure to get the wireless device ready at session start - Driver loading issues for the wireless devices - Failure to complete OEM preparation steps, due to the oem user remaining connected while it's being removed by the last steps of the OEM preparation process. [Background information] * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
Please also see https://bugs.debian.org/898038 ** Bug watch added: Debian Bug tracker #898038 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898038 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: Confirmed Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Bug description: On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0 liam@liam-lat:~$ ping 172.29.88.11 PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data. ^C --- 172.29.88.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3054ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:11:33 2018 InstallationDate: Installed on 2017-06-15 (258 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+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
