[Touch-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Also affects: linux (Ubuntu Impish) Importance: Low Status: Confirmed ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Hui Wang (hui.wang) -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) 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 Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
** Changed in: libx11 (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: libx11 (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: In Progress Status in libx11 source package in Focal: In Progress Status in libx11 source package in Groovy: Won't Fix Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+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 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Ubuntu 21.10 bug present. ** Tags added: impish ** Tags added: amd64 apport-bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1404172 Title: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Status in One Hundred Papercuts: Confirmed Status in Light Display Manager: Confirmed Status in systemd: New Status in lightdm package in Ubuntu: Confirmed Bug description: auth.log complaints: Dec 19 07:24:42 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 19 07:24:42 u32 lightdm: PAM adding faulty module: pam_kwallet.so Dec 19 07:24:42 u32 lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) Dec 19 07:24:42 u32 systemd-logind[656]: New session c1 of user lightdm. Dec 19 07:24:42 u32 systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0) Dec 19 07:24:46 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 19 07:24:46 u32 lightdm: PAM adding faulty module: pam_kwallet.so Dec 19 07:24:46 u32 lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "oem" Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm:session): session opened for user oem by (uid=0) As per lp:1309535 #18 comment such 'warnings' should be silenced (as they scared unawared users about the both needs of pam's gnome/kde) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0 Uname: Linux 3.18.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Fri Dec 19 10:47:07 2014 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1404172/+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 1938996] [NEW] pulseaudio-utils overwrites /usr/share/bash-completion/completions/pulseaudio which belongs to pulseaudio
Public bug reported: Unpacking pulseaudio-utils (1:15.0+dfsg1-1ubuntu1) over (1:14.2-2ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-fIyGyr/16-pulseaudio-utils_1%3a15.0+dfsg1-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/bash-completion/completions/pulseaudio', which is also in package pulseaudio 1:14.2-2ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amarao 5329 F pulseaudio /dev/snd/pcmC0D7p: amarao 5329 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Thu Aug 5 12:07:36 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-22 (1505 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: error while loading shared libraries: libpulsecommon-14.2.so: cannot open shared object file: No such file or directory RebootRequiredPkgs: libc6 libc6 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-06-03 (62 days ago) dmi.bios.date: 07/13/2020 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.2 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:br2.14:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. modified.conffile..etc.xdg.Xwayland-session.d.00-pulseaudio-x11: [deleted] ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1938996 Title: pulseaudio-utils overwrites /usr/share/bash- completion/completions/pulseaudio which belongs to pulseaudio Status in pulseaudio package in Ubuntu: New Bug description: Unpacking pulseaudio-utils (1:15.0+dfsg1-1ubuntu1) over (1:14.2-2ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-fIyGyr/16-pulseaudio-utils_1%3a15.0+dfsg1-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/bash-completion/completions/pulseaudio', which is also in package pulseaudio 1:14.2-2ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amarao 5329 F pulseaudio /dev/snd/pcmC0D7p: amarao 5329 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Thu Aug 5 12:07:36 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-22 (1505 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: error while loading shared libraries: libpulsecommon-14.2.so: cannot open shared object file: No such file or directory RebootRequiredPkgs: libc6 libc6 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-06-03 (62 days ago) dmi.bios.date: 07/13/2020 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.2 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:br2.14:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. modified.conffile..etc.xdg.Xwayland-session.d.00-pulseaudio-x11: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1938996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1938996] Re: pulseaudio-utils overwrites /usr/share/bash-completion/completions/pulseaudio which belongs to pulseaudio
*** This bug is a duplicate of bug 1938753 *** https://bugs.launchpad.net/bugs/1938753 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1938753, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1938753 package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist -- 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/1938996 Title: pulseaudio-utils overwrites /usr/share/bash- completion/completions/pulseaudio which belongs to pulseaudio Status in pulseaudio package in Ubuntu: New Bug description: Unpacking pulseaudio-utils (1:15.0+dfsg1-1ubuntu1) over (1:14.2-2ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-fIyGyr/16-pulseaudio-utils_1%3a15.0+dfsg1-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/bash-completion/completions/pulseaudio', which is also in package pulseaudio 1:14.2-2ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amarao 5329 F pulseaudio /dev/snd/pcmC0D7p: amarao 5329 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Thu Aug 5 12:07:36 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-22 (1505 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: error while loading shared libraries: libpulsecommon-14.2.so: cannot open shared object file: No such file or directory RebootRequiredPkgs: libc6 libc6 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-06-03 (62 days ago) dmi.bios.date: 07/13/2020 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.2 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:br2.14:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. modified.conffile..etc.xdg.Xwayland-session.d.00-pulseaudio-x11: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1938996/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
I am using netplan - default in bionic. I added the repo, made update and reboot. 'systemctl restart systemd-networkd' resulted with keepalived VIP lost. I added following file and rebooted: /etc/systemd/network/10-netplan-ens160.network : --- [Match] Name=ens160 [Network] KeepConfiguration=static --- Network did not come up after reboot. changed /etc/systemd/network/10-netplan-ens160.network and rebooted: --- [Match] Name=ens160 [Network] Address=10.1.1.233/29 Gateway=10.1.1.238 KeepConfiguration=static --- 'systemctl restart systemd-networkd' did not have any bad results - keepalived VIP remained as expected. Now I need to have IP and gateway in two files - /etc/netplan/01-netcfg.yaml and /etc/systemd/network/10-netplan- ens160.network Maanus -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Incomplete Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses o
[Touch-packages] [Bug 1939010] [NEW] Cannot manually switch to laptop speakers if headphones are plugged
Public bug reported: In a lot of scenari , one would like to plug its "one jack" headet to use the microphone , but would like to output sound to speakers Ubuntu 20.04 , kernel 5.11 , after plugging the headphone , it become the only option on the sound panel , laptop speakers are not available to be selected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem3009 F pulseaudio /dev/snd/pcmC0D0c: oem3009 F...m pulseaudio /dev/snd/pcmC0D0p: oem3009 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 5 12:55:31 2021 InstallationDate: Installed on 2021-04-29 (97 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2019 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL40_50CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd09/14/2019:br7.6:efr7.1:svnNotebook:pnNL40_50CU:pvrNotApplicable:rvnNotebook:rnNL40_50CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL40_50CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** 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/1939010 Title: Cannot manually switch to laptop speakers if headphones are plugged Status in alsa-driver package in Ubuntu: New Bug description: In a lot of scenari , one would like to plug its "one jack" headet to use the microphone , but would like to output sound to speakers Ubuntu 20.04 , kernel 5.11 , after plugging the headphone , it become the only option on the sound panel , laptop speakers are not available to be selected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem3009 F pulseaudio /dev/snd/pcmC0D0c: oem3009 F...m pulseaudio /dev/snd/pcmC0D0p: oem3009 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 5 12:55:31 2021 InstallationDate: Installed on 2021-04-29 (97 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2019 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL40_50CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd09/14/2019:br7.6:efr7.1:svnNotebook:pnNL40_50CU:pvrNotApplicable:rvnNotebook:rnNL40_50CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL40_50CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1939010/+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 1939013] [NEW] Xorg freezes in the lock screen
Public bug reported: When locking my screen, I often get the lock screen that freezes. I am able to move my mouse but I can't interact with anything on the screen. After "smashing" my keyboard (I press enter/space) sometimes the screen locks out and I can type my password to login into my system again. When I can't I have to reboot my system. This seems to have started a few weeks ago on hirsute hippo and unfortunately, I can't find a pattern to reproduce this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 5 13:22:57 2021 DistUpgraded: 2021-04-25 18:27:30,739 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1458:231b] InstallationDate: Installed on 2020-12-02 (245 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. B550 AORUS PRO AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=2bdda2d4-5abf-479e-9c59-d1a8cf5a01b9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to hirsute on 2021-04-25 (101 days ago) dmi.bios.date: 05/14/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS PRO AC dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd05/14/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSPROAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSPROAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B550 AORUS PRO AC dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze hirsute 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/1939013 Title: Xorg freezes in the lock screen Status in xorg package in Ubuntu: New Bug description: When locking my screen, I often get the lock screen that freezes. I am able to move my mouse but I can't interact with anything on the screen. After "smashing" my keyboard (I press enter/space) sometimes the screen locks out and I can type my password to login into my system again. When I can't I have to reboot my system. This seems to have started a few weeks ago on hirsute hippo and unfortunately, I can't find a pattern to reproduce this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 5 13:22:57 2021 DistUpgraded: 2021-04-25 18:27:30,739 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5)
[Touch-packages] [Bug 1939014] [NEW] date/time display issue on lock screen
Public bug reported: It seems the lock screen get sometimes some issues with the display of the date-time. This doesn't happen all the time so I managed to take a photo of the problem: https://assets.ubuntu.com/v1/06d2ef19-photo_2021-08-05_13-32-21.jpg ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 5 13:33:07 2021 DistUpgraded: 2021-04-25 18:27:30,739 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1458:231b] InstallationDate: Installed on 2020-12-02 (245 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. B550 AORUS PRO AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=2bdda2d4-5abf-479e-9c59-d1a8cf5a01b9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-25 (101 days ago) dmi.bios.date: 05/14/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS PRO AC dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd05/14/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSPROAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSPROAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B550 AORUS PRO AC dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1939014 Title: date/time display issue on lock screen Status in xorg package in Ubuntu: New Bug description: It seems the lock screen get sometimes some issues with the display of the date-time. This doesn't happen all the time so I managed to take a photo of the problem: https://assets.ubuntu.com/v1/06d2ef19-photo_2021-08-05_13-32-21.jpg ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 5 13:33:07 2021 DistUpgraded: 2021-04-25 18:27:30,739 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1458:231b] InstallationDate: Installed on 2020-12-02 (245 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. B550 AORUS PRO AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=2bdda2d4-5abf-479e-9c59-d1a8cf5a01b9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-25 (101 days ago) dmi.bios.date: 05/14/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default stri
[Touch-packages] [Bug 1939014] Re: date/time display issue on lock screen
** Package changed: xorg (Ubuntu) => xorg-server (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/1939014 Title: date/time display issue on lock screen Status in xorg-server package in Ubuntu: New Bug description: It seems the lock screen get sometimes some issues with the display of the date-time. This doesn't happen all the time so I managed to take a photo of the problem: https://assets.ubuntu.com/v1/06d2ef19-photo_2021-08-05_13-32-21.jpg ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 5 13:33:07 2021 DistUpgraded: 2021-04-25 18:27:30,739 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1458:231b] InstallationDate: Installed on 2020-12-02 (245 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. B550 AORUS PRO AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=2bdda2d4-5abf-479e-9c59-d1a8cf5a01b9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-25 (101 days ago) dmi.bios.date: 05/14/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS PRO AC dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd05/14/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSPROAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSPROAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B550 AORUS PRO AC dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1939014/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
Thanks @Maanus. So the outcome is positive here then. - Eric -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Incomplete Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses obfuscated) global_defs # Block id { notification_email { sysadm...@blah.com } notification_email_from keepali...@system3.hq.blah.com smtp_server 10.22.11.7 # IP smtp_connect_timeout 30 # integer, seconds router_id system3 # string identifying the machine, # (doesn't have to be hostname). vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18 vrrp_mcast_group6 ff02::12 # optional, default ff02::12 enable_traps # enable SNMP traps } vrrp_sync_group collection { group { wan
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
> Now I need to have IP and gateway in two files - /etc/netplan/01-netcfg.yaml > and > /etc/systemd/network/10-netplan-ens160.network to clarify, don't do that, you should create a systemd-networkd 'drop- in' instead of copying/modifying the file. For example, if the networkd config filename for your interface is '10-netplan-ens160.network' (regardless of which directory it's located in), you should create a new file '/etc/systemd/network/10-netplan- ens160.network.d/override.conf' with only the content you want to add/modify, specifically in this case: --- [Network] KeepConfiguration=static --- For more detail on systemd-networkd 'drop-in' files, see 'man systemd.network' in the first paragraph. -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Incomplete Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses obfuscated) global_defs # Block id {
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
Good catch Dan. Maanus could you repeat the testing with what Dan brought up ? -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Incomplete Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses obfuscated) global_defs # Block id { notification_email { sysadm...@blah.com } notification_email_from keepali...@system3.hq.blah.com smtp_server 10.22.11.7 # IP smtp_connect_timeout 30 # integer, seconds router_id system3 # string identifying the machine, # (doesn't have to be hostname). vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18 vrrp_mcast_group6 ff02::12 # optional, default ff02::12 enable_traps # enable SNMP traps } vrrp_sync_group collection { group {
[Touch-packages] [Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange
Hi Niklas, Thanks for putting in the effort into finding a reproducer for the reported issue. I could indeed reproduce the issue you have been experiencing. I am attaching a couple scripts to aid others to reproduce the bug (this includes a README file with further instructions). Interestingly, if you swap the preferred authentications order to read PreferredAuthentications=gssapi-keyex,gssapi-with-mic The bug will not manifest itself. Next, I will verify if other branches at https://github.com/openssh- gsskex/openssh-gsskex are also affected. If this is the case, we should report the issue there. ** Attachment added: "reproducer.tar.gz" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1938144/+attachment/5516128/+files/reproducer.tar.gz ** Changed in: openssh (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1938144 Title: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange Status in openssh package in Ubuntu: Triaged Bug description: I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and server) with the option "GSSAPIKeyExchange=yes", and this causes the connection to fail. The server has GSSAPI (Kerberos authentication) enabled, but is is only used for non-root users (root uses SSH keys). Client command: ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@server -v -p -o GSSAPIKeyExchange=yes Client log: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /home/user/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to compute-test [130.75.80.46] port . debug1: Connection established. debug1: identity file /home/rother/.ssh/id_rsa type 0 debug1: identity file /home/rother/.ssh/id_rsa-cert type -1 debug1: identity file /home/rother/.ssh/id_dsa type -1 debug1: identity file /home/rother/.ssh/id_dsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa type -1 debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519 type -1 debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_xmss type -1 debug1: identity file /home/rother/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400 debug1: Authenticating to server: as 'root' debug1: Offering GSSAPI proposal: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q== debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g== debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: Doing group exchange debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Received GSSAPI_COMPLETE debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Rekey has happened - updating saved versions debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent debug1: Will attempt key: /home/user/.ssh/id_dsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/user/.ssh/id_ed25519 debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk debug1: Will attempt key: /home/user/.ssh/id_xmss debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi
[Touch-packages] [Bug 1938588] Re: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata
** Tags added: fr-1551 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938588 Title: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata Status in ubuntu-meta package in Ubuntu: New Bug description: We have several factory-fresh Mitac industrial motherboards (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that we are unable to install Ubuntu Server 18.04.5 on. When we boot from the installation media we get the following error and the installation hangs (see attached screenshot, I've transcribed the error below too) ``` [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later) [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-241) ``` Googling the microcode bug, the normal advice appears to be "boot into an older, functioning kernel, update the `intel-microcode` package, and then reboot." But in this situation there is no older kernel to boot into; there is no OS installed _at all_ on these boards yet. I'm booting from a USB drive loaded with the latest version of Ubuntu Server 18.04. The only work-around I've found that works so far is to install Ubuntu Desktop 18.04, which can boot successfully on these boards, perform the minimal desktop installation, then use the desktop install to update the `intel-microcode` package, reboot, and then finally install Ubuntu Server. This is obviously not convenient needing to install a complete desktop OS just so I can update the microcode, and then immediately wiping it to install what I wanted in the first place. I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because these motherboards are being installed into robots that will be running ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have Noetic support yet). I have tried the following to modify the Ubuntu Server ISO, without success: 1- Adding the microcode to initrd --- I unpacked the contents of the Ubuntu Server ISO, decompressed install/initrd.gz, and used the bash script here https://www.kernel.org/doc/html/latest/x86/microcode.html to add the intel-microcode firmware to the image. Then I recompressed initrd.gz, and rebuild the ISO using xorisso. This did not have any effect: Ubuntu Server still encountered the same error when trying to install. 2- Using initrd from Ubuntu Desktop 18.04.5 -- I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz that Ubuntu Server normally uses). Then I rebuilt the Ubuntu Server with xorisso again. The resulted in the system booting, but immediately dropping into an initramfs busybox shell, saying boot files were missing. I assume this is because Ubuntu Server uses the `boot=casper` flag in order to boot into the live desktop session. At this point I'm running out of ideas for how to be able to make Ubuntu Server's installation media work with these boards. Ubuntu Desktop has no problem booting on them, so it's obviously something specific to the Ubuntu Server image, but I'm not sure exactly what or how to fix it. If you need any additional information/logs/etc... please let me know and I'll be happy to provide them. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1938588/+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 1938588] Re: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata
** Also affects: ubuntu-meta (Ubuntu Focal) Importance: Undecided Status: New ** Tags removed: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938588 Title: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Focal: New Bug description: We have several factory-fresh Mitac industrial motherboards (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that we are unable to install Ubuntu Server 18.04.5 on. When we boot from the installation media we get the following error and the installation hangs (see attached screenshot, I've transcribed the error below too) ``` [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later) [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-241) ``` Googling the microcode bug, the normal advice appears to be "boot into an older, functioning kernel, update the `intel-microcode` package, and then reboot." But in this situation there is no older kernel to boot into; there is no OS installed _at all_ on these boards yet. I'm booting from a USB drive loaded with the latest version of Ubuntu Server 18.04. The only work-around I've found that works so far is to install Ubuntu Desktop 18.04, which can boot successfully on these boards, perform the minimal desktop installation, then use the desktop install to update the `intel-microcode` package, reboot, and then finally install Ubuntu Server. This is obviously not convenient needing to install a complete desktop OS just so I can update the microcode, and then immediately wiping it to install what I wanted in the first place. I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because these motherboards are being installed into robots that will be running ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have Noetic support yet). I have tried the following to modify the Ubuntu Server ISO, without success: 1- Adding the microcode to initrd --- I unpacked the contents of the Ubuntu Server ISO, decompressed install/initrd.gz, and used the bash script here https://www.kernel.org/doc/html/latest/x86/microcode.html to add the intel-microcode firmware to the image. Then I recompressed initrd.gz, and rebuild the ISO using xorisso. This did not have any effect: Ubuntu Server still encountered the same error when trying to install. 2- Using initrd from Ubuntu Desktop 18.04.5 -- I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz that Ubuntu Server normally uses). Then I rebuilt the Ubuntu Server with xorisso again. The resulted in the system booting, but immediately dropping into an initramfs busybox shell, saying boot files were missing. I assume this is because Ubuntu Server uses the `boot=casper` flag in order to boot into the live desktop session. At this point I'm running out of ideas for how to be able to make Ubuntu Server's installation media work with these boards. Ubuntu Desktop has no problem booting on them, so it's obviously something specific to the Ubuntu Server image, but I'm not sure exactly what or how to fix it. If you need any additional information/logs/etc... please let me know and I'll be happy to provide them. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1938588/+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 1938588] Re: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata
We are looking at updating the server iso for the 20.04.3 point release which is coming up in a couple of weeks. However, there are no further point releases of 18.04 (and subsequently new isos) scheduled so this is unlikely to be fixed for that release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938588 Title: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Focal: New Bug description: We have several factory-fresh Mitac industrial motherboards (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that we are unable to install Ubuntu Server 18.04.5 on. When we boot from the installation media we get the following error and the installation hangs (see attached screenshot, I've transcribed the error below too) ``` [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later) [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-241) ``` Googling the microcode bug, the normal advice appears to be "boot into an older, functioning kernel, update the `intel-microcode` package, and then reboot." But in this situation there is no older kernel to boot into; there is no OS installed _at all_ on these boards yet. I'm booting from a USB drive loaded with the latest version of Ubuntu Server 18.04. The only work-around I've found that works so far is to install Ubuntu Desktop 18.04, which can boot successfully on these boards, perform the minimal desktop installation, then use the desktop install to update the `intel-microcode` package, reboot, and then finally install Ubuntu Server. This is obviously not convenient needing to install a complete desktop OS just so I can update the microcode, and then immediately wiping it to install what I wanted in the first place. I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because these motherboards are being installed into robots that will be running ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have Noetic support yet). I have tried the following to modify the Ubuntu Server ISO, without success: 1- Adding the microcode to initrd --- I unpacked the contents of the Ubuntu Server ISO, decompressed install/initrd.gz, and used the bash script here https://www.kernel.org/doc/html/latest/x86/microcode.html to add the intel-microcode firmware to the image. Then I recompressed initrd.gz, and rebuild the ISO using xorisso. This did not have any effect: Ubuntu Server still encountered the same error when trying to install. 2- Using initrd from Ubuntu Desktop 18.04.5 -- I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz that Ubuntu Server normally uses). Then I rebuilt the Ubuntu Server with xorisso again. The resulted in the system booting, but immediately dropping into an initramfs busybox shell, saying boot files were missing. I assume this is because Ubuntu Server uses the `boot=casper` flag in order to boot into the live desktop session. At this point I'm running out of ideas for how to be able to make Ubuntu Server's installation media work with these boards. Ubuntu Desktop has no problem booting on them, so it's obviously something specific to the Ubuntu Server image, but I'm not sure exactly what or how to fix it. If you need any additional information/logs/etc... please let me know and I'll be happy to provide them. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1938588/+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 1938588] Re: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata
That's disappointing, but understandable. Is there any chance you could provide me with a link to a guide to explain how I could edit the ISO on my own to make a custom ISO for these boards? I've already got some customized preseed files anyway, so making further modifications to the base Ubuntu Server image isn't a big deal. I just don't know what the exact process for adding the microcode would be. My previous efforts using the example script from https://www.kernel.org/doc/html/latest/x86/microcode.html to add the microcode to initrd weren't successful. But I'm not even sure if that's the correct process, or if there's an easier/better way to do it. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938588 Title: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Focal: New Bug description: We have several factory-fresh Mitac industrial motherboards (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that we are unable to install Ubuntu Server 18.04.5 on. When we boot from the installation media we get the following error and the installation hangs (see attached screenshot, I've transcribed the error below too) ``` [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later) [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-241) ``` Googling the microcode bug, the normal advice appears to be "boot into an older, functioning kernel, update the `intel-microcode` package, and then reboot." But in this situation there is no older kernel to boot into; there is no OS installed _at all_ on these boards yet. I'm booting from a USB drive loaded with the latest version of Ubuntu Server 18.04. The only work-around I've found that works so far is to install Ubuntu Desktop 18.04, which can boot successfully on these boards, perform the minimal desktop installation, then use the desktop install to update the `intel-microcode` package, reboot, and then finally install Ubuntu Server. This is obviously not convenient needing to install a complete desktop OS just so I can update the microcode, and then immediately wiping it to install what I wanted in the first place. I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because these motherboards are being installed into robots that will be running ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have Noetic support yet). I have tried the following to modify the Ubuntu Server ISO, without success: 1- Adding the microcode to initrd --- I unpacked the contents of the Ubuntu Server ISO, decompressed install/initrd.gz, and used the bash script here https://www.kernel.org/doc/html/latest/x86/microcode.html to add the intel-microcode firmware to the image. Then I recompressed initrd.gz, and rebuild the ISO using xorisso. This did not have any effect: Ubuntu Server still encountered the same error when trying to install. 2- Using initrd from Ubuntu Desktop 18.04.5 -- I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz that Ubuntu Server normally uses). Then I rebuilt the Ubuntu Server with xorisso again. The resulted in the system booting, but immediately dropping into an initramfs busybox shell, saying boot files were missing. I assume this is because Ubuntu Server uses the `boot=casper` flag in order to boot into the live desktop session. At this point I'm running out of ideas for how to be able to make Ubuntu Server's installation media work with these boards. Ubuntu Desktop has no problem booting on them, so it's obviously something specific to the Ubuntu Server image, but I'm not sure exactly what or how to fix it. If you need any additional information/logs/etc... please let me know and I'll be happy to provide them. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1938588/+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 1938886] Re: rrr:no dh_strip or strip loose setuid bit
This bug was fixed in the package debhelper - 13.3.4ubuntu2 --- debhelper (13.3.4ubuntu2) impish; urgency=medium * objcopy/strip changed in 2.36.1, not keeping file attributes of the original file. Work around that in dh_strip to write to a temporary file, copying attributes, cat'ing this to the original file, copying attributes again to keep the original attributes. LP: #1938886 -- Dimitri John Ledkov Wed, 04 Aug 2021 19:23:25 +0100 ** Changed in: debhelper (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1938886 Title: rrr:no dh_strip or strip loose setuid bit Status in bash package in Ubuntu: Invalid Status in binutils package in Ubuntu: New Status in dash package in Ubuntu: Invalid Status in debhelper package in Ubuntu: Fix Released Status in debugedit package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: New Bug description: Over at https://launchpadlibrarian.net/550715513/buildlog_ubuntu- hirsute-amd64.virtualbox_6.1.22-dfsg-2~ubuntu1.21.04.2_BUILDING.txt.gz I have rebuilt an earlier version of virtualbox, that sets Rules- Requires-Root: no and added extra ls statements to find where/when/why setuid bits are getting lost after fixperms. make[1]: Leaving directory '/<>' debian/rules override_dh_strip make[1]: Entering directory '/<>' ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL -rwsr-sr-x 1 buildd buildd 406808 Jul 29 14:34 debian/virtualbox/usr/lib/virtualbox/VBoxSDL ... dh_strip --dbgsym-migration='virtualbox-dbg' debugedit: debian/virtualbox/usr/lib/virtualbox/VBoxSDL.so: Unknown DWARF DW_FORM_0x1f20 a7cf3c43c8b18c3261d2d4737a475bf730ad1554 ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL -rwxr-xr-x 1 buildd buildd 166208 Jul 29 14:35 debian/virtualbox/usr/lib/virtualbox/VBoxSDL It seems to me that either dh_strip or something it calls (strip, debugedit) looses the setuid permission in hirsute and up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1938886/+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 1939065] [NEW] autopkgtest failure in 0002-benchmark test
Public bug reported: >From https://launchpad.net/ubuntu/+source/dbus-cpp/5.0.3-2, it looks like the build failed on all architectures except armhf, and on armhf there was a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/d/dbus-cpp/20210708_173150_9b648@/log.gz autopkgtest [17:31:26]: test 0002-benchmark: [--- DBus daemon: unix:abstract=/tmp/dbus-r1vtLBVT2b,guid=9e9dc7c56358b39bba3cf32260e73670 (dbus-test-runner:1285): libdbustest-WARNING **: 17:31:28.819: Unable to start process '/usr/lib/*/dbus-cpp/examples/benchmark/benchmark': Failed to execute child process ?/usr/lib/*/dbus-cpp/examples/benchmark/benchmark? (No such file or directory) task-0: Shutting down DBus daemon: Shutdown autopkgtest [17:31:29]: test 0002-benchmark: ---] 0002-benchmark FAIL non-zero exit status 253 Debian is seeing the same test failures in their CI framework: https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dbus-cpp/14056784/log.gz https://ci.debian.net/data/autopkgtest/unstable/arm64/d/dbus-cpp/14058472/log.gz ** Affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1939065 Title: autopkgtest failure in 0002-benchmark test Status in dbus-cpp package in Ubuntu: New Bug description: From https://launchpad.net/ubuntu/+source/dbus-cpp/5.0.3-2, it looks like the build failed on all architectures except armhf, and on armhf there was a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/d/dbus-cpp/20210708_173150_9b648@/log.gz autopkgtest [17:31:26]: test 0002-benchmark: [--- DBus daemon: unix:abstract=/tmp/dbus-r1vtLBVT2b,guid=9e9dc7c56358b39bba3cf32260e73670 (dbus-test-runner:1285): libdbustest-WARNING **: 17:31:28.819: Unable to start process '/usr/lib/*/dbus-cpp/examples/benchmark/benchmark': Failed to execute child process ?/usr/lib/*/dbus-cpp/examples/benchmark/benchmark? (No such file or directory) task-0: Shutting down DBus daemon: Shutdown autopkgtest [17:31:29]: test 0002-benchmark: ---] 0002-benchmark FAIL non-zero exit status 253 Debian is seeing the same test failures in their CI framework: https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dbus-cpp/14056784/log.gz https://ci.debian.net/data/autopkgtest/unstable/arm64/d/dbus-cpp/14058472/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1939065/+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 1939067] [NEW] FTBFS 5.0.3-2 due to missing symbols
Public bug reported: Most architectures are failing to build 5.0.3-2. I've reproduced failure locally: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libdbus-cpp5/DEBIAN/symbols doesn't match completely debian/libdbus-cpp5.symbols --- debian/libdbus-cpp5.symbols (libdbus-cpp5_5.0.3-2_amd64) +++ dpkg-gensymbolse5FPkP 2021-08-05 21:54:51.508307074 + @@ -218,10 +218,10 @@ _ZTSZN4core4dbus7Fixture7Private6SystemC4ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcUlSB_SB_E_@Base 5.0.1 _ZTSZN4core4dbus7Fixture7Private7SessionC4ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcUlSB_SB_E_@Base 5.0.1 _ZTSZN4core4dbus7Message7PrivateC4EP11DBusMessagebEUlS4_E_@Base 5.0.1 - _ZTVN4core4dbus3Bus6Errors12AlreadyOwnedE@Base 5.0.1 - _ZTVN4core4dbus3Bus6Errors12AlreadyOwnerE@Base 5.0.1 - _ZTVN4core4dbus3Bus6Errors8NoMemoryE@Base 5.0.1 - _ZTVN4core4dbus5types10ObjectPath6Errors37InvalidObjectPathStringRepresentationE@Base 5.0.1 +#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors12AlreadyOwnedE@Base 5.0.1 +#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors12AlreadyOwnerE@Base 5.0.1 +#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors8NoMemoryE@Base 5.0.1 +#MISSING: 5.0.3-2# _ZTVN4core4dbus5types10ObjectPath6Errors37InvalidObjectPathStringRepresentationE@Base 5.0.1 _ZTVN4core4dbus7FixtureE@Base 5.0.1 _ZZN4core4dbus4DBus21GetConnectionUnixUser4nameB5cxx11EvE1s@Base 5.0.1 _ZZN4core4dbus4DBus26GetConnectionUnixProcessID4nameB5cxx11EvE1s@Base 5.0.1 mv debian/.debhelper/generated/libdbus-cpp5/triggers.new debian/.debhelper/generated/libdbus-cpp5/triggers rm -f debian/dbus-cpp-bin/DEBIAN/shlibs rm -f debian/libdbus-cpp-dev/DEBIAN/shlibs rm -f debian/dbus-cpp-dev-examples/DEBIAN/shlibs dh_makeshlibs: error: failing due to earlier errors make: *** [debian/rules:16: binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 blame: ./dbus-cpp_5.0.3-2.dsc badpkg: rules build failed with exit code 2 autopkgtest [21:54:51]: ERROR: erroneous package: rules build failed with exit code 2 --- This release includes this modification to the symbols file: diff --git a/debian/libdbus-cpp5.symbols b/debian/libdbus-cpp5.symbols index d96a2d8..f84a0c5 100644 --- a/debian/libdbus-cpp5.symbols +++ b/debian/libdbus-cpp5.symbols @@ -1,5 +1,6 @@ # SymbolsHelper-Confirmed: 5.0.1 amd64 armel armhf i386 m68k mipsel x32 libdbus-cpp.so.5 libdbus-cpp5 #MINVER# +* Build-Depends-Package: libdbus-cpp-dev _ZN4core4dbus14ServiceWatcherC1ESt10shared_ptrINS0_6ObjectEERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN$ _ZN4core4dbus14ServiceWatcherC2ESt10shared_ptrINS0_6ObjectEERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN$ _ZN4core4dbus3Bus12remove_matchERKNS0_9MatchRuleE@Base 5.0.1 However, reverting this change has no effect; the build still fails the same way. ** Affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuses -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1939067 Title: FTBFS 5.0.3-2 due to missing symbols Status in dbus-cpp package in Ubuntu: New Bug description: Most architectures are failing to build 5.0.3-2. I've reproduced failure locally: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libdbus-cpp5/DEBIAN/symbols doesn't match completely debian/libdbus-cpp5.symbols --- debian/libdbus-cpp5.symbols (libdbus-cpp5_5.0.3-2_amd64) +++ dpkg-gensymbolse5FPkP 2021-08-05 21:54:51.508307074 + @@ -218,10 +218,10 @@ _ZTSZN4core4dbus7Fixture7Private6SystemC4ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcUlSB_SB_E_@Base 5.0.1 _ZTSZN4core4dbus7Fixture7Private7SessionC4ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcUlSB_SB_E_@Base 5.0.1 _ZTSZN4core4dbus7Message7PrivateC4EP11DBusMessagebEUlS4_E_@Base 5.0.1 - _ZTVN4core4dbus3Bus6Errors12AlreadyOwnedE@Base 5.0.1 - _ZTVN4core4dbus3Bus6Errors12AlreadyOwnerE@Base 5.0.1 - _ZTVN4core4dbus3Bus6Errors8NoMemoryE@Base 5.0.1 - _ZTVN4core4dbus5types10ObjectPath6Errors37InvalidObjectPathStringRepresentationE@Base 5.0.1 +#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors12AlreadyOwnedE@Base 5.0.1 +#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors12AlreadyOwnerE@Base 5.0.1 +#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors8NoMemoryE@Base 5.0.1 +#MISSING: 5.0.3-2# _ZTVN4core4dbus5types10ObjectPath6Errors37InvalidObjectPathStringRepresentationE@Base 5.0.1 _ZTVN4core4dbus7FixtureE@Base 5.0.1 _ZZN4core4dbus4DBus21GetConnectionUnixUser4nameB5cxx11EvE1s@Base 5.0.1 _ZZN4core4dbus4DBus26GetConnectionUnixProcessID4nameB5cxx11EvE1s@Base 5.0.1 mv debian/.debhelper/generated/libdb
[Touch-packages] [Bug 1939065] Re: autopkgtest failure in 0002-benchmark test
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1939065 Title: autopkgtest failure in 0002-benchmark test Status in dbus-cpp package in Ubuntu: New Bug description: From https://launchpad.net/ubuntu/+source/dbus-cpp/5.0.3-2, it looks like the build failed on all architectures except armhf, and on armhf there was a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/d/dbus-cpp/20210708_173150_9b648@/log.gz autopkgtest [17:31:26]: test 0002-benchmark: [--- DBus daemon: unix:abstract=/tmp/dbus-r1vtLBVT2b,guid=9e9dc7c56358b39bba3cf32260e73670 (dbus-test-runner:1285): libdbustest-WARNING **: 17:31:28.819: Unable to start process '/usr/lib/*/dbus-cpp/examples/benchmark/benchmark': Failed to execute child process ?/usr/lib/*/dbus-cpp/examples/benchmark/benchmark? (No such file or directory) task-0: Shutting down DBus daemon: Shutdown autopkgtest [17:31:29]: test 0002-benchmark: ---] 0002-benchmark FAIL non-zero exit status 253 Debian is seeing the same test failures in their CI framework: https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dbus-cpp/14056784/log.gz https://ci.debian.net/data/autopkgtest/unstable/arm64/d/dbus-cpp/14058472/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1939065/+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 1938753] Re: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, welches auch in Pa
** Tags added: rls-ii-incoming ** Changed in: pulseaudio (Ubuntu) Milestone: None => ubuntu-21.10 -- 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/1938753 Title: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist Status in pulseaudio package in Ubuntu: Confirmed Bug description: Just tried to install updates, then the error reporting popped up. ProblemType: Package DistroRelease: Ubuntu 21.10 Package: pulseaudio-utils 1:14.2-2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lucl 2483 F pulseaudio CasperMD5CheckResult: pass Date: Tue Aug 3 08:12:26 2021 ErrorMessage: Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist InstallationDate: Installed on 2021-08-02 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210801) PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: error while loading shared libraries: libpulsecommon-14.2.so: cannot open shared object file: No such file or directory Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.6 SourcePackage: pulseaudio Title: package pulseaudio-utils 1:14.2-2ubuntu2 failed to install/upgrade: Versuch, »/usr/share/bash-completion/completions/pulseaudio« zu überschreiben, welches auch in Paket pulseaudio 1:14.2-2ubuntu2 ist UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1938753/+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 1939073] [NEW] [USB-Audio - Saffire 6 USB, playback] Sound is distorted and high-pitched
You have been subscribed to a public bug: Probably after an upgrade of kernel to 5.11.0-25-generic from 5.8.0-50-generic which worked well in this regard, sound in the Focusrite card started to be high-pitched and distorted. When I use the normal audio output, the sound is correct. Further debug info can be found here: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/696837 This is from the times when I accidentally upgraded to a newer unofficial kernel and the same bug occurred to me. It seems that now an official kernel with this bug has been submitted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 1363 F pulseaudio /dev/snd/controlC2: michal 1363 F pulseaudio /dev/snd/controlC1: michal 1363 F pulseaudio /dev/snd/pcmC1D0p: michal 1363 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 01:50:14 2021 InstallationDate: Installed on 2021-06-16 (50 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: TU104 HD Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [USB-Audio - Saffire 6 USB, playback] Sound is distorted and high-pitched https://bugs.launchpad.net/bugs/1939073 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 1939073] Re: [USB-Audio - Saffire 6 USB, playback] Sound is distorted and high-pitched
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1939073 Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted and high- pitched Status in alsa-driver package in Ubuntu: New Bug description: Probably after an upgrade of kernel to 5.11.0-25-generic from 5.8.0-50-generic which worked well in this regard, sound in the Focusrite card started to be high-pitched and distorted. When I use the normal audio output, the sound is correct. Further debug info can be found here: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/696837 This is from the times when I accidentally upgraded to a newer unofficial kernel and the same bug occurred to me. It seems that now an official kernel with this bug has been submitted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 1363 F pulseaudio /dev/snd/controlC2: michal 1363 F pulseaudio /dev/snd/controlC1: michal 1363 F pulseaudio /dev/snd/pcmC1D0p: michal 1363 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 01:50:14 2021 InstallationDate: Installed on 2021-06-16 (50 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: TU104 HD Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1939073/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
It happened to me too ** Attachment added: "Crash log of amdgpu driver" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+attachment/5516220/+files/amdgu_crash.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+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 1939013] Re: Xorg freezes in the lock screen
If you can still move the mouse then Xorg hasn't crashed, but gnome- shell has. Next time the problem happens, please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. 5. Also follow these instructions to report any recent crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freezes in the lock screen + Screen freezes in the lock screen ** Tags added: amdgpu -- 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/1939013 Title: Screen freezes in the lock screen Status in Ubuntu: Incomplete Bug description: When locking my screen, I often get the lock screen that freezes. I am able to move my mouse but I can't interact with anything on the screen. After "smashing" my keyboard (I press enter/space) sometimes the screen locks out and I can type my password to login into my system again. When I can't I have to reboot my system. This seems to have started a few weeks ago on hirsute hippo and unfortunately, I can't find a pattern to reproduce this issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 5 13:22:57 2021 DistUpgraded: 2021-04-25 18:27:30,739 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1458:231b] InstallationDate: Installed on 2020-12-02 (245 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. B550 AORUS PRO AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=2bdda2d4-5abf-479e-9c59-d1a8cf5a01b9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to hirsute on 2021-04-25 (101 days ago) dmi.bios.date: 05/14/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS PRO AC dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd05/14/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSPROAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSPROAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B550 AORUS PRO AC dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1939013/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
The "default bionic install" uses only netplan yaml and /etc/systemd/network/ is empty. If I switch to systemd.network style, I have to create config files from scratch anyway and then this KeepConfiguration helps. (Of course I do not need to keep the netplan yaml after enabling systemd-networkd, my remark for having the IP configuration in two files was wrong) Using '/etc/systemd/network/10-netplan-ens160.network.d/override.conf' with KeepConfiguration works perfectly the same. -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Incomplete Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses obfuscated) global_defs # Block id { notification_email { sysadm...@blah.com } notification_email_from keepali...@system3.hq.blah.com smtp_server 10.22.11.7 # IP smtp_connect_timeout 30 # integer, seconds