[Touch-packages] [Bug 1959408] Comment bridged from LTC Bugzilla
--- Comment From andreas.kreb...@de.ibm.com 2022-04-07 02:38 EDT--- After the announcement support for the official machine name z16 has been added to binutils. Please consider picking up the following patch from 2.37 branch: commit e24d2a2d11008aa363366c1087219f3e3405782a (origin/binutils-2_37-branch, 2.37) Author: Andreas Krebbel Date: Thu Apr 7 07:45:49 2022 +0200 IBM zSystems: Add support for z16 as CPU name. So far z16 was identified as arch14. After the machine has been announced we can now add the real name. (cherry picked from commit 69341966def7f6551bc4452684136831d6a6941c) (cherry picked from commit fb4d148004f28494e9fb5d2400a13308d07a7988) -- 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/1959408 Title: [22.04 FEAT] BINUTILS: Support for new IBM Z Hardware Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: BINUTILS: Support for new IBM Z Hardware Upstream target: binutils = 2.37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959408/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
I did not reproduce this issue with ubuntu 22.04 desktop beta image. -- 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/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1396180] Re: package lsb-core 4.1+Debian11ubuntu6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
[Expired for lsb (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lsb (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1396180 Title: package lsb-core 4.1+Debian11ubuntu6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in lsb package in Ubuntu: Expired Bug description: ubuntu 14.04 problem when updated programs ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lsb-core 4.1+Debian11ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Tue Nov 25 15:22:53 2014 DuplicateSignature: package:lsb-core:4.1+Debian11ubuntu6:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-08-22 (95 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: lsb Title: package lsb-core 4.1+Debian11ubuntu6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1396180/+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 1267314] Re: package lsb-core 4.1+Debian11ubuntu4 failed to install/upgrade: package lsb-core is not ready for configuration cannot configure (current status `half-installed')
[Expired for lsb (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lsb (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1267314 Title: package lsb-core 4.1+Debian11ubuntu4 failed to install/upgrade: package lsb-core is not ready for configuration cannot configure (current status `half-installed') Status in lsb package in Ubuntu: Expired Bug description: loading up phablet and adb through software center ProblemType: Package DistroRelease: Ubuntu 13.10 Package: lsb-core 4.1+Debian11ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Jan 9 13:10:46 2014 DuplicateSignature: package:lsb-core:4.1+Debian11ubuntu4:package lsb-core is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package lsb-core is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2013-11-08 (61 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: lsb Title: package lsb-core 4.1+Debian11ubuntu4 failed to install/upgrade: package lsb-core is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: Upgraded to saucy on 2013-11-09 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1267314/+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 673707] Re: lsb-desktop lacking dependency on libQtNetwork
[Expired for lsb (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lsb (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/673707 Title: lsb-desktop lacking dependency on libQtNetwork Status in lsb package in Ubuntu: Expired Bug description: Binary package hint: lsb-desktop Install Ubuntu 10.10 (x86_64) Installed "lsb" keystone Attempted to run our beta 4.1 tests, and the precheck, as well as libchk report the absence of libQtNetwork.so.4. libQtNetwork was also required by LSB-3.2 and LSB-4.0 stewb@ubuntu1010-64:~$ lsb_release -rd Description: Ubuntu 10.10 Release: 10.10 stewb@ubuntu1010-64:~$ apt-cache policy lsb-desktop lsb-desktop: Installed: 4.0-0ubuntu8 Candidate: 4.0-0ubuntu8 Version table: *** 4.0-0ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/673707/+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 1437392] Re: package lsb-core 4.1+Debian11ubuntu8 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
[Expired for lsb (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lsb (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1437392 Title: package lsb-core 4.1+Debian11ubuntu8 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in lsb package in Ubuntu: Expired Bug description: no pudo instalarse ProblemType: Package DistroRelease: Ubuntu 15.04 Package: lsb-core 4.1+Debian11ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 Architecture: amd64 Date: Fri Mar 27 10:59:55 2015 DuplicateSignature: package:lsb-core:4.1+Debian11ubuntu8:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2014-05-02 (329 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.24ubuntu1 apt 1.0.9.7ubuntu3 SourcePackage: lsb Title: package lsb-core 4.1+Debian11ubuntu8 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1437392/+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 1489432] Re: package lsb-invalid-mta 4.1+Debian11ubuntu6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
[Expired for lsb (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lsb (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1489432 Title: package lsb-invalid-mta 4.1+Debian11ubuntu6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in lsb package in Ubuntu: Expired Bug description: package lsb-invalid-mta 4.1+Debian11ubuntu6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lsb-invalid-mta 4.1+Debian11ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-79.115-generic 3.2.67 Uname: Linux 3.2.0-79-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 Date: Wed Aug 26 18:26:00 2015 Dependencies: DuplicateSignature: package:lsb-invalid-mta:4.1+Debian11ubuntu6:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: lsb Title: package lsb-invalid-mta 4.1+Debian11ubuntu6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2015-03-27 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1489432/+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 1437635] Re: package lsb 4.1+Debian11ubuntu6 failed to install/upgrade: problemas de dependencias - se deja sin configurar
[Expired for lsb (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lsb (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1437635 Title: package lsb 4.1+Debian11ubuntu6 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in lsb package in Ubuntu: Expired Bug description: package lsb 4.1+Debian11ubuntu6 failed to install/upgrade: problemas de dependencias - se deja sin configurar ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lsb 4.1+Debian11ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 Date: Fri Mar 27 16:51:47 2015 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2015-03-23 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: lsb Title: package lsb 4.1+Debian11ubuntu6 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1437635/+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 1968109] Re: "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources
Forgot to add: the date in the screen record file is not correct because this laptop doesn't have a battery (that's on me; I'm working on that). I don't remember exactly when I took the screen record itself, but the recorded "last modified" time is April 2, 2022 at 7:33 PM. I transferred it to my smartphone offline (via cable) before transferring it to another computer (again via cable; it was the easy option for me) to send this bug report. This is the Ubuntu Studio 22.04 "beta" ISO, not a daily release. In Ubuntu Studio 21.10, I can get the correct time after I connect to the Internet, *because* I can do so. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1968109 Title: "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources Status in software-properties package in Ubuntu: New Bug description: I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009 MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of the box. What I expect to happen is something I can do successfully in Ubuntu Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that version. In KDE Settings I click on "Driver Manager", which automatically opens Software Sources (that's the only way I know how to get there). It finds and shows my [proprietary Broadcom] Wi-Fi driver; I click on it, then the "Apply Changes" button is enabled after a second or two. I click that, wait about half a minute with a progress bar in action below, and then the Wi-Fi options appear the notification area, allowing me to connect. I attached a screen record of what actually happens in Ubuntu Studio 22.04 beta (thankfully this distro comes with screen recording software out of the box). When I click on "Driver Manager", a "xterm" window (version 372-1ubuntu1 I think?) opens unexpectedly with some code showing up in it (the code is in the screen record), shortly before Software Sources (version 0.99.20) opens as expected. The same driver still appears on the list. When I click on the driver, it seems to still take that second or two to transition, with some more code appearing in "xterm", but the "Apply Changes" button never enables itself. It remains disabled so I can't click it. The "revert" button directly next to it is also disabled. Thus, I can't connect my computer to Wi-Fi in 22.04 beta. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE Date: Fri Mar 18 17:00:53 2022 LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968109/+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 1968109] [NEW] "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources
Public bug reported: I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009 MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of the box. What I expect to happen is something I can do successfully in Ubuntu Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that version. In KDE Settings I click on "Driver Manager", which automatically opens Software Sources (that's the only way I know how to get there). It finds and shows my [proprietary Broadcom] Wi-Fi driver; I click on it, then the "Apply Changes" button is enabled after a second or two. I click that, wait about half a minute with a progress bar in action below, and then the Wi-Fi options appear the notification area, allowing me to connect. I attached a screen record of what actually happens in Ubuntu Studio 22.04 beta (thankfully this distro comes with screen recording software out of the box). When I click on "Driver Manager", a "xterm" window (version 372-1ubuntu1 I think?) opens unexpectedly with some code showing up in it (the code is in the screen record), shortly before Software Sources (version 0.99.20) opens as expected. The same driver still appears on the list. When I click on the driver, it seems to still take that second or two to transition, with some more code appearing in "xterm", but the "Apply Changes" button never enables itself. It remains disabled so I can't click it. The "revert" button directly next to it is also disabled. Thus, I can't connect my computer to Wi-Fi in 22.04 beta. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE Date: Fri Mar 18 17:00:53 2022 LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screen record of the process I do in Ubuntu Studio 21.10 to get my Wi-Fi driver working, but fails in 22.04." https://bugs.launchpad.net/bugs/1968109/+attachment/5577783/+files/vokoscreenNG-2022-03-18_16-35-55.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1968109 Title: "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources Status in software-properties package in Ubuntu: New Bug description: I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009 MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of the box. What I expect to happen is something I can do successfully in Ubuntu Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that version. In KDE Settings I click on "Driver Manager", which automatically opens Software Sources (that's the only way I know how to get there). It finds and shows my [proprietary Broadcom] Wi-Fi driver; I click on it, then the "Apply Changes" button is enabled after a second or two. I click that, wait about half a minute with a progress bar in action below, and then the Wi-Fi options appear the notification area, allowing me to connect. I attached a screen record of what actually happens in Ubuntu Studio 22.04 beta (thankfully this distro comes with screen recording software out of the box). When I click on "Driver Manager", a "xterm" window (version 372-1ubuntu1 I think?) opens unexpectedly with some code showing up in it (the code is in the screen record), shortly before Software Sources (version 0.99.20) opens as expected. The same driver still appears on the list. When I click on the driver, it seems to still take that second or two to transition, with some more code appearing in "xterm", but the "Apply Changes" button never enables itself. It remains disabled so I can't click it. The "revert" button directly next to it is also disabled. Thus, I can't connect my computer to Wi-Fi in 22.04 beta. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE Date: Fri Mar 18 17:00:53 2022 LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bug
[Touch-packages] [Bug 1968100] [NEW] Reporting firefox bug redirect to general mozilla page
Public bug reported: When reporting a bug on firefox snap. A dialog is shown, that will redirect to https://support.mozilla.org/en-US/products/firefox and not the bug reporting website. If someone tries to file a bug this is pretty inconvenient. Starting a search there on 'report bug' shows as 2nd item. Reporting bugs is hard. The first item is about bugs fixed in a release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 10:55:35 2022 InstallationDate: Installed on 2022-03-17 (21 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: Upgraded to jammy on 2022-03-21 (16 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1968100 Title: Reporting firefox bug redirect to general mozilla page Status in apport package in Ubuntu: New Bug description: When reporting a bug on firefox snap. A dialog is shown, that will redirect to https://support.mozilla.org/en-US/products/firefox and not the bug reporting website. If someone tries to file a bug this is pretty inconvenient. Starting a search there on 'report bug' shows as 2nd item. Reporting bugs is hard. The first item is about bugs fixed in a release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 10:55:35 2022 InstallationDate: Installed on 2022-03-17 (21 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: Upgraded to jammy on 2022-03-21 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1968100/+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 1968074] Re: moc fails to parse include inside enum
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1968074 Title: moc fails to parse include inside enum Status in gudhi package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: Seen while trying to rebuild gudhi against qtbase5-dev/ 5.15.3+dfsg-1 : AutoMoc subprocess error The moc process failed to compile "SRC:/src/GudhUI/gui/MainWindow.cpp" into "SRC:/build/userversion/src/GudhUI/GudhUI_autogen/include/MainWindow.moc" included by "SRC:/src/GudhUI/gui/MainWindow.cpp" ... Output -- usr/include/tbb/tbb_profiling.:29: Parse error at "/usr/include/tbb/internal/_tbb_strings.h" Previous builds against qtbase5-dev/5.15.2+dfsg-15 were successful [1]. I found an upstream bug [2] with the same error, although the versions differ. I also found similar bug [3] that is reported to be fixed in 5.15.6. [1] https://launchpad.net/ubuntu/+source/gudhi/3.5.0+dfsg-1ubuntu1 [2] https://bugreports.qt.io/browse/QTBUG-94790 [3] https://bugreports.qt.io/browse/QTBUG-80990 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gudhi/+bug/1968074/+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 1968074] Re: moc fails to parse include inside enum
Reverting src/tools/moc/moc.cpp to as it was in 5.15.2+dfsg-15 (as per the attached patch) allows gudhi to build successfully again. ** Patch added: "revert_moc.cpp.patch" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1968074/+attachment/5577752/+files/revert_moc.cpp.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1968074 Title: moc fails to parse include inside enum Status in gudhi package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: Seen while trying to rebuild gudhi against qtbase5-dev/ 5.15.3+dfsg-1 : AutoMoc subprocess error The moc process failed to compile "SRC:/src/GudhUI/gui/MainWindow.cpp" into "SRC:/build/userversion/src/GudhUI/GudhUI_autogen/include/MainWindow.moc" included by "SRC:/src/GudhUI/gui/MainWindow.cpp" ... Output -- usr/include/tbb/tbb_profiling.:29: Parse error at "/usr/include/tbb/internal/_tbb_strings.h" Previous builds against qtbase5-dev/5.15.2+dfsg-15 were successful [1]. I found an upstream bug [2] with the same error, although the versions differ. I also found similar bug [3] that is reported to be fixed in 5.15.6. [1] https://launchpad.net/ubuntu/+source/gudhi/3.5.0+dfsg-1ubuntu1 [2] https://bugreports.qt.io/browse/QTBUG-94790 [3] https://bugreports.qt.io/browse/QTBUG-80990 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gudhi/+bug/1968074/+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 1968094] [NEW] BTRFS root subvolume @ mounted always as readonly (... ro rootflags=subvol=@ ...) on Jammy
Public bug reported: = Description = On Ubuntu Jammy Jellyfish (beta 220330) installed fully on BTRFS filesystem, root subvolume (subvol=@) is always mounted as read only. There is a kernel flag (ro) appended to GRUB configuration file /boot/grub/grub.cfg created by script /usr/sbin/update-grub during every kernel update. Only home subvolume (@home) is actually mounted as rw according to fstab which is correct. Image: Jammy Beta (220330) = Steps to Reproduce = 1. Install Jammy Beta (220330) on PC w. EFI and select FS root (/) to BTRFS (subvolumes @ and @home are created) 2. Launch the kernel via the default grub entry = Expected Results = root / should be mounted as rw (mount -v | grep @), there should be no (ro) flag on /proc/cmdline = Actual Results = in grub.cfg: linux /@/boot/vmlinuz-5.15.0-23-generic root=UUID=--... rootflags=subvol=@ ro quiet splash $vt_handoff in /proc/cmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=981dd6de-02fc-41a9-9e2a-09dbbc776b2b ro rootflags=subvol=@ quiet splash vt.handoff=7 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1968094 Title: BTRFS root subvolume @ mounted always as readonly (... ro rootflags=subvol=@ ...) on Jammy Status in network-manager package in Ubuntu: New Bug description: = Description = On Ubuntu Jammy Jellyfish (beta 220330) installed fully on BTRFS filesystem, root subvolume (subvol=@) is always mounted as read only. There is a kernel flag (ro) appended to GRUB configuration file /boot/grub/grub.cfg created by script /usr/sbin/update-grub during every kernel update. Only home subvolume (@home) is actually mounted as rw according to fstab which is correct. Image: Jammy Beta (220330) = Steps to Reproduce = 1. Install Jammy Beta (220330) on PC w. EFI and select FS root (/) to BTRFS (subvolumes @ and @home are created) 2. Launch the kernel via the default grub entry = Expected Results = root / should be mounted as rw (mount -v | grep @), there should be no (ro) flag on /proc/cmdline = Actual Results = in grub.cfg: linux /@/boot/vmlinuz-5.15.0-23-generic root=UUID=--... rootflags=subvol=@ ro quiet splash $vt_handoff in /proc/cmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=981dd6de-02fc-41a9-9e2a-09dbbc776b2b ro rootflags=subvol=@ quiet splash vt.handoff=7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1968094/+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 1968074] Re: moc fails to parse include inside enum
Failing logs are now visible at: https://launchpad.net/ubuntu/+source/gudhi/3.5.0+dfsg-1ubuntu2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1968074 Title: moc fails to parse include inside enum Status in gudhi package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: Seen while trying to rebuild gudhi against qtbase5-dev/ 5.15.3+dfsg-1 : AutoMoc subprocess error The moc process failed to compile "SRC:/src/GudhUI/gui/MainWindow.cpp" into "SRC:/build/userversion/src/GudhUI/GudhUI_autogen/include/MainWindow.moc" included by "SRC:/src/GudhUI/gui/MainWindow.cpp" ... Output -- usr/include/tbb/tbb_profiling.:29: Parse error at "/usr/include/tbb/internal/_tbb_strings.h" Previous builds against qtbase5-dev/5.15.2+dfsg-15 were successful [1]. I found an upstream bug [2] with the same error, although the versions differ. I also found similar bug [3] that is reported to be fixed in 5.15.6. [1] https://launchpad.net/ubuntu/+source/gudhi/3.5.0+dfsg-1ubuntu1 [2] https://bugreports.qt.io/browse/QTBUG-94790 [3] https://bugreports.qt.io/browse/QTBUG-80990 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gudhi/+bug/1968074/+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 1968047] Re: Ubuntu 22.04 Beta - Unable to compile ruby version 2.7.5, 3.0.3 and 3.3.3 problem with the openssl-dev package
Hopefully this is helpful for you: https://sources.debian.org/data/main/r/ruby3.0/3.0.3-1/debian/patches/Update- openssl-to-version-3.0.0.patch Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968047 Title: Ubuntu 22.04 Beta - Unable to compile ruby version 2.7.5, 3.0.3 and 3.3.3 problem with the openssl-dev package Status in openssl package in Ubuntu: New Bug description: This problem only exists in Ununto 22.04 beta When attempting to comple ruby (any version - I have tried 2.7.5, 3.0.3 & 3.1.1) it fails becuase of a problem with the libssl-dev package. The previous version of Ubuntu used version 1.1.1. The new version uses openssl-dev/libssl-dev 3.0.2 $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 sudo apt-cache policy libssl-dev libssl-dev: Installed: 3.0.2-0ubuntu1 Candidate: 3.0.2-0ubuntu1 Version table: *** 3.0.2-0ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968047/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
The same error when executing UIO tests in eclipse under docker environment [xcb] Unknown sequence number while processing reply [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. java: ../../src/xcb_io.c:702: _XReply: Assertion `!xcb_xlib_threads_sequence_lost' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcma
[Touch-packages] [Bug 1967127] Re: [FFe] update libarchive to 3.6.0
> https://github.com/libarchive/libarchive/releases/tag/v3.6.0 This looks fine. > https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0 I'm not reading this. An FFe request should include a human-readable *summary* of upstream feature-freeze-breaking that may introduce risk of regression; a git log is not that. FFe granted. ** Changed in: libarchive (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1967127 Title: [FFe] update libarchive to 3.6.0 Status in evince package in Ubuntu: New Status in libarchive package in Ubuntu: Triaged Bug description: I request a Feature Freeze Exception to update libarchive from 3.5.2 to 3.6.0 and build evince with libarchive 3.6. This will allow us to drop 2 revert commits we added to evince to build with the older libarchive. https://salsa.debian.org/gnome-team/evince/-/commit/badb5b65b Changes --- https://github.com/libarchive/libarchive/releases/tag/v3.6.0 https://github.com/libarchive/libarchive/compare/v3.5.2...v3.6.0 Other Changes - 1. libarchive: I am cherry-picking a security fix for CVE-2022-26280 2. libarchive: debian/rules was only running dh_auto_test if 'check' was set in DEB_BUILD_OPTIONS. I am changing that to only run if 'nocheck' is not set. That way we run the build tests by default. I'm forwarding both those changes to Debian soon. Build logs -- https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13404994/+listing-archive-extra https://buildd.debian.org/status/package.php?p=evince Testing done No errors in the install logs Evince still works fine to open a variety of PDFs and a .cbz file I have. File Roller still works fine to open a variety of compressed file types. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1967127/+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 1967965] Re: "Other problem" option is misleading or goes to the wrong menu
After talking to ~schopin, I think this is a real bug; the "Other" and "Display (X.Org)" entries are swapped. ** Attachment added: "Image showing the problem" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967965/+attachment/5577711/+files/FPrfrMMWUAEWjCU.png ** Summary changed: - "Other problem" option is misleading or goes to the wrong menu + "Other problem" and "Display" options are swapped -- 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/1967965 Title: "Other problem" and "Display" options are swapped Status in apport package in Ubuntu: New Bug description: When attempting to report https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was unable to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`. However doing so gave me a menu with unrelated option (as expected) and an "Other problem..." option. I assumed this was for generic other bugs, as I think is reasonable; however, it brings me to a menu that only makes sense for display-related bugs. I think this text should be changed to note that; perhaps "Other display problem...". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash 640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash CurrentDesktop: KDE Date: Tue Apr 5 19:58:56 2022 InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967965/+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 1967965] Re: "Other problem" option is misleading or goes to the wrong menu
Changing back the status to New, as it is actually a display bug in apport as found out in this Twitter thread: https://twitter.com/NoraDotCodes/status/1511763913418891267 I couldn't reproduce on my system (Gnome-based) --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ** Changed in: apport (Ubuntu) Status: Opinion => New -- 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/1967965 Title: "Other problem" and "Display" options are swapped Status in apport package in Ubuntu: New Bug description: When attempting to report https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was unable to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`. However doing so gave me a menu with unrelated option (as expected) and an "Other problem..." option. I assumed this was for generic other bugs, as I think is reasonable; however, it brings me to a menu that only makes sense for display-related bugs. I think this text should be changed to note that; perhaps "Other display problem...". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash 640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash CurrentDesktop: KDE Date: Tue Apr 5 19:58:56 2022 InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967965/+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 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1952947 Title: ubuntu-bug -w (using xprop) doesn't work under wayland Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Impish: Fix Released Status in apport source package in Jammy: Fix Released Bug description: [Impact] This bug makes it more difficult for Wayland users to report bugs with apport. When a Wayland user tries to use the -w,--window option, apport fails silently. We do not want users to face a high barrier to submitting bug reports. The patch for this bug adds a message explaining that the -w,--window option cannot be used on Wayland, and suggests a method for finding the window's PID instead. [Test Plan] * Log on to Ubuntu on Wayland. You can check that $XDG_SESSION_TYPE=="wayland" in your current session. * Open a terminal, and run `ubuntu-bug -w`. * Click on any other window, and observe that the apport UI will not respond. [Where problems could occur] The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to 'wayland'. If either of these strings in the patch were wrong, or the environment variable was not used in the target release, the condition would likely never be true. [Original Description] I want to report a Bug about the application Studio Controls. As I did it already quite a few times, I run "ubuntu-bug -w", get a message that I can select the window of the app I want to report a bug about after closing this message. I close the message with a click on the appropriate button. I click on the window of the application "Studio Controls" that I want to report a bug about. Nothing happens. I wait for a few minutes. Still nothing happens. In the console where I started ubuntu-bug -w I see the following message: (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed What I expect: Usaully when I use this procedure, after a relatively short while a new message window pops up asking me if the bug should be reported and showing me the data that is sent to Launchpad. I tried other applications, too, same effect. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apport 2.20.11-0ubuntu71 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 20:01:23 2021 InstallationDate: Installed on 2020-04-12 (597 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1968074] [NEW] moc fails to parse include inside enum
Public bug reported: Seen while trying to rebuild gudhi against qtbase5-dev/ 5.15.3+dfsg-1 : AutoMoc subprocess error The moc process failed to compile "SRC:/src/GudhUI/gui/MainWindow.cpp" into "SRC:/build/userversion/src/GudhUI/GudhUI_autogen/include/MainWindow.moc" included by "SRC:/src/GudhUI/gui/MainWindow.cpp" ... Output -- usr/include/tbb/tbb_profiling.:29: Parse error at "/usr/include/tbb/internal/_tbb_strings.h" Previous builds against qtbase5-dev/5.15.2+dfsg-15 were successful [1]. I found an upstream bug [2] with the same error, although the versions differ. I also found similar bug [3] that is reported to be fixed in 5.15.6. [1] https://launchpad.net/ubuntu/+source/gudhi/3.5.0+dfsg-1ubuntu1 [2] https://bugreports.qt.io/browse/QTBUG-94790 [3] https://bugreports.qt.io/browse/QTBUG-80990 ** Affects: gudhi (Ubuntu) Importance: Undecided Status: New ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: gudhi (Ubuntu) Importance: Undecided Status: New ** Description changed: Seen while trying to rebuild gudhi against qtbase5-dev/ 5.15.3+dfsg-1 : - AutoMoc subprocess error The moc process failed to compile "SRC:/src/GudhUI/gui/MainWindow.cpp" into "SRC:/build/userversion/src/GudhUI/GudhUI_autogen/include/MainWindow.moc" included by "SRC:/src/GudhUI/gui/MainWindow.cpp" ... - Output - -- + Output + -- usr/include/tbb/tbb_profiling.:29: Parse error at "/usr/include/tbb/internal/_tbb_strings.h" - Previous builds against qtbase5-dev/5.15.2+dfsg-15 were successful [1]. - I found an upstream bug [1] with the same error, although the versions differ. - I also found similar bug [2] that is reported to be fixed in 5.15.6. - + I found an upstream bug [2] with the same error, although the versions differ. + I also found similar bug [3] that is reported to be fixed in 5.15.6. [1] https://launchpad.net/ubuntu/+source/gudhi/3.5.0+dfsg-1ubuntu1 [2] https://bugreports.qt.io/browse/QTBUG-94790 [3] https://bugreports.qt.io/browse/QTBUG-80990 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1968074 Title: moc fails to parse include inside enum Status in gudhi package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: Seen while trying to rebuild gudhi against qtbase5-dev/ 5.15.3+dfsg-1 : AutoMoc subprocess error The moc process failed to compile "SRC:/src/GudhUI/gui/MainWindow.cpp" into "SRC:/build/userversion/src/GudhUI/GudhUI_autogen/include/MainWindow.moc" included by "SRC:/src/GudhUI/gui/MainWindow.cpp" ... Output -- usr/include/tbb/tbb_profiling.:29: Parse error at "/usr/include/tbb/internal/_tbb_strings.h" Previous builds against qtbase5-dev/5.15.2+dfsg-15 were successful [1]. I found an upstream bug [2] with the same error, although the versions differ. I also found similar bug [3] that is reported to be fixed in 5.15.6. [1] https://launchpad.net/ubuntu/+source/gudhi/3.5.0+dfsg-1ubuntu1 [2] https://bugreports.qt.io/browse/QTBUG-94790 [3] https://bugreports.qt.io/browse/QTBUG-80990 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gudhi/+bug/1968074/+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 1968063] Re: Jammy: Xorg crash on virtual QXL graphics
*** This bug is a duplicate of bug 1967901 *** https://bugs.launchpad.net/bugs/1967901 ** This bug has been marked a duplicate of bug 1967901 [qxl] Xorg fails to start with "Screen(s) found, but none have a usable configuration." -- 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/1968063 Title: Jammy: Xorg crash on virtual QXL graphics Status in xorg package in Ubuntu: New Bug description: Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg- Server will not start. Either directly via lightdm or via gdm/wayland selecting Xubuntu session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 6 17:59:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-focal dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968063/+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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mate-desktop-environment (Ubuntu) Status: New => Confirmed -- 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/1873750 Title: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator Status in brisk-menu package in Ubuntu: Invalid Status in classicmenu-indicator package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Confirmed Status in mate-desktop-environment package in Ubuntu: Triaged Status in mate-menu package in Ubuntu: Invalid Status in mate-menus package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: Invalid Status in mate-settings-daemon package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Triaged Status in vala-panel-appmenu package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu MATE 20.04 LTS 2. Install non-default terminal - Tilix, by `sudo apt-get install tilix` 3. Install terminal-based application - Midnight Commander, by `sudo apt-get install mc` 3. Set Tilix as default terminal in `mate-default-applications-properties` or programmatically: gsettings set org.mate.applications-terminal exec "'tilix'" 4. Set Tilix as alternative for x-terminal-emulator by update- alternatives: update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper sudo update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper 5. Reboot 6. Add Custom Application Launcher to the MATE Panel: Type: Application in Terminal Name: mc Command: mc 7. Click the icon of just created Custom Application Launcher Expected results: * Midnight Commander is opened in the user-defined terminal - in Tilix Actual results: * Midnight Commander is default terminal - in MATE Terminal Notes: * This also happens with desktop-files installed by Midnight Commander, it opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, Dock, + menu, Advanced Mate Menu (`mate-menu` package) * What is interesting, the + respects user preferences and uses Tilix * Also ++ opens Tilix as expected. --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mate-panel 1.24.0-2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Apr 20 10:48:51 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed -- 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/1873750 Title: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator Status in brisk-menu package in Ubuntu: Invalid Status in classicmenu-indicator package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Confirmed Status in mate-desktop-environment package in Ubuntu: Triaged Status in mate-menu package in Ubuntu: Invalid Status in mate-menus package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: Invalid Status in mate-settings-daemon package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Triaged Status in vala-panel-appmenu package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu MATE 20.04 LTS 2. Install non-default terminal - Tilix, by `sudo apt-get install tilix` 3. Install terminal-based application - Midnight Commander, by `sudo apt-get install mc` 3. Set Tilix as default terminal in `mate-default-applications-properties` or programmatically: gsettings set org.mate.applications-terminal exec "'tilix'" 4. Set Tilix as alternative for x-terminal-emulator by update- alternatives: update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper sudo update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper 5. Reboot 6. Add Custom Application Launcher to the MATE Panel: Type: Application in Terminal Name: mc Command: mc 7. Click the icon of just created Custom Application Launcher Expected results: * Midnight Commander is opened in the user-defined terminal - in Tilix Actual results: * Midnight Commander is default terminal - in MATE Terminal Notes: * This also happens with desktop-files installed by Midnight Commander, it opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, Dock, + menu, Advanced Mate Menu (`mate-menu` package) * What is interesting, the + respects user preferences and uses Tilix * Also ++ opens Tilix as expected. --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mate-panel 1.24.0-2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Apr 20 10:48:51 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-mate-settings (Ubuntu) Status: New => Confirmed -- 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/1873750 Title: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator Status in brisk-menu package in Ubuntu: Invalid Status in classicmenu-indicator package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Confirmed Status in mate-desktop-environment package in Ubuntu: Triaged Status in mate-menu package in Ubuntu: Invalid Status in mate-menus package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: Invalid Status in mate-settings-daemon package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Triaged Status in vala-panel-appmenu package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu MATE 20.04 LTS 2. Install non-default terminal - Tilix, by `sudo apt-get install tilix` 3. Install terminal-based application - Midnight Commander, by `sudo apt-get install mc` 3. Set Tilix as default terminal in `mate-default-applications-properties` or programmatically: gsettings set org.mate.applications-terminal exec "'tilix'" 4. Set Tilix as alternative for x-terminal-emulator by update- alternatives: update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper sudo update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper 5. Reboot 6. Add Custom Application Launcher to the MATE Panel: Type: Application in Terminal Name: mc Command: mc 7. Click the icon of just created Custom Application Launcher Expected results: * Midnight Commander is opened in the user-defined terminal - in Tilix Actual results: * Midnight Commander is default terminal - in MATE Terminal Notes: * This also happens with desktop-files installed by Midnight Commander, it opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, Dock, + menu, Advanced Mate Menu (`mate-menu` package) * What is interesting, the + respects user preferences and uses Tilix * Also ++ opens Tilix as expected. --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mate-panel 1.24.0-2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Apr 20 10:48:51 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator
glib doesn't support `x-terminal-emulator` so the first found supported terminal emulator (which will be mate-terminal in Ubuntu MATE) will be used, regardless of what preferred applications or alternatives have been configured. This is why panels/launchers will favour mate-terminal in Ubuntu MATE. ** Changed in: mate-desktop-environment (Ubuntu) Status: Confirmed => Triaged ** Changed in: ubuntu-mate-settings (Ubuntu) Status: Confirmed => Triaged -- 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/1873750 Title: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator Status in brisk-menu package in Ubuntu: Invalid Status in classicmenu-indicator package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Confirmed Status in mate-desktop-environment package in Ubuntu: Triaged Status in mate-menu package in Ubuntu: Invalid Status in mate-menus package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: Invalid Status in mate-settings-daemon package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Triaged Status in vala-panel-appmenu package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu MATE 20.04 LTS 2. Install non-default terminal - Tilix, by `sudo apt-get install tilix` 3. Install terminal-based application - Midnight Commander, by `sudo apt-get install mc` 3. Set Tilix as default terminal in `mate-default-applications-properties` or programmatically: gsettings set org.mate.applications-terminal exec "'tilix'" 4. Set Tilix as alternative for x-terminal-emulator by update- alternatives: update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper sudo update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper 5. Reboot 6. Add Custom Application Launcher to the MATE Panel: Type: Application in Terminal Name: mc Command: mc 7. Click the icon of just created Custom Application Launcher Expected results: * Midnight Commander is opened in the user-defined terminal - in Tilix Actual results: * Midnight Commander is default terminal - in MATE Terminal Notes: * This also happens with desktop-files installed by Midnight Commander, it opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, Dock, + menu, Advanced Mate Menu (`mate-menu` package) * What is interesting, the + respects user preferences and uses Tilix * Also ++ opens Tilix as expected. --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mate-panel 1.24.0-2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Apr 20 10:48:51 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+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 1873750] Re: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- 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/1873750 Title: Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator Status in brisk-menu package in Ubuntu: Invalid Status in classicmenu-indicator package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Confirmed Status in mate-desktop-environment package in Ubuntu: Triaged Status in mate-menu package in Ubuntu: Invalid Status in mate-menus package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: Invalid Status in mate-settings-daemon package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Triaged Status in vala-panel-appmenu package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu MATE 20.04 LTS 2. Install non-default terminal - Tilix, by `sudo apt-get install tilix` 3. Install terminal-based application - Midnight Commander, by `sudo apt-get install mc` 3. Set Tilix as default terminal in `mate-default-applications-properties` or programmatically: gsettings set org.mate.applications-terminal exec "'tilix'" 4. Set Tilix as alternative for x-terminal-emulator by update- alternatives: update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper sudo update-alternatives --set x-terminal-emulator /usr/bin/tilix.wrapper 5. Reboot 6. Add Custom Application Launcher to the MATE Panel: Type: Application in Terminal Name: mc Command: mc 7. Click the icon of just created Custom Application Launcher Expected results: * Midnight Commander is opened in the user-defined terminal - in Tilix Actual results: * Midnight Commander is default terminal - in MATE Terminal Notes: * This also happens with desktop-files installed by Midnight Commander, it opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, Dock, + menu, Advanced Mate Menu (`mate-menu` package) * What is interesting, the + respects user preferences and uses Tilix * Also ++ opens Tilix as expected. --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mate-panel 1.24.0-2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Apr 20 10:48:51 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1873750/+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 1968063] Re: Jammy: Xorg crash on virtual QXL graphics
adding Xorg crash dump ** Attachment added: "Xorg crash dump" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968063/+attachment/5577702/+files/_usr_lib_xorg_Xorg.126.crash -- 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/1968063 Title: Jammy: Xorg crash on virtual QXL graphics Status in xorg package in Ubuntu: New Bug description: Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg- Server will not start. Either directly via lightdm or via gdm/wayland selecting Xubuntu session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 6 17:59:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-focal dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968063/+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 1968063] [NEW] Jammy: Xorg crash on virtual QXL graphics
Public bug reported: Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg- Server will not start. Either directly via lightdm or via gdm/wayland selecting Xubuntu session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 6 17:59:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-focal dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash jammy 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/1968063 Title: Jammy: Xorg crash on virtual QXL graphics Status in xorg package in Ubuntu: New Bug description: Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg- Server will not start. Either directly via lightdm or via gdm/wayland selecting Xubuntu session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 6 17:59:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-focal dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver
[Touch-packages] [Bug 1968047] Re: Ubuntu 22.04 Beta - Unable to compile ruby version 2.7.5, 3.0.3 and 3.3.3 problem with the openssl-dev package
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968047 Title: Ubuntu 22.04 Beta - Unable to compile ruby version 2.7.5, 3.0.3 and 3.3.3 problem with the openssl-dev package Status in openssl package in Ubuntu: New Bug description: This problem only exists in Ununto 22.04 beta When attempting to comple ruby (any version - I have tried 2.7.5, 3.0.3 & 3.1.1) it fails becuase of a problem with the libssl-dev package. The previous version of Ubuntu used version 1.1.1. The new version uses openssl-dev/libssl-dev 3.0.2 $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 sudo apt-cache policy libssl-dev libssl-dev: Installed: 3.0.2-0ubuntu1 Candidate: 3.0.2-0ubuntu1 Version table: *** 3.0.2-0ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968047/+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 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition
This issue is still present. I just did a fresh 20.04.4 installation and tracker still used high CPU at system startup until I disabled it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/911981 Title: tracker-store uses 100% cpu and fills all the disk space in home partition Status in tracker package in Ubuntu: Confirmed Bug description: I recently noticed that several tracker related programs were using 100% cpu on my system and in particular tracker-store filled up completely all the available disk space in my home partition. I rerun tracker-preferences to make sure that indexing would not proceed if less than 20% of free space is available, but it seems that tracker-store ignores it. After I noticed that I had left only 44Kb free on the home partition, I deleted the cache from another program and I noticed that tracker-store filled up again the disk space that I freed few minutes before. This is the content of my .cache/tracker/ directory: totale 772068 -rw-r--r-- 1 eclipse eclipse 3072 2011-06-26 22:56 contents.db -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt -rw-r--r-- 1 eclipse eclipse 3072 2010-12-05 21:29 email-contents.db -rw-r--r-- 1 eclipse eclipse 3072 2009-05-06 19:16 email-fulltext.db -rw-r--r-- 1 eclipse eclipse 2359292 2011-06-26 22:54 email-index.db -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db -rw-r--r-- 1 eclipse eclipse 17062912 2011-06-26 19:30 file-contents.db -rw-r--r-- 1 eclipse eclipse 15014912 2010-01-12 20:26 file-fulltext.db -rw-r--r-- 1 eclipse eclipse 75609207 2011-06-26 22:54 file-index.db -rw-r--r-- 1 eclipse eclipse 37027840 2011-06-26 19:31 file-meta.db -rw--- 1 eclipse eclipse 1180048 2009-05-05 22:57 file-update-index.db -rw-r--r-- 1 eclipse eclipse 28376064 2011-10-20 09:34 fulltext.db -rw-r--r-- 1 eclipse eclipse 1024 2012-01-04 21:24 meta.db -rw-r--r-- 1 eclipse eclipse 4653056 2012-01-04 21:26 meta.db-shm -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 miner-applications-locale.txt -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb and this is how much space I have left on my home partition after I KILLED the tracker-store process: /dev/sda8 31G 30G 418M 99% /home --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 DistroRelease: Ubuntu 11.10 Package: tracker 0.10.24-1build2 PackageArchitecture: i386 ProcEnviron: LANGUAGE=it_IT:it:en_GB:en PATH=(custom, user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric Uname: Linux 3.0.0-14-generic i686 UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago) UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser pulse-access sambashare src video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/911981/+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 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
** Tags removed: server-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1893716 Title: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions Status in PAM: New Status in landscape-client package in Ubuntu: Fix Released Status in pam package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in update-motd package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: Fix Released Bug description: My client has 200+ devices automatically uploading information via sftp and scp to a server every few minutes. After a recent update, I noticed the load on their server spiking through the roof. Upon investigation, I discovered a horde of landscape-sysinfo and /usr/bin/lsb_release processes running that correlated with login session notifications in /var/log/syslog and the load spikes. It appears that even in non-interactive sessions where this information will never be seen, the configuration options below in /etc/pam.d/sshd cause these items to be launched (in fact, probably everything in /etc/update-motd.d). This only started on the system in question after a recent set of system updates were installed. The content of /etc/update-motd.d/* really, really, really shouldn't be executed if the session in question is not interactive, as it provides no value at all. Unfortunately, to disable it for these non- interactive sessions, we also have to disable it for the interactive ones as well where it has some value (though not enough to make spiking the load on this server through the roof an acceptable tradeoff). # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. #sessionoptional pam_motd.so motd=/run/motd.dynamic #sessionoptional pam_motd.so noupdate Also, looking at the script 00-header in /etc/update-motd.d/, /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release does include the necessary information: [ -r /etc/lsb-release ] && . /etc/lsb-release if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then # Fall back to using the very slow lsb_release utility DISTRIB_DESCRIPTION=$(lsb_release -s -d) fi # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/pam/+bug/1893716/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
Not an expert in seeds, but the changes made sense. Merged and pushed! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi Status in cloud-init package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-image package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Hi, On Raspberry Pi since Impish, the partition always grows even if I set the following in user-data of cloud-init. growpart: mode: off devices: ['/'] I have tested this on 21.04, and it works, but is broken on 21.10. (partition always grows) I've also tested this in KVM on amd64, and it works (partition does NOT grow). This is a problem for me because I am using runcmd in cloud init to migrate my drive to LVM/LUKS, and the partitioning step fails because the drive is already full. Cheers, Noah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/418662 -- 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/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in systemd package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
** Tags added: rls-jj-incoming -- 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/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in systemd package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1968047] [NEW] Ubuntu 22.04 Beta - Unable to compile ruby version 2.7.5, 3.0.3 and 3.3.3 problem with the openssl-dev package
Public bug reported: This problem only exists in Ununto 22.04 beta When attempting to comple ruby (any version - I have tried 2.7.5, 3.0.3 & 3.1.1) it fails becuase of a problem with the libssl-dev package. The previous version of Ubuntu used version 1.1.1. The new version uses openssl-dev/libssl-dev 3.0.2 $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 sudo apt-cache policy libssl-dev libssl-dev: Installed: 3.0.2-0ubuntu1 Candidate: 3.0.2-0ubuntu1 Version table: *** 3.0.2-0ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968047 Title: Ubuntu 22.04 Beta - Unable to compile ruby version 2.7.5, 3.0.3 and 3.3.3 problem with the openssl-dev package Status in openssl package in Ubuntu: New Bug description: This problem only exists in Ununto 22.04 beta When attempting to comple ruby (any version - I have tried 2.7.5, 3.0.3 & 3.1.1) it fails becuase of a problem with the libssl-dev package. The previous version of Ubuntu used version 1.1.1. The new version uses openssl-dev/libssl-dev 3.0.2 $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 sudo apt-cache policy libssl-dev libssl-dev: Installed: 3.0.2-0ubuntu1 Candidate: 3.0.2-0ubuntu1 Version table: *** 3.0.2-0ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968047/+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 1967009] Re: Missing support for Georgian uppercase characters
Any updates? It's planned to re-enable CSS uppercasing for Georgian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1967009 Title: Missing support for Georgian uppercase characters Status in fonts-dejavu package in Ubuntu: Incomplete Bug description: Georgian uppercase letters are encoded in Unicode 11 (2018), but there are no fonts in Ubuntu that can display these characters. Version info: Ubuntu 21.04 To reproduce: 1. add Georgian keyboard layout 2. open any text editor 3. type Georgian letters, then change them to uppercase Expected: Readable text Actual result: Shows squares Some other Linux distributions switched to Google-Noto-Georgian, which covers all Georgian characters. Can it be used in Ubuntu too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1967009/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
Ok, got it. Thanks for the really quick response! -- 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/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in systemd package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
udev is built by src:systemd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in systemd package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1962453] Update Released
The verification of the Stable Release Update for keyutils has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+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 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
This bug was fixed in the package keyutils - 1.5.9-9.2ubuntu2.1 --- keyutils (1.5.9-9.2ubuntu2.1) bionic; urgency=medium * d/p/apply-default-ttl-to-records.patch: Add patch to apply default TTL to records obtained from getaddrinfo(). (LP: #1962453) -- Utkarsh Gupta Tue, 08 Mar 2022 13:26:12 +0530 ** Changed in: keyutils (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+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 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU
** Changed in: marco (Ubuntu) Status: Confirmed => Invalid -- 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/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU Status in marco package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu boots normally to the display manager (login screen) as expected. But once I log in, everything on the screen is cut up into horizontal slices, with each slice offset farther right than the slice above, and squares of random colors running diagonally across the screen. I've attached a picture of my monitor showing the issue for reference. My hardware is a home-built PC with an ASUS Prime B450M motherboard, a Ryzen 3 2200G APU, and using that APU's integrated graphics. In terms of software I'm running Ubuntu 20.04, which I just upgraded to and did a software update on. I have Linux 5.4.0-33-generic, X.Org 1.20.8, and Mesa 20.0.4. Before I upgraded Ubuntu, I was affected by Bug #1880041 but it seems fixed in the new kernel. I don't believe they're related but I figure it's worth mentioning. I tried adding the nomodeset kernel option at boot, and it's an effective workaround. Also, I tried booting from an Ubuntu Mate 20.04 live USB to see if this was caused by some quirk of my particular software setup, and successfully reproduced the bug, proving it wasn't. If you'd like me to, I can provide log files, system information, etc. or help narrow it down by testing workarounds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Jun 8 06:41:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1043:876b] InstallationDate: Installed on 2019-10-20 (231 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=43189257-cc94-4e98-ac1d-e16336dd152e ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2006 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-A 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.:bvr2006:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A: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 N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/marco/+bug/1882525/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
I still see this issue even after the suggested change [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. java: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. java: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. in my docker file I have RUN echo 'deb http://archive.ubuntu.com/ubuntu/ focal-proposed main restricted' >> /etc/apt/sources.list && \ apt-get update -q -y && \ apt-get install -y --fix-missing --no-install-recommends \ libx11-6 && \ apt-get purge -y pm-utils xscreensaver* && \ apt-get autoremove -y && \ apt-get clean -y && \ rm -rf /var/lib/apt/lists/* -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/
[Touch-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
I made a new report in the proper place (i.e. udev package): https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1968036. It's a really easy backport so I hope it's through soon. Edit: Didn't see your message beforehand, sorry. Anyway the file is part of the udev package per dpkg-query, so if at all it should be reassigned to that, and the second issue I just created closed. -- 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/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in systemd package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
Well, I can reassign to see if the maintainer of systemd/udev could backport the patch for this. ** Package changed: xf86-input-wacom (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in systemd package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1926860] [NEW] XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
You have been subscribed to a public bug: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: Invalid ** Affects: xserver-xorg-input-libinput (Arch Linux) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade hirsute wayland-session -- XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 https://bugs.launchpad.net/bugs/1926860 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968028] Re: unattended-upgrades if enabled wont disable interactivemode
This can be seen with - 16.04 - 18.04 - 20.04 - 21.10 - 22.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1968028 Title: unattended-upgrades if enabled wont disable interactivemode Status in unattended-upgrades package in Ubuntu: New Bug description: unattended-upgrades if enabled wont disable interactive mode. In tune an unattended upgrade stops waiting for input never to expect, because the dialog displayed is never seen by anyone. Updates will not be installed at all in some cases. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: unattended-upgrades 2.8ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 6 12:27:22 2022 InstallationDate: Installed on 2021-08-18 (231 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1968028/+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 1968028] [NEW] unattended-upgrades if enabled wont disable interactivemode
Public bug reported: unattended-upgrades if enabled wont disable interactive mode. In tune an unattended upgrade stops waiting for input never to expect, because the dialog displayed is never seen by anyone. Updates will not be installed at all in some cases. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: unattended-upgrades 2.8ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 6 12:27:22 2022 InstallationDate: Installed on 2021-08-18 (231 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1968028 Title: unattended-upgrades if enabled wont disable interactivemode Status in unattended-upgrades package in Ubuntu: New Bug description: unattended-upgrades if enabled wont disable interactive mode. In tune an unattended upgrade stops waiting for input never to expect, because the dialog displayed is never seen by anyone. Updates will not be installed at all in some cases. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: unattended-upgrades 2.8ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 6 12:27:22 2022 InstallationDate: Installed on 2021-08-18 (231 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1968028/+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 1958019]
The issue appears to be that the Nvidia kernel module is failing to build and therefore you do not have working Nvidia support with this kernel. I'm not sure how you configured your kernel so I suspect you have one OR both of the following issues: 1. Nvidia's drivers do not yet support 5.18-rc1. Either Nvidia hasn't added support yet or your distribution's drivers are a little behind. Given that this is an rc1, it could be Nvidia that's behind. 2. Something in your kernel config is incompatible with the Nvidia drivers. I strongly suspect it's #1 as others are having the same problem. try: lsmod | grep nvidia You likely won't see anything. At this point, it depends what's more important to you... Gaming or sound. You can revert to an older kernel or remove the Nvidia drivers for now. Eventually, newer kernels will be supported. In my experience, Nvidia usually isn't too far behind the curve on newer kernel support. On a related note, brightness control with Nvidia in discrete mode has never worked for me on my Lenovo Legion 7i 16ITHg6. (In reply to Darin Miller from comment #594) > Currently the 5.18-rc1 kernel throws an error when attempting install 510 > drivers: > >dpkg: error processing package nvidia-driver-510 (--configure): > dependency problems - leaving unconfigured > > Subsequently, laptop refuses to boot discrete graphics when prime-select = > nvidia. However, on-demand "works" (but no perf tests to support). > > Regardless, brightness control have always worked in on-demand or "intel" > (built-in vega) graphics mode. > > As soon as I can fully install the 510 driver, I will check brightness > controls and report back. (We need another thread for this discussion other > this bug report... any suggestions?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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.lau
[Touch-packages] [Bug 1967620] Re: [FFe] LXC 5.0 LTS
This bug was fixed in the package lxc - 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 --- lxc (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1) jammy; urgency=medium * Pre-release snapshot of LXC 5.0 LTS (LP: #1967620) - New configuration keys: - lxc.cgroup.dir.monitor.pivot - lxc.cgroup.dir.monitor - lxc.cgroup.dir.container.inner - lxc.cgroup.dir.container - lxc.time.offset.boot - lxc.time.offset.monotonic - veth.n_rxqueues - veth.n_txqueues - veth.vlan.id - veth.vlan.tagged.id * Drop patches (now upstreamed): - 0002-lxc-checkconfig-Fix-bashism.patch - 0003-doc-Fix-reverse-allowlist-denylist.patch * Update lintian overrides for current lintian version * debian/control: Switch to debhelper-compat -- Stéphane Graber Tue, 05 Apr 2022 18:07:22 -0400 ** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1967620 Title: [FFe] LXC 5.0 LTS Status in lxc package in Ubuntu: Fix Released Bug description: LXC 5.0 LTS will very soon be released. The upstream release has been held up due to an incomplete port to meson (and deprecation of autotools), it's otherwise been ready to go for a few months. As far as LXC releases go, it's a very light one. Comparing it to current 4.0.12, we have: - No liblxc API changes at all (no new symbols or changes to headers) - Addition of a few configuration keys: - lxc.cgroup.dir.monitor.pivot - lxc.cgroup.dir.monitor - lxc.cgroup.dir.container.inner - lxc.cgroup.dir.container - lxc.time.offset.boot - lxc.time.offset.monotonic - veth.n_rxqueues - veth.n_txqueues - veth.vlan.id - veth.vlan.tagged.id - Port to meson (replacing autotools) Diffstat: ``` stgraber@dakara:~/data/code/lxc/lxc (lxc/master)$ git diff lxc-4.0.12.. . | diffstat .gitignore |1 config/init/systemd/Makefile.am| 10 + config/init/systemd/lxc-net.service.in |1 configure.ac |5 doc/api-extensions.md |9 + doc/ja/lxc.container.conf.sgml.in | 129 - doc/lxc.container.conf.sgml.in | 98 lxc.spec.in|1 meson.build|4 src/lxc/api_extensions.h |3 src/lxc/cgroups/cgfsng.c | 93 +++ src/lxc/cmd/lxc-checkconfig.in |6 - src/lxc/cmd/lxc_monitord.c | 59 + src/lxc/cmd/lxc_user_nic.c |2 src/lxc/conf.c | 11 + src/lxc/confile.c | 664 +--- src/lxc/network.c | 18 ++- src/lxc/network.h |4 src/lxc/terminal.c |1 src/lxc/terminal.h |3 src/lxc/tools/lxc_autostart.c |8 + src/lxc/utils.c|3 src/tests/aa.c |2 src/tests/config_jump_table.c |2 src/tests/containertests.c |2 src/tests/get_item.c | 90 ++- src/tests/getkeys.c|2 src/tests/locktests.c |2 src/tests/lxc-test-utils.c | 16 +- src/tests/meson.build | 534 ++ src/tests/mount_injection.c|2 src/tests/parse_config_file.c | 17 ++ src/tests/reboot.c |2 src/tests/share_ns.c |4 src/tests/snapshot.c |2 35 files changed, 1676 insertions(+), 134 deletions(-) ``` LXC 4.0.12 which we released on Feb 1st has all the bugfixes and other non-feature changes from LXC 5.0, making this quite a small and generally safe delta. The new features can be roughly categorized as: - Improve flexibility in cgroup configuration (make naming of /sys/fs/cgroup directories configurable) - Add support for the time namespace (clock offset) - Add support for configuring (basic sysctl) the number of veth queues - Add support for bridge VLAN filtering on veth devices LXC 5.0 will be an upstream LTS with a support duration matching that of Ubuntu 22.04 or until June 2027. Jammy currently ships LXC 4.0.12 which is only supported until June 2025 and will not see new bugfix releases after LXC 5.0 comes out (only security). LXC is unseeded and in universe these days. The main goal of putting the new LTS in the
[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
> Is there any option to do this via portals - ie can evince use > org.freedesktop.portal.OpenURI to open the URI? Would then this > allow to avoid going via xdg-open? Evince is using g_app_info_launch_default_for_uri(), which can use the portal interface: https://gitlab.gnome.org/GNOME/evince/-/blob/main/shell/ev- window.c#L6775-6778 However, it only does this as a fallback if no desktop file supports the URI. This is intended to allow a confined app to handle some file types within the sandbox before falling back to portals for everything else. In the case of Evince running on the host system and seeing all the desktop files in /usr/share/applications and other locations, it likely won't ever call the portal API. It'd be possible to code in explicit portal API calls, but it isn't something that Evince packaged as a flatpak or snap would need. So it might end up as a distro patch we'd be on the hook to maintain forever. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1961558] Re: 802.1x connection Handshake failure ssl3 error in Jammy Jellyfish
*** This bug is a duplicate of bug 1958267 *** https://bugs.launchpad.net/bugs/1958267 ** This bug has been marked a duplicate of bug 1958267 "Connection failed" for WPA Enterprise network eduroam -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1961558 Title: 802.1x connection Handshake failure ssl3 error in Jammy Jellyfish Status in network-manager package in Ubuntu: Confirmed Bug description: I had install Jammy (beta) release to test it. I have my network with Radius authentication configured, so we have made a Network Profile enabling 802.1x authentication in Ubuntu. When I tried to connecting to the network it doesn't worked. I saw the logs (see picture) and it says that it was a handshake failure in the connection because there is a SSL3 error. I read that probably it can be a problem with the legacy renegotiation in the handshake, but I'm not sure why happens that and what can I do to fix this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1961558/+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 1956603] Re: > Internal error: Could not resolve keysym ...
Just got 1.75-1 version from jammy-proposed. After a reboot, all the previous errors reported above are now gone. Thanks for the upload; this is fixed for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1956603 Title: > Internal error: Could not resolve keysym ... Status in xlibs: Unknown Status in libx11 package in Ubuntu: Fix Committed Status in x11-xkb-utils package in Ubuntu: Confirmed Bug description: Get lot of such warnings into Jammy logged; Actual libx11 is 1.7.2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86MediaRepeat /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Images /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NotificationCenter /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86PickupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86HangupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn_Esc /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86FnRightShift /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric0 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric1 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric3 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric4 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric5 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric6 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric7 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric8 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric9 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericStar /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericPound /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericA /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericB /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericC /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericD /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraFocus /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86WPSButton /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomIn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomOut /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraLeft /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraRight /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOff /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantToggle /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86LightsToggle --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed (WARNING! Diff b
[Touch-packages] [Bug 1956603] Re: > Internal error: Could not resolve keysym ...
M bad, it is 1.7.5-1 version indeed, but post #26 above is not editable : yellow icon seems inactive. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1956603 Title: > Internal error: Could not resolve keysym ... Status in xlibs: Unknown Status in libx11 package in Ubuntu: Fix Committed Status in x11-xkb-utils package in Ubuntu: Confirmed Bug description: Get lot of such warnings into Jammy logged; Actual libx11 is 1.7.2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86MediaRepeat /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF8610ChannelsDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Images /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NotificationCenter /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86PickupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86HangupPhone /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Fn_Esc /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86FnRightShift /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric0 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric1 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric2 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric3 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric4 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric5 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric6 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric7 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric8 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86Numeric9 /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericStar /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericPound /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericA /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericB /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericC /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86NumericD /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraFocus /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86WPSButton /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomIn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraZoomOut /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraUp /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraDown /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraLeft /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86CameraRight /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOn /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantOff /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86AttendantToggle /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym XF86LightsToggle --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed (WARNING! Diff between built and installed module!) GraphicsCard: Int
[Touch-packages] [Bug 1968007] [NEW] $HOME/.local/bin not added to PATH env variable
Public bug reported: Although the path $HOME/.local/bin exists, it is not added to the path environment variable in Ubuntu 22.04. Re-logging or rebooting does not fix the problem. Manually running if [ -d "$HOME/.local/bin" ] ; then PATH="$HOME/.local/bin:$PATH" fi works as expected. The aboth lines ARE included in the .profile script. I know that there were already some issued with the mentioned path in previous versions of Ubuntu, however, until now installing some program with pip install --user and re-logging always fixed the issue. I'm running Ubuntu jammy in a VirtualBox (Version 6.1.32 r149290), but I don't think this is of any relevance. Output of ubuntu-bug bash: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 10:11:13 2022 Dependencies: base-files 12ubuntu3 bash-completion 1:2.11-5ubuntu1 debianutils 5.5-1ubuntu2 gcc-12-base 12-20220319-1ubuntu1 libc6 2.35-0ubuntu3 libcrypt1 1:4.4.27-1 libgcc-s1 12-20220319-1ubuntu1 libidn2-0 2.3.2-2build1 libtinfo6 6.3-2 libunistring2 1.0-1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Package: bash 5.1-6ubuntu1 PackageArchitecture: amd64 ProcCpuinfoMinimal: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 158 model name : Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz stepping : 10 cpu MHz: 2904.002 cache size : 12288 KB physical id: 0 siblings : 4 core id: 3 cpu cores : 4 apicid : 3 initial apicid : 3 fpu: yes fpu_exception : yes cpuid level: 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti fsgsbase avx2 invpcid rdseed clflushopt md_clear flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds bogomips : 5808.00 clflush size : 64 cache_alignment: 64 address sizes : 39 bits physical, 48 bits virtual power management: ProcEnviron: LC_TIME=de_DE.UTF-8 LD_LIBRARY_PATH= LC_MONETARY=de_DE.UTF-8 TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LC_ADDRESS=de_DE.UTF-8 LANG=en_US.UTF-8 LC_TELEPHONE=de_DE.UTF-8 SHELL=/usr/bin/zsh LC_NAME=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 SourcePackage: bash Tags: wayland-session jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Tags added: jammy ** Package changed: cheese (Ubuntu) => bash (Ubuntu) -- 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/1968007 Title: $HOME/.local/bin not added to PATH env variable Status in bash package in Ubuntu: New Bug description: Although the path $HOME/.local/bin exists, it is not added to the path environment variable in Ubuntu 22.04. Re-logging or rebooting does not fix the problem. Manually running if [ -d "$HOME/.local/bin" ] ; then PATH="$HOME/.local/bin:$PATH" fi works as expected. The aboth lines ARE included in the .profile script. I know that there were already some issued with the mentioned path in previous versions of Ubuntu, however, until now installing some program with pip install --user and re-logging always fixed the issue. I'm running Ubuntu jammy in a VirtualBox (Version 6.1.32 r149290), but I don't think this is of any relevance. Output of ubuntu-bug bash: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 10:11:13 2022 Dependencies: base-files 12ubuntu3 bash-completion 1:2.11-5ubuntu1 debianutils 5.5-1ubuntu2 gcc-12-base 12-20220319-1ubuntu1 libc6 2.35-0ubuntu3 libcrypt1 1:4.4.27-1 libgcc-s1 12-20220319-1ubuntu1 libidn2-0 2.3.2-2build1 libtinfo6 6.3-2 libunistring2 1.0-1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Package: bash 5.1-6ubuntu1 PackageArchitecture: amd64 ProcCpuinfoMinimal: processor: 3 vendor_id: GenuineIntel cpu family : 6 mo
[Touch-packages] [Bug 1968007] [NEW] $HOME/.local/bin not added to PATH env variable
You have been subscribed to a public bug: Although the path $HOME/.local/bin exists, it is not added to the path environment variable in Ubuntu 22.04. Re-logging or rebooting does not fix the problem. Manually running if [ -d "$HOME/.local/bin" ] ; then PATH="$HOME/.local/bin:$PATH" fi works as expected. The aboth lines ARE included in the .profile script. I know that there were already some issued with the mentioned path in previous versions of Ubuntu, however, until now installing some program with pip install --user and re-logging always fixed the issue. I'm running Ubuntu jammy in a VirtualBox (Version 6.1.32 r149290), but I don't think this is of any relevance. Output of ubuntu-bug bash: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 10:11:13 2022 Dependencies: base-files 12ubuntu3 bash-completion 1:2.11-5ubuntu1 debianutils 5.5-1ubuntu2 gcc-12-base 12-20220319-1ubuntu1 libc6 2.35-0ubuntu3 libcrypt1 1:4.4.27-1 libgcc-s1 12-20220319-1ubuntu1 libidn2-0 2.3.2-2build1 libtinfo6 6.3-2 libunistring2 1.0-1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-30 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Package: bash 5.1-6ubuntu1 PackageArchitecture: amd64 ProcCpuinfoMinimal: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 158 model name : Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz stepping : 10 cpu MHz: 2904.002 cache size : 12288 KB physical id: 0 siblings : 4 core id: 3 cpu cores : 4 apicid : 3 initial apicid : 3 fpu: yes fpu_exception : yes cpuid level: 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti fsgsbase avx2 invpcid rdseed clflushopt md_clear flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds bogomips : 5808.00 clflush size : 64 cache_alignment: 64 address sizes : 39 bits physical, 48 bits virtual power management: ProcEnviron: LC_TIME=de_DE.UTF-8 LD_LIBRARY_PATH= LC_MONETARY=de_DE.UTF-8 TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LC_ADDRESS=de_DE.UTF-8 LANG=en_US.UTF-8 LC_TELEPHONE=de_DE.UTF-8 SHELL=/usr/bin/zsh LC_NAME=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 SourcePackage: bash Tags: wayland-session jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- $HOME/.local/bin not added to PATH env variable https://bugs.launchpad.net/bugs/1968007 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
** Changed in: pam Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1893716 Title: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions Status in PAM: New Status in landscape-client package in Ubuntu: Fix Released Status in pam package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in update-motd package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: Fix Released Bug description: My client has 200+ devices automatically uploading information via sftp and scp to a server every few minutes. After a recent update, I noticed the load on their server spiking through the roof. Upon investigation, I discovered a horde of landscape-sysinfo and /usr/bin/lsb_release processes running that correlated with login session notifications in /var/log/syslog and the load spikes. It appears that even in non-interactive sessions where this information will never be seen, the configuration options below in /etc/pam.d/sshd cause these items to be launched (in fact, probably everything in /etc/update-motd.d). This only started on the system in question after a recent set of system updates were installed. The content of /etc/update-motd.d/* really, really, really shouldn't be executed if the session in question is not interactive, as it provides no value at all. Unfortunately, to disable it for these non- interactive sessions, we also have to disable it for the interactive ones as well where it has some value (though not enough to make spiking the load on this server through the roof an acceptable tradeoff). # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. #sessionoptional pam_motd.so motd=/run/motd.dynamic #sessionoptional pam_motd.so noupdate Also, looking at the script 00-header in /etc/update-motd.d/, /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release does include the necessary information: [ -r /etc/lsb-release ] && . /etc/lsb-release if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then # Fall back to using the very slow lsb_release utility DISTRIB_DESCRIPTION=$(lsb_release -s -d) fi # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/pam/+bug/1893716/+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 1967620] Re: [FFe] LXC 5.0 LTS
** Changed in: lxc (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1967620 Title: [FFe] LXC 5.0 LTS Status in lxc package in Ubuntu: Triaged Bug description: LXC 5.0 LTS will very soon be released. The upstream release has been held up due to an incomplete port to meson (and deprecation of autotools), it's otherwise been ready to go for a few months. As far as LXC releases go, it's a very light one. Comparing it to current 4.0.12, we have: - No liblxc API changes at all (no new symbols or changes to headers) - Addition of a few configuration keys: - lxc.cgroup.dir.monitor.pivot - lxc.cgroup.dir.monitor - lxc.cgroup.dir.container.inner - lxc.cgroup.dir.container - lxc.time.offset.boot - lxc.time.offset.monotonic - veth.n_rxqueues - veth.n_txqueues - veth.vlan.id - veth.vlan.tagged.id - Port to meson (replacing autotools) Diffstat: ``` stgraber@dakara:~/data/code/lxc/lxc (lxc/master)$ git diff lxc-4.0.12.. . | diffstat .gitignore |1 config/init/systemd/Makefile.am| 10 + config/init/systemd/lxc-net.service.in |1 configure.ac |5 doc/api-extensions.md |9 + doc/ja/lxc.container.conf.sgml.in | 129 - doc/lxc.container.conf.sgml.in | 98 lxc.spec.in|1 meson.build|4 src/lxc/api_extensions.h |3 src/lxc/cgroups/cgfsng.c | 93 +++ src/lxc/cmd/lxc-checkconfig.in |6 - src/lxc/cmd/lxc_monitord.c | 59 + src/lxc/cmd/lxc_user_nic.c |2 src/lxc/conf.c | 11 + src/lxc/confile.c | 664 +--- src/lxc/network.c | 18 ++- src/lxc/network.h |4 src/lxc/terminal.c |1 src/lxc/terminal.h |3 src/lxc/tools/lxc_autostart.c |8 + src/lxc/utils.c|3 src/tests/aa.c |2 src/tests/config_jump_table.c |2 src/tests/containertests.c |2 src/tests/get_item.c | 90 ++- src/tests/getkeys.c|2 src/tests/locktests.c |2 src/tests/lxc-test-utils.c | 16 +- src/tests/meson.build | 534 ++ src/tests/mount_injection.c|2 src/tests/parse_config_file.c | 17 ++ src/tests/reboot.c |2 src/tests/share_ns.c |4 src/tests/snapshot.c |2 35 files changed, 1676 insertions(+), 134 deletions(-) ``` LXC 4.0.12 which we released on Feb 1st has all the bugfixes and other non-feature changes from LXC 5.0, making this quite a small and generally safe delta. The new features can be roughly categorized as: - Improve flexibility in cgroup configuration (make naming of /sys/fs/cgroup directories configurable) - Add support for the time namespace (clock offset) - Add support for configuring (basic sysctl) the number of veth queues - Add support for bridge VLAN filtering on veth devices LXC 5.0 will be an upstream LTS with a support duration matching that of Ubuntu 22.04 or until June 2027. Jammy currently ships LXC 4.0.12 which is only supported until June 2025 and will not see new bugfix releases after LXC 5.0 comes out (only security). LXC is unseeded and in universe these days. The main goal of putting the new LTS in the release is to reduce the maintenance cost for the Ubuntu LTS and to satisfy some of Canonical's customers that are directly using those packages and would expect a consistent set of LTS releases. LXCFS 5.0 is already in jammy and LXD 5.0 has similarly been released, though that one ships exclusively as a snap. If we can get general agreement that getting this LXC release in Ubuntu 22.04 is fine, what I can do to fast track things a bit is upload a 5.0~git-hash version which still relies on autotools, get that do clear autopkgtest and CI and then follow that up with the final 5.0 with the meson port as soon as it's complete on our side (expecting about a week, just got two directories to port). As a reminder, this is all unseeded and in universe, so overall impact should be quite low. Full upstream d
[Touch-packages] [Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
So can we consider the issue fixed from the pulseaudio side in the current release? It's built with gstreamer and working as expected, gst- plugins-bad is a suggests, we can't depends on it because it's in universe ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices Status in PulseAudio: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Confirmed Status in gstreamer1.0 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Bug description: After the announcements of PulseAudio 15 and Gstreamer 1.20, which both advertised LDAC and AptX (HD) support, I expected that jammy (22.04) would support those codecs. Though in reality it seems that something is missing, gstreamer reports that those codecs are supported but "pactl [...] list-codec" only lists sbc (and variants). Checking here https://packages.ubuntu.com/jammy/pulseaudio-module- bluetooth it seems that PulseAudio is not built with gstreamer support, is that the current blocker? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1960307/+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 1967993] Re: Skipping/stuttering audio in browser and gaming with steam
*** This bug is a duplicate of bug 1967995 *** https://bugs.launchpad.net/bugs/1967995 I'm regenerating this ticket as the proper user. ** This bug has been marked a duplicate of bug 1967995 [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound -- 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/1967993 Title: Skipping/stuttering audio in browser and gaming with steam Status in pulseaudio package in Ubuntu: New Bug description: In the last 24 hours, my system has started having skipping/stuttering audio when gaming, or watching videos on youtube in chrome, and no audio at all when using VLC to play music files or watching youtube in Firefox. I believe I did a system update in the last week or so but I don't know if that is the cause. Description: Ubuntu 20.04.4 LTS Release: 20.04 pulseaudio: Installed: 1:13.99.1-1ubuntu3.13 Candidate: 1:13.99.1-1ubuntu3.13 Version table: *** 1:13.99.1-1ubuntu3.13 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 5 23:54:40 2022 InstallationDate: Installed on 2020-08-31 (582 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-kitty PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450 I AORUS PRO WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450 I AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1967993/+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 1967993] [NEW] Skipping/stuttering audio in browser and gaming with steam
*** This bug is a duplicate of bug 1967995 *** https://bugs.launchpad.net/bugs/1967995 Public bug reported: In the last 24 hours, my system has started having skipping/stuttering audio when gaming, or watching videos on youtube in chrome, and no audio at all when using VLC to play music files or watching youtube in Firefox. I believe I did a system update in the last week or so but I don't know if that is the cause. Description:Ubuntu 20.04.4 LTS Release:20.04 pulseaudio: Installed: 1:13.99.1-1ubuntu3.13 Candidate: 1:13.99.1-1ubuntu3.13 Version table: *** 1:13.99.1-1ubuntu3.13 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 5 23:54:40 2022 InstallationDate: Installed on 2020-08-31 (582 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-kitty PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450 I AORUS PRO WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450 I AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1967993 Title: Skipping/stuttering audio in browser and gaming with steam Status in pulseaudio package in Ubuntu: New Bug description: In the last 24 hours, my system has started having skipping/stuttering audio when gaming, or watching videos on youtube in chrome, and no audio at all when using VLC to play music files or watching youtube in Firefox. I believe I did a system update in the last week or so but I don't know if that is the cause. Description: Ubuntu 20.04.4 LTS Release: 20.04 pulseaudio: Installed: 1:13.99.1-1ubuntu3.13 Candidate: 1:13.99.1-1ubuntu3.13 Version table: *** 1:13.99.1-1ubuntu3.13 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 5 23:54:40 2022 InstallationDate: Installed on 2020-08-31 (582 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-kitty PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450 I AORUS PRO WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 d
[Touch-packages] [Bug 1967993] Re: Skipping/stuttering audio in browser and gaming with steam
*** This bug is a duplicate of bug 1967995 *** https://bugs.launchpad.net/bugs/1967995 BTW pacmd list works fine if I run as my user. I think maybe submitting the bug as root caused that command to fail. Memory blocks currently allocated: 3, size: 143.3 KiB. Memory blocks allocated during the whole lifetime: 53948, size: 175.7 MiB. Memory blocks imported from other processes: 0, size: 0 B. Memory blocks exported to other processes: 0, size: 0 B. Total sample cache size: 79.3 KiB. Default sample spec: s16le 2ch 44100Hz Default channel map: front-left,front-right Default sink name: alsa_output.usb-Logitech_Logitech_G930_Headset-00.iec958-stereo Default source name: alsa_input.usb-Logitech_Logitech_G930_Headset-00.mono-fallback Memory blocks of type POOL: 2 allocated/29770 accumulated. Memory blocks of type POOL_EXTERNAL: 0 allocated/724 accumulated. Memory blocks of type APPENDED: 1 allocated/1 accumulated. Memory blocks of type USER: 0 allocated/0 accumulated. Memory blocks of type FIXED: 0 allocated/19341 accumulated. Memory blocks of type IMPORTED: 0 allocated/4836 accumulated. 30 module(s) loaded. index: 0 name: argument: <> used: -1 load once: yes properties: module.author = "Lennart Poettering" module.description = "Automatically restore the volume/mute state of devices" module.version = "13.99.1" index: 1 name: argument: <> used: -1 load once: yes properties: module.author = "Lennart Poettering" module.description = "Automatically restore the volume/mute/device state of streams" module.version = "13.99.1" index: 2 name: argument: <> used: -1 load once: yes properties: module.author = "Lennart Poettering" module.description = "Automatically restore profile of cards" module.version = "13.99.1" index: 3 name: argument: <> used: -1 load once: yes properties: module.author = "Lennart Poettering" module.description = "Augment the property sets of streams with additional static information" module.version = "13.99.1" index: 4 name: argument: <> used: -1 load once: yes properties: module.author = "David Henningsson" module.description = "Switches ports and profiles when devices are plugged/unplugged" module.version = "13.99.1" index: 5 name: argument: <> used: -1 load once: yes properties: module.author = "Michael Terry" module.description = "When a sink/source is added, switch to it or conditionally switch to it" module.version = "13.99.1" index: 6 name: argument: <> used: -1 load once: yes properties: module.author = "Lennart Poettering" module.description = "Detect available audio hardware and load matching drivers" module.version = "13.99.1" index: 7 name: argument: <> used: -1 load once: yes properties: module.author = "Frédéric Dalleau, Pali Rohár" module.description = "Policy module to make using bluetooth devices out-of-the-box easier" module.version = "13.99.1" index: 8 name: argument: <> used: -1 load once: yes properties: module.author = "João Paulo Rechi Vita" module.description = "Detect available Bluetooth daemon and load the corresponding discovery module" module.version = "13.99.1" index: 9 name: argument: <> used: -1 load once: yes properties: module.author = "João Paulo Rechi Vita" module.description = "Detect available BlueZ 5 Bluetooth audio devices and load BlueZ 5 Bluetooth audio drivers" module.version = "13.99.1" index: 10 name: argument: <> used: -1 load once: no properties: module.author = "Lennart Poettering" module.description = "Native protocol (UNIX sockets)" module.version = "13.99.1" index: 11 name: argument: <> used: -1 load once: yes properties: module.author = "Lennart Poettering" module.description = "Automatically restore the default sink and source" module.version = "13.99.1" index: 12 name: argument: <> used: -1 load once: yes properties: module.author = "Colin Guthrie" module.descri
[Touch-packages] [Bug 1967995] [NEW] [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound
Public bug reported: In the last 24 hours, my system has started having skipping/stuttering audio when gaming, or watching videos on youtube in chrome, and no audio at all when using VLC to play music files or watching youtube in Firefox. I believe I did a system update in the last week or so but I don't know if that is the cause. Description: Ubuntu 20.04.4 LTS Release: 20.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 00:05:34 2022 InstallationDate: Installed on 2020-08-31 (582 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Headset successful Symptom_Card: G930 - Logitech G930 Headset Symptom_PulseAudioLog: Apr 05 23:40:42 nzxt dbus-daemon[1169]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.40' (uid=125 pid=1765 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Apr 05 23:41:59 nzxt systemd[1655]: pulseaudio.service: Succeeded. Apr 05 23:42:09 nzxt systemd[1655]: pulseaudio.socket: Succeeded. Apr 05 23:49:33 nzxt sudo[8926]: root : TTY=unknown ; PWD=/home/raj ; USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; COMMAND=/usr/bin/xdg-open https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/b77c80a0-b575-11ec-b9ed-40a8f0305cb4? Apr 05 23:54:56 nzxt sudo[11680]: root : TTY=unknown ; PWD=/home/raj ; USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; COMMAND=/usr/bin/xdg-open https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/77aee818-b576-11ec-b78d-40a8f0308420? Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450 I AORUS PRO WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450 I AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1967995 Title: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: In the last 24 hours, my system has started having skipping/stuttering audio when gaming, or watching videos on youtube in chrome, and no audio at all when using VLC to play music files or watching youtube in Firefox. I believe I did a system update in the last week or so but I don't know if that is the cause. Description: Ubuntu 20.04.4 LTS Release: 20.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 00:05:34 2022 InstallationDate: Installed on 2020-08-31 (582 da
