[Bug 2081679] Re: error with syntax in /etc/grub.d/30_os-prober
For support, please see a different venue such as askubuntu, forums, matrix, irc, or ubuntu user mailing lists. ** Changed in: dpkg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081679 Title: error with syntax in /etc/grub.d/30_os-prober To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2081679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081715] Re: Cannot open "APP Center" with the new ubuntu release
** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu ** Package changed: ubuntu => snap-store-desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081715 Title: Cannot open "APP Center" with the new ubuntu release To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/2081715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081799] Re: 389-ds-base FTBFS due to hard-coded clap version in rust-cbindgen
Apologies this was caused by optimize=-lto in DEB_BUILD_OPTIONS - it seems sbuild forwards them to the container. ** Changed in: rust-cbindgen (Ubuntu) Status: Triaged => In Progress ** Changed in: rust-cbindgen (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081799 Title: 389-ds-base FTBFS due to hard-coded clap version in rust-cbindgen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2081799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081799] Re: 389-ds-base FTBFS due to hard-coded clap version in rust-cbindgen
rust-cbindgen fails to build (sbuild -d oracular rust-
cbindgen_0.27.0-1ubuntu1.dsc)
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', 'clean', '--verbose', '--verbose', '--config
profile.release.lto = false'],) {'check': True}
error: unexpected argument '--config profile.release.lto ' found
tip: a similar argument exists: '--config'
Usage: cargo clean --verbose... --config
Build log attached
** Attachment added: "rust-cbindgen_0.27.0-1ubuntu1_amd64.build"
https://bugs.launchpad.net/ubuntu/+source/rust-cbindgen/+bug/2081799/+attachment/5821460/+files/rust-cbindgen_0.27.0-1ubuntu1_amd64.build
** Changed in: 389-ds-base (Ubuntu)
Status: Incomplete => Triaged
** Changed in: rust-cbindgen (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081799
Title:
389-ds-base FTBFS due to hard-coded clap version in rust-cbindgen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2081799/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081799] Re: 389-ds-base FTBFS due to hard-coded clap version in rust-cbindgen
rust-cbindgen uploaded, we _should_ rebuild 389-ds-base once it is built but it's not a priority and we can't upload before rust-cbindgen is published on all architectures. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081799 Title: 389-ds-base FTBFS due to hard-coded clap version in rust-cbindgen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2081799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081799] Re: 389-ds-base FTBFS due to hard-coded clap version in rust-cbindgen
Sponsoroing ** Changed in: 389-ds-base (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081799 Title: 389-ds-base FTBFS due to hard-coded clap version in rust-cbindgen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2081799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081294] Re: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
The analysis below is for 47~rc1, 47.1 fixes the issue by not doing the broken
code path on Linux systems.
I believe this is related to the mutter displayconfig:
We receive this property change:
signal time=1727173020.361584 sender=:1.34 -> destination=(null destination)
serial=11943 path=/org/gnome/Mutter/DisplayConfig;
interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string "org.gnome.Mutter.DisplayConfig"
array [
dict entry(
string "Backlight"
variant struct {
uint32 7
array [
array [
dict entry(
string "connector"
variantstring "eDP-1"
)
dict entry(
string "active"
variantboolean true
)
]
]
}
)
]
array [
]
This is missing value/min/max, hence the update_mutter_backlight() code does
not enter:
if (g_variant_lookup (monitor, "value", "i",
&backlight->brightness_val)) {
g_variant_lookup (monitor, "min", "i",
&backlight->brightness_min);
g_variant_lookup (monitor, "max", "i",
&backlight->brightness_max);
have_backlight = TRUE;
}
So we set those values to -1:
if (!have_backlight) {
backlight->brightness_val = -1;
backlight->brightness_min = -1;
backlight->brightness_max = -1;
}
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081294
Title:
gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/2081294/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081294] Re: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
I did first see this with kernel 6.11 though, it may be possible that the kernel temporarily returns -1 in those sysfs files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081294 Title: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/2081294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081294] Re: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
Notably after a resume the backlight control should still be max 255,
e.g. here it is
root@jak-t14-g3:/sys/class/backlight/amdgpu_bl1# grep . * 2>/dev/null
actual_brightness:15
bl_power:0
brightness:15
max_brightness:255
scale:unknown
type:raw
Basically yes it passes -1:
(gdb)
#0 gsd_power_backlight_abs_to_percentage (min=-1, max=-1, value=-1) at
../plugins/power/gpm-common.c:54
__func__ = "gsd_power_backlight_abs_to_percentage"
#1 0x60bb8f841733 in gsd_backlight_set_brightness_val_async
(backlight=0x60bbaeda21d0 [GsdBacklight], value=,
callback=, user_data=, cancellable=0x0)
at ../plugins/power/gsd-backlight.c:480
task_data =
error = 0x0
task = 0x60bbaeda6200 [GTask]
monitor =
percent =
__func__ = { }
** Tags added: rls-oo-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081294
Title:
gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/2081294/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081562] Re: postgressql is something I am using and do not want to remove it for an upgrade
As the message said. You'll want to export your database, remove postgres, run the release upgrade, and then reinstall postgres and import your database, as we don't want to upgrade the database for you to prevent data loss. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081562 Title: postgressql is something I am using and do not want to remove it for an upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080940] Re: unattended-upgrades broken by python-upgrade
One proposed work around in Python is to change the email.generator module import: from email.errors import HeaderWriteError to graciously support the previous version email.errors: try: from email.errors import HeaderWriteError except ImportError: from email.errors import MessageError as HeaderWriteError This will work correctly for affected applications as they can't know about HeaderWriteError yet anyway, so we can't break any except clauses. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080940 Title: unattended-upgrades broken by python-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/2080940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080940] Re: unattended-upgrades broken by python-upgrade
While we're debating workarounds, to note: This issue affects unattended-upgrades only once, in a non-default configuration and does not break the ability to install upgrades. After the upgrade ran, the next upgrade will work correctly (as it will have imported the new email.errors due to restarting). This may not just affect unattended-upgrades. Third-party applications may be affected if 1. they use email.message to send or generate emails, and 2. they have not send an email prior to the update, and 3. they want to send an email after the update Their failure case may be worse in that they graciously handle failure and end up not crashing, and need a manual restart to be able to send emails again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080940 Title: unattended-upgrades broken by python-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/2080940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080940] Re: unattended-upgrades broken by python-upgrade
** Changed in: unattended-upgrades (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080940 Title: unattended-upgrades broken by python-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/2080940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080940] Re: unattended-upgrades broken by python-upgrade
** Also affects: python3.12 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080940 Title: unattended-upgrades broken by python-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/2080940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080837] Re: Upgrade to ubuntu 24 fails
Please file a new bug report for the remaining upgrade issue such that we get the debugging information for that one. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080837 Title: Upgrade to ubuntu 24 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080888] Re: LXD fails to start with message: "Required tool 'zpool' is missing"
This is a problem for the lxd people to fix ** Package changed: ubuntu-release-upgrader (Ubuntu) => lxd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080888 Title: LXD fails to start with message: "Required tool 'zpool' is missing" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2080888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080940] Re: unattended-upgrades broken by python-upgrade
The problem here is funny: `Message.as_string()` imports `email.generator` when called. Now, `email.generator` has been updated to the security update that depends on the new class `HeaderWriteError`. But we already had imported `email.errors` earlier, in either of the `email.charset` or `email.message` imports - so it is still at the old version and does not have the class. ** Also affects: python3.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: python3.8 (Ubuntu) Importance: Undecided Status: New ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080940 Title: unattended-upgrades broken by python-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/2080940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080856] Re: Ubuntu does not update to 24.04.1 LTS
You have configured ubuntu.mirror.serverloft.de as your mirror, but no such host exists, please fix your configuration. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080856 Title: Ubuntu does not update to 24.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080813] Re: Änderungen werden berechnet Änderungen werden berechnet Es konnte nicht ermittelt werden, welche Systemaktualisierungen verfügbar sind Ein unlösbares Problem trat während der Be
It is not possible to upgrade if you had installed a backported PPA version of pipewire. You may get lucky trying to resolve the issue by using: apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3' apt install '?installed?source-package(^pipewire$)/jammy-updates' ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080813 Title: Änderungen werden berechnet Änderungen werden berechnet Es konnte nicht ermittelt werden, welche Systemaktualisierungen verfügbar sind Ein unlösbares Problem trat während der Berechnung der Systemaktualisierung auf. Das Paket 'update-manager' ist zum Entfernen markiert, aber es befindet sich in der Ausnahmeliste zum Entfernen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080783] Re: I can't update to the latest version of the system because it is said to be "replicated" my source repositories.
Please select a new mirror, yours has not been updated since July 2023 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080783 Title: I can't update to the latest version of the system because it is said to be "replicated" my source repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080822] Re: Postgres maybe blocks upgrade from jammy jellfish to noble numbat
This is a feature, not a bug, to protect your Postgres databases from being automatically upgraded to newer Postgres versions which may cause data loss. You need to manually take backups, remove postgres, upgrade and then install the new postgres and restore the database backups. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080822 Title: Postgres maybe blocks upgrade from jammy jellfish to noble numbat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080837] Re: Upgrade to ubuntu 24 fails
It is not possible to upgrade if you had installed a backported PPA version of pipewire. You may get lucky trying to resolve the issue by using: apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3' apt install '?installed?source-package(^pipewire$)/jammy-updates' ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080837 Title: Upgrade to ubuntu 24 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080841] Re: Upgrading from Jammy to Noble removes ppp and freeradius packages
Please run ubuntu-bug 2080841 to attach additional information from the upgrade to the bug report. This may be a duplicate of bug 2079842, at least for the ppp thing; I don't know why/how freeradius was installed, we need the logs (so run the command). But likely this is a Won't Fix issue - we can't protect every random package from being removed. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080841 Title: Upgrading from Jammy to Noble removes ppp and freeradius packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079817] Re: Jammy to Noble ubuntu studio upgrade fails
Erich that's not (entirely) true. There may be missing seeded packages to force the solver into the right solution, or conflicting seeds. i.e. seeding pipewire-audio, pipewire, pipewire-alsa, libspa-0.2-bluetooth directly from ubuntustudio-desktop might solve the issue, but it's going to be a long and annoying thing to figure that out. ** Changed in: ubuntustudio-meta (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079817 Title: Jammy to Noble ubuntu studio upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2079817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080636] Re: upgrade script from 22.04 to 24.04 fails due to package 'postgresql-13-postgis-3'
We do not support upgrading Postgres versions as such you need to manually backup your databases, if any, remove postgres, upgrade and then install the latest packaged version. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080636 Title: upgrade script from 22.04 to 24.04 fails due to package 'postgresql-13-postgis-3' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079785] Re: apt / apt-get install produce spurious Warning
You can also use /usr/lib/apt/apt-helper drop-privs to run as _apt user for enhanced debugging. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079785 Title: apt / apt-get install produce spurious Warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2079785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079785] Re: apt / apt-get install produce spurious Warning
APT first drops all groups and then changes the effective user and group
id to the one for _apt, before attempting to
mkstemp("/var/cache/apt/archives/partial/.apt-acquire-privs-
test.XX")
to create a file. There must be some permission issue in some part of that
tree, check your /, /var, /var/cache, /var/cache/apt, /var/cache/apt/archives
directories as well - they must have the "executable" permission bit set for
the "other" user such that _apt can traverse them and get to the "partial"
directory.
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079785
Title:
apt / apt-get install produce spurious Warning
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2079785/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
Tagging this for the apt/noble and apt/oracular uploads. ** Changed in: apt (Ubuntu) Milestone: None => ubuntu-24.10 ** Tags removed: rls-nn-incoming ** Tags added: foundations-todo ** Changed in: apt (Ubuntu Noble) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: apt (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080233] Re: [wsl] do-release-upgrade fails with systemd disabled
** Tags removed: rls-nn-incoming ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080233 Title: [wsl] do-release-upgrade fails with systemd disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968613] Re: update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup'
Seems like somebody called close() while hanging on to the objects from the cache. ** Changed in: update-manager (Ubuntu) Status: New => Triaged ** Tags removed: rls-nn-incoming ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968613 Title: update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1968613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080216] Re: sshd cannot bind to IPv4 interfaces
** Tags removed: rls-nn-incoming ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080216 Title: sshd cannot bind to IPv4 interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2080216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080499] Re: /usr/share/apport/apport:ProcessLookupError:/usr/share/apport/apport@1248:main:_check_global_pid_and_forward:forward_crash_to_container
** Tags removed: rls-oo-incoming ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080499 Title: /usr/share/apport/apport:ProcessLookupError:/usr/share/apport/apport@1248:main:_check_global_pid_and_forward:forward_crash_to_container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2080499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080297] Re: installed shim-signed package post-installation script subprocess returned error exit status 32
This seems to be working correctly. The device you installed to no longer exists, so you need to select a different one. Since you are non- interactive, you cannot select a different one, so the upgrade has no choice but to fail. You are of course free to preseed the correct values for the option or change to the new cloud image installation style where supported: Template: grub-efi/cloud_style_installation Type: boolean Default: false _Description: Choose installation target based on the device containing /boot? ** Changed in: shim-signed (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080297 Title: installed shim-signed package post-installation script subprocess returned error exit status 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/2080297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080505] Re: Issue updating 22.04.5
The upgrade issue seems to stem from the fact that you had installed a backported PPA version of pipewire. You may get lucky trying to resolve the issue by using: apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3' apt install '?installed?source-package(^pipewire$)/jammy-updates' ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080505 Title: Issue updating 22.04.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080507] Re: upgrade fail
Most of the apt log is about various issues with ubuntukylin packages. ** Also affects: ubuntukylin-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080507 Title: upgrade fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080512] Re: Não é possível instalar 'lubuntu-desktop'
The upgrade issue seems to stem from the fact that you had installed a backported PPA version of pipewire. You may get lucky trying to resolve the issue by using: apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3' apt install '?installed?source-package(^pipewire$)/jammy-updates' ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080512 Title: Não é possível instalar 'lubuntu-desktop' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080296] Re: Noble not responding, stuck on Cleaning up phase, while Upgrading from 22 to 24
This is no longer an issue with apt 2.4.13, but I guess yes, we should run the main loop iteration ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Won't Fix => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080296 Title: Noble not responding, stuck on Cleaning up phase, while Upgrading from 22 to 24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874272] Re: Stage "searching for obsolete software" takes a very long time (30 minutes)
Yes, apt may have been phasing at the time, and it is shown at the top of /var/log/dist-upgrade/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874272 Title: Stage "searching for obsolete software" takes a very long time (30 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080274] Re: unable to upgrade from 22.04 to 24.04 now
*** This bug is a duplicate of bug 2078589 *** https://bugs.launchpad.net/bugs/2078589 ** This bug has been marked a duplicate of bug 2078589 fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080274 Title: unable to upgrade from 22.04 to 24.04 now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080323] Re: failed to upgrade to new release
Please note that after that it seems you may encounter bug 2078354 and/or bug 2078579 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080323 Title: failed to upgrade to new release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080323] Re: failed to upgrade to new release
You have installed a newer version of python3.12 in your 22.04 system than is available in 24.04: libpython3.12t64:amd64 Depends on libpython3.12-stdlib:amd64 < 3.12.6-1+jammy1 @ii mK > (= 3.12.3-1ubuntu0.1) can't be satisfied! => 3.12.6-1+jammy1 does not exist in the archive You may be able to force downgrade it with apt install '?installed?source-package(^python3.12$)/jammy-updates' or similar ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080323 Title: failed to upgrade to new release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080502] Re: ubuntu-release-upgrader bug
The upgrade issue seems to stem from the fact that you had installed a backported PPA version of pipewire. You may get lucky trying to resolve the issue by using: apt install '?installed?source-package(^pipewire$)=0.3.48-1ubuntu3' apt install '?installed?source-package(^pipewire$)/jammy-updates' You may experience other issues after this is resolved such as bug 2078589 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080502 Title: ubuntu-release-upgrader bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080364] Re: upgrade from 22.04 to 24.04 fails
*** This bug is a duplicate of bug 2078589 *** https://bugs.launchpad.net/bugs/2078589 ** This bug has been marked a duplicate of bug 2078589 fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080364 Title: upgrade from 22.04 to 24.04 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
@aaronmfeld If you have an upgrade issue, please file a separate issue, this particular one has been verified as fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080501] Re: ubuntu-release-upgrader crashed with apt_pkg.Error: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Fix in https://code.launchpad.net/~juliank/ubuntu-release- upgrader/+git/ubuntu-release-upgrader/+merge/473118 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080501 Title: ubuntu-release-upgrader crashed with apt_pkg.Error: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080431] Re: Upgrade stops: warten auf Sperre für Zwischenspeicher.. wird von Prozess 9585 gehalten
*** This bug is a duplicate of bug 2078354 *** https://bugs.launchpad.net/bugs/2078354 For support questions please use the Ubuntu Forums, askubuntu, IRC, Matrix, or mailing lists. I don't understand your message about the lock, that is to be expected: if you are running a release upgrade, you can't run a normal upgrade in parallel. As for what can be seen in the release upgrade failure, samba can't be upgraded, and it's not clear why. This is a duplicate of bug 2078354. It's possible you can get a release upgrade working by removing nautilus-share and/or samba first (and then should be able to reinstall post upgrade). ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 2078354 It does not made the upgrade fromo 22.04 to 24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080431 Title: Upgrade stops: warten auf Sperre für Zwischenspeicher.. wird von Prozess 9585 gehalten To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078354] Re: It does not made the upgrade fromo 22.04 to 24.04
I misread the apt debugging log, H is not hold but held ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Invalid => Incomplete ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078354 Title: It does not made the upgrade fromo 22.04 to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080460] Re: Update fails
*** This bug is a duplicate of bug 2078826 *** https://bugs.launchpad.net/bugs/2078826 ** This bug has been marked a duplicate of bug 2078826 Ubuntu budgie: pulseaudio-module-bluetooth fight -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080460 Title: Update fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080333] Re: Noble upgrade failed
*** This bug is a duplicate of bug 2078826 *** https://bugs.launchpad.net/bugs/2078826 ** This bug has been marked a duplicate of bug 2078826 Ubuntu budgie: pulseaudio-module-bluetooth fight -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080333 Title: Noble upgrade failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080406] Re: No upgrade candidate for libc6-dev?
*** This bug is a duplicate of bug 2078589 *** https://bugs.launchpad.net/bugs/2078589 Hello, I am at a loss as to what you want with libc6-dev, of course it exists, it is part of build-essential, and how it relates to your upgrade issue. I suggest you visit askubuntu, irc, matrix, or the support mailing lists if you need help installing it. As for the failed upgrade, that seems to be a duplicate of bug 2078589. ** This bug has been marked a duplicate of bug 2078589 fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080406 Title: No upgrade candidate for libc6-dev? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080264] Re: upgrade failure from 22.04 LTS to 24.04 LTS
You have replaced several core system components with ones from a System76 Pop!OS development PPA, this is not something we can support. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080264 Title: upgrade failure from 22.04 LTS to 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080250] Re: dpkg-source warns missing XSBC-Original-Maintainer for -0ubuntu1 version
That change is not correct, because there are plenty of 0ubuntu uploads of newer upstream versions that should have the field set, so you'd need to analyse debian/changelog and check if all previous uploads where Ubuntu ones to hide the warning, and I'm not sure that makes a lot of sense vs just ignoring the warning in your head. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080250 Title: dpkg-source warns missing XSBC-Original-Maintainer for -0ubuntu1 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2080250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080226] Re: ubuntu 22.04 to 24.04 ERROR Dist-upgrade failed: 'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.'
*** This bug is a duplicate of bug 2078589 *** https://bugs.launchpad.net/bugs/2078589 ** This bug has been marked a duplicate of bug 2078589 fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080226 Title: ubuntu 22.04 to 24.04 ERROR Dist-upgrade failed: 'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080248] Re: ubuntu 22 to 24 - unsolvable problem
You have removed the main Ubuntu sources from your system, that is, deb http://fr.archive.ubuntu.com/ubuntu/ jammy main as such the upgrade was not possible. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080248 Title: ubuntu 22 to 24 - unsolvable problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080242] Re: cannot upgrade from 22.04 to 24.04 LTS
*** This bug is a duplicate of bug 2078589 *** https://bugs.launchpad.net/bugs/2078589 A lot of packages have been replaced with versions from a PPA and these are causing issues, specifically wine is in a version newer than the one in 24.04 and libreoffice appears at the end. But all of them seem to be resolved by removing the affected packages, and you end up with a fontconfig-common vs kubuntu-settings-desktop bug, that is, a duplicate of bug 2078589 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 2078589 fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080242 Title: cannot upgrade from 22.04 to 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075274] Re: cannot upgrade from 22.04 to 24.04 LTS
*** This bug is a duplicate of bug 2078589 *** https://bugs.launchpad.net/bugs/2078589 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Invalid ** This bug has been marked a duplicate of bug 2078589 fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075274 Title: cannot upgrade from 22.04 to 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2075274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080239] Re: Software Updater "up to date" message is misleading with phasing
The release upgrader already ignores phasing updates when considering
whether all updates are installed, at least for the do-release-upgrade
entry point:
upgradable = [pkg for pkg in cache if pkg.is_upgradable]
for pkg in upgradable:
if 'Phased-Update-Percentage' in pkg.candidate.record:
# P-U-P does not exist if it is fully phased
continue
else:
install_count += 1
# one upgradeable package is enough to stop the dist-upgrade
break
if install_count > 0:
if not options.quiet:
print(_("Please install all available updates "
"for your release before upgrading."))
Hence you only see this issue when there are no-longer-phased updates
missing. However, there might of course be issues there in case an
update that finished phasing depends on another update that is still
phasing - it is then being kept back because its dependencies can't be
satisfied.
This is not a very common issue, and very likely not the one in the
example.
If you have a *specific* instance of the issue, specifically ones that
are not in the described failure case, we are going to need a
/var/lib/dpkg/status and /var/lib/apt/lists and /etc/apt attached to the
bug report.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080239
Title:
Software Updater "up to date" message is misleading with phasing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080239/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080239] Re: Software Updater "up to date" message is misleading with phasing
** Package changed: update-manager (Ubuntu) => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080239 Title: Software Updater "up to date" message is misleading with phasing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063101] Re: Update apt override from important to required
How does it calculate that? The package is Priority: required for the source in debian/control, which extends to Package: apt and accidentally I suppose to Package: apt-utils as well -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063101 Title: Update apt override from important to required To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2063101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874272] Re: Stage "searching for obsolete software" takes a very long time (30 minutes)
Andy, the issue re-occurs with 24.04.23 if you upgrade from an out-of- date jammy system that did not have apt 2.4.13 installed prior to starting the upgrade, or 23.10 (as we can't fix apt there), as we needed to add a fall-back to the old algorithm in that version in those cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874272 Title: Stage "searching for obsolete software" takes a very long time (30 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079958] Re: how to fix this
Your mirror is severely out of date, please configure a different one, for example, graphically, using the Software & Properties app (software- properties-qt/software-properties-gtk) ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079958 Title: how to fix this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2079958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080017] Re: unable to upgrade to 24.04 due to postgresql-9.5
You can run `sudo apt remove postgresql-9.5` prior to upgrading. We don't remove old versions of postgres ourselves due to the risk of data loss when upgrading to new versions so it should be an informed user- driven process. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080017 Title: unable to upgrade to 24.04 due to postgresql-9.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079924] Re: Could not determine the upgrade An unresolvable problem occurred while calculating the upgrade
Thanks, this is a very good bug report for debugging the issue of samba not being upgraded, I've seen this a couple times. You should be able to upgrade by first removing nautilus-share (and then can reinstall it after the upgrade). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079924 Title: Could not determine the upgrade An unresolvable problem occurred while calculating the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2079924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079922] Re: there is this error: /etc/apt/sources.list.d/third-party.sources URI parse.
Thank you for your bug report. I'd advise you to consult a support forum such as our IRC, Matrix channels, the mailing list, askubuntu, or the Ubuntu forums in case you need help with your repository configuration. ** Changed in: update-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079922 Title: there is this error: /etc/apt/sources.list.d/third-party.sources URI parse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2079922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079843] Re: gdm3 fails after release upgrade, have to use lightdm
Reassigning as the upgrade looks good. Consider checking what's up with your SATA controller it goes down and resumes at limited speed a lot: [ 995.233156] ata5: SATA link down (SStatus 1 SControl 310) [ 995.243104] ata5: limiting SATA link speed to 1.5 Gbps [ 997.473147] ata5: SATA link down (SStatus 1 SControl 310) [ 997.476944] ata5: limiting SATA link speed to 1.5 Gbps ** Package changed: ubuntu-release-upgrader (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079843 Title: gdm3 fails after release upgrade, have to use lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2079843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079817] Re: Jammy to Noble ubuntu studio upgrade fails
I do not believe there is anything substantially different here vs https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/2078639 but this one is probably the better reproducer than that bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079817 Title: Jammy to Noble ubuntu studio upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2079817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079817] Re: Jammy to Noble ubuntu studio upgrade fails
Failed to find is not a bug, but expected; it just logs packages that we did not find a t64 package for, which will be most of them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079817 Title: Jammy to Noble ubuntu studio upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2079817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079842] Re: mantic -> noble lxd VM: upgrade removes Recommended packages
Suggested spike: When u-r-u asks to remove obsolete packages, run apt autoremove -s in the terminal and see what it does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079842 Title: mantic -> noble lxd VM: upgrade removes Recommended packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2079842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079842] Re: mantic -> noble lxd VM: upgrade removes Recommended packages
This must be a silly bug in how we initialize the depcache in apt, as when reinstalling fwupd, marking it automatic, and then calling autoremove, the autoremove does nothing: root@mantic-to-noble-proposed:~# apt install fwupd [...] root@mantic-to-noble-proposed:~# apt-mark auto fwupd fwupd set to automatically installed. root@mantic-to-noble-proposed:~# apt-get autoremove -s Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079842 Title: mantic -> noble lxd VM: upgrade removes Recommended packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2079842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079842] [NEW] mantic -> noble lxd VM: upgrade removes Recommended packages
Public bug reported: After upgrading a mantic lxd VM to noble, bolt and fwupd are missing: They were considered unused dependencies during the upgrade: 2024-09-06 14:05:46,066 DEBUG Unused dependencies: libcbor0.8 libicu72 libqmi-glib5 libvolume-key1 libappstream4 libprotobuf-c1 libsmbios-c2 libmbim-utils python3-keyring perl-modules-5.36 libbytesize-common libnss3 libpython3.11 libjcat1 libpython3.11-minimal tpm-udev libpython3.11-stdlib libgcab-1.0-0 libnss-nisplus fwupd-signed python3-jeepney libaio1 usb-modeswitch libblockdev-crypto3 libnspr4 libqrtr-glib0 usb-modeswitch-data libqmi-proxy libmbim-glib4 libbytesize1 libunistring2 tzdata-icu python3-jaraco.classes libatasmart4 libblockdev3 irqbalance libtcl8.6 libtss2-mu0 udisks2 libarchive13t64 libmbim-proxy libudisks2-0 libblockdev-part3 python3.11 libnetplan0 gcc-13-base libqmi-utils libblockdev-nvme3 libblockdev-fs3 libnss-nis libgusb2 ubuntu-advantage-tools libnsl2 libjq1 libflashrom1 libnvme1t64 libperl5.36 jq libblockdev-loop3 libftdi1-2 libblockdev- utils3 libmm-glib0 modemmanager tcl bolt python3.11-minimal libfwupd2 libblockdev-mdraid3 libonig5 python3-secretstorage tcl8.6 libjson- glib-1.0-0 libblockdev-swap3 libgpgme11t64 libjson-glib-1.0-common But clearly they are not: root@mantic-to-noble-proposed:~# aptitude why bolt i ubuntu-server Recommends fwupd c fwupd Recommends bolt This is awkward because the unused dependencies are just the list of packages apt considers autoremovable, but with installed Reverse- Recommends, neither of them should be. To reproduce, run # lxc launch ubuntu:mantic mantic-to-noble-proposed # lxc exec mantic-to-noble-proposed apt-mark hold lxd-agent-loader # lxd bug # lxc exec mantic-to-noble-proposed do-release-upgrade -p ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Summary changed: - mantic -> noble lxd VM: upgrade removes fwupd, bolt + mantic -> noble lxd VM: upgrade removes Recommended packages ** Description changed: After upgrading a mantic lxd VM to noble, bolt and fwupd are missing: They were considered unused dependencies during the upgrade: 2024-09-06 14:05:46,066 DEBUG Unused dependencies: libcbor0.8 libicu72 libqmi-glib5 libvolume-key1 libappstream4 libprotobuf-c1 libsmbios-c2 libmbim-utils python3-keyring perl-modules-5.36 libbytesize-common libnss3 libpython3.11 libjcat1 libpython3.11-minimal tpm-udev libpython3.11-stdlib libgcab-1.0-0 libnss-nisplus fwupd-signed python3-jeepney libaio1 usb-modeswitch libblockdev-crypto3 libnspr4 libqrtr-glib0 usb-modeswitch-data libqmi-proxy libmbim-glib4 libbytesize1 libunistring2 tzdata-icu python3-jaraco.classes libatasmart4 libblockdev3 irqbalance libtcl8.6 libtss2-mu0 udisks2 libarchive13t64 libmbim-proxy libudisks2-0 libblockdev-part3 python3.11 libnetplan0 gcc-13-base libqmi-utils libblockdev-nvme3 libblockdev-fs3 libnss-nis libgusb2 ubuntu-advantage-tools libnsl2 libjq1 libflashrom1 libnvme1t64 libperl5.36 jq libblockdev-loop3 libftdi1-2 libblockdev- utils3 libmm-glib0 modemmanager tcl bolt python3.11-minimal libfwupd2 libblockdev-mdraid3 libonig5 python3-secretstorage tcl8.6 libjson- glib-1.0-0 libblockdev-swap3 libgpgme11t64 libjson-glib-1.0-common But clearly they are not: root@mantic-to-noble-proposed:~# aptitude why bolt i ubuntu-server Recommends fwupd - c fwupd Recommends bolt + c fwupd Recommends bolt + + This is awkward because the unused dependencies are just the list of + packages apt considers autoremovable, but with installed Reverse- + Recommends, neither of them should be. - This is awkward because the unused dependencies are just the list of packages apt considers autoremovable, but with installed Reverse-Recommends, neither of them should be. + To reproduce, run + + # lxc launch ubuntu:mantic mantic-to-noble-proposed + # lxc exec mantic-to-noble-proposed apt-mark hold lxd-agent-loader # lxd bug + # lxc exec mantic-to-noble-proposed do-release-upgrade -p -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079842 Title: mantic -> noble lxd VM: upgrade removes Recommended packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2079842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
Upgrading with ubuntu-release-upgrader from proposed also worked correctly: $ lxc list -c nft +--+--+-+ | NAME | BASE IMAGE | TYPE | +--+--+-+ | jammy-to-noble-proposed | d45dfeba51e0 | VIRTUAL-MACHINE | +--+--+-+ | mantic-to-noble-proposed | 554642c1987e | VIRTUAL-MACHINE | +--+--+-+ $ lxc exec mantic-to-noble-proposed grep "INFO.*version" /var/log/dist-upgrade/main.log 2024-09-06 13:58:31,556 INFO apt version: '2.7.3ubuntu0.1' 2024-09-06 13:58:31,556 INFO python version: '3.11.6 (main, Apr 10 2024, 17:26:07) [GCC 13.2.0]' 2024-09-06 13:58:31,558 INFO release-upgrader version '24.04.23' started $ lxc exec jammy-to-noble-proposed grep "INFO.*version" /var/log/dist-upgrade/main.log 2024-09-06 13:58:30,075 INFO apt version: '2.4.12' 2024-09-06 13:58:30,076 INFO python version: '3.10.12 (main, Jul 29 2024, 16:56:48) [GCC 11.4.0]' 2024-09-06 13:58:30,078 INFO release-upgrader version '24.04.23' started ^ looks good :) Now as for the verification itself: ***jammy*** Remove: libblockdev-crypto2 libblockdev-fs2 libblockdev-loop2 libblockdev-part-err2 libblockdev-part2 libblockdev-swap2 libblockdev-utils2 libblockdev2 libtss2-mu0 Remove (was auto installed) binutils binutils-common binutils-x86-64-linux-gnu gcc-12-base irqbalance isc-dhcp-client isc-dhcp-common libaio1 libappstream4 libbinutils libbpf0 libcbor0.8 libctf-nobfd0 libctf0 libdns-export1110 libgprofng0 libicu70 libisc-export1105 libldap-2.5-0 libmpdec3 libnetplan0 libnsl2 libpcre3 libperl5.34 libprocps8 libpython3.10 libpython3.10-minimal libpython3.10-stdlib libsframe1 libunistring2 linux-headers-kvm perl-modules-5.34 pkexec policykit-1 python3-jaraco.classes python3-jeepney python3-keyring python3-secretstorage python3.10 python3.10-minimal ubuntu-advantage-tools Finally: root@jammy-to-noble-proposed:~# apt-get upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: lxd-agent-loader 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. ***mantic*** Remove (was auto installed) bolt fwupd-signed gcc-13-base irqbalance jq libaio1 libappstream4 libarchive13t64 libatasmart4 libblockdev-crypto3 libblockdev-fs3 libblockdev-loop3 libblockdev-mdraid3 libblockdev-nvme3 libblockdev-part3 libblockdev-swap3 libblockdev-utils3 libblockdev3 libbytesize-common libbytesize1 libcbor0.8 libflashrom1 libftdi1-2 libfwupd2 libgcab-1.0-0 libgpgme11t64 libgusb2 libicu72 libjcat1 libjq1 libjson-glib-1.0-0 libjson-glib-1.0-common libmbim-glib4 libmbim-proxy libmbim-utils libmm-glib0 libnetplan0 libnsl2 libnspr4 libnss-nis libnss-nisplus libnss3 libnvme1t64 libonig5 libperl5.36 libprotobuf-c1 libpython3.11 libpython3.11-minimal libpython3.11-stdlib libqmi-glib5 libqmi-proxy libqmi-utils libqrtr-glib0 libsmbios-c2 libtcl8.6 libtss2-mu0 libudisks2-0 libunistring2 libvolume-key1 modemmanager perl-modules-5.36 python3-jaraco.classes python3-jeepney python3-keyring python3-secretstorage python3.11 python3.11-minimal tcl tcl8.6 tpm-udev tzdata-icu ubuntu-advantage-tools udisks2 usb-modeswitch usb-modeswitch-data Finally: root@mantic-to-noble-proposed:~# apt-get upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: lxd-agent-loader 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. ** Tags removed: verification-needed ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079826] Re: Ugrade from 22.04 to 24.04 failed
*** This bug is a duplicate of bug 2078589 *** https://bugs.launchpad.net/bugs/2078589 ** This bug has been marked a duplicate of bug 2078589 fight: desktop-base vs kubuntu-settings-desktop vs fontconfig-common: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079826 Title: Ugrade from 22.04 to 24.04 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2079826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
@sil2100 The regression in time is back to the old behavior prior to 24.04.20; actually it's a bit faster as there is just a single action group now. But the reason for it was that we iterated over all packages in the cache and recorded their selected state in case we needed to undo a change (verifying the change is allowed was equally expensive). What triggers this? The run time is linear to the number of obsolete Ubuntu packages (packages no longer in noble) you have installed. In a small lxd VM, it is sub-second vs 20 seconds or so, on a desktop with many obsolete packages installed it will be a lot longer. Updates from jammy to noble won't see the regression, the apt 2.4.13 SRU I just verified fixes the APT algorithm so it should never fallback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
Verifying the apt/jammy SRU: I installed libapt-pkg6.0=2.4.13 from proposed, then run `do-release- upgrade -p` (`-d` should work now too, but was broken before): The headers for the running kernel are not being removed: Remove (was auto installed) binutils binutils-common binutils-x86-64-linux-gnu gcc-12-base irqbalance isc-dhcp-client isc-dhcp-common libaio1 libappstream4 libbinutils libbpf0 libcbor0.8 libctf-nobfd0 libctf0 libdns-export1110 libgprofng0 libicu70 libisc-export1105 libldap-2.5-0 libmpdec3 libnetplan0 libnsl2 libpcre3 libperl5.34 libprocps8 libpython3.10 libpython3.10-minimal libpython3.10-stdlib libsframe1 libunistring2 linux-headers-kvm perl-modules-5.34 pkexec policykit-1 python3-jaraco.classes python3-jeepney python3-keyring python3-secretstorage python3.10 python3.10-minimal ubuntu-advantage-tools (linux-headers-kvm is, it got replaced by linux-headers-virtual). And apt upgrade is happy: root@jammy-to-noble:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: lxd-agent-loader 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. ** Tags removed: verification-needed-jammy verification-needed-noble ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079819] [NEW] xwayland repeats keypresses, ignores modifier
Public bug reported: I switch into Mattermost with Windows+3 key combination, this causes an endless stream of 3 to be written into the mattermost field until I press another key (similarly for any other number key, I did not try non-numbers) If we look at the keyboard input device with https://github.com/DIGImend/evdev-dump we can see that the key is not stuck, all the input events are correct: /dev/input/event4 1725622057.447632 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.447632 EV_KEY KEY_LEFTMETA 0x0002 ^ press windows key /dev/input/event4 1725622057.447632 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.477343 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.477343 EV_KEY KEY_3 0x0001 ^ press key 3 /dev/input/event4 1725622057.477343 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.627896 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.627896 EV_KEY KEY_3 0x ^ release key 3 /dev/input/event4 1725622057.627896 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.997495 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.997495 EV_KEY KEY_LEFTMETA 0x ^ release windows key (now it starts endlessly dumping 3 into mattermost) /dev/input/event4 1725622057.997495 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.869769 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622059.869769 EV_KEY KEY_LEFTMETA 0x0001 ^ press windows key again /dev/input/event4 1725622059.869769 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.919605 EV_MSC MSC_SCAN 0x0009 /dev/input/event4 1725622059.919605 EV_KEY KEY_8 0x0001 ^ press 8 to switch to the terminal window This only affects Xwayland, native Wayland clients behave correctly. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xwayland 2:24.1.2-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Sep 6 13:26:18 2024 InstallationDate: Installed on 2022-11-26 (650 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular wayland-session ** Description changed: I switch into Mattermost with Windows+3 key combination, this causes an endless stream of 3 to be written into the mattermost field until I - press another key. + press another key (similarly for any other number key, I did not try + non-numbers) If we look at the keyboard input device with https://github.com/DIGImend/evdev-dump we can see that the key is not stuck, all the input events are correct: /dev/input/event4 1725622057.447632 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.447632 EV_KEY KEY_LEFTMETA 0x0002 ^ press windows key /dev/input/event4 1725622057.447632 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.477343 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.477343 EV_KEY KEY_3 0x0001 ^ press key 3 /dev/input/event4 1725622057.477343 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.627896 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.627896 EV_KEY KEY_3 0x ^ release key 3 /dev/input/event4 1725622057.627896 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.997495 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.997495 EV_KEY KEY_LEFTMETA 0x ^ release windows key (now it starts endlessly dumping 3 into mattermost) /dev/input/event4 1725622057.997495 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.869769 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622059.869769 EV_KEY KEY_LEFTMETA 0x0001 ^ press windows key again /dev/input/event4 1725622059.869769 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.919605 EV_MSC MSC_SCAN 0x0009 /dev/input/event4 1725622059.919605 EV_KEY KEY_8 0x0001 ^ press 8 to switch to the terminal window - This only affects Xwayland, native Wayland clients behave correctly. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xwayland 2:24.1.2-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Sep 6 13:26:18 2024 InstallationDate: Installed on 2022-11-26 (650 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://b
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
** Description changed: (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates) [Impact] Obsolete packages can be removed despite still having reverse dependencies installed, for example: Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` [Test plan] ## Jammy APT verification To prepare the VMs, follow the following scheme: $ lxc launch ubuntu:jammy jammy-to-noble --vm If using lxc shell or exec to connect to it, also perform the step below: $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it resets On this jammy VM, edit /etc/update-manager/release-upgrades and set Prompt to "normal" (since release upgrades to noble via the lts prompt are temporarily blocked due to this bug) If this test run is meant to test the fix, then at this point you should install apt from jammy proposed. Otherwise, continue directly with the release upgrade. Then to continue with the test, proceed to the release upgrade: $ sudo do-release-upgrade + Check that currently booted linux-headers- are *not* removed as + obsolete. + After the reboot at the end, in the rebooted system, issue: $ sudo apt upgrade With the bug present, you will get an error like this: $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-5.15.0-1065-kvm : Depends: linux-kvm-headers-5.15.0-1065 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ## Noble APT verification To validate the APT change on noble, we must rely on the test suite as we won't have a noble->oracular upgrade bug causing it, most likely. To validate an ubuntu-release-upgrader change, instead run: ubuntu@jammy-to-noble$ do-release-upgrade -p ubuntu@mantic-to-noble$ do-release-upgrade -p [Where problems could occur: APT SRU] For the APT change, the function in question is used in a small number of places: In APT library: - In the `upgrade` command and library function. Removals are already undone there before calling it so we never reach the new code path. - In the phased update implementation, during dist-upgrade. I expect a failure is lurking there that is fixed by this, but I haven't been able to write a reproducer to trigger it just yet. In aptitude: - The
[Bug 2079810] Re: unattended-upgrades doesn't respect repo pin-priority
This is the expected behavior, it will pick the highest version (well highest priority version) from any allowed repository. You have not disallowed installing the Ubuntu one, and you also did not allow it to install the Mozilla one. You have two options 1) Pin the Ubuntu version down instead: Instead of Package: * Pin: origin packages.mozilla.org Pin-Priority: 1000 please use Package: firefox Pin: release o=Ubuntu* Pin-Priority: -1 or similar. 2) Add the Mozilla repository to the unattended-upgrades allow list. Unattended-Upgrade::Allowed-Origins 3) Add firefox to Unattended-Upgrade::Package-Blacklist You may also be able to pin the installed version to 1000 Package: firefox Pin: release now Pin-Priority: 1000 This should cause it to not consider the Ubuntu versions as allowed upgrades. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079810 Title: unattended-upgrades doesn't respect repo pin-priority To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2079810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079810] Re: unattended-upgrades doesn't respect repo pin-priority
** Changed in: unattended-upgrades (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079810 Title: unattended-upgrades doesn't respect repo pin-priority To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2079810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078307] Re: Grub 2.12 in Oracular is unable to boot Windows using chainloader
** Changed in: grub2 (Ubuntu) Milestone: None => ubuntu-24.10-beta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078307 Title: Grub 2.12 in Oracular is unable to boot Windows using chainloader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2078307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079792] Re: sudo apt upgrade ends in failure. 'running python rtupdate hooks for python 3.12' raises an exception
*** This bug is a duplicate of bug 2078995 *** https://bugs.launchpad.net/bugs/2078995 ** This bug has been marked a duplicate of bug 2078995 package ubuntu-release-upgrader-core 1:24.04.22 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079792 Title: sudo apt upgrade ends in failure. 'running python rtupdate hooks for python 3.12' raises an exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-core-upgrader/+bug/2079792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
** Description changed: + (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates) + [Impact] Obsolete packages can be removed despite still having reverse dependencies installed, for example: - Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` [Test plan] To prepare the VMs, follow the following scheme: $ lxc launch ubuntu:jammy jammy-to-noble $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it resets To validate the apt change on jammy, ubuntu@jammy-to-noble$ add-apt-repository -p proposed ubuntu@jammy-to-noble$ apt install libapt-pkg6.0 # to upgrade libapt-pkg6.0 ubuntu@jammy-to-noble$ do-release-upgrade To validate the APT change on noble, we must rely on the test suite as we won't have a noble->oracular upgrade bug causing it, most likely. To validate an ubuntu-release-upgrader change, instead run: ubuntu@jammy-to-noble$ do-release-upgrade -p ubuntu@mantic-to-noble$ do-release-upgrade -p [Where problems could occur: APT SRU] For the APT change, the function in question is used in a small number of places: In APT library: - In the `upgrade` command and library function. Removals are already undone there before calling it so we never reach the new code path. - In the phased update implementation, during dist-upgrade. I expect a failure is lurking there that is fixed by this, but I haven't been able to write a reproducer to trigger it just yet. In aptitude: - The function is wrapped, but the wrapper never called In QApt: - - QApt seems to rely on it for upgrading and doesn't seem to have any error checking of the return value. I expect it will read the error + - QApt seems to rely on it for upgrading and doesn't seem to have any error checking of the return value. I expect it will read the error [Where problems could occur: u-r-u SRU] Upgrades will now result in a consistent state, but may spend hours searching for obsolete software again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
ubuntu-release-upgrader SRU uploaded to noble and also uploaded to oracular. These reintroduce the slow path as a fallback, specifically for APT versions prior to this SRU (and hence mantic); they also fix that code to correctly consider running kernels (and KeepInstalledSection) in the removal of reverse dependencies of obsolete packages. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
apt/jammy SRU uploaded. The ones for noble and devel need a bit more massaging due to test suite failures but are not relevant before oracular is released (noble's apt is used for noble->oracular updates) ** Also affects: apt (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: ubuntu-release-upgrader (Ubuntu Jammy) ** Changed in: apt (Ubuntu Jammy) Status: New => In Progress ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
** Description changed: + [Impact] + Obsolete packages can be removed despite still having reverse dependencies installed, for example: + + Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to 24.04 via the `do-release-upgrade` command. This issue was seen whilst testing this upgrade path. Upgrading and later rebooting a jammy GCP instance results in `linux-headers-6.5.0-1025-gcp` being a broken state. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1025-gcp : Depends: linux-gcp-6.5-headers-6.5.0-1025 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` `linux-gcp-6.5-headers-6.5.0-1025` is a dependency of `linux-image-6.5.0-1025-gcp` which is also not removed during the upgrade. ``` $ apt-cache rdepends linux-headers-6.5.0-1025-gcp linux-headers-6.5.0-1025-gcp Reverse Depends: linux-image-6.5.0-1025-gcp $ apt-cache rdepends linux-image-6.5.0-1025-gcp linux-image-6.5.0-1025-gcp Reverse Depends: ``` Running `apt --fix-broken install` resolves the error. ``` $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: - linux-headers-6.5.0-1025-gcp + linux-headers-6.5.0-1025-gcp 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 27.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 83770 files and directories currently installed.) Removing linux-headers-6.5.0-1025-gcp (6.5.0-1025.27~22.04.1) ... $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ``` This issue was also observed after upgrading a jammy AWS instance to noble. ``` $ sudo apt install Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-headers-6.5.0-1024-aws : Depends: linux-aws-6.5-headers-6.5.0-1024 but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` + + [Test plan] + + To prepare the VMs, follow the following scheme: + + $ lxc launch ubuntu:jammy jammy-to-noble + $ lxc exec jammy-to-noble apt-mark lxd-agent-launcher # otherwise it resets + + To validate the apt change on jammy, + + ubuntu@jammy-to-noble$ add-apt-repository -p proposed + ubuntu@jammy-to-noble$ apt install libapt-pkg6.0 # to upgrade libapt-pkg6.0 + ubuntu@jammy-to-noble$ do-release-upgrade + + To validate the APT change on noble, we must rely on the test suite as + we won't have a noble->oracular upgrade bug causing it, most likely. + + To validate an ubuntu-release-upgrader change, instead run: + + ubuntu@jammy-to-noble$ do-release-upgrade -p + ubuntu@mantic-to-noble$ do-release-upgrade -p + + [Where problems could occur: APT SRU] + + For the APT change, the function in question is used in a small number + of places: + + In APT library: + - In the `upgrade` command and library function. Removals are already undone there before calling it so we never reach the new code path. + - In the phased update implementation, during dist-upgrade. I expect a failure is lurking there that is fixed by this, but I haven't been able to write a reproducer to trigger it just yet. + + In aptitude: + - The function is wrapped, but the wrapper never called + + In QApt: + - QApt seems to rely on it for upgrading and doesn't seem to have any error checking of the return value. I expect it will read the error + + [Where problems could occur: u-r-u SRU] + Upgrades will now result in a consistent state, but may spend hours searching for obsolete software again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
Turns out that yes this is a bug in the APT solver: https://salsa.debian.org/apt-team/apt/-/merge_requests/373/diffs It was not restoring/keeping obsolete (in its parlance, no longer downloadable) packages that are marked for removal due to a false optimization. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Triaged ** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078720] Re: Upgrading from jammy to noble results in a linux-headers package being in a broken state
Thanks this seems to be a bug in the APT solver not undoing the purge requests here, a regression from when we switched to the new obsoletes handling. This is odd, I am investigating -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078720 Title: Upgrading from jammy to noble results in a linux-headers package being in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2078720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078816] Re: Cannot upgrade Xubuntu 22.04 to 24.04
Somehow lightdm-gtk-greeter is marked for uninstall. MarkDelete lightdm-gtk-greeter:amd64 < 2.0.8-2ubuntu1 -> 2.0.9-0ubuntu3 @ii umU > FU=1 Is there a conflict between Ubuntu MATE and Xubuntu in how they configure lightdm perhaps? ** Also affects: xubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Cannot upgrade Xubuntu 22.04 to 24.04 + Cannot upgrade Xubuntu+MATE hybrid 22.04 to 24.04 ** Also affects: ubuntu-mate-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078816 Title: Cannot upgrade Xubuntu+MATE hybrid 22.04 to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/2078816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078826] Re: Ubuntu budgie: pulseaudio-module-bluetooth fight
Possibly this can be solved by adding Conflicts: pulseaudio-module- bluetooth to the ubuntu-budgie-desktop-meta package or something. This is similar to bug 2078639 ** Summary changed: - Cannot upgrade budgie from 22.04 to 24.04 + Ubuntu budgie: pulseaudio-module-bluetooth fight ** Also affects: ubuntu-budgie-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078826 Title: Ubuntu budgie: pulseaudio-module-bluetooth fight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2078826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078795] Re: Upgrade from 22.04.4 to 24.04 failing
You have disabled the 'main' Ubuntu repository, your system is not in a usable state, please re-renable it. In fact, you have main and restricted for (security) updates, but only universe enabled for the release pocket. You should be able to get back into a decent state by making sure all options are selected in software-properties. deb http://nl.archive.ubuntu.com/ubuntu/ jammy-backports main restricted deb http://security.ubuntu.com/ubuntu jammy-security main restricted deb http://archive.ubuntu.com/ubuntu jammy universe ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078795 Title: Upgrade from 22.04.4 to 24.04 failing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078870] Re: Upgrading to 24.04 LTS from 22.04 LTS
Disabling universe when running a community flavour is not a good idea, so the upgrade failed (and you did not get updates during 22.04 for Xfce either). As for the messages these are from Google Chrome and not interesting to us. For the audio issue, please file a bug using `ubuntu-bug linux` ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078870 Title: Upgrading to 24.04 LTS from 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078639] Re: Ubuntu Studio upgrade, pipewire <-> pulseaudio confict
** Summary changed: - The update crashes at the same place. I have looked but cannot find any non-Ubuntu apps that may cause a problem + Ubuntu Studio upgrade, pipewire <-> pulseaudio confict ** Summary changed: - Ubuntu Studio upgrade, pipewire <-> pulseaudio confict + Ubuntu Studio upgrade, pipewire <-> pulseaudio conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078639 Title: Ubuntu Studio upgrade, pipewire <-> pulseaudio conflict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078910] Re: cannot upgrade to 24.04 LTS
*** This bug is a duplicate of bug 2078639 *** https://bugs.launchpad.net/bugs/2078639 This looks like a standard Ubuntu Studio upgrade failure that we track in bug 2078639 ** This bug has been marked a duplicate of bug 2078639 The update crashes at the same place. I have looked but cannot find any non-Ubuntu apps that may cause a problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078910 Title: cannot upgrade to 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078995] Re: package ubuntu-release-upgrader-core 1:24.04.22 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
During configuration of python3,
/usr/share/python3/debpython/files.py fails to get the content of
packages-
error running python rtupdate hook rhythmbox-plugin-alternative-toolbar
Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in
main()
File "/usr/bin/py3clean", line 196, in main
pfiles = set(dpf.from_package(options.package))
^^
File "/usr/share/python3/debpython/files.py", line 55, in from_package
raise Exception("cannot get content of %s" % package_name)
Which seems to mean `dpkg -L` returned with an exit code != 0
which may be plausible, it is worht investigating if dpkg -L works when
the package is only unpacked.
That said, it's also plausible the file system is corrupted.
Reporter: Please add the output of ls -lh /var/lib/dpkg/info, and try to
run `dpkg -L apt-xapian-index` yourself.
** Package changed: ubuntu-release-upgrader (Ubuntu) => python3-defaults
(Ubuntu)
** Changed in: python3-defaults (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078995
Title:
package ubuntu-release-upgrader-core 1:24.04.22 failed to
install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078995/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078987] Re: due to this not letting me upgrade to ubuntu 24
*** This bug is a duplicate of bug 2078579 *** https://bugs.launchpad.net/bugs/2078579 I believe this is a duplicate of bug 2078579, the first thing that seemingly goes wrong is it not installing libpcap0.8t64 and then following that ppp and network-manager-pptp-gnome fail to upgrade, that said, we can't be sure what actually remains broken, the log doesn't tell us. Removing network-manager-pptp and ppp might help. ** This bug has been marked a duplicate of bug 2078579 Holding Back libpcap0.8t64:amd64 rather than change libibverbs1:amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078987 Title: due to this not letting me upgrade to ubuntu 24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073128] Re: Missing compiler flags
FWIW I seem to have added a bunch of $(LDFLAGS) to lines with $(call gb_ExternalProject_get_link_flags,...) - those are unnecessary and upstream likely should complain about those. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073128 Title: Missing compiler flags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073128] Re: Missing compiler flags
To add, the dump for noble main is available in
https://magenta.jak-linux.org/ubuntu-archive/noble-main.json
and https://magenta.jak-linux.org/ubuntu-archive/noble-main-
report.src.txt is the report of that. For libreoffice it was:
Source: libreoffice
Total: 68
Good: 66
Bad: 1
libreoffice-core:/usr/lib/libreoffice/program/libstaroffice-0.0-lo.so.0
Missing -fno-omit-frame-pointer
Partial: 1
libreoffice-draw:/usr/lib/libreoffice/program/libwpftdrawlo.so Missing
-fno-omit-frame-pointer (2 / 3)
Different toolchain: 1
libreoffice-core:/usr/lib/libreoffice/program/libskialo.so Compiled by LLVM:
{'Ubuntu clang version 18.1.3 (1)'} (1 / 1)
Unknown: 0
(Note that we deduplicated common strings, hence it shows 2/3 in the partial
case but it was more than 3 units affected).
(Skia is now validated too, oracular's clang dumps compiler flags into
DW_AT_producer too)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073128
Title:
Missing compiler flags
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073128/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073128] Re: Missing compiler flags
We have extracted the DW_AT_producer field from the DWARF debug info section, looking for -fno-omit-frame-pointer as part of the 24.04 validation of frame pointer enablement. I have provided a convenient script here that extracts those using python3-pyelftools: https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c There is a separate script to analyse its output, it still needs cleaning up. Particularly note that this only analyses CFLAGS/CXXFLAGS correctness as only compilation units (.o files) have that field; so linker flags and preprocessor flags are not validated (luckily that was enough for us). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073128 Title: Missing compiler flags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076929] Re: [SRU] Rebuild cd-boot-images-{amd64, arm64} against new shim
Andreas: The test plan for the assets included in cd-boot-images- is
ensuring that it matches the expected version of the packages; the boot
tests are part of their SRUs.
We don't do any real testing of cd-boot-images per se, it only affects
image builds, so what we need to do generally speaking is test it
contains the expected thing and then release it such that ISOs can be
built with it and ISO testing happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076929
Title:
[SRU] Rebuild cd-boot-images-{amd64,arm64} against new shim
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cd-boot-images-amd64/+bug/2076929/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
