[Touch-packages] [Bug 1799007] Re: no sound after 18.10 upgrade
I'm also facing the same issue, and "apport-collect 1799007" does not accept to run for me, stating I'm not on the bug :/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799007 Title: no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1799007] Re: no sound after 18.10 upgrade
Ok, in my case, |fuser -v| reveals that it's being blocked by timidity. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799007 Title: no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta
Same on upgrade from Ubuntu 18.04 to 18.10, fuser -v confirms exclusive access taken by timidity on the sound device, removing timidity* fixes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797714 Title: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Sadly, Quectel EM120 is not supported, so I can't use mine on ThinkPad P14s Gen2 laptop. -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Fix Released Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options . For
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Looks like https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402#note_1064882 does help, I have been able to enable my EM120 on 21.10. Take care to change the proper defines in the provided C code. The `mbim2sar.so` comes from the Snap package linked above. Thanks to Joar Wandborg ! ** Bug watch added: gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues #402 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/402 -- 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Fix Released Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems suppor
[Touch-packages] [Bug 1946481] [NEW] NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
Public bug reported: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: > GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in dbus package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1946481/+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 1946481] Re: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
> gnome-control-c[49211]: Error connecting to ModemManager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 5 matched rules; type="method_call", sender=":1.508" (uid=1000 pid=49211 comm="gnome-control-center " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination=":1.502" (uid=0 pid=48379 comm="/usr/sbin/ModemManager " label="unconfined") -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in dbus package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1946481/+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 1946481] Re: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
The output of `mmcli -L` was already provided above: > $ mmcli -L > error: couldn't create manager: > GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 5 > matched rules; type="method_call", sender=":1.269" (uid=1000 pid=48173 > comm="mmcli -L " label="unconfined") > interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" > error name="(unset)" requested_reply="0" destination=":1.17" (uid=0 pid=1702 > comm="/usr/sbin/ModemManager " label="unconfined") -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in dbus package in Ubuntu: Incomplete Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1946481/+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 1946481] Re: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1946481/+attachment/5532127/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in dbus package in Ubuntu: Incomplete Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1946481/+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 1946481] Re: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
Attached journal taken after following the previously documented STR: - Open Settings, - Go to Network tab -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in dbus package in Ubuntu: Incomplete Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1946481/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
NetworkManager itself is able to properly talk to ModemManager: > $ nmcli con show |grep gsm > Orange Internet0a196fc4-89e3-479b-b049-ab13dfff897b gsm -- And a `nmcli con "Orange Internet" up` works (assuming you have enabled the modem which is blocked on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402 in my case) -- 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/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
According to the policies in place for ModemManager in /etc/dbus-1/system.d/org.freedesktop.ModemManager1.conf it looks like only root can really do something. Assuming this is right, then I'm wondering why GNOME Control Center tries to directly access ModemManager instead of going via NetworkManager ? At least that is what I am wondering from the error in message #1 from `(uid=1000 pid=49211 comm="gnome-control-center " label="unconfined")` ** Summary changed: - NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" + GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" ** Bug watch added: gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues #402 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/402 -- 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/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
Running GNOME Control Center as root (not a good idea, I know), clearly gets the ModemManager connection to work. ** Attachment added: "GNOME Control Center (root)" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+attachment/5534919/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-10-21%2015-19-24.png -- 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/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
** Attachment added: "Running as normal user" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+attachment/5534920/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-10-21%2015-19-34.png -- 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/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1949621] Re: libmbim cannot make use of Quectel EM120
I just had a look and next version of Ubuntu uses ModemMamager 1.18.2 as of now, so it does not have the handling for FCC unlock procedure. ** Also 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/1949621 Title: libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
** Summary changed: - libmbim cannot make use of Quectel EM120 + modemmanager/libmbim cannot make use of Quectel EM120 -- 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/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
Trying to investigate https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1949621 I made a few local backports of modemmanager / libmm / libqmi packages from next 22.04 (but the source was still too old to handle the modem), and when I reverted to latest impish version, it seems the bug disappeared? I can now successfully: - use mmcli, as a standard user, like before - use modem-manager-gui, as a standard user, like before - see modem from GNOME Control Center and interact with it, as a standard user, like before. -- 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/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
Closing as invalid, since I can't repro anymore and I can't explain why. ** Changed in: modemmanager (Ubuntu) Status: New => Invalid -- 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/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: Invalid Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1695601] [NEW] IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet
Public bug reported: My ISP's router provides IPv6 connectivity and advertises valid lifetime of 900 secs and preferred lifetime of 300 secs. My Ubuntu 17.04 (and previous) installation has been showing weird behavior over IPv6, with connections dropping quite often but on a regular basis. After extensive debugging and verification that there was no issue on router side, and on WiFi physical connection, I have verified that this was not related to the lack of ICMPv6 RA packets. Running |watch -d -n1 ip -6 addr show dev wlan0| shows: - decreasing valid_lft and preferred_lft on both IPv6 addresses - upon ICMPv6 RA packet received, the global SLAAC address derived from MAC gets valid_lft and preferred_lft field updated - at the same time, the privacy extension address is still decreasing System uses NetworkManager to handle all of that. I could verify that my desktop system, running Debian Sid with NetworkManager v1.6 was not exposing the issue. Running NetworkManager in debug mode gives more informations: > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7897] > platform-linux: event-notification: NEWADDR, seq 0: > 2a01:::::::39c5/64 lft 900sec pref 300sec lifetime > 289-289[300,900] dev 3 flags secondary src kernel > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7901] > platform-linux: event-notification: NEWADDR, seq 0: > 2a01:::::::39c5/64 lft 622sec pref 22sec lifetime > 289-289[22,622] dev 3 flags secondary src kernel The two timestamps of the NEWADDR event are very very close. The first one shows proper update of the lifetimes values ; while the second one shows invalid values being pushed. With those informations in mind, I dug a little bit in the NetworkManager source code, and I found that there was one change between v1.4.4 (current Zesty package) and v1.6 (Debian sid package) that was touching the code handling IPv6 addresses sync: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1dbd9d7948 ; the commit states that without this change, NM might overwrite IPv6 temporary addresses changes. I took my chance and rebuilt network-manager-1.4.4 package with that patch included: IPv6 temporary privacy extensions enabled addresses gets proper updates of their lifetime when ICMPv6 packets reaches my system. ** 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/1695601 Title: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet Status in network-manager package in Ubuntu: New Bug description: My ISP's router provides IPv6 connectivity and advertises valid lifetime of 900 secs and preferred lifetime of 300 secs. My Ubuntu 17.04 (and previous) installation has been showing weird behavior over IPv6, with connections dropping quite often but on a regular basis. After extensive debugging and verification that there was no issue on router side, and on WiFi physical connection, I have verified that this was not related to the lack of ICMPv6 RA packets. Running |watch -d -n1 ip -6 addr show dev wlan0| shows: - decreasing valid_lft and preferred_lft on both IPv6 addresses - upon ICMPv6 RA packet received, the global SLAAC address derived from MAC gets valid_lft and preferred_lft field updated - at the same time, the privacy extension address is still decreasing System uses NetworkManager to handle all of that. I could verify that my desktop system, running Debian Sid with NetworkManager v1.6 was not exposing the issue. Running NetworkManager in debug mode gives more informations: > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7897] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 900sec pref 300sec lifetime 289-289[300,900] dev 3 flags secondary src kernel > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7901] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 622sec pref 22sec lifetime 289-289[22,622] dev 3 flags secondary src kernel The two timestamps of the NEWADDR event are very very close. The first one shows proper update of the lifetimes values ; while the second one shows invalid values being pushed. With those informations in mind, I dug a little bit in the NetworkManager source code, and I found that there was one change between v1.4.4 (current Zesty package) and v1.6 (Debian sid package) that was touching the code handling IPv6 addresses sync: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1dbd9d7948 ; the commit states that without this change, NM might overwrite IPv6 temporary addresses changes. I took my chance and rebuilt network-m
[Touch-packages] [Bug 1695601] Re: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet
I just got confirmation from Beniamino Galvani that this is consistent with his change. Also, the patch is part of the 1.4 branch and should be in the next release: https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=nm-1-4 -- 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/1695601 Title: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet Status in network-manager package in Ubuntu: New Bug description: My ISP's router provides IPv6 connectivity and advertises valid lifetime of 900 secs and preferred lifetime of 300 secs. My Ubuntu 17.04 (and previous) installation has been showing weird behavior over IPv6, with connections dropping quite often but on a regular basis. After extensive debugging and verification that there was no issue on router side, and on WiFi physical connection, I have verified that this was not related to the lack of ICMPv6 RA packets. Running |watch -d -n1 ip -6 addr show dev wlan0| shows: - decreasing valid_lft and preferred_lft on both IPv6 addresses - upon ICMPv6 RA packet received, the global SLAAC address derived from MAC gets valid_lft and preferred_lft field updated - at the same time, the privacy extension address is still decreasing System uses NetworkManager to handle all of that. I could verify that my desktop system, running Debian Sid with NetworkManager v1.6 was not exposing the issue. Running NetworkManager in debug mode gives more informations: > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7897] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 900sec pref 300sec lifetime 289-289[300,900] dev 3 flags secondary src kernel > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7901] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 622sec pref 22sec lifetime 289-289[22,622] dev 3 flags secondary src kernel The two timestamps of the NEWADDR event are very very close. The first one shows proper update of the lifetimes values ; while the second one shows invalid values being pushed. With those informations in mind, I dug a little bit in the NetworkManager source code, and I found that there was one change between v1.4.4 (current Zesty package) and v1.6 (Debian sid package) that was touching the code handling IPv6 addresses sync: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1dbd9d7948 ; the commit states that without this change, NM might overwrite IPv6 temporary addresses changes. I took my chance and rebuilt network-manager-1.4.4 package with that patch included: IPv6 temporary privacy extensions enabled addresses gets proper updates of their lifetime when ICMPv6 packets reaches my system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1695601/+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 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails
A workaround is to remove "[NOTFOUND=return] resolve" from /etc/nsswitch.conf, though it may break other things (but nothing visible so far). -- 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/1665394 Title: DNS resolution of irc.freenode.net or chat.freenode.net fails Status in systemd package in Ubuntu: Confirmed Bug description: I am running Ubuntu 16.10 (from a base install upgraded several times), with proposed-updates enabled. Recently, I started having problems where I am unable to resolve irc.freenode.net. This is unrelated to the networks. I have been able to confirm that systemd-resolved is able to perform the name resolution. Yet, getaddrinfo() call returns -EAI_AGAIN error. This can be reproduced using getent: > $ getent ahosts irc.freenode.net > $ While testing v4 or v6 directly returns something valid: > $ getent ahostsv4 irc.freenode.net > 38.229.70.22STREAM chat.freenode.net > 38.229.70.22DGRAM > 38.229.70.22RAW > 130.239.18.119 STREAM > 130.239.18.119 DGRAM > 130.239.18.119 RAW [...] > $ > $ getent ahostsv6 irc.freenode.net > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net > 2001:5a0:3604:1:64:86:243:181 DGRAM > 2001:5a0:3604:1:64:86:243:181 RAW > 2001:6b0:e:2a18::118 STREAM > 2001:6b0:e:2a18::118 DGRAM > 2001:6b0:e:2a18::118 RAW [...] > $ dpkg.log shows there has been some upgrade of systemd recently, though I cannot tell for sure if that directly relates to the problem, I do use suspend-to-ram a lot and reboot not that often. > $ lsb_release -a > LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch > Distributor ID: Ubuntu > Description:Ubuntu 16.10 > Release:16.10 > Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+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 1665394] [NEW] DNS resolution of irc.freenode.net or chat.freenode.net fails
Public bug reported: I am running Ubuntu 16.10 (from a base install upgraded several times), with proposed-updates enabled. Recently, I started having problems where I am unable to resolve irc.freenode.net. This is unrelated to the networks. I have been able to confirm that systemd-resolved is able to perform the name resolution. Yet, getaddrinfo() call returns -EAI_AGAIN error. This can be reproduced using getent: > $ getent ahosts irc.freenode.net > $ While testing v4 or v6 directly returns something valid: > $ getent ahostsv4 irc.freenode.net > 38.229.70.22STREAM chat.freenode.net > 38.229.70.22DGRAM > 38.229.70.22RAW > 130.239.18.119 STREAM > 130.239.18.119 DGRAM > 130.239.18.119 RAW [...] > $ > $ getent ahostsv6 irc.freenode.net > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net > 2001:5a0:3604:1:64:86:243:181 DGRAM > 2001:5a0:3604:1:64:86:243:181 RAW > 2001:6b0:e:2a18::118 STREAM > 2001:6b0:e:2a18::118 DGRAM > 2001:6b0:e:2a18::118 RAW [...] > $ dpkg.log shows there has been some upgrade of systemd recently, though I cannot tell for sure if that directly relates to the problem, I do use suspend-to-ram a lot and reboot not that often. > $ lsb_release -a > LSB Version: > core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch > Distributor ID: Ubuntu > Description: Ubuntu 16.10 > Release: 16.10 > Codename: yakkety ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Package changed: glibc (Ubuntu) => systemd (Ubuntu) -- 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/1665394 Title: DNS resolution of irc.freenode.net or chat.freenode.net fails Status in systemd package in Ubuntu: Confirmed Bug description: I am running Ubuntu 16.10 (from a base install upgraded several times), with proposed-updates enabled. Recently, I started having problems where I am unable to resolve irc.freenode.net. This is unrelated to the networks. I have been able to confirm that systemd-resolved is able to perform the name resolution. Yet, getaddrinfo() call returns -EAI_AGAIN error. This can be reproduced using getent: > $ getent ahosts irc.freenode.net > $ While testing v4 or v6 directly returns something valid: > $ getent ahostsv4 irc.freenode.net > 38.229.70.22STREAM chat.freenode.net > 38.229.70.22DGRAM > 38.229.70.22RAW > 130.239.18.119 STREAM > 130.239.18.119 DGRAM > 130.239.18.119 RAW [...] > $ > $ getent ahostsv6 irc.freenode.net > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net > 2001:5a0:3604:1:64:86:243:181 DGRAM > 2001:5a0:3604:1:64:86:243:181 RAW > 2001:6b0:e:2a18::118 STREAM > 2001:6b0:e:2a18::118 DGRAM > 2001:6b0:e:2a18::118 RAW [...] > $ dpkg.log shows there has been some upgrade of systemd recently, though I cannot tell for sure if that directly relates to the problem, I do use suspend-to-ram a lot and reboot not that often. > $ lsb_release -a > LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch > Distributor ID: Ubuntu > Description:Ubuntu 16.10 > Release:16.10 > Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+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 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails
Adding back "[NOTFOUND=return] resolve" to /etc/nsswitch.conf, setting DNSSEC=no in /etc/systemd/resolved.conf, restarting systemd-resolved process and then: > $ getent ahosts irc.freenode.net Gives proper list of hosts Commenting again the DNSSEC line of resolved.conf, restarting the service, and the resolution is still working. I'm a bit puzzled. -- 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/1665394 Title: DNS resolution of irc.freenode.net or chat.freenode.net fails Status in systemd package in Ubuntu: Confirmed Bug description: I am running Ubuntu 16.10 (from a base install upgraded several times), with proposed-updates enabled. Recently, I started having problems where I am unable to resolve irc.freenode.net. This is unrelated to the networks. I have been able to confirm that systemd-resolved is able to perform the name resolution. Yet, getaddrinfo() call returns -EAI_AGAIN error. This can be reproduced using getent: > $ getent ahosts irc.freenode.net > $ While testing v4 or v6 directly returns something valid: > $ getent ahostsv4 irc.freenode.net > 38.229.70.22STREAM chat.freenode.net > 38.229.70.22DGRAM > 38.229.70.22RAW > 130.239.18.119 STREAM > 130.239.18.119 DGRAM > 130.239.18.119 RAW [...] > $ > $ getent ahostsv6 irc.freenode.net > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net > 2001:5a0:3604:1:64:86:243:181 DGRAM > 2001:5a0:3604:1:64:86:243:181 RAW > 2001:6b0:e:2a18::118 STREAM > 2001:6b0:e:2a18::118 DGRAM > 2001:6b0:e:2a18::118 RAW [...] > $ dpkg.log shows there has been some upgrade of systemd recently, though I cannot tell for sure if that directly relates to the problem, I do use suspend-to-ram a lot and reboot not that often. > $ lsb_release -a > LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch > Distributor ID: Ubuntu > Description:Ubuntu 16.10 > Release:16.10 > Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+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 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails
So, comment #5 is somehow invalid, I got the whole story on why it started to work again: Schiggn (comment #4) contacted some Freenode staff, and they changed the DNS records to expose less addresses. This indeed proved to workaround the issue. -- 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/1665394 Title: DNS resolution of irc.freenode.net or chat.freenode.net fails Status in systemd package in Ubuntu: Confirmed Bug description: I am running Ubuntu 16.10 (from a base install upgraded several times), with proposed-updates enabled. Recently, I started having problems where I am unable to resolve irc.freenode.net. This is unrelated to the networks. I have been able to confirm that systemd-resolved is able to perform the name resolution. Yet, getaddrinfo() call returns -EAI_AGAIN error. This can be reproduced using getent: > $ getent ahosts irc.freenode.net > $ While testing v4 or v6 directly returns something valid: > $ getent ahostsv4 irc.freenode.net > 38.229.70.22STREAM chat.freenode.net > 38.229.70.22DGRAM > 38.229.70.22RAW > 130.239.18.119 STREAM > 130.239.18.119 DGRAM > 130.239.18.119 RAW [...] > $ > $ getent ahostsv6 irc.freenode.net > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net > 2001:5a0:3604:1:64:86:243:181 DGRAM > 2001:5a0:3604:1:64:86:243:181 RAW > 2001:6b0:e:2a18::118 STREAM > 2001:6b0:e:2a18::118 DGRAM > 2001:6b0:e:2a18::118 RAW [...] > $ dpkg.log shows there has been some upgrade of systemd recently, though I cannot tell for sure if that directly relates to the problem, I do use suspend-to-ram a lot and reboot not that often. > $ lsb_release -a > LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch > Distributor ID: Ubuntu > Description:Ubuntu 16.10 > Release:16.10 > Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+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 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails
It is likely to be an upstream problem. Given a zone with A/ records with enough addresses, I can reproduce the problem. Hacking in systemd source code, I could find those STR: - disable "resolve" in nsswitch.conf - add a resolution against a record with a lot of addresses in src/libsystemd/sd-resolve/test-resolve.c - build test-resolve tool - run ./test-resolve e.g.: > r = sd_resolve_getaddrinfo(resolve, &q2, "test.neteffmon.eu", NULL, &hints, > getaddrinfo_handler, NULL); Running this results in: > Assertion '*length <= maxlength' failed at > src/libsystemd/sd-resolve/sd-resolve.c:203, function serialize_addrinfo(). > Aborting. Changing BUFSIZE in src/libsystemd/sd-resolve/sd-resolve.c to something bigger (e.g. 65536U), rebuild and restart ./test-resolve, the resolution succeeds. -- 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/1665394 Title: DNS resolution of irc.freenode.net or chat.freenode.net fails Status in systemd package in Ubuntu: Confirmed Bug description: I am running Ubuntu 16.10 (from a base install upgraded several times), with proposed-updates enabled. Recently, I started having problems where I am unable to resolve irc.freenode.net. This is unrelated to the networks. I have been able to confirm that systemd-resolved is able to perform the name resolution. Yet, getaddrinfo() call returns -EAI_AGAIN error. This can be reproduced using getent: > $ getent ahosts irc.freenode.net > $ While testing v4 or v6 directly returns something valid: > $ getent ahostsv4 irc.freenode.net > 38.229.70.22STREAM chat.freenode.net > 38.229.70.22DGRAM > 38.229.70.22RAW > 130.239.18.119 STREAM > 130.239.18.119 DGRAM > 130.239.18.119 RAW [...] > $ > $ getent ahostsv6 irc.freenode.net > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net > 2001:5a0:3604:1:64:86:243:181 DGRAM > 2001:5a0:3604:1:64:86:243:181 RAW > 2001:6b0:e:2a18::118 STREAM > 2001:6b0:e:2a18::118 DGRAM > 2001:6b0:e:2a18::118 RAW [...] > $ dpkg.log shows there has been some upgrade of systemd recently, though I cannot tell for sure if that directly relates to the problem, I do use suspend-to-ram a lot and reboot not that often. > $ lsb_release -a > LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch > Distributor ID: Ubuntu > Description:Ubuntu 16.10 > Release:16.10 > Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+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 1966381] Re: systemd-oomd is counting cached as used and triggering more easily than it should
Sorry, I did not receive any email for your comment: - yes, I was on -proposed, so as I said, I had the version with the fix - I will try to capture those, but I disabled systemd-oomd since, and have not had issue (at all). -- 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/1966381 Title: systemd-oomd is counting cached as used and triggering more easily than it should Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 2039868] Re: amdgpu reset during usage of firefox
There's 6.5.0-15 package incoming on mantic-update, does it contains the
fix?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039868
Title:
amdgpu reset during usage of firefox
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Running nightly on 23.10 (since monday), I have been experiencing a
few amdgpu resets in the past hours
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 18:26:43 2023
HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
InstallationDate: Installed on 2022-07-04 (472 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A0CTO1WW
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+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 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
That would mean that Jammy, a LTS, will not be able to make use of LTE modems on 2021 shipped ThinkPad ? -- 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/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
Thanks, I just saw that Jammy has 1.26.2. I might try and give it a try to verify the behavior of the LTE modem there. -- 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/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
I gave a try and I can confirm that following the modemmanager docs to enable FCC unlock procedure at ModemManager level, the modem is properly unlocked and connects to the internet. However, this is another issue, but the firmware crashing persist when trying to make use of the LTE connection a bit more than just sending a ping. -- 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/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1966381] Re: systemd-oomd is counting cached as used and triggering more easily than it should
Was this released ? I've received an update of that package this morning: > $ dpkg --list systemd-oomd > Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder > | > État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements > |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) > ||/ NomVersion Architecture Description > +++-==-===-- > ii systemd-oomd 249.11-0ubuntu3 amd64Userspace out-of-memory (OOM) > killer But even with that version which fixes the issue according to: > systemd (249.11-0ubuntu3) jammy; urgency=medium > > * oomd: calculate 'used' memory with MemAvailable instead of MemFree (LP: > #1966381) > File: > debian/patches/lp1966381-oomd-calculate-used-memory-with-MemAvailable-instead-of-M.patch > > https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=15fc4c53d726e1dcae7296a9306cfd453fd1a046 > * hwdb: remove the tablet pad entry for the UC-Logic 1060N (LP: #1926860) > File: > debian/patches/lp1926860-hwdb-remove-the-tablet-pad-entry-for-the-UC-Logic-1060N.patch > > https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7bf31946a52e55f9f6ea4ecfa30e311685b20997 > > -- Nick Rosbrook Thu, 07 Apr 2022 15:28:15 > -0400 I still hit the problem after a few minutes of building a debug firefox on my laptop (ThinkPad P14s, 32GB RAM) > -- Boot c45108609edc41368bc948d9ffda1f4d -- > avril 08 12:30:44 portable-alex systemd[1]: Starting Userspace Out-Of-Memory > (OOM) Killer... > avril 08 12:30:44 portable-alex systemd[1]: Started Userspace Out-Of-Memory > (OOM) Killer. > avril 08 12:42:07 portable-alex systemd-oomd[1168]: Killed > /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-Alacritty-6631.scope > due to memory used (26327048192) / total (29247873024) and swap used > (1023406080) / total (1023406080) being more than 90.00% > -- Boot 2d12cd6e16d4432b94f957fc1cd77124 -- This is what I can see in the logs ; as you can see it's killing my term (alacritty). FTR, all things being equal otherwise, I have been able to run for days with systemd-oomd masked and disabled and the same usage. -- 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/1966381 Title: systemd-oomd is counting cached as used and triggering more easily than it should Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22
[Touch-packages] [Bug 1966381] Re: systemd-oomd is counting cached as used and triggering more easily than it should
And FTR I also have 1GB swap, the install is not from Jammy (rather 21.04 or 21.10) $ LC_ALL=C swapon -s FilenameTypeSizeUsed Priority /dev/dm-2 partition 999420 631852 -2 -- 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/1966381 Title: systemd-oomd is counting cached as used and triggering more easily than it should Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 2039868] Re: amdgpu reset during usage of firefox
Thanks, I'll try and keep you updated, however I am also facing bug
2039958 (probably a dupe of bug 2034619), so I might still need GNOME
45.1 to be released.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039868
Title:
amdgpu reset during usage of firefox
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
New
Bug description:
Running nightly on 23.10 (since monday), I have been experiencing a
few amdgpu resets in the past hours
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 18:26:43 2023
HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
InstallationDate: Installed on 2022-07-04 (472 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A0CTO1WW
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+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 1695601] Re: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet
Newer versions of NetworkManager, after upgrading from 17.04, have been bundling the proper fix. -- 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/1695601 Title: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet Status in network-manager package in Ubuntu: Confirmed Bug description: My ISP's router provides IPv6 connectivity and advertises valid lifetime of 900 secs and preferred lifetime of 300 secs. My Ubuntu 17.04 (and previous) installation has been showing weird behavior over IPv6, with connections dropping quite often but on a regular basis. After extensive debugging and verification that there was no issue on router side, and on WiFi physical connection, I have verified that this was not related to the lack of ICMPv6 RA packets. Running |watch -d -n1 ip -6 addr show dev wlan0| shows: - decreasing valid_lft and preferred_lft on both IPv6 addresses - upon ICMPv6 RA packet received, the global SLAAC address derived from MAC gets valid_lft and preferred_lft field updated - at the same time, the privacy extension address is still decreasing System uses NetworkManager to handle all of that. I could verify that my desktop system, running Debian Sid with NetworkManager v1.6 was not exposing the issue. Running NetworkManager in debug mode gives more informations: > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7897] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 900sec pref 300sec lifetime 289-289[300,900] dev 3 flags secondary src kernel > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7901] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 622sec pref 22sec lifetime 289-289[22,622] dev 3 flags secondary src kernel The two timestamps of the NEWADDR event are very very close. The first one shows proper update of the lifetimes values ; while the second one shows invalid values being pushed. With those informations in mind, I dug a little bit in the NetworkManager source code, and I found that there was one change between v1.4.4 (current Zesty package) and v1.6 (Debian sid package) that was touching the code handling IPv6 addresses sync: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1dbd9d7948 ; the commit states that without this change, NM might overwrite IPv6 temporary addresses changes. I took my chance and rebuilt network-manager-1.4.4 package with that patch included: IPv6 temporary privacy extensions enabled addresses gets proper updates of their lifetime when ICMPv6 packets reaches my system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1695601/+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
