[Touch-packages] [Bug 1868332] Re: Scrolling jumps after switching tabs
** Package changed: ubuntu => xorg (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/1868332 Title: Scrolling jumps after switching tabs Status in xorg package in Ubuntu: New Bug description: The bug has to do with mouse scrolling and switching windows; I do not know which package it is part of. The problem arises when I have two windows of two different applications open, such as Google Chrome and a text editor. To reproduce the error, I have Google Chrome open initially, then I switch tabs (using the shortcut Alt-Tab) to the text editor, then scroll around on the text editor. When I Alt-Tab back to Google Chrome, my first scroll leads to the page jumping by a large amount either up or down before resuming regular mouse scrolling. It is only this initial scroll after switching tabs that jumps like this. It also happens regardless of whether I use a mouse or the touch pad. I also notice, given the same scenario, if I scroll up on the text editor, the Google Chrome initial scroll jump will be upward. If I scroll down on the text editor, the Chrome jump will be downward. If I scroll a lot in the text editor, the Chrome jump will be large. If I scroll a small amount in the text editor, the Chrome jump will be small. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 17:17:39 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9] InstallationDate: Installed on 2020-01-26 (54 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: AMI dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 1WU65AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868332/+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 1868332] [NEW] Scrolling jumps after switching tabs
You have been subscribed to a public bug: The bug has to do with mouse scrolling and switching windows; I do not know which package it is part of. The problem arises when I have two windows of two different applications open, such as Google Chrome and a text editor. To reproduce the error, I have Google Chrome open initially, then I switch tabs (using the shortcut Alt-Tab) to the text editor, then scroll around on the text editor. When I Alt-Tab back to Google Chrome, my first scroll leads to the page jumping by a large amount either up or down before resuming regular mouse scrolling. It is only this initial scroll after switching tabs that jumps like this. It also happens regardless of whether I use a mouse or the touch pad. I also notice, given the same scenario, if I scroll up on the text editor, the Google Chrome initial scroll jump will be upward. If I scroll down on the text editor, the Chrome jump will be downward. If I scroll a lot in the text editor, the Chrome jump will be large. If I scroll a small amount in the text editor, the Chrome jump will be small. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 17:17:39 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9] InstallationDate: Installed on 2020-01-26 (54 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: AMI dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 1WU65AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- Scrolling jumps after switching tabs https://bugs.launchpad.net/bugs/1868332 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864992] Autopkgtest regression report (kmod/24-1ubuntu3.3)
All autopkgtests for the newly accepted kmod (24-1ubuntu3.3) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.39 (i386) linux-hwe-5.0/5.0.0-44.48~18.04.1 (armhf) ipset/6.34-1 (ppc64el, s390x, amd64, i386, arm64) chrony/3.2-4ubuntu4.2 (ppc64el, s390x, amd64, armhf, i386, arm64) 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/bionic/update_excuses.html#kmod [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 kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864992 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Bionic: Fix Committed Status in kmod source package in Disco: Won't Fix Status in kmod source package in Eoan: Fix Committed Status in kmod source package in Focal: Fix Released Bug description: [Impact] * There is no impact to the end user but spurious error messages (tons of them) causing the perception that something really bad happened: Example of one of those tons of messages: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' [Test Case] * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin * sudo depmod -a -F /boot/System.map-$(uname -r) This will cause the spurious error messages because depmod -a -F won't have the "modules.builtin.bin" file created. This is a simulation of what the linux-modules postinst package does and an example of why the messages happen. [Regression Potential] * We are reverting a debian patch so we will be closer to upstream code base. * the change is about 2 different priority changes on verbosity, so biggest problem would be extra (or fewer) stdout/stderr messages (for scripts relying on them, for example). * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed to work fine. [Other Info] * Original Description: During a Focal install from the ISO image several errors like: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' are logged in curtin's install logs. The installed system boots and works fine, but the error is clearly something we want to get rid of. At first glance this seems related to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261 but the version of initramfs-tools in both the installer and installed system (checked with `chroot /target dpkg -l initramfs-tools` during the installation) is 0.136ubuntu1, which should contain Rafael's fix for that bug. I wonder if the update-initramfs diversion has a role here. I verified this happens at least on amd64 and arm64. I'm attaching the full install logs for a amd64 installation. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperVersion: 1.439 DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU
[Touch-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Hi Kai Heng Feng, Sorry for delaying this for long. I already check and it already enable but in log file still not. I think there is something not meet with the configuration. Please see log file. Thanks and regards, ** Attachment added: "prevboot4.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860754/+attachment/5339588/+files/prevboot4.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/linux/+bug/1860754/+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 1853383] Re: autopkgtest regression in test_add_proc_info
** Changed in: apport (Ubuntu Disco)
Status: New => Won't Fix
--
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/1853383
Title:
autopkgtest regression in test_add_proc_info
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Xenial:
New
Status in apport source package in Bionic:
New
Status in apport source package in Disco:
Won't Fix
Status in apport source package in Eoan:
New
Bug description:
The security uploads for apport (2.20.11-0ubuntu8.2 for eoan,
2.20.10-0ubuntu27.2 for disco, and 2.20.9-0ubuntu7.8 for bionic - and
maybe those for older releases as well) have caused the
test_add_proc_info test to start failing[1]. The pattern changed after
the subsequent uploads to fix a regression, but it still fails[2].
[1]
==
ERROR: test_add_proc_info (__main__.T)
add_proc_info().
--
Traceback (most recent call last):
File "./test_report.py", line 100, in test_add_proc_info
pr.add_proc_info(extraenv=['PWD'])
File "/usr/lib/python3/dist-packages/apport/report.py", line 550, in
add_proc_info
self.add_proc_environ(pid, extraenv)
File "/usr/lib/python3/dist-packages/apport/report.py", line 619, in
add_proc_environ
env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in
_read_file
with open(path, 'rb', opener=lambda path, mode: os.open(path, mode,
dir_fd=dir_fd)) as fd:
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in
with open(path, 'rb', opener=lambda path, mode: os.open(path, mode,
dir_fd=dir_fd)) as fd:
TypeError: argument should be integer or None, not list
[2]
==
ERROR: test_add_proc_info (__main__.T)
add_proc_info().
--
Traceback (most recent call last):
File "./test_report.py", line 210, in test_add_proc_info
self.assertRaises(ValueError, pr.add_proc_info, p.pid)
File "/usr/lib/python3.7/unittest/case.py", line 743, in assertRaises
return context.handle('assertRaises', args, kwargs)
File "/usr/lib/python3.7/unittest/case.py", line 178, in handle
callable_obj(*args, **kwargs)
File "/usr/lib/python3/dist-packages/apport/report.py", line 544, in
add_proc_info
proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH |
os.O_DIRECTORY)
FileNotFoundError: [Errno 2] No such file or directory: '/proc/1899'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1853383/+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 1861446] Re: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts
** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu) -- 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/1861446 Title: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Bug description: Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The issue was filed against linux-signed-5.4 (Ubuntu) rather than linux (Ubuntu), and none of the logs usually included with kernel bug reports were included. After the bug was changed from linux-signed-5.4 to linux, I was prompted to run apport-collect by the kernel team's triagebot and that worked successfully: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity My guess is that apport needs to be updated to understand a change in kernel packaging. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu16 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashReports: 640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash 600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash 640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash Date: Thu Jan 30 18:44:47 2020 PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861446/+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 1717991] Re: file returns "name use count (30) exceeded"
FTR this was fixed upstream by bumping the default name recursion level from 30 to 50: https://bugs.astron.com/view.php?id=152 status fixcommitted ** Bug watch added: bugs.astron.com/ #152 https://bugs.astron.com/view.php?id=152 ** Changed in: file (Ubuntu) Status: Invalid => Confirmed ** Changed in: file (Debian) Status: Invalid => Fix Committed ** Changed in: file (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1717991 Title: file returns "name use count (30) exceeded" Status in file package in Ubuntu: Fix Committed Status in file package in Debian: Fix Committed Bug description: In Ubuntu 17.04 there seems to be a problem with "file": $ file test.jpg test.jpg: ERROR: JPEG image data, JFIF standard 1.01, resolution (DPI), density 240x240, segment length 16, Exif Standard: [TIFF image data, big-endian, direntries=8, description=Picture saved with settings embedded., orientation=upper-left, xresolution=148, yresolution=156, resolutionunit=2, software=Adobe Photoshop Lightroom 6.1.1 (Windows), datetime=2017:08:17 11:16:47] name use count (30) exceeded This problem was reported in Fedora a couple of years ago: https://bugzilla.redhat.com/show_bug.cgi?id=1201630 I found out about the problem when the Astrometry program suddenly stopped working on jpegs that it was previously able to process. I cannot say how "file" is supposed to normally output the data. I only found out about this when the program suddenly broke without any obvious reason after the upgrade from Ubuntu 16.04 to 17.04. Since there is another case reported for Fedora I tend to believe that the problem is indeed caused by "file". The required data: $ lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 $ apt-cache policy file file: Installed: 1:5.29-3ubuntu0.1 Candidate: 1:5.29-3ubuntu0.1 Version table: *** 1:5.29-3ubuntu0.1 500 500 http://fi.archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:5.29-3 500 500 http://fi.archive.ubuntu.com/ubuntu zesty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: file 1:5.29-3ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: sep4_0 socperf2_0 pax ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Sep 18 20:36:35 2017 InstallationDate: Installed on 2016-01-18 (609 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1717991/+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 1851542] Re: autopkgtest fails due to aspell SRU
** Tags removed: verification-needed
--
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/1851542
Title:
autopkgtest fails due to aspell SRU
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
Fix Released
Status in apport source package in Disco:
Won't Fix
Status in apport source package in Eoan:
Fix Released
Status in apport source package in Focal:
Fix Released
Bug description:
[Impact]
A new autopkgtest test regression began appearing after (and due to) an
aspell SRU.
==
FAIL: test_install_packages_versioned (__main__.T)
install_packages() with versions and with cache
--
Traceback (most recent call last):
File "./test_backend_apt_dpkg.py", line 557, in
test_install_packages_versioned
self.assertIn(result, 'aspell-doc version 1.1 required, but
0.60.7~20110707-3build1 is available\n')
AssertionError: 'aspell-doc version 1.1 required, but
0.60.7~20110707-3ubuntu0.1 is available\n' not found in 'aspell-doc version 1.1
required, but 0.60.7~20110707-3build1 is available\n'
--
Ran 37 tests in 191.123s
FAILED (failures=1)
[Test Case]
## From within autopkgtest source package, with autopkgtest deps installed
## This is a slightly modified version if debian/tests/upstream-system
# do not run in the source tree, as we want to check the system-installed
# apport
TESTDIR=${ADTTMP:-/tmp}/apport-tests
mkdir -p $TESTDIR
cp test/test_* test/run "$TESTDIR"
cd "$TESTDIR"
# clean up old crash reports
rm -rf /var/crash/*
export GNUPGHOME=$TESTDIR/gnupg
mkdir -m 700 $GNUPGHOME
./run backend_apt_dpkg
[Fix]
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2717
[Regression Risk]
Code is restricted to a test that is only ran via autopkgtest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851542/+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 1866996] Re: apport-retrace sandbox can not be used with https mirrors in sources.list
This bug was fixed in the package apport - 2.20.11-0ubuntu21 --- apport (2.20.11-0ubuntu21) focal; urgency=medium [ Brian Murray ] * backends/packaging-apt-dpkg.py: allow mirrors which are accessed via https in sources.list. Thanks to Launchpad user Esokrates for the fix. (LP: #1866996) * backends/packaging-apt-dpkg.py: when downloading packages from Launchpad do not require them to be authenticated. * test/test_backend_apt_dpkg.py: Fix check for connectivity and modify install from PPA test for a change in the PPA being tested. [ Matthieu Clemenceau ] * test/test_ui.py: Removed linux package version to fix autopkgtest with focal. Changed linux-5.4 and linux-signed-5.4 to linux and linux-signed -- Brian Murray Thu, 12 Mar 2020 15:46:30 -0700 ** Changed in: apport (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866996 Title: apport-retrace sandbox can not be used with https mirrors in sources.list Status in Apport: Triaged Status in apport package in Ubuntu: Fix Released Bug description: If /etc/apt/sources.list only contains https mirrors (and not a single http:// entry), then apport-retrace fails to determine the default mirror: apport-retrace -v -s -R -S system ./crash/_usr_bin_gnome-shell.1000.crash Ign http://ddebs.ubuntu.com focal InRelease Get:1 http://ppa.launchpad.net/saiarcot895/chromium-dev/ubuntu focal InRelease [20.8 kB] Get:2 http://ddebs.ubuntu.com focal Release [34.7 kB] Get:3 https://mirror.init7.net/ubuntu focal InRelease [255 kB] Get:4 http://ddebs.ubuntu.com focal Release.gpg [819 B] Get:5 http://ddebs.ubuntu.com focal/main amd64 Packages [526 kB] Get:6 http://ppa.launchpad.net/saiarcot895/chromium-dev/ubuntu focal/main amd64 Packages [1604 B] Get:7 https://mirror.init7.net/ubuntu focal-updates InRelease [79.7 kB] Get:8 http://ppa.launchpad.net/saiarcot895/chromium-dev/ubuntu focal/main Translation-en [1084 B] Get:9 https://mirror.init7.net/ubuntu focal-backports InRelease [79.7 kB] Get:10 https://mirror.init7.net/ubuntu focal-security InRelease [79.7 kB] Get:11 https://mirror.init7.net/ubuntu focal/multiverse Sources [175 kB] Get:12 http://ddebs.ubuntu.com focal/universe amd64 Packages [4435 kB] Get:13 https://mirror.init7.net/ubuntu focal/restricted Sources [7032 B] Get:14 https://mirror.init7.net/ubuntu focal/universe Sources [9784 kB] Get:15 http://ddebs.ubuntu.com focal/multiverse amd64 Packages [67.0 kB] Get:16 https://mirror.init7.net/ubuntu focal/main Sources [839 kB] Get:17 https://mirror.init7.net/ubuntu focal/main amd64 Packages [976 kB] Get:18 https://mirror.init7.net/ubuntu focal/main Translation-en [503 kB] Get:19 https://mirror.init7.net/ubuntu focal/main amd64 DEP-11 Metadata [517 kB] Get:20 https://mirror.init7.net/ubuntu focal/main DEP-11 48x48 Icons [93.7 kB] Get:21 https://mirror.init7.net/ubuntu focal/main DEP-11 64x64 Icons [164 kB] Get:22 https://mirror.init7.net/ubuntu focal amd64 Contents (deb) [41.2 MB] Get:23 https://mirror.init7.net/ubuntu focal/restricted amd64 Packages [21.5 kB] Get:24 https://mirror.init7.net/ubuntu focal/restricted Translation-en [6136 B] Get:25 https://mirror.init7.net/ubuntu focal/universe amd64 Packages [8623 kB] Get:26 https://mirror.init7.net/ubuntu focal/universe Translation-en [5154 kB] Get:27 https://mirror.init7.net/ubuntu focal/universe amd64 DEP-11 Metadata [3619 kB] Get:28 https://mirror.init7.net/ubuntu focal/universe DEP-11 48x48 Icons [3005 kB] Get:29 https://mirror.init7.net/ubuntu focal/universe DEP-11 64x64 Icons [7981 kB] Get:30 https://mirror.init7.net/ubuntu focal/multiverse amd64 Packages [145 kB] Get:31 https://mirror.init7.net/ubuntu focal/multiverse Translation-en [105 kB] Get:32 https://mirror.init7.net/ubuntu focal/multiverse amd64 DEP-11 Metadata [45.0 kB] Get:33 https://mirror.init7.net/ubuntu focal/multiverse DEP-11 48x48 Icons [17.6 kB] Get:34 https://mirror.init7.net/ubuntu focal/multiverse DEP-11 64x64 Icons [195 kB] Fetched 88.8 MB in 6s (1341 kB/s) Fetched 0 B in 0s (0 B/s) Extracting downloaded debs... Traceback (most recent call last): File "/usr/bin/apport-retrace", line 322, in sandbox, cache, outdated_msg = apport.sandboxutils.make_sandbox( File "/usr/lib/python3/dist-packages/apport/sandboxutils.py", line 220, in make_sandbox pkgs = needed_runtime_packages(report, sandbox_dir, pkgmap_cache_dir, pkg_versions,
[Touch-packages] [Bug 1854237] Re: autopkgtests fail after security fixes
** Changed in: apport (Ubuntu Disco) Status: New => Won't Fix -- 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/1854237 Title: autopkgtests fail after security fixes Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Released Status in apport source package in Bionic: Fix Released Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: Fix Released Bug description: The following autopkgtests fail after the recent security fixes: log:FAIL: test_get_logind_session (__main__.T) log:FAIL: test_core_dump_packaged (__main__.T) log:FAIL: test_core_dump_unpackaged (__main__.T) log:FAIL: test_crash_setuid_drop (__main__.T) log:FAIL: test_crash_setuid_keep (__main__.T) log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T) log:FAIL: test_lock_symlink (__main__.T) test_get_logind_session is a test failing to keep up with an API change. test_core_dump_* is failures to remove partly written core files. Both of these are easy fixes, I'll have a MP for them soon. test_crash_setuid_* are caused by the dropping of privileges when accessing the crashing process's /proc. They seem to be testing behaviour now explicitly forbidden by the fix to be honest! test_lock_symlink fails because the lock file is now always in /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could update the test, but is it really worth it after the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1854237/+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 1860544] Re: package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1
Same issue here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1860544 Title: package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 Status in util-linux package in Ubuntu: Confirmed Bug description: during update, the updater sent this message ProblemType: Package DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Jan 22 13:12:14 2020 ErrorMessage: installed uuid-runtime package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-01 (964 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: util-linux Title: package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-10-22 (91 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1860544/+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 1868353] [NEW] regression: Bose SL III works in bionic but not in focal
Public bug reported: blueman-manager successfully pairs and connects to the Bose SL III in both bionic and in focal. in bionic, the Bose SL III then immediately shows up in pavucontrol. in focal, it remains absent. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Fri Mar 20 19:53:54 2020 InstallationDate: Installed on 2020-03-15 (5 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1868353 Title: regression: Bose SL III works in bionic but not in focal Status in pulseaudio package in Ubuntu: New Bug description: blueman-manager successfully pairs and connects to the Bose SL III in both bionic and in focal. in bionic, the Bose SL III then immediately shows up in pavucontrol. in focal, it remains absent. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Fri Mar 20 19:53:54 2020 InstallationDate: Installed on 2020-03-15 (5 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868353/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Eddie, "When I plug in a headset with a mic in the 3.5mm port, it still seems to use the internal mic instead of that of the headset." What happens if you manually select usb headset from gnome-sound- setting->input devices. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1868319] Re: PCI/internal sound card not detected
5.3.0-42.34-generic has regression, please try with 5.3.0-43 kernel. -- 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/1868319 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+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 1868330] Re: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work
Please manually install alsa-ucm-conf package and reboot. This package will be put into the 20.04 image soon. -- 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/1868330 Title: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work Status in alsa-driver package in Ubuntu: New Bug description: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868330/+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 1868352] [NEW] grub2 2.04-1ubuntu12.2 breaks boot on some machines
Public bug reported: 2.04-1ubuntu12.2 broke boot on my machine. It doesn't work with kernels that don't have CONFIG_EFI_STUB=y configured. This really needs to fall back to the old mode if EFI handover is not supported by the kernel. Also, after using a kernel with CONFIG_EFI_STUB=y it still failed to boot one of my machines with root specified by UUID. I was able to workaround it by manually specifying the boot device with /dev/nvme0n1p2 at the grub menu, and then specifying GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.10-customskl x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Mar 20 21:19:01 2020 DistUpgraded: 2019-10-26 18:15:16,011 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.3, 5.5.10-customskl, x86_64: installed zfs, 0.8.3, 5.5.9-customskl, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:872f] InstallationDate: Installed on 2012-12-04 (2664 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.5.10-customskl root=/dev/nvme0n1p2 ro rootflags=subvol=@ drm_kms_helper.edid_firmware=DP-1:edid/monoprice_28_4k.edid SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-26 (146 days ago) dmi.bios.date: 10/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2203 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2203:bd10/07/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4~yasi1~19.10 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1~yasi1~19.10 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1~yasi1~19.10 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20191209.2226.f66d3954-0ubuntu0+yasi1~19.10 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan fonts kubuntu regression-update third-party-packages ubuntu ** Tags added: regression-update -- 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/1868352 Title: grub2 2.04-1ubuntu12.2 breaks boot on some machines Status in xorg package in Ubuntu: New Bug description: 2.04-1ubuntu12.2 broke boot on my machine. It doesn't work with kernels that don't have CONFIG_EFI_STUB=y configured. This really needs to fall back to the old mode if EFI handover is not supported by the kernel. Also, after using a kernel with CONFIG_EFI_STUB=y it still failed to boot one of my machines with root specified by UUID. I was able to workaround it by manually specifying the boot device with /dev/nvme0n1p2 at the grub menu, and then specifying GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.10-customskl x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Mar 20 21:19:01 2020 DistUpgraded: 2019-10-26 18:15:16,011 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.3, 5.5.10-customskl, x86_64: installed zfs, 0.8.3, 5.5.9-customskl, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop)
[Touch-packages] [Bug 1868335] [NEW] Sync colord 1.4.4-2 (main) from Debian unstable (main)
Public bug reported: Please sync colord 1.4.4-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * No-change rebuild with fixed binutils on arm64. * Omit colord-sensor-argyll on i386. The change to omit colord-sensor-argyll on i386 was adopted in Debian. Changelog entries since current focal version 1.4.4-1ubuntu2: colord (1.4.4-2) unstable; urgency=medium * Team upload. * Bump debhelper to 12 and install the daemons in /usr/libexec * debian/rules: Explicitly disable systemd and udev on non-linux architectures * debian/control: Bump Standards-Version to 4.5.0 (no further changes) * debian/control: Drop docbook-utils from build-dep, this doesn't seems necessary and add xsltproc instead * debian/control: Mark the -dev and gir packages as Multi-arch: same * Omit colord-sensor-argyll on Ubuntu/i386. Thanks to Steve Langasek (Closes: #948540) * debian/control: Set Rules-Requires-Root: no * debian/watch: Use https:// instead of http:// * d/p/tests-Make-the-build-reproductible.patch: Make the build reproductible * debian/gbp.conf: Set upstream-vcs-tag and make sure patches are not numbered -- Laurent Bigonville Fri, 20 Mar 2020 15:50:36 +0100 ** Affects: colord (Ubuntu) Importance: Wishlist Status: New ** Changed in: colord (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1868335 Title: Sync colord 1.4.4-2 (main) from Debian unstable (main) Status in colord package in Ubuntu: New Bug description: Please sync colord 1.4.4-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * No-change rebuild with fixed binutils on arm64. * Omit colord-sensor-argyll on i386. The change to omit colord-sensor-argyll on i386 was adopted in Debian. Changelog entries since current focal version 1.4.4-1ubuntu2: colord (1.4.4-2) unstable; urgency=medium * Team upload. * Bump debhelper to 12 and install the daemons in /usr/libexec * debian/rules: Explicitly disable systemd and udev on non-linux architectures * debian/control: Bump Standards-Version to 4.5.0 (no further changes) * debian/control: Drop docbook-utils from build-dep, this doesn't seems necessary and add xsltproc instead * debian/control: Mark the -dev and gir packages as Multi-arch: same * Omit colord-sensor-argyll on Ubuntu/i386. Thanks to Steve Langasek (Closes: #948540) * debian/control: Set Rules-Requires-Root: no * debian/watch: Use https:// instead of http:// * d/p/tests-Make-the-build-reproductible.patch: Make the build reproductible * debian/gbp.conf: Set upstream-vcs-tag and make sure patches are not numbered -- Laurent Bigonville Fri, 20 Mar 2020 15:50:36 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1868335/+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 1868331] Re: tracker-store crashed with SIGSEGV in tracker_data_commit_transaction()
*** This bug is a duplicate of bug 1843083 *** https://bugs.launchpad.net/bugs/1843083 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1843083, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1868331/+attachment/5339508/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339510/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339514/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339515/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339516/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339517/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339518/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1843083 tracker-store crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1868331 Title: tracker-store crashed with SIGSEGV in tracker_data_commit_transaction() Status in tracker package in Ubuntu: New Bug description: Error on boot ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: tracker 2.3.1-3build1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Mar 21 02:02:45 2020 ExecutablePath: /usr/lib/tracker/tracker-store ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: Segfault happened at: 0x55ea1dd73243:cmpq $0x0,0x8(%rdi) PC (0x55ea1dd73243) ok source "$0x0" ok destination "0x8(%rdi)" (0x0008) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: ?? () ?? () tracker_data_commit_transaction () from /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so ?? () from /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so ?? () Title: tracker-store crashed with SIGSEGV in tracker_data_commit_transaction() UpgradeStatus: Upgraded to focal on 2020-03-13 (7 days ago) UserGroups: adm cdrom dialout dip fax floppy lpadmin lxd plugdev sambashare sudo tape video separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1868331/+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 1868330] Re: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work
I've tried audacity and firefox too and no sound can be recorded. -- 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/1868330 Title: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work Status in alsa-driver package in Ubuntu: New Bug description: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868330/+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 1868330] [NEW] Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work
Public bug reported: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712 ** 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/1868330 Title: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work Status in alsa-driver package in Ubuntu: New Bug description: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available
[Touch-packages] [Bug 1868329] Re: ifupdown does not render viable /etc/network/interfaces on bionic ec2 cloud-images
** Description changed: Filing this bug for clarification and tracking on Ubuntu Bionic and later. Canonical cloudimages for Ec2 and other clouds leave an artifact that disables /etc/network/interface with the following content: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown In following the suggested text, installing the ifupdown deb continues to leave a broken system because ifupdown.postinst script creates an /etc/network/interfaces.d parts directory but does not write out a working /etc/network/interfaces file if the file exists on the system. This leaves a broken /etc/network/interfaces files which doesn't source /etc/network/interfaces.d/* and 3rd parties cannot use the interfaces.d parts directory to extend networking config. Cloud-init is one of those users of /etc/network/interfaces.d/ for rendering system networking on cloud images. Per LP: #1867029 + + I have attached ifupdwown-test.sh which exercises this issue on lxc by + mocking the CPC cloudimage artifact. ** Attachment added: "ifupdown-test.sh" https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1868329/+attachment/5339500/+files/ifupdown-test.sh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1868329 Title: ifupdown does not render viable /etc/network/interfaces on bionic ec2 cloud-images Status in ifupdown package in Ubuntu: New Bug description: Filing this bug for clarification and tracking on Ubuntu Bionic and later. Canonical cloudimages for Ec2 and other clouds leave an artifact that disables /etc/network/interface with the following content: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown In following the suggested text, installing the ifupdown deb continues to leave a broken system because ifupdown.postinst script creates an /etc/network/interfaces.d parts directory but does not write out a working /etc/network/interfaces file if the file exists on the system. This leaves a broken /etc/network/interfaces files which doesn't source /etc/network/interfaces.d/* and 3rd parties cannot use the interfaces.d parts directory to extend networking config. Cloud-init is one of those users of /etc/network/interfaces.d/ for rendering system networking on cloud images. Per LP: #1867029 I have attached ifupdwown-test.sh which exercises this issue on lxc by mocking the CPC cloudimage artifact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1868329/+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 1868329] [NEW] ifupdown does not render viable /etc/network/interfaces on bionic ec2 cloud-images
Public bug reported: Filing this bug for clarification and tracking on Ubuntu Bionic and later. Canonical cloudimages for Ec2 and other clouds leave an artifact that disables /etc/network/interface with the following content: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown In following the suggested text, installing the ifupdown deb continues to leave a broken system because ifupdown.postinst script creates an /etc/network/interfaces.d parts directory but does not write out a working /etc/network/interfaces file if the file exists on the system. This leaves a broken /etc/network/interfaces files which doesn't source /etc/network/interfaces.d/* and 3rd parties cannot use the interfaces.d parts directory to extend networking config. Cloud-init is one of those users of /etc/network/interfaces.d/ for rendering system networking on cloud images. Per LP: #1867029 ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: uec-images ** Description changed: Filing this bug for clarification and tracking on Ubuntu Bionic and later. - - Canonical cloudimages for Ec2 and other clouds leave an artifact that disables /etc/network/interface with the following content: + Canonical cloudimages for Ec2 and other clouds leave an artifact that + disables /etc/network/interface with the following content: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown - - In following the suggested text, installing the ifupdown deb continues to leave a broken system because ifupdown.postinst script creates an /etc/network/interfaces.d parts directory but does not write out a working /etc/network/interfaces file if the file exists on the system. + In following the suggested text, installing the ifupdown deb continues + to leave a broken system because ifupdown.postinst script creates an + /etc/network/interfaces.d parts directory but does not write out a + working /etc/network/interfaces file if the file exists on the system. This leaves a broken /etc/network/interfaces files which doesn't source /etc/network/interfaces.d/* and 3rd parties cannot use the interfaces.d parts directory to extend networking config. + + Cloud-init is one of those users of /etc/network/interfaces.d/ for + rendering system networking on cloud images. Per LP: #1867029 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1868329 Title: ifupdown does not render viable /etc/network/interfaces on bionic ec2 cloud-images Status in ifupdown package in Ubuntu: New Bug description: Filing this bug for clarification and tracking on Ubuntu Bionic and later. Canonical cloudimages for Ec2 and other clouds leave an artifact that disables /etc/network/interface with the following content: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown In following the suggested text, installing the ifupdown deb continues to leave a broken system because ifupdown.postinst script creates an /etc/network/interfaces.d parts directory but does not write out a working /etc/network/interfaces file if the file exists on the system. This leaves a broken /etc/network/interfaces files which doesn't source /etc/network/interfaces.d/* and 3rd parties cannot use the interfaces.d parts directory to extend networking config. Cloud-init is one of those users of /etc/network/interfaces.d/ for rendering system networking on cloud images. Per LP: #1867029 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1868329/+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 1867972] Re: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal
FFe granted. ** 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/1867972 Title: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal Status in systemd package in Ubuntu: Confirmed Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1864992] Autopkgtest regression report (kmod/26-1ubuntu1.1)
All autopkgtests for the newly accepted kmod (26-1ubuntu1.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: cross-toolchain-base-mipsen/unknown (armhf) systemd/242-7ubuntu3.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/eoan/update_excuses.html#kmod [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 kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864992 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Bionic: Fix Committed Status in kmod source package in Disco: Won't Fix Status in kmod source package in Eoan: Fix Committed Status in kmod source package in Focal: Fix Released Bug description: [Impact] * There is no impact to the end user but spurious error messages (tons of them) causing the perception that something really bad happened: Example of one of those tons of messages: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' [Test Case] * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin * sudo depmod -a -F /boot/System.map-$(uname -r) This will cause the spurious error messages because depmod -a -F won't have the "modules.builtin.bin" file created. This is a simulation of what the linux-modules postinst package does and an example of why the messages happen. [Regression Potential] * We are reverting a debian patch so we will be closer to upstream code base. * the change is about 2 different priority changes on verbosity, so biggest problem would be extra (or fewer) stdout/stderr messages (for scripts relying on them, for example). * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed to work fine. [Other Info] * Original Description: During a Focal install from the ISO image several errors like: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' are logged in curtin's install logs. The installed system boots and works fine, but the error is clearly something we want to get rid of. At first glance this seems related to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261 but the version of initramfs-tools in both the installer and installed system (checked with `chroot /target dpkg -l initramfs-tools` during the installation) is 0.136ubuntu1, which should contain Rafael's fix for that bug. I wonder if the update-initramfs diversion has a role here. I verified this happens at least on amd64 and arm64. I'm attaching the full install logs for a amd64 installation. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperVersion: 1.439 DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not
[Touch-packages] [Bug 1867029] Re: Package ifupdown breaks network configuration by cloud-init
** Changed in: cloud-init Status: Confirmed => In Progress ** Changed in: cloud-init Assignee: (unassigned) => Chad Smith (chad.smith) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1867029 Title: Package ifupdown breaks network configuration by cloud-init Status in cloud-init: In Progress Status in ifupdown package in Ubuntu: New Bug description: It appears the `ifupdown` package breaks networking configuration that cloud-init would normally handle (?) on both providers. The result, if you image an instance with the `ifupdown` package installed, is that the image is not bootable by Azure/AWS. I'm not familiar with how Azure/AWS/etc use cloud-init for network start up however. I'm filing here for now, in case `cloud-init` needs to be more defensive against `ifupdown`. To reproduce with Packer (I confirmed this method): * Add necessary Azure subscription env vars from `ifupdown-bug.json` * `packer build ifupdown-bug.json` * Try to boot an instance with resulting image * Instance will never boot -- more specifically, networking never comes up. See `boot.log` for an example boot To reproduce manually (only a guess, I did not confirm): * Boot 18.04 ubuntu instance * Install ifupdown * Image the instance * Try to boot instance using new image * Instance won't boot I hit this with Packer, creating new images for booting instances in scaling groups -- `ifupdown` is brought in by `salt`. If this is reproducible via manual installation, there could be some backup images/snapshots that are unable to boot though. This appears to be because cloud-init network start up operations are broken by whatever `ifupdown` sysv/systemd scripts perform on boot. With `ifupdown` installed on Azure, `eth0` does not get an IP address, the instance never fully boots according to Azure, and it will enter an error state. On AWS, the instance boots, but network operations like SSH fail. The `boot.log` is from Azure. Eventually `cloud-init` gives an exception (see `exception.log`), but this seems like a secondary issue related to networking being down. I did try to upgrade cloud-init using nightly PPAs (version 20.1 I believe), but no luck. This is on Ubuntu 18.04 instances from Azure marketplace and AWS Canonical AMI, cloud-init version `19.4-33-gbb4131a2-0ubuntu1~18.04.1`. Related: https://github.com/Azure/WALinuxAgent/issues/1612 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1867029/+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 1867972] Re: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal
@vorlon systemd-logind and systemd-nspawn did modprobe in ExecStartPre= and the new service is a nicer way of expressing the needed modules. https://github.com/systemd/systemd/commit/625077264ba01a108386eeea733ee244e6b7ff14 The tracing files will still be present at the old location for backward compatibility and the new location is the desired location according to the kernel documentation: https://www.kernel.org/doc/Documentation/trace/ftrace.txt ... When tracefs is configured into the kernel (which selecting any ftrace option will do) the directory /sys/kernel/tracing will be created. To mount this directory, you can add to your /etc/fstab file: tracefs /sys/kernel/tracing tracefs defaults0 0 Or you can mount it at run time with: mount -t tracefs nodev /sys/kernel/tracing For quicker access to that directory you may want to make a soft link to it: ln -s /sys/kernel/tracing /tracing *** NOTICE *** Before 4.1, all ftrace tracing control files were within the debugfs file system, which is typically located at /sys/kernel/debug/tracing. For backward compatibility, when mounting the debugfs file system, the tracefs file system will be automatically mounted at: /sys/kernel/debug/tracing All files located in the tracefs file system will be located in that debugfs file system directory as well. *** NOTICE *** ... The .mount will fail in LXC until the fix for LXD lands and it bind-mounts it. I can set ConditionVirtualization=!lxc until all supported LXD versions do that. -- 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/1867972 Title: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal Status in systemd package in Ubuntu: New Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1867972] Re: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal
That documents the new systemd units in the changelog, but doesn't explain what the impact is of these changes. There don't appear to have been any modprobe calls from systemd units previously, what calls have been moved to these units? All modprobe calls previously handled internally to udev? According to the changelog entry, the new tracing .mount is mounting tracefs at a different location than I have here already mounted by default, what's the impact of that? -- 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/1867972 Title: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal Status in systemd package in Ubuntu: New Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1867972] Re: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal
@vorlon I've updated debian/changelog mentioning those two new features. They are indeed missing from NEWS. The debug files are only in .ddebs, I've attached a pairwise debdiff on .debs. ** Changed in: systemd (Ubuntu) Status: Incomplete => New -- 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/1867972 Title: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal Status in systemd package in Ubuntu: New Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1867972] Re: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal
** Patch added: "245.2-1ubuntu1~rbalint1.debonly.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+attachment/5339490/+files/245.2-1ubuntu1~rbalint1.debonly.debdiff -- 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/1867972 Title: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal Status in systemd package in Ubuntu: New Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1868319] [NEW] PCI/internal sound card not detected
Public bug reported: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1868319 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+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 1867972] Re: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal
> -rw-r--r-- root/root /lib/systemd/system/modprobe@.service > -rw-r--r-- root/root /lib/systemd/system/sys-kernel-tracing.mount any more information available about these? adding new mounts seems worthy of a callout but there's no mention of it in the 245 news. > -rw-r--r-- root/root /usr/lib/debug/.build- id/78/dd21b51079de28b16140caf6a1cabda306cca7.debug A little confusing to have this as a debdiff over the .changes rather than individual .debs; I assume these bits are only in the dbgsyms package, not in the main systemd package. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1867972 Title: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal Status in systemd package in Ubuntu: Incomplete Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1868310] Re: configure_networking fails if dhcp provides no domain search path
** Changed in: initramfs-tools (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1868310 Title: configure_networking fails if dhcp provides no domain search path Status in initramfs-tools package in Ubuntu: In Progress Bug description: configure_networking() always returns an error for me. Using 'set -x', I observed the following at the end of a test script: + for n in $ns_addrs + '[' ', ' = '["192.168.122.1", ' ']' + continue + alist='["192.168.122.1"]' + '[' -n '' ']' + echo ' nameservers:' + echo 'addresses: ["192.168.122.1"]' + '[' -n '' ']' Which corresponds to this line of code in _render_netplan(): [ -n "$slist" ] && echo "search: $slist" I noticed that my dhcp server (default libvirt net) does not provide a domain search path, which is triggering this. If I move my VM to a network w/ a DHCP server that *does* provide this search path, it continues fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1868310/+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 1868310] [NEW] configure_networking fails if dhcp provides no domain search path
Public bug reported: configure_networking() always returns an error for me. Using 'set -x', I observed the following at the end of a test script: + for n in $ns_addrs + '[' ', ' = '["192.168.122.1", ' ']' + continue + alist='["192.168.122.1"]' + '[' -n '' ']' + echo ' nameservers:' + echo 'addresses: ["192.168.122.1"]' + '[' -n '' ']' Which corresponds to this line of code in _render_netplan(): [ -n "$slist" ] && echo "search: $slist" I noticed that my dhcp server (default libvirt net) does not provide a domain search path, which is triggering this. If I move my VM to a network w/ a DHCP server that *does* provide this search path, it continues fine. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1868310 Title: configure_networking fails if dhcp provides no domain search path Status in initramfs-tools package in Ubuntu: In Progress Bug description: configure_networking() always returns an error for me. Using 'set -x', I observed the following at the end of a test script: + for n in $ns_addrs + '[' ', ' = '["192.168.122.1", ' ']' + continue + alist='["192.168.122.1"]' + '[' -n '' ']' + echo ' nameservers:' + echo 'addresses: ["192.168.122.1"]' + '[' -n '' ']' Which corresponds to this line of code in _render_netplan(): [ -n "$slist" ] && echo "search: $slist" I noticed that my dhcp server (default libvirt net) does not provide a domain search path, which is triggering this. If I move my VM to a network w/ a DHCP server that *does* provide this search path, it continues fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1868310/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@hui.wang I'm not sure that I should file a bug against the Linux kernel; My USB headset works fine on 5.3.0-43-generic if I *don't* install libasound2 from your PPA. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1868286] [NEW] Disable A2DP when switch input device
Public bug reported: Hi, How to reproduce: 1) Connect the headset via Bluetooth 2) Automatically will use A2DP (until here everything ok) 3) Go to sound settings, will be the "internal microphone" selected. Switch to use the microphone of the headset and will switch to low-quality audio HSP Happens with the upgrade: bluez:amd64 (5.50-0ubuntu4 -> 5.50-0ubuntu5). Before that upgrade, everything was working fine. Only the automatic selection of A2DP fails sometimes but the microphone and A2DP were possible to use. After the mentioned upgrade to 5.50-0ubuntu5, it's just impossible to use the microphone and the A2DP audio at the same time. When I do the switch in the input device in the syslog it's the following message: kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 I tried to downgrade to 5.50-0ubuntu4 but didn't work, the A2DP is not usable at all. pulseaudio[8370]: Refused to switch profile to a2dp_sink: Not connected Description:Ubuntu 19.10 Release:19.10 Device: LE_WH-H900N (h.ear) Regards, ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1868286 Title: Disable A2DP when switch input device Status in bluez package in Ubuntu: New Bug description: Hi, How to reproduce: 1) Connect the headset via Bluetooth 2) Automatically will use A2DP (until here everything ok) 3) Go to sound settings, will be the "internal microphone" selected. Switch to use the microphone of the headset and will switch to low-quality audio HSP Happens with the upgrade: bluez:amd64 (5.50-0ubuntu4 -> 5.50-0ubuntu5). Before that upgrade, everything was working fine. Only the automatic selection of A2DP fails sometimes but the microphone and A2DP were possible to use. After the mentioned upgrade to 5.50-0ubuntu5, it's just impossible to use the microphone and the A2DP audio at the same time. When I do the switch in the input device in the syslog it's the following message: kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 I tried to downgrade to 5.50-0ubuntu4 but didn't work, the A2DP is not usable at all. pulseaudio[8370]: Refused to switch profile to a2dp_sink: Not connected Description: Ubuntu 19.10 Release: 19.10 Device: LE_WH-H900N (h.ear) Regards, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1868286/+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 1868268] Re: Cannot Print with Brother Brother QL-700 Label Printer, it's a big problem
** Package changed: ubuntu => cups (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1868268
Title:
Cannot Print with Brother Brother QL-700 Label Printer, it's a big
problem
Status in cups package in Ubuntu:
New
Bug description:
imprimante frère ql-700 imprimante d'étiquettes
205/5000
J'ai l'air d'être reconnu mais quand j'essaie d'imprimer un fichier édité
avec des glabels je ne peux pas le faire, cela me montre une première
impression d'infobulle, et une deuxième impression terminée, mais il ne réagit
pas
it's my log files
Page 1 ():
{ 'cups_ connection_ échec' : Faux}
Page 2 (<. Résoudre les problèmes CheckLocalServe . RPublishing
CheckLocalServe objet rPublishing à 0x7f122989e280>):
{ 'local_ server_ exporting_ imprimantes' : False}
Page 3 ():
{'cups_dest': ,
'cups_instance': None,
'cups_queue': 'Brother- QL-700 ',
' cups_ queue_listed ': Vrai}
Page 4 ():
{ 'cups_ device_ uri_scheme' : 'usb',
'cups_ printer_ dict': { 'appareil uri': « usb: // Brother / QL- 700? serial
= 000B7Z702725 ' ,
' imprimante- info ':' Brother QL-700 ',
' imprimante- est-partagé ' : Vrai,
' imprimante- emplacement ' :' puce- HP-Pavilion-
Power-Desktop- 580-0xx ' ,
'imprimante -marque-et- modèle': 'Brother QL-700 CUPS
v1.4',
message-d'état ' :' ',
' raisons- d'état- imprimante ' : [' aucun '],
' type d'imprimante ': 8523844,
' support d'imprimante -uri ' :' ipp: // localhost /
printers / Brother- QL -700' },
'cups_ printer_ à distance' : Faux,
'is_cups_class': Faux,
'local_ cups_queue_ attributs' : { 'charset- configured' : 'utf-8',
'charset- soutenu' : [ 'us-ascii' ,
'utf-8'],
'couleur prise en charge' : False,
'compressi on-supported' : ['aucun', 'gzip'],
'copies- default' : 1,
'copies- supported' : (1, ),
'cups- version' : '2.3.1',
'device- uri': 'usb: // Brother / QL-700?
serial = 000B7Z702725 ' ,
' document- format- default ' :' application
/ octet-stream ' ,
' document- format- supported ' : ['
application / octet-stream ' ,
' application
/ pdf ',
' application
/ postscript ' ,
'application /
vnd.
'application /
vnd.cups- command' ,
'application /
vnd.cups- pdf',
'application /
vnd.cups- pdf-banner' ,
'application /
vnd.cups- postscript' ,
'application /
vnd.cups- raster ' ,
' application
/ vnd.cups- raw ',
' application
/ x-cshell ' ,
' application
/ x-csource ' ,
' application
/ x-perl ' ,
' application
/ x-shell ' ,
' image / gif
',
'image /
jpeg',
'image / png
',
' image
/pwg-raster ' ,
' image / tiff
',
' image / urf
',
' image /
x-bitmap ' ,
' image /
x-photocd ' ,
' image /
x-portable- anymap ' ,
' image /
x-portable- bitmap ' ,
' image /
x-portable- graymap ' ,
[Touch-packages] [Bug 1868268] [NEW] Cannot Print with Brother Brother QL-700 Label Printer, it's a big problem
You have been subscribed to a public bug:
imprimante frère ql-700 imprimante d'étiquettes
205/5000
J'ai l'air d'être reconnu mais quand j'essaie d'imprimer un fichier édité avec
des glabels je ne peux pas le faire, cela me montre une première impression
d'infobulle, et une deuxième impression terminée, mais il ne réagit pas
it's my log files
Page 1 ():
{ 'cups_ connection_ échec' : Faux}
Page 2 (<. Résoudre les problèmes CheckLocalServe . RPublishing CheckLocalServe
objet rPublishing à 0x7f122989e280>):
{ 'local_ server_ exporting_ imprimantes' : False}
Page 3 ():
{'cups_dest': ,
'cups_instance': None,
'cups_queue': 'Brother- QL-700 ',
' cups_ queue_listed ': Vrai}
Page 4 ():
{ 'cups_ device_ uri_scheme' : 'usb',
'cups_ printer_ dict': { 'appareil uri': « usb: // Brother / QL- 700? serial =
000B7Z702725 ' ,
' imprimante- info ':' Brother QL-700 ',
' imprimante- est-partagé ' : Vrai,
' imprimante- emplacement ' :' puce- HP-Pavilion-
Power-Desktop- 580-0xx ' ,
'imprimante -marque-et- modèle': 'Brother QL-700 CUPS
v1.4',
message-d'état ' :' ',
' raisons- d'état- imprimante ' : [' aucun '],
' type d'imprimante ': 8523844,
' support d'imprimante -uri ' :' ipp: // localhost /
printers / Brother- QL -700' },
'cups_ printer_ à distance' : Faux,
'is_cups_class': Faux,
'local_ cups_queue_ attributs' : { 'charset- configured' : 'utf-8',
'charset- soutenu' : [ 'us-ascii' , 'utf-8'],
'couleur prise en charge' : False,
'compressi on-supported' : ['aucun', 'gzip'],
'copies- default' : 1,
'copies- supported' : (1, ),
'cups- version' : '2.3.1',
'device- uri': 'usb: // Brother / QL-700?
serial = 000B7Z702725 ' ,
' document- format- default ' :' application /
octet-stream ' ,
' document- format- supported ' : ['
application / octet-stream ' ,
' application /
pdf ',
' application /
postscript ' ,
'application /
vnd.
'application /
vnd.cups- command' ,
'application /
vnd.cups- pdf',
'application /
vnd.cups- pdf-banner' ,
'application /
vnd.cups- postscript' ,
'application /
vnd.cups- raster ' ,
' application /
vnd.cups- raw ',
' application /
x-cshell ' ,
' application /
x-csource ' ,
' application /
x-perl ' ,
' application /
x-shell ' ,
' image / gif ',
'image / jpeg',
'image / png ',
' image
/pwg-raster ' ,
' image / tiff
',
' image / urf ',
' image /
x-bitmap ' ,
' image /
x-photocd ' ,
' image /
x-portable- anymap ' ,
' image /
x-portable- bitmap ' ,
' image /
x-portable- graymap ' ,
' image /
x-portable- pixmap ' ,
' image /
x-sgi-rgb ' ,
' image /
x-sun-raster ' ,
' image /
x-xbitmapmap ' ,
'image /
x-xpixmap' ,
[Touch-packages] [Bug 1868276] Re: Libgcrypt warning: missing initialization - please fix the application
This is fixed in 2.0 in proposed. ** Changed in: apt (Ubuntu) Status: New => Invalid -- 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/1868276 Title: Libgcrypt warning: missing initialization - please fix the application Status in apt package in Ubuntu: Invalid Bug description: In Focal, running 'apt update' result in the following messages being logged: Mar 20 15:24:12 fa1 http[3392]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:12 fa1 http[3393]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:13 fa1 store[3550]: Libgcrypt warning: missing initialization - please fix the application # Steps to reproduce $ lxc launch images:ubuntu/focal fa1 $ lxc shell fa1 root@fa1:~# rm /var/lib/apt/lists/*InRelease # make sure we pull from the network root@fa1:~# apt update root@fa1:~# journalctl -b0 | grep -i Libgcrypt Mar 20 15:24:12 fa1 http[3392]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:12 fa1 http[3393]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:13 fa1 store[3550]: Libgcrypt warning: missing initialization - please fix the application # Additional information root@fa1:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@fa1:~# apt-cache policy apt apt: Installed: 1.9.10 Candidate: 1.9.10 Version table: *** 1.9.10 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1868276/+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 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
Ubuntu 19.10 with kernel 5.3.0-43-generic works as well WiFi interface is not detected but it is an other issue Thanks once more -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Fix Released Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+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 1868276] [NEW] Libgcrypt warning: missing initialization - please fix the application
Public bug reported: In Focal, running 'apt update' result in the following messages being logged: Mar 20 15:24:12 fa1 http[3392]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:12 fa1 http[3393]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:13 fa1 store[3550]: Libgcrypt warning: missing initialization - please fix the application # Steps to reproduce $ lxc launch images:ubuntu/focal fa1 $ lxc shell fa1 root@fa1:~# rm /var/lib/apt/lists/*InRelease # make sure we pull from the network root@fa1:~# apt update root@fa1:~# journalctl -b0 | grep -i Libgcrypt Mar 20 15:24:12 fa1 http[3392]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:12 fa1 http[3393]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:13 fa1 store[3550]: Libgcrypt warning: missing initialization - please fix the application # Additional information root@fa1:~# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 root@fa1:~# apt-cache policy apt apt: Installed: 1.9.10 Candidate: 1.9.10 Version table: *** 1.9.10 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1868276 Title: Libgcrypt warning: missing initialization - please fix the application Status in apt package in Ubuntu: New Bug description: In Focal, running 'apt update' result in the following messages being logged: Mar 20 15:24:12 fa1 http[3392]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:12 fa1 http[3393]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:13 fa1 store[3550]: Libgcrypt warning: missing initialization - please fix the application # Steps to reproduce $ lxc launch images:ubuntu/focal fa1 $ lxc shell fa1 root@fa1:~# rm /var/lib/apt/lists/*InRelease # make sure we pull from the network root@fa1:~# apt update root@fa1:~# journalctl -b0 | grep -i Libgcrypt Mar 20 15:24:12 fa1 http[3392]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:12 fa1 http[3393]: Libgcrypt warning: missing initialization - please fix the application Mar 20 15:24:13 fa1 store[3550]: Libgcrypt warning: missing initialization - please fix the application # Additional information root@fa1:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@fa1:~# apt-cache policy apt apt: Installed: 1.9.10 Candidate: 1.9.10 Version table: *** 1.9.10 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1868276/+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 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
Thanks for the update Zbigniew. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Fix Released Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+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 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
btw. I'm using Ubuntu 20.04 with kernel 5.4.0-18-generic -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+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 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
Problem solved. After upgrading linux-firmware to version 1.187 both input and output work as expected. Thanks a lot. -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+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 1858412] Re: systemd vacuuming does not work for remote journals
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Disco) 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/1858412 Title: systemd vacuuming does not work for remote journals Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Disco: Confirmed Status in systemd source package in Eoan: Confirmed Bug description: systemd has an issue in regard to vacuuming remote journals: https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as this version still has this problem. Steps to reproduce on "Description: Ubuntu 18.04.3 LTS": root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ Would it be possible to backport this trivial patch https://github.com/systemd/systemd/pull/13924 into 18.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858412/+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 1858412] Re: systemd vacuuming does not work for remote journals
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Eoan) 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/1858412 Title: systemd vacuuming does not work for remote journals Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Disco: Confirmed Status in systemd source package in Eoan: Confirmed Bug description: systemd has an issue in regard to vacuuming remote journals: https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as this version still has this problem. Steps to reproduce on "Description: Ubuntu 18.04.3 LTS": root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ Would it be possible to backport this trivial patch https://github.com/systemd/systemd/pull/13924 into 18.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858412/+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 1858412] Re: systemd vacuuming does not work for remote journals
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Bionic) 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/1858412 Title: systemd vacuuming does not work for remote journals Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Disco: Confirmed Status in systemd source package in Eoan: Confirmed Bug description: systemd has an issue in regard to vacuuming remote journals: https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as this version still has this problem. Steps to reproduce on "Description: Ubuntu 18.04.3 LTS": root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ Would it be possible to backport this trivial patch https://github.com/systemd/systemd/pull/13924 into 18.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858412/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
Hello Paride, or anyone else affected, Accepted kmod into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kmod/26-1ubuntu1.1 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- eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-eoan. 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: kmod (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan ** Changed in: kmod (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 kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864992 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Bionic: Fix Committed Status in kmod source package in Disco: Won't Fix Status in kmod source package in Eoan: Fix Committed Status in kmod source package in Focal: Fix Released Bug description: [Impact] * There is no impact to the end user but spurious error messages (tons of them) causing the perception that something really bad happened: Example of one of those tons of messages: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' [Test Case] * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin * sudo depmod -a -F /boot/System.map-$(uname -r) This will cause the spurious error messages because depmod -a -F won't have the "modules.builtin.bin" file created. This is a simulation of what the linux-modules postinst package does and an example of why the messages happen. [Regression Potential] * We are reverting a debian patch so we will be closer to upstream code base. * the change is about 2 different priority changes on verbosity, so biggest problem would be extra (or fewer) stdout/stderr messages (for scripts relying on them, for example). * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed to work fine. [Other Info] * Original Description: During a Focal install from the ISO image several errors like: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' are logged in curtin's install logs. The installed system boots and works fine, but the error is clearly something we want to get rid of. At first glance this seems related to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261 but the version of initramfs-tools in both the installer and installed system (checked with `chroot /target dpkg -l initramfs-tools` during the installation) is 0.136ubuntu1, which should contain Rafael's fix for that bug. I wonder if the update-initramfs diversion has a role here. I verified this happens at least on amd64 and arm64. I'm attaching the full install logs for a amd64 installation. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperVersion: 1.439 DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' LiveMediaBuild: Ubuntu-Server 20.04 LTS
[Touch-packages] [Bug 1864992] Please test proposed package
Hello Paride, or anyone else affected, Accepted kmod into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kmod/24-1ubuntu3.3 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864992 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Bionic: Fix Committed Status in kmod source package in Disco: Won't Fix Status in kmod source package in Eoan: Fix Committed Status in kmod source package in Focal: Fix Released Bug description: [Impact] * There is no impact to the end user but spurious error messages (tons of them) causing the perception that something really bad happened: Example of one of those tons of messages: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' [Test Case] * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin * sudo depmod -a -F /boot/System.map-$(uname -r) This will cause the spurious error messages because depmod -a -F won't have the "modules.builtin.bin" file created. This is a simulation of what the linux-modules postinst package does and an example of why the messages happen. [Regression Potential] * We are reverting a debian patch so we will be closer to upstream code base. * the change is about 2 different priority changes on verbosity, so biggest problem would be extra (or fewer) stdout/stderr messages (for scripts relying on them, for example). * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed to work fine. [Other Info] * Original Description: During a Focal install from the ISO image several errors like: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' are logged in curtin's install logs. The installed system boots and works fine, but the error is clearly something we want to get rid of. At first glance this seems related to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261 but the version of initramfs-tools in both the installer and installed system (checked with `chroot /target dpkg -l initramfs-tools` during the installation) is 0.136ubuntu1, which should contain Rafael's fix for that bug. I wonder if the update-initramfs diversion has a role here. I verified this happens at least on amd64 and arm64. I'm attaching the full install logs for a amd64 installation. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperVersion: 1.439 DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root
[Touch-packages] [Bug 1868085] Re: Bug related to the new kernel version 5.3.0-42-generic
** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1868085 Title: Bug related to the new kernel version 5.3.0-42-generic Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hi all, After an update of Ubuntu kernel (version 5.3.0-42-generic) I can't have sound any more. No soundcards are detected any I have a "dummy output" in the sound pannel in settings. Furthermore I can't resume from sleep anymore. Output of ALSA Information script: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Wed Mar 18 14:46:19 UTC 2020 !!Linux Distribution !!-- Ubuntu 18.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: HP Product Name: HP ZBook 15u G6 Product Version: Firmware Version: R70 Ver. 01.03.04 Board Vendor: HP Board Name:8549 !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/HPIC000C:00/status 15 /sys/bus/acpi/devices/HPQ6001:00/status15 /sys/bus/acpi/devices/IFX0785:00/status15 /sys/bus/acpi/devices/INT3400:00/status15 /sys/bus/acpi/devices/INT3403:00/status15 /sys/bus/acpi/devices/INT3403:01/status15 /sys/bus/acpi/devices/INT340E:00/status15 /sys/bus/acpi/devices/INT34BB:00/status15 /sys/bus/acpi/devices/INT3F0D:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 15 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0B00:00/status15 /sys/bus/acpi/devices/PNP0C02:00/status3 /sys/bus/acpi/devices/PNP0C02:01/status3 /sys/bus/acpi/devices/PNP0C02:05/status3 /sys/bus/acpi/devices/PNP0C09:00/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PRP1:00/status 11 /sys/bus/acpi/devices/SYNA3092:00/status 15 /sys/bus/acpi/devices/USBC000:00/status15 /sys/bus/acpi/devices/device:04/status 15 /sys/bus/acpi/devices/device:27/status 15 /sys/bus/acpi/devices/device:28/status 15 /sys/bus/acpi/devices/device:4c/status 15 !!Kernel Information !!-- Kernel release:5.3.0-42-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-42-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- --- no soundcards --- !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:9dc8] (rev 11) Subsystem: Hewlett-Packard Company Device [103c:8549] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!ALSA Device nodes !!- crw-rw 1 root audio 116, 1 Mar 18 14:45 /dev/snd/seq crw-rw 1 root audio 116, 33 Mar 18 14:44 /dev/snd/timer !!Aplay/Arecord output !! APLAY aplay: device_list:270: no soundcards found... ARECORD
[Touch-packages] [Bug 1868131] Re: [Toshiba NB250] Integrated speakers always muted
Writes down all circumstances - with the same hardware it is reproducible. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1868131 Title: [Toshiba NB250] Integrated speakers always muted Status in pulseaudio package in Ubuntu: Confirmed Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+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 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
** Tags added: id-5e73c372136ba285edff6d4d -- 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/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store: New Status in apport package in Ubuntu: Incomplete Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+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 1868164] Re: Create a general hook for subiquity
** Tags added: id-5e73c6769803ca1b31500eec
--
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/1868164
Title:
Create a general hook for subiquity
Status in apport package in Ubuntu:
New
Status in apport source package in Focal:
New
Bug description:
Users should be able to use "ubuntu-bug subiquity" on a system which
was installed with subiquity. The hook should include code like the
following which will send the bug to the subiquity project.
report['CrashDB'] = '''{
"impl": "launchpad",
"project": "subiquity",
"bug_pattern_url":
"http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml;,
}'''
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1868164/+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 1867204] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report
** Tags added: id-5e73cf3f5b07277c7fd75c79 -- 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/1867204 Title: /usr/share/apport/whoopsie-upload- all:FileNotFoundError:/usr/share/apport/whoopsie-upload- all@170:collect_info:process_report Status in apport package in Ubuntu: New Status in apport source package in Focal: New Bug 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-0ubuntu19, the problem page at https://errors.ubuntu.com/problem/7a3912ff155870bdb23500abfa48a21a6cb07171 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1867204/+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 962082] Re: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips
@Tim Abell (comment #18): I also have D-Link DBT-122. AD2P works fine, while I have no audio in HSP/HFP mode in Xenial. I didn't try the mic, but I bet it doesn't work either. On the net I see that the Mac recognize this adapter as a Broadcom BCM2035. Did you find a solution? Is there any firmware for this to fix the proble? Any help from anyone would be appreciated. -- 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/962082 Title: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips Status in HWE Next: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: This problem seems to occur on every device that uses the BCM20702A0 Bluetooth hardware. How to reproduce: (1) Pair a bluetooth headset with a machine equipped with a BCM20702A0. (2) Activate the device. Usually there is a button on the headset you should press to notify the bluetooth stack that you're ready to use the device. This creates SCO link and the plumbs the audio components. (3) Open the sound settings tool and select the bluetooth device under the "Input" and "Output" tabs. Under each tab you should see a table with an entry that has a headset icon on the left with the bluetooth device name to the right. This is the item to select. Now, everything should be configured so that you can use your bluetooth device to hear and record audio. Test this by: Testing Input: (1) In the sound settings tool, select the "Input" tab. (2) Make sure the "Input Volume" is not muted and the scale widget is not set to zero. (3) Make sounds into the headset mic -- you should see the "Input Level" bar raise. Testing Output: In the same program: (1) Select the "Hardware" tab. (2) In the box labeled "Choose a device to configure", select your bluetooth device. (3) A combobox should appear at the bottom of the window labeled "Settings for the selected device". Choose "Telephony Duplex (HSP/HFP)". (4) Now click on the "Test Speakers" button to the right. (5) Run speaker test. You should hear a sound. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/962082/+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 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
This is for eoan. Since focal will use the alsa-lib-1.2.1.2 and it already switch to use ucm2, so this SRU doesn't apply to focal, only for eoan and bionic. ** Patch added: "alsa-lib_1.1.9-0ubuntu1.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+attachment/5339265/+files/alsa-lib_1.1.9-0ubuntu1.3.debdiff ** Also affects: alsa-lib (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: alsa-lib (Ubuntu Eoan) Status: New => Confirmed ** Changed in: alsa-lib (Ubuntu Eoan) Importance: Undecided => High ** Description changed: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] + after applying this patch, I installed the testing alsa-lib on lenovo X1C7 and Dell vostro5390 which are all machines with the dmic connected to pch, after booing up, I checked the /usr/share/alsa/ucm/, the LENOVO-BIOSID-xxx folders are there, and the LENOVO machine loaded the N2H/*.conf, it worked well, the Dell machine still loaded the ucm by cardname, it worked as good as before. [Regression Potential] + low, just add some new ucms and let LENOVO machine find the ucm by bios_version if it fails by cardlongname. And already tested the change on lenovo and dell machines. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Eoan: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] after applying this patch, I installed the testing alsa-lib on lenovo X1C7 and Dell vostro5390 which are all machines with the dmic connected to pch, after booing up, I checked the /usr/share/alsa/ucm/, the LENOVO-BIOSID-xxx folders are there, and the LENOVO machine loaded the N2H/*.conf, it worked well, the Dell machine still loaded the ucm by cardname, it worked as good as before. [Regression Potential] low, just add some new ucms and let LENOVO machine find the ucm by bios_version if it fails by cardlongname. And already tested the change on lenovo and dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+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 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
** Changed in: alsa-lib (Ubuntu Focal) Status: New => Invalid ** Changed in: alsa-lib (Ubuntu Bionic) Status: New => Confirmed ** Changed in: alsa-lib (Ubuntu Bionic) Importance: Undecided => High ** Changed in: alsa-lib (Ubuntu Focal) Importance: Critical => Undecided ** Changed in: alsa-lib (Ubuntu Bionic) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: alsa-lib (Ubuntu Focal) Assignee: Hui Wang (hui.wang) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+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 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
@sponsor-team, This is a SRU of alsa-lib for bionic (18.04). thx. ** Patch added: "alsa-lib_1.1.3-5ubuntu0.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+attachment/5339264/+files/alsa-lib_1.1.3-5ubuntu0.5.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+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 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
** Also affects: alsa-lib (Ubuntu Focal) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Also affects: alsa-lib (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+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 1867390] Re: Update libarchive to 3.4.2
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1867390 Title: Update libarchive to 3.4.2 Status in libarchive package in Ubuntu: Triaged Status in libarchive package in Debian: Unknown Bug description: Please update libarchive to 3.4.2, also fixes LP: #1814109. The bug and security fixes outweighs the new features added in 3.4.1 and 3.4.2. https://github.com/libarchive/libarchive/releases Libarchive 3.4.2 is a feature and security release. New features: support for atomic file extraction (bsdtar -x --safe-writes) (#1289) support for mbed TLS (PolarSSL) (#1301) Important bugfixes: security fixes in RAR5 reader (#1280 #1326) compression buffer fix in XAR writer (#1317) fix uname and gname longer than 32 characters in PAX writer (#1319) fix segfault when archiving hard links in ISO9660 and XAR writers (#1325) fix support for extracting 7z archive entries with Delta filter (fixes LP: #1814109) (#987) Libarchive 3.4.1 is a feature and security release. New features: Unicode filename support for reading lha/lzh archives New pax write option "xattrhdr" Important bugfixes: security fixes in wide string processing (#1276 #1298) security fixes in RAR5 reader (#1212 #1217 #1296) security fixes and optimizations to write filter logic (#351) security fix related to use of readlink(2) (1dae5a5) sparse file handling fixes (#1218 #1260) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1867390/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Alexander, It is a kernel issue, please upload your dmesg to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678. Let us use 1845678 to track 5.3 kernel issue.. thx. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
I tried kernel 5.3.0-43 from proposed but my notebook does not wake up from S3 suspend anymore (Lenovo Carbon X1 7th gen). I'm returning to kernel 5.3.0-40 where this is working... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1868210] [NEW] [SRU] Load ucm on Lenovo notebooks based on bios version
Public bug reported: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] [Regression Potential] ** Affects: alsa-lib (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in alsa-lib package in Ubuntu: New Bug description: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+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 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
** Changed in: alsa-lib (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: alsa-lib (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in alsa-lib package in Ubuntu: New Bug description: [Impact] On some lenovo notebooks, ucm files are not loaded and mic can't be used [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+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
