[Touch-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
** Tags added: originate-from-2046930 -- 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/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
After enabled the proposed, updated the mesa packages, it works perfectly on ThinkPad MTL platforms. Thanks! Before: $ /usr/lib/nux/unity_support_test -p OpenGL vendor string: Mesa OpenGL renderer string: llvmpipe (LLVM 15.0.7, 256 bits) OpenGL version string: 4.5 (Compatibility Profile) Mesa 23.0.4-0ubuntu1~22.04.1 After: $ /usr/lib/nux/unity_support_test -p OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Graphics (MTL) OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.2.1-1ubuntu3.1~22.04.1 ** Tags added: originate-from-2046909 -- 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/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
I've encountered similar issue, and my installation is Ubuntu Mate 22.04. After some tinkering I found a workaround that works for me. On my Ubuntu Mate, there is a file /etc/X11/Xsession.d/80mate-environment containing a command to unset DBUS_SESSION_BUS_ADDRESS, this seems cause the subsequnt call to dbus-launch thought it should use a default value generated by it; so my workaround is to comment the line, from unset DBUS_SESSION_BUS_ADDRESS to #unset DBUS_SESSION_BUS_ADDRESS This works for me. Now Firefox or other none-classic snaps like telegram-desktop works fine. -- 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 1728616] Re: using 'devel' in sources.list causes apt-get update to fail
FYI This bug still exists (in Focal/Mantic made to use `devel`: `sudo sed -i 's/focal/devel/g' /etc/apt/sources.list` - https://discourse.ubuntu.com/t/ubuntu-as-rolling-release/14751/106). Any alternatives or workarounds to get as close to "rolling release" as possible, please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1728616 Title: using 'devel' in sources.list causes apt-get update to fail Status in apt package in Ubuntu: Opinion Bug description: Our /etc/apt/sources.list looks like this: $ cat /etc/apt/sources.list | deb http://archive.ubuntu.com//ubuntu devel main restricted universe multiverse | deb http://archive.ubuntu.com//ubuntu devel-updates main restricted universe multiverse | deb http://archive.ubuntu.com//ubuntu devel-security main restricted universe multiverse | deb http://archive.ubuntu.com//ubuntu devel-backports main restricted universe multiverse I noticed today that 'apt-get update' started failing. Likely that started on Thursday or Friday when bionic opened. This seems less than desireable, but even if the failure is expected, what is the solution to "accept" this change? It does mention 'apt-secure(8)' but nothing there obviously points to the solution. $ sudo apt-get update Hit:2 http://ppa.launchpad.net/uvtool-dev/master/ubuntu devel InRelease Get:1 http://archive.ubuntu.com//ubuntu devel InRelease [235 kB] Get:3 http://archive.ubuntu.com//ubuntu devel-updates InRelease [65.4 kB] Get:4 http://archive.ubuntu.com//ubuntu devel-security InRelease [65.4 kB] Get:5 http://archive.ubuntu.com//ubuntu devel-backports InRelease [65.5 kB] Reading package lists... Done W: Conflicting distribution: http://ppa.launchpad.net/uvtool-dev/master/ubuntu devel InRelease (expected devel but got zesty) W: Conflicting distribution: http://archive.ubuntu.com//ubuntu devel InRelease (expected devel but got bionic) N: Repository 'http://archive.ubuntu.com//ubuntu devel InRelease' changed its 'Version' value from '17.10' to '18.04' E: Repository 'http://archive.ubuntu.com//ubuntu devel InRelease' changed its 'Suite' value from 'artful' to 'bionic' E: Repository 'http://archive.ubuntu.com//ubuntu devel InRelease' changed its 'Codename' value from 'artful' to 'bionic' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. W: Conflicting distribution: http://archive.ubuntu.com//ubuntu devel-updates InRelease (expected devel-updates but got bionic) N: Repository 'http://archive.ubuntu.com//ubuntu devel-updates InRelease' changed its 'Version' value from '17.10' to '18.04' E: Repository 'http://archive.ubuntu.com//ubuntu devel-updates InRelease' changed its 'Suite' value from 'artful-updates' to 'bionic-updates' E: Repository 'http://archive.ubuntu.com//ubuntu devel-updates InRelease' changed its 'Codename' value from 'artful' to 'bionic' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. W: Conflicting distribution: http://archive.ubuntu.com//ubuntu devel-security InRelease (expected devel-security but got bionic) N: Repository 'http://archive.ubuntu.com//ubuntu devel-security InRelease' changed its 'Version' value from '17.10' to '18.04' E: Repository 'http://archive.ubuntu.com//ubuntu devel-security InRelease' changed its 'Suite' value from 'artful-security' to 'bionic-security' E: Repository 'http://archive.ubuntu.com//ubuntu devel-security InRelease' changed its 'Codename' value from 'artful' to 'bionic' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. W: Conflicting distribution: http://archive.ubuntu.com//ubuntu devel-backports InRelease (expected devel-backports but got bionic) N: Repository 'http://archive.ubuntu.com//ubuntu devel-backports InRelease' changed its 'Version' value from '17.10' to '18.04' E: Repository 'http://archive.ubuntu.com//ubuntu devel-backports InRelease' changed its 'Suite' value from 'artful-backports' to 'bionic-backports' E: Repository 'http://archive.ubuntu.com//ubuntu devel-backports InRelease' changed its 'Codename' value from 'artful' to 'bionic' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apt 1.5 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Mon Oct 30 14:37:22 2017 JournalErrors: Hint: You are currently not seeing messages from other users and the system.
[Touch-packages] [Bug 2047008] Re: [SRU] Add Telit FN990 compositions
Hi Simon, Thanks for your take up and the suggestion. If any new cases in the future, yes, we will try the DEP-3 patch headers :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: In Progress Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+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 2047314] Re: leap-second.list expiring this week
I have also been watching the days tick down to expiration. I see that this has been fixed in Debian with tzdata 2023c-5+deb12u1. It would be great if an updated package would flow through Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: leap-second.list expiring this week Status in tzdata package in Ubuntu: Triaged Bug description: It appears the tzdata package has not been updated with the 2023d timezone data. Current distribution is 2023c. leap-seconds.list is expiring Dec 28th 2023, My fix was to download and extract https://data.iana.org/time- zones/releases/tzdata2023d.tar.gz. Then copy the included leap- seconds.list and leapseconds files to /usr/share/zoneinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
kdeplasma should be a fairly easy fix without prompting. I'll work on a profile for it and its add-ons -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in apparmor package in Ubuntu: Confirmed Status in devhelp package in Ubuntu: New Status in digikam package in Ubuntu: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in gnome-packagekit package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kontact package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/+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 2047656] Re: libfluidsynth3 2.3.3-2.1 does not contain the version 2.3.3 but only version 2.3.2
Just going to add: the Ubuntu version *is* 2.3.3, don't let the -2 fool you, that's the Debian revision in the packaging. Looks like it just needs the patch you are referring to which got added between 2.3.3 and 2.3.4, so I can do that, but as I said in my previous comment, it won't be until after January 2 since I'm on break until then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/2047656 Title: libfluidsynth3 2.3.3-2.1 does not contain the version 2.3.3 but only version 2.3.2 Status in fluidsynth package in Ubuntu: Fix Released Status in fluidsynth source package in Mantic: Triaged Status in fluidsynth source package in Noble: Fix Released Bug description: The latest package of fluidsynth should include the sources from version 2.3.3 but the binary includes only version 2.3.2 This version has a bug (see https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to problems in EasyABC. Please include the latest version 2.3.3 from upstream in the ubuntu package. -- Description: Ubuntu 23.10 Release: 23.10 Codename: mantic $ apt-cache policy libfluidsynth3 libfluidsynth3: Installiert: 2.3.3-2.1 Installationskandidat: 2.3.3-2.1 Versionstabelle: *** 2.3.3-2.1 500 500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+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 2047656] Re: libfluidsynth3 2.3.3-2.1 does not contain the version 2.3.3 but only version 2.3.2
I'm on break until Jan 2, but I'll try to fix this as an SRU. ** Changed in: fluidsynth (Ubuntu) Importance: Undecided => Medium ** Changed in: fluidsynth (Ubuntu) Status: New => Triaged ** Changed in: fluidsynth (Ubuntu) Milestone: None => mantic-updates ** Also affects: fluidsynth (Ubuntu Noble) Importance: Medium Status: Triaged ** Also affects: fluidsynth (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: fluidsynth (Ubuntu Mantic) Status: New => Triaged ** Changed in: fluidsynth (Ubuntu Noble) Status: Triaged => Fix Released ** Changed in: fluidsynth (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: fluidsynth (Ubuntu Noble) Importance: Medium => Undecided ** Changed in: fluidsynth (Ubuntu Noble) Milestone: mantic-updates => None ** Changed in: fluidsynth (Ubuntu Mantic) Milestone: None => mantic-updates ** Changed in: fluidsynth (Ubuntu Mantic) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/2047656 Title: libfluidsynth3 2.3.3-2.1 does not contain the version 2.3.3 but only version 2.3.2 Status in fluidsynth package in Ubuntu: Fix Released Status in fluidsynth source package in Mantic: Triaged Status in fluidsynth source package in Noble: Fix Released Bug description: The latest package of fluidsynth should include the sources from version 2.3.3 but the binary includes only version 2.3.2 This version has a bug (see https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to problems in EasyABC. Please include the latest version 2.3.3 from upstream in the ubuntu package. -- Description: Ubuntu 23.10 Release: 23.10 Codename: mantic $ apt-cache policy libfluidsynth3 libfluidsynth3: Installiert: 2.3.3-2.1 Installationskandidat: 2.3.3-2.1 Versionstabelle: *** 2.3.3-2.1 500 500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+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 2047656] [NEW] libfluidsynth3 2.3.3-2.1 does not contain the version 2.3.3 but only version 2.3.2
Public bug reported: The latest package of fluidsynth should include the sources from version 2.3.3 but the binary includes only version 2.3.2 This version has a bug (see https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to problems in EasyABC. Please include the latest version 2.3.3 from upstream in the ubuntu package. -- Description:Ubuntu 23.10 Release:23.10 Codename: mantic $ apt-cache policy libfluidsynth3 libfluidsynth3: Installiert: 2.3.3-2.1 Installationskandidat: 2.3.3-2.1 Versionstabelle: *** 2.3.3-2.1 500 500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: fluidsynth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/2047656 Title: libfluidsynth3 2.3.3-2.1 does not contain the version 2.3.3 but only version 2.3.2 Status in fluidsynth package in Ubuntu: New Bug description: The latest package of fluidsynth should include the sources from version 2.3.3 but the binary includes only version 2.3.2 This version has a bug (see https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to problems in EasyABC. Please include the latest version 2.3.3 from upstream in the ubuntu package. -- Description: Ubuntu 23.10 Release: 23.10 Codename: mantic $ apt-cache policy libfluidsynth3 libfluidsynth3: Installiert: 2.3.3-2.1 Installationskandidat: 2.3.3-2.1 Versionstabelle: *** 2.3.3-2.1 500 500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+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 2040017] Re: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is dif
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-plugins (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/2040017 Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio- default.conf.example', which is different from other instances of package libasound2-plugins:i386 Status in alsa-plugins package in Ubuntu: Confirmed Bug description: I dont know much about ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libasound2-plugins 1.2.7.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Oct 21 02:05:11 2023 DuplicateSignature: package:libasound2-plugins:1.2.7.1-1ubuntu2 Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-KQ6wMx/50-libasound2-plugins_1.2.7.1-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 ErrorMessage: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 InstallationDate: Installed on 2022-12-23 (301 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: alsa-plugins Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 UpgradeStatus: Upgraded to mantic on 2023-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/2040017/+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 2047008] Re: [SRU] Add Telit FN990 compositions
Uploaded with a changelog tweak. It looks like there is precedent for this, but it's in the SRU team's hands now. DEP-3 patch headers next time? ;) ** Also affects: modemmanager (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: modemmanager (Ubuntu) Status: New => Fix Released ** Changed in: modemmanager (Ubuntu Jammy) Status: New => In Progress ** Changed in: modemmanager (Ubuntu) Importance: Undecided => High ** Changed in: modemmanager (Ubuntu Jammy) Importance: Undecided => High ** Changed in: modemmanager (Ubuntu Jammy) Assignee: (unassigned) => Laider Lai (laiderlai) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: In Progress Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Changed in: plasma-desktop (Ubuntu) Importance: Undecided => Critical ** Also affects: kdeplasma-addons (Ubuntu) Importance: Undecided Status: New ** Changed in: kdeplasma-addons (Ubuntu) Importance: Undecided => Critical ** Changed in: kdeplasma-addons (Ubuntu) Status: New => Confirmed -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in apparmor package in Ubuntu: Confirmed Status in devhelp package in Ubuntu: New Status in digikam package in Ubuntu: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in gnome-packagekit package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kontact package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/+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 1964506] [iputils/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: Fix Committed Bug description: = Impact = the ping statistics are incorrect when dealing with truncated packets = Test case = $ ping -c 1 -s 1200 8.8.8.8 should list truncated replies and received packets = Regression potential = the changes are limited to the ping source any regression would impact that utility, check that responses are correctly handled and statistics reflecting what is expected -- Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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]
Created attachment 305664 attachment-13865-0.html I am currently out of the office on holiday I will be returning on Tuesday January 2, I will not be checking email. -- 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.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
Hey it looks like Lenovo has released a new BIOS version for the Legion S7 16ARHA7 Slim model (the one I have that still has no sound). I'm curious if anyone has updated to this BIOS yet and if that's resolved any issues or if this would allow further development on the audio issue. -- 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.launchpad.net/ListHelp
[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Erich: Actually the web browser widget or picture frame are from the kdeplasma-addons source. So not a core part of the Plasma desktop. We just seed those addons packages by default as they are good to have for users. However, you are correct that when installed and a user tries to add them to the desktop, the resulting crash does bring down the whole desktop. -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in apparmor package in Ubuntu: Confirmed Status in devhelp package in Ubuntu: New Status in digikam package in Ubuntu: Confirmed Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in gnome-packagekit package in Ubuntu: Confirmed Status in kontact package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
Problem solved (At last!!). Since I am not a Linux/Debian/Ubuntu matter, I can't give detailed reasoning the cause-consequence relationship. But this is what I did after hundreds of tries. 1. Update SOF firmware binaries. Read this: https://askubuntu.com/questions/1421513/22-04-lts-no-sound-intel-sound-card-snd-hda-intel-not-working 2. Edit '/etc/modprobe.d/alsa-base.conf' to add 'options snd-intel-dspcfg dsp_driver=1' Read this: https://thesofproject.github.io/latest/getting_started/intel_debug/introduction.html Reboot and voilà! I would be happy if I see that this solution works for others. Please comment below if you try this. -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 2047595] Re: sound control panel security
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- 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/2047595 Title: sound control panel security Status in ubuntu-meta package in Ubuntu: New Bug description: The controls in the upper right hand corner, which consist of WiFi Bar, Sound Bar, and Battery Bar icons are unlocked when the machine is locked. This will enable anyone, who has physical access to the machine to change, disable or rearrange any settings available in this interface; 1. WiFi-- add or remove access points, disconnect WiFi, change power modes, styles, keyboard, etc. Power Modes. 2. Sounds, disable or modify sounds, lighting settings 3. Change or modify battery schemes. Power off machines, or sleep / Hibernate machine, etc. lsb_release -rd Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2047595/+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 2047595] [NEW] sound control panel security
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: The controls in the upper right hand corner, which consist of WiFi Bar, Sound Bar, and Battery Bar icons are unlocked when the machine is locked. This will enable anyone, who has physical access to the machine to change, disable or rearrange any settings available in this interface; 1. WiFi-- add or remove access points, disconnect WiFi, change power modes, styles, keyboard, etc. Power Modes. 2. Sounds, disable or modify sounds, lighting settings 3. Change or modify battery schemes. Power off machines, or sleep / Hibernate machine, etc. lsb_release -rd Ubuntu 23.10 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- sound control panel security https://bugs.launchpad.net/bugs/2047595 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta 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 1979258] Re: lxc: lxc-test-parse-config-file failed (failed to set config item)
Thanks! I have checked with our test result, this is not affecting newer kernels any more. But it's still visible <= Jammy (lxc-5.0.0~git2209-g5a7b9ce67). Looks like we will need to backport this. ** Changed in: lxc (Ubuntu) Status: New => Fix Released ** Changed in: lxc (Ubuntu Jammy) Status: New => Confirmed -- 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/1979258 Title: lxc: lxc-test-parse-config-file failed (failed to set config item) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Jammy: Confirmed Bug description: With bug 1943441 (expected value and retrieved value do not match) fixed with lxc 1:4.0.12-0ubuntu1 on Jammy (still exist on F / I) Now this test on Jammy with lxc 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 will fail with: Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file' parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set config item "lxc.selinux.context" to "system_u:system_r:lxc_t:s0:c22" parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set config item "lxc.seccomp.profile" to "/some/seccomp/file" parse_config_file.c: 580: main: lxc.seccomp.profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1979258/+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 1961566] Re: 5.15 kernel selftest srv6_end_dt6_l3vpn_test.sh failure
** Also affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: iproute2 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: iproute2 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1961566 Title: 5.15 kernel selftest srv6_end_dt6_l3vpn_test.sh failure Status in ubuntu-kernel-tests: New Status in iproute2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in iproute2 source package in Focal: New Status in linux source package in Focal: New Status in iproute2 source package in Jammy: Fix Released Status in linux source package in Jammy: Confirmed Bug description: Kernel selftest srv6_end_dt6_l3vpn_test.sh fails on s2lp4.s390x: # selftests: net: srv6_end_dt6_l3vpn_test.sh # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. ... # # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # # # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] # # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1961566/+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
