[Touch-packages] [Bug 2039340] Re: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries
No local extensions are installed. Only the default system extensions d...@rastersift.com and ubuntu-d...@ubuntu.com are installed following https://askubuntu.com/questions/1133782/command-to-list-installed-and- enabled-gnome-extensions. XFCE4 is now also broken so I'm without a GUI for the moment. I did try with a blank new user and they have no such issues. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2039340 Title: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries Status in Ubuntu: New Status in apparmor package in Ubuntu: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: Last time I hacked around a bug like this, it had portions in PAM, apparmor, Seahorse, and Gnome so this time I'd like someone more focused on broad stability to look at things. The problem is simple. Before the upgrade to 23.10, I could log in using the "Ubuntu", "Ubuntu on X.org". "Gnome", and "Gnome on X.org" WMs. Now I can't. I can still login using XFCE and TTY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2039340/+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 2039611] [NEW] [SRU] Fix fcc-unlock script for Lenovo X13s
Public bug reported: [ Impact ] Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon 8cx, come with an integrated 4G/5G modem. The modem on the X13s is manufactured by foxconn, and is based on the Qualcomm Snapdragon X55 PCIe modem. Here is the output of mmcli -m 0 on an X13s Hardware |manufacturer: foxconn | model: Qualcomm Snapdragon X55 5G | firmware revision: T99W175.F0.6.0.0.6.OG.005 | 045 1 [Feb 03 2023 10:00:00] All Linux kernel drivers are upstream to support this data modem, and included in the Ubuntu kernel for mantic. The support for this modem is also merged in modemmanager, including the fcc-unlock script for this modem model (https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22). We are however missing the symlink for the specific PCIe ID link reported on the X13s for this modem, which is shown by lspci as: 0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] [105b:e0c3] This is already fixed upstream with https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838. With the backport of this patch the modem on the X13S can be enabled by laptop users using the fcc-unlock generic guidelines. And mobile broadband is working out of the box. Without it, the modem won't work. [ Test Plan ] Without the ability to FCC unlock this modem model, any attempt to enable/start the modem will fail / stall, as detailed on https://modemmanager.org/docs/modemmanager/fcc-unlock/. With this backport/fix, the Ubuntu Mobile network settings/UI can be used to enabled the modem, unlock the SIM card and connect to the 4G/5G network (assuming the user has a SIM card with an appropriate data plan). [ Where problems could occur ] The patch is fairly isolated change. The purpose of this change is to create an additional symlink in /usr/share/ModemManager/fcc- unlock.available.d/ whose name is the PCIe ID of this specific device. PCIe IDs are documented here: https://cateee.net/lkddb/web- lkddb/MHI_BUS.html. Also links in this folder have no effect on the system, unless the user manually enable the appropriate fcc unlock script, typically by adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate modem model script. [ Other Info ] I am working on a debdiff, and will upload shortly ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2039611 Title: [SRU] Fix fcc-unlock script for Lenovo X13s Status in modemmanager package in Ubuntu: New Bug description: [ Impact ] Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon 8cx, come with an integrated 4G/5G modem. The modem on the X13s is manufactured by foxconn, and is based on the Qualcomm Snapdragon X55 PCIe modem. Here is the output of mmcli -m 0 on an X13s Hardware |manufacturer: foxconn | model: Qualcomm Snapdragon X55 5G | firmware revision: T99W175.F0.6.0.0.6.OG.005 | 045 1 [Feb 03 2023 10:00:00] All Linux kernel drivers are upstream to support this data modem, and included in the Ubuntu kernel for mantic. The support for this modem is also merged in modemmanager, including the fcc-unlock script for this modem model (https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22). We are however missing the symlink for the specific PCIe ID link reported on the X13s for this modem, which is shown by lspci as: 0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] [105b:e0c3] This is already fixed upstream with https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838. With the backport of this patch the modem on the X13S can be enabled by laptop users using the fcc-unlock generic guidelines. And mobile broadband is working out of the box. Without it, the modem won't work. [ Test Plan ] Without the ability to FCC unlock this modem model, any attempt to enable/start the modem will fail / stall, as detailed on https://modemmanager.org/docs/modemmanager/fcc-unlock/. With this backport/fix, the Ubuntu Mobile network settings/UI can be used to enabled the modem, unlock the SIM card and connect to the 4G/5G network (assuming the user has a SIM card with an appropriate data plan). [ Where problems could occur ] The patch is fairly isolated change. The purpose of this change is to create an additional
Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
I doubt the kernel but a standard desktop install should have given you the hwe kernel so something isn't right. There is no way you should get this problem running Firefox in a standard desktop install. The bug is mostly due to non standard logins and certainly a standard Ubuntu install delivers snaps that work. On Wed, 18 Oct 2023, 04:15 Janus Kobain, <1951...@bugs.launchpad.net> wrote: > Tim, this is a desktop installation of 22.04 LTS, I simply followed > where package updates led me. > > After installing linux-generic-hwe-22.04-edge package: > $ snap --version > snap2.60.4 > snapd 2.60.4 > series 16 > ubuntu 22.04 > kernel 6.2.0-36-generic > > $ firefox; chromium-browser > /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-97c582ae-0a89-4dc4-bef2-1a400d8b1688.scope > is not a snap cgroup > /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-97c582ae-0a89-4dc4-bef2-1a400d8b1688.scope > is not a snap cgroup > > Is the problem still in the kernel version? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1951491 > > Title: > Can't run snaps: .slice/session-1.scope is not a snap cgroup > > To manage notifications about this bug go to: > https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions > > -- 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 2039592] [NEW] no connection via SIM card
Public bug reported: Ubuntu 22.04 I can’t connect to the Internet via a SIM card. I can see how the Measurement Manager is being developed and the plugin is installed.. I'll add a module: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so) manager: rfkill: WWAN is jammed with radio; I'll become a file. the driver does not load!!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 19:40:10 2023 InstallationDate: Installed on 2023-10-03 (13 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) IpRoute: default via 192.168.43.63 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.43.0/24 dev wlo1 proto kernel scope link src 192.168.43.83 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlo1 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 ONEPLUS_A5000_co_aptsvo 174d782e-8952-4921-b779-adbd0266fe27 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled enabled enabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2039592 Title: no connection via SIM card Status in network-manager package in Ubuntu: New Bug description: Ubuntu 22.04 I can’t connect to the Internet via a SIM card. I can see how the Measurement Manager is being developed and the plugin is installed.. I'll add a module: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so) manager: rfkill: WWAN is jammed with radio; I'll become a file. the driver does not load!!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 19:40:10 2023 InstallationDate: Installed on 2023-10-03 (13 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) IpRoute: default via 192.168.43.63 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.43.0/24 dev wlo1 proto kernel scope link src 192.168.43.83 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlo1 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 ONEPLUS_A5000_co_aptsvo 174d782e-8952-4921-b779-adbd0266fe27 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled enabled
[Touch-packages] [Bug 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1
The bugfix was staged for the "devel" series, as the archive is still frozen: https://git.launchpad.net/network-manager/log/ I'm uploading this into Mantic: https://git.launchpad.net/network- manager/log/?h=ubuntu/mantic ** Description changed: + [ Impact ] + + * A failure to query nmcli will fail the network-manager.postinst + maintainer script (using "set -e") + + * This will make the package installation/upgrade fail + + * The fix catches the error on "ORIG_NAME=$(nmcli --get-values + connection.id con show "$UUID")" and skips the corresponding keyfile + with a warning message + + [ Test Plan ] + + $ sudo vim /etc/NetworkManager/system-connections/UPTOWN.guests # bad file + [connection] + id=UPTOWN.guests + uuid=491fa5c8-68ef-4140-8679-dca422f5c262 + type=wifi + + [wifi] + ssid=UPTOWN.guests + mode=infrastructure + mac-address=E0:9D:31:09:84:54 + + [ipv6] + method=auto + + [ipv4] + method=auto + + $ sudo vim /etc/NetworkManager/system-connections/aaaUPTOWN # good file + [connection] + id=aaaUPTOWN + uuid=491fa5c8-68ef---dca422f5c262 + type=wifi + + [wifi] + ssid=aaaUPTOWN + mode=infrastructure + mac-address=E0:9D:31:09:84:54 + + [ipv6] + method=auto + + [ipv4] + method=auto + + $ sudo chmod 600 /etc/NetworkManager/system-connections/*UPTOWN* + $ sudo nmcli con reload + $ ls -la /etc/NetworkManager/system-connections/ + total 32 + drwxr-xr-x 2 root root 12288 Oct 17 17:51 ./ + drwxr-xr-x 7 root root 12288 Oct 17 17:46 ../ + -rw--- 1 root root 199 Oct 17 17:05 UPTOWN.guests + -rw--- 1 root root 191 Oct 17 17:46 aaaUPTOWN + + # Install network-manager from proposed + $ apt update && apt install -t mantic-proposed network-manager # version 1.44.0-1ubuntu2.1 + + # Verify you don't see an error like this, breaking the pkg install + Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. + dpkg: error processing package network-manager (--configure): + installed network-manager package post-installation script subprocess returned error exit status 10 + + # Verify you see a migration log like this and the package installation is successful: + Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. + SKIP: UPTOWN.guests (491fa5c8-68ef-4140-8679-dca422f5c262) unknown to NetworkManager. + Migrating aaaUPTOWN (491fa5c8-68ef---dca422f5c262) to /etc/netplan + $ echo $? + 0 + + # Verify the good profile got migrated, while the bad one remains: + $ sudo grep -RH UPTOWN /etc/netplan/ + /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml: "aaaUPTOWN": + /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml: name: "aaaUPTOWN" + /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:name: "aaaUPTOWN" + $ ls -la /etc/NetworkManager/system-connections/ + insgesamt 28 + drwxr-xr-x 2 root root 12288 Okt 17 18:03 . + drwxr-xr-x 7 root root 12288 Okt 17 17:46 .. + -rw--- 1 root root 199 Okt 17 17:05 UPTOWN.guests + + + [ Where problems could occur ] + + * Think about what the upload changes in the software. Imagine the change is +wrong or breaks something else: how would this show up? + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This must '''never''' be "None" or "Low", or entirely an argument as to why +your upload is low risk. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [ Other Info ] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + + === original bug description === + lunar to mantic upgrade, exciting to see output from network-manager postinst migrating connections to /etc/netplan one by one. But then: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): - installed network-manager package post-installation script subprocess returned error exit status 10 + installed network-manager package post-installation script subprocess returned error exit status 10 That UUID appears in a file /etc/NetworkManager/system- connections/UPTOWN.guests that hasn't been touched since 2015. Contents of the file were: [connection] id=UPTOWN.guests uuid=491fa5c8-68ef-4140-8679-dca422f5c262 type=wifi [wifi] ssid=UPTOWN.guests mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto - I've removed it from disk and the migration continued to completion. Then I got another failure on: [connection] id=belkin.1e4.guests
[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Tim, this is a desktop installation of 22.04 LTS, I simply followed where package updates led me. After installing linux-generic-hwe-22.04-edge package: $ snap --version snap2.60.4 snapd 2.60.4 series 16 ubuntu 22.04 kernel 6.2.0-36-generic $ firefox; chromium-browser /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-97c582ae-0a89-4dc4-bef2-1a400d8b1688.scope is not a snap cgroup /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-97c582ae-0a89-4dc4-bef2-1a400d8b1688.scope is not a snap cgroup Is the problem still in the kernel version? -- 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 2038650] Re: crash reports not sent to the Error Tracker
Verified in a fresh Lunar VM. ** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2038650 Title: crash reports not sent to the Error Tracker Status in apport package in Ubuntu: Fix Released Status in apport source package in Lunar: Fix Committed Status in apport source package in Mantic: Fix Released Bug description: [ Impact ] Crash reports aren't sent in when going through the UI, unless the user looks at the crash details. [ Test Plan ] 0) Make sure that error reporting is set to manual in the system settings (in Privacy screen) 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog. DO NOT look at the details of the report. 4) ls -lh /var/crash/*xeyes* There should be 3 files: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded [ Where problems could occur ] If the patch is wrong, we actually see similar bugs for other UI paths, e.g. ticking the "Remember this" box, etc. I tried to cover them during manual testing but I might have missed some. [ Other Info ] If possible I'd like for us not to wait too long for this to mature in -proposed, as this would affect crashes during the upgrade. [ Original report ] From what I can tell when I click the send button to send a crash report to the Error Tracker the crash doesn't actually get sent. My testing process follows: 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog 4) ls -lh /var/crash I would expect there to be three files in /var/crash: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded However, after step #4 I'm only seeing the .crash file and not a .upload or .uploaded. I was able to get the .upload and .uploaded files created if I chose to "View Report" and then click "Send". It's worth noting though that I did notice the size of the .crash file increase after clicking "Send" so some post-processing was done. ProblemType: BugDistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 +0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 12:12:46 2023 InstallationDate: Installed on 2022-01-07 (637 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+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 2039411] Re: Addition of ppa repository failing intermittently
The root cause of this is "Launchpad API randomly returns empty
responses" https://bugs.launchpad.net/launchpad/+bug/2039251
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2039411
Title:
Addition of ppa repository failing intermittently
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
I get following error intermittently when trying to add ppa repository:
$ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports
Cannot add PPA: 'ppa:~longsleep/ubuntu/golang-backports'.
The user named '~longsleep' has no PPA named 'ubuntu/golang-backports'
Please choose from the following available PPAs:
* 'bcmwl': bcmwl
* 'couchdb': Apache CouchDB
* 'couchdb-precise-backport': Apache CouchDB with Erlang 18 for precise
* 'createrepo-backports': Createrepo Backports
* 'firehol-backports': Firehol Backports
* 'golang-backports': Golang Backports
* 'golang-backports-dev': Golang Backports Dev
* 'iridium-browser-dev': Iridium Browser Dev dependencies
* 'pixel-extras': Pixel extras
* 'python2.7-backports': Python 2.7 Backports
* 'python3-m2crypto-backports': Python 3 M2Crypto backports
* 'stuff': Stuff
* 'ubuntu-pine64-flavour-makers': Ubuntu Pine64 Makers PPA
After multiple attempts, it may succeed, but the same above command sometimes
may return following error as well (intermittently):
$ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 137, in
shortcut = shortcut_handler(line)
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
885, in shortcut_handler
ret = factory(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 469,
in shortcut_handler
return PPAShortcutHandler(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 426,
in __init__
info = get_ppa_info(self.shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 392,
in get_ppa_info
_get_suggested_ppa_message(user, ppa))
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 349,
in _get_suggested_ppa_message
lp_user = get_info_from_lp(LAUNCHPAD_USER_API % user)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 104,
in get_info_from_lp
return get_info_from_https(lp_url, True)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98,
in get_info_from_https
return json.loads(data)
File "/usr/lib/python3.8/json/__init__.py", line 357, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.8/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.8/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2039411/+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 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1
Right. The .guests suffix seems to be a problem here. But I don't know which suffixes are accepted/ignored now and in the future, so I'd avoid changing file names, as that will probably get us into other issues down the road (e.g. overwriting an already existing file of that new name). -- 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/2039503 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 Status in network-manager package in Ubuntu: New Status in network-manager source package in Mantic: New Bug description: [ Impact ] * A failure to query nmcli will fail the network-manager.postinst maintainer script (using "set -e") * This will make the package installation/upgrade fail * The fix catches the error on "ORIG_NAME=$(nmcli --get-values connection.id con show "$UUID")" and skips the corresponding keyfile with a warning message [ Test Plan ] $ sudo vim /etc/NetworkManager/system-connections/UPTOWN.guests # bad file [connection] id=UPTOWN.guests uuid=491fa5c8-68ef-4140-8679-dca422f5c262 type=wifi [wifi] ssid=UPTOWN.guests mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto $ sudo vim /etc/NetworkManager/system-connections/aaaUPTOWN # good file [connection] id=aaaUPTOWN uuid=491fa5c8-68ef---dca422f5c262 type=wifi [wifi] ssid=aaaUPTOWN mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto $ sudo chmod 600 /etc/NetworkManager/system-connections/*UPTOWN* $ sudo nmcli con reload $ ls -la /etc/NetworkManager/system-connections/ total 32 drwxr-xr-x 2 root root 12288 Oct 17 17:51 ./ drwxr-xr-x 7 root root 12288 Oct 17 17:46 ../ -rw--- 1 root root 199 Oct 17 17:05 UPTOWN.guests -rw--- 1 root root 191 Oct 17 17:46 aaaUPTOWN # Install network-manager from proposed $ apt update && apt install -t mantic-proposed network-manager # version 1.44.0-1ubuntu2.1 # Verify you don't see an error like this, breaking the pkg install Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess returned error exit status 10 # Verify you see a migration log like this and the package installation is successful: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. SKIP: UPTOWN.guests (491fa5c8-68ef-4140-8679-dca422f5c262) unknown to NetworkManager. Migrating aaaUPTOWN (491fa5c8-68ef---dca422f5c262) to /etc/netplan $ echo $? 0 # Verify the good profile got migrated, while the bad one remains: $ sudo grep -RH UPTOWN /etc/netplan/ /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml: "aaaUPTOWN": /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml: name: "aaaUPTOWN" /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:name: "aaaUPTOWN" $ ls -la /etc/NetworkManager/system-connections/ insgesamt 28 drwxr-xr-x 2 root root 12288 Okt 17 18:03 . drwxr-xr-x 7 root root 12288 Okt 17 17:46 .. -rw--- 1 root root 199 Okt 17 17:05 UPTOWN.guests [ Where problems could occur ] * Think about what the upload changes in the software. Imagine the change is wrong or breaks something else: how would this show up? * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This must '''never''' be "None" or "Low", or entirely an argument as to why your upload is low risk. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance === original bug description === lunar to mantic upgrade, exciting to see output from network-manager postinst migrating connections to /etc/netplan one by one. But then: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess returned error exit status 10 That UUID appears in a file /etc/NetworkManager/system- connections/UPTOWN.guests that hasn't been touched since 2015. Contents of the file were: [connection] id=UPTOWN.guests
[Touch-packages] [Bug 1990379] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2023-10-17 10:45 EDT--- Fix has been released to Focal, Jammy and Kinetic. With 22.10 being out of service, we can close the bug. ==> Changing the status to: "CLOSED" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: In Progress Status in zlib source package in Focal: Triaged Status in zlib source package in Jammy: Triaged Status in zlib source package in Kinetic: Won't Fix Bug description: SRU Justification: -- [ Impact ] * The zlib function inflate() does not update strm.adler in case DFLTCC is used. * This issue was exposed by Java Certification Kit (JCK) running on z15 hardware and newer and impacts all JDK versions (8,11,17, etc.) that use the system default settings. * The JCK failure impacts the ability to certify Java SDKs on this platform/Linux-distribution combination. * On top the incorrect alder32 result may cause functional issues with Java applications that depend on the result. [ Test Plan ] * An affected Ubuntu release (20.04, 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that makes use of the zlib1g library or run the Java Certification Kit. * Test will be done by IBM. [ Where problems could occur ] * The patch is a one-line change: https://launchpadlibrarian.net/626003193/410-lp1990379.patch and there are not many issues to expect. * There could be a potential problem with the adler field in the strm struct. For example in case the struct is not as assumed or contains and unexpected value, which would then ripple through the other fields, too. * Structural changes could be identified with a test build that was done for all affected Ubuntu releases and for all major architectures: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 [ Other Info ] * The patch itself is the same for all zlib version in 20.04, 22.04 and 22.10 - no further adjustments were needed. * This bug (LP#1990379) is solved in combination with LP#1982583, so that only one package update is needed. However, this bug affects Kinetic, jammy and Focal, but LP#1982583 only Jammy and Kinetic. * The debdiffs for Kinetic and Jammy should be taken from LP#1982583, and the remaining debdiff for Focal from here. __ == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. --- External link: https://warthogs.atlassian.net/browse/PEI-28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+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 2034986] Re: some text became unreadable during a distribution upgrade
Since this bug fix cannot be properly verified for Mantic until the archive is open for the next release, I have temporarily reverted this change in my last upload so that we can proceed with the fix in bug 2039356 for now. Edit: By "this change", I mean the most recent change related to this bug which was uploaded in 1:23.10.11. ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: Fix Committed => In Progress ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Assignee: Gunnar Hjalmarsson (gunnarhj) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Committed Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 2032851] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1
Targetted to the Focal series and removed the ~ubuntu-sponsors team, as the debdiff got already sponsored into Focal and does not affect the newer series (Jammy+): https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=apparmor ** Changed in: apparmor (Ubuntu Focal) Assignee: (unassigned) => Georgia Garcia (georgiag) ** Changed in: apparmor (Ubuntu Focal) Status: New => In Progress ** Changed in: apparmor (Ubuntu) Status: In Progress => Fix Released ** Changed in: apparmor (Ubuntu Focal) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2032851 Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Focal: In Progress Bug description: [ Impact ] * During an apparmor package upgrade, the cache files were deleted, but there could also be directories under /etc/apparmor.d/cache/ which the pre installation scripts did not account for. The upgrade would then fail with the following error message because it would not be able to remove the directories: package:apparmor:2.12-4ubuntu5.3 Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ... rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory dpkg: error processing archive /tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack): new apparmor package pre-installation script subprocess returned error exit status 1 ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1 [ Test Plan ] * On a bionic machine, create a directory under /etc/apparmor.d/cache sudo mkdir /etc/apparmor.d/cache/test * To simulate a system upgrade to focal, you can run the following steps 1. Add the focal archive sudo bash -c "cat
[Touch-packages] [Bug 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353
** Changed in: systemd (Ubuntu Mantic) Status: Confirmed => In Progress -- 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/2038894 Title: Ubuntu 23.10 cloud images unexpected UDP listening port 5353 Status in cloud-images: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Mantic: In Progress Bug description: [Impact] In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP listening port 5353. By default and by policy, aside from port 22 there should be no other open ports on Ubuntu cloud images. Listening port 5353 is a regression. [Test Plan] Check that port 5353 is not open, and in particular that systemd- resolved is not listening on 5353. This is what it looks like when systemd-resolved *is* listening on 5353: ``` $ ss --listening --no-header --tcp --udp --numeric udp UNCONN 00 127.0.0.54:53 0.0.0.0:* udp UNCONN 00 127.0.0.53%lo:53 0.0.0.0:* udp UNCONN 00 10.154.0.17%ens4:68 0.0.0.0:* udp UNCONN 00 127.0.0.1:323 0.0.0.0:* udp UNCONN 00 0.0.0.0:5353 0.0.0.0:* udp UNCONN 00 [::1]:323 [::]:* udp UNCONN 00 [::]:5353 [::]:* tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* tcp LISTEN 0 4096 *:22 *:* ``` ``` $ sudo lsof -i -n -P COMMANDPIDUSER FD TYPE DEVICE SIZE/OFF NODE NAME systemd 1
[Touch-packages] [Bug 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353
** Description changed: + [Impact] + + In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP + listening port 5353. + + By default and by policy, aside from port 22 there should be no other + open ports on Ubuntu cloud images. Listening port 5353 is a regression. + + [Test Plan] + + Check that port 5353 is not open, and in particular that systemd- + resolved is not listening on 5353. This is what it looks like when + systemd-resolved *is* listening on 5353: + + ``` + $ ss --listening --no-header --tcp --udp --numeric + udp UNCONN 00 127.0.0.54:53 0.0.0.0:* + udp UNCONN 00 127.0.0.53%lo:53 0.0.0.0:* + udp UNCONN 00 10.154.0.17%ens4:68 0.0.0.0:* + udp UNCONN 00 127.0.0.1:323 0.0.0.0:* + udp UNCONN 00 0.0.0.0:5353 0.0.0.0:* + udp UNCONN 00 [::1]:323 [::]:* + udp UNCONN 00 [::]:5353 [::]:* + tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* + tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* + tcp LISTEN 0 4096 *:22 *:* + ``` + + ``` + $ sudo lsof -i -n -P + COMMANDPIDUSER FD TYPE DEVICE SIZE/OFF NODE NAME + systemd 1root 153u IPv6 17848 0t0 TCP *:22 (LISTEN) + systemd-r 321 systemd-resolve 11u IPv4 16159 0t0 UDP *:5353 + systemd-r 321 systemd-resolve 12u IPv6 16161 0t0 UDP *:5353 + systemd-r 321 systemd-resolve 15u IPv4 16164 0t0 UDP 127.0.0.53:53 + systemd-r 321 systemd-resolve 16u IPv4 16165 0t0 TCP 127.0.0.53:53 (LISTEN) + systemd-r 321 systemd-resolve 17u IPv4 16166 0t0 UDP 127.0.0.54:53 +
[Touch-packages] [Bug 2032851] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1
** Also affects: apparmor (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2032851 Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 Status in apparmor package in Ubuntu: In Progress Status in apparmor source package in Focal: New Bug description: [ Impact ] * During an apparmor package upgrade, the cache files were deleted, but there could also be directories under /etc/apparmor.d/cache/ which the pre installation scripts did not account for. The upgrade would then fail with the following error message because it would not be able to remove the directories: package:apparmor:2.12-4ubuntu5.3 Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ... rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory dpkg: error processing archive /tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack): new apparmor package pre-installation script subprocess returned error exit status 1 ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1 [ Test Plan ] * On a bionic machine, create a directory under /etc/apparmor.d/cache sudo mkdir /etc/apparmor.d/cache/test * To simulate a system upgrade to focal, you can run the following steps 1. Add the focal archive sudo bash -c "cat
[Touch-packages] [Bug 2039280] Re: Support IP address protocol
Thank you! I confirmed that the added distro-patches match the upstream
patches. The feature looks useful, but it's not very common to backport
new features as part of an SRU... So I'll leave that decision to the SRU
team.
In either way, this should probably first be fixed in the current
"devel" series, i.e. by merging iproute2 v6.4+ from Debian unstable.
Once that is accomplished, we can consider this patch for SRU. Would you
be interested in working on that merge?
Nitpick: When aiming for SRU, you should consider updating the SRU
template in the bug description to the latest version (although, the one
you used might also be accepted as-is) and also change the version
number according to
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging,
e.g.: 6.1.0-1ubuntu2.1
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
Confirmed
Status in iproute2 source package in Mantic:
Confirmed
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
Two clean upstream cherry-picks, regression potential should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+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 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04
Focal isn't affected by this, so marking it as Fix Released.
** Changed in: ifupdown (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1981103
Title:
System with DNS server in /etc/network/interfaces has bogus systemd-
resolved config after upgrade to 22.04
Status in ifupdown package in Ubuntu:
Fix Released
Status in ifupdown source package in Focal:
Fix Released
Status in ifupdown source package in Jammy:
In Progress
Status in ifupdown source package in Lunar:
In Progress
Bug description:
[ Impact ]
ifupdown configurations will stop having a working DNS server on upgrade
[ Test Plan ]
Upgrading from an Ubuntu 18.04 or earlier release, bounce a network interface
with configured DNS server:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This should result in no errors, and in a valid network configuration with
working DNS resolution.
It's likely that existing netplan configuration needs to be removed and
migrated to classic ifupdown scripts before running the test above.
[ Where problems could occur ]
Although we're only fixing the resolved scripts, more complex network setups
might see regressions in DNS resolution for some cases. We should pay special
attention to bridges or virtual interfaces that have been configured through
ifupdown, as well as validate the other scripts under /etc/network/if-up.d/
[ Other Info ]
Description:Ubuntu 22.04 LTS
Release:22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after
reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using
/etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors,
easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13:
DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13:
DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious
bug and should be fixed before 22.04 upgrades are allowed for
everybody. Most servers provided by data centers like Hetzner
(Germany) are configure like that. After a do-release-upgrade you have
no working DNS anymore, unless you disable systemd-resolved. I don't
want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side
"$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 2039571] Re: systemd-modules-load fails on Azure 23.10 images on arm64
@enr0n noticed jumps in time in dmesg that could cause this issue: [Fri Oct 6 11:02:24 2023] systemd[1]: unit_file_build_name_map: normal unit file: /lib/systemd/system/multi-user.target [Fri Oct 6 11:02:24 2023] systemd[1]: unit_file_build_name_map: normal unit file: /lib/systemd/system/system-update-pre.target [Fri Oct 6 11:02:56 2023] systemd[1]: system-serial\x2dgetty.slice changed dead -> active [Fri Oct 6 11:02:56 2023] systemd[1]: system-serial\x2dgetty.slice: Job 190 system-serial\x2dgetty.slice/start finished, result=done [Fri Oct 6 11:02:56 2023] systemd[1]: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty. [Fri Oct 6 11:03:07 2023] hv_balloon: Max. dynamic memory size: 4096 MB [Fri Oct 6 11:03:26 2023] systemd[1]: system-systemd\x2dfsck.slice changed dead -> active [Fri Oct 6 11:03:26 2023] systemd[1]: system-systemd\x2dfsck.slice: Job 18 system-systemd\x2dfsck.slice/start finished, result=done [Fri Oct 6 11:03:26 2023] systemd[1]: Created slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck. [Fri Oct 6 11:03:57 2023] systemd[1]: user.slice changed dead -> active [Fri Oct 6 11:03:57 2023] systemd[1]: user.slice: Job 175 user.slice/start finished, result=done ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/2039571 Title: systemd-modules-load fails on Azure 23.10 images on arm64 Status in cloud-images: New Status in systemd package in Ubuntu: New Bug description: On some arm64 instances systemd-modules-load.service fails with the following error: $ sudo journalctl -u systemd-modules-load Oct 04 08:03:30 ubuntu systemd[1]: systemd-modules-load.service: start operation timed out. Terminating. Oct 04 08:03:30 ubuntu systemd[1]: systemd-modules-load.service: Main process exited, code=killed, status=15/TERM Oct 04 08:03:30 ubuntu systemd[1]: systemd-modules-load.service: Failed with result 'timeout'. Oct 04 08:03:30 ubuntu systemd[1]: Failed to start systemd-modules-load.service - Load Kernel Modules. It only fails on boot, when restarted manually the service runs fine. I can't find which module fails to load. The only kernel module that this service is supposed to load is multipathd and it appears to be loaded even when the service has failed. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2039571/+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 2039411] Re: Addition of ppa repository failing intermittently
I am seeing this on focal, when running command:
$ add-apt-repository ppa:snappy-dev/image -y
on 20.04. 22.04 seems to be fine.
The errors I see are of the same two types as those in the bug
description:
<<
Cannot add PPA: 'ppa:~snappy-dev/ubuntu/image'.
The team named '~snappy-dev' has no PPA named 'ubuntu/image'
Please choose from the following available PPAs:
* '15.04': DEPRECATED - WILL REMOVE SOON (Tools for Snappy 15.04)
* 'beta': Snappy beta
* 'edge': Snappy Edge
* 'image': Packages used in constructing the Ubuntu Core component of Snappy
...
>>
or the backtrace:
<<
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 137, in
shortcut = shortcut_handler(line)
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
885, in shortcut_handler
ret = factory(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 469, in
shortcut_handler
return PPAShortcutHandler(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 426, in
__init__
info = get_ppa_info(self.shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 392, in
get_ppa_info
_get_suggested_ppa_message(user, ppa))
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 349, in
_get_suggested_ppa_message
lp_user = get_info_from_lp(LAUNCHPAD_USER_API % user)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 104, in
get_info_from_lp
return get_info_from_https(lp_url, True)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98, in
get_info_from_https
return json.loads(data)
File "/usr/lib/python3.8/json/__init__.py", line 357, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.8/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.8/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
>>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2039411
Title:
Addition of ppa repository failing intermittently
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
I get following error intermittently when trying to add ppa repository:
$ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports
Cannot add PPA: 'ppa:~longsleep/ubuntu/golang-backports'.
The user named '~longsleep' has no PPA named 'ubuntu/golang-backports'
Please choose from the following available PPAs:
* 'bcmwl': bcmwl
* 'couchdb': Apache CouchDB
* 'couchdb-precise-backport': Apache CouchDB with Erlang 18 for precise
* 'createrepo-backports': Createrepo Backports
* 'firehol-backports': Firehol Backports
* 'golang-backports': Golang Backports
* 'golang-backports-dev': Golang Backports Dev
* 'iridium-browser-dev': Iridium Browser Dev dependencies
* 'pixel-extras': Pixel extras
* 'python2.7-backports': Python 2.7 Backports
* 'python3-m2crypto-backports': Python 3 M2Crypto backports
* 'stuff': Stuff
* 'ubuntu-pine64-flavour-makers': Ubuntu Pine64 Makers PPA
After multiple attempts, it may succeed, but the same above command sometimes
may return following error as well (intermittently):
$ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 137, in
shortcut = shortcut_handler(line)
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
885, in shortcut_handler
ret = factory(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 469,
in shortcut_handler
return PPAShortcutHandler(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 426,
in __init__
info = get_ppa_info(self.shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 392,
in get_ppa_info
_get_suggested_ppa_message(user, ppa))
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 349,
in _get_suggested_ppa_message
lp_user = get_info_from_lp(LAUNCHPAD_USER_API % user)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 104,
in get_info_from_lp
return get_info_from_https(lp_url, True)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98,
in get_info_from_https
return json.loads(data)
File "/usr/lib/python3.8/json/__init__.py", line 357, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.8/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File
[Touch-packages] [Bug 2039083] Re: "optional: true" flag introduces problem it's meant to fix in certain circumstances
closely related LP: #2036358 Whatever Ubuntu and systemd decide to do, the manual systemd-networkd-wait-online(8) also needs clarification: "[..] wait for all links it is aware of and which are managed by systemd-networkd.service(8) to be fully configured or failed, and for at least one link to be online." The "and at least one" phrase neither clarifies the previous, arguably preferable, Ubuntu patch - nor how the alternative is supposed to be used, where networkd knows it is not managing anything and goes to sleep(120) anyway, while some other network-online.target dependency might have already finished. -- 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/2039083 Title: "optional: true" flag introduces problem it's meant to fix in certain circumstances Status in netplan: Triaged Status in systemd package in Ubuntu: New Bug description: Hello! This bug is in relation to the situation where the "systemd-networkd- wait-online.service" hangs for several minutes on boot before eventually failing. I guess I don't know if this flag was introduced specifically for this situation, but I do know that one of the fixes for this issue is to add "optional: true" to any non-critical interfaces (as per the docs[1]). While this may be the case, it just so happens that adding this flag to an interface when it's the only configured interface in netplan can actually INTRODUCE the issue as well. Example: --- :~# grep -Ev "^#" /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: enp5s0: dhcp4: true optional: true --- The above config will cause the service hang/failure, and the removal of the flag will resolve the issue. I primarily opened this bug report with the idea that we might update aforementioned documentation to include a caveat that you want to avoid adding this flag to the only configured interface. However, it was also discussed that we might consider having the netplan config parser complain about such a setup and consider it invalid, which it kinda is. I believe in a situation where you may have a server that should have NO network connectivity, you would simply leave netplan unconfigured and/or stop any relevant services, rather than try to configure all interfaces as optional. My original test was on Jammy, though I tested this also on Focal and Bionic, and neither of those appear to be affected by this - setting the only interface as optional in either of those does not cause the "systemd-networkd-wait-online" service to hang and the system boots normally. Let me know if you'd like/need any more info from me! Thank you! [1] https://netplan.io/faq#prevent-waiting-for-interface To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2039083/+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 2037874] Re: Totem black screen playing an webm video
Thanks for the log and video example, it confirms that the issue is due to gstreamer-vaapi, the video plays fine without gstreamer1.0-vaapi installed ** Package changed: gstreamer1.0 (Ubuntu) => gstreamer-vaapi (Ubuntu) ** Changed in: gstreamer-vaapi (Ubuntu) Status: Incomplete => New ** Changed in: gstreamer-vaapi (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2037874 Title: Totem black screen playing an webm video Status in GStreamer: Unknown Status in gstreamer-vaapi package in Ubuntu: Triaged Bug description: Totem black screen playing an webm video. Video is payed ok by mpv. corrado@corrado-n02-mm-0923:~/Videos$ ffprobe -loglevel error -show_streams -show_format DSCF0001.webm [STREAM] index=0 codec_name=vp9 codec_long_name=Google VP9 profile=Profile 1 codec_type=video codec_tag_string=[0][0][0][0] codec_tag=0x width=1280 height=720 coded_width=1280 coded_height=720 closed_captions=0 film_grain=0 has_b_frames=0 sample_aspect_ratio=1:1 display_aspect_ratio=16:9 pix_fmt=yuv422p level=-99 color_range=tv color_space=bt470bg color_transfer=unknown color_primaries=unknown chroma_location=center field_order=progressive refs=1 id=N/A r_frame_rate=30/1 avg_frame_rate=30/1 time_base=1/1000 start_pts=0 start_time=0.00 duration_ts=N/A duration=N/A bit_rate=N/A max_bit_rate=N/A bits_per_raw_sample=N/A nb_frames=N/A nb_read_frames=N/A nb_read_packets=N/A DISPOSITION:default=0 DISPOSITION:dub=0 DISPOSITION:original=0 DISPOSITION:comment=0 DISPOSITION:lyrics=0 DISPOSITION:karaoke=0 DISPOSITION:forced=0 DISPOSITION:hearing_impaired=0 DISPOSITION:visual_impaired=0 DISPOSITION:clean_effects=0 DISPOSITION:attached_pic=0 DISPOSITION:timed_thumbnails=0 DISPOSITION:captions=0 DISPOSITION:descriptions=0 DISPOSITION:metadata=0 DISPOSITION:dependent=0 DISPOSITION:still_image=0 TAG:ENCODER=Lavc60.3.100 libvpx-vp9 TAG:DURATION=00:00:15.0 [/STREAM] [STREAM] index=1 codec_name=opus codec_long_name=Opus (Opus Interactive Audio Codec) profile=unknown codec_type=audio codec_tag_string=[0][0][0][0] codec_tag=0x sample_fmt=fltp sample_rate=48000 channels=1 channel_layout=mono bits_per_sample=0 initial_padding=312 id=N/A r_frame_rate=0/0 avg_frame_rate=0/0 time_base=1/1000 start_pts=-7 start_time=-0.007000 duration_ts=N/A duration=N/A bit_rate=N/A max_bit_rate=N/A bits_per_raw_sample=N/A nb_frames=N/A nb_read_frames=N/A nb_read_packets=N/A extradata_size=19 DISPOSITION:default=0 DISPOSITION:dub=0 DISPOSITION:original=0 DISPOSITION:comment=0 DISPOSITION:lyrics=0 DISPOSITION:karaoke=0 DISPOSITION:forced=0 DISPOSITION:hearing_impaired=0 DISPOSITION:visual_impaired=0 DISPOSITION:clean_effects=0 DISPOSITION:attached_pic=0 DISPOSITION:timed_thumbnails=0 DISPOSITION:captions=0 DISPOSITION:descriptions=0 DISPOSITION:metadata=0 DISPOSITION:dependent=0 DISPOSITION:still_image=0 TAG:ENCODER=Lavc60.3.100 libopus TAG:DURATION=00:00:15.00800 [/STREAM] [FORMAT] filename=DSCF0001.webm nb_streams=2 nb_programs=0 format_name=matroska,webm format_long_name=Matroska / WebM start_time=-0.007000 duration=15.008000 size=6005941 bit_rate=3201461 probe_score=100 TAG:ENCODER=Lavf60.3.100 [/FORMAT] corrado@corrado-n02-mm-0923:~/Videos$ totem DSCF0001.webm ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libgstreamer1.0-0 1.22.5-1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 1 09:39:34 2023 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2023-09-23 (8 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230923) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/2037874/+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 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1
hm Ok, in this case, the problem was the suffix actually: root@mantic:/etc/NetworkManager/system-connections# nmcli con load /etc/NetworkManager/system-connections/UPTOWN.guests Could not load file '/etc/NetworkManager/system-connections/UPTOWN.guests' root@mantic:/etc/NetworkManager/system-connections# mv /etc/NetworkManager/system-connections/UPTOWN.guests /etc/NetworkManager/system-connections/UPTOWN root@mantic:/etc/NetworkManager/system-connections# nmcli con load /etc/NetworkManager/system-connections/UPTOWN root@mantic:/etc/NetworkManager/system-connections# nmcli con show NAMEUUID TYPE DEVICE netplan-enp5s0 e1419a5e-5e1d-3fff-a17c-b2fc6d2cef99 ethernet enp5s0 lo e71fd408-7b42-49a1-af17-072edc915266 loopback lo UPTOWN.guests 491fa5c8-68ef-4140-8679-dca422f5c262 wifi -- root@mantic:/etc/NetworkManager/system-connections# It's considering the .guests a bad extension as far as I can see. Only removing the .guests makes it loadable. So we shouldn't load only .nmconnection files. -- 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/2039503 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 Status in network-manager package in Ubuntu: New Status in network-manager source package in Mantic: New Bug description: lunar to mantic upgrade, exciting to see output from network-manager postinst migrating connections to /etc/netplan one by one. But then: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess returned error exit status 10 That UUID appears in a file /etc/NetworkManager/system- connections/UPTOWN.guests that hasn't been touched since 2015. Contents of the file were: [connection] id=UPTOWN.guests uuid=491fa5c8-68ef-4140-8679-dca422f5c262 type=wifi [wifi] ssid=UPTOWN.guests mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto I've removed it from disk and the migration continued to completion. Then I got another failure on: [connection] id=belkin.1e4.guests uuid=2c77e512-f3e3-4238-b401-c94559cc6db0 type=802-11-wireless [802-11-wireless] ssid=belkin.1e4.guests mode=infrastructure mac-address=00:24:D7:1F:EA:20 [ipv6] method=auto [ipv4] method=auto Is it unhappy because of the . in the names? ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 16:12:43 2023 ErrorMessage: installed network-manager package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-12-23 (1393 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+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 2035076] Re: Wayland - Capital accented letters not recognized
Today I have updated the details of this bug report. After the 23.10 has been definitely released I went to a fresh installation in a different partition and realized that there were no problems with accented capital letters during the live session. So I thought the problem could be related to X11/wayland sessions. In fact running the xlsclients I could see that the problem doesn't effect softwares that use xwayland . Previous bug description and details were pointing the gnome-text-editor package, which is the first software that showed that problem. Now the report is pointing to the wayland package... NOT sure this is 100% correct but the issue should be more related to that area. EDIT: ok, just seen the package has been switched from wayland to gtk3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Wayland - Capital accented letters not recognized Status in gtk+3.0 package in Ubuntu: New Bug description: Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2035076/+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 2035076] Re: Wayland - Capital accented letters not recognized
** Package changed: wayland (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Wayland - Capital accented letters not recognized Status in gtk+3.0 package in Ubuntu: New Bug description: Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2035076/+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 2039536] Re: Feature request: allow user to check 'Show password' by default in the WiFi password dialogue
*** This bug is a duplicate of bug 2039422 *** https://bugs.launchpad.net/bugs/2039422 You reported it again on launchpad, the right place would be https://gitlab.gnome.org/GNOME/gnome-shell/-/issues ** This bug has been marked a duplicate of bug 2039422 Feature request: allow user to check 'Show password' by default in the WiFi password dialogue -- 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/2039536 Title: Feature request: allow user to check 'Show password' by default in the WiFi password dialogue Status in network-manager package in Ubuntu: New Bug description: Originally filed at https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/2039422, was advised to report the bug to gnome-shell. Whenever I connect to a new WiFi network, the password dialogue pops up. Every time (and I do mean literally every time), I end up clicking on the 'Show password' checkbox to make sure that I got it right. I understand the reasoning behind obscuring password fields, but for the vast majority of users, a WiFi password is not a personal secret. It's known to everyone in the same physical location, and obscuring the password is primarily a protection against shoulder surfing. It's usually also long and not easily memorable. I would like to request a user option to always check the 'Show password' box by default, which would initially be set to off (in other words, keeping the current behaviour by default, but allowing opt-in). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039536/+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 2035076] Re: Wayland - Capital accented letters not recognized
** Description changed: - Some programs (not only Gnome Text Editor... I had to choose at least one package to report the bug) don't recognize Italian accented capital letters. + Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. + I've noticed that everything works fine using the Live session which still uses X11 session. - This problem shows up with: - - Gnome Text Editor (deb) - - Libre Office (snap and deb) - - Firefox (snap) - - Sublime Text (snap) - - Gedit (snap) - - Gnome Terminal (deb) + It looks there's no problem with programs that use xwayland like Gimp + and MarkText. - No problems with the following software (all snap): - - Thunderbird - - MarkText - - Telegram + WORKAROUND === - WORKAROUND: - In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] - If I want É: + If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === - ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Wayland - Capital accented letters not recognized Status in wayland package in Ubuntu: New Bug description: Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2035076/+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 2035076] Re: Wayland - Capital accented letters not recognized
changed from gnome-text-editor to wayland package ** Summary changed: - Capital accented letters not recognized + Wayland - Capital accented letters not recognized ** Package changed: gnome-text-editor (Ubuntu) => wayland (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Wayland - Capital accented letters not recognized Status in wayland package in Ubuntu: New Bug description: Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2035076/+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 2035076] [NEW] Wayland - Capital accented letters not recognized
You have been subscribed to a public bug: Some programs (not only Gnome Text Editor... I had to choose at least one package to report the bug) don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. This problem shows up with: - Gnome Text Editor (deb) - Libre Office (snap and deb) - Firefox (snap) - Sublime Text (snap) - Gedit (snap) - Gnome Terminal (deb) No problems with the following software (all snap): - Thunderbird - MarkText - Telegram === WORKAROUND: In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If I want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- Wayland - Capital accented letters not recognized https://bugs.launchpad.net/bugs/2035076 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. -- 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 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1
NM can load keyfiles without any suffix, AFAIR. With my proposed patch it would migrate any keyfiles that are actually loaded by NM, skipping the other. We should not try to make it load (re-activate) old keyfiles, which NM isn't loading anymore itself, by renaming them. -- 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/2039503 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 Status in network-manager package in Ubuntu: New Status in network-manager source package in Mantic: New Bug description: lunar to mantic upgrade, exciting to see output from network-manager postinst migrating connections to /etc/netplan one by one. But then: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess returned error exit status 10 That UUID appears in a file /etc/NetworkManager/system- connections/UPTOWN.guests that hasn't been touched since 2015. Contents of the file were: [connection] id=UPTOWN.guests uuid=491fa5c8-68ef-4140-8679-dca422f5c262 type=wifi [wifi] ssid=UPTOWN.guests mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto I've removed it from disk and the migration continued to completion. Then I got another failure on: [connection] id=belkin.1e4.guests uuid=2c77e512-f3e3-4238-b401-c94559cc6db0 type=802-11-wireless [802-11-wireless] ssid=belkin.1e4.guests mode=infrastructure mac-address=00:24:D7:1F:EA:20 [ipv6] method=auto [ipv4] method=auto Is it unhappy because of the . in the names? ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 16:12:43 2023 ErrorMessage: installed network-manager package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-12-23 (1393 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+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 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1
Is the only problem the filename extension? Renaming it to UPTOWN.guests.nmconnection makes it loadable. Should we still try to load these files by renaming them first? Or, should we iterate over the *.nmconnection files only instead of *? -- 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/2039503 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 Status in network-manager package in Ubuntu: New Status in network-manager source package in Mantic: New Bug description: lunar to mantic upgrade, exciting to see output from network-manager postinst migrating connections to /etc/netplan one by one. But then: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess returned error exit status 10 That UUID appears in a file /etc/NetworkManager/system- connections/UPTOWN.guests that hasn't been touched since 2015. Contents of the file were: [connection] id=UPTOWN.guests uuid=491fa5c8-68ef-4140-8679-dca422f5c262 type=wifi [wifi] ssid=UPTOWN.guests mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto I've removed it from disk and the migration continued to completion. Then I got another failure on: [connection] id=belkin.1e4.guests uuid=2c77e512-f3e3-4238-b401-c94559cc6db0 type=802-11-wireless [802-11-wireless] ssid=belkin.1e4.guests mode=infrastructure mac-address=00:24:D7:1F:EA:20 [ipv6] method=auto [ipv4] method=auto Is it unhappy because of the . in the names? ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 16:12:43 2023 ErrorMessage: installed network-manager package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-12-23 (1393 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+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 2039541] [NEW] groupmems prompts for password when run as sudo/root
Public bug reported: When trying to clear users from a group using the groupmems command, the user is always prompted for the root's password, even when running as root or via sudo: (as root) # addgroup testgroup # groupmems -g testgroup -p Password: (via sudo) # sudo addgroup testgroup # sudo groupmems -g testgroup -p Password: I'm not sure if this is desired behavior, but I would expect this command to work without the root password. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2039541 Title: groupmems prompts for password when run as sudo/root Status in shadow package in Ubuntu: New Bug description: When trying to clear users from a group using the groupmems command, the user is always prompted for the root's password, even when running as root or via sudo: (as root) # addgroup testgroup # groupmems -g testgroup -p Password: (via sudo) # sudo addgroup testgroup # sudo groupmems -g testgroup -p Password: I'm not sure if this is desired behavior, but I would expect this command to work without the root password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2039541/+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 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1
I created a patch which should fix the issue: https://code.launchpad.net/~slyon/network-manager/+git/network- manager/+merge/453731 This also needs SRU -- 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/2039503 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 Status in network-manager package in Ubuntu: New Status in network-manager source package in Mantic: New Bug description: lunar to mantic upgrade, exciting to see output from network-manager postinst migrating connections to /etc/netplan one by one. But then: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess returned error exit status 10 That UUID appears in a file /etc/NetworkManager/system- connections/UPTOWN.guests that hasn't been touched since 2015. Contents of the file were: [connection] id=UPTOWN.guests uuid=491fa5c8-68ef-4140-8679-dca422f5c262 type=wifi [wifi] ssid=UPTOWN.guests mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto I've removed it from disk and the migration continued to completion. Then I got another failure on: [connection] id=belkin.1e4.guests uuid=2c77e512-f3e3-4238-b401-c94559cc6db0 type=802-11-wireless [802-11-wireless] ssid=belkin.1e4.guests mode=infrastructure mac-address=00:24:D7:1F:EA:20 [ipv6] method=auto [ipv4] method=auto Is it unhappy because of the . in the names? ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 16:12:43 2023 ErrorMessage: installed network-manager package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-12-23 (1393 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+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 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1
** Merge proposal linked: https://code.launchpad.net/~slyon/network-manager/+git/network-manager/+merge/453731 -- 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/2039503 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 Status in network-manager package in Ubuntu: New Status in network-manager source package in Mantic: New Bug description: lunar to mantic upgrade, exciting to see output from network-manager postinst migrating connections to /etc/netplan one by one. But then: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess returned error exit status 10 That UUID appears in a file /etc/NetworkManager/system- connections/UPTOWN.guests that hasn't been touched since 2015. Contents of the file were: [connection] id=UPTOWN.guests uuid=491fa5c8-68ef-4140-8679-dca422f5c262 type=wifi [wifi] ssid=UPTOWN.guests mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto I've removed it from disk and the migration continued to completion. Then I got another failure on: [connection] id=belkin.1e4.guests uuid=2c77e512-f3e3-4238-b401-c94559cc6db0 type=802-11-wireless [802-11-wireless] ssid=belkin.1e4.guests mode=infrastructure mac-address=00:24:D7:1F:EA:20 [ipv6] method=auto [ipv4] method=auto Is it unhappy because of the . in the names? ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 16:12:43 2023 ErrorMessage: installed network-manager package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-12-23 (1393 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+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 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1
Thank you for providing the keyfiles as a reproducer! I think this line in the migration script [1] is failing here. We need to catch and handle the error. > ORIG_NAME=$(nmcli --get-values connection.id con show "$UUID") The issue is, that this connection profile is apparently very old and doesn't get loaded into memory by modern NetworkManager anymore, therefor we cannot query NM about it. When trying to load it manually, I can see the following error in the journal: $ nmcli con load UPTOWN.guests $ journalctl -u NetworkManager -e NetworkManager[126986]: [1697527301.3708] settings: load: failure to load "/etc/NetworkManager/system-connections/UPTOWN.guests": filename is not valid for a keyfile [1] https://git.launchpad.net/network-manager/tree/debian/network-manager.postinst#n67 -- 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/2039503 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 Status in network-manager package in Ubuntu: New Status in network-manager source package in Mantic: New Bug description: lunar to mantic upgrade, exciting to see output from network-manager postinst migrating connections to /etc/netplan one by one. But then: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess returned error exit status 10 That UUID appears in a file /etc/NetworkManager/system- connections/UPTOWN.guests that hasn't been touched since 2015. Contents of the file were: [connection] id=UPTOWN.guests uuid=491fa5c8-68ef-4140-8679-dca422f5c262 type=wifi [wifi] ssid=UPTOWN.guests mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto I've removed it from disk and the migration continued to completion. Then I got another failure on: [connection] id=belkin.1e4.guests uuid=2c77e512-f3e3-4238-b401-c94559cc6db0 type=802-11-wireless [802-11-wireless] ssid=belkin.1e4.guests mode=infrastructure mac-address=00:24:D7:1F:EA:20 [ipv6] method=auto [ipv4] method=auto Is it unhappy because of the . in the names? ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 16:12:43 2023 ErrorMessage: installed network-manager package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-12-23 (1393 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+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 2039422] Re: Feature request: allow user to check 'Show password' by default in the WiFi password dialogue
I'm using XFCE, so presumably that means Gnome. I'll try filing a report there. -- 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/2039422 Title: Feature request: allow user to check 'Show password' by default in the WiFi password dialogue Status in network-manager package in Ubuntu: New Bug description: Whenever I connect to a new WiFi network, the password dialogue pops up. Every time (and I do mean literally every time), I end up clicking on the 'Show password' checkbox to make sure that I got it right. I understand the reasoning behind obscuring password fields, but for the vast majority of users, a WiFi password is not a personal secret. It's known to everyone in the same physical location, and obscuring the password is primarily a protection against shoulder surfing. It's usually also long and not easily memorable. I would like to request a user option to always check the 'Show password' box by default, which would initially be set to off (in other words, keeping the current behaviour by default, but allowing opt-in). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039422/+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 2039536] [NEW] Feature request: allow user to check 'Show password' by default in the WiFi password dialogue
Public bug reported: Originally filed at https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/2039422, was advised to report the bug to gnome-shell. Whenever I connect to a new WiFi network, the password dialogue pops up. Every time (and I do mean literally every time), I end up clicking on the 'Show password' checkbox to make sure that I got it right. I understand the reasoning behind obscuring password fields, but for the vast majority of users, a WiFi password is not a personal secret. It's known to everyone in the same physical location, and obscuring the password is primarily a protection against shoulder surfing. It's usually also long and not easily memorable. I would like to request a user option to always check the 'Show password' box by default, which would initially be set to off (in other words, keeping the current behaviour by default, but allowing opt-in). ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/2039536 Title: Feature request: allow user to check 'Show password' by default in the WiFi password dialogue Status in network-manager package in Ubuntu: New Bug description: Originally filed at https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/2039422, was advised to report the bug to gnome-shell. Whenever I connect to a new WiFi network, the password dialogue pops up. Every time (and I do mean literally every time), I end up clicking on the 'Show password' checkbox to make sure that I got it right. I understand the reasoning behind obscuring password fields, but for the vast majority of users, a WiFi password is not a personal secret. It's known to everyone in the same physical location, and obscuring the password is primarily a protection against shoulder surfing. It's usually also long and not easily memorable. I would like to request a user option to always check the 'Show password' box by default, which would initially be set to off (in other words, keeping the current behaviour by default, but allowing opt-in). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039536/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
This introduces an unacceptable regression on Raspberry Pis. An interface that is *not* listed must not cause a 2 min timeout. -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Lunar: Fix Committed Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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
