[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
When downgrading to the prior package, we do not see this problem. We've taken the following steps as a work-around: - apt-get -y --allow-downgrades install libsasl2-2=2.1.26.dfsg1-14build1 - apt-get -y --allow-downgrades install libsasl2-modules-db=2.1.26.dfsg1-14build1 - apt-get -y --allow-downgrades install libsasl2-modules=2.1.26.dfsg1-14build1 - apt-get -y --allow-downgrades install libsasl2-modules-gssapi-mit=2.1.26.dfsg1-14build1 Then we've used apt-pinning to pin those versions: Package: libsasl2-2 Pin: release o=Ubuntu version 2.1.26.dfsg1-14build1 Pin-Priority: 999 Package: libsasl2-modules Pin: release o=Ubuntu version 2.1.26.dfsg1-14build1 Pin-Priority: 999 Package: libsasl2-modules-db Pin: release o=Ubuntu version 2.1.26.dfsg1-14build1 Pin-Priority: 999 Package: libsasl2-modules-gssapi-mit Pin: release o=Ubuntu version 2.1.26.dfsg1-14build1 Pin-Priority: 999 And we've used a hold to (temporarily) keep them from being upgraded: echo hold | sudo dpkg --set-selections ... We've done that for each of the four above packages. Going this route does prevent the issue for now / keeps SSSD from failing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1860432] Re: juju agent fails to start on focal
Upgrade steps: https://github.com/juju/juju/pull/11159 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1860432 Title: juju agent fails to start on focal Status in juju: In Progress Status in systemd package in Ubuntu: Confirmed Bug description: during bootstrap, add-machine, deploy Juju fails on Focal due to systemd not finding the service. ll /etc/systemd/system jujud-machine-1.service -> /lib/systemd/system/jujud-machine-1/jujud-machine-1.service which is linked and calls ExecStart=/lib/systemd/system/jujud-machine-1/exec-start.sh The fact that it's in a jujud-machine-1 folder vs /system itself appears to be causing systemd to not be able to run it. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1860432/+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 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Attachment added: "Bug with SDB6 only" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323755/+files/Bug1857914-sdb6.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+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 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Attachment added: "Bug with only SDB2 partition" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323763/+files/Bug1857914-sdb2.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+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 1861230] Re: _sasl_plugin_load failed
Hi, Could you downgrade to the previous version and check if it happens there too? And so re upgrade and re-test? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1861230] Re: _sasl_plugin_load failed
Can you also please show your sssd version and where it comes from? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1860917] [NEW] uas_eh_abort_handler uas-tag inflight OUT
You have been subscribed to a public bug: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- uas_eh_abort_handler uas-tag inflight OUT https://bugs.launchpad.net/bugs/1860917 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
Hello. When I decide to reduce the size of a partition stored in an external drive and formatted in EXT4 after booting with ubuntu 19.10, this partition is destroyed. it seems abnormal to me. This is systematic for the twelve partitions and twelve boots in the prepared context. If several partitions are reduced in the same passage, only the first in the list is destroyed. The others are well treated! Failure does not occur if another external drive is used. The incident does not occur if the partition is formatted in EXT3 or if the size reduction is done with ubuntu 18.04.3 Some results will be provided as an attachment Here is the script used. export LC_ALL=POSIX Size=35957760k Debug="-d 60" Trace=Bug1857914-ThreePartitions.txt date>$Trace for Part in sdb1 sdb6 sdb7 ;do sudo umount /dev/$Part echo "check file system on /dev/$Part for errors with command sudo e2fsck -f -y -v /dev/$Part >>$TRACE" >>$Trace sudo e2fsck -f -y -v /dev/$Part 2>>$Trace >>$Trace echo " shrink for /dev/$Part with command sudo resize2fs $Debug -p /dev/$Part $Size >>$Trace" >>$Trace sudo resize2fs $Debug -p /dev/$Part $Size 2>>$Trace >>$Trace echo "check file system on /dev/$Part for errors with command sudo e2fsck -f -n -v /dev/$Part >>$TRACE" >>$Trace sudo e2fsck -f -n -v /dev/$Part 2>>$Trace >>$Trace echo "check for erreur on UAS module with command journalctl -b | egrep "resize2fs|uas_eh_abort_handler" >>$TRACE" >>$Trace done journalctl -b | grep -E "resize2fs|CDB|uas_eh_abort_handler|I/O error|sdb" >>$Trace date>>$Trace cat $Trace ** Attachment added: "An execution with three partitions" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323753/+files/Bug1857914-ThreePartitions.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+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 1861230] Re: _sasl_plugin_load failed
We are using SSSD version 1.16.1-1ubuntu1.4 on Ubuntu 18.04.3. The package itself is from the standard Ubuntu repos. $ dpkg -s sssd Package: sssd Status: install ok installed Priority: extra Section: metapackages Installed-Size: 32 Maintainer: Ubuntu Developers Architecture: amd64 Multi-Arch: foreign Version: 1.16.1-1ubuntu1.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Package changed: ubuntu => e2fsprogs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+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 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Attachment added: "Bug with only SDB5 partition" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323754/+files/Bug1857914-sdb5.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+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 1861322] [NEW] PPTP VPN doesn't work out of the box - nf_conntrack_pptp missing
Public bug reported: PPTP based VPN doesn't work out of the box on Focal Fossa. From syslog: Jan 29 19:41:35 thinkpad pppd[8734]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jan 29 19:41:35 thinkpad NetworkManager[8734]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jan 29 19:41:35 thinkpad pptp[8739]: nm-pptp-service-8722 log[main:pptp.c:353]: The synchronous pptp option is NOT activated Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 'Start-Control-Connection-Request' Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established. Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7 'Outgoing-Call-Request' Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply. Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_disp:pptp_ctrl.c:938]: Outgoing call established (call ID 44616, peer's call ID 0). Jan 29 19:42:03 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_disp:pptp_ctrl.c:976]: Call disconnect notification received (call id 44616) Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 log[logecho:pptp_ctrl.c:719]: Echo Request received. Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 6 'Echo-Reply' Jan 29 19:42:06 thinkpad pptp[8739]: nm-pptp-service-8722 warn[decaps_hdlc:pptp_gre.c:226]: short read (-1): Input/output error Jan 29 19:42:06 thinkpad pptp[8739]: nm-pptp-service-8722 warn[decaps_hdlc:pptp_gre.c:238]: pppd may have shutdown, see pppd log Jan 29 19:42:06 thinkpad pppd[8734]: Child process /usr/sbin/pptp 161.53.xxx.yyy --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-8722 (pid 8737) terminated with signal 15 Jan 29 19:42:06 thinkpad NetworkManager[8734]: Child process /usr/sbin/pptp 161.53.xxx.yyy --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-8722 (pid 8737) terminated with signal 15 Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 log[callmgr_main:pptp_callmgr.c:245]: Closing connection (unhandled) Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 12 'Call-Clear-Request' Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 log[call_callback:pptp_callmgr.c:84]: Closing connection (call state) Once nf_conntrack_pptp kernel module is loaded, VPN connection succeeds: Jan 29 19:44:02 thinkpad pppd[10166]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jan 29 19:44:02 thinkpad NetworkManager[10166]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jan 29 19:44:02 thinkpad pptp[10170]: nm-pptp-service-10156 log[main:pptp.c:353]: The synchronous pptp option is NOT activated Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 'Start-Control-Connection-Request' Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established. Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7 'Outgoing-Call-Request' Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply. Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156 log[ctrlp_disp:pptp_ctrl.c:938]: Outgoing call established (call ID 61223, peer's call ID 0). ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: champagne -- 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/1861322 Title: PPTP VPN doesn't work out of the box - nf_conntrack_pptp missing Status in network-manager package in Ubuntu: New Bug description: PPTP based VPN doesn't work out of the box on Focal Fossa. From syslog: Jan 29 19:41:35 thinkpad pppd[8734]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jan 29 19:41:35 thinkpad NetworkManager[8734]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded. Jan 29 19:41:35 thinkpad pptp[8739]: nm-pptp-service-8722 log[main:pptp.c:353]: The synchronous pptp option is NOT activated Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 'Start-Control-Connection-Request' Jan 29 19:41:35 thinkpad pptp[8750]:
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
What about ldap, is that openldap on the same server, or windows ad? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1861230] Re: _sasl_plugin_load failed
I can confirm the sssd dep8 tests pass in bionic with the updated sasl package: Get:3 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsasl2-2 amd64 2.1.27~101-g0780600+dfsg-3ubuntu2.1 [49.2 kB] Get:41 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 sssd-ldap amd64 1.16.1-1ubuntu1.4 [28.8 kB] autopkgtest [12:53:44]: test ldap-user-group-krb5-auth: - - - - - - - - - - results - - - - - - - - - - ldap-user-group-krb5-auth PASS autopkgtest [12:53:45]: summary ldap-user-group-ldap-auth PASS ldap-user-group-krb5-auth PASS (full output here: http://people.ubuntu.com/~ahasenack/sssd-dep8-update- sasl.txt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1861230] Re: _sasl_plugin_load failed
I will try updating the packages to their current-released versions and see if the problem persists. We ran into this issue across several 18.04 deployments yesterday, though. It prevented commands like `id -u username` from working (at least that is how we initially noticed a problem). I'll revert my work-arounds, update the affected packages, and will report-back shortly, though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1860432] Re: juju agent fails to start on focal
** Changed in: juju Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1860432 Title: juju agent fails to start on focal Status in juju: Fix Committed Status in systemd package in Ubuntu: Confirmed Bug description: during bootstrap, add-machine, deploy Juju fails on Focal due to systemd not finding the service. ll /etc/systemd/system jujud-machine-1.service -> /lib/systemd/system/jujud-machine-1/jujud-machine-1.service which is linked and calls ExecStart=/lib/systemd/system/jujud-machine-1/exec-start.sh The fact that it's in a jujud-machine-1 folder vs /system itself appears to be causing systemd to not be able to run it. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1860432/+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 1588562] Re: Please add ~/.local/bin to the default $PATH
This kind of behaviour (letting pass three years and still not fixing this silly to adhere to a known and used standard) is the exact reason I stopped advicing Ubuntu to people. Because it is the exact thing that let people say "this shitty GNU/Linux you adviced me does never work! It took me 5 minutes to start noticing bugs!". It still happens in Ubuntu 19.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1588562 Title: Please add ~/.local/bin to the default $PATH Status in bash package in Ubuntu: Fix Released Status in bash source package in Xenial: Fix Released Status in bash package in Debian: Fix Released Bug description: Starting in Xenial, 'pip install' by default places executables into ~/.local/bin. This is the de-facto standard place to put per-user executables -- for example, Fedora/Redhat puts it on the $PATH by default, and PEP 370 makes it the standard place for unprivileged installs of Python packages to put their scripts. But unfortunately, Ubuntu's does *not* add this directory to $PATH by default, which means that 'pip install' doesn't actually work -- any scripts that are installed are inaccessible, and every user has to manually add this to their PATH. Ubuntu should put ~/.local/bin onto PATH by default. Minor details (discussed with @doko at the PyCon sprints): - this should go at the beginning of PATH rather than the end, in accordance with Debian policy saying that more-local paths go before more-upstream paths. (This is inconsistent with how Fedora/RH do it, but consistent with how Python itself searches for packages.) - this will be added to /etc/skel/profile, so that it won't change any existing user accounts; it will only be applied to user accounts created *after* this change lands - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be added to PATH unconditionally, even if the directory doesn't exist. This is important to avoid a nasty trap for new users, where the first time they try to install a Python package they have to restart their shell. Since this only applies to new accounts, the directory will always start out nonexistent/empty, so having it in $PATH won't cause any unexpected changes in behavior. - possibly it would make sense to set this in /etc/environment or /etc/skel/.gnomerc or similar, so that it would also apply to non-shell processes (e.g. if the user wants to add a global key-binding to launch a Python program, then generally ~/.profile *doesn't* affect the environment where this command gets executed, and that can frustrate and confuse users if a command works fine from the terminal but not from a keybinding). But we should defer this discussion for the future, because even if this is a good idea, it isn't a good idea in a Xenial stable update. Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1588562/+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 1861307] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all
Public bug reported: No sound at all in ubuntu 16.4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-171.200-generic 4.4.203 Uname: Linux 4.4.0-171-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: andre 1507 F...m pulseaudio /dev/snd/pcmC0D0p: andre 1507 F...m pulseaudio /dev/snd/controlC0: andre 1507 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 11:18:59 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-atami161222-xenial-amd64-20170321-0 InstallationDate: Installed on 2019-05-16 (258 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20170321-07:27 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio Interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: andre 1507 F...m pulseaudio /dev/snd/pcmC0D0p: andre 1507 F...m pulseaudio /dev/snd/controlC0: andre 1507 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.44 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 831E dmi.board.vendor: HP dmi.board.version: 17.42 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.44:bd12/13/2018:svnHP:pnHPLaptop14-bs0xx:pvrType1ProductConfigId:rvnHP:rn831E:rvr17.42:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Laptop 14-bs0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1861307 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound at all in ubuntu 16.4 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-171.200-generic 4.4.203 Uname: Linux 4.4.0-171-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: andre 1507 F...m pulseaudio /dev/snd/pcmC0D0p: andre 1507 F...m pulseaudio /dev/snd/controlC0: andre 1507 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 29 11:18:59 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-atami161222-xenial-amd64-20170321-0 InstallationDate: Installed on 2019-05-16 (258 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20170321-07:27 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio Interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: andre 1507 F...m pulseaudio /dev/snd/pcmC0D0p: andre 1507 F...m pulseaudio /dev/snd/controlC0: andre 1507 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.44 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 831E dmi.board.vendor: HP dmi.board.version: 17.42 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.44:bd12/13/2018:svnHP:pnHPLaptop14-bs0xx:pvrType1ProductConfigId:rvnHP:rn831E:rvr17.42:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Laptop 14-bs0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861307/+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 1860522] Re: Mesa 19.2.8 stable release
Installed from the proposed repository the version 19.2.8-0ubuntu0~19.10.1 Works great on: Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-29-generic OS Type: 64-bit Processors: 4 × AMD A8-6500T APU with Radeon(tm) HD Graphics Memory: 7.0 GiB of RAM Thanks for backporting the update! ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Eoan: Fix Committed Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1861237] Re: Audio not detected on 20.04
probably needs 5.5 and newer sof firmware for it ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- 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/1861237 Title: Audio not detected on 20.04 Status in linux package in Ubuntu: Incomplete Bug description: I'm testing out Kubuntu 20.04 on my 4th gen ThinkPad X1 Yoga, and Ubuntu's not detecting audio from it at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861237/+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 1861230] Re: _sasl_plugin_load failed
If I only install the latest packages (without the earlier versions of these packages being installed previously) (i.e., if I do a clean install of the most current packages when deploying a new host), it does not work. If I downgrade the packages to the prior versions, and then upgrade the packages to their latest versions, it does work. To me, this is repeatable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio
I've installed the kernel packages following the guide (sudo dpkg -i FILENAME.deb) but I got the "You need to load the kernel first" grub error message. I guess some steps are missing from the guide? -- 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/1860930 Title: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio Status in alsa-driver package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB headphones. When the headphones are plugged in during boot the internal speakers won't work. There is only crackling sound coming from them. It doesn't help in I unplug the headphones. There is no problem if they are not plugged in during boot. I'm using Ubuntu 19.10. Please let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 19:26:35 2020 InstallationDate: Installed on 2019-12-19 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX531GXR.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX531GXR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus S dmi.product.name: Zephyrus S GX531GXR_GX531GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860930/+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 1861230] Re: _sasl_plugin_load failed
... I tried this following Leonidas' (leosilvab) request to "Could you downgrade to the previous version and check if it happens there too? And so re upgrade and re-test?" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1861230] Re: _sasl_plugin_load failed
By "packages", do you mean only the cyrus-sasl2 packages, or also sssd? In your tests, is sssd being restarted each time? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1861230] Re: _sasl_plugin_load failed
After allowing the packages to be upgraded to their newer versions, the problem does _not_ persist. We see expected / desired results. We only get a good outcome after the packages have been upgraded, though. When the packages are installed as the initial versions ... that is when we consistently see the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1861230] Re: _sasl_plugin_load failed
So, when the system is up-to-date, there is no issue? I thought you started seeing this problem *after* upgrading cyrus-sasl2. Sorry if I'm confused. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT UAS is "USB Attached SCSI", and this error indicates some kind of hardware issue (maybe a loose cable connector?). If you can't replicate the failure, it might be because it's a one-off hardware problem. One thing I would suggest is running e2fsck -f after shrinking the file system using resize2fs. If there is any corruption that you can see when using resize2fs with shrinking, preferably with a fixed HDD or SSD which is known to be good (USB cable instability is a nightmare and I generally don't recommend people to use USB attached storage on laptops because laptops tend to move, and USB cables getting jostled is a really common problem). So from a problem isolation perspective, it's really helpful to try to isolate variables. So if you can try to isolate the problem using a image file stored on a fixed storage device, and then try shrinking the file system on the image, so we don't have to worry about gpart bugs, hardware bugs, etc., that is really helpful.And if you use e2fsck to make sure the file system is consistent, as opposed to waiting for the kernel to trip on the file corruption, that would be also very helpful. If you are paying $$$ to Canonical, then there will be much more likely to be Ubuntu support engineers will do this sort of fault determination procedure. As an upstream developer for e2fsprogs, however, I'm really not going to get involved until you can give me a reproducible test case that doesn't require your specific hardware --- hence the request to see if you can reproduce the problem using an image file without using hardware and partitions. If this is really dependent on which partition is involved, then this might be a gpart bug. And no one (and certainly Canonical!) is paying me to try to debug gpart. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+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 1861230] Re: _sasl_plugin_load failed
Before I continue - I want to say thanks for your response to this report. I appreciate your effort and help. As for the issue, when I say, "If I only install the latest packages" I mean a fully up-to-date system at the time of install, including sssd version 1.16.1-1ubuntu1.4. As part of my testing, I always used sssd version 1.16.1-1ubuntu1.4 (even when I downgraded / upgraded the referenced libsasl packages (libsasl2-2, libsasl2-modules-db, libsasl2-modules, libsasl2-modules-gssapi-mit). In terms of back-end, we use Windows AD. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1851806] Re: 'module' object has no attribute 'O_PATH'
This bug was fixed in the package apport - 2.20.11-0ubuntu16 --- apport (2.20.11-0ubuntu16) focal; urgency=medium * SECURITY REGRESSION: 'module' object has no attribute 'O_PATH' (LP: #1851806) - apport/report.py, apport/ui.py: use file descriptors for /proc/pid directory access only when running under python 3; prevent reading /proc maps under python 2 as it does not provide a secure way to do so; use io.open for better compatibility between python 2 and 3. * data/apport: fix number of arguments passed through socks into a container. * test/test_report.py: test login session with both pid and proc_pid_fd. -- Tiago Stürmer Daitx Mon, 06 Jan 2020 13:28:40 + ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1851806 Title: 'module' object has no attribute 'O_PATH' Status in apport package in Ubuntu: Fix Released Bug description: I encountered the following exception in python-apport while encountering an exception `bup` which uses `python-apport`. I'm sure that the exception lies in the responsibility of `python-apport` (the `AttributeError` stacktrace is relevant): ``` Traceback (most recent call last): File "/usr/lib/bup/cmd/bup-index", line 269, in update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept) File "/usr/lib/bup/cmd/bup-index", line 191, in update_index mi.close() File "/usr/lib/bup/bup/index.py", line 528, in close os.rename(self.tmpname, self.filename) OSError: [Errno 13] Permission denied Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/bup/bup/helpers.py", line 916, in newhook return oldhook(exctype, value, traceback) File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in apport_excepthook pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME']) File "/usr/lib/python2.7/dist-packages/apport/report.py", line 544, in add_proc_info proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH | os.O_DIRECTORY) AttributeError: 'module' object has no attribute 'O_PATH' Original exception was: Traceback (most recent call last): File "/usr/lib/bup/cmd/bup-index", line 269, in update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept) File "/usr/lib/bup/cmd/bup-index", line 191, in update_index mi.close() File "/usr/lib/bup/bup/index.py", line 528, in close os.rename(self.tmpname, self.filename) OSError: [Errno 13] Permission denied ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: python-apport 2.20.11-0ubuntu8.2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 10:43:02 2019 PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-25 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851806/+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 1861345] [NEW] Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1
Public bug reported: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1861345/+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 1861358] Re: tracker search hangs and never returns results
I also found a similar bug report here: https://gitlab.gnome.org/GNOME/tracker/issues/161 ** Bug watch added: gitlab.gnome.org/GNOME/tracker/issues #161 https://gitlab.gnome.org/GNOME/tracker/issues/161 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1861358 Title: tracker search hangs and never returns results Status in tracker package in Ubuntu: New Bug description: When I run $ tracker search -f Bruni I see the following output on console - (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot register existing type 'TrackerLanguage' (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot add private field to invalid (non-instantiatable) type '' (tracker search:2): GLib-CRITICAL **: 00:31:10.761: g_once_init_leave: assertion 'result != 0' failed (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed - The program hangs and never returns. Sending Control-C brings me back to prompt ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.3.0-1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 30 00:31:59 2020 ExecutablePath: /usr/bin/tracker InstallationDate: Installed on 2016-11-05 (1180 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1861358/+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 1861358] [NEW] tracker search hangs and never returns results
Public bug reported: When I run $ tracker search -f Bruni I see the following output on console - (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot register existing type 'TrackerLanguage' (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot add private field to invalid (non-instantiatable) type '' (tracker search:2): GLib-CRITICAL **: 00:31:10.761: g_once_init_leave: assertion 'result != 0' failed (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed - The program hangs and never returns. Sending Control-C brings me back to prompt ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.3.0-1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 30 00:31:59 2020 ExecutablePath: /usr/bin/tracker InstallationDate: Installed on 2016-11-05 (1180 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago) ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1861358 Title: tracker search hangs and never returns results Status in tracker package in Ubuntu: New Bug description: When I run $ tracker search -f Bruni I see the following output on console - (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot register existing type 'TrackerLanguage' (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot add private field to invalid (non-instantiatable) type '' (tracker search:2): GLib-CRITICAL **: 00:31:10.761: g_once_init_leave: assertion 'result != 0' failed (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed - The program hangs and never returns. Sending Control-C brings me back to prompt ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.3.0-1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 30 00:31:59 2020 ExecutablePath: /usr/bin/tracker InstallationDate: Installed on 2016-11-05 (1180 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1861358/+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 1861364] [NEW] /etc/environment.d cannot be used to add to PATH
Public bug reported: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Bug watch added: github.com/systemd/systemd/issues #6414 https://github.com/systemd/systemd/issues/6414 ** Also affects: systemd via https://github.com/systemd/systemd/issues/6414 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861364 Title: /etc/environment.d cannot be used to add to PATH Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname:
[Touch-packages] [Bug 1861363] [NEW] /etc/environment.d cannot be used to add to PATH
Public bug reported: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861363 Title: /etc/environment.d cannot be used to add to PATH Status in systemd package in Ubuntu: New Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co.,
[Touch-packages] [Bug 1861177] Re: seccomp_rule_add is very slow
** Tags added: server-next -- 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: New Status in libseccomp package in Ubuntu: Triaged 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 1861364] Re: /etc/environment.d cannot be used to add to PATH
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861364 Title: /etc/environment.d cannot be used to add to PATH Status in systemd: Fix Released Status in systemd package in Ubuntu: New Bug description: I've added an executable file `/etc/environment.d/60-haskell.conf` with the following contents: PATH=/opt/ghc/bin:$PATH According to `man environment.d`, this is a proper procedure for altering the PATH variable via systemd. However, it does not work on Ubuntu. The PATH on reboot does not include `/opt/ghc/bin`. This is due to `/etc/profile` incorrectly overwriting the PATH according to comment #10 on https://github.com/systemd/systemd/issues/6414. There is a Debian bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=869144 that was prematurely closed because on the Debian side **because it was a Debian issue** rather than a systemd issue, which seems quite nonsensical. Perhaps that issue can be reopened or another can be opened. == Description:Ubuntu 18.04.3 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.33 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jan 29 19:07:31 2020 InstallationDate: Installed on 2019-10-10 (111 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=111df9fc-1d42-47eb-82a6-3a80a0aba4c7 ro consoleblank=0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU modified.conffile..etc.systemd.timesyncd.conf: [modified] mtime.conffile..etc.systemd.timesyncd.conf: 2019-10-10T02:35:05.488000 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1861364/+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 1861230] Re: _sasl_plugin_load failed
We are doing additional testing here. Please sit tight / do not research further until we check into things further on our end. Thanks again for your help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1861230] Re: _sasl_plugin_load failed
In trying to recreate the issue this afternoon, it looks as though installs based on all of the updated / most recent packages are succeeding again (i.e., this may no longer be an issue). In our dpkg logs, we noticed that an update came through today for libc- bin (2.27-3ubuntu1), and wonder if this update may have been part of what resolved the issue. If that is not part of why this is working, then I will bury my head / beg your forgiveness and try to figure out if there was some other cause. Please understand that this stopped working the same day that we got the libsasl2 package updates, and that reverting the libsasl2 updates allowed us to get our installs working, so that is why we filed a bug against this package. Thanks again for your help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1860929] Re: Should include a /usr/bin/python symlink unless..
Is this a written policy / guidance or just something you came up with on the fly? https://blogs.gnome.org/mcatanzaro/2018/02/16/on-python-shebangs/ has a good discussion of this issue and even suggests using python2.7 (as opposed to python2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1860929 Title: Should include a /usr/bin/python symlink unless.. Status in python2.7 package in Ubuntu: Invalid Bug description: Unless there is some plan to reuse /usr/bin/python for python3.x If not or if not in 20.04 then this package should also include a /usr/bin/python symlink to either /usr/bin/python2 or /usr/bin/python2.7 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python2.7-minimal 2.7.17-1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 26 12:52:07 2020 InstallationDate: Installed on 2020-01-13 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: python2.7 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1860929/+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 1861250] Re: Apparmor error failed to start profiles
I'm afraid the logs you attached don't include anything about the reason why you get this failure. Can you please attach the output of systemctl status -n200 apparmor.service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1861250 Title: Apparmor error failed to start profiles Status in apparmor package in Ubuntu: New Bug description: OS Ubuntu focal fossa 20.04 On boot error message - Apparmor Failed to start profiles. Steps attempted to correct 1.sudo as status lee@lee-desktop:~$ sudo aa-status apparmor module is loaded. 53 profiles are loaded. 51 profiles are in enforce mode. /sbin/dhclient /snap/core/8268/usr/lib/snapd/snap-confine /snap/core/8268/usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/bin/evince /usr/bin/evince-previewer /usr/bin/evince-previewer//sanitized_helper /usr/bin/evince-thumbnailer /usr/bin/evince//sanitized_helper /usr/bin/man /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script /usr/lib/cups/backend/cups-pdf /usr/lib/lightdm/lightdm-guest-session /usr/lib/lightdm/lightdm-guest-session//chromium /usr/lib/snapd/snap-confine /usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/lib/telepathy/mission-control-5 /usr/lib/telepathy/telepathy-* /usr/lib/telepathy/telepathy-*//pxgsettings /usr/lib/telepathy/telepathy-*//sanitized_helper /usr/lib/telepathy/telepathy-ofono /usr/sbin/cups-browsed /usr/sbin/cupsd /usr/sbin/cupsd//third_party /usr/sbin/ippusbxd /usr/sbin/tcpdump /usr/share/hplip/plugin.py /usr/share/hplip/sendfax.py /usr/share/hplip/setup.py /usr/share/hplip/systray.py /usr/share/hplip/toolbox.py libreoffice-senddoc libreoffice-soffice//gpg libreoffice-xpdfimport lsb_release man_filter man_groff nvidia_modprobe nvidia_modprobe//kmod snap-update-ns.core snap-update-ns.gnome-calculator snap-update-ns.gnome-characters snap-update-ns.gnome-logs snap-update-ns.gnome-system-monitor snap.core.hook.configure snap.gnome-calculator.gnome-calculator snap.gnome-characters.gnome-characters snap.gnome-logs.gnome-logs snap.gnome-system-monitor.gnome-system-monitor system_tor 2 profiles are in complain mode. libreoffice-oopslash libreoffice-soffice 3 processes have profiles defined. 3 processes are in enforce mode. /usr/lib/telepathy/mission-control-5 (3090) /usr/sbin/cupsd (1646) /usr/bin/tor (1861) system_tor 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. lee@lee-desktop:~$ 2.sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ 3.sudo rm -rf /etc/apparmor.d/cache/* 4. sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ Thanks, Lee ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 23:19:19 2020 InstallationDate: Installed on 2013-08-08 (2365 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=d2e1abc4-e044-467e-8cc2-57cbe4ef3115 ro drm.debug=0xe plymouth:debug SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1861250/+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
** Tags added: patch -- 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: New Status in libseccomp package in Ubuntu: Triaged 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 1861177] Re: seccomp_rule_add is very slow
The patch mentioned in the OP is attached for reference. Per [1] it was proposed for inclusion in Debian last November as patches db- consolidate-some-of-the-code-which-adds-rules-to-.patch and db-add- shadow-transactions.patch. The corresponding bug report upstream is [2]. 1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 2: https://github.com/seccomp/libseccomp/issues/153 ** Bug watch added: Debian Bug tracker #943913 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 ** Bug watch added: github.com/seccomp/libseccomp/issues #153 https://github.com/seccomp/libseccomp/issues/153 ** Patch added: "0001-Cherry-pick-upstream-commits-21b98d8-and-19af04d.patch" https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1861177/+attachment/5323922/+files/0001-Cherry-pick-upstream-commits-21b98d8-and-19af04d.patch -- 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: New Status in libseccomp package in Ubuntu: Triaged 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 1861177] Re: seccomp_rule_add is very slow
2.4.1 is currently available from xenial, bionic, disco, eoan; focal carries 2.4.2. None of these carry the patches for this bug report yet. ** Changed in: libseccomp (Ubuntu) Importance: Undecided => High ** Changed in: libseccomp (Ubuntu) Status: New => Triaged -- 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: New Status in libseccomp package in Ubuntu: Triaged 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 1861345] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1861345 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1
apport information ** Tags added: apport-collected ** Description changed: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: richard2533 F pulseaudio + /dev/snd/controlC1: richard2533 F pulseaudio + /dev/snd/controlC0: richard2533 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-01-28 (2 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-28-generic N/A + linux-backports-modules-5.3.0-28-generic N/A + linux-firmware1.173.14 + Tags: bionic + Uname: Linux 5.3.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/06/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F11 + dmi.board.asset.tag: Default string + dmi.board.name: X570 AORUS MASTER + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: Default string + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: Default string + dmi.product.name: X570 AORUS MASTER + dmi.product.sku: Default string + dmi.product.version: -CF + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324050/+files/AlsaInfo.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor:
[Touch-packages] [Bug 1861237] [NEW] Audio not detected on 20.04
You have been subscribed to a public bug: I'm testing out Kubuntu 20.04 on my 4th gen ThinkPad X1 Yoga, and Ubuntu's not detecting audio from it at all. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 audio focal thinkpad -- Audio not detected on 20.04 https://bugs.launchpad.net/bugs/1861237 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Note that iperf was identical whereas netperf and mtr showed up differences (so it's possibly sporadic as well, not continuous) 1. iperf tcp test -- GoodSystem.9.84 Gbits/sec BadSystem18.37 Gbits/sec BadSystem2...9.85 Gbits/sec 2. iperf udp test -- GoodSystem.1.05 Mbits/sec BadSystem2...1.05 Mbits/sec 3. mtr ping test --- GoodSystem..0.0% Loss; 0.2 Avg; 0.1 Best, 0.9 Worst, 0.1 StdDev BadSystem2...11.7% Loss; 0.1 Avg; 0.1 Best, 0.2 Worst, 0.0 StdDev 4. netperf tcp_rr 1/1 bytes GoodSystem..17921.83 t/sec BadSystem1.13912.45 t/sec BadSystem2 5. netperf tcp_rr 64/64 bytes GoodSystem..16987.48 t/sec BadSystem1.13355.93 t/sec BadSystem2 6. netperf tcp_rr 128/8192 bytes --- GoodSystem..2396.45 t/sec BadSystem1.1678.54 t/sec BadSystem2 -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
** Attachment added: "active interface ethtool-S" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1853638/+attachment/5324070/+files/ethtool-S-enp94s0f0 -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed the troubleshooting information on this link to try determine
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
** Attachment added: "backup interface ethtool-S" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1853638/+attachment/5324071/+files/ethtool-S-enp94s0f1d1 -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed the troubleshooting information on this link to try
[Touch-packages] [Bug 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1
** Tags added: bionic ** Package changed: pulseaudio (Ubuntu) => alsa-driver (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1834875] Re: cloud-init growpart race with udev
So I've been handed the job of moving this bug forward this iteration. Having just re-read all the comments again and read some source code while listening to loud techno music my observations/questions are these: 1) this is a doozy 2) I would really like to see complete udevadm monitor and inotify output for successful and failing boots 3) As far as I can read the gdisk source, there is no point when there no entry for the partition on disk (i.e. it only writes the partition tables once) 4) I think this comment "I believe the kernel event is emitted before the partition table has necessarily been fully updated so when udev processes the event and reads the partition table, sometimes it finds the partition and sometimes it doesn't." is not quite right, or at least there is another possibility entirely consistent with the observed facts: the diff in comment #24 looks more like udev finds the partition OK but fails to fill out the ID_PART_ENTRY_* entries. These come from libblkid via udev-builtin-blkid.c. The part about this theory that doesn't make sense is that the ID_FS_* entries are there and they come from the same codepath. So who knows! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: New Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio
You need four packages: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/linux- headers-5.5.0-050500_5.5.0-050500.202001262030_all.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/linux- headers-5.5.0-050500-generic_5.5.0-050500.202001262030_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/linux-image- unsigned-5.5.0-050500-generic_5.5.0-050500.202001262030_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/linux- modules-5.5.0-050500-generic_5.5.0-050500.202001262030_amd64.deb then install them together: sudo dpkg -i *.deb and then reboot. If it still doesn't work then try: sudo update-grub -- 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/1860930 Title: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio Status in alsa-driver package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB headphones. When the headphones are plugged in during boot the internal speakers won't work. There is only crackling sound coming from them. It doesn't help in I unplug the headphones. There is no problem if they are not plugged in during boot. I'm using Ubuntu 19.10. Please let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 19:26:35 2020 InstallationDate: Installed on 2019-12-19 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX531GXR.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX531GXR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus S dmi.product.name: Zephyrus S GX531GXR_GX531GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860930/+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 1861237] Re: Audio not detected on 20.04
Yes, probably, but the bug needs to be assigned to pulseaudio to collect both Pulse and ALSA info when apport-collect gets run. ** Package changed: linux (Ubuntu) => pulseaudio (Ubuntu) -- 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/1861237 Title: Audio not detected on 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm testing out Kubuntu 20.04 on my 4th gen ThinkPad X1 Yoga, and Ubuntu's not detecting audio from it at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1861237/+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 1860929] Re: Should include a /usr/bin/python symlink unless..
** Changed in: python2.7 (Ubuntu) Status: Invalid => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1860929 Title: Should include a /usr/bin/python symlink unless.. Status in python2.7 package in Ubuntu: Opinion Bug description: Unless there is some plan to reuse /usr/bin/python for python3.x If not or if not in 20.04 then this package should also include a /usr/bin/python symlink to either /usr/bin/python2 or /usr/bin/python2.7 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python2.7-minimal 2.7.17-1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 26 12:52:07 2020 InstallationDate: Installed on 2020-01-13 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) SourcePackage: python2.7 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1860929/+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 1861345] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324058/+files/Lspci.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324067/+files/RfKill.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Hello, Edwin, We have two separate users/customers filing reports, and I can answer for one of them. I'll ask the original poster separately as well to reply. With respect to one of these situations, this is the following system: Dell PowerEdge R440/0XP8V5, BIOS 2.2.11 06/14/2019 Note that a similar system does not have any issues: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.3.4 11/08/2016 So the NIC in the "bad" environment is: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller (rev 01) Product Name: Broadcom Adv. Dual 10G SFP+ Ethernet The NIC in the "good" environment is: Broadcom Inc. and subsidiaries NetXtreme II BCM57810 10 Gigabit Ethernet [14e4:1006] Product Name: QLogic 57810 10 Gigabit Ethernet I'll have to scrub some files and see what I can attach, apologies, I'll have it here by tmrw. Unfortunately, we don't have an easy reproducer. A single iperf and netperf test (both UDP and TCP) showed identical results from both "good" and "bad" environments. What we have is an identical kernel, network configuration and stack with the "bad" system showing double, triple the latency to the systems from a remote server. I'll have more information for you shortly here regarding the exact k8 cmd. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error.
[Touch-packages] [Bug 1861345] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324068/+files/UdevDb.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1
I have already tested it in the mainline kernel. I ran the command as told. Same problem persists in all kernels I have tried. Currently, tested on uname -r = 5.3.0-28-generic the mainline kernel for 18.04.3 LTS. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324054/+files/CurrentDmesg.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324052/+files/CRDA.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324069/+files/WifiSyslog.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324062/+files/ProcCpuinfoMinimal.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324063/+files/ProcEnviron.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324056/+files/IwConfig.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324066/+files/PulseList.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324064/+files/ProcInterrupts.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324065/+files/ProcModules.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324061/+files/ProcCpuinfo.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1861345] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1861345/+attachment/5324060/+files/Lsusb.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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1860268] Re: window titlebar is disturbed on all non-maximized windows
*** This bug is a duplicate of bug 1841718 *** https://bugs.launchpad.net/bugs/1841718 was fixed for me with common Ubuntu updates related to bug #1841718. ** This bug has been marked a duplicate of bug 1841718 [radeon] Rendering of combo boxes and tooltips is broken -- 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/1860268 Title: window titlebar is disturbed on all non-maximized windows Status in mesa package in Ubuntu: New Bug description: * After todays package update, the window titlebar area of all windows is rendered in a disturbed way. * Package update include a kernel change to 5.3 from 5.0. The bug is not related to the kernel; it also happen with the last one. Therefore, it's related to the new graphic packages. * This don't happen if the window is maximized. * This was also on a second PC with idential hardware (Dell 755 & Radeon HD 6450 video card) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-26-generic 5.3.0-26.28~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 19 12:44:46 2020 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860268/+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 1854355] Re: LUKS partition on LVM has wrong device name
I have changed the title of this bug as I have encountered the same issue on a laptop that only has a single disk so a system having more than one disk isn't causing this issue. Details of the other machine Ubuntu release: Ubuntu Desktop 18.04.2 LTS Kernel: 5.3.0-26-generic Storage devices: 2TB HDD Output of lsblk: sda 8:00 1.8T 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:20 732M 0 part /boot └─sda3 8:30 1.8T 0 part └─sdb3_crypt 253:00 1.8T 0 crypt ├─ubuntu--vg-root 253:10 1.8T 0 lvm / └─ubuntu--vg-swap_1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1854355 Title: LUKS partition on LVM has wrong device name Status in lvm2 package in Ubuntu: New Bug description: Ubuntu release: Ubuntu Desktop 18.04.2 LTS Kernel: 5.0.0-36-generic Storage devices: two NVMe SSDs (1TB and 512GB) Ubuntu Desktop install – selected the options to use disk encryption and LVM The largest disk (1TB) is used for the Ubuntu install and this has the device name /dev/nvme0n1 in the Ubiquity installer. Install completes and upon rebooting the operating system asks for the encryption passphrase for the LUKS partition (nvme0n1p3_crypt) which does decrypt as expected. Now when logging in and running lsblk it shows the LUKS partition to be in the wrong place. The 1TB disk now has the name nvme1n1 but the LUKS partition on that disk has the name nvme0n1p3_crypt. Output of lsblk: nvme1n1 259:00 953.9G 0 disk ├─nvme1n1p1 259:10 512M 0 part /boot/efi ├─nvme1n1p2 259:20 732M 0 part /boot └─nvme1n1p3 259:30 952.7G 0 part └─nvme0n1p3_crypt 253:00 952.7G 0 crypt ├─ubuntu--vg-root 253:10 930.4G 0 lvm / └─ubuntu--vg-swap_1 253:20 976M 0 lvm [SWAP] nvme0n1 259:40 477G 0 disk The LUKS partition doesn’t appear to be under nvme0n1p3 but it does on nvme1n1p3 which can be seen when running a luksDump command. Output of luksDump: root@USERPC:~# cryptsetup luksDump /dev/nvme0n1p3 | grep -i "slot 0" Device /dev/nvme0n1p3 doesn't exist or access denied. root@USERPC:~# cryptsetup luksDump /dev/nvme1n1p3 | grep -i "slot 0" Key Slot 0: ENABLED The implications of this so far in my case is not being able to find the correct LUKS partition device name via custom scripts to populate/modify key slots (e.g. 'dmsetup ls' returns the device name nvme0n1p3_crypt). There has not been an issue with Ubuntu decrypting the disk before the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1854355/+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 1854355] Re: LUKS partition on LVM has wrong device name
** Summary changed: - LUKS partition on LVM with two disks has wrong device name + LUKS partition on LVM has wrong device name -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1854355 Title: LUKS partition on LVM has wrong device name Status in lvm2 package in Ubuntu: New Bug description: Ubuntu release: Ubuntu Desktop 18.04.2 LTS Kernel: 5.0.0-36-generic Storage devices: two NVMe SSDs (1TB and 512GB) Ubuntu Desktop install – selected the options to use disk encryption and LVM The largest disk (1TB) is used for the Ubuntu install and this has the device name /dev/nvme0n1 in the Ubiquity installer. Install completes and upon rebooting the operating system asks for the encryption passphrase for the LUKS partition (nvme0n1p3_crypt) which does decrypt as expected. Now when logging in and running lsblk it shows the LUKS partition to be in the wrong place. The 1TB disk now has the name nvme1n1 but the LUKS partition on that disk has the name nvme0n1p3_crypt. Output of lsblk: nvme1n1 259:00 953.9G 0 disk ├─nvme1n1p1 259:10 512M 0 part /boot/efi ├─nvme1n1p2 259:20 732M 0 part /boot └─nvme1n1p3 259:30 952.7G 0 part └─nvme0n1p3_crypt 253:00 952.7G 0 crypt ├─ubuntu--vg-root 253:10 930.4G 0 lvm / └─ubuntu--vg-swap_1 253:20 976M 0 lvm [SWAP] nvme0n1 259:40 477G 0 disk The LUKS partition doesn’t appear to be under nvme0n1p3 but it does on nvme1n1p3 which can be seen when running a luksDump command. Output of luksDump: root@USERPC:~# cryptsetup luksDump /dev/nvme0n1p3 | grep -i "slot 0" Device /dev/nvme0n1p3 doesn't exist or access denied. root@USERPC:~# cryptsetup luksDump /dev/nvme1n1p3 | grep -i "slot 0" Key Slot 0: ENABLED The implications of this so far in my case is not being able to find the correct LUKS partition device name via custom scripts to populate/modify key slots (e.g. 'dmsetup ls' returns the device name nvme0n1p3_crypt). There has not been an issue with Ubuntu decrypting the disk before the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1854355/+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 1836444] Re: Merge qt4-x11 4:4.8.7+dfsg-18 (universe) from Debian unstable (main)
As we are looking to completely remove Qt4 in Focal, that would be a waste of time/effort. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1836444 Title: Merge qt4-x11 4:4.8.7+dfsg-18 (universe) from Debian unstable (main) Status in qt4-x11 package in Ubuntu: New Bug description: Please merge qt4-x11 4:4.8.7+dfsg-18 (universe) from Debian unstable (main) I cannot work on this merge myself. I filed this bug as a reference. Explanation of the Ubuntu delta: * Merge with Debian since qtchooser has versioned Breaks. (LP: #1584654) * Add one more macro to qt4-x11 moc to fix failing to parse BOOST_JOIN. * No-change rebuild for libpng soname change. * Rebuild against libmysqlclient20. * Merge with Debian; remaining changes: - Pass list-missing to dh_install instead of fail-missing, since we don't install the QtWebkit headers - Make sure libqt4-opengl-dev depends on gles libs for armel and armhf - Do not package ibase/firebird and sqlite2 package + remove from debian/control + libqt4-sql doesn't recommend libqt4-sql-ibase and libqt4-sql-sqlite2 - Also exclude webkit examples from dh_shlibdeps - Do not build libqt4-phonon, disable in debian/control - Add debian/Trolltech.conf and install it in libqtcore4.install - Build with -no-neon on armel and armhf - Build with -no-javascript-jit on arm64 - Add patches: + kubuntu_10_ibus_input_method.diff + kubuntu_12_fix_stack_protector.diff + kubuntu_28_xi2.1.patch + kubuntu_30_translucent_drag_pixmap.diff + kubuntu_37_cups_settings.diff + kubuntu_39_fix_medium_font.diff + kubuntu_40_disable_neon.patch + kubuntu_43_no_meego_helper.patch + kubuntu_93_disable_overlay_scrollbars.diff + kubuntu_94_xinput_valuators_fix.diff + kubuntu_95_qt_disable_bounce.diff + kubuntu_97_a11y_qt_and_qml_backport.diff + kubuntu_98_a11y_fix_crash.diff + kubuntu_glib-honor-ExcludeSocketNotifiers-flag.diff + kubuntu_qclipboard_delay.diff + kubuntu_qclipboard_fix_recursive.diff - Drop powerpc_designer_gstabs.diff, it breaks powerpc * Update symbols files. Changelog entries since current eoan version 4:4.8.7+dfsg-7ubuntu1: qt4-x11 (4:4.8.7+dfsg-18) unstable; urgency=medium * Team upload. [ Edward Betts ] * debian/NEWS: Replace UNRELEASED with unstable. [ Alexander Volkov ] * Backport some vulnerability fixes from Qt 5 (closes: #923003). - CVE-2018-15518: double free or corruption in QXmlStreamReader. - CVE-2018-19869: Qt Svg crash when parsing malformed url reference. - CVE-2018-19870: NULL pointer dereference in QGifHandler. - CVE-2018-19871: QTgaFile CPU exhaustion. - CVE-2018-19872: crash when parsing a malformed PPM image. - CVE-2018-19873: QBmpHandler segfault on malformed BMP file. -- Dmitry Shachnev Fri, 12 Apr 2019 23:10:28 +0300 qt4-x11 (4:4.8.7+dfsg-17) unstable; urgency=medium * Add fix-build-icu59.patch from OpenSuse. Fixes build with icu59 (Closes: #898542). Thanks John Paul Adrian Glaubitz for digging the patch! * Put the source package in section oldlibs. We do not expect new developments with qt4-x11. * Update Vcs-[Git Browser] to the new location in salsa.debian.org. -- Lisandro Damián Nicanor Pérez Meyer Tue, 15 May 2018 13:24:10 -0300 qt4-x11 (4:4.8.7+dfsg-16) unstable; urgency=medium * Update symbols files with buildds' logs. * Add a patch by Manuel A. Fernandez Montecelo to provide riscv64 support (Closes: #897667). -- Lisandro Damián Nicanor Pérez Meyer Fri, 04 May 2018 22:53:17 -0300 qt4-x11 (4:4.8.7+dfsg-15) unstable; urgency=medium * Actually upload it to unstable. -- Lisandro Damián Nicanor Pérez Meyer Wed, 18 Apr 2018 17:45:31 -0300 qt4-x11 (4:4.8.7+dfsg-14) experimental; urgency=medium * Update symbols files with buildds' logs. * Add NEWS.Debian to explicitely tell users of the OpenSSL 1.1 patch. -- Lisandro Damián Nicanor Pérez Meyer Wed, 18 Apr 2018 16:30:10 -0300 qt4-x11 (4:4.8.7+dfsg-13) experimental; urgency=medium * Add extra patch from Dmitry Eremin-Solenikov to make Qt4 work with OpenSSL 1.1 (Closes: #873275). * Recommend default-libmysqlclient-dev instead of libmysqlclient-dev. -- Lisandro Damián Nicanor Pérez Meyer Fri, 10 Nov 2017 15:36:11 -0300 qt4-x11 (4:4.8.7+dfsg-12) experimental; urgency=medium * Add openssl_1.1.patch to let Qt4 use OpenSSL 1.1 (Closes: #828522). - Switch libssl-1.0-dev to libssl-dev to use OpenSSL 1.1. * Update symbols files with current build log. -- Lisandro Damián Nicanor Pérez Meyer Tue, 15 Aug 2017 13:25:00 -0300 qt4-x11 (4:4.8.7+dfsg-11)
[Touch-packages] [Bug 1859246] Re: Built in audio speakers/earphones + microphone + SPDIF not activated.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1859246 Title: Built in audio speakers/earphones + microphone + SPDIF not activated. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Only audio through HDMI activated and working. Ubuntu is 20.04 LTS, but issue with audio is the same independent of Ubuntu release in use. See created alsa-information script through link: http://alsa-project.org/db/?f=c5f459dfb6183f1cd98f8a0bfd649a98869f009a Shorted below: !Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b10 irq 145 !!PCI Soundcards installed in the system !!-- 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) !!Loaded sound module options !!--- !!Module: snd_hda_intel !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Intel Kabylake HDMI Address: 2 APLAY *** List of PLAYBACK Hardware Devices *** card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1859246/+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 1859246] Re: Built in audio speakers/earphones + microphone + SPDIF not activated.
Related to https://answers.launchpad.net/ubuntu/+source/alsa- driver/+question/682843 -- 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/1859246 Title: Built in audio speakers/earphones + microphone + SPDIF not activated. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Only audio through HDMI activated and working. Ubuntu is 20.04 LTS, but issue with audio is the same independent of Ubuntu release in use. See created alsa-information script through link: http://alsa-project.org/db/?f=c5f459dfb6183f1cd98f8a0bfd649a98869f009a Shorted below: !Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b10 irq 145 !!PCI Soundcards installed in the system !!-- 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) !!Loaded sound module options !!--- !!Module: snd_hda_intel !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Intel Kabylake HDMI Address: 2 APLAY *** List of PLAYBACK Hardware Devices *** card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1859246/+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