[Touch-packages] [Bug 1896361] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1
bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1896361 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1 Status in lvm2 package in Ubuntu: New Bug description: bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: vboxnetflt vboxdrv ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 20 02:40:56 2020 ErrorMessage: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-09-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1896361/+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 1896361] [NEW] package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1
Public bug reported: bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: vboxnetflt vboxdrv ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 20 02:40:56 2020 ErrorMessage: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-09-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1896361 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1 Status in lvm2 package in Ubuntu: New Bug description: bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: vboxnetflt vboxdrv ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 20 02:40:56 2020 ErrorMessage: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-09-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote lvm2, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1896361/+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 1896333] Re: "Select an audio" menu when user have not even inserted headphone jack.
"collect the log, when problem happens" When problem happens, I have to select the one of the audio option and log in. And then only I can take the log by using terminal. Does this type log record what I have expirenced a moment ago!? -- 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/1896333 Title: "Select an audio" menu when user have not even inserted headphone jack. Status in pulseaudio package in Ubuntu: New Bug description: GNOME 3.36.3 | Ubuntu 20.04.1 It has been a month and I have been experiencing this weird behavior. Earphone option like this 3 while unlocking the laptop as if I have inserted earphones. Some details this issue: I have to wait like 10 min or so after the lock of the screen. This will trigger something and when I open the lid or touch mouse pad to unlock, I get earphone options to chooose in the screen as if I have inserted headphone jack. Something is wrong. I want to know why. This didn't used to happen a month ago. I waited a month to report this issue thinking it will get resolved in upcoming updates but sadly no changes so far. I think some Ubuntu's GNOME update might have something to do this. This is my wild guess. But very certain about it. Let me know. Although the issue might seems really small issue but very annoying to go throw this EVERYDAY. I would love to know what is causing this? When its fixed? Is there something wrong on my side? Note: This happens ONLY when I try to unlock the screen after like >10 min or so. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pranav 3554 F pulseaudio /dev/snd/controlC0: pranav 3554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 20:54:36 2020 InstallationDate: Installed on 2020-02-16 (216 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-08 (134 days ago) dmi.bios.date: 05/28/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896333/+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 1886826] Re: high packet loss on 18.04 with systemd
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1886826 Title: high packet loss on 18.04 with systemd Status in systemd package in Ubuntu: Expired Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 systemctl --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid Our issue is that we have a k8s (1.18, kube-router CNI) cluster comprised of a number of Ubuntu 16.04 nodes, we are in the process of upgrading the nodes to Ubuntu 18.04 - however after upgrading the first node and adding it back to the cluster we observed high packet loss from other cluster nodes to the 18.04 node as well as ping error messages when running a continuous ping from the 18.04 node to another node in the cluster, eg: 64 bytes from 10.8.11.1: icmp_seq=91 ttl=64 time=0.088 ms 64 bytes from 10.8.11.1: icmp_seq=92 ttl=64 time=0.076 ms ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available Another observation is that one of our daemonset pods (promtail) could not start. After many days of troubleshooting various possibilities, changing network cable, NIC, trying a different server, checking/changing various sysctl values, I eventually tried switching from systemd- networkd to NetworkManager as the backend via netplan config. After rebooting the server with NetworkManager in place and re-adding the node back to the k8s cluster, the packet loss disappeared as did the ping errors and the daemonset pod (promtail) also started normally. I would like to use Ubuntu's default of systemd-networkd to handle our NIC/route config - but cannot until I've figured out what in systemd- networkd is breaking. Any help is much appreciated on this matter. Thanks! Luke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886826/+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 1887655] Re: unattended-upgrades triggers reboot despite configuration
[Expired for unattended-upgrades (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1887655 Title: unattended-upgrades triggers reboot despite configuration Status in unattended-upgrades package in Ubuntu: Expired Bug description: I've been having problems with my Ubuntu machine suddenly rebooting without any warning. To my knowledge Ubuntu Desktop is not supposed to reboot without warning by default. I believe this is being triggered by unattended-upgrades unattended-upgrades 2.3 (amd64) Ubuntu Desktop: Description: Ubuntu 20.04 LTS Release: 20.04 One pattern that emerges is that the reboot happens right after unattended-upgrades completes successfully. There are multiple examples in my /var/log/syslog, but all show "unattended- upgrades.service: Succeeded." the same second everything begins to shut down, with nothing for a minute or two prior. Example: Jul 15 11:17:01 pc systemd[2065]: Starting Notification regarding a new release of Ubuntu... Jul 15 11:17:14 pc charon: 08[IKE] sending keep alive to 10.10.10.10[4500] Jul 15 11:17:22 pc check-new-release-gtk[71843]: /usr/lib/ubuntu-release-upgrader/check-new-release-gtk:30: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk' , '3.0') before import to ensure that the right version gets loaded. Jul 15 11:17:22 pc check-new-release-gtk[71843]: from gi.repository import Gtk Jul 15 11:17:22 pc check-new-release-gtk[71843]: WARNING:root:timeout reached, exiting Jul 15 11:17:22 pc systemd[2065]: update-notifier-release.service: Succeeded. Jul 15 11:17:22 pc systemd[2065]: Finished Notification regarding a new release of Ubuntu. Jul 15 11:17:48 pc mysql-workbench[33350]: gtk_tree_view_unref_tree_helper: assertion 'node != NULL' failed Jul 15 11:17:54 pc charon: 09[IKE] sending keep alive to 10.10.10.10[4500] Jul 15 11:18:03 pc systemd[1]: unattended-upgrades.service: Succeeded. Jul 15 11:18:03 pc systemd[1]: Stopping Session 3 of user philip. Jul 15 11:18:03 pc systemd[1]: Removed slice system-clean\x2dmount\x2dpoint.slice. Jul 15 11:18:03 pc systemd[1]: Removed slice system-getty.slice. Jul 15 11:18:03 pc systemd[1]: Removed slice system-modprobe.slice. Jul 15 11:18:03 pc systemd[1]: Stopped target Block Device Preparation for /dev/mapper/ubuntu. Jul 15 11:18:03 pc systemd[2065]: Stopped target GNOME Wayland Session (session: gnome). From memory I've never edited the contents of /etc/apt/apt.conf.d/ and the configuration for unattended upgrades claims to be default (NOT to reboot): $ grep -irnC4 reboot /etc/apt/apt.conf.d/ /etc/apt/apt.conf.d/50unattended-upgrades-88-// Do automatic removal of unused packages after the upgrade /etc/apt/apt.conf.d/50unattended-upgrades-89-// (equivalent to apt-get autoremove) /etc/apt/apt.conf.d/50unattended-upgrades-90-//Unattended-Upgrade::Remove-Unused-Dependencies "false"; /etc/apt/apt.conf.d/50unattended-upgrades-91- /etc/apt/apt.conf.d/50unattended-upgrades:92:// Automatically reboot *WITHOUT CONFIRMATION* if /etc/apt/apt.conf.d/50unattended-upgrades:93:// the file /var/run/reboot-required is found after the upgrade /etc/apt/apt.conf.d/50unattended-upgrades:94://Unattended-Upgrade::Automatic-Reboot "false"; /etc/apt/apt.conf.d/50unattended-upgrades-95- /etc/apt/apt.conf.d/50unattended-upgrades:96:// Automatically reboot even if there are users currently logged in /etc/apt/apt.conf.d/50unattended-upgrades:97:// when Unattended-Upgrade::Automatic-Reboot is set to true /etc/apt/apt.conf.d/50unattended-upgrades:98://Unattended-Upgrade::Automatic-Reboot-WithUsers "true"; /etc/apt/apt.conf.d/50unattended-upgrades-99- /etc/apt/apt.conf.d/50unattended-upgrades:100:// If automatic reboot is enabled and needed, reboot at the specific /etc/apt/apt.conf.d/50unattended-upgrades-101-// time instead of immediately /etc/apt/apt.conf.d/50unattended-upgrades-102-// Default: "now" /etc/apt/apt.conf.d/50unattended-upgrades:103://Unattended-Upgrade::Automatic-Reboot-Time "02:00"; /etc/apt/apt.conf.d/50unattended-upgrades-104- /etc/apt/apt.conf.d/50unattended-upgrades-105-// Use apt bandwidth limit feature, this example limits the download /etc/apt/apt.conf.d/50unattended-upgrades-106-// speed to 70kb/sec /etc/apt/apt.conf.d/50unattended-upgrades-107-//Acquire::http::Dl-Limit "70"; journalctl -u unattended-upgrades Jul 10 07:52:31 PC systemd[1]: Started Unattended Upgrades Shutdown. Jul 14 10:03:03 PC systemd[1]: unattended-upgrades.service: Succeeded. -- Reboot -- Jul 14 10:04:11 PC systemd[1]: Started Unattended Upgrades Shutdown. Jul 15 11:18:03 PC systemd[1]: un
[Touch-packages] [Bug 1896333] Re: "Select an audio" menu when user have not even inserted headphone jack.
I guess when problem happens, the alsa driver gets a fake plugging in event. Please help collect the log: when problem happens, run 'pa-info > pa-info.txt' and upload the pa- info.txt. -- 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/1896333 Title: "Select an audio" menu when user have not even inserted headphone jack. Status in pulseaudio package in Ubuntu: New Bug description: GNOME 3.36.3 | Ubuntu 20.04.1 It has been a month and I have been experiencing this weird behavior. Earphone option like this 3 while unlocking the laptop as if I have inserted earphones. Some details this issue: I have to wait like 10 min or so after the lock of the screen. This will trigger something and when I open the lid or touch mouse pad to unlock, I get earphone options to chooose in the screen as if I have inserted headphone jack. Something is wrong. I want to know why. This didn't used to happen a month ago. I waited a month to report this issue thinking it will get resolved in upcoming updates but sadly no changes so far. I think some Ubuntu's GNOME update might have something to do this. This is my wild guess. But very certain about it. Let me know. Although the issue might seems really small issue but very annoying to go throw this EVERYDAY. I would love to know what is causing this? When its fixed? Is there something wrong on my side? Note: This happens ONLY when I try to unlock the screen after like >10 min or so. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pranav 3554 F pulseaudio /dev/snd/controlC0: pranav 3554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 20:54:36 2020 InstallationDate: Installed on 2020-02-16 (216 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-08 (134 days ago) dmi.bios.date: 05/28/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896333/+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 1896349] Re: PCI/internal sound card not detected
** 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/1896349 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 I can select my default audio hardware When I test it, doesn't work. When watching a Youtube video, for example, audio doesn't work as well. Thru the command lspci, this shows up: 00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03) 00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB Controller (rev 03) 00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30) 00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Management Engine Interface (rev 30) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 30) 00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #5 (rev 30) 00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 (rev 30) 00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30) 00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30) 00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30) 00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound Technology Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI Controller (rev 30) 01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 (rev 03) 04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 19:24:38 2020 InstallationDate: Installed on 2020-09-19 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875C dmi.board.vendor: HP dmi.board.version: 10.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd02/13/2020:svnHP:pnHPENVYLaptop17m-cg0xxx:pvrType1ProductConfigId:rvnHP:rn875C:rvr10.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 17m-cg0xxx dmi.product.sku: 9XM78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896349/+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 1896349] [NEW] PCI/internal sound card not detected
You have been subscribed to a public bug: Description:Ubuntu 20.04.1 LTS Release:20.04 I can select my default audio hardware When I test it, doesn't work. When watching a Youtube video, for example, audio doesn't work as well. Thru the command lspci, this shows up: 00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03) 00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB Controller (rev 03) 00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30) 00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Management Engine Interface (rev 30) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 30) 00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #5 (rev 30) 00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 (rev 30) 00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30) 00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30) 00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30) 00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound Technology Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI Controller (rev 30) 01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 (rev 03) 04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 19:24:38 2020 InstallationDate: Installed on 2020-09-19 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875C dmi.board.vendor: HP dmi.board.version: 10.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd02/13/2020:svnHP:pnHPENVYLaptop17m-cg0xxx:pvrType1ProductConfigId:rvnHP:rn875C:rvr10.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 17m-cg0xxx dmi.product.sku: 9XM78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- PCI/internal sound card not detected https://bugs.launchpad.net/bugs/1896349 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 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)
Awesome, that worked for me too! Thanks! -- 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/1895422 Title: Sound card not detected on Dell Latitude 9510 (Realtek ALC711) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am running Ubuntu 20.04.01 LTS, kernel version 5.6.0-1027-oem (checked via uname -r). I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics-cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en-us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
>From what I can gather this is not a function of the headset or Bluetooth device, but it's a function of firmware differences in the host side Bluetooth adapters. For example, I have a Sony WH-1000MX3. I have a USB dongle adapter that does not work in the HSP/HFP mode. When selecting the mode the active profile throws various errors then returns to the "off" PulseAudio/ALSA profile. lsusb on the CSR USB dongle. ``` Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize064 idVendor 0x0a12 Cambridge Silicon Radio, Ltd idProduct 0x0001 Bluetooth Dongle (HCI mode) bcdDevice 88.91 iManufacturer 0 iProduct2 iSerial 0 bNumConfigurations 1 ``` I also have an Intel Bluetooth/WiFi 802.11ac card (Bluetooth is on the USB bus), that does support the HSP/HFP mode, abet with noticeably reduced audio quality. I think there is a separate bug in launchpad tracking the audio quality issues of that mode though. header for `lsusb -v` on the Intel card. ``` Bus 001 Device 005: ID 8087:07dc Intel Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize064 idVendor 0x8087 Intel Corp. idProduct 0x07dc bcdDevice0.01 iManufacturer 0 iProduct0 iSerial 0 bNumConfigurations 1 ``` lspci on the intel card ``` 04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 Flags: bus master, fast devsel, latency 0, IRQ 96 Memory at f760 (64-bit, non-prefetchable) [size=8K] Capabilities: Kernel driver in use: iwlwifi Kernel modules: iwlwifi ``` -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1846334] Re: cupsd assert failure: free(): invalid pointer
This happens to me too. The printer reports on the display a low toner warning right after switch on and after every finished print job. My printer: Samsung C1860FW This is also reported on https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=961345. ** Bug watch added: Debian Bug tracker #961345 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961345 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1846334 Title: cupsd assert failure: free(): invalid pointer Status in cups package in Ubuntu: Confirmed Bug description: Just running in the background, no user action (printing) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: free(): invalid pointer Date: Tue Oct 1 19:41:35 2019 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-09 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: letter PpdFiles: HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at malloc.c:5332 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+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 1896333] [NEW] "Select an audio" menu when user have not even inserted headphone jack.
Public bug reported: GNOME 3.36.3 | Ubuntu 20.04.1 It has been a month and I have been experiencing this weird behavior. Earphone option like this 3 while unlocking the laptop as if I have inserted earphones. Some details this issue: I have to wait like 10 min or so after the lock of the screen. This will trigger something and when I open the lid or touch mouse pad to unlock, I get earphone options to chooose in the screen as if I have inserted headphone jack. Something is wrong. I want to know why. This didn't used to happen a month ago. I waited a month to report this issue thinking it will get resolved in upcoming updates but sadly no changes so far. I think some Ubuntu's GNOME update might have something to do this. This is my wild guess. But very certain about it. Let me know. Although the issue might seems really small issue but very annoying to go throw this EVERYDAY. I would love to know what is causing this? When its fixed? Is there something wrong on my side? Note: This happens ONLY when I try to unlock the screen after like >10 min or so. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pranav 3554 F pulseaudio /dev/snd/controlC0: pranav 3554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 20:54:36 2020 InstallationDate: Installed on 2020-02-16 (216 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-08 (134 days ago) dmi.bios.date: 05/28/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Attachment added: "Screenshot of getting "Select an audio" option in locked screen state." https://bugs.launchpad.net/bugs/1896333/+attachment/5412437/+files/Screenshot%20from%202020-09-19%2013-47-59.png -- 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/1896333 Title: "Select an audio" menu when user have not even inserted headphone jack. Status in pulseaudio package in Ubuntu: New Bug description: GNOME 3.36.3 | Ubuntu 20.04.1 It has been a month and I have been experiencing this weird behavior. Earphone option like this 3 while unlocking the laptop as if I have inserted earphones. Some details this issue: I have to wait like 10 min or so after the lock of the screen. This will trigger something and when I open the lid or touch mouse pad to unlock, I get earphone options to chooose in the screen as if I have inserted headphone jack. Something is wrong. I want to know why. This didn't used to happen a month ago. I waited a month to report this issue thinking it will get resolved in upcoming updates but sadly no changes so far. I think some Ubuntu's GNOME update might have something to do this. This is my wild guess. But very certain about it. Let me know. Although the issue might seems really small issue but very annoying to go throw this EVERYDAY. I would love to know what is causing this? When its fixed? Is there something wrong on my side? Note: This happens ONLY when I try to unlock the screen after like >10 min or so. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pranav 3554 F pulseaudio /dev/snd/controlC0: pranav 3554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 20:54:36 2020 InstallationDate: Installed on 2020-02-16 (216 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-08 (134 days ago) dmi.bios.date: 05/28/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor:
[Touch-packages] [Bug 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)
I have fixed following this: https://www.reddit.com/r/Dell/comments/husu3r/how_to_get_fully_working_audio_in_ubuntu_2004_on/ -- 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/1895422 Title: Sound card not detected on Dell Latitude 9510 (Realtek ALC711) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am running Ubuntu 20.04.01 LTS, kernel version 5.6.0-1027-oem (checked via uname -r). I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics-cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en-us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1279344] Re: A significant grammar error/unclear wording is used in an error pop-up.
The message is unchanged in gdebi 0.9.5.7+nmu3 on Ubuntu Groovy. ** Tags added: bionic focal groovy xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1279344 Title: A significant grammar error/unclear wording is used in an error pop- up. Status in Linux Mint: New Status in gdebi package in Ubuntu: Confirmed Bug description: The pop-up in question is: gdebi-gtk "Only one software management tool is allowed to run at the same time." This should clearly be changed to: "Only one software management tool is allowed to run at a time." OR "Multiple software management tools cannot be run at the same time." 1) Version: Linux Mint 16, 64-bit 2) Reproduce pop-up by manually launching a package installer while another is running. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1279344/+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 1712433] Re: man page typo
Looks like the upstream fix was included in the newer version of mount which is available in Ubuntu 18.04. The typo is now gone from http://manpages.ubuntu.com/manpages/bionic/en/man8/mount.8.html ** Changed in: util-linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1712433 Title: man page typo Status in util-linux package in Ubuntu: Fix Released Bug description: man mount contains the following section: Note that mount is very strict about non-root users and all paths specified on command line are verified before fstab is parsed or a helper program is executed. It's strogly recommended to use a valid mountpoint to specify filesystem, other‐ wise mount may fail. For example it's bad idea to use NFS or CIFS source on command line. The word 'strogly' should be 'strongly' ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: mount 2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Wed Aug 23 07:48:32 2017 InstallationDate: Installed on 2017-03-23 (152 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) SourcePackage: util-linux UpgradeStatus: Upgraded to zesty on 2017-08-13 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1712433/+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 1895370] Re: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit
But it does not what you say dpkg -l | grep libip4tc2 ii libip4tc2:amd641.8.4-3ubuntu2 It does not explain why a fully functioning system suddenly stop working after upgrade. Also the lib you mentioned is installed. And you don't care about what I reported. The package libgnutls30 if get upgraded then causing errors. After that day I run apt update ; apt upgrade again and it wont ask me to upgrade libgnutls30 anymore. Do you really carer about the information I typed or just ignore it by thinking the way you think rather than based on facts? Possibly someone at ubuntu fix the dependencies about the lib libgnutls30 which no no longer get upgraded. Or something incorrect about the package metadata. For whatever it takes, it is not the simple reason you noted and change the status `Not completed` I don't think the ignorant behavior is good here. regards -- 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/1895370 Title: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit Status in systemd package in Ubuntu: Incomplete Bug description: Last run apt update and apt upgrade and reboot render my system unbootable because systemd failed with message: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit So I tried to reset to the previous state and re-run the update and after the re-run update I try to run the systemd command and having the same result. root@work ~# apt update; apt upgrade Get:1 http://au.archive.ubuntu.com/ubuntu focal InRelease [265 kB] Get:2 http://au.archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB] Get:3 http://au.archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Get:4 http://ppa.launchpad.net/audio-recorder/ppa/ubuntu focal InRelease [15.9 kB] Get:5 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB] Get:6 http://dl.google.com/linux/chrome/deb stable InRelease [1,811 B] Get:7 http://au.archive.ubuntu.com/ubuntu focal/main amd64 Packages [970 kB] Get:9 http://au.archive.ubuntu.com/ubuntu focal/main i386 Packages [718 kB] Get:10 http://au.archive.ubuntu.com/ubuntu focal/main Translation-en_AU [1,836 B] Get:11 http://au.archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB] Get:12 https://packages.microsoft.com/repos/ms-teams stable InRelease [17.5 kB] Get:13 http://au.archive.ubuntu.com/ubuntu focal/main amd64 DEP-11 Metadata [494 kB] Get:14 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 48x48 Icons [98.4 kB] Get:15 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 64x64 Icons [163 kB] Get:16 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 64x64@2 Icons [15.8 kB] Get:17 https://packages.microsoft.com/repos/ms-teams stable/main amd64 Packages [6,403 B] Get:18 http://au.archive.ubuntu.com/ubuntu focal/main amd64 c-n-f Metadata [29.5 kB] Get:19 http://au.archive.ubuntu.com/ubuntu focal/restricted i386 Packages [8,112 B] Ign:20 http://ppa.launchpad.net/hermlnx/dislocker/ubuntu focal InRelease Get:21 http://au.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [22.0 kB] Get:22 http://au.archive.ubuntu.com/ubuntu focal/restricted Translation-en_AU [1,144 B] Get:23 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1,163 B]
[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 I have the same issue. My Bose 700 connect and have sound output for A2DP, but nothing when trying to select HSP/HFP. Laptop: HP Spectre X360 2019 OS: Ubuntu 20.04.01 LTS Kernel: 5.4.0-47-generic Headset: Bose 700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1544251] Re: mount ignores exec option for 'users' mounts
same bug in 18.04LTS, it seems -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1544251 Title: mount ignores exec option for 'users' mounts Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Trusty: New Bug description: The version of 'mount' included in Ubuntu 14.04 LTS and 12.04 LTS has a bug wherein the 'exec' option in /etc/fstab is ignored on mounts with the 'user' or 'users' options when they are mounted by root. For example: $ grep 48tb2d /etc/fstab labdisk.site.com:/Public4 /mnt/lab_48tb2d nfs users,exec,nosuid 0 0 $ sudo mount /mnt/lab_48tb2d $ mount | grep 48tb2d labdisk.site.com:/Public4 on /mnt/lab_48tb2d type nfs (rw,nosuid,nodev,noexec,addr=172.16.222.158) $ umount /mnt/lab_48tb2d $ mount /mnt/lab_48tb2d $ mount | grep 48tb2d labdisk.site.com:/Public4 on /mnt/lab_48tb2d type nfs (rw,nosuid,nodev,addr=172.16.222.158) This bug was fixed upstream several years ago and I believe therefore doesn't affect 15.10, but seems not to have made it into the current LTS releases of ubuntu. https://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/mount/mount.c?id=a4c0cc75ff9744299f108c259efab1bd30c8007a https://bugzilla.redhat.com/show_bug.cgi?id=769636 System info: Ubuntu 14.04.3 LTS, util-linux 2.20.1-5.1ubuntu20.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1544251/+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