[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
** Changed in: oem-priority Assignee: Andy Chi (andch) => jeremyszu (os369510) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in OEM Priority Project: In Progress Status in Provider for Plainbox - Checkbox: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: == SRU Justification == [Impact] When the system is under memory pressure, the entire desktop session may crash. [Fix] Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory") [Test] Run memory stress and the session crashed in less than 5 minutes. With the fix applied, run memory stress for 24 hours and the desktop session is still alive. [Where problems could occur] Doing a reset might make the system even more sluggish when under memory pressure. == Original bug report == I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/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 1929833] Re: bluez: meshctl missing
** Changed in: bluez (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1929833 Title: bluez: meshctl missing Status in bluez package in Ubuntu: Fix Committed Status in bluez package in Debian: Fix Released Bug description: bluez has added a new tool for BT mesh handling. Debian has a new binary package: https://packages.debian.org/bullseye /bluez-meshd Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1907886] Re: avinfo is missing
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1907886 Title: avinfo is missing Status in bluez package in Ubuntu: Fix Committed Bug description: The "avinfo" command line tools available in bluez/tools (https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools) is not available in the package. The package bluez-tools (https://packages.ubuntu.com/groovy/bluez- tools) seems to map another project external to bluez (https://github.com/khvzak/bluez-tools) and not the "tools" folder of bluez. "avinfo" is used for example in order to check which codecs are supported by a headphone set (see https://github.com/EHfive /pulseaudio-modules-bt/issues/31#issuecomment-462717049). Maybe have "bluez-tools" map the "tools" folder of bluez, and move the other project to another package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1907886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Changed in: bluez (Ubuntu Impish) Status: In Progress => Fix Committed -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) 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 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1929833] Re: bluez: meshctl missing
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed ** Bug watch added: Debian Bug tracker #973579 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 ** Also affects: bluez (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1929833 Title: bluez: meshctl missing Status in bluez package in Ubuntu: Fix Committed Status in bluez package in Debian: Unknown Bug description: bluez has added a new tool for BT mesh handling. Debian has a new binary package: https://packages.debian.org/bullseye /bluez-meshd Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1932022] Re: Can you add the btvirt executable to bluez-tests?
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932022 Title: Can you add the btvirt executable to bluez-tests? Status in bluez package in Ubuntu: Fix Committed Bug description: See the Debian package: https://packages.debian.org/buster/i386/bluez- test-tools/filelist The Ubuntu package contains the same tools, except for btvirt. Would it be possible to add this? The buildlog shows that the btvirt executable is already built, but just not put into the *.deb package. Additions to be done to debian/bluez-tests.install: emulator/b1ee usr/bin emulator/btvirt usr/bin emulator/hfp usr/bin Having the btvirt tool available will make testing on CI systems a lot easier. References: https://github.com/hadess/bluez/blob/master/Makefile.tools#L76-L82 https://answers.launchpad.net/ubuntu/+source/bluez/+question/697542 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933078] Re: BlueZ 5.59 release
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
** No longer affects: mesa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in OEM Priority Project: In Progress Status in Provider for Plainbox - Checkbox: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: == SRU Justification == [Impact] When the system is under memory pressure, the entire desktop session may crash. [Fix] Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory") [Test] Run memory stress and the session crashed in less than 5 minutes. With the fix applied, run memory stress for 24 hours and the desktop session is still alive. [Where problems could occur] Doing a reset might make the system even more sluggish when under memory pressure. == Original bug report == I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/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 1925761] Re: libnns-mymachines update breaks local mdns discovery
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1925761 Title: libnns-mymachines update breaks local mdns discovery Status in systemd package in Ubuntu: Expired Bug description: After the last systemd update 245.4-ubuntu3.6 on 20.04 focal, I discovered I couldn't use .local network names anymore. All returning Name or service unknown. Nothing explicitly showing a problem in avahi-deamon systemd logs, no firewall activated, and no changes done to /etc/nsswitch.conf. After noticing those packages just had been updated, I downgraded systemd to 245.4-ubuntu3 through aptitude and it works again. So I'm pretty sure something's wrong with last package from focal-updates of libnss-mymachines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925761/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Thanks Andy. I've added the fix to the 5.59 release (bug 1933078) and it works great. ** No longer affects: linux (Ubuntu) ** Also affects: gnome-settings-daemon (Ubuntu Impish) Importance: Undecided Status: Fix Released ** Also affects: bluez (Ubuntu Impish) Importance: High Assignee: Andy Chi (andch) Status: In Progress ** Also affects: gnome-settings-daemon (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: gnome-settings-daemon (Ubuntu Focal) ** No longer affects: gnome-settings-daemon (Ubuntu Hirsute) ** Changed in: bluez (Ubuntu Focal) Status: New => In Progress ** Changed in: bluez (Ubuntu Hirsute) Status: New => In Progress ** Changed in: bluez (Ubuntu Focal) Importance: Undecided => High ** Changed in: bluez (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: bluez (Ubuntu Focal) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: bluez (Ubuntu Hirsute) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: bluez (Ubuntu Impish) Assignee: Andy Chi (andch) => Daniel van Vugt (vanvugt) ** Description changed: [Impact] - * On/off of Bluetooth in gnome-control-center will not work properly. - - * Devices are not refreshed in the list anymore. - - * The passed struct will depend on the length of the submitted read() and the -kernel version. - + On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. + [Test Plan] - * Open gnome-control-center and select Bluetooth + 1. Open gnome-control-center and select Bluetooth + 2. Turn off Bluetooth via UI + 3. Turn on Bluetooth via UI - * turn off Bluetooth via UI - - * turn on Bluetooth via UI + Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] - * If user install newer kernel such as 5.13, they may have this issue. + Since the fix involves the 'rfkill' logic it has the potential to affect + any Bluetooth or Wifi on/off setting. - * Tested on Intel AX201 and Intel 6235 with kernel version - 5.13.0-1003-oem. + [Other info] - * Upstream bug in gnome-bluetooth -https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 + Upstream bug in gnome-bluetooth: + https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 - * Discussion in linux-bluetooth -https://marc.info/?t=16200475893=1=2 + Discussion in linux-bluetooth: + https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) 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 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16
[Touch-packages] [Bug 1933078] Re: BlueZ 5.59 release
** Attachment added: "bluez_5.59-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+attachment/5506368/+files/bluez_5.59-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933276] Re: trash
Ubuntu 14.04 (trusty) reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- 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/1933276 Title: trash Status in Ubuntu: Won't Fix Bug description: system locks when trash can is emptied. Doesn't empty. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jun 22 18:16:17 2021 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:9035] Subsystem: Sony Corporation Device [104d:9035] InstallationDate: Installed on 2014-12-20 (2376 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Sony Corporation VGN-FW170J ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=97ba2d83-7962-452a-82d3-a77935bf95bf ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270Y0:bd10/07/2009:svnSonyCorporation:pnVGN-FW170J:pvrC600HH56:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FW170J dmi.product.version: C600HH56 dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jun 22 09:16:31 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1933276/+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 1899962] Re: Wrong audio output device selected on Raspberry Pi Desktop
See also bug 1877194. -- 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/1899962 Title: Wrong audio output device selected on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: Incomplete Bug description: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 Got it, thanks for sharing. -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
** Summary changed: - switch-on-connect mistakes startup for USB hotplug + switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot -- 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/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Triaged Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1933244] Re: Pulseaudio does not remember default input/output device
*** This bug is a duplicate of bug 1877194 *** https://bugs.launchpad.net/bugs/1877194 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 1877194, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1877194 switch-on-connect mistakes startup for USB hotplug -- 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/1933244 Title: Pulseaudio does not remember default input/output device Status in pulseaudio package in Ubuntu: Confirmed Bug description: On my ubuntu 18.04 and 20.04 pulseaudio does not remember default device. I have headset and webcam. When I choose my headset as default input/output device and it works.But when I logout or reboot/power off my PC, it again chooses my webcam as default device. It`s so annoying, after each logout or power off to select defaut device. I found a solution, which solves this problem.Deleting of patch 0030 -load-module-switch-on-connect.patch fixes my problem.So, unloading module module-switch-on-connect, makes pulseaudio remember default device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1933244/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 In a case like this it might have been easier to find just by searching for bluez bugs and ordering them newest-to-oldest. When you do that, bug 1926062 is near the top. -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1931902] Re: [AMD Ellesmere HDMI Audio] Crackling sound on Pulseaudio for Ubuntu 21.04
** Summary changed: - [Asus PRIME B450-PLUS] Crackling sound on Pulseaudio for Ubuntu 21.04 + [AMD Ellesmere HDMI Audio] Crackling sound on Pulseaudio for Ubuntu 21.04 ** Summary changed: - [AMD Ellesmere HDMI Audio] Crackling sound on Pulseaudio for Ubuntu 21.04 + [AMD Ellesmere HDMI Audio over DisplayPort] Crackling sound on Pulseaudio for Ubuntu 21.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1931902 Title: [AMD Ellesmere HDMI Audio over DisplayPort] Crackling sound on Pulseaudio for Ubuntu 21.04 Status in pulseaudio package in Ubuntu: New Bug description: While playing back any sounds, a certain crackling sound (static) will play with a fixed delay of the sound being played. The amount and volume of the static will depend on the sound/music that is being played, and this only starts occurring after a somewhat long time (30 minutes or more). What is interesting to see is that while playing back music from Spotify (Snap) the static will only start after a second or so, but when playing YouTube videos on Firefox, it will be immediate and output that static while the video is playing. I've added two sound recordings, one while playing back a song from Spotify and the other while playing a song from YouTube. This issue goes away when restarting the PulseAudio service, but it comes back after a random amount of time. 1) Description: Ubuntu 21.04 Release: 21.04 2) pulseaudio: Installed: 1:14.2-1ubuntu1 Candidate: 1:14.2-1ubuntu1 Version table: 1:14.2-1ubuntu1.1 1 (phased 10%) 500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:14.2-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: matheus 18662 F pulseaudio /dev/snd/controlC2: matheus 18662 F pulseaudio /dev/snd/controlC0: matheus 18662 F pulseaudio /dev/snd/pcmC0D8p: matheus 18662 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 14 16:58:43 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-05-03 (41 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Hi @Daniel, Yes, it has not been upstreamed yet. Linux-bluetooth does not reply the thread, maybe I'll have a try to send mail to them. -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in bluez package in Ubuntu: In Progress Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) 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 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
Sounds like the upstream bug: https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 needs to be unlinked from this bug. It's still open and already linked to bug 1871959 instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in Provider for Plainbox - Checkbox: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: == SRU Justification == [Impact] When the system is under memory pressure, the entire desktop session may crash. [Fix] Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory") [Test] Run memory stress and the session crashed in less than 5 minutes. With the fix applied, run memory stress for 24 hours and the desktop session is still alive. [Where problems could occur] Doing a reset might make the system even more sluggish when under memory pressure. == Original bug report == I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 Hi @Daniel, Sorry for that, I tried to search for existing bug, I guess I'm not using the right words to search. Will be careful next time or ask in mattermost channel first. Thanks. -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Description changed: + [Impact] + + * On/off of Bluetooth in gnome-control-center will not work properly. + + * Devices are not refreshed in the list anymore. + + * The passed struct will depend on the length of the submitted read() and the +kernel version. + + [Test Plan] + + * Open gnome-control-center and select Bluetooth + + * turn off Bluetooth via UI + + * turn on Bluetooth via UI + + [Where problems could occur] + + * If user install newer kernel such as 5.13, they may have this issue. + + * Tested on Intel AX201 and Intel 6235 with kernel version + 5.13.0-1003-oem. + + * Upstream bug in gnome-bluetooth +https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 + + * Discussion in linux-bluetooth +https://marc.info/?t=16200475893=1=2 + + [Original bug report] + When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS - Bluetooth: hci0: HCI reset during shutdown failed + Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) 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 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 ** Tags added: regression-release -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in bluez package in Ubuntu: In Progress Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) 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 Architecture: amd64
[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 ** This bug has been marked a duplicate of bug 1926062 [hirsute/impish] Can't turn bluetooth on again after turning it off -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933078] Re: BlueZ 5.59 release
On hold again since there's also a fix for bug 1926062 coming. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933259] Re: Bluetooth not working/can't turn it on
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 ** This bug has been marked a duplicate of bug 1926062 [hirsute/impish] Can't turn bluetooth on again after turning it off -- 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/1933259 Title: Bluetooth not working/can't turn it on Status in bluez package in Ubuntu: New Bug description: Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the returns: ``` bluetoothctl Agent registered [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes [bluetooth]# connect 60:14:B3:AC:14:C8 Device 60:14:B3:AC:14:C8 not available [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933259/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
The bluez fix has not been upstreamed yet. Is that pending? ** Package changed: gnome-control-center (Ubuntu) => gnome-settings- daemon (Ubuntu) ** Changed in: gnome-settings-daemon (Ubuntu) Status: Invalid => Fix Released ** Tags added: fixed-in-gsd-3.38.2 fixed-in-gsd-40.0.1 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues #38 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 ** Also affects: gnome-bluetooth via https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Importance: Unknown Status: Unknown ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: bluez (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in bluez package in Ubuntu: In Progress Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) 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 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 Since the fix isn't in impish yet and that has to come first, we have time to clean up the duplicate bugs. Please use bug 1926062 instead. -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
Thanks for the fix, but please be more careful to check for existing bugs (bug 1926062) in future rather than opening new ones. -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933276] [NEW] trash
Public bug reported: system locks when trash can is emptied. Doesn't empty. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jun 22 18:16:17 2021 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:9035] Subsystem: Sony Corporation Device [104d:9035] InstallationDate: Installed on 2014-12-20 (2376 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Sony Corporation VGN-FW170J ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=97ba2d83-7962-452a-82d3-a77935bf95bf ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270Y0:bd10/07/2009:svnSonyCorporation:pnVGN-FW170J:pvrC600HH56:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FW170J dmi.product.version: C600HH56 dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jun 22 09:16:31 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.11 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933276 Title: trash Status in xorg package in Ubuntu: New Bug description: system locks when trash can is emptied. Doesn't empty. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jun 22 18:16:17 2021 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:9035] Subsystem: Sony Corporation Device [104d:9035] InstallationDate: Installed on 2014-12-20 (2376 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Sony Corporation VGN-FW170J ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=97ba2d83-7962-452a-82d3-a77935bf95bf ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag:
[Touch-packages] [Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable
*** This bug is a duplicate of bug 1872778 *** https://bugs.launchpad.net/bugs/1872778 Followed Deziel #8 which worked perfectly for email (many thanks), but then got the same error message when I tried to add my Outlook calendar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: I can no longer connect to my ISP mail server. Works in previous version 19.10 "The reported error was “Failed to get capabilities: Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough).”." I've tried finding a workaround but so far no luck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution 3.35.92-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 11:07:01 2020 InstallationDate: Installed on 2020-03-03 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+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
Diffoscope already handles zstd compressed members well. ** Changed in: diffoscope (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default Status in appstream-glib package in Ubuntu: New Status in apt package in Ubuntu: Fix Released Status in aptly package in Ubuntu: New Status in boinc package in Ubuntu: New Status in busybox package in Ubuntu: New Status in cdebootstrap package in Ubuntu: New Status in cdist package in Ubuntu: New Status in debdelta package in Ubuntu: New Status in debian-el package in Ubuntu: New Status in debootstrap package in Ubuntu: Fix Released Status in debsig-verify package in Ubuntu: New Status in debsigs package in Ubuntu: New Status in diffoscope package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in dpkg-sig package in Ubuntu: New Status in file package in Ubuntu: New Status in hello package in Ubuntu: Fix Released Status in libsolv package in Ubuntu: New Status in lintian package in Ubuntu: Fix Released Status in lutris package in Ubuntu: New Status in obs-build package in Ubuntu: New Status in osc package in Ubuntu: New Status in radare2 package in Ubuntu: New Status in reprepro package in Ubuntu: Fix Released Status in vim-scripts package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: New Status in debian-el package in Debian: Unknown Bug description: https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built on Hirsute having both data and control members of the .deb being compressed with zstd. It can be handy for testing various tools. [dpkg] Decompression support in dpkg landed first in Bionic and is being SRUd to Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the zstd-compressed binary packages. From dpkg's perspective the upgrade path is cleared. The original plan was compressing only the internal data.tar .deb member, but dpkg uses uniform compression by default since dpkg 1.19.0 thus I'm collecting all the changes to support control.tar.zst, too, in this bug. Reviewed packages from: https://codesearch.debian.net/search?q=data.tar.xz=1=1 https://codesearch.debian.net/search?q=control.tar.xz=1=1 appstream-glib - needs fix: libappstream-builder/asb-package-deb.c aptly - needs fix: deb/deb.go boinc - needs fix: debian/fetch_example_applications.sh busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c cdebootstrap- needs fix: src/package.c cdist - may need fix, can use dpkg-deb: cdist/preos/debootstrap/files/devuan-debootstrap/functions debdelta- needs fix: debdelta debpatch.sh debian-el - needs fix: deb-view.el debian-handbook - needs fix, maybe later, for Debian debootstrap - needs fix, https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54 debsigs - needs fix, debsigs debsig-verify - needs fix, src/debsig-verify.c diffoscope - needs fix, diffoscope/comparators/deb.py dpkg- needs fix, change default dpkg-sig- needs fix, dpkg-sig dpmb- needs fix, maybe later, for Debian elfutils- may need fix, uses dpkg-deb if it is available, does not handle .gz either file- needs fix, magic/Magdir/archive libsolv - needs fix, ext/repo_deb.c lintian - needs fix malformed-deb-archive lutris - needs fix, lutris/util/extract.py obs-build - needs fix Build/Deb.pm osc - needs fix osc/util/debquery.py control.tar.zst only python-apt - needs fix apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() radare2 - needs fix reprepro- needs fix, debfile.c vim-scripts - needs fix debPlugin/autoload/deb.vim winetricks - needs fix when Debian switches src/winetricks zeroinstall-injector - needs fix src/zeroinstall/archive.ml acr - skip, does not _have to_ be fixed, just creates packages, see dist/deb_hand.mak alien - skip, uses dpkg-deb to extract .deb ansible - not affected, just test data in dbdata.tar.xz anthy - not affected, just changelog entry apt - seems fixed already ceph- not affected in Ubuntu's version circlator - not affected, just test data cowdancer - not affected, just documentation eccodes - skip, just orig-data.tar.xz eckit - skip, just ...orig-data.tar.xz firefox - skip, profdata.tar.xz firefox-esr - skip, profdata.tar.xz galculator - skip, just changelog grads - skip, ...orig-data.tar.xz gvmd- skip, just creates xz compressed .deb
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
Proposed diffoscope fix: https://salsa.debian.org/reproducible- builds/diffoscope/-/merge_requests/83 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default Status in appstream-glib package in Ubuntu: New Status in apt package in Ubuntu: Fix Released Status in aptly package in Ubuntu: New Status in boinc package in Ubuntu: New Status in busybox package in Ubuntu: New Status in cdebootstrap package in Ubuntu: New Status in cdist package in Ubuntu: New Status in debdelta package in Ubuntu: New Status in debian-el package in Ubuntu: New Status in debootstrap package in Ubuntu: Fix Released Status in debsig-verify package in Ubuntu: New Status in debsigs package in Ubuntu: New Status in diffoscope package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in dpkg-sig package in Ubuntu: New Status in file package in Ubuntu: New Status in hello package in Ubuntu: Fix Released Status in libsolv package in Ubuntu: New Status in lintian package in Ubuntu: Fix Released Status in lutris package in Ubuntu: New Status in obs-build package in Ubuntu: New Status in osc package in Ubuntu: New Status in radare2 package in Ubuntu: New Status in reprepro package in Ubuntu: Fix Released Status in vim-scripts package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: New Status in debian-el package in Debian: Unknown Bug description: https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built on Hirsute having both data and control members of the .deb being compressed with zstd. It can be handy for testing various tools. [dpkg] Decompression support in dpkg landed first in Bionic and is being SRUd to Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the zstd-compressed binary packages. From dpkg's perspective the upgrade path is cleared. The original plan was compressing only the internal data.tar .deb member, but dpkg uses uniform compression by default since dpkg 1.19.0 thus I'm collecting all the changes to support control.tar.zst, too, in this bug. Reviewed packages from: https://codesearch.debian.net/search?q=data.tar.xz=1=1 https://codesearch.debian.net/search?q=control.tar.xz=1=1 appstream-glib - needs fix: libappstream-builder/asb-package-deb.c aptly - needs fix: deb/deb.go boinc - needs fix: debian/fetch_example_applications.sh busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c cdebootstrap- needs fix: src/package.c cdist - may need fix, can use dpkg-deb: cdist/preos/debootstrap/files/devuan-debootstrap/functions debdelta- needs fix: debdelta debpatch.sh debian-el - needs fix: deb-view.el debian-handbook - needs fix, maybe later, for Debian debootstrap - needs fix, https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54 debsigs - needs fix, debsigs debsig-verify - needs fix, src/debsig-verify.c diffoscope - needs fix, diffoscope/comparators/deb.py dpkg- needs fix, change default dpkg-sig- needs fix, dpkg-sig dpmb- needs fix, maybe later, for Debian elfutils- may need fix, uses dpkg-deb if it is available, does not handle .gz either file- needs fix, magic/Magdir/archive libsolv - needs fix, ext/repo_deb.c lintian - needs fix malformed-deb-archive lutris - needs fix, lutris/util/extract.py obs-build - needs fix Build/Deb.pm osc - needs fix osc/util/debquery.py control.tar.zst only python-apt - needs fix apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() radare2 - needs fix reprepro- needs fix, debfile.c vim-scripts - needs fix debPlugin/autoload/deb.vim winetricks - needs fix when Debian switches src/winetricks zeroinstall-injector - needs fix src/zeroinstall/archive.ml acr - skip, does not _have to_ be fixed, just creates packages, see dist/deb_hand.mak alien - skip, uses dpkg-deb to extract .deb ansible - not affected, just test data in dbdata.tar.xz anthy - not affected, just changelog entry apt - seems fixed already ceph- not affected in Ubuntu's version circlator - not affected, just test data cowdancer - not affected, just documentation eccodes - skip, just orig-data.tar.xz eckit - skip, just ...orig-data.tar.xz firefox - skip, profdata.tar.xz firefox-esr - skip, profdata.tar.xz galculator - skip, just changelog grads - skip, ...orig-data.tar.xz gvmd- skip, just creates xz compressed .deb insighttoolkit4 - skip,
Re: [Touch-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Em quinta-feira, 17 de junho de 2021, às 00:45:30 -03, Thiago Jung Bauermann escreveu: > > > I think it may be related to a change in mesa. Specifically mesa > > > commit > > > 820dec3f7c7. For more info see > > > https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 > > > > I’ll run with Mario’s build of Mesa with that patch backported. > > Thanks, Mario! > > I’m running with the Mesa build from Mario’s PPA now. If I don’t see any > issue within two weeks, I think it will be possible to say that the bug > is gone, or at least much harder to hit. > > I can’t use my reproducer in this case, because I can’t change the Mesa > version inside the flatpak image. I just had this bug happen again spontaneously, while running with Mesa from Mario’s PPA. So this bug isn’t fixed by the patch mentioned by Alex. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
** Bug watch added: Debian Bug tracker #878900 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878900 ** Also affects: debian-el (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878900 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default Status in appstream-glib package in Ubuntu: New Status in apt package in Ubuntu: Fix Released Status in aptly package in Ubuntu: New Status in boinc package in Ubuntu: New Status in busybox package in Ubuntu: New Status in cdebootstrap package in Ubuntu: New Status in cdist package in Ubuntu: New Status in debdelta package in Ubuntu: New Status in debian-el package in Ubuntu: New Status in debootstrap package in Ubuntu: Fix Released Status in debsig-verify package in Ubuntu: New Status in debsigs package in Ubuntu: New Status in diffoscope package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in dpkg-sig package in Ubuntu: New Status in file package in Ubuntu: New Status in hello package in Ubuntu: Fix Released Status in libsolv package in Ubuntu: New Status in lintian package in Ubuntu: Fix Released Status in lutris package in Ubuntu: New Status in obs-build package in Ubuntu: New Status in osc package in Ubuntu: New Status in radare2 package in Ubuntu: New Status in reprepro package in Ubuntu: Fix Released Status in vim-scripts package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: New Status in debian-el package in Debian: Unknown Bug description: https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built on Hirsute having both data and control members of the .deb being compressed with zstd. It can be handy for testing various tools. [dpkg] Decompression support in dpkg landed first in Bionic and is being SRUd to Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the zstd-compressed binary packages. From dpkg's perspective the upgrade path is cleared. The original plan was compressing only the internal data.tar .deb member, but dpkg uses uniform compression by default since dpkg 1.19.0 thus I'm collecting all the changes to support control.tar.zst, too, in this bug. Reviewed packages from: https://codesearch.debian.net/search?q=data.tar.xz=1=1 https://codesearch.debian.net/search?q=control.tar.xz=1=1 appstream-glib - needs fix: libappstream-builder/asb-package-deb.c aptly - needs fix: deb/deb.go boinc - needs fix: debian/fetch_example_applications.sh busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c cdebootstrap- needs fix: src/package.c cdist - may need fix, can use dpkg-deb: cdist/preos/debootstrap/files/devuan-debootstrap/functions debdelta- needs fix: debdelta debpatch.sh debian-el - needs fix: deb-view.el debian-handbook - needs fix, maybe later, for Debian debootstrap - needs fix, https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54 debsigs - needs fix, debsigs debsig-verify - needs fix, src/debsig-verify.c diffoscope - needs fix, diffoscope/comparators/deb.py dpkg- needs fix, change default dpkg-sig- needs fix, dpkg-sig dpmb- needs fix, maybe later, for Debian elfutils- may need fix, uses dpkg-deb if it is available, does not handle .gz either file- needs fix, magic/Magdir/archive libsolv - needs fix, ext/repo_deb.c lintian - needs fix malformed-deb-archive lutris - needs fix, lutris/util/extract.py obs-build - needs fix Build/Deb.pm osc - needs fix osc/util/debquery.py control.tar.zst only python-apt - needs fix apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() radare2 - needs fix reprepro- needs fix, debfile.c vim-scripts - needs fix debPlugin/autoload/deb.vim winetricks - needs fix when Debian switches src/winetricks zeroinstall-injector - needs fix src/zeroinstall/archive.ml acr - skip, does not _have to_ be fixed, just creates packages, see dist/deb_hand.mak alien - skip, uses dpkg-deb to extract .deb ansible - not affected, just test data in dbdata.tar.xz anthy - not affected, just changelog entry apt - seems fixed already ceph- not affected in Ubuntu's version circlator - not affected, just test data cowdancer - not affected, just documentation eccodes - skip, just orig-data.tar.xz eckit - skip, just ...orig-data.tar.xz firefox - skip, profdata.tar.xz firefox-esr - skip, profdata.tar.xz galculator - skip,
[Touch-packages] [Bug 1931902] Re: [Asus PRIME B450-PLUS] Crackling sound on Pulseaudio for Ubuntu 21.04
This issue isn't related to the motherboard itself, because I have the monitor connected to the RX 580's DisplayPort output, not the internal audio output. I don't get this issue while using USB-C audio, Analog output/input or through HDMI, only DisplayPort. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1931902 Title: [Asus PRIME B450-PLUS] Crackling sound on Pulseaudio for Ubuntu 21.04 Status in pulseaudio package in Ubuntu: New Bug description: While playing back any sounds, a certain crackling sound (static) will play with a fixed delay of the sound being played. The amount and volume of the static will depend on the sound/music that is being played, and this only starts occurring after a somewhat long time (30 minutes or more). What is interesting to see is that while playing back music from Spotify (Snap) the static will only start after a second or so, but when playing YouTube videos on Firefox, it will be immediate and output that static while the video is playing. I've added two sound recordings, one while playing back a song from Spotify and the other while playing a song from YouTube. This issue goes away when restarting the PulseAudio service, but it comes back after a random amount of time. 1) Description: Ubuntu 21.04 Release: 21.04 2) pulseaudio: Installed: 1:14.2-1ubuntu1 Candidate: 1:14.2-1ubuntu1 Version table: 1:14.2-1ubuntu1.1 1 (phased 10%) 500 http://br.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:14.2-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: matheus 18662 F pulseaudio /dev/snd/controlC2: matheus 18662 F pulseaudio /dev/snd/controlC0: matheus 18662 F pulseaudio /dev/snd/pcmC0D8p: matheus 18662 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 14 16:58:43 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-05-03 (41 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916651] Re: asks about irc user home directory during upgrade
Same for me when upgrading 20.10 to 21.04. I'm running i3wm window manager with picom composition manager, if that's related in any way.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1916651 Title: asks about irc user home directory during upgrade Status in base-passwd package in Ubuntu: Confirmed Status in base-passwd source package in Hirsute: Confirmed Bug description: Upgrading from groovy to hirsuite, base-passwd asks if the `irc` user's home directory should be moved from `/var/run/ircd` to `/run/ircd`. Having no IRC server installed makes this very confusing, but appears harmless (https://askubuntu.com/questions/876975/user-irc-inside-of-default- ubuntu-16-04-server). Possibly caused by https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=946884, but can this not prompt the user for a decision? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: base-passwd 3.5.49 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Feb 23 12:02:59 2021 InstallationDate: Installed on 2019-08-17 (556 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: libc6 libc6 libssl1.1 libssl1.1 SourcePackage: base-passwd UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1916651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Hello Denys, or anyone else affected, Accepted evolution-data-server into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /evolution-data-server/3.40.0-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933259] Re: Bluetooth not working/can't turn it on
I should mention that bluetooth was working on 20.04 and 20.10 but after upgrade to 21.04 it doesn't work anymore. -- 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/1933259 Title: Bluetooth not working/can't turn it on Status in bluez package in Ubuntu: New Bug description: Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the returns: ``` bluetoothctl Agent registered [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes [bluetooth]# connect 60:14:B3:AC:14:C8 Device 60:14:B3:AC:14:C8 not available [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933259/+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 1933259] [NEW] Bluetooth not working/can't turn it on
Public bug reported: Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the returns: ``` bluetoothctl Agent registered [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes [bluetooth]# connect 60:14:B3:AC:14:C8 Device 60:14:B3:AC:14:C8 not available [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# ``` ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth bluetoothctl -- 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/1933259 Title: Bluetooth not working/can't turn it on Status in bluez package in Ubuntu: New Bug description: Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the returns: ``` bluetoothctl Agent registered [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes [bluetooth]# connect 60:14:B3:AC:14:C8 Device 60:14:B3:AC:14:C8 not available [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
uploaded to hirsute SRU queue for review now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
** Changed in: evolution-data-server (Ubuntu Focal) Importance: Undecided => High ** Changed in: evolution-data-server (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: evolution-data-server (Ubuntu Hirsute) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
** Also affects: libgweather (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gnome-weather (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-weather (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libgweather (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-weather (Ubuntu Focal) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: libgweather (Ubuntu Focal) Assignee: (unassigned) => Iain Lane (laney) ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-weather source package in Focal: New Status in libgweather source package in Focal: New Status in gnome-weather package in Fedora: New Bug description: [Impact] The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.2 == This version switches the yr.no backend to use met.no instead. Please note that this backport is only meant as a compatibility layer. Where at all possible, the newer libgweather 40 should be used as applications cannot fully comply with the met.no ToS otherwise. [Test case] - gnome-weather shows the weather forecast - gnome-shell shows the weather forecast in the calendar menu [Regression potential] - Weather forecast is totally broken now and can't be more broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
** Changed in: evolution-data-server (Ubuntu Hirsute) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Triaged Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
** Changed in: mesa (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Hirsute) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in Provider for Plainbox - Checkbox: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: == SRU Justification == [Impact] When the system is under memory pressure, the entire desktop session may crash. [Fix] Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory") [Test] Run memory stress and the session crashed in less than 5 minutes. With the fix applied, run memory stress for 24 hours and the desktop session is still alive. [Where problems could occur] Doing a reset might make the system even more sluggish when under memory pressure. == Original bug report == I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1932311] Re: migrate to llvm 12
** Changed in: mesa (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Hirsute) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1932311 Title: migrate to llvm 12 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: (split off from bug 1917763) [Impact] Mesa should migrate to llvm 12 for new AMDGPU features and HW support. Normally this would be done during the devel series, but this version was delayed too much to migrate before hirsute was out. [Fix] Build-depend on the new packages, including libclc which is now built from llvm sources. [Test case] Test AMD graphics and/or qemu desktop (llvmpipe) after installing migrated packages. [Regression potential] This has been in Impish for a month now without issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1932311/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Changed in: accountsservice (Ubuntu Groovy) Status: New => Invalid ** Changed in: accountsservice (Ubuntu Hirsute) Status: New => Invalid ** Changed in: gnome-shell (Ubuntu Groovy) Status: New => Invalid ** Changed in: gnome-shell (Ubuntu Hirsute) Status: New => Invalid ** Changed in: dbus (Ubuntu Groovy) Status: New => Incomplete ** Changed in: dbus (Ubuntu Hirsute) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Incomplete Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Incomplete Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log
[Touch-packages] [Bug 1925467] Re: stack-buffer-overflow of text.c in function _import_ansi
** Changed in: libcaca Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcaca in Ubuntu. https://bugs.launchpad.net/bugs/1925467 Title: stack-buffer-overflow of text.c in function _import_ansi Status in libcaca: New Status in libcaca package in Ubuntu: Triaged Bug description: Hello ubuntu security team issues: https://github.com/cacalabs/libcaca/issues/55 System info: Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0 Fedora 33: clang 11.0.0 , gcc 10.2.1 libcaca version e4968ba Verification steps: 1.Get the source code of libcaca 2.Compile the libcaca.so library $ cd libcaca $ ./bootstrap $ ./configure $ make or $ cd libcaca $ ./bootstrap $ ../configure CC="clang -O2 -fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2 -fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" $ make 3.Create the poc_ansi.cc && build #include "config.h" #include "caca.h" //#include "common-image.h" #include #include #include #include #include #include using namespace std; void crash(const uint8_t *Data, size_t Size) { if(Size<8) return ; size_t len=0; caca_canvas_t *cv; cv = caca_create_canvas(0,0); caca_create_frame(cv,0); caca_set_frame(cv,0); caca_import_canvas_from_memory(cv,Data,Size,"ansi"); caca_free_canvas(cv); cv=NULL; } int main(int args,char* argv[]){ size_t len = 0; unsigned char buffer[] = {0x20,0x4a,0x0c,0x0a,0x20,0x0a,0x20,0x0c,0xc,0xc}; len = sizeof(buffer)/sizeof(unsigned char); printf("%d\n",sizeof(buffer)/sizeof(unsigned char)); crash((const uint8_t*)buffer,len); return 0; } 4.compile poc_ansi.cc clang++ -g poc_ansi.cc -O2 -fno-omit-frame-pointer -fsanitize=address -I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_ansi 5.Run poc_ansi asan info: = ==3763372==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffda0164bea at pc 0x7f098d82c310 bp 0x7ffda01647b0 sp 0x7ffda01647a8 READ of size 1 at 0x7ffda0164bea thread T0 #0 0x7f098d82c30f in _import_ansi /home/hh/Downloads/libcaca/caca/codec/text.c:391:38 #1 0x4c6c72 in crash(unsigned char const*, unsigned long) /home/hh/Downloads/libcaca/poc_bin.cc:21:3 #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9 #3 0x7f098d2780b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16 #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_mbay+0x41c38d) Address 0x7ffda0164bea is located in stack of thread T0 at offset 42 in frame #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28 This frame has 1 object(s): [32, 42) 'buffer' (line 31) <== Memory access at offset 42 overflows this variable HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork (longjmp and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: stack-buffer-overflow /home/hh/Downloads/libcaca/caca/codec/text.c:391:38 in _import_ansi Shadow bytes around the buggy address: 0x100034024920: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 0x100034024930: f8 f8 f8 f8 f8 f8 f8 f8 f8 f2 f2 f2 f2 f2 f2 f2 0x100034024940: f2 f2 f8 f2 f2 f2 f8 f3 f3 f3 f3 f3 00 00 00 00 0x100034024950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100034024960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x100034024970: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00[02]f3 f3 0x100034024980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100034024990: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1000340249a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1000340249b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1000340249c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user:f7 Container overflow: fc Array cookie:ac Intra object redzone:bb ASan internal: fe Left alloca redzone: ca Right alloca redzone:cb Shadow gap: cc ==3763372==ABORTING Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/libcaca/+bug/1925467/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1925468] Re: stack-buffer-overflow of import.c in function _import_bin
** Changed in: libcaca Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcaca in Ubuntu. https://bugs.launchpad.net/bugs/1925468 Title: stack-buffer-overflow of import.c in function _import_bin Status in libcaca: New Status in libcaca package in Ubuntu: Triaged Bug description: Hello ubuntu security team issues:https://github.com/cacalabs/libcaca/issues/56 System info: Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0 Fedora 33: clang 11.0.0 , gcc 10.2.1 libcaca version e4968ba Verification steps: 1.Get the source code of libcaca 2.Compile the libcaca.so library $ cd libcaca $ ./bootstrap $ ./configure $ make or $ cd libcaca $ ./bootstrap $ ../configure CC="clang -O2 -fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2 -fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" $ make 3.Create the poc_bin.cc && build #include "config.h" #include "caca.h" //#include "common-image.h" #include #include #include #include #include #include using namespace std; void crash(const uint8_t *Data, size_t Size) { if(Size<8) return ; size_t len=0; caca_canvas_t *cv; cv = caca_create_canvas(0,0); caca_create_frame(cv,0); caca_set_frame(cv,0); caca_import_canvas_from_memory(cv,Data,Size,"bin"); caca_free_canvas(cv); cv=NULL; } int main(int args,char* argv[]){ size_t len = 0; unsigned char buffer[] = {0x0a,0x20,0x0a,0x0a,0x20,0x20,0x20,0x20,0x20,0x20,0x47,0x47,0x47}; len = sizeof(buffer)/sizeof(unsigned char); printf("%d\n",sizeof(buffer)/sizeof(unsigned char)); crash((const uint8_t*)buffer,len); return 0; } 4.compile poc_bin.cc clang++ -g poc_bin.cc -O2 -fno-omit-frame-pointer -fsanitize=address -I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_bin 5.Run poc_bin asan info: = ==3817476==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffe7cd3774d at pc 0x7f8c6314acfd bp 0x7ffe7cd376c0 sp 0x7ffe7cd376b8 READ of size 1 at 0x7ffe7cd3774d thread T0 #0 0x7f8c6314acfc in _import_bin /home/hh/Downloads/libcaca/caca/codec/import.c:425:33 #1 0x4c6c72 in crash(unsigned char const*, unsigned long) /home/hh/Downloads/libcaca/poc_bin.cc:21:3 #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9 #3 0x7f8c62ba00b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16 #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_bin+0x41c38d) Address 0x7ffe7cd3774d is located in stack of thread T0 at offset 45 in frame #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28 This frame has 1 object(s): [32, 45) 'buffer' (line 31) <== Memory access at offset 45 overflows this variable HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork (longjmp and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: stack-buffer-overflow /home/hh/Downloads/libcaca/caca/codec/import.c:425:33 in _import_bin Shadow bytes around the buggy address: 0x10004f99ee90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99eea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99eeb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99eec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99eed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x10004f99eee0: 00 00 00 00 f1 f1 f1 f1 00[05]f3 f3 00 00 00 00 0x10004f99eef0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99ef00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99ef10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99ef20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99ef30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user:f7 Container overflow: fc Array cookie:ac Intra object redzone:bb ASan internal: fe Left alloca redzone: ca Right alloca redzone:cb Shadow gap: cc ==3817476==ABORTING Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/libcaca/+bug/1925468/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1899962] Re: Wrong audio output device selected on Raspberry Pi Desktop
Thank you for the report§. Is the issue specific to hdmi connections? Is that different from already reported hdmi related problem like bug #1924903 ? ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete -- 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/1899962 Title: Wrong audio output device selected on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: Incomplete Bug description: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+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 1933244] Re: Pulseaudio does not remember default input/output device
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) 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/1933244 Title: Pulseaudio does not remember default input/output device Status in pulseaudio package in Ubuntu: Confirmed Bug description: On my ubuntu 18.04 and 20.04 pulseaudio does not remember default device. I have headset and webcam. When I choose my headset as default input/output device and it works.But when I logout or reboot/power off my PC, it again chooses my webcam as default device. It`s so annoying, after each logout or power off to select defaut device. I found a solution, which solves this problem.Deleting of patch 0030 -load-module-switch-on-connect.patch fixes my problem.So, unloading module module-switch-on-connect, makes pulseaudio remember default device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1933244/+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 1933244] [NEW] Pulseaudio does not remember default input/output device
Public bug reported: On my ubuntu 18.04 and 20.04 pulseaudio does not remember default device. I have headset and webcam. When I choose my headset as default input/output device and it works.But when I logout or reboot/power off my PC, it again chooses my webcam as default device. It`s so annoying, after each logout or power off to select defaut device. I found a solution, which solves this problem.Deleting of patch 0030 -load-module-switch-on-connect.patch fixes my problem.So, unloading module module-switch-on-connect, makes pulseaudio remember default device. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Confirmed ** Description changed: - On my ubuntu 18.04 and 20.04 pulseaudio does not remember default device. - I have headset and webcam. When I choose my headset as default input/output device and it works.But when I logout or reboot/power off my PC, it again choose my webcam as default device. It`s so annoying, after each logout or power off to select defaut device. - I found a solution, which solves this problem.Deleting of patch 0030-load-module-switch-on-connect.patch fixes my problem.So, unloading module module-switch-on-connect, makes pulseaudio to remember default device. + On my ubuntu 18.04 and 20.04 pulseaudio does not remember default + device. + + I have headset and webcam. When I choose my headset as default + input/output device and it works.But when I logout or reboot/power off + my PC, it again chooses my webcam as default device. It`s so annoying, + after each logout or power off to select defaut device. + + I found a solution, which solves this problem.Deleting of patch 0030 + -load-module-switch-on-connect.patch fixes my problem.So, unloading + module module-switch-on-connect, makes pulseaudio remember default + device. + + I`ve created the issue + https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1170 + already, but have not received any feedback. ** Description changed: On my ubuntu 18.04 and 20.04 pulseaudio does not remember default device. I have headset and webcam. When I choose my headset as default input/output device and it works.But when I logout or reboot/power off my PC, it again chooses my webcam as default device. It`s so annoying, after each logout or power off to select defaut device. I found a solution, which solves this problem.Deleting of patch 0030 -load-module-switch-on-connect.patch fixes my problem.So, unloading module module-switch-on-connect, makes pulseaudio remember default device. - - I`ve created the issue - https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1170 - already, but have not received any feedback. -- 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/1933244 Title: Pulseaudio does not remember default input/output device Status in pulseaudio package in Ubuntu: Confirmed Bug description: On my ubuntu 18.04 and 20.04 pulseaudio does not remember default device. I have headset and webcam. When I choose my headset as default input/output device and it works.But when I logout or reboot/power off my PC, it again chooses my webcam as default device. It`s so annoying, after each logout or power off to select defaut device. I found a solution, which solves this problem.Deleting of patch 0030 -load-module-switch-on-connect.patch fixes my problem.So, unloading module module-switch-on-connect, makes pulseaudio remember default device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1933244/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
Do you need 20.10? I don't think we have kernels that trigger the issue on that serie and I don't think it's worth the effort since it's non-LTS and not-current-stable? Upload to hirsute and focal now with the bug reference added to the changelog as required by the SRU process We will handle impish as we update bluez to the current upstream version -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
** Changed in: bluez (Ubuntu) Status: New => Fix Committed ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Ok, so the issue there was triggered by kernel changes, you can read the details in the commit message of the GNOME fix https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/d2200632 The fix is in gnome-settings-daemon 3.38.2 in impish, bluez also requires a similar fix which is being SRUed now as bug #1933221. Daniel since you are working on updating bluez to 5.59 in impish could you check if that commit is included and if it's not then cherrypick the change? ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Committed -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Fix Committed Status in gnome-control-center package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) 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 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Hi Sergio, Thanks I appreciate your answer. Yes I can use the package provided in your PPA, even if it's not very convenient to install and update it on Production machines. About that, will you maintain these packages with further security updates ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall Status in openldap package in Ubuntu: Confirmed Status in openldap source package in Bionic: Triaged Bug description: On a production server, sometimes slapd become unbresponsive, some threads loops in sched_yield syscall and consumme all CPU. To recover, slapd needs to restart. No related information is reported in log file. All same issues in OpenLDAP upstream project are old and fixed. So maybe this issue affects only Ubuntu package. It occurs randomly, so I have no steps to reproduce. OS : Bionic Openldap version: libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10 libldap-common 2.4.45+dfsg-1ubuntu1.10 slapd 2.4.45+dfsg-1ubuntu1.10 Modules loaded: olcModuleLoad: {0}back_bdb olcModuleLoad: {1}syncprov olcModuleLoad: {2}back_monitor olcModuleLoad: {3}memberof.la olcModuleLoad: {4}refint.la olcModuleLoad: {5}rwm olcModuleload: {6}back_ldap Backend is BDB. slapd run in (single) master - (multi) slave mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925467] Re: stack-buffer-overflow of text.c in function _import_ansi
** Bug watch added: github.com/cacalabs/libcaca/issues #55 https://github.com/cacalabs/libcaca/issues/55 ** Also affects: libcaca via https://github.com/cacalabs/libcaca/issues/55 Importance: Unknown Status: Unknown ** Changed in: libcaca (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcaca in Ubuntu. https://bugs.launchpad.net/bugs/1925467 Title: stack-buffer-overflow of text.c in function _import_ansi Status in libcaca: Unknown Status in libcaca package in Ubuntu: Triaged Bug description: Hello ubuntu security team issues: https://github.com/cacalabs/libcaca/issues/55 System info: Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0 Fedora 33: clang 11.0.0 , gcc 10.2.1 libcaca version e4968ba Verification steps: 1.Get the source code of libcaca 2.Compile the libcaca.so library $ cd libcaca $ ./bootstrap $ ./configure $ make or $ cd libcaca $ ./bootstrap $ ../configure CC="clang -O2 -fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2 -fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" $ make 3.Create the poc_ansi.cc && build #include "config.h" #include "caca.h" //#include "common-image.h" #include #include #include #include #include #include using namespace std; void crash(const uint8_t *Data, size_t Size) { if(Size<8) return ; size_t len=0; caca_canvas_t *cv; cv = caca_create_canvas(0,0); caca_create_frame(cv,0); caca_set_frame(cv,0); caca_import_canvas_from_memory(cv,Data,Size,"ansi"); caca_free_canvas(cv); cv=NULL; } int main(int args,char* argv[]){ size_t len = 0; unsigned char buffer[] = {0x20,0x4a,0x0c,0x0a,0x20,0x0a,0x20,0x0c,0xc,0xc}; len = sizeof(buffer)/sizeof(unsigned char); printf("%d\n",sizeof(buffer)/sizeof(unsigned char)); crash((const uint8_t*)buffer,len); return 0; } 4.compile poc_ansi.cc clang++ -g poc_ansi.cc -O2 -fno-omit-frame-pointer -fsanitize=address -I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_ansi 5.Run poc_ansi asan info: = ==3763372==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffda0164bea at pc 0x7f098d82c310 bp 0x7ffda01647b0 sp 0x7ffda01647a8 READ of size 1 at 0x7ffda0164bea thread T0 #0 0x7f098d82c30f in _import_ansi /home/hh/Downloads/libcaca/caca/codec/text.c:391:38 #1 0x4c6c72 in crash(unsigned char const*, unsigned long) /home/hh/Downloads/libcaca/poc_bin.cc:21:3 #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9 #3 0x7f098d2780b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16 #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_mbay+0x41c38d) Address 0x7ffda0164bea is located in stack of thread T0 at offset 42 in frame #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28 This frame has 1 object(s): [32, 42) 'buffer' (line 31) <== Memory access at offset 42 overflows this variable HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork (longjmp and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: stack-buffer-overflow /home/hh/Downloads/libcaca/caca/codec/text.c:391:38 in _import_ansi Shadow bytes around the buggy address: 0x100034024920: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 0x100034024930: f8 f8 f8 f8 f8 f8 f8 f8 f8 f2 f2 f2 f2 f2 f2 f2 0x100034024940: f2 f2 f8 f2 f2 f2 f8 f3 f3 f3 f3 f3 00 00 00 00 0x100034024950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100034024960: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x100034024970: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00[02]f3 f3 0x100034024980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100034024990: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1000340249a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1000340249b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x1000340249c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user:f7 Container overflow: fc Array cookie:ac Intra object redzone:bb ASan internal: fe Left alloca redzone:
[Touch-packages] [Bug 1925468] Re: stack-buffer-overflow of import.c in function _import_bin
** Bug watch added: github.com/cacalabs/libcaca/issues #56 https://github.com/cacalabs/libcaca/issues/56 ** Also affects: libcaca via https://github.com/cacalabs/libcaca/issues/56 Importance: Unknown Status: Unknown ** Changed in: libcaca (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcaca in Ubuntu. https://bugs.launchpad.net/bugs/1925468 Title: stack-buffer-overflow of import.c in function _import_bin Status in libcaca: Unknown Status in libcaca package in Ubuntu: Triaged Bug description: Hello ubuntu security team issues:https://github.com/cacalabs/libcaca/issues/56 System info: Ubuntu 20.04 : clang 10.0.0 , gcc 9.3.0 Fedora 33: clang 11.0.0 , gcc 10.2.1 libcaca version e4968ba Verification steps: 1.Get the source code of libcaca 2.Compile the libcaca.so library $ cd libcaca $ ./bootstrap $ ./configure $ make or $ cd libcaca $ ./bootstrap $ ../configure CC="clang -O2 -fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" CXX="clang++ -O2 -fno-omit-frame-pointer -g -fsanitize=address,fuzzer-no-link -fsanitize-coverage=bb" $ make 3.Create the poc_bin.cc && build #include "config.h" #include "caca.h" //#include "common-image.h" #include #include #include #include #include #include using namespace std; void crash(const uint8_t *Data, size_t Size) { if(Size<8) return ; size_t len=0; caca_canvas_t *cv; cv = caca_create_canvas(0,0); caca_create_frame(cv,0); caca_set_frame(cv,0); caca_import_canvas_from_memory(cv,Data,Size,"bin"); caca_free_canvas(cv); cv=NULL; } int main(int args,char* argv[]){ size_t len = 0; unsigned char buffer[] = {0x0a,0x20,0x0a,0x0a,0x20,0x20,0x20,0x20,0x20,0x20,0x47,0x47,0x47}; len = sizeof(buffer)/sizeof(unsigned char); printf("%d\n",sizeof(buffer)/sizeof(unsigned char)); crash((const uint8_t*)buffer,len); return 0; } 4.compile poc_bin.cc clang++ -g poc_bin.cc -O2 -fno-omit-frame-pointer -fsanitize=address -I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_bin 5.Run poc_bin asan info: = ==3817476==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffe7cd3774d at pc 0x7f8c6314acfd bp 0x7ffe7cd376c0 sp 0x7ffe7cd376b8 READ of size 1 at 0x7ffe7cd3774d thread T0 #0 0x7f8c6314acfc in _import_bin /home/hh/Downloads/libcaca/caca/codec/import.c:425:33 #1 0x4c6c72 in crash(unsigned char const*, unsigned long) /home/hh/Downloads/libcaca/poc_bin.cc:21:3 #2 0x4c6c72 in main /home/hh/Downloads/libcaca/poc_bin.cc:34:9 #3 0x7f8c62ba00b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/../csu/libc-start.c:308:16 #4 0x41c38d in _start (/home/hh/Downloads/libcaca/poc_bin+0x41c38d) Address 0x7ffe7cd3774d is located in stack of thread T0 at offset 45 in frame #0 0x4c6b9f in main /home/hh/Downloads/libcaca/poc_bin.cc:28 This frame has 1 object(s): [32, 45) 'buffer' (line 31) <== Memory access at offset 45 overflows this variable HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork (longjmp and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: stack-buffer-overflow /home/hh/Downloads/libcaca/caca/codec/import.c:425:33 in _import_bin Shadow bytes around the buggy address: 0x10004f99ee90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99eea0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99eeb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99eec0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99eed0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x10004f99eee0: 00 00 00 00 f1 f1 f1 f1 00[05]f3 f3 00 00 00 00 0x10004f99eef0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99ef00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99ef10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99ef20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10004f99ef30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user:f7 Container overflow: fc Array cookie:ac Intra object redzone:bb ASan internal: fe Left
[Touch-packages] [Bug 1932542] Update Released
The verification of the Stable Release Update for initramfs-tools 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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1932542 Title: Add support for zstd Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Released Bug description: [Impact] * initramfs-tools in impish has changed default initrd compression to zstd. To allow compressing and uncompressing such initrds on Focal LTS release we should backport zstd support in the mkinitramfs & unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinitramfs tool to unpack and inspect impish initrds on a focal host. * Cherrypicking the feature from 0.138 release, which is also present in Hirsute and Impish. [Test Plan] * Create initrd with zstd $ mkinitramfs -c zstd -o zstd-initrd.img * Uncompress it with $ unmkinitramfs ./zstd-initrd.img zstd-initrd- unpacked [Where problems could occur] * This adds support for zstd compressed initrd in both mkinitramfs and unmkinitramfs. However our GA kernels do not support zstd compressed initrds. And depends on zstd package is not added either. Meaning one still has to install zstd to gain the unpack support. Changing initramfs.conf to zstd may result in unbootable instance when used with GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1932542] Re: Add support for zstd
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.6 --- initramfs-tools (0.136ubuntu6.6) focal; urgency=medium * Cherrypick zstd support from upstream. LP: #1932542 -- Dimitri John Ledkov Fri, 18 Jun 2021 14:22:25 +0100 ** Changed in: initramfs-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1932542 Title: Add support for zstd Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Released Bug description: [Impact] * initramfs-tools in impish has changed default initrd compression to zstd. To allow compressing and uncompressing such initrds on Focal LTS release we should backport zstd support in the mkinitramfs & unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinitramfs tool to unpack and inspect impish initrds on a focal host. * Cherrypicking the feature from 0.138 release, which is also present in Hirsute and Impish. [Test Plan] * Create initrd with zstd $ mkinitramfs -c zstd -o zstd-initrd.img * Uncompress it with $ unmkinitramfs ./zstd-initrd.img zstd-initrd- unpacked [Where problems could occur] * This adds support for zstd compressed initrd in both mkinitramfs and unmkinitramfs. However our GA kernels do not support zstd compressed initrds. And depends on zstd package is not added either. Meaning one still has to install zstd to gain the unpack support. Changing initramfs.conf to zstd may result in unbootable instance when used with GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1932542] Re: Add support for zstd
Thanks for the verification! Even though I REALLY hate releasing things early, with the nature of this package and the SRUed changes, I think we can do it conditionally - just this one time - to unblock image builds for impish. Please be sure to keep your eyes open for any weird bug reports on focal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1932542 Title: Add support for zstd Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Released Bug description: [Impact] * initramfs-tools in impish has changed default initrd compression to zstd. To allow compressing and uncompressing such initrds on Focal LTS release we should backport zstd support in the mkinitramfs & unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinitramfs tool to unpack and inspect impish initrds on a focal host. * Cherrypicking the feature from 0.138 release, which is also present in Hirsute and Impish. [Test Plan] * Create initrd with zstd $ mkinitramfs -c zstd -o zstd-initrd.img * Uncompress it with $ unmkinitramfs ./zstd-initrd.img zstd-initrd- unpacked [Where problems could occur] * This adds support for zstd compressed initrd in both mkinitramfs and unmkinitramfs. However our GA kernels do not support zstd compressed initrds. And depends on zstd package is not added either. Meaning one still has to install zstd to gain the unpack support. Changing initramfs.conf to zstd may result in unbootable instance when used with GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1932542] Re: Add support for zstd
# mkinitramfs -czstd -o /boot/initrd.img-5.4.0-76-generic 5.4.0-76-generic # unmkinitramfs /boot/initrd.img-5.4.0-76-generic foo # ls foo/ bin conf etc init lib lib64 run sbin scripts usr # dpkg-query -W initramfs-tools zstd initramfs-tools 0.136ubuntu6.6 zstd1.4.4+dfsg-3ubuntu0.1 # apt remove --purge zstd # unmkinitramfs /boot/initrd.img-5.4.0-76-generic no-zstd cpio: premature end of archive With zstd package installed initramfs-tools 0.136ubuntu6.6 works with zstd compressed initrds correctly. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1932542 Title: Add support for zstd Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Released Bug description: [Impact] * initramfs-tools in impish has changed default initrd compression to zstd. To allow compressing and uncompressing such initrds on Focal LTS release we should backport zstd support in the mkinitramfs & unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinitramfs tool to unpack and inspect impish initrds on a focal host. * Cherrypicking the feature from 0.138 release, which is also present in Hirsute and Impish. [Test Plan] * Create initrd with zstd $ mkinitramfs -c zstd -o zstd-initrd.img * Uncompress it with $ unmkinitramfs ./zstd-initrd.img zstd-initrd- unpacked [Where problems could occur] * This adds support for zstd compressed initrd in both mkinitramfs and unmkinitramfs. However our GA kernels do not support zstd compressed initrds. And depends on zstd package is not added either. Meaning one still has to install zstd to gain the unpack support. Changing initramfs.conf to zstd may result in unbootable instance when used with GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
upload debdiff of hirsute ** Patch added: "bluez_5.56-0ubuntu4.2~1.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933221/+attachment/5506236/+files/bluez_5.56-0ubuntu4.2~1.debdiff -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: New Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
Sent patch to upstream (LTP): https://lists.linux.it/pipermail/ltp/2021-June/023346.html ** Changed in: ubuntu-kernel-tests Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
update debdiff of groovy. ** Patch added: "bluez_5.55-0ubuntu1.3~1.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933221/+attachment/5506235/+files/bluez_5.55-0ubuntu1.3~1.debdiff -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: New Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933221] [NEW] Blutooth on/off does not work properly from gnome-control-center
Public bug reported: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 ** Affects: oem-priority Importance: Critical Assignee: Andy Chi (andch) Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1931048 somerville ** Attachment added: "debdiff of focal" https://bugs.launchpad.net/bugs/1933221/+attachment/5506234/+files/bluez_5.53-0ubuntu3.3~1.debdiff ** Tags added: oem-priority originate-from-1931048 somerville ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) ** Changed in: oem-priority Importance: Undecided => Critical -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: New Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1928931] Re: German strings in deja-dup.mo for en_GB
> hm, do we actually know *why* this happened? Yes, someone mis-translated the strings on Launchpad. I reverted them all now, but I don't think we have any way of dealing with that happening again, do we? I've just verified the SRU. I installed language-pack-gnome-en 1:21.10+20210415ubuntu1 and ran deja-dup --prompt. With the SRU the buttons are in English again! ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en in Ubuntu. https://bugs.launchpad.net/bugs/1928931 Title: German strings in deja-dup.mo for en_GB Status in language-pack-gnome-en package in Ubuntu: In Progress Status in language-pack-gnome-en source package in Hirsute: Fix Committed Bug description: [ Description ] Some German strings were accidentally translated under en_GB. They affect the default Ubuntu install - some of them are strings which are displayed as a notification some time after first logging in, so it's quite visible. See the attached screenshot. [ Fix ] Revert the German and go back to the proper English text. The way to fix langpacks is to upload the language-pack-gnome-XX package which replaces files in language-pack-gnome-XX-base. [ Devel release ] I'd like to propose to binary copy forward, and let the normal langpack release schedule take care of eventually dominating these away in impish. [ QA ] To verify the diff, compare deja-dup.po from language-pack-gnome-en- base to the one in this upload. You'll have to do that manually. 0. Be in en_GB. 1. Install the SRU 2. In an Ubuntu Desktop session, open a terminal and run `deja-dup --prompt`. 3. Note the buttons in the notification that shows up. They should be in English. [ What could go wrong ] 1. There could be other instances of this in different packages we haven't noticed yet 2. If I break the .po file, it could either break the build or the translations at runtime (but this is English, so if we fall back to C it's not too bad) 3. If my diff is wrong then I might have dropped some en_GB translations or made them wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+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 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
Subscribe the sponsor team again, since our oem project needs this fix to be landed to bionic too. This is the debdiff for bionic, please help review and upload thx. ** Patch added: "alsa-lib_1.1.3-5ubuntu0.6.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1921452/+attachment/5506230/+files/alsa-lib_1.1.3-5ubuntu0.6.debdiff ** Changed in: alsa-lib (Ubuntu Bionic) Importance: Critical => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: In Progress Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1933078] Re: BlueZ 5.59 release
** Attachment added: "bluez_5.59.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+attachment/5506232/+files/bluez_5.59.orig.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933078] Re: BlueZ 5.59 release
** Attachment added: "bluez_5.59-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+attachment/5506233/+files/bluez_5.59-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
** Changed in: alsa-lib (Ubuntu Bionic) Status: New => In Progress ** Changed in: alsa-lib (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: alsa-lib (Ubuntu Bionic) Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: In Progress Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1932311] Re: migrate to llvm 12
** Description changed: (split off from bug 1917763) [Impact] Mesa should migrate to llvm 12 for new AMDGPU features and HW support. + Normally this would be done during the devel series, but this version + was delayed too much to migrate before hirsute was out. [Fix] Build-depend on the new packages, including libclc which is now built from llvm sources. - [Test case] Test AMD graphics and/or qemu desktop (llvmpipe) after installing migrated packages. [Regression potential] This has been in Impish for a month now without issues. -- 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/1932311 Title: migrate to llvm 12 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: (split off from bug 1917763) [Impact] Mesa should migrate to llvm 12 for new AMDGPU features and HW support. Normally this would be done during the devel series, but this version was delayed too much to migrate before hirsute was out. [Fix] Build-depend on the new packages, including libclc which is now built from llvm sources. [Test case] Test AMD graphics and/or qemu desktop (llvmpipe) after installing migrated packages. [Regression potential] This has been in Impish for a month now without issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1932311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1932022] Re: Can you add the btvirt executable to bluez-tests?
> similar to bug #1907886 if upstream decided to include it in the noinst set they might have a reason? In bug 1907886 that consideration sounds like it was overridden by the statement: "fedora is including it in their binary though, we could probably do the same for Ubuntu". As for this bug, 'btvirt' is being packaged by Debian already. On top of that 'btvirt' has no external dependencies (only libc). So users are requesting 'btvirt' (hence this bug), Debian already packages it, and I see no dependency problems. I see no reason why we can't package it. That doesn't speak for the quality or correctness of the program, but I don't have any evidence that it's below that of other BlueZ binaries. Even if it was, getting it released for people to test it and report bugs seems like the most sensible approach to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932022 Title: Can you add the btvirt executable to bluez-tests? Status in bluez package in Ubuntu: In Progress Bug description: See the Debian package: https://packages.debian.org/buster/i386/bluez- test-tools/filelist The Ubuntu package contains the same tools, except for btvirt. Would it be possible to add this? The buildlog shows that the btvirt executable is already built, but just not put into the *.deb package. Additions to be done to debian/bluez-tests.install: emulator/b1ee usr/bin emulator/btvirt usr/bin emulator/hfp usr/bin Having the btvirt tool available will make testing on CI systems a lot easier. References: https://github.com/hadess/bluez/blob/master/Makefile.tools#L76-L82 https://answers.launchpad.net/ubuntu/+source/bluez/+question/697542 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
** Also affects: alsa-lib (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: New Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
** Changed in: ubuntu-kernel-tests Assignee: Sean Feole (sfeole) => Krzysztof Kozlowski (krzk) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933198] Re: Display mode after wake-up
Usually bugs like this happen when the system detects different monitor capabilities, so it thinks it has a different monitor setup and reverts to a default arrangement. Please try running: xrandr before and after sleeping, and then compare the results. ** Summary changed: - Display mode after wake-up + [nvidia] Display mode after wake-up ** Tags added: multimonitor nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1933198 Title: [nvidia] Display mode after wake-up Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: My dual display setup sometimes switches to a mirror display mode (from joined display) when waking up from sleep. This could be totally unrelated but I have two graphic cards, and both screens are connected to the same one (Hdmi and display port). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..25.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..26.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 22 09:26:34 2021 DistUpgraded: 2021-06-09 14:41:25,219 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2060 Rev. A] [1458:37d9] NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:2484] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:146b] InstallationDate: Installed on 2021-04-16 (66 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=cbccb375-44f4-4f88-a12a-2a70cc613676 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-06-09 (12 days ago) dmi.bios.date: 04/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 GAMING PLUS MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH.60:bd04/18/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr3.0:rvnMicro-StarInternationalCo.,Ltd:rnB450GAMINGPLUSMAX(MS-7B86):rvr3.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
[Touch-packages] [Bug 1933194] Re: lagg display
Thanks for the bug report. Your kernel log is showing a couple of different problems that would explain poor performance: [ 1432.047693] pcieport :00:1c.4: AER: Corrected error received: :00:1c.4 [ 1432.047705] pcieport :00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 1432.047713] pcieport :00:1c.4: AER: device [8086:9d14] error status/mask=0001/2000 [ 1432.047718] pcieport :00:1c.4: AER:[ 0] RxErr (First) [ 1434.967857] amdgpu: VI should always have 2 performance levels In both cases they are kernel (or hardware) issues. ** Tags added: amdgpu ** Tags added: performance ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Package changed: linux (Ubuntu) => linux-hwe-5.8 (Ubuntu) ** Summary changed: - lagg display + [Lenovo V330-15IKB] lagg display -- 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/1933194 Title: [Lenovo V330-15IKB] lagg display Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: lagg display ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 22 11:46:23 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3973] Subsystem: Device [03ea:1af4] InstallationDate: Installed on 2021-06-20 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera Bus 001 Device 006: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81AX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-55-generic root=UUID=dd6defad-6211-4700-8037-049192e91a9b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN41WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvr6SCN41WW:bd12/19/2018:br1.41:efr1.19:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1933194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
** Changed in: dnsmasq (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq package in Debian: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
@rbalint @ddstreed any update on this issue? -- 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/1919177 Title: Azure: issues with accelerated networking on Hirsute Status in cloud-init: Incomplete Status in cloud-init package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Hirsute: Incomplete Status in linux-azure source package in Hirsute: Invalid Status in systemd source package in Hirsute: New Bug description: [General] On Azure, when provisioning a Hirsute VM with Accelerated Networking enabled, sometimes part of the cloud-init configuration is not applied. Especially, in those cases, the public SSH key is not setup properly. [how to reproduce] Start a VM with AN enabled: ``` az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" --image 'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" --accelerated-networking ``` After a moment, try to SSH: if you succeed, delete and recreate a new VM. [troubleshooting] To be able to connect into the VM, run: az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME" ``` In "/run/cloud-init/instance-data.json", I can see: ``` "publicKeys": [ { "keyData": "", "path": "/home/ubuntu/.ssh/authorized_keys" } ], ``` as expected. [workaround] As mentioned, Azure allows the user to run command into the VM without SSH connection. To do so, one can use the Azure CLI: az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME" This example uses "ssh-import-id" but it's also possible to just echo a given public key into /home/ubuntu/.ssh/authorized_keys NOTE: this will only solves the SSH issue, I do not know if this bug affects other things. If so the user would have to apply those things manually. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1919177/+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 1933198] Re: Display mode after wake-up
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933198 Title: Display mode after wake-up Status in xorg package in Ubuntu: New Bug description: My dual display setup sometimes switches to a mirror display mode (from joined display) when waking up from sleep. This could be totally unrelated but I have two graphic cards, and both screens are connected to the same one (Hdmi and display port). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..25.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..26.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 22 09:26:34 2021 DistUpgraded: 2021-06-09 14:41:25,219 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2060 Rev. A] [1458:37d9] NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:2484] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:146b] InstallationDate: Installed on 2021-04-16 (66 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=cbccb375-44f4-4f88-a12a-2a70cc613676 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-06-09 (12 days ago) dmi.bios.date: 04/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 GAMING PLUS MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH.60:bd04/18/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr3.0:rvnMicro-StarInternationalCo.,Ltd:rnB450GAMINGPLUSMAX(MS-7B86):rvr3.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1933198/+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 1933198] [NEW] Display mode after wake-up
You have been subscribed to a public bug: My dual display setup sometimes switches to a mirror display mode (from joined display) when waking up from sleep. This could be totally unrelated but I have two graphic cards, and both screens are connected to the same one (Hdmi and display port). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..25.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..26.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 22 09:26:34 2021 DistUpgraded: 2021-06-09 14:41:25,219 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2060 Rev. A] [1458:37d9] NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:2484] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:146b] InstallationDate: Installed on 2021-04-16 (66 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=cbccb375-44f4-4f88-a12a-2a70cc613676 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-06-09 (12 days ago) dmi.bios.date: 04/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 GAMING PLUS MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH.60:bd04/18/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr3.0:rvnMicro-StarInternationalCo.,Ltd:rnB450GAMINGPLUSMAX(MS-7B86):rvr3.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu -- Display mode after wake-up https://bugs.launchpad.net/bugs/1933198 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1933188] Re: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned er
** Package changed: fprintd (Ubuntu) => systemd (Ubuntu) -- 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/1933188 Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post- installation script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: Got this problem when doing a regular "Update/upgrade" from shell /usr/bin/deb-systemd-invoke: 32 =head1: not found /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected Endless loop of these two lines in bash before the crash. June 22 sentout uopdate ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114 Uname: Linux 5.4.0-74-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: alsa-ucm-conf:amd64: Install libpam-fprintd:amd64: Install fprintd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 22 06:52:05 2021 ErrorMessage: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-03-29 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: fprintd Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1933188/+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 1933194] Re: lagg display
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (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/1933194 Title: lagg display Status in xorg package in Ubuntu: Incomplete Bug description: lagg display ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 22 11:46:23 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3973] Subsystem: Device [03ea:1af4] InstallationDate: Installed on 2021-06-20 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera Bus 001 Device 006: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81AX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-55-generic root=UUID=dd6defad-6211-4700-8037-049192e91a9b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN41WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvr6SCN41WW:bd12/19/2018:br1.41:efr1.19:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1933194/+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 1933188] [NEW] package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned
You have been subscribed to a public bug: Got this problem when doing a regular "Update/upgrade" from shell /usr/bin/deb-systemd-invoke: 32 =head1: not found /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected Endless loop of these two lines in bash before the crash. June 22 sentout uopdate ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114 Uname: Linux 5.4.0-74-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: alsa-ucm-conf:amd64: Install libpam-fprintd:amd64: Install fprintd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 22 06:52:05 2021 ErrorMessage: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-03-29 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: fprintd Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 https://bugs.launchpad.net/bugs/1933188 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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 1933194] [NEW] lagg display
Public bug reported: lagg display ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 22 11:46:23 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3973] Subsystem: Device [03ea:1af4] InstallationDate: Installed on 2021-06-20 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera Bus 001 Device 006: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81AX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-55-generic root=UUID=dd6defad-6211-4700-8037-049192e91a9b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN41WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvr6SCN41WW:bd12/19/2018:br1.41:efr1.19:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933194 Title: lagg display Status in xorg package in Ubuntu: New Bug description: lagg display ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 22 11:46:23 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3973] Subsystem: Device [03ea:1af4] InstallationDate: Installed on 2021-06-20 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera Bus 001 Device 006: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81AX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-55-generic root=UUID=dd6defad-6211-4700-8037-049192e91a9b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN41WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.ec.firmware.release: 1.19 dmi.modalias:
[Touch-packages] [Bug 1932980] Re: window title in mate terminal not change after I logout from ssh
So it really depends on OpenSSH server version. I'm not sure how to correctly debug this issue, so I have added openssh package to this bug-report to get some comments from them. ** Also affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1932980 Title: window title in mate terminal not change after I logout from ssh Status in Ubuntu MATE: New Status in mate-terminal package in Ubuntu: New Status in openssh package in Ubuntu: New Bug description: I use Ubuntu Mate 20.04. I always update my system. When, I open mate terminal and login into my server via ssh, the window title is change to my server @. But, its not change after I logout. In this report I attach a proof. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1932980/+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