[Touch-packages] [Bug 1902403] [NEW] [HP Compaq 6005 Pro SFF PC, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
Public bug reported: No audio at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saint 1685 F pulseaudio /dev/snd/controlC0: saint 1685 F pulseaudio /dev/snd/pcmC0D0p: saint 1685 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 23:27:11 2020 InstallationDate: Installed on 2020-11-01 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [HP Compaq 6005 Pro SFF PC, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G6 v01.15 dmi.board.asset.tag: 2UA1320F73 dmi.board.name: 3047h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA1320F73 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G6v01.15:bd08/02/2011:svnHewlett-Packard:pnHPCompaq6005ProSFFPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 6005 Pro SFF PC dmi.product.sku: SN052UC#ABA dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1902403 Title: [HP Compaq 6005 Pro SFF PC, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No audio at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saint 1685 F pulseaudio /dev/snd/controlC0: saint 1685 F pulseaudio /dev/snd/pcmC0D0p: saint 1685 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 23:27:11 2020 InstallationDate: Installed on 2020-11-01 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [HP Compaq 6005 Pro SFF PC, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G6 v01.15 dmi.board.asset.tag: 2UA1320F73 dmi.board.name: 3047h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA1320F73 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G6v01.15:bd08/02/2011:svnHewlett-Packard:pnHPCompaq6005ProSFFPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 6005 Pro SFF PC dmi.product.sku: SN052UC#ABA dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1902403/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Changed in: aptdaemon Assignee: (unassigned) => Ahmed Mohamed Tayel (atayel18) ** Changed in: debconf (Ubuntu) Assignee: (unassigned) => Ahmed Mohamed Tayel (atayel18) ** Changed in: aptdaemon (Ubuntu) Assignee: (unassigned) => Ahmed Mohamed Tayel (atayel18) ** Changed in: debconf (Ubuntu) Status: Triaged => New ** Changed in: debconf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Fix Released Status in Debconf: New Status in aptdaemon package in Ubuntu: Invalid Status in debconf package in Ubuntu: Fix Released Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1902391] [NEW] Who maintain isc-dhcp-server.service ?
Public bug reported: I cant find this file in repository https://salsa.debian.org/dhcp-team /isc-dhcp The file seams to be long unmaintained and outdated and I don't even know where to post a patch. There are multiple bugs associated with it: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172 https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1824433 https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1774342 The file /etc/default/isc-dhcp-server format was changed but no one has changed the /lib/systemd/system/isc-dhcp-server.service ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1902391 Title: Who maintain isc-dhcp-server.service ? Status in isc-dhcp package in Ubuntu: New Bug description: I cant find this file in repository https://salsa.debian.org/dhcp-team /isc-dhcp The file seams to be long unmaintained and outdated and I don't even know where to post a patch. There are multiple bugs associated with it: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172 https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1824433 https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1774342 The file /etc/default/isc-dhcp-server format was changed but no one has changed the /lib/systemd/system/isc-dhcp-server.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1902391/+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 1902375] Re: network printer - unable to send print jobs from desktop
** Package changed: ubuntu => cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1902375 Title: network printer - unable to send print jobs from desktop Status in cups package in Ubuntu: New Bug description: ubuntu-bug cups information sent via ubuntu-bug cups able to print to same printer via Samsung mobile app and from Windows 10 PC. Ubuntu 20.04.1 LTS, release 20.04 Printer is turned on, print job sent, printer then powers off abruptly with no print job performed and then turns back on again. cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 17:18:14 2020 InstallationDate: Installed on 2020-04-26 (188 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for Samsung_CLX_3300_Series_SEC001599DA3F52_: implicitclass://Samsung_CLX_3300_Series_SEC001599DA3F52_/ device for Samsung_CLX_3300_Series_SEC001599DA3F52_@SEC001599DA3F52.local: implicitclass://Samsung_CLX_3300_Series_SEC001599DA3F52_%40SEC001599DA3F52.local/ MachineType: TOSHIBA QOSMIO DX730 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/samsung_clx_3300_series_sec001599da3f...@sec001599da3f52.local.ppd', '/etc/cups/ppd/Samsung_CLX_3300_Series_SEC001599DA3F52_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/samsung_clx_3300_series_sec001599da3f...@sec001599da3f52.local.ppd: Permission denied grep: /etc/cups/ppd/Samsung_CLX_3300_Series_SEC001599DA3F52_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.name: All In One PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd10/17/2011:svnTOSHIBA:pnQOSMIODX730:pvrPQQ10E-01Y00CEN:rvnTOSHIBA:rnAllInOnePC:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct13:cvrOEMChassisVersion: dmi.product.name: QOSMIO DX730 dmi.product.sku: PQQ10E-01Y00CEN dmi.product.version: PQQ10E-01Y00CEN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1902375/+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 1902375] [NEW] network printer - unable to send print jobs from desktop
You have been subscribed to a public bug: ubuntu-bug cups information sent via ubuntu-bug cups able to print to same printer via Samsung mobile app and from Windows 10 PC. Ubuntu 20.04.1 LTS, release 20.04 Printer is turned on, print job sent, printer then powers off abruptly with no print job performed and then turns back on again. cups: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 17:18:14 2020 InstallationDate: Installed on 2020-04-26 (188 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for Samsung_CLX_3300_Series_SEC001599DA3F52_: implicitclass://Samsung_CLX_3300_Series_SEC001599DA3F52_/ device for Samsung_CLX_3300_Series_SEC001599DA3F52_@SEC001599DA3F52.local: implicitclass://Samsung_CLX_3300_Series_SEC001599DA3F52_%40SEC001599DA3F52.local/ MachineType: TOSHIBA QOSMIO DX730 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/samsung_clx_3300_series_sec001599da3f...@sec001599da3f52.local.ppd', '/etc/cups/ppd/Samsung_CLX_3300_Series_SEC001599DA3F52_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/samsung_clx_3300_series_sec001599da3f...@sec001599da3f52.local.ppd: Permission denied grep: /etc/cups/ppd/Samsung_CLX_3300_Series_SEC001599DA3F52_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.name: All In One PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd10/17/2011:svnTOSHIBA:pnQOSMIODX730:pvrPQQ10E-01Y00CEN:rvnTOSHIBA:rnAllInOnePC:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct13:cvrOEMChassisVersion: dmi.product.name: QOSMIO DX730 dmi.product.sku: PQQ10E-01Y00CEN dmi.product.version: PQQ10E-01Y00CEN dmi.sys.vendor: TOSHIBA ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- network printer - unable to send print jobs from desktop https://bugs.launchpad.net/bugs/1902375 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups 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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: glibc (Ubuntu) Assignee: Ahmed Mohamed Tayel (atayel18) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in GLibC: New Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Committed Status in glibc package in Ubuntu: Invalid Status in apt source package in Bionic: Triaged Status in glibc source package in Bionic: Invalid Status in apt source package in Focal: Triaged Status in glibc source package in Focal: Invalid Status in apt source package in Groovy: Fix Committed Status in apt package in Debian: Fix Released Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: glibc (Ubuntu) Assignee: (unassigned) => Ahmed Mohamed Tayel (atayel18) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in GLibC: New Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Committed Status in glibc package in Ubuntu: Invalid Status in apt source package in Bionic: Triaged Status in glibc source package in Bionic: Invalid Status in apt source package in Focal: Triaged Status in glibc source package in Focal: Invalid Status in apt source package in Groovy: Fix Committed Status in apt package in Debian: Fix Released Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic
[Touch-packages] [Bug 1044549] Re: The "Access Prompt" randomly pop up!
@raphael-droz stop subscribing people to your pet issue. If you can't leverage the fact that this is open source and you're free to modify it to your needs, then go buy a support contract to get the help! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1044549 Title: The "Access Prompt" randomly pop up! Status in gcr package in Ubuntu: Triaged Bug description: Access Prompt randomly pop up and prompt you for the password. Have you ever when opened Youtube, Facebook, Launchpad account!n And now opened a picture of the computer when pop up"Access Prompt" I use autologin. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gcr 3.5.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 Date: Fri Aug 31 22:33:44 2012 ExecutablePath: /usr/lib/gcr/gcr-prompter InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) SourcePackage: gcr UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (gnome-settings-daemon:1401): libappindicator-WARNING **: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.48 was not provided by any .service files (gnome-control-center:2016): background-cc-panel-WARNING **: Could not load /usr/share/themes/Adwaita/index.theme: Nincs ilyen fájl vagy könyvtár (gnome-control-center:2016): GLib-GIO-CRITICAL **: g_settings_set_value: assertion `G_IS_SETTINGS (settings)' failed (gnome-control-center:2016): Gtk-CRITICAL **: gtk_builder_get_object: assertion `GTK_IS_BUILDER (builder)' failed (gnome-control-center:2016): Gtk-CRITICAL **: gtk_icon_view_get_selected_items: assertion `GTK_IS_ICON_VIEW (icon_view)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549/+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 1464735] Re: package libtiff4 (not installed) failed to install/upgrade: trying to overwrite shared '/usr/share/lintian/overrides/libtiff4', which is different from other instanc
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tiff (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1464735 Title: package libtiff4 (not installed) failed to install/upgrade: trying to overwrite shared '/usr/share/lintian/overrides/libtiff4', which is different from other instances of package libtiff4:amd64 Status in tiff package in Ubuntu: Confirmed Bug description: unsupported library libtiff4 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libtiff4 (not installed) ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 Uname: Linux 3.13.0-51-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 AptOrdering: libtiff4: Install libtiff4: Configure Architecture: amd64 Date: Thu Jun 11 23:28:34 2015 DpkgTerminalLog: Preparing to unpack .../libtiff4_3.9.5-2ubuntu1.8_amd64.deb ... Unpacking libtiff4:amd64 (3.9.5-2ubuntu1.8) ... dpkg: error processing archive /var/cache/apt/archives/libtiff4_3.9.5-2ubuntu1.8_amd64.deb (--unpack): trying to overwrite shared '/usr/share/lintian/overrides/libtiff4', which is different from other instances of package libtiff4:amd64 DuplicateSignature: package:libtiff4:(not installed):trying to overwrite shared '/usr/share/lintian/overrides/libtiff4', which is different from other instances of package libtiff4:amd64 ErrorMessage: trying to overwrite shared '/usr/share/lintian/overrides/libtiff4', which is different from other instances of package libtiff4:amd64 InstallationDate: Installed on 2014-05-24 (384 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: tiff Title: package libtiff4 (not installed) failed to install/upgrade: trying to overwrite shared '/usr/share/lintian/overrides/libtiff4', which is different from other instances of package libtiff4:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1464735/+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 1880571] Re: PCI/internal sound card not detected on ubuntu focal
*** This bug is a duplicate of bug 1793640 *** https://bugs.launchpad.net/bugs/1793640 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: timidity (Ubuntu) Status: New => Confirmed -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in timidity package in Ubuntu: Confirmed Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1880571/+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 1902358] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429770/+files/UdevDb.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429765/+files/ProcCpuinfoMinimal.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429771/+files/acpidump.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429764/+files/ProcCpuinfo.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] SystemdDelta.txt
apport information ** Attachment added: "SystemdDelta.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429769/+files/SystemdDelta.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429759/+files/Lspci.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429762/+files/Lsusb-t.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429763/+files/Lsusb-v.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429768/+files/ProcModules.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429766/+files/ProcEnviron.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429767/+files/ProcInterrupts.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429761/+files/Lsusb.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429760/+files/Lspci-vt.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429758/+files/Dependencies.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. PowerEdge R730 NonfreeKernelModules: nvidia_modeset nvidia Package: systemd 245.4-4ubuntu3.2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.3 dmi.board.name: 0WCJNT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] Re: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline
apport information ** Tags added: apport-collected focal uec-images ** Description changed: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.10 + Architecture: amd64 + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-10-31 (0 days ago) + InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + MachineType: Dell Inc. PowerEdge R730 + NonfreeKernelModules: nvidia_modeset nvidia + Package: systemd 245.4-4ubuntu3.2 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=14d488b4-d8f0-4b48-8793-780af41edd93 ro + ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 + Tags: focal uec-images + Uname: Linux 5.4.0-52-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 01/17/2017 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.4.3 + dmi.board.name: 0WCJNT + dmi.board.vendor: Dell Inc. + dmi.board.version: A07 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.4.3:bd01/17/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0WCJNT:rvrA07:cvnDellInc.:ct23:cvr: + dmi.product.name: PowerEdge R730 + dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R730 + dmi.sys.vendor: Dell Inc. ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1902358/+attachment/5429757/+files/CurrentDmesg.txt -- 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/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-31 (0 days ago)
[Touch-packages] [Bug 1902358] Re: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline
** Package changed: linux (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1902358 Title: Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline Status in systemd package in Ubuntu: Incomplete Bug description: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902358/+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 1902358] [NEW] Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline
You have been subscribed to a public bug: IMO this is not related to Kubernetes so I filed the bug here. **What happened**: Processes in container can't connect to `kubernetes.default` service. **What you expected to happen**: It should be able to connect. **How to reproduce it (as minimally and precisely as possible)**: ```bash host# tc qdisc add dev eth0 root fq host# nsenter -n -t $(pidof some-process-in-container) container-net-ns# nc -vv 10.97.0.1 443 # Could not connect ``` **Anything else we need to know?**: ```bash host# tc qdisc add dev eth0 root noqueue # this works host# tc qdisc add dev eth0 root fq_codel # this works too ``` - `host` is where the workload container is, not Kubernetes master. - When the bug condition is met, packets won't be sent on wire. - kube-proxy works in IPVS mode. - The reason to tinker with qdisc is to enable TCP BBR, which requires fq qdisc. - fq qdisc works in `Linux node1 4.15.0-106-generic #107-Ubuntu SMP Thu Jun 4 11:27:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (Ubuntu 18.04)` **Environment**: - Cloud provider or hardware configuration: `NIC: Intel X520-DA1 (82599)` - OS (e.g: `cat /etc/os-release`): `Ubuntu 20.04.1 LTS \n \l` - Kernel (e.g. `uname -a`): `Linux Proton 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux` - Install tools: - Network plugin and version (if this is a network-related bug): `Calico v3.14.1 with IPIP & NAT-Outgoing` - Others: ** Affects: systemd (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic -- Kubernetes service connectivity issue Ubuntu 20.04 + fq queue discipline https://bugs.launchpad.net/bugs/1902358 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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 1902361] [NEW] Delete key inputs Unicode Delete character (007F) instead of deleting the next character
Public bug reported: When pressed, the delete key inputs the Unicode 007F character instead of deleting the following character. In most cases, this is difficult to see, but in a terminal, the 007F is clearly visible. The xev output for the key press is following: KeyPress event, serial 36, synthetic NO, window 0x421, root 0x5df, subw 0x0, time 81101326, (1403,948), root:(1453,1062), state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES, XLookupString gives 1 bytes: (7f) "" XmbLookupString gives 1 bytes: (7f) "" XFilterEvent returns: False KeyRelease event, serial 36, synthetic NO, window 0x421, root 0x5df, subw 0x0, time 81101443, (1403,948), root:(1453,1062), state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES, XLookupString gives 1 bytes: (7f) "" XFilterEvent returns: False This is a new fresh install of Ubuntu 20.04, I don't remember the delete key working at any point since the installation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 12:54:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 (Whiskey Lake) [1025:1312] InstallationDate: Installed on 2020-10-14 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Swift SF514-53T ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd04/25/2019:svnAcer:pnSwiftSF514-53T:pvrV1.09:rvnWL:rnCarlsberg_WL:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902361 Title: Delete key inputs Unicode Delete character (007F) instead of deleting the next character Status in xorg package in Ubuntu: New Bug description: When pressed, the delete key inputs the Unicode 007F character instead of deleting the following character. In most cases, this is difficult to see, but in a terminal, the 007F is clearly visible. The xev output for the key press is following: KeyPress event, serial 36, synthetic NO, window 0x421, root 0x5df, subw 0x0, time 81101326, (1403,948), root:(1453,1062), state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES, XLookupString gives 1 bytes: (7f) "" XmbLookupString gives 1 bytes: (7f) "" XFilterEvent returns: False KeyRelease event, serial 36, synthetic NO, window 0x421, root 0x5df, subw 0x0, time 81101443, (1403,948), root:(1453,1062), state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES, XLookupString gives 1 bytes: (7f) "" XFilterEvent returns: False This is a new fresh install of Ubuntu 20.04, I don't remember the delete key working at any point since the installation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugin
[Touch-packages] [Bug 1902352] [NEW] apt-get -u upgrade yields "-bash: /usr/bin/snap: No such file or directory"
Public bug reported: I'm running Kubuntu 20.04. To the best of my knowledge, I purged all snap-related packages, including snap itself. Now, every time I update my packages with `apt-get update && apt-get -u upgrade`, I get this output at the end: -bash: /usr/bin/snap: No such file or directory How can I get rid of this message? ** Affects: snap (Ubuntu) Importance: Undecided Status: New ** Package changed: pulseaudio (Ubuntu) => snap (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/1902352 Title: apt-get -u upgrade yields "-bash: /usr/bin/snap: No such file or directory" Status in snap package in Ubuntu: New Bug description: I'm running Kubuntu 20.04. To the best of my knowledge, I purged all snap-related packages, including snap itself. Now, every time I update my packages with `apt-get update && apt-get -u upgrade`, I get this output at the end: -bash: /usr/bin/snap: No such file or directory How can I get rid of this message? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1902352/+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 1902311] Re: GNU sha256(1) &tc --check (-c) output depends on order of --quiet and --warn
Thanks for taking your time to report this issue and help making Ubuntu better. I tried the simple example given in the description and got the same, somewhat unexpected result with coreutils 8.32-3ubuntu1 on Ubuntu 20.10. Thus marking confirmed. By the way, if you click the yellow pencil next to the title, you can update it :) ** Changed in: coreutils (Ubuntu) Status: New => Confirmed ** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1902311 Title: GNU sha256(1) &tc --check (-c) output depends on order of --quiet and --warn Status in coreutils package in Ubuntu: Confirmed Bug description: The output of GNU sha256sum --check (or -c), and related tools (i.e., sha1sum, sha224sum, sha384sum, and sha512sum) depends on the order of the --quiet and --warn options. This is counter-intuitive, not documented in the man(1) pages, and unnecessary. Simple example: 1$ date >/tmp/data 2$ sha256sum /tmp/data >/tmp/sums 3$ sha256sum -c --warn --quiet /tmp/sums# No output (expected) 4$ sha256sum -c --quiet --warn /tmp/sums# Unexpected "Ok"... /tmp/data: OK 5$ The manual page says (spurious lines omitted): The following five options are useful only when verifying checksums: --quiet don't print OK for each successfully verified file -w, --warnwarn about improperly formatted checksum lines There is no reason --warn should affect the operation of --quiet (nor visa-versa). The operations as documented are orthogonal. Attached is a bash(1) shell script written when puzzling over this inconsistent behaviour; it may be useful (use --help for a summary). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: coreutils 8.30-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Oct 30 21:34:31 2020 InstallationDate: Installed on 2020-10-19 (11 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1902311/+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 1786495] Re: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all
I have the same problem on Ubuntu 20.10. nic30 solution works for me. I have a Dell Precision M4800. -- 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/1786495 Title: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am head no sound from my headphone jack. Laptop speaker work fine. Tried 2 different headphones and still no sound. pavucontrol can see my headphone and I see the sound bar move but no sound comes out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: hhernandez 2083 F...m pulseaudio /dev/snd/controlC1: hhernandez 2083 F pulseaudio /dev/snd/controlC0: hhernandez 2083 F pulseaudio CurrentDesktop: MATE Date: Fri Aug 10 07:59:09 2018 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hhernandez 2083 F pulseaudio /dev/snd/controlC0: hhernandez 2083 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0V5GVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/19/2015:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0V5GVY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1786495/+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
