[Touch-packages] [Bug 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
This probably would hide all such shutdown crashes though:
https://salsa.debian.org/gnome-team/gnome-shell/-/merge_requests/63
--
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/1994010
Title:
gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
mozilla::detail::IntrinsicMemoryOps::load()
Status in gjs package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mozjs102 package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
__b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
priv =
cx = 0x561efe351c00
js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+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 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
It's not fixed in lunar either. We're now seeing reports:
https://errors.ubuntu.com/?release=Ubuntu%2023.04=gnome-
shell=week
** Tags added: lunar
--
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/1994010
Title:
gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
mozilla::detail::IntrinsicMemoryOps::load()
Status in gjs package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mozjs102 package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
__b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
priv =
cx = 0x561efe351c00
js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+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 2007217] Re: error from xdiagnose application
I'm not seeing any problems in the attached files. If the main issue is not with Ubuntu but with Skype then please report that to Skype/Microsoft. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2007217 Title: error from xdiagnose application Status in Ubuntu: Incomplete Bug description: i have some problem run the skype application so i run the xdiagnose application and show this errors so i don't know what mean thanks in advance ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-202.213-generic 4.15.18 Uname: Linux 4.15.0-202-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.28 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Feb 14 08:14:11 2023 DistUpgraded: 2023-01-07 20:49:41,429 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1179:fdc0] Subsystem: Toshiba America Info Systems Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1179:fdc0] InstallationDate: Installed on 2022-12-15 (60 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: TOSHIBA TOSHIBA NB500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-202-generic root=UUID=4e71438a-25ca-4b55-96a3-d60c7e8b980d ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2023-01-07 (37 days ago) dmi.bios.date: 12/21/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.40 dmi.board.name: PBU00 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.40:bd12/21/2010:svnTOSHIBA:pnTOSHIBANB500:pvrPLL50H-00401X:rvnTOSHIBA:rnPBU00:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB500 dmi.product.version: PLL50H-00401X dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.13 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jan 7 18:33:56 2023 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 661 vendor LGD xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2007217/+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 2007268] Re: Wayland/Gnome doesn't DPMS screens on idle/screensaver wasting energy and burning LEDs
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2003237, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: wayland (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 2003237 Monitor does not turn off after idle timeout is reached -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2007268 Title: Wayland/Gnome doesn't DPMS screens on idle/screensaver wasting energy and burning LEDs Status in mutter package in Ubuntu: New Bug description: In the 2022/2023 energy crisis era, this shall not happen. But... I haven't found solution other than "switch to X", which is not an options with my scaling settings for both 4K screens I'm using. On idle when the system blanks screen backlight remains on, wasting energy and burning LEDs in my screens. Please provide solution that would let Gnome set DPMS properly and actually send screens to proper sleep when OS goes idle (enables screen saver). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwayland-bin 1.20.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 11:59:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-58-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-60-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev d1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2023-01-04 (40 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zrhf1w@/vmlinuz-5.15.0-58-generic root=ZFS=rpool/ROOT/ubuntu_zrhf1w ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.23:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2007268/+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 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
** Tags added: oem-priority originate-from-1998757 stella -- 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/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Confirmed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Confirmed Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+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 2006517] Re: Bluetooth works on desktop but not on ubuntu core
Are you sure the function is lost? Looks like the Adv Monitor is running even the features callback returns an invalid value. Feb 07 23:50:34 ubuntu bluetoothd[1562]: src/advertising.c:read_adv_features_callback() Failed to read advertising features: Not Supported (0x0c) Feb 07 23:50:34 ubuntu bluetoothd[1562]: Adv Monitor Manager created with supported features:0x0001, enabled features:0x0001, max number of supported monitors:32, max number of supported patterns:16 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+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 2007331] [NEW] Fix HFP mSBC support on Realtek Bluetooth USB controller
Public bug reported: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: pulseaudio (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Affects: pulseaudio (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: pulseaudio (Ubuntu Kinetic) Importance: Medium Status: Confirmed ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: pulseaudio (Ubuntu Lunar) Importance: Medium Status: Confirmed ** Package changed: linux (Ubuntu) => linux-oem-6.1 (Ubuntu) ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Low => Medium ** Also affects: pulseaudio (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: pulseaudio (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu Jammy) Status: New => Confirmed ** Changed in: pulseaudio (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu Kinetic) Status: New => Confirmed ** Changed in: pulseaudio (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu Lunar) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Confirmed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Confirmed Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until
[Touch-packages] [Bug 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
I also don't have sound from my internal speakers on HP Envy x360 15-ew0023dx, but I can play audio from headphone jack, HDMI, or bluetooth. I've tried Ubuntu 22.04 and 22.10, linux kernel 5.15, 5.19.17, and 6.1.11, none fixed it. -- 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/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 2006756] Re: composite emoji shows extra vertical color lines
Mateusz, if you have tested this package, please also leave a comment mentioning what version you have tested and what testing you have done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 source package in Jammy: Fix Committed Bug description: Impact -- Composite emoji (such as [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- This is a one line fix cherry-picked from pango 1.50.8 (plus 30+ lines for a test case). pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+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 1992178] Re: autopkgtest: upstream tests that run in qemu hang on ppc64el
Backtraces are on the upstream bug, eg: https://github.com/systemd/systemd/issues/25091#issuecomment-1401824195 https://github.com/systemd/systemd/issues/25091#issuecomment-1402425787 It would be better if the IBM developers could engage directly on the upstream ticket for the initial investigation, given the information is recorded there. Thanks! -- 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/1992178 Title: autopkgtest: upstream tests that run in qemu hang on ppc64el Status in systemd: Unknown Status in The Ubuntu-power-systems project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Bug description: I believe this started early in the kinetic cycle, cf. https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el. Timeouts in the upstream tests have been an issue for a while, but kinetic on ppc64el consistently times out with upstream tests that run in QEMU. Skipping individual tests does not help, because *which* tests time out appears to change with each build. For example, in 251.4-1ubuntu4 the TEST-36-NUMAPOLICY test was consistently the culprit, but now in 251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out. I have not been able to identify a root cause for this, but it seems that running tests in QEMU is very fragile on ppc64el, where as the tests that run in nspawn are more consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1992178/+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 1992178] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2023-02-14 17:28 EDT--- Howdy. Adding developers from KVM on Power and Toolchain to our bug but it would be good to understand exactly what IBM needs to look at. For example, you mention a backtrace you see but I don't see that in the bug. Any details you can provide are appreciated. -- 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/1992178 Title: autopkgtest: upstream tests that run in qemu hang on ppc64el Status in systemd: Unknown Status in The Ubuntu-power-systems project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Bug description: I believe this started early in the kinetic cycle, cf. https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el. Timeouts in the upstream tests have been an issue for a while, but kinetic on ppc64el consistently times out with upstream tests that run in QEMU. Skipping individual tests does not help, because *which* tests time out appears to change with each build. For example, in 251.4-1ubuntu4 the TEST-36-NUMAPOLICY test was consistently the culprit, but now in 251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out. I have not been able to identify a root cause for this, but it seems that running tests in QEMU is very fragile on ppc64el, where as the tests that run in nspawn are more consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1992178/+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 2007317] [NEW] PCI/internal sound card not detected
Public bug reported: After updating Ubuntu 22.04.1 LTS from kernel 5.15.0-58 to 5.15.0-60 all audio in and out was lost. Using grub to boot to the previous kernel (5.15.0-58) restored proper audio functionality. So the problem appears to be associated with the new kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:rreed 1481 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 17:07:09 2023 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to jammy on 2022-06-27 (232 days ago) dmi.bios.date: 09/18/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd09/18/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2007317 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: After updating Ubuntu 22.04.1 LTS from kernel 5.15.0-58 to 5.15.0-60 all audio in and out was lost. Using grub to boot to the previous kernel (5.15.0-58) restored proper audio functionality. So the problem appears to be associated with the new kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:rreed 1481 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 17:07:09 2023 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to jammy on 2022-06-27 (232 days ago) dmi.bios.date: 09/18/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd09/18/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007317/+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 2007050] Re: Microsoft Surface keyboard not available during initrd
Thanks to oerheks for pointing me to a related (though AMD there) report at https://github.com/linux-surface/linux-surface/issues/839#issuecomment-1140287888 Placing the following in /etc/initramfs-tools/modules #-- Starts here -- surface_hid_core surface_hid surface_aggregator_registry surface_aggregator pinctrl_tigerlake 8250_dw #-- Ends here -- then running sudo update-initramfs -c -k $(uname -r) and finally rebooting works around it for me. It appears that whatever detects the modules to be included in the (default) "MOST" set when generating an initrd will need updating. (It may be possible to reduce the above list of modules to specifically include in the initrd can be reduced, yet - let me know if you want me to work this out.) ** Bug watch added: github.com/linux-surface/linux-surface/issues #839 https://github.com/linux-surface/linux-surface/issues/839 ** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu) ** Summary changed: - Microsoft Surface keyboard not available during initrd + Check for Microsoft Surface keyboard modules when generating initrd -- 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/2007050 Title: Check for Microsoft Surface keyboard modules when generating initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1
[Touch-packages] [Bug 2007050] [NEW] Microsoft Surface keyboard not available during initrd
You have been subscribed to a public bug: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1 linux-base 4.5ubuntu9 linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1 logsave 1.46.5-2ubuntu1.1 lsb-base 11.1.0ubuntu4 mount 2.37.2-4ubuntu3 openssl 3.0.2-0ubuntu1.8 os-prober 1.79ubuntu2 passwd 1:4.8.1-2ubuntu2.1 perl-base 5.34.0-3ubuntu1.1 sensible-utils 0.0.17 systemd-hwe-hwdb 249.11.2 tar 1.34+dfsg-1build3 ubuntu-keyring 2021.03.26 ucf 3.0043 udev 249.11-0ubuntu3.6 util-linux 2.37.2-4ubuntu3 uuid-runtime 2.37.2-4ubuntu3 zlib1g 1:1.2.11.dfsg-2ubuntu9.2 zstd 1.4.8+dfsg-3build1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-12 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: linux-image-5.19.0-28-generic 5.19.0-28.29~22.04.1 PackageArchitecture: amd64 ProcCpuinfoMinimal: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 140 model name : 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz stepping : 1 microcode : 0xa4 cpu MHz: 4643.410 cache size : 12288 KB physical id: 0 siblings : 8 core id: 3 cpu cores : 4 apicid : 7 initial apicid : 7 fpu: yes fpu_exception : yes cpuid level: 27 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid
[Touch-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
@Daniel, Those denials should be resolved by this PR (https://github.com/snapcore/snapd/pull/12496). The problem is if we run this snap in devmode, skipping over apparmor entirely, the root problem still exists. Namely, bluetooth does not function on the device. With the relevant interface changes made and the snap installed fully confined on the two devices Alex mentions above, the snap in question works fine. This indicates to me that this is more a problem with something in the pc-kernel snap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+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 2007286] Re: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed
There can be many reasons why files remain. Did you purge the packages for those Linux versions? Did you do any dkms modules. This is not a bug in apt, apt is not responsible for those files. ** Changed in: apt (Ubuntu) Status: New => Invalid ** Package changed: apt (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Invalid => 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/2007286 Title: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed Status in linux package in Ubuntu: Incomplete Bug description: corrado@corrado-x-kinetic:~$ ls /lib/modules 5.19.0-23-generic 5.19.0-28-generic 5.19.0-29-generic 5.19.0-31-generic corrado@corrado-x-kinetic:~$ ls /boot config-5.19.0-29-generic memtest86+.elf config-5.19.0-31-generic memtest86+_multiboot.bin efi System.map-5.19.0-29-generic grub System.map-5.19.0-31-generic initrd.imgvmlinuz initrd.img-5.19.0-29-generic vmlinuz-5.19.0-29-generic initrd.img-5.19.0-31-generic vmlinuz-5.19.0-31-generic initrd.img.oldvmlinuz.old memtest86+.bin corrado@corrado-x-kinetic:~$ see also https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apt 2.5.3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 16:23:49 2023 InstallationDate: Installed on 2022-11-28 (77 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007286/+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 2006756] Re: composite emoji shows extra vertical color lines
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 source package in Jammy: Fix Committed Bug description: Impact -- Composite emoji (such as [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- This is a one line fix cherry-picked from pango 1.50.8 (plus 30+ lines for a test case). pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+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 2007286] Re: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed
This is reproducible on both Ubuntu 20.04 and 22.04 Server, on both AMD64 and ARM64 (Raspberry Pi). For AMD64 (Intel): $ ls -l /lib/modules/5.4.0-xx-generic -rw-r--r-- 1 root 143K 2022-04-28 18:36 modules.alias -rw-r--r-- 1 root 154K 2022-04-28 18:36 modules.alias.bin -rw-r--r-- 1 root 8.0K 2022-04-08 10:44 modules.builtin -rw-r--r-- 1 root 25K 2022-04-28 18:36 modules.builtin.alias.bin -rw-r--r-- 1 root 11K 2022-04-28 18:36 modules.builtin.bin -rw-r--r-- 1 root 63K 2022-04-08 10:44 modules.builtin.modinfo -rw-r--r-- 1 root 85K 2022-04-28 18:36 modules.dep -rw-r--r-- 1 root 123K 2022-04-28 18:36 modules.dep.bin -rw-r--r-- 1 root 268 2022-04-28 18:36 modules.devname -rw-r--r-- 1 root 215K 2022-04-08 10:44 modules.order -rw-r--r-- 1 root 489 2022-04-28 18:36 modules.softdep -rw-r--r-- 1 root 279K 2022-04-28 18:36 modules.symbols -rw-r--r-- 1 root 326K 2022-04-28 18:36 modules.symbols.bin For ARM64 (RasPi): $ ls -l /lib/modules/5.4.0--raspi -rw-r--r-- 1 root 859K 2022-04-25 17:31 modules.alias -rw-r--r-- 1 root 893K 2022-04-25 17:31 modules.alias.bin -rw-r--r-- 1 root 11K 2022-04-04 13:33 modules.builtin -rw-r--r-- 1 root 27K 2022-04-25 17:31 modules.builtin.alias.bin -rw-r--r-- 1 root 14K 2022-04-25 17:31 modules.builtin.bin -rw-r--r-- 1 root 84K 2022-04-04 13:33 modules.builtin.modinfo -rw-r--r-- 1 root 399K 2022-04-25 17:31 modules.dep -rw-r--r-- 1 root 548K 2022-04-25 17:31 modules.dep.bin -rw-r--r-- 1 root 250 2022-04-25 17:31 modules.devname -rw-r--r-- 1 root 209K 2022-04-04 13:33 modules.order -rw-r--r-- 1 root 950 2022-04-25 17:31 modules.softdep -rw-r--r-- 1 root 354K 2022-04-25 17:31 modules.symbols -rw-r--r-- 1 root 425K 2022-04-25 17:31 modules.symbols.bin -- 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/2007286 Title: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed Status in apt package in Ubuntu: New Bug description: corrado@corrado-x-kinetic:~$ ls /lib/modules 5.19.0-23-generic 5.19.0-28-generic 5.19.0-29-generic 5.19.0-31-generic corrado@corrado-x-kinetic:~$ ls /boot config-5.19.0-29-generic memtest86+.elf config-5.19.0-31-generic memtest86+_multiboot.bin efi System.map-5.19.0-29-generic grub System.map-5.19.0-31-generic initrd.imgvmlinuz initrd.img-5.19.0-29-generic vmlinuz-5.19.0-29-generic initrd.img-5.19.0-31-generic vmlinuz-5.19.0-31-generic initrd.img.oldvmlinuz.old memtest86+.bin corrado@corrado-x-kinetic:~$ see also https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apt 2.5.3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 16:23:49 2023 InstallationDate: Installed on 2022-11-28 (77 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2007286/+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 2007286] [NEW] Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed
Public bug reported: corrado@corrado-x-kinetic:~$ ls /lib/modules 5.19.0-23-generic 5.19.0-28-generic 5.19.0-29-generic 5.19.0-31-generic corrado@corrado-x-kinetic:~$ ls /boot config-5.19.0-29-generic memtest86+.elf config-5.19.0-31-generic memtest86+_multiboot.bin efi System.map-5.19.0-29-generic grub System.map-5.19.0-31-generic initrd.imgvmlinuz initrd.img-5.19.0-29-generic vmlinuz-5.19.0-29-generic initrd.img-5.19.0-31-generic vmlinuz-5.19.0-31-generic initrd.img.oldvmlinuz.old memtest86+.bin corrado@corrado-x-kinetic:~$ see also https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apt 2.5.3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 16:23:49 2023 InstallationDate: Installed on 2022-11-28 (77 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/2007286 Title: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed Status in apt package in Ubuntu: New Bug description: corrado@corrado-x-kinetic:~$ ls /lib/modules 5.19.0-23-generic 5.19.0-28-generic 5.19.0-29-generic 5.19.0-31-generic corrado@corrado-x-kinetic:~$ ls /boot config-5.19.0-29-generic memtest86+.elf config-5.19.0-31-generic memtest86+_multiboot.bin efi System.map-5.19.0-29-generic grub System.map-5.19.0-31-generic initrd.imgvmlinuz initrd.img-5.19.0-29-generic vmlinuz-5.19.0-29-generic initrd.img-5.19.0-31-generic vmlinuz-5.19.0-31-generic initrd.img.oldvmlinuz.old memtest86+.bin corrado@corrado-x-kinetic:~$ see also https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apt 2.5.3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 16:23:49 2023 InstallationDate: Installed on 2022-11-28 (77 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2007286/+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 1992178] Re: autopkgtest: upstream tests that run in qemu hang on ppc64el
** Tags added: architecture-ppc64le bugnameltc-201628 severity-medium targetmilestone-inin--- -- 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/1992178 Title: autopkgtest: upstream tests that run in qemu hang on ppc64el Status in systemd: Unknown Status in The Ubuntu-power-systems project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Bug description: I believe this started early in the kinetic cycle, cf. https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el. Timeouts in the upstream tests have been an issue for a while, but kinetic on ppc64el consistently times out with upstream tests that run in QEMU. Skipping individual tests does not help, because *which* tests time out appears to change with each build. For example, in 251.4-1ubuntu4 the TEST-36-NUMAPOLICY test was consistently the culprit, but now in 251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out. I have not been able to identify a root cause for this, but it seems that running tests in QEMU is very fragile on ppc64el, where as the tests that run in nspawn are more consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1992178/+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 2007217] Re: error from xdiagnose application
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2007217 Title: error from xdiagnose application Status in xorg package in Ubuntu: New Bug description: i have some problem run the skype application so i run the xdiagnose application and show this errors so i don't know what mean thanks in advance ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-202.213-generic 4.15.18 Uname: Linux 4.15.0-202-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.28 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Feb 14 08:14:11 2023 DistUpgraded: 2023-01-07 20:49:41,429 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1179:fdc0] Subsystem: Toshiba America Info Systems Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1179:fdc0] InstallationDate: Installed on 2022-12-15 (60 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: TOSHIBA TOSHIBA NB500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-202-generic root=UUID=4e71438a-25ca-4b55-96a3-d60c7e8b980d ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2023-01-07 (37 days ago) dmi.bios.date: 12/21/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.40 dmi.board.name: PBU00 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.40:bd12/21/2010:svnTOSHIBA:pnTOSHIBANB500:pvrPLL50H-00401X:rvnTOSHIBA:rnPBU00:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB500 dmi.product.version: PLL50H-00401X dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.13 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jan 7 18:33:56 2023 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 661 vendor LGD xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2007217/+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 2007274] Re: I have ubuntu 22.04 on my system and have the following vulnerability : CVE-2022-46908. On which release/path of Ubuntu can I expect them to be fixed ?
Thanks for taking the time to report this bug and helping to make Ubuntu better. This is low priority CVE for us, it will only get patched if a higher priority CVE for sqlite3 in 22.04 shows up. Right now there are none, therefore no ETA. ** Description changed: I have ubuntu 22.04 on my system and it has the following vulnerability : CVE-2022-46908. Here is the link to the Ubuntu CVE link : - https://ubuntu.com/security/CVE-2022-46908#:~:text=SQLite%20through%203.40.,UDF%20functions%20such%20as%20WRITEFILE. - On which version/patch of Ubuntu can I expect this to get fixed ? + https://ubuntu.com/security/CVE-2022-46908. On which version/patch of + Ubuntu can I expect this to get fixed ? ** Information type changed from Private Security to Public Security ** Changed in: sqlite3 (Ubuntu) Status: New => Confirmed -- 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/2007274 Title: I have ubuntu 22.04 on my system and have the following vulnerability : CVE-2022-46908. On which release/path of Ubuntu can I expect them to be fixed ? Status in sqlite3 package in Ubuntu: Confirmed Bug description: I have ubuntu 22.04 on my system and it has the following vulnerability : CVE-2022-46908. Here is the link to the Ubuntu CVE link : https://ubuntu.com/security/CVE-2022-46908. On which version/patch of Ubuntu can I expect this to get fixed ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/2007274/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
** Tags removed: sru-2023-01-30 ** Tags added: sru-20230130 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Triaged Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
** Tags added: sru-2023-01-30 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Triaged Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+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 2007268] [NEW] Wayland/Gnome doesn't DPMS screens on idle/screensaver wasting energy and burning LEDs
Public bug reported: In the 2022/2023 energy crisis era, this shall not happen. But... I haven't found solution other than "switch to X", which is not an options with my scaling settings for both 4K screens I'm using. On idle when the system blanks screen backlight remains on, wasting energy and burning LEDs in my screens. Please provide solution that would let Gnome set DPMS properly and actually send screens to proper sleep when OS goes idle (enables screen saver). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwayland-bin 1.20.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 11:59:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-58-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-60-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev d1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2023-01-04 (40 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zrhf1w@/vmlinuz-5.15.0-58-generic root=ZFS=rpool/ROOT/ubuntu_zrhf1w ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.23:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2007268 Title: Wayland/Gnome doesn't DPMS screens on idle/screensaver wasting energy and burning LEDs Status in wayland package in Ubuntu: New Bug description: In the 2022/2023 energy crisis era, this shall not happen. But... I haven't found solution other than "switch to X", which is not an options with my scaling settings for both 4K screens I'm using. On idle when the system blanks screen backlight remains on, wasting energy and burning LEDs in my screens. Please provide solution that would let Gnome set DPMS properly and actually send screens to proper sleep when OS goes idle (enables screen saver). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwayland-bin 1.20.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 11:59:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-58-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-60-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev d1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2023-01-04 (40 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO
[Touch-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
After taking another look at this I noticed that the function where we create the Netplan YAML is called when the connection is created AND when the connection is going down as though it was being updated. The first time it's called the parameters is_volatile, is_nm_generated and is_external are all set to true so we skip the libnetplan calls. Although when it's called when the connection is going down they are all false. And that's when the Netplan file is created and network-manager gets to a point in the code it shouldn't reach, so it crashes and the files are never removed. Not sure if calling the plugin writer in this case is a bug or not as the connection is volatile and is going to be deleted anyway. Maybe lost tracking of the connection nature (volatile, nm_generated and external) is the actual bug, not sure yet. One way to work around this is generating Netplan YAMLs regardless if the connection is volatile. If network-manager will create a file for it we could create a file for Netplan too. In fact, after removing the conditions to call libnetplan, the files are created and deleted when the OpenVPN client and/or server is stopped. Note that from network-manager 1.42.0 on, even the loopback interface can be represented as a connection, so we will have a Netplan file for it as well. -- 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/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: *** Note: This bug is mostly about comment #10, now *** When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+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 2007264] Re: I have ubuntu 22.04 on my system and have the following vulnerabilities . On which release/path of Ubuntu can I expect them to be fixed
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3715 ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/2007264 Title: I have ubuntu 22.04 on my system and have the following vulnerabilities . On which release/path of Ubuntu can I expect them to be fixed Status in bash package in Ubuntu: New Bug description: I have ubuntu 22.04 on my system and it has the following vulnerability : CVE-2022-3715 . Here is the link to the Ubuntu CVE link : https://ubuntu.com/security/CVE-2022-3715. On which version/patch of Ubuntu can I expect this to get fixed ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2007264/+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 2007264] [NEW] I have ubuntu 22.04 on my system and have the following vulnerabilities . On which release/path of Ubuntu can I expect them to be fixed
Public bug reported: I have ubuntu 22.04 on my system and it has the following vulnerability : CVE-2022-3715 . Here is the link to the Ubuntu CVE link : https://ubuntu.com/security/CVE-2022-3715. On which version/patch of Ubuntu can I expect this to get fixed ? ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/2007264 Title: I have ubuntu 22.04 on my system and have the following vulnerabilities . On which release/path of Ubuntu can I expect them to be fixed Status in bash package in Ubuntu: New Bug description: I have ubuntu 22.04 on my system and it has the following vulnerability : CVE-2022-3715 . Here is the link to the Ubuntu CVE link : https://ubuntu.com/security/CVE-2022-3715. On which version/patch of Ubuntu can I expect this to get fixed ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2007264/+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
