[Touch-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
Tested with Upstream ModemManager, libmbim and libqmi. The WWAN function can be turned on through gnome-control-center, and 5G function works correctly. The upstream version get with "git rev-parse --short HEAD" listed as below: ModemManager: eebdbc45 libmbim: add668b libqmi: fa6c7a97 -- 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/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+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 1958059] Re: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available.
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- 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/1958059 Title: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available. Status in apport package in Ubuntu: Expired Bug description: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available. This is clean fresh 32-bit 18.04.6 updated from 18.04.5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:29:27 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: 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/1958059/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
** Also affects: libmbim Importance: Undecided Status: New ** No longer affects: libmbim ** Also affects: libmbim Importance: Undecided Status: New ** Project changed: libmbim => libmbim (Ubuntu) ** Also affects: libqmi Importance: Undecided Status: New ** Project changed: libqmi => libqmi (Ubuntu) -- 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/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
** Tags added: oem-priority originate-from-1962525 somerville ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Dirk Su (dirksu) ** Changed in: oem-priority Status: New => Confirmed -- 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/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+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 1984067] Re: Xorg crash
Thanks for the bug report. I think we need proper debug symbols to get a more accurate stack trace. So please just follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1984067 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: All logs should be added automatically but the central issue is: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Backtrace: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b7984596e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f3e6a242520] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x55b7982ee1e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x55b7982efc85] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x55b7982f0183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x55b7982f1183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x55b7983cfa7d] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x55b7983f9e4c] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x55b7983f2f21] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x55b7983f311e] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x55b798452c60] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x55b798452ee8] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55b7982e3257] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x55b7982e7524] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f3e6a229d90] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f3e6a229e40] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x55b7982d05f5] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Segmentation fault at address 0x7ffc51d3 Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Fatal server error: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Caught signal 11 (Segmentation fault). Server aborting Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Please consult the The X.Org Foundation support Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: #011 at http://wiki.x.org Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: for help. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular
[Touch-packages] [Bug 1981385] Re: initrd lacks modules to mount boot image from http boot
You may need "nfit" module in the initrd too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1981385 Title: initrd lacks modules to mount boot image from http boot Status in initramfs-tools package in Ubuntu: New Bug description: If you use UEFI http boot to boot an image (rather than an EFI executable) and get all the way to a normal userspace, you can access the boot image as /dev/pmem0. But this is not accessible in the initrd; presumably some modules are missing. Dimitri added some modules that are clearly going to be necessary (kernel/drivers/nvdimm) in 0.140ubuntu14 and I added kernel/drivers/dax too in local experiments but this appears not to be enough to get it to appear. This is desirable because then you can just feed an installer ISO to a machine via http boot and the installer just works as normal (the speed and, uh, quality, of the implementation of HTTP in a given machine's firmware may mean this isn't always the best option but it would be nice if it worked in case someone's machine actually does this well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981385/+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 1983618] Re: New upstream microrelease 2.5.13
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/427967 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1983618 Title: New upstream microrelease 2.5.13 Status in openldap package in Ubuntu: Invalid Status in openldap source package in Jammy: In Progress Bug description: [ Impact ] * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.13. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/3PLJDVP7QWTRFHC2GPQTGBLEQFCBUZZ2/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/pipelines/4504 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/RXOSXVLKTIDM4XJUA5EZZ42677JXRHYN/ * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in bileto and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: https://launchpad.net/~ci-train- ppa-service/+archive/ubuntu/4887/+build/24250107 * Bileto ticket: https://bileto.ubuntu.com/#/ticket/4887 [ Where problems could occur ] * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since we are dealing with a microrelease upgrade. Whenever a test failure is detected, we will be on top of it and make sure it doesn't affect existing users. [ Other Info ] * This is a reoccurring MRE. See below for links to previous OpenLDAP MREs. * CVEs fixed by this release: - None. Current versions in supported releases that got updates: openldap | 2.5.12+dfsg-0ubuntu0.22.04.1 | jammy-updates | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 As usual we test and prep from the PPA and then push through SRU/Security as applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1983618/+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 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
YC is in the process of doing an SRU for a bunch of other bugs in fwupd and the fix should come in that same SRU I expect. ** Changed in: fwupd (Ubuntu Jammy) Assignee: (unassigned) => Yosu (yc) ** Changed in: fwupd (Ubuntu Jammy) Assignee: Yosu (yc) => Yuan-Chen Cheng (ycheng-twn) -- 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/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in systemd: New Status in fwupd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: Confirmed Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: Won't Fix Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: Confirmed Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1979313] Re: kubeadm doesn't work with containerd version of apt install
Deleted the apt task instead so comments don't go apt subscribers for all eternity. ** No longer affects: apt (Ubuntu) ** No longer affects: apt (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1979313 Title: kubeadm doesn't work with containerd version of apt install Status in containerd package in Ubuntu: Triaged Status in containerd source package in Focal: Triaged Bug description: Version of Ubuntu: Description:Ubuntu 22.04 LTS Release:22.04 kubeadm: Installed: 1.24.2-00 Candidate: 1.24.2-00 Package that has the problem: containerd: Installed: 1.5.9-0ubuntu3 Candidate: 1.5.9-0ubuntu3 Version table: *** 1.5.9-0ubuntu3 500 500 http://ro.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Problem: Kubeadm is not compatibile with this version of containerd that is installed by `apt install containerd`. If I use `kubeadm init` it will create a cluster which instead of staying alive will die after a couple of minutes. The problem is in the config file of containerd, which has the following parameter set to false: `SystemdCgroup = false` Solution: To solve this, the containerd config parameter SystemdCgroup needs to be set to true. It is set to true in the containerd v1.6.2, but by default, apt installs the version v1.5.9, which worked on Ubuntu 20.04 but does not work for Ubuntu 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1979313/+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 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
I think Eric has a good point. Why this fix is not ported back to Jammy? Jammy is a LTS Version so this service won't work for the next two years if the fix gets not back ported for all who stick to LTS for whatever reason. This is then from my point of view also a security issue, since if this service is not running no firmware updates will be installed for several devices automatically. Since this is what this service is supposed to do and FW updates may also fix security issues. But the user thinks this service is there and doing it's job. Since from my experience most users never check if all the services are up and running fine as long as there is no unexpected behavior. So the user will also not manually check for FW updates, he believes the service does. And this service does not start on any Ubuntu installation at the moment! Also Focal needs this fix, since it is still supported for two more years. So can you please explain? -- 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/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in systemd: New Status in fwupd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: Confirmed Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: Won't Fix Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: Confirmed Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1979313] Re: kubeadm doesn't work with containerd version of apt install
** Also affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: containerd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: containerd (Ubuntu Focal) Importance: Undecided => Low ** Changed in: containerd (Ubuntu Focal) Status: New => Triaged ** Changed in: apt (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1979313 Title: kubeadm doesn't work with containerd version of apt install Status in apt package in Ubuntu: Invalid Status in containerd package in Ubuntu: Triaged Status in apt source package in Focal: Invalid Status in containerd source package in Focal: Triaged Bug description: Version of Ubuntu: Description:Ubuntu 22.04 LTS Release:22.04 kubeadm: Installed: 1.24.2-00 Candidate: 1.24.2-00 Package that has the problem: containerd: Installed: 1.5.9-0ubuntu3 Candidate: 1.5.9-0ubuntu3 Version table: *** 1.5.9-0ubuntu3 500 500 http://ro.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Problem: Kubeadm is not compatibile with this version of containerd that is installed by `apt install containerd`. If I use `kubeadm init` it will create a cluster which instead of staying alive will die after a couple of minutes. The problem is in the config file of containerd, which has the following parameter set to false: `SystemdCgroup = false` Solution: To solve this, the containerd config parameter SystemdCgroup needs to be set to true. It is set to true in the containerd v1.6.2, but by default, apt installs the version v1.5.9, which worked on Ubuntu 20.04 but does not work for Ubuntu 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1979313/+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 1979313] Re: kubeadm doesn't work with containerd version of apt install
Thanks for taking the time to report this bug and trying to make Ubuntu better. This seems to be a real issue, in the kubernetes documentation they tell users to set this variable to true: https://kubernetes.io/docs/setup/production-environment/container- runtimes/#containerd-systemd We are planning to update containerd to the latest upstream version which will fix this issue as you mentioned. While this does not happen here users can find a simple workaround for that. ** Changed in: containerd (Ubuntu) Status: New => Triaged ** Changed in: containerd (Ubuntu) Importance: Undecided => Low ** Changed in: apt (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1979313 Title: kubeadm doesn't work with containerd version of apt install Status in apt package in Ubuntu: Invalid Status in containerd package in Ubuntu: Triaged Bug description: Version of Ubuntu: Description:Ubuntu 22.04 LTS Release:22.04 kubeadm: Installed: 1.24.2-00 Candidate: 1.24.2-00 Package that has the problem: containerd: Installed: 1.5.9-0ubuntu3 Candidate: 1.5.9-0ubuntu3 Version table: *** 1.5.9-0ubuntu3 500 500 http://ro.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Problem: Kubeadm is not compatibile with this version of containerd that is installed by `apt install containerd`. If I use `kubeadm init` it will create a cluster which instead of staying alive will die after a couple of minutes. The problem is in the config file of containerd, which has the following parameter set to false: `SystemdCgroup = false` Solution: To solve this, the containerd config parameter SystemdCgroup needs to be set to true. It is set to true in the containerd v1.6.2, but by default, apt installs the version v1.5.9, which worked on Ubuntu 20.04 but does not work for Ubuntu 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1979313/+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 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1820584 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. Status in avahi package in Ubuntu: Confirmed Bug description: - Description: Ubuntu Disco Dingo (development branch) Release: 19.04 - seahorse: Installed: 3.32-1 Candidate: 3.32-1 Version table: *** 3.32-1 500 500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status - I have absolutely no idea why or how. Just collected this report from apport-cli. Some times receiving "internal error" reports, no details provided, just "Cancel" or "Send report" options. So, I decided to check apport and there was this report. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: seahorse 3.32-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 18:09:01 2019 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316) ProcCmdline: /usr/bin/seahorse --gapplication-service Signal: 6 SourcePackage: seahorse StacktraceTop: __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at assert.c:101 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+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
Re: [Touch-packages] [Bug 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Good point: since this is the first bug I have ever actively pursued, this is one of possibly many avenues I should follow. > On 9 Aug 2022, at 19:30, Thorsten Glaser <1954...@bugs.launchpad.net> wrote: > > Have you considered informing klibc upstream? (Granted, save for hpa > that’s basically the Debian maintainers, but they don’t necessarily get > Launchpad bugreports either.) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1983620). > https://bugs.launchpad.net/bugs/1954716 > > Title: > rpi nfsroot vers=4 not supported anymore? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Have you considered informing klibc upstream? (Granted, save for hpa that’s basically the Debian maintainers, but they don’t necessarily get Launchpad bugreports either.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf
** Changed in: systemd (Debian) Status: Incomplete => Fix Released -- 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/1892798 Title: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf Status in systemd package in Ubuntu: Won't Fix Status in wireguard package in Ubuntu: Confirmed Status in systemd package in Debian: Fix Released Bug description: By default Ubuntu now uses systemd to manage the nameservers in resolv.conf, so resolvconf and openresolv seem to be redundant. However, it appears that systemd's resolvectl is compatable with resolvconf style commands if symlinked as resolvconf. I'm not really sure how deb packaging works, but if it possible to check for the resolvconf command, and if not found just symlink /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work without additional packages. See https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8) for more info. Apologies if there is a better place to direct this info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
I encountered this crash after a fresh install of Ubuntu 22.04 LTS and reported it to the Ubuntu Error Tracker. After doing so I was able to find the following crash bucket with tens of thousands of incidents: https://errors.ubuntu.com/bucket/?id=/usr/bin/seahorse%3Aseahorse%3A%20glib- watch.c%3A195%3A%20timeout_update%3A%20Assertion%20%60%21t-%3Edead%27%20failed. ** Tags added: jammy rls-jj-incoming ** Changed in: avahi (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. Status in avahi package in Ubuntu: Confirmed Bug description: - Description: Ubuntu Disco Dingo (development branch) Release: 19.04 - seahorse: Installed: 3.32-1 Candidate: 3.32-1 Version table: *** 3.32-1 500 500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status - I have absolutely no idea why or how. Just collected this report from apport-cli. Some times receiving "internal error" reports, no details provided, just "Cancel" or "Send report" options. So, I decided to check apport and there was this report. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: seahorse 3.32-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 18:09:01 2019 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316) ProcCmdline: /usr/bin/seahorse --gapplication-service Signal: 6 SourcePackage: seahorse StacktraceTop: __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at assert.c:101 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+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 1982553] Re: Search domains not working after upgrading to Ubuntu 22.04
This might actually be an issue/change in systemd-resolved between Focal and Jammy. On Focal the search domain is appended even to FQDNs. On Jammy the search domain is only appended to single-label hostnames (hostnames containing no dots), to make them FQDNs. Would you mind sharing your output of `resolvectl` (from Focal & Jammy)? It needs more investigation. ** 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/1982553 Title: Search domains not working after upgrading to Ubuntu 22.04 Status in netplan.io package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Hello, After upgrading to Ubuntu 22.04, I noticed that search domains are not working anymore. Either I configure search domains via netplan or with graphical "nm- connection-editor", this is not taken into account when resolving domain names. For instance if I configure "domain.com" in search domains list, looking for "host" does not look for "host.domain.com". This is confirmed with a wireshark capture. Consequently if I want to connect with SSH to host.domain.com, I have to type the entire url. In Ubuntu 20.04 this works correctly. With a packet capture I can see one domain lookup for each of my search domains configured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1982553/+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 1983859] Re: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04
** Package changed: tracker (Ubuntu) => tracker-miners (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1983859 Title: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04 Status in tracker-miners package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty much always) a crash from tracker-extract, as described in the following error report: https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0 The crash occurs during the upgrade, which means it's fairly hard to investigate exactly what's going on as apport fails to extract a stack trace, the binaries being overwritten during the upgrade. However, the crash occurs because of a unhandled SIGSYS, meaning a seccomp filter issue. I've tried backporting this patch fixing a similar issue: https://gitlab.gnome.org/GNOME/tracker- miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef but it doesn't apply, likely due to the code having diverged too much since. My proposal is thus to disable tracker-extract during upgrade, including in all user sessions. I'm assuming that the new version will be enabled automatically as its unit file changed name anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1983859/+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 1981807] Re: qt5-network openssl3 armhf does not support tls1.3
This bug was fixed in the package qtbase-opensource-src - 5.15.4+dfsg-5
---
qtbase-opensource-src (5.15.4+dfsg-5) unstable; urgency=medium
* Add a patch to update signature of SSL_CTX_set_options for OpenSSL 3
(LP: #1981807). Thanks Michael Saxl!
-- Dmitry Shachnev Sun, 07 Aug 2022 16:56:40
+0300
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1981807
Title:
qt5-network openssl3 armhf does not support tls1.3
Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Bug description:
lsb_release
Description:Ubuntu 22.04 LTS
Release:22.04
libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf
the qt5 armhf version shipped with ubuntu jammy has a regression in
tls1.3 support (simply missing in runtime).
openssl supports tls1.3, so the underlying library works.
x86_64 is obviously not affected
the short sample applications writes -1 on armhf, 15 on x86_64 (unknown
protocol vs tls1.3)
QSslSocket* s = new QSslSocket();
QSslConfiguration cfg = s->sslConfiguration();
cfg.setProtocol(QSsl::TlsV1_3OrLater);
s->setSslConfiguration(cfg);
s->connectToHostEncrypted("tls13-enabled.server",443);
s->waitForConnected();
printf("%d\n",s->sessionProtocol());
marking it as security since the most secure tls protocol is not used
on some platforms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+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 1930482] Re: netplan crash on ubuntu 20.04 disabling network
Hi Nick,
I cannot longer reproduce this. This was about 1 year ago in a VPS in
OVH that we no longer have.
--
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/1930482
Title:
netplan crash on ubuntu 20.04 disabling network
Status in netplan:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Incomplete
Bug description:
On ubuntu 20.04 with netplan 0.102-0ubuntu1~20.04.2, the server loss
both IPv4 and IPv6 address in a while with DHCP config. The are no way
to restore network, only by rebooting the server.
Trying to restart the server networking using "systemctl restart
systemd-networkd" or "netplan apply" fails.
Note: systemctl and netplay apply fails also with a netplan with
static IP address
The server runs on OVS in cloud.ramnode.com
I'm pasting config, logs, netplan and restart output (IP and mac
address are masked)
I don't see a workaound yet, only to restart server to change the
network configuration.
File: 50-cloud-init.yaml
==
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
accept-ra: true
dhcp4: true
dhcp6: true
match:
macaddress: **:**:**:**:**:**:**
mtu: 1500
set-name: ens3
=
Syslog
=
2021-06-01T19:31:01.063935-04:00 server systemd[1]: Stopped Network Service.
2021-06-01T19:31:01.066766-04:00 server systemd[1]: Starting Network
Service...
2021-06-01T19:31:01.161797-04:00 server systemd-networkd[2302]:
/run/systemd/network/10-netplan-ens3.network: MTUBytes= in [Link] section and
UseMTU= in [DHCP] section are set. Disabling UseMTU=.
2021-06-01T19:31:01.161990-04:00 server systemd-networkd[2302]: loop3456:
netdev ready
2021-06-01T19:31:01.162073-04:00 server systemd-networkd[2302]: Tunnel127:
Gained IPv6LL
2021-06-01T19:31:01.162184-04:00 server systemd-networkd[2302]: Tunnel126:
Gained IPv6LL
2021-06-01T19:31:01.162275-04:00 server systemd-networkd[2302]: loop3456:
Gained IPv6LL
2021-06-01T19:31:01.162349-04:00 server systemd-networkd[2302]: ens3: Gained
IPv6LL
2021-06-01T19:31:01.164685-04:00 server systemd-networkd[2302]: Assertion
'ifindex' failed at src/network/networkd-link.c:757, function link_get().
Aborting.
2021-06-01T19:31:01.553611-04:00 server systemd[1]: systemd-networkd.service:
Main process exited, code=dumped, status=6/ABRT
2021-06-01T19:31:01.553796-04:00 server systemd[1]: systemd-networkd.service:
Failed with result 'core-dump'.
2021-06-01T19:31:01.553892-04:00 server systemd[1]: Failed to start Network
Service.
2021-06-01T19:31:01.553983-04:00 server systemd[1]: systemd-networkd.service:
Scheduled restart job, restart counter is at 2.
output of: netapply --debug try
DEBUG:ens3 not found in {}
DEBUG:loop3456 not found in {}
DEBUG:Merged config:
network:
bridges:
loop3456:
accept-ra: false
addresses:
- 10.65.0.3/32
dhcp4: false
dhcp6: false
interfaces: []
ethernets:
ens3:
accept-ra: true
addresses:
- XXX.XXX.XXX.XXX/24
dhcp4: false
dhcp6: true
gateway4: XXX.XXX.XXX.XXX
match:
macaddress: **:**:**:**:**:**:**
mtu: 1500
nameservers:
addresses:
- 8.8.8.8
- 8.8.4.4
search:
- uc.edu.ve
set-name: ens3
version: 2
DEBUG:New interfaces: set()
** (generate:1484): DEBUG: 20:14:22.895: Processing input file
/etc/netplan/50-static.yaml..
** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
** (generate:1484): DEBUG: 20:14:22.895: Processing input file
/etc/netplan/99-local.yaml..
** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
** (generate:1484): DEBUG: 20:14:22.895: We have some netdefs, pass them
through a final round of validation
** (generate:1484): DEBUG: 20:14:22.895: ens3: setting default backend to 1
** (generate:1484): DEBUG: 20:14:22.895: Configuration is valid
** (generate:1484): DEBUG: 20:14:22.895: loop3456: setting default backend to
1
** (generate:1484): DEBUG: 20:14:22.895: Configuration is valid
** (generate:1484): DEBUG: 20:14:22.896: Generating output files..
** (generate:1484):
[Touch-packages] [Bug 1984107] [NEW] Printer SSL certificates are added but never removed, resulting in "no suitable destination host found by cups-browsed"
Public bug reported: If a printer preferrably prints through ipps, Cups will store the printers (self signed) certificate in /etc/cups/ssl/ However, if this certificate becomes outdated or invalid, or if it changes, it will *not be removed* and Cups only complains that the "backend returned status 4", "No suitable destination host found by cups-browsed". Even removing the printer manually will not remove the old certificate, rendering the printer invalid for life: when te printer re-appears, the old, invalid certificate is still there, resulting in the printer still not working. Steps to reproduce: - use a printer that prefers ipps, let's call it printer_bob - let this printer appear in your printer list - make a test print - Now remove the printer and check that the certificate will survive: lpadmin -x printer_bob; ls -al /etc/cups/ssl/*bob*crt What happens: - certificate is still there What should happen: - a removed printer should not have a certificate left Now in this example, it's rather harmless because the certificate is probably still valid. But a printer update, rename or otherwise will render it invalid and printing will become impossible. You could simulate a name change for printers: mv /etc/cups/ssl/printer-carol.local.crt /etc/cups/ssl/printer-bob.local.crt Or simply mess up the certificate: sed -i '2s/./a/g' /etc/cups/ssl/printer-bob.local.crt After this, you will *not* be able to print to printer-bob, because bob has the wrong certificate (obviously). Removing printer-bob does not help. You will need to manually remove the certificate in order to make bob print again. /var/log/cups/error.log will only say that "no suitable destination host found", which is not true: there *is* a destination but the SSL certificate does not match and Cups will only try the first printing method, ipps. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Printer SSL certificates are added but never removed, resulting in non working printers + Printer SSL certificates are added but never removed, resulting in "no suitable destination host found by cups-browsed" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1984107 Title: Printer SSL certificates are added but never removed, resulting in "no suitable destination host found by cups-browsed" Status in cups package in Ubuntu: New Bug description: If a printer preferrably prints through ipps, Cups will store the printers (self signed) certificate in /etc/cups/ssl/ However, if this certificate becomes outdated or invalid, or if it changes, it will *not be removed* and Cups only complains that the "backend returned status 4", "No suitable destination host found by cups-browsed". Even removing the printer manually will not remove the old certificate, rendering the printer invalid for life: when te printer re-appears, the old, invalid certificate is still there, resulting in the printer still not working. Steps to reproduce: - use a printer that prefers ipps, let's call it printer_bob - let this printer appear in your printer list - make a test print - Now remove the printer and check that the certificate will survive: lpadmin -x printer_bob; ls -al /etc/cups/ssl/*bob*crt What happens: - certificate is still there What should happen: - a removed printer should not have a certificate left Now in this example, it's rather harmless because the certificate is probably still valid. But a printer update, rename or otherwise will render it invalid and printing will become impossible. You could simulate a name change for printers: mv /etc/cups/ssl/printer-carol.local.crt /etc/cups/ssl/printer-bob.local.crt Or simply mess up the certificate: sed -i '2s/./a/g' /etc/cups/ssl/printer-bob.local.crt After this, you will *not* be able to print to printer-bob, because bob has the wrong certificate (obviously). Removing printer-bob does not help. You will need to manually remove the certificate in order to make bob print again. /var/log/cups/error.log will only say that "no suitable destination host found", which is not true: there *is* a destination but the SSL certificate does not match and Cups will only try the first printing method, ipps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1984107/+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 1984058] Re: File size mismatch with http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages.xz
*** This bug is a duplicate of bug 1976233 *** https://bugs.launchpad.net/bugs/1976233 ** This bug has been marked a duplicate of bug 1976233 "File has unexpected size" error on Focal ddebs repository -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1984058 Title: File size mismatch with http://ddebs.ubuntu.com/dists/focal- updates/main/binary-amd64/Packages.xz Status in apt package in Ubuntu: New Bug description: Steps to reproduce: 1. configured debug repo with vim into /etc/apt/source.list like: deb http://ddebs.ubuntu.com/ubuntu/ focal-updates main Did that in a docker container where the following is installed: apt update; apt-get install -y ca-certificates; apt install curl -y; apt install vim -y; apt install gnupg -y 2.add the GPG key with apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3. apt clean before I fired up apt update. Then the file size mismatch: Err:4 http://ddebs.ubuntu.com focal-updates/main amd64 Packages File has unexpected size (480536 != 480068). Mirror sync in progress? [IP: 185.125.190.18 80] Hashes of expected file: - Filesize:480068 [weak] - SHA512:e54fc7753595b90e1acc1a5f6660f2755965b40329b56bf5326ead40cc702fa920d972331994c4fb789ffbc85a35387442258e29e16f6ffd7c2599ce16bfb9be - SHA256:09419d32f4ea0298bebc27026a2401a3c5468fbb64a9d8568d51060e10969a3a - SHA1:ba9b972190d2bbfbd12b5eea1dab1274a122124e [weak] - MD5Sum:08a8d42aa6f1782d1ca490b21ab12fd3 [weak] Release file created at: Wed, 27 Jul 2022 20:48:02 + Fetched 42.7 kB in 1s (30.3 kB/s) Reading package lists... Done E: Failed to fetch http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages.xz File has unexpected size (480536 != 480068). Mirror sync in progress? [IP: 185.125.190.18 80] Hashes of expected file: - Filesize:480068 [weak] - SHA512:e54fc7753595b90e1acc1a5f6660f2755965b40329b56bf5326ead40cc702fa920d972331994c4fb789ffbc85a35387442258e29e16f6ffd7c2599ce16bfb9be - SHA256:09419d32f4ea0298bebc27026a2401a3c5468fbb64a9d8568d51060e10969a3a - SHA1:ba9b972190d2bbfbd12b5eea1dab1274a122124e [weak] - MD5Sum:08a8d42aa6f1782d1ca490b21ab12fd3 [weak] Release file created at: Wed, 27 Jul 2022 20:48:02 + E: Some index files failed to download. They have been ignored, or old ones used instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.6 Uname: Linux 121a7a7831cf 5.10.104-linuxkit x86_64 Architecture: amd64 Date: Tue 09 Aug 2022 09:11:32 AM UTC SourcePackage: apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1984058/+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
Re: [Touch-packages] [Bug 1954716] Re: rpi nfsroot vers=4 not supported anymore?
I will test the work-around, but I won’t get round to it before the end of the week. > On 9 Aug 2022, at 13:55, Juerg Haefliger <1954...@bugs.launchpad.net> wrote: > > Please do test the work-around. If indeed NFSv4 solves your overlayfs > problem then that would be another reason for fixing nfsmount. > > We can carry Ubuntu specific fixes if for some reason Debian doesn't > want them but the preferred way is obviously to fix it in Debian so that > it tickles down naturally to Ubuntu (and other Debian based distros). > > I'm looking at it atm but NFS is not my strong suit :-) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1983620). > https://bugs.launchpad.net/bugs/1954716 > > Title: > rpi nfsroot vers=4 not supported anymore? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1802521] Re: ubuntu-bug hangs when Cancel button pressed
Thanks for reporting the bug and providing an easy step to reproduce. I could kind-of reproduce this behavior in a Ubuntu 20.04 (focal) VM: Run "ubuntu-bug gnome-terminal" and then click directly on abort. The windows froze for several seconds (but not mintues) until it closes. On Ubuntu 22.04 it hang for around three seconds. On Ubuntu 18.04 it hang for around 4 seconds. I don't know why the window hanged for several minutes on your system (maybe your system is significant slower or you hit another bug as well. Apport should instantly hide the window and stop the collection. ** Changed in: apport (Ubuntu) Status: New => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Low -- 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/1802521 Title: ubuntu-bug hangs when Cancel button pressed Status in apport package in Ubuntu: Triaged Bug description: I ran `ubuntu-bug gnome-terminal`, but then realized a second or so later that's not what I had intended to do. I therefore clicked the Cancel button on the "Collecting problem information / Information is being collected that may help the developers fix the problem you report." dialog that had popped up. It hung, i.e., the back-and-forth progress bar in the dialog stopped moving, and nothing else happened, and it's still sitting several minutes later doing nothing. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu13 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 9 09:21:14 2018 InstallationDate: Installed on 2018-09-27 (42 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to cosmic on 2018-11-08 (0 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1802521/+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 1984067] Re: Xorg crash
** Attachment added: "xorg.1 file from crashed session" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1984067/+attachment/5607529/+files/Xorg.1.log.old -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1984067 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: All logs should be added automatically but the central issue is: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Backtrace: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b7984596e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f3e6a242520] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x55b7982ee1e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x55b7982efc85] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x55b7982f0183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x55b7982f1183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x55b7983cfa7d] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x55b7983f9e4c] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x55b7983f2f21] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x55b7983f311e] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x55b798452c60] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x55b798452ee8] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55b7982e3257] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x55b7982e7524] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f3e6a229d90] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f3e6a229e40] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x55b7982d05f5] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Segmentation fault at address 0x7ffc51d3 Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Fatal server error: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Caught signal 11 (Segmentation fault). Server aborting Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Please consult the The X.Org Foundation support Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: #011 at http://wiki.x.org Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: for help. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None
[Touch-packages] [Bug 1984067] [NEW] Xorg crash
Public bug reported: All logs should be added automatically but the central issue is: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Backtrace: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b7984596e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f3e6a242520] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x55b7982ee1e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x55b7982efc85] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x55b7982f0183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x55b7982f1183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x55b7983cfa7d] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x55b7983f9e4c] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x55b7983f2f21] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x55b7983f311e] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x55b798452c60] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x55b798452ee8] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55b7982e3257] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x55b7982e7524] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f3e6a229d90] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f3e6a229e40] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x55b7982d05f5] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Segmentation fault at address 0x7ffc51d3 Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Fatal server error: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Caught signal 11 (Segmentation fault). Server aborting Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Please consult the The X.Org Foundation support Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: #011 at http://wiki.x.org Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: for help. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 9 15:22:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: acpi-call/1.2.2, 5.15.0-41-generic, x86_64: installed acpi-call/1.2.2, 5.15.0-43-generic, x86_64: installed fwts-efi-runtime-dkms/22.03.00, 5.15.0-41-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/22.03.00, 5.15.0-43-generic, x86_64: installed (WARNING! Diff between built and installed module!) DpkgLog:
[Touch-packages] [Bug 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Please do test the work-around. If indeed NFSv4 solves your overlayfs problem then that would be another reason for fixing nfsmount. We can carry Ubuntu specific fixes if for some reason Debian doesn't want them but the preferred way is obviously to fix it in Debian so that it tickles down naturally to Ubuntu (and other Debian based distros). I'm looking at it atm but NFS is not my strong suit :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
** Changed in: gdk-pixbuf (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: Fix Released Status in gdk-pixbuf source package in Focal: Fix Released Bug description: [Impact] * A buffer overwrite exists in gdk-pixbuf's thumbnailer. * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. * Or, in other ways, bad gif files in other applications can open the door for exploits. * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] * Take the POC's - they can be found in the issue in the GNOME repo * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - Nautilus, GNOME's file manager - Nemo, Cinnamon's file manager - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes - PCManFM, LXDE's file manager which straight up crashes - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app still usable, no memory issues) - Eye of GNOME (eog) triggers the segfault in syslog - Eye of MATE (eom) segfaults * If you or the system couldn't tell something is wrong, cat /var/log/syslog and enjoy the segfaults or out of memory warnings or even kernel spam. [Where problems could occur] * The patch itself is simple, but since gdk-pixbuf is often used with GTK apps a mistake here could be problematic. * It is possible, and has happened in the past (which has been patched) that other bad GIFs can cause other crashes. * That patch is essentially overflow checks - changes with GLib (GNOME's, not to be confused with glibc) and the functions used in not only the patch but all of gdk-pixbuf can cause problems * Other failures to properly handle GIFs and broken or intentionally tampered GIFs can continue and always will open the door for security holes for other bugs * Again, overall a simple patch but as long as the GIFs remain handled properly, and no changes to the GLib functions are made and to other apps that use gdk-pixbuf (and assuming are not affected by the change and still work), the patch does not have much regression potential. [Other Info] * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. * Files attached are examples or crashes * Again, all apps using gdk-pixbuf are affected * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 * https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Thanks Juerg, you’ve been very helpful. Presumably there is no quick fix for this because of the klibc/glibc thing, so it’s an architectural rather than a programming issue. And it needs to be fixed in Debian rather than in Ubuntu. I’d offer to help but I arrived here after drilling down from a completely different realm and it’s outside my comfort zone. I want to evaluate the work-around against using RaspiOS before deciding how to proceed. Is there any way of crowd-funding bug fixing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1975383] Re: Please enable vmci support
You should probably report it to Debian: https://bugs.debian.org/cgi- bin/pkgreport.cgi?repeatmerged=no=zeromq3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1975383 Title: Please enable vmci support Status in zeromq3 package in Ubuntu: New Bug description: zmq supports vsock for communication between virtual machines and hosts. For example, to listen on a vsock port you can specify vmci://*: for the socket. This feature is enabled with the option '--with-vmci' for the configure script. I have made that change in the debian/rules file and the resulting package works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1975383/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
** No longer affects: linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: New Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1983859] Re: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04
I tried to produce a usable backtrace by copying the crash file back to a VM that were in the state before the upgrade, but the backtrace there has GDB warnings: Section `.reg-xstate/$number' in core file too small. I assume that the crash happens when already some package were updated. What I saw the the journal log: dbus-daemon[813]: Unknown group "power" in message bus configuration file You can try to create the GDB backtrace directly after the crash. Modify ExecStart in /usr/lib/systemd/user/tracker-extract.service to: ExecStart=/usr/bin/gdb --batch --ex run --ex bt /usr/libexec/tracker- extract -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1983859 Title: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04 Status in tracker package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty much always) a crash from tracker-extract, as described in the following error report: https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0 The crash occurs during the upgrade, which means it's fairly hard to investigate exactly what's going on as apport fails to extract a stack trace, the binaries being overwritten during the upgrade. However, the crash occurs because of a unhandled SIGSYS, meaning a seccomp filter issue. I've tried backporting this patch fixing a similar issue: https://gitlab.gnome.org/GNOME/tracker- miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef but it doesn't apply, likely due to the code having diverged too much since. My proposal is thus to disable tracker-extract during upgrade, including in all user sessions. I'm assuming that the new version will be enabled automatically as its unit file changed name anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1983859/+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 1983998] Re: USB sound card not detected
Hello Erich! May be it is really inappropriate project to report but i found that usbc not working at all. I suspect usb power problems in kernel. Please help me to find appropriate project on launchpad (i'm new here). As i understand, device will not be disconnected in case of just not compliant to anything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1983998 Title: USB sound card not detected Status in alsa-driver package in Ubuntu: Invalid Bug description: usbc mics https://www.boya-mic.com/lavaliermicrophones/1430.html connects and immediately disconnects, ls usb hangs for a while, when usbc device is connected. it works on win laptop well. ``` [10877.622942] usb 3-4: new full-speed USB device number 28 using xhci_hcd [10877.779590] usb 3-4: New USB device found, idVendor=0c76, idProduct=153f, bcdDevice= 1.00 [10877.779596] usb 3-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [10877.779599] usb 3-4: Product: USB PnP Audio Device [10877.983589] usb 3-4: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10877.983593] usb 3-4: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16 [10878.009593] usb 3-4: Warning! Unlikely big volume range (=1008), cval->res is probably wrong. [10878.009597] usb 3-4: [49] FU [Speaker Playback Volume] ch = 2, val = -16129/-1/16 [10878.035587] usb 3-4: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.035591] usb 3-4: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16 [10878.038757] input: USB PnP Audio Device as /devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-4/3-4:1.3/0003:0C76:153F.001B/input/input45 [10878.095081] hid-generic 0003:0C76:153F.001B: input,hidraw6: USB HID v1.00 Device [USB PnP Audio Device] on usb-:06:00.3-4/input3 [10878.095179] usb 3-3: USB disconnect, device number 27 [10878.426945] usb 3-3: new full-speed USB device number 29 using xhci_hcd [10878.587590] usb 3-3: New USB device found, idVendor=0c76, idProduct=153f, bcdDevice= 1.00 [10878.587597] usb 3-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [10878.587599] usb 3-3: Product: USB PnP Audio Device [10878.783592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.783597] usb 3-3: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16 [10878.809597] usb 3-3: Warning! Unlikely big volume range (=1008), cval->res is probably wrong. [10878.809601] usb 3-3: [49] FU [Speaker Playback Volume] ch = 2, val = -16129/-1/16 [10878.835592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.835596] usb 3-3: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16 [10878.838754] input: USB PnP Audio Device as /devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-3/3-3:1.3/0003:0C76:153F.001C/input/input46 [10878.895092] hid-generic 0003:0C76:153F.001C: input,hidraw5: USB HID v1.00 Device [USB PnP Audio Device] on usb-:06:00.3-3/input3 [10878.895190] usb 3-4: USB disconnect, device number 28 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-45.48-generic 5.15.39 Uname: Linux 5.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vany 12211 F pulseaudio /dev/snd/controlC0: vany 12211 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 8 18:28:32 2022 InstallationDate: Installed on 2020-11-26 (619 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to jammy on 2022-05-23 (76 days ago) dmi.bios.date: 04/01/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1407 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1407:bd04/01/2020:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To
[Touch-packages] [Bug 1984058] [NEW] File size mismatch with http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages.xz
Public bug reported: Steps to reproduce: 1. configured debug repo with vim into /etc/apt/source.list like: deb http://ddebs.ubuntu.com/ubuntu/ focal-updates main Did that in a docker container where the following is installed: apt update; apt-get install -y ca-certificates; apt install curl -y; apt install vim -y; apt install gnupg -y 2.add the GPG key with apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3. apt clean before I fired up apt update. Then the file size mismatch: Err:4 http://ddebs.ubuntu.com focal-updates/main amd64 Packages File has unexpected size (480536 != 480068). Mirror sync in progress? [IP: 185.125.190.18 80] Hashes of expected file: - Filesize:480068 [weak] - SHA512:e54fc7753595b90e1acc1a5f6660f2755965b40329b56bf5326ead40cc702fa920d972331994c4fb789ffbc85a35387442258e29e16f6ffd7c2599ce16bfb9be - SHA256:09419d32f4ea0298bebc27026a2401a3c5468fbb64a9d8568d51060e10969a3a - SHA1:ba9b972190d2bbfbd12b5eea1dab1274a122124e [weak] - MD5Sum:08a8d42aa6f1782d1ca490b21ab12fd3 [weak] Release file created at: Wed, 27 Jul 2022 20:48:02 + Fetched 42.7 kB in 1s (30.3 kB/s) Reading package lists... Done E: Failed to fetch http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages.xz File has unexpected size (480536 != 480068). Mirror sync in progress? [IP: 185.125.190.18 80] Hashes of expected file: - Filesize:480068 [weak] - SHA512:e54fc7753595b90e1acc1a5f6660f2755965b40329b56bf5326ead40cc702fa920d972331994c4fb789ffbc85a35387442258e29e16f6ffd7c2599ce16bfb9be - SHA256:09419d32f4ea0298bebc27026a2401a3c5468fbb64a9d8568d51060e10969a3a - SHA1:ba9b972190d2bbfbd12b5eea1dab1274a122124e [weak] - MD5Sum:08a8d42aa6f1782d1ca490b21ab12fd3 [weak] Release file created at: Wed, 27 Jul 2022 20:48:02 + E: Some index files failed to download. They have been ignored, or old ones used instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.6 Uname: Linux 121a7a7831cf 5.10.104-linuxkit x86_64 Architecture: amd64 Date: Tue 09 Aug 2022 09:11:32 AM UTC SourcePackage: apt ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1984058 Title: File size mismatch with http://ddebs.ubuntu.com/dists/focal- updates/main/binary-amd64/Packages.xz Status in apt package in Ubuntu: New Bug description: Steps to reproduce: 1. configured debug repo with vim into /etc/apt/source.list like: deb http://ddebs.ubuntu.com/ubuntu/ focal-updates main Did that in a docker container where the following is installed: apt update; apt-get install -y ca-certificates; apt install curl -y; apt install vim -y; apt install gnupg -y 2.add the GPG key with apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3. apt clean before I fired up apt update. Then the file size mismatch: Err:4 http://ddebs.ubuntu.com focal-updates/main amd64 Packages File has unexpected size (480536 != 480068). Mirror sync in progress? [IP: 185.125.190.18 80] Hashes of expected file: - Filesize:480068 [weak] - SHA512:e54fc7753595b90e1acc1a5f6660f2755965b40329b56bf5326ead40cc702fa920d972331994c4fb789ffbc85a35387442258e29e16f6ffd7c2599ce16bfb9be - SHA256:09419d32f4ea0298bebc27026a2401a3c5468fbb64a9d8568d51060e10969a3a - SHA1:ba9b972190d2bbfbd12b5eea1dab1274a122124e [weak] - MD5Sum:08a8d42aa6f1782d1ca490b21ab12fd3 [weak] Release file created at: Wed, 27 Jul 2022 20:48:02 + Fetched 42.7 kB in 1s (30.3 kB/s) Reading package lists... Done E: Failed to fetch http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages.xz File has unexpected size (480536 != 480068). Mirror sync in progress? [IP: 185.125.190.18 80] Hashes of expected file: - Filesize:480068 [weak] - SHA512:e54fc7753595b90e1acc1a5f6660f2755965b40329b56bf5326ead40cc702fa920d972331994c4fb789ffbc85a35387442258e29e16f6ffd7c2599ce16bfb9be - SHA256:09419d32f4ea0298bebc27026a2401a3c5468fbb64a9d8568d51060e10969a3a - SHA1:ba9b972190d2bbfbd12b5eea1dab1274a122124e [weak] - MD5Sum:08a8d42aa6f1782d1ca490b21ab12fd3 [weak] Release file created at: Wed, 27 Jul 2022 20:48:02 + E: Some index files failed to download. They have been ignored, or old ones used instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.6 Uname: Linux 121a7a7831cf 5.10.104-linuxkit x86_64 Architecture: amd64 Date: Tue 09 Aug 2022 09:11:32 AM UTC SourcePackage: apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1984058/+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 1954716] Re: rpi nfsroot vers=4 not supported anymore?
It simply means that the ticket has been acknowledged as a bug/issue, nothing more. As you might have noticed it's been reported in Debian in 2007, so it doesn't seem to be that important. I know that doesn't help you but the fact that there's a work-around makes it even less important. I'll take a look, no guarantees. As for reporting issues, it might help to jump in an IRC channel [1] and harass people directly, then it's harder for them to ignore you ;-) [1] https://wiki.ubuntu.com/IRC/ChannelList -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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
