[Touch-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
Here is fccunlock package for the Dell platform. http://dell.archive.canonical.com/dists/jammy-somerville/public/binary- amd64/Packages Package: oem-fix-misc-intel-fccunlock Priority: optional Section: misc Installed-Size: 116 Maintainer: Commercial Engineering Architecture: amd64 Version: 5 Filename: pool/public/o/oem-fix-misc-intel-fccunlock/oem-fix-misc-intel-fccunlock_5_amd64.deb Size: 25304 SHA256: 7d582be18039443bfcccfd4c54ef3c95396d8429f5b63b476fde85697375ad1c SHA1: 58fc9cbee65caa02514b0f0c9064cd9187451cfd MD5sum: 91215c90ef0de45155b586e2698ee9ac Description: This is a fccunlock application used for unlocking 7560 R+ and FM350 modem. Description-md5: 994674e9a65d631a0b92e571f9867bae Modaliases: oem(pci:v14C3d4D75sv*sd*bc*sc*i*, pci:v8086d7560sv*sd*bc*sc*i*) -- 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/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1981190/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
How did you get the FCC Unlock to enable the modem? -- 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/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1981190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy
On Tue, Oct 31, 2023 at 01:13:11PM -, Adrien Nader wrote:
> ** Description changed:
>
> === SRU information ===
> [Meta]
> - This bug is part of a series of four bugs for a single SRU.
> + This bug is part of a series of three bugs for a single SRU.
> The "central" bug with the global information and debdiff is
> http://pad.lv/2033422
>
> [Impact]
> Decryption for Blowfish with OFB and CFB modes fails due to using a key
> shorter than expected by default.
Adrien, am I correct that this particular bug (1990216) is actually no longer
included at all in the LP:#2033422 SRU ?
Nathan
--
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/1990216
Title:
backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL
1.1 with blowfish in OFB or CFB modes" to Jammy
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Jammy:
In Progress
Status in openssl source package in Lunar:
Fix Released
Bug description:
=== SRU information ===
[Meta]
This bug is part of a series of three bugs for a single SRU.
The "central" bug with the global information and debdiff is
http://pad.lv/2033422
[Impact]
Decryption for Blowfish with OFB and CFB modes fails due to using a key
shorter than expected by default.
Encryption will also use a key shorter than expected.
Exchange of encrypted data from/to Jammy using BF OFB/CFB will therefore lead
to decryption issues.
[Test plan]
On Focal, run the following and copy the output to your clipboard
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do echo "Test with ${cipher}"
| openssl enc -${cipher} -k test -pbkdf2 -out "pouet.${cipher}"; done
tar c pouet.bf-* | xz | base64 -w 60
You can also run this on Lunar or Mantic if you add "-provider legacy
-provider default" to the "openssl enc" invocation.
On Jammy, run the following and paste your clipboard
base64 -d | xz -d | tar x
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do openssl enc -d -provider
legacy -provider default -${cipher} -k test -pbkdf2 -d -in "pouet.${cipher}";
done
Only "Test with bf-cbc" and "Test with bf-ecb" will be properly
decrypted: the other two will result in garbage on screen.
Here is the result of the enc + tar + xz + base64 on Focal (works with
Lunar/Mantic too but you need to added ):
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARBdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc5VcodF6fu0hEp801tvirgSFNMSAHk5HMN/w
hCgU1BIr/nK51g3A3Lkdv7QNbaUw2ux1AmO/MpCLKLffCB9ElFZH4tuOS5AR
m9CJMzi6LQOw9wytGKm2IK3Ph7WpU6JQ/3HJilffQwHbFLnukiWGpLNO5v0O
D/4AJikrU9iemfChT0jXDbIRZ8a8VpVhJqu0u6eYOheVTqmSRiHHpIC/p1VA
ecFb0mACF/TQhjxcMUWGSGO/mtof+VaLiyg0KB87GKlChfwXTEvgbNuP9hmu
GL64VhX568Oy9EakSxlcXiIRk14kJKv0MdHQqY1R22wAACzqSr/nzpwqAAGs
AoBQAACjzq5WscRn+wIABFla
Here is the same but from Jammy if you want to test encryption on
Jammy and decryption on Lunar/Mantic:
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARFdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc1zK4HR2g3CiLJet+R++nZy/gph6RscQ6hI3
HySjdDOFRfjIVttiNK3DvRsZb37r8SXkj/JCYWicZGjWPZxVE3OAZhEed5qe
jrFv871QAbm4jVGD4oIc4cOb5V/xDN7KWgwEzpWQy6+tcfPm3KLPQvULx56N
2qQf60hP//p5EXS3RpCitUsrGUoYzTynjOUIRy2yCmgZDh62RmchUshyWePa
k0nEYlDbl5/dSHXbWEWESqW+QDj136MZRwQRY+QC4MvLXg2Bo8H+Dl/xvNDF
/5J4layZdFlh76lWOtFRVoIbX6JtpAP34g4zx1422GSNAABRzyqPdCqX
1AABrQKAUAAABh3ynbHEZ/sCAARZWg==
The contents are expected to be different due to the use of
randomness. Don't try to compare the base64 outputs: I'm only using
them to ease testing across containers.
[Where problems could occur]
This patch makes openssl match the documented default (see "man openssl-enc"
and search for "Blowfish" for instance) and fixes decryption from an up-to-date
Jammy to pretty much everything else, but it also create an issue for data
encrypted on Jammy without this patch and Jammy with this patch.
There are two possible cases: encrypted data being streamed across
this boundary or data at rest being transferred or read later.
Streaming is probably not an issue in practice because it's rather the
current situation that has been an issue and it's easy to remedy by
updating everything (which is relatively few machines since that's
only Jammy and not any other OS or distribution).
Data at rest is more annoying since updating Jammy will make it
impossible to read the data again without updates to other pieces of
software. That sounds like a really bad thing and it kind of is but at
the same, the benefits are much larger than the issues. Indeed, there
is already an incompatibility at the moment between Jammy and
everything else and the more time passes by, the more such problematic
files can be
[Touch-packages] [Bug 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy
On Thu, Oct 26, 2023 at 09:54:51AM -, Simon Chopin wrote:
> I'm very much against uploading this fix as an SRU. While it is a shame
> that we have interop problems with the rest of the world, fixing this in
> Jammy right now means we *will* break production for anyone that stores
> Blowfish-encrypted data.
Simon, just to clarify: the original issue I ran into was not
"interop problems with the rest of the world" exactly, but rather
interop between Tinc nodes running on different versions of
Ubuntu (i.e. a Tinc node running Jammy can't connect to existing
nodes running on older releases). (Though obviously interop will
fail with the rest of the world, too.)
I am not particularly involved in the OpenSSL community, but have
been trying to keep an eye on this specific issue since I ran
into it, and as far as I have noticed/found on the internet there
haven't been any mentions about this OpenSSL bug other than in
the two LP bugs related to this Tinc issue and the related
Github-for-tinc bug ( https://github.com/gsliepen/tinc/issues/414
).
So while I certainly agree in general with need for "apt upgrade"
to be a very safe operation, in this particular case I am not
sure how to weigh the chance that someone might possibly have a
custom app using Blowfish to encrypt local data (while at the
same time not already having in place mechanisms to deal with
this compatibility issue for pre-and-post Jammy Ubuntu) with the
publicly-raised-by-at-least-a-few-people problem of Tinc
incompatibility between nodes that this causes
Nathan
** Bug watch added: github.com/gsliepen/tinc/issues #414
https://github.com/gsliepen/tinc/issues/414
--
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/1990216
Title:
backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL
1.1 with blowfish in OFB or CFB modes" to Jammy
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Jammy:
In Progress
Status in openssl source package in Lunar:
Fix Released
Bug description:
=== SRU information ===
[Meta]
This bug is part of a series of three bugs for a single SRU.
The "central" bug with the global information and debdiff is
http://pad.lv/2033422
[Impact]
Decryption for Blowfish with OFB and CFB modes fails due to using a key
shorter than expected by default.
Encryption will also use a key shorter than expected.
Exchange of encrypted data from/to Jammy using BF OFB/CFB will therefore lead
to decryption issues.
[Test plan]
On Focal, run the following and copy the output to your clipboard
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do echo "Test with ${cipher}"
| openssl enc -${cipher} -k test -pbkdf2 -out "pouet.${cipher}"; done
tar c pouet.bf-* | xz | base64 -w 60
You can also run this on Lunar or Mantic if you add "-provider legacy
-provider default" to the "openssl enc" invocation.
On Jammy, run the following and paste your clipboard
base64 -d | xz -d | tar x
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do openssl enc -d -provider
legacy -provider default -${cipher} -k test -pbkdf2 -d -in "pouet.${cipher}";
done
Only "Test with bf-cbc" and "Test with bf-ecb" will be properly
decrypted: the other two will result in garbage on screen.
Here is the result of the enc + tar + xz + base64 on Focal (works with
Lunar/Mantic too but you need to added ):
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARBdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc5VcodF6fu0hEp801tvirgSFNMSAHk5HMN/w
hCgU1BIr/nK51g3A3Lkdv7QNbaUw2ux1AmO/MpCLKLffCB9ElFZH4tuOS5AR
m9CJMzi6LQOw9wytGKm2IK3Ph7WpU6JQ/3HJilffQwHbFLnukiWGpLNO5v0O
D/4AJikrU9iemfChT0jXDbIRZ8a8VpVhJqu0u6eYOheVTqmSRiHHpIC/p1VA
ecFb0mACF/TQhjxcMUWGSGO/mtof+VaLiyg0KB87GKlChfwXTEvgbNuP9hmu
GL64VhX568Oy9EakSxlcXiIRk14kJKv0MdHQqY1R22wAACzqSr/nzpwqAAGs
AoBQAACjzq5WscRn+wIABFla
Here is the same but from Jammy if you want to test encryption on
Jammy and decryption on Lunar/Mantic:
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARFdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc1zK4HR2g3CiLJet+R++nZy/gph6RscQ6hI3
HySjdDOFRfjIVttiNK3DvRsZb37r8SXkj/JCYWicZGjWPZxVE3OAZhEed5qe
jrFv871QAbm4jVGD4oIc4cOb5V/xDN7KWgwEzpWQy6+tcfPm3KLPQvULx56N
2qQf60hP//p5EXS3RpCitUsrGUoYzTynjOUIRy2yCmgZDh62RmchUshyWePa
k0nEYlDbl5/dSHXbWEWESqW+QDj136MZRwQRY+QC4MvLXg2Bo8H+Dl/xvNDF
/5J4layZdFlh76lWOtFRVoIbX6JtpAP34g4zx1422GSNAABRzyqPdCqX
1AABrQKAUAAABh3ynbHEZ/sCAARZWg==
The contents are expected to be different due to the use of
randomness. Don't try to compare the base64 outputs: I'm only using
them to ease testing across containers.
[Where problems could occur]
This patch makes openssl match the documented default (see "man openssl-enc"
and search
[Touch-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
This bug is awaiting verification that the linux-nvidia-6.5/6.5.0-1004.4
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-nvidia-6.5' to 'verification-done-
jammy-linux-nvidia-6.5'. If the problem still exists, change the tag
'verification-needed-jammy-linux-nvidia-6.5' to 'verification-failed-
jammy-linux-nvidia-6.5'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-nvidia-6.5-v2
verification-needed-jammy-linux-nvidia-6.5
--
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
Fix Released
Status in MAAS:
Fix Released
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in systemd source package in Lunar:
Invalid
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature
This bug is awaiting verification that the linux-nvidia-6.5/6.5.0-1004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to 'verification-done- jammy-linux-nvidia-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to 'verification-failed- jammy-linux-nvidia-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-6.5-v2 verification-needed-jammy-linux-nvidia-6.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: Confirmed Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2042367] [NEW] eglinfo device platform eglInitialize failed
Public bug reported: On an Intel NUC13RNGi9 system with 13900K processor with integrated Intel UHD 770 Graphics, the command "eglinfo" fails to initialize the Device platform: $ eglinfo ... Device platform: eglinfo: eglInitialize failed The other platforms (X11, Wayland, GBM) initialize. The reason I am reporting is I'm trying to fix an issue in my system where: EGLDisplay display = eglGetDisplay(EGL_DEFAULT_DISPLAY) is returning EGL_NO_DISPLAY on my system, and I think it's due to the Device platform failing to initialize. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 09:42:40 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:a780] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:3033] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Intel(R) Client Systems NUC13RNGi9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2023 dmi.bios.release: 5.27 dmi.bios.vendor: Intel Corp. dmi.bios.version: SBRPL579.0056.2023.0204.0233 dmi.board.name: NUC13SBBi9 dmi.board.vendor: Intel Corporation dmi.board.version: M58736-304 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 44.0 dmi.modalias: dmi:bvnIntelCorp.:bvrSBRPL579.0056.2023.0204.0233:bd02/04/2023:br5.27:efr44.0:svnIntel(R)ClientSystems:pnNUC13RNGi9:pvrM89920-304:rvnIntelCorporation:rnNUC13SBBi9:rvrM58736-304:cvnIntelCorporation:ct35:cvr2.0:skuRNUC13RNGi9: dmi.product.family: RN dmi.product.name: NUC13RNGi9 dmi.product.sku: RNUC13RNGi9 dmi.product.version: M89920-304 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 jammy ubuntu wayland-session -- 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/2042367 Title: eglinfo device platform eglInitialize failed Status in xorg package in Ubuntu: New Bug description: On an Intel NUC13RNGi9 system with 13900K processor with integrated Intel UHD 770 Graphics, the command "eglinfo" fails to initialize the Device platform: $ eglinfo ... Device platform: eglinfo: eglInitialize failed The other platforms (X11, Wayland, GBM) initialize. The reason I am reporting is I'm trying to fix an issue in my system where: EGLDisplay display = eglGetDisplay(EGL_DEFAULT_DISPLAY) is returning EGL_NO_DISPLAY on my system, and I think it's due to the Device platform failing to initialize. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 09:42:40 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:a780] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:3033] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Intel(R) Client Systems NUC13RNGi9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2023
[Touch-packages] [Bug 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353
This bug was fixed in the package systemd - 253.5-1ubuntu7 --- systemd (253.5-1ubuntu7) noble; urgency=medium * Revert "debian/rules: set MulticastDNS=resolve by default" (LP: #2038894) File: debian/rules https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3d753238699f54e8c2892d8107136d49f09e44b6 * debian/gbp.conf: update for noble File: debian/gbp.conf https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a65decb3a73592af8b952b159cfb453e9c0babd5 -- Nick Rosbrook Thu, 26 Oct 2023 09:51:33 -0400 ** Changed in: systemd (Ubuntu Noble) Status: Fix Committed => Fix Released -- 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/2038894 Title: Ubuntu 23.10 cloud images unexpected UDP listening port 5353 Status in cloud-images: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Mantic: Fix Committed Status in systemd source package in Noble: Fix Released Bug description: [Impact] In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP listening port 5353. By default and by policy, aside from port 22 there should be no other open ports on Ubuntu cloud images. Listening port 5353 is a regression. [Test Plan] Check that port 5353 is not open, and in particular that systemd- resolved is not listening on 5353. This is what it looks like when systemd-resolved *is* listening on 5353: ``` $ ss --listening --no-header --tcp --udp --numeric udp UNCONN 00 127.0.0.54:53 0.0.0.0:* udp UNCONN 00 127.0.0.53%lo:53 0.0.0.0:* udp UNCONN 00 10.154.0.17%ens4:68 0.0.0.0:* udp UNCONN 00 127.0.0.1:323 0.0.0.0:* udp UNCONN 00 0.0.0.0:5353 0.0.0.0:* udp UNCONN 00 [::1]:323 [::]:* udp UNCONN 00 [::]:5353 [::]:* tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* tcp LISTEN 0 4096
[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
Is this fixed in noble now? No. Is this due to be fixed; I've not heard anything, but happy to be corrected if this is on a roadmap somewhere? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Thank you for reporting this and helping make Ubuntu better. Could you please boot into a Ubuntu kernel (not third party kernel) and execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2011385 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug. Please include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments. This information can be gathered for you automatically by using the following command only once: apport-collect -p alsa-base 2011385 ** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic
[Unsubscribing sponsors pending resolution of Robie's request] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic Status in lxc package in Ubuntu: Confirmed Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2041396] Re: gdb 12.1 generates SIGILL on armhf
Currently waiting for an SRU team member to process the update through
the upload queue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Fix Released
Status in gdb package in Ubuntu:
New
Status in gdb source package in Jammy:
New
Bug description:
[ Impact ]
* GDB 12.1 introduced a regression where it will break program execution
when the program contains mixed ARM code and THUMB code.
* Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.
[ Test Plan ]
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands ...
```
b 3
r
c
```
(you can save the contents above to a file and run GDB using `gdb -x
script ./repro`)
... you will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
[ Where problems could occur ]
* GDB is a complex software. As the patch suggests, it may break other use
cases (like single-stepping) entirely.
* Since this is an ARM-only patch, it's unlikely to affect other CPU
architectures. However, it is possible that this fix may break ARM64 execution.
[ Other Info ]
* This bug has been fixed in GDB 13, but the fix was never backported to GDB
12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+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 1419391] Re: LANG=C environment breaks clock
** Bug watch added: Sourceware.org Bugzilla #21668 https://sourceware.org/bugzilla/show_bug.cgi?id=21668 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1419391 Title: LANG=C environment breaks clock Status in indicator-datetime package in Ubuntu: New Bug description: When the environment contains LANG=C (in .pam_environment, for example), the clock in gnome-panel disapears if it is either in 12-hour format, or it displays seconds. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-panel 1:3.8.0-1ubuntu12.2 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 8 14:06:58 2015 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-panel GsettingsChanges: InstallationDate: Installed on 2014-09-26 (134 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1419391/+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 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353
** Changed in: systemd (Ubuntu Noble) Status: New => Fix Committed -- 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/2038894 Title: Ubuntu 23.10 cloud images unexpected UDP listening port 5353 Status in cloud-images: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Mantic: Fix Committed Status in systemd source package in Noble: Fix Committed Bug description: [Impact] In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP listening port 5353. By default and by policy, aside from port 22 there should be no other open ports on Ubuntu cloud images. Listening port 5353 is a regression. [Test Plan] Check that port 5353 is not open, and in particular that systemd- resolved is not listening on 5353. This is what it looks like when systemd-resolved *is* listening on 5353: ``` $ ss --listening --no-header --tcp --udp --numeric udp UNCONN 00 127.0.0.54:53 0.0.0.0:* udp UNCONN 00 127.0.0.53%lo:53 0.0.0.0:* udp UNCONN 00 10.154.0.17%ens4:68 0.0.0.0:* udp UNCONN 00 127.0.0.1:323 0.0.0.0:* udp UNCONN 00 0.0.0.0:5353 0.0.0.0:* udp UNCONN 00 [::1]:323 [::]:* udp UNCONN 00 [::]:5353 [::]:* tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* tcp LISTEN 0 4096 *:22 *:* ``` ``` $ sudo lsof -i -n -P COMMANDPIDUSER FD TYPE
[Touch-packages] [Bug 2025339] Re: FDE image fails to run e2fsck
** Also affects: e2fsprogs (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031622 Importance: Unknown Status: Unknown ** Changed in: e2fsprogs (Ubuntu Lunar) Status: Confirmed => In Progress ** Changed in: e2fsprogs (Ubuntu Lunar) Assignee: (unassigned) => Paul Mars (upils) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Jammy: Confirmed Status in e2fsprogs source package in Lunar: In Progress Status in e2fsprogs package in Debian: Unknown Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+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 2025339] Re: FDE image fails to run e2fsck
** Merge proposal linked: https://code.launchpad.net/~upils/ubuntu/+source/e2fsprogs/+git/e2fsprogs/+merge/454796 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Jammy: Confirmed Status in e2fsprogs source package in Lunar: Confirmed Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+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 2041845] Re: Notifies about some ancient downgrades on every boot
That's it. pkcon offline-status Status: Success Updated google-chrome-stable-113.0.5672.126-1.amd64 Updated mdadm-4.2-0ubuntu2.amd64 Updated google-chrome-stable-113.0.5672.126-1.amd64 Updated mdadm-4.2-0ubuntu2.amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2041845 Title: Notifies about some ancient downgrades on every boot Status in gnome-software package in Ubuntu: Incomplete Status in packagekit package in Ubuntu: Incomplete Bug description: Preparing for upgrade from 22.04 to 23.04 some packages were downgraded (or just marked as such?) and now update-notifier reminds me about them on every boot, this makes me likely to miss important upgrades available, because I tend now to dismiss it without looking. google-chrome-stable was upgraded many times since then, but I still get notifications about that 113.0... version. Btw, it says about downgrade from the current version! It's update-notifier/lunar,now 3.192.64 amd64 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: update-notifier 3.192.64 ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 14:47:30 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2016-11-26 (2529 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: update-notifier UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago) upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 new release available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2041845/+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 2041845] Re: Notifies about some ancient downgrades on every boot
> you may want to see if pkcon get-updates shows the same issue. pkcon get-updates Getting updates [=] Loading cache [=] Finished[=] There are no updates available at this time. However notification says about installed updates, not available. For some reason it just doesn't forget about it over time. I also have `unattended-upgrades` installed, for which those notifications would make sense - if it was something new. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2041845 Title: Notifies about some ancient downgrades on every boot Status in gnome-software package in Ubuntu: Incomplete Status in packagekit package in Ubuntu: Incomplete Bug description: Preparing for upgrade from 22.04 to 23.04 some packages were downgraded (or just marked as such?) and now update-notifier reminds me about them on every boot, this makes me likely to miss important upgrades available, because I tend now to dismiss it without looking. google-chrome-stable was upgraded many times since then, but I still get notifications about that 113.0... version. Btw, it says about downgrade from the current version! It's update-notifier/lunar,now 3.192.64 amd64 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: update-notifier 3.192.64 ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 14:47:30 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2016-11-26 (2529 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: update-notifier UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago) upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 new release available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2041845/+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 1951586] Re: Need option to specify wifi regulatory domain
Is this fixed in Noble? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 2023322] Re: GTK internal browser does not render with Nvidia drivers
browser works now but sign in does not work. I enter my google credentials and it just spins forever but never signs in to the account. Luckily I bypassed this a long time ago just creating a direct app link to google calendar so really don't need it but it is too bad Ubuntu can't seem to get this fixed On Thu, Oct 26, 2023 at 1:00 AM Daniel van Vugt <2023...@bugs.launchpad.net> wrote: > Verified working in webkit2gtk 2.42.1-2. > > Tested Nvidia 535 with both X11 and Wayland, in both Online Accounts and > Ubuntu Desktop Guide. > > > ** Changed in: webkit2gtk (Ubuntu) >Status: In Progress => Fix Released > > ** Changed in: yelp (Ubuntu) >Status: Triaged => Invalid > > ** Changed in: gnome-control-center (Ubuntu) >Status: Triaged => Invalid > > ** Changed in: gnome-online-accounts (Ubuntu) >Status: Triaged => Invalid > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2027737). > https://bugs.launchpad.net/bugs/2023322 > > Title: > GTK internal browser does not render with Nvidia drivers > > Status in Webkit: > Confirmed > Status in gnome-control-center package in Ubuntu: > Invalid > Status in gnome-online-accounts package in Ubuntu: > Invalid > Status in webkit2gtk package in Ubuntu: > Fix Released > Status in yelp package in Ubuntu: > Invalid > Status in webkit2gtk package in Debian: > Fix Released > > Bug description: > When I go into Settings > Online Accounts > Google, I get to the > prompt for email address, once in a while it stops accepting input > there. But often I can get to the password screen. Once I do, I can't > type anything or paste anything. > > This is a fresh install of Ubuntu 23.04 and I have installed all > updates. > > Nothing in /var/crash > > Jun 08 11:15:59 CCW-HAL systemd[3523]: > vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU > time. > Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion > 'closure->ref_count > 0' failed > Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion > 'closure->ref_count > 0' failed > Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion > 'closure->ref_count > 0' failed > Jun 08 11:16:29 CCW-HAL systemd[3523]: Started > app-gnome-org.gnome.Terminal-10924.scope - Application launched by > gnome-shell. > Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] > Activating via systemd: service name='org.gnome.Terminal' > unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 > pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") > Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting > gnome-terminal-server.service - GNOME Terminal Server... > Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] > Successfully activated service 'org.gnome.Terminal' > Jun 08 11:16:29 CCW-HAL systemd[3523]: Started > gnome-terminal-server.service - GNOME Terminal Server. > Jun 08 11:16:29 CCW-HAL systemd[3523]: Started > vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process > 10955 launched by gnome-terminal-server process 10931. > Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: > Child process exited with code 1 > Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: > GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock > if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found > default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is > not thread-safe and should not be used after threads are createdGLib-GIO: > _g_io_module_get_default: Found default implementation dconf > (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all > providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - > windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - > imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos > providerGLib-GIO: _g_io_module_get_default: Found default implementation > gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: > Dialog was dismissed > Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not > map pid: Could not determine pid namespace: Could not find instance-id in > process's /.flatpak-info > Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session > opened for user root(uid=0) by (uid=0) > Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts > --report /etc/cron.hourly) > Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session > closed for user root > Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at > 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU > 2 (core 2, socket 0) > Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at > 0x55bd22ad9ab2. > Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window
[Touch-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
** Also affects: mesa (Ubuntu Noble) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: Fix Released ** Also affects: ubuntu-settings (Ubuntu Noble) Importance: Undecided Assignee: Dave Jones (waveform) Status: Fix Released ** Also affects: pipewire (Ubuntu Noble) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: Invalid ** Also affects: linux-meta-raspi (Ubuntu Noble) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: Fix Released ** Also affects: linux-raspi (Ubuntu Noble) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: Fix Released ** Also affects: libcamera (Ubuntu Noble) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: Triaged ** Also affects: rpi-eeprom (Ubuntu Noble) Importance: Undecided Assignee: Dave Jones (waveform) Status: Fix Released -- 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/2037642 Title: [FFe] Raspberry Pi 5 support Status in Release Notes for Ubuntu: Fix Released Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in libcamera source package in Noble: Triaged Status in linux-meta-raspi source package in Noble: Fix Released Status in linux-raspi source package in Noble: Fix Released Status in mesa source package in Noble: Fix Released Status in pipewire source package in Noble: Invalid Status in rpi-eeprom source package in Noble: Fix Released Status in ubuntu-settings source package in Noble: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+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 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353
** Also affects: systemd (Ubuntu Noble) Importance: High Assignee: Nick Rosbrook (enr0n) Status: New -- 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/2038894 Title: Ubuntu 23.10 cloud images unexpected UDP listening port 5353 Status in cloud-images: New Status in systemd package in Ubuntu: New Status in systemd source package in Mantic: Fix Committed Status in systemd source package in Noble: New Bug description: [Impact] In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP listening port 5353. By default and by policy, aside from port 22 there should be no other open ports on Ubuntu cloud images. Listening port 5353 is a regression. [Test Plan] Check that port 5353 is not open, and in particular that systemd- resolved is not listening on 5353. This is what it looks like when systemd-resolved *is* listening on 5353: ``` $ ss --listening --no-header --tcp --udp --numeric udp UNCONN 00 127.0.0.54:53 0.0.0.0:* udp UNCONN 00 127.0.0.53%lo:53 0.0.0.0:* udp UNCONN 00 10.154.0.17%ens4:68 0.0.0.0:* udp UNCONN 00 127.0.0.1:323 0.0.0.0:* udp UNCONN 00 0.0.0.0:5353 0.0.0.0:* udp UNCONN 00 [::1]:323 [::]:* udp UNCONN 00 [::]:5353 [::]:* tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* tcp LISTEN 0 4096 *:22 *:* ``` ``` $ sudo lsof -i -n -P COMMANDPID
[Touch-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
In Krita there could be seen(and set) various colour profiles ICC standards for images(could be seen on Create New Image). If some vague generated colour profile for unsupported monitors or hardware vendors uninterested for such GNOME thing(may be different in other DE?) is lack of corporate funding interest on this area, but at least CMYK colour profile standard means that such image should looked same on monitor as printed, but todays advanced monitors support sometimes 10bit colours or 8+2computed and also not only advanced SRGB ~100% coverage of colours, but it is also towards 100% DCI-P3 coverage of possible colours and such thing should colour profile support and if "generated" don't, problem occurs(or shit images). Now is also OKLCH colour standard instead of RGB in CSS web. More on advancement on this area in articles: https://evilmartians.com/chronicles/oklch-a-color-picker-made-to-help-think-perceptively and https://evilmartians.com/chronicles/oklch-in-css-why-quit-rgb-hsl Adobe software is maybe long standard in this area(maybe with web apps), but industry is much wider... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in Eye of GNOME: New Status in GNOME Shell: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: 1. Settings > Colour > turn off the toggle switch for your monitor. 2. Restart any affected apps. Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
** Changed in: linux Status: Unknown => New -- 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/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in Linux: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in mesa source package in Jammy: New Status in linux source package in Lunar: New Status in linux-oem-6.5 source package in Lunar: Invalid Status in mesa source package in Lunar: New Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in mesa source package in Mantic: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Status in mesa source package in Noble: New Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/linux/+bug/2042054/+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 2042042] Re: Browser does not remember workspace after leaving full screen video
After more testing it seems that regardless on which workspace the
browser was in before going into full screen that it will end up on the
opposite workspace after getting unmaximized.
--
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/2042042
Title:
Browser does not remember workspace after leaving full screen video
Status in xorg package in Ubuntu:
New
Bug description:
Using 2x screens in portrait mode, if I display my browser on the
right-side panel of workspace 1, watch a video and full screen it,
after I off the video the browser will now be displayed on the
left-side panel of workspace 1.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Mon Oct 30 23:06:47 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X /
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (199 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (17 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.cron.daily.apport: [deleted]
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/xorg/+bug/2042042/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
It's unclear if this is a BIOS, mesa or kernel bug at this time, but it's certainly not an Xorg bug as it was reproduced in Wayland. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2954 https://gitlab.freedesktop.org/drm/amd/-/issues/2954 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/2954 Importance: Unknown Status: Unknown ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Also affects: mesa (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in Linux: Unknown Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in mesa source package in Jammy: New Status in linux source package in Lunar: New Status in linux-oem-6.5 source package in Lunar: Invalid Status in mesa source package in Lunar: New Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in mesa source package in Mantic: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Status in mesa source package in Noble: New Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name:
[Touch-packages] [Bug 2017770] Re: "Enter code on ubuntu.com/pro/attach" is not clickable URL like everything else
** Merge proposal linked: https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/454886 -- 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/2017770 Title: "Enter code on ubuntu.com/pro/attach" is not clickable URL like everything else Status in software-properties package in Ubuntu: Confirmed Bug description: Enter code on ubuntu.com/pro/attach is not a clickable url. however ubuntu.com/pro and "register new account" are. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2017770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1962549] Re: openssl cms -decrypt doesn't work properly when using an engine
> I don't know why LP expired this bug since you commented after I changed > the its status... AFAIK, LP will not switch back the status to anything after a comment has been left. That makes sense, as it wouldn't know what the new status is supposed to be. -- 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/1962549 Title: openssl cms -decrypt doesn't work properly when using an engine Status in openssl package in Ubuntu: New Bug description: I'm using: bsci@ip-10-132-42-225:~/test$ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 bsci@ip-10-132-42-225:~/test$ apt-cache policy openssl openssl: Installed: 1.1.1f-1ubuntu2.10 Candidate: 1.1.1f-1ubuntu2.10 Version table: *** 1.1.1f-1ubuntu2.10 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.1f-1ubuntu2.8 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1.1.1f-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages I have a private EC key held in a TPM 2.0 platform hierarchy. I'm encrypting a message like this: openssl cms -encrypt -in message.txt -out message.cipher transport.pem Here, transport.pem is the cert. for the EC key held in the TPM. I'm attempting to decrypt like this: openssl cms -decrypt -in message.cipher -out /dev/stdout -inkey 0x8181 -keyform engine -engine tpm2tss -recip transport.pem Instead of seeing the original message text, I'm getting the following error: engine "tpm2tss" set. Error decrypting CMS using private key 139626757388096:error:1010107D:elliptic curve routines:ecdh_simple_compute_key:missing private key:../crypto/ec/ecdh_ossl.c:61: It seems that the code is expecting the actual private key instead of using the key held in the TPM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1962549/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
** Package changed: xorg (Ubuntu) => mesa (Ubuntu) -- 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/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in mesa package in Ubuntu: New Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/mesa/+bug/2042054/+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 2041845] Re: Notifies about some ancient downgrades on every boot
The messages in the screenshot seem to be from gnome-software which is a third party software in universe and not part of the Ubuntu user experience. It's not clear why it would show downgrades to packages no longer in the cache. gnome-software uses PackageKit so you may want to see if pkcon get-updates shows the same issue. ** Package changed: update-notifier (Ubuntu) => gnome-software (Ubuntu) ** Also affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Changed in: packagekit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2041845 Title: Notifies about some ancient downgrades on every boot Status in gnome-software package in Ubuntu: Incomplete Status in packagekit package in Ubuntu: Incomplete Bug description: Preparing for upgrade from 22.04 to 23.04 some packages were downgraded (or just marked as such?) and now update-notifier reminds me about them on every boot, this makes me likely to miss important upgrades available, because I tend now to dismiss it without looking. google-chrome-stable was upgraded many times since then, but I still get notifications about that 113.0... version. Btw, it says about downgrade from the current version! It's update-notifier/lunar,now 3.192.64 amd64 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: update-notifier 3.192.64 ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 14:47:30 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2016-11-26 (2529 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: update-notifier UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago) upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 new release available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2041845/+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 1962549] Re: openssl cms -decrypt doesn't work properly when using an engine
I don't know why LP expired this bug since you commented after I changed the its status... Anyway, I'm going to mark it as New again. Unfortunately, I haven't had time to try to reproduce this again and I won't have time before at least two weeks due to some time off and Canonical events. It would be tremendously helpful if you manage to directly provide the comments for the steps. ** Changed in: openssl (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1962549 Title: openssl cms -decrypt doesn't work properly when using an engine Status in openssl package in Ubuntu: New Bug description: I'm using: bsci@ip-10-132-42-225:~/test$ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 bsci@ip-10-132-42-225:~/test$ apt-cache policy openssl openssl: Installed: 1.1.1f-1ubuntu2.10 Candidate: 1.1.1f-1ubuntu2.10 Version table: *** 1.1.1f-1ubuntu2.10 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.1f-1ubuntu2.8 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1.1.1f-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages I have a private EC key held in a TPM 2.0 platform hierarchy. I'm encrypting a message like this: openssl cms -encrypt -in message.txt -out message.cipher transport.pem Here, transport.pem is the cert. for the EC key held in the TPM. I'm attempting to decrypt like this: openssl cms -decrypt -in message.cipher -out /dev/stdout -inkey 0x8181 -keyform engine -engine tpm2tss -recip transport.pem Instead of seeing the original message text, I'm getting the following error: engine "tpm2tss" set. Error decrypting CMS using private key 139626757388096:error:1010107D:elliptic curve routines:ecdh_simple_compute_key:missing private key:../crypto/ec/ecdh_ossl.c:61: It seems that the code is expecting the actual private key instead of using the key held in the TPM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1962549/+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 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy
** Description changed:
=== SRU information ===
[Meta]
- This bug is part of a series of four bugs for a single SRU.
+ This bug is part of a series of three bugs for a single SRU.
The "central" bug with the global information and debdiff is
http://pad.lv/2033422
[Impact]
Decryption for Blowfish with OFB and CFB modes fails due to using a key
shorter than expected by default.
Encryption will also use a key shorter than expected.
Exchange of encrypted data from/to Jammy using BF OFB/CFB will therefore lead
to decryption issues.
[Test plan]
On Focal, run the following and copy the output to your clipboard
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do echo "Test with ${cipher}"
| openssl enc -${cipher} -k test -pbkdf2 -out "pouet.${cipher}"; done
tar c pouet.bf-* | xz | base64 -w 60
You can also run this on Lunar or Mantic if you add "-provider legacy
-provider default" to the "openssl enc" invocation.
On Jammy, run the following and paste your clipboard
base64 -d | xz -d | tar x
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do openssl enc -d -provider
legacy -provider default -${cipher} -k test -pbkdf2 -d -in "pouet.${cipher}";
done
Only "Test with bf-cbc" and "Test with bf-ecb" will be properly
decrypted: the other two will result in garbage on screen.
Here is the result of the enc + tar + xz + base64 on Focal (works with
Lunar/Mantic too but you need to added ):
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARBdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc5VcodF6fu0hEp801tvirgSFNMSAHk5HMN/w
hCgU1BIr/nK51g3A3Lkdv7QNbaUw2ux1AmO/MpCLKLffCB9ElFZH4tuOS5AR
m9CJMzi6LQOw9wytGKm2IK3Ph7WpU6JQ/3HJilffQwHbFLnukiWGpLNO5v0O
D/4AJikrU9iemfChT0jXDbIRZ8a8VpVhJqu0u6eYOheVTqmSRiHHpIC/p1VA
ecFb0mACF/TQhjxcMUWGSGO/mtof+VaLiyg0KB87GKlChfwXTEvgbNuP9hmu
GL64VhX568Oy9EakSxlcXiIRk14kJKv0MdHQqY1R22wAACzqSr/nzpwqAAGs
AoBQAACjzq5WscRn+wIABFla
Here is the same but from Jammy if you want to test encryption on Jammy
and decryption on Lunar/Mantic:
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARFdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc1zK4HR2g3CiLJet+R++nZy/gph6RscQ6hI3
HySjdDOFRfjIVttiNK3DvRsZb37r8SXkj/JCYWicZGjWPZxVE3OAZhEed5qe
jrFv871QAbm4jVGD4oIc4cOb5V/xDN7KWgwEzpWQy6+tcfPm3KLPQvULx56N
2qQf60hP//p5EXS3RpCitUsrGUoYzTynjOUIRy2yCmgZDh62RmchUshyWePa
k0nEYlDbl5/dSHXbWEWESqW+QDj136MZRwQRY+QC4MvLXg2Bo8H+Dl/xvNDF
/5J4layZdFlh76lWOtFRVoIbX6JtpAP34g4zx1422GSNAABRzyqPdCqX
1AABrQKAUAAABh3ynbHEZ/sCAARZWg==
The contents are expected to be different due to the use of randomness.
Don't try to compare the base64 outputs: I'm only using them to ease
testing across containers.
[Where problems could occur]
This patch makes openssl match the documented default (see "man openssl-enc"
and search for "Blowfish" for instance) and fixes decryption from an up-to-date
Jammy to pretty much everything else, but it also create an issue for data
encrypted on Jammy without this patch and Jammy with this patch.
There are two possible cases: encrypted data being streamed across this
boundary or data at rest being transferred or read later.
Streaming is probably not an issue in practice because it's rather the
current situation that has been an issue and it's easy to remedy by
updating everything (which is relatively few machines since that's only
Jammy and not any other OS or distribution).
Data at rest is more annoying since updating Jammy will make it
impossible to read the data again without updates to other pieces of
software. That sounds like a really bad thing and it kind of is but at
the same, the benefits are much larger than the issues. Indeed, there is
already an incompatibility at the moment between Jammy and everything
else and the more time passes by, the more such problematic files can be
created. Luckily very few people are using blowfish nowadays and it's
not even enabled by default anymore in openssl. Moreover the software
update to work around the issue should be a single API call which is
documented in the upstream bug report (
https://github.com/openssl/openssl/issues/18359 ). Finally, I have
warned the two projects that I am aware are impacted; this is made
easier by the fact that they encountered the initial incompatibility.
[Patches]
The patches come directly from upstream and apply cleanly.
https://github.com/openssl/openssl/issues/18359
*
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-Fix-regression-in-default-key-length-for-Blowfish-CF.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0
*
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Test-the-default-key-length-of-the-Blowfish-ciphers.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0
=== Original
[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
** Description changed: === SRU information === [Meta] - This bug is part of a series of four bugs for a single SRU. + This bug is part of a series of three bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] S/MIME signature can fail silently The commit by upstream propagates the return code of some functions rather than ignore it. [Test plan] This issue is not very simple to reproduce because "openssl cms" cannot be used to do so. This has to be done with the openssl API instead. At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. [Where problems could occur] At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/pull/18876 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` -- 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/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: Won't Fix Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of three bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] S/MIME signature can fail silently The commit by upstream propagates the return code of some functions rather than ignore it. [Test plan] This issue is not very simple to reproduce because "openssl cms" cannot be used to do so. This has to be done with the openssl API instead. At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. [Where problems could occur] At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/pull/18876 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return
[Touch-packages] [Bug 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate
** Description changed: === SRU information === [Meta] - This bug is part of a series of four bugs for a single SRU. + This bug is part of a series of three bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] Openssl using an engine dumps core upon certificate creation; other operations are probably affected too. Overall, engines are likely mostly unusable. [Test plan] An engine is needed to test the fix and I don't think we have many in the archive. This complicates reproducing the issue. I have been relying on user reports which have been very detailled and helpful. The issue has also been reported independently and with another engine (devcrypto). The issue is fixed in openssl 3.0.8 which landed in lunar. [Where problems could occur] I don't pretend to understand the lifecycle of providers in openssl3 but the patch is simple and has been widely tested by now, including on ubuntu. Thus, I see little chance an unexpected problem would occur with it. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/issues/18578 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy- sru-0001-Release-the-drbg-in-the-global-default-context- befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' ---Problem Description--- OpenSSL with ibmca engine configured dumps core when creating a new certificate. # openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support # openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' Segmentation fault (core dumped) # journalctl Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b ilc:2 in libc.so.6[3ffae08+1ca000] Jun 07 13:06:08 SYSTEM kernel: Failing address: TEID: 0800 Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user ASCE. Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024 Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded Not tainted 5.15.0-73-generic #80-Ubuntu Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0) Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708 Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:0 PM:0 RI:0 EA:3 Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 02aa3289f9d0 Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 02aa328a4300 Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 02aa03ff Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 03ffae437c22 03ffec2fe000 Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2 lgr%r11,%r2 03ffae11c700: 4700bc0,0 #03ffae11c704: b24f00a0ear%r10,%a0 >03ffae11c708: 58102018l%r1,24(%r2) 03ffae11c70c: ebaa002dsllg%r10,%r10,32 03ffae11c712: b24f00a1ear%r10,%a1 03ffae11c716: 5910a0d0c%r1,208(%r10) 03ffae11c71a: a7840033brc8,03ffae11c780 Jun 07 13:06:08 SYSTEM kernel: Last Breaking-Event-Address: Jun 07 13:06:08 SYSTEM kernel: [<03ffae33242c>] 0x3ffae33242c Jun 07 13:06:08 SYSTEM systemd[1]: Started Process Core Dump (PID 2345/UID 0). Jun 07 13:06:08 SYSTEM systemd-coredump[2350]: Process 2344 (openssl) of user 0 dumped core. Found module linux-vdso64.so.1 with build-id: bcfab8ac8dbd44c758c3c5494e2952db16905d2e Found module libica.so.4 with build-id: 0cc5ace50644dfba6d0ecf4f783477cd04a55731 Found module ibmca.so with build-id: 27daaf0ed1857fdad3761c2b3db21020999eee08 Found module ld64.so.1 with build-id: 31d4856f0ba9ea058c91a34f4d684ae0fe01964c
[Touch-packages] [Bug 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
** Description changed: === SRU information === [ATTENTION] - This SRU contains FOUR changes which are listed in the section below. + This SRU contains THREE changes which are listed in the section below. [Meta] This bug is part of a series of four bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses four issues with Jammy's openssl version: - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections + - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections (this one) The SRU information has been added to the four bug reports and I am attaching the debdiff here only for all four. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). I have also pushed the code to git (without any attempt to make it git- ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . To test, follow these steps: - run "time python3 main.py" # using the aforementioned main.py script - apt install -t jammy-proposed libssl3 - run "time python3 main.py" - compare the runtimes for the two main.py runs You can run this on x86_64, Raspberry Pi 4 or any machine, and get a very large speed-up in all cases. The improvements are not architecture- dependant. Using this changeset, I get the following numbers for ten runs on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used slightly different versions (upstreams rather than patched with cherry-picks) but at least one of the version used does not include other performance change. He also used different hardware and this performance issue seems to depend on the number of CPUs available but also obtained a performance several times better. Results on a given machine vary also very little across runs (less than 2% variation on runs of size 10). They are also very similar on a Raspberry Pi 4 (8GB). The benchmark uses https://www.google.com/humans.txt which takes around 130ms to download on my machine but I modified the script to download something only 20ms away. Results are so close to the ones using humans.txt that they are within the error margin. This is consistent with the high-concurrency in the benchmark which both saturates CPU, and "hides" latencies that are relatively low. Finally, there are positive reports on github. Unfortunately they are not always completely targeted at these patches only and therefore I will not link directly to them but they have also been encouraging. [Where problems could occur] The change is spread over several patches which touch the internals of openssl. As such, the engine and provider functionality could be broken by these changes. Fortunately, in addition to upstream's code review, these patches are included in openssl 3.0.4 (iirc) and therefore in kinetic. No issue related to these changes was reported on launchpad or upstream. However, it is possible that there were more patch dependencies than these in either 3.0.3 or 3.0.4. In that case there
[Touch-packages] [Bug 2031413] Re: Inherited NFSv4 ACLs are overwritten when moving a file
** Changed in: glib Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2031413 Title: Inherited NFSv4 ACLs are overwritten when moving a file Status in GLib: New Status in glib2.0 package in Ubuntu: Triaged Bug description: Ubuntu version: 22.04 libglib2.0 version: libglib2.0-0_2.72.4-0ubuntu2.2 We are mounting an NFS share from an NFS server (FreeBSD 13). Authorization to directories in that share is enforced through NFSv4 ACLs on the server. When copying or moving a file to the share, it will inherit ACLs from the destination directory. In most of the cases this works fine. However, when we move a file that has ACLs to a directory in the share using Nautilus or "gio move", the ACL inheritance goes wrong. The destination file will end up with the original ACLs (the ACLs it had in the source location) instead of the ACLs that are inherited by the destination directory. This behaviour changed when we upgraded from Ubuntu 20.04 to Ubuntu 22.04. In Ubuntu 20.04 the ACL inheritance worked as expected. I assume what happens is the following: 1. A server-side move is performed 2. The destination file is assigned ACLs (they are inherited from the destination directory) 3. glib overwrites the ACLs of the destination file with the original ACLs To workaround the issue we patched glib and removed a call to g_file_set_attributes_from_info, see the attached patch. This brings the expected behaviour but may have unintended side effects. Steps to reproduce: 1. on the server (FreeBSD): prepare two directories A and B and assign the following NFSv4 ACLs: # file: A # owner: root # group: wheel user:alice:rwx--daARWc--s:fd-:allow owner@:rwxp-daARWc--s:fd-:allow group@:--a-R-c--s:fd-:allow everyone@:--a-R-c--s:fd-:allow # file: B # owner: root # group: wheel user:alice:rwx--daARWc--s:fd-:allow user:bob:rwx--daARWc--s:fd-:allow owner@:rwxp-daARWc--s:fd-:allow group@:--a-R-c--s:fd-:allow everyone@:--a-R-c--s:fd-:allow Note the inheritance flags (fd), which indicate that files in the directories will inherit the ACLs. 2. on the client (Ubuntu): mount the NFS share to /mnt using credentials of user "alice" 3. on the client: echo "hello world" > /mnt/A/test.txt 4. on the server: list the ACLs of A/test.txt: # file: A/test.txt # owner: alice # group: wheel user:alice:rw---daARWc--s:--I:allow owner@:rw-p-daARWc--s:--I:allow group@:--a-R-c--s:--I:allow everyone@:--a-R-c--s:--I:allow 5. on the client: gio move /mnt/A/test.txt /mnt/B/test.txt 6. on the server: list the ACLs of B/test.txt # file: B/test.txt # owner: alice # group: wheel user:alice:rw---daARWc--s:--I:allow owner@:rw-p-daARWc--s:--I:allow group@:--a-R-c--s:--I:allow everyone@:--a-R-c--s:--I:allow We expected an ACE for user bob, but it is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2031413/+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 2042042] [NEW] Browser does not remember workspace after leaving full screen video
Public bug reported:
Using 2x screens in portrait mode, if I display my browser on the right-
side panel of workspace 1, watch a video and full screen it, after I
off the video the browser will now be displayed on the left-side
panel of workspace 1.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Mon Oct 30 23:06:47 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX
540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (199 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (17 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.cron.daily.apport: [deleted]
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 mantic 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/2042042
Title:
Browser does not remember workspace after leaving full screen video
Status in xorg package in Ubuntu:
New
Bug description:
Using 2x screens in portrait mode, if I display my browser on the
right-side panel of workspace 1, watch a video and full screen it,
after I off the video the browser will now be displayed on the
left-side panel of workspace 1.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Mon Oct 30 23:06:47 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X /
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (199 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']}
[Touch-packages] [Bug 2042054] [NEW] 22.04.3, zen 4 7840, screen turn white exception
Public bug reported: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 corruption jammy ubuntu wayland-session ** Attachment added: "1698726947_bPTLiRIb.jpg" https://bugs.launchpad.net/bugs/2042054/+attachment/5714550/+files/1698726947_bPTLiRIb.jpg -- 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/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in xorg package in Ubuntu: New Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag
[Touch-packages] [Bug 1698593] Re: [Blade, Realtek ALC298, Black Mic, Left] No sound at all
2023 still having this issue here -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1698593 Title: [Blade, Realtek ALC298, Black Mic, Left] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I'm trying to get the mic from the combo jack on my Razer Blade working. Headphones are functioning perfectly, but the mic seems to be picking up on random data, unrelated to sound output or my surroundings. I know the jack is working as I dual-boot Windows, and it works great there. I've added the `options snd-hda-intel model=laptop-dmic` line as recommended in some other threads, and tried setting pin 0x18 to mic using hdajackretask, but it hasn't fixed it or made any difference. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: octy 1971 F...m pulseaudio /dev/snd/pcmC0D0p: octy 1971 F...m pulseaudio /dev/snd/controlC0: octy 1971 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sat Jun 17 15:21:41 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-06 (72 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: octy 1971 F...m pulseaudio /dev/snd/pcmC0D0p: octy 1971 F...m pulseaudio /dev/snd/controlC0: octy 1971 F pulseaudio Symptom_Jack: Black Mic, Left Symptom_Type: No sound at all Title: [Blade, Realtek ALC298, Black Mic, Left] No sound at all UpgradeStatus: Upgraded to zesty on 2017-04-15 (63 days ago) dmi.bios.date: 01/10/2017 dmi.bios.vendor: Razer dmi.bios.version: 1.00 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.name: Blade dmi.product.version: 6.06 dmi.sys.vendor: Razer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:06:35.753276 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1698593/+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 2023183] Re: network-manager autokpgtest failure (nm.py)
This bug was fixed in the package network-manager - 1.44.2-1ubuntu2 --- network-manager (1.44.2-1ubuntu2) noble; urgency=medium [ Lukas Märdian ] * network-manager.postinst: Skip unknown connection profiles (LP: #2039503) * d/network-manager.postinst: Drop reboot notification (LP: #2040292) [ Danilo Egea Gondolfo ] * debian/tests/nm_netplan.py Start Network Manager via systemd. The .service unit file sets ProtectSystem to true and we want to run the Netplan tests with this restriction enabled. * d/p/netplan/0003-Allow-the-NetworkManager-daemon-to-write-to-lib-netp.patch Allow-list /usr/lib/netplan so libnetplan can open files from that directory with writing permission. See LP: #2040153 * debian/tests/control Add all the dependencies required by the nm_netplan.py tests. * debian/tests/network_test_base.py. Increase the waiting time between creating a veth pair and reading their MAC addresses. On arm64, the system is taking longer to change the MAC after creation, leading to failures due to differences in the expected and current MAC addresses. See LP: #2023183 -- Lukas Märdian Thu, 26 Oct 2023 11:48:18 +0200 ** Changed in: network-manager (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2023183 Title: network-manager autokpgtest failure (nm.py) Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Lunar: Confirmed Status in network-manager source package in Mantic: Confirmed Status in network-manager source package in Noble: Fix Released Bug description: This fails only on arm64. https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz To be determined if there is a bug in the package or linux kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023183/+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 2034986] Re: some text became unreadable during a distribution upgrade
Because upgrades are not enabled yet for mantic -> noble, we still cannot explicitly verify the XDG_SESSION_TYPE fix for mantic. However, (a) since this exact patch was verified for lunar -> mantic, (b) this patch relates to upgrading *from* mantic rather than *to* mantic, and (c) we do not want to further delay upgrades to mantic, I believe it is reasonable to release ubuntu-release-upgrader to mantic-updates without explicit verification of the XDG_SESSION_TYPE fix. Hence, I am marking this bug as verified, and am requesting that the SRU team accepts this rationale. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
the screen turn into full white or full black or full strips randomly ** Attachment added: "1698726477_aX6I7W6U.jpg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042054/+attachment/5714568/+files/1698726477_aX6I7W6U.jpg -- 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/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in xorg package in Ubuntu: New Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042054/+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 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted
This bug was fixed in the package network-manager - 1.44.2-1ubuntu2 --- network-manager (1.44.2-1ubuntu2) noble; urgency=medium [ Lukas Märdian ] * network-manager.postinst: Skip unknown connection profiles (LP: #2039503) * d/network-manager.postinst: Drop reboot notification (LP: #2040292) [ Danilo Egea Gondolfo ] * debian/tests/nm_netplan.py Start Network Manager via systemd. The .service unit file sets ProtectSystem to true and we want to run the Netplan tests with this restriction enabled. * d/p/netplan/0003-Allow-the-NetworkManager-daemon-to-write-to-lib-netp.patch Allow-list /usr/lib/netplan so libnetplan can open files from that directory with writing permission. See LP: #2040153 * debian/tests/control Add all the dependencies required by the nm_netplan.py tests. * debian/tests/network_test_base.py. Increase the waiting time between creating a veth pair and reading their MAC addresses. On arm64, the system is taking longer to change the MAC after creation, leading to failures due to differences in the expected and current MAC addresses. See LP: #2023183 -- Lukas Märdian Thu, 26 Oct 2023 11:48:18 +0200 ** Changed in: network-manager (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2040153 Title: Network Manager will not remove Netplan YAMLs when connections are deleted Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Fix Released Status in netplan.io source package in Mantic: Invalid Status in network-manager source package in Mantic: Fix Released Bug description: [ Impact ] Desktop users, or any users with YAML files in /usr/lib/netplan, can't delete Network Manager connections persistently. That means that, when the connection is deliberately deleted by the user, it will re-appear when the system is rebooted or netplan apply is executed. This is happening because the systemd service unit is setting the property "ProtectSystem" to true. Because of that, /usr is being presented to the Network Manager daemon as read-only. When connections are deleted, libnetplan will try to open its YAML files with writing permissions and will fail for files from /usr/lib/netplan. Even if the user hasn't added any files there manually, the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by the package ubuntu-settings. This issue is fixed by allow-listing /usr/lib/netplan with ReadWritePaths=/usr/lib/netplan in systemd so the Network Manager's daemon will be able to write to that directory. This upload also improves the autopkgtests related to Netplan. Network Manager will be started by systemd, which ensures we are testing in the same environment conditions used by a desktop installation. It also adds a few more instances of connections deletions so we can test a bit more that YAML files are being removed. It also adds all the dependencies required by the test script (which sadly was causing the nm_netplan.py tests to be skipped). [ Test Plan ] Launch a new Mantic VM: $ lxc launch ubuntu:mantic --vm Install network-manager and ubuntu-settings: # apt install network-manager ubuntu-settings Run Netplan # netplan apply Create a dummy connection via nmcli: # nmcli con add type dummy connection.interface-name dummy0 Check a new YAML will be created in /etc/netplan Delete the connection with nmcli # nmcli con del dummy-dummy0 Check the YAML WAS NOT removed from /etc/netplan You will see the error below in the NetworkManager's journal netplan_delete_connection: Cannot write output state: Read-only file system Add the PPA containing the fix and run the same test described above # add-apt-repository ppa:danilogondolfo/network-manager # apt update # apt upgrade Check that the YAML will be created when the connection is added and deleted and the connection is removed. [ Where problems could occur ] As the only change is a relaxation of the restrictions applied by systemd on the environment where Network Manager runs, we are not expecting any regression. As for the changes in the autopkgtest related to Netplan, they are passing on all architectures. Autopkgtests amd64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/amd64/n/network-manager/20231023_175203_b2798@/log.gz ppc64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/ppc64el/n/network-manager/20231023_182332_f0497@/log.gz s390x - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/s390x/n/network-manager/20231023_190810_ced8d@/log.gz arm64 -
[Touch-packages] [Bug 2040292] Re: network-manager SRU flags system for restart required but also restarted the service
This bug was fixed in the package network-manager - 1.44.2-1ubuntu2 --- network-manager (1.44.2-1ubuntu2) noble; urgency=medium [ Lukas Märdian ] * network-manager.postinst: Skip unknown connection profiles (LP: #2039503) * d/network-manager.postinst: Drop reboot notification (LP: #2040292) [ Danilo Egea Gondolfo ] * debian/tests/nm_netplan.py Start Network Manager via systemd. The .service unit file sets ProtectSystem to true and we want to run the Netplan tests with this restriction enabled. * d/p/netplan/0003-Allow-the-NetworkManager-daemon-to-write-to-lib-netp.patch Allow-list /usr/lib/netplan so libnetplan can open files from that directory with writing permission. See LP: #2040153 * debian/tests/control Add all the dependencies required by the nm_netplan.py tests. * debian/tests/network_test_base.py. Increase the waiting time between creating a veth pair and reading their MAC addresses. On arm64, the system is taking longer to change the MAC after creation, leading to failures due to differences in the expected and current MAC addresses. See LP: #2023183 -- Lukas Märdian Thu, 26 Oct 2023 11:48:18 +0200 ** Changed in: network-manager (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2040292 Title: network-manager SRU flags system for restart required but also restarted the service Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Mantic: New Bug description: [ Impact ] * During an upgrade (or installation) of the network-manager package, its debian/network-manager.postinst maintainer script restarts NetworkManager.service and also requests users to reboot their system. * It requests a reboot, by calling into /usr/share/update-notifier/notify-reboot-required and listing "network-manager" in /var/run/reboot-required.pkgs * Restarting the systemd service AND asking for a reboot isn't needed. Just the service restart is enough and we shouldn't ask for a reboot as that is bad UX [ Test Plan ] * Reboot your system (or clear /var/run/reboot-required.pkgs) echo "" | sudo tee /var/run/reboot-required.pkgs * Install network-manager from mantic-proposed apt install [--reinstall] -t mantic-proposed network-manager * Observe that the NetworkManager.service was restarted by this operation: "active (running) [...] 2 min ago" systemctl status Networkmanager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; preset: enabled) Active: active (running) since Wed 2023-10-25 15:21:27 CEST; 2min ago Docs: man:NetworkManager(8) Main PID: 3880250 (NetworkManager) Tasks: 4 (limit: 28344) Memory: 6.1M CPU: 425ms CGroup: /system.slice/NetworkManager.service └─3880250 /usr/sbin/NetworkManager --no-daemon * Observe that network-manager was NOT written to /var/run/reboot-required.pkgs cat /var/run/reboot-required.pkgs * Observe that no GUI popped up asking you for a reboot because of NetworkManager [ Where problems could occur ] * This change is touching a maintainer script (.postinst) * Failures or syntax errors could leave the network-manager package unconfigured * It could break installation of the network-manager package [ Other Info ] * This SRU should probably just be staged, using `block-proposed-mantic` and bundled with the next upload. === original description === After applying the network-manager SRU in mantic, I get a notification that a system restart is required to fully apply updates. This immediately raised a question, because I KNOW my network connection was restarted when the SRU was installed (I have a VPN that did not auto-reconnect). And I checked the state of the process - it was definitely restarted and is running from the binary currently on disk. The network-manager postinst has the following code: # request a reboot (NM tears down interfaces on restart # which is not the way we want to go) [ -x /usr/share/update-notifier/notify-reboot-required ] && \ /usr/share/update-notifier/notify-reboot-required But the service restart is also happening. debian/rules currently has: override_dh_installsystemd: dh_installsystemd -pnetwork-manager --no-start NetworkManager-dispatcher.service NetworkManager-wait-online.service nm-priv-helper.service dh_installsystemd -pnetwork-manager --no-also NetworkManager.service No other systemd overrides. Nothing inhibits the restart of the service. It needs to be one or the other. And if we're doing SRUs of network- manager, then this is
