[Touch-packages] [Bug 1899745] Re: [SRU] alsa-utils: let alsactl support _boot section defined in ucm
Finish verification on CID: 202010-28346 kernel version: 5.6.0-1032-oem BIOS version: 0.5.9 verify step: 1. add proposed channel 2. $ sudo apt install alsa-utils 3. Check alsa-utils version is 1.2.2-1ubuntu2 4. $ sudo rm /var/lib/alsa/asound.state 5. $ sudo sh -c 'echo b > /proc/sysrq-trigger' After reboot, check if the ucm init.conf has been applied successfully. The BootSequence in ucm config are applied successfully. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1899745 Title: [SRU] alsa-utils: let alsactl support _boot section defined in ucm Status in HWE Next: New Status in alsa-utils package in Ubuntu: Fix Released Status in alsa-utils source package in Focal: Fix Committed Bug description: This patchset was backported from mainline alsa-utils 1.2.3, and groovy already integrated alsa-utils 1.2.3, there is no need to SRU this patchset to groovy, so only for focal. [Impact] We enabled 2 Dell soundwire audio machines, these machines depend on ucm to make the audio work, and in the ucm, the _boot section defined some amixers values for the 1st booting, these amixer values should be set to audio driver at the 1st booting, otherwise the whole audio doesn't work. [Fix] Backport some patches from mainline v1.2.3, these patches make the alsactl support _boot section in the ucm, then the systemd will call alsactl init after booting, the alsactl init will setting all amixers defined in the _boot section of ucm. [Test Case] On the Dell soundwire audio machines, After booting up, run 'amixer contents | less' to check all amixer values defined in the _boot section of ucm, all values read from driver are same as the ones in the ucm, test speaker/microphone/headset, all work well. [Regression Risk] This could introduce failure on runing 'alsactl init' for some machines, then the amixers will not be initialized correctly, users will experience all audio can't work like speaker doesn't output sound or microphone can't record sound. But this regression possibility is very low, since We have tested it both on soundwire machines and non-soundwire machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899745/+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 1246981] Re: Bluetooth devices fail to re-connect after sleep.
Like I mentioned, the kernel drivers seem fine. It appears to be a userspace software regression, either in bluez or in the gnome components that call bluez. the adaptor seems dead after resuming from sleep, until the gnome bluetooth settings panel is opened. this must call some sort of refresh function, and then everything works fine again. whatever this function is, it must've been called after resume previously in 20.04, and isn't being called now in 20.10, hence the regression. i don't know anything about bluez or the gnome internals, but i'm happy to provide whatever logs would be helpful in identifying the root cause and getting it fixed, since it's making my current desktop usage a nightmare. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth devices fail to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1898869] Re: System slow on booting
Could you provide journal log from the last boot? journalctl -b 0 should do the trick -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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
@Hui, Here's my device: Bus 003 Device 004: ID 8087:0026 Intel Corp. Marco. -- 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 1901295] Re: python3-chardet breaks install of python-chardet
PS: just to be clear: what I really mean is that, if python3-chardet was split into a "python3-chardet" (with only the module), and a "chardet" package (with only the binaries / manpage), it would then be possible for a third party to provide a "python-chardet" without the binaries / manpages that would also depend on "chardet". The new "python-chardet" (for python2) would of course not need to be maintained into Debian. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-chardet in Ubuntu. https://bugs.launchpad.net/bugs/1901295 Title: python3-chardet breaks install of python-chardet Status in python3-chardet package in Ubuntu: Confirmed Bug description: I'm trying to install python-chardet (for python-2.7), but it fails because latest python3-chardet breaks python-chardet. I fail to understand why the python3 version of chardet would break the python2.7 version of the same module. PS: I know that python2.7 is not supported anymore, but I have an application that depends on it, and I need to install it, and that's now impossible because of this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-chardet/+bug/1901295/+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 1901295] Re: python3-chardet breaks install of python-chardet
I analyzed the two packages and I think I found the reason why they break each other: both contain /usr/bin/chardet and /usr/bin/chardetect (as well as the associated man pages). So, a possible solution could be remove those two binaries, and their man pages from both python-chardet and python3-chardet, and create a new package "chardet" on which both would depend. Of course, this is just a suggestion, and I'm pretty sure the package maintainer is well aware of the situation and has his own reasons not to split the packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-chardet in Ubuntu. https://bugs.launchpad.net/bugs/1901295 Title: python3-chardet breaks install of python-chardet Status in python3-chardet package in Ubuntu: Confirmed Bug description: I'm trying to install python-chardet (for python-2.7), but it fails because latest python3-chardet breaks python-chardet. I fail to understand why the python3 version of chardet would break the python2.7 version of the same module. PS: I know that python2.7 is not supported anymore, but I have an application that depends on it, and I need to install it, and that's now impossible because of this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-chardet/+bug/1901295/+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 1901808] Re: Laptop displays has lags and tearing
** Summary changed: - no acceleration on Intel HD 4400 + Laptop displays has lags and tearing -- 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/1901808 Title: Laptop displays has lags and tearing Status in xorg package in Ubuntu: New Bug description: I have laptop dell with intel i5-4100U, intel hd 4400 and geforce 820m on board. I added zotac gtx 960 and one monitor via rizer. gtx and monitor worked correctly. but laptop displays has lags and tearing. I tried install i915 i965-va-drivers intel config section Section "Device" Identifier "Device1" Driver "intel" VendorName "Intel Corporation" Option "TearFree" "true" Option "DRI" "2" EndSection ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.32.00 Wed Oct 14 22:46:18 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Deepin Date: Wed Oct 28 11:03:01 2020 DistUpgraded: 2020-08-20 21:43:47,424 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0652] NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] [19da:2378] Subsystem: Dell GeForce 820M [1028:0652] InstallationDate: Installed on 2020-07-16 (103 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-52-generic root=UUID=ab9e3a31-2ad4-4c5f-a786-92ff7dbde56d ro rootflags=subvol=@ nouveau.modeset=0 DEEPIN_GFXMODE= crashkernel=512M-:192M SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-08-20 (68 days ago) dmi.bios.date: 03/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0926J6 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd03/28/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0926J6:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.sku: 0652 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1901808/+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 1901808] Re: Laptop displays has lags and tearing
*** This bug is a duplicate of bug 1853094 *** https://bugs.launchpad.net/bugs/1853094 If you are using the modeset driver and have HDMI connected and that HDMI port is connected to the Intel GPU then this is bug 1853094. If you are using the old intel driver you can avoid that by using 'TearFree' but your XorgLogOld.txt shows TearFree was still disabled. If you experience tearing in fullscreen windows on the laptop screen, then this is bug 1754284. If you experience tearing in accelerated windows powered by the Nvidia GPU then this is bug 1881909. It's unclear which of those bugs this is, but it seems likely it's already covered by those. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** This bug has been marked a duplicate of bug 1853094 [modeset] Screen tearing when using multiple monitors -- 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/1901808 Title: Laptop displays has lags and tearing Status in xorg-server package in Ubuntu: New Bug description: I have laptop dell with intel i5-4100U, intel hd 4400 and geforce 820m on board. I added zotac gtx 960 and one monitor via rizer. gtx and monitor worked correctly. but laptop displays has lags and tearing. I tried install i915 i965-va-drivers intel config section Section "Device" Identifier "Device1" Driver "intel" VendorName "Intel Corporation" Option "TearFree" "true" Option "DRI" "2" EndSection ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.32.00 Wed Oct 14 22:46:18 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Deepin Date: Wed Oct 28 11:03:01 2020 DistUpgraded: 2020-08-20 21:43:47,424 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0652] NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] [19da:2378] Subsystem: Dell GeForce 820M [1028:0652] InstallationDate: Installed on 2020-07-16 (103 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-52-generic root=UUID=ab9e3a31-2ad4-4c5f-a786-92ff7dbde56d ro rootflags=subvol=@ nouveau.modeset=0 DEEPIN_GFXMODE= crashkernel=512M-:192M SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-08-20 (68 days ago) dmi.bios.date: 03/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0926J6 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd03/28/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0926J6:rvrA01:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.sku: 0652 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xse
[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Hi all, throwing in my experience: Sony WH-H910N, ThinkPad P1 Gen 2, Bus 001 Device 007: ID 8087:0029 Intel Corp. Worked under 18.04 When upgraded to 20.04 rcX (before it was released), still kept working. Not much later - already on released 20.04 - with a fw/kernel/whatever upgrade it stopped working in HSP/HFP mode. Since there were errors in dmesg related to the FW loading, I downloaded upstream FW from git, put them under /lib/firmware, and added a dpkg-diversion for the package provided versions, so that it survives an upgrade: dpkg-divert --list | grep ibt local diversion of /lib/firmware/intel/ibt-20-1-3.sfi to /lib/firmware/intel/ibt-20-1-3.sfi.dist local diversion of /lib/firmware/intel/ibt-20-1-3.ddc to /lib/firmware/intel/ibt-20-1-3.ddc.dist Headphones Sony WH-H910N do work out of the box on a different system with the same distro - with BT HW 8087:0a2a. -- 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 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]
Re #14 and #15: I have installed both of the mentioned packages. But I also suffer from the crashing behaviour. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872106 Title: isc-dhcp-server crashing constantly [Ubuntu 20.04] Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Focal: Confirmed Bug description: isc-dhcp-server crashing constantly (sometimes within seconds or minutes, sometimes within hours) with the following error messages: Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service. Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ?? Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ?? Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ?? Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ?? Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ?? Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+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 1897744] Re: VerifyHostKeyDNS not working due to missing trust-ad flag
Hello Brian, I installed version 245.4-4ubuntu3.3 from focal-proposed on my focal systems, did some restarts, checked the content of the /etc/resolv.conf (trust-ad was always present). Connection to servers using sshfp is working without authenticity question except those servers without sshfp key in DNS. So everything works as it is supposed to. Thanks a lot and I have changed the tag for focal. Daniel ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1897744 Title: VerifyHostKeyDNS not working due to missing trust-ad flag Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] without trust-ad resolv.conf option, glibc will strip AD from systemd- resolved responses. one thing this will prevent working is ssh VerifyHostKeyDNS [test case] see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1898590/comments/7 [regression potential] regressions would likely involve DNS lookup failures, probably if DNSSEC is enabled but possibly even without, and likely when the application requesting the dns lookup processes the response AD. [scope] this is needed only in focal. glibc first stripped the AD in version 2.31, so this is not needed in bionic or earlier. this was added upstream in commit a742f9828ea which was included in v246, so this is fixed already in groovy. [original description] Hi, 1) Description: Ubuntu 20.04.1 LTS Release: 20.04 2) systemd:245.4-4ubuntu3.2 3) I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp. 4) I still get the security question Matching host key fingerprint found in DNS. Are you sure you want to continue connecting (yes/no/[fingerprint])? The issue is known and fixed in systemd v246. https://github.com/systemd/systemd/pull/16072 Best regards Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897744/+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
@Marco, I just have a lenovo laptop with the usb bluetooth module 8087:0026, I will test if it could work on my laptop. @Istvan, Yes, most of this kind of issues are in the bluetooth firmware or kernel driver, and nearly has nothing to do with pulseaudio. -- 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 1901828] [NEW] upgrade modifies /etc/default/grub inappropriately
Public bug reported: If I have: GRUB_CMDLINE_LINUX="nomodeset" in /etc/default/grub, boot hangs with "Failed to start Light Display Manager". No problem, I delete the line and run update-grub. However, running apt upgrade sometimes appends the line GRUB_CMDLINE_LINUX="nomodeset" to /etc/default/grub, resulting in a failed boot after upgrade. I am sure it is appending the line to the file because the rest of the file is unchanged. This has been happening occasionally for a long time. Most recently, it happened when I used do-release-upgrade to go from 18.04 to 20.04 I guess some package thinks it is a good idea to add this option, but I don't know which one, or how to stop it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 16:51:45 2020 InstallationDate: Installed on 2017-06-29 (1217 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-10-24 (4 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1901828 Title: upgrade modifies /etc/default/grub inappropriately Status in apt package in Ubuntu: New Bug description: If I have: GRUB_CMDLINE_LINUX="nomodeset" in /etc/default/grub, boot hangs with "Failed to start Light Display Manager". No problem, I delete the line and run update-grub. However, running apt upgrade sometimes appends the line GRUB_CMDLINE_LINUX="nomodeset" to /etc/default/grub, resulting in a failed boot after upgrade. I am sure it is appending the line to the file because the rest of the file is unchanged. This has been happening occasionally for a long time. Most recently, it happened when I used do-release-upgrade to go from 18.04 to 20.04 I guess some package thinks it is a good idea to add this option, but I don't know which one, or how to stop it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 16:51:45 2020 InstallationDate: Installed on 2017-06-29 (1217 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-10-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1901828/+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 1824260] Re: wrong kerning in SS-5 PDF form fields
Thank you. I have done as you suggest. Upstream merge request is here: https://gitlab.freedesktop.org/fontconfig/fontconfig/-/merge_requests/128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1824260 Title: wrong kerning in SS-5 PDF form fields Status in Fontconfig: Unknown Status in Poppler: New Status in fontconfig package in Ubuntu: In Progress Bug description: What I expected to happen: I am filling out the SS-5 Social Security Administration form (see attached). I entered "John Jacob Smith" into the "First", "Full Middle Name", and "Last" fields on page 5. What happened instead: I can enter the text without issue, but some of the letters are wrongly positioned, i.e. the kerning is wrong. For example, the letter "i" overlaps with the letter "m" in "Smith" (see attached image). It looks like the font in the fields might be displaying a variable width font when it is supposed to be a fixed-wdith font. Discussion: Since this bug is also present in xpdf and Okular (but not mupdf), I'm guessing this isn't a bug in Evince itself. However, I am reporting it here as a courtesy to other users (since Evince is the default PDF reader) and because I'm not sure which dependency is responsible. (I'm also not sure if it's a direct dependency problem or if it's something else like a font configuration issue.) Here is the output for pdffonts ss-5.pdf: name type encoding emb sub uni object ID - --- --- --- - IHPIKC+ArialMT CID TrueType Identity-H yes yes yes824 0 ArialMT TrueType WinAnsi no no no 826 0 Arial-BoldMT TrueType WinAnsi no no no 828 0 CourierStd Type 1WinAnsi no no no 145 0 HelveticaType 1WinAnsi no no no 197 0 MyriadPro-RegularType 1WinAnsi no no no 198 0 ZapfDingbats Type 1ZapfDingbats no no no 199 0 I asked about this in an Ask Ubuntu question nearly a year ago, but received no response, so I am reporting a bug now instead: https://askubuntu.com/questions/1031235/wrong-letter-positioning-and- font-in-pdf-form Ubuntu version: Description: Ubuntu 18.04.2 LTS Release: 18.04 evince version: $ apt-cache policy evince evince: Installed: 3.28.4-0ubuntu1 Candidate: 3.28.4-0ubuntu1 Version table: *** 3.28.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 10 21:27:11 2019 InstallationDate: Installed on 2018-12-12 (119 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/1824260/+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 1900727] Re: Update ca-certificates with latest NSS roots
This bug was fixed in the package ca-certificates - 20201027ubuntu0.20.10.1 --- ca-certificates (20201027ubuntu0.20.10.1) groovy-security; urgency=medium * mozilla/{certdata.txt,nssckbi.h}: Update Mozilla certificate authority bundle to version 2.44. (LP: #1900727) The following certificate authorities were added (+): + "Microsoft ECC Root Certificate Authority 2017" + "Microsoft RSA Root Certificate Authority 2017" + "e-Szigno Root CA 2017" + "certSIGN Root CA G2" + "Trustwave Global Certification Authority" + "Trustwave Global ECC P256 Certification Authority" + "Trustwave Global ECC P384 Certification Authority" The following certificate authorities were removed (-): - "Verisign Class 3 Public Primary Certification Authority - G3" - "Taiwan GRCA" - "Staat der Nederlanden Root CA - G2" - "EE Certification Centre Root CA" - "LuxTrust Global Root 2" - "OISTE WISeKey Global Root GA CA" -- Marc Deslauriers Tue, 27 Oct 2020 07:37:00 -0400 ** Changed in: ca-certificates (Ubuntu) Status: New => Fix Released ** Changed in: ca-certificates (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1900727 Title: Update ca-certificates with latest NSS roots Status in ca-certificates package in Ubuntu: Fix Released Bug description: Please refresh the default ca-certificates package with the latest NSS roots? Specifically, we would like to ensure these two roots from NSS 3.54 (26 June 2020) are included in the package: Bug 1641716 - Microsoft ECC Root Certificate Authority 2017 SHA-256 Fingerprint: 358DF39D764AF9E1B766E9C972DF352EE15CFAC227AF6AD1D70E8E4A6EDCBA02 Bug 1641716 - Microsoft RSA Root Certificate Authority 2017 SHA-256 Fingerprint: C741F70F4B2A8D88BF2E71C14122EF53EF10EBA0CFA5E64CFA20F418853073E0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1900727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1897440] Re: Since ~Sep 25 updates HDMI Digital Out disappeared, Headphones stop working
Problem self-healed after upgrading to Ubuntu 20.10 . -- 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/1897440 Title: Since ~Sep 25 updates HDMI Digital Out disappeared, Headphones stop working Status in alsa-driver package in Ubuntu: New Bug description: For last couple of months I've been using 20.04 sound OK on my Dell laptop but since last apt update/upgrade two strange things happened: 1. the HDMI Out sound device completely disappeared and I can't select it in pavucontrol/GNOME/any application 2. when I use Built-In Audio Analog Stereo > Headphones , it works for only few seconds and then stops. Thus the only sound that remains working is Built-In Audio Analog Stereo > Speakers (cheesy built-in speakers). This is what worked all the time during the ubuntu-bug test. Please rollback! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 27 10:56:45 2020 InstallationDate: Installed on 2020-08-06 (51 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [G5 5587, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0M2MWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd08/29/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.product.sku: 0825 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897440/+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 1900727] Re: Update ca-certificates with latest NSS roots
This bug was fixed in the package ca-certificates - 20201027ubuntu0.18.04.1 --- ca-certificates (20201027ubuntu0.18.04.1) bionic-security; urgency=medium * mozilla/{certdata.txt,nssckbi.h}: Update Mozilla certificate authority bundle to version 2.44. (LP: #1900727) -- Marc Deslauriers Tue, 27 Oct 2020 07:37:00 -0400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1900727 Title: Update ca-certificates with latest NSS roots Status in ca-certificates package in Ubuntu: Fix Released Bug description: Please refresh the default ca-certificates package with the latest NSS roots? Specifically, we would like to ensure these two roots from NSS 3.54 (26 June 2020) are included in the package: Bug 1641716 - Microsoft ECC Root Certificate Authority 2017 SHA-256 Fingerprint: 358DF39D764AF9E1B766E9C972DF352EE15CFAC227AF6AD1D70E8E4A6EDCBA02 Bug 1641716 - Microsoft RSA Root Certificate Authority 2017 SHA-256 Fingerprint: C741F70F4B2A8D88BF2E71C14122EF53EF10EBA0CFA5E64CFA20F418853073E0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1900727/+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 1900727] Re: Update ca-certificates with latest NSS roots
This bug was fixed in the package ca-certificates - 20201027ubuntu0.20.04.1 --- ca-certificates (20201027ubuntu0.20.04.1) focal-security; urgency=medium * mozilla/{certdata.txt,nssckbi.h}: Update Mozilla certificate authority bundle to version 2.44. (LP: #1900727) -- Marc Deslauriers Tue, 27 Oct 2020 07:37:00 -0400 ** Changed in: ca-certificates (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1900727 Title: Update ca-certificates with latest NSS roots Status in ca-certificates package in Ubuntu: Fix Released Bug description: Please refresh the default ca-certificates package with the latest NSS roots? Specifically, we would like to ensure these two roots from NSS 3.54 (26 June 2020) are included in the package: Bug 1641716 - Microsoft ECC Root Certificate Authority 2017 SHA-256 Fingerprint: 358DF39D764AF9E1B766E9C972DF352EE15CFAC227AF6AD1D70E8E4A6EDCBA02 Bug 1641716 - Microsoft RSA Root Certificate Authority 2017 SHA-256 Fingerprint: C741F70F4B2A8D88BF2E71C14122EF53EF10EBA0CFA5E64CFA20F418853073E0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1900727/+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 1897440] Re: Since ~Sep 25 updates HDMI Digital Out disappeared, Headphones stop working
thanks, closing the report since it's resolved ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low ** Changed in: alsa-driver (Ubuntu) Status: New => Fix Released -- 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/1897440 Title: Since ~Sep 25 updates HDMI Digital Out disappeared, Headphones stop working Status in alsa-driver package in Ubuntu: Fix Released Bug description: For last couple of months I've been using 20.04 sound OK on my Dell laptop but since last apt update/upgrade two strange things happened: 1. the HDMI Out sound device completely disappeared and I can't select it in pavucontrol/GNOME/any application 2. when I use Built-In Audio Analog Stereo > Headphones , it works for only few seconds and then stops. Thus the only sound that remains working is Built-In Audio Analog Stereo > Speakers (cheesy built-in speakers). This is what worked all the time during the ubuntu-bug test. Please rollback! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 27 10:56:45 2020 InstallationDate: Installed on 2020-08-06 (51 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [G5 5587, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0M2MWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd08/29/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.product.sku: 0825 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897440/+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 1901885] [NEW] line output device unailable on kde after reboot
Public bug reported: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy package-from-proposed -- 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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901885/+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 1898869] Re: System slow on booting
Providing... P.S.: This bug is not supposed to be acted up on ASAP, but it would be nice to be kept here as a notice that the boot is slow and needs to be taken into account for future work. That's in my opinion. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+attachment/5428519/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1901885] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428544/+files/CurrentDmesg.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901885/+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 1901885] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428543/+files/AudioDevicesInUse.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901885/+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 1901885] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428545/+files/Dependencies.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901885/+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 1901885] Re: line output device unailable on kde after reboot
apport information ** Tags added: apport-collected ** Description changed: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2019-06-02 (514 days ago) + InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + Package: pulseaudio 1:13.99.2-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 + Tags: groovy package-from-proposed + Uname: Linux 5.8.0-26-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) + UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/16/2018 + dmi.bios.release: 5.12 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P2.50 + dmi.board.name: H270M-ITX/ac + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428542/+files/AlsaInfo.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled B
[Touch-packages] [Bug 1901885] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428547/+files/ProcCpuinfoMinimal.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901885/+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 1901885] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428549/+files/PulseList.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901885/+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 1901885] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428548/+files/ProcEnviron.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901885/+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 1901885] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428546/+files/PaInfo.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901885/+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
For those who are using the laptop with Intel BT module 8087:0029: The firmware in the current 20.04 is: md5sum 8cadd1fa93ab9790f61165f384466b0d ibt-20-1-3.sfi The firmware in the current 20.10 is: md5sum a2ebb8594804b5230a406b536804988c ibt-20-1-3.sfi The hsp/hfp could work in the 20.10 but couldn't work in the current 20.04 due to the firmware difference. There are 3 new commits applied to 20.10 firmware: commit b7849f7ccf268a909a80b090db131ab22ca160b9 Author: Kiran K Date: Fri Jul 10 19:51:29 2020 +0530 linux-firmware: Update firmware file for Intel Bluetooth AX200 This patch adds new firmware file for Intel Bluetooth AX200 Also it is known as Intel CyclonePeak (CcP). FW Build: REL9916 Release Version: 21.110.0.3 Signed-off-by: Kiran K Signed-off-by: Josh Boyer commit 887d2a103c2bdd267dbca5bed39b1b493d6cbe13 Author: Amit K Bag Date: Wed May 27 15:30:49 2020 +0530 linux-firmware: Update firmware file for Intel Bluetooth AX200 This patch updates new firmware file for Intel Bluetooth AX200 Also it is known as Intel CyclonePeak (CcP). FW Build: REL8301 Release Version: 21.90.3.2 Signed-off-by: Amit K Bag Signed-off-by: Josh Boyer commit b2cad6a2d733d9b10d25a31874a51d96908d6e89 Author: Amit K Bag Date: Wed Apr 22 15:02:44 2020 +0530 linux-firmware: Update firmware file for Intel Bluetooth AX200 This patch updates new firmware file for Intel Bluetooth AX200 Also it is known as Intel CyclonePeak (CcP). FW Build: REL6356 Release Version: 21.90.0.3 Signed-off-by: Amit K Bag Signed-off-by: Josh Boyer -- 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 1901901] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1901901/+attachment/5428550/+files/AlsaInfo.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/1901901 Title: Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10 Status in pulseaudio package in Ubuntu: New Bug description: My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04. But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card is not detected, "System => Sound => Output Device" shows only "Dummy Output". I'm able to reproduce it even with live Ubuntu 20.10 from USB key. I checked that the issue happens in Ubuntu 20.10 with official kernel 5.8.0 and even with 5.9.1. Note that in Ubuntu 20.04 it worked well with 5.4 and 5.8.x So it doesn't seem to be depend on used kernel. --- $ systemctl --user status pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-10-28 14:25:34 CET; 25min ago TriggeredBy: ● pulseaudio.socket Main PID: 3002 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─3002 /usr/bin/pulseaudio --daemonize=no --log-target=journal Oct 28 14:25:34 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Tried to configure /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) more often than 5 time> --- When pulseaudio starts in verbose mode: $ pulseaudio -v ... I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC2D0c' failed (-16) I: [pulseaudio] alsa-util.c: Error opening PCM device hw:acp: Device or resource busy D: [pulseaudio] alsa-mixer.c: Profile set 0x558aa38b6670, auto_profiles=no, probed=yes, n_mappings=0, n_profiles=0, n_decibel_fixes=0 E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. I: [pulseaudio] module-udev-detect.c: Card /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) failed to load module. --- $ lspci -nnk | grep -A2 Audio 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:380d] Kernel driver in use: snd_hda_intel -- 03:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:380d] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 03:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:380d] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel --
[Touch-packages] [Bug 1901901] [NEW] Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10
Public bug reported: My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04. But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card is not detected, "System => Sound => Output Device" shows only "Dummy Output". I'm able to reproduce it even with live Ubuntu 20.10 from USB key. I checked that the issue happens in Ubuntu 20.10 with official kernel 5.8.0 and even with 5.9.1. Note that in Ubuntu 20.04 it worked well with 5.4 and 5.8.x So it doesn't seem to be depend on used kernel. --- $ systemctl --user status pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-10-28 14:25:34 CET; 25min ago TriggeredBy: ● pulseaudio.socket Main PID: 3002 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─3002 /usr/bin/pulseaudio --daemonize=no --log-target=journal Oct 28 14:25:34 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Tried to configure /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) more often than 5 time> --- When pulseaudio starts in verbose mode: $ pulseaudio -v ... I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC2D0c' failed (-16) I: [pulseaudio] alsa-util.c: Error opening PCM device hw:acp: Device or resource busy D: [pulseaudio] alsa-mixer.c: Profile set 0x558aa38b6670, auto_profiles=no, probed=yes, n_mappings=0, n_profiles=0, n_decibel_fixes=0 E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. I: [pulseaudio] module-udev-detect.c: Card /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) failed to load module. --- $ lspci -nnk | grep -A2 Audio 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:380d] Kernel driver in use: snd_hda_intel -- 03:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:380d] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 03:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:380d] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel --- $ cat /proc/asound/cards 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0x805c8000 irq 100 1 [Generic_1 ]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0x805c irq 101 2 [acp]: acp - acp LENOVO-82A2-YogaSlim714ARE05-LNVNB161216 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mirao 9326 F pulseaudio /dev/
[Touch-packages] [Bug 1901901] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1901901/+attachment/5428555/+files/ProcEnviron.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/1901901 Title: Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10 Status in pulseaudio package in Ubuntu: New Bug description: My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04. But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card is not detected, "System => Sound => Output Device" shows only "Dummy Output". I'm able to reproduce it even with live Ubuntu 20.10 from USB key. I checked that the issue happens in Ubuntu 20.10 with official kernel 5.8.0 and even with 5.9.1. Note that in Ubuntu 20.04 it worked well with 5.4 and 5.8.x So it doesn't seem to be depend on used kernel. --- $ systemctl --user status pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-10-28 14:25:34 CET; 25min ago TriggeredBy: ● pulseaudio.socket Main PID: 3002 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─3002 /usr/bin/pulseaudio --daemonize=no --log-target=journal Oct 28 14:25:34 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Tried to configure /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) more often than 5 time> --- When pulseaudio starts in verbose mode: $ pulseaudio -v ... I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC2D0c' failed (-16) I: [pulseaudio] alsa-util.c: Error opening PCM device hw:acp: Device or resource busy D: [pulseaudio] alsa-mixer.c: Profile set 0x558aa38b6670, auto_profiles=no, probed=yes, n_mappings=0, n_profiles=0, n_decibel_fixes=0 E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. I: [pulseaudio] module-udev-detect.c: Card /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) failed to load module. --- $ lspci -nnk | grep -A2 Audio 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:380d] Kernel driver in use: snd_hda_intel -- 03:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:380d] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 03:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:380d] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel
[Touch-packages] [Bug 1901901] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1901901/+attachment/5428551/+files/CurrentDmesg.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/1901901 Title: Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10 Status in pulseaudio package in Ubuntu: New Bug description: My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04. But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card is not detected, "System => Sound => Output Device" shows only "Dummy Output". I'm able to reproduce it even with live Ubuntu 20.10 from USB key. I checked that the issue happens in Ubuntu 20.10 with official kernel 5.8.0 and even with 5.9.1. Note that in Ubuntu 20.04 it worked well with 5.4 and 5.8.x So it doesn't seem to be depend on used kernel. --- $ systemctl --user status pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-10-28 14:25:34 CET; 25min ago TriggeredBy: ● pulseaudio.socket Main PID: 3002 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─3002 /usr/bin/pulseaudio --daemonize=no --log-target=journal Oct 28 14:25:34 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Tried to configure /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) more often than 5 time> --- When pulseaudio starts in verbose mode: $ pulseaudio -v ... I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC2D0c' failed (-16) I: [pulseaudio] alsa-util.c: Error opening PCM device hw:acp: Device or resource busy D: [pulseaudio] alsa-mixer.c: Profile set 0x558aa38b6670, auto_profiles=no, probed=yes, n_mappings=0, n_profiles=0, n_decibel_fixes=0 E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. I: [pulseaudio] module-udev-detect.c: Card /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) failed to load module. --- $ lspci -nnk | grep -A2 Audio 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:380d] Kernel driver in use: snd_hda_intel -- 03:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:380d] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 03:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:380d] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel --
[Touch-packages] [Bug 1901901] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1901901/+attachment/5428553/+files/PaInfo.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/1901901 Title: Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10 Status in pulseaudio package in Ubuntu: New Bug description: My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04. But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card is not detected, "System => Sound => Output Device" shows only "Dummy Output". I'm able to reproduce it even with live Ubuntu 20.10 from USB key. I checked that the issue happens in Ubuntu 20.10 with official kernel 5.8.0 and even with 5.9.1. Note that in Ubuntu 20.04 it worked well with 5.4 and 5.8.x So it doesn't seem to be depend on used kernel. --- $ systemctl --user status pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-10-28 14:25:34 CET; 25min ago TriggeredBy: ● pulseaudio.socket Main PID: 3002 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─3002 /usr/bin/pulseaudio --daemonize=no --log-target=journal Oct 28 14:25:34 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Tried to configure /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) more often than 5 time> --- When pulseaudio starts in verbose mode: $ pulseaudio -v ... I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC2D0c' failed (-16) I: [pulseaudio] alsa-util.c: Error opening PCM device hw:acp: Device or resource busy D: [pulseaudio] alsa-mixer.c: Profile set 0x558aa38b6670, auto_profiles=no, probed=yes, n_mappings=0, n_profiles=0, n_decibel_fixes=0 E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. I: [pulseaudio] module-udev-detect.c: Card /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) failed to load module. --- $ lspci -nnk | grep -A2 Audio 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:380d] Kernel driver in use: snd_hda_intel -- 03:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:380d] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 03:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:380d] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ---
[Touch-packages] [Bug 1898869] Re: System slow on booting
erm ... this is an atom/celeron laptop with 4GB that starts BOINC as a system service during boot ? there seems to also be a lot of broken gnome-shell extensions installed on this system that error out during startup ... there is ifupdown installed which is probably involved with the network manager slowness (was this an upgrade from a former LTS ? (ifupdown is deprecated since years now and should not be installed at all) ... have you ever tried a plain unmodified 20.04.1 on this machine without installing all this extra software on top ? -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1901901] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1901901/+attachment/5428552/+files/Dependencies.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/1901901 Title: Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10 Status in pulseaudio package in Ubuntu: New Bug description: My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04. But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card is not detected, "System => Sound => Output Device" shows only "Dummy Output". I'm able to reproduce it even with live Ubuntu 20.10 from USB key. I checked that the issue happens in Ubuntu 20.10 with official kernel 5.8.0 and even with 5.9.1. Note that in Ubuntu 20.04 it worked well with 5.4 and 5.8.x So it doesn't seem to be depend on used kernel. --- $ systemctl --user status pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-10-28 14:25:34 CET; 25min ago TriggeredBy: ● pulseaudio.socket Main PID: 3002 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─3002 /usr/bin/pulseaudio --daemonize=no --log-target=journal Oct 28 14:25:34 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Tried to configure /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) more often than 5 time> --- When pulseaudio starts in verbose mode: $ pulseaudio -v ... I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC2D0c' failed (-16) I: [pulseaudio] alsa-util.c: Error opening PCM device hw:acp: Device or resource busy D: [pulseaudio] alsa-mixer.c: Profile set 0x558aa38b6670, auto_profiles=no, probed=yes, n_mappings=0, n_profiles=0, n_decibel_fixes=0 E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. I: [pulseaudio] module-udev-detect.c: Card /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) failed to load module. --- $ lspci -nnk | grep -A2 Audio 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:380d] Kernel driver in use: snd_hda_intel -- 03:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:380d] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 03:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:380d] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel --
[Touch-packages] [Bug 1899195] Proposed package upload rejected
An upload of apport to bionic-proposed has been rejected from the upload queue for the following reason: "Symlinks appear inadvertently flattened; for example bin/apport-collect has changed from a symlink to a flat file.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: In Progress Status in apport source package in Bionic: In Progress Status in apport source package in Focal: In Progress Bug description: Impact -- apport is crashing for some users when a crash file is created about an executable which has been deleted. Test Case - While you won't get a Traceback (because there is a location for apport to print its usages message) with the following test case you will see apport usage printed: $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] With the fixed version of apport you'll see no such usage message. Regression Potential Because new code is being added its possible that the python syntax could be bad which would result in another crash, so careful review the code. Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): File "/usr/share/apport/apport", line 451, in options = parse_arguments() File "/usr/share/apport/apport", line 396, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. The fix below from bdmurray seems to fix it. https://paste.ubuntu.com/p/pVKNP9kWP4/ There is report of this issue in Focal, Bionic and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+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 1899195] Proposed package upload rejected
An upload of apport to focal-proposed has been rejected from the upload queue for the following reason: "Symlinks appear inadvertently flattened; for example bin/apport-collect has changed from a symlink to a flat file.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: In Progress Status in apport source package in Bionic: In Progress Status in apport source package in Focal: In Progress Bug description: Impact -- apport is crashing for some users when a crash file is created about an executable which has been deleted. Test Case - While you won't get a Traceback (because there is a location for apport to print its usages message) with the following test case you will see apport usage printed: $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] With the fixed version of apport you'll see no such usage message. Regression Potential Because new code is being added its possible that the python syntax could be bad which would result in another crash, so careful review the code. Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): File "/usr/share/apport/apport", line 451, in options = parse_arguments() File "/usr/share/apport/apport", line 396, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. The fix below from bdmurray seems to fix it. https://paste.ubuntu.com/p/pVKNP9kWP4/ There is report of this issue in Focal, Bionic and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+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 1901901] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1901901/+attachment/5428554/+files/ProcCpuinfoMinimal.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/1901901 Title: Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10 Status in pulseaudio package in Ubuntu: New Bug description: My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04. But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card is not detected, "System => Sound => Output Device" shows only "Dummy Output". I'm able to reproduce it even with live Ubuntu 20.10 from USB key. I checked that the issue happens in Ubuntu 20.10 with official kernel 5.8.0 and even with 5.9.1. Note that in Ubuntu 20.04 it worked well with 5.4 and 5.8.x So it doesn't seem to be depend on used kernel. --- $ systemctl --user status pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-10-28 14:25:34 CET; 25min ago TriggeredBy: ● pulseaudio.socket Main PID: 3002 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─3002 /usr/bin/pulseaudio --daemonize=no --log-target=journal Oct 28 14:25:34 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Tried to configure /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) more often than 5 time> --- When pulseaudio starts in verbose mode: $ pulseaudio -v ... I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC2D0c' failed (-16) I: [pulseaudio] alsa-util.c: Error opening PCM device hw:acp: Device or resource busy D: [pulseaudio] alsa-mixer.c: Profile set 0x558aa38b6670, auto_profiles=no, probed=yes, n_mappings=0, n_profiles=0, n_decibel_fixes=0 E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. I: [pulseaudio] module-udev-detect.c: Card /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) failed to load module. --- $ lspci -nnk | grep -A2 Audio 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:380d] Kernel driver in use: snd_hda_intel -- 03:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:380d] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 03:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:380d] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel --
[Touch-packages] [Bug 1901901] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1901901/+attachment/5428556/+files/PulseList.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/1901901 Title: Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10 Status in pulseaudio package in Ubuntu: New Bug description: My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04. But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card is not detected, "System => Sound => Output Device" shows only "Dummy Output". I'm able to reproduce it even with live Ubuntu 20.10 from USB key. I checked that the issue happens in Ubuntu 20.10 with official kernel 5.8.0 and even with 5.9.1. Note that in Ubuntu 20.04 it worked well with 5.4 and 5.8.x So it doesn't seem to be depend on used kernel. --- $ systemctl --user status pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-10-28 14:25:34 CET; 25min ago TriggeredBy: ● pulseaudio.socket Main PID: 3002 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─3002 /usr/bin/pulseaudio --daemonize=no --log-target=journal Oct 28 14:25:34 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Tried to configure /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) more often than 5 time> --- When pulseaudio starts in verbose mode: $ pulseaudio -v ... I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC2D0c' failed (-16) I: [pulseaudio] alsa-util.c: Error opening PCM device hw:acp: Device or resource busy D: [pulseaudio] alsa-mixer.c: Profile set 0x558aa38b6670, auto_profiles=no, probed=yes, n_mappings=0, n_profiles=0, n_decibel_fixes=0 E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. I: [pulseaudio] module-udev-detect.c: Card /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) failed to load module. --- $ lspci -nnk | grep -A2 Audio 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:380d] Kernel driver in use: snd_hda_intel -- 03:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:380d] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 03:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:380d] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel
[Touch-packages] [Bug 1901885] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428578/+files/AudioDevicesInUse.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.v
[Touch-packages] [Bug 1901885] Re: line output device unailable on kde after reboot
apport information ** Description changed: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2019-06-02 (514 days ago) + InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + Package: pulseaudio 1:13.99.2-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 + Tags: groovy package-from-proposed + Uname: Linux 5.4.0-52-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) + UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/16/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P2.50 + dmi.board.name: H270M-ITX/ac + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428577/+files/AlsaInfo.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/1901885 Title: line output device unailable
[Touch-packages] [Bug 1901885] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428580/+files/Dependencies.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To
[Touch-packages] [Bug 1901885] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428579/+files/CurrentDmesg.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To
[Touch-packages] [Bug 1901901] Re: Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10
A workaround exists: * Add "options snd-hda-intel index=1" into /etc/modprobe.d/alsa-base.conf * Restart OS * When login screen appears, sound works ✔️. Actually the device "Speaker - HD-Audio Generic" is used instead of "Speaker - Family 17h HD Audio Controller", but sound works well. * When I login, sometimes sound stops working ("Dummy Output" again), but then it's enough to run "pulseaudio -k" (pulseaudio is restarted) and I can hear sound -- 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/1901901 Title: Yoga Slim 7: Sound output device is not detected after upgrade from Ubuntu 20.04 to 20.10 Status in pulseaudio package in Ubuntu: New Bug description: My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04. But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card is not detected, "System => Sound => Output Device" shows only "Dummy Output". I'm able to reproduce it even with live Ubuntu 20.10 from USB key. I checked that the issue happens in Ubuntu 20.10 with official kernel 5.8.0 and even with 5.9.1. Note that in Ubuntu 20.04 it worked well with 5.4 and 5.8.x So it doesn't seem to be depend on used kernel. --- $ systemctl --user status pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-10-28 14:25:34 CET; 25min ago TriggeredBy: ● pulseaudio.socket Main PID: 3002 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─3002 /usr/bin/pulseaudio --daemonize=no --log-target=journal Oct 28 14:25:34 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to find a working profile. Oct 28 14:25:35 yoga pulseaudio[3002]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6> Oct 28 14:25:35 yoga pulseaudio[3002]: Tried to configure /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) more often than 5 time> --- When pulseaudio starts in verbose mode: $ pulseaudio -v ... I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC2D0c' failed (-16) I: [pulseaudio] alsa-util.c: Error opening PCM device hw:acp: Device or resource busy D: [pulseaudio] alsa-mixer.c: Profile set 0x558aa38b6670, auto_profiles=no, probed=yes, n_mappings=0, n_profiles=0, n_decibel_fixes=0 E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_03_00.6" card_name="alsa_card.pci-_03_00.6" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. I: [pulseaudio] module-udev-detect.c: Card /devices/pci:00/:00:08.1/:03:00.6/sound/card1 (alsa_card.pci-_03_00.6) failed to load module. --- $ lspci -nnk | grep -A2 Audio 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:380d] Kernel driver in use: snd_hda_intel -- 03:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:380d] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 03:00.6 Audio device [0403]: Advanc
[Touch-packages] [Bug 1901885] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428584/+files/PulseList.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Fi
[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Marco On my machine with BT moudle 8087:0026, I reproduced the problem, and replaced with 20.10 firmware ibt-19-0-4.sfi, but still could not work in hsp/hfp mode. What I found is the bt driver can't receive the SCO packet, the returned packet length is always 0. And if the bt headset can't work in the hsp/hfp mode, please run hci config, if the output like below (RX bytes: sco:0 TX bytes: sco:1), that means the bt driver can't receive SCO packets, as a result the headset can't work in hsp/hfp mode since hsp/hfp mode depends on SCO link. hci0: Type: Primary Bus: USB BD Address: D4:D2:52:3D:49:E6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:23638 acl:85 sco:0 events:3463 errors:0 TX bytes:980646 acl:323 sco:1 commands:3121 errors:0 -- 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 1901885] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428583/+files/ProcEnviron.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To B
[Touch-packages] [Bug 1901885] Re: line output device unailable on kde after reboot
booting with linux-image-5.4.0-52-generic solves the problem. The selected output sink is bad but the 'line out' sink is present and can be selected, as opposed to booting with linux-image-5.8.0-26-generic the apport-collect will be with linux-image-5.4.0-49-generic, to show the differences. -- 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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.pr
[Touch-packages] [Bug 1901885] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428581/+files/PaInfo.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By
[Touch-packages] [Bug 1901885] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1901885/+attachment/5428582/+files/ProcCpuinfoMinimal.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/1901885 Title: line output device unailable on kde after reboot Status in pulseaudio package in Ubuntu: New Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product
[Touch-packages] [Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
Hello errors.ubuntu.com, or anyone else affected, Accepted apport into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.1-0ubuntu2.26 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Committed Status in apport source package in Bionic: In Progress Status in apport source package in Focal: In Progress Bug description: Impact -- apport is crashing for some users when a crash file is created about an executable which has been deleted. Test Case - While you won't get a Traceback (because there is a location for apport to print its usages message) with the following test case you will see apport usage printed: $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] With the fixed version of apport you'll see no such usage message. Regression Potential Because new code is being added its possible that the python syntax could be bad which would result in another crash, so careful review the code. Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): File "/usr/share/apport/apport", line 451, in options = parse_arguments() File "/usr/share/apport/apport", line 396, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. The fix below from bdmurray seems to fix it. https://paste.ubuntu.com/p/pVKNP9kWP4/ There is report of this issue in Focal, Bionic and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+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 1901908] [NEW] [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem
Public bug reported: The volume keys of my keyboard not working since the last ubuntu update release. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lumantar 3208 F pulseaudio /dev/snd/controlC0: lumantar 3208 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 10:01:27 2020 InstallationDate: Installed on 2018-09-14 (775 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: oct 28 09:15:18 lumantar dbus-daemon[776]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=120 pid=1243 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") oct 28 09:15:23 lumantar pulseaudio[1243]: No UCM verb is valid for hw:0 oct 28 09:15:26 lumantar pulseaudio[1243]: No UCM verb is valid for hw:2 oct 28 09:19:41 lumantar systemd[1199]: pulseaudio.service: Succeeded. oct 28 09:19:51 lumantar systemd[1199]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to focal on 2020-10-21 (7 days ago) dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN31WW:bd04/20/2015:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1901908 Title: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem Status in alsa-driver package in Ubuntu: New Bug description: The volume keys of my keyboard not working since the last ubuntu update release. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lumantar 3208 F pulseaudio /dev/snd/controlC0: lumantar 3208 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 10:01:27 2020 InstallationDate: Installed on 2018-09-14 (775 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: oct 28 09:15:18 lumantar dbus-daemon[776]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=120 pid=1243 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") oct 28 09:15:23 lumantar pulseaudio[1243]: No UCM verb is valid for hw:0 oct 28 09:15:26 lumantar pulseaudio[1243]: No UCM verb is valid for hw:2 oct 28 09:19:41 lumantar systemd[1199]: pulseaudio.service: Succeeded. oct 28 09:19:51 lumantar systemd[1199]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to focal on 2020-10-21 (7 days ago) dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN31WW:bd04/20/2015:svnLENOVO:pn20354:pvrLenovoZ50-70
[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Marco and Hui Wang My Dell Latitude 5411 also contains an Intel BT Module 8087:0026. I can also reproduce the problem with my Sony WH-CH700N headphones. A2DP is fine, HSP/HFP is broken. I also tried Marco's fix and copied the newer firmware (https://launchpad.net/ubuntu/+source/linux-firmware/1.190) for ibt-19-0-4, but just like Hui Wang the problem still exists. I can also confirm the hciconfig behaviour, every time I switch to HSP/HFP, the TX sco counter increases by one, but the RX sco counter stays at 0. -- 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 1898869] Re: System slow on booting
This is an official Kubuntu 20.04 LTS installed from ISO because Windows has broken so much that even the recovery options were broken. Nevertheless, Windows was booting much faster on this very same laptop, likely because of the "fast boot" feature. It was booting in under a minute, I'm pretty sure of this even if i haven't used a stopwatch. The reality is that 2 and a half minutes is way too much compared to one minute at worst. -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1901909] [NEW] package python3-apport 2.20.11-0ubuntu27.10 failed to install/upgrade: installed python3-apport package post-installation script subprocess returned error exit sta
Public bug reported: apport error reported and not able to upgrade or update or remove any package ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-apport 2.20.11-0ubuntu27.10 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:0:117:211980:2020-10-27 21:10:52.322911977 +0530:2020-10-27 21:10:53.322911977 +0530:/var/crash/python3-apport.0.crash 600:0:117:777645:2020-10-27 23:59:36.918364411 +0530:2020-10-28 18:25:36.906290013 +0530:/var/crash/udev.0.crash 644:0:117:1017800:2020-10-28 18:50:24.606360952 +0530:2020-10-28 19:32:38.226656672 +0530:/var/crash/mysql-server-8.0.0.crash Date: Tue Oct 27 21:10:53 2020 DuplicateSignature: package:python3-apport:2.20.11-0ubuntu27.10 Setting up python3-apport (2.20.9-0ubuntu7.18) ... /usr/lib/python3/dist-packages/apport/__pycache__/ui.cpython-36.pyc is a non-regular file and will be changed into a regular one if import writes a byte-compiled file to it dpkg: error processing package python3-apport (--configure): installed python3-apport package post-installation script subprocess returned error exit status 1 ErrorMessage: installed python3-apport package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-10-09 (385 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: apport Title: package python3-apport 2.20.11-0ubuntu27.10 failed to install/upgrade: installed python3-apport package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1901909 Title: package python3-apport 2.20.11-0ubuntu27.10 failed to install/upgrade: installed python3-apport package post-installation script subprocess returned error exit status 1 Status in apport package in Ubuntu: New Bug description: apport error reported and not able to upgrade or update or remove any package ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-apport 2.20.11-0ubuntu27.10 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:0:117:211980:2020-10-27 21:10:52.322911977 +0530:2020-10-27 21:10:53.322911977 +0530:/var/crash/python3-apport.0.crash 600:0:117:777645:2020-10-27 23:59:36.918364411 +0530:2020-10-28 18:25:36.906290013 +0530:/var/crash/udev.0.crash 644:0:117:1017800:2020-10-28 18:50:24.606360952 +0530:2020-10-28 19:32:38.226656672 +0530:/var/crash/mysql-server-8.0.0.crash Date: Tue Oct 27 21:10:53 2020 DuplicateSignature: package:python3-apport:2.20.11-0ubuntu27.10 Setting up python3-apport (2.20.9-0ubuntu7.18) ... /usr/lib/python3/dist-packages/apport/__pycache__/ui.cpython-36.pyc is a non-regular file and will be changed into a regular one if import writes a byte-compiled file to it dpkg: error processing package python3-apport (--configure): installed python3-apport package post-installation script subprocess returned error exit status 1 ErrorMessage: installed python3-apport package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-10-09 (385 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: apport Title: package python3-apport 2.20.11-0ubuntu27.10 failed to install/upgrade: installed python3-apport package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1901909/+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 1901909] Re: package python3-apport 2.20.11-0ubuntu27.10 failed to install/upgrade: installed python3-apport package post-installation script subprocess returned error exit statu
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1901909 Title: package python3-apport 2.20.11-0ubuntu27.10 failed to install/upgrade: installed python3-apport package post-installation script subprocess returned error exit status 1 Status in apport package in Ubuntu: New Bug description: apport error reported and not able to upgrade or update or remove any package ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-apport 2.20.11-0ubuntu27.10 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:0:117:211980:2020-10-27 21:10:52.322911977 +0530:2020-10-27 21:10:53.322911977 +0530:/var/crash/python3-apport.0.crash 600:0:117:777645:2020-10-27 23:59:36.918364411 +0530:2020-10-28 18:25:36.906290013 +0530:/var/crash/udev.0.crash 644:0:117:1017800:2020-10-28 18:50:24.606360952 +0530:2020-10-28 19:32:38.226656672 +0530:/var/crash/mysql-server-8.0.0.crash Date: Tue Oct 27 21:10:53 2020 DuplicateSignature: package:python3-apport:2.20.11-0ubuntu27.10 Setting up python3-apport (2.20.9-0ubuntu7.18) ... /usr/lib/python3/dist-packages/apport/__pycache__/ui.cpython-36.pyc is a non-regular file and will be changed into a regular one if import writes a byte-compiled file to it dpkg: error processing package python3-apport (--configure): installed python3-apport package post-installation script subprocess returned error exit status 1 ErrorMessage: installed python3-apport package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-10-09 (385 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: apport Title: package python3-apport 2.20.11-0ubuntu27.10 failed to install/upgrade: installed python3-apport package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1901909/+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 1896614] Re: Race condition when starting dbus services
# VERIFICATION Note: As a reminder, the issue here is that there's a race condition between any DBUS service and systemctl daemon-reload, where systemd adds the DBUS filter (AddMatch) that looks for a name change when that has already happened. I'll be using systemd-logind as the DBUS service in my reproducer. Using the following reproducer: for i in $(seq 1 1000); do echo $i; ssh $SERVER 'sudo systemctl daemon- reload & sudo systemctl restart systemd-logind'; done - With systemd=237-3ubuntu10.42 (-updates), after a few runs, systemd-logind is stuck as a running job and ssh is not responsive. DBUS messages[1] show that the AddMatch filter is set by systemd after systemd-logind has acquired its final name (systemd-login1) - With systemd=237-3ubuntu10.43 (-proposed), systemd-logind does not get stuck and everything continues to work. In a scenario[2] where the systemd DBUS AddMatch message arrives after the final systemd-logind NameOwnerChanged, systemd is able to catch up thanks to the GetNameOwner introduced in the patch [1] https://pastebin.ubuntu.com/p/NxRNX9bwCP/ [2] https://pastebin.ubuntu.com/p/jpKpW3g2bK/ -- 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/1896614 Title: Race condition when starting dbus services Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] In certain scenarios, such as high load environments or when "systemctl daemon-reload" runs at the same time a dbus service is starting (e.g. systemd-logind), systemd is not able to track properly when the service has started, keeping the job 'running' forever. [test case] set up a 1-cpu VM with Bionic, and configure the system with a ssh key so the user can ssh to localhost. Then run something like: $ while timeout 5 ssh localhost true; do echo 'reloading'; sudo systemctl restart systemd-logind & sudo systemctl daemon-reload; done if that doesn't work try: $ while timeout 5 ssh localhost true; do echo 'reloading'; sudo sh -c 'systemctl restart systemd-logind & systemctl daemon-reload'; done once the reproducer exits the while loop, there should be a running job for systemd-logind, and any logins attempted after the bug is reproduced should also hang waiting for the systemd-logind job to complete, e.g.: ubuntu@lp1896614-b:~$ systemctl list-jobs JOB UNIT TYPE STATE 525 systemd-logind.service start running 669 session-6.scopestart waiting 664 session-5.scopestart waiting 3 jobs listed. [regression potential] any regression would likely involve services that are Type=dbus failing to complete starting. as with any systemd change, regressions could also involve assertion failures in systemd which causes it to exit. [scope] this is needed only for bionic. this is fixed upstream with commit a5a8776ae5e4244b7f5acb2a1bfbe6e0b4d8a870 which is including starting in v243, so it is included already in focal and later. (per upstream bug) this was introduced by upstream commit 75152a4d6aedbfd3ee8b2d5782b9edf27407622a which was included starting in v237, so this bug is not present in xenial or earlier. [original description] In certain scenarios, such as high load environments or when "systemctl daemon-reload" runs at the same time a dbus service is starting (e.g. systemd-logind), systemd is not able to track properly when the service has started, keeping the job 'running' forever. The issue appears when systemd runs the "AddMatch" dbus method call to track the service's "NameOwnerChange" once it has already ran. A working instance would look like this: https://pastebin.ubuntu.com/p/868J6WBRQx/ A failing instance would be: https://pastebin.ubuntu.com/p/HhJZ4p8dT5/ I've been able to reproduce the issue on Bionic (237-3ubuntu10.42) running: sudo systemctl daemon-reload & sudo systemctl restart systemd-logind To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1896614/+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
Update: If the bluetooth module is 8087:0029 or 8087:0026, the firmware in the 20.04 has some problem, we need to update the firmware, and I found the most import is *.ddc instead of *.sfi, For 8087:0029, please update ibt-20-1-3.sfi and ibt-20-1-3.ddc from 20.10 or latest upstream For 8087:0026, please update ibt-19-0-4.sfi and ibt-19-0-4.ddc from 20.10 or latest upstream After update, please poweroff the machine (not reboot), this could guarantee the bt driver will reload the firmware (sfi and ddc), then power on the machine, test the hsp/hfp mode. I have tested, after update the ddc, hsp/hfp could work with 8087:0029 and 8087:0026 now. -- 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 1901020] Re: new upstream release 2020d
Hello Brian, or anyone else affected, Accepted tzdata into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2020d- 0ubuntu0.20.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tzdata (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: In Progress Status in tzdata source package in Trusty: In Progress Status in tzdata source package in Xenial: In Progress Status in tzdata source package in Bionic: In Progress Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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 1898869] Re: System slow on booting
Oh, excuse me. Just realised that you mentioned BOINC. I'm very sorry, but i have uploaded the wrong file. This one is from my Acer Aspire, not from the grandma's laptop. I'm sorry again, i've created that journal.txt due to another issue and both files were named that way. My PC is an upgrade, yes. I'm attaching her journal.txt now. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+attachment/5428613/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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
@Hui Wang After I powered off the machine instead of a reboot, the HSP/HFP mode is now working. However there are two things to note, that might be related to this problem: 1. In the sound settings menu (I'm using Linux Mint Ulyana) I cannot play a test sound in HSP/HFP mode, only in A2DP mode. 2. The sound quality is significantly worse when using HSP/HFP. It really sounds like using a telephone / landline connection. As soon as I switch to A2DP, the sound ist normal again. -- 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 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
Hello errors.ubuntu.com, or anyone else affected, Accepted apport into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu27.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Committed Status in apport source package in Bionic: In Progress Status in apport source package in Focal: Fix Committed Bug description: Impact -- apport is crashing for some users when a crash file is created about an executable which has been deleted. Test Case - While you won't get a Traceback (because there is a location for apport to print its usages message) with the following test case you will see apport usage printed: $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] With the fixed version of apport you'll see no such usage message. Regression Potential Because new code is being added its possible that the python syntax could be bad which would result in another crash, so careful review the code. Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): File "/usr/share/apport/apport", line 451, in options = parse_arguments() File "/usr/share/apport/apport", line 396, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. The fix below from bdmurray seems to fix it. https://paste.ubuntu.com/p/pVKNP9kWP4/ There is report of this issue in Focal, Bionic and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+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 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
Hello errors.ubuntu.com, or anyone else affected, Accepted apport into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.19 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Committed Status in apport source package in Bionic: Fix Committed Status in apport source package in Focal: Fix Committed Bug description: Impact -- apport is crashing for some users when a crash file is created about an executable which has been deleted. Test Case - While you won't get a Traceback (because there is a location for apport to print its usages message) with the following test case you will see apport usage printed: $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] With the fixed version of apport you'll see no such usage message. Regression Potential Because new code is being added its possible that the python syntax could be bad which would result in another crash, so careful review the code. Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): File "/usr/share/apport/apport", line 451, in options = parse_arguments() File "/usr/share/apport/apport", line 396, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. The fix below from bdmurray seems to fix it. https://paste.ubuntu.com/p/pVKNP9kWP4/ There is report of this issue in Focal, Bionic and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+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 1901922] [NEW] No sound output device on startup
Public bug reported: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1901922 Title: No sound output device on startup Status in pulseaudio package in Ubuntu: New Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENO
[Touch-packages] [Bug 1899195] Autopkgtest regression report (apport/2.20.1-0ubuntu2.26)
All autopkgtests for the newly accepted apport (2.20.1-0ubuntu2.26) for xenial have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.1-0ubuntu2.26 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/xenial/update_excuses.html#apport [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Committed Status in apport source package in Bionic: Fix Committed Status in apport source package in Focal: Fix Committed Bug description: Impact -- apport is crashing for some users when a crash file is created about an executable which has been deleted. Test Case - While you won't get a Traceback (because there is a location for apport to print its usages message) with the following test case you will see apport usage printed: $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] With the fixed version of apport you'll see no such usage message. Regression Potential Because new code is being added its possible that the python syntax could be bad which would result in another crash, so careful review the code. Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): File "/usr/share/apport/apport", line 451, in options = parse_arguments() File "/usr/share/apport/apport", line 396, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. The fix below from bdmurray seems to fix it. https://paste.ubuntu.com/p/pVKNP9kWP4/ There is report of this issue in Focal, Bionic and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+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 1901020] Re: new upstream release 2020d
Hello Brian, or anyone else affected, Accepted tzdata into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2020d- 0ubuntu0.18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tzdata (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic ** Changed in: tzdata (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: In Progress Status in tzdata source package in Trusty: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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 1901020] Please test proposed package
Hello Brian, or anyone else affected, Accepted tzdata into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2020d- 0ubuntu0.16.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: In Progress Status in tzdata source package in Trusty: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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
@Hui: thanks for the update :) @Benny: the issue with pulseaudio and bt sound quality is a neverending story... e.g.: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/776 https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838151 I'm considering an USB audio adapter (as someone is suggesting in the other threads) since it's almost impossible to have a decent conversation using my laptop and my bt headset... ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #776 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/776 -- 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 1898869] Re: System slow on booting
oh, and i missed, d) there is a mis-configured postfix install running on that device too ... since it is not configured and crashing in a loop during boot anyway, i'd recomend removing postfix ... -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1898869] Re: System slow on booting
okay, thats quite different ... a) you run the lowlatency kernel for whatever reason ... this is clearly the worst choice you can pick for already slow hardware (low latency -> do one thing as fast as you can ... ignore other things ... i.e. you trade overall system performance for the ability to do one single task very fast (a typical use for this kernel is fully reliable professional audio processing (no crackling, no jitter) at the cost of desktop performance) b) the (third party) wlan driver crashes in a loop, preventing the network from coming up for quite some time ... c) you seem to run dnscrypt-proxy and that seems to effectively delay working DNS resolution until the end of the boot for whatever reason ... same question as before ... have you tired running a completely unmodified install of 20.04.1 on this hardware ? did that behave similarly slow ? -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1901926] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
Public bug reported: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) dmi.bios.date: 11/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03REZ.041.191104.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P03REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 ** 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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: New Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) dmi.bios.date: 11/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03REZ.041.191104.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-P
[Touch-packages] [Bug 1901929] [NEW] [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all
Public bug reported: Hi. I am new to ubuntu. I had sound at first then it just disappeared. I have tried to fix it. Note: When I woke ubuntu from sleep it would have no sound until I rebooted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.0-050600-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 17:32:40 2020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: No sound at all Title: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V22.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970 GAMING (MS-7693) dmi.board.vendor: MSI dmi.board.version: 4.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: MSI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-28T16:45:58.098082 ** 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/1901929 Title: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi. I am new to ubuntu. I had sound at first then it just disappeared. I have tried to fix it. Note: When I woke ubuntu from sleep it would have no sound until I rebooted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.0-050600-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 17:32:40 2020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: No sound at all Title: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V22.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970 GAMING (MS-7693) dmi.board.vendor: MSI dmi.board.version: 4.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: MSI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-28T16:45:58.098082 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More hel
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Have a question about USB bluetooth transmitters mentioned above. Both models include Talk/Listen switches. Do you have to use them to get decent quality for music and for calls? Or is music quality good even in Talk mode? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I can only speak to the one that I linked, but yes it has talk/list switch. The talk mode is only for talking (the music quality is BAD), the lisen mode is only for listening (the music quality is good). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1881447] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
Hey Vern, Sorry you were having difficulties. 'sudo apt install -f' should cause apt to attempt to finish installing packages that had problems during the post install phase, where the error that is tripped over (like the dangling symlink in /etc/ssl/certs) has been resolved. ** Changed in: ca-certificates (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1881447 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: Incomplete Bug description: Upgrading from 16.04 LTS to 18.04 LTS. This is a WEB server with a Let's Encrypt certificate. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Sat May 30 20:00:50 2020 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-09-16 (987 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-05-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1881447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I've got a DG60 dongle (a slightly bigger cousin), and my experiences with a headset that does only have SBC/MP3 codecs (Aftershokz Aeropex) - It switches attached to my Linux (Ubuntu 18.04) automatically to HFP/HSP profile (mono + microphone, but in good quality) when my laptop starts to use the microphone. - You can switch mode manually (for the very seldom case where it somehow does not realize that it should switch). Andreas Am Mi., 28. Okt. 2020 um 19:30 Uhr schrieb Falc <1838...@bugs.launchpad.net >: > I can only speak to the one that I linked, but yes it has talk/list > switch. The talk mode is only for talking (the music quality is BAD), > the lisen mode is only for listening (the music quality is good). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1838151 > > Title: > Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing > wide band speech support (Bluetooth A2DP codecs). > > To manage notifications about this bug go to: > https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1898869] Re: System slow on booting
** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1901929] Re: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all
Oops sorry -- 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/1901929 Title: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi. I am new to ubuntu. I had sound at first then it just disappeared. I have tried to fix it. Note: When I woke ubuntu from sleep it would have no sound until I rebooted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.0-050600-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 17:32:40 2020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: No sound at all Title: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V22.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970 GAMING (MS-7693) dmi.board.vendor: MSI dmi.board.version: 4.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: MSI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-28T16:45:58.098082 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901929/+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 1664844] Re: No distinction between link-up and link-down interfaces
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Bug description: [Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
How do we get the Kernel maintainers to approve the remaining patches? I thought it might be fixed in 20.10 (KUbuntu), but it is not. I would think there is at least one kernel approver within Canonical? If not, who do I get in touch to talk about this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1901236] Re: Getting notifications twice
I'm closing this since according to upstream they are the ones who should fix this (but it's blocked on a Gnome Shell issue). ** Changed in: evolution-data-server (Ubuntu) Status: Incomplete => Invalid ** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #262 https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/262 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1901236 Title: Getting notifications twice Status in evolution-data-server package in Ubuntu: Invalid Bug description: I would like to revisit https://bugs.launchpad.net/ubuntu/+source /evolution-data-server/+bug/1805666 For years, I've been closing both the "modern" notification popup and the "classic" popup window at the same time, many times a day. Sometimes even the "e-a-n is ready" notification. This is really annoying. The only way of disabling this is to remove or modify a desktop file that will be overwritten with the next package update. Isn't it time to remove /etc/xdg/autostart/org.gnome.Evolution-alarm- notify.desktop ? Or is this an upstream issue ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1901236/+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 1901236] Re: Getting notifications twice
For future reference: Upstream report: https://gitlab.gnome.org/GNOME/evolution-data- server/-/issues/262 Workarounds: - Disable autostart as described above, but this will cancel both Gnome Shell and e-a-n notifications. - Alternatively, set /org/gnome/evolution-data-server/calendar/notify-with-tray which keeps Gnome Shell notifications but hides the standalone e-a-n popup window. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1901236 Title: Getting notifications twice Status in evolution-data-server package in Ubuntu: Invalid Bug description: I would like to revisit https://bugs.launchpad.net/ubuntu/+source /evolution-data-server/+bug/1805666 For years, I've been closing both the "modern" notification popup and the "classic" popup window at the same time, many times a day. Sometimes even the "e-a-n is ready" notification. This is really annoying. The only way of disabling this is to remove or modify a desktop file that will be overwritten with the next package update. Isn't it time to remove /etc/xdg/autostart/org.gnome.Evolution-alarm- notify.desktop ? Or is this an upstream issue ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1901236/+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 1901020] Autopkgtest regression report (tzdata/2020d-0ubuntu0.20.04)
All autopkgtests for the newly accepted tzdata (2020d-0ubuntu0.20.04) for focal have finished running. The following regressions have been reported in tests triggered by the package: gnustep-base/1.26.0-7 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#tzdata [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: In Progress Status in tzdata source package in Trusty: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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 1901946] [NEW] [HDA-Intel - HDA Intel PCH, recording] Pulseaudio fails to detect card
Public bug reported: After upgrading distribution pulseaudio only sees dummy output and no input ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:16:37 2020 InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Title: [HDA-Intel - HDA Intel PCH, recording] Pulseaudio fails to detect card UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1901946 Title: [HDA-Intel - HDA Intel PCH, recording] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: After upgrading distribution pulseaudio only sees dummy output and no input ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:16:37 2020 InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Title: [HDA-Intel - HDA Intel PCH, recording] Pulseaudio fails to detect card UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901946/+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 1901947] Re: Xorg freeze
Correction, I installed nvidia-455 driver to try to solve the issue, not 550. -- 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/1901947 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I have a lenovo ideapad 330 with and intel and a nvidia card geforce1050. The nvidia driver was not used, no nvidia files in /dev, no output on nvidia-smi. The logs that you seee are from a boot with the intel GPU only otherwise I cannot boot to xorg by deselecting software chooses GPU on Bios. If I go to recovery mode a go into CLI I can see the card detected in ubuntu-devices and nvidia-smi. If I continue the boot process from there I get a black screen and gets stuck there. No splash screen. Black. When the boot process freezes I can still switch Caps lock and Num lock so it is not completely dead but I left it for 30 minutes and it doesn't move. The dots in the spash screen (plymouth) stop after a minute and that's it. This behaviour was happening with 20.04 LTS so I upgraded to the new gorilla thing one and no changes except that pulseaudio now crashes and there is no sound input or output. 1 last point, I do not see any drivers in Additional drivers in the software center when I get to boot to xorg succesfully with Intel only GPU. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:20:51 2020 DistUpgraded: 2020-10-28 19:08:21,380 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.23.04, 5.4.0-52-generic, x86_64: installed nvidia, 455.23.04, 5.8.0-26-generic, x86_64: installed virtualbox, 6.1.14, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb] InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b629 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 002: ID 03f0:0941 HP, Inc X500 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=cddaf19f-5264-46b1-9acb-11810749ed99 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1901947/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/
[Touch-packages] [Bug 1901947] [NEW] Xorg freeze
Public bug reported: I have a lenovo ideapad 330 with and intel and a nvidia card geforce1050. The nvidia driver was not used, no nvidia files in /dev, no output on nvidia-smi. The logs that you seee are from a boot with the intel GPU only otherwise I cannot boot to xorg by deselecting software chooses GPU on Bios. If I go to recovery mode a go into CLI I can see the card detected in ubuntu-devices and nvidia-smi. If I continue the boot process from there I get a black screen and gets stuck there. No splash screen. Black. When the boot process freezes I can still switch Caps lock and Num lock so it is not completely dead but I left it for 30 minutes and it doesn't move. The dots in the spash screen (plymouth) stop after a minute and that's it. This behaviour was happening with 20.04 LTS so I upgraded to the new gorilla thing one and no changes except that pulseaudio now crashes and there is no sound input or output. 1 last point, I do not see any drivers in Additional drivers in the software center when I get to boot to xorg succesfully with Intel only GPU. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:20:51 2020 DistUpgraded: 2020-10-28 19:08:21,380 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.23.04, 5.4.0-52-generic, x86_64: installed nvidia, 455.23.04, 5.8.0-26-generic, x86_64: installed virtualbox, 6.1.14, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb] InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b629 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 002: ID 03f0:0941 HP, Inc X500 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=cddaf19f-5264-46b1-9acb-11810749ed99 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze groovy possible-manual-nvidia-install third-party-packages 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/1901947 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I have a lenovo ideapad 330 with and intel and a nvidia card geforce1050. The nvidia driver was not used, no nvidia files in /dev, no output on nvidia-smi. The logs that you seee are from a boot with the intel GPU only otherwise I cannot boot to xorg by deselecting software chooses
[Touch-packages] [Bug 1901954] [NEW] Bluetooth sound card not detected
Public bug reported: Uso o Ubuntu 20.04, e por algum motibo meu fone de ouvido Beats Dr.dree nao parea com o bluetooth. Uso o Ubuntu baixado direto do site nao fiz nenhuma alteração relevante, mesmo assim o bluetooth nao funciona especificamente com o Beats Studio3 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inuyasha 1106 F pulseaudio /dev/snd/controlC0: inuyasha 1106 F pulseaudio /dev/snd/pcmC0D0p: inuyasha 1106 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 18:08:17 2020 InstallationDate: Installed on 2020-10-24 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2012 dmi.bios.vendor: Copyright Itautec S.A. ST 4273 dmi.bios.version: F2N BI-SL2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ST 4273 dmi.board.vendor: Itautec S.A. dmi.board.version: ST-4273 Custom 01(Itau-Unibanco) dmi.chassis.type: 3 dmi.chassis.vendor: Itautec S.A. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnCopyrightItautecS.A.ST4273:bvrF2NBI-SL2:bd12/24/2012:svnItautecS.A.:pnInfowayST-4273:pvrCorp:rvnItautecS.A.:rnST4273:rvrST-4273Custom01(Itau-Unibanco):cvnItautecS.A.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Infoway ST-4273 dmi.product.sku: 40071191 dmi.product.version: Corp dmi.sys.vendor: Itautec S.A. ** 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/1901954 Title: Bluetooth sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Uso o Ubuntu 20.04, e por algum motibo meu fone de ouvido Beats Dr.dree nao parea com o bluetooth. Uso o Ubuntu baixado direto do site nao fiz nenhuma alteração relevante, mesmo assim o bluetooth nao funciona especificamente com o Beats Studio3 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inuyasha 1106 F pulseaudio /dev/snd/controlC0: inuyasha 1106 F pulseaudio /dev/snd/pcmC0D0p: inuyasha 1106 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 18:08:17 2020 InstallationDate: Installed on 2020-10-24 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2012 dmi.bios.vendor: Copyright Itautec S.A. ST 4273 dmi.bios.version: F2N BI-SL2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ST 4273 dmi.board.vendor: Itautec S.A. dmi.board.version: ST-4273 Custom 01(Itau-Unibanco) dmi.chassis.type: 3 dmi.chassis.vendor: Itautec S.A. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnCopyrightItautecS.A.ST4273:bvrF2NBI-SL2:bd12/24/2012:svnItautecS.A.:pnInfowayST-4273:pvrCorp:rvnItautecS.A.:rnST4273:rvrST-4273Custom01(Itau-Unibanco):cvnItautecS.A.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Infoway ST-4273 dmi.product.sku: 40071191 dmi.product.version: Corp dmi.sys.vendor: Itautec S.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901954/+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 1898869] Re: System slow on booting
a) On theory it compromises the throughput (the whole CPU time that will take for a process to finish will be longer) for better responsiveness, even under high load. So mouse clicks/UI events should be handled faster and say, when decompressing large files or other CPU load by specific process the user interface should not freeze. b) I'll have to look at this and maybe report a bug somewhere. I should really get used to checking the logs more frequently. c) I'll also have to investigate this, but maybe it's because i have overridden the DNS address to be used from the default one and dnscrypt- proxy hasn't started yet, plus systemd-resolved listening on a different port than the used one. d) I have removed it, thanks! I can't speak with the numbers, it might have been a little bit faster, but it was noticeably slower than Windows. -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+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 1901020] Re: new upstream release 2020d
Groovy verification of tzdata using Fiji: bdmurray@clean-groovy-amd64:~$ zdump -v Pacific/Fiji | grep 2020 Pacific/Fiji Sat Jan 11 13:59:59 2020 UT = Sun Jan 12 02:59:59 2020 +13 isdst=1 gmtoff=46800 Pacific/Fiji Sat Jan 11 14:00:00 2020 UT = Sun Jan 12 02:00:00 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Nov 7 13:59:59 2020 UT = Sun Nov 8 01:59:59 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Nov 7 14:00:00 2020 UT = Sun Nov 8 03:00:00 2020 +13 isdst=1 gmtoff=46800 bdmurray@clean-groovy-amd64:~$ sudo apt-get install tzdata Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: tzdata 1 upgraded, 0 newly installed, 0 to remove and 348 not upgraded. Need to get 0 B/293 kB of archives. After this operation, 0 B of additional disk space will be used. Preconfiguring packages ... (Reading database ... 190075 files and directories currently installed.) Preparing to unpack .../tzdata_2020d-1ubuntu1_all.deb ... Unpacking tzdata (2020d-1ubuntu1) over (2020b-1ubuntu1) ... Setting up tzdata (2020d-1ubuntu1) ... Current default time zone: 'America/Los_Angeles' Local time is now: Wed Oct 28 15:27:00 PDT 2020. Universal Time is now: Wed Oct 28 22:27:00 UTC 2020. Run 'dpkg-reconfigure tzdata' if you wish to change it. bdmurray@clean-groovy-amd64:~$ zdump -v Pacific/Fiji | grep 2020 Pacific/Fiji Sat Jan 11 13:59:59 2020 UT = Sun Jan 12 02:59:59 2020 +13 isdst=1 gmtoff=46800 Pacific/Fiji Sat Jan 11 14:00:00 2020 UT = Sun Jan 12 02:00:00 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Dec 19 13:59:59 2020 UT = Sun Dec 20 01:59:59 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Dec 19 14:00:00 2020 UT = Sun Dec 20 03:00:00 2020 +13 isdst=1 gmtoff=46800 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: In Progress Status in tzdata source package in Trusty: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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 1901020] Re: new upstream release 2020d
On Groovy using python3-icu to verify the same change but for the bundled icu-data: bdmurray@clean-groovy-amd64:~$ python3 -c "from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Fiji')); print(str(tz.utcoffset(datetime(2020, 11, 10" 13:00:00 bdmurray@clean-groovy-amd64:~$ sudo apt-get install tzdata Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: tzdata 1 upgraded, 0 newly installed, 0 to remove and 348 not upgraded. Need to get 0 B/293 kB of archives. After this operation, 0 B of additional disk space will be used. Preconfiguring packages ... (Reading database ... 190075 files and directories currently installed.) Preparing to unpack .../tzdata_2020d-1ubuntu1_all.deb ... Unpacking tzdata (2020d-1ubuntu1) over (2020b-1ubuntu1) ... Setting up tzdata (2020d-1ubuntu1) ... Current default time zone: 'America/Los_Angeles' Local time is now: Wed Oct 28 15:35:35 PDT 2020. Universal Time is now: Wed Oct 28 22:35:35 UTC 2020. Run 'dpkg-reconfigure tzdata' if you wish to change it. bdmurray@clean-groovy-amd64:~$ python3 -c "from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Fiji')); print(str(tz.utcoffset(datetime(2020, 11, 10" 12:00:00 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: In Progress Status in tzdata source package in Trusty: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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 1901020] Re: new upstream release 2020d
** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: In Progress Status in tzdata source package in Trusty: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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 1901020] Re: new upstream release 2020d
Focal verification: bdmurray@clean-focal-amd64:~$ apt-cache policy tzdata tzdata: Installed: 2020a-0ubuntu0.20.04 Candidate: 2020a-0ubuntu0.20.04 Version table: *** 2020a-0ubuntu0.20.04 500 500 http://192.168.10.7/ubuntu focal-updates/main amd64 Packages 500 http://192.168.10.7/ubuntu focal-updates/main i386 Packages 500 http://192.168.10.7/ubuntu focal-security/main amd64 Packages 500 http://192.168.10.7/ubuntu focal-security/main i386 Packages 100 /var/lib/dpkg/status 2019c-3ubuntu1 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages 500 http://192.168.10.7/ubuntu focal/main i386 Packages bdmurray@clean-focal-amd64:~$ zdump -v Pacific/Fiji | grep 2020 Pacific/Fiji Sat Jan 11 13:59:59 2020 UT = Sun Jan 12 02:59:59 2020 +13 isdst=1 gmtoff=46800 Pacific/Fiji Sat Jan 11 14:00:00 2020 UT = Sun Jan 12 02:00:00 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Nov 7 13:59:59 2020 UT = Sun Nov 8 01:59:59 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Nov 7 14:00:00 2020 UT = Sun Nov 8 03:00:00 2020 +13 isdst=1 gmtoff=46800 bdmurray@clean-focal-amd64:~$ python3 -c "from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Fiji')); print(str(tz.utcoffset(datetime(2020, 11, 10" 13:00:00 bdmurray@clean-focal-amd64:~$ apt-cache policy tzdata tzdata: Installed: 2020d-0ubuntu0.20.04 Candidate: 2020d-0ubuntu0.20.04 Version table: *** 2020d-0ubuntu0.20.04 500 500 http://192.168.10.7/ubuntu focal-proposed/main amd64 Packages 500 http://192.168.10.7/ubuntu focal-proposed/main i386 Packages 100 /var/lib/dpkg/status 2020a-0ubuntu0.20.04 500 500 http://192.168.10.7/ubuntu focal-updates/main amd64 Packages 500 http://192.168.10.7/ubuntu focal-updates/main i386 Packages 500 http://192.168.10.7/ubuntu focal-security/main amd64 Packages 500 http://192.168.10.7/ubuntu focal-security/main i386 Packages 2019c-3ubuntu1 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages 500 http://192.168.10.7/ubuntu focal/main i386 Packages bdmurray@clean-focal-amd64:~$ zdump -v Pacific/Fiji | grep 2020 Pacific/Fiji Sat Jan 11 13:59:59 2020 UT = Sun Jan 12 02:59:59 2020 +13 isdst=1 gmtoff=46800 Pacific/Fiji Sat Jan 11 14:00:00 2020 UT = Sun Jan 12 02:00:00 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Dec 19 13:59:59 2020 UT = Sun Dec 20 01:59:59 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Dec 19 14:00:00 2020 UT = Sun Dec 20 03:00:00 2020 +13 isdst=1 gmtoff=46800 bdmurray@clean-focal-amd64:~$ python3 -c "from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Fiji')); print(str(tz.utcoffset(datetime(2020, 11, 10" 12:00:00 Confirming that SystemV is still good: diff <(zdump -v America/Phoenix | cut -d\ -f2-) <(zdump -v SystemV/MST7 | cut -d\ -f2-) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: In Progress Status in tzdata source package in Trusty: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+
[Touch-packages] [Bug 1901020] Re: new upstream release 2020d
Verification on Bionic: bdmurray@clean-bionic-amd64:~$ apt list tzdata Listing... Done tzdata/bionic-updates,bionic-updates,bionic-security,bionic-security,now 2020a-0ubuntu0.18.04 all [installed,automatic] N: There is 1 additional version. Please use the '-a' switch to see it bdmurray@clean-bionic-amd64:~$ zdump -v Pacific/Fiji | grep 2020 Pacific/Fiji Sat Jan 11 13:59:59 2020 UT = Sun Jan 12 02:59:59 2020 +13 isdst=1 gmtoff=46800 Pacific/Fiji Sat Jan 11 14:00:00 2020 UT = Sun Jan 12 02:00:00 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Nov 7 13:59:59 2020 UT = Sun Nov 8 01:59:59 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Nov 7 14:00:00 2020 UT = Sun Nov 8 03:00:00 2020 +13 isdst=1 gmtoff=46800 bdmurray@clean-bionic-amd64:~$ python3 -c "from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Fiji')); print(str(tz.utcoffset(datetime(2020, 11, 10" 13:00:00 bdmurray@clean-bionic-amd64:~$ apt list tzdata Listing... Done tzdata/bionic-proposed,bionic-proposed,now 2020d-0ubuntu0.18.04 all [installed] N: There are 2 additional versions. Please use the '-a' switch to see them. bdmurray@clean-bionic-amd64:~$ zdump -v Pacific/Fiji | grep 2020 Pacific/Fiji Sat Jan 11 13:59:59 2020 UT = Sun Jan 12 02:59:59 2020 +13 isdst=1 gmtoff=46800 Pacific/Fiji Sat Jan 11 14:00:00 2020 UT = Sun Jan 12 02:00:00 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Dec 19 13:59:59 2020 UT = Sun Dec 20 01:59:59 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Dec 19 14:00:00 2020 UT = Sun Dec 20 03:00:00 2020 +13 isdst=1 gmtoff=46800 bdmurray@clean-bionic-amd64:~$ python3 -c "from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.create TimeZone('Pacific/Fiji')); print(str(tz.utcoffset(datetime(2020, 11, 10" 13:00:00 Actually the icu-data info didn't change - this needs investigating. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: In Progress Status in tzdata source package in Trusty: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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 1901020] Re: new upstream release 2020d
Actually icu-data isn't bundled with tzdata in Bionic so that's all good! Confirming that SystemV is still good: bdmurray@clean-bionic-amd64:~$ diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) bdmurray@clean-bionic-amd64:~$ ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: In Progress Status in tzdata source package in Trusty: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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 1901020] Re: new upstream release 2020d
Verifying for Xenial: bdmurray@clean-xenial-amd64:~$ apt list tzdata Listing... Done tzdata/xenial-updates,xenial-updates,xenial-security,xenial-security,now 2020a-0ubuntu0.16.04 all [installed] N: There is 1 additional version. Please use the '-a' switch to see it bdmurray@clean-xenial-amd64:~$ zdump -v Pacific/Fiji | grep 2020 Pacific/Fiji Sat Jan 11 13:59:59 2020 UT = Sun Jan 12 02:59:59 2020 +13 isdst=1 gmtoff=46800 Pacific/Fiji Sat Jan 11 14:00:00 2020 UT = Sun Jan 12 02:00:00 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Nov 7 13:59:59 2020 UT = Sun Nov 8 01:59:59 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Nov 7 14:00:00 2020 UT = Sun Nov 8 03:00:00 2020 +13 isdst=1 gmtoff=46800 bdmurray@clean-xenial-amd64:~$ apt list tzdata Listing... Done tzdata/xenial-proposed,xenial-proposed,now 2020d-0ubuntu0.16.04 all [installed] N: There are 2 additional versions. Please use the '-a' switch to see them. bdmurray@clean-xenial-amd64:~$ zdump -v Pacific/Fiji | grep 2020 Pacific/Fiji Sat Jan 11 13:59:59 2020 UT = Sun Jan 12 02:59:59 2020 +13 isdst=1 gmtoff=46800 Pacific/Fiji Sat Jan 11 14:00:00 2020 UT = Sun Jan 12 02:00:00 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Dec 19 13:59:59 2020 UT = Sun Dec 20 01:59:59 2020 +12 isdst=0 gmtoff=43200 Pacific/Fiji Sat Dec 19 14:00:00 2020 UT = Sun Dec 20 03:00:00 2020 +13 isdst=1 gmtoff=46800 And SystemV stuff: bdmurray@clean-xenial-amd64:~$ diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) bdmurray@clean-xenial-amd64:~$ ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: In Progress Status in tzdata source package in Trusty: In Progress Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+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 1895008] Re: software updater removes realtek r8125 driver and installs incorrect r8169 driver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed -- 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/1895008 Title: software updater removes realtek r8125 driver and installs incorrect r8169 driver Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Release: Ubuntu 18.04.5 LTS Package: Software Updater I have a "MSI MPG B550 Gaming Edge Wifi" motherboard which requires Realtek Driver r8125. When the weekly update runs, it automatically replaces the correct driver with version r8169. This causes the Ethernet connection to not work at all. Fix: Manually remove r8169 driver and reinstall the Realtek r8125 driver downloaded from Realtek website. Additionally, I have tried to blacklist the r8169 driver in /etc/modprobe.d/blacklist.conf as # Blacklist bad ethernet driver blacklist r8169 This caused the updater to remove the r8125 driver, but not replace it with anything (as far as I can tell). There are no files under /var/log/dist-upgrade (directory is empty). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1895008/+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 1896073] Re: SRU the current 2.3.6 stable update
Hello Sebastien, or anyone else affected, Accepted tracker into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tracker/2.3.6-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1896073 Title: SRU the current 2.3.6 stable update Status in tracker package in Ubuntu: Fix Released Status in tracker source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS The update add a 'tracker export' command, that's new and not used into any integration so has no real regression potential. It's an optional new option that can be used to export the data to migrate them to the incoming tracker3. * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that file search works correctly from the command line, shell and nautilus * Regression potential There is no specific change or feature to test in that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861358] Re: tracker search hangs and never returns results
Hello Christoph, or anyone else affected, Accepted tracker into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tracker/2.3.6-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tracker (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1861358 Title: tracker search hangs and never returns results Status in tracker package in Ubuntu: Fix Released Status in tracker source package in Focal: Fix Committed Bug description: * Impact the tracker search utility isn't working * Test case $ tracker search something it should return results if there are any matching items * regression potential it's a build flag change, just check that the tracker search works including in the desktop and nautilus -- When I run $ tracker search -f Bruni I see the following output on console - (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot register existing type 'TrackerLanguage' (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot add private field to invalid (non-instantiatable) type '' (tracker search:2): GLib-CRITICAL **: 00:31:10.761: g_once_init_leave: assertion 'result != 0' failed (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed - The program hangs and never returns. Sending Control-C brings me back to prompt ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.3.0-1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 30 00:31:59 2020 ExecutablePath: /usr/bin/tracker InstallationDate: Installed on 2016-11-05 (1180 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1861358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp