[Bug 1936139] Re: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936139 Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1936139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936139] [NEW] package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10
Public bug reported: package looks broken ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 14 10:49:02 2021 Dependencies: ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-07-14 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: chromium-browser Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936139 Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1936139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936137] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: This was automatically generated by my system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 13 23:41:10 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936137 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1936137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936137] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936137 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1936137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936136] [NEW] ceph on bcache performance regression
Public bug reported: Ceph on bcache could have serious performance degradation (10 times drop) when the below two conditions are met: 1. bluefs_buffered_io is turned on 2. Any OSD bcache’s cache_available_percent is less than 60 As many of us may already know that bcache will force all writes to go directly to the backing device when the cache_available_percent is less than CUTOFF_WRITEBACK_SYNC(30). But the thing is that bcache will start to bypass *some* writes when cache_available_percent reached to CUTOFF_WRITEBACK(60), and those are the writes that are not carrying any synchronization flags. Those are kernel IO flags: REQ_SYNC, REQ_FUA, REQ_PREFLUSH. The code is here https://github.com/torvalds/linux/blob/master/drivers/md/bcache/writeback.h#L123 The problem I found from a recent case (bionic-stein + 4.15 kernel) is that when bluefs are submitting writes with bluefs_buffered_io turned on, the writes that send to bcache won’t carry any of the sync flags, and when the cache_available_percent dropped lower than 60 (which is quite easy to hit), all bluefs IO will be forced to be performed in a non-writeback mode. This is equivalent to setting up the bluestore DB on an HDD device, so every IO is bounded by the HDD speed. I’m not sure How the sync flags are propagated from ceph all the way to the kernel bcache layer. But I’ve verified all different ceph/kernel/ubuntu versions when bluefs_buffered_io turned on: N: no issue, all writes contain SYNC flag. P: has the issue, disable bluefs_buffered_io works. Bionic-ussuri + kernel 5.4.0 -> N Bionic-ussuri + kernel 4.15.0 -> P Bionic-stein + kernel 5.4.0 -> N Bionic-stein + kernel 4.15.0 -> P Bionic-train + kernel 5.4.0 -> N Bionic-train + kernel 4.15.0 -> P Focal(octopus) + kernel 5.4.0 -> N Focal(octopus) + kernel 5.8.0 -> N Focal-wallaby + kernel 5.4.0 -> N Focal-wallaby + kernel 5.8.0 -> N As we can see the issue appears to hit when bluefs_buffered_io = true and the kernel with 4.15.0. I’m not sure how/why the SYNC flag is added in the 5.4 or 5.8 kernel when bluefs_buffered_io is enabled. Currently, I know 5.4 and 5.8 are good when bluefs_buffered_io is turned on. Note that if all OSDs are deployed with separate NVME as the bluestore DB device, then the cluster won’t hit the issue, only those OSDs that put bluestore DB on bcache device will hit this issue. Ceph releases with bluefs_buffered_io enabled by default: bluefs_buffered_io was enabled by default in v13.2.0 and v14.2.0. bluefs_buffered_io was disabled by default in v14.2.10 and v15.2.0. bluefs_buffered io was re-enabled in the following point releases: v14.2.22 v15.2.13 v16.2.0 So in a summary, if all below 3 are met, this cluster will very likely hit the issue when any OSD bcache has the cache_available_percent dropped to 60: 1. ceph has bluefs_buffered_io enabled 2. OSDs are putting bluestore DB on top of bcache device 3. kernel version is bionic-ga (4.15.0) ** Affects: ceph (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/1936136 Title: ceph on bcache performance regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1936136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935728] Re: [radeon] Mouse pointer randomly disappears - other mouse operations still work
Yes. Please try logging into 'Ubuntu on Wayland' and tell us if it hits the same issue eventually. More interruptive but also useful to know, please try other desktop environments like: sudo apt install unity-session sudo apt install xfce4-session sudo apt install cinnamon-session and then you can select which one on the login screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935728 Title: [radeon] Mouse pointer randomly disappears - other mouse operations still work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1935728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927660] Re: Update from 18.04 to 20.04 fails to calculate
Plague meant I started the update, and have only now been able to get back to text if it worked. It did. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927660 Title: Update from 18.04 to 20.04 fails to calculate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1927660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935728] Re: [radeon] Mouse pointer randomly disappears - other mouse operations still work
Are there any tests I can do? Tried a few different blue tooth mouses - same result. Slowed the mouse speed, changed screen resolution - same result. Can't find a pattern as to what triggers this - sometimes heavy usage, some times very little. I'm happy to run any diagnostics - if we can't resolve this I will have to look at getting a different hardware but would like to keep using this if we can resolve it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935728 Title: [radeon] Mouse pointer randomly disappears - other mouse operations still work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1935728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936047] Re: [snap] GUI not show. Opening Thunderbird snap causes 2 processes to open (Ubuntu 21.04)
** Description changed: In a laptop Thinkpad t14s AMD 4750 PRO (Renoir GPU) with Ubuntu 21.04 (5.11.0-22-generic) When opening Thunderbird Snap, from GUI menu or from command line, 2 processes are opened, and the program GUI is not displayed. eduardo@edu-ThinkPad-T14s:~$ pgrep -a thunderbird 9173 /snap/thunderbird/127/thunderbird-bin 9253 /snap/thunderbird/127/thunderbird-bin + Killing the last process allows the program GUI to start fully and be + displayed. - Killing the last process allows the program GUI to start fully and be displayed. Thunderbird Snap version: - NameVersion Rev Tracking Publisher - thunderbird 78.11.0 12 latest/stable canonical✓ + NameVersion.Rev.Tracking.Publisher + thunderbird 78.11.0 12 latest/stable canonical✓ + Here are the jurnalctl -t audit -f logs jul 13 21:38:41 edu-ThinkPad-T14s audit[8630]: AVC apparmor="DENIED" operation="capable" profile="/snap/snapd/12398/usr/lib/snapd/snap-confine" pid=8630 comm="snap-confine" capability=4 capname="fsetid" jul 13 21:38:47 edu-ThinkPad-T14s audit[8630]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.thunderbird.thunderbird pid=8630 comm=64636F6E6620776F726B6572 exe="/snap/thunderbird/127/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7f5c7f6b1639 code=0x5 jul 13 21:41:32 edu-ThinkPad-T14s audit[9016]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=9016 comm="MainThread" exe="/snap/firefox/558/firefox-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fd5bdfa8639 code=0x5 jul 13 21:43:54 edu-ThinkPad-T14s audit[9173]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.thunderbird.thunderbird pid=9173 comm=64636F6E6620776F726B6572 exe="/snap/thunderbird/127/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fc72440b639 code=0x5 jul 13 21:53:44 edu-ThinkPad-T14s audit[9788]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.thunderbird.thunderbird pid=9788 comm=64636F6E6620776F726B6572 exe="/snap/thunderbird/127/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7f09bf711639 code=0x5 + After killing the last process the GUI its fully loaded and thunderbird + snap work. - After killing the last process the GUI its fully loaded and thunderbird snap work. - - This is a related Answer form Launchpad + This is a related Answer form Launchpad https://answers.launchpad.net/snappy/+question/697307 Maybe its something with new amdgpu drivers, since in another laptop (thinkpad t460 intel with Ubuntu 21.04) this does not happen. ** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936047 Title: [snap] GUI not show. Opening Thunderbird snap causes 2 processes to open (Ubuntu 21.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1936047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936051] [NEW] [snap] GUI not show. Opening LibreOffice snap causes 2 processes to open (Ubuntu 21.04)
Public bug reported: In a laptop Thinkpad t14s AMD 4750 PRO (Renoir GPU) with Ubuntu 21.04 (5.11.0-22-generic) When opening ANY LibreOffice app as a Snap, from GUI menu or from command line, 2 processes are opened, and the program GUI is not displayed. eduardo@edu-ThinkPad-T14s:~$ pgrep -a soffice 10612 /snap/libreoffice/223/lib/libreoffice/program/soffice.bin --writer 10613 /snap/libreoffice/223/lib/libreoffice/program/soffice.bin --writer eduardo@edu-ThinkPad-T14s:~$ pgrep -a soffice 10803 /snap/libreoffice/223/lib/libreoffice/program/soffice.bin --impress 10804 /snap/libreoffice/223/lib/libreoffice/program/soffice.bin --impress eduardo@edu-ThinkPad-T14s:~$ pgrep -a soffice 11002 /snap/libreoffice/223/lib/libreoffice/program/soffice.bin --calc 11003 /snap/libreoffice/223/lib/libreoffice/program/soffice.bin --calc Killing the last process of any LibreOffice app allows the program GUI to start fully and be displayed. LibreOffice Snap version: NameVersion.Rev.Tracking Publisher thunderbird 78.11.0 12 latest/stable canonical✓ Here are the jurnalctl -t audit -f logs jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin" exe="/snap/libreoffice/223/lib/libreoffice/program/soffice.bin" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fa1753ecc7f code=0x5 jul 13 22:14:31 edu-ThinkPad-T14s audit[11213]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.libreoffice.writer pid=11213 comm="soffice.bin"
[Bug 1923195] Re: Impossible to upgrade from 18.04 to 20.04.2
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923195 Title: Impossible to upgrade from 18.04 to 20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923293] Re: upgrade from Ubuntu studio 18.04 to 20.04 failed
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923293 Title: upgrade from Ubuntu studio 18.04 to 20.04 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923351] Re: cant upgrade from 18.04 to 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923351 Title: cant upgrade from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923353] Re: My xubuntu don't want to update itself (sorry for english)
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923353 Title: My xubuntu don't want to update itself (sorry for english) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923600] Re: Cannot upgrade to LTS 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923600 Title: Cannot upgrade to LTS 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923650] Re: unable to upgrade ubuntu from version 18.04 to 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923650 Title: unable to upgrade ubuntu from version 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923713] Re: Upgrade to Ubuntu 20.04.2 from 18.04 fails- Can't calculate the upgrade
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923713 Title: Upgrade to Ubuntu 20.04.2 from 18.04 fails- Can't calculate the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923681] Re: upgrader aborts with "could not calculate the upgrade"
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923681 Title: upgrader aborts with "could not calculate the upgrade" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923875] Re: Cannot upgrade a fresh install of bionic
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923875 Title: Cannot upgrade a fresh install of bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924196] Re: can't upgrade to new LTS and ppa-purge didn't help
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924196 Title: can't upgrade to new LTS and ppa-purge didn't help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924239] Re: upgrade to ubuntu20.04 from 18.04 failed
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924239 Title: upgrade to ubuntu20.04 from 18.04 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924736] Re: imposible upgrade ubuntu 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924736 Title: imposible upgrade ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924769] Re: MS Azure 20.04 release upgrade fails
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924769 Title: MS Azure 20.04 release upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924783] Re: 5.8.0-49 broke the OS
[Expired for linux-signed-hwe-5.8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924783 Title: 5.8.0-49 broke the OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1924783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924892] Re: An unresolvable problem occurred while calculating the upgrade.
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924892 Title: An unresolvable problem occurred while calculating the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924909] Re: crashed on upgrade from 18.04 to 20.XX
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924909 Title: crashed on upgrade from 18.04 to 20.XX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924929] Re: Upgrade from 18.04 to 20.04 fails. Purged all PPA's
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924929 Title: Upgrade from 18.04 to 20.04 fails. Purged all PPA's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924937] Re: Can't update to 20.04 lts
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924937 Title: Can't update to 20.04 lts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924972] Re: update impossible
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924972 Title: update impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925070] Re: upgrade 18.04 to 20.04 fails
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925070 Title: upgrade 18.04 to 20.04 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1925070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925250] Re: do-release-upgrade cannot calculate upgrade to 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925250 Title: do-release-upgrade cannot calculate upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1925250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925426] Re: unresolvable problem occurred while calculating upgrade
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925426 Title: unresolvable problem occurred while calculating upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1925426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925504] Re: Se produjo un problema irresoluble al calcular la actualización (do-release-upgrade error)
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925504 Title: Se produjo un problema irresoluble al calcular la actualización (do- release-upgrade error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1925504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925960] Re: upgrade from 18.04 to 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925960 Title: upgrade from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1925960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925980] Re: cant upgrade
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925980 Title: cant upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1925980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926057] Re: nextcloud crashes with SIGSEV
[Expired for nextcloud-desktop (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nextcloud-desktop (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926057 Title: nextcloud crashes with SIGSEV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1926057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926077] Re: Unable to upgrade from 18.04 to 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926077 Title: Unable to upgrade from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926091] Re: Attempt to upgrade to 20.04 LTS from 18.04 LTS. Fails on suspected PPA anomaly.
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926091 Title: Attempt to upgrade to 20.04 LTS from 18.04 LTS. Fails on suspected PPA anomaly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926328] Re: upgrade from 18.04 to 20.04 failed
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926328 Title: upgrade from 18.04 to 20.04 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926152] Re: version upgrade did not work
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926152 Title: version upgrade did not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926349] Re: crash upgrade 18.04 to 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926349 Title: crash upgrade 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926367] Re: Unable to update from 18.04 to 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926367 Title: Unable to update from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926542] Re: failed 20.04 upgrade fom 18.04; all ppas removed; update is current
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926542 Title: failed 20.04 upgrade fom 18.04; all ppas removed; update is current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926645] Re: update fails from 18 to 20 but everything is ok
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926645 Title: update fails from 18 to 20 but everything is ok To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926761] Re: ubuntu-release-upgrader-core
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926761 Title: ubuntu-release-upgrader-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926842] Re: An unresolvable problem occurred while calculating the upgrade from 18.04 to 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926842 Title: An unresolvable problem occurred while calculating the upgrade from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926876] Re: issues upgrading from 18.04.05 LTS to 20.04.02
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926876 Title: issues upgrading from 18.04.05 LTS to 20.04.02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926924] Re: Failed upgrade from 18.04 LTS to 20.04 LTS
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926924 Title: Failed upgrade from 18.04 LTS to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926945] Re: Kernel 5.8.0.50 fails to boot
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926945 Title: Kernel 5.8.0.50 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927068] Re: i cannot do upgrade to focal fossa becouse thirdy party app in my system
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927068 Title: i cannot do upgrade to focal fossa becouse thirdy party app in my system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1927068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927073] Re: Upgrade from 18.04.5 LTS to 20.04.32 failed several times
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927073 Title: Upgrade from 18.04.5 LTS to 20.04.32 failed several times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1927073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927190] Re: I can't upgrade my Ubuntu 18.04 to 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927190 Title: I can't upgrade my Ubuntu 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1927190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927245] Re: attempting to upgrade to 20.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927245 Title: attempting to upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1927245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927268] Re: Upgrading distro invalid packages
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927268 Title: Upgrading distro invalid packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1927268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927660] Re: Update from 18.04 to 20.04 fails to calculate
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927660 Title: Update from 18.04 to 20.04 fails to calculate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1927660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927716] Re: 'ALPS Touchpad' now working on emachines D525
[Expired for linux-signed-hwe-5.8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927716 Title: 'ALPS Touchpad' now working on emachines D525 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1927716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927680] Re: Release 18.04.5 LTS. Could not calculate the upgrade. An unresolvable occureed while calculating the changes.
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927680 Title: Release 18.04.5 LTS. Could not calculate the upgrade. An unresolvable occureed while calculating the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1927680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928338] Re: package openssh-client 1:8.4p1-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928338 Title: package openssh-client 1:8.4p1-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1928338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928189] Re: Facing issue while upgrading from 16 to 18
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928189 Title: Facing issue while upgrading from 16 to 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1928189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936047] Re: [snap] GUI not show. Opening Thunderbird snap causes 2 processes to open (Ubuntu 21.04)
** Summary changed: - [Snap] GUI not show. Opening Thunderbird snap causes 2 processes to open (Ubuntu 21.04) + [snap] GUI not show. Opening Thunderbird snap causes 2 processes to open (Ubuntu 21.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936047 Title: [snap] GUI not show. Opening Thunderbird snap causes 2 processes to open (Ubuntu 21.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1936047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936047] [NEW] [Snap] GUI not show. Opening Thunderbird snap causes 2 processes to open (Ubuntu 21.04)
Public bug reported: In a laptop Thinkpad t14s AMD 4750 PRO (Renoir GPU) with Ubuntu 21.04 (5.11.0-22-generic) When opening Thunderbird Snap, from GUI menu or from command line, 2 processes are opened, and the program GUI is not displayed. eduardo@edu-ThinkPad-T14s:~$ pgrep -a thunderbird 9173 /snap/thunderbird/127/thunderbird-bin 9253 /snap/thunderbird/127/thunderbird-bin Killing the last process allows the program GUI to start fully and be displayed. Thunderbird Snap version: NameVersion Rev Tracking Publisher thunderbird 78.11.0 12 latest/stable canonical✓ Here are the jurnalctl -t audit -f logs jul 13 21:38:41 edu-ThinkPad-T14s audit[8630]: AVC apparmor="DENIED" operation="capable" profile="/snap/snapd/12398/usr/lib/snapd/snap-confine" pid=8630 comm="snap-confine" capability=4 capname="fsetid" jul 13 21:38:47 edu-ThinkPad-T14s audit[8630]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.thunderbird.thunderbird pid=8630 comm=64636F6E6620776F726B6572 exe="/snap/thunderbird/127/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7f5c7f6b1639 code=0x5 jul 13 21:41:32 edu-ThinkPad-T14s audit[9016]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.firefox.firefox pid=9016 comm="MainThread" exe="/snap/firefox/558/firefox-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fd5bdfa8639 code=0x5 jul 13 21:43:54 edu-ThinkPad-T14s audit[9173]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.thunderbird.thunderbird pid=9173 comm=64636F6E6620776F726B6572 exe="/snap/thunderbird/127/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fc72440b639 code=0x5 jul 13 21:53:44 edu-ThinkPad-T14s audit[9788]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.thunderbird.thunderbird pid=9788 comm=64636F6E6620776F726B6572 exe="/snap/thunderbird/127/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7f09bf711639 code=0x5 After killing the last process the GUI its fully loaded and thunderbird snap work. This is a related Answer form Launchpad https://answers.launchpad.net/snappy/+question/697307 Maybe its something with new amdgpu drivers, since in another laptop (thinkpad t460 intel with Ubuntu 21.04) this does not happen. ** Affects: thunderbird (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/1936047 Title: [Snap] GUI not show. Opening Thunderbird snap causes 2 processes to open (Ubuntu 21.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1936047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731916] Re: ifupdown integration does not start ovs daemon
This bug was fixed in the package openvswitch - 2.15.1-0ubuntu1 --- openvswitch (2.15.1-0ubuntu1) impish; urgency=medium [ Christian Ehrhardt ] * New upstream minor release 2.15.1 * drop d/p/ovs-dev-ovs-ctl-Allow-recording-hostname-separately.patch which is upstream in 2.15.1 * d/control: python3-six bdep is no more needed * drop d/p/py3-compat.patch as upstream switched to python3 in 2.15.1 [ James Page ] * d/ifupdown.sh: Correct paths for systemctl and the openvswitch-switch systemd unit for ifupdown integration (LP: #1731916). -- Christian Ehrhardt Tue, 13 Jul 2021 14:58:38 +0200 ** Changed in: openvswitch (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731916 Title: ifupdown integration does not start ovs daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1731916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935892] Re: OEM 5.6 kernel is now transited to 5.10 but pre-signed nvidia is not and cause no nvidia driver after oem kernel transition
** Changed in: linux-restricted-modules-oem-5.6 (Ubuntu) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-restricted-modules-oem-5.6 (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/1935892 Title: OEM 5.6 kernel is now transited to 5.10 but pre-signed nvidia is not and cause no nvidia driver after oem kernel transition To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1935892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933415] Re: Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0.
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ iwlwifi may encounter firmware crash when running 5.13 kernel with
+ outdated firmware.
+
+ [Fix]
+
+ Commit 2b13afc1a0ff82 ("iwlwifi: add new FWs from core60-51 release")
+ added new rev -63 firmware.
+
+ [Test Case]
+
+ 1. disconnect/connect stress
+
+$ sudo add-apt-repository ppa:checkbox-dev/ppa
+$ sudo apt install plainbox-provider-checkbox
+$ checkbox-cli run
com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress
+
+ignore connect bluetooth part, and set the SSID and password to
+ proceed.
+
+ 2. suspend/resume stress
+
+$ for i in $(seq 200); do \
+echo "Round $i..."; \
+nmcli d; \
+sleep 15; \
+rtcwake -m mem -s 15; \
+done
+
+ [Where problems could occur]
+
+ Rev -63 firmware is only used by 5.13 kernel or newer.
+
+ [Other Info]
+
+ While 5.13 kernel is only available in Focal and Impish, only Focal is
+ nominated here.
+
+ == original bug description ==
+
[Reproduce steps]
1. disconnect/connect stress
$ sudo add-apt-repository ppa:checkbox-dev/ppa
$ sudo apt install plainbox-provider-checkbox
$ checkbox-cli run
com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress
ignore connect bluetooth part, and set the SSID and password to proceed.
2. suspend/resume stress
$ for i in $(seq 200); do \
- echo "Round $i..."; \
- nmcli d; \
- sleep 15; \
- rtcwake -m mem -s 15; \
+ echo "Round $i..."; \
+ nmcli d; \
+ sleep 15; \
+ rtcwake -m mem -s 15; \
done
kernel: iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x0.
[100/1757]
- kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
+ kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
kernel: iwlwifi :03:00.0: Status: 0x0040, count: 6
- kernel: iwlwifi :03:00.0: Loaded firmware version: 59.601f3a66.0
ty-a0-gf-a0-59.ucode
- kernel: iwlwifi :03:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
- kernel: iwlwifi :03:00.0: 0x00A08200 | trm_hw_status0
- kernel: iwlwifi :03:00.0: 0x | trm_hw_status1
- kernel: iwlwifi :03:00.0: 0x004D9BDC | branchlink2
+ kernel: iwlwifi :03:00.0: Loaded firmware version: 59.601f3a66.0
ty-a0-gf-a0-59.ucode
+ kernel: iwlwifi :03:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
+ kernel: iwlwifi :03:00.0: 0x00A08200 | trm_hw_status0
+ kernel: iwlwifi :03:00.0: 0x | trm_hw_status1
+ kernel: iwlwifi :03:00.0: 0x004D9BDC | branchlink2
kernel: iwlwifi :03:00.0: 0x922A | interruptlink1
kernel: iwlwifi :03:00.0: 0x922A | interruptlink2
- kernel: iwlwifi :03:00.0: 0x000161C4 | data1
- kernel: iwlwifi :03:00.0: 0x0010 | data2
- kernel: iwlwifi :03:00.0: 0x | data3
- kernel: iwlwifi :03:00.0: 0x1C405003 | beacon time
- kernel: iwlwifi :03:00.0: 0x72B40004 | tsf low
- kernel: iwlwifi :03:00.0: 0x03E4 | tsf hi
+ kernel: iwlwifi :03:00.0: 0x000161C4 | data1
+ kernel: iwlwifi :03:00.0: 0x0010 | data2
+ kernel: iwlwifi :03:00.0: 0x | data3
+ kernel: iwlwifi :03:00.0: 0x1C405003 | beacon time
+ kernel: iwlwifi :03:00.0: 0x72B40004 | tsf low
+ kernel: iwlwifi :03:00.0: 0x03E4 | tsf hi
kernel: iwlwifi :03:00.0: 0x | time gp1
kernel: iwlwifi :03:00.0: 0x00EF1CDC | time gp2
kernel: iwlwifi :03:00.0: 0x0001 | uCode revision type
kernel: iwlwifi :03:00.0: 0x003B | uCode version major
kernel: iwlwifi :03:00.0: 0x601F3A66 | uCode version minor
kernel: iwlwifi :03:00.0: 0x0420 | hw version
kernel: iwlwifi :03:00.0: 0x00489002 | board version
kernel: iwlwifi :03:00.0: 0x8011001C | hcmd
kernel: iwlwifi :03:00.0: 0xE6863000 | isr0
kernel: iwlwifi :03:00.0: 0x0104 | isr1
kernel: iwlwifi :03:00.0: 0x68FA | isr2
kernel: iwlwifi :03:00.0: 0x00C44C4F | isr3
kernel: iwlwifi :03:00.0: 0x0020 | isr4
kernel: iwlwifi :03:00.0: 0x007C019C | last cmd Id
kernel: iwlwifi :03:00.0: 0x000161C4 | wait_event
kernel: iwlwifi :03:00.0: 0x00D0 | l2p_control
kernel: iwlwifi :03:00.0: 0x00018034 | l2p_duration
kernel: iwlwifi :03:00.0: 0x003F | l2p_mhvalid
kernel: iwlwifi :03:00.0: 0x00CF00F8 | l2p_addr_match
kernel: iwlwifi :03:00.0: 0x0009 | lmpm_pmg_sel
kernel: iwlwifi :03:00.0: 0x |
[Bug 1936019] [NEW] please remove armhf binary (ANAIS)
Public bug reported: https://launchpad.net/ubuntu/+source/atlas-ecmwf/0.25.0-2 dropped support for all 32 bit architectures ** Affects: atlas-ecmwf (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936019 Title: please remove armhf binary (ANAIS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atlas-ecmwf/+bug/1936019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935951] Re: [nvidia] HomeOffice & Un-/Docking: X11 crash on resume when docked to multi monitor
** No longer affects: xorg-server ** No longer affects: xorg-server (Ubuntu) ** Bug watch removed: gitlab.freedesktop.org/xorg/xserver/-/issues #1197 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1197 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935951 Title: [nvidia] HomeOffice & Un-/Docking: X11 crash on resume when docked to multi monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1935951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935882] Autopkgtest regression report (python-pip/20.0.2-5ubuntu1.6)
All autopkgtests for the newly accepted python-pip (20.0.2-5ubuntu1.6) for focal have finished running. The following regressions have been reported in tests triggered by the package: python3.9/3.9.5-3~20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#python-pip [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935882 Title: pypy virtualenv has broken pip on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1935882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936009] Re: The internal mic of Dell Precision 5750 can't record sound
This is the debdiff for focal. thx. ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.9.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1936009/+attachment/5510794/+files/alsa-ucm-conf_1.2.2-1ubuntu0.9.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936009 Title: The internal mic of Dell Precision 5750 can't record sound To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936009] Re: The internal mic of Dell Precision 5750 can't record sound
This is the debdiff for hirsute. thx. ** Patch added: "alsa-ucm-conf_1.2.4-2ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1936009/+attachment/5510793/+files/alsa-ucm-conf_1.2.4-2ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936009 Title: The internal mic of Dell Precision 5750 can't record sound To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936009] Re: The internal mic of Dell Precision 5750 can't record sound
This is the debdiff for impish. thx. ** Description changed: - This bug is for tracking purpose. + [Impact] + After upgrade the linux kernel, the mixer names of rt715 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't record sound from internal mic since the internal mic is routed to the codec rt715. + + [Fix] + Backport 3 upstream commits, after applying these 3 commits, the ucm conf file dosn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. + + [Test] + run 'alsactl init 1' on the precision 5750 with old and new kernel, there is no error logs, use the internal mic to record sound, it could record successfully. + + [Where problems will occur] + The change only affects the rt715 codec, so far, that codec only connects to the internal mic on Dell soundwire audio machines, so it could introduce regression on the internal mic like users can't record sound via internal mic anymore on the Dell soundwire audio machines. But this possibility is very low since we already tested these 3 commits on different Dell soundwire audio machines (latitude and precision). We tested it with old kernel and new kernel, all worked well. ** Patch added: "alsa-ucm-conf_1.2.4-2ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1936009/+attachment/5510792/+files/alsa-ucm-conf_1.2.4-2ubuntu3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936009 Title: The internal mic of Dell Precision 5750 can't record sound To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936012] [NEW] Mate-Dock completely disappears
Public bug reported: After loading the OS on the first mouse action on the desktop, the mate- dock of munity completely disappears from the desktop. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mate-dock-applet (not installed) ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Jul 13 21:21:09 2021 InstallationDate: Installed on 2021-05-09 (65 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210508) SourcePackage: mate-dock-applet UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-dock-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936012 Title: Mate-Dock completely disappears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-dock-applet/+bug/1936012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935882] Re: pypy virtualenv has broken pip on focal
Tests successfully for me, although I have to clear the virtualenv cached eggs with --clear-app-data. We could upload virtualenv to bump the version again, like https://launchpad.net/ubuntu/+source/python- virtualenv/20.0.17-1ubuntu0.3 to make this automatic, and avoid users who have hit the bug, needing to --clear-app-data, to resolve it. ** Description changed: [Impact] - * pypy and pypy3 virtualenvs created with virtualenv have an unuseable + * pypy and pypy3 virtualenvs created with virtualenv have an unuseable pip. [Test Plan] # apt install pypy virtualenv - $ virtualenv -p pypy testve + $ virtualenv -p pypy testve --clear-app-data $ testve/bin/python -m pip Failure: A traceback ending in: ModuleNotFoundError: No module named 'pip._vendor.six' Success: --help output [Where problems could occur] - * This change has been carried in Debian and Ubuntu since 20.1-2, so + * This change has been carried in Debian and Ubuntu since 20.1-2, so it's well tested. It's very simple, and should have been included in the Bug #1904945 SRU [Original Bug report] I reproduced this in a docker image (ubuntu:20.04) Reproduction steps: 1) install `virtualenv` and `pypy` 2) run `virtualenv --python pypy venv` 3) run `venv/bin/pip` This fails with this error output: Traceback (most recent call last): File "venv/bin/pip", line 5, in from pip._internal.cli.main import main File "/venv/site-packages/pip/_internal/cli/main.py", line 10, in from pip._internal.cli.autocompletion import autocomplete File "/venv/site-packages/pip/_internal/cli/autocompletion.py", line 9, in from pip._internal.cli.main_parser import create_main_parser File "/venv/site-packages/pip/_internal/cli/main_parser.py", line 7, in from pip._internal.cli import cmdoptions File "/venv/site-packages/pip/_internal/cli/cmdoptions.py", line 24, in from pip._internal.exceptions import CommandError File "/venv/site-packages/pip/_internal/exceptions.py", line 10, in from pip._vendor.six import iteritems ImportError: No module named pip._vendor.six This should have printed out the usage information for pip. I tried working around this by running `virtualenv --python pypy --download venv`. This allows running just `venv/bin/pip` to succeed, but a typical real usage of it fails like this: # venv/bin/pip install requests DEPRECATION: pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality. Collecting requests Downloading requests-2.25.1-py2.py3-none-any.whl (61 kB) || 61 kB 8.8 MB/s Collecting chardet<5,>=3.0.2 Downloading chardet-4.0.0-py2.py3-none-any.whl (178 kB) || 178 kB 26.8 MB/s Collecting idna<3,>=2.5 Downloading idna-2.10-py2.py3-none-any.whl (58 kB) || 58 kB 9.8 MB/s Collecting urllib3<1.27,>=1.21.1 Downloading urllib3-1.26.6-py2.py3-none-any.whl (138 kB) || 138 kB 43.6 MB/s Collecting certifi>=2017.4.17 Downloading certifi-2021.5.30-py2.py3-none-any.whl (145 kB) || 145 kB 48.1 MB/s Installing collected packages: chardet, idna, urllib3, certifi, requests ERROR: Exception: Traceback (most recent call last): File "/venv/site-packages/pip/_internal/cli/base_command.py", line 223, in _main status = self.run(options, args) File "/venv/site-packages/pip/_internal/cli/req_command.py", line 180, in wrapper return func(self, options, args) File "/venv/site-packages/pip/_internal/commands/install.py", line 404, in run pycompile=options.compile, File "/venv/site-packages/pip/_internal/req/__init__.py", line 90, in install_given_reqs pycompile=pycompile, File "/venv/site-packages/pip/_internal/req/req_install.py", line 824, in install requested=self.user_supplied, File "/venv/site-packages/pip/_internal/operations/install/wheel.py", line 845, in install_wheel requested=requested, File "/venv/site-packages/pip/_internal/operations/install/wheel.py", line 719, in _install_wheel assert os.path.exists(pyc_path) AssertionError This should have installed the requests package, instead of failing. It's worth noting this seems to work with cpython. I specifically tried with python2.7 and the default python3 (python3.8). Using pypy3 fails in the same way. Release info: # lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935882 Title:
[Bug 1932028] Re: missing version dependency on distro-info
This bug was fixed in the package ubuntu-advantage-tools - 27.2~21.10.1 --- ubuntu-advantage-tools (27.2~21.10.1) impish; urgency=medium * d/control: - add comments to explain complex build-depends - add version requirement to distro-info (LP: #1932028) * d/tools.postinst: - run status.json schema patch script to avoid non-root status errors * New upstream release 27.2: - attach: print contract server reason for 403 (GH: #1630) - cli: add ua config set, unset and show subcommands - config: + add default ua_config setting values + only allow some fields to be set by envvar + use defaults for contract and security url - docs: + add proxy config options to man page + add instructions to generate MOTD messages + add support matrix info + remove broken api link - enable: allow downgrading packages during enable (GH: #1659) - fips: + add focal test for fips-updates + alert if wrong fips package installed on gov clouds + install correct fips package on gov clouds + only install conditional_packages if necessary and available - logs: log env vars that affect config on cli runs - proxy: + add config options to set proxies + print message when setting proxy + support configuring apt proxies + support configuring snap and livepatch proxies + support setting proxy for web requests + validate urls before setting as proxies - refresh: support refreshing config and contract separately - status + add config info to json output + add env vars to json output + do not show unavailable services in json output + support yaml format with same content as json format + update account info in json output + update contract info in json output + update root level keys of json output - refactor: + remove side effects from can_enable (GH: #1654, #1571) + use DatetimeAwareJSONDecoder to parse date strings - tests: + add additional enable test for incompatible services + add flag to enable proposed pocket + add test to check and print version being tested + drop trusty specific tests -- Grant Orndorff Fri, 09 Jul 2021 13:07:23 -0400 ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932028 Title: missing version dependency on distro-info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1932028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start
Performing verification for Focal.
I will first reproduce the problem with glib2.0 2.64.6-1~ubuntu20.04.3
from -security with the libglib2.0-0 libglib2.0-bin libglib2.0-data
packages.
I deleted all existing schemas from /usr/share/glib-2.0/schemas and
replaced them with a set of schemas which reproduce the problem easily
from my customer.
$ cd /usr/share/glib-2.0/schemas/
$ sudo rm *
$ sudo cp ~/schemas/* .
The gsettings.compiled from the customer has been corrupted, and when I
reboot, gdm fails to start and I get a blank screen with a blinking
insertion pointer.
The sha256 of the customers corrupted gsettings.compiled is:
$ sudo openssl sha256 /usr/share/glib-2.0/schemas/gschemas.compiled
SHA256(/usr/share/glib-2.0/schemas/gschemas.compiled)=
2c98dc9a7fdbac858a8d5ca7e4dd813f16058a46dba2c54b5239cd8cdba5bb3e
When I ssh back in, and recompile the file:
$ sudo glib-compile-schemas /usr/share/glib-2.0/schemas
Error parsing key “logout” in schema
“org.gnome.settings-daemon.plugins.media-keys” as specified in override file
“/usr/share/glib-2.0/schemas/50_vmware_viewagent.gschema.override”: 0-22:can
not parse as value of type 'as'. Ignoring override for this key.
$ sudo openssl sha256 /usr/share/glib-2.0/schemas/gschemas.compiled
SHA256(/usr/share/glib-2.0/schemas/gschemas.compiled)=
78163b5fefbd6320ce0d355c9531bf657a4f4dc15f057d95ef144323cd56
The sha256 has changed. Doing a bindiff, I see:
$ sudo cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 4F
3771 A4 C2
We see two bytes different. These bytes are the uninitialised memory
this bug is about. When I reboot, gdm starts fine, but that is because
this time I got lucky and the parser for the gschema.compiled file
thinks 4F and C2 are okay. But there are combinations which aren't okay,
and will end up with a corrupted gschema.compiled file.
Re-compiling the file again:
$ sudo glib-compile-schemas /usr/share/glib-2.0/schemas
Error parsing key “logout” in schema
“org.gnome.settings-daemon.plugins.media-keys” as specified in override file
“/usr/share/glib-2.0/schemas/50_vmware_viewagent.gschema.override”: 0-22:can
not parse as value of type 'as'. Ignoring override for this key.
$ sudo openssl sha256 /usr/share/glib-2.0/schemas/gschemas.compiled
SHA256(/usr/share/glib-2.0/schemas/gschemas.compiled)=
460c70faca7afc26fa88a0e5918d312478e15f20ad84f4afaa5d17627a823e01
The sha256 changed, and if we bindiff, the bytes have changed:
$ sudo cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 A6
3771 A4 A1
If we run glib-compile-schemas through valgrind, it reports that we are
writing to uninitialised memory:
https://paste.ubuntu.com/p/sxrQtbswpw/
I then enabled -proposed and installed libglib2.0-0 libglib2.0-bin
libglib2.0-data version 2.64.6-1~ubuntu20.04.4.
Now, when I re-compile the gschemas.compiled file, the sha256 matches
every time, meaning no more non-deterministic behaviour caused by
writing unitialised memory to disk:
$ sudo glib-compile-schemas /usr/share/glib-2.0/schemas
Error parsing key “logout” in schema
“org.gnome.settings-daemon.plugins.media-keys” as specified in override file
“/usr/share/glib-2.0/schemas/50_vmware_viewagent.gschema.override”: 0-22:can
not parse as value of type 'as'. Ignoring override for this key.
$ sudo openssl sha256 /usr/share/glib-2.0/schemas/gschemas.compiled
SHA256(/usr/share/glib-2.0/schemas/gschemas.compiled)=
cd9132d18b596a304251cd1eb50b64aa6fd7511a312906f9a49e1975a319fbf1
$ sudo glib-compile-schemas /usr/share/glib-2.0/schemas
Error parsing key “logout” in schema
“org.gnome.settings-daemon.plugins.media-keys” as specified in override file
“/usr/share/glib-2.0/schemas/50_vmware_viewagent.gschema.override”: 0-22:can
not parse as value of type 'as'. Ignoring override for this key.
$ sudo openssl sha256 /usr/share/glib-2.0/schemas/gschemas.compiled
SHA256(/usr/share/glib-2.0/schemas/gschemas.compiled)=
cd9132d18b596a304251cd1eb50b64aa6fd7511a312906f9a49e1975a319fbf1
Doing a bindiff, I see the changed bytes from before are now all zeros,
which is what the patch initialises the buffer to:
$ sudo cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 00
3771 A4 00
3772 55 00
Doing a run through valgrind, we no longer get a report about writing to
uninitialised memory:
https://paste.ubuntu.com/p/z52DGZcdz3/
Rebooting, the VM comes up and GDM starts properly, so glib can parse
the gsettings.compiled file without any issues.
Wonderful. The problem is fixed by the package in -proposed, happy to
mark as verified.
** Tags removed: sts-sponsor verification-needed verification-needed-focal
** Tags added:
[Bug 1935604] Re: network-manager-applet: stored auto connect VPN gets changed when viewing settings
For anyone who may not want to download the full ova just to see the
bug, I've created a screen recording of the bug as I experience it.
It can be viewed here: https://www.youtube.com/watch?v=RVFoaiHCto8
From the video description to give some context to what I'm
demonstrating in the video:
A demonstration of an nm-connection-editor bug I'm experiencing. For
some reason the saved VPN does not persist across future saves even if I
change nothing in the dialog. Simply saving the dialog is enough to
trick it into swapping behind the scenes.
This video demonstrates 2 things:
1. The first demo shows that when the VPN selected is "Vancouver" then every
time the dialog is saved the stored VPN is changed.
2. When Vancouver is selected it rotates only through "Vancouver", "US West",
and "Corp - UK London"
3. If either of the remaining 2 VPNs are chosen ("Corp - Hong Kong" or "US
East") then they do NOT exhibit the bug.
4. Swapping back to any of the original 3 causes the bug to express again.
To test the bug locally it's enough to create 5 VPNs with the same names
as mine. They need not be fully functional as you don't need to connect
to the VPN to trigger the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935604
Title:
network-manager-applet: stored auto connect VPN gets changed when
viewing settings
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935969] Re: Ubuntu 20.04.2 LTS installer crash when letting the system determine size of additional LV
No, encryption haven’t been enabled. Just a plain vanilla vm with a single disk (hw ver 13, paravirtual scsi controller, thin provisioned disk residing on a Netapp flash SAN). I’ve worked around it already so I don’t have a .crash file at the time of this writing. It’s easily reproduced though so I’ll deploy a new vm in the morning and get you that file. Anything else you know you might need to aid in this investigation? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935969 Title: Ubuntu 20.04.2 LTS installer crash when letting the system determine size of additional LV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1935969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935604] Re: network-manager-applet: stored auto connect VPN gets changed when viewing settings
I've created a virutal machine which expresses the bug in Xubuntu 20.04.02 from a fresh install. You'll need to log in as the user "user" with the password "password". In order to experience the bug you'll need to change and save the VPN once, then you should be able to follow the instructions above. Hopefully having this virtual machine will make it a little easier to identify the cause. I've so far been unable to identify what could possibly be causing it. The VM export in ova format can be found here: http://files.coderjoe.net/Xubuntu.ova -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920675] Re: pypy3 interactively -> help() -> modules => ShimWarning & missing togl
** Changed in: python Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920675 Title: pypy3 interactively -> help() -> modules => ShimWarning & missing togl To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1920675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931531] Re: clisp crashed in impish compiling xindy
Ah so the unrelated reasons would be that glibc snapshot I have in that PPA -- clisp with PIE disabled for s390x and ppc64el built fine in a different PPA and then xindy built with the resulting clisp too so I'll upload that. It would be better to fix this properly by choosing better addresses for clisp but well for now it will do. ** Changed in: xindy (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/1931531 Title: clisp crashed in impish compiling xindy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clisp/+bug/1931531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936009] [NEW] The internal mic of Dell Precision 5750 can't record sound
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: alsa-ucm-conf (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: alsa-ucm-conf (Ubuntu Focal) Importance: High Status: In Progress ** Affects: alsa-ucm-conf (Ubuntu Hirsute) Importance: High Status: In Progress ** Affects: alsa-ucm-conf (Ubuntu Impish) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: oem-priority originate-from-1935805 somerville ** Changed in: alsa-ucm-conf (Ubuntu) Importance: Undecided => High ** Also affects: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Impish) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => High ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Impish) Status: New => In Progress ** Tags added: oem-priority originate-from-1935805 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936009 Title: The internal mic of Dell Precision 5750 can't record sound To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852985] Re: X Error of failed request: BadLength (poly request too large or internal Xlib length error)
I confirm `sudo apt purge fonts-noto-color-emoji` did fix this issue for me. `sudo apt install unifont` did NOT solve it I'm on Kubuntu 20.04 if that matters -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852985 Title: X Error of failed request: BadLength (poly request too large or internal Xlib length error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1852985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931312] Re: i386 version of libpipewire-0.3 for Ubuntu Focal 20.04
Hi, after steam updated today it stopped launching I also have the problem with this file: libpipewire-0.3.so.0 te other file it was asking for I manaed to install. I have tried to --reset steam but I get this error message home/michael/.steam/debian-installation/ubuntu12_32/steam-runtime/setup.sh is missing, this runtime is invalid or corrupted. I have tried following commands: nano ~/.steam/registry.vdf and changed RememberPassword from "1" to "0" but still not working. I also tried to apt purge steam and after apt install steam again for trying to reinstall. Now I am a little stuck on what to try next I am runnin a linux ubuntu 20.04 64bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931312 Title: i386 version of libpipewire-0.3 for Ubuntu Focal 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1931312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932158] Autopkgtest regression report (backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4)
All autopkgtests for the newly accepted backport-iwlwifi-dkms (8324-0ubuntu3~20.04.4) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64, ppc64el, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#backport-iwlwifi-dkms [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932158 Title: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1932158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
Hello Shengyao, or anyone else affected, Accepted alsa-lib into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.1.3-5ubuntu0.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936008] [NEW] Trackpad interfering with trackpoint even when disabled
Public bug reported: I am running Ubuntu 20.04 on a new ThinkPad P14s AMD. I noticed that my trackpoint was very laggy and choppy. After a while I realized that the trackpoint is smooth as long as I am not touching the trackpad (very difficult). Even with the trackpad disabled in GNOME and the BIOS (which seems to only affect Windows) the interference continues. Using the command "libinput debug-events" I can see "POINTER_MOTION" events being registered despite the trackpad being off. This seems to be what is causing the trackpoint lag. Disabling the trackpad in the BIOS does not help. I have the same behaviour on a 21.04 live USB session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 13 19:09:36 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2021-07-08 (5 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1S00C00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=9fdec65c-f9fc-4efc-be65-1f1fba5ad5ba ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET63W(1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1S00C00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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:bvrR1BET63W(1.32):bd04/12/2021:br1.32:efr1.32:svnLENOVO:pn20Y1S00C00:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1S00C00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1S00C00 dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107+git2107030500.9cef5d~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.2~git2107130600.9d225c~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 21.2~git2107130600.9d225c~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal thinkpad third-party-packages trackpoint ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936008 Title: Trackpad interfering with trackpoint even when disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1936008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
@alexander-deucher CPU model: AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx Kernel: 5.10.49 Firmware: VCE feature version: 0, firmware version: 0x UVD feature version: 0, firmware version: 0x MC feature version: 0, firmware version: 0x ME feature version: 52, firmware version: 0x00a4 PFP feature version: 52, firmware version: 0x00bc CE feature version: 52, firmware version: 0x004f RLC feature version: 1, firmware version: 0x0213 RLC SRLC feature version: 1, firmware version: 0x0001 RLC SRLG feature version: 1, firmware version: 0x0001 RLC SRLS feature version: 1, firmware version: 0x0001 MEC feature version: 52, firmware version: 0x01c2 MEC2 feature version: 52, firmware version: 0x01c2 SOS feature version: 0, firmware version: 0x ASD feature version: 0, firmware version: 0x2155 TA RAS feature version: 0x, firmware version: 0x212b TA XGMI feature version: 0x, firmware version: 0x212b TA HDCP feature version: 0x1711, firmware version: 0x212b TA DTM feature version: 0x1203, firmware version: 0x212b SMC feature version: 0, firmware version: 0x1e49 SDMA0 feature version: 41, firmware version: 0x0028 VCN feature version: 0, firmware version: 0x0210c005 DMCU feature version: 0, firmware version: 0x DMCUB feature version: 0, firmware version: 0x VBIOS version: 113-RAVEN-107 Also affected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935969] Re: Ubuntu 20.04.2 LTS installer crash when letting the system determine size of additional LV
Are you enabling encryption in the guided screen? This sort of bug means we are mis-estimating how large the VG is going to be and we've had a few bugs like this in the past but I thought they were mostly fixed. The .crash file from /var/crash would be great help in figuring out what is going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935969 Title: Ubuntu 20.04.2 LTS installer crash when letting the system determine size of additional LV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1935969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821869] Re: bus error in test_gil test on armhf with 64bit kernel
** Changed in: python Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821869 Title: bus error in test_gil test on armhf with 64bit kernel To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1821869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931602] Re: [apparmor] Segfault in logs with apparmor enabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931602 Title: [apparmor] Segfault in logs with apparmor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931602] Re: [apparmor] Segfault in logs with apparmor enabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931602 Title: [apparmor] Segfault in logs with apparmor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927065] Re: ClamTk does not run scan
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927065 Title: ClamTk does not run scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamtk/+bug/1927065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932158] Re: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Hello Kleber, or anyone else affected, Accepted backport-iwlwifi-dkms into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/backport-iwlwifi- dkms/8324-0ubuntu3~20.04.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: backport-iwlwifi-dkms (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932158 Title: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1932158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923162] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted u-boot-menu into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/u-boot- menu/4.0.2ubuntu5~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925267] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted u-boot-menu into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/u-boot- menu/4.0.2ubuntu5~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: u-boot-menu (Ubuntu) Importance: Undecided Status: New ** Changed in: u-boot-menu (Ubuntu) Status: New => Fix Released ** Changed in: u-boot-menu (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925267 Title: u-boot unmatched dtb does not match kernel dtb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1925267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927065] Re: ClamTk does not run scan
Hi @Dave M, Thank you very much for your feedback! @Ubuntu repos maintainer: According to the Debian ClamTk package maintainer, the version in Debian testing/unstable should work. They back-ported the changes and verified that scanning files is possible. That means that ClamTk version 6.03-3, which is currently part of the future 21.10 release and fixes the corresponding Debian bug #981384 (in version 6.03-2) according to its changelog, should work. It would be great if that version 6.03-3 was back-ported to the current 20.04 release, to fix this issue there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927065 Title: ClamTk does not run scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamtk/+bug/1927065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934791] Re: SRU u-boot to focal to enable HiFive Unmatched booting
Hello William, or anyone else affected, Accepted u-boot into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-3ubuntu0~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: u-boot (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934791 Title: SRU u-boot to focal to enable HiFive Unmatched booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1934791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923162] Re: riscv64 images fail to boot in qemu
Hello Dimitri, or anyone else affected, Accepted u-boot into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-3ubuntu0~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: u-boot (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924761] Re: unleashed fails to boot of sd-card with u-boot-sifive from hirsute
Hello Dimitri, or anyone else affected, Accepted u-boot into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-3ubuntu0~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: u-boot (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924761 Title: unleashed fails to boot of sd-card with u-boot-sifive from hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1924761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925267] Re: u-boot unmatched dtb does not match kernel dtb
Hello Dimitri, or anyone else affected, Accepted u-boot into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-3ubuntu0~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: u-boot (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925267 Title: u-boot unmatched dtb does not match kernel dtb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1925267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935882] Re: pypy virtualenv has broken pip on focal
Hello Ben, or anyone else affected, Accepted python-pip into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python- pip/20.0.2-5ubuntu1.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal ** Also affects: python-pip (Ubuntu) Importance: Undecided Status: New ** Changed in: python-pip (Ubuntu) Status: New => Fix Released ** Changed in: python-pip (Ubuntu Focal) Status: New => Fix Committed ** Changed in: python-pip (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935882 Title: pypy virtualenv has broken pip on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1935882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
