[Touch-packages] [Bug 1921562] Re: Intermittent hangs during ldap_search_ext when TLS enabled
To be clear the fix that was mentioned is in 2.4.49+dfsg-4 and later, 442 openldap (2.4.49+dfsg-4) unstable; urgency=medium ... 453 * Import upstream patch to properly retry gnutls_handshake() after it 454 returns GNUTLS_E_AGAIN. (ITS#8650) (Closes: #861838) Thereby groovy is fixed as well, marking that in the bug tasks. ** Also affects: openldap (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: openldap (Ubuntu Groovy) Status: New => Fix Released -- 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/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Focal: In Progress Status in openldap source package in Groovy: Fix Released Bug description: [Impact] When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit. [Test Plan] === When using openldap on 20.04, this bug causes failures in the SSSD LDAP backend, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up With the patched version, this should no longer be a problem. [Where Problems Could Occur] With this patch applied, there may be few edge cases in (and varying b/w) different versions of GnuTLS. And also some bits that are discussed in https://bugs.openldap.org/show_bug.cgi?id=8650. But that said, the patched version is already being run in production for over two weeks time (at the time of writing - 07/04/21). So I believe the SRU will clearly benefit from this and has lower risk of regression. [More Info] === A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+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 1921562] Re: Intermittent hangs during ldap_search_ext when TLS enabled
** Merge proposal linked: https://code.launchpad.net/~utkarsh/ubuntu/+source/openldap/+git/openldap/+merge/400754 -- 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/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Focal: In Progress Bug description: [Impact] When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit. [Test Plan] === When using openldap on 20.04, this bug causes failures in the SSSD LDAP backend, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up With the patched version, this should no longer be a problem. [Where Problems Could Occur] With this patch applied, there may be few edge cases in (and varying b/w) different versions of GnuTLS. And also some bits that are discussed in https://bugs.openldap.org/show_bug.cgi?id=8650. But that said, the patched version is already being run in production for over two weeks time (at the time of writing - 07/04/21). So I believe the SRU will clearly benefit from this and has lower risk of regression. [More Info] === A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/gdm3/+bug/1922414/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/gdm3/+bug/1922414/+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 1922989] Re: After some usage i get issue with gnome
*** This bug is a duplicate of bug 1922353 *** https://bugs.launchpad.net/bugs/1922353 Thanks for the bug report. I think this kind of looks like the issue described in bug 1922353 so we can group it there for now. It would be useful for more people to discuss the problem they see in a single place. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 1922353 Overview sometimes fail to appear or disappear and [JS ERROR: Error: Wrong type number; float expected. But it's out of range: -Infinity ... from _syncWorkspacesActualGeometry workspacesView.js:728] -- 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/1922989 Title: After some usage i get issue with gnome Status in gnome-shell package in Ubuntu: New Bug description: Hi i get unormaly windows on gnome when go to menu and charge programs did not know why its happing but i need to logout or reboot computer only happed one time yet. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Er en mappe: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Er en mappe: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Er en mappe: '/proc/driver/nvidia/gpus/:0a:00.0' .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.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: gcc version 10.2.1 20210401 (Ubuntu 10.2.1-24ubuntu1) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Ikke tilgang: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 06:25:29 2021 DistUpgraded: 2021-04-06 19:55:49,907 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: Fila eller mappa finnes ikke (1)) DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.67, 5.11.0-051100-generic, x86_64: installed nvidia, 460.67, 5.11.0-13-generic, x86_64: installed r8168, 8.048.03, 5.11.0-051100-generic, x86_64: installed r8168, 8.048.03, 5.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] InstallationDate: Installed on 2019-05-07 (701 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=ce175d2d-f51e-41b2-a88f-0adb7680b419 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-04-06 (1 days ago) dmi.bios.date: 07/28/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5603 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO 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.:bvr5603:bd07/28/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO: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 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 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/gnome-shell/+bug/1922989/+subscriptions
[Touch-packages] [Bug 1921562] Re: Intermittent hangs during ldap_search_ext when TLS enabled
** Description changed: + [Impact] + + When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as - https://bugs.openldap.org/show_bug.cgi?id=8650 which was fixed in - https://git.openldap.org/openldap/openldap/-/commit/735e1ab and was - released as part of version 2.4.50. This bug effects Ubuntu 20.04 LTS - and potentially earlier Ubuntu releases. Later Ubuntu releases use an - openldap version that is at least 2.4.50 and are therefore not affected. + https://bugs.openldap.org/show_bug.cgi?id=8650. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be + restart after a timeout has been hit. + + + [Test Plan] + === + + When using openldap on 20.04, this bug causes failures in the SSSD LDAP + backend, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up + + With the patched version, this should no longer be a problem. + + + [Where Problems Could Occur] + + + With this patch applied, there may be few edge cases in (and varying + b/w) different versions of GnuTLS. And also some bits that are discussed + in https://bugs.openldap.org/show_bug.cgi?id=8650. + + But that said, the patched version is already being run in production + for over two weeks time (at the time of writing - 07/04/21). So I + believe the SRU will clearly benefit from this and has lower risk of + regression. + + + [More Info] + === A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. - - As this bug affects all systems using LDAP with TLS, I suggest that the - fix for this bug is ported to Ubuntu 20.04 LTS and potentially earlier - versions. -- 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/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Focal: In Progress Bug description: [Impact] When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit. [Test Plan] === When using openldap on 20.04, this bug causes failures in the SSSD LDAP backend, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up With the patched version, this should no longer be a problem. [Where Problems Could Occur] With this patch applied, there may be few edge cases in (and varying b/w) different versions of GnuTLS. And also some bits that are discussed in https://bugs.openldap.org/show_bug.cgi?id=8650. But that said, the patched version is already being run in production for over two weeks time (at the time of writing - 07/04/21). So I believe the SRU will clearly benefit from this and has lower risk of regression. [More Info] === A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+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 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
This bug was fixed in the package libqofono - 0.90+16.10.20160901-0ubuntu3 --- libqofono (0.90+16.10.20160901-0ubuntu3) hirsute; urgency=medium * Remove build dependency on qt5-default, which no longer exists (LP: #1921781). -- Logan Rosen Wed, 07 Apr 2021 15:32:59 -0400 ** Changed in: libqofono (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: New Status in libqofono package in Ubuntu: Fix Released Status in poppler-qml-plugin package in Ubuntu: New Status in qtpowerd package in Ubuntu: New Status in qtubuntu-cameraplugin-fake package in Ubuntu: New Status in signon-keyring-extension package in Ubuntu: Fix Released Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1921562] Re: Intermittent hangs during ldap_search_ext when TLS enabled
Hello Vincent, I've uploaded a fixed package in my PPA: https://launchpad.net/~utkarsh/+archive/ubuntu/experimental-dump. Could you please test this if it work alright for you before I push this to the official archive? Thanks! ** Changed in: openldap (Ubuntu Focal) Assignee: (unassigned) => Utkarsh Gupta (utkarsh) ** Changed in: openldap (Ubuntu Focal) Status: Triaged => In Progress -- 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/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Focal: In Progress Bug description: When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650 which was fixed in https://git.openldap.org/openldap/openldap/-/commit/735e1ab and was released as part of version 2.4.50. This bug effects Ubuntu 20.04 LTS and potentially earlier Ubuntu releases. Later Ubuntu releases use an openldap version that is at least 2.4.50 and are therefore not affected. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. As this bug affects all systems using LDAP with TLS, I suggest that the fix for this bug is ported to Ubuntu 20.04 LTS and potentially earlier versions. To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+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 1922989] [NEW] After some usage i get issue with gnome
Public bug reported: Hi i get unormaly windows on gnome when go to menu and charge programs did not know why its happing but i need to logout or reboot computer only happed one time yet. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Er en mappe: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Er en mappe: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Er en mappe: '/proc/driver/nvidia/gpus/:0a:00.0' .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.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: gcc version 10.2.1 20210401 (Ubuntu 10.2.1-24ubuntu1) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Ikke tilgang: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 06:25:29 2021 DistUpgraded: 2021-04-06 19:55:49,907 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: Fila eller mappa finnes ikke (1)) DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.67, 5.11.0-051100-generic, x86_64: installed nvidia, 460.67, 5.11.0-13-generic, x86_64: installed r8168, 8.048.03, 5.11.0-051100-generic, x86_64: installed r8168, 8.048.03, 5.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] InstallationDate: Installed on 2019-05-07 (701 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=ce175d2d-f51e-41b2-a88f-0adb7680b419 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-04-06 (1 days ago) dmi.bios.date: 07/28/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5603 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO 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.:bvr5603:bd07/28/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO: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 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 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 possible-manual-nvidia-install ubuntu ** Attachment added: "Skjermdump fra 2021-04-07 22-14-36.png" https://bugs.launchpad.net/bugs/1922989/+attachment/5485407/+files/Skjermdump%20fra%202021-04-07%2022-14-36.png -- 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/1922989 Title: After some usage i get issue with gnome Status in xorg package in Ubuntu: New Bug description: Hi i get unormaly windows on gnome when go to menu and charge programs did not know why its happing but i need to logout or reboot computer only happed one time yet. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Er en mappe: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Er en mappe:
[Touch-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi
** Summary changed: - Bluez should notify users when they need to reboot to apply changes on arm64 + Bluez should notify users when they need to reboot to apply changes on Raspberry Pi -- 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/1922792 Title: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi Status in bluez package in Ubuntu: Triaged Bug description: In the case of upgrading bluez on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+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 1922543] Re: No sound, no audio profiles, until i do 'killall pulseaudio' (Asus Zenbook 14 UM431D, ALC294 Analog)
*** This bug is a duplicate of bug 1897965 *** https://bugs.launchpad.net/bugs/1897965 ** This bug has been marked a duplicate of bug 1897965 PulseAudio doesn't work when pipewire is installed (ie. KDE) -- 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/1922543 Title: No sound, no audio profiles, until i do 'killall pulseaudio' (Asus Zenbook 14 UM431D, ALC294 Analog) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello. Since i installed KUbuntu 20.10 i have an issue with the audio system. Every time i boot the system, the system audio profiles and devices are not recognized correctly, and normally there isn't an output audio at all and no sound. However, if i do a "killall pulseaudio", suddenly everything appears in the KDE audio profiles and the sound becomes available. My laptop (Asus Zenbook UM431DA, ALC294 Analog) have 4 speakers: 2 in front (in both sides of the keyboard) and 2 in the back. It have also a HDMI Audio output which is not recognized. But like i said, if i do a "killall pulseaudio" everything appears, including the HDMI audio, and all the expected audio profiles (Stereo, Stereo Duplex, 2.1, 4.0... all with variants with and without input). If i don't do that, all i have is "Off" and "Input Analog". With the KUbuntu 20.10 LiveUSB (Kernel 5.8.0-25) i didn't have the issue (every boot brings all profiles) but since i installed in the laptop (early installed Kernel was 5.8.0-31) i have the issue. Actually i have kernel 5.8.0-44, the last official one from Ubuntu, and everything is exactly the same. I tried too using kernels via Ubuntu Mainline Kernel Installer, and i had some differences with newer kernels. I was updating once in a while from there, and at some point, i can be sure, the kernel could bring at boot a different list of available profiles (sometimes only input, other only Stereo, or Stereo + 2.1, or Stereo + 2.1 + 4.0... each one with the input option) and sometimes the HDMI audio appears and sometimes don't. But in all cases, if i do "killall pulseaudio", all profiles come back. However, Kernel 5.11.4 from mainline was the last one with that behaviour. 5.11.5 do the same as 5.8.0-44, every time at boot the only profiles are "Off" and "Input Analog". Actually i have 5.12.0-051200rc5 with exact the same results. Using "pasuspender -- aplay -Dplughw:1 example.wav" to bypass PulseAudio gives me sound in every case. Also i have an issue (maybe related) with ALSA about i can't adjust the volume from back speakers (between 1%~100% are always 100%, between 100%~150% works) and front speakers have a low volume. But it's directly related to ALSA because with pasuspender the behaviour is the same. I reported that here https://bugzilla.kernel.org/show_bug.cgi?id=212547. I can provide alsa-info and dmesg from 5.8.0-44 (last official one from Ubuntu), but also from 5.8.0-25 (from KUbuntu LiveUSB), and a complete collection of alsa-info, dmesg and image of KDE audio profiles from 5.11.0 (A kernel with the behaviour of different options with every boot). Further, i can add alsa-info before and after "killall pulseaudio", and data from 5.11.4 and 5.11.5, or 5.12.0-051200rc5, which is the last one available in mainline. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1922543/+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 1874824] Autopkgtest regression report (procps/2:3.3.16-1ubuntu2.1)
All autopkgtests for the newly accepted procps (2:3.3.16-1ubuntu2.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: ranger/1.9.3-1build1 (s390x) xpra/3.0.6+dfsg1-1build1 (amd64) reprotest/0.7.14 (ppc64el, amd64) s3ql/3.3.2+dfsg-1ubuntu1 (armhf) apport/2.20.11-0ubuntu27.16 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#procps [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: Fix Committed Status in procps source package in Groovy: Fix Committed Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
> I suspected that this patch https://github.com/systemd/systemd/pull/16982 solved the issue. can you explain *why* you suspect that fixes your problem? -- 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/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Invalid Status in systemd source package in Groovy: Invalid Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+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 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
This bug was fixed in the package signon-keyring-extension - 0.6+14.10.20140513-0ubuntu3 --- signon-keyring-extension (0.6+14.10.20140513-0ubuntu3) hirsute; urgency=medium * Remove build dependency on qt5-default, which no longer exists (LP: #1921781). -- Logan Rosen Wed, 07 Apr 2021 15:44:36 -0400 ** Changed in: signon-keyring-extension (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: New Status in libqofono package in Ubuntu: New Status in poppler-qml-plugin package in Ubuntu: New Status in qtpowerd package in Ubuntu: New Status in qtubuntu-cameraplugin-fake package in Ubuntu: New Status in signon-keyring-extension package in Ubuntu: Fix Released Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1642634] Re: indicator-datetime uses excessive memory
Confirm that this bug is still alive and kicking on Ubuntu 20.04. This effectively prevents using Ubuntu as a business OS... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1642634 Title: indicator-datetime uses excessive memory Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: On my Aquaris 4.5, OTA-13, indicator-datetime 15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS is 315892, almost three times as much as unity8. I believe this is an OTA regression. I'm not sure if it regressed from OTA-11 or OTA-12. Just now, I got caught in an oom killer loop with constant killing of unity8-dash because of this, making my phone unusable. I had to kill indicator-datetime manually. It then restarted automatically and now uses 80456 RSS only. I see bug 1633319 exists complaining about a memory leak. It's not exactly the same version since mine is 15.10+15.04.20160820.1-0ubuntu1 and that one is 15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are the same or something? Perhaps the two are dupes, but I'll let someone more familiar make that determination. I have only a handful of alarms (perhaps five on average; rarely more) but I do have my Google calendar syncing with perhaps hundreds of events. However, there's no reason that this should cause indicator- datetime to use more RSS; it shouldn't be keeping these in memory. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
On Tue, Apr 06, 2021 at 10:56:02AM -, Khurshid Alam wrote: > What is alternet meta package which pulls default version of qt hirsute? There is none. There is no longer any non-default qt version supported, so the qtchooser logic is no longer needed. Build-Depend on the relevant qt5 devel packages instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: New Status in libqofono package in Ubuntu: New Status in poppler-qml-plugin package in Ubuntu: New Status in qtpowerd package in Ubuntu: New Status in qtubuntu-cameraplugin-fake package in Ubuntu: New Status in signon-keyring-extension package in Ubuntu: New Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1915502] Re: "systemd --user" fails to start for non-local users
Dan, thanks for the comments, appreciate it. In reply: Using only "compat" in /etc/nsswitch.conf is legitimate and we use it without issue on multiple Linux distributions as well as older Ubuntu releases. It invokes a different behaviour to using "nis", allowing more fine grained control of who can authenticate from the NIS database by appending +user|+netgroup to /etc/passwd. FWIW, replacing "compat" with "nis" and removing the + entries at the end of the passwd file yields the same systemd behaviour. Earlier in testing I tried using sssd, going direct to AD, cutting out NIS entirely. Using sssd also failed to start the systemd user context. I will try that again tomorrow with the debug flags to see that shows up anything new. getent passwd amcvey responds immediately and correctly, suggesting the underlying calls to getpwnam() are also working correctly. All other NIS accounts are also resolved correctly and without delay. I don't think using nscd will help much here, the issue is not the response time from the NIS server(s) or the number of calls being made. This also makes me think that the bug you referenced (https://github.com/systemd/systemd/issues/12702) is not the root cause here, as there are performance issues in that use case, which I'm not seeing here at all. -- 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/1915502 Title: "systemd --user" fails to start for non-local users Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Bug description: systemd-logind fails to start the systemd --user process for non-local users on Ubuntu 20.04. This is a reproducible problem; all our systems are displaying the same symptoms. The systems are using Kerberos (Active Directory) for authentication, and NIS for account meta-data and authorisation (groups) A base installation is performed using the server 20.04 ISO image. No additional packages are selected. Post-install, I run: apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd I set up the NIS client (supply the default domain name, check ypbind is running and ypcat passwd is working) I then set up /etc/krb5.conf for kerberos authentication to a domain controller, confirm that kinit works and a kerberos ticket is issued. I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to the end of each. /etc/nsswitch.conf is modified to support compat mode, as well as systemd: passwd: compat systemd group: compat systemd shadow: compat I can log in remotely via ssh using my NIS account and Kerberos credentials. MY NIS meta-data looks like: amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh (where UID and GID are replaced with values unique to the organisation) On login, the following occurs: hostname:~> systemctl --user Failed to connect to bus: No such file or directory I put pam-systemd and systemd-logind into debug mode to get more information: Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from [redact] port 58849 ssh2: RSA SHA256:[redact] Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened for user amcvey by (uid=0) Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd initializing Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user desktop= seat= vtnr=0 tty= display= remote=yes remote_user= remote_host=10.105.121.110 Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41 reply_cookie=0 signature=s error-name=n/a error-message=n/a
[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment
** Branch linked: lp:~ubuntu-core-dev/ubuntu/hirsute/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Won't Fix Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1922937] Re: reading casper-md5check.json fails
** Branch linked: lp:~ubuntu-core-dev/ubuntu/hirsute/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1922937 Title: reading casper-md5check.json fails Status in apport package in Ubuntu: In Progress Status in apport source package in Hirsute: In Progress Bug description: bdmurray@clean-hirsute-amd64:/tmp$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 995, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1922937/+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 1866180] Re: Re-Upload in to Focal
** Changed in: hud (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1866180 Title: Re-Upload in to Focal Status in hud package in Ubuntu: Fix Released Bug description: Hud was removed in LP: #1850748 due to python dependency. The merge request attached fixes that issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1866180/+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 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: New Status in libqofono package in Ubuntu: New Status in poppler-qml-plugin package in Ubuntu: New Status in qtpowerd package in Ubuntu: New Status in qtubuntu-cameraplugin-fake package in Ubuntu: New Status in signon-keyring-extension package in Ubuntu: New Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1922792] Re: Bluez should notify users when they need to reboot to apply changes on arm64
Attached is a patch for Hirsute. If this is accepted I will SRU to focal and groovy. ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) ** Patch added: "Hirsute Patch" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+attachment/5485323/+files/lp1922792.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/1922792 Title: Bluez should notify users when they need to reboot to apply changes on arm64 Status in bluez package in Ubuntu: Triaged Bug description: In the case of upgrading bluez on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
Looks like /etc/X11/Xsession is not executed, but the files in /etc/X11/Xsession.d/ are sourced somehow. My best guess is that there's some other mechanism emulating Xsession's behaviour but without defining has_option. Maybe this is a pending bug introduced in an earlier version of Ubuntu that has come to light just now, after has_option has been moved as #3 points out. BTW: I'm using lightdm with the Arctica Greeter. -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/gdm3/+bug/1922414/+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 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0
** Also affects: unity-china-video-scope (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-scope-video-remote (Ubuntu) Importance: Undecided Status: New ** Also affects: libzeitgeist (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-lens-files Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart-app-launch in Ubuntu. https://bugs.launchpad.net/bugs/1197569 Title: Move from zeitgeist-1.0 to zeitgeist-2.0 Status in Bijiben: Fix Released Status in Cairo-Dock Plug-ins: Fix Released Status in Diodon: Fix Released Status in Scratch: Fix Released Status in Totem: Fix Released Status in Ubuntu Application Launcher: Fix Released Status in Unity: Fix Released Status in unity-lens-applications: In Progress Status in unity-lens-files: Fix Released Status in Unity Videos Lens: In Progress Status in activity-log-manager package in Ubuntu: Fix Released Status in bijiben package in Ubuntu: Fix Released Status in cairo-dock-plug-ins package in Ubuntu: Fix Released Status in diodon package in Ubuntu: Fix Released Status in folks package in Ubuntu: Fix Released Status in libzeitgeist package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in synapse package in Ubuntu: Fix Released Status in totem package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-china-video-scope package in Ubuntu: New Status in unity-lens-applications package in Ubuntu: In Progress Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: In Progress Status in unity-scope-video-remote package in Ubuntu: New Status in upstart-app-launch package in Ubuntu: Fix Released Bug description: The older libzeitgeist (http://launchpad.net/libzeitgeist) served its days and will be deprecated soon. All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0) To manage notifications about this bug go to: https://bugs.launchpad.net/bijiben/+bug/1197569/+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 1521989] Re: Please remove libzeitgeist from the archive
*** This bug is a duplicate of bug 1197569 *** https://bugs.launchpad.net/bugs/1197569 ** Description changed: libzeitgeist-1.0-1 is superseded by libzeitgeist-2.0-0 which is built by zeitgeist with a slightly different API. All rpdends must transition to it: - unity-china-video-scope, unity-lens-applications, unity-lens-video + unity-china-video-scope, unity-lens-applications, unity-lens-video, unity-scope-video-remote ** Also affects: unity-china-video-scope (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-lens-applications (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-lens-video (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-scope-video-remote (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1197569 Move from zeitgeist-1.0 to zeitgeist-2.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libzeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1521989 Title: Please remove libzeitgeist from the archive Status in libzeitgeist package in Ubuntu: New Status in unity-china-video-scope package in Ubuntu: New Status in unity-lens-applications package in Ubuntu: New Status in unity-lens-video package in Ubuntu: New Status in unity-scope-video-remote package in Ubuntu: New Bug description: libzeitgeist-1.0-1 is superseded by libzeitgeist-2.0-0 which is built by zeitgeist with a slightly different API. All rpdends must transition to it: unity-china-video-scope, unity-lens-applications, unity-lens-video, unity-scope-video-remote To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzeitgeist/+bug/1521989/+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 1922937] Re: reading casper-md5check.json fails
** Tags added: fr-1268 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1922937 Title: reading casper-md5check.json fails Status in apport package in Ubuntu: In Progress Status in apport source package in Hirsute: In Progress Bug description: bdmurray@clean-hirsute-amd64:/tmp$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 995, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1922937/+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 1683576] Re: cd with multiple directory argument fails
This is still broken in Ubuntu 18.04.5 LTS / GNU bash, version 4.4.20(1)-release and in Ubuntu 20.04.1 LTS / GNU bash, version 5.0.17(1)-release. The manual pages for Bash 4.2, Bash 4.4 and Bash 5.0 all specify "Any additional arguments following dir are ignored. (Only bash 4.2 works correctly.) This is a bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1683576 Title: cd with multiple directory argument fails Status in bash package in Ubuntu: Confirmed Bug description: In bash 4.4, a new behaviour was introduced for cd, where it would complain if multiple arguments are provided. From config-top.h [1]: /* Define CD_COMPLAINS if you want the non-standard, but sometimes-desired error messages about multiple directory arguments to `cd'. */ #define CD_COMPLAINS It seems like this is enabled for Ubuntu. However, this behaviour conflicts with the manual (both Ubuntu's and GNU's), which says something similar to: "Any additional arguments following directory are ignored." Please revert to the old behaviour, or correct the manual. This is not a user-configurable setting, and push is also affected. Ubuntu 17.04 bash 4.4-2ubuntu1 [1]: http://git.savannah.gnu.org/cgit/bash.git/tree/config-top.h#n30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1683576/+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 1922951] [NEW] SRU the current 3.36.5 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade ** Affects: evolution-data-server (Ubuntu) Importance: Low Status: Fix Released ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Low ** Changed in: evolution-data-server (Ubuntu) Status: New => Fix Released -- 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/1922951 Title: SRU the current 3.36.5 stable update Status in evolution-data-server package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1922951/+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 1922947] Re: package libglib2.0-data 2.48.0-1ubuntu4 failed to install/upgrade: package libglib2.0-data is not ready for configuration cannot configure (current status 'half-inst
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1922947 Title: package libglib2.0-data 2.48.0-1ubuntu4 failed to install/upgrade: package libglib2.0-data is not ready for configuration cannot configure (current status 'half-installed') Status in glib2.0 package in Ubuntu: New Bug description: I can't download up-dates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-data 2.48.0-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 Uname: Linux 4.4.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed Apr 7 15:56:31 2021 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DuplicateSignature: Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package libglib2.0-data (--configure): package libglib2.0-data is not ready for configuration ErrorMessage: package libglib2.0-data is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2021-01-18 (78 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.10ubuntu1 SourcePackage: glib2.0 Title: package libglib2.0-data 2.48.0-1ubuntu4 failed to install/upgrade: package libglib2.0-data is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1922947/+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 1922947] [NEW] package libglib2.0-data 2.48.0-1ubuntu4 failed to install/upgrade: package libglib2.0-data is not ready for configuration cannot configure (current status 'half-in
Public bug reported: I can't download up-dates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-data 2.48.0-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 Uname: Linux 4.4.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed Apr 7 15:56:31 2021 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DuplicateSignature: Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package libglib2.0-data (--configure): package libglib2.0-data is not ready for configuration ErrorMessage: package libglib2.0-data is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2021-01-18 (78 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.10ubuntu1 SourcePackage: glib2.0 Title: package libglib2.0-data 2.48.0-1ubuntu4 failed to install/upgrade: package libglib2.0-data is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1922947 Title: package libglib2.0-data 2.48.0-1ubuntu4 failed to install/upgrade: package libglib2.0-data is not ready for configuration cannot configure (current status 'half-installed') Status in glib2.0 package in Ubuntu: New Bug description: I can't download up-dates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-data 2.48.0-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 Uname: Linux 4.4.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed Apr 7 15:56:31 2021 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DuplicateSignature: Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package libglib2.0-data (--configure): package libglib2.0-data is not ready for configuration ErrorMessage: package libglib2.0-data is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2021-01-18 (78 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.10ubuntu1 SourcePackage: glib2.0 Title: package libglib2.0-data 2.48.0-1ubuntu4 failed to install/upgrade: package libglib2.0-data is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1922947/+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 1922543] Re: No sound, no audio profiles, until i do 'killall pulseaudio' (Asus Zenbook 14 UM431D, ALC294 Analog)
I uninstalled pipewire (0.3.10-4) and the profiles are always the ones they should at every boot. I tried to install again pipewire and the "changing profiles at every boot" appeared again. So, it's the source of the issue. I don't know if it was installed by the base Ubuntu or KDE/Kubuntu, or any program i tested (i don't have any of its inverse dependencies installed) so i will keep it uninstalled, and if is installed in the new (K)Ubuntu version (hirsute) it should be a fixed version (It will install >0.3.24-3, and in the issue you linked it seems it fixed in 0.3.19-3). Thanks to put me in the right path. -- 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/1922543 Title: No sound, no audio profiles, until i do 'killall pulseaudio' (Asus Zenbook 14 UM431D, ALC294 Analog) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello. Since i installed KUbuntu 20.10 i have an issue with the audio system. Every time i boot the system, the system audio profiles and devices are not recognized correctly, and normally there isn't an output audio at all and no sound. However, if i do a "killall pulseaudio", suddenly everything appears in the KDE audio profiles and the sound becomes available. My laptop (Asus Zenbook UM431DA, ALC294 Analog) have 4 speakers: 2 in front (in both sides of the keyboard) and 2 in the back. It have also a HDMI Audio output which is not recognized. But like i said, if i do a "killall pulseaudio" everything appears, including the HDMI audio, and all the expected audio profiles (Stereo, Stereo Duplex, 2.1, 4.0... all with variants with and without input). If i don't do that, all i have is "Off" and "Input Analog". With the KUbuntu 20.10 LiveUSB (Kernel 5.8.0-25) i didn't have the issue (every boot brings all profiles) but since i installed in the laptop (early installed Kernel was 5.8.0-31) i have the issue. Actually i have kernel 5.8.0-44, the last official one from Ubuntu, and everything is exactly the same. I tried too using kernels via Ubuntu Mainline Kernel Installer, and i had some differences with newer kernels. I was updating once in a while from there, and at some point, i can be sure, the kernel could bring at boot a different list of available profiles (sometimes only input, other only Stereo, or Stereo + 2.1, or Stereo + 2.1 + 4.0... each one with the input option) and sometimes the HDMI audio appears and sometimes don't. But in all cases, if i do "killall pulseaudio", all profiles come back. However, Kernel 5.11.4 from mainline was the last one with that behaviour. 5.11.5 do the same as 5.8.0-44, every time at boot the only profiles are "Off" and "Input Analog". Actually i have 5.12.0-051200rc5 with exact the same results. Using "pasuspender -- aplay -Dplughw:1 example.wav" to bypass PulseAudio gives me sound in every case. Also i have an issue (maybe related) with ALSA about i can't adjust the volume from back speakers (between 1%~100% are always 100%, between 100%~150% works) and front speakers have a low volume. But it's directly related to ALSA because with pasuspender the behaviour is the same. I reported that here https://bugzilla.kernel.org/show_bug.cgi?id=212547. I can provide alsa-info and dmesg from 5.8.0-44 (last official one from Ubuntu), but also from 5.8.0-25 (from KUbuntu LiveUSB), and a complete collection of alsa-info, dmesg and image of KDE audio profiles from 5.11.0 (A kernel with the behaviour of different options with every boot). Further, i can add alsa-info before and after "killall pulseaudio", and data from 5.11.4 and 5.11.5, or 5.12.0-051200rc5, which is the last one available in mainline. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1922543/+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 1920837] Re: apport bugs from official raspi or riscv images are not identified
I've gone ahead and went with the /proc/device-tree/compatible - thanks for the patch Dave! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1920837 Title: apport bugs from official raspi or riscv images are not identified Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: In Progress Status in apport source package in Groovy: In Progress Bug description: It would be helpful if bugs reported from images for Raspberry Pi's or RISCV systems were tagged so that one could search for bugs from systems running those images e.g. 'raspi-image'. [Test Case] After installing a preinstalled image of Ubuntu for Raspberry Pi do the following: 1) run 'ubuntu-bug apport' 2) view the bug report and check the Tags field With the current version of apport you will not see the tag 'raspi-image'. With the version of apport in -proposed you will see the tag 'raspi-image'. [Where problems could occur] If the code being added is syntactically incorrect then we'd see a Traceback which would be bad as it could affect all bug / crash reports. [Other Info] Since there aren't any Groovy images for RISC-V there will be nothing to test there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+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 1874824] Please test proposed package
Hello Sven, or anyone else affected, Accepted procps into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/procps/2:3.3.16-5ubuntu2.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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: procps (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: Fix Committed Status in procps source package in Groovy: Fix Committed Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1874824] Please test proposed package
Hello Sven, or anyone else affected, Accepted procps into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/procps/2:3.3.16-1ubuntu2.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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: Fix Committed Status in procps source package in Groovy: Fix Committed Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
Ah, sorry, my mistake. I didn't think that pgrep.c would be used for a different command. Now I see that pkill is a symlink to pgrep in /usr/bin. ** Changed in: procps (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: Fix Committed Status in procps source package in Groovy: Fix Committed Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1922937] [NEW] reading casper-md5check.json fails
Public bug reported: bdmurray@clean-hirsute-amd64:/tmp$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 995, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' ** Affects: apport (Ubuntu) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Affects: apport (Ubuntu Hirsute) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Also affects: apport (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Hirsute) Status: New => In Progress ** Changed in: apport (Ubuntu Hirsute) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Hirsute) Milestone: None => ubuntu-21.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1922937 Title: reading casper-md5check.json fails Status in apport package in Ubuntu: In Progress Status in apport source package in Hirsute: In Progress Bug description: bdmurray@clean-hirsute-amd64:/tmp$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 995, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1922937/+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 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
Robie, pgrep and pkill are sharing the same code. Essentially pkill runs pgrep and then issues a kill signal to the resulting pid. Therefore this fix applies to both pkill and pgrep. Additionally, the source of the problem comes from the behavior of `sysconf(_SC_ARG_MAX)` changing in newer kernels. This function call only exists in one place in the procps codebase, so no other commands are affected by the same issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Groovy: In Progress Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1915502] Re: "systemd --user" fails to start for non-local users
First, from re-reading the bug description, it seems like you don't have nis in your nsswitch.conf file? I'm not an expert in NIS config/usage, but I think you need to add that, e.g. at *least*: passwd: compat nis systemd you might need to add it to group, shadow, and gshadow as well. Second, does getent work? If not, that's most likely your problem; e.g.: $ getent passwd 198083 Third, you could try setting up nscd if you haven't already, which may help if your NIS lookups are slow. Finally note that this upstream systemd bug appears to match your problem, and the conclusion there was the problem is either a local config issue or NIS bug: https://github.com/systemd/systemd/issues/12702 ** Bug watch added: github.com/systemd/systemd/issues #12702 https://github.com/systemd/systemd/issues/12702 ** Changed in: systemd (Ubuntu Focal) Status: New => Incomplete -- 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/1915502 Title: "systemd --user" fails to start for non-local users Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Bug description: systemd-logind fails to start the systemd --user process for non-local users on Ubuntu 20.04. This is a reproducible problem; all our systems are displaying the same symptoms. The systems are using Kerberos (Active Directory) for authentication, and NIS for account meta-data and authorisation (groups) A base installation is performed using the server 20.04 ISO image. No additional packages are selected. Post-install, I run: apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd I set up the NIS client (supply the default domain name, check ypbind is running and ypcat passwd is working) I then set up /etc/krb5.conf for kerberos authentication to a domain controller, confirm that kinit works and a kerberos ticket is issued. I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to the end of each. /etc/nsswitch.conf is modified to support compat mode, as well as systemd: passwd: compat systemd group: compat systemd shadow: compat I can log in remotely via ssh using my NIS account and Kerberos credentials. MY NIS meta-data looks like: amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh (where UID and GID are replaced with values unique to the organisation) On login, the following occurs: hostname:~> systemctl --user Failed to connect to bus: No such file or directory I put pam-systemd and systemd-logind into debug mode to get more information: Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from [redact] port 58849 ssh2: RSA SHA256:[redact] Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened for user amcvey by (uid=0) Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd initializing Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user desktop= seat= vtnr=0 tty= display= remote=yes remote_user= remote_host=10.105.121.110 Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to create session: No such process Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to
[Touch-packages] [Bug 1903874] Re: [21.04 FEAT] Upgrade binutils to latest version 2.35.1
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1903874 Title: [21.04 FEAT] Upgrade binutils to latest version 2.35.1 Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: Update binutils to latest version. Currently 2.35.1 was made available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903874/+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 1922926] [NEW] Battery applet not updated after sleep
Public bug reported: Ubuntu Budgie 21.04. On battery, for example, battery says 40%. Close lid of laptop and then plug the laptop into AC. Open laptop on AC and applet still says 40% and gives no indication of being on AC. Disconnect AC and reconnect AC no change. The applet uses Upower to respond to battery events. So whatever is feeding Upower isnt being updated after a resume. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: upower 0.99.11-2 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Wed Apr 7 07:17:27 2021 InstallationDate: Installed on 2020-04-18 (353 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) SourcePackage: upower UpgradeStatus: Upgraded to hirsute on 2021-03-28 (9 days ago) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1922926 Title: Battery applet not updated after sleep Status in upower package in Ubuntu: New Bug description: Ubuntu Budgie 21.04. On battery, for example, battery says 40%. Close lid of laptop and then plug the laptop into AC. Open laptop on AC and applet still says 40% and gives no indication of being on AC. Disconnect AC and reconnect AC no change. The applet uses Upower to respond to battery events. So whatever is feeding Upower isnt being updated after a resume. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: upower 0.99.11-2 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Wed Apr 7 07:17:27 2021 InstallationDate: Installed on 2020-04-18 (353 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) SourcePackage: upower UpgradeStatus: Upgraded to hirsute on 2021-03-28 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1922926/+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 1915502] Re: "systemd --user" fails to start for non-local users
Below is contents of /var/log/syslog right at the point I press return
on entering the password. I've removed the systemd-resolved messages as
all they're showing is the response from the kerberos service, which is
clean.
Apr 7 12:28:45 myhostname systemd[1]: n/a: New incoming connection.
Apr 7 12:28:45 myhostname systemd[1]: n/a: Connections of user 0: 0 (of 1024
max)
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: setting state
idle-server
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: New incoming message:
{"method":"io.systemd.UserDatabase.GetMemberships","parameters":{"userName":"amcvey","service":"io.systemd.DynamicUser"},"more":true}
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
idle-server → processing-method-more
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: Sending message:
{"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
processing-method-more → processed-method
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
processed-method → idle-server
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: Got POLLHUP from socket.
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
idle-server → pending-disconnect
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
pending-disconnect → processing-disconnect
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
processing-disconnect → disconnected
Apr 7 12:28:45 myhostname systemd[1]: n/a: New incoming connection.
Apr 7 12:28:45 myhostname systemd[1]: n/a: Connections of user 0: 0 (of 1024
max)
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: setting state
idle-server
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: New incoming message:
{"method":"io.systemd.UserDatabase.GetMemberships","parameters":{"userName":"amcvey","service":"io.systemd.DynamicUser"},"more":true}
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
idle-server → processing-method-more
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: Sending message:
{"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
processing-method-more → processed-method
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
processed-method → idle-server
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: Got POLLHUP from socket.
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
idle-server → pending-disconnect
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
pending-disconnect → processing-disconnect
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
processing-disconnect → disconnected
Apr 7 12:28:45 myhostname systemd[1]: n/a: New incoming connection.
Apr 7 12:28:45 myhostname systemd[1]: n/a: Connections of user 0: 0 (of 1024
max)
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: setting state
idle-server
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: New incoming message:
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"userName":"amcvey","service":"io.systemd.DynamicUser"}}
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
idle-server → processing-method
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: Sending message:
{"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
processing-method → processed-method
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
processed-method → idle-server
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: Got POLLHUP from socket.
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
idle-server → pending-disconnect
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
pending-disconnect → processing-disconnect
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
processing-disconnect → disconnected
Apr 7 12:28:45 myhostname systemd[1]: n/a: New incoming connection.
Apr 7 12:28:45 myhostname systemd[1]: n/a: Connections of user 0: 0 (of 1024
max)
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: setting state
idle-server
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: New incoming message:
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":198083,"service":"io.systemd.DynamicUser"}}
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
idle-server → processing-method
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: Sending message:
{"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Apr 7 12:28:45 myhostname systemd[1]: varlink-55: varlink: changing state
processing-method → processed-method
[Touch-packages] [Bug 1908818] Re: pure packaging of libnss3
Hello Sergey, or anyone else affected,
Accepted nss into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nss/2:3.55-1ubuntu3.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: nss (Ubuntu Groovy)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1908818
Title:
pure packaging of libnss3
Status in nss package in Ubuntu:
Fix Released
Status in nss source package in Groovy:
Fix Committed
Status in nss source package in Hirsute:
Fix Released
Bug description:
[Impact]
* A packaging error in the current version has led library symlinks
to be broken and in the wrong place.
* Fix by applying the later change to Groovy as well
[Test Plan]
* install libnss3
* check (path depends on the architecture) the lib links
$ dpkg -L libnss3 | grep MULTIARCH
# ^^ should be empty
$ ll /usr/lib/x86_64-linux-gnu/libfreebl3.so
# vv should look like that:
lrwxrwxrwx 1 root root 17 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
root@h:~# ll /usr/lib/x86_64-linux-gnu/libfreebl*
lrwxrwxrwx 1 root root 18 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.chk -> nss/libfreebl3.chk
lrwxrwxrwx 1 root root 17 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
lrwxrwxrwx 1 root root 22 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.chk -> nss/libfreeblpriv3.chk
lrwxrwxrwx 1 root root 21 Feb 16 15:18
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so
[Where problems could occur]
* I first was afraid, that no matter how bad the paths would
have been we'd need to retain them for anyone using them
already. But the existing links go into nowhere since they
are relative therefore the regression risk should be minimal
root@g:~# ll '/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk'
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk'
lrwxrwxrwx 1 root root 18 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk' -> nss/libfreebl3.chk
lrwxrwxrwx 1 root root 17 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so' -> nss/libfreebl3.so
lrwxrwxrwx 1 root root 22 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk' -> nss/libfreeblpriv3.chk
lrwxrwxrwx 1 root root 21 Sep 29 2020
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so' -> nss/libfreeblpriv3.so
* never the less, to be clear - if problems occur they would be in
loading these libraries. E.g. a user could have had this package
and a self built nss on his system, after the change it might load the
packaged one.
[Other Info]
* n/a
---
dpkg -L libnss3
/.
/usr
/usr/lib
/usr/lib/${DEB_HOST_MULTIARCH}
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
/usr/lib/x86_64-linux-gnu/nss
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
/usr/share
/usr/share/doc
/usr/share/doc/libnss3
/usr/share/doc/libnss3/changelog.Debian.gz
/usr/share/doc/libnss3/copyright
/usr/share/lintian
/usr/share/lintian/overrides
[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
> The problem is the same for other popular tools like pkill from the same package. The SRU uploads fix pgrep, but not pkill. Isn't pkill also affected? Rather than fixing that in a separate SRU causing users to have to update twice, should we be fixing both at the same time? Or are you intending to never fix pkill in an SRU? Are there any other commands affected by the same issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Groovy: In Progress Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+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 1922548] Re: Error accessing Home of another user [Oops! Something went wrong. Unhandled error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject
Seems it was broken due to the changes in https://gitlab.gnome.org/GNOME/gvfs/-/issues/515 ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #515 https://gitlab.gnome.org/GNOME/gvfs/-/issues/515 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1922548 Title: Error accessing Home of another user [Oops! Something went wrong. Unhandled error message: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject does not have uid set] Status in PolicyKit: Unknown Status in nautilus package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Bug description: On my PC I have some different users. If from one user I try to access the Home directory of a different user I enter the password and then I have a crash. Seen attached screenshot. Problem happens with both x11 and Wayland sessions. More: opening this bug I have the messages: corrado@corrado-n2-hh-0402:~$ ubuntu-bug -w ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 227, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 945, in attach_casper_md5check with open(location) as json_file: PermissionError: [Errno 13] Permission denied: '/var/log/installer/casper-md5check.json' corrado@corrado-n2-hh-0402:~$ [GFX1-]: glxtest: Could not connect to wayland socket ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 12:05:27 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1137, 611)' InstallationDate: Installed on 2021-04-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.39.2-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/policykit/+bug/1922548/+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 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
This bug was fixed in the package signon-ui - 0.17+18.04.20171027+really20160406-0ubuntu3 --- signon-ui (0.17+18.04.20171027+really20160406-0ubuntu3) hirsute; urgency=medium * Remove build dependency on qt5-default, which no longer exists (LP: #1921781). -- Logan Rosen Tue, 06 Apr 2021 23:43:03 -0400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler-qml-plugin in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: New Status in libqofono package in Ubuntu: New Status in poppler-qml-plugin package in Ubuntu: New Status in qtpowerd package in Ubuntu: New Status in qtubuntu-cameraplugin-fake package in Ubuntu: New Status in signon-keyring-extension package in Ubuntu: New Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
This bug was fixed in the package signon-plugin-sasl - 0.1+16.04.20151203-0ubuntu2 --- signon-plugin-sasl (0.1+16.04.20151203-0ubuntu2) hirsute; urgency=medium * Remove build dependency on qt5-default, which no longer exists (LP: #1921781). -- Logan Rosen Tue, 06 Apr 2021 23:54:01 -0400 ** Changed in: signon-plugin-sasl (Ubuntu) Status: New => Fix Released ** Changed in: signon-ui (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler-qml-plugin in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: New Status in libqofono package in Ubuntu: New Status in poppler-qml-plugin package in Ubuntu: New Status in qtpowerd package in Ubuntu: New Status in qtubuntu-cameraplugin-fake package in Ubuntu: New Status in signon-keyring-extension package in Ubuntu: New Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
I can confirm the workaround by boxeus works on Ubuntu 20.04 LTS. To
improve on that, the lines can be added to the /etc/dropbear-
initramfs/config config file instead to avoid upgrade issues. It is
loaded towards the end of /usr/share/initramfs-tools/scripts/init-
bottom/dropbear anyway.
Automation two-liner:
echo -e "rm /run/net-*.conf\nrm /run/netplan/*.yaml" >>
/etc/dropbear-initramfs/config
update-initramfs -u
After that, netplan actually works again.
--
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/1813394
Title:
DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
Status in dropbear package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
On bionic, setting the network interface up (e.g. eno1) with DHCP now
causes a /run/netplan/eno1.yaml and a /run/net-eno1.conf file to be
written. The former gets imported by netplan after boot and causes the
DHCP lease from the initrd to be around forever, which I think goes
against the intent of DROPBEAR_IFDOWN=*.
I have brewed up a workaround script that lives in /etc/initramfs-
tools/scripts/init-bottom/hack-delete-netif-netplan.sh for now:
8< cut >8
#!/bin/sh
PREREQ=""
prereqs() {
echo "$PREREQ"
}
case "$1" in
prereqs)
prereqs
exit 0
;;
esac
. /scripts/functions
log_begin_msg "Deleting all network configuration that systemd could try to
import"
rm /run/net-*.conf
rm /run/netplan/*.yaml
log_end_msg
8< cut >8
I think that dropbear-intiramfs's init-bottom script should do this in
addition to downing the interfaces that it finds via the
DROPBEAR_IFDOWN pattern. Do you agree?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
We'll see, Fedora 34 seems to have switched to Pipewire, and F34 is in my near future, so I'll be experimenting. Am Mi., 7. Apr. 2021 um 11:51 Uhr schrieb Luis Alberto Pabón < 1838...@bugs.launchpad.net>: > That would be for 21.10 at this point yes? > > I wonder, how close/far is Ubuntu to swap PA for Pipewire? After next > lts? I do believe this particular issue is not present on current > Pipewire. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1838151 > > Title: > Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing > wide band speech support (Bluetooth A2DP codecs). > > To manage notifications about this bug go to: > https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions > -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
That would be for 21.10 at this point yes? I wonder, how close/far is Ubuntu to swap PA for Pipewire? After next lts? I do believe this particular issue is not present on current Pipewire. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
this is caused by the zink driver, and there's a fix upstream -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1912940] Re: Bluetooth (ideapad_bluetooth) disabled every time on startup
Thanks Karol. That's good news you have found the point of regression was 5.11.0 but also strange because this bug suggests it was broken in 5.10.0 also. ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: gnome-settings-daemon (Ubuntu) ** 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/1912940 Title: Bluetooth (ideapad_bluetooth) disabled every time on startup Status in linux package in Ubuntu: Confirmed Bug description: [Policy] AutoEnable=true not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jan 24 19:49:49 2021 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81CG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: 6NCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 520-12IKB dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB: dmi.product.family: MIIX 520-12IKB dmi.product.name: 81CG dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB dmi.product.version: MIIX 520-12IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:213889 acl:13940 sco:0 events:310 errors:0 TX bytes:40352 acl:45 sco:0 commands:249 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912940/+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 1912940] Re: Bluetooth (ideapad_bluetooth) disabled every time on startup
I've tested a few versions: 1) Working fine: 5.8.0-48 (official repo) 5.9.16 5.10.0 5.10.14 5.10.27 (last build of 5.10) 2) The issue first appears on 5.11.0-051100. I haven't tested release candidates. -- 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/1912940 Title: Bluetooth (ideapad_bluetooth) disabled every time on startup Status in bluez package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: [Policy] AutoEnable=true not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jan 24 19:49:49 2021 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81CG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: 6NCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 520-12IKB dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB: dmi.product.family: MIIX 520-12IKB dmi.product.name: 81CG dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB dmi.product.version: MIIX 520-12IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:213889 acl:13940 sco:0 events:310 errors:0 TX bytes:40352 acl:45 sco:0 commands:249 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1912940/+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 1912940] Re: Bluetooth (ideapad_bluetooth) disabled every time on startup
Interesting these bug reports are all from kernel 5.10 and later, and all related to ideapad_bluetooth. This sounds like a kernel regression in that area. Can anyone test some older/newer kernels? https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D -- 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/1912940 Title: Bluetooth (ideapad_bluetooth) disabled every time on startup Status in bluez package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: [Policy] AutoEnable=true not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jan 24 19:49:49 2021 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81CG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: 6NCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 520-12IKB dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB: dmi.product.family: MIIX 520-12IKB dmi.product.name: 81CG dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB dmi.product.version: MIIX 520-12IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:213889 acl:13940 sco:0 events:310 errors:0 TX bytes:40352 acl:45 sco:0 commands:249 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1912940/+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 1912940] Re: Bluetooth (ideapad_bluetooth) disabled every time on startup
We've been discussing rfkill on the duplicate bug (#1922338). The rfkill output from just after boot was: ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan unblocked unblocked 1 bluetooth ideapad_bluetooth blocked unblocked 2 wlan phy0 unblocked unblocked 4 bluetooth hci0 blocked unblocked And we've come to the conclusion that the GUI does not run rfkill unblock, however I've checked today and after flicking the GUI switch it does indeed unblock the device: ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan unblocked unblocked 1 bluetooth ideapad_bluetooth unblocked unblocked 2 wlan phy0 unblocked unblocked 4 bluetooth hci0 unblocked unblocked It still doesn't work of course. I can also manually run rfkill unblock 1 (and 3), but that doesn't work either. Bluetooth starts working only after unblocking and then restarting bluetooth.service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1912940 Title: Bluetooth (ideapad_bluetooth) disabled every time on startup Status in bluez package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: [Policy] AutoEnable=true not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jan 24 19:49:49 2021 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81CG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: 6NCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 520-12IKB dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB: dmi.product.family: MIIX 520-12IKB dmi.product.name: 81CG dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB dmi.product.version: MIIX 520-12IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:213889 acl:13940 sco:0 events:310 errors:0 TX bytes:40352 acl:45 sco:0 commands:249 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1912940/+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 1922877] Re: bug and screen tearing with intel graphic card
*** This bug is a duplicate of bug 1867668 *** https://bugs.launchpad.net/bugs/1867668 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 1867668, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** This bug has been marked a duplicate of bug 1867668 Visual artifacts in Gnome Shell when using the old 'intel' Xorg driver -- 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/1922877 Title: bug and screen tearing with intel graphic card Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: im using intel onboard graphic card,and work flawlessly on windows.But im facing problems with ubuntu.My screen also tearing,and some program migh not run properly because intel graphic. plz update the intel graphic driver.or give us alternaltive ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 7 14:06:28 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 82G33/G31 Express Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2021-04-07 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b2f17f40-d055-49bf-86c9-eaf28475b9cc ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FJ dmi.board.name: G31M-ES2C dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFJ:bd08/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2C:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2C:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2C dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.1 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/xserver-xorg-video-intel/+bug/1922877/+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 1922877] [NEW] bug and screen tearing with intel graphic card
Public bug reported: im using intel onboard graphic card,and work flawlessly on windows.But im facing problems with ubuntu.My screen also tearing,and some program migh not run properly because intel graphic. plz update the intel graphic driver.or give us alternaltive ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 7 14:06:28 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 82G33/G31 Express Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2021-04-07 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b2f17f40-d055-49bf-86c9-eaf28475b9cc ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FJ dmi.board.name: G31M-ES2C dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFJ:bd08/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2C:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2C:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2C dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1922877 Title: bug and screen tearing with intel graphic card Status in xorg package in Ubuntu: New Bug description: im using intel onboard graphic card,and work flawlessly on windows.But im facing problems with ubuntu.My screen also tearing,and some program migh not run properly because intel graphic. plz update the intel graphic driver.or give us alternaltive ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 7 14:06:28 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 82G33/G31 Express Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2021-04-07 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b2f17f40-d055-49bf-86c9-eaf28475b9cc ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FJ dmi.board.name: G31M-ES2C dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFJ:bd08/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2C:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2C:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2C dmi.sys.vendor: Gigabyte Technology
