[Touch-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
** Tags added: fixed-in-mesa-22.3.0 -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Committed Status in kwin package in Debian: New Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
** Changed in: kwin (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Committed -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Committed Status in kwin package in Debian: New Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006756] Re: composite emoji shows extra vertical color lines
This bug was fixed in the package pango1.0 - 1.50.6+ds-2ubuntu1 --- pango1.0 (1.50.6+ds-2ubuntu1) jammy; urgency=medium * Cherry-pick fix for vertical color lines showing with composite emoji (LP: #2006756) -- Jeremy Bicha Thu, 09 Feb 2023 11:34:31 -0500 ** Changed in: pango1.0 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 source package in Jammy: Fix Released Bug description: Impact -- Composite emoji (such as 🫱🏾 [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: 🫱🏾 It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- This is a one line fix cherry-picked from pango 1.50.8 (plus 30+ lines for a test case). pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006756] Update Released
The verification of the Stable Release Update for pango1.0 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 pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 source package in Jammy: Fix Released Bug description: Impact -- Composite emoji (such as 🫱🏾 [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: 🫱🏾 It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- This is a one line fix cherry-picked from pango 1.50.8 (plus 30+ lines for a test case). pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003250] Re: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss
Thank you very much for the status. On our side we improved the ansible logic configuring the networking via netplan the way ansible actually performs netplan apply **only if** there is netplan configuration change. This helps to minimize unexpected bond toggling, but still far from being solved. -- 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/2003250 Title: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: We currently use Ubuntu 22.04.1 LTS including updates for our production cloud (switched from legacy Centos 7). Although we like the distribution we recently hit serious systemd buggy behavior described in [1] bugreport using packages [2]. Unfortunatelly the clouds we are running consist of openstack on top of kubernetes and we need to have complex network configuration including linux bond devices. Our observation is that every time we apply our configuration via CI/CD infrastructure using ansible and netplan (regardless whether there is actual network configuration change) we see approximatelly 8-16 seconds network interruptions and see bond interfaces going DOWN and then UP. We expect bond interfaces stay UP when there is no network configuration change. We went though couple of options how to solve the issue and the first one is to add such existing patch [3] into current systemd-249.11-0ubuntu3.6. Could you comment whether this kind of non-security patch is likely to land in 22.04.1 LTS soon. We are able to help to bring patch into systemd package community way if you suggest the steps. [1] https://github.com/systemd/systemd/issues/25067 [2] Packages root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)' netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 [installed,automatic] systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic] [3] https://github.com/systemd/systemd/pull/25162 [4] # lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250/+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 2002918] Re: ERROR: rejecting excluded file-list name
Yes, it's horribly broken :-( ** Changed in: rsync (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2002918 Title: ERROR: rejecting excluded file-list name Status in rsync package in Ubuntu: Confirmed Bug description: Problems related to --exclude and --filter=protect options are raising error while execution of rsync. The following error is launched: ERROR: rejecting excluded file-list name: rsync error: protocol incompatibility (code 2) at flist.c(994) [receiver=3.2.5] rsync: [sender] write error: Broken pipe (32) It was already reported in: https://github.com/WayneD/rsync/issues/375 There is also a patch released. --- lsb_release -rd Description:Ubuntu 22.10 Release:22.10 apt-cache policy rsync rsync: Instalado: 3.2.5-1 Candidato: 3.2.5-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2002918/+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 1988730] Re: package libsasl2-modules provides only unsafe SASL bind mechanims
This bug was fixed in the package cyrus-sasl2 - 2.1.27+dfsg2-3ubuntu1.2
---
cyrus-sasl2 (2.1.27+dfsg2-3ubuntu1.2) jammy; urgency=medium
* d/control, d/libsasl2-modules-gssapi-mit.install,
d/libsasl2-modules.install: move the SCRAM mechanism to
the libsasl2-modules package (LP: #1988730)
-- Andreas Hasenack Mon, 12 Dec 2022 08:52:45
-0300
** Changed in: cyrus-sasl2 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1988730
Title:
package libsasl2-modules provides only unsafe SASL bind mechanims
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 source package in Jammy:
Fix Released
Status in cyrus-sasl2 package in Debian:
Fix Released
Bug description:
[ Impact ]
The SASL SCRAM mechanism is incorrectly part of the libsasl2-modules-
gssapi-mit package. It has nothing to do with MIT or GSSAPI, and
should be in libsasl2-modules.
Normally this would just be an annoyance, but it just so happens that
this also prevents to have the SCRAM mechanism coexist with the GSSAPI
Heimdal one, because libsasl2-modules-gssapi-{mit,heimdal} conflict
with each other.
This change is moving a file from one package to another, so
appropriate breaks/replaces changes have to be made. This move follows
case #10 from the package transition table[1].
[ Test Plan ]
This test plan revolves around dependency checking and upgrades, to make sure
we don't:
- have conflicting files which would break an upgrade
- have no loss of functionality after an upgrade (since a plugin moved
between packages)
a) SCRAM remains installed
# Install the package that provides SCRAM in jammy
$ sudo apt install libsasl2-modules-gssapi-mit
# Confirm mechanism is there and belongs to libsasl2-modules-gssapi-
mit:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules-gssapi-mit:amd64:
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
# list installed sasl2 packages:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.1
# dist-upgrade or install the new sasl2 packages from proposed
# Confirm the same packages are installed as before the upgrade, just at
their newer versions:
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.2
# Confirm the scram mechanism is still there, as before:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
# But now it belongs to the libsasl2-modules package:
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
b) Following (a), perform a release-upgrade to kinetic, and confirm
that the same sasl2 packages remain installed, but now at the kinetic
version:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-db:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-gssapi-mit:amd64 2.1.28+dfsg-6ubuntu2
And that the scram mechanism is there, and still belongs to the
libsasl2-modules package:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
c) A jammy system WITHOUT the SCRAM mechanism available (i.e.,
libsasl2-modules-gssapi-mit is NOT installed), will get SCRAM
available after the upgrade, but without installing any new package.
# Start with these sasl2 packages installed on jammy:
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
# Confirm SCRAM is not installed:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
ls: cannot access '/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2': No such
file or directory
# Upgrade to the packages in proposed
# Confirm no new sasl2 packages were installed:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
libsa
[Touch-packages] [Bug 1988730] Update Released
The verification of the Stable Release Update for cyrus-sasl2 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 cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1988730
Title:
package libsasl2-modules provides only unsafe SASL bind mechanims
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 source package in Jammy:
Fix Released
Status in cyrus-sasl2 package in Debian:
Fix Released
Bug description:
[ Impact ]
The SASL SCRAM mechanism is incorrectly part of the libsasl2-modules-
gssapi-mit package. It has nothing to do with MIT or GSSAPI, and
should be in libsasl2-modules.
Normally this would just be an annoyance, but it just so happens that
this also prevents to have the SCRAM mechanism coexist with the GSSAPI
Heimdal one, because libsasl2-modules-gssapi-{mit,heimdal} conflict
with each other.
This change is moving a file from one package to another, so
appropriate breaks/replaces changes have to be made. This move follows
case #10 from the package transition table[1].
[ Test Plan ]
This test plan revolves around dependency checking and upgrades, to make sure
we don't:
- have conflicting files which would break an upgrade
- have no loss of functionality after an upgrade (since a plugin moved
between packages)
a) SCRAM remains installed
# Install the package that provides SCRAM in jammy
$ sudo apt install libsasl2-modules-gssapi-mit
# Confirm mechanism is there and belongs to libsasl2-modules-gssapi-
mit:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules-gssapi-mit:amd64:
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
# list installed sasl2 packages:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.1
# dist-upgrade or install the new sasl2 packages from proposed
# Confirm the same packages are installed as before the upgrade, just at
their newer versions:
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.2
# Confirm the scram mechanism is still there, as before:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
# But now it belongs to the libsasl2-modules package:
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
b) Following (a), perform a release-upgrade to kinetic, and confirm
that the same sasl2 packages remain installed, but now at the kinetic
version:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-db:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-gssapi-mit:amd64 2.1.28+dfsg-6ubuntu2
And that the scram mechanism is there, and still belongs to the
libsasl2-modules package:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
c) A jammy system WITHOUT the SCRAM mechanism available (i.e.,
libsasl2-modules-gssapi-mit is NOT installed), will get SCRAM
available after the upgrade, but without installing any new package.
# Start with these sasl2 packages installed on jammy:
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
# Confirm SCRAM is not installed:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
ls: cannot access '/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2': No such
file or directory
# Upgrade to the packages in proposed
# Confirm no new sasl2 packages were installed:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules:amd64 2.1.27+dfsg2-3ubunt
[Touch-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
This bug was fixed in the package libqmi - 1.32.0-1ubuntu0.22.04.1 --- libqmi (1.32.0-1ubuntu0.22.04.1) jammy; urgency=medium * Backport the newer modemmanager stack to the LTS as part of new hardware enablement including FM350 modems (lp: #1950282) -- Sebastien Bacher Tue, 22 Nov 2022 13:17:29 +0100 -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Fix Released Status in libqmi source package in Jammy: Fix Released Status in linux source package in Jammy: New Status in modemmanager source package in Jammy: Fix Released Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
This bug was fixed in the package modemmanager - 1.20.0-1~ubuntu22.04.1 --- modemmanager (1.20.0-1~ubuntu22.04.1) jammy; urgency=medium * Backport the newer modemmanager stack to the LTS as part of new hardware enablement including FM350 modems (lp: #1950282) -- Sebastien Bacher Tue, 13 Dec 2022 13:38:07 +0100 ** Changed in: libqmi (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Fix Released Status in libqmi source package in Jammy: Fix Released Status in linux source package in Jammy: New Status in modemmanager source package in Jammy: Fix Released Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
This bug was fixed in the package libmbim - 1.28.0-1~ubuntu20.04.1 --- libmbim (1.28.0-1~ubuntu20.04.1) jammy; urgency=medium * Backport the newer modemmanager stack to the LTS as part of new hardware enablement including FM350 modems (lp: #1950282) -- Sebastien Bacher Tue, 13 Dec 2022 13:35:17 +0100 ** Changed in: libmbim (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: modemmanager (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Fix Released Status in libqmi source package in Jammy: Fix Released Status in linux source package in Jammy: New Status in modemmanager source package in Jammy: Fix Released Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages M
[Touch-packages] [Bug 2008592] Re: editing python code with idle
I installed the qt6 wayland adapter, and it corrected some problems. I will report back about this occurrence. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2008592 Title: editing python code with idle Status in ibus package in Ubuntu: New Bug description: Using raspPi400, insert using combination of keyboard keys, Shift-Fn- Delete/Insert. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-1 Uname: Linux 5.19.0-1012-raspi aarch64 Architecture: arm64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 25 15:12:32 2023 ExecutablePath: /usr/libexec/ibus-x11 ExecutableTimestamp: 1677098999 ProcCmdline: /usr/libexec/ibus-x11 ProcCwd: /home/hcmeyer ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: ibus UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2008592/+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 1950282] Update Released
The verification of the Stable Release Update for libmbim 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 modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Fix Committed Status in libqmi source package in Jammy: Fix Committed Status in linux source package in Jammy: New Status in modemmanager source package in Jammy: Fix Committed Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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.n
[Touch-packages] [Bug 2008846] [NEW] package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1
Public bug reported: encounter error when attempting to do sudo update, upgrade, and full- upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libssl3:amd64 3.0.2-0ubuntu1.8 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 1 10:28:26 2023 ErrorMessage: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-01 (150 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: openssl Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2008846 Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 Status in openssl package in Ubuntu: New Bug description: encounter error when attempting to do sudo update, upgrade, and full- upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libssl3:amd64 3.0.2-0ubuntu1.8 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 1 10:28:26 2023 ErrorMessage: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-01 (150 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: openssl Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2008846/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
This bug was fixed in the package evince - 42.3-0ubuntu3 --- evince (42.3-0ubuntu3) jammy; urgency=medium * debian/apparmor-profile: - allow access to the libproxy helper pxgsettings which is needed on some configuration to access remote printers (LP: #1915910) -- Sebastien Bacher Wed, 07 Dec 2022 11:35:07 +0100 ** Changed in: evince (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Fix Released Status in libproxy package in Ubuntu: Invalid Status in evince source package in Jammy: Fix Released Status in evince source package in Kinetic: Fix Released Status in evince package in Debian: Fix Released Bug description: * Impact Evince hangs when opening the printing dialog for some users with a remote printer configured and connected * Test case - configure a remote printer and turn it on - open a pdf - try to print the document the print dialog shouldn't freeze the viewer * What could go wrong The change is only allowing access to one extra system binary from the apparmor profile so shouldn't really have an impact on the software behaviour. If the syntax or content of the change was incorrect it could make the apparmor profile not been loaded anymore or block access to thing that should be allowed, so ensure that opening documents, printing and thumbnailing are still working -- audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 2008797] Re: Mouse problems
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Mouse problems + USB mouse doesn't work after resuming from sleep ** Tags added: suspend-resume -- 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/2008797 Title: USB mouse doesn't work after resuming from sleep Status in linux package in Ubuntu: New Bug description: Basic problem is that the usb mouse connects at the start, but after sleep, suddenly stops. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 20:56:40 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GA107M [GeForce RTX 3050 Mobile] [103c:88ec] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Cezanne [103c:88ec] InstallationDate: Installed on 2023-02-28 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: HP Victus by HP Laptop 16-e0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=42da8321-31cc-4d70-aeb1-d0e0f86cc2f9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2021 dmi.bios.release: 15.4 dmi.bios.vendor: AMI dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88EC dmi.board.vendor: HP dmi.board.version: 80.22 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.22 dmi.modalias: dmi:bvnAMI:bvrF.04:bd06/17/2021:br15.4:efr80.22:svnHP:pnVictusbyHPLaptop16-e0xxx:pvr:rvnHP:rn88EC:rvr80.22:cvnHP:ct10:cvrChassisVersion:sku494P3PA#ACJ: dmi.product.family: 103C_5335M7 HP VICTUS dmi.product.name: Victus by HP Laptop 16-e0xxx dmi.product.sku: 494P3PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/linux/+bug/2008797/+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 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op
This bug was fixed in the package software-properties - 0.99.9.11 --- software-properties (0.99.9.11) focal; urgency=medium [ Nathan Pratta Teodosio ] * Disable the Ubuntu Pro UI with an explanation when not connected (lp: #2004634) * Catch exceptions to wait (lp: #2003996) * Initialize pin as empty string (lp: #2004245) -- Sebastien Bacher Fri, 03 Feb 2023 12:30:09 +0100 -- 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/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when opening the 'Enable Ubuntu Pro' dialog on a system not connected to internet * Test case Start software-properties-gtk on a offline system, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 * Regression potential The fix is making the magic token request conditional to the connectivity status, if that was wrong we could end up in a situation where we should display a pincode but don't. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 144, in poll_for_magic_token response = wait(options) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 57, in wait return _wait(options, UAConfig()) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 73, in _wait wait_resp = contract.get_magic_attach_token_info( File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 202, in get_magic_attach_token_info response, _ = self.request_url( File "/usr/lib/python3/dist-packages/uaclient/serviceclient.py", line 72, in request_url response, headers = util.readurl( File "/usr/lib/python3/dist-packages/uaclient/util.py", line 324, in readurl resp = request.urlopen(req, timeout=timeout) File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.10/urllib/request.py", line 519, in open response = self._open(req, data) File "/usr/lib/python3.10/urllib/request.py", line 536, in _open result = self._call_chain(self.handle_open, protocol, protocol + File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain result = func(*args) File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open return self.do_open(http.client.HTTPSConnection, req, File "/usr/lib/python3.10/urllib/request.py", line 1352, in do_open r = h.getresponse() File "/usr/lib/python3.10/http/client.py", line 1374, in getresponse response.begin() File "/usr/lib/python3.10/http/client.py", line 318, in begin version, status, reason = self._read_status() File "/usr/lib/python3.10/http/client.py", line 279, in _read_status line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") File "/usr/lib/python3.10/socket.py", line 705, in readinto return self._sock.recv_into(b) File "/usr/lib/python3.10/ssl.py", line 1274, in recv_into return self.read(nbytes, buffer) File "/usr/lib/python3.10/ssl.py", line 1130, in read return self._sslobj.read(len, buffer) TimeoutError: The read operation timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+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 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op
This bug was fixed in the package software-properties - 0.99.22.6 --- software-properties (0.99.22.6) jammy; urgency=medium [ Nathan Pratta Teodosio ] * Disable the Ubuntu Pro UI with an explanation when not connected (lp: #2004634) * Catch exceptions to wait (lp: #2003996) * Initialize pin as empty string (lp: #2004245) -- Sebastien Bacher Fri, 03 Feb 2023 11:35:08 +0100 ** Changed in: software-properties (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: software-properties (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when opening the 'Enable Ubuntu Pro' dialog on a system not connected to internet * Test case Start software-properties-gtk on a offline system, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 * Regression potential The fix is making the magic token request conditional to the connectivity status, if that was wrong we could end up in a situation where we should display a pincode but don't. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 144, in poll_for_magic_token response = wait(options) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 57, in wait return _wait(options, UAConfig()) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 73, in _wait wait_resp = contract.get_magic_attach_token_info( File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 202, in get_magic_attach_token_info response, _ = self.request_url( File "/usr/lib/python3/dist-packages/uaclient/serviceclient.py", line 72, in request_url response, headers = util.readurl( File "/usr/lib/python3/dist-packages/uaclient/util.py", line 324, in readurl resp = request.urlopen(req, timeout=timeout) File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.10/urllib/request.py", line 519, in open response = self._open(req, data) File "/usr/lib/python3.10/urllib/request.py", line 536, in _open result = self._call_chain(self.handle_open, protocol, protocol + File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain result = func(*args) File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open return self.do_open(http.client.HTTPSConnection, req, File "/usr/lib/python3.10/urllib/request.py", line 1352, in do_open r = h.getresponse() File "/usr/lib/python3.10/http/client.py", line 1374, in getresponse response.begin() File "/usr/lib/python3.10/http/client.py", line 318, in begin version, status, reason = self._read_status() File "/usr/lib/python3.10/http/client.py", line 279, in _read_status line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") File "/usr/lib/python3.10/socket.py", line 705, in readinto return self._sock.recv_into(b) File "/usr/lib/python3.10/ssl.py", line 1274, in recv_into return self.read(nbytes, buffer) File "/usr/lib/python3.10/ssl.py", line 1130, in read return self._sslobj.read(len, buffer) TimeoutError: The read operation timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+subscriptions -- Mailing list: htt
[Touch-packages] [Bug 2004245] Re: /usr/bin/software-properties-gtk:AttributeError:on_radio_toggled:update_state
This bug was fixed in the package software-properties - 0.99.9.11 --- software-properties (0.99.9.11) focal; urgency=medium [ Nathan Pratta Teodosio ] * Disable the Ubuntu Pro UI with an explanation when not connected (lp: #2004634) * Catch exceptions to wait (lp: #2003996) * Initialize pin as empty string (lp: #2004245) -- Sebastien Bacher Fri, 03 Feb 2023 12:30:09 +0100 -- 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/2004245 Title: /usr/bin/software-properties- gtk:AttributeError:on_radio_toggled:update_state Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when fetching a pin from the Ubuntu Pro server is failing * Test case Start software-properties-gtk on a system offline or having internet connectivity issue, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 * Regression potential The fix for that specific issue is to set an initial value to the pin label. If the change of value would confuse some code it would be visible in the Pin section of the Ubuntu Pro tab not reflected the pin code from the server as expected --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+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 2004245] Re: /usr/bin/software-properties-gtk:AttributeError:on_radio_toggled:update_state
This bug was fixed in the package software-properties - 0.99.22.6 --- software-properties (0.99.22.6) jammy; urgency=medium [ Nathan Pratta Teodosio ] * Disable the Ubuntu Pro UI with an explanation when not connected (lp: #2004634) * Catch exceptions to wait (lp: #2003996) * Initialize pin as empty string (lp: #2004245) -- Sebastien Bacher Fri, 03 Feb 2023 11:35:08 +0100 ** Changed in: software-properties (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: software-properties (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004245 Title: /usr/bin/software-properties- gtk:AttributeError:on_radio_toggled:update_state Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when fetching a pin from the Ubuntu Pro server is failing * Test case Start software-properties-gtk on a system offline or having internet connectivity issue, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 * Regression potential The fix for that specific issue is to set an initial value to the pin label. If the change of value would confuse some code it would be visible in the Pin section of the Ubuntu Pro tab not reflected the pin code from the server as expected --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+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 2004634] Re: Disable Ubuntu Pro registration when not online
This bug was fixed in the package software-properties - 0.99.9.11 --- software-properties (0.99.9.11) focal; urgency=medium [ Nathan Pratta Teodosio ] * Disable the Ubuntu Pro UI with an explanation when not connected (lp: #2004634) * Catch exceptions to wait (lp: #2003996) * Initialize pin as empty string (lp: #2004245) -- Sebastien Bacher Fri, 03 Feb 2023 12:30:09 +0100 -- 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/2004634 Title: Disable Ubuntu Pro registration when not online Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact The current UI allows the user to try to register to Ubuntu Pro even when the system isn't online, which eventually leads to an error since the client fails to contact the server. The updated design disable the registration UI in those cases and inform the user they need to get online to be able to register which is a better experience. * Test Case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - disconnect the system, using for example the top panel indicator - start software-properties-gtk and select the Ubuntu Pro tab - click 'Enable Ubuntu Pro' - The dialog controls should be disabled and a string 'Unable to connect to Ubuntu Pro servers. Check your internet connection.' displayed at the bottom - reconnect the system - the dialog control should become active and the label be removed - register to Ubuntu Pro, that should be working * Regression potential If the connectivity check was wrong or not reliable it could be that the dialog controls would be disabled even if the system is online, or that it would fail to detect that the system isn't connected and let the user try to register anyway. The change also adds a new translatable string. Since currently we don't include translations for that new UI it isn't really a regression. We still plan to fix that by the next languagepack update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004634/+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 2004634] Re: Disable Ubuntu Pro registration when not online
This bug was fixed in the package software-properties - 0.99.22.6 --- software-properties (0.99.22.6) jammy; urgency=medium [ Nathan Pratta Teodosio ] * Disable the Ubuntu Pro UI with an explanation when not connected (lp: #2004634) * Catch exceptions to wait (lp: #2003996) * Initialize pin as empty string (lp: #2004245) -- Sebastien Bacher Fri, 03 Feb 2023 11:35:08 +0100 ** Changed in: software-properties (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: software-properties (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004634 Title: Disable Ubuntu Pro registration when not online Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact The current UI allows the user to try to register to Ubuntu Pro even when the system isn't online, which eventually leads to an error since the client fails to contact the server. The updated design disable the registration UI in those cases and inform the user they need to get online to be able to register which is a better experience. * Test Case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - disconnect the system, using for example the top panel indicator - start software-properties-gtk and select the Ubuntu Pro tab - click 'Enable Ubuntu Pro' - The dialog controls should be disabled and a string 'Unable to connect to Ubuntu Pro servers. Check your internet connection.' displayed at the bottom - reconnect the system - the dialog control should become active and the label be removed - register to Ubuntu Pro, that should be working * Regression potential If the connectivity check was wrong or not reliable it could be that the dialog controls would be disabled even if the system is online, or that it would fail to detect that the system isn't connected and let the user try to register anyway. The change also adds a new translatable string. Since currently we don't include translations for that new UI it isn't really a regression. We still plan to fix that by the next languagepack update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004634/+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 2003996] Update Released
The verification of the Stable Release Update for software-properties 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when opening the 'Enable Ubuntu Pro' dialog on a system not connected to internet * Test case Start software-properties-gtk on a offline system, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 * Regression potential The fix is making the magic token request conditional to the connectivity status, if that was wrong we could end up in a situation where we should display a pincode but don't. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 144, in poll_for_magic_token response = wait(options) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 57, in wait return _wait(options, UAConfig()) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 73, in _wait wait_resp = contract.get_magic_attach_token_info( File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 202, in get_magic_attach_token_info response, _ = self.request_url( File "/usr/lib/python3/dist-packages/uaclient/serviceclient.py", line 72, in request_url response, headers = util.readurl( File "/usr/lib/python3/dist-packages/uaclient/util.py", line 324, in readurl resp = request.urlopen(req, timeout=timeout) File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.10/urllib/request.py", line 519, in open response = self._open(req, data) File "/usr/lib/python3.10/urllib/request.py", line 536, in _open result = self._call_chain(self.handle_open, protocol, protocol + File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain result = func(*args) File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open return self.do_open(http.client.HTTPSConnection, req, File "/usr/lib/python3.10/urllib/request.py", line 1352, in do_open r = h.getresponse() File "/usr/lib/python3.10/http/client.py", line 1374, in getresponse response.begin() File "/usr/lib/python3.10/http/client.py", line 318, in begin version, status, reason = self._read_status() File "/usr/lib/python3.10/http/client.py", line 279, in _read_status line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") File "/usr/lib/python3.10/socket.py", line 705, in readinto return self._sock.recv_into(b) File "/usr/lib/python3.10/ssl.py", line 1274, in recv_into return self.read(nbytes, buffer) File "/usr/lib/python3.10/ssl.py", line 1130, in read return self._sslobj.read(len, buffer) TimeoutError: The read operation timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~
[Touch-packages] [Bug 2004245] Update Released
The verification of the Stable Release Update for software-properties 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004245 Title: /usr/bin/software-properties- gtk:AttributeError:on_radio_toggled:update_state Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact An error is triggered when fetching a pin from the Ubuntu Pro server is failing * Test case Start software-properties-gtk on a system offline or having internet connectivity issue, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 * Regression potential The fix for that specific issue is to set an initial value to the pin label. If the change of value would confuse some code it would be visible in the Pin section of the Ubuntu Pro tab not reflected the pin code from the server as expected --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+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 2004634] Update Released
The verification of the Stable Release Update for software-properties 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004634 Title: Disable Ubuntu Pro registration when not online Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact The current UI allows the user to try to register to Ubuntu Pro even when the system isn't online, which eventually leads to an error since the client fails to contact the server. The updated design disable the registration UI in those cases and inform the user they need to get online to be able to register which is a better experience. * Test Case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - disconnect the system, using for example the top panel indicator - start software-properties-gtk and select the Ubuntu Pro tab - click 'Enable Ubuntu Pro' - The dialog controls should be disabled and a string 'Unable to connect to Ubuntu Pro servers. Check your internet connection.' displayed at the bottom - reconnect the system - the dialog control should become active and the label be removed - register to Ubuntu Pro, that should be working * Regression potential If the connectivity check was wrong or not reliable it could be that the dialog controls would be disabled even if the system is online, or that it would fail to detect that the system isn't connected and let the user try to register anyway. The change also adds a new translatable string. Since currently we don't include translations for that new UI it isn't really a regression. We still plan to fix that by the next languagepack update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004634/+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 1978351] Re: MITM vector: ifupdown puts .domains TLD in resolv.conf
This is still a problem. Who would set the importance and assign someone to this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1978351 Title: MITM vector: ifupdown puts .domains TLD in resolv.conf Status in ifupdown package in Ubuntu: Confirmed Bug description: The bug described in https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878?comments=all is a security vulnerability because DNS names that would normally fail are now attempted as "foo.domains". ".domains" is a real TLD, with the registrar "Donuts, Inc." based in Bellvue, WA. "google.com.domains" is registered, for example. So is "test.domains". For users with ifupdown, any Internet request (especially that does not involve some cryptographic payload and destination signature verification) is potentially sending packets to an unintended audience. It's impossible to say, but likely, that malicious registrants are squatting sensitive and common names in the .domains TLD. The ifupdown package is still used by some cloud providers that have not adopted netplan. This vulnerability affects 22.04 and potentially other releases. This issue has not been corrected in 0.8.36+nmu1ubuntu4. With 0.8.36+nmu1ubuntu3 and after an update to 0.8.36+nmu1ubuntu4, the resolv.conf looks like the following (which is vulnerable to mitm attacks): ``` root@foo:~# cat /etc/resolv.conf # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 trust-ad search DOMAINS ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1978351/+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 2000880] Re: systemd-networkd: ActivationPolicy ignored in VLANs
It turns out the issue I was seeing was caused by a patch I was testing for bug 2003250. Without that, this patch works as expected. -- 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/2000880 Title: systemd-networkd: ActivationPolicy ignored in VLANs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Fix Released Bug description: This has been fixed upstream, see Upstream bug: https://github.com/systemd/systemd/issues/22593 Any chance of a backport of the fix to 22.04? Fix: https://github.com/systemd/systemd-stable/pull/211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000880/+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 2003250] Re: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss
Applying the patch from upstream had some unexpected problems, i.e. causing other interfaces not to come up when I would have expected them to. This needs further investigation -- maybe there is some missing logic from current upstream that makes the patch incorrect when backported. For now, this patch will not be backported. -- 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/2003250 Title: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: We currently use Ubuntu 22.04.1 LTS including updates for our production cloud (switched from legacy Centos 7). Although we like the distribution we recently hit serious systemd buggy behavior described in [1] bugreport using packages [2]. Unfortunatelly the clouds we are running consist of openstack on top of kubernetes and we need to have complex network configuration including linux bond devices. Our observation is that every time we apply our configuration via CI/CD infrastructure using ansible and netplan (regardless whether there is actual network configuration change) we see approximatelly 8-16 seconds network interruptions and see bond interfaces going DOWN and then UP. We expect bond interfaces stay UP when there is no network configuration change. We went though couple of options how to solve the issue and the first one is to add such existing patch [3] into current systemd-249.11-0ubuntu3.6. Could you comment whether this kind of non-security patch is likely to land in 22.04.1 LTS soon. We are able to help to bring patch into systemd package community way if you suggest the steps. [1] https://github.com/systemd/systemd/issues/25067 [2] Packages root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)' netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 [installed,automatic] systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic] [3] https://github.com/systemd/systemd/pull/25162 [4] # lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250/+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 610774] Re: pam-auth-update profile for pam-group missing
pam_consolekit is no longer a thing. What's the modern solution now? -- 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/610774 Title: pam-auth-update profile for pam-group missing Status in pam package in Ubuntu: Won't Fix Bug description: Binary package hint: libpam-runtime There is no pam-auth-update profile for pam_group.so This makes it very difficult to actually make use of pam_group.so because even if I add it to /etc/pam.d/common-auth I cannot make use of pam-auth-update any more. This means that instead of relying on pam-auth-update to manage my PAM stack I will have to do it all manually once I start using pam_group.so IMHO pam-auth-update is a great invention and I hope that it will soon become the standard tool for this task. However, a logical consequence of inventing pam-auth-update is in my opinion to supply profiles for common PAM modules. I therefore would like to suggest to break out pam_group.so from libpam-runtime into a package of its own (libpam-group) which would bring the PAM module and the corresponding pam-auth-update profile. A user wishing to use pam_group.so would then be able to simply install libpam-group and have the pam_group.so module enabled automatically through pam-auth-update in the postinst script of libpam-group. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/610774/+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 2008393] Re: armhf dep8 failure due to restrictions changing apparmor profile status
** Description changed: The armhf DEP8 testers in Ubuntu infrastructure have some restrictions and cannot change an apparmor profile. This is causing the tests to fail, because they try to make sure rsyslog is being tested in enforced mode: Enforcing the /etc/apparmor.d/usr.sbin.rsyslogd apparmor profile Setting /etc/apparmor.d/usr.sbin.rsyslogd to enforce mode. ERROR: /sbin/apparmor_parser: Unable to replace "rsyslogd". Permission denied; attempted to load a profile while confined? The package migrated to lunar even with this error because it never had DEP8 tests before, and the armhf baseline was born in this error state. These are the LXD settings used for armhf containers: https://git.launchpad.net/autopkgtest- cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest- cloud/tools/armhf-lxd.userdata#n76 I created an armhf container on a pi4 host (arm64) with these settings, but couldn't reproduce the issue there. There is something else going on in the autopkgtest infra regarding arhmf. FTR, I created the container like this: lxc launch ubuntu-daily:lunar pi4:l-armhf \ -c raw.lxc="apparmor.profile=unconfined" \ -c raw.lxc="seccomp.profile=" \ -c security.nesting=true EDIT: hm, the above actually doesn't work. Only the last raw.lxc value is used. See https://blog.simos.info/how-to-add-multi-line-raw-lxc- configuration-to-lxd/ + + But still, apparmor works just fine. There is some other setup going on + in the autopkgtest infrastructure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2008393 Title: armhf dep8 failure due to restrictions changing apparmor profile status Status in rsyslog package in Ubuntu: In Progress Bug description: The armhf DEP8 testers in Ubuntu infrastructure have some restrictions and cannot change an apparmor profile. This is causing the tests to fail, because they try to make sure rsyslog is being tested in enforced mode: Enforcing the /etc/apparmor.d/usr.sbin.rsyslogd apparmor profile Setting /etc/apparmor.d/usr.sbin.rsyslogd to enforce mode. ERROR: /sbin/apparmor_parser: Unable to replace "rsyslogd". Permission denied; attempted to load a profile while confined? The package migrated to lunar even with this error because it never had DEP8 tests before, and the armhf baseline was born in this error state. These are the LXD settings used for armhf containers: https://git.launchpad.net/autopkgtest- cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest- cloud/tools/armhf-lxd.userdata#n76 I created an armhf container on a pi4 host (arm64) with these settings, but couldn't reproduce the issue there. There is something else going on in the autopkgtest infra regarding arhmf. FTR, I created the container like this: lxc launch ubuntu-daily:lunar pi4:l-armhf \ -c raw.lxc="apparmor.profile=unconfined" \ -c raw.lxc="seccomp.profile=" \ -c security.nesting=true EDIT: hm, the above actually doesn't work. Only the last raw.lxc value is used. See https://blog.simos.info/how-to-add-multi-line-raw-lxc- configuration-to-lxd/ But still, apparmor works just fine. There is some other setup going on in the autopkgtest infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2008393/+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 2000880] Re: systemd-networkd: ActivationPolicy ignored in VLANs
This patch does not seem to work as expected in Jammy. The interface is just not created at all, rather than being created but left DOWN/not activated. I'm not sure we will have time to investigate this further for this upcoming SRU since there are higher-priority issues. -- 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/2000880 Title: systemd-networkd: ActivationPolicy ignored in VLANs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Fix Released Bug description: This has been fixed upstream, see Upstream bug: https://github.com/systemd/systemd/issues/22593 Any chance of a backport of the fix to 22.04? Fix: https://github.com/systemd/systemd-stable/pull/211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000880/+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 2008393] Re: armhf dep8 failure due to restrictions changing apparmor profile status
** Description changed: The armhf DEP8 testers in Ubuntu infrastructure have some restrictions and cannot change an apparmor profile. This is causing the tests to fail, because they try to make sure rsyslog is being tested in enforced mode: Enforcing the /etc/apparmor.d/usr.sbin.rsyslogd apparmor profile Setting /etc/apparmor.d/usr.sbin.rsyslogd to enforce mode. ERROR: /sbin/apparmor_parser: Unable to replace "rsyslogd". Permission denied; attempted to load a profile while confined? The package migrated to lunar even with this error because it never had DEP8 tests before, and the armhf baseline was born in this error state. - - These are the LXD settings used for armhf containers: https://git.launchpad.net/autopkgtest-cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/tools/armhf-lxd.userdata#n76 + These are the LXD settings used for armhf containers: + https://git.launchpad.net/autopkgtest- + cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest- + cloud/tools/armhf-lxd.userdata#n76 I created an armhf container on a pi4 host (arm64) with these settings, but couldn't reproduce the issue there. There is something else going on in the autopkgtest infra regarding arhmf. FTR, I created the container like this: lxc launch ubuntu-daily:lunar pi4:l-armhf \ -c raw.lxc="apparmor.profile=unconfined" \ -c raw.lxc="seccomp.profile=" \ -c security.nesting=true + + EDIT: hm, the above actually doesn't work. Only the last raw.lxc value + is used. See https://blog.simos.info/how-to-add-multi-line-raw-lxc- + configuration-to-lxd/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2008393 Title: armhf dep8 failure due to restrictions changing apparmor profile status Status in rsyslog package in Ubuntu: In Progress Bug description: The armhf DEP8 testers in Ubuntu infrastructure have some restrictions and cannot change an apparmor profile. This is causing the tests to fail, because they try to make sure rsyslog is being tested in enforced mode: Enforcing the /etc/apparmor.d/usr.sbin.rsyslogd apparmor profile Setting /etc/apparmor.d/usr.sbin.rsyslogd to enforce mode. ERROR: /sbin/apparmor_parser: Unable to replace "rsyslogd". Permission denied; attempted to load a profile while confined? The package migrated to lunar even with this error because it never had DEP8 tests before, and the armhf baseline was born in this error state. These are the LXD settings used for armhf containers: https://git.launchpad.net/autopkgtest- cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest- cloud/tools/armhf-lxd.userdata#n76 I created an armhf container on a pi4 host (arm64) with these settings, but couldn't reproduce the issue there. There is something else going on in the autopkgtest infra regarding arhmf. FTR, I created the container like this: lxc launch ubuntu-daily:lunar pi4:l-armhf \ -c raw.lxc="apparmor.profile=unconfined" \ -c raw.lxc="seccomp.profile=" \ -c security.nesting=true EDIT: hm, the above actually doesn't work. Only the last raw.lxc value is used. See https://blog.simos.info/how-to-add-multi-line-raw-lxc- configuration-to-lxd/ But still, apparmor works just fine. There is some other setup going on in the autopkgtest infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2008393/+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 2008393] Re: armhf dep8 failure due to restrictions changing apparmor profile status
** Description changed: The armhf DEP8 testers in Ubuntu infrastructure have some restrictions and cannot change an apparmor profile. This is causing the tests to fail, because they try to make sure rsyslog is being tested in enforced mode: Enforcing the /etc/apparmor.d/usr.sbin.rsyslogd apparmor profile Setting /etc/apparmor.d/usr.sbin.rsyslogd to enforce mode. ERROR: /sbin/apparmor_parser: Unable to replace "rsyslogd". Permission denied; attempted to load a profile while confined? The package migrated to lunar even with this error because it never had DEP8 tests before, and the armhf baseline was born in this error state. + + + These are the LXD settings used for armhf containers: https://git.launchpad.net/autopkgtest-cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/tools/armhf-lxd.userdata#n76 + + I created an armhf container on a pi4 host (arm64) with these settings, + but couldn't reproduce the issue there. There is something else going on + in the autopkgtest infra regarding arhmf. + + FTR, I created the container like this: + + lxc launch ubuntu-daily:lunar pi4:l-armhf \ + -c raw.lxc="apparmor.profile=unconfined" \ + -c raw.lxc="seccomp.profile=" \ + -c security.nesting=true -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2008393 Title: armhf dep8 failure due to restrictions changing apparmor profile status Status in rsyslog package in Ubuntu: In Progress Bug description: The armhf DEP8 testers in Ubuntu infrastructure have some restrictions and cannot change an apparmor profile. This is causing the tests to fail, because they try to make sure rsyslog is being tested in enforced mode: Enforcing the /etc/apparmor.d/usr.sbin.rsyslogd apparmor profile Setting /etc/apparmor.d/usr.sbin.rsyslogd to enforce mode. ERROR: /sbin/apparmor_parser: Unable to replace "rsyslogd". Permission denied; attempted to load a profile while confined? The package migrated to lunar even with this error because it never had DEP8 tests before, and the armhf baseline was born in this error state. These are the LXD settings used for armhf containers: https://git.launchpad.net/autopkgtest- cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest- cloud/tools/armhf-lxd.userdata#n76 I created an armhf container on a pi4 host (arm64) with these settings, but couldn't reproduce the issue there. There is something else going on in the autopkgtest infra regarding arhmf. FTR, I created the container like this: lxc launch ubuntu-daily:lunar pi4:l-armhf \ -c raw.lxc="apparmor.profile=unconfined" \ -c raw.lxc="seccomp.profile=" \ -c security.nesting=true EDIT: hm, the above actually doesn't work. Only the last raw.lxc value is used. See https://blog.simos.info/how-to-add-multi-line-raw-lxc- configuration-to-lxd/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2008393/+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 2008797] [NEW] Mouse problems
Public bug reported: Basic problem is that the usb mouse connects at the start, but after sleep, suddenly stops. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 20:56:40 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GA107M [GeForce RTX 3050 Mobile] [103c:88ec] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Cezanne [103c:88ec] InstallationDate: Installed on 2023-02-28 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: HP Victus by HP Laptop 16-e0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=42da8321-31cc-4d70-aeb1-d0e0f86cc2f9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2021 dmi.bios.release: 15.4 dmi.bios.vendor: AMI dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88EC dmi.board.vendor: HP dmi.board.version: 80.22 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.22 dmi.modalias: dmi:bvnAMI:bvrF.04:bd06/17/2021:br15.4:efr80.22:svnHP:pnVictusbyHPLaptop16-e0xxx:pvr:rvnHP:rn88EC:rvr80.22:cvnHP:ct10:cvrChassisVersion:sku494P3PA#ACJ: dmi.product.family: 103C_5335M7 HP VICTUS dmi.product.name: Victus by HP Laptop 16-e0xxx dmi.product.sku: 494P3PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 kinetic 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/2008797 Title: Mouse problems Status in xorg package in Ubuntu: New Bug description: Basic problem is that the usb mouse connects at the start, but after sleep, suddenly stops. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error:
[Touch-packages] [Bug 2008763] Re: mkinitramfs reproducible fonts uuid
** Project changed: ubuntu-cdimage => initramfs-tools (Ubuntu) ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2008763 Title: mkinitramfs reproducible fonts uuid Status in initramfs-tools package in Ubuntu: New Bug description: Dear all, I am trying to do some reproducible builds of the daily isos and noticed that in chroot with a daily xubuntu Jammy iso mkinitramfs fails to create a reproducible initrd by setting random uuid's and filenames in the initrd: main/usr/share/fonts/.uuid main/usr/share/fonts/truetype/.uuid main/usr/share/fonts/truetype/ubuntu/.uuid main/usr/local/share/fonts/.uuid main/var/cache/fontconfig/***random-file-names*** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2008763/+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 2008763] [NEW] mkinitramfs reproducible fonts uuid
You have been subscribed to a public bug: Dear all, I am trying to do some reproducible builds of the daily isos and noticed that in chroot with a daily xubuntu Jammy iso mkinitramfs fails to create a reproducible initrd by setting random uuid's and filenames in the initrd: main/usr/share/fonts/.uuid main/usr/share/fonts/truetype/.uuid main/usr/share/fonts/truetype/ubuntu/.uuid main/usr/local/share/fonts/.uuid main/var/cache/fontconfig/***random-file-names*** ** Affects: initramfs-tools (Ubuntu) Importance: Low Status: New -- mkinitramfs reproducible fonts uuid https://bugs.launchpad.net/bugs/2008763 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools 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 1980805] Autopkgtest regression report (llvm-toolchain-13/1:13.0.1-2ubuntu2~20.04.1)
All autopkgtests for the newly accepted llvm-toolchain-13 (1:13.0.1-2ubuntu2~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: cargo/0.62.0ubuntu0libgit2-0ubuntu0.20.04.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#llvm-toolchain-13 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1980805 Title: Backport packages for 20.04.5 HWE stack Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mesa-amber package in Ubuntu: Invalid Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-13 source package in Focal: Fix Committed Status in mesa source package in Focal: New Status in mesa-amber source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.5 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: pci-id updates, some minor api updates mesa: a new major release, but we'll pull the final stable release of 22.0.x series, so there shouldn't be any regressions left at that point mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI drivers that were removed from main mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1980805/+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 2008469] Re: ubuntu jammy debug mirror out of sync
** Package changed: pulseaudio (Ubuntu) => ddeb-retriever -- 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/2008469 Title: ubuntu jammy debug mirror out of sync Status in ddeb-retriever: Confirmed Bug description: Why dose the Ubuntu debug mirror is again out of sync how should it be used in a productive environment when every month the mirror is for one week broken. libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 2.7.4-1ubuntu3.1 is to be installed libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2 is to be installed libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 2.1.27+dfsg2-3ubuntu1.1 is to be installed libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 7:4.4.2-0ubuntu0.22.04.1 is to be installed libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 2:1.0.25-1ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ddeb-retriever/+bug/2008469/+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 2008469] Re: ubuntu jammy debug mirror out of sync
** Package changed: ubuntu-keyring (Ubuntu) => pulseaudio (Ubuntu) -- 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/2008469 Title: ubuntu jammy debug mirror out of sync Status in pulseaudio package in Ubuntu: Confirmed Bug description: Why dose the Ubuntu debug mirror is again out of sync how should it be used in a productive environment when every month the mirror is for one week broken. libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 2.7.4-1ubuntu3.1 is to be installed libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2 is to be installed libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 2.1.27+dfsg2-3ubuntu1.1 is to be installed libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 7:4.4.2-0ubuntu0.22.04.1 is to be installed libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 2:1.0.25-1ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2008469/+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 2005115] Re: ubuntu-bug fails when wslu is installed
Thank you for taking the time to report this bug and helping to make Ubuntu better. I tried to reproduce your failure, but was not successful: * Install Ubuntu Desktop 22.04 in a VM * apt install wslu # version 3.2.3-0ubuntu3 * ubuntu-bug linux Apport presented a window with a report. There was no error message on the terminal. There is probably some environmental difference. ``` bdrung@ubuntu-22-04:~$ /usr/bin/wslview grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory WSL Interopability is disabled. Please enable it before using WSL. grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory [error] WSL Interoperability is disabled. Please enable it before using WSL. [error] No input, aborting bdrung@ubuntu-22-04:~$ grep -r wslview /usr/share/apport/ bdrung@ubuntu-22-04:~$ ``` I assume that there is some Apport hook in /usr/share/apport that executes wslview. The question is which package could ship it (wslu 3.2.3-0ubuntu3 does not ship any apport hook). -- 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/2005115 Title: ubuntu-bug fails when wslu is installed Status in apport package in Ubuntu: New Bug description: ubuntu-bug fails with the following error ubuntu-bug linux grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory WSL Interopability is disabled. Please enable it before using WSL. grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory [error] WSL Interoperability is disabled. Please enable it before using WSL. /usr/bin/wslview: line 216: /mnt/c/Windows/System32/reg.exe: No such file or directory /usr/bin/wslview: line 149: /mnt/c/Windows/System32/chcp.com: No such file or directory /usr/bin/wslview: line 156: /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe: No such file or directory /usr/bin/wslview: line 149: /mnt/c/Windows/System32/chcp.com: No such file or directory sudo apt remove wslu solved the problem but it is listed in the dependence of some help translation package of gimp I am running ubuntu on hardware, no WSL involved lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy apport 2.20.11-0ubuntu82.3 apt-cache policy wslu 3.2.3-0ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.3 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 4 04:11:09 2023 InstallationDate: Installed on 2023-01-26 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash 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/2005115/+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 2005115] Re: ubuntu-bug fails when wslu is installed
** Description changed: ubuntu-bug fails with the following error ubuntu-bug linux grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory WSL Interopability is disabled. Please enable it before using WSL. grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory [error] WSL Interoperability is disabled. Please enable it before using WSL. /usr/bin/wslview: line 216: /mnt/c/Windows/System32/reg.exe: No such file or directory /usr/bin/wslview: line 149: /mnt/c/Windows/System32/chcp.com: No such file or directory /usr/bin/wslview: line 156: /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe: No such file or directory /usr/bin/wslview: line 149: /mnt/c/Windows/System32/chcp.com: No such file or directory - sudo apt remove wslu + sudo apt remove wslu solved the problem but it is listed in the dependence of some help translation package of gimp I am running ubuntu on hardware, no WSL involved lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy apport 2.20.11-0ubuntu82.3 - pt-cache policy wslu + apt-cache policy wslu 3.2.3-0ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.3 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 4 04:11:09 2023 InstallationDate: Installed on 2023-01-26 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=ru_RU.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ru_RU.UTF-8 + SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2005115 Title: ubuntu-bug fails when wslu is installed Status in apport package in Ubuntu: New Bug description: ubuntu-bug fails with the following error ubuntu-bug linux grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory WSL Interopability is disabled. Please enable it before using WSL. grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory [error] WSL Interoperability is disabled. Please enable it before using WSL. /usr/bin/wslview: line 216: /mnt/c/Windows/System32/reg.exe: No such file or directory /usr/bin/wslview: line 149: /mnt/c/Windows/System32/chcp.com: No such file or directory /usr/bin/wslview: line 156: /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe: No such file or directory /usr/bin/wslview: line 149: /mnt/c/Windows/System32/chcp.com: No such file or directory sudo apt remove wslu solved the problem but it is listed in the dependence of some help translation package of gimp I am running ubuntu on hardware, no WSL involved lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy apport 2.20.11-0ubuntu82.3 apt-cache policy wslu 3.2.3-0ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.3 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 4 04:11:09 2023 InstallationDate: Installed on 2023-01-26 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash 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/2005115/+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 2008773] [NEW] CIFS mount in fstab ignores noauto if share name same as mount point
Public bug reported: If a cifs mount is defined in fstab, it will be automatically mounted even if noauto is specified in the options if the share name and the mount directory are the same. For example, the following line will automount despite it having the noauto flag as the first option: //172.18.0.50/mythtv /mythtv cifs noauto,credentials=/home/mythfrontend/.smbcredentials,iocharset=utf8,vers=3.0,gid=1000 0 2 However if you change the mount point to a different name, it will not be auto mounted: //172.18.0.50/mythtv /mithtv cifs noauto,credentials=/home/mythfrontend/.smbcredentials,iocharset=utf8,vers=3.0,gid=1000 0 2 Finally, if noauto is removed, it'll automount as expected: //172.18.0.50/mythtv /mithtv cifs credentials=/home/mythfrontend/.smbcredentials,iocharset=utf8,vers=3.0,gid=1000 0 2 Observed using ubuntu 22.04.2 LTS ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Tags: cifs fstab noauto -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/2008773 Title: CIFS mount in fstab ignores noauto if share name same as mount point Status in eglibc package in Ubuntu: New Bug description: If a cifs mount is defined in fstab, it will be automatically mounted even if noauto is specified in the options if the share name and the mount directory are the same. For example, the following line will automount despite it having the noauto flag as the first option: //172.18.0.50/mythtv /mythtv cifs noauto,credentials=/home/mythfrontend/.smbcredentials,iocharset=utf8,vers=3.0,gid=1000 0 2 However if you change the mount point to a different name, it will not be auto mounted: //172.18.0.50/mythtv /mithtv cifs noauto,credentials=/home/mythfrontend/.smbcredentials,iocharset=utf8,vers=3.0,gid=1000 0 2 Finally, if noauto is removed, it'll automount as expected: //172.18.0.50/mythtv /mithtv cifs credentials=/home/mythfrontend/.smbcredentials,iocharset=utf8,vers=3.0,gid=1000 0 2 Observed using ubuntu 22.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/2008773/+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 2008773] Re: CIFS mount in fstab ignores noauto if share name same as mount point
(assumes that /mythtv and /mithtv both exist, same permissions, yadda yadda yadda) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/2008773 Title: CIFS mount in fstab ignores noauto if share name same as mount point Status in eglibc package in Ubuntu: New Bug description: If a cifs mount is defined in fstab, it will be automatically mounted even if noauto is specified in the options if the share name and the mount directory are the same. For example, the following line will automount despite it having the noauto flag as the first option: //172.18.0.50/mythtv /mythtv cifs noauto,credentials=/home/mythfrontend/.smbcredentials,iocharset=utf8,vers=3.0,gid=1000 0 2 However if you change the mount point to a different name, it will not be auto mounted: //172.18.0.50/mythtv /mithtv cifs noauto,credentials=/home/mythfrontend/.smbcredentials,iocharset=utf8,vers=3.0,gid=1000 0 2 Finally, if noauto is removed, it'll automount as expected: //172.18.0.50/mythtv /mithtv cifs credentials=/home/mythfrontend/.smbcredentials,iocharset=utf8,vers=3.0,gid=1000 0 2 Observed using ubuntu 22.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/2008773/+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 2008465] Re: apt repository broken when having only jammy and jammy-security apt-repos enabled
Following the recomendation to assign to a package because no reaction, but I assume this is a general relase process bug, though. ** Package changed: ubuntu => openldap (Ubuntu) ** Description changed: Having installed Ubuntu 22 server from server-live-cd https://releases.ubuntu.com/22.04/ubuntu-22.04.1-live-server-amd64.iso (md5sum e8d2a77c51b599c10651608a5d8c286f) without network connection to internet (so no connection to ubuntu apt repositories). After offline installation completed, we remove the "jammy-updates" from the /etc/apt/sources.list so it looks like so: # cat /etc/apt/sources.list deb http://de.archive.ubuntu.com/ubuntu jammy main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu jammy-security main restricted universe multiverse + + Now we give the host network access and do "apt update" to refresh the + apt repository. We assume that the installed package libldap-2.5-0 version 2.5.12+dfsg-0ubuntu0.22.04.1 was installed from the ubuntu installer cd which is a version from jammy-updates. Now we are unable to install package "ldap-utils" because that depends on package libldap-2.5-0 version 2.5.11+dfsg-1~exp1ubuntu3.1 (which is older than the offline installed version 2.5.12+dfsg-0ubuntu0.22.04.1) # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy # apt-cache policy libldap-2.5-0 libldap-2.5-0: Installed: 2.5.12+dfsg-0ubuntu0.22.04.1 Candidate: 2.5.12+dfsg-0ubuntu0.22.04.1 Version table: *** 2.5.12+dfsg-0ubuntu0.22.04.1 100 100 /var/lib/dpkg/status 2.5.11+dfsg-1~exp1ubuntu3.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 2.5.11+dfsg-1~exp1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # apt install --simulate ldap-utils Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ldap-utils : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3.1) but 2.5.12+dfsg-0ubuntu0.22.04.1 is to be installed E: Unable to correct problems, you have held broken packages. -- The problem is solved when adding line deb http://de.archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse to /etc/apt/sources.list But we want _only_ security updates, to keep the updates minimal. Other workaround is "apt remove libldap-2.5-0", then when installing ldap-utils that fetches the older libldap-2.5-0 version 2.5.11+dfsg-1~exp1ubuntu3.1 and repo is consistent. Questions: - Can you confirm that the package version from the server-live-cd see above is the version from the jammy-updates repository? - Do you agree that when the above question is answered yes, having jammy-updates apt-repository is mandatory? - if jammy-updates repo should be mandatory should this be documented? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2008465 Title: apt repository broken when having only jammy and jammy-security apt- repos enabled Status in openldap package in Ubuntu: New Bug description: Having installed Ubuntu 22 server from server-live-cd https://releases.ubuntu.com/22.04/ubuntu-22.04.1-live-server-amd64.iso (md5sum e8d2a77c51b599c10651608a5d8c286f) without network connection to internet (so no connection to ubuntu apt repositories). After offline installation completed, we remove the "jammy-updates" from the /etc/apt/sources.list so it looks like so: # cat /etc/apt/sources.list deb http://de.archive.ubuntu.com/ubuntu jammy main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu jammy-security main restricted universe multiverse Now we give the host network access and do "apt update" to refresh the apt repository. We assume that the installed package libldap-2.5-0 version 2.5.12+dfsg-0ubuntu0.22.04.1 was installed from the ubuntu installer cd which is a version from jammy-updates. Now we are unable to install package "ldap-utils" because that depends on package libldap-2.5-0 version 2.5.11+dfsg-1~exp1ubuntu3.1 (which is older than the offline installed version 2.5.12+dfsg-0ubuntu0.22.04.1) # lsb_release -a No LSB modules are available.
[Touch-packages] [Bug 2008465] [NEW] apt repository broken when having only jammy and jammy-security apt-repos enabled
You have been subscribed to a public bug: Having installed Ubuntu 22 server from server-live-cd https://releases.ubuntu.com/22.04/ubuntu-22.04.1-live-server-amd64.iso (md5sum e8d2a77c51b599c10651608a5d8c286f) without network connection to internet (so no connection to ubuntu apt repositories). After offline installation completed, we remove the "jammy-updates" from the /etc/apt/sources.list so it looks like so: # cat /etc/apt/sources.list deb http://de.archive.ubuntu.com/ubuntu jammy main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu jammy-security main restricted universe multiverse We assume that the installed package libldap-2.5-0 version 2.5.12+dfsg-0ubuntu0.22.04.1 was installed from the ubuntu installer cd which is a version from jammy-updates. Now we are unable to install package "ldap-utils" because that depends on package libldap-2.5-0 version 2.5.11+dfsg-1~exp1ubuntu3.1 (which is older than the offline installed version 2.5.12+dfsg-0ubuntu0.22.04.1) # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy # apt-cache policy libldap-2.5-0 libldap-2.5-0: Installed: 2.5.12+dfsg-0ubuntu0.22.04.1 Candidate: 2.5.12+dfsg-0ubuntu0.22.04.1 Version table: *** 2.5.12+dfsg-0ubuntu0.22.04.1 100 100 /var/lib/dpkg/status 2.5.11+dfsg-1~exp1ubuntu3.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 2.5.11+dfsg-1~exp1ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # apt install --simulate ldap-utils Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ldap-utils : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3.1) but 2.5.12+dfsg-0ubuntu0.22.04.1 is to be installed E: Unable to correct problems, you have held broken packages. -- The problem is solved when adding line deb http://de.archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse to /etc/apt/sources.list But we want _only_ security updates, to keep the updates minimal. Other workaround is "apt remove libldap-2.5-0", then when installing ldap-utils that fetches the older libldap-2.5-0 version 2.5.11+dfsg-1~exp1ubuntu3.1 and repo is consistent. Questions: - Can you confirm that the package version from the server-live-cd see above is the version from the jammy-updates repository? - Do you agree that when the above question is answered yes, having jammy-updates apt-repository is mandatory? - if jammy-updates repo should be mandatory should this be documented? ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- apt repository broken when having only jammy and jammy-security apt-repos enabled https://bugs.launchpad.net/bugs/2008465 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap 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
