[Touch-packages] [Bug 1929647] Re: debian helper tools for python never updates
stil there ** Attachment added: "update still fails" https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+attachment/5502353/+files/cannot%20update%20Peek%202021-06-04%2008-29.gif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1929647 Title: debian helper tools for python never updates Status in python-debian package in Ubuntu: New Bug description: software updater prompts new updates debian helper tools for python is always one of them but I cannot select the checkbox so debian helper tools for python never updates Here's the screen shot https://i.imgur.com/AjDd5yo.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+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 1918855] Re: Xorg xserver got signal 6 to abort
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11178 -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in Provider for Plainbox - Checkbox: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1918021] Re: Got Setting up libpaper1:amd64 (1.1.28) ... ucf: do not have write privilege to the state data while building simple Docker container
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: docker.io (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1918021 Title: Got Setting up libpaper1:amd64 (1.1.28) ... ucf: do not have write privilege to the state data while building simple Docker container Status in docker.io package in Ubuntu: Confirmed Status in libpaper package in Ubuntu: Invalid Status in ucf package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have simple Dockerfile as shown below: ``` mkdir ~/ubuntu-mate-hirsute cat < ~/ubuntu-mate-hirsute/Dockerfile FROM ubuntu:hirsute ENV SHELL=/bin/bash RUN apt-get update && \ env DEBIAN_FRONTEND=noninteractive apt-get install -y ubuntu-mate-desktop CMD ["mate-session"] EOF ``` 2. Build this Dockerfile by the command shown below docker build ~/ubuntu-mate-hirsute/ -t ubuntu-mate:hirsute Expected result: * Docker container is built and tagged as it was requested - ubuntu-mate:hirsute . Actual results: * Docker container is not built, have the following errors instead: ... Setting up libpaper1:amd64 (1.1.28) ... ucf: do not have write privilege to the state data dpkg: error processing package libpaper1:amd64 (--configure): installed libpaper1:amd64 package post-installation script subprocess returned error exit status 1 ... dpkg: dependency problems prevent configuration of libgs9:amd64: libgs9:amd64 depends on libpaper1; however: Package libpaper1:amd64 is not configured yet. dpkg: error processing package libgs9:amd64 (--configure): dependency problems - leaving unconfigured ... Setting up fonts-tlwg-umpush (1:0.7.2-1build1) ... dpkg: dependency problems prevent configuration of libpaper-utils: libpaper-utils depends on libpaper1; however: Package libpaper1:amd64 is not configured yet. dpkg: error processing package libpaper-utils (--configure): dependency problems - leaving unconfigured Setting up samba-common (2:4.13.3+dfsg-1ubuntu2) ... ucf: do not have write privilege to the state data dpkg: error processing package samba-common (--configure): installed samba-common package post-installation script subprocess returned error exit status 1 ... dpkg: dependency problems prevent configuration of ghostscript: ghostscript depends on libgs9 (= 9.53.3~dfsg-7); however: Package libgs9:amd64 is not configured yet. dpkg: error processing package ghostscript (--configure): dependency problems - leaving unconfigured ... Setting up fonts-tlwg-mono (1:0.7.2-1build1) ... dpkg: dependency problems prevent configuration of libatrildocument3: libatrildocument3 depends on libspectre1 (>= 0.2.3); however: Package libspectre1:amd64 is not configured yet. dpkg: error processing package libatrildocument3 (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of cups-daemon: cups-daemon depends on libpaper1; however: Package libpaper1:amd64 is not configured yet. dpkg: error processing package cups-daemon (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of atril: atril depends on libatrildocument3 (= 1.24.0-1); however: Package libatrildocument3 is not configured yet. dpkg: error processing package atril (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of libatrilview3: libatrilview3 depends on libatrildocument3 (= 1.24.0-1); however: Package libatrildocument3 is not configured yet. dpkg: error processing package libatrilview3 (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of smbclient: smbclient depends on samba-common (= 2:4.13.3+dfsg-1ubuntu2); however: Package samba-common is not configured yet. dpkg: error processing package smbclient (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of samba-common-bin: samba-common-bin depends on samba-common (= 2:4.13.3+dfsg-1ubuntu2); however: Package samba-common is not configured yet. dpkg: error processing package samba-common-bin (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of printer-driver-ptouch: printer-driver-ptouch depends on ghostscript; however: Package ghostscript is not configured yet. dpkg: error processing package printer-driver-ptouch (--configure): dependency problems - leaving unconfigured ... dpkg: dependency problems prevent configuration of cups-filters: cups-filters depends on ghostscript; however: Package ghostscript
[Touch-packages] [Bug 804178] Re: "Front" ALSA volume control affects headphones on some machines
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/804178 Title: "Front" ALSA volume control affects headphones on some machines Status in pulseaudio package in Ubuntu: Expired Bug description: There is no sound playing through my headphones, nor through my computer speakers. They worked for a moment, but stopped abruptly. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfce78000 irq 20' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,103c2a9e,00100202' Controls : 35 Simple ctrls : 20 Date: Fri Jul 1 07:59:15 2011 LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: Internal Audio - HDA NVidia Symptom_DevicesInUse: 4622 10827 Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [AY020AA-ABA p6320f, Realtek ALC888, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: VIOLET6 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 6.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/12/2009:svnHP-Pavilion:pnAY020AA-ABAp6320f:pvr:rvnPEGATRONCORPORATION:rnVIOLET6:rvr6.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: AY020AA-ABA p6320f dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/804178/+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 804178] Re: "Front" ALSA volume control affects headphones on some machines
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/804178 Title: "Front" ALSA volume control affects headphones on some machines Status in pulseaudio package in Ubuntu: Expired Bug description: There is no sound playing through my headphones, nor through my computer speakers. They worked for a moment, but stopped abruptly. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfce78000 irq 20' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,103c2a9e,00100202' Controls : 35 Simple ctrls : 20 Date: Fri Jul 1 07:59:15 2011 LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: Internal Audio - HDA NVidia Symptom_DevicesInUse: 4622 10827 Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [AY020AA-ABA p6320f, Realtek ALC888, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: VIOLET6 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 6.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/12/2009:svnHP-Pavilion:pnAY020AA-ABAp6320f:pvr:rvnPEGATRONCORPORATION:rnVIOLET6:rvr6.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: AY020AA-ABA p6320f dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/804178/+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 40214] Re: ld checks for libs in wrong order. it should be inline with ld.so and check configured folders first.
** Changed in: binutils Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/40214 Title: ld checks for libs in wrong order. it should be inline with ld.so and check configured folders first. Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: if one installs a new version of a lib to /usr/local/lib and has an old version from the system in /usr/lib linking fails with gcc. it tries to link the version in /usr/lib removing the version from /usr/lib, linking works. ldd shows the right version in /usr/local/lib since the version of libtool in ubuntu does not include dependency_libs from the .la file, one has to specify the dependency libs manualy or remove the libs from /usr/lib; both merly workarounds that i dont want to use upstream. not sure what the right place for this bug is. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/40214/+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 40214]
Documented -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/40214 Title: ld checks for libs in wrong order. it should be inline with ld.so and check configured folders first. Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: if one installs a new version of a lib to /usr/local/lib and has an old version from the system in /usr/lib linking fails with gcc. it tries to link the version in /usr/lib removing the version from /usr/lib, linking works. ldd shows the right version in /usr/local/lib since the version of libtool in ubuntu does not include dependency_libs from the .la file, one has to specify the dependency libs manualy or remove the libs from /usr/lib; both merly workarounds that i dont want to use upstream. not sure what the right place for this bug is. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/40214/+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 40214]
The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;h=364d77297723712a2952072fd6768601f17070bd commit 364d77297723712a2952072fd6768601f17070bd Author: Alan Modra Date: Thu Jun 3 18:32:30 2021 +0930 PR2589, ld vs. ld.so PR 2589 * ld.texi (link-time runtime library search path): Mention plugin library path. Correct order of search. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/40214 Title: ld checks for libs in wrong order. it should be inline with ld.so and check configured folders first. Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: if one installs a new version of a lib to /usr/local/lib and has an old version from the system in /usr/lib linking fails with gcc. it tries to link the version in /usr/lib removing the version from /usr/lib, linking works. ldd shows the right version in /usr/local/lib since the version of libtool in ubuntu does not include dependency_libs from the .la file, one has to specify the dependency libs manualy or remove the libs from /usr/lib; both merly workarounds that i dont want to use upstream. not sure what the right place for this bug is. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/40214/+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 1843479]
There's a missing range check when decoding the LDST instruction.
https://bubbleshooter.io/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1843479
Title:
gzip in Ubuntu Eoan results in Exec format error on WSL1
Status in binutils:
Fix Released
Status in binutils package in Ubuntu:
Fix Released
Status in gzip package in Ubuntu:
Fix Released
Status in binutils source package in Eoan:
Fix Released
Status in gzip source package in Eoan:
Fix Released
Bug description:
[Impact]
* Running gzip on WSL1 results in the following error:
$ gzip
-bash: /bin/gzip: cannot execute binary file: Exec format error
* The error occurs frequently in package updates and makes gzip inoperable
on WSL1
* The problem is caused by PT_LOAD offset pointing past the end of file and
the fix is fixing strip to not generate such ELF files and recompiling gzip
with the fixed strip.
[Test Case]
* Check the gzip binary for wrong offset:
$ FILE=/usr/bin/gzip; readelf -W --program-headers $FILE | awk -v
size=$(stat -c %s $FILE) '/^ LOAD/ {if (strtonum($2) > size) {print "wrong
offset ("$2" ("strtonum($2)") points past EOF:" size; exit 1;}}'
[ Regression Potential ]
* The binutils fix could cause binutils to generate invalid ELF files. The
fix is very small and isolated and has been tested and accepted by upstream,
which makes such problems unlikely.
* Bugs in the toolchain in general can make the rebuilt gzip show new
errors, but this generally applies to many SRUs and security updates. The
testing period in proposed should mitigate this risk.
[Other Info]
* Binutils 2.33.1-6ubuntu1.1 was accidentally built in -proposed
instead of in a PPA. I've rebuilt it in https://launchpad.net/~ci-
train-ppa-service/+archive/ubuntu/3878 for the -security pocket as
2.33-2ubuntu1.2.
[Originial Bug Text]
Summary:
Running gzip on WSL1 results in the following error:
$ gzip
-bash: /bin/gzip: cannot execute binary file: Exec format error
What I expect to happen:
gzip executes correctly on WSL1.
What happens instead:
gzip fails with an Exec format error.
Notes:
I suspect a change in how gzip is being built for Eoan is causing
issues with ELF parsing on the WSL1 translation layer. For example:
On Disco with gzip 1.9-3:
$ file /bin/gzip
/bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux
3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped
On Eoan with gzip 1.10-0ubuntu3:
$ file /bin/gzip
/bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2,
BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0,
stripped
Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do
not believe this is an issue in 1.10 because this error does not occur
when building gzip from GNU project source on Ubuntu Eoan.
Justifications:
WSL1 will need to be patched in future Windows builds for this change
in ELF. However that patch will likely not be backported to older
builds of Windows, including Windows Enterprise/Server 2019.
To ensure Eoan can run on current and older builds of Windows Ubuntu
should consider looking at how it's building gzip and see if it can be
made to 'play nice' until WSL1 can be updated.
This was originally reported here:
https://github.com/microsoft/WSL/issues/4461
Details:
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
gzip:
Installed: 1.10-0ubuntu3
Candidate: 1.10-0ubuntu3
Version table:
*** 1.10-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1843479/+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 1785383] Re: missing EDNS0 record confuses systemd-resolved
ubuntu@lp1785383-b:~$ dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.47 amd64system and service manager
ubuntu@lp1785383-b:~$ sudo systemd-resolve --reset-server-features
ubuntu@lp1785383-b:~$ sudo systemd-resolve --flush-caches
ubuntu@lp1785383-b:~$ time host test.test
test.test has address 1.2.3.4
real0m5.024s
user0m0.012s
sys 0m0.008s
ubuntu@lp1785383-b:~$ dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.48 amd64system and service manager
ubuntu@lp1785383-b:~$ sudo systemd-resolve --reset-server-features
ubuntu@lp1785383-b:~$ sudo systemd-resolve --flush-caches
ubuntu@lp1785383-b:~$ time host test.test
test.test has address 1.2.3.4
real0m0.023s
user0m0.013s
sys 0m0.000s
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
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/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Fix Released
Status in dnsmasq package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in dnsmasq source package in Bionic:
Triaged
Status in systemd source package in Bionic:
Fix Committed
Status in dnsmasq source package in Focal:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in dnsmasq source package in Groovy:
Fix Released
Status in systemd source package in Groovy:
Fix Committed
Status in dnsmasq source package in Hirsute:
Fix Released
Status in systemd source package in Hirsute:
Fix Committed
Status in dnsmasq source package in Impish:
Fix Released
Status in systemd source package in Impish:
Fix Committed
Bug description:
[Impact]
dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer
for a domain it is authoritative for. systemd-resolved seems to get confused by
this in certain circumstances; when using the stub resolver and requesting an
address for which there are no records, there can sometimes be a five
second hang in resolution.
[Fix]
This is fixed by upstream commit
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
Not sure if it is worth cherry picking? I imagine the most likely
trigger will be dnsmasq on routers which are not likely to be running
Ubuntu, but maybe just in case.
I also think there are some logic issues in systemd-resolved, upstream
bug filed:
https://github.com/systemd/systemd/issues/9785
[Test Case]
Simple-ish test case for bionic:
---
IFACE=dummy0
SUBNET=10.0.0
ip link add $IFACE type dummy
ifconfig $IFACE ${SUBNET}.1/24
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,${SUBNET}.1 --server=/test/ &
dig -t a test.test @10.0.0.1 | grep EDNS
# should return "; EDNS ..."
dig -t test.test @10.0.0.1 | grep EDNS
# again, should return "; EDNS ..." but doesn't
---
To reproduce the systemd-resolved side of the problem
---
# as above, but
# now configure systemd-resolved to look at only 10.0.0.1, then
systemd-resolve --reset-server-features
# should exhibit five second delay then connect, assuming sshd is running :)
ssh test.test
---
More detailed test case for focal and later:
install dnsmasq on a bionic system and start it, listening to an
interface that is externally reachable, e.g. for a normal libvirt vm
with interface name 'ens3':
IFACE=ens3
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,1.2.3.4 --server=/test/
note that the '1.2.3.4' address doesn't matter, any addr is ok.
then setup a test system that can reach the dnsmasq system, and
configure networkd to use the dnsmasq server, e.g. using config like:
[Match]
Name=ens3
[Network]
DHCP=yes
DNS=DNSMASQ_IP_ADDRESS
Domains=test
[DHCPv4]
UseDNS=no
UseDomains=no
replace 'DNSMASQ_IP_ADDRESS' with the addr of the bionic system where
dnsmasq is running, and replace 'ens3' with whatever the test system
interface name is. Then restart systemd-networkd, and test:
systemd-resolve --reset-server-features
systemd-resolve --flush-caches
host test.test
The lookup using 'host' should complete immediately;.
[Discussion]
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsmasq-base 2.79-1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Aug 4 11:33:56 2018
InstallationDate: Installed on 2018-05-31 (64 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
[Touch-packages] [Bug 1785383] Re: missing EDNS0 record confuses systemd-resolved
ubuntu@lp1785383-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.6 amd64system and service manager
ubuntu@lp1785383-f:~$ systemd-resolve --reset-server-features
ubuntu@lp1785383-f:~$ systemd-resolve --flush-caches
ubuntu@lp1785383-f:~$ time host test.test
test.test has address 1.2.3.4
real0m5.047s
user0m0.015s
sys 0m0.018s
ubuntu@lp1785383-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.7 amd64system and service manager
ubuntu@lp1785383-f:~$ systemd-resolve --reset-server-features
ubuntu@lp1785383-f:~$ systemd-resolve --flush-caches
ubuntu@lp1785383-f:~$ time host test.test
test.test has address 1.2.3.4
real0m0.020s
user0m0.008s
sys 0m0.008s
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Fix Released
Status in dnsmasq package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in dnsmasq source package in Bionic:
Triaged
Status in systemd source package in Bionic:
Fix Committed
Status in dnsmasq source package in Focal:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in dnsmasq source package in Groovy:
Fix Released
Status in systemd source package in Groovy:
Fix Committed
Status in dnsmasq source package in Hirsute:
Fix Released
Status in systemd source package in Hirsute:
Fix Committed
Status in dnsmasq source package in Impish:
Fix Released
Status in systemd source package in Impish:
Fix Committed
Bug description:
[Impact]
dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer
for a domain it is authoritative for. systemd-resolved seems to get confused by
this in certain circumstances; when using the stub resolver and requesting an
address for which there are no records, there can sometimes be a five
second hang in resolution.
[Fix]
This is fixed by upstream commit
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
Not sure if it is worth cherry picking? I imagine the most likely
trigger will be dnsmasq on routers which are not likely to be running
Ubuntu, but maybe just in case.
I also think there are some logic issues in systemd-resolved, upstream
bug filed:
https://github.com/systemd/systemd/issues/9785
[Test Case]
Simple-ish test case for bionic:
---
IFACE=dummy0
SUBNET=10.0.0
ip link add $IFACE type dummy
ifconfig $IFACE ${SUBNET}.1/24
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,${SUBNET}.1 --server=/test/ &
dig -t a test.test @10.0.0.1 | grep EDNS
# should return "; EDNS ..."
dig -t test.test @10.0.0.1 | grep EDNS
# again, should return "; EDNS ..." but doesn't
---
To reproduce the systemd-resolved side of the problem
---
# as above, but
# now configure systemd-resolved to look at only 10.0.0.1, then
systemd-resolve --reset-server-features
# should exhibit five second delay then connect, assuming sshd is running :)
ssh test.test
---
More detailed test case for focal and later:
install dnsmasq on a bionic system and start it, listening to an
interface that is externally reachable, e.g. for a normal libvirt vm
with interface name 'ens3':
IFACE=ens3
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,1.2.3.4 --server=/test/
note that the '1.2.3.4' address doesn't matter, any addr is ok.
then setup a test system that can reach the dnsmasq system, and
configure networkd to use the dnsmasq server, e.g. using config like:
[Match]
Name=ens3
[Network]
DHCP=yes
DNS=DNSMASQ_IP_ADDRESS
Domains=test
[DHCPv4]
UseDNS=no
UseDomains=no
replace 'DNSMASQ_IP_ADDRESS' with the addr of the bionic system where
dnsmasq is running, and replace 'ens3' with whatever the test system
interface name is. Then restart systemd-networkd, and test:
systemd-resolve --reset-server-features
systemd-resolve --flush-caches
host test.test
The lookup using 'host' should complete immediately;.
[Discussion]
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsmasq-base 2.79-1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Aug 4 11:33:56 2018
InstallationDate: Installed on 2018-05-31 (64 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1785383] Re: missing EDNS0 record confuses systemd-resolved
ubuntu@lp1785383-g:~$ dpkg -l systemd|grep systemd
ii systemd246.6-1ubuntu1.3 amd64system and service manager
ubuntu@lp1785383-g:~$ systemd-resolve --reset-server-features
ubuntu@lp1785383-g:~$ systemd-resolve --flush-caches
ubuntu@lp1785383-g:~$ time host test.test
test.test has address 1.2.3.4
real0m5.040s
user0m0.013s
sys 0m0.013s
ubuntu@lp1785383-g:~$ dpkg -l systemd|grep systemd
ii systemd246.6-1ubuntu1.4 amd64system and service manager
ubuntu@lp1785383-g:~$ systemd-resolve --reset-server-features
ubuntu@lp1785383-g:~$ systemd-resolve --flush-caches
ubuntu@lp1785383-g:~$ time host test.test
test.test has address 1.2.3.4
real0m0.023s
user0m0.010s
sys 0m0.011s
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Fix Released
Status in dnsmasq package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in dnsmasq source package in Bionic:
Triaged
Status in systemd source package in Bionic:
Fix Committed
Status in dnsmasq source package in Focal:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in dnsmasq source package in Groovy:
Fix Released
Status in systemd source package in Groovy:
Fix Committed
Status in dnsmasq source package in Hirsute:
Fix Released
Status in systemd source package in Hirsute:
Fix Committed
Status in dnsmasq source package in Impish:
Fix Released
Status in systemd source package in Impish:
Fix Committed
Bug description:
[Impact]
dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer
for a domain it is authoritative for. systemd-resolved seems to get confused by
this in certain circumstances; when using the stub resolver and requesting an
address for which there are no records, there can sometimes be a five
second hang in resolution.
[Fix]
This is fixed by upstream commit
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
Not sure if it is worth cherry picking? I imagine the most likely
trigger will be dnsmasq on routers which are not likely to be running
Ubuntu, but maybe just in case.
I also think there are some logic issues in systemd-resolved, upstream
bug filed:
https://github.com/systemd/systemd/issues/9785
[Test Case]
Simple-ish test case for bionic:
---
IFACE=dummy0
SUBNET=10.0.0
ip link add $IFACE type dummy
ifconfig $IFACE ${SUBNET}.1/24
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,${SUBNET}.1 --server=/test/ &
dig -t a test.test @10.0.0.1 | grep EDNS
# should return "; EDNS ..."
dig -t test.test @10.0.0.1 | grep EDNS
# again, should return "; EDNS ..." but doesn't
---
To reproduce the systemd-resolved side of the problem
---
# as above, but
# now configure systemd-resolved to look at only 10.0.0.1, then
systemd-resolve --reset-server-features
# should exhibit five second delay then connect, assuming sshd is running :)
ssh test.test
---
More detailed test case for focal and later:
install dnsmasq on a bionic system and start it, listening to an
interface that is externally reachable, e.g. for a normal libvirt vm
with interface name 'ens3':
IFACE=ens3
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,1.2.3.4 --server=/test/
note that the '1.2.3.4' address doesn't matter, any addr is ok.
then setup a test system that can reach the dnsmasq system, and
configure networkd to use the dnsmasq server, e.g. using config like:
[Match]
Name=ens3
[Network]
DHCP=yes
DNS=DNSMASQ_IP_ADDRESS
Domains=test
[DHCPv4]
UseDNS=no
UseDomains=no
replace 'DNSMASQ_IP_ADDRESS' with the addr of the bionic system where
dnsmasq is running, and replace 'ens3' with whatever the test system
interface name is. Then restart systemd-networkd, and test:
systemd-resolve --reset-server-features
systemd-resolve --flush-caches
host test.test
The lookup using 'host' should complete immediately;.
[Discussion]
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsmasq-base 2.79-1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Aug 4 11:33:56 2018
InstallationDate: Installed on 2018-05-31 (64 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1785383] Re: missing EDNS0 record confuses systemd-resolved
ubuntu@lp1785383-h:~$ dpkg -l systemd|grep systemd
ii systemd247.3-3ubuntu3 amd64system and service manager
ubuntu@lp1785383-h:~$ systemd-resolve --reset-server-features
ubuntu@lp1785383-h:~$ systemd-resolve --flush-caches
ubuntu@lp1785383-h:~$ time host test.test
test.test has address 1.2.3.4
real0m5.066s
user0m0.012s
sys 0m0.012s
ubuntu@lp1785383-h:~$ dpkg -l systemd|grep systemd
ii systemd247.3-3ubuntu3.1 amd64system and service manager
ubuntu@lp1785383-h:~$ systemd-resolve --reset-server-features
ubuntu@lp1785383-h:~$ systemd-resolve --flush-caches
ubuntu@lp1785383-h:~$ time host test.test
test.test has address 1.2.3.4
real0m0.044s
user0m0.006s
sys 0m0.017s
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
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/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Fix Released
Status in dnsmasq package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in dnsmasq source package in Bionic:
Triaged
Status in systemd source package in Bionic:
Fix Committed
Status in dnsmasq source package in Focal:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in dnsmasq source package in Groovy:
Fix Released
Status in systemd source package in Groovy:
Fix Committed
Status in dnsmasq source package in Hirsute:
Fix Released
Status in systemd source package in Hirsute:
Fix Committed
Status in dnsmasq source package in Impish:
Fix Released
Status in systemd source package in Impish:
Fix Committed
Bug description:
[Impact]
dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer
for a domain it is authoritative for. systemd-resolved seems to get confused by
this in certain circumstances; when using the stub resolver and requesting an
address for which there are no records, there can sometimes be a five
second hang in resolution.
[Fix]
This is fixed by upstream commit
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
Not sure if it is worth cherry picking? I imagine the most likely
trigger will be dnsmasq on routers which are not likely to be running
Ubuntu, but maybe just in case.
I also think there are some logic issues in systemd-resolved, upstream
bug filed:
https://github.com/systemd/systemd/issues/9785
[Test Case]
Simple-ish test case for bionic:
---
IFACE=dummy0
SUBNET=10.0.0
ip link add $IFACE type dummy
ifconfig $IFACE ${SUBNET}.1/24
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,${SUBNET}.1 --server=/test/ &
dig -t a test.test @10.0.0.1 | grep EDNS
# should return "; EDNS ..."
dig -t test.test @10.0.0.1 | grep EDNS
# again, should return "; EDNS ..." but doesn't
---
To reproduce the systemd-resolved side of the problem
---
# as above, but
# now configure systemd-resolved to look at only 10.0.0.1, then
systemd-resolve --reset-server-features
# should exhibit five second delay then connect, assuming sshd is running :)
ssh test.test
---
More detailed test case for focal and later:
install dnsmasq on a bionic system and start it, listening to an
interface that is externally reachable, e.g. for a normal libvirt vm
with interface name 'ens3':
IFACE=ens3
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,1.2.3.4 --server=/test/
note that the '1.2.3.4' address doesn't matter, any addr is ok.
then setup a test system that can reach the dnsmasq system, and
configure networkd to use the dnsmasq server, e.g. using config like:
[Match]
Name=ens3
[Network]
DHCP=yes
DNS=DNSMASQ_IP_ADDRESS
Domains=test
[DHCPv4]
UseDNS=no
UseDomains=no
replace 'DNSMASQ_IP_ADDRESS' with the addr of the bionic system where
dnsmasq is running, and replace 'ens3' with whatever the test system
interface name is. Then restart systemd-networkd, and test:
systemd-resolve --reset-server-features
systemd-resolve --flush-caches
host test.test
The lookup using 'host' should complete immediately;.
[Discussion]
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsmasq-base 2.79-1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Aug 4 11:33:56 2018
InstallationDate: Installed on 2018-05-31 (64 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping
** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- 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/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Status in systemd source package in Hirsute: Fix Committed Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1929849] Re: ftbfs on hirsute due to kernel changing type of RFKILL_EVENT_SIZE_V1
successfully built on hirsute.
** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute
--
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/1929849
Title:
ftbfs on hirsute due to kernel changing type of RFKILL_EVENT_SIZE_V1
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Hirsute:
Fix Committed
Bug description:
[impact]
ftbfs
[test case]
try to build, e.g.:
https://launchpadlibrarian.net/540746512/buildlog_ubuntu-hirsute-
amd64.systemd_247.3-3ubuntu3.1_BUILDING.txt.gz
../src/rfkill/rfkill.c: In function ‘load_state’:
../src/rfkill/rfkill.c:180:15: warning: comparison of integer expressions of
different signedness: ‘ssize_t’ {aka ‘long int’} and ‘long unsigned int’
[-Wsign-compare]
180 | if (l < RFKILL_EVENT_SIZE_V1)
[regression potential]
any regression would likely cause ftbfs or could cause improper
reading/parsing of the kernel rfkill data
[scope]
this is needed only for h
this is fixed upstream in systemd by commit ab1aa6368a8 which was
pulled into i already.
this does not exist for g or earlier, as the upstream kernel commit
71826654ce401 changed the macro value and introduced this problem, and
that was first included in kernel v5.12 and then backported into
hirsute v5.11 kernel in commit a8c36c7222055 which was first included
in Ubuntu-5.11.0-18.19
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1929849/+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 1921475] Re: [2.9.2] Commissioning does not collect correct storage information
> The disks are not SCSI, but I suspect they are identified as such due to the HBA? yes, your system sees the disks as scsi: > "type": "scsi" -- 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/1921475 Title: [2.9.2] Commissioning does not collect correct storage information Status in lxd: Fix Released Status in MAAS: Invalid Status in systemd package in Ubuntu: Invalid Bug description: MAAS version 2.9.2 When commissioning servers with different storage types (SSDs in a virtual disk behind RAID controller, NVMes and HDDs), but everything shows up tagged as SSD. The commissioning step 50-maas-01-commissioning is generating _incorrect_ storage info such as a random serial and it’s missing the rpm for the virtual disk (behind RAID controller) and the HDDs. The commissioning step maas-lshw generates the correct info, but is not used. I have added screenshot of storage after commission and outputs from both 50-maas-01-commissioning and maas-lshw here: https://discourse.maas.io/t/how-to-work-with-storage- tags/4344/3?u=szeestraten See https://discourse.maas.io/t/how-to-work-with-storage-tags/4344 for conversation To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1921475/+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 1929824] Re: Icons do not appear in the Qt version of "Software & Updates"
*** This bug is a duplicate of bug 1930697 *** https://bugs.launchpad.net/bugs/1930697 Marked as a duplicate of #1930697 as it is the same problem. ** This bug has been marked a duplicate of bug 1930697 Qt applications are opened corruptly in root mode and appimages -- 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/1929824 Title: Icons do not appear in the Qt version of "Software & Updates" Status in software-properties package in Ubuntu: New Bug description: Icons (excluding "V" icons) do not appear in the Qt version of "Software & Updates". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1929824/+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 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt
This bug was fixed in the package python-apt - 2.1.3ubuntu1.4
---
python-apt (2.1.3ubuntu1.4) groovy; urgency=medium
* debfile: Pass `Name` instead of `Binary` to ExtractTar.
Passing the binary causes it to fail trying to find the `false`
compressor when a binary for a given compressor is not installed.
(LP: #1926437)
* Update mirror lists
-- Julian Andres Klode Thu, 29 Apr 2021 15:31:59
+0200
** Changed in: python-apt (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Released
Status in python-apt source package in Bionic:
Fix Released
Status in python-apt source package in Focal:
Fix Released
Status in python-apt source package in Groovy:
Fix Released
Status in python-apt source package in Hirsute:
Fix Released
Status in python-apt source package in Impish:
Fix Released
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1930738] [NEW] network configuration failed on reboot
Public bug reported:
This issue was reported at
https://github.com/systemd/systemd/issues/17012
**Used distribution**
> Ubuntu 20.04.1 LTS
**systemd version the issue has been seen with**
> 245.4-4ubuntu3.2
**Issue details**
I configured 255 IPv4 address (including primary IP) using netplan but when the
server restart, it time out on configuring the interface. If I limit total
IPv4 addresses to 181 or less, it works. But anything larger than 181 fails.
Below are my configurations and error logs.
**/etc/netplan/10-ens3.yaml**
```
network:
version: 2
renderer: networkd
ethernets:
ens3:
dhcp4: no
addresses:
- 140.XX.XX.XX/23
- 103.XXX.XX.1/24
- 103.XXX.XX.2/24
- CONTINUED IP ADDRESS UPTO BELOW ...
- 103.XXX.XX.254/24
gateway4: 140.XX.XX.X
nameservers:
addresses: [1.1.1.1, 1.0.0.1]
routes:
- to: 169.254.0.0/16
via: 140.XX.XX.X
metric: 100
```
The above config works if I run `netplan apply` but when I reboot, it does not
work.
**networkctl**
```
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 ens3 etherroutablefailed
2 links listed.
```
**/etc/systemd/system/systemd-networkd.service.d/override.conf**
```
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
```
**systemctl status systemd-networkd.service**
```
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service;
enabled-runtime; vendor preset: enabled)
Drop-In: /etc/systemd/system/systemd-networkd.service.d
└─override.conf
Active: active (running) since Thu 2020-09-10 19:46:58 UTC; 1min 36s ago
Docs: man:systemd-networkd.service(8)
Main PID: 346 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 1074)
Memory: 3.8M
CGroup: /system.slice/systemd-networkd.service
└─346 /lib/systemd/systemd-networkd
Sep 10 19:47:03 test-server systemd-networkd[346]: NDISC: Sent Router
Solicitation, next solicitation in 7s
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: No RA received before
link confirmation timeout
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Invoking callback for
'timeout' event.
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Sent Router
Solicitation, next solicitation in 15s
Sep 10 19:47:23 test-server systemd-networkd[346]: Assertion 'm->sealed' failed
at src/libsystemd/sd-netlink/netlink-message.c:582, function
netlink_message_read_internal(). Ignoring.
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Could not set address:
Connection timed out
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Failed
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: State changed:
configuring -> failed
Sep 10 19:47:23 test-server systemd-networkd[346]: Sent message type=signal
sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=13
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sep 10 19:47:23 test-server systemd-networkd[346]: NDISC: Stopping IPv6 Router
Solicitation client
```
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930738
Title:
network configuration failed on reboot
Status in systemd package in Ubuntu:
New
Bug description:
This issue was reported at
https://github.com/systemd/systemd/issues/17012
**Used distribution**
> Ubuntu 20.04.1 LTS
**systemd version the issue has been seen with**
> 245.4-4ubuntu3.2
**Issue details**
I configured 255 IPv4 address (including primary IP) using netplan but when
the server restart, it time out on configuring the interface. If I limit total
IPv4 addresses to 181 or less, it works. But anything larger than 181 fails.
Below are my configurations and error logs.
**/etc/netplan/10-ens3.yaml**
```
network:
version: 2
renderer: networkd
ethernets:
ens3:
dhcp4: no
addresses:
- 140.XX.XX.XX/23
- 103.XXX.XX.1/24
- 103.XXX.XX.2/24
- CONTINUED IP ADDRESS UPTO BELOW ...
- 103.XXX.XX.254/24
gateway4: 140.XX.XX.X
nameservers:
addresses: [1.1.1.1, 1.0.0.1]
routes:
- to: 169.254.0.0/16
via: 140.XX.XX.X
metric: 100
```
The above config works if I run `netplan apply` but when I reboot, it does
not work.
**networkctl**
```
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 ens3 etherroutablefailed
2 links listed.
```
**/etc/systemd/system/systemd-networkd.service.d/override.conf**
```
[Service]
[Touch-packages] [Bug 1929122] Re: networkd crashes when advertising blackhole route thru BGP
Hey Brian, Works like a charm! root@routing-focal-l3:~# uname -a Linux routing-focal-l3 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@routing-focal-l3:~# systemd --version systemd 245 (245.4-4ubuntu3.7) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid The test performed was the one described in the bug report. Test case: - add "aggregate-address X.X.X.X/X" to frr - restart frr and blackhole route is installed After the blackhole route was installed networkd was still working fine which confirms the bug was fixed. Thanks! BR, Matija -- 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/1929122 Title: networkd crashes when advertising blackhole route thru BGP Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Invalid Status in systemd source package in Focal: Fix Committed Bug description: [impact] systemd-networkd crashes due to assertion failure [test case] run systemd-networkd and FRR as described in original description below [regression potential] and regression would likely involve incorrectly configured routes [scope] this is needed only for f this is fixed upstream by commit 25b831bac8a5e545e1eda5199392c11c7aed4e42 which is first in v246, so this is fixed in groovy and later the code involved in this isn't present in b so this doesn't apply there [original description] lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.6 [Impact] Networkd crashes when a blackhole route (route aggregation is installed as a blackhole route) is advertised via FRR. [Fix] networkd should not crash [Test case] Bug was reported to systemd (not accepted because systemd version too old) where a test case is described: https://github.com/systemd/systemd/issues/19648 Lower in the comment you can find the full debug log from networkd. Here you can see the core dump: https://drive.google.com/file/d/1tCKiOSnGkLbx3w9du5_NNepkOQZC_hx7/view?usp=sharing For convenience I also packed the relevant parts of the prod env in a vagrant box showing the issue: vagrant init matijavizintin/networkd- debug After some more testing i noticed that immediately after the route is being advertised, networkd detects the change and crashes with "Assertion 'ifindex' failed at src/network/networkd-link.c:757, function link_get(). Aborting." Steps how it happens: 1. networkd is running 2. frr is started without advertising the aggregated address 3. add aggregated address and reload frr 4. blackhole route is installed and networkd crashes with the error above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1929122/+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 1930732] Re: ubuntu-release-upgrader crashed with apt_pkg.Error: E:can not open /var/lib/apt/lists/in.archive.ubuntu.com_ubuntu_dists_bionic_InRelease - fopen (13: Permission den
I was able to recreate this my using "chmod o-r /var/lib/apt/lists/*". Is this a configuration issue on the system or should apt cache only be used by root? ** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1930732 Title: ubuntu-release-upgrader crashed with apt_pkg.Error: E:can not open /var/lib/apt/lists/in.archive.ubuntu.com_ubuntu_dists_bionic_InRelease - fopen (13: Permission denied), E:The package lists or status file could not be parsed or opened. Status in python-apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-release-upgrader. This problem was most recently seen with package version 1:20.10.16, the problem page at https://errors.ubuntu.com/problem/31fbeeb9c2355df96a76732a48d29d35851ada3d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1930732/+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 1925320] Autopkgtest regression report (xorg-server/2:1.20.11-1ubuntu1~20.04.1)
All autopkgtests for the newly accepted xorg-server (2:1.20.11-1ubuntu1~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: notepadqq/2.0.0~beta1-1build1 (armhf) ubuntu-release-upgrader/1:20.04.33 (s390x, ppc64el, arm64, armhf, amd64) apport/2.20.11-0ubuntu27.18 (amd64) bambam/1.0.1+dfsg-1 (arm64, armhf) aptdaemon/1.1.1+bzr982-0ubuntu32.3 (s390x, ppc64el, armhf, amd64) libsoup2.4/2.70.0-1 (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/focal/update_excuses.html#xorg-server [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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-12 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake
This bug does no more happened since several weeks on my Ubuntu 20.04/Nvidia card GTX770 -- 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/1888598 Title: Pulseaudio breaks HDMI audio on sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1930550] Re: usb sound devices crackling
Here connected audeze (Port 8: Dev 8) and xd05p ( Port 1: Dev 7). It share bus 3, but only keyboard and mouse here. i have no other usb. Cracks exists even if only one usb audio is connected at a time. And the major thing - it was fine before upgrade. /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M |__ Port 5: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 5: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 3: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 3: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 8: Dev 8, If 0, Class=Audio, Driver=snd-usb-audio, 480M |__ Port 8: Dev 8, If 1, Class=Audio, Driver=snd-usb-audio, 480M |__ Port 8: Dev 8, If 2, Class=Audio, Driver=snd-usb-audio, 480M |__ Port 8: Dev 8, If 3, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 9: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 7, If 1, Class=Audio, Driver=snd-usb-audio, 480M |__ Port 1: Dev 7, If 2, Class=Application Specific Interface, Driver=, 480M |__ Port 1: Dev 7, If 0, Class=Audio, Driver=snd-usb-audio, 480M |__ Port 12: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 12: Dev 6, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 12: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M -- 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/1930550 Title: usb sound devices crackling Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrade from 20.04 to 21.04 all 3 my usb sound devices start crackling, i have xduoo05plus, audeze mobius, audient id4. I also tried to modify default-fragments = 5 default-fragment-size-msec = 2 to different sugested on stackoverflow articles setting Also this is in my config: high-priority = yes nice-level = -11 realtime-scheduling = yes realtime-priority = 5 I even tried to switch to pipewire, but it still the same. Possible issue in alsa kernel drivers for usb interface, submitting bug to pulse as it default in ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 2 11:11:55 2021 InstallationDate: Installed on 2019-08-13 (658 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to hirsute on 2021-05-16 (16 days ago) dmi.bios.date: 08/12/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd08/12/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2021-05-18T13:33:15.787174 mtime.conffile..etc.pulse.system.pa: 2021-05-18T11:20:40.860787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
OK perfect )
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
Confirmed
Status in openldap source package in Bionic:
Triaged
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1930669] Re: Ubuntu 20.04 suspend not working with nvidia-driver-450-server
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-450 (Ubuntu) ** Tags added: nvidia suspend-resume -- 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/1930669 Title: Ubuntu 20.04 suspend not working with nvidia-driver-450-server Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: I switched to nvidia-driver-450-server because my second monitor stopped working after switching to nvidia-driver-460. However, this switch broke suspend on my ThinkPad running Ubuntu 20.04. The laptop doesn't properly suspend anymore, and when trying to get it out of suspend it gets stuck on a black screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 450.119.04 Sat Apr 24 00:01:33 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 07:54:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-srv, 450.119.04, 5.10.0-1029-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22c0] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0] InstallationDate: Installed on 2020-12-15 (169 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=ea99ef49-df2d-48fa-9558-61bcea3e36cd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET30W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN2VET30W(1.15):bd04/15/2021:br1.15:efr1.8:svnLENOVO:pn20THCTO1WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCTO1WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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/nvidia-graphics-drivers-450/+bug/1930669/+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 1930669] [NEW] Ubuntu 20.04 suspend not working with nvidia-driver-450-server
Public bug reported: I switched to nvidia-driver-450-server because my second monitor stopped working after switching to nvidia-driver-460. However, this switch broke suspend on my ThinkPad running Ubuntu 20.04. The laptop doesn't properly suspend anymore, and when trying to get it out of suspend it gets stuck on a black screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 450.119.04 Sat Apr 24 00:01:33 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 07:54:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-srv, 450.119.04, 5.10.0-1029-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22c0] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0] InstallationDate: Installed on 2020-12-15 (169 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=ea99ef49-df2d-48fa-9558-61bcea3e36cd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET30W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN2VET30W(1.15):bd04/15/2021:br1.15:efr1.8:svnLENOVO:pn20THCTO1WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCTO1WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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 focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1930669 Title: Ubuntu 20.04 suspend not working with nvidia-driver-450-server Status in xorg package in Ubuntu: New Bug description: I switched to nvidia-driver-450-server because my second monitor stopped working after switching to nvidia-driver-460. However, this switch broke suspend on my ThinkPad running Ubuntu 20.04. The laptop doesn't properly suspend anymore, and when trying to get it out of suspend it gets stuck on a black screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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
