[Touch-packages] [Bug 1891987] Re: epson stylus photo rx560 is detected, added, but when printing, task is ending up immediatelly with success
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/1891987 Title: epson stylus photo rx560 is detected, added, but when printing, task is ending up immediatelly with success Status in cups package in Ubuntu: Expired Bug description: Tried with both manufacturer and gutenprint driver: 1. plug an epson stylus photo rx560 via usb 2. add the driver (manufacturer first, retried with gutenprint) autodetected our gtk ubuntu specific application. 3. Tried to print with multiple apps: the task is queued and then immediately terminated with success. Nothing is printed. $ lsmod | grep usb usb_storage77824 1 uas usblp 24576 0 btusb 57344 0 btrtl 24576 1 btusb btbcm 16384 1 btusb btintel24576 1 btusb bluetooth 581632 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm usbhid 57344 0 hid 131072 2 usbhid,hid_generic Logs when adding the printer: $ tail -f /var/log/syslog Aug 18 09:36:00 casanier kernel: [ 2570.342143] usb 1-1: new high-speed USB device number 10 using xhci_hcd Aug 18 09:36:00 casanier kernel: [ 2570.501144] usb 1-1: New USB device found, idVendor=04b8, idProduct=0827, bcdDevice= 1.00 Aug 18 09:36:00 casanier kernel: [ 2570.501150] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 18 09:36:00 casanier kernel: [ 2570.501154] usb 1-1: Product: USB2.0 MFP(Hi-Speed) Aug 18 09:36:00 casanier kernel: [ 2570.501157] usb 1-1: Manufacturer: EPSON Aug 18 09:36:00 casanier kernel: [ 2570.501159] usb 1-1: SerialNumber: LH1010609180813040 Aug 18 09:36:00 casanier kernel: [ 2570.514421] usblp 1-1:1.1: usblp0: USB Bidirectional printer dev 10 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0827 Aug 18 09:36:00 casanier kernel: [ 2570.516384] usb-storage 1-1:1.2: USB Mass Storage device detected Aug 18 09:36:00 casanier kernel: [ 2570.516676] scsi host5: usb-storage 1-1:1.2 Aug 18 09:36:00 casanier systemd[1]: Started Configure Plugged-In Printer. Aug 18 09:36:00 casanier udev-configure-printer: add usb-001-010 Aug 18 09:36:00 casanier udev-configure-printer: device devpath is /devices/pci:00/:00:14.0/usb1/1-1 Aug 18 09:36:00 casanier udev-configure-printer: Device already handled Aug 18 09:36:00 casanier systemd[1]: configure-printer@usb-001-010.service: Main process exited, code=exited, status=1/FAILURE Aug 18 09:36:00 casanier systemd[1]: configure-printer@usb-001-010.service: Failed with result 'exit-code'. Aug 18 09:36:01 casanier kernel: [ 2571.538832] scsi 5:0:0:0: Direct-Access EPSONStylus Storage 1.00 PQ: 0 ANSI: 2 Aug 18 09:36:01 casanier kernel: [ 2571.539702] sd 5:0:0:0: Attached scsi generic sg0 type 0 Aug 18 09:36:01 casanier kernel: [ 2571.545241] sd 5:0:0:0: Power-on or device reset occurred Aug 18 09:36:01 casanier kernel: [ 2571.601212] sd 5:0:0:0: [sda] Attached SCSI removable disk ^C $ ls -l /dev/usb/lp0 crw-rw 1 root lp 180, 0 août 18 09:36 /dev/usb/lp0 $ ls -l /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 août 18 08:53 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 1 août 18 08:53 /dev/bus/usb/001/002 crw-rw-r-- 1 root root189, 2 août 18 08:53 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 août 18 08:53 /dev/bus/usb/001/004 crw-rw 1 root plugdev 189, 4 août 18 08:53 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 août 18 08:53 /dev/bus/usb/001/006 crw-rw-r--+ 1 root lp 189, 9 août 18 09:36 /dev/bus/usb/001/010 crw-rw-r-- 1 root root189, 128 août 18 08:53 /dev/bus/usb/002/001 $ sudo usb_printerid /dev/usb/lp0 GET_DEVICE_ID string: MFG:EPSON;CMD:ESCPL2,BDC,D4,D4PX,ESCPR1;MDL:Stylus Photo RX560;CLS:PRINTER;DES:EPSON Stylus Photo RX560; $ lpinfo -v file cups-brf:/ network socket network lpd network http network beh network https network ipp direct hp network ipps direct usb://EPSON/Stylus%20Photo%20RX560?serial=LH1010609180813040&interface=1 direct hpfax ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: W [18/Aug/2020:09:01:38 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Stylus-Photo-RX560-Gray..\' already exists W [18/Aug/2020:09:01:38 +0200] CreateProfile failed: org.freedesktop.ColorManager.A
[Touch-packages] [Bug 1900098] Re: software-properties-gtk fails to open with error
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1900098 Title: software-properties-gtk fails to open with error Status in software-properties package in Ubuntu: Expired Bug description: When trying to open software-properties-gtk via Terminal (via GUI: “Settings & Livepatch”) the following error is returned in the terminal and software-properties-gtk does not open. ERROR:dbus.proxies:Introspect error on :1.121:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 211, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.121 was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 08:17:15 2020 InstallationDate: Installed on 2020-10-09 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1900098/+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 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
@Timo, The change in this SRU will not affect volume-test. Maybe need a re- upload on riscv64 and see if this failure could be reproduced (not 100% fail, with a fail rate)? -- 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/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Committed Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1887964] Re: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found
I've encountered a similar issue for a root volume group w/ encryption. How can I try the same workaround as @veribaka starting from a busybox prompt? In busybox /etc/crypttab does not exist. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887964 Title: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume group is no longer found. During boot the console shows Volume group "vg01" not found Cannot process volume group vg01 Gave up waiting for suspend/resume device ALERT! /dev/mapper/vg01-root does not exist. Dropping to a shell! Attached dist-upgrade logs and console output. Tried the "vgck --updatemetadata vg01" recommended on this bug report: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887964/+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 1908758] [NEW] no more HDMI devices after upgrade to 20_04
Public bug reported: Some two hours ago, I listened to audio through the extenal monitor, also used as display. Then I upgraded to 20_04 from 18_04. Now the display still works, but pulseaudio doesn't see nor offer the HDMI sink any longer on my lenovo T410s. What a bad mishap ... . And what to do now? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: udippel1690 F pulseaudio /dev/snd/pcmC0D0p: udippel1690 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 18 22:35:06 2020 InstallationDate: Installed on 2018-08-30 (841 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-12-18 (0 days ago) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WZ6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WZ6:pvrThinkPadT410s:rvnLENOVO:rn2924WZ6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2924WZ6 dmi.product.version: ThinkPad T410s 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/1908758 Title: no more HDMI devices after upgrade to 20_04 Status in pulseaudio package in Ubuntu: New Bug description: Some two hours ago, I listened to audio through the extenal monitor, also used as display. Then I upgraded to 20_04 from 18_04. Now the display still works, but pulseaudio doesn't see nor offer the HDMI sink any longer on my lenovo T410s. What a bad mishap ... . And what to do now? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: udippel1690 F pulseaudio /dev/snd/pcmC0D0p: udippel1690 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 18 22:35:06 2020 InstallationDate: Installed on 2018-08-30 (841 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-12-18 (0 days ago) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WZ6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WZ6:pvrThinkPadT410s:rvnLENOVO:rn2924WZ6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410s dmi.product.name: 2924WZ6 dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908758/+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 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
** Tags added: sru-20201130 -- 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/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+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 1908756] [NEW] Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Public bug reported:
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32 bit
process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to use
libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
** Affects: elfutils (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-190488 severity-medium
targetmilestone-inin2104
** Tags added: architecture-s39064 bugnameltc-190488 severity-medium
targetmilestone-inin2104
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => elfutils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1908756
Title:
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Status in elfutils package in Ubuntu:
New
Bug description:
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32 bit
process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to
use libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1908756/+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 1908756] [NEW] Ubuntu 20.10 - elfutils unwinding broken for s390 compat
You have been subscribed to a public bug:
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32 bit
process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to use
libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
** Affects: elfutils (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-190488 severity-medium
targetmilestone-inin2104
--
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
https://bugs.launchpad.net/bugs/1908756
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to elfutils 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 1906701] Re: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)
Uploaded to Hirsute. ** Changed in: logrotate (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1906701 Title: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: Fix Committed Bug description: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) At the time of filling this bug, the target debian unstable version is 3.17.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1906701/+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 1908334] Re: Printer managed wrongly in Settings -> Printers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1908334] Re: Printer managed wrongly in Settings -> Printers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1908334 Title: Printer managed wrongly in Settings -> Printers Status in cups package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Settings -> Printers automatically adds "EPSON_L3160_Series" device but it is unusable. I cannot remove it as it keeps getting automatically added. It is also completely unusable and its "Printing Options" shows blank. "Printing Details" shows Address: null, Driver: "EPSON EPSON L3160 Series". When I search for printers it gets detected again, now as Name: "L3160", Address: "localhost" Driver: "EPSON L3160 Series, driverless". I guess these automatically detected drivers are fine because it is printing (although it also has some issues). Before adding this second one the first one is shown in the list of printing applications, but keeps saying "Retrieving information" status. After the second one is added, the first one disappears from the list in the applications, although it is still present in the Settings->Printers. 1. Don't know if this printer gets automatically re-added, or it just disappeares from the Settings UI when it is not actually deleted. Because CUPS web ui, and the applications are not showing the one that keeps comming back in the Settings->Printers ui 2. If it keeps getting re-added why is it not automatically set up as when I go Add... and click on it 3. When I wait a bit more in the Add... search, I get 3 printers (check attachement). The one that comes up immediately (the first one) is the working one from description above. But the third one also works. I guess all 3 point to the same physical printer. Why is this happening and can it be improved? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (395 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for EPSON_L3160_Series: implicitclass://EPSON_L3160_Series/ MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_L3160_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_L3160_Series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1908334/+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 1854838] Re: Power off dialog does not appear in ~0.4% of cases when the power button is pressed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upower (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1854838 Title: Power off dialog does not appear in ~0.4% of cases when the power button is pressed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: 18.04 LTS During soft power cycle test, the option to shut down not available in Ubuntu. This occurred 4/1000 times during test. Power needed to be removed from the unit in order to power down. Test steps - 1) Press power button on unit with power connected 2) Wait for system to boot - verify by observing Ubuntu OS "user select" screen 3) Select the power button/icon 4) Select "power off" from the available options Repeat steps 1-4 1000 times. Expected result - Each time the user selects the power button/icon they will be presented with options to power off or restart the unit. Actual result - Of 1000 cycles, 4 cycles resulted in the system not presenting the options to power off or restart the unit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1854838/+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 1854838] Re: Power off dialog does not appear in ~0.4% of cases when the power button is pressed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1854838 Title: Power off dialog does not appear in ~0.4% of cases when the power button is pressed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: 18.04 LTS During soft power cycle test, the option to shut down not available in Ubuntu. This occurred 4/1000 times during test. Power needed to be removed from the unit in order to power down. Test steps - 1) Press power button on unit with power connected 2) Wait for system to boot - verify by observing Ubuntu OS "user select" screen 3) Select the power button/icon 4) Select "power off" from the available options Repeat steps 1-4 1000 times. Expected result - Each time the user selects the power button/icon they will be presented with options to power off or restart the unit. Actual result - Of 1000 cycles, 4 cycles resulted in the system not presenting the options to power off or restart the unit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1854838/+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 1854838] Re: Power off dialog does not appear in ~0.4% of cases when the power button is pressed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1854838 Title: Power off dialog does not appear in ~0.4% of cases when the power button is pressed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: 18.04 LTS During soft power cycle test, the option to shut down not available in Ubuntu. This occurred 4/1000 times during test. Power needed to be removed from the unit in order to power down. Test steps - 1) Press power button on unit with power connected 2) Wait for system to boot - verify by observing Ubuntu OS "user select" screen 3) Select the power button/icon 4) Select "power off" from the available options Repeat steps 1-4 1000 times. Expected result - Each time the user selects the power button/icon they will be presented with options to power off or restart the unit. Actual result - Of 1000 cycles, 4 cycles resulted in the system not presenting the options to power off or restart the unit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1854838/+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 1908553] Re: Wireless/Ethernet icon shows no internet
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1908553 Title: Wireless/Ethernet icon shows no internet Status in network-manager package in Ubuntu: Confirmed Bug description: I'm currently connected to wifi & ethernet cable and we know that in wifi the triage has white color showing the wireless strength. But in my case, there is a question mark "?" in wifi symbol. Even in the ethernet, it (ethernet icon) shows that there is no internet connection while there is. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 17 22:50:11 2020 InstallationDate: Installed on 2020-05-04 (227 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1908553/+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 1908728] Re: Xorg crash
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1908728 Title: Xorg crash Status in xorg package in Ubuntu: Confirmed Bug description: Usually after the screen lock has been engaged for some time this error occurs. X will freeze and eventually crash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 18 16:13:18 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 1660 Ti] [1462:3750] InstallationDate: Installed on 2020-08-04 (135 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B08911 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V8.1 dmi.board.name: MS-78511 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 3.1 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-B08911 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1908728/+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 980519] Re: Random log off in Ubuntu 12.04 LTS
This is not an issue with 12.04. I have experienced this consistently in 16.04, 18.04 and 20.04 I have nvidia, so the common theme seems to be nvidia (however, may not even be that). I have tried in vain to find a fix for the last 4 years and have now learned to live with it (save frequently, etc). It sucks but not enough to go back to Windows Recently I plugged in a 3rd monitor to my desktop and the issue seems to have increased -- 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/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in gnome-desktop package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in Fedora: New Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+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 1908273] Re: Software stopped working
In /var/crash there is only one relevant crash file and I tried ubuntu-bug
YOURFILE.crash but nothing happens, the command just hangs forever.
I've tried "https://errors.ubuntu.com/user/ID where ID is the content of file
/var/lib/whoopsie/whoopsie-id" but it just says "Sorry, you are not a member of
a group that is allowed to see the data from error reports. Please fill out
this form to request access." but that form wanted me to give my personal info
which I'm not comfortable with.
Below there are outputs of running the affected apps from a terminal
window.
-
anna@anna:~$ vmd
rlwrap: Command not found.
/home/anna/Programy/vmd/vmd_LINUXAMD64: /lib/x86_64-linux-gnu/libGL.so.1: no
version information available (required by
/home/anna/Programy/vmd/vmd_LINUXAMD64)
Info) VMD for LINUXAMD64, version 1.9.4a38 (October 17, 2019)
Info) http://www.ks.uiuc.edu/Research/vmd/
Info) Email questions and bug reports to v...@ks.uiuc.edu
Info) Please include this reference in published work using VMD:
Info)Humphrey, W., Dalke, A. and Schulten, K., `VMD - Visual
Info)Molecular Dynamics', J. Molec. Graphics 1996, 14.1, 33-38.
Info) -
Info) Multithreading available, 8 CPUs detected.
Info) CPU features: SSE2 AVX AVX2 FMA
Info) Free system memory: 11GB (68%)
Info) No CUDA accelerator devices available.
Warning) Detected X11 'Composite' extension: if incorrect display occurs
Warning) try disabling this X server option. Most OpenGL drivers
Warning) disable stereoscopic display when 'Composite' is enabled.
Info) OpenGL renderer: Mesa Intel(R) UHD Graphics 620 (WHL GT2)
Info) Features: STENCIL MSAA(4) MDE CVA MTX NPOT PP PS GLSL(OVFS)
Info) Full GLSL rendering mode is available.
Info) Textures: 2-D (16384x16384), 3-D (512x512x512), Multitexture (8)
Info) Dynamically loaded 3 plugins in directory:
Info) /home/anna/Programy/vmd/plugins/LINUXAMD64/molfile
Aborted (core dumped)
-
anna@anna:~/Programy/Biovia/Discovery-Studio/bin$ ./DiscoveryStudio2020
# Parse application name from $0 unless it's already set for us
if [ -z "$ACCELRYS_APPNAME" ] ; then
ACCELRYS_APPNAME=`basename $0`
fi
# Path to the installation
abspath="$(cd "${0%/*}" 2>/dev/null; echo "$PWD"/"${0##*/}")"
libfolder=`dirname "$abspath"`
ACCELRYS_ROOT="$libfolder/.."
# Source the global resource configuration file
GLOBALRC=$ACCELRYS_ROOT/etc/shrc
if [ -f "$GLOBALRC" ] ; then
. $GLOBALRC
fi
# Bourne Shell Resource Configuration file for the DS client and server
# applications
if [ -z "$ACCELRYS_ROOT" ] ; then
echo "ACCELRYS_ROOT is not set"
exit 1
fi
# Detect the platform name
if [ -z "$ACCELRYS_PLATFORM" ] ; then
case `uname` in
IRIX64) ACCELRYS_PLATFORM=irix;;
IRIX*) ACCELRYS_PLATFORM=irix;;
AIX)ACCELRYS_PLATFORM=aix;;
OSF1) ACCELRYS_PLATFORM=tru64;;
SunOS) ACCELRYS_PLATFORM=solaris;;
Linux) ACCELRYS_PLATFORM=linux;;
CYGWIN*)ACCELRYS_PLATFORM=win32;;
*) ACCELRYS_PLATFORM=unknown;;
esac
# special case for Itanium
if [ `uname -m` = "ia64" ] ; then
ACCELRYS_PLATFORM=linux_ia64
fi
fi
export ACCELRYS_PLATFORM
# Set up the executable and library paths
PATH=$ACCELRYS_ROOT/bin:$ACCELRYS_ROOT/lib:$PATH
LD_LIBRARY_PATH=$ACCELRYS_ROOT/lib:$ACCELRYS_ROOT/lib64
export ACCELRYS_ROOT
export PATH
export LD_LIBRARY_PATH
# -- Begin License check
# Set up the License Pack environment
# IMPORTANT - Any changes to this section should also be made in
# the apps/accelrys/ds/data/shrc file until these two files
# can be replaced by a single file, if possible
lp_location=$ACCELRYS_ROOT/share/license/data/lp_location
if [ -r "$lp_location" ] ; then
lp_dir=`cat "$lp_location"`
if [ -d "$lp_dir" ]; then
lp_varfile=$lp_dir/etc/lp_echovars
if [ -r "$lp_varfile" ] ; then
eval `"$lp_varfile" -l sh`
else
echo "Required file $lp_varfile can not be read."
fi
else
echo "License Pack location ($lp_dir) is not a valid location."
echo "Run $ACCELRYS_ROOT/bin/config_lp_location "
echo "to reconfigure."
fi
else
echo "Required file '$lp_location' can not be read."
fi
# -- End License check
if [ "$ACCELRYS_PLATFORM" != "irix" -a "$ACCELRYS_PLATFORM" != "aix" ] ; then
# Avoids difficult-to-debug crashes for several apps
ulimit -s 10240
fi
# Source the application resource configuration file
APPRC=$ACCELRYS_ROOT/share/$ACCELRYS_APPNAME/shrc
if [ -f "$APPRC" ] ; then
. $APPRC
fi
# Default value for how we exec the application
if [ -z "$ACCELRYS_EXEC" ] ; then
ACCELRYS_EXEC=exec
fi
# The binary executable for the application
ACCELRYS_BIN=$ACCELRYS_ROOT/lib/${ACCELRYS_APPNAME}-bin
if [ ! -f "$ACCELRYS_BIN" ] ; then
echo "ERROR: Application binary '
[Touch-packages] [Bug 1908634] Re: [USB-Audio - DAC-X6, playback] Underruns, dropouts or crackling sound
** Description changed: I was playing back from SoundCloud where I pay for Go and use the "High Quality" streaming settings. I'm also working on a react native app and this issue seems to happen after I start the bundle server (react-native start). I can't show you the code because I'm selling it. I connected my headphones through an FX-Audio DAC-X6, a FiiO K3 Type-C USB DAC, and my motherboard and I get the exact same crackling, so it's defiantly a software issue. As for the actual sounds, the popping sound like a momentary drop in all sound, I don't have an oscilloscope but I suspect the pops would look like ~15ish milliseconds of 0 volts right in the middle of the sound wave. Also these pops are repetitive, like there's a pattern to them starting with a big one and then smaller ones at regular intervals leading me to think some number isn't getting processed properly. Now that I think about it I might have been experiencing this bug ever since Ubuntu 19.10 but haven't noticed it up until I got these high impedance headphones and now have to turn up my DAC to twice the gain. It doesn't sound like static, but more like a single clap but slowed down. I have already followed a menagerie of solutions (2 most recent ones): https://wiki.ubuntu.com/Audio/PositionReporting https://itectec.com/ubuntu/ubuntu-annoying-click-popping-sound-on- ubuntu-20-04/ And none of them have made a difference. Appended you will find an audio file where I put my headphones on my condenser mic and played a 440hz tone in an attempt to record the pops. It's alittle quiet, so I'd recommend trying to amplify it. I hoped I could use Audacity to visually identify the pops in the actual waveform but I wasn't sure what I was looking for. I really want this fixed because right now I absolutely can't use my headphones, I literally feel each and every pop and it hurts. If you - have any further questions or want to test on my hardware, please call - me at +1-201-675-9961 or email me at dan.ha...@gmail.com. Thank you. + have any further questions or want to test on my hardware, please email + me at dan.ha...@gmail.com. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Dec 17 22:49:22 2020 InstallationDate: Installed on 2020-12-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DACX6 failed Symptom_Card: DAC-X6 - DAC-X6 Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - DAC-X6, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V17.12 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GM-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 4.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV17.12:bd11/28/2012:svnMSI:pnMS-7641:pvr4.0:rvnMSI:rn760GM-P34(FX)(MS-7641):rvr4.0:cvnMSI:ct3:cvr4.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7641 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: MSI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-12-17T22:21:33.927437 -- 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/1908634 Title: [USB-Audio - DAC-X6, playback] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: I was playing back from SoundCloud where I pay for Go and use the "High Quality" streaming settings. I'm also working on a react native app and this issue seems to happen after I start the bundle server (react-native start). I can't show you the code because I'm selling it. I connected my headphones through an FX-Audio DAC-X6, a FiiO K3 Type-C USB DAC, and my motherboard and I get the exact same crackling, so it's defiantly a software issue. As for the actual sounds, the popping sound like a momentary drop in all sound, I don't have an oscilloscope but I suspect the pops would look like ~15ish milliseconds of 0 volts right in the middle of the sound wave. Also these pops are repetitive, like there's a pattern to them starting with a big one and then smaller on
[Touch-packages] [Bug 1908728] [NEW] Xorg crash
Public bug reported: Usually after the screen lock has been engaged for some time this error occurs. X will freeze and eventually crash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 18 16:13:18 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 1660 Ti] [1462:3750] InstallationDate: Installed on 2020-08-04 (135 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B08911 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V8.1 dmi.board.name: MS-78511 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 3.1 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-B08911 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908728 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: Usually after the screen lock has been engaged for some time this error occurs. X will freeze and eventually crash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.
[Touch-packages] [Bug 1906364] Autopkgtest regression report (docker.io/19.03.6-0ubuntu1~18.04.3)
All autopkgtests for the newly accepted docker.io (19.03.6-0ubuntu1~18.04.3) for bionic have finished running. The following regressions have been reported in tests triggered by the package: ubuntu-fan/0.12.10 (amd64) 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#docker.io [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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons Status in docker.io package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in docker.io source package in Xenial: Fix Committed Status in unattended-upgrades source package in Xenial: Won't Fix Status in docker.io source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: Won't Fix Status in docker.io source package in Focal: Fix Committed Status in unattended-upgrades source package in Focal: Won't Fix Status in docker.io source package in Groovy: Fix Committed Status in unattended-upgrades source package in Groovy: Won't Fix Status in docker.io source package in Hirsute: Fix Released Status in unattended-upgrades source package in Hirsute: Won't Fix Bug description: [Impact] Docker uses containerd under the hood. When containerd is upgraded it stops and restarts its service; docker stops when containerd stops but doesn’t restart. Particularly when doing unattended upgrades, an SRU fix rolled out for containerd can result in unexpected and widespread service outages for docker. [Test Case] $ sudo apt install docker.io $ sudo systemctl start docker $ systemctl status docker | grep Active Active: active (running) since[...] $ systemctl status containerd | grep Active Active: active (running) since[...] $ docker pull ubuntu/redis:latest $ docker run -e REDIS_PASSWORD=1234 --network host \ --name test-redis -d ubuntu/redis:latest $ telnet localhost 6379 $ docker container logs test-redis $ sudo apt install --reinstall containerd $ systemctl status containerd | grep Active Active: active (running) since $ systemctl status docker | grep Active Active: inactive (dead) since [...]; 8s ago $ docker container logs test-redis [Where Problems Could Occur] The challenge with this issue is addressing all important corner cases, and as such the biggest risk is that we miss a corner case and fail to keep the two services running when they should. Areas to watch will be failures during start/stop/restart/upgrade type operations. Issues during runtime are unlikely to relate to this change. [Original Report] Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO Starting unattended upgrades script 2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:50,733 INFO Initial whitelist (not strict): Also this happened for us on plenty of our servers almost at the same (why the unattended updates are not spread over time?), which destroyed the second time an production environment. This is not how unattended-upgraded should be, sadly this package lost our trust and we disable it and schedule the 'unattended updates' now on our own. PS: Not to say that on some servers the docker daemon did not even restart.. To manage notifications about this bug go to: https:
[Touch-packages] [Bug 1908726] [NEW] Update the package for Focal Fossa to >= 0.27.3
Public bug reported: The current Darktable from the Focal Fossa repo can't be upgraded because it requires libexiv2-27 (>= 0.27.3) and the currently available one is libexiv2-27/0.27.2-8ubuntu2 Can you please update it to >= 0.27.3 ? $ sudo apt upgrade darktable Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: darktable : Depends: libexiv2-27 (>= 0.27.3) but 0.27.2-8ubuntu2 is to be installed Depends: libilmbase25 (>= 2.5.3) but it is not installable Depends: libjson-glib-1.0-0 (>= 1.5.2) but 1.4.4-2ubuntu2 is to be installed Depends: libopenexr25 (>= 2.5.3) but it is not installable E: Broken packages ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1908726 Title: Update the package for Focal Fossa to >= 0.27.3 Status in exiv2 package in Ubuntu: New Bug description: The current Darktable from the Focal Fossa repo can't be upgraded because it requires libexiv2-27 (>= 0.27.3) and the currently available one is libexiv2-27/0.27.2-8ubuntu2 Can you please update it to >= 0.27.3 ? $ sudo apt upgrade darktable Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: darktable : Depends: libexiv2-27 (>= 0.27.3) but 0.27.2-8ubuntu2 is to be installed Depends: libilmbase25 (>= 2.5.3) but it is not installable Depends: libjson-glib-1.0-0 (>= 1.5.2) but 1.4.4-2ubuntu2 is to be installed Depends: libopenexr25 (>= 2.5.3) but it is not installable E: Broken packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1908726/+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 1908725] [NEW] Update the package for Focal Fossa to >= 2.5.3
Public bug reported: The current Darktable from the Focal Fossa repo can't be upgraded because it requires libopenexr25 (>= 2.5.3) and the currently available one is libopenexr24/focal-updates,focal-security,now 2.3.0-6ubuntu0.2 Can you please update it to >=2.5.3 ? $ sudo apt upgrade darktable Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: darktable : Depends: libexiv2-27 (>= 0.27.3) but 0.27.2-8ubuntu2 is to be installed Depends: libilmbase25 (>= 2.5.3) but it is not installable Depends: libjson-glib-1.0-0 (>= 1.5.2) but 1.4.4-2ubuntu2 is to be installed Depends: libopenexr25 (>= 2.5.3) but it is not installable E: Broken packages ** Affects: openexr (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openexr in Ubuntu. https://bugs.launchpad.net/bugs/1908725 Title: Update the package for Focal Fossa to >= 2.5.3 Status in openexr package in Ubuntu: New Bug description: The current Darktable from the Focal Fossa repo can't be upgraded because it requires libopenexr25 (>= 2.5.3) and the currently available one is libopenexr24/focal-updates,focal-security,now 2.3.0-6ubuntu0.2 Can you please update it to >=2.5.3 ? $ sudo apt upgrade darktable Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: darktable : Depends: libexiv2-27 (>= 0.27.3) but 0.27.2-8ubuntu2 is to be installed Depends: libilmbase25 (>= 2.5.3) but it is not installable Depends: libjson-glib-1.0-0 (>= 1.5.2) but 1.4.4-2ubuntu2 is to be installed Depends: libopenexr25 (>= 2.5.3) but it is not installable E: Broken packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1908725/+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 1906364] Autopkgtest regression report (docker.io/18.09.7-0ubuntu1~16.04.7)
All autopkgtests for the newly accepted docker.io (18.09.7-0ubuntu1~16.04.7) for xenial have finished running. The following regressions have been reported in tests triggered by the package: docker.io/18.09.7-0ubuntu1~16.04.7 (amd64, arm64, s390x, i386, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/xenial/update_excuses.html#docker.io [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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons Status in docker.io package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in docker.io source package in Xenial: Fix Committed Status in unattended-upgrades source package in Xenial: Won't Fix Status in docker.io source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: Won't Fix Status in docker.io source package in Focal: Fix Committed Status in unattended-upgrades source package in Focal: Won't Fix Status in docker.io source package in Groovy: Fix Committed Status in unattended-upgrades source package in Groovy: Won't Fix Status in docker.io source package in Hirsute: Fix Released Status in unattended-upgrades source package in Hirsute: Won't Fix Bug description: [Impact] Docker uses containerd under the hood. When containerd is upgraded it stops and restarts its service; docker stops when containerd stops but doesn’t restart. Particularly when doing unattended upgrades, an SRU fix rolled out for containerd can result in unexpected and widespread service outages for docker. [Test Case] $ sudo apt install docker.io $ sudo systemctl start docker $ systemctl status docker | grep Active Active: active (running) since[...] $ systemctl status containerd | grep Active Active: active (running) since[...] $ docker pull ubuntu/redis:latest $ docker run -e REDIS_PASSWORD=1234 --network host \ --name test-redis -d ubuntu/redis:latest $ telnet localhost 6379 $ docker container logs test-redis $ sudo apt install --reinstall containerd $ systemctl status containerd | grep Active Active: active (running) since $ systemctl status docker | grep Active Active: inactive (dead) since [...]; 8s ago $ docker container logs test-redis [Where Problems Could Occur] The challenge with this issue is addressing all important corner cases, and as such the biggest risk is that we miss a corner case and fail to keep the two services running when they should. Areas to watch will be failures during start/stop/restart/upgrade type operations. Issues during runtime are unlikely to relate to this change. [Original Report] Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO Starting unattended upgrades script 2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:50,733 INFO Initial whitelist (not strict): Also this happened for us on plenty of our servers almost at the same (why the unattended updates are not spread over time?), which destroyed the second time an production environment. This is not how unattended-upgraded should be, sadly this package lost our trust and we disable it and schedule the 'unattended updates' now on our own. PS: Not to say that on some servers the docker daemon did not even restart.. To mana
[Touch-packages] [Bug 1906364] Re: [SRU] unattended-upgrade still restarts blacklisted daemons
Hello sascha, or anyone else affected, Accepted docker.io into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/18.09.7-0ubuntu1~16.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker.io (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons Status in docker.io package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in docker.io source package in Xenial: Fix Committed Status in unattended-upgrades source package in Xenial: Won't Fix Status in docker.io source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: Won't Fix Status in docker.io source package in Focal: Fix Committed Status in unattended-upgrades source package in Focal: Won't Fix Status in docker.io source package in Groovy: Fix Committed Status in unattended-upgrades source package in Groovy: Won't Fix Status in docker.io source package in Hirsute: Fix Released Status in unattended-upgrades source package in Hirsute: Won't Fix Bug description: [Impact] Docker uses containerd under the hood. When containerd is upgraded it stops and restarts its service; docker stops when containerd stops but doesn’t restart. Particularly when doing unattended upgrades, an SRU fix rolled out for containerd can result in unexpected and widespread service outages for docker. [Test Case] $ sudo apt install docker.io $ sudo systemctl start docker $ systemctl status docker | grep Active Active: active (running) since[...] $ systemctl status containerd | grep Active Active: active (running) since[...] $ docker pull ubuntu/redis:latest $ docker run -e REDIS_PASSWORD=1234 --network host \ --name test-redis -d ubuntu/redis:latest $ telnet localhost 6379 $ docker container logs test-redis $ sudo apt install --reinstall containerd $ systemctl status containerd | grep Active Active: active (running) since $ systemctl status docker | grep Active Active: inactive (dead) since [...]; 8s ago $ docker container logs test-redis [Where Problems Could Occur] The challenge with this issue is addressing all important corner cases, and as such the biggest risk is that we miss a corner case and fail to keep the two services running when they should. Areas to watch will be failures during start/stop/restart/upgrade type operations. Issues during runtime are unlikely to relate to this change. [Original Report] Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO Starting
[Touch-packages] [Bug 1906364] Please test proposed package
Hello sascha, or anyone else affected, Accepted docker.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/19.03.6-0ubuntu1~18.04.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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons Status in docker.io package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in docker.io source package in Xenial: In Progress Status in unattended-upgrades source package in Xenial: Won't Fix Status in docker.io source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: Won't Fix Status in docker.io source package in Focal: Fix Committed Status in unattended-upgrades source package in Focal: Won't Fix Status in docker.io source package in Groovy: Fix Committed Status in unattended-upgrades source package in Groovy: Won't Fix Status in docker.io source package in Hirsute: Fix Released Status in unattended-upgrades source package in Hirsute: Won't Fix Bug description: [Impact] Docker uses containerd under the hood. When containerd is upgraded it stops and restarts its service; docker stops when containerd stops but doesn’t restart. Particularly when doing unattended upgrades, an SRU fix rolled out for containerd can result in unexpected and widespread service outages for docker. [Test Case] $ sudo apt install docker.io $ sudo systemctl start docker $ systemctl status docker | grep Active Active: active (running) since[...] $ systemctl status containerd | grep Active Active: active (running) since[...] $ docker pull ubuntu/redis:latest $ docker run -e REDIS_PASSWORD=1234 --network host \ --name test-redis -d ubuntu/redis:latest $ telnet localhost 6379 $ docker container logs test-redis $ sudo apt install --reinstall containerd $ systemctl status containerd | grep Active Active: active (running) since $ systemctl status docker | grep Active Active: inactive (dead) since [...]; 8s ago $ docker container logs test-redis [Where Problems Could Occur] The challenge with this issue is addressing all important corner cases, and as such the biggest risk is that we miss a corner case and fail to keep the two services running when they should. Areas to watch will be failures during start/stop/restart/upgrade type operations. Issues during runtime are unlikely to relate to this change. [Original Report] Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO Starting unattended upgrades script 2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=Ubu
[Touch-packages] [Bug 1906364] Re: [SRU] unattended-upgrade still restarts blacklisted daemons
Hello sascha, or anyone else affected, Accepted docker.io into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/19.03.8-0ubuntu1.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker.io (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal ** Changed in: docker.io (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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons Status in docker.io package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in docker.io source package in Xenial: In Progress Status in unattended-upgrades source package in Xenial: Won't Fix Status in docker.io source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: Won't Fix Status in docker.io source package in Focal: Fix Committed Status in unattended-upgrades source package in Focal: Won't Fix Status in docker.io source package in Groovy: Fix Committed Status in unattended-upgrades source package in Groovy: Won't Fix Status in docker.io source package in Hirsute: Fix Released Status in unattended-upgrades source package in Hirsute: Won't Fix Bug description: [Impact] Docker uses containerd under the hood. When containerd is upgraded it stops and restarts its service; docker stops when containerd stops but doesn’t restart. Particularly when doing unattended upgrades, an SRU fix rolled out for containerd can result in unexpected and widespread service outages for docker. [Test Case] $ sudo apt install docker.io $ sudo systemctl start docker $ systemctl status docker | grep Active Active: active (running) since[...] $ systemctl status containerd | grep Active Active: active (running) since[...] $ docker pull ubuntu/redis:latest $ docker run -e REDIS_PASSWORD=1234 --network host \ --name test-redis -d ubuntu/redis:latest $ telnet localhost 6379 $ docker container logs test-redis $ sudo apt install --reinstall containerd $ systemctl status containerd | grep Active Active: active (running) since $ systemctl status docker | grep Active Active: inactive (dead) since [...]; 8s ago $ docker container logs test-redis [Where Problems Could Occur] The challenge with this issue is addressing all important corner cases, and as such the biggest risk is that we miss a corner case and fail to keep the two services running when they should. Areas to watch will be failures during start/stop/restart/upgrade type operations. Issues during runtime are unlikely to relate to this change. [Original Report] Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/u
[Touch-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound
*** This bug is a duplicate of bug 1797002 *** https://bugs.launchpad.net/bugs/1797002 ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443423/+files/AlsaInfo.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443424/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443425/+files/Dependencies.txt ** Attachment removed: "PaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443426/+files/PaInfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443427/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443428/+files/PulseList.txt ** Attachment removed: "Symptom_PulseAudioLog.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443429/+files/Symptom_PulseAudioLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908064 Title: [Multiple bluetooth speakers, playback] Stuttering sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Constant stuttering sound, stuttering at maybe 10 times/second. More than one speaker with the same symptoms. Speakers work in Windows 10 / macOS 10.14+ running on same hardware. Same speakers work on Ubuntu Mate 18.04 32 bit running on different hardware. Remote control commands work (play/pause button on speakers). Initial pairing and connection requires from 2 to about 10 retries. All tested within 1 m distance. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username3486 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 13:49:26 2020 InstallationDate: Installed on 2020-10-30 (45 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: Crossbeat Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Crossbeat, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 264.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.family: MacBook Air dmi.product.name: MacBookAir5,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+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 1906364] Re: [SRU] unattended-upgrade still restarts blacklisted daemons
Hello sascha, or anyone else affected, Accepted docker.io into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/19.03.13-0ubuntu3.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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: docker.io (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons Status in docker.io package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in docker.io source package in Xenial: In Progress Status in unattended-upgrades source package in Xenial: Won't Fix Status in docker.io source package in Bionic: In Progress Status in unattended-upgrades source package in Bionic: Won't Fix Status in docker.io source package in Focal: In Progress Status in unattended-upgrades source package in Focal: Won't Fix Status in docker.io source package in Groovy: Fix Committed Status in unattended-upgrades source package in Groovy: Won't Fix Status in docker.io source package in Hirsute: Fix Released Status in unattended-upgrades source package in Hirsute: Won't Fix Bug description: [Impact] Docker uses containerd under the hood. When containerd is upgraded it stops and restarts its service; docker stops when containerd stops but doesn’t restart. Particularly when doing unattended upgrades, an SRU fix rolled out for containerd can result in unexpected and widespread service outages for docker. [Test Case] $ sudo apt install docker.io $ sudo systemctl start docker $ systemctl status docker | grep Active Active: active (running) since[...] $ systemctl status containerd | grep Active Active: active (running) since[...] $ docker pull ubuntu/redis:latest $ docker run -e REDIS_PASSWORD=1234 --network host \ --name test-redis -d ubuntu/redis:latest $ telnet localhost 6379 $ docker container logs test-redis $ sudo apt install --reinstall containerd $ systemctl status containerd | grep Active Active: active (running) since $ systemctl status docker | grep Active Active: inactive (dead) since [...]; 8s ago $ docker container logs test-redis [Where Problems Could Occur] The challenge with this issue is addressing all important corner cases, and as such the biggest risk is that we miss a corner case and fail to keep the two services running when they should. Areas to watch will be failures during start/stop/restart/upgrade type operations. Issues during runtime are unlikely to relate to this change. [Original Report] Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO
[Touch-packages] [Bug 1908706] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo sta
** Tags removed: need-duplicate-check -- 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/1908706 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post- installation ha restituito lo stato di errore 1 Status in initramfs-tools package in Ubuntu: New Bug description: while do-release-upgrade from 18.04 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 18 12:22:57 2020 ErrorMessage: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2013-12-11 (2564 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to focal on 2020-12-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1908706/+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 1908706] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo s
Public bug reported: while do-release-upgrade from 18.04 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 18 12:22:57 2020 ErrorMessage: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2013-12-11 (2564 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to focal on 2020-12-18 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- 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/1908706 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post- installation ha restituito lo stato di errore 1 Status in initramfs-tools package in Ubuntu: New Bug description: while do-release-upgrade from 18.04 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 18 12:22:57 2020 ErrorMessage: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2013-12-11 (2564 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to focal on 2020-12-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1908706/+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 1908699] Re: New bugfix release 20.2.6
** Changed in: mesa (Ubuntu Groovy) Status: New => In Progress ** Changed in: mesa (Ubuntu Focal) Status: New => In Progress -- 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/1908699 Title: New bugfix release 20.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: In Progress Status in mesa source package in Groovy: In Progress Bug description: [Impact] This is the last point-release of the 20.2.x-series, we should put it in groovy so latest bugfixes would get there, and for focal because that would minimize the risk of regressions when going from 20.0.x to 20.2.x. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+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 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound
*** This bug is a duplicate of bug 1797002 *** https://bugs.launchpad.net/bugs/1797002 I understand. I was assuming that gnome-shell was big enough to warrant at least one person who could view private reports, and that the message suggested a mistake. Thanks for the info. -- 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/1908064 Title: [Multiple bluetooth speakers, playback] Stuttering sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Constant stuttering sound, stuttering at maybe 10 times/second. More than one speaker with the same symptoms. Speakers work in Windows 10 / macOS 10.14+ running on same hardware. Same speakers work on Ubuntu Mate 18.04 32 bit running on different hardware. Remote control commands work (play/pause button on speakers). Initial pairing and connection requires from 2 to about 10 retries. All tested within 1 m distance. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username3486 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 13:49:26 2020 InstallationDate: Installed on 2020-10-30 (45 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: Crossbeat Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Crossbeat, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 264.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.family: MacBook Air dmi.product.name: MacBookAir5,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+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 1908699] [NEW] New bugfix release 20.2.6
Public bug reported: [Impact] This is the last point-release of the 20.2.x-series, we should put it in groovy so latest bugfixes would get there, and for focal because that would minimize the risk of regressions when going from 20.0.x to 20.2.x. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mesa (Ubuntu Focal) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Affects: mesa (Ubuntu Groovy) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Changed in: mesa (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Groovy) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Description changed: [Impact] This is the last point-release of the 20.2.x-series, we should put it in groovy so latest bugfixes would get there, and for focal because that would minimize the risk of regressions when going from 20.0.x to 20.2.x. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. - [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this - update. + update, since upstream and vendor (Intel) CI machinery have tested + these. -- 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/1908699 Title: New bugfix release 20.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Groovy: New Bug description: [Impact] This is the last point-release of the 20.2.x-series, we should put it in groovy so latest bugfixes would get there, and for focal because that would minimize the risk of regressions when going from 20.0.x to 20.2.x. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+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 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''
Validate on Latitude 9420. Its codec init.conf under /usr/share/alsa/ucm2/codecs/rt715-sdca/init.conf introduced by https://github.com/thesofproject/alsa-ucm-conf/pull/45 The command: cset "name='rt714 ADC 22 Mux' 'DMIC3'" cset "name='rt714 ADC 23 Mux' 'DMIC4'" doesn't work, and internal microphone is not able to use. After update the libasound2. run $ alsactl init $ amixer cget name='rt714 ADC 22 Mux' numid=85,iface=MIXER,name='rt714 ADC 22 Mux' ; type=ENUMERATED,access=rw--,values=1,items=8 ; Item #0 'MIC1' ; Item #1 'MIC2' ; Item #2 'LINE1' ; Item #3 'LINE2' ; Item #4 'DMIC1' ; Item #5 'DMIC2' ; Item #6 'DMIC3' ; Item #7 'DMIC4' : values=6 $ amixer cget name='rt714 ADC 23 Mux' numid=86,iface=MIXER,name='rt714 ADC 23 Mux' ; type=ENUMERATED,access=rw--,values=1,items=8 ; Item #0 'MIC1' ; Item #1 'MIC2' ; Item #2 'LINE1' ; Item #3 'LINE2' ; Item #4 'DMIC1' ; Item #5 'DMIC2' ; Item #6 'DMIC3' ; Item #7 'DMIC4' : values=7 And the internal microphone works. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Recently the ucm added some amixer settings, like this one: cset "name='rt711 ADC 23 Mux' 'MIC2'" This setting is needed for Dell soundwire audio machines, and only this setting is set correctly, the headset-mic could work. And we already backported this ucm to focal. But the alsa-lib ctl parse doesn't support the enum value in the '' yet, so this amixer setting can't be set correctly under current focal and groovy, we need to backport a patch from alsa-lib master branch. [Fix] Backport a patch from upstream, this patch is not in the groovy yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this patch. [Test Case] On the Dell soundwire audio machine, run alsactl init, then check if the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set correctly, it means the alsalib enum ctl parse support both "" and '' now. [Regression Risk] This could introduce failure on setting enum amixer settings, users will experience the failure of audio device like the speaker can't output sound, the mic can't record sound. But this possibility is very low since we have tested this SRU on many LENOVO and Dell machines (with and without soundwire audio), all worked as fine as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+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
