[Touch-packages] [Bug 1117804] Re: ausearch doesn't show AppArmor denial messages
responding to @intrigeri (sorry this got lost some how).
tldr: yes we are basically on the same page.
AppArmor does not fit into the 1400 range formats, every one of our
messages have some custom fields. Some of them could be
reformated/reworked to share more, but we would still need custom
fields.
Our message fields are in the common name=value format. So in that sense
they do fit in.
Kernel side this is fairly easy, we use common lsm_audit for the
messages we share in common, the code provides a callback to add your
own fields. Basically all that is needed is patch to allow different
number ranges to be used.
Userspace there needs to be some patching so LSM specific fields are
known about.
Whether is best to allocate new fields in a single number (say 1500),
with no fixed number of fields to output or it better to split into a
range of based on message type, I am not picky. When 1500 was taken away
from us I think it was 1500-1505 that we used, but expect we wouldn't
use the same mappings today if we had a choice.
so we have the generic audit type that is carried { audit, allowed,
denied, killed, prompt, hint, status, error }
this could carried as a common field, or we could use an allocated block
for
we have rule class, which is another way things are broken down, its
things like { file, cap, network, dbus, ...} there are currently about
25 of them currently.
common fields that can occur within apparmor messages { operation, info,
error, namespace, profile, label }, some fields aren't output if not
needed. Eg. we are auditing an access to say /etc/shadow that is allowed
but we want an audit trail for error won't be output, if its a system
status message that is not generated by a profiles rule set, profile=
won't be used. This set does not lend itself to an audit range as they
each take on basically a string value.
Then within a given class there are set of fields, some of them are shared by
several classes, but not all, and there are some that are only used by a single
class. Some examples would be, most mediation class share requested= and
denied= the values are class depended even those may be shared by a subset of
classes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1117804
Title:
ausearch doesn't show AppArmor denial messages
Status in AppArmor:
Confirmed
Status in audit package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Incomplete
Bug description:
The following command should display all AVC denials:
ausearch -m avc
However, it doesn't work with AppArmor denials. Here's a quick test
case to generate a denial, search for it with ausearch, and see that
no messages are displayed:
$ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current
cat: /proc/self/attr/current: Permission denied
$ sudo ausearch -m avc -c cat
ausearch claims that there are no matches, but there's a matching
audit message if you look in audit.log:
type=AVC msg=audit(1360193426.539:64): apparmor="DENIED"
operation="open" parent=8253 profile="/usr/sbin/tcpdump"
name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=1000
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1117804/+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 1959866] Re: lubuntu jammy - unable to submit bug via `ubuntu-bug calamares`
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1959866 Title: lubuntu jammy - unable to submit bug via `ubuntu-bug calamares` Status in apport package in Ubuntu: Expired Bug description: Lubuntu jammy QA-test install on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) but it failed; calamares issue... No prob; file bug. I had issues filing bug, thus this additional report. ** BACKGROUND on the install & other report calamares bug filed as https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865 was filed online; then apport-collect run successfully on box. That link is now added to this report here as `apport-collect` was run during the same boot or live session as issue occurred. As noted in comment #7 (of this report) and the now provided link; a end-users filing of an install issue had me attempt a 'strange' (stupid?) install; a QA-testcase we call "install using existing partition"; https://discourse.lubuntu.me/t/testing-checklist- understanding-the-testcases/2743 where you just re-use existing partitions without format.. EXCEPT I was attempting it here with an encrypted partition... no mount or anything; just selecting in calamares)... it was this install type that no doubt led to this error. ** EXPECTED OUTCOME `ubuntu-bug calamares` and file bug report via firefox.. ** ACTUAL OUTCOME Alas `ubuntu-bug` won't work with this error --- The problem cannot be reported: Your /tmp partition has less than 32.33792 MB of free space available, which leads to problems using applications and installing updates. Please free some space. Press any key to continue... --- Full terminal session follows --- lubuntu@lubuntu:~$ ubuntu-bug calamares *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** The contents of the files attached to this report will help developers diagnose your bug more quickly. It may be possible that there is sensitive information in these files. You will be able to review these attachments before they are sent. Do you want to include these files? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y *** Problem in calamares The problem cannot be reported: Your /tmp partition has less than 32.33792 MB of free space available, which leads to problems using applications and installing updates. Please free some space. Press any key to continue... No pending crash reports. Try --help for more information. -- Note: apport-collect has NOW been run on same box; same daily ISO, but it's a later reboot/session --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: LXQt DistroRelease: Ubuntu 22.04 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) Package: apport 2.20.11-0ubuntu76 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic 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/apport/+bug/1959866/+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 2028970] Re: Apport Crash
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2028970 Title: Apport Crash Status in apport package in Ubuntu: Expired Bug description: Powerglt crashed, but on report bug, apport-gtk crashed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport-gtk 2.20.11-0ubuntu82.5 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: GNOME Date: Fri Jul 28 11:41:11 2023 InstallationDate: Installed on 2022-09-19 (312 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2028970/+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 2028972] Re: Crash prompt dialog says that netplan script encountered an error
[Expired for apport (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apport (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2028972
Title:
Crash prompt dialog says that netplan script encountered an error
Status in apport package in Ubuntu:
Expired
Status in netplan.io package in Ubuntu:
Expired
Bug description:
I think this is on the ethernet NIC of this machine, which it is
having a problem connecting static... But generates and applies
without error.
I just replaced the motherboard from a Supermicro H8SGL-F with an AMD
Opteron 6386 SE to a MSI MPG Z790 Edge Wifi with Intel i9-13900K and
migrated the system to it: Legacy to UEFI, and LVM2 to ZFS.
This does have KVM and OpenVSwitch...
Output of Netplan Generate and Apply is:
mafoelffen@msi-ubuntu:~$ sudo netplan --debug generate
[sudo] password for mafoelffen:
DEBUG:command generate: running ['/lib/netplan/generate']
** (generate:37983): DEBUG: 11:58:12.511: starting new processing pass
** (generate:37983): DEBUG: 11:58:12.511: starting new processing pass
** (generate:37983): DEBUG: 11:58:12.511: enp5s0: adding new route
** (generate:37983): DEBUG: 11:58:12.511: We have some netdefs, pass them
through a final round of validation
** (generate:37983): DEBUG: 11:58:12.511: enp5s0: setting default backend to 1
** (generate:37983): DEBUG: 11:58:12.511: Configuration is valid
** (generate:37983): DEBUG: 11:58:12.511: Generating output files..
** (generate:37983): DEBUG: 11:58:12.511: openvswitch: definition enp5s0 is
not for us (backend 1)
** (generate:37983): DEBUG: 11:58:12.511: NetworkManager: definition enp5s0
is not for us (backend 1)
mafoelffen@msi-ubuntu:~$ sudo netplan --debug apply
** (generate:39541): DEBUG: 11:59:58.834: starting new processing pass
** (generate:39541): DEBUG: 11:59:58.834: starting new processing pass
** (generate:39541): DEBUG: 11:59:58.834: enp5s0: adding new route
** (generate:39541): DEBUG: 11:59:58.834: We have some netdefs, pass them
through a final round of validation
** (generate:39541): DEBUG: 11:59:58.834: enp5s0: setting default backend to 1
** (generate:39541): DEBUG: 11:59:58.834: Configuration is valid
** (generate:39541): DEBUG: 11:59:58.834: Generating output files..
** (generate:39541): DEBUG: 11:59:58.834: openvswitch: definition enp5s0 is
not for us (backend 1)
** (generate:39541): DEBUG: 11:59:58.834: NetworkManager: definition enp5s0
is not for us (backend 1)
DEBUG:netplan generated networkd configuration changed, reloading networkd
** (process:39539): DEBUG: 11:59:59.479: starting new processing pass
** (process:39539): DEBUG: 11:59:59.479: starting new processing pass
** (process:39539): DEBUG: 11:59:59.479: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.479: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.479: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.479: Configuration is valid
DEBUG:Merged config:
b''
DEBUG:no netplan generated NM configuration exists
** (process:39539): DEBUG: 11:59:59.490: starting new processing pass
** (process:39539): DEBUG: 11:59:59.491: starting new processing pass
** (process:39539): DEBUG: 11:59:59.491: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.491: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.491: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.491: Configuration is valid
DEBUG:Merged config:
b''
DEBUG:Link changes: {}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp5s0
DEBUG:netplan triggering .link rules for wlo1
DEBUG:netplan triggering .link rules for virbr2
DEBUG:netplan triggering .link rules for virbr1
DEBUG:netplan triggering .link rules for virbr0
DEBUG:netplan triggering .link rules for virbr3
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.604: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.604: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.604: Configuration is valid
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.604: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG:
[Touch-packages] [Bug 2028972] Re: Crash prompt dialog says that netplan script encountered an error
[Expired for netplan.io (Ubuntu) because there has been no activity for
60 days.]
** Changed in: netplan.io (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2028972
Title:
Crash prompt dialog says that netplan script encountered an error
Status in apport package in Ubuntu:
Expired
Status in netplan.io package in Ubuntu:
Expired
Bug description:
I think this is on the ethernet NIC of this machine, which it is
having a problem connecting static... But generates and applies
without error.
I just replaced the motherboard from a Supermicro H8SGL-F with an AMD
Opteron 6386 SE to a MSI MPG Z790 Edge Wifi with Intel i9-13900K and
migrated the system to it: Legacy to UEFI, and LVM2 to ZFS.
This does have KVM and OpenVSwitch...
Output of Netplan Generate and Apply is:
mafoelffen@msi-ubuntu:~$ sudo netplan --debug generate
[sudo] password for mafoelffen:
DEBUG:command generate: running ['/lib/netplan/generate']
** (generate:37983): DEBUG: 11:58:12.511: starting new processing pass
** (generate:37983): DEBUG: 11:58:12.511: starting new processing pass
** (generate:37983): DEBUG: 11:58:12.511: enp5s0: adding new route
** (generate:37983): DEBUG: 11:58:12.511: We have some netdefs, pass them
through a final round of validation
** (generate:37983): DEBUG: 11:58:12.511: enp5s0: setting default backend to 1
** (generate:37983): DEBUG: 11:58:12.511: Configuration is valid
** (generate:37983): DEBUG: 11:58:12.511: Generating output files..
** (generate:37983): DEBUG: 11:58:12.511: openvswitch: definition enp5s0 is
not for us (backend 1)
** (generate:37983): DEBUG: 11:58:12.511: NetworkManager: definition enp5s0
is not for us (backend 1)
mafoelffen@msi-ubuntu:~$ sudo netplan --debug apply
** (generate:39541): DEBUG: 11:59:58.834: starting new processing pass
** (generate:39541): DEBUG: 11:59:58.834: starting new processing pass
** (generate:39541): DEBUG: 11:59:58.834: enp5s0: adding new route
** (generate:39541): DEBUG: 11:59:58.834: We have some netdefs, pass them
through a final round of validation
** (generate:39541): DEBUG: 11:59:58.834: enp5s0: setting default backend to 1
** (generate:39541): DEBUG: 11:59:58.834: Configuration is valid
** (generate:39541): DEBUG: 11:59:58.834: Generating output files..
** (generate:39541): DEBUG: 11:59:58.834: openvswitch: definition enp5s0 is
not for us (backend 1)
** (generate:39541): DEBUG: 11:59:58.834: NetworkManager: definition enp5s0
is not for us (backend 1)
DEBUG:netplan generated networkd configuration changed, reloading networkd
** (process:39539): DEBUG: 11:59:59.479: starting new processing pass
** (process:39539): DEBUG: 11:59:59.479: starting new processing pass
** (process:39539): DEBUG: 11:59:59.479: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.479: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.479: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.479: Configuration is valid
DEBUG:Merged config:
b''
DEBUG:no netplan generated NM configuration exists
** (process:39539): DEBUG: 11:59:59.490: starting new processing pass
** (process:39539): DEBUG: 11:59:59.491: starting new processing pass
** (process:39539): DEBUG: 11:59:59.491: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.491: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.491: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.491: Configuration is valid
DEBUG:Merged config:
b''
DEBUG:Link changes: {}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp5s0
DEBUG:netplan triggering .link rules for wlo1
DEBUG:netplan triggering .link rules for virbr2
DEBUG:netplan triggering .link rules for virbr1
DEBUG:netplan triggering .link rules for virbr0
DEBUG:netplan triggering .link rules for virbr3
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.604: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.604: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.604: Configuration is valid
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.604: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG:
[Touch-packages] [Bug 1811596] Re: Ubuntu Single Sign-On GUI not showing login button
** Changed in: gnome-online-accounts Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1811596 Title: Ubuntu Single Sign-On GUI not showing login button Status in gnome-online-accounts: Fix Released Status in gnome-online-accounts package in Ubuntu: Triaged Status in unity-control-center package in Ubuntu: Invalid Bug description: System Settings->Online Accounts->Ubuntu Single Sign-On I can enter my email address and password abd select "I have an Ubuntu Single Sign-On account". But there is no "Save" or "Login" or any other button. I can only close the window. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1811596/+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 2049402] Re: sshd doesn't properly disable KbdInteractiveAuthentication
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2049402 Title: sshd doesn't properly disable KbdInteractiveAuthentication Status in openssh package in Ubuntu: Incomplete Bug description: On 22.04 in OpenSSH_8.9p1 Ubuntu-3ubuntu0.6, OpenSSL 3.0.2 15 Mar 2022 setting KbdInteractiveAuthentication=no in sshd_config does not disable keyboard-interactive authentication. After updating (and restarting the sshd service) `sshd -T` still reports `kbdinteractiveauthentication yes` attempts to connect to sshd also allow keyboard-interactive authentication. Possibly related to https://bugs.archlinux.org/task/71941 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2049402/+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 1529431] Re: Add insert-text icon to non-full icon package
This bug was fixed in the package adwaita-icon-theme - 45.0-4 --- adwaita-icon-theme (45.0-4) unstable; urgency=medium * Depend on ubuntu-mono on Ubuntu * Run wrap-and-sort * Sync to Ubuntu and drop adwaita-icon-theme-full (LP: #2045962, LP: #1961495, LP: #1882271, LP: #1529431) -- Jeremy Bícha Fri, 09 Feb 2024 07:40:37 -0500 ** Changed in: adwaita-icon-theme (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1529431 Title: Add insert-text icon to non-full icon package Status in adwaita-icon-theme package in Ubuntu: Fix Released Status in gnome-icon-theme package in Ubuntu: Fix Released Bug description: Please can you move the "insert-text" icon from gnome-icon-theme-full to gnome-icon-theme, and from adwaita-icon-theme-full to adwaita-icon- theme. Currently easytag has an ubuntu specific patch to use gnome-icon- theme-full instead of gnome-icon-theme so it can use this icon, but reading the description of the package split it seems to me that gnome-icon-theme should still "provide" it somehow - even if it gets installed through a dependency on an ubuntu specific icon theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1529431/+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 2052851] Re: add-apt-repository Cannot Manage deb822 Repository Sources
** Description changed: On Ubuntu 23.10... * When adding a PPA, 'add-apt-repository' will add the repository in the - new deb822 format as a .sources file in + new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages quite frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html -- 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/2052851 Title: add-apt-repository Cannot Manage deb822 Repository Sources Status in software-properties package in Ubuntu: New Bug description: On Ubuntu 23.10... * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages quite frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2052851/+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 1117804] Re: ausearch doesn't show AppArmor denial messages
As far as I know, no one has made an effort to try to improve the situation lately. There's some discussion at https://lists.ubuntu.com/archives/apparmor/2024-February/013091.html that may be enlightening, if not encouraging. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1117804 Title: ausearch doesn't show AppArmor denial messages Status in AppArmor: Confirmed Status in audit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: The following command should display all AVC denials: ausearch -m avc However, it doesn't work with AppArmor denials. Here's a quick test case to generate a denial, search for it with ausearch, and see that no messages are displayed: $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current cat: /proc/self/attr/current: Permission denied $ sudo ausearch -m avc -c cat ausearch claims that there are no matches, but there's a matching audit message if you look in audit.log: type=AVC msg=audit(1360193426.539:64): apparmor="DENIED" operation="open" parent=8253 profile="/usr/sbin/tcpdump" name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1117804/+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 2052851] Re: add-apt-repository Cannot Manage deb822 Repository Sources
For now I'm using the following workaround to create the old style
'.list' file from the command line (ZSH). It's a pain, but PPA
management works peachy again.
1. Created an 'aptaddppa' function:
---
aptaddppa () {
curl -fsSL
"https://keyserver.ubuntu.com/pks/lookup?op=get=0x${4}; | sudo
gpg --dearmor -o /etc/apt/trusted.gpg.d/"${1}".gpg
echo "deb [arch=$(dpkg --print-architecture)] ${2} $(lsb_release
-cs) ${3}" | sudo tee /etc/apt/sources.list.d/"${1}".list
sudo apt update
}
---
2. From the command line (ZSH):
$ aptaddppa flacon https://ppa.launchpadcontent.net/flacon/ppa/ubuntu
main 0606FBEA73863686801BE20ED5790E4FF2A61FE5
--
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/2052851
Title:
add-apt-repository Cannot Manage deb822 Repository Sources
Status in software-properties package in Ubuntu:
New
Bug description:
On Ubuntu 23.10...
* When adding a PPA, 'add-apt-repository' will add the repository in
the new deb822 format as a .sources file in
'/etc/apt/sources.list.d'
* However, 'add-apt-repository --list' cannot see/understand the new
'.sources' file
For example, with the flacon ppa
(https://launchpad.net/~flacon/+archive/ubuntu/ppa):
1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as
'/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources'
2. apt can install and update from the new repo, as expected. you can
also remove the repo, as expected, by running 'sudo add-apt-repository
--remove ppa:flacon/ppa'
3. However, 'add-apt-repository --list' does not list the repo as it
should. GUI package managers such as Muon and Synaptic also do not see
the new repo.
It makes working with packages quite frustrating, and unfortunately,
per Julian Andres Klode (juliank), there seems to be no plan to fix
the broken 'software-properties-common' any time soon. See here:
https://bugs.launchpad.net/ubuntu/+source/software-
properties/+bug/2033949
Also see related issues:
https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288
https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2052851/+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 2052851] [NEW] add-apt-repository Cannot Manage deb822 Repository Sources
Public bug reported: On Ubuntu 23.10... * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a .sources file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages quite frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: mantic ** Description changed: On Ubuntu 23.10... * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a .sources file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): - 1. `sudo add-apt-repository ppa:flacon/ppa` adds the flacon repo as - `/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources` + 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as + '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can - also remove the repo, as expected, by running `sudo add-apt-repository - --remove ppa:flacon/ppa` + also remove the repo, as expected, by running 'sudo add-apt-repository + --remove ppa:flacon/ppa' - 3. However, `add-apt-repository --list` does not list the repo as it + 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages quite frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the - broken `software-properties-common`. See here: + broken 'software-properties-common'. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html ** Description changed: On Ubuntu 23.10... * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a .sources file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages quite frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the - broken 'software-properties-common'. See here: + broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties
[Touch-packages] [Bug 2040405] Re: Merge openldap from Debian unstable for noble
** Changed in: openldap (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2040405
Title:
Merge openldap from Debian unstable for noble
Status in openldap package in Ubuntu:
Fix Committed
Bug description:
Upstream: tbd
Debian: 2.5.13+dfsg-52.6.6+dfsg-1~exp2
Ubuntu: 2.6.6+dfsg-1~exp1ubuntu1
Debian new has 2.6.6+dfsg-1~exp2, which may be available for merge
soon.
If it turns out this needs a sync rather than a merge, please change
the tag 'needs-merge' to 'needs-sync', and (optionally) update the
title as desired.
### New Debian Changes ###
openldap (2.5.13+dfsg-5) unstable; urgency=medium
* Fix sha2-contrib autopkgtest failure. Call slappasswd using its full path.
(Closes: #1030814)
* Disable flaky test test069-delta-multiprovider-starttls.
-- Ryan Tandy Tue, 07 Feb 2023 17:56:12 -0800
openldap (2.5.13+dfsg-4) unstable; urgency=medium
[ Andreas Hasenack ]
* d/rules: Fix passwd/sha2 build (Closes: #1030716, LP: #2000817)
* d/t/sha2-contrib: add test for sha2 module
-- Ryan Tandy Mon, 06 Feb 2023 19:21:05 -0800
openldap (2.5.13+dfsg-3) unstable; urgency=medium
[ Ryan Tandy ]
* Disable flaky test test063-delta-multiprovider. Mitigates #1010608.
[ Gioele Barabucci ]
* slapd.scripts-common: Avoid double-UTF8-encoding org name (Closes:
#1016185)
* d/slapd.scripts-common: Remove outdated `migrate_to_slapd_d_style`
* d/slapd.postinst: Remove test for ancient version
* slapd.scripts-common: Remove unused `normalize_ldif`
* d/slapd.scripts-common: Use sed instead of perl in `release_diagnostics`
-- Ryan Tandy Fri, 13 Jan 2023 16:29:59 -0800
openldap (2.5.13+dfsg-2) unstable; urgency=medium
* d/tests/smbk5pwd: Grant slapd access to /var/lib/heimdal-kdc. Fixes the
autopkgtest failure due to heimdal setting mode 700 on this directory.
(Closes: #1020442)
* d/source/lintian-overrides: Add wildcards to make overrides compatible
with both older and newer versions of lintian.
* d/slapd-contrib.lintian-overrides: Remove unused
custom-library-search-path override now that krb5-config no longer sets
-rpath.
-- Ryan Tandy Sat, 24 Sep 2022 12:40:21 -0700
openldap (2.5.13+dfsg-1) unstable; urgency=medium
* d/rules: Remove get-orig-source, now unnecessary.
* Check PGP signature when running uscan.
* d/watch: Modernize watch file; use repacksuffix.
* d/copyright: Update according to DEP-5.
* d/control: Add myself to Uploaders.
* New upstream release.
-- Sergio Durigan Junior Sun, 18 Sep 2022
18:29:46 -0400
openldap (2.5.12+dfsg-2) unstable; urgency=medium
* Stop slapd explicitly in prerm as a workaround for #1006147, which caused
dpkg-reconfigure to not restart the service, so the new configuration was
not applied. See also #994204. (Closes: #1010971)
-- Ryan Tandy Mon, 23 May 2022 10:14:53 -0700
openldap (2.5.12+dfsg-1) unstable; urgency=medium
* New upstream release.
- Fixed SQL injection in back-sql (ITS#9815) (CVE-2022-29155)
* Update debconf translations:
- German, thanks to Helge Kreutzmann. (Closes: #1007728)
- Spanish, thanks to Camaleón. (Closes: #1008529)
- Dutch, thanks to Frans Spiesschaert. (Closes: #1010034)
-- Ryan Tandy Wed, 04 May 2022 18:00:16 -0700
openldap (2.5.11+dfsg-1) unstable; urgency=medium
* Upload to unstable.
-- Ryan Tandy Fri, 11 Mar 2022 19:38:02 -0800
openldap (2.5.11+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
* Add openssl to Build-Depends to enable more checks in test067-tls.
* Update slapd-contrib's custom-library-search-path override to work with
current Lintian.
-- Ryan Tandy Sun, 23 Jan 2022 17:16:05 -0800
openldap (2.5.8+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
* Update slapd-contrib's custom-library-search-path override to work with
Lintian 2.108.0.
-- Ryan Tandy Wed, 13 Oct 2021 18:42:55 -0700
openldap (2.5.7+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
* Don't run autoreconf in contrib/ldapc++. We don't build it, and it is not
### Old Ubuntu Delta ###
openldap (2.6.6+dfsg-1~exp1ubuntu1) mantic; urgency=medium
* Merge with Debian unstable (LP: #2028721). Remaining changes:
- Enable AppArmor support:
+ d/apparmor-profile: add AppArmor profile
+ d/rules: use dh_apparmor
+ d/control: Build-Depends on dh-apparmor
+ d/slapd.README.Debian: add note about AppArmor
- Enable ufw support:
+ d/control: suggest ufw.
+ d/rules: install ufw profile.
+ d/slapd.ufw.profile: add ufw profile.
- d/{rules,slapd.py}: Add apport
[Touch-packages] [Bug 2040465] Re: New upstream microrelease 2.5.17
dep8 results: Results: (from http://autopkgtest.ubuntu.com/results/autopkgtest-jammy-sergiodj-openldap/?format=plain) openldap @ amd64: http://autopkgtest.ubuntu.com/results/autopkgtest-jammy-sergiodj-openldap/jammy/amd64/o/openldap/20240209_225823_2ec27@/log.gz 09.02.24 22:58:23 ✅ Triggers: openldap/2.5.17+dfsg-0ubuntu0.22.04.1~ppa1 openldap @ arm64: http://autopkgtest.ubuntu.com/results/autopkgtest-jammy-sergiodj-openldap/jammy/arm64/o/openldap/20240209_230358_34851@/log.gz 09.02.24 23:03:58 ✅ Triggers: openldap/2.5.17+dfsg-0ubuntu0.22.04.1~ppa1 openldap @ armhf: http://autopkgtest.ubuntu.com/results/autopkgtest-jammy-sergiodj-openldap/jammy/armhf/o/openldap/20240209_230114_34851@/log.gz 09.02.24 23:01:14 ✅ Triggers: openldap/2.5.17+dfsg-0ubuntu0.22.04.1~ppa1 openldap @ ppc64el: http://autopkgtest.ubuntu.com/results/autopkgtest-jammy-sergiodj-openldap/jammy/ppc64el/o/openldap/20240209_231213_2ec27@/log.gz 09.02.24 23:12:13 ✅ Triggers: openldap/2.5.17+dfsg-0ubuntu0.22.04.1~ppa1 openldap @ s390x: http://autopkgtest.ubuntu.com/results/autopkgtest-jammy-sergiodj-openldap/jammy/s390x/o/openldap/20240209_225840_2ec27@/log.gz 09.02.24 22:58:40 ✅ Triggers: openldap/2.5.17+dfsg-0ubuntu0.22.04.1~ppa1 ** Changed in: openldap (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2040465 Title: New upstream microrelease 2.5.17 Status in openldap package in Ubuntu: Invalid Status in openldap source package in Jammy: In Progress Bug description: [ Impact ] * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.17. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/XRQE4CVQDLTG4EYPKVEU2L76DYGIFR2Q/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/commit/99a124bb434052a71cf4ff115d0f949f6c6b7208/pipelines?ref=OPENLDAP_REL_ENG_2_5 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/4744NWC2HJP7L24WOUMZF4VCYGGUMRI7/ * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in a PPA and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: - https://launchpadlibrarian.net/679769800/buildlog_ubuntu-jammy-amd64.openldap_2.5.16+dfsg-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz [ Where problems could occur ] * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since we are dealing with a microrelease upgrade. Whenever a test failure is detected, we will be on top of it and make sure it doesn't affect existing users. [ Other Info ] * This is a reoccurring MRE. See below for links to previous OpenLDAP MREs. * CVEs fixed by this release: - None. Current versions in supported releases that got updates: openldap | 2.5.16+dfsg-0ubuntu0.22.04.2 | jammy-security | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 - https://pad.lv/1983618 - https://pad.lv/2007625 - https://pad.lv/2027079 - https://pad.lv/2029170 As usual we test and prep from the PPA and then push through SRU/Security as applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2040465/+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 2040465] Re: New upstream microrelease 2.5.17
As per Steve's reply here: https://lists.ubuntu.com/archives/ubuntu-devel/2023-December/042854.html I'm not going to run autopkgtest against all reverse dependencies of the package. Instead, I will rely on the results from the archive and act accordingly. Therefore, I've just uploaded the package to Jammy unapproved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2040465 Title: New upstream microrelease 2.5.17 Status in openldap package in Ubuntu: Invalid Status in openldap source package in Jammy: In Progress Bug description: [ Impact ] * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.17. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/XRQE4CVQDLTG4EYPKVEU2L76DYGIFR2Q/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/commit/99a124bb434052a71cf4ff115d0f949f6c6b7208/pipelines?ref=OPENLDAP_REL_ENG_2_5 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/4744NWC2HJP7L24WOUMZF4VCYGGUMRI7/ * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in a PPA and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: - https://launchpadlibrarian.net/679769800/buildlog_ubuntu-jammy-amd64.openldap_2.5.16+dfsg-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz [ Where problems could occur ] * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since we are dealing with a microrelease upgrade. Whenever a test failure is detected, we will be on top of it and make sure it doesn't affect existing users. [ Other Info ] * This is a reoccurring MRE. See below for links to previous OpenLDAP MREs. * CVEs fixed by this release: - None. Current versions in supported releases that got updates: openldap | 2.5.16+dfsg-0ubuntu0.22.04.2 | jammy-security | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 - https://pad.lv/1983618 - https://pad.lv/2007625 - https://pad.lv/2027079 - https://pad.lv/2029170 As usual we test and prep from the PPA and then push through SRU/Security as applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2040465/+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 2046624] Re: apparmor breaks surfshark vpn
*** This bug is a duplicate of bug 2046844 *** https://bugs.launchpad.net/bugs/2046844 Late for the party, But>>> Verified on KVM install "Active apt repos in: /etc/apt/sources.list.d/apparmor-dev-ubuntu-unprivileged-userns-noble.sources 1: deb https://ppa.launchpadcontent.net/apparmor-dev/unprivileged-userns/ubuntu/ noble main " And "sudo aa-status |grep Surfshark* /opt/Surfshark/surfshark (2399) surfshark /opt/Surfshark/surfshark (2636) surfshark /opt/Surfshark/surfshark (2637) surfshark /opt/Surfshark/surfshark (2668) surfshark /opt/Surfshark/chrome_crashpad_handler (2720) surfshark /opt/Surfshark/surfshark (2770) surfshark /opt/Surfshark/surfshark (2777) surfshark /opt/Surfshark/surfshark (2793) surfshark " -- 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/2046624 Title: apparmor breaks surfshark vpn Status in apparmor package in Ubuntu: New Bug description: with the new apparmor Candidate: 4.0.0~alpha2-0ubuntu7 Breaks my VPN *surfshark [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap It will work with --no-sandbox "surfshark --no-sandbox" not ideal. I removed apparmor for proof *apt policy apparmor apparmor: Installed: (none) Candidate: 4.0.0~alpha2-0ubuntu7 Version table: 4.0.0~alpha2-0ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages Now my VPN works as expected, spent 2 hrs this morning with surfshark support, they will get back to me in a day or two, but they can't find anything wrong on their end. So far it points to apparmor ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apparmor (not installed) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Dec 16 10:40:00 2023 InstallationDate: Installed on 2023-12-10 (6 days ago) InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2052735] Re: python-memcache: autopkgtests fails due to invalid escape sequence '\ ' with python 3.12
** Changed in: python-memcache (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2052735 Title: python-memcache: autopkgtests fails due to invalid escape sequence '\ ' with python 3.12 Status in python-memcache package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in python-memcache package in Debian: Fix Released Bug description: When running autopkgtests with python 3.12 the following failure occurs: 39s Removing autopkgtest-satdep (0) ... 439s autopkgtest [14:50:01]: test command1: python3 -c "import memcache; print(memcache.__version__)" 439s autopkgtest [14:50:01]: test command1: [--- 439s /tmp/autopkgtest.K47W5d/build.QVn/src/memcache.py:110: SyntaxWarning: invalid escape sequence '\ ' 439s """Object representing a pool of memcache servers. 439s 1.58 440s autopkgtest [14:50:02]: test command1: ---] 440s autopkgtest [14:50:02]: test command1: - - - - - - - - - - results - - - - - - - - - - 440s command1 FAIL stderr: /tmp/autopkgtest.K47W5d/build.QVn/src/memcache.py:110: SyntaxWarning: invalid escape sequence '\ ' 440s autopkgtest [14:50:02]: test command1: - - - - - - - - - - stderr - - - - - - - - - - 440s /tmp/autopkgtest.K47W5d/build.QVn/src/memcache.py:110: SyntaxWarning: invalid escape sequence '\ ' 440s """Object representing a pool of memcache servers. 440s autopkgtest [14:50:02]: test unittests: preparing testbed [1] This warning was fixed upstream in the following commit[2] [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/p/python-memcache/20240207_145048_20ad0@/log.gz [2] https://github.com/linsomniac/python-memcached/commit/6e57445fd3be869e9928ef609a107342500c8e97 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-memcache/+bug/2052735/+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 2039358] Re: Audio via bluetooth gets intermitent when a browser is started
*** This bug is a duplicate of bug 2038539 *** https://bugs.launchpad.net/bugs/2038539 the duplicate bug appears as fixed ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Released -- 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/2039358 Title: Audio via bluetooth gets intermitent when a browser is started Status in alsa-driver package in Ubuntu: Fix Released Bug description: listening to a fresh boot of mantic install .. sound works properly and bluetooh headphones/speaker connection is flawless.. starting a browser .. audio becomes choppy via bluetooth .. laptop speaker suffer no degradation.. occurs with kernels above 6.5.0-5 see bug 2038539 also.. (reported from a 6.5.0-5 kernel instance This report was added so a report from a 6.5.0-9 kernel instance is made ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derk 1707 F wireplumber /dev/snd/controlC1: derk 1707 F wireplumber /dev/snd/seq:derk 1704 F pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Oct 14 10:39:35 2023 InstallationDate: Installed on 2023-10-04 (10 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16ABR8 dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8: dmi.product.family: IdeaPad Slim 5 16ABR8 dmi.product.name: 82XG dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8 dmi.product.version: IdeaPad Slim 5 16ABR8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2039358/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
I'm glad to hear you are seeing an improvement! The current implementation is still racy as mentioned in Comment #22. I did a search of the logs I downloaded, and I believe this one shows that the mount_partition() race isn't just theoretical: https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/amd64/l/livecd-rootfs/20230928_132941_a6800@/log.gz So my suggestion is that we: 1) wait for systemd 255.3 to be merged in noble to fix the issue w/ `udevadm lock` 2) convert livecd-rootfs to use udevadm lock in noble, addressing the remaining known races. 3) backport `udevadm lock` to jammy (likely as a low-priority SRU) 4) backport the`udevadm lock` support to livecd-rootfs I realize that'll take some time, so if you want to SRU the partial fix as a stop-gap, feel free. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: New Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2040465] Re: MRE updates of openldap for noble
** Description changed: - Backport openldap as MRE to noble once the update for noble has been - completed. + [ Impact ] - + * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.17. - [Impact] - TBD + This update includes bugfixes only following the SRU policy exception + defined at https://wiki.ubuntu.com/OpenLDAPUpdates. - [Major Changes] - TBD + [ Major Changes ] - [Test Plan] - TBD + * See the list of bugs fixed in this release here: - [Regression Potential] - Upstream has an extensive build and integration test suite. So regressions would likely arise from a change in interaction with Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. - + https://lists.openldap.org/hyperkitty/list/openldap- + annou...@openldap.org/thread/XRQE4CVQDLTG4EYPKVEU2L76DYGIFR2Q/ + + [ Test Plan ] + + * Upstream gitlab pipeline results: + + https://git.openldap.org/openldap/openldap/-/commit/99a124bb434052a71cf4ff115d0f949f6c6b7208/pipelines?ref=OPENLDAP_REL_ENG_2_5 + + * Upstream "call for testing": + + https://lists.openldap.org/hyperkitty/list/openldap- + techni...@openldap.org/thread/4744NWC2HJP7L24WOUMZF4VCYGGUMRI7/ + + * As described in the MRE wiki page for OpenLDAP, the test plan is to + build the package in a PPA and make sure that (1) all build-time tests + pass and (2) all autopkgtest runs (from reverse dependencies) also pass. + + * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: + - https://launchpadlibrarian.net/679769800/buildlog_ubuntu-jammy-amd64.openldap_2.5.16+dfsg-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz + + [ Where problems could occur ] + + * Upstream tests are always executed during build-time. There are many + reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage + is good. Nevertheless, there is always a risk for something to break + since we are dealing with a microrelease upgrade. Whenever a test + failure is detected, we will be on top of it and make sure it doesn't + affect existing users. + + [ Other Info ] + + * This is a reoccurring MRE. See below for links to previous OpenLDAP + MREs. + + * CVEs fixed by this release: +- None. + + Current versions in supported releases that got updates: + openldap | 2.5.16+dfsg-0ubuntu0.22.04.2 | jammy-security | source + + Special cases: + - None. + + Previous MREs for OpenLDAP: + - https://pad.lv/1977627 + - https://pad.lv/1983618 + - https://pad.lv/2007625 + - https://pad.lv/2027079 + - https://pad.lv/2029170 + + As usual we test and prep from the PPA and then push through + SRU/Security as applicable. ** Also affects: openldap (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: openldap (Ubuntu Noble) ** Changed in: openldap (Ubuntu) Status: New => Invalid ** Changed in: openldap (Ubuntu Jammy) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Summary changed: - MRE updates of openldap for noble + New upstream microrelease 2.5.17 ** Changed in: openldap (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2040465 Title: New upstream microrelease 2.5.17 Status in openldap package in Ubuntu: Invalid Status in openldap source package in Jammy: Triaged Bug description: [ Impact ] * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.17. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/XRQE4CVQDLTG4EYPKVEU2L76DYGIFR2Q/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/commit/99a124bb434052a71cf4ff115d0f949f6c6b7208/pipelines?ref=OPENLDAP_REL_ENG_2_5 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/4744NWC2HJP7L24WOUMZF4VCYGGUMRI7/ * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in a PPA and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: - https://launchpadlibrarian.net/679769800/buildlog_ubuntu-jammy-amd64.openldap_2.5.16+dfsg-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz [ Where problems could occur ] * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since
[Touch-packages] [Bug 2049318] Re: [SRU] free(): double free detected in tcache 2
I have now tested the second more complicated test as mentioned in the test plan and can confirm that the test has passed. The previous error is not seen any more. For reference, I am attaching my terminal log. Package tested: $ apt-cache policy iptables iptables: Installed: 1.8.7-1ubuntu5.2 Candidate: 1.8.7-1ubuntu5.2 Version table: *** 1.8.7-1ubuntu5.2 500 500 http://gb.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.8.7-1ubuntu5.1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 1.8.7-1ubuntu5 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Attachment added: "terminal.log" https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2049318/+attachment/5745470/+files/terminal.log ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2049318 Title: [SRU] free(): double free detected in tcache 2 Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Jammy: Fix Committed Bug description: [ Impact ] iptables is unable to list the iptables rules or save the iptables rules if a nftables ruleset is defined which iptables does not recognize. [ Test Plan ] 1. Simple test plan based on upstream test case: sudo nft -f - < rules.txt * Convert the rule to nftables ruleset - sudo iptables-nft-restore < rules.txt * List the nftables ruleset - sudo nft list ruleset * Also confirm that iptables can list the old rule - sudo iptables -L * Now add another nftables rule (this rule is taken from upstream test case) sudo nft -f -
[Touch-packages] [Bug 2029473] Please test proposed package
Hello Nathan, or anyone else affected, Accepted software-properties into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software-properties/0.96.20.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2029473 Title: Backport Ubuntu Pro to Xenial Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: Fix Committed Bug description: * Impact We want desktop integration with Ubuntu Pro * Test case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - $ software-properties-gtk -> the list of tabs should include an 'Ubuntu Pro' one The Ubuntu Pro tab should state 'This machine is not covered by an Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have other controls inactive - click 'Enable Ubuntu Pro' -> A dialog 'Enable Ubuntu Pro' opens -> the first option 'Enter code on ubuntu.com/pro/attach' is selected -> a pincode is displayed under the option - go to http//ubuntu.com/pro/attach and enter the pincode -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode - click 'Confirm' -> you should get an authentification prompt - enter your password -> a spinner starts animating instead of the 'Valid token' label -> once the attachment job is done the dialog is autoclosed -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) - check that the '$ pro status' output matches the UI one - try enabling/disable options -> verify that the 'pro status' change accordingly - Click 'Disable Ubuntu Pro' -> you get asked for confirmation and password -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore - Go through the testcase again but selecting the 'Or add token manually' option, the steps should be similar * Regression Potential There could be problems in the UI The new service could be not working as expected Strings are new and currently have no translations The livepatch checkbox is also inactive because the current update- notifier version in xenial doesn't include livepatch support - Ubuntu Pro enables extended support for 10 years for long term support Ubuntu series. Xenial is therefore currently also supported under Ubuntu Pro. Xenial's software-properties-gtk, however, doesn't have the Ubuntu Pro functionality that exists in Bionic, Focal etc. Thus this request to backport the Ubuntu Pro functionality to Xenial. This depends on LP:2029089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2029473/+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 2052137] Re: bonded link goes down on reconfigure
** Changed in: systemd Status: New => 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/2052137 Title: bonded link goes down on reconfigure Status in systemd: Fix Released Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: systemd-networkd brings down member interfaces of a bond when they get reconfigured Jan 31 15:43:46 unique-slug systemd-networkd[2430]: pn1: Bringing link down This has a result that a server has complete downtime for a few seconds, this has also been reported upstream https://github.com/systemd/systemd/issues/31165. A pull request has been opened to fix this https://github.com/systemd/systemd/pull/31172 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/2052137/+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 2052307] Re: ALSA error: snd_pcm_open failed: Operation not supported.
Additional error messages from starting audaciuos with radio stream. cliff@Desktopps:~$ audacious http://stream.srg-ssr.ch/rsc_fr/mp3_128.m3u Gdk-Message: 09:09:07.328: Unable to load col-resize from the cursor theme Gdk-Message: 09:09:07.328: Unable to load col-resize from the cursor theme Gdk-Message: 09:09:07.328: Unable to load col-resize from the cursor theme Gdk-Message: 09:09:07.328: Unable to load col-resize from the cursor theme Gdk-Message: 09:09:07.328: Unable to load col-resize from the cursor theme ERROR ../src/libaudgui/util.cc:328 [audgui_simple_message]: ALSA error: snd_pcm_open failed: Operation not supported. -- 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/2052307 Title: ALSA error: snd_pcm_open failed: Operation not supported. Status in alsa-driver package in Ubuntu: New Bug description: Getting the following error trying to play a radio stream in Audacious. ERROR ../src/libaudgui/util.cc:328 [audgui_simple_message]: ALSA error: snd_pcm_open failed: Operation not supported. This occurred after the daily update on 2/2/24. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:cliff 2336 F pipewire /dev/snd/controlC0: cliff 2341 F wireplumber /dev/snd/controlC1: cliff 2341 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 2 08:53:34 2024 InstallationDate: Installed on 2023-12-02 (62 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2052307/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
I've been seeing this bug as far back as losetup is used (jammy) and the previously merged fix has a significant improvement on successful builds (0/3 succeeded without the patch applied vs 5/5 succeeded with the patch applied this week) in jammy. Is someone already looking to SRU that patch back to mantic and jammy or should I work on it? Even if it's not perfectly, I think it would be extremely benefitial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: New Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2051990] Re: python3-defaults 3.12 causes aubio to fail to build from source
** Changed in: aubio (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051990
Title:
python3-defaults 3.12 causes aubio to fail to build from source
Status in aubio package in Ubuntu:
Fix Released
Status in python3-defaults package in Ubuntu:
Invalid
Status in aubio package in Debian:
Fix Released
Bug description:
python3 ./waf configure --verbose --destdir=debian/tmp --prefix=/usr
--enable-fftw3f --libdir=/usr/lib/x86_64-linux-gnu
/<>/waflib/Utils.py:443: SyntaxWarning: invalid escape sequence
'\d'
return re.split('\d+$',s)[0]
/<>/waflib/ConfigSet.py:7: SyntaxWarning: invalid escape
sequence '\ '
re_imp=re.compile('^(#)*?([^#=]*?)\ =\ (.*?)$',re.M)
/<>/waflib/ansiterm.py:178: SyntaxWarning: invalid escape
sequence '\['
ansi_tokens=re.compile('(?:\x1b\[([0-9?;]*)([a-zA-Z])|([^\x1b]+))')
Traceback (most recent call last):
File "/<>/./waf", line 164, in
from waflib import Scripting
File "/<>/waflib/Scripting.py", line 7, in
from waflib import
Utils,Configure,Logs,Options,ConfigSet,Context,Errors,Build,Node
File "/<>/waflib/Configure.py", line 6, in
from waflib import ConfigSet,Utils,Options,Logs,Context,Build,Errors
File "/<>/waflib/Options.py", line 6, in
from waflib import Logs,Utils,Context,Errors
File "/<>/waflib/Context.py", line 5, in
import os,re,imp,sys
ModuleNotFoundError: No module named 'imp'
make[1]: *** [debian/rules:45: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2024-02-01T21:23:22Z
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aubio/+bug/2051990/+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 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
I had the same problem. I followed the instructions of Nathan Vaughn (nathanvme) and it worked for me. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) Hardware info (not sure if relevant): cpu: intel gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 2052794] Re: 2.79.1 test issue on s390x
** Description changed: One of the newly added tests in the 2.79 serie is failing on s390x. The issue is being discussed upstream on https://gitlab.gnome.org/GNOME/glib/-/issues/3252 , the test is new and is currently buggy. Upstream/Debian/Ubuntu already disabled similar tests in 2.79.1 but that one as not noticed to fail because it's skipped - during build. + during build so is only showing now in the installed-tests result and in + autopkgtest. (And the package is in Debian/experimental where it didn't + get tested by the Debian CI) -- 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/2052794 Title: 2.79.1 test issue on s390x Status in GLib: New Status in glib2.0 package in Ubuntu: In Progress Bug description: One of the newly added tests in the 2.79 serie is failing on s390x. The issue is being discussed upstream on https://gitlab.gnome.org/GNOME/glib/-/issues/3252 , the test is new and is currently buggy. Upstream/Debian/Ubuntu already disabled similar tests in 2.79.1 but that one as not noticed to fail because it's skipped during build so is only showing now in the installed- tests result and in autopkgtest. (And the package is in Debian/experimental where it didn't get tested by the Debian CI) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2052794/+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 2052794] Re: 2.79.1 test issue on s390x
We will disable the test but I've asked the release team to ignore the result to let the package migrate to avoid doing another upload to that effect that would load the infra and might create delays in other ongoing transitions -- 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/2052794 Title: 2.79.1 test issue on s390x Status in GLib: New Status in glib2.0 package in Ubuntu: In Progress Bug description: One of the newly added tests in the 2.79 serie is failing on s390x. The issue is being discussed upstream on https://gitlab.gnome.org/GNOME/glib/-/issues/3252 , the test is new and is currently buggy. Upstream/Debian/Ubuntu already disabled similar tests in 2.79.1 but that one as not noticed to fail because it's skipped during build so is only showing now in the installed- tests result and in autopkgtest. (And the package is in Debian/experimental where it didn't get tested by the Debian CI) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2052794/+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 2052794] Re: 2.79.1 test issue on s390x
** 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/2052794 Title: 2.79.1 test issue on s390x Status in GLib: New Status in glib2.0 package in Ubuntu: In Progress Bug description: One of the newly added tests in the 2.79 serie is failing on s390x. The issue is being discussed upstream on https://gitlab.gnome.org/GNOME/glib/-/issues/3252 , the test is new and is currently buggy. Upstream/Debian/Ubuntu already disabled similar tests in 2.79.1 but that one as not noticed to fail because it's skipped during build so is only showing now in the installed- tests result and in autopkgtest. (And the package is in Debian/experimental where it didn't get tested by the Debian CI) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2052794/+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 2052794] [NEW] 2.79.1 test issue on s390x
Public bug reported: One of the newly added tests in the 2.79 serie is failing on s390x. The issue is being discussed upstream on https://gitlab.gnome.org/GNOME/glib/-/issues/3252 , the test is new and is currently buggy. Upstream/Debian/Ubuntu already disabled similar tests in 2.79.1 but that one as not noticed to fail because it's skipped during build so is only showing now in the installed-tests result and in autopkgtest. (And the package is in Debian/experimental where it didn't get tested by the Debian CI) ** Affects: glib Importance: Unknown Status: New ** Affects: glib2.0 (Ubuntu) Importance: High Status: In Progress ** Tags: noble update-excuse ** Tags added: update-excuse ** Tags added: noble ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3252 https://gitlab.gnome.org/GNOME/glib/-/issues/3252 ** Also affects: glib via https://gitlab.gnome.org/GNOME/glib/-/issues/3252 Importance: Unknown Status: Unknown ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => High ** Changed in: glib2.0 (Ubuntu) Status: New => In Progress -- 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/2052794 Title: 2.79.1 test issue on s390x Status in GLib: New Status in glib2.0 package in Ubuntu: In Progress Bug description: One of the newly added tests in the 2.79 serie is failing on s390x. The issue is being discussed upstream on https://gitlab.gnome.org/GNOME/glib/-/issues/3252 , the test is new and is currently buggy. Upstream/Debian/Ubuntu already disabled similar tests in 2.79.1 but that one as not noticed to fail because it's skipped during build so is only showing now in the installed- tests result and in autopkgtest. (And the package is in Debian/experimental where it didn't get tested by the Debian CI) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2052794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Changed in: kalgebra (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: In Progress Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: In Progress Status in konqueror package in Ubuntu: In Progress Status in kontact package in Ubuntu: In Progress Status in marble package in Ubuntu: In Progress Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: In Progress Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051997] Re: bdebstrap fails to build with python3-defaults 3.12
** Changed in: bdebstrap (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051997
Title:
bdebstrap fails to build with python3-defaults 3.12
Status in bdebstrap package in Ubuntu:
Fix Released
Status in python3-defaults package in Ubuntu:
Invalid
Status in bdebstrap package in Debian:
Fix Released
Bug description:
When building bdebstrap with python3-default 3.12 the following error occurs
--
usr/bin/python3.12 -m pylint --rcfile=/<>/tests/pylint.conf --
/<>/bdebstrap tests /<>/setup.py
FAIL
test_flake8 (tests.test_shellcheck.ShellcheckTestCase.test_flake8)
Test: Run shellcheck on Shell source code. ... Running following command:
shellcheck /<>/hooks/disable-units
/<>/hooks/enable-units
ok
==
FAIL: test_pylint (tests.test_pylint.PylintTestCase.test_pylint)
Test: Run pylint on Python source code.
--
Traceback (most recent call last):
File "/<>/tests/test_pylint.py", line 74, in test_pylint
self.fail("\n".join(msgs))
AssertionError: pylint found issues:
* Module setup
/<>/setup.py:26:0: E0401: Unable to import 'distutils.log'
(import-error)
/<>/setup.py:27:0: E0401: Unable to import
'distutils.command.build' (import-error)
/<>/setup.py:28:0: E0401: Unable to import
'distutils.command.clean' (import-error)
/<>/setup.py:57:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:54:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
/<>/setup.py:65:4: C0116: Missing function or method docstring
(missing-function-docstring)
/<>/setup.py:62:0: R0903: Too few public methods (1/2)
(too-few-public-methods)
--
due to removal of distutils in python 3.12
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/2051997/+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 2051512] Re: apport ftbfs with Python 3.12 as the default
After further investigations into the gzip issue in python 3.12, it
turns out there was an undocumented change: it is now a buffered writer.
So the fire pattern used in the snippet above doesn't work
anymore, we now need to use it as a proper IO object instead.
I still think this should be reported upstream because of the
documentation issue, but I'll work on changing the apport code to Do The
Right Thing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051512
Title:
apport ftbfs with Python 3.12 as the default
Status in apport package in Ubuntu:
Confirmed
Status in python3-defaults package in Ubuntu:
New
Status in python3.12 package in Ubuntu:
New
Status in apport source package in Noble:
Confirmed
Status in python3-defaults source package in Noble:
New
Status in python3.12 source package in Noble:
New
Bug description:
[Description]
Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
(maybe all?)
[Test Plan]
Run the following script:
import gzip
import io
out = io.BytesIO()
gzip.GzipFile("foo", mode="wb", fileobj=out, mtime=0).write(b"FooFoo")
# print(out.getvalue())
print(gzip.decompress(out.getvalue()))
Expected output (as on Python 3.11):
FooFoo
Buggy output (tail end of the stack trace):
EOFError: Compressed file ended before the end-of-stream marker was reached
[Original report]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tests/run-linters --errors-only
Skipping mypy tests, mypy is not installed
Running pylint...
* Module apport-retrace
bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment
(used-before-assignment)
make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2051512/+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 2051512] Re: apport ftbfs with Python 3.12 as the default
** Also affects: python3.12 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
-debian/rules override_dh_auto_test
+ [Description]
+
+ Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
+ (maybe all?)
+
+ [Test Plan]
+
+ Run the following script:
+
+ import gzip
+ import io
+ out = io.BytesIO()
+ gzip.GzipFile("foo", mode="wb", fileobj=out, mtime=0).write(b"FooFoo")
+ # print(out.getvalue())
+ print(gzip.decompress(out.getvalue()))
+
+ Expected output (as on Python 3.11):
+ FooFoo
+
+ Buggy output (tail end of the stack trace):
+ EOFError: Compressed file ended before the end-of-stream marker was reached
+
+ [Original report]
+
+ debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tests/run-linters --errors-only
Skipping mypy tests, mypy is not installed
Running pylint...
* Module apport-retrace
bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment
(used-before-assignment)
make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051512
Title:
apport ftbfs with Python 3.12 as the default
Status in apport package in Ubuntu:
Confirmed
Status in python3-defaults package in Ubuntu:
New
Status in python3.12 package in Ubuntu:
New
Status in apport source package in Noble:
Confirmed
Status in python3-defaults source package in Noble:
New
Status in python3.12 source package in Noble:
New
Bug description:
[Description]
Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
(maybe all?)
[Test Plan]
Run the following script:
import gzip
import io
out = io.BytesIO()
gzip.GzipFile("foo", mode="wb", fileobj=out, mtime=0).write(b"FooFoo")
# print(out.getvalue())
print(gzip.decompress(out.getvalue()))
Expected output (as on Python 3.11):
FooFoo
Buggy output (tail end of the stack trace):
EOFError: Compressed file ended before the end-of-stream marker was reached
[Original report]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tests/run-linters --errors-only
Skipping mypy tests, mypy is not installed
Running pylint...
* Module apport-retrace
bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment
(used-before-assignment)
make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2051512/+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
