[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
I think it's another bug. The log from original bug report shows that the system has 32G ram, so the abort() is less likely triggered by OOM. -- 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: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: == SRU Justification == [Impact] When the system is under memory pressure, the entire desktop session may crash. [Fix] Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory") [Test] Run memory stress and the session crashed in less than 5 minutes. With the fix applied, run memory stress for 24 hours and the desktop session is still alive. [Where problems could occur] Doing a reset might make the system even more sluggish when under memory pressure. == Original bug report == 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 1497593] Re: [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed.
** Description changed: - webbrowser-app crashed with SIGABRT in __assert_fail_base() - - ProblemType: Crash - DistroRelease: Ubuntu 15.10 - Package: webbrowser-app 0.23+15.10.20150913-0ubuntu1 - ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 - Uname: Linux 4.2.0-10-generic x86_64 - ApportVersion: 2.18.1-0ubuntu1 - Architecture: amd64 - CurrentDesktop: Unity - Date: Sat Sep 19 20:05:51 2015 - ExecutablePath: /usr/bin/webbrowser-app - InstallationDate: Installed on 2015-09-18 (1 days ago) - InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150918) - ProcCmdline: webbrowser-app - Signal: 6 - SourcePackage: webbrowser-app - StacktraceTop: - __assert_fail_base (fmt=0x7f1aba6fd028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f1aa469f879 "kref", file=file@entry=0x7f1aa469f85a "../../nouveau/pushbuf.c", line=line@entry=726, function=function@entry=0x7f1aa469f8a0 "nouveau_pushbuf_data") at assert.c:92 - __GI___assert_fail (assertion=0x7f1aa469f879 "kref", file=0x7f1aa469f85a "../../nouveau/pushbuf.c", line=726, function=0x7f1aa469f8a0 "nouveau_pushbuf_data") at assert.c:101 - nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 - nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 - ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 - Title: webbrowser-app crashed with SIGABRT in __assert_fail_base() - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' + failed. Because nouveau is not thread safe(?) -- 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/1497593 Title: [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. Status in Mesa: Unknown Status in libdrm package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. Because nouveau is not thread safe(?) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1497593/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Fixed in bug 1918855? -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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
Is this the same issue as bug 1871959? -- 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: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: == SRU Justification == [Impact] When the system is under memory pressure, the entire desktop session may crash. [Fix] Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory") [Test] Run memory stress and the session crashed in less than 5 minutes. With the fix applied, run memory stress for 24 hours and the desktop session is still alive. [Where problems could occur] Doing a reset might make the system even more sluggish when under memory pressure. == Original bug report == 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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
Yeah I'm also not entirely sure. But I'm assuming that the maintainers insight into all the interactions is better than mine and therefore tend to follow. About the "why the difference DHCPv6 vs SLAAC" I think that is fine because the code now allows to behave different (reasonable). And the defaults as configured by NM or anything else could configure lifetimes for DHCPv6+SLAAC then no behavior change would happen. Thereby (with a lot of un-sureness left) I'd intend to drop this change now (somewhat early/mid in 21.10) to identify any worse fallout better now than later. I've closed my Debian bug that I spawned back in the day. I will prepare an upload of dnsmasq, then we will see which tests or behavior break on it nowadays. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq package in Debian: New Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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
** Also affects: mesa (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New -- 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: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: == SRU Justification == [Impact] When the system is under memory pressure, the entire desktop session may crash. [Fix] Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory") [Test] Run memory stress and the session crashed in less than 5 minutes. With the fix applied, run memory stress for 24 hours and the desktop session is still alive. [Where problems could occur] Doing a reset might make the system even more sluggish when under memory pressure. == Original bug report == 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 1933118] Re: Xorg freeze
If the mouse cursor still moves then Xorg is still working. This usually means it's the gnome-shell process that has frozen or crashed, so please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Summary changed: - Xorg freeze + Screen freeze -- 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/1933118 Title: Screen freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot of work. If I try the 'REISUB' method of shutting down, it usually does not work. If I remote log in and do a shutdown, it takes several minutes to actually shut down - as if waiting for some process to time out. I haven't any obvious errors for this bug, and i don't know where to look for possible error messages. It is possible that if there is a deadlock, there is no error message, unless shutting down causes the process to generate an error message. The bug happens very often, sometimes several times a week. If you could tell me what commands to run when the problem occurs in order to gather more information, I can remote login and run those commands. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.143 Fri Mar 12 07:24:47 UTC 2021 GCC version: 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: Mon Jun 21 15:14:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-53-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GLM [Quadro K1100M] [103c:2256] InstallationDate: Installed on 2021-01-11 (161 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=62a0870e-1f83-43a4-a2ff-864901a24fb6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2015 dmi.bios.release: 1.12 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.12 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:br1.12:efr3.16:svnHewlett-Packard:pnHPZBook17G2:pvrA3009DD10203:rvnHewlett-Packard:rn2255:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z41AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2
[Touch-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+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 1923845] Re: Please compress packages with zstd by default
This bug was fixed in the package reprepro - 5.3.0-1.3 --- reprepro (5.3.0-1.3) experimental; urgency=medium * Non-maintainer upload. * Add support for Zstd compressed debs. (LP: #1923845) -- Dimitri John Ledkov Mon, 21 Jun 2021 10:16:53 +0100 ** Changed in: reprepro (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default Status in appstream-glib package in Ubuntu: New Status in apt package in Ubuntu: Fix Released Status in aptly package in Ubuntu: New Status in boinc package in Ubuntu: New Status in busybox package in Ubuntu: New Status in cdebootstrap package in Ubuntu: New Status in cdist package in Ubuntu: New Status in debdelta package in Ubuntu: New Status in debian-el package in Ubuntu: New Status in debootstrap package in Ubuntu: Fix Released Status in debsig-verify package in Ubuntu: New Status in debsigs package in Ubuntu: New Status in diffoscope package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in dpkg-sig package in Ubuntu: New Status in file package in Ubuntu: New Status in hello package in Ubuntu: Fix Released Status in libsolv package in Ubuntu: New Status in lintian package in Ubuntu: Fix Released Status in lutris package in Ubuntu: New Status in obs-build package in Ubuntu: New Status in osc package in Ubuntu: New Status in radare2 package in Ubuntu: New Status in reprepro package in Ubuntu: Fix Released Status in vim-scripts package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: New Bug description: https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built on Hirsute having both data and control members of the .deb being compressed with zstd. It can be handy for testing various tools. [dpkg] Decompression support in dpkg landed first in Bionic and is being SRUd to Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the zstd-compressed binary packages. From dpkg's perspective the upgrade path is cleared. The original plan was compressing only the internal data.tar .deb member, but dpkg uses uniform compression by default since dpkg 1.19.0 thus I'm collecting all the changes to support control.tar.zst, too, in this bug. Reviewed packages from: https://codesearch.debian.net/search?q=data.tar.xz=1=1 https://codesearch.debian.net/search?q=control.tar.xz=1=1 appstream-glib - needs fix: libappstream-builder/asb-package-deb.c aptly - needs fix: deb/deb.go boinc - needs fix: debian/fetch_example_applications.sh busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c cdebootstrap- needs fix: src/package.c cdist - may need fix, can use dpkg-deb: cdist/preos/debootstrap/files/devuan-debootstrap/functions debdelta- needs fix: debdelta debpatch.sh debian-el - needs fix: deb-view.el debian-handbook - needs fix, maybe later, for Debian debootstrap - needs fix, https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54 debsigs - needs fix, debsigs debsig-verify - needs fix, src/debsig-verify.c diffoscope - needs fix, diffoscope/comparators/deb.py dpkg- needs fix, change default dpkg-sig- needs fix, dpkg-sig dpmb- needs fix, maybe later, for Debian elfutils- may need fix, uses dpkg-deb if it is available, does not handle .gz either file- needs fix, magic/Magdir/archive libsolv - needs fix, ext/repo_deb.c lintian - needs fix malformed-deb-archive lutris - needs fix, lutris/util/extract.py obs-build - needs fix Build/Deb.pm osc - needs fix osc/util/debquery.py control.tar.zst only python-apt - needs fix apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() radare2 - needs fix reprepro- needs fix, debfile.c vim-scripts - needs fix debPlugin/autoload/deb.vim winetricks - needs fix when Debian switches src/winetricks zeroinstall-injector - needs fix src/zeroinstall/archive.ml acr - skip, does not _have to_ be fixed, just creates packages, see dist/deb_hand.mak alien - skip, uses dpkg-deb to extract .deb ansible - not affected, just test data in dbdata.tar.xz anthy - not affected, just changelog entry apt - seems fixed already ceph- not affected in Ubuntu's version circlator - not affected, just test data cowdancer - not affected, just documentation eccodes - skip, just orig-data.tar.xz eckit - skip, just ...orig-data.tar.xz firefox - skip, profdata.tar.xz firefox-esr - skip,
[Touch-packages] [Bug 1776381] Re: lxc-test-api-reboot will hang with autopkgtest
Seeing on bionic/fips 4.15.0-1061.69 s390x host s2lp3 ** Tags added: 4.15 fips s390x sru-20210531 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1776381 Title: lxc-test-api-reboot will hang with autopkgtest Status in ubuntu-kernel-tests: Confirmed Status in lxc package in Ubuntu: Invalid Bug description: Steps: 1. Deploy Bionic on a bare-metal system. 2. Enable deb-src, install the autopkgtest package 3. sudo autopkgtest lxc -- null Result: * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: Connected to tty 1 Type to exit the console, to enter Ctrl+a itself * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1776381/+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
Found on B-5.4/aws, cycle sru-20210531 . ** Tags added: sru-20210531 -- 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 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
Observed with B-5.4/aws, cycle sru-20210531 . ** Tags added: sru-20210531 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1884024 Title: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4 Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Committed Bug description: Issue found on with 5.4.0-1016.16~18.04.1-oracle on both VM.Standard2.1 and VM.Standard2.16 Test failed with: FAIL: lxc-tests: lxc-test-device-add-remove (1s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on VM.Standard2.16 but passed on VM.Standard2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Hello lincvz, Sorry about the delay. I have been busy with other stuff and did not have time to follow up on this bug. Here is the lay of the land right now: 1) Unfortunately, it is unlikely that we will be able to get the SRU team to accept an upload that reintroduces an issue. This means that removing the patch that causes the infinite loop is something that we would rather not do, because another problem will reappear. 2) The ideal course of action here would be to investigate whether it would be possible to backport the patch at https://github.com/openldap/openldap/commit/735e1ab14bb055344b4e767a216aa410aa7d1503 and make it fully work. This is probably a non-trivial task, as Ryan himself said. I am still looking into a possible solution for this, but I cannot guarantee anything for now, I'm sorry (I'm very busy with other stuff, including updating OpenLDAP in Impish to 2.5!) Given that I have provided a PPA with a package that fixes the issue for you, I would say that for now you are better off using it. Last, but not least: if you feel like giving it a try and trying to backport https://github.com/openldap/openldap/commit/735e1ab14bb055344b4e767a216aa410aa7d1503 to the openldap version that's in Bionic, that would be awesome. We can review whatever you have and guide you through the SRU process. Thank you. -- 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 1931301] Re: NIC unavailable after suspend to RAM
i did a fresh install of 21.04, not an upgrade. the same problem. Doesn't seem to be upgrade related. -- 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/1931301 Title: NIC unavailable after suspend to RAM Status in network-manager package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1931301/+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 1931301] Re: NIC unavailable after suspend to RAM
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/1931301 Title: NIC unavailable after suspend to RAM Status in network-manager package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1931301/+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 1933002] Re: VMs lost network access after hypervisor upgraded to systemd 245.4-4ubuntu3.7
# Prevent virtual networks and Wi-Fi NIC from acquiring link local IPv6 addresses (fe80::) vnet: match: name: vnet* link-local: [ ] wlx00c0caa5e44f: link-local: [ ] that will break your networking, likely causing your problem ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1933002 Title: VMs lost network access after hypervisor upgraded to systemd 245.4-4ubuntu3.7 Status in systemd package in Ubuntu: Invalid Bug description: Hi, I have a home server running Ubuntu 20.04. It is using KVM to run several VMs (router, Wi-Fi access point, NAS, ...). Everything has been running fine for years now, very happy, very grateful for all the work but... On June 17th, on the hypervisor systemd upgraded from 245.4-4ubuntu3.6 to 245.4-4ubuntu3.7 and all the VMs lost network connectivity. Packages that were upgraded on June 17th: libnss-mymachines libnss-systemd libpam-systemd libsystemd0 libudev1 systemd systemd-container systemd-sysv systemd-timesyncd udev Package installation log: Log started: 2021-06-17 06:34:27 Preparing to unpack .../0-libnss-systemd_245.4-4ubuntu3.7_amd64.deb ... Unpacking libnss-systemd:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ... Preparing to unpack .../1-systemd-timesyncd_245.4-4ubuntu3.7_amd64.deb ... Unpacking systemd-timesyncd (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ... Preparing to unpack .../2-systemd-sysv_245.4-4ubuntu3.7_amd64.deb ... Unpacking systemd-sysv (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ... Preparing to unpack .../3-libnss-mymachines_245.4-4ubuntu3.7_amd64.deb ... Unpacking libnss-mymachines:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ... Preparing to unpack .../4-systemd-container_245.4-4ubuntu3.7_amd64.deb ... Unpacking systemd-container (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ... Preparing to unpack .../5-libpam-systemd_245.4-4ubuntu3.7_amd64.deb ... Unpacking libpam-systemd:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ... Preparing to unpack .../6-systemd_245.4-4ubuntu3.7_amd64.deb ... Unpacking systemd (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ... Preparing to unpack .../7-libsystemd0_245.4-4ubuntu3.7_amd64.deb ... Unpacking libsystemd0:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ... Setting up libsystemd0:amd64 (245.4-4ubuntu3.7) ... Setting up systemd (245.4-4ubuntu3.7) ... Setting up systemd-timesyncd (245.4-4ubuntu3.7) ... Setting up systemd-container (245.4-4ubuntu3.7) ... Setting up systemd-sysv (245.4-4ubuntu3.7) ... Setting up libnss-systemd:amd64 (245.4-4ubuntu3.7) ... Setting up libnss-mymachines:amd64 (245.4-4ubuntu3.7) ... Setting up libpam-systemd:amd64 (245.4-4ubuntu3.7) ... Processing triggers for libc-bin (2.31-0ubuntu9.3) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for dbus (1.12.16-2ubuntu2.1) ... Log ended: 2021-06-17 06:34:34 Log started: 2021-06-17 06:34:35 Preparing to unpack .../udev_245.4-4ubuntu3.7_amd64.deb ... Unpacking udev (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ... Preparing to unpack .../libudev1_245.4-4ubuntu3.7_amd64.deb ... Unpacking libudev1:amd64 (245.4-4ubuntu3.7) over (245.4-4ubuntu3.6) ... Setting up libudev1:amd64 (245.4-4ubuntu3.7) ... Setting up udev (245.4-4ubuntu3.7) ... update-initramfs: deferring update (trigger activated) Processing triggers for systemd (245.4-4ubuntu3.7) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for libc-bin (2.31-0ubuntu9.3) ... Processing triggers for initramfs-tools (0.136ubuntu6.5) ... update-initramfs: Generating /boot/initrd.img-5.4.0-74-generic Log ended: 2021-06-17 06:35:03 I then tried to revert these packages. apt-cache show libsystemd0 I find 2 versions, 245.4-4ubuntu3 & 245.4-4ubuntu3.7 Not sure why it is not 245.4-4ubuntu3.6 & 245.4-4ubuntu3.7 but anyway... I reverted these packages to 245.4-4ubuntu3 sudo aptitude install libnss-systemd=245.4-4ubuntu3 systemd-timesyncd=245.4-4ubuntu3 systemd-sysv=245.4-4ubuntu3 libnss-mymachines=245.4-4ubuntu3 systemd-container=245.4-4ubuntu3 libpam-systemd=245.4-4ubuntu3 systemd=245.4-4ubuntu3 libsystemd0=245.4-4ubuntu3 sudo reboot All the VMs have access to the network again. My setup: I have 2 NICs on the server: - eno1 is my WAN plugged to my ISP's router and attached to the br-wan bridge - enp2s0 is my LAN and is attached to the br-lan bridge I use static addressing The LAN is IPv4 and IPv6 The WAN is IPv4 only wlx00c0caa5e44f is a USB Wi-Fi adapter attached to br-lan using hostapd VMs use the classic vnet attachement vi /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more
[Touch-packages] [Bug 1923232] Re: SRU of LXC 4.0.6 to focal (upstream bugfix release)
This bug was fixed in the package lxc - 1:4.0.6-0ubuntu1~20.04.1 --- lxc (1:4.0.6-0ubuntu1~20.04.1) focal; urgency=medium * Backport hirsute fixes to focal. (LP: #1923232) -- Serge Hallyn Fri, 09 Apr 2021 11:19:38 -0500 ** Changed in: lxc (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1923232 Title: SRU of LXC 4.0.6 to focal (upstream bugfix release) Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Focal: Fix Released Bug description: LXC released 4.0.6 as a bugfix release with the following changelog: - Improve handling for compatibility architectures for seccomp - Harden seccomp notifier implementation - Rework parsing of /proc//mountinfo to handle kernel regression - Improve network device restoration - Significantly cleanup and harden config file parsing - Support new capabilities CAP_PERFORM, CAP_BPF, and CAP_CHECKPOINT_RESTORE - Harden containers started without CAP_NET_ADMIN * New upstream bugfix release (4.0.5): - Support allocating PTS devices from within the container - Harden more path/mount handling logics - Rework LSM logic to limit initializer use * Cherry-pick upstream fixes: - 0002-commands-fix-check-for-seccomp-notify-support.patch - 0003-configure-skip-libseccomp-tests-if-it-is-disabled.patch - 0004-conf-fix-containers-retaining-CAP_NET_ADMIN.patch - 0005-cgroups-fix-cgroup-mounting.patch - 0006-lsm-remove-obsolute-comment-about-constructor.patch - 0007-lxc_attach-include-rexec-conditionally.patch - 0008-tree-wide-fix-some-header-inclusions.patch - 0009-initutils-fix-missing-includes.patch - 0010-configure-support-static-binaries.patch - 0011-autotools-enable-static-builds-for-tools.patch - 0012-autotools-enable-static-builds-for-commands.patch - 0013-tree-wide-fix-compilation-with-Wstrict-prototypes-Wo.patch - 0014-config-update-ax_pthread.m4.patch - 0015-configure-add-AC_SYS_LARGEFILE-checking.patch - 0016-autotools-update-build.patch - 0017-file_utils-introduce-read_file_at.patch - 0018-string_utils-add-must_make_path_relative.patch - 0019-cgroups-coding-style-fixes.patch - 0020-cgroups-rework-cg_unified_init.patch - 0021-cgroups-detect-and-record-cgroup2-freezer-support.patch - 0022-criu-handle-cgroup2-freezer.patch - 0023-mkdir-p-proc-sys-on-container-startup.patch - 0024-conf-fix-coding-style.patch - 0025-conf-coding-style-fixes.patch - 0026-conf-move-proc-and-sys-mountpoint-creation-int-lxc_m.patch - 0027-attach-invert-child-parent-handling.patch - 0028-attach-use-__do_free-cleanup-macro-for-cwd.patch - 0029-attach-tweak-logging.patch - 0030-attach-use-__do_close-for-labelfd.patch - 0031-attach-coding-style-fixes.patch - 0032-attach-use-free_disarm.patch - 0033-attach-s-attach_child_main-do_attach-g.patch - 0034-attach-mark-do_attach-as-__noreturn.patch - 0035-attach-make-do_attach-void.patch - 0036-attach-use-close_prot_errno_disarm.patch - 0037-attach-add-some-DEBUG-logging-to-stdfd-dpulication.patch - 0038-cgroups-fix-cgroup-mounting.patch - 0039-utils-fix-mount_at.patch - 0040-configure-fix-static-builds-with-clang-12-and-LTO.patch - 0041-cgroups-bpf-fixes.patch - 0042-croups-improve-__do_bpf_program_free.patch - 0043-cgroups-coding-style-fixes.patch - 0044-cgroups-don-t-initiliaze-NULL-log.patch - 0045-cgroups-ensure-all-memory-is-zeroed.patch - 0046-cgroups-use-zalloc.patch - 0047-cgroups-tweak-cgroup-initialization.patch - 0048-log-remove-pointless-inline.patch - 0049-log-add-lxc_log_get_fd.patch - 0050-seccomp-use-lxc_log_get_fd.patch - 0051-log-rework-lxc_log_get_level.patch - 0052-seccomp-use-lxc_log_get_level.patch - 0053-cgroups-use-bpf-log-when-logging-at-trace-level.patch - 0054-log-add-lxc_log_trace-helper.patch - 0055-cgroups-use-PTR_TO_U64.patch - 0056-cgroups-align-methods.patch - 0057-utils-use-SYSTRACE-when-logging-stdio-permission-fix.patch - 0058-attach-log-failues-to-dup2-with-SYSDEBUG.patch - 0059-attach-fix-logging-for-stdfd-replacement.patch - 0060-attach-fix-error-checking-for-dup2.patch - 0061-cgroups-initialize-variable.patch - 0062-commands_utils-don-t-leak-memory.patch - 0063-conf-use-lxc_log_trace.patch - 0064-confile_utils-use-lxc_log_trace.patch - 0065-rexec-check-lseek-return-value.patch * Cherry-pick upstream bugfix: - cgroups: fix armhf builds * Cherry-pick upstream bugfix: - cgfsng: fix cgroup attach cgroup creation * New upstream
[Touch-packages] [Bug 1923232] Update Released
The verification of the Stable Release Update for lxc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1923232 Title: SRU of LXC 4.0.6 to focal (upstream bugfix release) Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Focal: Fix Released Bug description: LXC released 4.0.6 as a bugfix release with the following changelog: - Improve handling for compatibility architectures for seccomp - Harden seccomp notifier implementation - Rework parsing of /proc//mountinfo to handle kernel regression - Improve network device restoration - Significantly cleanup and harden config file parsing - Support new capabilities CAP_PERFORM, CAP_BPF, and CAP_CHECKPOINT_RESTORE - Harden containers started without CAP_NET_ADMIN * New upstream bugfix release (4.0.5): - Support allocating PTS devices from within the container - Harden more path/mount handling logics - Rework LSM logic to limit initializer use * Cherry-pick upstream fixes: - 0002-commands-fix-check-for-seccomp-notify-support.patch - 0003-configure-skip-libseccomp-tests-if-it-is-disabled.patch - 0004-conf-fix-containers-retaining-CAP_NET_ADMIN.patch - 0005-cgroups-fix-cgroup-mounting.patch - 0006-lsm-remove-obsolute-comment-about-constructor.patch - 0007-lxc_attach-include-rexec-conditionally.patch - 0008-tree-wide-fix-some-header-inclusions.patch - 0009-initutils-fix-missing-includes.patch - 0010-configure-support-static-binaries.patch - 0011-autotools-enable-static-builds-for-tools.patch - 0012-autotools-enable-static-builds-for-commands.patch - 0013-tree-wide-fix-compilation-with-Wstrict-prototypes-Wo.patch - 0014-config-update-ax_pthread.m4.patch - 0015-configure-add-AC_SYS_LARGEFILE-checking.patch - 0016-autotools-update-build.patch - 0017-file_utils-introduce-read_file_at.patch - 0018-string_utils-add-must_make_path_relative.patch - 0019-cgroups-coding-style-fixes.patch - 0020-cgroups-rework-cg_unified_init.patch - 0021-cgroups-detect-and-record-cgroup2-freezer-support.patch - 0022-criu-handle-cgroup2-freezer.patch - 0023-mkdir-p-proc-sys-on-container-startup.patch - 0024-conf-fix-coding-style.patch - 0025-conf-coding-style-fixes.patch - 0026-conf-move-proc-and-sys-mountpoint-creation-int-lxc_m.patch - 0027-attach-invert-child-parent-handling.patch - 0028-attach-use-__do_free-cleanup-macro-for-cwd.patch - 0029-attach-tweak-logging.patch - 0030-attach-use-__do_close-for-labelfd.patch - 0031-attach-coding-style-fixes.patch - 0032-attach-use-free_disarm.patch - 0033-attach-s-attach_child_main-do_attach-g.patch - 0034-attach-mark-do_attach-as-__noreturn.patch - 0035-attach-make-do_attach-void.patch - 0036-attach-use-close_prot_errno_disarm.patch - 0037-attach-add-some-DEBUG-logging-to-stdfd-dpulication.patch - 0038-cgroups-fix-cgroup-mounting.patch - 0039-utils-fix-mount_at.patch - 0040-configure-fix-static-builds-with-clang-12-and-LTO.patch - 0041-cgroups-bpf-fixes.patch - 0042-croups-improve-__do_bpf_program_free.patch - 0043-cgroups-coding-style-fixes.patch - 0044-cgroups-don-t-initiliaze-NULL-log.patch - 0045-cgroups-ensure-all-memory-is-zeroed.patch - 0046-cgroups-use-zalloc.patch - 0047-cgroups-tweak-cgroup-initialization.patch - 0048-log-remove-pointless-inline.patch - 0049-log-add-lxc_log_get_fd.patch - 0050-seccomp-use-lxc_log_get_fd.patch - 0051-log-rework-lxc_log_get_level.patch - 0052-seccomp-use-lxc_log_get_level.patch - 0053-cgroups-use-bpf-log-when-logging-at-trace-level.patch - 0054-log-add-lxc_log_trace-helper.patch - 0055-cgroups-use-PTR_TO_U64.patch - 0056-cgroups-align-methods.patch - 0057-utils-use-SYSTRACE-when-logging-stdio-permission-fix.patch - 0058-attach-log-failues-to-dup2-with-SYSDEBUG.patch - 0059-attach-fix-logging-for-stdfd-replacement.patch - 0060-attach-fix-error-checking-for-dup2.patch - 0061-cgroups-initialize-variable.patch - 0062-commands_utils-don-t-leak-memory.patch - 0063-conf-use-lxc_log_trace.patch - 0064-confile_utils-use-lxc_log_trace.patch - 0065-rexec-check-lseek-return-value.patch * Cherry-pick upstream bugfix:
[Touch-packages] [Bug 1923232] Re: SRU of LXC 4.0.6 to focal (upstream bugfix release)
Since this version of lxc was SRU'ed only to Ubuntu 20.04 LTS and not Ubuntu 20.10 we have a situation where the version in 20.04 is greater than 20.10. However, I tried an upgrade from 20.04 to 20.10 and the upgrade was calculable and the 20.04 version of lxc was kept installed. Given that Ubuntu 20.10 will be reaching its end of life in about 30 days (and then the upgrade from 20.04 will be to 21.04) and most people who upgrade to interim releases have already done so I think it's okay to release this. ** 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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/1923232 Title: SRU of LXC 4.0.6 to focal (upstream bugfix release) Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Focal: Fix Released Bug description: LXC released 4.0.6 as a bugfix release with the following changelog: - Improve handling for compatibility architectures for seccomp - Harden seccomp notifier implementation - Rework parsing of /proc//mountinfo to handle kernel regression - Improve network device restoration - Significantly cleanup and harden config file parsing - Support new capabilities CAP_PERFORM, CAP_BPF, and CAP_CHECKPOINT_RESTORE - Harden containers started without CAP_NET_ADMIN * New upstream bugfix release (4.0.5): - Support allocating PTS devices from within the container - Harden more path/mount handling logics - Rework LSM logic to limit initializer use * Cherry-pick upstream fixes: - 0002-commands-fix-check-for-seccomp-notify-support.patch - 0003-configure-skip-libseccomp-tests-if-it-is-disabled.patch - 0004-conf-fix-containers-retaining-CAP_NET_ADMIN.patch - 0005-cgroups-fix-cgroup-mounting.patch - 0006-lsm-remove-obsolute-comment-about-constructor.patch - 0007-lxc_attach-include-rexec-conditionally.patch - 0008-tree-wide-fix-some-header-inclusions.patch - 0009-initutils-fix-missing-includes.patch - 0010-configure-support-static-binaries.patch - 0011-autotools-enable-static-builds-for-tools.patch - 0012-autotools-enable-static-builds-for-commands.patch - 0013-tree-wide-fix-compilation-with-Wstrict-prototypes-Wo.patch - 0014-config-update-ax_pthread.m4.patch - 0015-configure-add-AC_SYS_LARGEFILE-checking.patch - 0016-autotools-update-build.patch - 0017-file_utils-introduce-read_file_at.patch - 0018-string_utils-add-must_make_path_relative.patch - 0019-cgroups-coding-style-fixes.patch - 0020-cgroups-rework-cg_unified_init.patch - 0021-cgroups-detect-and-record-cgroup2-freezer-support.patch - 0022-criu-handle-cgroup2-freezer.patch - 0023-mkdir-p-proc-sys-on-container-startup.patch - 0024-conf-fix-coding-style.patch - 0025-conf-coding-style-fixes.patch - 0026-conf-move-proc-and-sys-mountpoint-creation-int-lxc_m.patch - 0027-attach-invert-child-parent-handling.patch - 0028-attach-use-__do_free-cleanup-macro-for-cwd.patch - 0029-attach-tweak-logging.patch - 0030-attach-use-__do_close-for-labelfd.patch - 0031-attach-coding-style-fixes.patch - 0032-attach-use-free_disarm.patch - 0033-attach-s-attach_child_main-do_attach-g.patch - 0034-attach-mark-do_attach-as-__noreturn.patch - 0035-attach-make-do_attach-void.patch - 0036-attach-use-close_prot_errno_disarm.patch - 0037-attach-add-some-DEBUG-logging-to-stdfd-dpulication.patch - 0038-cgroups-fix-cgroup-mounting.patch - 0039-utils-fix-mount_at.patch - 0040-configure-fix-static-builds-with-clang-12-and-LTO.patch - 0041-cgroups-bpf-fixes.patch - 0042-croups-improve-__do_bpf_program_free.patch - 0043-cgroups-coding-style-fixes.patch - 0044-cgroups-don-t-initiliaze-NULL-log.patch - 0045-cgroups-ensure-all-memory-is-zeroed.patch - 0046-cgroups-use-zalloc.patch - 0047-cgroups-tweak-cgroup-initialization.patch - 0048-log-remove-pointless-inline.patch - 0049-log-add-lxc_log_get_fd.patch - 0050-seccomp-use-lxc_log_get_fd.patch - 0051-log-rework-lxc_log_get_level.patch - 0052-seccomp-use-lxc_log_get_level.patch - 0053-cgroups-use-bpf-log-when-logging-at-trace-level.patch - 0054-log-add-lxc_log_trace-helper.patch - 0055-cgroups-use-PTR_TO_U64.patch - 0056-cgroups-align-methods.patch - 0057-utils-use-SYSTRACE-when-logging-stdio-permission-fix.patch - 0058-attach-log-failues-to-dup2-with-SYSDEBUG.patch - 0059-attach-fix-logging-for-stdfd-replacement.patch - 0060-attach-fix-error-checking-for-dup2.patch - 0061-cgroups-initialize-variable.patch - 0062-commands_utils-don-t-leak-memory.patch -
[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
This bug was fixed in the package mesa - 21.1.2-1 --- mesa (21.1.2-1) experimental; urgency=medium * New upstream release. * iris-avoid-abort-if-enomem.diff: Don't abort when out of memory. (LP: #1918855) -- Timo Aaltonen Fri, 18 Jun 2021 14:33:09 +0300 ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- 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: Fix Released Bug description: == SRU Justification == [Impact] When the system is under memory pressure, the entire desktop session may crash. [Fix] Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory") [Test] Run memory stress and the session crashed in less than 5 minutes. With the fix applied, run memory stress for 24 hours and the desktop session is still alive. [Where problems could occur] Doing a reset might make the system even more sluggish when under memory pressure. == Original bug report == 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 1928100] Re: TLS handshake is fatal, not transient - hence not retried
autopkgtest have passed, so verified ** 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1928100 Title: TLS handshake is fatal, not transient - hence not retried Status in apt package in Ubuntu: Fix Released Status in apt source package in Hirsute: Fix Committed Bug description: [Impact] TLS handshakes are reported as fatal errors rather than transient errors like other connection errors on unencrypted connections. This seems wrong - a server may just be spinning up or down and fail during the handshake, and prevents retrying such downloads [Test plan] A test case has been added to the integration test suite that ensures handshake errors are retried upon configuration. [Where problems could occur] Transient errors do not cause an error exit from apt update, so scripts relying on errors from TLS handshakes in such situations will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1928100/+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 1932066] Re: PulseAudio Preferences searches for libraries in incorrect location
*** This bug is a duplicate of bug 1907882 *** https://bugs.launchpad.net/bugs/1907882 ** This bug has been marked a duplicate of bug 1907882 paprefs does not find modules -- 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/1932066 Title: PulseAudio Preferences searches for libraries in incorrect location Status in pulseaudio package in Ubuntu: New Bug description: PulseAudio Preferences (paprefs) appears to be searching for modules in the wrong location. Specifically, the "install" button appears when modules relevant modules cannot be found by paprefs. paprefs is searching for modules in the location: /usr/lib/pulse-13.99/modules/ the modules are actually located in: /usr/lib/pulse-13.99.1/modules/ The specifics of this were determined via `strace paprefs`, which (among a lot of other things), produces: access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) = -1 ENOENT (No such file or directory) creating a symlink from /usr/lib/pulse-13.99.1 to /usr/lib/pulse-13.99 resolves the issue. paprefs should perhaps be updated to match the version of the pulseaudio package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1932066/+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 1921626] Re: size mismatch error if request of unknown size is larger than others
autopkgtests for apt itself have passed, verifying the fix. We still battle with one apport regression on focal, but it seems unrelated - they've failed before. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal ** Tags added: verification-done verification-done-bionic verification-done-focal -- 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/1921626 Title: size mismatch error if request of unknown size is larger than others Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: New Status in apt source package in Hirsute: Fix Released Bug description: [Impact] Downloads fail if: - there is at least one package each with Size and no size on a mirror - a package without a Size field is larger than a package with a Size field that's currently in the pipeline Also, this was silent, we need to add an error so people fix repos. For hirsute and earlier, this is a warning; for hirsute+1 it's an error so people's CI fails on them and doesn't "succeed with warnings" [Test plan] We have included a test case in the apt integration tests, which downloads three packages a, b, c where b is largest and has no Size field. With 2.2.2, it fails; with 2.2.3 it succceeds. We have also added a test case that a warning is shown. [Where problems could occur] Problems can only occur if you try to download packages without a Size field, as that is the only place code changes (adding code guarded with if ... Size ... == 0; 0 being unknown size). [Other changes] 2.2.3 includes the same change as 2.2.2ubuntu1 [Original bug report] 1) Ubuntu 18.04.5 LTS 2) apt 1.6.12ubuntu0.2 3) What you expected to happen I set a custom set of repositories in /etc/apt/sources.list and then I run "apt install ". I expect the command to download and install the packages. 4) What happened instead "apt install ..." fails during the download phase with "File has unexpected size " 5) What I've established trying to debug the issue: - Disabling http pipelining resolves the issue: "apt -oAcquire::http::Pipeline-Depth=0 install ..." - All the packages, and repo metadata in the referenced repositories is correct - The issue is easily reproducible in my setup with different repositories - tcpdump shows that requests and responses are in the correct order, and contain the correct data More details about the issue: https://projects.theforeman.org/issues/32178 With all the above in mind, it appears that this must be a bug in apt's http pipeline handling. It seem that apt is trying to match a request to do wrong response, and size doesn't match. I've attached an example log, where the error pops up for multiple packages, and they all appear to be compared to one size (86464 bytes). That size is correct for one of the package being downloaded, but somehow apt is trying to match to multiple other packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1921626/+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 1926150] Re: [SRU] Backport JSON hooks 0.2
autopkgtests for apt itself have passed, verifying the fix. We still battle with one apport regression on focal, but it seems unrelated - they've failed before. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-hirsute -- 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/1926150 Title: [SRU] Backport JSON hooks 0.2 Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Hirsute: Fix Committed Status in apt source package in Impish: Fix Released Bug description: [Impact] We want to be able to use JSON hooks 0.2 in xenial and later releases to display messages to users during dist-upgrade. For xenial, we backport the JSON hook support in its entirety, whereas for later releases, we only need to cherry-pick bugfixes and the v0.2 improvements. [Test plan] We have included unit and integration tests for the new JSON code to test the writer and prevent regressions in future changes. Regressions in other parts of the code should be caught by the test suite. [Where problems could occur] There may be bugs in the JSON code (apt-private/private-json-hooks.*) and in the integration thereof. The JSON hook code is identical to 2.3.2, whereas the integration code needed slight adjustments. The integration changes are limited to adding the hooks, and (for xenial, already in later releases) collecting all unknown package names. We believe the regression potential of these changes to be fairly limited. However, errors in JSON hooks are fatal, so once JSON hooks are running, they can cause apt to fail, which has to be kept in mind. Existing JSON hooks might not expect the new notifications, and break, but we are only aware of the snapd hook and it ignores any unknown notifications, so that should not pose a problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926150/+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 1928687] Re: Avoid infinite loop on EOF on media change prompt
I've not been able to reproduce this recently, there seems to be a race in the cdrom testing code somewhere and I've not been lucky to trigger it; but we saw no regressions in the test suite, and the fix is one of the obvious correct ones, so marking as verified. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-dobe-hirsute verification-done verification-done-bionic verification-done-focal ** Tags removed: verification-dobe-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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1928687 Title: Avoid infinite loop on EOF on media change prompt Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Committed Status in apt source package in Hirsute: Fix Committed Status in apt source package in Impish: Fix Released Bug description: [Impact] The cdrom media change prompt hangs on EOF. This causes the autopkgtest to hang when run in a debian lxd container for unknown reasons related to lxd/systemd isolation likely (it works fine in Ubuntu), but it's also surprising behavior in general. [Test plan] We did not really come up with a test for this except running autopkgtest -- lxd autopkgtest/debian/$suite/$arch. That being said, the change is minimal, and we do test the positive case in the test suite. [Where problems could occur] This change is isolated to the handling of pressing 'c' or hitting EOF inside the media change prompt, so any regressions would occur solely within that space. We do not foresee any regressions from the change as intended, as it seems unlikely that "hanging" is what you actually want. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1928687/+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 1932022] Re: Can you add the btvirt executable to bluez-tests?
similar to bug #1907886 if upstream decided to include it in the noinst set they might have a reason? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932022 Title: Can you add the btvirt executable to bluez-tests? Status in bluez package in Ubuntu: In Progress Bug description: See the Debian package: https://packages.debian.org/buster/i386/bluez- test-tools/filelist The Ubuntu package contains the same tools, except for btvirt. Would it be possible to add this? The buildlog shows that the btvirt executable is already built, but just not put into the *.deb package. Additions to be done to debian/bluez-tests.install: emulator/b1ee usr/bin emulator/btvirt usr/bin emulator/hfp usr/bin Having the btvirt tool available will make testing on CI systems a lot easier. References: https://github.com/hadess/bluez/blob/master/Makefile.tools#L76-L82 https://answers.launchpad.net/ubuntu/+source/bluez/+question/697542 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932022/+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 1933118] [NEW] Xorg freeze
Public bug reported: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot of work. If I try the 'REISUB' method of shutting down, it usually does not work. If I remote log in and do a shutdown, it takes several minutes to actually shut down - as if waiting for some process to time out. I haven't any obvious errors for this bug, and i don't know where to look for possible error messages. It is possible that if there is a deadlock, there is no error message, unless shutting down causes the process to generate an error message. The bug happens very often, sometimes several times a week. If you could tell me what commands to run when the problem occurs in order to gather more information, I can remote login and run those commands. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.143 Fri Mar 12 07:24:47 UTC 2021 GCC version: 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: Mon Jun 21 15:14:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-53-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GLM [Quadro K1100M] [103c:2256] InstallationDate: Installed on 2021-01-11 (161 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=62a0870e-1f83-43a4-a2ff-864901a24fb6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2015 dmi.bios.release: 1.12 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.12 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:br1.12:efr3.16:svnHewlett-Packard:pnHPZBook17G2:pvrA3009DD10203:rvnHewlett-Packard:rn2255:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z41AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard 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 20.2.6-0ubuntu0.20.04.1 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 N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze possible-manual-nvidia-install third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933118 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is
[Touch-packages] [Bug 1932542] Re: Add support for zstd
http://launchpadlibrarian.net/543778464/initramfs- tools_0.140ubuntu5_0.140ubuntu6.diff.gz for the depends change in impish. -- 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/1932542 Title: Add support for zstd Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Committed Bug description: [Impact] * initramfs-tools in impish has changed default initrd compression to zstd. To allow compressing and uncompressing such initrds on Focal LTS release we should backport zstd support in the mkinitramfs & unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinitramfs tool to unpack and inspect impish initrds on a focal host. * Cherrypicking the feature from 0.138 release, which is also present in Hirsute and Impish. [Test Plan] * Create initrd with zstd $ mkinitramfs -c zstd -o zstd-initrd.img * Uncompress it with $ unmkinitramfs ./zstd-initrd.img zstd-initrd- unpacked [Where problems could occur] * This adds support for zstd compressed initrd in both mkinitramfs and unmkinitramfs. However our GA kernels do not support zstd compressed initrds. And depends on zstd package is not added either. Meaning one still has to install zstd to gain the unpack support. Changing initramfs.conf to zstd may result in unbootable instance when used with GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932542/+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 1932542] Re: Add support for zstd
@sil2100 zstd depends was added in the devel series. Historically, we only had the depends on the tool that is needed at a time for a given series... ie. gzip, xz, lz4, zstd. Given that zstd compressed initrds are not supported by the linux GA kernel in Focal, I am hesitant to impose zstd dependency on everyone in focal. Only .3 hwe will have support for zstd compressed initrds. Note we don't add depends on other compression methods that are supported either, ie. bzip2. -- 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/1932542 Title: Add support for zstd Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Committed Bug description: [Impact] * initramfs-tools in impish has changed default initrd compression to zstd. To allow compressing and uncompressing such initrds on Focal LTS release we should backport zstd support in the mkinitramfs & unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinitramfs tool to unpack and inspect impish initrds on a focal host. * Cherrypicking the feature from 0.138 release, which is also present in Hirsute and Impish. [Test Plan] * Create initrd with zstd $ mkinitramfs -c zstd -o zstd-initrd.img * Uncompress it with $ unmkinitramfs ./zstd-initrd.img zstd-initrd- unpacked [Where problems could occur] * This adds support for zstd compressed initrd in both mkinitramfs and unmkinitramfs. However our GA kernels do not support zstd compressed initrds. And depends on zstd package is not added either. Meaning one still has to install zstd to gain the unpack support. Changing initramfs.conf to zstd may result in unbootable instance when used with GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932542/+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 1932542] Re: Add support for zstd
When reviewing this package I was actually thinking if maybe we should add a depends on zstd to initramfs-tools, even though this wasn't the case for the devel series. -- 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/1932542 Title: Add support for zstd Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Committed Bug description: [Impact] * initramfs-tools in impish has changed default initrd compression to zstd. To allow compressing and uncompressing such initrds on Focal LTS release we should backport zstd support in the mkinitramfs & unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinitramfs tool to unpack and inspect impish initrds on a focal host. * Cherrypicking the feature from 0.138 release, which is also present in Hirsute and Impish. [Test Plan] * Create initrd with zstd $ mkinitramfs -c zstd -o zstd-initrd.img * Uncompress it with $ unmkinitramfs ./zstd-initrd.img zstd-initrd- unpacked [Where problems could occur] * This adds support for zstd compressed initrd in both mkinitramfs and unmkinitramfs. However our GA kernels do not support zstd compressed initrds. And depends on zstd package is not added either. Meaning one still has to install zstd to gain the unpack support. Changing initramfs.conf to zstd may result in unbootable instance when used with GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932542/+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 1932542] Re: Add support for zstd
Hello Dimitri, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.6 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: initramfs-tools (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1932542 Title: Add support for zstd Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Committed Bug description: [Impact] * initramfs-tools in impish has changed default initrd compression to zstd. To allow compressing and uncompressing such initrds on Focal LTS release we should backport zstd support in the mkinitramfs & unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinitramfs tool to unpack and inspect impish initrds on a focal host. * Cherrypicking the feature from 0.138 release, which is also present in Hirsute and Impish. [Test Plan] * Create initrd with zstd $ mkinitramfs -c zstd -o zstd-initrd.img * Uncompress it with $ unmkinitramfs ./zstd-initrd.img zstd-initrd- unpacked [Where problems could occur] * This adds support for zstd compressed initrd in both mkinitramfs and unmkinitramfs. However our GA kernels do not support zstd compressed initrds. And depends on zstd package is not added either. Meaning one still has to install zstd to gain the unpack support. Changing initramfs.conf to zstd may result in unbootable instance when used with GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932542/+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 1923845] Re: Please compress packages with zstd by default
This bug was fixed in the package hello - 2.10-2ubuntu3 --- hello (2.10-2ubuntu3) impish; urgency=medium * Ubuntu Impish will be switching default dpkg compression format to Zstd. This upload is the first canary to signal the archive format change. dpkg in Ubuntu supports zstd in xenial and up. If any issues are identified with this package, please report them at https://pad.lv/1923845 LP: #1923845 -- Dimitri John Ledkov Fri, 18 Jun 2021 11:58:54 +0100 ** Changed in: hello (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default Status in appstream-glib package in Ubuntu: New Status in apt package in Ubuntu: Fix Released Status in aptly package in Ubuntu: New Status in boinc package in Ubuntu: New Status in busybox package in Ubuntu: New Status in cdebootstrap package in Ubuntu: New Status in cdist package in Ubuntu: New Status in debdelta package in Ubuntu: New Status in debian-el package in Ubuntu: New Status in debootstrap package in Ubuntu: Fix Released Status in debsig-verify package in Ubuntu: New Status in debsigs package in Ubuntu: New Status in diffoscope package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in dpkg-sig package in Ubuntu: New Status in file package in Ubuntu: New Status in hello package in Ubuntu: Fix Released Status in libsolv package in Ubuntu: New Status in lintian package in Ubuntu: Fix Released Status in lutris package in Ubuntu: New Status in obs-build package in Ubuntu: New Status in osc package in Ubuntu: New Status in radare2 package in Ubuntu: New Status in reprepro package in Ubuntu: New Status in vim-scripts package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: New Bug description: https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built on Hirsute having both data and control members of the .deb being compressed with zstd. It can be handy for testing various tools. [dpkg] Decompression support in dpkg landed first in Bionic and is being SRUd to Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the zstd-compressed binary packages. From dpkg's perspective the upgrade path is cleared. The original plan was compressing only the internal data.tar .deb member, but dpkg uses uniform compression by default since dpkg 1.19.0 thus I'm collecting all the changes to support control.tar.zst, too, in this bug. Reviewed packages from: https://codesearch.debian.net/search?q=data.tar.xz=1=1 https://codesearch.debian.net/search?q=control.tar.xz=1=1 appstream-glib - needs fix: libappstream-builder/asb-package-deb.c aptly - needs fix: deb/deb.go boinc - needs fix: debian/fetch_example_applications.sh busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c cdebootstrap- needs fix: src/package.c cdist - may need fix, can use dpkg-deb: cdist/preos/debootstrap/files/devuan-debootstrap/functions debdelta- needs fix: debdelta debpatch.sh debian-el - needs fix: deb-view.el debian-handbook - needs fix, maybe later, for Debian debootstrap - needs fix, https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54 debsigs - needs fix, debsigs debsig-verify - needs fix, src/debsig-verify.c diffoscope - needs fix, diffoscope/comparators/deb.py dpkg- needs fix, change default dpkg-sig- needs fix, dpkg-sig dpmb- needs fix, maybe later, for Debian elfutils- may need fix, uses dpkg-deb if it is available, does not handle .gz either file- needs fix, magic/Magdir/archive libsolv - needs fix, ext/repo_deb.c lintian - needs fix malformed-deb-archive lutris - needs fix, lutris/util/extract.py obs-build - needs fix Build/Deb.pm osc - needs fix osc/util/debquery.py control.tar.zst only python-apt - needs fix apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() radare2 - needs fix reprepro- needs fix, debfile.c vim-scripts - needs fix debPlugin/autoload/deb.vim winetricks - needs fix when Debian switches src/winetricks zeroinstall-injector - needs fix src/zeroinstall/archive.ml acr - skip, does not _have to_ be fixed, just creates packages, see dist/deb_hand.mak alien - skip, uses dpkg-deb to extract .deb ansible - not affected, just test data in dbdata.tar.xz anthy - not affected, just changelog entry apt - seems fixed already ceph- not affected in Ubuntu's version circlator - not affected, just test data cowdancer
[Touch-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.7 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
The tests actually ran with systemd/245.4-4ubuntu3.6 and not with systemd/245.4-4ubuntu3.7. We are having some issues with the hwe-5.11 meta packages which caused the tests with 3.7 to be run with the wrong kernel. ** Description changed: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz + armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz + s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz + + In arm64, ppc64el and s390x, 'root-unittests' fails with: + + /* test_protect_sysctl */ + Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function test_protect_sysctl(). A + borting. + sysctlseccomp terminated by signal ABRT. + Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == EXIT_SUCCESS' failed at s + rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting. + FAIL: test-seccomp (code: 134) + + In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which + apparently is caused by the same 'test-seccomp.c:311' assertion failure. ** Summary changed: - systemd/245.4-4ubuntu3.7 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 + systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 -- 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/1933090 Title: systemd/245.4-4ubuntu3.6 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in systemd package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in systemd source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz In arm64, ppc64el and s390x, 'root-unittests' fails with: /* test_protect_sysctl */ Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function test_protect_sysctl(). A borting. sysctlseccomp terminated by signal ABRT. Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == EXIT_SUCCESS' failed at s rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting. FAIL: test-seccomp (code: 134) In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which apparently is caused by the same 'test-seccomp.c:311' assertion failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+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 1933090] [NEW] systemd/245.4-4ubuntu3.7 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Public bug reported: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-5.11 (Ubuntu Focal) 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/1933090 Title: systemd/245.4-4ubuntu3.7 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in systemd package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in systemd source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+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 1907886] Re: avinfo is missing
** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1907886 Title: avinfo is missing Status in bluez package in Ubuntu: In Progress Bug description: The "avinfo" command line tools available in bluez/tools (https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools) is not available in the package. The package bluez-tools (https://packages.ubuntu.com/groovy/bluez- tools) seems to map another project external to bluez (https://github.com/khvzak/bluez-tools) and not the "tools" folder of bluez. "avinfo" is used for example in order to check which codecs are supported by a headphone set (see https://github.com/EHfive /pulseaudio-modules-bt/issues/31#issuecomment-462717049). Maybe have "bluez-tools" map the "tools" folder of bluez, and move the other project to another package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1907886/+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 1917601] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51
Found on groovy/aws 5.8.0-1036.38 ** Tags added: aws -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1917601 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51 Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Groovy: Confirmed Bug description: We seem to get failed dep8 testing on lxc in Groovy for a while. What we are interested in is knowing whether this is known problems in the testing or something that waits on kernel fixes (who would be driving those if this is the case). Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/lxc/20210224_161232_5c8ac@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/l/lxc/20210224_202135_e7aed@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/l/lxc/20210224_172418_73aab@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/l/lxc/20210224_164056_06e00@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917601/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Thank you Brian for following up on this! Is there any news regarding the fix in Hirsute yet? Two months of not being able to access iCloud mails in a core component of the current supported Ubuntu release is a really long time ... :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Triaged Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1932022] Re: Can you add the btvirt executable to bluez-tests?
** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932022 Title: Can you add the btvirt executable to bluez-tests? Status in bluez package in Ubuntu: In Progress Bug description: See the Debian package: https://packages.debian.org/buster/i386/bluez- test-tools/filelist The Ubuntu package contains the same tools, except for btvirt. Would it be possible to add this? The buildlog shows that the btvirt executable is already built, but just not put into the *.deb package. Additions to be done to debian/bluez-tests.install: emulator/b1ee usr/bin emulator/btvirt usr/bin emulator/hfp usr/bin Having the btvirt tool available will make testing on CI systems a lot easier. References: https://github.com/hadess/bluez/blob/master/Makefile.tools#L76-L82 https://answers.launchpad.net/ubuntu/+source/bluez/+question/697542 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932022/+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 1901115] Re: package bluez failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to start Bluetooth service.
** Summary changed: - package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to start Bluetooth service.] + package bluez failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to start Bluetooth service.] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1901115 Title: package bluez failed to install/upgrade: installed bluez package post- installation script subprocess returned error exit status 1 [Failed to start Bluetooth service.] Status in bluez package in Ubuntu: Confirmed Bug description: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 23 07:08:46 2020 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=8e6f60a5-d013-4d5d-83ed-df27737e1381 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: bluez Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago) dmi.bios.date: 10/03/2019 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05YMV0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd10/03/2019:br1.10:svnDellInc.:pnLatitude3180:pvr:rvnDellInc.:rn05YMV0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3180 dmi.product.sku: 07B2 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 74:70:FD:58:F6:73 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:2712 acl:0 sco:0 events:305 errors:0 TX bytes:50942 acl:0 sco:0 commands:305 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901115/+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 1929833] Re: bluez: meshctl missing
** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1929833 Title: bluez: meshctl missing Status in bluez package in Ubuntu: In Progress Bug description: bluez has added a new tool for BT mesh handling. Debian has a new binary package: https://packages.debian.org/bullseye /bluez-meshd Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+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 1933080] Re: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1901115 *** https://bugs.launchpad.net/bugs/1901115 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1901115, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1901115 package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to start Bluetooth service.] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933080 Title: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 21 11:08:56 2021 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-11 (101 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=05af585d-21ef-4aab-a647-bf6f798a1ee1 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bluez Title: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.3:bd03/17/2021:br1.14:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:8D:7C:B4 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:28400076 acl:327 sco:0 events:3488107 errors:0 TX bytes:2059958316 acl:3291744 sco:0 commands:27448 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933080/+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 1899193] Re: local denial of service due to parsing bugs in arfile.cc
its laging and not adding my pakadges or exepting my passwords -- 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/1899193 Title: local denial of service due to parsing bugs in arfile.cc Status in apt package in Ubuntu: Fix Released Status in aptdaemon package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Fix Released Bug description: # GitHub Security Lab (GHSL) Vulnerability Report: `GHSL-2020-168`, `GHSL-2020-169`, `GHSL-2020-170` The [GitHub Security Lab](https://securitylab.github.com) team has identified potential security vulnerabilities in aptd. We are committed to working with you to help resolve these issues. In this report you will find everything you need to effectively coordinate a resolution of these issues with the GHSL team. If at any point you have concerns or questions about this process, please do not hesitate to reach out to us at `security...@github.com` (please include `GHSL-2020-168`, `GHSL-2020-169`, or `GHSL-2020-170` as a reference). If you are _NOT_ the correct point of contact for this report, please let us know! ## Summary The aptd daemon is a system service for installing and updating packages. It is accessible via [dbus](https://www.freedesktop.org/wiki/Software/dbus/) and has a method named "InstallFile" which is used for installing local `.deb` packages. Although polkit is used to prevent an unprivileged user from using "InstallFile" to install a malicious `.deb` package, it does not prevent aptd from parsing the contents of the `.deb` file. The parsing logic is provided by two packages, [libapt-pkg- dev](https://packages.ubuntu.com/focal/libapt-pkg-dev) and [python- apt](https://packages.ubuntu.com/source/focal/python-apt), and is implemented in C. These two packages contain several bugs, which an unprivileged user can exploit to trigger a local denial of service attack. ## Product aptd ## Tested Version * libapt-pkg-dev: version 2.0.2ubuntu0.1 * python-apt: 2.0.0ubuntu0.20.04.1 * Tested on Ubuntu 20.04.1 LTS ## Details ### Issue 1: aptd crash due to integer overflow in arfile.cc (GHSL-2020-168) A crafted `.deb` package can trigger a negative integer overflow at [arfile.cc, line 116](https://git.launchpad.net/ubuntu/+source/apt/tree/apt- pkg/contrib/arfile.cc?h=applied/ubuntu/focal- updates=4c264e60b524855b211751e1632ba48526f6b44d#n116): ```c Memb->Size -= Len; ``` Due to the integer overflow, the value of `Memb->Size` is `0x`. This leads to an out-of-memory error at [arfile.cc, line 602](https://git.launchpad.net/ubuntu/+source/python- apt/tree/python/arfile.cc?h=applied/ubuntu/focal- updates=0f7cc93acdb51d943114f1cd79002288c4ca4d24#n602): ```c char* value = new char[member->Size]; ``` The out-of-memory error causes aptd to crash. Please note that the source locations above refer to two separate files, both named `arfile.cc`. The first is from the libapt-pkg-dev package and the second is from the python-apt package. To trigger the crash, first use the attached source file named "createdeb.c" to generate the malicious `.deb` file: ```bash gcc createdeb.c -o createdeb ./createdeb crash test.deb ``` Now use `dbus-send` to send the malicious `.deb` file to aptd: ```bash $ dbus-send --system --type="method_call" --print-reply --dest=org.debian.apt /org/debian/apt org.debian.apt.InstallFile string:`realpath test.deb` boolean:true method return time=1602245339.731762 sender=:1.287 -> destination=:1.288 serial=8 reply_serial=2 string "/org/debian/apt/transaction/90f29de930854568964af1918f6ca5eb" $ dbus-send --system --type="method_call" --print-reply --dest=org.debian.apt /org/debian/apt/transaction/90f29de930854568964af1918f6ca5eb org.debian.apt.transaction.Run ``` Note that you need to use the "transaction id" returned by the first `dbus-send` in the second `dbus-send` command. Impact This issue may lead to local denial of service. Resources I have attached `createdeb.c`, which can be used to generate the malicious `.deb` file. ### Issue 2: aptd infinite loop due to integer overflow in arfile.cc (GHSL-2020-169) This issue is very similar to issue 1, but is caused by a different bug. This bug occurs during the call to `StrToNum` at [arfile.cc, line 92](https://git.launchpad.net/ubuntu/+source/apt/tree/apt- pkg/contrib/arfile.cc?h=applied/ubuntu/focal- updates=4c264e60b524855b211751e1632ba48526f6b44d#n92): ```c StrToNum(Head.Size,Memb->Size,sizeof(Head.Size)) == false) ``` The bug is due to the use of `strtoul` in [StrToNum](https://git.launchpad.net/ubuntu/+source/apt/tree/apt- pkg/contrib/strutl.cc?h=applied/ubuntu/focal- updates=4c264e60b524855b211751e1632ba48526f6b44d#n1169): ```c //
[Touch-packages] [Bug 1933080] Re: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933080 Title: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 21 11:08:56 2021 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-11 (101 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=05af585d-21ef-4aab-a647-bf6f798a1ee1 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bluez Title: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.3:bd03/17/2021:br1.14:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:8D:7C:B4 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:28400076 acl:327 sco:0 events:3488107 errors:0 TX bytes:2059958316 acl:3291744 sco:0 commands:27448 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933080/+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 1923845] Re: Please compress packages with zstd by default
** Tags removed: block-proposed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default Status in appstream-glib package in Ubuntu: New Status in apt package in Ubuntu: Fix Released Status in aptly package in Ubuntu: New Status in boinc package in Ubuntu: New Status in busybox package in Ubuntu: New Status in cdebootstrap package in Ubuntu: New Status in cdist package in Ubuntu: New Status in debdelta package in Ubuntu: New Status in debian-el package in Ubuntu: New Status in debootstrap package in Ubuntu: Fix Released Status in debsig-verify package in Ubuntu: New Status in debsigs package in Ubuntu: New Status in diffoscope package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in dpkg-sig package in Ubuntu: New Status in file package in Ubuntu: New Status in hello package in Ubuntu: New Status in libsolv package in Ubuntu: New Status in lintian package in Ubuntu: Fix Released Status in lutris package in Ubuntu: New Status in obs-build package in Ubuntu: New Status in osc package in Ubuntu: New Status in radare2 package in Ubuntu: New Status in reprepro package in Ubuntu: New Status in vim-scripts package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: New Bug description: https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built on Hirsute having both data and control members of the .deb being compressed with zstd. It can be handy for testing various tools. [dpkg] Decompression support in dpkg landed first in Bionic and is being SRUd to Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the zstd-compressed binary packages. From dpkg's perspective the upgrade path is cleared. The original plan was compressing only the internal data.tar .deb member, but dpkg uses uniform compression by default since dpkg 1.19.0 thus I'm collecting all the changes to support control.tar.zst, too, in this bug. Reviewed packages from: https://codesearch.debian.net/search?q=data.tar.xz=1=1 https://codesearch.debian.net/search?q=control.tar.xz=1=1 appstream-glib - needs fix: libappstream-builder/asb-package-deb.c aptly - needs fix: deb/deb.go boinc - needs fix: debian/fetch_example_applications.sh busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c cdebootstrap- needs fix: src/package.c cdist - may need fix, can use dpkg-deb: cdist/preos/debootstrap/files/devuan-debootstrap/functions debdelta- needs fix: debdelta debpatch.sh debian-el - needs fix: deb-view.el debian-handbook - needs fix, maybe later, for Debian debootstrap - needs fix, https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54 debsigs - needs fix, debsigs debsig-verify - needs fix, src/debsig-verify.c diffoscope - needs fix, diffoscope/comparators/deb.py dpkg- needs fix, change default dpkg-sig- needs fix, dpkg-sig dpmb- needs fix, maybe later, for Debian elfutils- may need fix, uses dpkg-deb if it is available, does not handle .gz either file- needs fix, magic/Magdir/archive libsolv - needs fix, ext/repo_deb.c lintian - needs fix malformed-deb-archive lutris - needs fix, lutris/util/extract.py obs-build - needs fix Build/Deb.pm osc - needs fix osc/util/debquery.py control.tar.zst only python-apt - needs fix apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() radare2 - needs fix reprepro- needs fix, debfile.c vim-scripts - needs fix debPlugin/autoload/deb.vim winetricks - needs fix when Debian switches src/winetricks zeroinstall-injector - needs fix src/zeroinstall/archive.ml acr - skip, does not _have to_ be fixed, just creates packages, see dist/deb_hand.mak alien - skip, uses dpkg-deb to extract .deb ansible - not affected, just test data in dbdata.tar.xz anthy - not affected, just changelog entry apt - seems fixed already ceph- not affected in Ubuntu's version circlator - not affected, just test data cowdancer - not affected, just documentation eccodes - skip, just orig-data.tar.xz eckit - skip, just ...orig-data.tar.xz firefox - skip, profdata.tar.xz firefox-esr - skip, profdata.tar.xz galculator - skip, just changelog grads - skip, ...orig-data.tar.xz gvmd- skip, just creates xz compressed .deb insighttoolkit4 - skip, ...orig-data.tar.xz jdeb- skip, just creates compressed .deb packages jmol- skip, just local data archive jq
[Touch-packages] [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Seems the patch is so hard to backport (?) -- 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 1933080] [NEW] package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 21 11:08:56 2021 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-11 (101 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=05af585d-21ef-4aab-a647-bf6f798a1ee1 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bluez Title: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.3:bd03/17/2021:br1.14:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:8D:7C:B4 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:28400076 acl:327 sco:0 events:3488107 errors:0 TX bytes:2059958316 acl:3291744 sco:0 commands:27448 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933080 Title: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 21 11:08:56 2021 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-11 (101 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=05af585d-21ef-4aab-a647-bf6f798a1ee1 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: bluez Title: package bluez 5.53-0ubuntu3.2 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.3:bd03/17/2021:br1.14:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6
[Touch-packages] [Bug 1933078] [NEW] BlueZ 5.59 release
Public bug reported: Release BlueZ 5.59 to impish. ** Affects: bluez (Ubuntu) Importance: Wishlist Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
On Mon, Jun 21, 2021 at 05:53:41AM -, Christian Ehrhardt wrote: > We finally got an answer to our questions/pings (thanks Simon) > => > https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q2/015134.html > > TL;DR: this might be wanted new behavior :/ ?! > > @Laney - You initially started this when we have faced this bug > I wonder now if we should indeed drop our delta and resolve the fallout in > other places like the formerly breaking tests. > You have back then thought deeper into this, while I only carried this delta > a few times. > Therefore I'd appreciate if you could let me know what you think of that > reply. > > P.S. Because if we drop it then I guess we better do that now than e.g. > late in 22.04 :-) I don't know to be honest. What do you think, does that argument make sense? I don't really understand why it should be different whether you're using DHCPv6 or SLAAC, but maybe it's just me not getting something right now. If it's fine, then feel free to drop the patch and upload a NM with adjusted regexes (preferrably committing to the VCS too). Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq package in Debian: New Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1916827] Re: Update libgweather to v40
** Changed in: libgweather (Ubuntu) Status: New => Fix Committed ** Changed in: libgweather (Ubuntu) Importance: Undecided => High ** Changed in: libgweather (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1916827 Title: Update libgweather to v40 Status in libgweather package in Ubuntu: Fix Committed Bug description: Without the latest gweather v40, gnome-shell 40 fails to start: (gnome-shell:14525): Gjs-CRITICAL **: 14:24:49.987: JS ERROR: Error: No property application_id on GWeatherInfo WeatherClient@resource:///org/gnome/shell/misc/weather.js:75:29 _init@resource:///org/gnome/shell/ui/dateMenu.js:478:31 _init@resource:///org/gnome/shell/ui/dateMenu.js:872:29 _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1012:25 _updateBox@resource:///org/gnome/shell/ui/panel.js:1023:34 _updatePanel@resource:///org/gnome/shell/ui/panel.js:968:14 _init@resource:///org/gnome/shell/ui/panel.js:778:14 _initializeUI@resource:///org/gnome/shell/ui/main.js:228:13 start@resource:///org/gnome/shell/ui/main.js:169:5 @:1:47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1916827/+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 1919134] Re: Please package gsettings-desktop-schemas >= 40.alpha
** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1919134 Title: Please package gsettings-desktop-schemas >= 40.alpha Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Bug description: Please package gsettings-desktop-schemas >= 40.alpha as it is required to build mutter 40. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1919134/+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
** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1227 Importance: Unknown Status: Unknown ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- 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: Unknown Status in pulseaudio package in Ubuntu: New 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/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 help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.11 --- pulseaudio (1:13.99.1-1ubuntu3.11) focal; urgency=medium * d/p/0016-check_off_profile_when_switching_profile.patch * d/p/0017-add_dynamic_priority_bonus_base_for_alsa_profiles.patch Fix a "Rear Mic" always showing on input list when using dual codec. (LP: #1929371) [ Hui Wang ] * d/p/0704-alsa-mixer-use-safe-dB-range-values-when-the-overrid.patch * d/p/0705-alsa-mixer-add-support-up-8-mixer-channels.patch - The linux kernel 5.11 starts supporting more than 2 channels for the digital mic, we need to add the support of 8 channels for a single alsa mixer, otherwise the PA can't change the hardware input volume of the digital mic. (LP: #1929817) -- Jeremy Szu Tue, 25 May 2021 16:04:07 + -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: Triaged Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] In Lenovo P520, which using a codec for front panel, the other codec for rear panel and both are on a same card. In this case, the rear Mic will present on input devices of "Sound Settings" even if attaching nothing to rear mic jack. [Fix] For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl because of ``` control.18 { iface CARD name 'Rear Mic Jack' value true comment { access read type BOOLEAN count 1 } } ``` After applying "Rear Mic Jack", the rear Mic will not always there anymore but it's not there as well if hot-plugging audio device on rear mic. Thus, it needs to change pulseaudio to handle if all devices are off cases. For pulseaudio, if there is no any audio devices attached, then attaching an input device on rear mic jack. The port will not be selected automatically because the profiles is off. It needs patch pulseaudio to check off profiles (for dual codec case). [Test] After applying these patches, the rear mic jack works good in all cases (boot without mic and then attach mic, boot with mic and then hotplug it) and other functions (line-in / line-out) work pretty well. [Where problems could occur] This change only apply the bonus on below cases: ``` if ((has_input_port && found_available_input_port && !has_output_port) || (has_output_port && found_available_output_port && !has_input_port) || (has_input_port && found_available_input_port && has_output_port && found_available_output_port)) ``` and these cases have been tested. If there are some complex codec design then it might cause problem but so far we didn't see that. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929817] Update Released
The verification of the Stable Release Update for pulseaudio has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.8 --- alsa-ucm-conf (1.2.2-1ubuntu0.8) focal; urgency=medium * d/p/0001-HDA-Intel-add-RearMic-JackControl.patch Add "Rear Mic Jack" to make P520 rear mic works correctly. (LP: #1929371) -- Jeremy Szu Tue, 25 May 2021 11:42:01 + ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: Triaged Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] In Lenovo P520, which using a codec for front panel, the other codec for rear panel and both are on a same card. In this case, the rear Mic will present on input devices of "Sound Settings" even if attaching nothing to rear mic jack. [Fix] For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl because of ``` control.18 { iface CARD name 'Rear Mic Jack' value true comment { access read type BOOLEAN count 1 } } ``` After applying "Rear Mic Jack", the rear Mic will not always there anymore but it's not there as well if hot-plugging audio device on rear mic. Thus, it needs to change pulseaudio to handle if all devices are off cases. For pulseaudio, if there is no any audio devices attached, then attaching an input device on rear mic jack. The port will not be selected automatically because the profiles is off. It needs patch pulseaudio to check off profiles (for dual codec case). [Test] After applying these patches, the rear mic jack works good in all cases (boot without mic and then attach mic, boot with mic and then hotplug it) and other functions (line-in / line-out) work pretty well. [Where problems could occur] This change only apply the bonus on below cases: ``` if ((has_input_port && found_available_input_port && !has_output_port) || (has_output_port && found_available_output_port && !has_input_port) || (has_input_port && found_available_input_port && has_output_port && found_available_output_port)) ``` and these cases have been tested. If there are some complex codec design then it might cause problem but so far we didn't see that. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.11 --- pulseaudio (1:13.99.1-1ubuntu3.11) focal; urgency=medium * d/p/0016-check_off_profile_when_switching_profile.patch * d/p/0017-add_dynamic_priority_bonus_base_for_alsa_profiles.patch Fix a "Rear Mic" always showing on input list when using dual codec. (LP: #1929371) [ Hui Wang ] * d/p/0704-alsa-mixer-use-safe-dB-range-values-when-the-overrid.patch * d/p/0705-alsa-mixer-add-support-up-8-mixer-channels.patch - The linux kernel 5.11 starts supporting more than 2 channels for the digital mic, we need to add the support of 8 channels for a single alsa mixer, otherwise the PA can't change the hardware input volume of the digital mic. (LP: #1929817) -- Jeremy Szu Tue, 25 May 2021 16:04:07 + ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+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
created report https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1227 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1227 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1227 -- 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 help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1932021] Re: cannot find proper graphics drivers and cannot install
Thanks for the bug report. It appears the correct driver for your Nvidia GPU is version 390.143 which does exist in hirsute. You can try installing it by: sudo apt install nvidia-driver-390 Also, you appear to have some unsupported graphics packages installed from the 'oidbaf' PPA, which is known to cause bugs. Please remove that PPA from your system. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Summary changed: - cannot find proper graphics drivers and cannot install + cannot find proper graphics drivers and cannot install (NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]) -- 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/1932021 Title: cannot find proper graphics drivers and cannot install (NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]) Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Invalid Bug description: in the additional driver, till the last update 20.10 i had option to choose the nvidia graphics diver. now after the upgrade to hippo i am unable to change the driver. also cannot install drivers from command line as well. while installing the latest or any other nvidia drivers had issues of mismatch packages and the install was broken every time i try. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 15 19:02:03 2021 DistUpgraded: 2021-06-15 01:56:42,836 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-55-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [17aa:3817] InstallationDate: Installed on 2020-09-14 (274 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20404 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=5bdb42c7-4383-40ee-b1ba-ee63c9932b5f ro quiet splash i8042.nokbd vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-06-14 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: A0CN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Flex 2-14 dmi.board.vendor: LENOVO dmi.board.version: 31900059 Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Flex 2-14 dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrA0CN26WW:bd05/21/2014:br1.9:efr1.3:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900059Std:cvnLENOVO:ct10:cvrLenovoFlex2-14: dmi.product.family: IDEAPAD dmi.product.name: 20404 dmi.product.sku: LENOVO_MT_20404_BU_idea_FM_Lenovo Flex 2-14 dmi.product.version: Lenovo Flex 2-14 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104+git2101240500.19f0a9~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.1~git2102070600.92f129~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 21.1~git2102070600.92f129~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1932021/+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 1932021] Re: cannot find proper graphics drivers and cannot install (NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M])
Since the 'oibaf' PPA is likely the problem here I am going to close this bug. Please uninstall the PPA, reboot, and if the problem continues to occur then open a new bug. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Invalid ** Changed in: software-properties (Ubuntu) Status: New => Invalid -- 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/1932021 Title: cannot find proper graphics drivers and cannot install (NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]) Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Invalid Bug description: in the additional driver, till the last update 20.10 i had option to choose the nvidia graphics diver. now after the upgrade to hippo i am unable to change the driver. also cannot install drivers from command line as well. while installing the latest or any other nvidia drivers had issues of mismatch packages and the install was broken every time i try. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 15 19:02:03 2021 DistUpgraded: 2021-06-15 01:56:42,836 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-18-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-55-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [17aa:3817] InstallationDate: Installed on 2020-09-14 (274 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20404 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=5bdb42c7-4383-40ee-b1ba-ee63c9932b5f ro quiet splash i8042.nokbd vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-06-14 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: A0CN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Flex 2-14 dmi.board.vendor: LENOVO dmi.board.version: 31900059 Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Flex 2-14 dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrA0CN26WW:bd05/21/2014:br1.9:efr1.3:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900059Std:cvnLENOVO:ct10:cvrLenovoFlex2-14: dmi.product.family: IDEAPAD dmi.product.name: 20404 dmi.product.sku: LENOVO_MT_20404_BU_idea_FM_Lenovo Flex 2-14 dmi.product.version: Lenovo Flex 2-14 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104+git2101240500.19f0a9~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.1~git2102070600.92f129~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 21.1~git2102070600.92f129~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1932021/+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 1931793] Re: two bluetooth icons
** Package changed: xorg (Ubuntu) => gnome-shell (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/1931793 Title: two bluetooth icons Status in gnome-shell package in Ubuntu: Incomplete Bug description: There two different bluetooth icons on my taskbar. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 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: Sun Jun 13 13:49:02 2021 DistUpgraded: 2020-05-22 21:25:58,624 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81eb] InstallationDate: Installed on 2020-01-28 (501 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd HP TrueVision HD Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=e8d9a762-01b7-4681-bf37-86327e77af4a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-22 (386 days ago) dmi.bios.date: 01/05/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EB dmi.board.vendor: HP dmi.board.version: 61.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/05/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: 1DE70PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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 20.2.6-0ubuntu0.20.04.1 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/gnome-shell/+bug/1931793/+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 1933064] Re: [Clevo NS50MU] Max screen brightness after suspend
** Summary changed: - Max screen brightness after suspend + [Clevo NS50MU] Max screen brightness after suspend ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Package changed: linux (Ubuntu) => linux-hwe-5.8 (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/1933064 Title: [Clevo NS50MU] Max screen brightness after suspend Status in linux-hwe-5.8 package in Ubuntu: New Bug description: When I suspend my laptop and start using it again, screen brightness is always at a maximum. When I then adjust the screen brightness, it all of a sudden remembers the state it was in before suspending (usually the lowest setting). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 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: Mon Jun 21 08:49:49 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:51a1] InstallationDate: Installed on 2021-05-31 (20 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Notebook NS50MU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-55-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=! acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06LWL dmi.board.name: NS50MU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06LWL:bd09/07/2020:br7.6:efr7.2:svnNotebook:pnNS50MU:pvrNotApplicable:rvnNotebook:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NS50MU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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.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/linux-hwe-5.8/+bug/1933064/+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 1933067] Re: Startup bios defective
Please explain in more detail what kind of problem you are experiencing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1933067 Title: Startup bios defective Status in Ubuntu: Incomplete Bug description: Ubuntu updates prone to fail. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-119.120-generic 4.15.18 Uname: Linux 4.15.0-119-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 21 00:12:50 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2015-12-20 (2010 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-119-generic root=UUID=a019a556-761b-432a-9ed2-c81051ae44fe ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.15 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.15:bd02/23/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.15:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.15 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Sep 17 01:04:12 2018 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5504 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1933067/+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 1933003] Re: left click on USB mouse stops working
Sounds like either a faulty mouse or a Xorg-specific bug (the login screen doesn't use Xorg). Please try either a new mouse, or selecting 'Ubuntu on Wayland' from the login screen. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1933003 Title: left click on USB mouse stops working Status in xorg-server package in Ubuntu: Incomplete Bug description: ## Issue with mouse left-button click Issue with left-button (button 1) click. After login left mouse button click stops working. Within xev rectangle, it (button 1) does not show output first time. but after right button click it starts showing output in xen output as shown in xev-output.log file. After that, left button click works once or twice in other windows like chrome etc, but then stops working after that. full manufacturer and model of your mouse. - HP X1000 Wired Mouse - Connected via USB - Has 2-buttons and one middle scrooll wheel and has optical sensor ## Attachements (inside 'debug-attachments.zip' file_ - Recent apt updates are in apt-history.log file - xen output as shown in xev-output.log file - xmodmap -pp > ~/xmodmap-pp ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.03 Mon Mar 29 17:51:27 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: Sat Jun 19 20:10:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.119.03, 5.8.0-53-generic, x86_64: installed nvidia, 450.119.03, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83ba] Subsystem: Hewlett-Packard Company GP108M [GeForce MX150] [103c:83ba] InstallationDate: Installed on 2020-05-18 (396 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 003: ID 0408:5251 Quanta Computer, Inc. HP Wide Vision FHD Camera Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 15-ch0xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=10b0a8d0-b11d-4604-a11a-0717ee06ce60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2019 dmi.bios.release: 15.31 dmi.bios.vendor: AMI dmi.bios.version: F.31 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83BA dmi.board.vendor: HP dmi.board.version: 57.33 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 57.33 dmi.modalias: dmi:bvnAMI:bvrF.31:bd05/20/2019:br15.31:efr57.33:svnHP:pnHPSpectrex360Convertible15-ch0xx:pvr:rvnHP:rn83BA:rvr57.33:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-ch0xx dmi.product.sku: 2LV24UA#ABA dmi.sys.vendor: HP 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 20.2.6-0ubuntu0.20.04.1 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
[Touch-packages] [Bug 1932979] Re: blank screen with cursor after login
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1932979 Title: blank screen with cursor after login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 on amd64. I came back to the machine after it was idle long enough for the screen to go blank. I can see the cursor move with the mouse, but nothing else. This is VT2. VT1 shows a login screen. I can get to console VTs as well and did so to file the report. I see the following in the system log that may be related: Jun 18 18:29:54 cerberus gnome-shell[4694]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3568871 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3568998 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: Source ID 3569045 was not found when attempting to remove it Jun 18 18:29:54 cerberus gnome-shell[4694]: [System monitor] applet disable Jun 18 18:29:54 cerberus gnome-shell[4694]: g_dbus_connection_emit_signal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 18 19:33:55 2021 DistUpgraded: 2020-11-04 10:03:47,100 DEBUG running doUpdate() (showErrors=True) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2020-05-29 (385 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Supermicro X10DAi ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=linux XDG_RUNTIME_DIR= PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=/dev/mapper/ubuntu--vg-root ro amdgpu.dc=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-11-04 (226 days ago) dmi.bios.date: 12/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 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.:bvr3.2:bd12/16/2019:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.sku: 083615D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro 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 20.2.6-0ubuntu0.20.04.1 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/gnome-shell/+bug/1932979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless
It appears the offending kernel is indeed about two weeks old: https://launchpad.net/ubuntu/+source/linux-oem-5.10/5.10.0-1029.30 ** Summary changed: - Video conferences constantly freeze when I am on wireless + [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless ** Package changed: xorg (Ubuntu) => linux-oem-5.10 (Ubuntu) ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. 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 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. 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 20.2.6-0ubuntu0.20.04.1 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/linux-oem-5.10/+bug/1932548/+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 1933067] [NEW] Startup bios defective
Public bug reported: Ubuntu updates prone to fail. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-119.120-generic 4.15.18 Uname: Linux 4.15.0-119-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 21 00:12:50 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2015-12-20 (2010 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-119-generic root=UUID=a019a556-761b-432a-9ed2-c81051ae44fe ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.15 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.15:bd02/23/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.15:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.15 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Sep 17 01:04:12 2018 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5504 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1933067 Title: Startup bios defective Status in xorg package in Ubuntu: New Bug description: Ubuntu updates prone to fail. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-119.120-generic 4.15.18 Uname: Linux 4.15.0-119-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 21 00:12:50 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2015-12-20 (2010 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-119-generic root=UUID=a019a556-761b-432a-9ed2-c81051ae44fe ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.15 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC
[Touch-packages] [Bug 1932108] Re: bluetooth not starting also airplane mode is not working. laptop hp pavillion g6
Thanks for the bug report. The only log information I can find that might be relevant is: [ 30.453981] Bluetooth: hci0: command 0x1009 tx timeout which suggests a problem with the kernel driver, or the hardware. ** Summary changed: - bluetooth not starting also airplane mode is not working. laptop hp pavillion g6 + [USB 0a5c:21b4 Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR] [HP Pavilion g6] Bluetooth not starting also airplane mode is not working. ** Package changed: bluez (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932108 Title: [USB 0a5c:21b4 Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR] Bluetooth not starting also airplane mode is not working. Status in linux package in Ubuntu: Confirmed Bug description: native bluetooth is not working.Sometimes disabling the wifi and bluetooth hardware and then enabling it again enables bluetooth. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 16 11:28:58 2021 InstallationDate: Installed on 2021-01-27 (140 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=35e14111-9084-42ac-baef-472ae96d2665 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-06-08 (7 days ago) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:34 acl:0 sco:0 events:3 errors:0 TX bytes:12 acl:0 sco:0 commands:4 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932108/+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 1932377] Re: [HDA-Intel - HDA Intel MID, playback] No sound at all. bluetooth hedphones aren connected but in built speakers are used. to make bluetooth headphones to work i need
*** This bug is a duplicate of bug 1932108 *** https://bugs.launchpad.net/bugs/1932108 ** This bug has been marked a duplicate of bug 1932108 [USB 0a5c:21b4 Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR] Bluetooth not starting also airplane mode is not working. -- 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/1932377 Title: [HDA-Intel - HDA Intel MID, playback] No sound at all. bluetooth hedphones aren connected but in built speakers are used. to make bluetooth headphones to work i need to remove them from settings and addd them again. hp pavillion g6 Status in alsa-driver package in Ubuntu: New Bug description: firstly bluetooth services is somehow dead. to make it work we need to disable the hardware for some time so that in power settings both wifi and bluetooth is turned off and them enable it again for bluetooth to work. and after that if bluetooth is connected automatically then the audio input and output both works from laptop and after removing and adding again the bluetooth then only output is given from headphone. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 2136 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:26:55 2021 InstallationDate: Installed on 2021-01-27 (141 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 2136 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel MID, playback] No sound at all UpgradeStatus: Upgraded to hirsute on 2021-06-08 (9 days ago) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1932377/+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 1932066] Re: PulseAudio Preferences searches for libraries in incorrect location
** Tags added: 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/1932066 Title: PulseAudio Preferences searches for libraries in incorrect location Status in pulseaudio package in Ubuntu: New Bug description: PulseAudio Preferences (paprefs) appears to be searching for modules in the wrong location. Specifically, the "install" button appears when modules relevant modules cannot be found by paprefs. paprefs is searching for modules in the location: /usr/lib/pulse-13.99/modules/ the modules are actually located in: /usr/lib/pulse-13.99.1/modules/ The specifics of this were determined via `strace paprefs`, which (among a lot of other things), produces: access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT (No such file or directory) access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) = -1 ENOENT (No such file or directory) creating a symlink from /usr/lib/pulse-13.99.1 to /usr/lib/pulse-13.99 resolves the issue. paprefs should perhaps be updated to match the version of the pulseaudio package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1932066/+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 1932022] Re: Can you add the btvirt executable to bluez-tests?
** Tags added: impish ** Changed in: bluez (Ubuntu) Importance: Undecided => Wishlist ** Changed in: bluez (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932022 Title: Can you add the btvirt executable to bluez-tests? Status in bluez package in Ubuntu: Triaged Bug description: See the Debian package: https://packages.debian.org/buster/i386/bluez- test-tools/filelist The Ubuntu package contains the same tools, except for btvirt. Would it be possible to add this? The buildlog shows that the btvirt executable is already built, but just not put into the *.deb package. Additions to be done to debian/bluez-tests.install: emulator/b1ee usr/bin emulator/btvirt usr/bin emulator/hfp usr/bin Having the btvirt tool available will make testing on CI systems a lot easier. References: https://github.com/hadess/bluez/blob/master/Makefile.tools#L76-L82 https://answers.launchpad.net/ubuntu/+source/bluez/+question/697542 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932022/+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 1933064] [NEW] Max screen brightness after suspend
Public bug reported: When I suspend my laptop and start using it again, screen brightness is always at a maximum. When I then adjust the screen brightness, it all of a sudden remembers the state it was in before suspending (usually the lowest setting). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 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: Mon Jun 21 08:49:49 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:51a1] InstallationDate: Installed on 2021-05-31 (20 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Notebook NS50MU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-55-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=! acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06LWL dmi.board.name: NS50MU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06LWL:bd09/07/2020:br7.6:efr7.2:svnNotebook:pnNS50MU:pvrNotApplicable:rvnNotebook:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NS50MU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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.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 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/1933064 Title: Max screen brightness after suspend Status in xorg package in Ubuntu: New Bug description: When I suspend my laptop and start using it again, screen brightness is always at a maximum. When I then adjust the screen brightness, it all of a sudden remembers the state it was in before suspending (usually the lowest setting). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 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: Mon Jun 21 08:49:49 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:51a1] InstallationDate: Installed on 2021-05-31 (20 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Notebook NS50MU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-55-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=! acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06LWL dmi.board.name: NS50MU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06LWL:bd09/07/2020:br7.6:efr7.2:svnNotebook:pnNS50MU:pvrNotApplicable:rvnNotebook:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NS50MU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook
[Touch-packages] [Bug 1931902] Re: [Asus PRIME B450-PLUS] Crackling sound on Pulseaudio for Ubuntu 21.04
** Summary changed: - Crackling sound on Pulseaudio for Ubuntu 21.04 + [Asus PRIME B450-PLUS] Crackling sound on Pulseaudio for Ubuntu 21.04 -- 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/1931902 Title: [Asus PRIME B450-PLUS] Crackling sound on Pulseaudio for Ubuntu 21.04 Status in pulseaudio package in Ubuntu: New Bug description: While playing back any sounds, a certain crackling sound (static) will play with a fixed delay of the sound being played. The amount and volume of the static will depend on the sound/music that is being played, and this only starts occurring after a somewhat long time (30 minutes or more). What is interesting to see is that while playing back music from Spotify (Snap) the static will only start after a second or so, but when playing YouTube videos on Firefox, it will be immediate and output that static while the video is playing. I've added two sound recordings, one while playing back a song from Spotify and the other while playing a song from YouTube. This issue goes away when restarting the PulseAudio service, but it comes back after a random amount of time. 1) Description: Ubuntu 21.04 Release: 21.04 2) pulseaudio: Installed: 1:14.2-1ubuntu1 Candidate: 1:14.2-1ubuntu1 Version table: 1:14.2-1ubuntu1.1 1 (phased 10%) 500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:14.2-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: matheus 18662 F pulseaudio /dev/snd/controlC2: matheus 18662 F pulseaudio /dev/snd/controlC0: matheus 18662 F pulseaudio /dev/snd/pcmC0D8p: matheus 18662 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 14 16:58:43 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-05-03 (41 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+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 1931870] Re: System freezes several times per week, sometimes more than once per day
The open source 'nouveau' driver you are using is known to be unstable. Please use the 'Additional Drivers' app to install the official Nvidia driver. ** Tags added: nouveau ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - System freezes several times per week, sometimes more than once per day + [nouveau] System freezes several times per week, sometimes more than once per day -- 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/1931870 Title: [nouveau] System freezes several times per week, sometimes more than once per day Status in linux package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-55.62-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Jun 14 15:18:03 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (150 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QQS0KL13 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-55-generic root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS0KL13 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: ZF211710 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:br1.23:efr1.14:svnLENOVO:pn20QQS0KL13:pvrThinkPadP53:rvnLENOVO:rn20QQS0KL13:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QQS0KL13 dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931870/+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 1931807] Re: unable to install intel hd graphic on ubuntu
There is nothing to install. Intel drivers are built-in and yours appear to be working properly. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1931807 Title: unable to install intel hd graphic on ubuntu Status in Ubuntu: Invalid Bug description: kindly fix the issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 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: Sun Jun 13 20:34:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics [8086:1606] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics [103c:80c1] InstallationDate: Installed on 2021-02-20 (112 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57d6 Realtek Semiconductor Corp. HP Truevision HD Bus 001 Device 002: ID 0bda:b006 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=bf96a269-335b-44b8-ad20-bbdd984dd05b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.release: 15.38 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: HP dmi.board.version: 96.51 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 96.51 dmi.modalias: dmi:bvnInsyde:bvrF.26:bd03/06/2018:br15.38:efr96.51:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C1:rvr96.51:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: P4Y39PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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.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/+bug/1931807/+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 1931741] Re: Second Display Never Supports Proper Resolution
*** This bug is a duplicate of bug 1901470 *** https://bugs.launchpad.net/bugs/1901470 I've decoded your monitor's EDID data (see attached) and it only supports the detailed modes 3440x1440 or 2560x1080. Not "2560x1440", although you can fake it with xrandr as you say. So if that's the only issue then this bug is invalid. If you find 3440x1440 or 2560x1080 are missing by default however, then this is kernel bug 1901470. ** Attachment added: "edid-decoded.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1931741/+attachment/5505924/+files/edid-decoded.txt ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1931741 Title: Second Display Never Supports Proper Resolution Status in Ubuntu: New Bug description: I have tried cables, drivers, upgrades --no matter what I do I cannot get Ubuntu to recognize that my 32" UHD LG display supports 2560x1440. I can work around it with `cvt` and `xrandr` but this is tedious and is not saved across sessions, and xorg.conf is no longer a possibility (bricks the system). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 12:06:05 2021 DistUpgraded: 2021-06-11 10:51:25,279 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09a4] InstallationDate: Installed on 2021-03-08 (95 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. OptiPlex 7080 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-11 (0 days ago) dmi.bios.date: 12/24/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0J37VM dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd12/24/2020:br1.3:svnDellInc.:pnOptiPlex7080:pvr:rvnDellInc.:rn0J37VM:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7080 dmi.product.sku: 09A4 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1931741/+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 1931756] Re: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
So far the 20.04 uses 5.8.0-generic kernel, it is not easy to backport soundwire code to 5.8 kernel. And the 20.04 is going to replace 5.8 kernel with 5.11.0-generic kernel soon, when this happens, the LTS will support your machine. -- 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/1931756 Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: Fix Released Bug description: I have tried modifications to DKMS, modprobe.d, pulseaudio and alsa but all were no sound. The modprobe,d modifications did result in the "dummy" message being replaced by a device. This was done 2 installs ago,sorry. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pbea 1894 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Jun 11 23:34:27 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0P25F6 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd03/04/2021:br1.7:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P25F6:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1931756/+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
I'm not familiar with mpd. It sounds like maybe you should seek advice from the developers by opening an upstream issue at: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues or https://gitlab.freedesktop.org/pipewire/pipewire/-/issues -- 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 help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
We finally got an answer to our questions/pings (thanks Simon) => https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q2/015134.html TL;DR: this might be wanted new behavior :/ ?! @Laney - You initially started this when we have faced this bug I wonder now if we should indeed drop our delta and resolve the fallout in other places like the formerly breaking tests. You have back then thought deeper into this, while I only carried this delta a few times. Therefore I'd appreciate if you could let me know what you think of that reply. P.S. Because if we drop it then I guess we better do that now than e.g. late in 22.04 :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq package in Debian: New Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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