[Bug 2083736] Re: Update auf die Neue LTS Version wegen SIGNAL nicht möglich. Deinstalieren von SIGNAL reicht nicht aus um den Fehler zu umgehen.
https://updates.signal.org/desktop/apt ist noch irgendwo in /etc/apt/sources.list oder unterhalb /etc/apt/sources.list.d hinterlegt, bitte den Eintrag löschen. (the https://updates.signal.org/desktop/apt source is still configured and presumably broken key) ** 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/2083736 Title: Update auf die Neue LTS Version wegen SIGNAL nicht möglich. Deinstalieren von SIGNAL reicht nicht aus um den Fehler zu umgehen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
** Also affects: firefox (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/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2083538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately
FWIW, the message in the "terse" UI in 2.9.x is "Not upgrading yet due to phasing:" It's a particular challenge to get it into terse UI, as we need to start with a verb in progressive form (well here it's negated), stating the action we will (not) take. Though arguably it has a second form. If we start with an adjective, it states a notice about something related to the transaction that will not take effect such as "Suggested packages". We could also state "Phased upgrades (available soon)" "Upcoming upgrades (in phased rollout)" "Upcoming upgrades, in phased rollout" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1988819 Title: When apt keeps back packages due to phased updates, it should list them separately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately
@jwms It's particularly difficult to get the message correctly, the feature is known as "phased updates", hence it's worded such that you can search "Ubuntu phasing" and get decent results. If we set "staged rollout", you could not find results for it. A "phased rollout" might work. If we literally said "The following phased updates will become available soon" or something, we'd run afoul of terminology issues: In APT we say "upgrades", not "updates" ("update" updates the metadata), and I did not want to introduce "Phased upgrades" as secondary vernacular. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1988819 Title: When apt keeps back packages due to phased updates, it should list them separately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081714] Re: upgrading process crash and restore previous version
*** This bug is a duplicate of bug 2083068 *** https://bugs.launchpad.net/bugs/2083068 This is a bit hard to figure out but it seems to be the same issue as 2083068, i.e. libglib2.0-dev:i386 has wrong dependencies, you could try removing it to upgrade. ** This bug has been marked a duplicate of bug 2083068 Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081714 Title: upgrading process crash and restore previous version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081986] Re: upgrade from 22.04 to 24.04 failed
Several core system packages have been replaced by Pop!OS packages as such we cannot provide support. ** 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/2081986 Title: upgrade 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/2081986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052381] Re: [grub-mkconfig] Unable to modify current generating grub.cfg
I suggest submitting this to upstream (git-send-email to grub- de...@gnu.org), this is not worth diverging on downstream. ** Changed in: grub2 (Ubuntu) Status: Confirmed => 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/2052381 Title: [grub-mkconfig] Unable to modify current generating grub.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2052381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083027] Re: lubuntu: pipewire vs pulseaudio
** Summary changed: - Upgrade to Noble Failed + lubuntu: pipewire vs pulseaudio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083027 Title: lubuntu: pipewire vs pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083568] Re: full system freezes and needs to be hard rebooted
** Package changed: ubuntu-release-upgrader (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083568 Title: full system freezes and needs to be hard rebooted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2083568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083575] Re: failed upgrade left apt sources on wrong release
This is a funny instance where ubuntu-minimal isn't even installed, so after upgrading the sources we don't see one, so we fail a step too early with a crash instead of doing a clean rollback. ** Tags added: rls-nn-incoming ** Changed in: ubuntu-release-upgrader (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/2083575 Title: failed upgrade left apt sources on wrong release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083576] Re: failed upgrade, unhelpful looping
*** This bug is a duplicate of bug 2081323 *** https://bugs.launchpad.net/bugs/2081323 ** This bug has been marked a duplicate of bug 2081323 Local-only mirror disabled; no mirror left -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083576 Title: failed upgrade, unhelpful looping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083604] Re: aaa
This is a network configuration issue, or an issue with your name servers themselves, your DNS servers failed to resolve the domain name: 2024-10-03 13:20:24,629 DEBUG error from httplib: '' You might want to retry at some point ** 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/2083604 Title: aaa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083529] Re: networkd-dispatcher: scripts not executed for renamed interfaces
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083529 Title: networkd-dispatcher: scripts not executed for renamed interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/2083529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
To the best of my knowledge the issue started happening when the kernel was upgraded. That being said, the Firefox process that seemingly causes stalls is a snap so it is using its own mesa and not the host one, and I can't speak to the snap's mesa version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083626] Re: package grub-pc 2.12-1ubuntu7 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1
There appears to be a local configuration/state issue: mdadm: /dev/md does not appear to be an md device ** Changed in: grub2 (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/2083626 Title: package grub-pc 2.12-1ubuntu7 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2083626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083640] Re: problem to upgrade from distr 20.04 to 22.04
*** This bug is a duplicate of bug 2081323 *** https://bugs.launchpad.net/bugs/2081323 Please switch to an official mirror to upgrade. ** This bug has been marked a duplicate of bug 2081323 Local-only mirror disabled; no mirror left -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083640 Title: problem to upgrade from distr 20.04 to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083646] Re: Upgrade to Ubuntu from 22.04 to 24.04.1
*** This bug is a duplicate of bug 2078639 *** https://bugs.launchpad.net/bugs/2078639 ** This bug has been marked a duplicate of bug 2078639 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/2083646 Title: Upgrade to Ubuntu from 22.04 to 24.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083655] Re: package not available in my nearest server for Pakistan
*** This bug is a duplicate of bug 2081323 *** https://bugs.launchpad.net/bugs/2081323 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 2081323 Local-only mirror disabled; no mirror left -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083655 Title: package not available in my nearest server for Pakistan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083538] [NEW] amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
Public bug reported: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular third-party-packages wayland-session ** Attachment added: "PreviousBootDmesg.txt" https://bugs.launchpad.net/bugs/2083538/+attachment/5824189/+files/PreviousBootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076419] Re: lxml: Does not respect compiler flags
I have improved the test case now. I wasn't aware you can copy it back from the rejected queue (or forgot), and I irregularly delete past uploads, so that could have meant recreating it. Most of the time, if a test plan is lacking a bit, the SRU gets accepted with a note to add some missing bits to the test plan. ** Description changed: [Impact] The packaging does not respect compiler flags, notably hardening flags like the stack protector, as well as frame pointer, as it never uses dpkg-buildflags and is still old manual style. This means there is a higher security risk, which given the nature of the library seems ill-advised, and the lack of frame pointers hampers profiling. [Test plan] Look at the build log and see that the build flags have been passed, notably stuff like - -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -O2 -Werror=implicit-function-declaration -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=for - mat-security -fcf-protection + -fno-strict-overflow + -Werror=implicit-function-declaration + -fno-omit-frame-pointer + -mno-omit-leaf-frame-pointer + -fstack-protector-strong + -fstack-clash-protection + -Wformat + -Werror=for - Parse some xml and see that it works + Run https://gist.github.com/julian- + klode/85e3f85c410a1b856a93dce77208 on the ELF binaries and ensure + that all lines have -fno-omit-frame-pointer + + + Run a smoke test to see the parser still works: + + from lxml import etree + from urllib.request import urlopen + + with urlopen("https://www.w3.org/TR/REC-xml/REC-xml-20081126.xml";) as xml: + xml=xml.read() + tree=etree.fromstring(xml, base_url="https://www.w3.org/TR/REC-xml/REC-xml-20081126.xml";) + + for element in tree.iter(): + print(element) + + print(etree.tostring(tree)) + [Where problems could occur] Hardening flags could surface existing (possibly security) bugs that have been asymptomatic so far; frame pointers will incur some slow down. ** Description changed: [Impact] The packaging does not respect compiler flags, notably hardening flags like the stack protector, as well as frame pointer, as it never uses dpkg-buildflags and is still old manual style. This means there is a higher security risk, which given the nature of the library seems ill-advised, and the lack of frame pointers hampers profiling. [Test plan] - Look at the build log and see that the build flags have been passed, notably stuff like + Skim at the build log and see that the build flags have been passed, notably stuff like -fno-strict-overflow -Werror=implicit-function-declaration -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fstack-protector-strong - -fstack-clash-protection - -Wformat + -fstack-clash-protection + -Wformat -Werror=for Run https://gist.github.com/julian- klode/85e3f85c410a1b856a93dce77208 on the ELF binaries and ensure that all lines have -fno-omit-frame-pointer - Run a smoke test to see the parser still works: from lxml import etree from urllib.request import urlopen with urlopen("https://www.w3.org/TR/REC-xml/REC-xml-20081126.xml";) as xml: - xml=xml.read() + xml=xml.read() tree=etree.fromstring(xml, base_url="https://www.w3.org/TR/REC-xml/REC-xml-20081126.xml";) for element in tree.iter(): - print(element) + print(element) print(etree.tostring(tree)) - [Where problems could occur] Hardening flags could surface existing (possibly security) bugs that have been asymptomatic so far; frame pointers will incur some slow down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076419 Title: lxml: Does not respect compiler flags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxml/+bug/2076419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083468] Re: upgrade from 22.04 to 24.04 fails
Core system packages have been replaced by Pop!OS components which 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/2083468 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/2083468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080656] Re: cannot upgrade from 22.04 to 24.04.1 : update-manager is marked for removal and in the no-removal list
Core system packages have been replaced by ones from Pop!OS, as such 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/2080656 Title: cannot upgrade from 22.04 to 24.04.1 : update-manager is marked for removal and in the no-removal list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078464] Re: Erroneous 'restart required' messages during distro-upgrade
** Changed in: update-manager-core (Ubuntu) Status: New => Triaged ** Tags added: rls-oo-incoming ** Package changed: update-manager-core (Ubuntu) => update-manager (Ubuntu) ** Package changed: update-manager (Ubuntu) => update-notifier (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078464 Title: Erroneous 'restart required' messages during distro-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2078464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1997882] Re: do-release-upgrade fails for point release
It's neither clear what is being upgraded (from -> to), nor what the actual encountered error message is. ** Changed in: usrmerge (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/1997882 Title: do-release-upgrade fails for point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usrmerge/+bug/1997882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080801] Re: Error: The Non-Volatile Variable Storage is About Full
As in the other bug report closed earlier; I don't see the point of this bug. The title is about full nvram; that's entirely unrelated to acpi- call, and the null pointer dereference you hit you already filed. Filled up NVRAM is also nothing we can help you with. ** Changed in: acpi-call (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/2080801 Title: Error: The Non-Volatile Variable Storage is About Full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/2080801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080541] Re: Failed upgrade from 22.04.4 LTS to 24.04.1 LTS due to gconf2 "dependency problems".
We have unpacked a new psmisc, but then as part of gir1.2-nma4-1.0:amd64 configuration, the gconf2 triggers are being run, and gconf2 depends on psmisc, but psmisc has not been configured yet. This may be an internal ordering bug in dpkg, but also gconf2 should have been removed, not kept installed. ** Also affects: dpkg (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/2080541 Title: Failed upgrade from 22.04.4 LTS to 24.04.1 LTS due to gconf2 "dependency problems". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2080541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069433] Re: Enabling new pockets does not enable deb-src for them, even if source code is enabled
I forgot to verify it when I was in the vicinity of my noble system and other stuff took the priority over setting up a new desktop VM so far. But I can try tomorrow, unless you have a noble machine around where you can just follow the steps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069433 Title: Enabling new pockets does not enable deb-src for them, even if source code is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2069433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078464] Re: Erroneous 'restart required' messages during distro-upgrade
Thanks, I put that on the consideration for reworking the reboot experience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078464 Title: Erroneous 'restart required' messages during distro-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2078464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083313] Re: Ubuntu budgie: PulseAudio vs PipeWire
** Summary changed: - cannot upgrade to 24.04 + Ubuntu budgie: PulseAudio vs PipeWire ** Summary changed: - Ubuntu budgie: PulseAudio vs PipeWire + Ubuntu budgie: PulseAudio vs PipeWire fight -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083313 Title: Ubuntu budgie: PulseAudio vs PipeWire fight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083439] Re: não atualiza da versao 22 para a versão ubuntu 24
*** 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/2083439 Title: não atualiza da versao 22 para a versão ubuntu 24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829893] Re: Default redis-sentinel config has incorrect comments
Redis doesn't have a maintainer to speak of, I subscribed at some point as I run it on my server, but it is "community-maintained" and there is no one looking at it specifically that I am aware of, so it is up to the people who want something fixed to fix it themselves. As in, familiarize yourself with the SRU process in https://canonical- sru-docs.readthedocs-hosted.com/en/latest/, prepare updated packages, and request sponsoring for them using https://wiki.ubuntu.com/SponsorshipProcess -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829893 Title: Default redis-sentinel config has incorrect comments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1829893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080217] Re: upgrade problem 22.04 to 24.04.1
You cannnot manage packages with Discover in parallel to upgrading your system. ** 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/2080217 Title: upgrade problem 22.04 to 24.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083286] Re: cannot upgrade to 24.01
Your mirror was broken at this point: 2024-10-01 08:05:28,397 DEBUG examining: 'deb http://mirrors.layeronline.com/ubuntu/ jammy main restricted' 2024-10-01 08:05:28,397 DEBUG verifySourcesListEntry: deb http://mirrors.layeronline.com/ubuntu/ noble main restricted 2024-10-01 08:05:28,398 DEBUG url_downloadable: http://mirrors.layeronline.com/ubuntu//dists/noble/Release 2024-10-01 08:05:28,398 DEBUG s='http' n='mirrors.layeronline.com' p='/ubuntu//dists/noble/Release' q='' f='' 2024-10-01 08:05:28,457 DEBUG error from httplib: 'HTTP Error 403: Forbidden' It dsoes appear to be working now from a cursory look. ** 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/2083286 Title: cannot upgrade to 24.01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080751] Re: Upgrade prematurely terminated.
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' If after this you still cannot upgrade, please open a new bug. ** 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/2080751 Title: Upgrade prematurely terminated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080675] Re: do-release-upgrade from 18.04 to 22.04
It seems you have some weird file system layout: Can't rename /bin: Invalid cross-device link at /usr/lib/usrmerge/convert-usrmerge line 255. Please include the output of ls -l / /usr mount ** Package changed: ubuntu-release-upgrader (Ubuntu) => usrmerge (Ubuntu) ** Changed in: usrmerge (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/2080675 Title: do-release-upgrade from 18.04 to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usrmerge/+bug/2080675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078470] Re: Rather silly suggestions at release-upgrade in case of insufficient space
** Changed in: update-manager-core (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/2078470 Title: Rather silly suggestions at release-upgrade in case of insufficient space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager-core/+bug/2078470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083305] Re: Could not calculate the upgrade because 'update-manager' is marked for removal
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' If after this you still cannot upgrade, please open a new bug. (Particularly I see a weird failure to keep grub installed) ** 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/2083305 Title: Could not calculate the upgrade because 'update-manager' is marked for removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080567] Re: Erreur pour mise à niveau nouvelle version LTS
You'll want to back up your database, remove postgres, upgrade, and install a Postgres supported in 24.04. Note that you have several very outdated postgres installed such as 9.5 which have not been included in a release for a long time. ** 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/2080567 Title: Erreur pour mise à niveau nouvelle version LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080779] Re: upgrade from 22.04 to 24.04 crashes
*** This bug is a duplicate of bug 2078639 *** https://bugs.launchpad.net/bugs/2078639 ** This bug has been marked a duplicate of bug 2078639 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/2080779 Title: upgrade from 22.04 to 24.04 crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080710] Re: after upgrade to 24.04 problem with snap
Your disk appears to be broken, please check if it is correctly attached, and if so, purchase a new one and reinstall. You can see it both in the terminal output: dpkg-deb (subprocess): decompressing archive '/tmp/apt-dpkg-install-s3S2hs/23-snapd_2.63.1+24.04_amd64.deb' (size=28042126) member 'data.tar': zstd error: Restored data doesn't match checksum dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive /tmp/apt-dpkg-install-s3S2hs/23-snapd_2.63.1+24.04_amd64.deb (--unpack): cannot copy extracted data for './usr/share/doc/snapd/changelog.gz' to '/usr/shar as well as by all the spamming in dmesg of corrected errors: [77837.531643] pcieport :00:1c.7: device [8086:9d17] error status/mask=0001/2000 [77837.531659] pcieport :00:1c.7:[ 0] RxErr [77862.530982] pcieport :00:1c.7: AER: Corrected error message received from :00:1c.7 [77862.531015] pcieport :00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [77862.531025] pcieport :00:1c.7: device [8086:9d17] error status/mask=0001/2000 [77862.531037] pcieport :00:1c.7:[ 0] RxErr [77897.525095] pcieport :00:1c.7: AER: Corrected error message received from :00:1c.7 [77897.525111] pcieport :00:1c.7: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [77897.525114] pcieport :00:1c.7: device [8086:9d17] error status/mask=0001/2000 [77897.525116] pcieport :00:1c.7:[ 0] RxErr ** 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/2080710 Title: after upgrade to 24.04 problem with snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080769] Re: Update auf 24.04. wurde unterbrochen
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' If after this you still cannot upgrade, please open a new bug. ** 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/2080769 Title: Update auf 24.04. wurde unterbrochen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080770] Re: I can´t upgrade from 24.04 to 24.04.1 distribution
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' If after this you still cannot upgrade, please open a new bug. ** 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/2080770 Title: I can´t upgrade from 24.04 to 24.04.1 distribution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080867] Re: An unresolvable problem occurred while calculating the upgrade. (from 22.04 to 24.04.1)
Core system packages have been replaced with ones from Pop!Os, as such we will not further investigate this report. ** 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/2080867 Title: An unresolvable problem occurred while calculating the upgrade. (from 22.04 to 24.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080781] Re: Essai de passage sur Ubuntu 24.04
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' If after this you still cannot upgrade, please open a new bug. ** 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/2080781 Title: Essai de passage sur Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083285] Re: Ever Diminishing support for lenovo Helix 2
While this is sad, this is a bug tracker, and not a place to just go rant. For constructive bug reports, please file individual bug reports per issue, optimally assigned to the right packages. Which you state you already did, anyway. ** Changed in: grub2 (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/2083285 Title: Ever Diminishing support for lenovo Helix 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2083285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083280] Re: malformed entry 1 in sources file /etc/apt sources.list.d/third-party.sources (URI parse) E: the list of sources could not be read
For support in how to configure sources, please consult a support resource. Please note that third-party.sources uses the newer deb822 .sources format, not the legacy .list format; for further information, see `man sources.list`. ** 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/2083280 Title: malformed entry 1 in sources file /etc/apt sources.list.d/third- party.sources (URI parse) E: the list of sources could not be read To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083275] Re: Upgrade to 24.04LTS not possible because of Postgres-12
You already received all instructions and reasoning should need by the tool: > To prevent data loss, postgresql packages are not removed automatically during the upgrade. If you are certain you no longer need postgresql-12, you can manually remove it and try the upgrade again.' Now of course if you still need PostgreSQL you need to back up your database, remove it, upgrade, install new version, and restore the database ** 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/2083275 Title: Upgrade to 24.04LTS not possible because of Postgres-12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083247] Re: This Bug is collectet automatically while acualising the System
*** This bug is a duplicate of bug 2081323 *** https://bugs.launchpad.net/bugs/2081323 You are using an unofficial mirror, it got disabled during the upgrade, leaving no mirror enabled to fetch the new release from. ** This bug has been marked a duplicate of bug 2081323 Local-only mirror disabled; no mirror left -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083247 Title: This Bug is collectet automatically while acualising the System To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083247/+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
The other one got remangled into an analysis of nvme links disappearing. Either way, the problem remains, the partition to install on is tied to the physical hardware, not the file system. ** This bug is no longer a duplicate of bug 2083176 grub-efi/install_devices becoming stale due to by-id/nvme-eui.* symlinks disappearing -- 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 2081008] Re: I am facing problem while upgrading from ubuntu22 to ubuntu24, it gives some message like "Could not calculate the upgrade An unresolvable problem occurred while calculating the upgr
For data safety reasons we do not upgrade Postgres between major versions / remove postgres during upgrades. You'll want to ensure your database is backed up, remove postgres packages, upgrade, install the latest postgres and restore. ** 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/2081008 Title: I am facing problem while upgrading from ubuntu22 to ubuntu24, it gives some message like "Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. The package postgresql-16-postgis-1' is marked for removal but it is in the removal deny list. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at main.log and apt. log" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081075] Re: Upgrade button exits silently from 22.04 to 24.04
You are not authorized to execute this commannd Sep 18 10:38:23 username-Virtual-Machine pkexec[6823]: username: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/home/username] [COMMAND=/usr/bin/do-release-upgrade --frontend=DistUpgradeViewGtk3 --env=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus,XDG_SESSION_TYPE=x11,XDG_CURRENT_DESKTOP=ubuntu:GNOME] ** Also affects: update-manager (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/2081075 Title: Upgrade button exits silently from 22.04 to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081143] Re: Upgrading to server 24.04 aborts
For some reason the logs from /var/log/dist-upgrade are missing, without them, we can't analyse the bug. ** 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/2081143 Title: Upgrading to server 24.04 aborts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081102] Re: upgrade 22.04 to 24.04.1 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/2081102 Title: upgrade 22.04 to 24.04.1 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081164] Re: OS Upgrade to current version failed.
*** This bug is a duplicate of bug 2081323 *** https://bugs.launchpad.net/bugs/2081323 ** This bug has been marked a duplicate of bug 2081323 Local-only mirror disabled; no mirror left -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081164 Title: OS Upgrade to current version failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081323] Re: Local-only mirror disabled; no mirror left
** Summary changed: - distro upgrade failed when checking for ubuntu-minimal package being present + Local-only mirror disabled; no mirror left -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081323 Title: Local-only mirror disabled; no mirror left To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081175] Re: Cannot uppgrade from 22.04 to 24.04
For some reason you have installed grub-efi-amd64:i386 and grub2-common:i386 and possibly more, please try to reinstall them on amd64. It's not clear how you ended up in that state but this is clearly wrong. ** 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/2081175 Title: Cannot uppgrade from 22.04 to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081225] Re: 24 LTS upgrade broke my Ubuntu 22 OS - lost data & had to rebuild from scratch; OS locks up ~ 50 % of the time when asking for file actions: like copy to or just opening a flash driv
It seems your system is slow, but I can't say why. Note that your sda1 disk is corrupted: Sep 19 10:56:08 hostname kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. I assume that is your flash drive. I also see a couple of nouveau bugs, and most importantly, nouveau is the thing hanging in the thing. ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081225 Title: 24 LTS upgrade broke my Ubuntu 22 OS - lost data & had to rebuild from scratch; OS locks up ~ 50 % of the time when asking for file actions: like copy to or just opening a flash drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081316] Re: upgrade from 22.04 to 24.04, an error " Could not install 'libapache2-mod-wsgi-py3"
Sadly the postinst doesn't actually produce an error message. dpkg: error processing package libapache2-mod-wsgi-py3 (--configure): installed libapache2-mod-wsgi-py3 package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081316 Title: upgrade from 22.04 to 24.04, an error " Could not install 'libapache2-mod-wsgi-py3" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081297] Re: while upgrade ubuntu via 'software updater' receive an error
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' If after this you still cannot upgrade, please open a new bug. ** 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/2081297 Title: while upgrade ubuntu via 'software updater' receive an error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078354] Re: Broken nautilus-share:amd64 Depende on samba:amd64 < 2:4.15.13+dfsg-0ubuntu1.6 @ii umR >
** Summary changed: - It does not made the upgrade fromo 22.04 to 24.04 + Broken nautilus-share:amd64 Depende on samba:amd64 < 2:4.15.13+dfsg-0ubuntu1.6 @ii umR > ** Description changed: - No se ha podido calcular la actualización + [Impact] + The solver ends up in a sort of endless loop trying to change nautilus-share:amd64 and keep it back alternatingly, to then be terminated at the 19th iteration (its limit). - Se produjo un problema irresoluble al calcular la actualización. + Investigating (19) nautilus:amd64 < 1:42.6-0ubuntu1 -> 1:46.2-0ubuntu0.2 @ii umU Ib > + Broken nautilus:amd64 Rompe on nautilus-share:amd64 < 0.7.3-2ubuntu6 | 0.7.5-0.3build2 @ii umH > (< 0.7.3-2ubuntu7~) + Considering nautilus-share:amd64 0 as a solution to nautilus:amd64 9 + Upgrading nautilus-share:amd64 due to Breaks field in nautilus:amd64 + Investigating (19) nautilus-share:amd64 < 0.7.3-2ubuntu6 -> 0.7.5-0.3build2 @ii umU Ib > + Broken nautilus-share:amd64 Depende on samba:amd64 < 2:4.15.13+dfsg-0ubuntu1.6 @ii umR > + Considering samba:amd64 752 as a solution to nautilus-share:amd64 0 + MarkKeep nautilus-share:amd64 < 0.7.3-2ubuntu6 -> 0.7.5-0.3build2 @ii umU Ib > FU=0 + Holding Back nautilus-share:amd64 rather than change samba:amd64 - Esto podría deberse a: - * Paquetes de software no oficiales, no proporcionados por Ubuntu - Utilice la herramienta «ppa-purge» desde el paquete - ppa-purge para quitar software de una PPA de Launchpad PPA e - intente actualizar de nuevo. - Si nada de esto es aplicable, entonces informe de este error usando el - comando «ubuntu-bug ubuntu-release-upgrader-core» en una terminal. Si - quiere investigar el problema por su cuenta, los registros en - «/var/log/dist-upgrade» contienen detalles de la actualización; en - particular, consulte «main.log» y «apt.log». + [Meta data] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 5.15.0-119.129-generic 5.15.160 Uname: Linux 5.15.0-119-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 16:34:54 2024 InstallationDate: Installed on 2017-05-19 (2658 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=es_ES.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=es_ES.UTF-8 + SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-08-29 (0 days ago) VarLogDistupgradeAptHistorylog: - Start-Date: 2024-08-29 16:33:29 - Requested-By: juan (1000) - End-Date: 2024-08-29 16:33:29 + Start-Date: 2024-08-29 16:33:29 + Requested-By: juan (1000) + End-Date: 2024-08-29 16:33:29 VarLogDistupgradeApttermlog: - Log started: 2024-08-29 16:33:29 - Log ended: 2024-08-29 16:33:29 + Log started: 2024-08-29 16:33:29 + Log ended: 2024-08-29 16:33:29 VarLogDistupgradeTermlog: - - mtime.conffile..etc.update-manager.release-upgrades: 2024-08-29T16:28:17.430070 + + mtime.conffile..etc.update-manager.release-upgrades: + 2024-08-29T16:28:17.430070 -- 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: Broken nautilus-share:amd64 Depende on samba:amd64 < 2:4.15.13+dfsg-0ubuntu1.6 @ii umR > 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 2081323] Re: distro upgrade failed when checking for ubuntu-minimal package being present
You are using a local mirror, which is disabled on upgrades. Normally I believe we'd then use the default mirror; however, it may be that because the esm.ubuntu.com urls were rewritten that the fallback does not trigger, and hence you end up without any sources for the new release. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Triaged ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081323 Title: distro upgrade failed when checking for ubuntu-minimal package being present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081406] Re: Could not upgrade to 24.04
*** This bug is a duplicate of bug 2078354 *** https://bugs.launchpad.net/bugs/2078354 ** This bug has been marked a duplicate of bug 2078354 Broken nautilus-share:amd64 Depende on samba:amd64 < 2:4.15.13+dfsg-0ubuntu1.6 @ii umR > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081406 Title: Could not upgrade to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081583] Re: 22.04 to 24.04 error
*** This bug is a duplicate of bug 2078354 *** https://bugs.launchpad.net/bugs/2078354 This runs out of iterations trying to change nautilus-share vs samba back and forth. ** 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/2081583 Title: 22.04 to 24.04 error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081432] Re: system update to 24.04.1 - installed linux-image-5.15.0-121-generic package post-removal script subprocess returned error exit status 127
/etc/grub.d/bin/grubcfg_proxy is a third-party program. ** 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/2081432 Title: system update to 24.04.1 - installed linux-image-5.15.0-121-generic package post-removal script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081587] Re: While I am upgrading my ubuntu 22.04 to 24.0 the upgrade fails
The main log is missing the lines: 2024-09-30 13:39:45,515 ERROR Dist-upgrade failed: 'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.' 2024-09-30 13:39:45,525 DEBUG abort called 2024-09-30 13:39:45,526 DEBUG openCache() 2024-09-30 13:39:46,995 DEBUG Comparing 6.5.0-45 with 2024-09-30 13:39:46,996 DEBUG Comparing 6.8.0-40 with 6.5.0-45 2024-09-30 13:39:46,996 DEBUG Comparing 6.8.0-45 with 6.8.0-40 2024-09-30 13:39:47,081 DEBUG /openCache(), new cache size 93666 Log time: 2024-09-30 13:39:33.294648 Log time: 2024-09-30 13:39:35.338162 Log time: 2024-09-30 13:39:41.381399 But yes I can reproduce this ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081587 Title: While I am upgrading my ubuntu 22.04 to 24.0 the upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081591] Re: Unable to upgrade to newer version
Your mirror is out of date, please configure a new one. ** 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/2081591 Title: Unable to upgrade to newer version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081607] Re: upgrade from 2022.04.1 to 2024.04.1 fails
These are not failure messages but debugging messages. For data safety reasons we do not upgrade Postgres between major versions / remove postgres during upgrades. You'll want to ensure your database is backed up, remove postgres packages, upgrade, install the latest postgres and restore. ** 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/2081607 Title: upgrade from 2022.04.1 to 2024.04.1 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081614] Re: I'm trying upgrade to Ubuntu 24.04 from 22.04 and one error related to postgres16 is announced.
For data safety reasons we do not upgrade Postgres between major versions / remove postgres during upgrades. You'll want to ensure your database is backed up, remove postgres packages, upgrade, install the latest postgres and restore. ** 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/2081614 Title: I'm trying upgrade to Ubuntu 24.04 from 22.04 and one error related to postgres16 is announced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081623] Re: Can't upgrade to 24.04
2024-09-22 14:08:49,162 DEBUG error from httplib: '' Your domain name resolution is broken. ** 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/2081623 Title: Can't upgrade to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081638] Re: when I try to open Discover, it begins to act like it will open, but then terminates the process.
For snaps to be shown in discover, plasma-discover-backend-snap needs to be installed. ** Package changed: ubuntu-release-upgrader (Ubuntu) => plasma-discover (Ubuntu) ** Changed in: plasma-discover (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/2081638 Title: when I try to open Discover, it begins to act like it will open, but then terminates the process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/2081638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Cross-grades/replacements are considered replacement packages
** Description changed: [Impact] Some packages such as libcap2-bin or ghostscript-x get replaced by cross-graded/or cross-replacement packages, such as libcap2-bin:amd64 => libcap2-bin:i386 ghostscript-x:amd64 => ghostscript:i386 (should be ghostscript:amd64) [Test plan] - Ensure the apt-clone tarballs in this bug and bug 2081864 (ghostscript) - can be properly upgraded/upgrade resolution completes. + Ensure the apt-clone tarballs in this bug can be properly + upgraded/upgrade resolution completes. - A quick validation is to + A quick validation is to 1. start a container 2. replace its /var/lib/dpkg/status with /var/lib/apt-clone/dpkg-status 3. check that do-release-upgrade fails 4. check that do-release-upgrade -p gets to the install prompt A more extensive E2E validation is to fully restore the tarball in a VM, - and then actually execute the full upgrade and not just calculate it. - + and then actually execute the full upgrade and not just calculate it, + but this seems superfluous. [Where problems could occur] We are skipping removals for packages where the only detected replacement packages are for another architecture; there could be problems if there are packages that really only have replacements on a different architecture. - [Original bug report] Hello ubuntu devs, Trying to upgrade from mantic to noble but my system has broken packages. About 93 now. Before they were almost 200 I tried removing some broken packages and made some mistakes on the way I guess. The point is that I also have some fundamental packages in broken state. For instance, python3 and I cannot remove it since it depends on grub-common. The error from /var/log/dist-upgrade is: # grep 'E:' main.log 2024-09-24 18:26:37,663 ERROR Dist-upgrade failed: 'E:Unable to correct problems, you have held broken packages.' I tried many things, I checked with dpkg --get-selections if I had hold packages and I did not have. My last try was to mark as "hold" grub packages: # apt-mark showhold grub-efi-amd64-bin grub-efi-amd64-signed Could you please give a hand on this one? Thank you very much in advance! ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.14 ProcVersionSignature: Ubuntu 6.5.0-44.44-generic 6.5.13 Uname: Linux 6.5.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:115:325160:2024-09-23 19:38:03.393134716 +0200:2024-09-23 19:37:57.853134596 +0200:/var/crash/_usr_sbin_thermald.0.crash 640:1000:115:933873:2024-09-22 13:47:22.006442070 +0200:2024-09-22 13:47:23.006442070 +0200:/var/crash/_usr_bin_light-locker.1000.crash CurrentDesktop: KDE Date: Tue Sep 24 18:33:04 2024 InstallationDate: Installed on 2016-03-16 (3114 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2024-09-24 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-09-24 18:25:07 Requested-By: beatpanic (1000) End-Date: 2024-09-24 18:25:07 VarLogDistupgradeApttermlog: Log started: 2024-09-24 18:25:07 Log ended: 2024-09-24 18:25:07 ** Description changed: [Impact] Some packages such as libcap2-bin or ghostscript-x get replaced by cross-graded/or cross-replacement packages, such as libcap2-bin:amd64 => libcap2-bin:i386 ghostscript-x:amd64 => ghostscript:i386 (should be ghostscript:amd64) + + The 2nd case is actually fine (the result is marking ghostscript-x for + removal, but the correct replacement exists), but the first one, the one + in this bug, breaks upgrades (there may be more instances) [Test plan] Ensure the apt-clone tarballs in this bug can be properly upgraded/upgrade resolution completes. A quick validation is to 1. start a container 2. replace its /var/lib/dpkg/status with /var/lib/apt-clone/dpkg-status 3. check that do-release-upgrade fails 4. check that do-release-upgrade -p gets to the install prompt A more extensive E2E validation is to fully restore the tarball in a VM, and then actually execute the full upgrade and not just calculate it, but this seems superfluous. [Where problems could occur] We are skipping removals for packages where the only detected replacement packages are for another architecture; there could be problems if there are packages that really only have replacements on a different architecture. [Original bug report] Hello ubuntu devs, Trying to upgrade from mantic to noble but my system has broken packages. About 93 now. Before they were almost 200 I tried removing some broken packages and made some mistakes on the way I guess. The point is that I also have some f
[Bug 2081680] Re: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Pleas
** This bug is no longer a duplicate of bug 2081864 Cross-grades/replacements are considered replacement packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081680 Title: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081654] Re: upgrading 22.04 LTS to 24.04 LTS
You have added `[arch=amd64]` to your Ubuntu sources, that is not supported. You need to either remove all i386 packages (apt remove ?installed?architecture(i386)') and then run `dpkg --remove-architecture i386` or keep i386 enabled for your Ubuntu sources. ** 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/2081654 Title: upgrading 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/2081654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081680] Re: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Pleas
*** This bug is a duplicate of bug 2081864 *** https://bugs.launchpad.net/bugs/2081864 This is another instance of bug 2081864, for a different package (ghostscript-x instead of libcap2-bin) ** This bug has been marked a duplicate of bug 2081864 Cross-grades are considered replacement packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081680 Title: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Cross-grades are considered replacement packages
** Description changed: + [Impact] + Some packages such as libcap2-bin or ghostscript-x get replaced by cross-graded/or cross-replacement packages, such as + + libcap2-bin:amd64 => libcap2-bin:i386 + ghostscript-x:amd64 => ghostscript:i386 (should be ghostscript:amd64) + + [Test plan] + + Ensure the apt-clone tarballs in this bug and bug 2081864 (ghostscript) + can be properly upgraded/upgrade resolution completes. + + A quick validation is to + 1. start a container + 2. replace its /var/lib/dpkg/status with /var/lib/apt-clone/dpkg-status + 3. check that do-release-upgrade fails + 4. check that do-release-upgrade -p gets to the install prompt + + A more extensive E2E validation is to fully restore the tarball in a VM, + and then actually execute the full upgrade and not just calculate it. + + + [Where problems could occur] + We are skipping removals for packages where the only detected replacement packages are for another architecture; there could be problems if there are + packages that really only have replacements on a different architecture. + + + [Original bug report] Hello ubuntu devs, Trying to upgrade from mantic to noble but my system has broken packages. About 93 now. Before they were almost 200 I tried removing some broken packages and made some mistakes on the way I guess. The point is that I also have some fundamental packages in broken state. For instance, python3 and I cannot remove it since it depends on grub-common. The error from /var/log/dist-upgrade is: # grep 'E:' main.log 2024-09-24 18:26:37,663 ERROR Dist-upgrade failed: 'E:Unable to correct problems, you have held broken packages.' I tried many things, I checked with dpkg --get-selections if I had hold packages and I did not have. My last try was to mark as "hold" grub packages: # apt-mark showhold grub-efi-amd64-bin grub-efi-amd64-signed Could you please give a hand on this one? Thank you very much in advance! ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.14 ProcVersionSignature: Ubuntu 6.5.0-44.44-generic 6.5.13 Uname: Linux 6.5.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: - 640:0:115:325160:2024-09-23 19:38:03.393134716 +0200:2024-09-23 19:37:57.853134596 +0200:/var/crash/_usr_sbin_thermald.0.crash - 640:1000:115:933873:2024-09-22 13:47:22.006442070 +0200:2024-09-22 13:47:23.006442070 +0200:/var/crash/_usr_bin_light-locker.1000.crash + 640:0:115:325160:2024-09-23 19:38:03.393134716 +0200:2024-09-23 19:37:57.853134596 +0200:/var/crash/_usr_sbin_thermald.0.crash + 640:1000:115:933873:2024-09-22 13:47:22.006442070 +0200:2024-09-22 13:47:23.006442070 +0200:/var/crash/_usr_bin_light-locker.1000.crash CurrentDesktop: KDE Date: Tue Sep 24 18:33:04 2024 InstallationDate: Installed on 2016-03-16 (3114 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2024-09-24 (0 days ago) VarLogDistupgradeAptHistorylog: - Start-Date: 2024-09-24 18:25:07 - Requested-By: beatpanic (1000) - End-Date: 2024-09-24 18:25:07 + Start-Date: 2024-09-24 18:25:07 + Requested-By: beatpanic (1000) + End-Date: 2024-09-24 18:25:07 VarLogDistupgradeApttermlog: - Log started: 2024-09-24 18:25:07 - Log ended: 2024-09-24 18:25:07 + Log started: 2024-09-24 18:25:07 + Log ended: 2024-09-24 18:25:07 ** Summary changed: - Cross-grades are considered replacement packages + Cross-grades/replacements are considered replacement packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081864 Title: Cross-grades/replacements are considered replacement packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081681] Re: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Pleas
*** This bug is a duplicate of bug 2081864 *** https://bugs.launchpad.net/bugs/2081864 ** This bug is no longer a duplicate of bug 2081680 Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. ** This bug has been marked a duplicate of bug 2081864 Cross-grades are considered replacement packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081681 Title: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081681] Re: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Pleas
*** This bug is a duplicate of bug 2081864 *** https://bugs.launchpad.net/bugs/2081864 ** This bug has been marked a duplicate of bug 2081680 Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081681 Title: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083176] Re: grub-efi install device being prompted on upgrade, despite only /boot/efi being an option.
That's correct yes; if the option hasn't been set yet, and /boot/efi is mounted, it migrates /boot/efi into it: # We either migrate /boot/efi over, or we check if we have invalid devices if [ -z "$RET" ] && [ "$seen" != "true" ]; then echo "Trying to migrate /boot/efi into esp config" esp="$(get_mounted_device /boot/efi)" if [ "$esp" ]; then esp="$(device_to_id "$esp")" fi if [ "$esp" ]; then db_set grub-efi/install_devices "$esp" db_fset grub-efi/install_devices seen true RET="$esp" fi else for device in $RET; do if [ ! -e "${device%,}" ]; then valid=0 break fi done fi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083176 Title: grub-efi install device being prompted on upgrade, despite only /boot/efi being an option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2083176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Cross-grades are considered replacement packages.
** Summary changed: - Upgrade from mantic to noble aborted. Broken packages + Cross-grades are considered replacement packages. ** Summary changed: - Cross-grades are considered replacement packages. + Cross-grades are considered replacement packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081864 Title: Cross-grades are considered replacement packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081844] Re: do-release-upgrade does not work (22.4.5 -> 24.4.1)
*** 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/2081844 Title: do-release-upgrade does not work (22.4.5 -> 24.4.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081854] Re: Latest upgrade caused issues
/etc/grub.d/bin/grubcfg_proxy is a third-party binary that is failing. ** 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/2081854 Title: Latest upgrade caused issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Upgrade from mantic to noble aborted. Broken packages
Notably this was actually the main culprit, and I verified the fix allows upgrading ** Also affects: ubuntu-release-upgrader (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) 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/2081864 Title: Upgrade from mantic to noble aborted. Broken packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081864] Re: Upgrade from mantic to noble aborted. Broken packages
This seems to be the culprit: MarkInstall libqt5quick5-gles:amd64 < 5.15.10+dfsg-2 -> 5.15.13+dfsg-2 @ii umU Ib > FU=0 Installing libqt5gui5-gles:amd64 as Depends of libqt5quick5-gles:amd64 MarkKeep libqt5gui5t64:amd64 < none -> 5.15.13+dfsg-1ubuntu1 @un umN > FU It's not clear to me why this happens, but this is blocking libqt5gui5t64:amd64 from being installed which then later leads to hilarious conflicts. Likewise MarkDelete libcap2-bin:amd64 < 100:2.48-1 @ii mK NPb Ib > FU=1 seems wrong as well, the culprit for that is funny: 2024-09-24 18:26:04,453 DEBUG Found replacement libcap2-bin:i386 for libcap2-bin I am going to use this bug to track the 2nd issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081864 Title: Upgrade from mantic to noble aborted. Broken packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081880] Re: trying to upgrade from xubuntu 22.04 to 24.04
You had a network outage 2024-09-25 02:34:22,944 DEBUG s='http' n='my.archive.ubuntu.com' p='/ubuntu//dists/noble/Release' q='' f='' 2024-09-25 02:36:38,923 DEBUG error from httplib: '' ** 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/2081880 Title: trying to upgrade from xubuntu 22.04 to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081887] Re: Upgrade to Ubuntu 24.02
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/2081887 Title: Upgrade to Ubuntu 24.02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081887/+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 bug is a duplicate of bug 2083176 *** https://bugs.launchpad.net/bugs/2083176 Apologies there was some misunderstanding here, in that /boot/efi is the only option. I am going to mark this as a duplicate of bug 2083176, my general perspective is: If we had one partition configured before, and /boot/efi is the only option now, then we should automatically select /boot/efi. If we had multiple targets selected before, then we still need to prompt (or fail in non-interactive mode), the failure scenario there would otherwise be: 1. You accidentally unplug disk 2 2. A grub update silently reconfigures to install to disk 1 only 3. You notice disk 2 is unplugged, plug it back in (or replace it with a new disk 2) 4. Disk 2 is never being updated again Scary! ** This bug has been marked a duplicate of bug 2083176 grub-efi install device being prompted on upgrade, despite only /boot/efi being an option. -- 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 2081956] Re: do-release-upgrade does not work (22.4.5 -> 24.4.1)
*** 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/2081956 Title: do-release-upgrade does not work (22.4.5 -> 24.4.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083176] Re: grub-efi install device being prompted on upgrade, despite only /boot/efi being an option.
It's possible that there were two ESPs configured, and we must not silently downgrade to a single ESP, so we must count how many ESPs were previously configured. ** Summary changed: - grub-efi install device being prompted on upgrade + grub-efi install device being prompted on upgrade, despite only /boot/efi being an option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083176 Title: grub-efi install device being prompted on upgrade, despite only /boot/efi being an option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2083176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083068] Re: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH >
** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083068 Title: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2083068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083068] Re: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH >
For oracular is the solution architecture-properties? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083068 Title: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2083068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083068] Re: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH >
Tracking Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > here. Which happens due to Depends: python3 | qemu-user | qemu-user-static in libglib2.0-dev:i386 (thanks helmut). i.e. it says python3 needs to be the same architecture, or you need qemu-user to execute bits. For reasons of lazyness I'd propose changing this to: Depends: python3:amd64 [i386] | python3 | qemu-user | qemu-user-static This ensures we do not enter the broken python3:i386 code path. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Triaged => Won't Fix ** Changed in: glib2.0 (Ubuntu) Status: New => Triaged ** Also affects: glib2.0 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Noble) 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/2083068 Title: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2083068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083068] Re: upgrading distribution process crash and restore previous version of Ubuntu
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Triaged ** Summary changed: - upgrading distribution process crash and restore previous version of Ubuntu + Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083068 Title: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083120] Re: Unable to upgrade to 24.04 on System76 Laptop
Closing this as systemd is installed from Pos!OS (in version 249.11-0ubuntu3.11pop0~1704473387~22.04~3ce38bf~dev), we cannot support systems with core packages replaced by third-party repositories. ** 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/2083120 Title: Unable to upgrade to 24.04 on System76 Laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083091] Re: The package 'postgresql-14-auto-failover' is marked for removal but it is in the removal deny list.
For reasons of data safety, we do not perform upgrades that would require removing postgres packages; you'll want to manually back up your databases, remove postgres, upgrade, and install the latest and restore the database. ** 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/2083091 Title: The package 'postgresql-14-auto-failover' is marked for removal but it is in the removal deny list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083176] Re: grub-efi install device being prompted on upgrade
In this particular instance, the only option is the partition already mounted at /boot/efi, so in that case it seems sensible to automatically use it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083176 Title: grub-efi install device being prompted on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2083176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082162] Re: after updating , brightness is not working
Brightness is managed by gnome-settings-daemon. This report seems similar to bug 2081294 which was reported for oracular and fixed in 47.1. I haven't checked if noble also is affected, but either way we need more information. My suggestion would simply be to run ubuntu-bug 2082162 to attach the data. ** Package changed: gnome-shell (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082162 Title: after updating , brightness is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2082162/+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
Please consult more appropriate venues for user support, this is a bug tracker. If you remove your ESP, do not set up a new /boot/efi mount, the correct behavior for the upgrade is to fail as it cannot safely guess a new one. -- 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 2081546] Re: package grub-pc 2.12-1ubuntu7 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1
This seems to be some hackery on the local system - an interactive shell appears instead of the postinst: Setting up grub-pc (2.12-1ubuntu7) ... [?2004h]0;root@Latitude-5330: /root@Latitude-5330:/# ls [?2004l [0m[01;36mbin[0m[01;34metc[0m [01;34mlib.usr-is-merged[0m [01;34mopt[0m [01;34msbin.usr-is-merged[0m [01;34musr[0m [01;34mbin.usr-is-merged[0m [01;34mhome[0m [01;36mlibx32[0m [01;34mproc[0m [01;34msnap[0m[01;34mvar[0m [01;34mboot[0m [01;36mlib[0m[01;34mlost+found[0m [01;34mroot[0m [01;34msrv[0m [01;34mcdrom[0m [01;36mlib32[0m [01;34mmedia[0m [01;34mrun[0m [01;34msys[0m [01;34mdev[0m[01;36mlib64[0m [01;34mmnt[0m [01;36msbin[0m [30;42mtmp[0m [?2004h]0;root@Latitude-5330: /root@Latitude-5330:/# exit [?2004l exit dpkg: error processing package grub-pc (--configure): installed grub-pc package post-installation script subprocess returned error exit status 1 ** Changed in: grub2 (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/2081546 Title: package grub-pc 2.12-1ubuntu7 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2081546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081640] Re: Upgrade to the Kubuntu 24.10 beta errors out complaining that the 24.10 kernel does not support ZFS
zfs is not usually loaded in the kernel if no zfs file systems are used but it may perhaps be loaded for other reasons, and/or you have zfs- utils installed in which case I think it may be warranted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081640 Title: Upgrade to the Kubuntu 24.10 beta errors out complaining that the 24.10 kernel does not support ZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081855] Re: Following recent Ubuntu 24.04.1 LTS upgrade an 'Error: opening the cache'.
** Changed in: apt (Ubuntu) Status: New => Invalid ** Changed in: apt (Ubuntu) Status: Invalid => Incomplete ** Package changed: apt (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/2081855 Title: Following recent Ubuntu 24.04.1 LTS upgrade an 'Error: opening the cache'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2081855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs