Re: [Touch-packages] [Bug 1983794] Please test proposed package
On Fri, 2023-01-27 at 17:06 +, Timo Aaltonen wrote:
> Hello Lindsay, or anyone else affected,
>
> Accepted libcanberra into jammy-proposed. The package will build now
> and
> be available at
> https://launchpad.net/ubuntu/+source/libcanberra/0.30-10ubuntu1.22.04.1
> in a few hours, and then in the -proposed repository.
>
> Please help us by testing this new package.
I'll be happy to test this out, but I'm a bit out to sea on building
from source these days. I couple of issues:
First, I received an email about 4 hours after yours with the
following:
libcanberra (0.30-10ubuntu1 to 0.30-10ubuntu1.22.04.1)
Migration status for libcanberra (0.30-10ubuntu1 to 0.30-
10ubuntu1.22.04.1): BLOCKED: Rejected/violates migration
policy/introduces a regression
Is there an issue here about which I should be concerned? is the .deb
in the -proposed repository, or has it gone back to the shop for minor
repairs?
Second, I downloaded libcanberra_0.30-10ubuntu1.22.04.1.debian.tar.xz,
unpacked it, and apparently times have changed. I've built dozens of
packages using the autogen.sh; configure; make; sudo mail install
routine but although this source has an autogen.sh script, it lacks a
configure.in file and autogen.sh fails.
No need to bring me up to speed in public. A private reply re. the
required build technique will do.
Thanks for your work!!!
--
Lindsay Haisley | "The world is full of monsters with friendly
FMP Computer Services | faces and angels with scars."
512-496-7118 |
http://www.fmp.com| - Heather Brewer
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1983794] Autopkgtest regression report (libcanberra/0.30-10ubuntu1.22.04.1)
All autopkgtests for the newly accepted libcanberra (0.30-10ubuntu1.22.04.1)
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
mutter/42.5-0ubuntu1 (arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#libcanberra
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."
Just a follow up, I'm getting the same issue on Ubuntu 22.10 as well. I reimaged the server from scratch and tried to install the following, which had the same issue: apt -y install db-util db5.3-util krb5-admin-server krb5-config krb5-kdc krb5-kdc-ldap krb5-user ldap-utils libgssrpc4 libkadm5clnt-mit12 libkadm5srv-mit12 libkdb5-10 libltdl7 libodbc2 libsasl2-modules-gssapi- mit libverto-libevent1 libverto1 sasl2-bin schema2ldif slapd None of those should cause a conflict. I did a "dpkg-reconfigure" on all of them, and the only one with an issue is krb5-kdc, and on 22.10 the error is a slightly different line, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145." That's line 145 instead of 142, seems like it's that systemd-invoke line, is there a way for me to get additional debug from that command? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/2003756 Title: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142." Status in init-system-helpers package in Ubuntu: New Bug description: I have a fresh install of Ubuntu Server 22.04.01 LTS. After installing the server and running all updates, I run the following command: apt -y install slapd ldap-utils schema2ldif sasl2-bin libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc This will be installing krb5-kdc 1.19.2-2. This is in preparation for setting up an OpenLDAP server, a Kerberos server with an LDAP backend, and saslauthd for pass-through authentication. krb5-kdc was auto-selected when running the steps in the guide here in my development environment: https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend When installing that, I get the following in the output: Setting up krb5-kdc (1.19.2-2) ... Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service → /lib/systemd/system/krb5-kdc.service. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I do get the prompts for the realm, kdc, and admin server hostnames, and they are reflected in /etc/krb5.conf. If I then run the following: dpkg-reconfigure krb5-kdc I am prompted for whether I want the package to create the Kerberos KDC configuration automatically, and when I say yes, it then repeats the following error: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I cannot find any further debug in the syslog or anything to indicate what the root cause is; the list of packages here are all installed together on a separate development server where I experimented with the configuration I will be deploying here in production so I don't think it's incompatible packages in the install list, but I am open to feedback on that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes
** Description changed: - The libunwind version we ship in kinetic crahes on arm64 platforms with page sizes > 4k. - This was fixed in libunwind upstream. The fix made it into the debian version synced to lunar. + [ Impact ] - Debian bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026217 - Upstream commit: https://github.com/libunwind/libunwind/commit/2d004eafc77f3c6a4bd9a44b1c35735273fd4e97 + * On kernels with page size > 4K xorg (and presumably other applications +relying on libunwind) crashes on startup. This affects anyone +running the official arm64 generic-64k kernel or custom non 4k kernels +(as used by e.g. apple silicon). + + [ Test Plan ] + + * Make sure Xorg works on a variety of different archs and kernels with +different page sizes. + + [ Where problems could occur ] + + * We will have to make sure the fixed version still works with 4k +kernels. The patch is already widely in use so the risk seems low if +we test properly. + + [ Other Info ] + + * The lunar version ships the bug fix synced from debian + + * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026217 + + * Upstream fix: + https://github.com/libunwind/libunwind/commit/e85b65cec757ef589f28957d0c6c21c498a03bdf -- 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/2004039 Title: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes Status in libunwind package in Ubuntu: New Status in libunwind source package in Kinetic: New Bug description: [ Impact ] * On kernels with page size > 4K xorg (and presumably other applications relying on libunwind) crashes on startup. This affects anyone running the official arm64 generic-64k kernel or custom non 4k kernels (as used by e.g. apple silicon). [ Test Plan ] * Make sure Xorg works on a variety of different archs and kernels with different page sizes. [ Where problems could occur ] * We will have to make sure the fixed version still works with 4k kernels. The patch is already widely in use so the risk seems low if we test properly. [ Other Info ] * The lunar version ships the bug fix synced from debian * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026217 * Upstream fix: https://github.com/libunwind/libunwind/commit/e85b65cec757ef589f28957d0c6c21c498a03bdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+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 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes
Attached is a debdiff with the backported fix from lunar ** Patch added: "kinetic-fix" https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+attachment/5643674/+files/libunwind_1.6.2-0ubuntu2.debdiff -- 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/2004039 Title: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes Status in libunwind package in Ubuntu: New Status in libunwind source package in Kinetic: New Bug description: The libunwind version we ship in kinetic crahes on arm64 platforms with page sizes > 4k. This was fixed in libunwind upstream. The fix made it into the debian version synced to lunar. Debian bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026217 Upstream commit: https://github.com/libunwind/libunwind/commit/2d004eafc77f3c6a4bd9a44b1c35735273fd4e97 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+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 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes
** Also affects: libunwind (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: libunwind (Ubuntu Jammy) ** Also affects: libunwind (Ubuntu Kinetic) Importance: Undecided Status: New -- 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/2004039 Title: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes Status in libunwind package in Ubuntu: New Status in libunwind source package in Kinetic: New Bug description: The libunwind version we ship in kinetic crahes on arm64 platforms with page sizes > 4k. This was fixed in libunwind upstream. The fix made it into the debian version synced to lunar. Debian bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026217 Upstream commit: https://github.com/libunwind/libunwind/commit/2d004eafc77f3c6a4bd9a44b1c35735273fd4e97 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+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 2004039] [NEW] libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes
Public bug reported: The libunwind version we ship in kinetic crahes on arm64 platforms with page sizes > 4k. This was fixed in libunwind upstream. The fix made it into the debian version synced to lunar. Debian bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026217 Upstream commit: https://github.com/libunwind/libunwind/commit/2d004eafc77f3c6a4bd9a44b1c35735273fd4e97 ** Affects: libunwind (Ubuntu) Importance: Undecided Status: New -- 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/2004039 Title: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes Status in libunwind package in Ubuntu: New Bug description: The libunwind version we ship in kinetic crahes on arm64 platforms with page sizes > 4k. This was fixed in libunwind upstream. The fix made it into the debian version synced to lunar. Debian bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026217 Upstream commit: https://github.com/libunwind/libunwind/commit/2d004eafc77f3c6a4bd9a44b1c35735273fd4e97 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+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 1983794] Please test proposed package
Hello Lindsay, or anyone else affected,
Accepted libcanberra into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libcanberra/0.30-10ubuntu1.22.04.1
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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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 libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1983794] Re: Evolution not deleting autosave files
Hello Lindsay, or anyone else affected,
Accepted libcanberra into kinetic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libcanberra/0.30-10ubuntu1.22.10.1
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-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. 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.
** Changed in: libcanberra (Ubuntu Kinetic)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-kinetic
** Changed in: libcanberra (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
Hello Hans-Petter, or anyone else affected, Accepted libcanberra into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libcanberra/0.30-10ubuntu1.22.10.1 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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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. ** Changed in: libcanberra (Ubuntu Kinetic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Won't Fix Status in libcanberra package in Ubuntu: Fix Released Status in libcanberra source package in Kinetic: Fix Committed Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4 This seems to be a result of Xwayland crashing and gnome-shell then trying to recover (and failing). Although gnome-shell shouldn't be using GTK, and Wayland sessions shouldn't be dependent on having an X11 server (Xwayland) available. Fixing either of those should resolve this. WORKAROUND: sudo apt remove libcanberra-gtk3-module TEST CASE: 1. Log into a Wayland session. 2. Open a Terminal. 3. $ xrandr # Just to ensure Xwayland starts 4. $ killall Xwayland Expected: gnome-shell still responds. Observed: gnome-shell freezes or exits. --- ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell 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: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 2003845] Re: updating NSS on 18.04
Hello Vijay and thanks for this bug report. The ca-certificates package is periodically upgraded in stable releases. The package changelog [1] will tell you which CAs are added/removed with the past updates. If you still believe you spotted an issue with missing certificate please specify: 1. Which version of the package you are using; 2. Which CA is missing. On the other hand if you agree the package actually ships all you need please mark this bug report as Invalid. Thanks! [1] /usr/share/doc/ca-certificates/changelog.gz ** Package changed: nss (Ubuntu) => ca-certificates (Ubuntu) ** Changed in: ca-certificates (Ubuntu) Status: New => Incomplete ** Summary changed: - updating NSS on 18.04 + updating CA certificates on 18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/2003845 Title: updating CA certificates on 18.04 Status in ca-certificates package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 uses older version of NSS (version 3.35) by which the latest root certificates distributed by NSS are not trusted in Ubuntu 18.04. Hence, please update it to latest version of NSS. For example, Mozilla Firefox uses version 3.86 of NSS in Ubuntu 18.04. This issue is impacting a set of users using their TLS certificates from latest root CAs, where website connections are failing due to untrusted certificate authorities. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2003845/+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 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
Hello Aaron, or anyone else affected, Accepted ubiquity into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubiquity/22.04.19 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. ** Changed in: ubiquity (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Status in ubiquity source package in Jammy: Fix Committed Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 2004035] [NEW] package openssh-server 1:8.9p1-3ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit statu
Public bug reported: The following NEW packages will be installed: ncurses-term openssh-server openssh-sftp-server ssh-import-id 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 750 kB of archives. After this operation, 6,046 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 openssh-sftp-server amd64 1:8.9p1-3ubuntu0.1 [38.7 kB] Get:2 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 openssh-server amd64 1:8.9p1-3ubuntu0.1 [434 kB] Get:3 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 ncurses-term all 6.3-2 [267 kB] Get:4 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 ssh-import-id all 5.11-0ubuntu1 [10.1 kB] Fetched 750 kB in 0s (2,652 kB/s) Preconfiguring packages ... Selecting previously unselected package openssh-sftp-server. (Reading database ... 143729 files and directories currently installed.) Preparing to unpack .../openssh-sftp-server_1%3a8.9p1-3ubuntu0.1_amd64.deb ... Unpacking openssh-sftp-server (1:8.9p1-3ubuntu0.1) ... Selecting previously unselected package openssh-server. Preparing to unpack .../openssh-server_1%3a8.9p1-3ubuntu0.1_amd64.deb ... Unpacking openssh-server (1:8.9p1-3ubuntu0.1) ... Selecting previously unselected package ncurses-term. Preparing to unpack .../ncurses-term_6.3-2_all.deb ... Unpacking ncurses-term (6.3-2) ... Selecting previously unselected package ssh-import-id. Preparing to unpack .../ssh-import-id_5.11-0ubuntu1_all.deb ... Unpacking ssh-import-id (5.11-0ubuntu1) ... Setting up openssh-sftp-server (1:8.9p1-3ubuntu0.1) ... Setting up openssh-server (1:8.9p1-3ubuntu0.1) ... Not replacing deleted config file /etc/ssh/sshd_config dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Setting up ssh-import-id (5.11-0ubuntu1) ... Setting up ncurses-term (6.3-2) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for ufw (0.36.1-4build1) ... Errors were encountered while processing: openssh-server ProblemType: Package DistroRelease: Ubuntu 22.04 Package: openssh-server 1:8.9p1-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: openssh-sftp-server:amd64: Install openssh-server:amd64: Install ncurses-term:amd64: Install ssh-import-id:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 27 08:22:28 2023 DuplicateSignature: package:openssh-server:1:8.9p1-3ubuntu0.1 Setting up openssh-server (1:8.9p1-3ubuntu0.1) ... Not replacing deleted config file /etc/ssh/sshd_config dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-01-20 (371 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:8.9p1-3ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-01-26 (0 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2004035 Title: package openssh-server 1:8.9p1-3ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: The following NEW packages will be installed: ncurses-term openssh-server openssh-sftp-server ssh-import-id 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 750 kB of archives. After this operation, 6,046 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 openssh-sftp-server amd64 1:8.9p1-3ubuntu0.1 [38.7 kB] Get:2 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 openssh-server amd64 1:8.9p1-3ubuntu0.1 [434 kB] Get:3 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 ncurses-term all 6.3-2 [267 kB] Get:4 http://us.archive.ubuntu.com/ubuntu jammy/main
[Touch-packages] [Bug 2004035] Re: package openssh-server 1:8.9p1-3ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- 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/2004035 Title: package openssh-server 1:8.9p1-3ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: The following NEW packages will be installed: ncurses-term openssh-server openssh-sftp-server ssh-import-id 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 750 kB of archives. After this operation, 6,046 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 openssh-sftp-server amd64 1:8.9p1-3ubuntu0.1 [38.7 kB] Get:2 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 openssh-server amd64 1:8.9p1-3ubuntu0.1 [434 kB] Get:3 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 ncurses-term all 6.3-2 [267 kB] Get:4 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 ssh-import-id all 5.11-0ubuntu1 [10.1 kB] Fetched 750 kB in 0s (2,652 kB/s) Preconfiguring packages ... Selecting previously unselected package openssh-sftp-server. (Reading database ... 143729 files and directories currently installed.) Preparing to unpack .../openssh-sftp-server_1%3a8.9p1-3ubuntu0.1_amd64.deb ... Unpacking openssh-sftp-server (1:8.9p1-3ubuntu0.1) ... Selecting previously unselected package openssh-server. Preparing to unpack .../openssh-server_1%3a8.9p1-3ubuntu0.1_amd64.deb ... Unpacking openssh-server (1:8.9p1-3ubuntu0.1) ... Selecting previously unselected package ncurses-term. Preparing to unpack .../ncurses-term_6.3-2_all.deb ... Unpacking ncurses-term (6.3-2) ... Selecting previously unselected package ssh-import-id. Preparing to unpack .../ssh-import-id_5.11-0ubuntu1_all.deb ... Unpacking ssh-import-id (5.11-0ubuntu1) ... Setting up openssh-sftp-server (1:8.9p1-3ubuntu0.1) ... Setting up openssh-server (1:8.9p1-3ubuntu0.1) ... Not replacing deleted config file /etc/ssh/sshd_config dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Setting up ssh-import-id (5.11-0ubuntu1) ... Setting up ncurses-term (6.3-2) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for ufw (0.36.1-4build1) ... Errors were encountered while processing: openssh-server ProblemType: Package DistroRelease: Ubuntu 22.04 Package: openssh-server 1:8.9p1-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: openssh-sftp-server:amd64: Install openssh-server:amd64: Install ncurses-term:amd64: Install ssh-import-id:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 27 08:22:28 2023 DuplicateSignature: package:openssh-server:1:8.9p1-3ubuntu0.1 Setting up openssh-server (1:8.9p1-3ubuntu0.1) ... Not replacing deleted config file /etc/ssh/sshd_config dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-01-20 (371 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:8.9p1-3ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-01-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2004035/+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 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received
Jammy/22.04: - test packages in ppa:mfo/lp1926139 - reproduction steps delta (based on comment #9) ... Reproducer based on GDB and DHCP noise injection. It uses 3 veth pairs (DHCP server/client/injector, the latter two under namespaces) on a linux bridge. ... LXD VM: lxc launch ubuntu:jammy lp1926139-jammy --vm lxc shell lp1926139-jammy GDB Reproducer (original package): == Debug symbols: # wget https://launchpad.net/ubuntu/+archive/primary/+files/isc-dhcp-client-dbgsym_4.4.1-2.3ubuntu2.3_amd64.ddeb # apt install -y ./isc-dhcp-client-dbgsym_4.4.1-2.3ubuntu2.3_amd64.ddeb Source code line numbers (for breakpoint): 198 isc_result_t omapi_register_io_object (omapi_object_t *h, ... 259 status = isc_socket_fdwatchcreate(dhcp_gbl_ctx.socketmgr, ... 279 for (p = omapi_io_states.next; Attempt to reproduce the issue with a delay introduced via breakpoint on line 279: # ip netns exec ns1 \ gdb -ex 'set target-async on' -ex 'set non-stop on' -ex 'set pagination off' -ex 'set confirm off' -q dhclient (gdb) break omapip/dispatch.c:279 (gdb) commands shell sleep 0.2 continue end (gdb) run -v -d veth1 GDB Reproducer (patched package): == Client & Debug symbols: # wget \ https://launchpad.net/~mfo/+archive/ubuntu/lp1926139/+files/isc-dhcp-client_4.4.1-2.3ubuntu2.3+lp1926139.2_amd64.deb \ https://launchpad.net/~mfo/+archive/ubuntu/lp1926139/+files/isc-dhcp-client-dbgsym_4.4.1-2.3ubuntu2.3+lp1926139.2_amd64.ddeb # sudo apt install \ ./isc-dhcp-client_4.4.1-2.3ubuntu2.3+lp1926139.2_amd64.deb \ ./isc-dhcp-client-dbgsym_4.4.1-2.3ubuntu2.3+lp1926139.2_amd64.ddeb Source code line numbers (for breakpoint): 233 isc_result_t omapi_register_io_object (omapi_object_t *h, ... 312 status = isc_socket_fdwatchcreate(dhcp_gbl_ctx.socketmgr, ... 333 for (p = omapi_io_states.next; Attempt to reproduce the issue again, the same way, with a delay introduced via breakpoint on line 333: # ip netns exec ns1 \ gdb -ex 'set target-async on' -ex 'set non-stop on' -ex 'set pagination off' -ex 'set confirm off' -q dhclient (gdb) break omapip/dispatch.c:333 (gdb) commands shell sleep 0.2 continue end (gdb) run -v -d veth1 ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1926139 Title: dhclient: thread concurrency race leads to DHCPOFFER packets not being received Status in bind9-libs package in Ubuntu: Won't Fix Status in isc-dhcp package in Ubuntu: Invalid Status in isc-dhcp source package in Focal: In Progress Status in isc-dhcp source package in Jammy: In Progress Bug description: [Impact] Occasionally, during instance boot or machine start-up, dhclient will attempt to acquire a dhcp lease and fail, leaving the instance with no IP address and making it unreachable. This happens about once every 100 reboots on bare metal, or Chris Patterson in comment #2 describes it as affecting between ~0.3% to 2% of deployments on Microsoft Azure. Azure uses dhclient called from cloud-init instead of systemd-networkd, and this is causing issues with larger deployments. The logs of an affected dhclient produce the following: Listening on LPF/enp1s0/52:54:00:1c:d7:00 Sending on LPF/enp1s0/52:54:00:1c:d7:00 Sending on Socket/fallback DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 3 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 5 (xid=0xd222950f) ... (omitting 20 similar lines) ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 13 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 8 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 6 (xid=0xd222950f) No DHCPOFFERS received. No working leases in persistent database - sleeping. Full log: https://paste.ubuntu.com/p/8yBfw2KR5h/ Log of a working run: https://paste.ubuntu.com/p/N3ZgqrxyQD/ The bizarre thing is when you tcpdump dhclient, we see all DHCPDISOVER packets being replied to with DHCPOFFER packets, but the got_one() callback is never called, dhclient does not read these DHCPOFFER packets, and continues sending DHCPDISCOVER packets. Once it reaches 25 DHCPDISCOVER packets sent, it gives up. tcpdump: Screenshot of Wireshark: This behaviour led several bug reporters to believe it was a kernel issue, with the kernel not pushing DHCPOFFER packets to dhclient. This is not the case, the actual problem is dhclient containing a thread concurrency race condition, and when the race occurs, the read socket is closed prematurely, and dhclient does not read any of the DHCPOFFER replies. The full explanation is in the "Other Info" section, but the fix is to add a mutex that restricts access to the global linked list of open sockets, and ensures that a newly created socket is added to
[Touch-packages] [Bug 1995247] Re: Leftover /tmp/apt-key.* files after updates with embedded gpg keys in deb822 sources
Marking as verified per test instructions, as the autopkgtests have all passed (and the reported regression also has been fixed in a retry apparently, hooray). ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1995247 Title: Leftover /tmp/apt-key.* files after updates with embedded gpg keys in deb822 sources Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Status in apt source package in Kinetic: Fix Committed Status in apt source package in Lunar: Fix Released Bug description: [Impact] When keys are embedded into deb822 sources files as Signed-By, apt writes them to a temporary file, but the code to delete them accidentally had an if (0) in front of the deletion, so they don't get deleted and accumulate with each `apt update` run. [Test plan] Including a test case for this in our comprehensive integration test suite which runs as autopkgtest, so passing autopkgtest = good. [Where problems could occur] Files could end up being removed too soon if the code is otherwise wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op
** Changed in: software-properties (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op
** Merge proposal linked: https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/436428 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op
** Attachment added: "unhandled-exception.log" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+attachment/5643651/+files/unhandled-exception.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op
** Attachment added: "exception-caught.log" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+attachment/5643652/+files/exception-caught.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op
Since poll_for_magic_token runs in a thread, a not handled exception
raised there terminates only the polling thread and indicates some
connection problem.
I cannot specifically get the TimeoutError (at least by disconnecting
after initiating the Ubuntu Pro dialog), but rather ConnectivityError,
as the API indeed specifies[1]. {unhandled-exception.log}
Simply ignoring the exceptions raised from wait() is fine {exception-
caught.log}, but the user should likely be informed that the connection
to the server is failing for whatever reason.
All in all, the reported error is innocuous but the UI should likely to
warn the user about connectivity issue.
[1]: https://github.com/canonical/ubuntu-advantage-
client/blob/main/docs/references/api.md#uproattachmagicwaitv1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2003996
Title:
/usr/bin/software-properties-
gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read
Status in software-properties package in Ubuntu:
In Progress
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.99.22.5, the problem page at
https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op
** Changed in: software-properties (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004011] Re: Checks are not skipped when building esm packages package from source
** Description changed: **Describe the bug** Under the policy, building deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options - However, this is what `override_dh_auto_test` target in `debian/rules` looks like in your case: + However, this is what `override_dh_auto_test` target in `debian/rules` looks like in `heimdal=1.7~git20150920+dfsg-4ubuntu1.16.04.1+esm3`: ``` override_dh_auto_test: - $(MAKE) check + $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. + Apparently, this has been patched: + https://salsa.debian.org/debian/heimdal/-/commit/b1a7b04591873e7d0e88acaf24cc76073ee47fc9 - **Expected behavior** - `override_dh_auto_test` target in `debian/rules` should normally look like this: - ``` - override_dh_auto_test: - ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) - ./run-upstream-testsuite - endif - ``` - This way checks are not run when `DEB_BUILD_OPTIONS="nocheck"` is provided. + However, the patch did not make its way to ESM packages for 16.04. Is it + possible to cherry-pick this commit to the packages? ** Description changed: **Describe the bug** - Under the policy, building deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: + Under the policy, building a deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in `heimdal=1.7~git20150920+dfsg-4ubuntu1.16.04.1+esm3`: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. Apparently, this has been patched: https://salsa.debian.org/debian/heimdal/-/commit/b1a7b04591873e7d0e88acaf24cc76073ee47fc9 However, the patch did not make its way to ESM packages for 16.04. Is it possible to cherry-pick this commit to the packages? ** Description changed: **Describe the bug** Under the policy, building a deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in `heimdal=1.7~git20150920+dfsg-4ubuntu1.16.04.1+esm3`: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. Apparently, this has been patched: https://salsa.debian.org/debian/heimdal/-/commit/b1a7b04591873e7d0e88acaf24cc76073ee47fc9 However, the patch did not make its way to ESM packages for 16.04. Is it - possible to cherry-pick this commit to the packages? + possible to cherry-pick this commit to the packages ESM? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2004011 Title: Checks are not skipped when building esm packages package from source Status in heimdal package in Ubuntu: New Bug description: **Describe the bug** Under the policy, building a deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in `heimdal=1.7~git20150920+dfsg-4ubuntu1.16.04.1+esm3`: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. Apparently, this has been patched: https://salsa.debian.org/debian/heimdal/-/commit/b1a7b04591873e7d0e88acaf24cc76073ee47fc9 However, the patch did not make its way to ESM packages for 16.04. Is it possible to cherry-pick this commit to the packages ESM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2004011/+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 2004011] [NEW] Checks are not skipped when building esm packages package from source
Public bug reported: **Describe the bug** Under the policy, building deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in your case: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. **Expected behavior** `override_dh_auto_test` target in `debian/rules` should normally look like this: ``` override_dh_auto_test: ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) ./run-upstream-testsuite endif ``` This way checks are not run when `DEB_BUILD_OPTIONS="nocheck"` is provided. ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2004011 Title: Checks are not skipped when building esm packages package from source Status in heimdal package in Ubuntu: New Bug description: **Describe the bug** Under the policy, building deb package from source should not run checks when provided with env var `DEB_BUILD_OPTIONS="nocheck"`: https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options However, this is what `override_dh_auto_test` target in `debian/rules` looks like in your case: ``` override_dh_auto_test: $(MAKE) check ``` So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided. **Expected behavior** `override_dh_auto_test` target in `debian/rules` should normally look like this: ``` override_dh_auto_test: ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS))) ./run-upstream-testsuite endif ``` This way checks are not run when `DEB_BUILD_OPTIONS="nocheck"` is provided. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2004011/+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 1995137] Re: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64
whoops, wrong arch: hrw-r--r-- root/root 0 2022-12-11 19:06 ./usr/lib/riscv64-linux- gnu/dri/sun4i-drm_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/armada- drm_dri.so -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1995137 Title: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: Fix Committed Bug description: [Impact] lima driver is missing from riscv64, but in order to enable it we need to disable anything that uses JIT on riscv64: swrast for vulkan, and draw-use-llvm for gallium. JIT for riscv64 is buggy and should be fixed in a future llvm release. [Test case] Check that sun4i-drm_dri.so is in libgl1-mesa-dri deb for riscv64, and that it works. [Where things could go wrong] This is a new driver for the architecture, so there's little chance of breakage. -- "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+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 1995137] Re: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64
hrw-r--r-- root/root 0 2022-12-11 19:06 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so nevermind, the driver is there ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1995137 Title: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: Fix Committed Bug description: [Impact] lima driver is missing from riscv64, but in order to enable it we need to disable anything that uses JIT on riscv64: swrast for vulkan, and draw-use-llvm for gallium. JIT for riscv64 is buggy and should be fixed in a future llvm release. [Test case] Check that sun4i-drm_dri.so is in libgl1-mesa-dri deb for riscv64, and that it works. [Where things could go wrong] This is a new driver for the architecture, so there's little chance of breakage. -- "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+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 1995137] Re: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64
Isaac, care to test kinetic that everything is in place now? This is blocking the mesa update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1995137 Title: Add "sun4i-drm_dri.so" to libg1-mesa-dri and fix compilation on riscv64 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: Fix Committed Bug description: [Impact] lima driver is missing from riscv64, but in order to enable it we need to disable anything that uses JIT on riscv64: swrast for vulkan, and draw-use-llvm for gallium. JIT for riscv64 is buggy and should be fixed in a future llvm release. [Test case] Check that sun4i-drm_dri.so is in libgl1-mesa-dri deb for riscv64, and that it works. [Where things could go wrong] This is a new driver for the architecture, so there's little chance of breakage. -- "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+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 2004003] [NEW] /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script
Public bug reported: Just found the following errors in "systemctl status networking" × networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2023-01-27 12:26:29 MSK; 3min 10s ago Docs: man:interfaces(5) Process: 3963 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Main PID: 3963 (code=exited, status=1/FAILURE) CPU: 147ms янв 27 12:26:29 gerbera systemd[1]: Starting Raise network interfaces... янв 27 12:26:29 gerbera ifup[3976]: /etc/network/if-up.d/resolved: line 12: mystatedir: command not found янв 27 12:26:29 gerbera ifup[3973]: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script янв 27 12:26:29 gerbera ifup[3969]: run-parts: /etc/network/if-up.d/resolved exited with return code 2 янв 27 12:26:29 gerbera ifup[3963]: ifup: failed to bring up lo янв 27 12:26:29 gerbera systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE янв 27 12:26:29 gerbera systemd[1]: networking.service: Failed with result 'exit-code'. янв 27 12:26:29 gerbera systemd[1]: Failed to start Raise network interfaces. The error with mystatedir has been already reported as bug#1907878. However, patches there do not fix unexpected return statement. ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/2004003 Title: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script Status in ifupdown package in Ubuntu: New Bug description: Just found the following errors in "systemctl status networking" × networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2023-01-27 12:26:29 MSK; 3min 10s ago Docs: man:interfaces(5) Process: 3963 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Main PID: 3963 (code=exited, status=1/FAILURE) CPU: 147ms янв 27 12:26:29 gerbera systemd[1]: Starting Raise network interfaces... янв 27 12:26:29 gerbera ifup[3976]: /etc/network/if-up.d/resolved: line 12: mystatedir: command not found янв 27 12:26:29 gerbera ifup[3973]: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script янв 27 12:26:29 gerbera ifup[3969]: run-parts: /etc/network/if-up.d/resolved exited with return code 2 янв 27 12:26:29 gerbera ifup[3963]: ifup: failed to bring up lo янв 27 12:26:29 gerbera systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE янв 27 12:26:29 gerbera systemd[1]: networking.service: Failed with result 'exit-code'. янв 27 12:26:29 gerbera systemd[1]: Failed to start Raise network interfaces. The error with mystatedir has been already reported as bug#1907878. However, patches there do not fix unexpected return statement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2004003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op
** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
