[Touch-packages] [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
that would require a newer libepoxy
--
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 crashed with SIGABRT when under memory pressure
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Released
Status in mesa source package in Hirsute:
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/oem-priority/+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 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
this bug was about iris, if you have some other issue that *requires
iris*, then file a new one
--
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 crashed with SIGABRT when under memory pressure
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Released
Status in mesa source package in Hirsute:
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/oem-priority/+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 1940503] [NEW] Illegal instruction (core dumped) on apt update
Public bug reported: Ran `apt update` and received Illegal instruction (core dumped) Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi' E: Sub-process returned an error code at the end. Ran `apt update` again with no problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.6 ProcVersionSignature: Ubuntu 5.13.0-1010.11-oem 5.13.1 Uname: Linux 5.13.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Aug 19 08:46:31 2021 InstallationDate: Installed on 2018-11-21 (1001 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-04-21 (484 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "apt update output" https://bugs.launchpad.net/bugs/1940503/+attachment/5519001/+files/apt-update-bug.txt -- 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/1940503 Title: Illegal instruction (core dumped) on apt update Status in apt package in Ubuntu: New Bug description: Ran `apt update` and received Illegal instruction (core dumped) Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi' E: Sub-process returned an error code at the end. Ran `apt update` again with no problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.6 ProcVersionSignature: Ubuntu 5.13.0-1010.11-oem 5.13.1 Uname: Linux 5.13.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Aug 19 08:46:31 2021 InstallationDate: Installed on 2018-11-21 (1001 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-04-21 (484 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1940503/+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 crashed with SIGABRT when under memory pressure
Also remember you can test iris using environment
MESA_LOADER_DRIVER_OVERRIDE=iris
--
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 crashed with SIGABRT when under memory pressure
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Released
Status in mesa source package in Hirsute:
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/oem-priority/+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 1940504] [NEW] Support Alder Lake P/M graphics
Public bug reported: [Impact] [Fix] [Test case] [Where things could go wrong] ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: libdrm (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1940504 Title: Support Alder Lake P/M graphics Status in libdrm package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in libdrm source package in Focal: New Status in linux-oem-5.13 source package in Focal: New Status in mesa source package in Focal: New Bug description: [Impact] [Fix] [Test case] [Where things could go wrong] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 crashed with SIGABRT when under memory pressure
I encountered exactly same issue as this bug on bionic so I would like to
leverage iris fix (iris-avoid-abort-if-enomem.diff) but bionic mesa prefer i965
by default over iris.
Do I need to file a new one on mesa/i965 driver?
Aug 3 03:12:39 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) glamor0: GL
error: GL_OUT_OF_MEMORY in glTexImage2D
Aug 3 03:12:50 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE)
Aug 3 03:12:50 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) Backtrace:
Aug 3 03:12:54 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) 0:
/usr/lib/xorg/Xorg (?+0x0) [0x556430b27080]
Aug 3 03:12:54 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (?+0x0) [0x7f7778ae697f]
Aug 3 03:12:56 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) 2:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so (?+0x0) [0x7f7773960a70]
Aug 3 03:12:56 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) 3:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so (?+0x0) [0x7f7773960d10]
Aug 3 03:12:56 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so (?+0x0) [0x7f7773960de0]
--
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 crashed with SIGABRT when under memory pressure
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Released
Status in mesa source package in Hirsute:
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/oem-priority/+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 1940505] [NEW] monero FTBFS on riscv64
Public bug reported: monero FTBFS on riscv64 due to toolchain issues: [ 64%] Linking CXX executable signature_fuzz_tests cd "/<>/obj-riscv64-linux-gnu/tests/fuzz" && /usr/bin/cmake -E cmake_link_script CMakeFiles/signature_fuzz_tests.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DNO_AES -fno-strict-aliasing -std=c++11 -D_GNU_SOURCE -Wall -Wextra -Wpointer-arith -Wundef -Wvla -Wwrite-strings -Wno-error=extra -Wno-error=deprecated-declarations -Wno-unused-parameter -Wno-unused-variable -Wno-error=unused-variable -Wno-error=undef -Wno-error=uninitialized -Wlogical-op -Wno-error=maybe-uninitialized -Wno-error=cpp -Wno-reorder -Wno-missing-field-initializers -fPIC -Wformat -Wformat-security -fstack-protector -fstack-protector-strong -fstack-clash-protection -fno-strict-aliasing -ftemplate-depth=900 -Wl,-Bsymbolic-functions -Wl,-z,relro -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack -rdynamic CMakeFiles/signature_fuzz_tests.dir/signature.cpp.o CMakeFiles/signature_fuzz_tests.dir/fuzzer.cpp.o -o signature_fuzz_tests ../../lib/libwallet.a ../../src/cryptonote_core/libcryptonote_core.a ../../src/p2p/libp2p.a ../../contrib/epee/src/libepee.a ../../src/device/libdevice.a -Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl ../../src/rpc/librpc_base.a ../../src/mnemonics/libmnemonics.a ../../src/device_trezor/libdevice_trezor.a ../../src/cryptonote_core/libcryptonote_core.a ../../src/multisig/libmultisig.a ../../src/blockchain_db/libblockchain_db.a ../../external/db_drivers/liblmdb/liblmdb.a ../../src/ringct/libringct.a ../../src/cryptonote_basic/libcryptonote_basic.a ../../src/device/libdevice.a -lhidapi-libusb ../../src/ringct/libringct_basic.a ../../src/blocks/libblocks.a ../../src/checkpoints/libcheckpoints.a ../../src/hardforks/libhardforks.a ../../src/net/libnet.a ../../src/common/libcommon.a ../../src/crypto/libcncrypto.a ../../contrib/epee/src/libepee.a ../../external/easylogging++/libeasylogging.a -lrandomx -lunbound -lboost_regex -lboost_date_time -lssl -lcrypto -lzmq -lpgm -lnorm -lgssapi_krb5 -lsodium ../../src/libversion.a -lminiupnpc -lboost_chrono -lboost_serialization -lboost_filesystem -lboost_system -lboost_thread -lboost_program_options -Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl -latomic ../../external/db_drivers/liblmdb/liblmdb.a(mdb.c.o): in function `mdb_node_add': ./obj-riscv64-linux-gnu/external/db_drivers/liblmdb/./external/db_drivers/liblmdb/mdb.c:8245:(.text+0x44e6): relocation truncated to fit: R_RISCV_JAL against `mdb_assert_fail.constprop.0' collect2: error: ld returned 1 exit status make[3]: *** [tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/build.make:166: tests/fuzz/signature_fuzz_tests] Error 1 make[3]: Leaving directory '/<>/obj-riscv64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:4165: tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/all] Error 2 make[2]: Leaving directory '/<>/obj-riscv64-linux-gnu' make[1]: *** [Makefile:163: all] Error 2 make[1]: Leaving directory '/<>/obj-riscv64-linux-gnu' dh_auto_build: error: cd obj-riscv64-linux-gnu && make -j1 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:47: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 ** Affects: binutils Importance: Unknown Status: Unknown ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Affects: monero (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs ** Bug watch added: Sourceware.org Bugzilla #25181 https://sourceware.org/bugzilla/show_bug.cgi?id=25181 ** Also affects: xmr-stak-cpu via https://sourceware.org/bugzilla/show_bug.cgi?id=25181 Importance: Unknown Status: Unknown ** No longer affects: xmr-stak-cpu ** Summary changed: - FTBFS on riscv64 + monero FTBFS on riscv64 ** Also affects: binutils (Ubuntu) Importance: Undecided Status: New ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=25181 Importance: Unknown Status: Unknown ** Bug watch added: github.com/riscv/riscv-gnu-toolchain/issues #738 https://github.com/riscv/riscv-gnu-toolchain/issues/738 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1940505 Title: monero FTBFS on riscv64 Status in binutils: Unknown Status in binutils package in Ubuntu: New Status in monero package in Ubuntu: New Bug description: monero FTBFS on riscv64 due to toolchain issues: [ 64%] Linking CXX executable signature_fuzz_tests cd "/<>/obj-riscv64-linux-gnu/tests/fuzz" && /usr/bin/cmake -E cmake_link_script CMakeFiles/signature_fuzz_tests.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wfor
[Touch-packages] [Bug 1940505] Re: monero FTBFS on riscv64
Some context: https://github.com/riscv/riscv-gnu-toolchain/issues/738 https://sourceware.org/bugzilla/show_bug.cgi?id=25181 According to the latter, this should already be fixed in upstream binutils since several years... why does it still happen? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1940505 Title: monero FTBFS on riscv64 Status in binutils: Unknown Status in binutils package in Ubuntu: New Status in monero package in Ubuntu: New Bug description: monero FTBFS on riscv64 due to toolchain issues: [ 64%] Linking CXX executable signature_fuzz_tests cd "/<>/obj-riscv64-linux-gnu/tests/fuzz" && /usr/bin/cmake -E cmake_link_script CMakeFiles/signature_fuzz_tests.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DNO_AES -fno-strict-aliasing -std=c++11 -D_GNU_SOURCE -Wall -Wextra -Wpointer-arith -Wundef -Wvla -Wwrite-strings -Wno-error=extra -Wno-error=deprecated-declarations -Wno-unused-parameter -Wno-unused-variable -Wno-error=unused-variable -Wno-error=undef -Wno-error=uninitialized -Wlogical-op -Wno-error=maybe-uninitialized -Wno-error=cpp -Wno-reorder -Wno-missing-field-initializers -fPIC -Wformat -Wformat-security -fstack-protector -fstack-protector-strong -fstack-clash-protection -fno-strict-aliasing -ftemplate-depth=900 -Wl,-Bsymbolic-functions -Wl,-z,relro -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack -rdynamic CMakeFiles/signature_fuzz_tests.dir/signature.cpp.o CMakeFiles/signature_fuzz_tests.dir/fuzzer.cpp.o -o signature_fuzz_tests ../../lib/libwallet.a ../../src/cryptonote_core/libcryptonote_core.a ../../src/p2p/libp2p.a ../../contrib/epee/src/libepee.a ../../src/device/libdevice.a -Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl ../../src/rpc/librpc_base.a ../../src/mnemonics/libmnemonics.a ../../src/device_trezor/libdevice_trezor.a ../../src/cryptonote_core/libcryptonote_core.a ../../src/multisig/libmultisig.a ../../src/blockchain_db/libblockchain_db.a ../../external/db_drivers/liblmdb/liblmdb.a ../../src/ringct/libringct.a ../../src/cryptonote_basic/libcryptonote_basic.a ../../src/device/libdevice.a -lhidapi-libusb ../../src/ringct/libringct_basic.a ../../src/blocks/libblocks.a ../../src/checkpoints/libcheckpoints.a ../../src/hardforks/libhardforks.a ../../src/net/libnet.a ../../src/common/libcommon.a ../../src/crypto/libcncrypto.a ../../contrib/epee/src/libepee.a ../../external/easylogging++/libeasylogging.a -lrandomx -lunbound -lboost_regex -lboost_date_time -lssl -lcrypto -lzmq -lpgm -lnorm -lgssapi_krb5 -lsodium ../../src/libversion.a -lminiupnpc -lboost_chrono -lboost_serialization -lboost_filesystem -lboost_system -lboost_thread -lboost_program_options -Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl -latomic ../../external/db_drivers/liblmdb/liblmdb.a(mdb.c.o): in function `mdb_node_add': ./obj-riscv64-linux-gnu/external/db_drivers/liblmdb/./external/db_drivers/liblmdb/mdb.c:8245:(.text+0x44e6): relocation truncated to fit: R_RISCV_JAL against `mdb_assert_fail.constprop.0' collect2: error: ld returned 1 exit status make[3]: *** [tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/build.make:166: tests/fuzz/signature_fuzz_tests] Error 1 make[3]: Leaving directory '/<>/obj-riscv64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:4165: tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/all] Error 2 make[2]: Leaving directory '/<>/obj-riscv64-linux-gnu' make[1]: *** [Makefile:163: all] Error 2 make[1]: Leaving directory '/<>/obj-riscv64-linux-gnu' dh_auto_build: error: cd obj-riscv64-linux-gnu && make -j1 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:47: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1940505/+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 1940504] Re: Support Alder Lake P graphics
** Summary changed: - Support Alder Lake P/M graphics + Support Alder Lake P graphics -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1940504 Title: Support Alder Lake P graphics Status in libdrm package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in libdrm source package in Focal: New Status in linux-oem-5.13 source package in Focal: New Status in mesa source package in Focal: New Bug description: [Impact] [Fix] [Test case] [Where things could go wrong] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 crashed with SIGABRT when under memory pressure
Although that stack trace is not useful the GL_OUT_OF_MEMORY does kind
of give it away that it's the same kind of issue as this. I would say it
makes sense to do a different fix for i965 but keep using this same bug
ID.
--
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 crashed with SIGABRT when under memory pressure
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Released
Status in mesa source package in Hirsute:
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/oem-priority/+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 1940503] Re: Illegal instruction (core dumped) on apt update
This seems to be a bug in command-not-found, Python, or any of the libraries it used. For further investigation, we need a core dump from that process, did apport not prompt you for that? ** Package changed: apt (Ubuntu) => command-not-found (Ubuntu) ** Changed in: command-not-found (Ubuntu) Status: New => Incomplete -- 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/1940503 Title: Illegal instruction (core dumped) on apt update Status in command-not-found package in Ubuntu: Incomplete Bug description: Ran `apt update` and received Illegal instruction (core dumped) Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi' E: Sub-process returned an error code at the end. Ran `apt update` again with no problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.6 ProcVersionSignature: Ubuntu 5.13.0-1010.11-oem 5.13.1 Uname: Linux 5.13.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Aug 19 08:46:31 2021 InstallationDate: Installed on 2018-11-21 (1001 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-04-21 (484 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1940503/+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 1940504] Re: Support Alder Lake P graphics
** Changed in: libdrm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1940504 Title: Support Alder Lake P graphics Status in libdrm package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in libdrm source package in Focal: New Status in linux-oem-5.13 source package in Focal: New Status in mesa source package in Focal: New Bug description: [Impact] [Fix] [Test case] [Where things could go wrong] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1929184] Re: [21.10 FEAT] RoCE: Predictable Interface Names - systemd part
The modified version already landed in -proposed. Hence updating the status to Fix Committed. ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Committed ** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- 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/1929184 Title: [21.10 FEAT] RoCE: Predictable Interface Names - systemd part Status in Ubuntu on IBM z Systems: Fix Committed Status in systemd package in Ubuntu: Fix Committed Bug description: Feature Description: - Interface names for RoCE Express adapters are currently very hard to predict, causing problems with the installer which requires knowledge of the interface name - Interface names can change between re-boots, invalidating any previously stored network card configuration To fix this requires changes in the Linux kernel to indicate whether UIDs are unique (and therefore usable), and in systemd to generate an interface name based on UIDs all the time. Business Case: Increase usability, lower service efforts. The code is in the upstream repository and should eventually be contained in the upcoming systemd release 249 a496a23 udev: fix slot based network names on s390 b08c3fb udev: add missing initialization to fix freeing invalid address 5a7eb46 udev: allow onboard index up to 65535 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929184/+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 1940516] [NEW] A potential bug of return stack address
Public bug reported: Ubuntu version: 18.04 sqlite version:3.22 Hello,I found apotential bugs in package sqlite3,and the .docx file in the attachment I uploaded shows the occurrence process of the bug in a graphical way.Would you help me check whether the bug mentioned below are true? Thank you very much for your patience. In file sqlite3/build/shell.c(build is a directory generated by configure) In function zipfileFilter In line 4923: load value of pointer which is parameter of function to pCsr In line 4966: load stack address to member of *pCsr The entire graphic description is shown in figure 1 in .docx file. ** Affects: sqlite3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "return_stack_address.docx" https://bugs.launchpad.net/bugs/1940516/+attachment/5519049/+files/return_stack_address.docx -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1940516 Title: A potential bug of return stack address Status in sqlite3 package in Ubuntu: New Bug description: Ubuntu version: 18.04 sqlite version:3.22 Hello,I found apotential bugs in package sqlite3,and the .docx file in the attachment I uploaded shows the occurrence process of the bug in a graphical way.Would you help me check whether the bug mentioned below are true? Thank you very much for your patience. In file sqlite3/build/shell.c(build is a directory generated by configure) In function zipfileFilter In line 4923: load value of pointer which is parameter of function to pCsr In line 4966: load stack address to member of *pCsr The entire graphic description is shown in figure 1 in .docx file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1940516/+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 1940517] [NEW] Several potential bugs of memory leak
Public bug reported: Ubuntu version: 18.04 sqlite version:3.22 Hello,I found two apotential bugs in package sqlite3,and the .docx file in the attachment I uploaded shows the occurrence process of the bugs in a graphical way.Would you help me check whether the bugs mentioned below are true? Thank you very much for your patience. In file sqlite3-3.22.0\tool\lemon.c In function pathsearch there is allocation of memory,and in certain way,this memory can not be freed correctly. The entire graphic description is shown in figure 1 in .docx file. In file sqlite3\build\shell.c(build is a directory contain files generated by configure) In function readfile there is allocation of memory,and in certain way,this memory can not be freed correctly. The entire graphic description is shown in figure 2 in .docx file. ** Affects: sqlite3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "memory_leak.docx" https://bugs.launchpad.net/bugs/1940517/+attachment/5519050/+files/memory_leak.docx -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1940517 Title: Several potential bugs of memory leak Status in sqlite3 package in Ubuntu: New Bug description: Ubuntu version: 18.04 sqlite version:3.22 Hello,I found two apotential bugs in package sqlite3,and the .docx file in the attachment I uploaded shows the occurrence process of the bugs in a graphical way.Would you help me check whether the bugs mentioned below are true? Thank you very much for your patience. In file sqlite3-3.22.0\tool\lemon.c In function pathsearch there is allocation of memory,and in certain way,this memory can not be freed correctly. The entire graphic description is shown in figure 1 in .docx file. In file sqlite3\build\shell.c(build is a directory contain files generated by configure) In function readfile there is allocation of memory,and in certain way,this memory can not be freed correctly. The entire graphic description is shown in figure 2 in .docx file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1940517/+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 1940504] Re: Support Alder Lake P graphics
** Description changed: + NOTE: this is for focal only, hirsute/impish do not and will not have + kernel support for this. + [Impact] + ADL-P machines need to use the native driver. [Fix] + Backport support from upstream. + + libdrm: a single patch from 2.4.107 + mesa: three commits to add pci-id's and a workaround + kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports [Test case] + Boot a machine and check that it's using the native driver and that the usual workloads are fine. [Where things could go wrong] ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1940504 Title: Support Alder Lake P graphics Status in libdrm package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Focal: New Status in linux-oem-5.13 source package in Focal: New Status in mesa source package in Focal: New Bug description: NOTE: this is for focal only, hirsute/impish do not and will not have kernel support for this. [Impact] ADL-P machines need to use the native driver. [Fix] Backport support from upstream. libdrm: a single patch from 2.4.107 mesa: three commits to add pci-id's and a workaround kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports [Test case] Boot a machine and check that it's using the native driver and that the usual workloads are fine. [Where things could go wrong] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1921518] Re: OpenSSL "double free" error
Cannot reproduce the issue when using `openssl s_client -connect` or when using `wget` so it is specific to curl + openssl + engine at the moment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1921518 Title: OpenSSL "double free" error Status in openssl package in Ubuntu: New Bug description: "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+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 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
And then I tried "sudo linux-purge --keep=1". That has tidied up a bit, but there's still not much space?field.comment=And then I tried "sudo linux-purge --keep=1". That has tidied up a bit, but there's still not much space. Now /boot contains: # du -sh /boot/* 248K/boot/config-5.10.0-1038-oem 248K/boot/config-5.10.0-1044-oem 248K/boot/config-5.11.0-25-generic 248K/boot/config-5.11.0-27-generic 48M /boot/efi 8.0M/boot/grub 0 /boot/initrd.img 113M/boot/initrd.img-5.10.0-1038-oem 113M/boot/initrd.img-5.10.0-1044-oem 112M/boot/initrd.img-5.11.0-25-generic 112M/boot/initrd.img-5.11.0-27-generic 0 /boot/initrd.img.old 16K /boot/lost+found 180K/boot/memtest86+.bin 184K/boot/memtest86+.elf 184K/boot/memtest86+_multiboot.bin 5.6M/boot/System.map-5.10.0-1038-oem 5.6M/boot/System.map-5.10.0-1044-oem 5.6M/boot/System.map-5.11.0-25-generic 5.6M/boot/System.map-5.11.0-27-generic 0 /boot/vmlinuz 12M /boot/vmlinuz-5.10.0-1038-oem 12M /boot/vmlinuz-5.10.0-1044-oem 9.7M/boot/vmlinuz-5.11.0-25-generic 9.7M/boot/vmlinuz-5.11.0-27-generic 0 /boot/vmlinuz.old # df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p2 705M 526M 129M 81% /boot ** Attachment added: "linux-purge-keep-1.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+attachment/5519055/+files/linux-purge-keep-1.txt -- 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/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full Status in initramfs-tools package in Ubuntu: Confirmed Bug description: System calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u". The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the update-initramfs script should be fixed. But there may not be such a partition.. Anyway the likely case when space runs out is when there is a separate /boot partition. Alternatively the init scripts should remove the respective /boot/initrd.img- file when removing/installing the linux-image-extra package. That could also be done by update-initramfs -d -k That may be worse way, as then initrd.img file is missing for longer period of time and system integrity may suffer in case of e.g. power cut. Related question: http://askubuntu.com/q/898499/21005 The output of 'dpkg --purge' presented there shows that corresponding linux-image package may get successfully removed while the linux-image-extra is left broken. If the linux-image-extra package will be removed later, the post-installation script will create an initrd.img file for a non-installed kernel! Same would happen, if removing would be done by apt-get purge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+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 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
Here is the result of linux-purge --info My /boot is like this: # du -sh /boot/* 248K/boot/config-5.10.0-1038-oem 248K/boot/config-5.10.0-1044-oem 248K/boot/config-5.11.0-25-generic 248K/boot/config-5.11.0-27-generic 244K/boot/config-5.8.0-63-generic 48M /boot/efi 8.0M/boot/grub 0 /boot/initrd.img 113M/boot/initrd.img-5.10.0-1038-oem 113M/boot/initrd.img-5.10.0-1044-oem 112M/boot/initrd.img-5.11.0-25-generic 112M/boot/initrd.img-5.11.0-27-generic 113M/boot/initrd.img-5.8.0-63-generic 0 /boot/initrd.img.old 16K /boot/lost+found 180K/boot/memtest86+.bin 184K/boot/memtest86+.elf 184K/boot/memtest86+_multiboot.bin 5.6M/boot/System.map-5.10.0-1038-oem 5.6M/boot/System.map-5.10.0-1044-oem 5.6M/boot/System.map-5.11.0-25-generic 5.6M/boot/System.map-5.11.0-27-generic 5.3M/boot/System.map-5.8.0-63-generic 0 /boot/vmlinuz 12M /boot/vmlinuz-5.10.0-1038-oem 12M /boot/vmlinuz-5.10.0-1044-oem 9.7M/boot/vmlinuz-5.11.0-25-generic 9.7M/boot/vmlinuz-5.11.0-27-generic 9.4M/boot/vmlinuz-5.8.0-63-generic 0 /boot/vmlinuz.old ** Attachment added: "linux-purge-info.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+attachment/5519054/+files/linux-purge-info.txt -- 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/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full Status in initramfs-tools package in Ubuntu: Confirmed Bug description: System calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u". The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the update-initramfs script should be fixed. But there may not be such a partition.. Anyway the likely case when space runs out is when there is a separate /boot partition. Alternatively the init scripts should remove the respective /boot/initrd.img- file when removing/installing the linux-image-extra package. That could also be done by update-initramfs -d -k That may be worse way, as then initrd.img file is missing for longer period of time and system integrity may suffer in case of e.g. power cut. Related question: http://askubuntu.com/q/898499/21005 The output of 'dpkg --purge' presented there shows that corresponding linux-image package may get successfully removed while the linux-image-extra is left broken. If the linux-image-extra package will be removed later, the post-installation script will create an initrd.img file for a non-installed kernel! Same would happen, if removing would be done by apt-get purge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+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 1929184] Re: [21.10 FEAT] RoCE: Predictable Interface Names - systemd part
--- Comment From boris.m...@de.ibm.com 2021-08-19 06:35 EDT--- Despite the initial concern because of the amount of fixes, Canonical managed to get this feature (systemd part) into Impish 21.10. This way, we will have the full functionality of this feature and don't have to add a release note regarding limitations. Therefore, changing Target Milestone back from 22.04 -> 21.10 ** Tags removed: targetmilestone-inin2204 ** Tags added: targetmilestone-inin2110 -- 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/1929184 Title: [21.10 FEAT] RoCE: Predictable Interface Names - systemd part Status in Ubuntu on IBM z Systems: Fix Committed Status in systemd package in Ubuntu: Fix Committed Bug description: Feature Description: - Interface names for RoCE Express adapters are currently very hard to predict, causing problems with the installer which requires knowledge of the interface name - Interface names can change between re-boots, invalidating any previously stored network card configuration To fix this requires changes in the Linux kernel to indicate whether UIDs are unique (and therefore usable), and in systemd to generate an interface name based on UIDs all the time. Business Case: Increase usability, lower service efforts. The code is in the upstream repository and should eventually be contained in the upcoming systemd release 249 a496a23 udev: fix slot based network names on s390 b08c3fb udev: add missing initialization to fix freeing invalid address 5a7eb46 udev: allow onboard index up to 65535 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929184/+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 1921518] Re: OpenSSL "double free" error
Found curl missuse of openssl api; Found missing use-after-free fixes in openssl; in addition to the pka engine fixes that are possible. Imho all three should be fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1921518 Title: OpenSSL "double free" error Status in openssl package in Ubuntu: New Bug description: "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+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 1940528] [NEW] curl 7.68 does not init OpenSSL correctly
Public bug reported: [Impact] * curl 7.68 does not correctly use OpenSSL 1.1.0+ api to init OpenSSL global state prior to executing any OpenSSL APIs. This may lead to duplicate engine initiation, which upon engine unload may cause use- after-free or double-free of any methods that engine installs. This has been fixed in curl 7.74 by correctly calling OpenSSL init api prior to any other calls to OpenSSL apis. [Test Plan] * This should be reproducible with any engines that allocate & register methods, and free them upon engine unload. Then use curl with openssl backend to test for corrupted stack. * I.e. on arm64, compile and configure pka engine from https://github.com/Mellanox/pka/commit/b0f32fa05298bf9e3997ea43fc1c11b90e0d662f (i.e. without the double-free protections proposed in https://github.com/Mellanox/pka/pull/37 ) on any arm64 hardware, there is no need for the engine to actually work or have access to anything, as the issue is reproducible when engine is enabled but cannot be effectively used. * curl any https website ... PKA_DEV: pka_dev_open_ring_vfio: error: failed to get ring 50 device name PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 3520 0 --:--:-- --:--:-- --:--:-- 3520 (exit status 0) is good output from fixed curl. Whereas: PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 1169 0 --:--:-- --:--:-- --:--:-- 1169 Segmentation fault (core dumped) (exit status non-zero) is bad output from currently broken curl. [Where problems could occur] * Correctly calling OpenSSL init function prior to any other OpenSSL apis changes the behaviour of the library slightly - specifically openssl configuration file and engines are initialised and loaded earlier, meaning that site-local customizations are applied correctly whenever using curl cli utility or libcurl4 (the openssl version of curl). This will make engine support working correctly across the board. However, if one has missconfigured openssl conf and missconfigured engines which are now actually attempted to be used one may experience unexpected behaviour changes (since potentially existing configuration was not actually taking effect). [Other Info] * References: https://github.com/curl/curl/commit/1835cb916e0d40eb8bc1165d5627a0b64f911bac https://github.com/openssl/openssl/issues/13548 https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518 ** Affects: curl (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: curl (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: curl (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: curl (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: curl (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: curl (Ubuntu Focal) Status: New => Confirmed ** Changed in: curl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1940528 Title: curl 7.68 does not init OpenSSL correctly Status in curl package in Ubuntu: Fix Released Status in curl source package in Bionic: New Status in curl source package in Focal: Confirmed Bug description: [Impact] * curl 7.68 does not correctly use OpenSSL 1.1.0+ api to init OpenSSL global state prior to executing any OpenSSL APIs. This may lead to duplicate engine initiation, which upon engine unload may cause use- after-free or double-free of any methods that engine installs. This has been fixed in curl 7.74 by correctly calling OpenSSL init api prior to any other calls to OpenSSL apis. [Test Plan] * This should be reproducible with any engines that allocate & register methods, and free them upon engine unload. Then use curl with openssl backend to test for corrupted stack. * I.e. on arm64, compile and configure pka engine from https://github.com/Mellanox/pka/commit/b0f32fa05298bf9e3997ea43fc1c11b90e0d662f (i.e. without the double-free protections proposed in https://github.com/Mellanox/pka/pull/37 ) on any arm64 hardware, there is no need for the engine to actually work or have access to anything, as the issue is reproducible when engine is enabled but cannot be effectively used. * curl any https website ... PKA_DEV: pka_dev_open_ring_vfio: error: failed to get ring 50 device name PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 3520 0 --:--:-- --:--:-- --:--:-- 3520 (exit status 0) is good output from fixed curl. Whereas: PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 1169 0 --:--:-- --:--
[Touch-packages] [Bug 1900905] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwer
/boot was full -- 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/1900905 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in initramfs-tools package in Ubuntu: Confirmed Bug description: do-release-upgrade from 18.04 LTS to 20.04 LTS results in this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 21 23:15:14 2020 ErrorMessage: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2015-02-06 (2084 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2020-10-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1900905/+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 1940528] Re: curl 7.68 does not init OpenSSL correctly
** Patch added: "lp1940528-openssl-use-OPENSSL_init_ssl-with-1.1.0.patch" https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528/+attachment/5519059/+files/lp1940528-openssl-use-OPENSSL_init_ssl-with-1.1.0.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1940528 Title: curl 7.68 does not init OpenSSL correctly Status in curl package in Ubuntu: Fix Released Status in curl source package in Bionic: New Status in curl source package in Focal: Confirmed Bug description: [Impact] * curl 7.68 does not correctly use OpenSSL 1.1.0+ api to init OpenSSL global state prior to executing any OpenSSL APIs. This may lead to duplicate engine initiation, which upon engine unload may cause use- after-free or double-free of any methods that engine installs. This has been fixed in curl 7.74 by correctly calling OpenSSL init api prior to any other calls to OpenSSL apis. [Test Plan] * This should be reproducible with any engines that allocate & register methods, and free them upon engine unload. Then use curl with openssl backend to test for corrupted stack. * I.e. on arm64, compile and configure pka engine from https://github.com/Mellanox/pka/commit/b0f32fa05298bf9e3997ea43fc1c11b90e0d662f (i.e. without the double-free protections proposed in https://github.com/Mellanox/pka/pull/37 ) on any arm64 hardware, there is no need for the engine to actually work or have access to anything, as the issue is reproducible when engine is enabled but cannot be effectively used. * curl any https website ... PKA_DEV: pka_dev_open_ring_vfio: error: failed to get ring 50 device name PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 3520 0 --:--:-- --:--:-- --:--:-- 3520 (exit status 0) is good output from fixed curl. Whereas: PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 1169 0 --:--:-- --:--:-- --:--:-- 1169 Segmentation fault (core dumped) (exit status non-zero) is bad output from currently broken curl. [Where problems could occur] * Correctly calling OpenSSL init function prior to any other OpenSSL apis changes the behaviour of the library slightly - specifically openssl configuration file and engines are initialised and loaded earlier, meaning that site-local customizations are applied correctly whenever using curl cli utility or libcurl4 (the openssl version of curl). This will make engine support working correctly across the board. However, if one has missconfigured openssl conf and missconfigured engines which are now actually attempted to be used one may experience unexpected behaviour changes (since potentially existing configuration was not actually taking effect). [Other Info] * References: https://github.com/curl/curl/commit/1835cb916e0d40eb8bc1165d5627a0b64f911bac https://github.com/openssl/openssl/issues/13548 https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528/+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 1921518] Re: OpenSSL "double free" error
Curl bug report https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1921518 Title: OpenSSL "double free" error Status in openssl package in Ubuntu: New Bug description: "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+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 1884079] Re: unmkinitramfs in initramfs-tools-core doesn't fully extract an initrd in bionic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1884079 Title: unmkinitramfs in initramfs-tools-core doesn't fully extract an initrd in bionic Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I am running Ubuntu 18.04.4 I am looking at the initrd found in the desktop live cd (/casper/initrd). If you execute `binwalk initrd`, binwalk informs that the initrd file contains 2 cpio archives and a lzma archive The first cpio archive is supposed to contain kernel/x86/microcode/AuthenticAMD.bin The second cpio archive is supposed to contain kernel/x86/microcode/GenuineIntel.bin The third file is a LZMA compressed data Now, if you execute `unmkinitramfs /casper/initrd new- directory` , you will see 2 directories, "early" and "main". "early" has the AuthenticAMD.bin, which means it corresponds to the first cpio. "main" is the actual initial ram disk file system, which comes from the LZMA compressed data. What I expect to see is also the GenuineIntel.bin firmware. `binwalk` says it's there, but `unmkinitramfs` is not able to extract it out. Why? I see binwalk is at version 2.1.1-16, while initramfs-tools-core (which provides unmkinitramfs) is at version 0.130ubuntu3.9. How do I extract the ubuntu 18 initramfs and get all the contents that binwalk is able to see? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1884079/+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 1884079] Re: unmkinitramfs in initramfs-tools-core doesn't fully extract an initrd in bionic
Issue persists in Ubuntu 20.04. Images created with update-mkinitramfs and default configuration are not fully extracted by unmkinitramfs. -- 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/1884079 Title: unmkinitramfs in initramfs-tools-core doesn't fully extract an initrd in bionic Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I am running Ubuntu 18.04.4 I am looking at the initrd found in the desktop live cd (/casper/initrd). If you execute `binwalk initrd`, binwalk informs that the initrd file contains 2 cpio archives and a lzma archive The first cpio archive is supposed to contain kernel/x86/microcode/AuthenticAMD.bin The second cpio archive is supposed to contain kernel/x86/microcode/GenuineIntel.bin The third file is a LZMA compressed data Now, if you execute `unmkinitramfs /casper/initrd new- directory` , you will see 2 directories, "early" and "main". "early" has the AuthenticAMD.bin, which means it corresponds to the first cpio. "main" is the actual initial ram disk file system, which comes from the LZMA compressed data. What I expect to see is also the GenuineIntel.bin firmware. `binwalk` says it's there, but `unmkinitramfs` is not able to extract it out. Why? I see binwalk is at version 2.1.1-16, while initramfs-tools-core (which provides unmkinitramfs) is at version 0.130ubuntu3.9. How do I extract the ubuntu 18 initramfs and get all the contents that binwalk is able to see? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1884079/+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 1650961] Re: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106
Same here on Ubuntu 20.04.2 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1650961 Title: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 Status in apport package in Ubuntu: Invalid Bug description: caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux caravena@caravena-530U3C-530U4C:~$ [12375:12409:1218/134054:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 Se creó una nueva ventana en la sesión existente del navegador. [7185:7220:1218/142107:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/142111:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7318:1218/142115:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/142117:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -105 [7185:7220:1218/143613:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/144540:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/145430:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/162533:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/162540:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -21 [7185:7318:1218/162540:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux caravena@caravena-530U3C-530U4C:~$ [18327:18362:1218/165822:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 18 17:32:53 2016 InstallationDate: Installed on 2015-07-26 (511 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to zesty on 2016-10-29 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1650961/+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 1940545] [NEW] Update Mesa to mesa-21.1.7 on Ubuntu 20.04
Public bug reported: With the recent MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa, we (NVIDIA) have added ability to GBM to dynamically load the backends. So we request to upgrade mesa libs to its latest version (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our development. ** Affects: mesa (Ubuntu) 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/1940545 Title: Update Mesa to mesa-21.1.7 on Ubuntu 20.04 Status in mesa package in Ubuntu: New Bug description: With the recent MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa, we (NVIDIA) have added ability to GBM to dynamically load the backends. So we request to upgrade mesa libs to its latest version (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04
** Description changed: With the recent MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa, - we have added ability to GBM to dynamically load the backends. So we - request to upgrade mesa libs to its latest version (mesa-21.1.7) on - Ubuntu 20.04 to use the added feature for our development. + we (NVIDIA) have added ability to GBM to dynamically load the backends. + So we request to upgrade mesa libs to its latest version (mesa-21.1.7) + on Ubuntu 20.04 to use the added feature for our development. -- 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/1940545 Title: Update Mesa to mesa-21.1.7 on Ubuntu 20.04 Status in mesa package in Ubuntu: New Bug description: With the recent MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa, we (NVIDIA) have added ability to GBM to dynamically load the backends. So we request to upgrade mesa libs to its latest version (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1939973] Re: make 4.3-4.1 triggers build failures
** Also affects: make-dfsg (Ubuntu Impish) Importance: High Status: Confirmed ** Tags removed: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1939973 Title: make 4.3-4.1 triggers build failures Status in make-dfsg package in Ubuntu: Confirmed Status in make-dfsg source package in Impish: Confirmed Bug description: trying to rebuild cross-toolchain-base from https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages triggers a build failure: [...] START stamp-dir/init-binutils tar -x -f /usr/src/binutils/binutils-2.37.tar.xz set -e; cd binutils-2.37 ; cp -a /usr/src/binutils/debian/ . ; if [ -n "$(grep -v '^\#' /<>/debian/patches/binutils/series)" ]; then QUILT_PATCHES=/<>/debian/patches/binutils quilt --quiltrc /dev/null push -a; fi; rm -rf .pc cd binutils-2.37 ; env -i CROSS_ARCHS="amd64 i386 s390x ppc64el arm64 armhf armel powerpc" debian/rules stamps/control make: dpkg-architecture: No such file or directory make: lsb_release: No such file or directory make: lsb_release: No such file or directory make: pwd: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory debian/rules:163: *** unexpected source package name: . Stop. make: *** [debian/rules:215: stamp-dir/init-binutils] Error 2 dpkg-buildpackage.pl: error: debian/rules build subprocess returned exit status 2 working around by omitting the -i option to env, or by setting PATH explicitly. Reverting to the version in the release pocket lets the c-t-b- build succeed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1939973/+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 1940528] Re: curl 7.68 does not init OpenSSL correctly
Building test package in https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4654 But also uploaded it into focal unapproved, which is currently soft frozen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1940528 Title: curl 7.68 does not init OpenSSL correctly Status in curl package in Ubuntu: Fix Released Status in curl source package in Bionic: New Status in curl source package in Focal: Confirmed Bug description: [Impact] * curl 7.68 does not correctly use OpenSSL 1.1.0+ api to init OpenSSL global state prior to executing any OpenSSL APIs. This may lead to duplicate engine initiation, which upon engine unload may cause use- after-free or double-free of any methods that engine installs. This has been fixed in curl 7.74 by correctly calling OpenSSL init api prior to any other calls to OpenSSL apis. [Test Plan] * This should be reproducible with any engines that allocate & register methods, and free them upon engine unload. Then use curl with openssl backend to test for corrupted stack. * I.e. on arm64, compile and configure pka engine from https://github.com/Mellanox/pka/commit/b0f32fa05298bf9e3997ea43fc1c11b90e0d662f (i.e. without the double-free protections proposed in https://github.com/Mellanox/pka/pull/37 ) on any arm64 hardware, there is no need for the engine to actually work or have access to anything, as the issue is reproducible when engine is enabled but cannot be effectively used. * curl any https website ... PKA_DEV: pka_dev_open_ring_vfio: error: failed to get ring 50 device name PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 3520 0 --:--:-- --:--:-- --:--:-- 3520 (exit status 0) is good output from fixed curl. Whereas: PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 1169 0 --:--:-- --:--:-- --:--:-- 1169 Segmentation fault (core dumped) (exit status non-zero) is bad output from currently broken curl. [Where problems could occur] * Correctly calling OpenSSL init function prior to any other OpenSSL apis changes the behaviour of the library slightly - specifically openssl configuration file and engines are initialised and loaded earlier, meaning that site-local customizations are applied correctly whenever using curl cli utility or libcurl4 (the openssl version of curl). This will make engine support working correctly across the board. However, if one has missconfigured openssl conf and missconfigured engines which are now actually attempted to be used one may experience unexpected behaviour changes (since potentially existing configuration was not actually taking effect). [Other Info] * References: https://github.com/curl/curl/commit/1835cb916e0d40eb8bc1165d5627a0b64f911bac https://github.com/openssl/openssl/issues/13548 https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528/+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 1928989] Re: expiring trust anchor compatibility issue
The Ubuntu Security Team is okay with publishig the xenial openssl in proposed (1.0.2g-1ubuntu4.20) to xenial-security and updates. I didn't see any symbol changes or dependency changes in the binaries that would have indicated that building against xenial-updates was a problem. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1928989 Title: expiring trust anchor compatibility issue Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Trusty: New Status in openssl source package in Xenial: Fix Committed Bug description: [Impact] * openssl fails to talk to letsencrypt website past September 2021, despite trusting the letsencrypt root certificate. [Test Plan] * Import staging cert equivalent to ISRG Root X1 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem * Import expired staging cert equivalen tto DST Root CA X3 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem * Test connectivity to the expired-root-ca test website https://expired-root-ca-test.germancoding.com setup: apt install openssl ca-certificates wget wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem cat letsencrypt-stg-root-x1.pem letsencrypt-stg-root-dst.pem >> ca.pem test case: openssl s_client -connect expired-root-ca-test.germancoding.com:443 -servername expired-root-ca-test.germancoding.com -verify 1 -verifyCAfile ca.pem bad result: connection failed verify depth is 1 CONNECTED(0003) depth=3 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Doctored Durian Root CA X3 verify error:num=10:certificate has expired notAfter=Jan 30 14:01:15 2021 GMT 140672978626200:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1264: good result: connection successful verify depth is 1 CONNECTED(0003) depth=2 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Pretend Pear X1 verify return:1 depth=1 C = US, O = (STAGING) Let's Encrypt, CN = (STAGING) Artificial Apricot R3 verify return:1 depth=0 CN = expired-root-ca-test.germancoding.com verify return:1 --- Certificate chain 0 s:/CN=expired-root-ca-test.germancoding.com i:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 1 s:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 2 s:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Doctored Durian Root CA X3 --- Server certificate -BEGIN CERTIFICATE- Connection should be successful and trusted with correctly working openssl s_client that can manage to ignore expired CA, and build a valid trust path using non-expired CA in the chain. [Testcase #2] $ sudo apt install ca-certificates wget faketime # Good connectivity $ wget -O /dev/null https://canonical.com --2021-07-13 11:54:20-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 30933 (30K) [text/html] Saving to: '/dev/null' /dev/null 100%[>] 30.21K --.-KB/sin 0.001s 2021-07-13 11:54:20 (22.3 MB/s) - '/dev/null' saved [30933/30933] # Jump to october to experience failure $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. ERROR: cannot verify canonical.com's certificate, issued by 'CN=R3,O=Let\'s Encrypt,C=US': Issued certificate has expired. To connect to canonical.com insecurely, use `--no-check-certificate'. # upgrade to new openssl, to see that connectivity is restored, even in october $ dpkg-query -W libssl1.0.0 libssl1.0.0:amd64 1.0.2g-1ubuntu4.20 $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2c, 2001:67c:1360:8001::2b, 91.189.88.180, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2c|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 30933 (30K) [text/html] Saving to: '/dev/null' /dev/null 100%[
[Touch-packages] [Bug 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04
We just got 21.0.x from Ubuntu 21.04 backported, the next one will be 21.2.x from impish after it has 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/1940545 Title: Update Mesa to mesa-21.1.7 on Ubuntu 20.04 Status in mesa package in Ubuntu: New Bug description: With the recent MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa, we (NVIDIA) have added ability to GBM to dynamically load the backends. So we request to upgrade mesa libs to its latest version (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04
Besides, 21.1.7 does not have that merge request in it, only master/21.2-branch do. -- 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/1940545 Title: Update Mesa to mesa-21.1.7 on Ubuntu 20.04 Status in mesa package in Ubuntu: New Bug description: With the recent MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa, we (NVIDIA) have added ability to GBM to dynamically load the backends. So we request to upgrade mesa libs to its latest version (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1928989] Re: expiring trust anchor compatibility issue
This bug was fixed in the package openssl - 1.0.2g-1ubuntu4.20 --- openssl (1.0.2g-1ubuntu4.20) xenial-security; urgency=medium * Enable X509_V_FLAG_TRUSTED_FIRST by default, such that letsencrypt connection with the default chain remains trusted even after the expiry of the redundant CA certificate. LP: #1928989 -- Dimitri John Ledkov Mon, 28 Jun 2021 14:05:36 +0100 ** Changed in: openssl (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1928989 Title: expiring trust anchor compatibility issue Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Trusty: New Status in openssl source package in Xenial: Fix Released Bug description: [Impact] * openssl fails to talk to letsencrypt website past September 2021, despite trusting the letsencrypt root certificate. [Test Plan] * Import staging cert equivalent to ISRG Root X1 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem * Import expired staging cert equivalen tto DST Root CA X3 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem * Test connectivity to the expired-root-ca test website https://expired-root-ca-test.germancoding.com setup: apt install openssl ca-certificates wget wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem cat letsencrypt-stg-root-x1.pem letsencrypt-stg-root-dst.pem >> ca.pem test case: openssl s_client -connect expired-root-ca-test.germancoding.com:443 -servername expired-root-ca-test.germancoding.com -verify 1 -verifyCAfile ca.pem bad result: connection failed verify depth is 1 CONNECTED(0003) depth=3 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Doctored Durian Root CA X3 verify error:num=10:certificate has expired notAfter=Jan 30 14:01:15 2021 GMT 140672978626200:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1264: good result: connection successful verify depth is 1 CONNECTED(0003) depth=2 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Pretend Pear X1 verify return:1 depth=1 C = US, O = (STAGING) Let's Encrypt, CN = (STAGING) Artificial Apricot R3 verify return:1 depth=0 CN = expired-root-ca-test.germancoding.com verify return:1 --- Certificate chain 0 s:/CN=expired-root-ca-test.germancoding.com i:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 1 s:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 2 s:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Doctored Durian Root CA X3 --- Server certificate -BEGIN CERTIFICATE- Connection should be successful and trusted with correctly working openssl s_client that can manage to ignore expired CA, and build a valid trust path using non-expired CA in the chain. [Testcase #2] $ sudo apt install ca-certificates wget faketime # Good connectivity $ wget -O /dev/null https://canonical.com --2021-07-13 11:54:20-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 30933 (30K) [text/html] Saving to: '/dev/null' /dev/null 100%[>] 30.21K --.-KB/sin 0.001s 2021-07-13 11:54:20 (22.3 MB/s) - '/dev/null' saved [30933/30933] # Jump to october to experience failure $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. ERROR: cannot verify canonical.com's certificate, issued by 'CN=R3,O=Let\'s Encrypt,C=US': Issued certificate has expired. To connect to canonical.com insecurely, use `--no-check-certificate'. # upgrade to new openssl, to see that connectivity is restored, even in october $ dpkg-query -W libssl1.0.0 libssl1.0.0:amd64 1.0.2g-1ubuntu4.20 $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2c, 2001:67c:1360:8001::2b, 91.189.88.180, ... Connecting to canonical.com (canon
[Touch-packages] [Bug 1928989] Update Released
The verification of the Stable Release Update for openssl 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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1928989 Title: expiring trust anchor compatibility issue Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Trusty: New Status in openssl source package in Xenial: Fix Released Bug description: [Impact] * openssl fails to talk to letsencrypt website past September 2021, despite trusting the letsencrypt root certificate. [Test Plan] * Import staging cert equivalent to ISRG Root X1 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem * Import expired staging cert equivalen tto DST Root CA X3 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem * Test connectivity to the expired-root-ca test website https://expired-root-ca-test.germancoding.com setup: apt install openssl ca-certificates wget wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem cat letsencrypt-stg-root-x1.pem letsencrypt-stg-root-dst.pem >> ca.pem test case: openssl s_client -connect expired-root-ca-test.germancoding.com:443 -servername expired-root-ca-test.germancoding.com -verify 1 -verifyCAfile ca.pem bad result: connection failed verify depth is 1 CONNECTED(0003) depth=3 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Doctored Durian Root CA X3 verify error:num=10:certificate has expired notAfter=Jan 30 14:01:15 2021 GMT 140672978626200:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1264: good result: connection successful verify depth is 1 CONNECTED(0003) depth=2 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Pretend Pear X1 verify return:1 depth=1 C = US, O = (STAGING) Let's Encrypt, CN = (STAGING) Artificial Apricot R3 verify return:1 depth=0 CN = expired-root-ca-test.germancoding.com verify return:1 --- Certificate chain 0 s:/CN=expired-root-ca-test.germancoding.com i:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 1 s:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 2 s:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Doctored Durian Root CA X3 --- Server certificate -BEGIN CERTIFICATE- Connection should be successful and trusted with correctly working openssl s_client that can manage to ignore expired CA, and build a valid trust path using non-expired CA in the chain. [Testcase #2] $ sudo apt install ca-certificates wget faketime # Good connectivity $ wget -O /dev/null https://canonical.com --2021-07-13 11:54:20-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 30933 (30K) [text/html] Saving to: '/dev/null' /dev/null 100%[>] 30.21K --.-KB/sin 0.001s 2021-07-13 11:54:20 (22.3 MB/s) - '/dev/null' saved [30933/30933] # Jump to october to experience failure $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. ERROR: cannot verify canonical.com's certificate, issued by 'CN=R3,O=Let\'s Encrypt,C=US': Issued certificate has expired. To connect to canonical.com insecurely, use `--no-check-certificate'. # upgrade to new openssl, to see that connectivity is restored, even in october $ dpkg-query -W libssl1.0.0 libssl1.0.0:amd64 1.0.2g-1ubuntu4.20 $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2c, 2001:67c:1360:8001::2b, 91.189.88.180, ... Connecting to canonical.com (canonical.com)|2001:67c:1
[Touch-packages] [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
** Description changed: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: - Version = TLS 1.2 (0x303) - Content Type = ApplicationData (23) - Length = 1591 - Inner Content Type = Handshake (22) - CertificateRequest, Length=1570 - request_context (len=0): - extensions, length = 1567 - extension_type=status_request(5), length=1521 - - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. - 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. - 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. - 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG + Version = TLS 1.2 (0x303) + Content Type = ApplicationData (23) + Length = 1591 + Inner Content Type = Handshake (22) + CertificateRequest, Length=1570 + request_context (len=0): + extensions, length = 1567 + extension_type=status_request(5), length=1521 + - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. + 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. + 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. + 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break - with this patch. As a non-empty reply is incorrect behavior + with this patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bu
[Touch-packages] [Bug 1935051] Re: systemd pid 1 memory leak
Can you check the systemd build in this ppa to see if it fixes the leak for you? https://launchpad.net/~ddstreet/+archive/ubuntu/systemd -- 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/1935051 Title: systemd pid 1 memory leak Status in systemd package in Ubuntu: New Bug description: Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. Environment: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: systemd: Installed: 245.4-4ubuntu3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+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 1940570] [NEW] rewrite 50-motd-news to use wget instead of curl
Public bug reported: 50-motd-news is shipped in base-files and uses curl but cannot depend on it. curl is not included by default on desktop installs. It'd be better if wget was used instead of curl to get the news from motd.ubuntu.com. This is not trivial to implement, the script uses several advanced options of curl which don't appear to have direct equivalents in wget. ** Affects: base-files (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1940570 Title: rewrite 50-motd-news to use wget instead of curl Status in base-files package in Ubuntu: New Bug description: 50-motd-news is shipped in base-files and uses curl but cannot depend on it. curl is not included by default on desktop installs. It'd be better if wget was used instead of curl to get the news from motd.ubuntu.com. This is not trivial to implement, the script uses several advanced options of curl which don't appear to have direct equivalents in wget. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1940570/+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 1921518] Re: OpenSSL "double free" error
** Also affects: openssl (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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1921518 Title: OpenSSL "double free" error Status in openssl package in Ubuntu: New Status in openssl source package in Focal: New Bug description: "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+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 1887372] Re: Cannot create lvm upon IMSM raid array
** Changed in: lvm2 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: lvm2 (Ubuntu Focal) Status: Confirmed => Incomplete ** Changed in: lvm2 (Ubuntu Hirsute) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array Status in lvm2 package in Ubuntu: Incomplete Status in lvm2 source package in Focal: Incomplete Status in lvm2 source package in Groovy: Won't Fix Status in lvm2 source package in Hirsute: Incomplete Bug description: The issue has been observed on 2.3.7 (Ubuntu 20.04). Reported to lvm team: https://bugzilla.redhat.com/show_bug.cgi?id=1855251 Steps to Reproduce: 1. Create IMSM raid array: #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G 2. Create lvm volume on raid: # pvcreate -ff -y /dev/md/vol # vgcreate group0 /dev/md/vol # lvcreate -Z y -y -l +100%FREE group0 -n lvm0 Actual results: Vg creation fails. Expected results: LVM should be able to determine the best drive and ignore duplicates. Additional info: IMSM metadata is written at the end of the drive. The first drive sector belongs to the raid volume and other metadata saved there (like lvm) can be recognized directly on raid members. The following patches should fix the issue (not verified yet): https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+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 1921518] Re: OpenSSL "double free" error
** Changed in: openssl (Ubuntu Focal) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1921518 Title: OpenSSL "double free" error Status in openssl package in Ubuntu: New Status in openssl source package in Focal: New Bug description: "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+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 1939409] Re: e2fsprogs 1.46.3-1 on architecture s390x fails in test f_baddotdir
Note that I've just released e2fsprogs 1.46.4-1 for Debian: E2fsprogs 1.46.4 (August 18, 2021) == Updates/Fixes since v1.46.3: UI and Features --- The defaults for mke2fs now call for 256 byte inodes for all file systems (with the exception of file systems for the GNU Hurd, which only supports 128 byte inodes). Creating non-Hurd file systems with 128 byte inodes will trigger a warning message to make sure users are aware of the potential problems of using small/legacy inode sizes. The bigalloc feature is now considered supported if the cluster size no more than 16 times the block size. So the mke2fs program has been changes to only warn if the cluster size is larger than that. Fixes - E2fsck now checks to make sure directory entries do not reference internal quota inodes. E2image now includes the quota inodes when creating file system image, since they are part of the file system metadata. E2fsck now properly accounts the quota usage of the project quota file. Fix a regression introduced in 1.64.3 where attempting to create a file system image using mke2fs into a non-existent file would fail. (Addresses Debian Bug: #992094) Fix mke2fs to correctly create Posix ACL's on big-endian systems when copying files from a directory hierarchy. Updated and clarified the resize2fs man pages. (Addresses Debian Bug: #979411) Performance, Internal Implementation, Development Support etc. -- Improve various regression tests to be more portable and to reflect the new default inode size of 256 byte inodes, even for small file systems. Fixed a GNU Hurd portability problem which was causing tests to fail. Fixed a test failure in f_baddotdir on big-endian systems. This wasn't necessarily a bug per se in e2fsck, but rather e2fsck having different behaviour on big-endian systems. (Addresses Debian Bug: #991922) Use WantedBy=multi-user.target in e2scrub_reap.service. (Addresses Debian Bug: #991349) Synchronize e2fsck/recovery.c with the kernel's fs/jbd2/recovery.c Fix various Coverity and compiler warnings. Fix various error pathes to make sure we don't leak resources or potentially use or try to free uninitialized pointers. Added a setup-schroot command for use on Debian porter boxes. Updated config.guess and config.sub with newer versions from the FSF. Update Czech, Dutch, French, Polish, Portuguese, and Swedish translations. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939409 Title: e2fsprogs 1.46.3-1 on architecture s390x fails in test f_baddotdir Status in e2fsprogs package in Ubuntu: In Progress Bug description: e2fsprogs 1.46.3-1ubuntu1 is in proposed. Architecture s390x fail in test f_baddotdir. The test image was changed with the new release. Next step should be analyzing the error on a s390x virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939409/+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
** Also affects: python-debian (Ubuntu)
Importance: Undecided
Status: New
--
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:
Fix Released
Status in dpkg package in Ubuntu:
Fix Released
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 python-debian 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
Status in reprepro source package in Focal:
Fix Released
Status in reprepro source package in Groovy:
Fix Released
Status in reprepro source package in Hirsute:
Fix Released
Status in debian-el package in Debian:
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&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=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
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
dh-cmake currently FTBFS [1].
While investigating the issue, I realized that, now dpkg-deb defaults to
compressing with zstd, python-debian can no longer decompress the
compressed data into the binary package archive.
I am proposing a patch for python-debian in the following MP:
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/python-
debian/+git/python-debian/+merge/407413
A PPA with the proposed fix is available at
https://launchpad.net/~athos-ribeiro/+archive/ubuntu/lp-1923845-python-
debian/+packages
[1] https://launchpadlibrarian.net/552708462/buildlog_ubuntu-impish-
amd64.dh-cmake_0.6.1_BUILDING.txt.gz
--
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:
Fix Released
Status in dpkg package in Ubuntu:
Fix Released
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 python-debian 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
Status in reprepro source package in Focal:
Fix Released
Status in reprepro source package in Groovy:
Fix Released
Status in reprepro source package in Hirsute:
Fix Released
Status in debian-el package in Debian:
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&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=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 _h
[Touch-packages] [Bug 1937087] Re: 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input)
apport information ** Tags added: apport-collected ** Description changed: Using 21.04-latest on a laptop that's main function is to listen to TV and watch videos. The laptop is constantly plugged via HDMI into a 65" LCD screen and our goal is to use the sound/speakers of the TV and not of the laptop. The problem is not only two folds but it's also random. After I did a full OS reinstall and left the settings to bare minimum(vanilla), I have selected a RANDOM screensaver as default alongside "Digital Stereo HDMI Output + analog Stereo Input" and when I play a video, sound works as expected. Also, there is no "UI defects" when selecting the hardware audio output (More on that "defect" later). So all is well. If, for example, I leave the laptop idle and the(any? still not sure about that) screensaver kicks in it will happen SOMETIMES that 1. the default hardware audio gets defaulted back to "Analog Stereo Duplex" (AKA the laptop speakers), the sound volume goes back to 100% (Because it doesn't make sense from a user's perspective when watching a movie that the sound only is set to 100%, it needs to be set to 160% or 200% for the experience to be good(note to self: maybe I should also open another bug/annoyance for that)) Also, when restoring the session and that the volume went back to 100% and that the default hardware output felt back to analog stereo duplex ON TOP of that it seems there is a UI defect (look at the picture I will be posting after this). Hope this is clear If not, thanks for letting me know. xo + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: t 947 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: MATE + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2019-11-15 (643 days ago) + InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: pulseaudio 1:14.2-1ubuntu1.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 + Tags: hirsute + Uname: Linux 5.11.0-31-generic x86_64 + UpgradeStatus: Upgraded to hirsute on 2021-05-28 (83 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/19/2017 + dmi.bios.release: 5.12 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 5.12 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: KU31 + dmi.board.vendor: Intel Corp. + dmi.board.version: RVP7 + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 9 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd07/19/2017:br5.12:svnIntelCorporation:pnKabylakePlatform:pvr0.1:rvnIntelCorp.:rnKU31:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: + dmi.product.family: Kabylake System + dmi.product.name: Kabylake Platform + dmi.product.sku: System SKUNumber + dmi.product.version: 0.1 + dmi.sys.vendor: Intel Corporation ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1937087/+attachment/5519186/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937087 Title: 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) Status in Ubuntu MATE: Invalid Status in alsa-tools package in Ubuntu: Incomplete Status in mate-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: Using 21.04-latest on a laptop that's main function is to listen to TV and watch videos. The laptop is constantly plugged via HDMI into a 65" LCD screen and our goal is to use the sound/speakers of the TV and not of the laptop. The problem is not only two folds but it's also random. After I did a full OS reinstall and left the settings to bare minimum(vanilla), I have selected a RANDOM screensaver as default alongside "Digital Stereo HDMI Output + analog Stereo Input" and when I play a video, sound works as expected. Also, there is no "UI defects" when selecting the hardware audio output (More on that "defect" later). So all is well. If, for example, I leave the laptop idle and the(any? still not sure about that) screensaver kicks in it will happen SOMETIMES that 1. the default hardware audio gets defaulted back to "Analog Stereo Duplex" (AKA the laptop speakers), the sound volume goes back to 100% (Because it doesn't make sense from a user's perspective when watching a movie that the sound only is set to 100%, it needs to be set to 160% or 200% for the experience to be good(note to self: maybe I should also open another bug/annoyance for that)) Also, when res
[Touch-packages] [Bug 1937087] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1937087/+attachment/5519187/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937087 Title: 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) Status in Ubuntu MATE: Invalid Status in alsa-tools package in Ubuntu: Incomplete Status in mate-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: Using 21.04-latest on a laptop that's main function is to listen to TV and watch videos. The laptop is constantly plugged via HDMI into a 65" LCD screen and our goal is to use the sound/speakers of the TV and not of the laptop. The problem is not only two folds but it's also random. After I did a full OS reinstall and left the settings to bare minimum(vanilla), I have selected a RANDOM screensaver as default alongside "Digital Stereo HDMI Output + analog Stereo Input" and when I play a video, sound works as expected. Also, there is no "UI defects" when selecting the hardware audio output (More on that "defect" later). So all is well. If, for example, I leave the laptop idle and the(any? still not sure about that) screensaver kicks in it will happen SOMETIMES that 1. the default hardware audio gets defaulted back to "Analog Stereo Duplex" (AKA the laptop speakers), the sound volume goes back to 100% (Because it doesn't make sense from a user's perspective when watching a movie that the sound only is set to 100%, it needs to be set to 160% or 200% for the experience to be good(note to self: maybe I should also open another bug/annoyance for that)) Also, when restoring the session and that the volume went back to 100% and that the default hardware output felt back to analog stereo duplex ON TOP of that it seems there is a UI defect (look at the picture I will be posting after this). Hope this is clear If not, thanks for letting me know. xo --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: t 947 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2019-11-15 (643 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: pulseaudio 1:14.2-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-05-28 (83 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: KU31 dmi.board.vendor: Intel Corp. dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd07/19/2017:br5.12:svnIntelCorporation:pnKabylakePlatform:pvr0.1:rvnIntelCorp.:rnKU31:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Kabylake System dmi.product.name: Kabylake Platform dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1937087/+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 1937087] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1937087/+attachment/5519188/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937087 Title: 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) Status in Ubuntu MATE: Invalid Status in alsa-tools package in Ubuntu: Incomplete Status in mate-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: Using 21.04-latest on a laptop that's main function is to listen to TV and watch videos. The laptop is constantly plugged via HDMI into a 65" LCD screen and our goal is to use the sound/speakers of the TV and not of the laptop. The problem is not only two folds but it's also random. After I did a full OS reinstall and left the settings to bare minimum(vanilla), I have selected a RANDOM screensaver as default alongside "Digital Stereo HDMI Output + analog Stereo Input" and when I play a video, sound works as expected. Also, there is no "UI defects" when selecting the hardware audio output (More on that "defect" later). So all is well. If, for example, I leave the laptop idle and the(any? still not sure about that) screensaver kicks in it will happen SOMETIMES that 1. the default hardware audio gets defaulted back to "Analog Stereo Duplex" (AKA the laptop speakers), the sound volume goes back to 100% (Because it doesn't make sense from a user's perspective when watching a movie that the sound only is set to 100%, it needs to be set to 160% or 200% for the experience to be good(note to self: maybe I should also open another bug/annoyance for that)) Also, when restoring the session and that the volume went back to 100% and that the default hardware output felt back to analog stereo duplex ON TOP of that it seems there is a UI defect (look at the picture I will be posting after this). Hope this is clear If not, thanks for letting me know. xo --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: t 947 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2019-11-15 (643 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: pulseaudio 1:14.2-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-05-28 (83 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: KU31 dmi.board.vendor: Intel Corp. dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd07/19/2017:br5.12:svnIntelCorporation:pnKabylakePlatform:pvr0.1:rvnIntelCorp.:rnKU31:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Kabylake System dmi.product.name: Kabylake Platform dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1937087/+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 1937087] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1937087/+attachment/5519189/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937087 Title: 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) Status in Ubuntu MATE: Invalid Status in alsa-tools package in Ubuntu: Incomplete Status in mate-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: Using 21.04-latest on a laptop that's main function is to listen to TV and watch videos. The laptop is constantly plugged via HDMI into a 65" LCD screen and our goal is to use the sound/speakers of the TV and not of the laptop. The problem is not only two folds but it's also random. After I did a full OS reinstall and left the settings to bare minimum(vanilla), I have selected a RANDOM screensaver as default alongside "Digital Stereo HDMI Output + analog Stereo Input" and when I play a video, sound works as expected. Also, there is no "UI defects" when selecting the hardware audio output (More on that "defect" later). So all is well. If, for example, I leave the laptop idle and the(any? still not sure about that) screensaver kicks in it will happen SOMETIMES that 1. the default hardware audio gets defaulted back to "Analog Stereo Duplex" (AKA the laptop speakers), the sound volume goes back to 100% (Because it doesn't make sense from a user's perspective when watching a movie that the sound only is set to 100%, it needs to be set to 160% or 200% for the experience to be good(note to self: maybe I should also open another bug/annoyance for that)) Also, when restoring the session and that the volume went back to 100% and that the default hardware output felt back to analog stereo duplex ON TOP of that it seems there is a UI defect (look at the picture I will be posting after this). Hope this is clear If not, thanks for letting me know. xo --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: t 947 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2019-11-15 (643 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: pulseaudio 1:14.2-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-05-28 (83 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: KU31 dmi.board.vendor: Intel Corp. dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd07/19/2017:br5.12:svnIntelCorporation:pnKabylakePlatform:pvr0.1:rvnIntelCorp.:rnKU31:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Kabylake System dmi.product.name: Kabylake Platform dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1937087/+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 1937087] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1937087/+attachment/5519190/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937087 Title: 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) Status in Ubuntu MATE: Invalid Status in alsa-tools package in Ubuntu: Incomplete Status in mate-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: Using 21.04-latest on a laptop that's main function is to listen to TV and watch videos. The laptop is constantly plugged via HDMI into a 65" LCD screen and our goal is to use the sound/speakers of the TV and not of the laptop. The problem is not only two folds but it's also random. After I did a full OS reinstall and left the settings to bare minimum(vanilla), I have selected a RANDOM screensaver as default alongside "Digital Stereo HDMI Output + analog Stereo Input" and when I play a video, sound works as expected. Also, there is no "UI defects" when selecting the hardware audio output (More on that "defect" later). So all is well. If, for example, I leave the laptop idle and the(any? still not sure about that) screensaver kicks in it will happen SOMETIMES that 1. the default hardware audio gets defaulted back to "Analog Stereo Duplex" (AKA the laptop speakers), the sound volume goes back to 100% (Because it doesn't make sense from a user's perspective when watching a movie that the sound only is set to 100%, it needs to be set to 160% or 200% for the experience to be good(note to self: maybe I should also open another bug/annoyance for that)) Also, when restoring the session and that the volume went back to 100% and that the default hardware output felt back to analog stereo duplex ON TOP of that it seems there is a UI defect (look at the picture I will be posting after this). Hope this is clear If not, thanks for letting me know. xo --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: t 947 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2019-11-15 (643 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: pulseaudio 1:14.2-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-05-28 (83 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: KU31 dmi.board.vendor: Intel Corp. dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd07/19/2017:br5.12:svnIntelCorporation:pnKabylakePlatform:pvr0.1:rvnIntelCorp.:rnKU31:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Kabylake System dmi.product.name: Kabylake Platform dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1937087/+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 1937087] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1937087/+attachment/5519191/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937087 Title: 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) Status in Ubuntu MATE: Invalid Status in alsa-tools package in Ubuntu: Incomplete Status in mate-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: Using 21.04-latest on a laptop that's main function is to listen to TV and watch videos. The laptop is constantly plugged via HDMI into a 65" LCD screen and our goal is to use the sound/speakers of the TV and not of the laptop. The problem is not only two folds but it's also random. After I did a full OS reinstall and left the settings to bare minimum(vanilla), I have selected a RANDOM screensaver as default alongside "Digital Stereo HDMI Output + analog Stereo Input" and when I play a video, sound works as expected. Also, there is no "UI defects" when selecting the hardware audio output (More on that "defect" later). So all is well. If, for example, I leave the laptop idle and the(any? still not sure about that) screensaver kicks in it will happen SOMETIMES that 1. the default hardware audio gets defaulted back to "Analog Stereo Duplex" (AKA the laptop speakers), the sound volume goes back to 100% (Because it doesn't make sense from a user's perspective when watching a movie that the sound only is set to 100%, it needs to be set to 160% or 200% for the experience to be good(note to self: maybe I should also open another bug/annoyance for that)) Also, when restoring the session and that the volume went back to 100% and that the default hardware output felt back to analog stereo duplex ON TOP of that it seems there is a UI defect (look at the picture I will be posting after this). Hope this is clear If not, thanks for letting me know. xo --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: t 947 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2019-11-15 (643 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: pulseaudio 1:14.2-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-05-28 (83 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: KU31 dmi.board.vendor: Intel Corp. dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd07/19/2017:br5.12:svnIntelCorporation:pnKabylakePlatform:pvr0.1:rvnIntelCorp.:rnKU31:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Kabylake System dmi.product.name: Kabylake Platform dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1937087/+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 1937087] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1937087/+attachment/5519192/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937087 Title: 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) Status in Ubuntu MATE: Invalid Status in alsa-tools package in Ubuntu: Incomplete Status in mate-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: Using 21.04-latest on a laptop that's main function is to listen to TV and watch videos. The laptop is constantly plugged via HDMI into a 65" LCD screen and our goal is to use the sound/speakers of the TV and not of the laptop. The problem is not only two folds but it's also random. After I did a full OS reinstall and left the settings to bare minimum(vanilla), I have selected a RANDOM screensaver as default alongside "Digital Stereo HDMI Output + analog Stereo Input" and when I play a video, sound works as expected. Also, there is no "UI defects" when selecting the hardware audio output (More on that "defect" later). So all is well. If, for example, I leave the laptop idle and the(any? still not sure about that) screensaver kicks in it will happen SOMETIMES that 1. the default hardware audio gets defaulted back to "Analog Stereo Duplex" (AKA the laptop speakers), the sound volume goes back to 100% (Because it doesn't make sense from a user's perspective when watching a movie that the sound only is set to 100%, it needs to be set to 160% or 200% for the experience to be good(note to self: maybe I should also open another bug/annoyance for that)) Also, when restoring the session and that the volume went back to 100% and that the default hardware output felt back to analog stereo duplex ON TOP of that it seems there is a UI defect (look at the picture I will be posting after this). Hope this is clear If not, thanks for letting me know. xo --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: t 947 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2019-11-15 (643 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: pulseaudio 1:14.2-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-05-28 (83 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: KU31 dmi.board.vendor: Intel Corp. dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd07/19/2017:br5.12:svnIntelCorporation:pnKabylakePlatform:pvr0.1:rvnIntelCorp.:rnKU31:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Kabylake System dmi.product.name: Kabylake Platform dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1937087/+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 1937087] Re: 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input)
** Changed in: alsa-tools (Ubuntu) Status: Incomplete => New ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New ** No longer affects: mate-control-center (Ubuntu) ** Project changed: ubuntu-mate => ubuntu ** No longer affects: ubuntu -- 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/1937087 Title: 21.04 - Sound issues (Analog Stereo Duplex VS Digital Stereo (HDMI) Output + analog stereo input) Status in alsa-tools package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Using 21.04-latest on a laptop that's main function is to listen to TV and watch videos. The laptop is constantly plugged via HDMI into a 65" LCD screen and our goal is to use the sound/speakers of the TV and not of the laptop. The problem is not only two folds but it's also random. After I did a full OS reinstall and left the settings to bare minimum(vanilla), I have selected a RANDOM screensaver as default alongside "Digital Stereo HDMI Output + analog Stereo Input" and when I play a video, sound works as expected. Also, there is no "UI defects" when selecting the hardware audio output (More on that "defect" later). So all is well. If, for example, I leave the laptop idle and the(any? still not sure about that) screensaver kicks in it will happen SOMETIMES that 1. the default hardware audio gets defaulted back to "Analog Stereo Duplex" (AKA the laptop speakers), the sound volume goes back to 100% (Because it doesn't make sense from a user's perspective when watching a movie that the sound only is set to 100%, it needs to be set to 160% or 200% for the experience to be good(note to self: maybe I should also open another bug/annoyance for that)) Also, when restoring the session and that the volume went back to 100% and that the default hardware output felt back to analog stereo duplex ON TOP of that it seems there is a UI defect (look at the picture I will be posting after this). Hope this is clear If not, thanks for letting me know. xo --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: t 947 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2019-11-15 (643 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: pulseaudio 1:14.2-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Tags: hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-05-28 (83 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: KU31 dmi.board.vendor: Intel Corp. dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd07/19/2017:br5.12:svnIntelCorporation:pnKabylakePlatform:pvr0.1:rvnIntelCorp.:rnKU31:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Kabylake System dmi.product.name: Kabylake Platform dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-tools/+bug/1937087/+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 crashed with SIGABRT when under memory pressure
@Daniel @Timo,
I fund the root cause of my X crash issue, which is not same as this bug.
Please ignore my comments and thanks for your response.
--
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 crashed with SIGABRT when under memory pressure
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Released
Status in mesa source package in Hirsute:
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/oem-priority/+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 1940597] [NEW] [ATH-SR30BT] Bluetooth headset disconnected after auto-connected
You have been subscribed to a public bug: I've paired the headset with Ubuntu. On the other day when I turn the headset on, I can see it is auto-connected in the bluetooth devices list. However, a second (or less) later, it is disconnected. I need to connect it manually to make it connected again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fikr4n 1860 F pulseaudio /dev/snd/controlC0: fikr4n 1860 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 20 09:16:51 2021 InstallationDate: Installed on 2021-06-05 (75 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ATH-SR30BT Symptom_Type: None of the above Title: [ATH-SR30BT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 15.5 dmi.bios.vendor: AMI dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 878E dmi.board.vendor: HP dmi.board.version: 18.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 18.32 dmi.modalias: dmi:bvnAMI:bvrF.05:bd12/29/2020:br15.5:efr18.32:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP ENVY dmi.product.name: HP ENVY Laptop 15-ep0xxx dmi.product.sku: 16P91PA#AR6 dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [ATH-SR30BT] Bluetooth headset disconnected after auto-connected https://bugs.launchpad.net/bugs/1940597 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940545] Re: Update Mesa to mesa-21.1.7 on Ubuntu 20.04
Will that be updated only on impish (21.10) ? Actually we need the update on focal (20.04). -- 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/1940545 Title: Update Mesa to mesa-21.1.7 on Ubuntu 20.04 Status in mesa package in Ubuntu: New Bug description: With the recent MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 to Mesa, we (NVIDIA) have added ability to GBM to dynamically load the backends. So we request to upgrade mesa libs to its latest version (mesa-21.1.7) on Ubuntu 20.04 to use the added feature for our development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1940545/+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 1940597] Re: [ATH-SR30BT] Bluetooth headset disconnected after auto-connected
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1940597 Title: [ATH-SR30BT] Bluetooth headset disconnected after auto-connected Status in alsa-driver package in Ubuntu: New Bug description: I've paired the headset with Ubuntu. On the other day when I turn the headset on, I can see it is auto-connected in the bluetooth devices list. However, a second (or less) later, it is disconnected. I need to connect it manually to make it connected again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fikr4n 1860 F pulseaudio /dev/snd/controlC0: fikr4n 1860 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 20 09:16:51 2021 InstallationDate: Installed on 2021-06-05 (75 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ATH-SR30BT Symptom_Type: None of the above Title: [ATH-SR30BT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 15.5 dmi.bios.vendor: AMI dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 878E dmi.board.vendor: HP dmi.board.version: 18.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 18.32 dmi.modalias: dmi:bvnAMI:bvrF.05:bd12/29/2020:br15.5:efr18.32:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP ENVY dmi.product.name: HP ENVY Laptop 15-ep0xxx dmi.product.sku: 16P91PA#AR6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1940597/+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 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
@Gabriel Because this modem passed the test using Focal, can you help to test the following cases for comparison? (1) Using Hirsute The ModemManager is replaced from the -proposed channel The default kernel in Hirsute is replaced with Focal’s kernel (2) Using Focal The ModemManager is replaced from the -proposed channel The default kernel in Focal is replaced with Hirsute’s kernel If (1) passed, no need to test (2) -- 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/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in network-manager package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True 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/1940377/+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 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
@Jerry-lee-tpe, Following your steps: Hirsute is installed on L460 , the kernel is replaced with Focal's kernel (5.8.0-63-generic) (1) is passed. The initial kernel of Hirsute is 5.11.0-16-generic, the issue reproduces; Upgrade kernel to 5.11.0-31-generic, the issue reproduces. -- 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/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in network-manager package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True 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/1940377/+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 1940481] Re: dhclient.conf should set send DHCPv6 host-name option
** Description changed: Despite the fix in 2012 (bug #991360) the default configuration shipped - with isb-dhcp-client /etc/dhclient.conf in 2021 still does not set the - DHCPv6 hostname option by default. All it needs is: + with isb-dhcp-client /etc/dhcp/dhclient.conf in 2021 still does not set + the DHCPv6 hostname option by default. All it needs is: # send host-name with DHCPv6 not just DHCPv4 send fqdn.fqdn = gethostname(); Without this option it causes dhcpy6d's dynamic DNS update (to bind9) to fail because the hostname is empty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1940481 Title: dhclient.conf should set send DHCPv6 host-name option Status in isc-dhcp package in Ubuntu: New Bug description: Despite the fix in 2012 (bug #991360) the default configuration shipped with isb-dhcp-client /etc/dhcp/dhclient.conf in 2021 still does not set the DHCPv6 hostname option by default. All it needs is: # send host-name with DHCPv6 not just DHCPv4 send fqdn.fqdn = gethostname(); Without this option it causes dhcpy6d's dynamic DNS update (to bind9) to fail because the hostname is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1940481/+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
