[Touch-packages] [Bug 2090806] Re: TIMEOUT and NETWORK_TIMEOUT don't work when SSL is involved
** Patch removed: "Debdiff for openldap on focal"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2090806/+attachment/5843023/+files/lp2090806_focal.debdiff
** Changed in: openldap (Ubuntu Focal)
Status: In Progress => Won't Fix
--
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/2090806
Title:
TIMEOUT and NETWORK_TIMEOUT don't work when SSL is involved
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Focal:
Won't Fix
Status in openldap source package in Jammy:
In Progress
Status in openldap source package in Noble:
In Progress
Status in openldap source package in Oracular:
In Progress
Status in openldap source package in Plucky:
Fix Released
Bug description:
[Impact]
If you connect to a slapd server using TLS and for some reason, the connection
hangs or fails to completely establish, TIMEOUT and NETWORK_TIMEOUT values
do not function as they are intended. They get ignored, and the connecting
process e.g. ldapsearch just sits there at 100% CPU waiting forever.
If slapd is set up in High Availability with servers to failover to, the
failover will never occur, due to the connecting processes sitting there at
100% CPU waiting for the connection that will never succeed, leading to
outages.
You can simulate this easily with:
$ ldapsearch -x -H ldaps://example.com
$ sudo kill -STOP
$ ldapsearch -x -H ldaps://example.com
and the last call will hang forever.
There doesn't seem to be any workaround for this, apart from not using
SSL.
[Testcase]
You can get away with just the one VM for this.
Set up the ldap server (from server docs):
https://ubuntu.com/server/docs/install-and-configure-ldap
$ sudo apt install slapd ldap-utils
$ sudo dpkg-reconfigure slapd
Set DNS to example.com
$ ldapsearch -x -LLL -H ldap:/// -b dc=example,dc=com dn
dn: dc=example,dc=com
$ vim add_content.ldif
dn: ou=People,dc=example,dc=com
objectClass: organizationalUnit
ou: People
dn: ou=Groups,dc=example,dc=com
objectClass: organizationalUnit
ou: Groups
dn: cn=miners,ou=Groups,dc=example,dc=com
objectClass: posixGroup
cn: miners
gidNumber: 5000
dn: uid=john,ou=People,dc=example,dc=com
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: shadowAccount
uid: john
sn: Doe
givenName: John
cn: John Doe
displayName: John Doe
uidNumber: 1
gidNumber: 5000
userPassword: {CRYPT}x
gecos: John Doe
loginShell: /bin/bash
homeDirectory: /home/john
$ ldapadd -x -D cn=admin,dc=example,dc=com -W -f add_content.ldif
$ ldapsearch -x -LLL -b dc=example,dc=com '(uid=john)' cn gidNumber
dn: uid=john,ou=People,dc=example,dc=com
cn: John Doe
gidNumber: 5000
$ ldappasswd -x -D cn=admin,dc=example,dc=com -W -S
uid=john,ou=people,dc=example,dc=com
New password:
Re-enter new password:
Enter LDAP Password:
Configure the server for SSL (from server docs):
https://ubuntu.com/server/docs/ldap-and-transport-layer-security-tls
$ sudo apt install gnutls-bin ssl-cert
$ sudo certtool --generate-privkey --bits 4096 --outfile
/etc/ssl/private/mycakey.pem
$ sudo vim /etc/ssl/ca.info
cn = Example Company
ca
cert_signing_key
expiration_days = 3650
$ sudo certtool --generate-self-signed \
--load-privkey /etc/ssl/private/mycakey.pem \
--template /etc/ssl/ca.info \
--outfile /usr/local/share/ca-certificates/mycacert.crt
$ sudo update-ca-certificates
$ sudo certtool --generate-privkey \
--bits 2048 \
--outfile /etc/ldap/ldap01_slapd_key.pem
$ sudo vim /etc/ssl/ldap01.info
organization = Example Company
cn = example.com
tls_www_server
encryption_key
signing_key
expiration_days = 365
$ sudo certtool --generate-certificate \
--load-privkey /etc/ldap/ldap01_slapd_key.pem \
--load-ca-certificate /etc/ssl/certs/mycacert.pem \
--load-ca-privkey /etc/ssl/private/mycakey.pem \
--template /etc/ssl/ldap01.info \
--outfile /etc/ldap/ldap01_slapd_cert.pem
$ sudo chgrp openldap /etc/ldap/ldap01_slapd_key.pem
$ sudo chmod 0640 /etc/ldap/ldap01_slapd_key.pem
$ sudo vim certinfo.ldif
dn: cn=config
add: olcTLSCACertificateFile
olcTLSCACertificateFile: /etc/ssl/certs/mycacert.pem
-
add: olcTLSCertificateFile
olcTLSCertificateFile: /etc/ldap/ldap01_slapd_cert.pem
-
add: olcTLSCertificateKeyFile
olcTLSCertificateKeyFile: /etc/ldap/ldap01_slapd_key.pem
$ sudo ldapmodify -Y EXTERNAL -H ldapi:/// -f certinfo.ldif
$ sudo vim /etc/default/slapd
Change
LAPD_SERVICES="ldap:/// ldapi:///"
to
SLAPD_SERVICES="ldap:/// ldapi:/// ldaps:///"
Next add TIMEOUT and NETWORK_TIMEOUT to the config file.
$ sudo vim /etc/ldap/ldap.conf
NETWORK_TIMEOUT 30
TIMEOUT 30
$ sudo systemctl restart slapd
Reproduce the problem:
$ ldapsearch -x -H ldaps://example.com
# extended LDIF
[Touch-packages] [Bug 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()
I'm thinking that maybe in the new workflow described in bug 2087535 we should incorporate a check for a viable GUI environment. ** Changed in: apport (Ubuntu) Status: Incomplete => Triaged -- 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/2006981 Title: apport-gtk crashed with signal 5 in g_log_writer_default() Status in apport package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I can´t provide any other information other than what was collected. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.24.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:9017369:2023-02-10 20:09:56.662793636 -0300:2023-02-10 20:09:57.662793636 -0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash 640:1000:124:1463707:2023-02-10 20:09:58.698746919 -0300:2023-02-10 20:09:59.698746919 -0300:/var/crash/_usr_bin_kwin_x11.1000.crash 640:1000:124:633811:2023-02-10 20:09:59.986718177 -0300:2023-02-10 20:10:00.986718177 -0300:/var/crash/_usr_bin_xembedsniproxy.1000.crash 640:1000:124:653094:2023-02-10 20:10:01.258690357 -0300:2023-02-10 20:10:02.258690357 -0300:/var/crash/_usr_bin_gmenudbusmenuproxy.1000.crash 640:1000:124:990:2023-02-10 20:10:05.770595073 -0300:2023-02-10 20:10:06.770595073 -0300:/var/crash/_usr_share_apport_apport-gtk.1000.crash CurrentDesktop: KDE Date: Fri Feb 10 20:10:04 2023 ExecutablePath: /usr/share/apport/apport-gtk InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A Signal: 5 SourcePackage: apport StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2006981/+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 2091228] Re: apport-gtk crashed with SIGTRAP in g_log_writer_default()
*** This bug is a duplicate of bug 2006981 ***
https://bugs.launchpad.net/bugs/2006981
** This bug has been marked a duplicate of bug 2006981
apport-gtk crashed with signal 5 in g_log_writer_default()
--
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/2091228
Title:
apport-gtk crashed with SIGTRAP in g_log_writer_default()
Status in apport package in Ubuntu:
Confirmed
Bug description:
Unknown error after installing Unity 25.04 Daily Build.
ProblemType: Crash
DistroRelease: Ubuntu 25.04
Package: apport-gtk 2.30.0-0ubuntu5
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CrashReports:
664:0:111:0:2024-12-07 22:47:15.566220174 -0600:2024-12-07
22:47:15.566220174 -0600:/var/crash/_usr_bin_add-apt-repository.0.upload
640:0:111:9374885:2024-12-07 21:12:48.279499292 -0600:2024-12-07
21:12:49.279499292 -0600:/var/crash/_usr_share_apport_apport-gtk.0.crash
640:0:111:30796:2024-12-07 22:47:11.070472717 -0600:2024-12-07
22:47:15.758316193 -0600:/var/crash/_usr_bin_add-apt-repository.0.crash
600:107:111:37:2024-12-07 22:47:16.893883811 -0600:2024-12-07
22:47:16.893883811 -0600:/var/crash/_usr_bin_add-apt-repository.0.uploaded
Date: Sat Dec 7 21:12:40 2024
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2024-12-08 (0 days ago)
InstallationMedia: Ubuntu-Unity 25.04 "Plucky Puffin" - Daily amd64 (20241206)
InterpreterPath: /usr/bin/python3.12
JournalErrors:
Dec 07 21:12:40 hostname pkexec[7961]: _gtk_css_lookup_resolve: assertion
'(((__extension__ ({ GTypeInstance *__inst = (GTypeInstance*) ((provider));
GType __t = ((_gtk_style_provider_private_get_type ())); gboolean __r; if
(!__inst) __r = (0); else if (__inst->g_class && __inst->g_class->g_type ==
__t) __r = (!(0)); else __r = g_type_check_instance_is_a (__inst, __t); __r;
}' failed
Dec 07 21:12:40 hostname pkexec[7961]: Can't create a GtkStyleContext
without a display connection
Dec 07 21:12:43 hostname kernel: block sda: the capability attribute has
been deprecated.
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
Python3Details: /usr/bin/python3.12, Python 3.12.7, python3-minimal,
3.12.6-0ubuntu1
PythonDetails: N/A
Signal: 5
SignalName: SIGTRAP
SourcePackage: apport
StacktraceTop:
g_log_writer_default () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_structured_array () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_structured_standard () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0
g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: apport-gtk crashed with SIGTRAP in g_log_writer_default()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2091228/+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 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()
Huh, I realize I didn't actually write my conclusions beforehand: This seems to happen on crashes of the desktop environment itself, e.g. gnome-shell. While it'd be nice for GTK to bubble up a proper exception for us to catch, we probably can do better than that. Easy reproducer: WAYLAND_DISPLAY=bogus DISPLAY=:42 /usr/share/apport/apport-gtk -- 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/2006981 Title: apport-gtk crashed with signal 5 in g_log_writer_default() Status in apport package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I can´t provide any other information other than what was collected. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.24.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:9017369:2023-02-10 20:09:56.662793636 -0300:2023-02-10 20:09:57.662793636 -0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash 640:1000:124:1463707:2023-02-10 20:09:58.698746919 -0300:2023-02-10 20:09:59.698746919 -0300:/var/crash/_usr_bin_kwin_x11.1000.crash 640:1000:124:633811:2023-02-10 20:09:59.986718177 -0300:2023-02-10 20:10:00.986718177 -0300:/var/crash/_usr_bin_xembedsniproxy.1000.crash 640:1000:124:653094:2023-02-10 20:10:01.258690357 -0300:2023-02-10 20:10:02.258690357 -0300:/var/crash/_usr_bin_gmenudbusmenuproxy.1000.crash 640:1000:124:990:2023-02-10 20:10:05.770595073 -0300:2023-02-10 20:10:06.770595073 -0300:/var/crash/_usr_share_apport_apport-gtk.1000.crash CurrentDesktop: KDE Date: Fri Feb 10 20:10:04 2023 ExecutablePath: /usr/share/apport/apport-gtk InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A Signal: 5 SourcePackage: apport StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2006981/+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 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()
And after a bit of investigation, the following snippet seems to detect that we don't have a valid backend: ``` if Gdk.Display.get_default() is None: exit(-1) ``` ** Changed in: apport (Ubuntu) Status: Triaged => Confirmed ** Tags added: rls-pp-incoming -- 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/2006981 Title: apport-gtk crashed with signal 5 in g_log_writer_default() Status in apport package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I can´t provide any other information other than what was collected. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.24.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:9017369:2023-02-10 20:09:56.662793636 -0300:2023-02-10 20:09:57.662793636 -0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash 640:1000:124:1463707:2023-02-10 20:09:58.698746919 -0300:2023-02-10 20:09:59.698746919 -0300:/var/crash/_usr_bin_kwin_x11.1000.crash 640:1000:124:633811:2023-02-10 20:09:59.986718177 -0300:2023-02-10 20:10:00.986718177 -0300:/var/crash/_usr_bin_xembedsniproxy.1000.crash 640:1000:124:653094:2023-02-10 20:10:01.258690357 -0300:2023-02-10 20:10:02.258690357 -0300:/var/crash/_usr_bin_gmenudbusmenuproxy.1000.crash 640:1000:124:990:2023-02-10 20:10:05.770595073 -0300:2023-02-10 20:10:06.770595073 -0300:/var/crash/_usr_share_apport_apport-gtk.1000.crash CurrentDesktop: KDE Date: Fri Feb 10 20:10:04 2023 ExecutablePath: /usr/share/apport/apport-gtk InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A Signal: 5 SourcePackage: apport StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2006981/+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 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()
Marking this for further discussion and schedule a proper fix (i.e. someone needs to write up the fix and appropriate tests, and try it by forcing gnome-shell to commit suicide rather than in my completely artificial reproducer) -- 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/2006981 Title: apport-gtk crashed with signal 5 in g_log_writer_default() Status in apport package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I can´t provide any other information other than what was collected. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.24.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:9017369:2023-02-10 20:09:56.662793636 -0300:2023-02-10 20:09:57.662793636 -0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash 640:1000:124:1463707:2023-02-10 20:09:58.698746919 -0300:2023-02-10 20:09:59.698746919 -0300:/var/crash/_usr_bin_kwin_x11.1000.crash 640:1000:124:633811:2023-02-10 20:09:59.986718177 -0300:2023-02-10 20:10:00.986718177 -0300:/var/crash/_usr_bin_xembedsniproxy.1000.crash 640:1000:124:653094:2023-02-10 20:10:01.258690357 -0300:2023-02-10 20:10:02.258690357 -0300:/var/crash/_usr_bin_gmenudbusmenuproxy.1000.crash 640:1000:124:990:2023-02-10 20:10:05.770595073 -0300:2023-02-10 20:10:06.770595073 -0300:/var/crash/_usr_share_apport_apport-gtk.1000.crash CurrentDesktop: KDE Date: Fri Feb 10 20:10:04 2023 ExecutablePath: /usr/share/apport/apport-gtk InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A Signal: 5 SourcePackage: apport StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2006981/+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 2087820] Re: BlueZ release 5.79
** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/2087820 Title: BlueZ release 5.79 Status in bluez package in Ubuntu: Fix Released Bug description: Release to Plucky: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.79.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2087820/+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 2093402] Re: The calculator in 24.04.1 does not work in the Financial settings.
Issue seems to have been resolved. May have come in as one of the updates sent out recently. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/2093402 Title: The calculator in 24.04.1 does not work in the Financial settings. Status in libnotify package in Ubuntu: New Bug description: The calculator in 24.04.1 does not work in the Financial settings mode. I tried updating, reopening and restarting the computer, even purged the gnome-calculator but the bug still exists. but it still doesn't work. I guess this is a regression. It was working earlier must have been one of the recent updates that causes this issue. Ideally /normally it should the value even without pressing the '=' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/2093402/+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 2081762] Re: [SRU] lxc-excecute NULL pointer dereference causes segfault when sharing rootfs with host
** Changed in: lxc (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2081762 Title: [SRU] lxc-excecute NULL pointer dereference causes segfault when sharing rootfs with host Status in lxc: Fix Released Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Noble: Fix Released Status in lxc source package in Oracular: Fix Released Status in lxc source package in Plucky: Fix Released Status in lxc package in Debian: Fix Released Bug description: [ Impact ] lxc-execute will crash with a segfault if the user tries to use the host rootfs as a shared rootfs. $ sudo lxc-execute -n lxc-test-1 -f lxc.conf -l TRACE -- ls /usr Segmentation fault [ Test Plan ] install lxc $ cat > lxc.confstorage->type causes a segfault. Steps to reproduce: 1. use lxc.conf: lxc.uts.name=lxc-test-1 lxc.net.0.type = empty lxc.console.path = none lxc.tty.max = 1 lxc.pty.max = 128 lxc.mount.auto = proc:rw sys cgroup lxc.autodev = 1 2. Run: $ sudo lxc-execute -n lxc-test-1 -f lxc.conf -l TRACE -- ls /dev Segmentation fault I've attached a patch as a possible fix. Running the same example above with the patch applied runs without crashing. To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/2081762/+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 2091228] Re: apport-gtk crashed with SIGTRAP in g_log_writer_default()
** Tags added: rls-pp-incoming
--
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/2091228
Title:
apport-gtk crashed with SIGTRAP in g_log_writer_default()
Status in apport package in Ubuntu:
Confirmed
Bug description:
Unknown error after installing Unity 25.04 Daily Build.
ProblemType: Crash
DistroRelease: Ubuntu 25.04
Package: apport-gtk 2.30.0-0ubuntu5
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CrashReports:
664:0:111:0:2024-12-07 22:47:15.566220174 -0600:2024-12-07
22:47:15.566220174 -0600:/var/crash/_usr_bin_add-apt-repository.0.upload
640:0:111:9374885:2024-12-07 21:12:48.279499292 -0600:2024-12-07
21:12:49.279499292 -0600:/var/crash/_usr_share_apport_apport-gtk.0.crash
640:0:111:30796:2024-12-07 22:47:11.070472717 -0600:2024-12-07
22:47:15.758316193 -0600:/var/crash/_usr_bin_add-apt-repository.0.crash
600:107:111:37:2024-12-07 22:47:16.893883811 -0600:2024-12-07
22:47:16.893883811 -0600:/var/crash/_usr_bin_add-apt-repository.0.uploaded
Date: Sat Dec 7 21:12:40 2024
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2024-12-08 (0 days ago)
InstallationMedia: Ubuntu-Unity 25.04 "Plucky Puffin" - Daily amd64 (20241206)
InterpreterPath: /usr/bin/python3.12
JournalErrors:
Dec 07 21:12:40 hostname pkexec[7961]: _gtk_css_lookup_resolve: assertion
'(((__extension__ ({ GTypeInstance *__inst = (GTypeInstance*) ((provider));
GType __t = ((_gtk_style_provider_private_get_type ())); gboolean __r; if
(!__inst) __r = (0); else if (__inst->g_class && __inst->g_class->g_type ==
__t) __r = (!(0)); else __r = g_type_check_instance_is_a (__inst, __t); __r;
}' failed
Dec 07 21:12:40 hostname pkexec[7961]: Can't create a GtkStyleContext
without a display connection
Dec 07 21:12:43 hostname kernel: block sda: the capability attribute has
been deprecated.
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
Python3Details: /usr/bin/python3.12, Python 3.12.7, python3-minimal,
3.12.6-0ubuntu1
PythonDetails: N/A
Signal: 5
SignalName: SIGTRAP
SourcePackage: apport
StacktraceTop:
g_log_writer_default () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_structured_array () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_structured_standard () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0
g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: apport-gtk crashed with SIGTRAP in g_log_writer_default()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2091228/+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 2093824] Re: fwupd crashed with SIGTRAP in g_wakeup_new()
The good news is that I can't find this crash in errors.ubuntu.com or any or the relevant bug trackers yet. -- 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/2093824 Title: fwupd crashed with SIGTRAP in g_wakeup_new() Status in glib2.0 package in Ubuntu: Confirmed Bug description: After couple of minutes after starting the computer a dialogue displayed that a system program had crashed. The Chrome browser, Ubuntu desktop appeared unaffected and continued to operate normally. ProblemType: Crash DistroRelease: Ubuntu 25.04 Package: fwupd 2.0.3-3 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.31.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jan 11 20:42:34 2025 ExecutablePath: /usr/libexec/fwupd/fwupd InstallationDate: Installed on 2025-01-11 (1 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250111) JournalErrors: Jan 11 20:42:40 hostname systemd[1]: fwupd.service: Main process exited, code=dumped, status=5/TRAP Jan 11 20:42:40 hostname systemd[1]: fwupd.service: Failed with result 'core-dump'. Jan 11 20:42:40 hostname systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Jan 11 20:42:40 hostname systemd[1]: Failed to start fwupd-refresh.service - Refresh fwupd metadata and update motd. ProcCmdline: /usr/libexec/fwupd/fwupd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 5 SignalName: SIGTRAP SourcePackage: fwupd StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new_with_flags () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: fwupd crashed with SIGTRAP in g_main_context_new_with_flags() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2093824/+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 2093824] Re: fwupd crashed with SIGTRAP in g_wakeup_new()
> Creating pipes for GWakeup: Too many open files We can't see what opens too many files from the crash stacktrace, but most likely not glib2 itself. -- 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/2093824 Title: fwupd crashed with SIGTRAP in g_wakeup_new() Status in glib2.0 package in Ubuntu: Confirmed Bug description: After couple of minutes after starting the computer a dialogue displayed that a system program had crashed. The Chrome browser, Ubuntu desktop appeared unaffected and continued to operate normally. ProblemType: Crash DistroRelease: Ubuntu 25.04 Package: fwupd 2.0.3-3 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.31.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jan 11 20:42:34 2025 ExecutablePath: /usr/libexec/fwupd/fwupd InstallationDate: Installed on 2025-01-11 (1 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250111) JournalErrors: Jan 11 20:42:40 hostname systemd[1]: fwupd.service: Main process exited, code=dumped, status=5/TRAP Jan 11 20:42:40 hostname systemd[1]: fwupd.service: Failed with result 'core-dump'. Jan 11 20:42:40 hostname systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Jan 11 20:42:40 hostname systemd[1]: Failed to start fwupd-refresh.service - Refresh fwupd metadata and update motd. ProcCmdline: /usr/libexec/fwupd/fwupd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 5 SignalName: SIGTRAP SourcePackage: fwupd StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new_with_flags () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: fwupd crashed with SIGTRAP in g_main_context_new_with_flags() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2093824/+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 2096615] Re: iptables: merge 1.8.11-2 from unstable
** Merge proposal linked: https://code.launchpad.net/~adrien/ubuntu/+source/iptables/+git/iptables/+merge/480036 -- 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/2096615 Title: iptables: merge 1.8.11-2 from unstable Status in iptables package in Ubuntu: In Progress Bug description: There is a new version in Debian (1.8.11-2) and merging it fixes tests failures for the new libnftnl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2096615/+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 2096615] [NEW] iptables: merge 1.8.11-2 from unstable
Public bug reported: There is a new version in Debian (1.8.11-2) and merging it fixes tests failures for the new libnftnl. ** Affects: iptables (Ubuntu) Importance: High Assignee: Adrien Nader (adrien) Status: In Progress ** Tags: update-excuse -- 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/2096615 Title: iptables: merge 1.8.11-2 from unstable Status in iptables package in Ubuntu: In Progress Bug description: There is a new version in Debian (1.8.11-2) and merging it fixes tests failures for the new libnftnl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2096615/+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 1957024] Re: pam-mkhomedir does not honor private home directories
This bug was fixed in the package pam - 1.4.0-11ubuntu2.5 --- pam (1.4.0-11ubuntu2.5) jammy; urgency=medium * Honor private home directory permissions (LP: #1957024) -- Ponnuvel Palaniyappan Sun, 17 Nov 2024 10:17:22 + ** Changed in: pam (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1957024 Title: pam-mkhomedir does not honor private home directories Status in pam package in Ubuntu: Fix Released Status in pam source package in Focal: In Progress Status in pam source package in Jammy: Fix Released Status in pam source package in Noble: Fix Released Status in pam source package in Oracular: Fix Released Status in pam source package in Plucky: Fix Released Bug description: [Impact] A common situation is to have a central set of users (e.g. in LDAP) and use pam_mkhomedir.so to create the home directory when the user first logs in. These changes do not cover this situation. The default configuration of pam_mkhomedir.so will result in a home directory created with 0755 permissions. To make pam_mkhomedir.so create a home directory by default with permissions consistent with the other tools then a umask argument can be added to the pam_mkhomedir.so module in the file /usr/share/pam- configs/mkhomedir. I believe this would have to be done before enabling the module. The file is part of the libpam-modules package. [Test plan] 1. Test with current defaults and confirm the permission is 0755 for home directory. # enable pam_mkhomedir.so configuration pam-auth-update --enable mkhomedir # create a user with adduser that creates the home directory adduser --disabled-password --gecos adduser homemadebyadduser # create a user with useradd that creates the home directory useradd --create-home homemadebyuseradd # create a user with useradd that does *not* create the home directory so that pam_mkhomedir.so can create it useradd --no-create-home homemadebymkhomedir # trigger pam_mkhomedir.so to create the home directory su - homemadebymkhomedir -c exit # verify the permissions are 0755 for the one created by pam and 0750 for the one by adduser' root@ubuntu:~# ls -al /home 2. Install the package with the fix # enable mkhomedir again pam-auth-update --enable mkhomedir # create a user with useradd that does *not* create the home directory so that pam_mkhomedir.so can create it useradd --no-create-home homemadebymkhomedirpatch # trigger pam_mkhomedir.so to create the home directory su - homemadebymkhomedirpatch -c exit # verify that the home dir created by pam has 0750 as well [ Where problems could occur ] This could result in inconsistent permissions between existing home directories created by pam (before the fix) and the ones created with this fix. While there's no reason to believe it could result in any actual issues, this can be mitigated by changing the existing home directories to have 0750 for consistency. Anyone in the 'others' group will lose access to the home directories of the rest of the users whose $HOME was created by pam. That behaviour should be treated as unexpected as that's how $HOME adduser will behave. In general, one's not expected to have access to $HOME of others. In the absolute pathological cases, where it's desired to give to $HOME to everyone, the permissions can be adjusted manually and the umask can be changed in the conf file on those systems. But this should be treated as 'workaround' and non-standard behaviour. [other info] This has been at https://discourse.ubuntu.com/t/private-home- directories-for-ubuntu-21-04-onwards/19533/13: And agreed that (1) having $HOME consistent across tools is the right behaviour and (2) 0750 is the desired permission for $HOME. This has been merged into Plucky already: https://git.launchpad.net/ubuntu/+source/pam/commit/?id=c576b5c19abb383ce53dfc10a986d7cf164eaeaf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1957024/+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 2095325] Re: libunwind: FTBFS on arm64 and i386 plus test failures
** Changed in: libunwind (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/2095325 Title: libunwind: FTBFS on arm64 and i386 plus test failures Status in libunwind package in Ubuntu: Confirmed Status in libunwind package in Debian: Fix Released Bug description: libunwind 1.7.2 fails to build from source on arm64 and i386 and introduces bugs in some programs. Version 1.8.1 fixes these issues but hasn't been uploaded in Debian yet. I don't think we need the update so I would simply wait for a change in Debian rather than introduce a delta. Launchpad won't let me point to several Debian bugs it seems so I'll list all the related bugs here (they should be fixed by the same upload anyway): - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082282 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082284 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082659 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091302 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2095325/+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 2095074] Re: [SRU] Upgrade to media driver version 24.3.4 in Noble
** Description changed: [ Description ] Intel has requested us to update the media driver (free and non-free) to 24.3.4 due to the need to have Lunar Lake (LNL) and Battle Mage (BMG) support. This request has a strong dependency on an intel-gmmlib version bump to 22.5.2 and a libva version bump to 2.22.0. [ Impact ] - * Users with Lunar Lake or Battlemage currently do not have an LTS support option, which is not a good option for some users, as seen here: + * Users with Lunar Lake or Battlemage currently do not have an LTS support option, which is not a good option for some users, as seen here: https://github.com/canonical/intel-graphics-preview/issues/8 - * Users with Lunar Lake or Battlemage hardware will not have hardware- + * Users with Lunar Lake or Battlemage hardware will not have hardware- enabled media support, which can effect the power consumption and CPU utilization of the machine during encode/decode/transcode operations, video calls, streaming, etc. [ Test Plan ] # On a Lunar Lake or Battlemage machine # Required at this time to get baseline enablement sudo add-apt-repository ppa:kobuk-team/intel-graphics-testing sudo apt update # Get the original versions back sudo apt install -y intel-media-va-driver-non-free=24.1.0+ds1-1 libva2=2.20.0-2build1 libigdgmm12=22.3.17+ds1-1 vainfo=2.12.0+ds1-1 libva-drm2=2.20.0-2build1 libva-wayland2=2.20.0-2build1 libva-x11-2=2.20.0-2build1 # This should result in an error sudo vainfo sudo add-apt-repository -y ppa:mckeesh/testing && sudo apt -y update # Only upgrade the media packages sudo apt install -y intel-media-va-driver-non-free=24.3.4+ds1-0ubuntu1 libva2=2.22.0-1ubuntu1 libigdgmm12=22.5.2-0ubuntu1 libva-drm2=2.22.0-1ubuntu1 libva-wayland2=2.22.0-1ubuntu1 libva-x11-2=2.22.0-1ubuntu1 vainfo=2.12.0+ds1-1 # This should no longer result in an error sudo vainfo [ Where problems could occur ] - * This is a sizable change, and while significant testing goes into + * This is a sizable change, and while significant testing goes into making sure the media stack does not regress, it's always a risk. Ubuntu has a large user base with many, many corner cases, and media stack bumps can always accidentally regress a less popular codec on an older platform. However, we can address any smaller regressions that might arise when the benefit is enablement of LNL and BMG. + * Beyond Intel's extensive in-house testing, we have done our own + testing via FFMPEG to check for AV1, VP9, and H264 hardware acceleration + for encode and decode at 1080p and 4K. In addition to Lunar Lake and + Battlemage, we have also tested Alder Lake, Comet Lake, and Gemini Lake + and found no regressions across these platforms + [ Other Info ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/2095074 Title: [SRU] Upgrade to media driver version 24.3.4 in Noble Status in intel-gmmlib package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: Fix Released Status in intel-media-driver-non-free package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in intel-gmmlib source package in Noble: New Status in intel-media-driver source package in Noble: New Status in intel-media-driver-non-free source package in Noble: New Status in libva source package in Noble: New Bug description: [ Description ] Intel has requested us to update the media driver (free and non-free) to 24.3.4 due to the need to have Lunar Lake (LNL) and Battle Mage (BMG) support. This request has a strong dependency on an intel-gmmlib version bump to 22.5.2 and a libva version bump to 2.22.0. [ Impact ] * Users with Lunar Lake or Battlemage currently do not have an LTS support option, which is not a good option for some users, as seen here: https://github.com/canonical/intel-graphics-preview/issues/8 * Users with Lunar Lake or Battlemage hardware will not have hardware-enabled media support, which can effect the power consumption and CPU utilization of the machine during encode/decode/transcode operations, video calls, streaming, etc. [ Test Plan ] # On a Lunar Lake or Battlemage machine # Required at this time to get baseline enablement sudo add-apt-repository ppa:kobuk-team/intel-graphics-testing sudo apt update # Get the original versions back sudo apt install -y intel-media-va-driver-non-free=24.1.0+ds1-1 libva2=2.20.0-2build1 libigdgmm12=22.3.17+ds1-1 vainfo=2.12.0+ds1-1 libva-drm2=2.20.0-2build1 libva-wayland2=2.20.0-2build1 libva-x11-2=2.20.0-2build1 # This should result in an error sudo vainfo sudo add-apt-repository -y ppa:mckeesh/testing && sudo apt -y update # Only upgrade the media packages sudo apt install -y intel-media-va-driver-non-free=24.3.4+ds1-0ubun
[Touch-packages] [Bug 1957024] Update Released
The verification of the Stable Release Update for pam has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1957024 Title: pam-mkhomedir does not honor private home directories Status in pam package in Ubuntu: Fix Released Status in pam source package in Focal: In Progress Status in pam source package in Jammy: Fix Released Status in pam source package in Noble: Fix Released Status in pam source package in Oracular: Fix Released Status in pam source package in Plucky: Fix Released Bug description: [Impact] A common situation is to have a central set of users (e.g. in LDAP) and use pam_mkhomedir.so to create the home directory when the user first logs in. These changes do not cover this situation. The default configuration of pam_mkhomedir.so will result in a home directory created with 0755 permissions. To make pam_mkhomedir.so create a home directory by default with permissions consistent with the other tools then a umask argument can be added to the pam_mkhomedir.so module in the file /usr/share/pam- configs/mkhomedir. I believe this would have to be done before enabling the module. The file is part of the libpam-modules package. [Test plan] 1. Test with current defaults and confirm the permission is 0755 for home directory. # enable pam_mkhomedir.so configuration pam-auth-update --enable mkhomedir # create a user with adduser that creates the home directory adduser --disabled-password --gecos adduser homemadebyadduser # create a user with useradd that creates the home directory useradd --create-home homemadebyuseradd # create a user with useradd that does *not* create the home directory so that pam_mkhomedir.so can create it useradd --no-create-home homemadebymkhomedir # trigger pam_mkhomedir.so to create the home directory su - homemadebymkhomedir -c exit # verify the permissions are 0755 for the one created by pam and 0750 for the one by adduser' root@ubuntu:~# ls -al /home 2. Install the package with the fix # enable mkhomedir again pam-auth-update --enable mkhomedir # create a user with useradd that does *not* create the home directory so that pam_mkhomedir.so can create it useradd --no-create-home homemadebymkhomedirpatch # trigger pam_mkhomedir.so to create the home directory su - homemadebymkhomedirpatch -c exit # verify that the home dir created by pam has 0750 as well [ Where problems could occur ] This could result in inconsistent permissions between existing home directories created by pam (before the fix) and the ones created with this fix. While there's no reason to believe it could result in any actual issues, this can be mitigated by changing the existing home directories to have 0750 for consistency. Anyone in the 'others' group will lose access to the home directories of the rest of the users whose $HOME was created by pam. That behaviour should be treated as unexpected as that's how $HOME adduser will behave. In general, one's not expected to have access to $HOME of others. In the absolute pathological cases, where it's desired to give to $HOME to everyone, the permissions can be adjusted manually and the umask can be changed in the conf file on those systems. But this should be treated as 'workaround' and non-standard behaviour. [other info] This has been at https://discourse.ubuntu.com/t/private-home- directories-for-ubuntu-21-04-onwards/19533/13: And agreed that (1) having $HOME consistent across tools is the right behaviour and (2) 0750 is the desired permission for $HOME. This has been merged into Plucky already: https://git.launchpad.net/ubuntu/+source/pam/commit/?id=c576b5c19abb383ce53dfc10a986d7cf164eaeaf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1957024/+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 1957024] Re: pam-mkhomedir does not honor private home directories
** Changed in: pam (Ubuntu Focal) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1957024 Title: pam-mkhomedir does not honor private home directories Status in pam package in Ubuntu: Fix Released Status in pam source package in Focal: Won't Fix Status in pam source package in Jammy: Fix Released Status in pam source package in Noble: Fix Released Status in pam source package in Oracular: Fix Released Status in pam source package in Plucky: Fix Released Bug description: [Impact] A common situation is to have a central set of users (e.g. in LDAP) and use pam_mkhomedir.so to create the home directory when the user first logs in. These changes do not cover this situation. The default configuration of pam_mkhomedir.so will result in a home directory created with 0755 permissions. To make pam_mkhomedir.so create a home directory by default with permissions consistent with the other tools then a umask argument can be added to the pam_mkhomedir.so module in the file /usr/share/pam- configs/mkhomedir. I believe this would have to be done before enabling the module. The file is part of the libpam-modules package. [Test plan] 1. Test with current defaults and confirm the permission is 0755 for home directory. # enable pam_mkhomedir.so configuration pam-auth-update --enable mkhomedir # create a user with adduser that creates the home directory adduser --disabled-password --gecos adduser homemadebyadduser # create a user with useradd that creates the home directory useradd --create-home homemadebyuseradd # create a user with useradd that does *not* create the home directory so that pam_mkhomedir.so can create it useradd --no-create-home homemadebymkhomedir # trigger pam_mkhomedir.so to create the home directory su - homemadebymkhomedir -c exit # verify the permissions are 0755 for the one created by pam and 0750 for the one by adduser' root@ubuntu:~# ls -al /home 2. Install the package with the fix # enable mkhomedir again pam-auth-update --enable mkhomedir # create a user with useradd that does *not* create the home directory so that pam_mkhomedir.so can create it useradd --no-create-home homemadebymkhomedirpatch # trigger pam_mkhomedir.so to create the home directory su - homemadebymkhomedirpatch -c exit # verify that the home dir created by pam has 0750 as well [ Where problems could occur ] This could result in inconsistent permissions between existing home directories created by pam (before the fix) and the ones created with this fix. While there's no reason to believe it could result in any actual issues, this can be mitigated by changing the existing home directories to have 0750 for consistency. Anyone in the 'others' group will lose access to the home directories of the rest of the users whose $HOME was created by pam. That behaviour should be treated as unexpected as that's how $HOME adduser will behave. In general, one's not expected to have access to $HOME of others. In the absolute pathological cases, where it's desired to give to $HOME to everyone, the permissions can be adjusted manually and the umask can be changed in the conf file on those systems. But this should be treated as 'workaround' and non-standard behaviour. [other info] This has been at https://discourse.ubuntu.com/t/private-home- directories-for-ubuntu-21-04-onwards/19533/13: And agreed that (1) having $HOME consistent across tools is the right behaviour and (2) 0750 is the desired permission for $HOME. This has been merged into Plucky already: https://git.launchpad.net/ubuntu/+source/pam/commit/?id=c576b5c19abb383ce53dfc10a986d7cf164eaeaf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1957024/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
Oh sorry, seems we forgot to verify the bug is resolved. I'll try to get this done soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: Fix Committed Status in debootstrap source package in Jammy: Fix Released Status in base-files source package in Mantic: Won't Fix Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mk-sbuild - pbuilder-dist $release create - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2095370] Re: AppArmor early policy load not funcitoning
The bug was caused by a commit [1] in the Ubuntu kernel that would change the kernel features hash based on the status of the userns and io_uring restriction. When the policy cache was generated, userns restriction would be available and the hash under /etc/apparmor/earlypolicy/ would match the set of features with userns enabled, but when systemd executed at boot, the permission was disabled, causing the hash mismatch, so no policy would be loaded. [1] https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?id=8bd4ee319a029669787588e648bce3c28adf4369 -- 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/2095370 Title: AppArmor early policy load not funcitoning Status in apparmor package in Ubuntu: Confirmed Bug description: Profile cache files in /etc/apparmor/earlypolicy/ should be loaded by systemd during early boot to enable full system confinement. Systemd should load the cache and try to enter confinement as documented in https://gitlab.com/apparmor/apparmor/-/wikis/AppArmorInSystemd However this is not happening on noble. The early policy is not being loaded and systemd does not appear to attempt to enter the systemd profile, which should result in the following error if the systemd profile is not part of the early cache set. Failed to change to AppArmor profile 'systemd'. Please ensure that one of the binary profile files in policy cache directory /etc/apparmor/earlypolicy/X contains a profile with that name." systemd on boot does report that it has been built with apparmor support [2.011794] systemd[1]: systemd 257-2ubuntu1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -BTF -XKBCOMMON -UTMP +SYSVINIT +LIBARCHIVE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2095370/+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 2094785] Re: [SRU] New upstream 2.11 release for Wi-Fi 7 support
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2094785 Title: [SRU] New upstream 2.11 release for Wi-Fi 7 support Status in wpa package in Ubuntu: New Bug description: [Impact] To support the Wi-Fi 7 features, we need to upgrade wpa_supplicant to 2.11, the latest upstream stable release. [Test case] The upgrade version should not break legacy Wi-Fi functions, we should test on all Wi-Fi chips as much as possible. [Where problem could occur] This is a new stable release which is required by Wi-Fi 7. The risk is high that we might break existing Wi-Fi solutions. [Additional information] Upstream has released 2.11 on 2024-07-20 [1]. It provides more features which are required by Wi-Fi 7. [1] https://w1.fi/releases.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2094785/+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 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()
** Tags removed: rls-pp-incoming ** Tags added: foundations-todo ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Benjamin Drung (bdrung) -- 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/2006981 Title: apport-gtk crashed with signal 5 in g_log_writer_default() Status in apport package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I can´t provide any other information other than what was collected. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.24.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:9017369:2023-02-10 20:09:56.662793636 -0300:2023-02-10 20:09:57.662793636 -0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash 640:1000:124:1463707:2023-02-10 20:09:58.698746919 -0300:2023-02-10 20:09:59.698746919 -0300:/var/crash/_usr_bin_kwin_x11.1000.crash 640:1000:124:633811:2023-02-10 20:09:59.986718177 -0300:2023-02-10 20:10:00.986718177 -0300:/var/crash/_usr_bin_xembedsniproxy.1000.crash 640:1000:124:653094:2023-02-10 20:10:01.258690357 -0300:2023-02-10 20:10:02.258690357 -0300:/var/crash/_usr_bin_gmenudbusmenuproxy.1000.crash 640:1000:124:990:2023-02-10 20:10:05.770595073 -0300:2023-02-10 20:10:06.770595073 -0300:/var/crash/_usr_share_apport_apport-gtk.1000.crash CurrentDesktop: KDE Date: Fri Feb 10 20:10:04 2023 ExecutablePath: /usr/share/apport/apport-gtk InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A Signal: 5 SourcePackage: apport StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2006981/+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 2095597] Re: apparmor: removal of Python standard libraries in Python 3.13
As noted in the original Debian bug, this issue is tracked upstream at https://gitlab.com/apparmor/apparmor/-/issues/447. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed ** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #447 https://gitlab.com/apparmor/apparmor/-/issues/447 -- 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/2095597 Title: apparmor: removal of Python standard libraries in Python 3.13 Status in apparmor package in Ubuntu: Confirmed Status in apparmor package in Debian: Confirmed Bug description: Imported from Debian bug http://bugs.debian.org/1084647: Source: apparmor Severity: important User: debian-pyt...@lists.debian.org Usertags: pep-594-deprecation-313 Dear maintainer(s), Python 3.13 removes a large amount of so called 'dead battery' libraries from the standard library. As such, code that imports these libraries will no longer work in Python 3.13, which is the targeted version for Trixie. The following removed libraries were found in this package: cgitb: utils/apparmor/fail.py:11 See this link for more details: https://peps.python.org/pep-0594/#deprecated-modules Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2095597/+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 2095597] Re: apparmor: removal of Python standard libraries in Python 3.13
** Changed in: apparmor (Debian) Status: New => Confirmed ** Changed in: apparmor (Debian) Importance: Undecided => Unknown -- 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/2095597 Title: apparmor: removal of Python standard libraries in Python 3.13 Status in apparmor package in Ubuntu: New Status in apparmor package in Debian: Confirmed Bug description: Imported from Debian bug http://bugs.debian.org/1084647: Source: apparmor Severity: important User: debian-pyt...@lists.debian.org Usertags: pep-594-deprecation-313 Dear maintainer(s), Python 3.13 removes a large amount of so called 'dead battery' libraries from the standard library. As such, code that imports these libraries will no longer work in Python 3.13, which is the targeted version for Trixie. The following removed libraries were found in this package: cgitb: utils/apparmor/fail.py:11 See this link for more details: https://peps.python.org/pep-0594/#deprecated-modules Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2095597/+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 2093824] Re: fwupd crashed with SIGTRAP in g_wakeup_new()
As Alessandro pointed out the issue there is a system one where the limit of files open is reached, could be any process leaking files descriptors. Are you running any non standard or resources consuming software? ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Incomplete -- 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/2093824 Title: fwupd crashed with SIGTRAP in g_wakeup_new() Status in glib2.0 package in Ubuntu: Incomplete Bug description: After couple of minutes after starting the computer a dialogue displayed that a system program had crashed. The Chrome browser, Ubuntu desktop appeared unaffected and continued to operate normally. ProblemType: Crash DistroRelease: Ubuntu 25.04 Package: fwupd 2.0.3-3 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.31.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jan 11 20:42:34 2025 ExecutablePath: /usr/libexec/fwupd/fwupd InstallationDate: Installed on 2025-01-11 (1 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250111) JournalErrors: Jan 11 20:42:40 hostname systemd[1]: fwupd.service: Main process exited, code=dumped, status=5/TRAP Jan 11 20:42:40 hostname systemd[1]: fwupd.service: Failed with result 'core-dump'. Jan 11 20:42:40 hostname systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Jan 11 20:42:40 hostname systemd[1]: Failed to start fwupd-refresh.service - Refresh fwupd metadata and update motd. ProcCmdline: /usr/libexec/fwupd/fwupd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 5 SignalName: SIGTRAP SourcePackage: fwupd StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new_with_flags () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: fwupd crashed with SIGTRAP in g_main_context_new_with_flags() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2093824/+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 2059078] Re: proposed-migration for faketime 0.9.10-2.1ubuntu1
faketime migrated, I reverted sssd change, let's see what happens ** Changed in: faketime (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/2059078 Title: proposed-migration for faketime 0.9.10-2.1ubuntu1 Status in bash package in Ubuntu: Fix Released Status in faketime package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Triaged Bug description: faketime 0.9.10-2.1ubuntu1 is stuck in -proposed with build failures on armhf. On armhf, the testsuite confusingly fails with a stack smash error. But this error happens in bash, which isn't even meant to be the process under test. Minimal reproducer: # LD_PRELOAD=./src/libfaketime.so.1 bash -c 'exit 0' *** stack smashing detected ***: terminated Aborted (core dumped) # Confusingly, ltrace shows different results for the newly-built binary than from one built without 64-bit time_t. # LD_PRELOAD=./src/libfaketime.so.1 ltrace --library '*faketime*' bash -c 'exit 0' bash->getrandom(0x1f3bf08, 1, 0x9683b0, 0) = 0xc8202 bash->getrandom(0xc8203, 0xf7fad53c, 1023, 0xf7eef801) = 0xc8202 *** stack smashing detected ***: terminated --- SIGABRT (Aborted) --- +++ killed by SIGABRT +++ # LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/faketime/libfaketime.so.1 ltrace --library '*faketime*' bash -c 'exit 0' bash->gettimeofday(0x8b07a0, 0) = 0 bash->getpid() = 819717 bash->gettimeofday(0xffb88714, 0)= 0 bash->getpid() = 819717 bash->gettimeofday(0xffb8871c, 0)= 0 bash->getpid() = 819717 +++ exited (status 0) +++ # Unsetting -DFAKE_RANDOM in debian/rules does not fix the problem however. So simply loading the LD_PRELOAD library without executing it seems to be enough to break bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2059078/+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 1436211] Re: Remove GTK3 from phone images
** Changed in: evolution-data-server (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1436211 Title: Remove GTK3 from phone images Status in Canonical System Image: In Progress Status in address-book-service package in Ubuntu: Confirmed Status in evolution-data-server package in Ubuntu: In Progress Status in gnome-control-center-signon package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Invalid Status in unity-asset-pool package in Ubuntu: Confirmed Status in evolution-data-server package in Debian: Fix Released Bug description: This is a wishlist bug to eventually remove GTK3 from Ubuntu Phone images to save some space. ===TODO=== -- address-book-service -- address-book-service depends on evolution-data-server, which depends on GTK3. evolution-data-server further depends on libgweather-3-6 and libgcr-ui-3-1 which both directly depend on GTK3 too. Would it be possible to work with libfolks-eds25 and other libraries alone? Or would it be possible to modify evolution-data-server building to not depend on GTK3 since we're not using the toolkit anyway? -- themes (unity-asset-pool, adwaita-icon-theme...) -- humanity-icon-theme, ubuntu-mono and unity-asset-pool depend on adwaita-icon-theme. adwaita-icon-theme directly depends on GTK3. -- ubuntu-system-settings -- ubuntu-system-settings depends on libtimezonemap1 which directly depends on GTK3. Maybe the library could be made not to depend on GTK3? ===DONE=== -- gnome-control-center-signon -- Since libaccount-plugin-1.0-0 is included on Ubuntu Phone images, would it be possible to refactor it so that it would not depend on GTK3 bringing it on the images? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436211/+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 2095597] [NEW] apparmor: removal of Python standard libraries in Python 3.13
Public bug reported: Imported from Debian bug http://bugs.debian.org/1084647: Source: apparmor Severity: important User: debian-pyt...@lists.debian.org Usertags: pep-594-deprecation-313 Dear maintainer(s), Python 3.13 removes a large amount of so called 'dead battery' libraries from the standard library. As such, code that imports these libraries will no longer work in Python 3.13, which is the targeted version for Trixie. The following removed libraries were found in this package: cgitb: utils/apparmor/fail.py:11 See this link for more details: https://peps.python.org/pep-0594/#deprecated-modules Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: apparmor (Debian) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1084647 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084647 ** Changed in: apparmor (Debian) Remote watch: None => Debian Bug tracker #1084647 -- 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/2095597 Title: apparmor: removal of Python standard libraries in Python 3.13 Status in apparmor package in Ubuntu: New Status in apparmor package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1084647: Source: apparmor Severity: important User: debian-pyt...@lists.debian.org Usertags: pep-594-deprecation-313 Dear maintainer(s), Python 3.13 removes a large amount of so called 'dead battery' libraries from the standard library. As such, code that imports these libraries will no longer work in Python 3.13, which is the targeted version for Trixie. The following removed libraries were found in this package: cgitb: utils/apparmor/fail.py:11 See this link for more details: https://peps.python.org/pep-0594/#deprecated-modules Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2095597/+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 2096327] [NEW] Ubuntu-bug crashes with error in apport-gtk
Public bug reported: The tale is slightly convoluted. After doing an "apt upgrade" yesterday, xsane and simple-scan started failing: scanner detected, but could not scan. Trying to report it with ubuntu-bug then crashed with the following error: $ sudo ubuntu-bug simple-scan Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 650, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 917, in run_argv return self.run_report_bug() ^ File "/usr/lib/python3/dist-packages/apport/ui.py", line 740, in run_report_bug self.file_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 1788, in file_report upthread.exc_raise() File "/usr/lib/python3/dist-packages/apport/REThread.py", line 67, in exc_raise raise self._exception[1].with_traceback(self._exception[2]) File "/usr/lib/python3/dist-packages/apport/REThread.py", line 42, in run self._retval = self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 222, in upload ticket = upload_blob(blob_file, progress_callback, hostname=self.get_hostname()) ^^^ File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 1246, in upload_blob assert ticket ^^ AssertionError This is a blocker for me. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2096327 Title: Ubuntu-bug crashes with error in apport-gtk Status in apport package in Ubuntu: New Bug description: The tale is slightly convoluted. After doing an "apt upgrade" yesterday, xsane and simple-scan started failing: scanner detected, but could not scan. Trying to report it with ubuntu-bug then crashed with the following error: $ sudo ubuntu-bug simple-scan Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 650, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 917, in run_argv return self.run_report_bug() ^ File "/usr/lib/python3/dist-packages/apport/ui.py", line 740, in run_report_bug self.file_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 1788, in file_report upthread.exc_raise() File "/usr/lib/python3/dist-packages/apport/REThread.py", line 67, in exc_raise raise self._exception[1].with_traceback(self._exception[2]) File "/usr/lib/python3/dist-packages/apport/REThread.py", line 42, in run self._retval = self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 222, in upload ticket = upload_blob(blob_file, progress_callback, hostname=self.get_hostname()) ^^^ File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 1246, in upload_blob assert ticket ^^ AssertionError This is a blocker for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2096327/+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 2018539] Re: File selector extremely slow
Wow. I have been having this problem for some time as well. I generally noticed it when opening `~/Downloads` from chrome, but file pickers were similarly slow. The suggestion from comment #18 fixed this -immediately-. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2018539 Title: File selector extremely slow Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Bug description: When you try to upload/download a file in an application (e.g. Firefox, Signal, etc) the file selector that opens is extremely slow to appear, search and change directory. Often times, if I try to search for a file in it, I have to wait 10 or more second before the letters I typed appear, and most of the time the last letter I pressed when typing, will appear before the rest of what I wrote, meaning I have to wait for my query to be deleted before I re-type it again. This has only just started since upgrading to Ubuntu 23.04. I noticed that Nautilus has been faster in general since the update, but in the file selector specifically, it's become unusable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:39:48 2023 InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2018539/+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
