[Touch-packages] [Bug 920749] Re: pam configuration for SSH prevents LANG override
I feel like this setup violates the principle of least surprise. As a user, sshing into a machine, I have my ssh client configured to SendEnv LC_* and LANG. Awesome. Look, /etc/ssh/sshd_config, the server is even accepting these in its default configuration! Except some setting that I *personally* never would have thought of in pam configuration, completely outside of the control of a mere mortal (read: non-root user) comes in and sets the locale to whatever the person who set up the machine originally configured. And I have no real control over it. I do recognize the issue raised when there's a difference in client/server locale meanings (my en_US is your en_US.utf8 I think is one someone mentioned), but I feel like that's solveable on the client side by specifying different values to be sent for those variables in their ssh configuration (SetEnv option) Even the ssh_config manpage specifies that... > the Debian openssh-client package sets several options as standard in > /etc/ssh/ssh_config which are not the default in ssh(1): > * SendEnv LANG LC_* So why would it then have a default configuration to stomp all over those environment variables? Am I missing something? I'm not even a non-english user, I was just trying to figure out why emacs when I ssh in shows \u2505 instead of a fancy pipe character, but when I use mosh it works fine, and fell down this rabbit hole :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/920749 Title: pam configuration for SSH prevents LANG override Status in portable OpenSSH: Confirmed Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: Confirmed Bug description: The default /etc/pam.d/sshd configuration has: # Read environment variables from /etc/environment and # /etc/security/pam_env.conf. #auth required pam_env.so # [1] # In Debian 4.0 (etch), locale-related environment variables were moved to # /etc/default/locale, so read that as well. auth required pam_env.so envfile=/etc/default/locale The default SSH client configuration has "Send LC_*" and the default SSH server configuration has "Accept LC_*". The PAM configuration prevents any user-overrides for locale settings. For example, if /etc/default/locale has: LANG=en_US.UTF-8 LC_COLLATE=C Then running "LANG=zh_SG.utf8 LC_COLLATE=en_US.UTF-8 ssh myspecialhost.foo.bar.com" yields: ubuntu@ip-10-12-15-243:~$ locale LANG=en_US.UTF-8 LC_COLLATE=C (output truncated for clarity) While having a blank /etc/default/locale yeilds: ubuntu@ip-10-12-15-243:~$ locale locale: Cannot set LC_ALL to default locale: No such file or directory LANG=zh_SG.utf8 LC_COLLATE=en_US.UTF-8 (output truncated for clarity) I think, although I am not sure, that this is a bug with the default configuration. It means that in order for server to accept multple languages or LC_* bindings, the system locale default would have to be unset. Effectively this is forcing the system default on all users. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/920749/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
Same issues with JBL E50BT!!! :-/ Only the output is working (A2DP-Profil). But that's it no matter what changes I make to config's. - Microphone is not working (no matter what profil is chosen) - On A2DP listening to audio is possible Ubuntu 20.04 - Linux 5.4.0-37-generic pulseaudio 1:13.99.1-1ubuntu3.3 amd64 bluez 5.53-0ubuntu3 amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1877633] Autopkgtest regression report (libseccomp/2.4.3-1ubuntu3.16.04.2)
All autopkgtests for the newly accepted libseccomp (2.4.3-1ubuntu3.16.04.2) for xenial have finished running. The following regressions have been reported in tests triggered by the package: systemd/229-4ubuntu21.28 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/xenial/update_excuses.html#libseccomp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Focal: In Progress Status in libseccomp source package in Groovy: Fix Released Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1876055] Autopkgtest regression report (libseccomp/2.4.3-1ubuntu3.16.04.2)
All autopkgtests for the newly accepted libseccomp (2.4.3-1ubuntu3.16.04.2) for xenial have finished running. The following regressions have been reported in tests triggered by the package: systemd/229-4ubuntu21.28 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/xenial/update_excuses.html#libseccomp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876055 Title: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: Fix Committed Status in libseccomp source package in Bionic: Fix Committed Status in libseccomp source package in Eoan: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: [Impact] The combination of snap-confine and snap-seccomp from snapd uses libseccomp to filter various system calls for confinement. The current version in eoan/bionic/xenial (2.4.1) is missing knowledge of various system calls for various architectures. As such this causes strange issues like python snaps segfaulting (https://github.com/snapcore/core20/issues/48) or the inadvertent denial of system calls which should be permitted by the base policy (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237). libseccomp in groovy is using the latest upstream base release (2.4.3) plus it includes a patch to add some missing aarch64 system calls (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633). SRUing this version back to older stable releases allows libseccomp to operate correctly on all supported architectures. Included as part of this SRU are test-suite reliability improvements - currently the xenial libseccomp package overrides test-suite failures at build time to ignore failures. This masks the fact that on ppc64el and s390x there are currently test suite failures at build time for xenial - these failures occur since libseccomp now includes knowledge of system calls for these architectures but which the linux-libc-dev package for xenial does not actually define (since this is based of the 4.4 kernel in xenial whereas libseccomp 2.4.1 in xenial has knowledge of all system calls up to 5.4). In this SRU I have instead fixed the test suite failures for xenial by including a local (test-suite specific) set of architecture specific kernel headers from the linux-libc-dev in focal for all releases. These are just the headers which define the system call numbers for each architecture *and* these are added to tests/include/$ARCH in the source package (and tests/Makefile.am is then updated to include these new headers only). As such this ensures the actual build of libseccomp or any of the tools does not reference these headers. This allows the test suite in libseccomp to then be aware of theses system calls and so all unit tests for all architectures now pass. In any future updates for libseccomp to add new system calls, we can then similarly update these local headers to ensure the unit tests continue to work as expected. [Test Case] libseccomp includes a significant unit test suite that is run during the build and as part of autopkgtests. To verify the new aarch64 system calls are resolved as expected the scmp_sys_resolver command can be used as well: $ scmp_sys_resolver -a aarch64 getrlimit 163 (whereas in the current version in focal this returns -10180 as libseccomp was not aware of this system-call at compile-time). As part of this SRU, the test suite in libseccomp has been patched to include a local copy of the architecture-specific kernel headers from the 5.4 kernel in focal *for all releases*, so that all system calls which are defined for the 5.4 kernel are known about *for the libseccomp test suite*. This allows all unit tests to pass on older releases as well and defaults the build to fail on unit test failures (whereas currently in xenial this has been overridden to ignore failures). [Regression Potential] This has a low regression potential due to significant testing with many packages that depend on libseccomp (lxc, qemu, snapd, apt, man etc) and none have shown any regression using this new version. The re-enablement of build failure on test failure at build time also ensures that we can reliably detect FTBFS issues in the future. No symbols hav
[Touch-packages] [Bug 1876882] Re: Backport packages for 18.04.5 HWE stack
I'll open a separate bug for the migration to llvm 10, so dropping libclc from here ** Changed in: libclc (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1876882 Title: Backport packages for 18.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-10 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Invalid Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-10 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.5 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-10: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 20.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any [Other info] mesa and libclc will migrate to llvm-10 in a separate upload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1876882/+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 1882901] [NEW] Migrate mesa to llvm 10
Public bug reported: [Impact] Mesa should migrate to llvm 10. Focal didn't migrate to it before release, because there was a build issue on ppc64el, which has since been fixed. [Test case] Test AMD graphics after installing migrated packages. [Regression potential] This has been in Debian for a month now without issues. ** Affects: libclc (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: libclc (Ubuntu Bionic) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Affects: mesa (Ubuntu Bionic) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Affects: libclc (Ubuntu Focal) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Affects: mesa (Ubuntu Focal) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libclc (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libclc (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: - WIP + [Impact] + + Mesa should migrate to llvm 10. Focal didn't migrate to it before + release, because there was a build issue on ppc64el, which has since + been fixed. + + [Test case] + + Test AMD graphics after installing migrated packages. + + [Regression potential] + + This has been in Debian for a month now without issues. ** Changed in: libclc (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: libclc (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1882901 Title: Migrate mesa to llvm 10 Status in libclc package in Ubuntu: New Status in mesa package in Ubuntu: New Status in libclc source package in Bionic: New Status in mesa source package in Bionic: New Status in libclc source package in Focal: New Status in mesa source package in Focal: New Bug description: [Impact] Mesa should migrate to llvm 10. Focal didn't migrate to it before release, because there was a build issue on ppc64el, which has since been fixed. [Test case] Test AMD graphics after installing migrated packages. [Regression potential] This has been in Debian for a month now without issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1882901/+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 1877633] Autopkgtest regression report (libseccomp/2.4.3-1ubuntu3.18.04.2)
All autopkgtests for the newly accepted libseccomp (2.4.3-1ubuntu3.18.04.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apt/1.6.12ubuntu0.1 (arm64) chrony/3.2-4ubuntu4.4 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#libseccomp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Focal: In Progress Status in libseccomp source package in Groovy: Fix Released Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1876055] Autopkgtest regression report (libseccomp/2.4.3-1ubuntu3.18.04.2)
All autopkgtests for the newly accepted libseccomp (2.4.3-1ubuntu3.18.04.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apt/1.6.12ubuntu0.1 (arm64) chrony/3.2-4ubuntu4.4 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#libseccomp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876055 Title: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: Fix Committed Status in libseccomp source package in Bionic: Fix Committed Status in libseccomp source package in Eoan: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: [Impact] The combination of snap-confine and snap-seccomp from snapd uses libseccomp to filter various system calls for confinement. The current version in eoan/bionic/xenial (2.4.1) is missing knowledge of various system calls for various architectures. As such this causes strange issues like python snaps segfaulting (https://github.com/snapcore/core20/issues/48) or the inadvertent denial of system calls which should be permitted by the base policy (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237). libseccomp in groovy is using the latest upstream base release (2.4.3) plus it includes a patch to add some missing aarch64 system calls (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633). SRUing this version back to older stable releases allows libseccomp to operate correctly on all supported architectures. Included as part of this SRU are test-suite reliability improvements - currently the xenial libseccomp package overrides test-suite failures at build time to ignore failures. This masks the fact that on ppc64el and s390x there are currently test suite failures at build time for xenial - these failures occur since libseccomp now includes knowledge of system calls for these architectures but which the linux-libc-dev package for xenial does not actually define (since this is based of the 4.4 kernel in xenial whereas libseccomp 2.4.1 in xenial has knowledge of all system calls up to 5.4). In this SRU I have instead fixed the test suite failures for xenial by including a local (test-suite specific) set of architecture specific kernel headers from the linux-libc-dev in focal for all releases. These are just the headers which define the system call numbers for each architecture *and* these are added to tests/include/$ARCH in the source package (and tests/Makefile.am is then updated to include these new headers only). As such this ensures the actual build of libseccomp or any of the tools does not reference these headers. This allows the test suite in libseccomp to then be aware of theses system calls and so all unit tests for all architectures now pass. In any future updates for libseccomp to add new system calls, we can then similarly update these local headers to ensure the unit tests continue to work as expected. [Test Case] libseccomp includes a significant unit test suite that is run during the build and as part of autopkgtests. To verify the new aarch64 system calls are resolved as expected the scmp_sys_resolver command can be used as well: $ scmp_sys_resolver -a aarch64 getrlimit 163 (whereas in the current version in focal this returns -10180 as libseccomp was not aware of this system-call at compile-time). As part of this SRU, the test suite in libseccomp has been patched to include a local copy of the architecture-specific kernel headers from the 5.4 kernel in focal *for all releases*, so that all system calls which are defined for the 5.4 kernel are known about *for the libseccomp test suite*. This allows all unit tests to pass on older releases as well and defaults the build to fail on unit test failures (whereas currently in xenial this has been overridden to ignore failures). [Regression Potential] This has a low regression potential due to significant testing with many packages that depend on libseccomp (lxc, qemu, snapd, apt, man etc) and none have shown any regression using this new version. The re-enablement of build failure on test failure at build time also ensures that we can reliably detect FTBFS issues in the
[Touch-packages] [Bug 1874953] Re: dpkg: conffile difference visualizer subprocess returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: smartmontools (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1874953 Title: dpkg: conffile difference visualizer subprocess returned error exit status 127 Status in dpkg package in Ubuntu: Triaged Status in less package in Ubuntu: Fix Released Status in smartmontools package in Ubuntu: Invalid Status in dpkg source package in Focal: Confirmed Status in less source package in Focal: Triaged Status in smartmontools source package in Focal: Confirmed Status in dpkg source package in Groovy: Triaged Status in less source package in Groovy: Fix Released Status in smartmontools source package in Groovy: Invalid Status in dpkg package in Debian: New Bug description: Issue occurred on upgrade from 19.10 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: smartmontools 7.1-1build1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 21:33:08 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2011-06-18 (3233 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: smartmontools Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) mtime.conffile..etc.default.smartmontools: 2017-12-08T19:12:02.064375 mtime.conffile..etc.smartd.conf: 2017-12-08T20:27:28.727282 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1874953/+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 1874953] Re: dpkg: conffile difference visualizer subprocess returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dpkg (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1874953 Title: dpkg: conffile difference visualizer subprocess returned error exit status 127 Status in dpkg package in Ubuntu: Triaged Status in less package in Ubuntu: Fix Released Status in smartmontools package in Ubuntu: Invalid Status in dpkg source package in Focal: Confirmed Status in less source package in Focal: Triaged Status in smartmontools source package in Focal: Confirmed Status in dpkg source package in Groovy: Triaged Status in less source package in Groovy: Fix Released Status in smartmontools source package in Groovy: Invalid Status in dpkg package in Debian: New Bug description: Issue occurred on upgrade from 19.10 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: smartmontools 7.1-1build1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 21:33:08 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2011-06-18 (3233 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: smartmontools Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) mtime.conffile..etc.default.smartmontools: 2017-12-08T19:12:02.064375 mtime.conffile..etc.smartd.conf: 2017-12-08T20:27:28.727282 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1874953/+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 1882923] [NEW] Ubuntu 20.04, login screen, unable to click with trackpad
Public bug reported: Hi, In login screen, mouse works but clicking is possible only with click button. Click on trackpad does not work. Once entered Ubuntu session, click on trackpad works. But if used i3wm (sudo apt install i3 + choosing i3 in right below button on login ) - problem persists even after login (mouse clicks possible only with mouse buttons) Thank you, Igor ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: i3 Date: Wed Jun 10 12:18:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:229f] InstallationDate: Installed on 2020-04-01 (69 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: LENOVO 20QTCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- 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/1882923 Title: Ubuntu 20.04, login screen, unable to click with trackpad Status in xorg package in Ubuntu: New Bug description: Hi, In login screen, mouse works but clicking is possible only with click button. Click on trackpad does not work. Once entered Ubuntu session, click on trackpad works. But if used i3wm (sudo apt install i3 + choosing i3 in right below button on login ) - problem persists even after login (mouse clicks possible only with mouse buttons) Thank you, Igor ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: i3 Date: Wed Jun 10 12:18:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:229f] InstallationDate: Installed on 2020-04-01 (69 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: LENOVO 20QTCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R
[Touch-packages] [Bug 1882897] Re: Suddent log off/abort in middle of session
** Information type changed from Private Security to Public Security -- 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/1882897 Title: Suddent log off/abort in middle of session Status in xorg package in Ubuntu: New Bug description: This problem starts recently while I was watching some video files on videos. After that whenever I click on any video file it just forces me to log off the system and crash the work environment. Then after uninstalling the Videos software it was working fine. But now recently I installed qgis software. Again this log off problem starts. Whenever I try to add some plugins to qgis my system crashes and forces me to log off from the current session. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 12:53:21 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107GL [Quadro P400] [1028:11be] InstallationDate: Installed on 2019-08-31 (283 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:301a Dell Computer Corp. Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 3630 Tower ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-53-generic root=UUID=46512e15-013e-4c05-8e5a-6b0ccc6f6d7a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.name: 0NNNCT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3630Tower:pvr:rvnDellInc.:rn0NNNCT:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision 3630 Tower dmi.product.sku: 0871 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882897/+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 1877633] Autopkgtest regression report (libseccomp/2.4.3-1ubuntu3.20.04.2)
All autopkgtests for the newly accepted libseccomp (2.4.3-1ubuntu3.20.04.2) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/unknown (armhf) systemd/245.4-4ubuntu3.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#libseccomp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Focal: In Progress Status in libseccomp source package in Groovy: Fix Released Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1877633] Autopkgtest regression report (libseccomp/2.4.3-1ubuntu3.19.10.2)
All autopkgtests for the newly accepted libseccomp (2.4.3-1ubuntu3.19.10.2) for eoan have finished running. The following regressions have been reported in tests triggered by the package: systemd/242-7ubuntu3.9 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#libseccomp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Focal: In Progress Status in libseccomp source package in Groovy: Fix Released Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1876055] Autopkgtest regression report (libseccomp/2.4.3-1ubuntu3.19.10.2)
All autopkgtests for the newly accepted libseccomp (2.4.3-1ubuntu3.19.10.2) for eoan have finished running. The following regressions have been reported in tests triggered by the package: systemd/242-7ubuntu3.9 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#libseccomp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876055 Title: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: Fix Committed Status in libseccomp source package in Bionic: Fix Committed Status in libseccomp source package in Eoan: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: [Impact] The combination of snap-confine and snap-seccomp from snapd uses libseccomp to filter various system calls for confinement. The current version in eoan/bionic/xenial (2.4.1) is missing knowledge of various system calls for various architectures. As such this causes strange issues like python snaps segfaulting (https://github.com/snapcore/core20/issues/48) or the inadvertent denial of system calls which should be permitted by the base policy (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237). libseccomp in groovy is using the latest upstream base release (2.4.3) plus it includes a patch to add some missing aarch64 system calls (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633). SRUing this version back to older stable releases allows libseccomp to operate correctly on all supported architectures. Included as part of this SRU are test-suite reliability improvements - currently the xenial libseccomp package overrides test-suite failures at build time to ignore failures. This masks the fact that on ppc64el and s390x there are currently test suite failures at build time for xenial - these failures occur since libseccomp now includes knowledge of system calls for these architectures but which the linux-libc-dev package for xenial does not actually define (since this is based of the 4.4 kernel in xenial whereas libseccomp 2.4.1 in xenial has knowledge of all system calls up to 5.4). In this SRU I have instead fixed the test suite failures for xenial by including a local (test-suite specific) set of architecture specific kernel headers from the linux-libc-dev in focal for all releases. These are just the headers which define the system call numbers for each architecture *and* these are added to tests/include/$ARCH in the source package (and tests/Makefile.am is then updated to include these new headers only). As such this ensures the actual build of libseccomp or any of the tools does not reference these headers. This allows the test suite in libseccomp to then be aware of theses system calls and so all unit tests for all architectures now pass. In any future updates for libseccomp to add new system calls, we can then similarly update these local headers to ensure the unit tests continue to work as expected. [Test Case] libseccomp includes a significant unit test suite that is run during the build and as part of autopkgtests. To verify the new aarch64 system calls are resolved as expected the scmp_sys_resolver command can be used as well: $ scmp_sys_resolver -a aarch64 getrlimit 163 (whereas in the current version in focal this returns -10180 as libseccomp was not aware of this system-call at compile-time). As part of this SRU, the test suite in libseccomp has been patched to include a local copy of the architecture-specific kernel headers from the 5.4 kernel in focal *for all releases*, so that all system calls which are defined for the 5.4 kernel are known about *for the libseccomp test suite*. This allows all unit tests to pass on older releases as well and defaults the build to fail on unit test failures (whereas currently in xenial this has been overridden to ignore failures). [Regression Potential] This has a low regression potential due to significant testing with many packages that depend on libseccomp (lxc, qemu, snapd, apt, man etc) and none have shown any regression using this new version. The re-enablement of build failure on test failure at build time also ensures that we can reliably detect FTBFS issues in the future. No symbols have been
[Touch-packages] [Bug 1876055] Autopkgtest regression report (libseccomp/2.4.3-1ubuntu3.20.04.2)
All autopkgtests for the newly accepted libseccomp (2.4.3-1ubuntu3.20.04.2) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/unknown (armhf) systemd/245.4-4ubuntu3.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#libseccomp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876055 Title: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: Fix Committed Status in libseccomp source package in Bionic: Fix Committed Status in libseccomp source package in Eoan: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: [Impact] The combination of snap-confine and snap-seccomp from snapd uses libseccomp to filter various system calls for confinement. The current version in eoan/bionic/xenial (2.4.1) is missing knowledge of various system calls for various architectures. As such this causes strange issues like python snaps segfaulting (https://github.com/snapcore/core20/issues/48) or the inadvertent denial of system calls which should be permitted by the base policy (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237). libseccomp in groovy is using the latest upstream base release (2.4.3) plus it includes a patch to add some missing aarch64 system calls (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633). SRUing this version back to older stable releases allows libseccomp to operate correctly on all supported architectures. Included as part of this SRU are test-suite reliability improvements - currently the xenial libseccomp package overrides test-suite failures at build time to ignore failures. This masks the fact that on ppc64el and s390x there are currently test suite failures at build time for xenial - these failures occur since libseccomp now includes knowledge of system calls for these architectures but which the linux-libc-dev package for xenial does not actually define (since this is based of the 4.4 kernel in xenial whereas libseccomp 2.4.1 in xenial has knowledge of all system calls up to 5.4). In this SRU I have instead fixed the test suite failures for xenial by including a local (test-suite specific) set of architecture specific kernel headers from the linux-libc-dev in focal for all releases. These are just the headers which define the system call numbers for each architecture *and* these are added to tests/include/$ARCH in the source package (and tests/Makefile.am is then updated to include these new headers only). As such this ensures the actual build of libseccomp or any of the tools does not reference these headers. This allows the test suite in libseccomp to then be aware of theses system calls and so all unit tests for all architectures now pass. In any future updates for libseccomp to add new system calls, we can then similarly update these local headers to ensure the unit tests continue to work as expected. [Test Case] libseccomp includes a significant unit test suite that is run during the build and as part of autopkgtests. To verify the new aarch64 system calls are resolved as expected the scmp_sys_resolver command can be used as well: $ scmp_sys_resolver -a aarch64 getrlimit 163 (whereas in the current version in focal this returns -10180 as libseccomp was not aware of this system-call at compile-time). As part of this SRU, the test suite in libseccomp has been patched to include a local copy of the architecture-specific kernel headers from the 5.4 kernel in focal *for all releases*, so that all system calls which are defined for the 5.4 kernel are known about *for the libseccomp test suite*. This allows all unit tests to pass on older releases as well and defaults the build to fail on unit test failures (whereas currently in xenial this has been overridden to ignore failures). [Regression Potential] This has a low regression potential due to significant testing with many packages that depend on libseccomp (lxc, qemu, snapd, apt, man etc) and none have shown any regression using this new version. The re-enablement of build failure on test failure at build time also ensures that we can reliably detect FTBFS issues in the fut
[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed
I was dealing with some of these issues after install new kernel version this morning. However I was able to boot with older kernel versions. After a lot of test, now I am able to boot in the new kernel without any problem. Here there are some checks and tasks that I could accomplish: -) Check in /etc/fstab and make sure that there are not duplicated mount points for EFI. -) Try apt install --reinstall linux-image-5.4.0-37-generic -) Try sudo update-grub Also, I removed drivers for nvidia and VirtualBox because some errors that I saw in journalctl. Hope this helps somebody. -- 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/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1882923] Re: Ubuntu 20.04, login screen, unable to click with trackpad
*** This bug is a duplicate of bug 1711538 *** https://bugs.launchpad.net/bugs/1711538 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1711538, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1711538 Tap-to-click does not work on the GDM login screen -- 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/1882923 Title: Ubuntu 20.04, login screen, unable to click with trackpad Status in xorg package in Ubuntu: New Bug description: Hi, In login screen, mouse works but clicking is possible only with click button. Click on trackpad does not work. Once entered Ubuntu session, click on trackpad works. But if used i3wm (sudo apt install i3 + choosing i3 in right below button on login ) - problem persists even after login (mouse clicks possible only with mouse buttons) Thank you, Igor ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: i3 Date: Wed Jun 10 12:18:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:229f] InstallationDate: Installed on 2020-04-01 (69 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: LENOVO 20QTCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882923/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Still having the same problem on my ASUS laptop running 20.04. There's been various updates and things since I last posted but none of them have fixed it! I'm hoping for a fix soon. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1882923] Re: Ubuntu 20.04, login screen, unable to click with trackpad
*** This bug is a duplicate of bug 1711538 *** https://bugs.launchpad.net/bugs/1711538 Hi Daniel, Thank you reply. When login using default login manager, once you are logged in, it works as intended. On the other hand, if you login with i3 window manager, this problem is still there, tap to click does not work. Is it question for i3 team? Thank you, Igor On Wed, Jun 10, 2020, 13:40 Daniel van Vugt <1882...@bugs.launchpad.net> wrote: > *** This bug is a duplicate of bug 1711538 *** > https://bugs.launchpad.net/bugs/1711538 > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. This particular bug has already been reported and is a > duplicate of bug 1711538, so it is being marked as such. Please look at > the other bug report to see if there is any missing information that you > can provide, or to see if there is a workaround for the bug. > Additionally, any further discussion regarding the bug should occur in > the other report. Feel free to continue to report any other bugs you may > find. > > > ** This bug has been marked a duplicate of bug 1711538 >Tap-to-click does not work on the GDM login screen > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1882923 > > Title: > Ubuntu 20.04, login screen, unable to click with trackpad > > Status in xorg package in Ubuntu: > New > > Bug description: > Hi, > > In login screen, mouse works but clicking is possible only with click > button. > Click on trackpad does not work. > Once entered Ubuntu session, click on trackpad works. > But if used i3wm (sudo apt install i3 + choosing i3 in right below > button on login ) - problem persists even after login (mouse clicks > possible only with mouse buttons) > > Thank you, > Igor > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 > Uname: Linux 5.4.0-28-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: i3 > Date: Wed Jun 10 12:18:15 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > GraphicsCard: >Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 > [VGA controller]) > Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] >NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:229f] > InstallationDate: Installed on 2020-04-01 (69 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) > MachineType: LENOVO 20QTCTO1WW > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic > root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/20/2020 > dmi.bios.vendor: LENOVO > dmi.bios.version: N2OET42W (1.29 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 20QTCTO1WW > dmi.board.vendor: LENOVO > dmi.board.version: SDK0R32862 WIN > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: None > dmi.modalias: > dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: > dmi.product.family: ThinkPad P1 Gen 2 > dmi.product.name: 20QTCTO1WW > dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 > dmi.product.version: ThinkPad P1 Gen 2 > dmi.sys.vendor: LENOVO > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882923/+subscriptions > -- 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/1882923 Title: Ubuntu 20.04, login screen, unable to click with trackpad Status in xorg package in Ubuntu: New Bug description: Hi, In login screen, mouse works but clicking is possible only with click button. Click on trackpad does not work. On
[Touch-packages] [Bug 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64
FYI, I copied xenial-focal from the security-proposed ppa to -proposed. Borrowing from the ubuntu-sru team's SRU verification text: Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification- needed- to verification-done-. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libseccomp (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1874953] Re: dpkg: conffile difference visualizer subprocess returned error exit status 127
I filed a less bug in Debian: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=962590 ** Bug watch added: Debian Bug tracker #962590 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962590 ** Also affects: less (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962590 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1874953 Title: dpkg: conffile difference visualizer subprocess returned error exit status 127 Status in dpkg package in Ubuntu: Triaged Status in less package in Ubuntu: Fix Released Status in smartmontools package in Ubuntu: Invalid Status in dpkg source package in Focal: Confirmed Status in less source package in Focal: Triaged Status in smartmontools source package in Focal: Confirmed Status in dpkg source package in Groovy: Triaged Status in less source package in Groovy: Fix Released Status in smartmontools source package in Groovy: Invalid Status in dpkg package in Debian: New Status in less package in Debian: Unknown Bug description: Issue occurred on upgrade from 19.10 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: smartmontools 7.1-1build1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 21:33:08 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2011-06-18 (3233 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: smartmontools Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) mtime.conffile..etc.default.smartmontools: 2017-12-08T19:12:02.064375 mtime.conffile..etc.smartd.conf: 2017-12-08T20:27:28.727282 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1874953/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Hi, Since recent updates : - External mic (in headphones) : Working - Internal mic : Not Working / Not recognized >arecord -l Liste des Périphériques Matériels CAPTURE carte 0: PCH [HDA Intel PCH], périphérique 0: ALC215 Analog [ALC215 Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 >uname -a Linux 5.3.0-53-generic #47~18.04.1-Ubuntu SMP Thu May 7 13:10:50 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Laptop : HP EliteBook 840 G6 -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1879087] Re: dbus errors, frequent roaming and unstable connectivity
** Description changed: * Impact extra roaming events are been generated * Test case - check the output of `journalctl -lu wpa_supplicant`, it should have warnings + check the output of `journalctl -lu wpa_supplicant`, it shouldn't have warnings dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 the roaming events should not be too frequent * Regression potential check that wifi connection keep working correctly -- When using this version of wpa_supplicant with my company WPA2-Enterprise wireless setup, I'm experiencing far too frequent roaming events (even when not moving around) accompanied by hiccups in connectivity. I also see these messages in the wpa_supplicant log: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Having done a little research, at least the dbus errors seem to be fixed by this commit upstream: https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756 So I built a version of wpa_supplicant including this particular patch and installed on my machine. Apart from solving the dbus errors completely, it seems to have had a positive impact on the frequent roaming and unstable connectivity as well (I've run for a day with no burst of roaming events at all, where they used to happen every few minutes most of the time.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 16 16:47:27 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: * Impact extra roaming events are been generated * Test case - check the output of `journalctl -lu wpa_supplicant`, it shouldn't have warnings + check the output of `journalctl -lu wpa_supplicant`, it shouldn't have those warnings dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 the roaming events should not be too frequent * Regression potential check that wifi connection keep working correctly -- When using this version of wpa_supplicant with my company WPA2-Enterprise wireless setup, I'm experiencing far too frequent roaming events (even when not moving around) accompanied by hiccups in connectivity. I also see these messages in the wpa_supplicant log: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Having done a little research, at least the dbus errors seem to be fixed by this commit upstream: https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756 So I built a version of wpa_supplicant including this particular patch and installed on my machine. Apart from solving the dbus errors completely, it seems to have had a positive impact on the frequent roaming and unstable connectivity as well (I've run for a day with no burst of roaming events at all, where they used to happen every few minutes most of the time.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 16 16:47:27 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1879087 Title: dbus errors, frequent roaming and unstable connectivity Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Incomplete Bug description: * Impact extra roaming events are been generated * Test case check the output of `journalc
[Touch-packages] [Bug 1877590] Re: SRU the current 3.24.20 stable update
Looks like there are some theme changes too. Should these be visually checked that there aren't any breakages during SRU verification? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877590 Title: SRU the current 3.24.20 stable update Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that GNOME Desktop and GTK software still work correctly * Regression potential The update has some fixes in the filechooser and the emoji picker, test those To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877590/+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 1877590] Please test proposed package
Hello Sebastien, or anyone else affected, Accepted gtk+3.0 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.20-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877590 Title: SRU the current 3.24.20 stable update Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that GNOME Desktop and GTK software still work correctly * Regression potential The update has some fixes in the filechooser and the emoji picker, test those To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877590/+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 1877590] Re: SRU the current 3.24.20 stable update
The use of the version string 3.24.20-0ubuntu1 for Focal would make a similar bump for Eoan awkward. I assume there are no plans to update Eoan. ** Changed in: gtk+3.0 (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877590 Title: SRU the current 3.24.20 stable update Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that GNOME Desktop and GTK software still work correctly * Regression potential The update has some fixes in the filechooser and the emoji picker, test those To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877590/+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 1874953] Re: dpkg: conffile difference visualizer subprocess returned error exit status 127
** Changed in: less (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1874953 Title: dpkg: conffile difference visualizer subprocess returned error exit status 127 Status in dpkg package in Ubuntu: Triaged Status in less package in Ubuntu: Fix Released Status in smartmontools package in Ubuntu: Invalid Status in dpkg source package in Focal: Confirmed Status in less source package in Focal: Triaged Status in smartmontools source package in Focal: Confirmed Status in dpkg source package in Groovy: Triaged Status in less source package in Groovy: Fix Released Status in smartmontools source package in Groovy: Invalid Status in dpkg package in Debian: New Status in less package in Debian: New Bug description: Issue occurred on upgrade from 19.10 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: smartmontools 7.1-1build1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 21:33:08 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2011-06-18 (3233 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: smartmontools Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) mtime.conffile..etc.default.smartmontools: 2017-12-08T19:12:02.064375 mtime.conffile..etc.smartd.conf: 2017-12-08T20:27:28.727282 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1874953/+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 1877590] Re: SRU the current 3.24.20 stable update
@Robie, thanks, indeed there is no plan to update to eoan. I've updated the testcase to mention to check for the theme changes potential impact ** Description changed: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that GNOME Desktop and GTK software still work correctly * Regression potential The update has some fixes in the filechooser and the emoji picker, test those + + Check also that GUI elements in Adwaita and Yaru still look correct -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877590 Title: SRU the current 3.24.20 stable update Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that GNOME Desktop and GTK software still work correctly * Regression potential The update has some fixes in the filechooser and the emoji picker, test those Check also that GUI elements in Adwaita and Yaru still look correct To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877590/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
I have the same with the headset that was initially reported - the Sennheiser HD 4.50 BTNC. A2DP works perfectly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1882958] [NEW] [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all
Public bug reported: No sound at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinikir2517 F pulseaudio /dev/snd/pcmC0D1p: vinikir2517 F...m pulseaudio /dev/snd/controlC1: vinikir2517 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed Jun 10 11:20:26 2020 InstallationDate: Installed on 2020-02-06 (125 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinikir2517 F pulseaudio /dev/snd/pcmC0D1p: vinikir2517 F...m pulseaudio /dev/snd/controlC1: vinikir2517 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0810 dmi.board.asset.tag: Default string dmi.board.name: PRIME B250M-PLUS/BR 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.:bvr0810:bd07/07/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-PLUS/BR:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882958 Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: No sound at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinikir2517 F pulseaudio /dev/snd/pcmC0D1p: vinikir2517 F...m pulseaudio /dev/snd/controlC1: vinikir2517 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed Jun 10 11:20:26 2020 InstallationDate: Installed on 2020-02-06 (125 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinikir2517 F pulseaudio /dev/snd/pcmC0D1p: vinikir2517 F...m pulseaudio /dev/snd/controlC1: vinikir2517 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0810 dmi.board.asset.tag: Default string dmi.board.name: PRIME B250M-PLUS/BR 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.:bvr0810:bd07/07/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-PLUS/BR:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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 man
[Touch-packages] [Bug 1876055] Re: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness
FYI, I reran the xenial autopkgtests and there are now no regressions. ** Tags removed: verification-done-bionic verification-done-eoan verification-done-focal verification-done-xenial ** Tags added: verification-needed-bionic verification-needed-eoan verification-needed-focal verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876055 Title: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: Fix Committed Status in libseccomp source package in Bionic: Fix Committed Status in libseccomp source package in Eoan: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: [Impact] The combination of snap-confine and snap-seccomp from snapd uses libseccomp to filter various system calls for confinement. The current version in eoan/bionic/xenial (2.4.1) is missing knowledge of various system calls for various architectures. As such this causes strange issues like python snaps segfaulting (https://github.com/snapcore/core20/issues/48) or the inadvertent denial of system calls which should be permitted by the base policy (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237). libseccomp in groovy is using the latest upstream base release (2.4.3) plus it includes a patch to add some missing aarch64 system calls (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633). SRUing this version back to older stable releases allows libseccomp to operate correctly on all supported architectures. Included as part of this SRU are test-suite reliability improvements - currently the xenial libseccomp package overrides test-suite failures at build time to ignore failures. This masks the fact that on ppc64el and s390x there are currently test suite failures at build time for xenial - these failures occur since libseccomp now includes knowledge of system calls for these architectures but which the linux-libc-dev package for xenial does not actually define (since this is based of the 4.4 kernel in xenial whereas libseccomp 2.4.1 in xenial has knowledge of all system calls up to 5.4). In this SRU I have instead fixed the test suite failures for xenial by including a local (test-suite specific) set of architecture specific kernel headers from the linux-libc-dev in focal for all releases. These are just the headers which define the system call numbers for each architecture *and* these are added to tests/include/$ARCH in the source package (and tests/Makefile.am is then updated to include these new headers only). As such this ensures the actual build of libseccomp or any of the tools does not reference these headers. This allows the test suite in libseccomp to then be aware of theses system calls and so all unit tests for all architectures now pass. In any future updates for libseccomp to add new system calls, we can then similarly update these local headers to ensure the unit tests continue to work as expected. [Test Case] libseccomp includes a significant unit test suite that is run during the build and as part of autopkgtests. To verify the new aarch64 system calls are resolved as expected the scmp_sys_resolver command can be used as well: $ scmp_sys_resolver -a aarch64 getrlimit 163 (whereas in the current version in focal this returns -10180 as libseccomp was not aware of this system-call at compile-time). As part of this SRU, the test suite in libseccomp has been patched to include a local copy of the architecture-specific kernel headers from the 5.4 kernel in focal *for all releases*, so that all system calls which are defined for the 5.4 kernel are known about *for the libseccomp test suite*. This allows all unit tests to pass on older releases as well and defaults the build to fail on unit test failures (whereas currently in xenial this has been overridden to ignore failures). [Regression Potential] This has a low regression potential due to significant testing with many packages that depend on libseccomp (lxc, qemu, snapd, apt, man etc) and none have shown any regression using this new version. The re-enablement of build failure on test failure at build time also ensures that we can reliably detect FTBFS issues in the future. No symbols have been removed (or added) with this update in version so there is no chance of regression due to ABI change etc. In the past, the security team has performed more significant version upgrades for libseccomp (2.2, 2.3, 2.4) -> 2.4.1 without major incident. In the case of *this
[Touch-packages] [Bug 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64
FYI, I reran the xenial autopkgtests and they now pass. ** Tags removed: verification-done-focal ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1882849] Re: Doesn't send dhcpv6 request
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882849 Title: Doesn't send dhcpv6 request Status in network-manager package in Ubuntu: Confirmed Bug description: I'm using network-manager 1.22.10-1ubuntu2.1 in Ubuntu Focal 20.04. After a connection the internal dhcp doesn't send request to dhcpv6 server. All options in NM are default. IPv4 is ok. Using tcpdump I can see the packages: 17:47:38.428145 IP6 fe80::426e:5cc5:ab6b:e126.546 > ff02::1:2.547: dhcp6 solicit 17:47:38.428902 IP6 fe80::20e:1eff:fe7a:9ed0.547 > fe80::426e:5cc5:ab6b:e126.546: dhcp6 advertise After dhcp6 advertise the NM doesn't send any request. After some seconds I can see a timeout on logs. NetworkManager[3803]: [1591735670.9313] dhcp6 (eno1): request timed out NetworkManager[3803]: [1591735670.9314] dhcp6 (eno1): state changed unknown -> timeout As man says, we can change the dhcp client. If I change /etc/NetworkManager/NetworkManager.conf adding [main] dhcp=dhclient so everything works nice. I think there is some problem with the internal dhcp client of NetworkManager. Tks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1882849/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
This bug was fixed in the package linux-riscv - 5.4.0-27.31 --- linux-riscv (5.4.0-27.31) focal; urgency=medium * focal/linux-riscv: 5.4.0-27.31 -proposed tracker (LP: #1878798) * Add support for Ambiq micro AM1805 RTC chip (LP: #1876667) - [config] riscv: disable am-1805 RTC driver * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 (LP: #1875665) - [Config][focal/linux-riscv] Turn off CONFIG_RT_GROUP_SCHED [ Ubuntu: 5.4.0-34.38 ] * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118) * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Focal update: v5.4.41 upstream stable release (LP: #1878649) - USB: serial: qcserial: Add DW5816e support - nvme: refactor nvme_identify_ns_descs error handling - nvme: fix possible hang when ns scanning fails during error recovery - tracing/kprobes: Fix a double initialization typo - net: macb: Fix runtime PM refcounting - drm/amdgpu: move kfd suspend after ip_suspend_phase1 - drm/amdgpu: drop redundant cg/pg ungate on runpm enter - vt: fix unicode console freeing with a common interface - tty: xilinx_uartps: Fix missing id assignment to the console - devlink: fix return value after hitting end in region read - dp83640: reverse arguments to list_add_tail - fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks - ipv6: Use global sernum for dst validation with nexthop objects - mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly - neigh: send protocol value in neighbor create notification - net: dsa: Do not leave DSA master with NULL netdev_ops - net: macb: fix an issue about leak related system resources - net: macsec: preserve ingress frame ordering - net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() - net_sched: sch_skbprio: add message validation to skbprio_change() - net: stricter validation of untrusted gso packets - net: tc35815: Fix phydev supported/advertising mask - net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() - net/tls: Fix sk_psock refcnt leak when in tls_data_ready() - net: usb: qmi_wwan: add support for DW5816e - nfp: abm: fix a memory leak bug - sch_choke: avoid potential panic in choke_reset() - sch_sfq: validate silly quantum values - tipc: fix partial topology connection closure - tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 - bnxt_en: Fix VF anti-spoof filter setup. - bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. - bnxt_en: Improve AER slot reset. - bnxt_en: Return error when allocating zero size context memory. - bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). - net/mlx5: DR, On creation set CQ's arm_db member to right value - net/mlx5: Fix forced completion access non initialized command entry - net/mlx5: Fix command entry leak in Internal Error State - net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx() - net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del() - HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices - sctp: Fix bundling of SHUTDOWN with COOKIE-ACK - Revert "HID: wacom: generic: read the number of expected touches on a per collection basis" - HID: usbhid: Fix race between usbhid_close() and usbhid_stop() - HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT - USB: uas: add quirk for LaCie 2Big Quadra - usb: chipidea: msm: Ensure proper controller reset using role switch API - USB: serial: garmin_gps: add sanity checking for data length - tracing: Add a vmalloc_sync_mappings() for safe measure - crypto: arch/nhpoly1305 - process in explicit 4k chunks - KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction - KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path - KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER - KVM: arm64: Fix 32bit PC wrap-around - arm64: hugetlb: avoid potential NULL dereference - drm: ingenic-drm: add MODULE_DEVICE_TABLE - ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() - epoll: atomically remove wait entry on wake up - eventpoll: fix missing wakeup for ovflist in ep_poll_callback - mm/page_alloc: fix watchdog soft lockups during set_zone_contiguous() - mm: limit boost_watermark on small zones - ceph: demote quotarealm lookup warning to a debug message - staging: gasket: Check the return value of gasket_get_bar_index() - coredump: fix crash when umh is disabled - iocost: protect iocg->abs_vdebt with iocg->waitq.lock - batman-adv: fix batadv_nc_random_weight_tq - batman-adv: Fix refcnt leak in batadv_show_throughput_overri
[Touch-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages
I've tested on xubuntu now - start a new focal xubuntu image - download the eog focal deb from focal - clicked on it from the file manager -> gnome-software is opened then after installing desktop-file-utils 0.24-1ubuntu3 trying the same steps gave the same result after restarting the session is was still working as expected the gio mime command also showed the default was still correct and gnome-software there setting back to verification-done now ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Fix Released Status in gdebi package in Ubuntu: Invalid Status in desktop-file-utils source package in Focal: Fix Committed Status in gdebi source package in Focal: Invalid Bug description: [Impact] * When a deb is downloaded the default handler is not capable of installing on 20.04. [Test Case] We should perform this test on Ubuntu 20.04 as well as some flavors to ensure we do not regress. * Download any deb in firefox, double click on the downloaded file - On Ubuntu this should open "Ubuntu Software" - On flavors it should open whatever their default app for handling debs is [Regression Potential] * For Ubuntu, very low, rarely would a user expect to open a deb with file-roller * Other flavors of ubuntu are overriding this default and should not be affected. We do need to test this on other flavors to ensure their defaults are still honored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1882966] [NEW] Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04
Public bug reported: The recent update of the libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter packages makes it impossible to build Orca Master in Ubuntu-MATE 20.04. Reproduction steps: 1. You need to have Ubuntu-MATE 20.04 with the latest updates; 2. Install the following packages: git autoconf autopoint yelp-tools libgstreamer1.0-dev python-gi-dev libatspi2.0-dev libatk-bridge2.0-dev 3. Clone the Orca repository: git clone https://gitlab.gnome.org/GNOME/orca.git 4. Navigate to the cloned repository: cd orca 5. Run the command: ./autogen.sh The command output ends with the following lines: checking for ATKBRIDGE... no configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met: Package 'atk', required by 'atk-bridge-2.0', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS and ATKBRIDGE_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. If libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter are forcibly downgraded to version 2.34.1-3, this error disappears. Many thanks for fixing this issues. ** Affects: at-spi2-atk (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Description changed: The recent update of the libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter packages makes it impossible to build Orca Master in - Ubuntu 20.04. Reproduction steps: + Ubuntu-MATE 20.04. Reproduction steps: 1. You need to have Ubuntu-MATE 20.04 with the latest updates; 2. Install the following packages: git autoconf autopoint yelp-tools libgstreamer1.0-dev python-gi-dev libatspi2.0-dev libatk-bridge2.0-dev 3. Clone the Orca repository: git clone https://gitlab.gnome.org/GNOME/orca.git 4. Navigate to the cloned repository: cd orca 5. Run the command: ./autogen.sh The command output ends with the following lines: checking for ATKBRIDGE... no configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met: Package 'atk', required by 'atk-bridge-2.0', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS and ATKBRIDGE_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. If libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter are forcibly downgraded to version 2.34.1-3, this error disappears. Many thanks for fixing this issues. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1882966 Title: Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04 Status in at-spi2-atk package in Ubuntu: New Bug description: The recent update of the libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter packages makes it impossible to build Orca Master in Ubuntu-MATE 20.04. Reproduction steps: 1. You need to have Ubuntu-MATE 20.04 with the latest updates; 2. Install the following packages: git autoconf autopoint yelp-tools libgstreamer1.0-dev python-gi-dev libatspi2.0-dev libatk-bridge2.0-dev 3. Clone the Orca repository: git clone https://gitlab.gnome.org/GNOME/orca.git 4. Navigate to the cloned repository: cd orca 5. Run the command: ./autogen.sh The command output ends with the following lines: checking for ATKBRIDGE... no configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met: Package 'atk', required by 'atk-bridge-2.0', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS and ATKBRIDGE_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. If libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter are forcibly downgraded to version 2.34.1-3, this error disappears. Many thanks for fixing this issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1882966/+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 1861177] Re: seccomp_rule_add is very slow
There isn't a snapd task (snap-seccomp is compiled against libseccomp but it can't influence this behavior), so unassigning Ian and marking that task as Invalid. ** Changed in: snapd Status: Triaged => Invalid ** Changed in: snapd Assignee: Ian Johnson (anonymouse67) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1861177 Title: seccomp_rule_add is very slow Status in snapd: Invalid Status in libseccomp package in Ubuntu: In Progress Bug description: There is a known and patched issue with version 2.4 of libseccomp where certain operations have a large performance regression. This is causing some packages that use libseccomp such as container orchestration systems to occasionally time out or otherwise fail under certain workloads. Please consider porting the patch into the various Ubuntu versions that have version 2.4 of libseccomp and into the backports. The performance patch from version 2.5 (yet to be released) applies cleanly on top of the 2.4 branch of libseccomp. For more information, and for a copy of the patch (which can also be cherry picked from the upstream libseccomp repos) see the similar Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1861177/+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 1864207] Re: Update request: 0.8.0 released
https://launchpad.net/ubuntu/+source/avahi/0.8-3ubuntu1 ** Changed in: avahi (Ubuntu) Status: Triaged => Fix Released -- 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/1864207 Title: Update request: 0.8.0 released Status in avahi package in Ubuntu: Fix Released Bug description: Version 0.8.0 of Avahi got released: https://github.com/lathiat/avahi/releases/tag/v0.8 Would be great to have this in Ubuntu 20.04 LTS (Focal) -- The Avahi 0.8 release brings a number of new features and bug fix changes including a backward-compatible addition to the D-Bus API and the avahi-core API. The existing API is still fully supported however clients using the new API will not work with older Avahi releases. The avahi-client library is not affected. See the "API Changes" section for further details. New Features: New options for filtering reflected queries between networks (reflect-filter) New mainloop integration for Qt5 and libevent docs/THREADS: Information for multi-threaded avahi-client apps Listen on loopback interfaces by default, allowing local-only services to be consumed by the local machine New D-Bus V2 API and additions to the avahi-core API for splitting "New" calls into "Prepare" and "Start". See "API Changes" for more details. Notable Changes: avahi-autoipd: Initial IP selection based on MAC previously ignored first octet - this will cause all hosts to select a different link-local IP than previous versions based on the same MAC address avahi-daemon: Delay sending results on an object for 10ms in an attempt to give clients enough time to subscribe to signals from the new object after receiving it's path in response so the New call. See "API Changes" for more info Bug Fixes: avahi-python: Various Python 3 enhancements including encoding unicode strings as UTF-8 avahi-common: avahi_string_list_to_string will now escape embedded quotes, backslashes and control characters. avahi-daemon: Fix a crash when txt records have an empty value in .xml service files avahi-daemon: reflector: do not incorrectly cache responses on outgoing interfaces. Previously we would incorrectly cache responses reflected from one interface on the outgoing interface. These responses were later sent to clients on that network even if the original client had disappeared and could cause those clients to have a hostname conflict with themselves on restart. We no longer incorrectly cache such traffic. Security Fixes: Drop legacy unicast queries from address not on local link which can lead to UDP traffic amplification attacks (CVE-2017-6519) API Changes: The avahi-core API and D-Bus API have implemented a new API where a call to the "New" method can now be split into a "Prepare" and then "Start" method for some objects. The previous "New" API is still fully supported and there is no intention to deprecate it. This change affects the the following objects: AsyncAddressResolver, AsyncHostNameResolver, AsyncServiceResolver, DomainBrowser, RecordBrowser, ServiceBrowser, ServiceTypeBrowser This is because the D-Bus implementation in some languages would only bind to signals of an object after it was created and had received the new object's path. This led to such languages missing the initial results sent between the time the object was created and it had setup a filter to receive it's signals. This primarily occured in languages that create dynamic bindings for D-Bus objects using introspection such as Python. The avahi-client C api was not affected as it globally binds to all avahi signals without specifying individual object paths and still makes use of the V1 API. The v2 Prepare/Start API is available under the new org.freedesktop.Avahi.Server2 D-Bus interface and also has corresponding avahi_s_* calls for users of the embedded avahi-core library. The old org.freedesktop.Avahi.Server interface is still supported and there is no intention to remove this API. Additionally this problem has also been solved for old clients by adding a very small 10ms delay before we start sending results to give the client time to bind to the signals which should silently fix the issue in most cases without introducing a noticable or impactful delay. Clients implementing the new org.freedesktop.Avahi.Server2 D-Bus interface will not work with older Avahi daemons. It is suggested that clients may wish to either check for and fallback to the older API version, or continue to use the OLD API and rely on the 10ms timer to resolve the issue. Big thank-you to everyone contributing to the project through issues & pull requests, including the the following people who contributed changes to this release: Daniel S, David Kerr, Eric Bischoff, James Rudd, Jan Alexander Steffen
[Touch-packages] [Bug 1771033] Re: [needs-packaging] python3-avahi is not available in Ubuntu/debian
The switch to pyhon3 has been done now in this upload https://launchpad.net/ubuntu/+source/avahi/0.8-3ubuntu1 ** Changed in: avahi (Ubuntu) Status: Fix Committed => Fix Released -- 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/1771033 Title: [needs-packaging] python3-avahi is not available in Ubuntu/debian Status in avahi package in Ubuntu: Fix Released Status in avahi package in Debian: Fix Released Bug description: Under Ubuntu 18.04 if you install the package Gajim the local account is permanently disabled because of missing dependencies. https://dev.gajim.org/gajim/gajim/issues/9125 The required package is python3-avahi The python3-avahi package is missing, apt-get is unable to find it. This is a vital feature for us, we use Gajim internally without internet, and this simply works, no adding accounts, no information or messages sent over the internet, it all works locally. I hope this package can be added, if this is the wrong place to file this bug I applologize. I don't have a lot of experience reporting bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1771033/+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 1873658] Re: Deb Files are not associated with an application that manages packages
This bug was fixed in the package desktop-file-utils - 0.24-1ubuntu3 --- desktop-file-utils (0.24-1ubuntu3) focal; urgency=medium * debian/defaults.list - Updated for the transition to snap-store (LP: #1873658) -- Ken VanDine Tue, 21 Apr 2020 09:38:59 -0400 ** Changed in: desktop-file-utils (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Fix Released Status in gdebi package in Ubuntu: Invalid Status in desktop-file-utils source package in Focal: Fix Released Status in gdebi source package in Focal: Invalid Bug description: [Impact] * When a deb is downloaded the default handler is not capable of installing on 20.04. [Test Case] We should perform this test on Ubuntu 20.04 as well as some flavors to ensure we do not regress. * Download any deb in firefox, double click on the downloaded file - On Ubuntu this should open "Ubuntu Software" - On flavors it should open whatever their default app for handling debs is [Regression Potential] * For Ubuntu, very low, rarely would a user expect to open a deb with file-roller * Other flavors of ubuntu are overriding this default and should not be affected. We do need to test this on other flavors to ensure their defaults are still honored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1873658] Update Released
The verification of the Stable Release Update for desktop-file-utils has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Fix Released Status in gdebi package in Ubuntu: Invalid Status in desktop-file-utils source package in Focal: Fix Released Status in gdebi source package in Focal: Invalid Bug description: [Impact] * When a deb is downloaded the default handler is not capable of installing on 20.04. [Test Case] We should perform this test on Ubuntu 20.04 as well as some flavors to ensure we do not regress. * Download any deb in firefox, double click on the downloaded file - On Ubuntu this should open "Ubuntu Software" - On flavors it should open whatever their default app for handling debs is [Regression Potential] * For Ubuntu, very low, rarely would a user expect to open a deb with file-roller * Other flavors of ubuntu are overriding this default and should not be affected. We do need to test this on other flavors to ensure their defaults are still honored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1861177] Re: seccomp_rule_add is very slow
Thanks for the follow ups. If the server team doesn't want to take this on, could someone provide me with a team or person I could contact to try and gently prod this forward (maybe someone on the security team)? I've got some customers that are running into this and telling them to rebuild this library themselves doesn't seem to have made them happy :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1861177 Title: seccomp_rule_add is very slow Status in snapd: Invalid Status in libseccomp package in Ubuntu: In Progress Bug description: There is a known and patched issue with version 2.4 of libseccomp where certain operations have a large performance regression. This is causing some packages that use libseccomp such as container orchestration systems to occasionally time out or otherwise fail under certain workloads. Please consider porting the patch into the various Ubuntu versions that have version 2.4 of libseccomp and into the backports. The performance patch from version 2.5 (yet to be released) applies cleanly on top of the 2.4 branch of libseccomp. For more information, and for a copy of the patch (which can also be cherry picked from the upstream libseccomp repos) see the similar Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1861177/+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 1882897] Re: Suddent log off/abort in middle of session
Solved already. Problem was related to Nvidia driver Similar bug Solution at the link https://askubuntu.com/questions/1128350/ubuntu-18-10-settings-bug ** Description changed: This problem starts recently while I was watching some video files on videos. After that whenever I click on any video file it just forces me to log off the system and crash the work environment. Then after uninstalling the Videos software it was working fine. But now recently I installed qgis software. Again this log off problem starts. Whenever I try to add some plugins to qgis my system crashes and forces me to log off from the current session. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 12:53:21 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Dell GP107GL [Quadro P400] [1028:11be] + NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Dell GP107GL [Quadro P400] [1028:11be] InstallationDate: Installed on 2019-08-31 (283 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 413c:301a Dell Computer Corp. - Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. - Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 413c:301a Dell Computer Corp. + Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. + Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 3630 Tower ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-53-generic root=UUID=46512e15-013e-4c05-8e5a-6b0ccc6f6d7a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.name: 0NNNCT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3630Tower:pvr:rvnDellInc.:rn0NNNCT:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision 3630 Tower dmi.product.sku: 0871 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A -- 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/1882897 Title: Suddent log off/abort in middle of session Status in xorg package in Ubuntu: New Bug description: This problem starts recently while I was watching some video files on videos. After that whenever I click on any video file it just forces me to log off the system and crash the work environment. Then after uninstalling the Videos software it was working fine. But now recently I installed qgis software. Again this log off problem starts. Whenever I try to add some plugins to qgis my system crashes and forces me to log off from the current session. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 12:53:21 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107GL [Quadr
[Touch-packages] [Bug 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu -- 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/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store: New Status in apport package in Ubuntu: Triaged Status in apport source package in Focal: Triaged Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+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 1883005] [NEW] Xorg freeze
Public bug reported: This bug have been happing on my PC, in the applications when i open some application folder and after click out of it, to close it. The screen just freeze and i have to reboot my notebook (Lenovo- ideapad-310). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 15:08:37 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: I don't know GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822] InstallationDate: Installed on 2020-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 80UH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=31e5e6b9-3228-4c0a-b10a-d78f6218b8db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 5A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UH:pvrLenovoideapad310-15ISK:rvnLENOVO:rnToronto5A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UH dmi.product.sku: LENOVO_MT_80UH_BU_idea_FM_Lenovo ideapad 310-15ISK dmi.product.version: Lenovo ideapad 310-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Assignee: adsson andre da silva gomes (adsson) Status: New ** Tags: amd64 apport-bug focal freeze ubuntu ** Attachment added: "Screenshot from 2020-06-10 15-29-03.png" https://bugs.launchpad.net/bugs/1883005/+attachment/5382591/+files/Screenshot%20from%202020-06-10%2015-29-03.png ** Changed in: xorg (Ubuntu) Assignee: (unassigned) => adsson andre da silva gomes (adsson) -- 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/1883005 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: This bug have been happing on my PC, in the applications when i open some application folder and after click out of it, to close it. The screen just freeze and i have to reboot my notebook (Lenovo- ideapad-310). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 15:08:37 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: I don't know GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822] InstallationDate: Installed on 2020-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 80UH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=31e5e6b9-3228-4c0a-b10a-d78f6218b8db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW
[Touch-packages] [Bug 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64
Sorry, I reran bionic and *focal* autopkgtests and there are now no regressions. Running eoan again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64
FYI, I reran the bionic and eoan autopkgtests and there are now no regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1877633 Title: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64 Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: This was reported via the snapcraft forum[1]: On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2 $ lsb_release -d Description: Ubuntu 18.04.4 LTS $ scmp_sys_resolver -a aarch64 163 getrlimit $ scmp_sys_resolver -a aarch64 getrlimit 163 focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__* $ lsb_release -d Description: Ubuntu 20.04 LTS $ scmp_sys_resolver -a aarch64 163 UNKNOWN $ scmp_sys_resolver -a aarch64 getrlimit -10180 [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1876055] Re: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness
Sorry, I reran bionic and *focal* autopkgtests and there are now no regressions. Running eoan again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876055 Title: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: Fix Committed Status in libseccomp source package in Bionic: Fix Committed Status in libseccomp source package in Eoan: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: [Impact] The combination of snap-confine and snap-seccomp from snapd uses libseccomp to filter various system calls for confinement. The current version in eoan/bionic/xenial (2.4.1) is missing knowledge of various system calls for various architectures. As such this causes strange issues like python snaps segfaulting (https://github.com/snapcore/core20/issues/48) or the inadvertent denial of system calls which should be permitted by the base policy (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237). libseccomp in groovy is using the latest upstream base release (2.4.3) plus it includes a patch to add some missing aarch64 system calls (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633). SRUing this version back to older stable releases allows libseccomp to operate correctly on all supported architectures. Included as part of this SRU are test-suite reliability improvements - currently the xenial libseccomp package overrides test-suite failures at build time to ignore failures. This masks the fact that on ppc64el and s390x there are currently test suite failures at build time for xenial - these failures occur since libseccomp now includes knowledge of system calls for these architectures but which the linux-libc-dev package for xenial does not actually define (since this is based of the 4.4 kernel in xenial whereas libseccomp 2.4.1 in xenial has knowledge of all system calls up to 5.4). In this SRU I have instead fixed the test suite failures for xenial by including a local (test-suite specific) set of architecture specific kernel headers from the linux-libc-dev in focal for all releases. These are just the headers which define the system call numbers for each architecture *and* these are added to tests/include/$ARCH in the source package (and tests/Makefile.am is then updated to include these new headers only). As such this ensures the actual build of libseccomp or any of the tools does not reference these headers. This allows the test suite in libseccomp to then be aware of theses system calls and so all unit tests for all architectures now pass. In any future updates for libseccomp to add new system calls, we can then similarly update these local headers to ensure the unit tests continue to work as expected. [Test Case] libseccomp includes a significant unit test suite that is run during the build and as part of autopkgtests. To verify the new aarch64 system calls are resolved as expected the scmp_sys_resolver command can be used as well: $ scmp_sys_resolver -a aarch64 getrlimit 163 (whereas in the current version in focal this returns -10180 as libseccomp was not aware of this system-call at compile-time). As part of this SRU, the test suite in libseccomp has been patched to include a local copy of the architecture-specific kernel headers from the 5.4 kernel in focal *for all releases*, so that all system calls which are defined for the 5.4 kernel are known about *for the libseccomp test suite*. This allows all unit tests to pass on older releases as well and defaults the build to fail on unit test failures (whereas currently in xenial this has been overridden to ignore failures). [Regression Potential] This has a low regression potential due to significant testing with many packages that depend on libseccomp (lxc, qemu, snapd, apt, man etc) and none have shown any regression using this new version. The re-enablement of build failure on test failure at build time also ensures that we can reliably detect FTBFS issues in the future. No symbols have been removed (or added) with this update in version so there is no chance of regression due to ABI change etc. In the past, the security team has performed more significant version upgrades for libseccomp (2.2, 2.3, 2.4) -> 2.4.1 without major incident. In the case of *this* SRU, we are only doing a micro-version upgrade from 2.4.1 to 2.4.3 so this carries even less change of regressions. Any possible regressions may include applications now seeing correct system call r
[Touch-packages] [Bug 1876055] Re: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness
FYI, I reran the bionic and eoan autopkgtests and there are now no regressions. ** Tags removed: verification-needed-bionic verification-needed-eoan verification-needed-focal verification-needed-xenial ** Tags added: verification-done-bionic verification-done-eoan verification-done-focal verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876055 Title: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: Fix Committed Status in libseccomp source package in Bionic: Fix Committed Status in libseccomp source package in Eoan: Fix Committed Status in libseccomp source package in Focal: Fix Committed Status in libseccomp source package in Groovy: Fix Released Bug description: [Impact] The combination of snap-confine and snap-seccomp from snapd uses libseccomp to filter various system calls for confinement. The current version in eoan/bionic/xenial (2.4.1) is missing knowledge of various system calls for various architectures. As such this causes strange issues like python snaps segfaulting (https://github.com/snapcore/core20/issues/48) or the inadvertent denial of system calls which should be permitted by the base policy (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237). libseccomp in groovy is using the latest upstream base release (2.4.3) plus it includes a patch to add some missing aarch64 system calls (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633). SRUing this version back to older stable releases allows libseccomp to operate correctly on all supported architectures. Included as part of this SRU are test-suite reliability improvements - currently the xenial libseccomp package overrides test-suite failures at build time to ignore failures. This masks the fact that on ppc64el and s390x there are currently test suite failures at build time for xenial - these failures occur since libseccomp now includes knowledge of system calls for these architectures but which the linux-libc-dev package for xenial does not actually define (since this is based of the 4.4 kernel in xenial whereas libseccomp 2.4.1 in xenial has knowledge of all system calls up to 5.4). In this SRU I have instead fixed the test suite failures for xenial by including a local (test-suite specific) set of architecture specific kernel headers from the linux-libc-dev in focal for all releases. These are just the headers which define the system call numbers for each architecture *and* these are added to tests/include/$ARCH in the source package (and tests/Makefile.am is then updated to include these new headers only). As such this ensures the actual build of libseccomp or any of the tools does not reference these headers. This allows the test suite in libseccomp to then be aware of theses system calls and so all unit tests for all architectures now pass. In any future updates for libseccomp to add new system calls, we can then similarly update these local headers to ensure the unit tests continue to work as expected. [Test Case] libseccomp includes a significant unit test suite that is run during the build and as part of autopkgtests. To verify the new aarch64 system calls are resolved as expected the scmp_sys_resolver command can be used as well: $ scmp_sys_resolver -a aarch64 getrlimit 163 (whereas in the current version in focal this returns -10180 as libseccomp was not aware of this system-call at compile-time). As part of this SRU, the test suite in libseccomp has been patched to include a local copy of the architecture-specific kernel headers from the 5.4 kernel in focal *for all releases*, so that all system calls which are defined for the 5.4 kernel are known about *for the libseccomp test suite*. This allows all unit tests to pass on older releases as well and defaults the build to fail on unit test failures (whereas currently in xenial this has been overridden to ignore failures). [Regression Potential] This has a low regression potential due to significant testing with many packages that depend on libseccomp (lxc, qemu, snapd, apt, man etc) and none have shown any regression using this new version. The re-enablement of build failure on test failure at build time also ensures that we can reliably detect FTBFS issues in the future. No symbols have been removed (or added) with this update in version so there is no chance of regression due to ABI change etc. In the past, the security team has performed more significant version upgrades for libseccomp (2.2, 2.3, 2.4) -> 2.4.1 without major incident. In the case
[Touch-packages] [Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
Privacy: Ubuntu users don't have the opportunity to opt-out from motd-news before all the private infos and telemetry are sent via User-Agent. So even if people change ENABLED=1 to ENABLED=0 in /etc/default/motd-news they only stop future leaks but the initial leak has already been done in background after the boot via systemd/motd-news service. I repeat, this doesn't look GRPD-compliant at all. There is no prior consent ever asked for. The GDPR was adopted on 14 April 2016, and became enforceable beginning 25 May 2018. motd-news has been designed in 2017 and is enabled by default on all Ubuntu Server, Ubuntu Desktop, Ubuntu Flavors (such as Mate, Raspberry), Ubuntu derived such as Nvidia Jetson Nano without prior consent. Security: Run curl as root every 12h are you serious? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Confirmed Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1881966] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382631/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] NetDevice.enp3s0.txt
apport information ** Attachment added: "NetDevice.enp3s0.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382632/+files/NetDevice.enp3s0.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] NetDevice.wlx74ee2af4348b.txt
apport information ** Attachment added: "NetDevice.wlx74ee2af4348b.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382636/+files/NetDevice.wlx74ee2af4348b.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382637/+files/NetworkManager.conf.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382629/+files/IpAddr.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382638/+files/PciNetwork.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382639/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382633/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] IpRoute.txt
apport information ** Attachment added: "IpRoute.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382630/+files/IpRoute.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] NetDevice.virbr0-nic.txt
apport information ** Attachment added: "NetDevice.virbr0-nic.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382635/+files/NetDevice.virbr0-nic.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] NetDevice.virbr0.txt
apport information ** Attachment added: "NetDevice.virbr0.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382634/+files/NetDevice.virbr0.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382640/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382642/+files/nmcli-con.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382641/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] Re: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04
apport information ** Tags added: apport-collected focal ** Description changed: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. - I am happy to provide any information necessary to resolve this issue. - Thanks + I am happy to provide any information necessary to resolve this issue. Thanks + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.04 + IfupdownConfig: + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback + InstallationDate: Installed on 2020-02-01 (130 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + NonfreeKernelModules: nvidia_modeset nvidia + Package: network-manager 1.22.10-1ubuntu2.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: focal + Uname: Linux 5.4.0-33-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) + UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True + modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: + [connection] + wifi.powersave = 2 + mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382627/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu
[Touch-packages] [Bug 1881966] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382628/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1881966/+attachment/5382643/+files/nmcli-dev.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-01 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2020-05-28T00:00:40.294938 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1586528] Re: Avahi-daemon withdraws address record
Are you guys sure it isn't Avahi? It was still happening to me after stopping the network manager service. Is it not the incompatibility mentioned in the Arch docs? https://wiki.archlinux.org/index.php/Avahi My ip and dns finally stopped changing when I disabled Avahi. Also happened to this guy: https://jrs-s.net/2015/01/09/avahi-killed-my- server/ I have a similar bridge setup to his. Maybe my case (and that guy's) is a different bug/issue though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1870058] Re: Collect deleted users
Thanks Didier, that's perfect. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1870058 Title: Collect deleted users Status in shadow package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Fix Released Status in shadow source package in Focal: New Status in zsys source package in Focal: New Bug description: [Impact] * Deleting users were preserving corresponding ZFS user datasets, without marking them for cleanup. * This is covered by dedicated use cases. [Test Case] 1. Ensure you have a foo user: 2. Run userdel --remove foo 3. Check that rpool/USERDATA/foo_ has its content removed and is not mounted 4. zfs get com.ubuntu.zsys:bootfs-dataset rpool/USERDATA/foo_ is not associated with current system dataset --- Other use case: 1.Ensure you have a foo user: 2. Run userdel foo 3. Check that rpool/USERDATA/foo_ still has its content, but is not mounted. 4. zfs get com.ubuntu.zsys:bootfs-dataset rpool/USERDATA/foo_ is not associated with current system dataset --- On a non ZFS installation : 1. Ensure you have a foo user: 2. Run userdel --remove foo 3. The user is deleted, no error occured. --- On a non ZFS installation with ZSys installed : 1. Ensure you have a foo user: 2. Run userdel --remove foo 3. The user is deleted, no error occured. [Regression Potential] * A new hidden command is added, triggered by userdel. * Tests are covering this new command and GRPC request. * The methodology is similar to useradd and usermod. The dependency between shadow and zsys is weak on purpose: - the ZSys hidden command is available and is a no-op if not called - if calling the command failed on userdel, nothing is done on ZSys side, but the code path is similar to ZSys not being installed or running on a non ZFS system. Ideally, we would untag them as part of GC so that we can clean them up later. However, those can be linked to states on other pools with same pool name than targetted one, and it will be hard to match them. Give a command for users to see them in status and then manually remove suspicious datasets ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1870058/+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 1882897] Re: Suddent log off/abort in middle of session
** Information type changed from Public Security to Public -- 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/1882897 Title: Suddent log off/abort in middle of session Status in xorg package in Ubuntu: New Bug description: This problem starts recently while I was watching some video files on videos. After that whenever I click on any video file it just forces me to log off the system and crash the work environment. Then after uninstalling the Videos software it was working fine. But now recently I installed qgis software. Again this log off problem starts. Whenever I try to add some plugins to qgis my system crashes and forces me to log off from the current session. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 12:53:21 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107GL [Quadro P400] [1028:11be] InstallationDate: Installed on 2019-08-31 (283 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:301a Dell Computer Corp. Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 3630 Tower ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-53-generic root=UUID=46512e15-013e-4c05-8e5a-6b0ccc6f6d7a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.name: 0NNNCT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3630Tower:pvr:rvnDellInc.:rn0NNNCT:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision 3630 Tower dmi.product.sku: 0871 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882897/+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 1857769] Re: program linked to protobuf crashes before main
I downloaded the latest protocol buffer release (protobuf-
cpp-3.12.3.tar.gz) and the simple test app does not crash with that. So
this problem seems to be unique to 20.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1857769
Title:
program linked to protobuf crashes before main
Status in protobuf package in Ubuntu:
New
Bug description:
This simple test crashes on a system that I installed Ubuntu Server 20.04
daily build on yesterday:
echo "syntax = \"proto2\";" >| test.pbc
echo "message TestMsg" >> test.pbc
echo "{" >> test.pbc
echo " required double f1 = 1;" >> test.pbc
echo "}" >> test.pbc
echo "int main() {return 0;}" >| test.cc
protoc --cpp_out=. ./test.pbc
g++ -c -o test.pbc.pb.o test.pbc.pb.cc
g++ -c -o test.o test.cc
g++ -o test test.o test.pbc.pb.o -lprotobuf
./test
terminate called after throwing an instance of 'std::system_error'
what(): Unknown error -1
Aborted (core dumped)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: protobuf-compiler 3.6.1.3-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
Date: Sat Dec 28 19:10:20 2019
InstallationDate: Installed on 2019-12-27 (1 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64
(20191227)
SourcePackage: protobuf
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1857769/+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 1883028] [NEW] Bluetooth devices don't reconnect after sleep.
Public bug reported: Bluetooth devices don't reconnect after sleep. Includes BT audio receiver and BT Keyboard. One way to repro is to switch BT pairing on multi-pairing keyboard, then switch back to Ubuntu. The BT connection state will be very confused, keyboard will not work. Another way to repro is to get a bluetooth receiver, pair it. Let the BT device (or PC?) sleep... now wake up the system. The audio will not play. BT UI slider says disconnected. If you click the slider it will go back to off. If you click it quickly >25 times, no joke, it will reconnect and work. FYI: Raspbian handles the keyboard fine, have not tested the audio. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 17:09:06 2020 InstallationDate: Installed on 2019-06-10 (366 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20HRCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=df7df2a3-26f4-4fe6-8621-51673ae55b6f ro intel_pstate=disable SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET61W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET61W(1.46):bd04/08/2020:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 88:B1:11:77:AE:CE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:6243797 acl:69580 sco:0 events:629809 errors:0 TX bytes:488355907 acl:570780 sco:0 commands:32574 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1883028 Title: Bluetooth devices don't reconnect after sleep. Status in bluez package in Ubuntu: New Bug description: Bluetooth devices don't reconnect after sleep. Includes BT audio receiver and BT Keyboard. One way to repro is to switch BT pairing on multi-pairing keyboard, then switch back to Ubuntu. The BT connection state will be very confused, keyboard will not work. Another way to repro is to get a bluetooth receiver, pair it. Let the BT device (or PC?) sleep... now wake up the system. The audio will not play. BT UI slider says disconnected. If you click the slider it will go back to off. If you click it quickly >25 times, no joke, it will reconnect and work. FYI: Raspbian handles the keyboard fine, have not tested the audio. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 17:09:06 2020 InstallationDate: Installed on 2019-06-10 (366 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20HRCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=df7df2a3-26f4-4fe6-8621-51673ae55b6f ro intel_pstate=disable SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET61W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET61W(1.46):bd04/08/2020:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Add
[Touch-packages] [Bug 1883028] Re: Bluetooth devices don't reconnect after sleep.
** Description changed: - Bluetooth devices don't reconnect after sleep. Includes BT audio - receiver and BT Keyboard. One way to repro is to switch BT pairing on - multi-pairing keyboard, then switch back to Ubuntu. The BT connection - state will be very confused, keyboard will not work. + Bluetooth devices don't reconnect after sleep, or something along those + lines. - Another way to repro is to get a bluetooth receiver, pair it. Let the BT - device (or PC?) sleep... now wake up the system. The audio will not - play. BT UI slider says disconnected. If you click the slider it will - go back to off. If you click it quickly >25 times, no joke, it will - reconnect and work. + Includes BT audio receiver and BT Keyboard. One way to repro is to + switch BT pairing on multi-pairing keyboard, then switch back to Ubuntu. + The BT connection state will be very confused, keyboard will not work. + Another way to repro is to get a bluetooth audio receiver, pair it. Let + the BT device (or PC?) sleep... now wake up the system. The audio will + not play. BT UI slider says disconnected. If you click the slider it + will go back to off. If you click it quickly >25 times, no joke, it + will reconnect and work. FYI: Raspbian handles the keyboard fine, have not tested the audio. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 17:09:06 2020 InstallationDate: Installed on 2019-06-10 (366 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20HRCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=df7df2a3-26f4-4fe6-8621-51673ae55b6f ro intel_pstate=disable SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET61W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET61W(1.46):bd04/08/2020:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO hciconfig: - hci0:Type: Primary Bus: USB - BD Address: 88:B1:11:77:AE:CE ACL MTU: 1021:4 SCO MTU: 96:6 - UP RUNNING PSCAN ISCAN - RX bytes:6243797 acl:69580 sco:0 events:629809 errors:0 - TX bytes:488355907 acl:570780 sco:0 commands:32574 errors:0 + hci0:Type: Primary Bus: USB + BD Address: 88:B1:11:77:AE:CE ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING PSCAN ISCAN + RX bytes:6243797 acl:69580 sco:0 events:629809 errors:0 + TX bytes:488355907 acl:570780 sco:0 commands:32574 errors:0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1883028 Title: Bluetooth devices don't reconnect after sleep. Status in bluez package in Ubuntu: New Bug description: Bluetooth devices don't reconnect after sleep, or something along those lines. Includes BT audio receiver and BT Keyboard. One way to repro is to switch BT pairing on multi-pairing keyboard, then switch back to Ubuntu. The BT connection state will be very confused, keyboard will not work. Another way to repro is to get a bluetooth audio receiver, pair it. Let the BT device (or PC?) sleep... now wake up the system. The audio will not play. BT UI slider says disconnected. If you click the slider it will go back to off. If you click it quickly >25 times, no joke, it will reconnect and work. FYI: Raspbian handles the keyboard fine, have not tested the audio. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 17:09:06 2020 InstallationDate: Installed on 2019-06-10 (366 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20HRCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=df7df2a3-26f4-4fe6-8621-51
[Touch-packages] [Bug 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64
Verified on focal using the following procedure - full log attached as well: # install seccomp $ apt install seccomp # try resolving getrlimit for aarch64 $ scmp_sys_resolver -a aarch64 getrlimit -10180 # on the current focal version this fails to resolve correctly and returns -10180 # enable -proposed $ cat
[Touch-packages] [Bug 1881982] Re: Memory leak in parse_report()
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1881982 Title: Memory leak in parse_report() Status in whoopsie package in Ubuntu: New Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. ## Vulnerability in whoopsie - whoopsie 0.2.69 and earlier have a memory leak vulnerability. - An attacker can cause a denial of service (application crash) via a crafted .crash file. ## Basic When a program has been crashed, Linux system tries to create a '.crash' file on '/var/crash/' directory with python script located in '/usr/share/apport/apport'. The file contains a series of system crash information including core dump, syslog, stack trace, memory map info, etc. A user is given read and write permission to the file. After then, whoopsie parses key-value pairs in ‘.crash’ file and encodes it into binary json (bson) format. Lastly, whoopsie forwards the data to a remotely connected Ubuntu error report system. ## Vulnerability We have found a memory leak vulnerability during the parsing the crash file, when a collision occurs on GHashTable through g_hash_table_insert(). According to [1], if the key already exists in the GHashTable, its current value is replaced with the new value. If 'key_destory_func' and 'value_destroy_func' are supplied when creating the table, the old value and the passed key are freed using that function. Unfortunately, whoopsie does not handle the old value and the passed key when collision happens. If a crash file contains same repetitive key-value pairs, it leads to memory leak as much as the amount of repetition and results in denial-of-service. ## Attack 1) Create a fake.crash file memory_leak_poc.py script measures an available memory and generates a malicious crash file that contains same repetitive key-value pairs as much as 20% of the available memory size; 'ProblemType: Crash'. 20% indicates arbitrary amount of the memory leakage. 2) Before the attack, the script checks memory usage of whoopsie process with psutil 3) It triggers the whoopsie to read the fake.crash file 4) Then, it measures the memory usage of whoopsie process 5) It results in denial-of-service and then other users can no longer report crash to the Ubuntu error report system. ## Mitigation We should use g_hash_table_new_full() with ‘key_destroy_func’ and ‘value_destroy_func’ functions instead of g_hash_table_new(). Otherwise, before g_hash_table_insert(), we should check the collision via g_hash_table_lookup_extended() and obtain pointer to the old value and remove it. Sincerely, [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g -hash-table-insert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1883028] Re: Bluetooth devices don't reconnect after sleep.
** Description changed: Bluetooth devices don't reconnect after sleep, or something along those lines. - Includes BT audio receiver and BT Keyboard. One way to repro is to - switch BT pairing on multi-pairing keyboard, then switch back to Ubuntu. - The BT connection state will be very confused, keyboard will not work. + I have experienced this with a BT audio receiver and BT Keyboard. One + way to repro is to switch BT pairing on multi-pairing keyboard, then + switch back to Ubuntu. The BT connection state will be very confused, + keyboard will not work. Another way to repro is to get a bluetooth audio receiver, pair it. Let the BT device (or PC?) sleep... now wake up the system. The audio will not play. BT UI slider says disconnected. If you click the slider it will go back to off. If you click it quickly >25 times, no joke, it will reconnect and work. FYI: Raspbian handles the keyboard fine, have not tested the audio. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 17:09:06 2020 InstallationDate: Installed on 2019-06-10 (366 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20HRCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=df7df2a3-26f4-4fe6-8621-51673ae55b6f ro intel_pstate=disable SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET61W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET61W(1.46):bd04/08/2020:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 88:B1:11:77:AE:CE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:6243797 acl:69580 sco:0 events:629809 errors:0 TX bytes:488355907 acl:570780 sco:0 commands:32574 errors:0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1883028 Title: Bluetooth devices don't reconnect after sleep. Status in bluez package in Ubuntu: New Bug description: Bluetooth devices don't reconnect after sleep, or something along those lines. I have experienced this with a BT audio receiver and BT Keyboard. One way to repro is to switch BT pairing on multi-pairing keyboard, then switch back to Ubuntu. The BT connection state will be very confused, keyboard will not work. Another way to repro is to get a bluetooth audio receiver, pair it. Let the BT device (or PC?) sleep... now wake up the system. The audio will not play. BT UI slider says disconnected. If you click the slider it will go back to off. If you click it quickly >25 times, no joke, it will reconnect and work. FYI: Raspbian handles the keyboard fine, have not tested the audio. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 17:09:06 2020 InstallationDate: Installed on 2019-06-10 (366 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20HRCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=df7df2a3-26f4-4fe6-8621-51673ae55b6f ro intel_pstate=disable SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET61W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET61W(1.46):bd04/08/2020:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR
[Touch-packages] [Bug 1883005] Re: Gnome Shell freeze
*** This bug is a duplicate of bug 1872268 *** https://bugs.launchpad.net/bugs/1872268 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1872268, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - Xorg freeze + Gnome Shell freeze ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Assignee: adsson andre da silva gomes (adsson) => (unassigned) ** This bug has been marked a duplicate of bug 1872268 Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) -- 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/1883005 Title: Gnome Shell freeze Status in gnome-shell package in Ubuntu: New Bug description: This bug have been happing on my PC, in the applications when i open some application folder and after click out of it, to close it. The screen just freeze and i have to reboot my notebook (Lenovo- ideapad-310). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 15:08:37 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: I don't know GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822] InstallationDate: Installed on 2020-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 80UH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=31e5e6b9-3228-4c0a-b10a-d78f6218b8db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 5A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UH:pvrLenovoideapad310-15ISK:rvnLENOVO:rnToronto5A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UH dmi.product.sku: LENOVO_MT_80UH_BU_idea_FM_Lenovo ideapad 310-15ISK dmi.product.version: Lenovo ideapad 310-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883005/+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 1883041] [NEW] libpam-cgfs fails to create freezer cgroup writable by user
Public bug reported: This is on 16.04.6. It appears that on some systems, libpam-cgfs doesn't set the correct cgroup information, which prevents containers from starting. This can be seen by looking at the contents of /proc/self/cgroup, which in my case was: blkio:/user.slice cpu,cpuacct:/user.slice cpuset:/ devices:/user.slice freezer:/ hugetlb:/ memory:/user.slice name=systemd:/user.slice/user-18160.slice/session-12214.scope net_cls,net_prio:/ perf_event:/ pids:/user.slice/user-18160.slice whereas it should have instead of freezer:/ freezer:/user//0 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1883041 Title: libpam-cgfs fails to create freezer cgroup writable by user Status in lxc package in Ubuntu: New Bug description: This is on 16.04.6. It appears that on some systems, libpam-cgfs doesn't set the correct cgroup information, which prevents containers from starting. This can be seen by looking at the contents of /proc/self/cgroup, which in my case was: blkio:/user.slice cpu,cpuacct:/user.slice cpuset:/ devices:/user.slice freezer:/ hugetlb:/ memory:/user.slice name=systemd:/user.slice/user-18160.slice/session-12214.scope net_cls,net_prio:/ perf_event:/ pids:/user.slice/user-18160.slice whereas it should have instead of freezer:/ freezer:/user//0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1883041/+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 1881982] Re: Memory leak in parse_report()
The attachment "g_hash_table_memory_leak.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1881982 Title: Memory leak in parse_report() Status in whoopsie package in Ubuntu: New Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. ## Vulnerability in whoopsie - whoopsie 0.2.69 and earlier have a memory leak vulnerability. - An attacker can cause a denial of service (application crash) via a crafted .crash file. ## Basic When a program has been crashed, Linux system tries to create a '.crash' file on '/var/crash/' directory with python script located in '/usr/share/apport/apport'. The file contains a series of system crash information including core dump, syslog, stack trace, memory map info, etc. A user is given read and write permission to the file. After then, whoopsie parses key-value pairs in ‘.crash’ file and encodes it into binary json (bson) format. Lastly, whoopsie forwards the data to a remotely connected Ubuntu error report system. ## Vulnerability We have found a memory leak vulnerability during the parsing the crash file, when a collision occurs on GHashTable through g_hash_table_insert(). According to [1], if the key already exists in the GHashTable, its current value is replaced with the new value. If 'key_destory_func' and 'value_destroy_func' are supplied when creating the table, the old value and the passed key are freed using that function. Unfortunately, whoopsie does not handle the old value and the passed key when collision happens. If a crash file contains same repetitive key-value pairs, it leads to memory leak as much as the amount of repetition and results in denial-of-service. ## Attack 1) Create a fake.crash file memory_leak_poc.py script measures an available memory and generates a malicious crash file that contains same repetitive key-value pairs as much as 20% of the available memory size; 'ProblemType: Crash'. 20% indicates arbitrary amount of the memory leakage. 2) Before the attack, the script checks memory usage of whoopsie process with psutil 3) It triggers the whoopsie to read the fake.crash file 4) Then, it measures the memory usage of whoopsie process 5) It results in denial-of-service and then other users can no longer report crash to the Ubuntu error report system. ## Mitigation We should use g_hash_table_new_full() with ‘key_destroy_func’ and ‘value_destroy_func’ functions instead of g_hash_table_new(). Otherwise, before g_hash_table_insert(), we should check the collision via g_hash_table_lookup_extended() and obtain pointer to the old value and remove it. Sincerely, [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g -hash-table-insert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1883054] [NEW] Built-in audio device not available until alsa is reloaded
Public bug reported: I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and audio worked fine, using either the built-in speakers/mic on the laptop or via a USB headset when that was plugged in. However, after upgrading to 20.04, the built-in audio device is no longer available until I run "sudo alsa force-reload". Wthhout that WAR, all I see is a dummy audio device. Luckily the USB headset works fine, if plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: swarren7664 F pulseaudio /dev/snd/controlC0: swarren7664 F pulseaudio /dev/snd/pcmC0D0c: swarren7664 F...m pulseaudio /dev/snd/pcmC0D0p: swarren7664 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 10 23:57:08 2020 InstallationDate: Installed on 2016-03-03 (1561 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1DETA6W (2.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ERCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P70 dmi.product.name: 20ERCTO1WW dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70 dmi.product.version: ThinkPad P70 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1883054 Title: Built-in audio device not available until alsa is reloaded Status in alsa-driver package in Ubuntu: New Bug description: I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and audio worked fine, using either the built-in speakers/mic on the laptop or via a USB headset when that was plugged in. However, after upgrading to 20.04, the built-in audio device is no longer available until I run "sudo alsa force-reload". Wthhout that WAR, all I see is a dummy audio device. Luckily the USB headset works fine, if plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: swarren7664 F pulseaudio /dev/snd/controlC0: swarren7664 F pulseaudio /dev/snd/pcmC0D0c: swarren7664 F...m pulseaudio /dev/snd/pcmC0D0p: swarren7664 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 10 23:57:08 2020 InstallationDate: Installed on 2016-03-03 (1561 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1DETA6W (2.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ERCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P70 dmi.product.name: 20ERCTO1WW dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70 dmi.product.version: ThinkPad P70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883054/+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 1883054] Re: Built-in audio device not available until alsa is reloaded
I ran alsa-info before/after running "sudo alsa force-reload" to see if there were any obvious differences in the output. While there are a few differences, nothing really stands out as causing this issue. ** Attachment added: "diff for alsa-info output before/after reloading alsa" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883054/+attachment/5382790/+files/alsa-info-diff.txt -- 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/1883054 Title: Built-in audio device not available until alsa is reloaded Status in alsa-driver package in Ubuntu: New Bug description: I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and audio worked fine, using either the built-in speakers/mic on the laptop or via a USB headset when that was plugged in. However, after upgrading to 20.04, the built-in audio device is no longer available until I run "sudo alsa force-reload". Wthhout that WAR, all I see is a dummy audio device. Luckily the USB headset works fine, if plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: swarren7664 F pulseaudio /dev/snd/controlC0: swarren7664 F pulseaudio /dev/snd/pcmC0D0c: swarren7664 F...m pulseaudio /dev/snd/pcmC0D0p: swarren7664 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 10 23:57:08 2020 InstallationDate: Installed on 2016-03-03 (1561 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1DETA6W (2.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ERCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P70 dmi.product.name: 20ERCTO1WW dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70 dmi.product.version: ThinkPad P70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883054/+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 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
This bug was fixed in the package apport - 2.20.11-0ubuntu40 --- apport (2.20.11-0ubuntu40) groovy; urgency=medium * Build-depend on python3-requests-unixsocket. -- Brian Murray Wed, 10 Jun 2020 12:30:43 -0700 ** Changed in: apport (Ubuntu) Status: Triaged => Fix Released -- 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/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Triaged Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+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
