[Bug 1895246] Re: Plugin calls the incorrect API
** Changed in: xfce4-weather-plugin (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895246 Title: Plugin calls the incorrect API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1895246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915536] Re: one grub
grub2-unsigned (2.04-1ubuntu44) hirsute; urgency=medium * Compile grub-efi-amd64 installable i386 platform on hirsute, to make it available in bionic and earlier as part of onegrub builds. * Source package generated from src:grub2 using make -f ./debian/rules generate-grub2-unsigned -- Dimitri John Ledkov Wed, 03 Mar 2021 11:42:28 + ** Changed in: grub2-unsigned (Ubuntu Hirsute) 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/1915536 Title: one grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920052] Re: pdftopcf missing
Thank you for your bug report > The package is installed but command-not-found keeps suggesting it. The wording might be a bit confusing but what it states is 'Command 'pdftopcf' not found, did you mean: command 'bdftopcf' from deb xfonts-utils (1:7.7+6)' Basically the pdftopcf command you are trying to use isn't available but it's suggesting bdftopcf which is close enough in naming in case you did a typo and that's what you meant. Checking for pdftopcf on the upstream xorg gitlab has no result, are you sure that utility exists? ** Changed in: xfonts-utils (Ubuntu) Importance: Undecided => Low ** Changed in: xfonts-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920052 Title: pdftopcf missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfonts-utils/+bug/1920052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Autopkgtest regression report (runc/1.0.0~rc93-0ubuntu1~20.04.1)
All autopkgtests for the newly accepted runc (1.0.0~rc93-0ubuntu1~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: golang-github-docker-go-connections/0.4.0-1 (arm64, armhf, ppc64el, amd64, s390x) opengcs/0.3.4+dfsg2-0ubuntu3 (amd64, s390x, arm64, armhf, ppc64el) 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#runc [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/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919322] Autopkgtest regression report (runc/1.0.0~rc93-0ubuntu1~20.04.1)
All autopkgtests for the newly accepted runc (1.0.0~rc93-0ubuntu1~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: golang-github-docker-go-connections/0.4.0-1 (arm64, armhf, ppc64el, amd64, s390x) opengcs/0.3.4+dfsg2-0ubuntu3 (amd64, s390x, arm64, armhf, ppc64el) 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#runc [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/1919322 Title: Backport the container stack in Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1919322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919419] Re: Phishing vulnerability: Template generation allows external parameters to override placeholders
** Changed in: shibboleth-sp (Ubuntu) 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/1919419 Title: Phishing vulnerability: Template generation allows external parameters to override placeholders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shibboleth-sp/+bug/1919419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
** Changed in: xorg-server (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920103] [NEW] package ansible (not installed) failed to install/upgrade: trying to overwrite '/etc/ansible/ansible.cfg', which is also in package ansible-base 2.10.7-1ppa~focal
Public bug reported: Already had ansible-base installed, installing ansible caused an error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ansible (not installed) ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Mar 19 00:34:12 2021 ErrorMessage: trying to overwrite '/etc/ansible/ansible.cfg', which is also in package ansible-base 2.10.7-1ppa~focal InstallationDate: Installed on 2019-11-15 (490 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: ansible Title: package ansible (not installed) failed to install/upgrade: trying to overwrite '/etc/ansible/ansible.cfg', which is also in package ansible-base 2.10.7-1ppa~focal UpgradeStatus: Upgraded to focal on 2020-04-23 (329 days ago) mtime.conffile..etc.ansible.ansible.cfg: 2021-03-15T18:16:19 mtime.conffile..etc.ansible.hosts: 2021-03-15T18:16:19 ** Affects: ansible (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/1920103 Title: package ansible (not installed) failed to install/upgrade: trying to overwrite '/etc/ansible/ansible.cfg', which is also in package ansible-base 2.10.7-1ppa~focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1920103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920104] [NEW] package linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1 failed to install/upgrade: installed linux-image-5.8.0-43-generic package pre-removal script subprocess returned error exit
Public bug reported: not sure if it is a bug, tryng to figure it out ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Mar 18 22:16:18 2021 DpkgHistoryLog: Start-Date: 2021-03-18 22:15:17 Commandline: apt autoremove Requested-By: rdcryptonite (1000) Remove: linux-image-5.8.0-43-generic:amd64 (5.8.0-43.49~20.04.1), linux-modules-extra-5.8.0-43-generic:amd64 (5.8.0-43.49~20.04.1), linux-headers-5.8.0-43-generic:amd64 (5.8.0-43.49~20.04.1), linux-modules-5.8.0-43-generic:amd64 (5.8.0-43.49~20.04.1), linux-hwe-5.8-headers-5.8.0-43:amd64 (5.8.0-43.49~20.04.1) ErrorMessage: installed linux-image-5.8.0-43-generic package pre-removal script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: linux-signed-hwe-5.8 Title: package linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1 failed to install/upgrade: installed linux-image-5.8.0-43-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: 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/1920104 Title: package linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1 failed to install/upgrade: installed linux-image-5.8.0-43-generic package pre- removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1920104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918258] Re: Failure due to "Data files not found"
** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918258 Title: Failure due to "Data files not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libchipcard/+bug/1918258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919985] Re: Sync libchipcard 5.1.5rc2-7 (universe) from Debian unstable (main)
** Changed in: libchipcard (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919985 Title: Sync libchipcard 5.1.5rc2-7 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libchipcard/+bug/1919985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
** Changed in: bluez (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu Groovy) 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918874] Re: [regression] Application windows appear over the icon grid when Ubuntu Dock or Dash To Dock is loaded
** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu) ** No longer affects: gnome-shell-extension-dashtodock (Ubuntu) ** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918874 Title: [regression] Application windows appear over the icon grid when Ubuntu Dock or Dash To Dock is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1918874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
** Changed in: bluez (Ubuntu Groovy) 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/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
** Changed in: flatpak (Ubuntu Bionic) Importance: High => Medium ** Changed in: flatpak (Ubuntu Focal) Importance: High => Medium ** Changed in: flatpak (Ubuntu Groovy) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919044] Re: Dell Inspiron 7567 Freezes/Hangs Randomly
Update: It still crashes even if pstate is disabled. Now I do not know what is going on anymore. This issue never happens in windows. So it definitely is not a hardware issue. When music is played when this happens the music loops to the last few seconds endlessly until I hold the power button. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919044 Title: Dell Inspiron 7567 Freezes/Hangs Randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1919044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920061] Re: when I go to restart it claims there is someone logged in remotely when no one is
Maybe there's a process subtree somewhere that looks like a separate login. What do you get from this command? pstree $USER -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920061 Title: when I go to restart it claims there is someone logged in remotely when no one is To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908677] Re: Dell Latitude 9510 capture volume is too low
** Also affects: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: alsa-ucm-conf (Ubuntu Groovy) 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/1908677 Title: Dell Latitude 9510 capture volume is too low To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912783] Re: west-chamber-dkms fails to build after ip_route_me_harder() signature change
** Changed in: west-chamber (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912783 Title: west-chamber-dkms fails to build after ip_route_me_harder() signature change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/west-chamber/+bug/1912783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910323] Re: Fix implicit declaration warnings for kselftests/memfd test on newer releases
** Description changed:
[Impact]
While debugging bug 1910277, I found that the test compilation will print
some warnings:
memfd_test.c:64:7: warning: implicit declaration of function ‘open’;
memfd_test.c:90:6: warning: implicit declaration of function ‘fcntl’
memfd_test.c:397:6: warning: implicit declaration of function ‘fallocate’;
fuse_test.c:67:6: warning: implicit declaration of function ‘fcntl’
fuse_test.c:261:7: warning: implicit declaration of function ‘open’;
And there is a fix in upstream for this.
[Fix]
* 1c49e3783f8899 ("selftests/memfd: Fix implicit declaration warnings")
- This fix can be cherry-picked into F/G and compiled without any issue.
+ This fix can be cherry-picked into F/G and compiled without any problem.
+ Older kernel does not have this issue.
[Test Case]
Build the memfd test in kselftests with:
sudo make TARGETS=memfd
With this fix, these warnings will be gone.
[Where problems could occur]
This fix is just for fixing the test case compilation, so it's not affecting
real kernel functionality. If we need to fix it on older release X/B, this
patch will cause compilation errors as they're missing some other vital
commits, since we're not running this test on older releases I think it's fine
to ignore them for now.
** Description changed:
[Impact]
While debugging bug 1910277, I found that the test compilation will print
some warnings:
memfd_test.c:64:7: warning: implicit declaration of function ‘open’;
memfd_test.c:90:6: warning: implicit declaration of function ‘fcntl’
memfd_test.c:397:6: warning: implicit declaration of function ‘fallocate’;
fuse_test.c:67:6: warning: implicit declaration of function ‘fcntl’
fuse_test.c:261:7: warning: implicit declaration of function ‘open’;
And there is a fix in upstream for this.
[Fix]
* 1c49e3783f8899 ("selftests/memfd: Fix implicit declaration warnings")
This fix can be cherry-picked into F/G and compiled without any problem.
Older kernel does not have this issue.
[Test Case]
Build the memfd test in kselftests with:
sudo make TARGETS=memfd
With this fix, these warnings will be gone.
[Where problems could occur]
- This fix is just for fixing the test case compilation, so it's not affecting
real kernel functionality. If we need to fix it on older release X/B, this
patch will cause compilation errors as they're missing some other vital
commits, since we're not running this test on older releases I think it's fine
to ignore them for now.
+ This fix is just for fixing the test case compilation, so it's not affecting
real kernel functionality. If we need to fix it on older release X/B, this
patch will cause compilation errors as they're missing some other vital
commits, I think it's fine to ignore them for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910323
Title:
Fix implicit declaration warnings for kselftests/memfd test on newer
releases
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910323/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Autopkgtest regression report (runc/1.0.0~rc93-0ubuntu1~18.04.1)
All autopkgtests for the newly accepted runc (1.0.0~rc93-0ubuntu1~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: opengcs/0.3.4+dfsg2-0ubuntu3 (s390x, armhf, amd64, i386, 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/bionic/update_excuses.html#runc [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/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919322] Autopkgtest regression report (runc/1.0.0~rc93-0ubuntu1~18.04.1)
All autopkgtests for the newly accepted runc (1.0.0~rc93-0ubuntu1~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: opengcs/0.3.4+dfsg2-0ubuntu3 (s390x, armhf, amd64, i386, 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/bionic/update_excuses.html#runc [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/1919322 Title: Backport the container stack in Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1919322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920061] Re: when I go to restart it claims there is someone logged in remotely when no one is
It says "No inhibitors", and yet there is still no one else logged in remotely and it is still claiming that there is when I try to restart. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920061 Title: when I go to restart it claims there is someone logged in remotely when no one is To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
** Description changed: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- - Xilinx has upstreamed the patch. + Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html - But, it's still under review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority/focal Importance: Undecided => High ** Changed in: oem-priority Importance: High => Critical ** Changed in: oem-priority/focal Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] [NEW] Cursor bleeds on the platform with Mali armsoc driver
Public bug reported: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx has upstreamed the patch. https://lists.x.org/archives/xorg-devel/2021-March/058672.html But, it's still under review. ** Affects: oem-priority Importance: Critical Status: New ** Affects: oem-priority/focal Importance: Critical Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/focal 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/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
The attachment "xorg-server_1.20.10-3ubuntu4.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
debdiff for focal ** Patch added: "xorg-server_1.20.9-2ubuntu1.2~20.04.2.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1920096/+attachment/5478042/+files/xorg-server_1.20.9-2ubuntu1.2~20.04.2.debdiff ** Description changed: [Impact] - The cursor bleeds because of the bug in xorg which does not refresh the sprite background. + The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx has upstreamed the patch. https://lists.x.org/archives/xorg-devel/2021-March/058672.html But, it's still under review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
debdiff for hirsute ** Patch added: "xorg-server_1.20.10-3ubuntu4.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1920096/+attachment/5478041/+files/xorg-server_1.20.10-3ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
The issue is fixed by the attached patch in comment#1 and #2. Please help to review and integrate it to hirsute and focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905370] Re: Qt-based tray icons not displayed on start-up
This bug was fixed in the package gnome-shell-extension-appindicator - 35-1 --- gnome-shell-extension-appindicator (35-1) experimental; urgency=medium [ Marco Trevisan (Treviño) ] * New upstream release * debian/control: - Add myself to the Uploaders - Build depend on eslint when tests are enabled * debian/gbp.conf: - Use multimaint-merge in dch and sign tags - Set upstream branch to upstream/latest - Set upstream-vcs-tag while use default upsteram-tag * debian/patches: - Use tap formatter for eslint by default - Refresh * util: Ignore errors if we can't find a listed dbus name * util: Properly call logger static method * appIndicator: Use promises for the async code * appIndicator: Re-indent and cleanup code to create from pixmaps * appIndicator: Cancel icons loading when we're required to invalidate it * appIndicator: Use low-priority idles to load pixmap icons in batches * cleanup: Replace more GLib Sources with promises * promiseUtils: Backport the current gjs promisfy implementation * appIndicator: Use an async function to initialize the proxy * appIndicator: Fix a typo in a variable name * util: Promisify refreshPropertyOnProxy * promiseUtils: Polyfill a Promise.allSettled implementation * statusNotifierWatcher: Use fully async implementation for DBus traversing * statusNotifierWatcher: Only perform DBus lookup on idle * promiseUtils: Add promise to wait for a single signal emission * statusNotifierWatcher: Use a simple promise to wait startup * statusNotifierWatcher: Ensure we catch errors on indicator initialization * statusNotifierWatcher: Move name watching into the indicator logic * statusNotifierItem: Emit signals about removed items on destruction * statusNotifierWatcher: Emit the uniqueId when emitting (Un)Registered events * Util: define an unique name watcher and reuse it as watch dog and for the indicator * indicatorStatusIcon: Handle scroll events on label too, not only on icon * indicatorStatusIcon: Use virtual functions to monitor button events * eslint: Add linter rules based on upstream gnome-shell and gjs and use auto-fix * cleanup: Cleanup code to match eslint rules * Utils: Do not support connecting to signals via method names [ Matteo F. Vescovi ] * debian/control: debhelper bump 12 -> 13 [ Fran Dieguez ] * Add support for GNOME 40 [ Dennis Fölster ] * Register the StatusNotifierWatcher as soon as possible (LP: #1905370, Closes: #977695). * Fix incorrect placed import. * Use strict equals comparison. -- Marco Trevisan (Treviño) Thu, 18 Mar 2021 01:11:51 +0100 ** Changed in: gnome-shell-extension-appindicator (Ubuntu Hirsute) Status: Triaged => 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/1905370 Title: Qt-based tray icons not displayed on start-up To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1905370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920098] [NEW] Auto Doc Feeder on Epson WF-4720 will not work in 20.04 but it works in 20.10 and Fedora 33
Public bug reported: Flatbed scanner worked. Not the auto document feeder. This is with the Document Scanner program. (is it a rename of Simple Scan?) Simple Scan 3.36.4-1 Other than that, the Distro is Fabulous!! Keep up the good work. Thanks! John ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: simple-scan 3.36.4-1 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 19 00:09:06 2021 InstallationDate: Installed on 2020-11-03 (136 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. OptiPlex 3060 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=e02030f3-4a63-4fbe-be68-a31bd0daa38a ro quiet splash vt.handoff=7 SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: Upgraded to groovy on 2021-03-13 (5 days ago) dmi.bios.date: 07/02/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0T0MHW dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/02/2020:br1.7:svnDellInc.:pnOptiPlex3060:pvr:rvnDellInc.:rn0T0MHW:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 3060 dmi.product.sku: 085C dmi.sys.vendor: Dell Inc. ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920098 Title: Auto Doc Feeder on Epson WF-4720 will not work in 20.04 but it works in 20.10 and Fedora 33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1920098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908286] Re: Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10
Marked as Incomplete as per request in comment #7 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908286 Title: Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920029] Re: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops
*** This bug is a duplicate of bug 1920030 *** https://bugs.launchpad.net/bugs/1920030 ** This bug has been marked a duplicate of bug 1920030 Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920029 Title: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480219] Re: [Dell OptiPlex 3030] No display after rotation
Trusty EOL. ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480219 Title: [Dell OptiPlex 3030] No display after rotation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1480219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1378744] Re: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash
Trusty EOL, closing this. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378744 Title: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1378744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919360] Re: Headphone Sound is not clear and its showing a2dp unavailable
** Summary changed: - Headphone Sound is not clear and its show a2dp not available + Headphone Sound is not clear and its showing a2dp unavailable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919360 Title: Headphone Sound is not clear and its showing a2dp unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1919360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766938] Re: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached
Yeah it's just a missing/unsupported bit depth in old versions of
mutter:
static int
standard_pict_format_for_depth (int depth)
{
switch (depth)
{
case 1:
return PictStandardA1;
case 24:
return PictStandardRGB24;
case 32:
return PictStandardARGB32;
default:
g_assert_not_reached ();
}
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766938
Title:
gnome-shell crashed in
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code
should not be reached
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1766938/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766938] Re: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached
For any poor saps that encounter this in the future in a similar situation, replacing the graphics driver with 'virtio' in the KVM/qemu config fixes this: Instead of the default 'cirrus' or whatever. Found this in my age-old notes from the last time I encountered this problem a year ago. I'm not sure whether this triggered a cache clear or whether the bit depth is different or what... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1766938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766938] Re: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached
I get this error which the internet suggests means a problem getting a core dump. Upping the limits didn't in apport didn't seem to help. I attached the file in /var/crash $ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash *** Error: Problem in gnome-shell Sorry, the program "gnome-shell" closed unexpectedly Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers. Press any key to continue... ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+attachment/5478034/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1766938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766938] Re: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached
It appears the crashing function was removed in mutter 3.34 onward. That means this is "fixed" for Ubuntu 20.04 and later. ** Changed in: mutter (Ubuntu) Status: Invalid => Fix Released ** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1766938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766938] Re: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached
** Summary changed: - gnome-shell crashed in standard_pict_format_for_depth() + gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1766938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] Re: Xorg with EVDI can't start with Mesa 21.0
Yeah I wrote that before your Mesa findings :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920067 Title: Xorg with EVDI can't start with Mesa 21.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918874] Re: [regression] Application windows appear over the icon grid when Ubuntu Dock or Dash To Dock is loaded
Also https://salsa.debian.org/gnome-team/mutter/-/merge_requests/70 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918874 Title: [regression] Application windows appear over the icon grid when Ubuntu Dock or Dash To Dock is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
I'm seeing this crash on a brand new Ubuntu 18.04 install running on KVM (the host itself is on 16.04). When I connect via KVM's VNC and try to open settings app, I get a 100% crash. It's weird because I haven't installed any additional software. Mar 18 22:42:11 riv18 org.gnome.Shell.desktop[2561]: ** Mar 18 22:42:11 riv18 org.gnome.Shell.desktop[2561]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Mar 18 22:42:11 riv18 org.gnome.Shell.desktop[2561]: == Stack trace for context 0x55663fe03320 == Mar 18 22:42:11 riv18 gnome-session[2482]: gnome-session-binary[2482]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Mar 18 22:42:11 riv18 gnome-session-binary[2482]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Mar 18 22:42:12 riv18 gsd-media-keys[2649]: g_variant_get_va: assertion 'value != NULL' failed Mar 18 22:42:12 riv18 gsd-media-keys[2649]: g_variant_unref: assertion 'value != NULL' failed Mar 18 22:42:12 riv18 org.gnome.Shell.desktop[2942]: current session already has an ibus-daemon. Mar 18 22:42:12 riv18 dbus-daemon[445]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.178' (uid=1000 pid=2942 comm="/usr/bin/gnome-shell " label="unconfined") Mar 18 22:42:12 riv18 systemd[1]: Starting Location Lookup Service... Mar 18 22:42:13 riv18 dbus-daemon[445]: [system] Successfully activated service 'org.freedesktop.GeoClue2' Mar 18 22:42:13 riv18 systemd[1]: Started Location Lookup Service. Mar 18 22:42:13 riv18 gnome-shell[2942]: Telepathy is not available, chat integration will be disabled. Mar 18 22:42:13 riv18 gsd-media-keys[2649]: g_variant_get_va: assertion 'value != NULL' failed Mar 18 22:42:13 riv18 gsd-media-keys[2649]: g_variant_unref: assertion 'value != NULL' failed Mar 18 22:42:13 riv18 gnome-shell[2942]: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1028]: unreachable code after return statement Mar 18 22:42:13 riv18 org.gnome.Shell.desktop[2942]: ** Mar 18 22:42:13 riv18 org.gnome.Shell.desktop[2942]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
I've attached the full logs I see. Can anyone tell me where to look for more details? ** Attachment added: "ubuntu-logs" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+attachment/5478029/+files/ubuntu-logs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917194] Re: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04
@Ariel, would you like try the oem kerenl!? #sudo apt install linux-image-oem-20.04b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917194 Title: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] Re: Xorg with EVDI can't start with Mesa 21.0
I performed the splash -> nosplash test described above; it made no difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920067 Title: Xorg with EVDI can't start with Mesa 21.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] Re: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel
I should also note that kernel 5.10 no longer exists in any version of Ubuntu, so "Won't Fix" is probably accurate if the kernel is the factor here. Instead we should probably focus on bug 1920059 only. ** Tags added: regression-release ** Summary changed: - Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel + Xorg with EVDI can't start with Mesa 21.0 ** Changed in: mesa (Ubuntu) Importance: Undecided => High ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920067 Title: Xorg with EVDI can't start with Mesa 21.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] Re: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel
** Also affects: mesa (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/1920067 Title: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] Re: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel
I debugged this further and discovered that one of the following updates caused evdi with kernel 5.10 to start failing as described above: 2021-03-18 21:55:45 upgrade libegl-mesa0:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:45 upgrade libgbm1:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:45 upgrade libgl1-mesa-dri:i386 20.3.4-1 21.0.0-1 2021-03-18 21:55:46 upgrade libgl1-mesa-dri:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:47 upgrade libglx-mesa0:i386 20.3.4-1 21.0.0-1 2021-03-18 21:55:48 upgrade libglx-mesa0:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:48 upgrade libglapi-mesa:amd64 20.3.4-1 21.0.0-1 2021-03-18 21:55:48 upgrade libglapi-mesa:i386 20.3.4-1 21.0.0-1 When I downgraded all of the listed debs to the old version indicated (20.3.4-1) and rebooted, evdi with kernel 5.10 started working again. So I guess this is a mesa bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920067 Title: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] Re: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel
When drmSetMaster fails it generally means a display server (Xorg) is trying to start while some other display server is already busy with the graphics hardware (has not yet called drmDropMaster). That "other" display server might be plymouthd if the login screen fails to start. To test that theory you can try changing the kernel parameter "splash" to "nosplash". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920067 Title: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920067] Re: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920067 Title: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920061] Re: when I go to restart it claims there is someone logged in remotely when no one is
Sounds like https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3119 You might be able to use this command to find out the relevant apps: gnome-session-inhibit -l ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3119 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3119 ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920061 Title: when I go to restart it claims there is someone logged in remotely when no one is To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920036] Re: [DisplayLink] screen flicker on gnome with t450s with ultra dock
Please run these commands: lspci -kv > lspci.txt journalctl -b0 > journal.txt and attach the resulting text files here. ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920036 Title: [DisplayLink] screen flicker on gnome with t450s with ultra dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1920036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920036] Re: screen flicker on gnome with t450s with ultra dock
That libinput error is not related to this issue - it's something everyone sees. ** Summary changed: - screen flicker on gnome with t450s with ultra dock + [DisplayLink] screen flicker on gnome with t450s with ultra dock ** Tags added: displaylink -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920036 Title: [DisplayLink] screen flicker on gnome with t450s with ultra dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1920036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919429] Re: Impossible Login: if dual screen is active, mouse is locked only in one monitor, the wrong one
*** This bug is a duplicate of bug 1760849 *** https://bugs.launchpad.net/bugs/1760849 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1760849, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1760849 Login screen appears on only one monitor and it's not the one I want -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919429 Title: Impossible Login: if dual screen is active, mouse is locked only in one monitor, the wrong one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919408] Re: General protection fault, kernel panics on ASUS M5A99FX PRO R2.0
Thanks for the logs. I am seeing "general protection fault" in multiple different processes so it sounds like a hardware problem, if not a kernel bug. Please try testing your RAM per comment #7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919408 Title: General protection fault, kernel panics on ASUS M5A99FX PRO R2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919408] Re: General protection fault, kernel panics on ASUS M5A99FX PRO R2.0
Please also check your RAM in case it's faulty using one of: https://www.memtest.org/ https://www.memtest86.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919408 Title: General protection fault, kernel panics on ASUS M5A99FX PRO R2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295627] Re: Wrong language (German) after fresh install
*** This bug is a duplicate of bug 1907914 *** https://bugs.launchpad.net/bugs/1907914 Ubuntu 20.10 is a short-lived release so there won't be any updates to the installer where 20.10 can ever be fixed. And 20.10 reaches end of life in July (https://wiki.ubuntu.com/Releases). The fix is in 21.04 already, and if you would like to see it in 20.04.3 then please click the nominate button in bug 1907914. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295627 Title: Wrong language (German) after fresh install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1295627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
** Tags added: performance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896186] Re: Raspberry Pi HDMI output looks dull, low contrast
Still affects hirsute. ** 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/1896186 Title: Raspberry Pi HDMI output looks dull, low contrast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1896186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908677] Re: Dell Latitude 9510 capture volume is too low
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu1 --- alsa-ucm-conf (1.2.4-2ubuntu1) hirsute; urgency=medium * d/p/0001-rt715-init-setup-ADC07-to-a-proper-volume.patch Correct rt715 init volume setting. (LP: #1908677) -- Kai-Chuan Hsieh Thu, 18 Mar 2021 11:10:27 +0100 ** Changed in: alsa-ucm-conf (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/1908677 Title: Dell Latitude 9510 capture volume is too low To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter
I've just tried Surajee's patch on Ubuntu's latest kernel 5.11.0-11 for upcoming Hirsute and it consistently unlatches IOMMU after 6 x 20 msec tries on my Ryzen 2400G. Mainline 5.12-rc2 gave identical results. Paul Menzel too gets failure even after 10 x 20 msecs on a 2200G and regards so long a delay as most unacceptable. Alexander Monakov's very simple patch always works for me but I haven't seen data from other people. Surajee has mentioned problems with it for some part of AMD's product range and, as one of AMD's IOMMU experts down at Austen Texas, he should know his onions :-). I would be tempted to run with the patch (11 x 20 msecs), log the exit count number and get some user feedback. Hopefully an improved patch will emerge! AMD may have commercial as well as technical reasons not leave it unaddressed. Best regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917203 Title: AMD-Vi: Unable to read/write to IOMMU perf counter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920070] Re: stage 3 script doesn't stop services due to incorrect service directory
The attachment "use-etc-service-in-stage-3-script.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920070 Title: stage 3 script doesn't stop services due to incorrect service directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1920070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845756] Re: lubuntu - strange movement of wallpaper on monitor.settings change (or next login)
I just experienced this again at login on a QA-test install performed yesterday. - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) I was using box for support purposes (remote access from remmina) & indirectly caused my real/visible session to logout (I was trying to logout/close my remote session). On logging back in with the physical session, - my top display is now black (no wallpaper), bottom display has the top-half of the actual wallpaper. (box has two displays, one above the other) - top (black) display now shows openbox options on right-click of black- background - bottom display (top half of wallpaper) right-click has expected LXQt/Lubuntu menu appear -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845756 Title: lubuntu - strange movement of wallpaper on monitor.settings change (or next login) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1845756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917194] Re: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04
Tried 5.8.0-43 kernel and didn't work. I also tried booting Manjaro which uses 5.6.15-1-MANJARO and the issue is present. I ended up doing a workaround, compiling an ubuntu kernel with `pci- stub` as builtin and `xhci-hcd` as a dynamic module. That way I can make pci-stub bind to the culprit device and everything works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917194 Title: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896947] Re: Release 20.2
** Changed in: curtin 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/1896947 Title: Release 20.2 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1896947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901817] Re: subiquity installation (on s390x) reusing existing partitions fails with 'Network plugin raised an exception'
pretty sure this was fixed in 20.04.2. ** Changed in: curtin 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/1901817 Title: subiquity installation (on s390x) reusing existing partitions fails with 'Network plugin raised an exception' To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1901817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Please test proposed package
Hello Florian, or anyone else affected, Accepted runc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.0.0~rc93-0ubuntu1~18.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- 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Please test proposed package
Hello Florian, or anyone else affected, Accepted runc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.0.0~rc93-0ubuntu1~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: runc (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: 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/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916485] Re: test -x fails inside shell scripts in containers
Hello Florian, or anyone else affected, Accepted runc into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.0.0~rc93-0ubuntu1~20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: runc (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: runc (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/1916485 Title: test -x fails inside shell scripts in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919322] Please test proposed package
Hello Lucas, or anyone else affected, Accepted runc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.0.0~rc93-0ubuntu1~18.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- 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919322 Title: Backport the container stack in Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1919322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919322] Please test proposed package
Hello Lucas, or anyone else affected, Accepted runc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.0.0~rc93-0ubuntu1~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: runc (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: 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/1919322 Title: Backport the container stack in Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1919322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919322] Re: Backport the container stack in Hirsute
Hello Lucas, or anyone else affected, Accepted runc into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.0.0~rc93-0ubuntu1~20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: runc (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: runc (Ubuntu Focal) Status: In Progress => 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/1919322 Title: Backport the container stack in Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1919322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868177] Re: /snap/subiquity/1561/usr/bin/subiquity:ValueError:main:wrapper:log_time:block_meta:meta_clear:clear_holders:wipe_superblock:_wipe_superblock:wipe_volume:quick_zero:zero_file_at_offse
** Merge proposal linked: https://code.launchpad.net/~mwhudson/curtin/+git/curtin/+merge/399893 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868177 Title: /snap/subiquity/1561/usr/bin/subiquity:ValueError:main:wrapper:log_time:block_meta:meta_clear:clear_holders:wipe_superblock:_wipe_superblock:wipe_volume:quick_zero:zero_file_at_offsets To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1868177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916325] Re: Overly strict NAME_REGEX rejects valid hostnames
** Changed in: curtin (Ubuntu) Status: New => Invalid ** Changed in: curtin 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/1916325 Title: Overly strict NAME_REGEX rejects valid hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1916325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868177] Re: /snap/subiquity/1561/usr/bin/subiquity:ValueError:main:wrapper:log_time:block_meta:meta_clear:clear_holders:wipe_superblock:_wipe_superblock:wipe_volume:quick_zero:zero_file_at_offse
** Also affects: curtin 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/1868177 Title: /snap/subiquity/1561/usr/bin/subiquity:ValueError:main:wrapper:log_time:block_meta:meta_clear:clear_holders:wipe_superblock:_wipe_superblock:wipe_volume:quick_zero:zero_file_at_offsets To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1868177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920081] [NEW] update-manager pop-ups may lead to accidental reboots
Public bug reported: I encounter the (rare) situation where the update-manager's "reminder" popped up with the "Restart Now" button below my mouse cursor just when I clicked with the intention to select something in the window below the newly opened reminder window. As a result, my PC rebooted with all my work lost. This is unacceptable. Even though this might only occur in rare circumstances, the desktop should not present random windows to the user that might lead to a loss of work. I suggest that the update-manager should be properly integrated into the GNOME software centre (as it is on Debian), or at least only show a notification should be shown that opens the current pop-up when clicked on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: update-manager 1:20.04.10.6 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 18 23:14:22 2021 PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920081 Title: update-manager pop-ups may lead to accidental reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1920081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897515] Re: Ubuntu server 20.04.1 Subiquity running from DVD doesn't see drive 0 as a drive to install to
** Changed in: subiquity Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897515 Title: Ubuntu server 20.04.1 Subiquity running from DVD doesn't see drive 0 as a drive to install to To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1897515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782517] Re: Failed to recover stopped instance
** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Also affects: cloud-archive/stein Importance: Undecided Status: New ** Also affects: cloud-archive/victoria Importance: Undecided Status: New ** Also affects: cloud-archive/train Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby 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/1782517 Title: Failed to recover stopped instance To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1782517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905412] Re: LVM install broken if other disks have meta-data on the VG name already
** Changed in: subiquity Status: Confirmed => 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/1905412 Title: LVM install broken if other disks have meta-data on the VG name already To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1905412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782517] Re: Failed to recover stopped instance
** Changed in: masakari (Ubuntu Hirsute) 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/1782517 Title: Failed to recover stopped instance To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1782517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918265] Re: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2
Hi, So for secureboot it's off, the system doesn't boot with it on (compatible key not included with 2012R2's Hyper-V i suppose. The shim used was the one setup from 20.04.2 install image, technically it's not the same as the one in the "shim" package: 78415fb8fb9b909f8029858113f1335f /boot/efi/EFI/ubuntu/shimx64.efi 9bdc83ad343e8745e1f3d55c36cf2df6 /usr/lib/shim/shimx64.efi But some build information extracted from the binary seem to say otherwise : $Version: 15 $ $BuildMachine: Linux x86_64 x86_64 x86_64 GNU/Linux $ $Commit: a4a1fbe728c9545fc5647129df0cf1593b953bec $ $Version: 15 $ $BuildMachine: Linux x86_64 x86_64 x86_64 GNU/Linux $ $Commit: a4a1fbe728c9545fc5647129df0cf1593b953bec $ I have attached a still frame captured from grub boot with "set debug=all". It's the frame just before the VM reboot. As for the linux-azure kernel, i see no differences on the boot process in any of the three following kernels: vmlinuz-5.8.0-44-generic vmlinuz-5.4.0-1041-azure vmlinuz-5.4.0-67-generic It may be interesting to know however that when the linux- azure-5.4.0.1041.21 kernel was introduced into Ubuntu 18.04 i started to experience weird boot issues causing me to un-install it and fall back to the 5.0.0-1036-azure kernel. There might be some commun issue here ** Attachment added: "2021-03-18 23-26-47.00_00_09_21.Still001.png" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265/+attachment/5478015/+files/2021-03-18%2023-26-47.00_00_09_21.Still001.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918265 Title: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889310] Re: pdfarranger not shown in gnome-software als official package
** Changed in: pdfarranger (Ubuntu) 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/1889310 Title: pdfarranger not shown in gnome-software als official package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfarranger/+bug/1889310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919097] Re: Installation crashed
Thanks @jouni-mettala That day I was installing Ubuntu on a friend's system. I faced that error and thought it is good to report. I'm not sure what caused that and what fixed that. But that night I went into a lot of tweaks in bios and filesystem. Last thing I tried was to convert MBR -> GPT using `gdisk`. And then I could install Ubuntu. Thanks for devoting time on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919097 Title: Installation crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1919097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920076] [NEW] critical error grub file
Public bug reported: critical error grub file ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 18 23:20:50 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=cs_CZ.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920076 Title: critical error grub file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1920076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868664] Re: grub 2.04 can't read f2fs volume
Anything we sign increases our attack surface. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868664 Title: grub 2.04 can't read f2fs volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1868664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896734] Re: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack
Verified Focal Ussuri using [Test Plan]: # apt-cache policy neutron-common neutron-common: Installed: 2:16.3.0-0ubuntu3 Candidate: 2:16.3.0-0ubuntu3 Version table: *** 2:16.3.0-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2:16.2.0-0ubuntu3 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2:16.0.0~b3~git2020041516.5f42488a9a-0ubuntu2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896734 Title: A privsep daemon spawned by neutron-openvswitch-agent hangs when debug logging is enabled (large number of registered NICs) - an RPC response is too large for msgpack To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1896734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920070] [NEW] stage 3 script doesn't stop services due to incorrect service directory
Public bug reported: The stage 3 script at /etc/runit/3 has commands to gracefully stop services, but they don't work because they assume services are at /service instead of /etc/service. The patch 0001-default-directory-for-services-on-Debian-is-etc- servi.diff changed the service directory from /service to /etc/service but did not alter the included scripts that assume the service directory is /service. This affects all runit package versions that include the above-mentioned patch (all versions, probably). The attached trivial patch is based off the state of /etc/runit/3 in runit 2.1.2-9.2ubuntu1 ** Affects: runit (Ubuntu) Importance: Undecided Status: New ** Patch added: "use-etc-service-in-stage-3-script.patch" https://bugs.launchpad.net/bugs/1920070/+attachment/5478004/+files/use-etc-service-in-stage-3-script.patch ** Summary changed: - stage 3 script doesn't stop services due to incorrect services directory + stage 3 script doesn't stop services due to incorrect service directory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920070 Title: stage 3 script doesn't stop services due to incorrect service directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1920070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920008] Re: grub2-signed depends on grub2-common
This bug was fixed in the package grub2-signed - 1.167 --- grub2-signed (1.167) hirsute; urgency=medium * grub-efi-amd64-signed: add depends on grub2-common with support for R_X86_64_PLT32 relocations. LP: #1920008 -- Dimitri John Ledkov Thu, 18 Mar 2021 11:17:14 + ** Changed in: grub2-signed (Ubuntu) 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/1920008 Title: grub2-signed depends on grub2-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1920008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885430] Re: [Bionic/Stein] Ceilometer-agent fails to collect metrics after restart
---> Installed version root@juju-bf8c6a-lm-ceilometer-7:/home/ubuntu# dpkg -l |grep -i ceilometer ii ceilometer-agent-compute 1:12.1.1-0ubuntu1~cloud1 all ceilometer compute agent ii ceilometer-common1:12.1.1-0ubuntu1~cloud1 all ceilometer common files ii python3-ceilometer 1:12.1.1-0ubuntu1~cloud1 all ceilometer python libraries Run through 2 cases 1) Service restart 2) Reboot ---> Service restart case root@juju-bf8c6a-lm-ceilometer-7:/home/ubuntu# systemctl status ceilometer-agent-compute ● ceilometer-agent-compute.service - Ceilometer Agent Compute Loaded: loaded (/lib/systemd/system/ceilometer-agent-compute.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2021-03-18 21:20:01 UTC; 2min 35s ago Main PID: 27650 (ceilometer-poll) Tasks: 6 (limit: 4702) CGroup: /system.slice/ceilometer-agent-compute.service ├─27650 ceilometer-polling: master process [/usr/bin/ceilometer-polling --config-file=/etc/ceilometer/ceilometer.conf --polling-namespaces compute --log-file=/var/log/cei └─27735 ceilometer-polling: AgentManager worker(0) Mar 18 21:20:01 juju-bf8c6a-lm-ceilometer-7 systemd[1]: Stopped Ceilometer Agent Compute. Mar 18 21:20:01 juju-bf8c6a-lm-ceilometer-7 systemd[1]: Started Ceilometer Agent Compute. Mar 18 21:20:03 juju-bf8c6a-lm-ceilometer-7 ceilometer-agent-compute[27650]: Deprecated: Option "logdir" from group "DEFAULT" is deprecated. Use option "log-dir" from group "DEFAULT root@juju-bf8c6a-lm-ceilometer-7:/home/ubuntu# systemctl status nova-compute ● nova-compute.service - OpenStack Compute Loaded: loaded (/lib/systemd/system/nova-compute.service; disabled; vendor preset: enabled) Active: active (running) since Thu 2021-03-18 18:46:56 UTC; 2h 35min ago Main PID: 2199 (nova-compute) Tasks: 22 (limit: 4702) CGroup: /system.slice/nova-compute.service └─2199 /usr/bin/python3 /usr/bin/nova-compute --config-file=/etc/nova/nova.conf --config-file=/etc/nova/nova-compute.conf --log-file=/var/log/nova/nova-compute.log Mar 18 18:46:56 juju-bf8c6a-lm-ceilometer-7 systemd[1]: Started OpenStack Compute. -- root@juju-bf8c6a-lm-ceilometer-7:/home/ubuntu# systemctl stop nova-compute root@juju-bf8c6a-lm-ceilometer-7:/home/ubuntu# systemctl disable nova-compute.service Synchronizing state of nova-compute.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install disable nova-compute root@juju-bf8c6a-lm-ceilometer-7:/home/ubuntu# systemctl status nova-compute ● nova-compute.service - OpenStack Compute Loaded: loaded (/lib/systemd/system/nova-compute.service; disabled; vendor preset: enabled) Active: inactive (dead) since Thu 2021-03-18 21:23:30 UTC; 7s ago Main PID: 2199 (code=exited, status=0/SUCCESS) Mar 18 18:46:56 juju-bf8c6a-lm-ceilometer-7 systemd[1]: Started OpenStack Compute. Mar 18 21:23:24 juju-bf8c6a-lm-ceilometer-7 systemd[1]: Stopping OpenStack Compute... Mar 18 21:23:30 juju-bf8c6a-lm-ceilometer-7 systemd[1]: Stopped OpenStack Compute. root@juju-bf8c6a-lm-ceilometer-7:/home/ubuntu# root@juju-bf8c6a-lm-ceilometer-7:/home/ubuntu# systemctl status ceilometer-agent-compute ● ceilometer-agent-compute.service - Ceilometer Agent Compute Loaded: loaded (/lib/systemd/system/ceilometer-agent-compute.service; enabled; vendor preset: enabled) Active: inactive (dead) since Thu 2021-03-18 21:23:24 UTC; 29s ago Main PID: 761 (code=exited, status=0/SUCCESS) Mar 18 21:23:13 juju-bf8c6a-lm-ceilometer-7 systemd[1]: Started Ceilometer Agent Compute. Mar 18 21:23:14 juju-bf8c6a-lm-ceilometer-7 ceilometer-agent-compute[761]: Deprecated: Option "logdir" from group "DEFAULT" is deprecated. Use option "log-dir" from group "DEFAULT". Mar 18 21:23:24 juju-bf8c6a-lm-ceilometer-7 systemd[1]: Stopping Ceilometer Agent Compute... Mar 18 21:23:24 juju-bf8c6a-lm-ceilometer-7 systemd[1]: Stopped Ceilometer Agent Compute. root@juju-bf8c6a-lm-ceilometer-7:/home/ubuntu# /etc/init.d/ceilometer-agent-compute restart [ ok ] Restarting ceilometer-agent-compute (via systemctl): ceilometer-agent-compute.service. root@juju-bf8c6a-lm-ceilometer-7:/home/ubuntu# systemctl status ceilometer-agent-compute ● ceilometer-agent-compute.service - Ceilometer Agent Compute Loaded: loaded (/lib/systemd/system/ceilometer-agent-compute.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2021-03-18 21:24:13 UTC; 2s ago Main PID: 1549 (ceilometer-poll) Tasks: 6 (limit: 4702) CGroup: /system.slice/ceilometer-agent-compute.service ├─1549 ceilometer-polling: master process [/usr/bin/ceilometer-polling --config-file=/etc/ceilometer/ceilometer.conf --polling-namespaces compute --log-file=/var/log/ceil └─1604 ceilometer-polling: AgentManager worker(0) Mar 18
[Bug 1916761] Re: [dvr] bound port permanent arp entries never deleted
Verified Focal Ussuri (UCA) using [Test Plan] and the output is as follows: https://pastebin.ubuntu.com/p/Hd2DShbMCX/ # apt-cache policy neutron-common neutron-common: Installed: 2:16.3.0-0ubuntu3 Candidate: 2:16.3.0-0ubuntu3 Version table: *** 2:16.3.0-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2:16.2.0-0ubuntu3 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2:16.0.0~b3~git2020041516.5f42488a9a-0ubuntu2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Tags removed: verification-ussuri-needed ** Tags added: verification-ussuri-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916761 Title: [dvr] bound port permanent arp entries never deleted To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1916761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault
This issue affects other applications as well, such as Pidgin with Perl plugins segfaulting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1897561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
On Thu, Mar 18, 2021 at 12:25 PM Ryan Harper <1918...@bugs.launchpad.net> wrote: > > * dann frazier <1918...@bugs.launchpad.net> [2021-03-18 12:11]: > > On Thu, Mar 18, 2021 at 10:25 AM Ryan Harper <1918...@bugs.launchpad.net> > > wrote: > > > > > > * dann frazier <1918...@bugs.launchpad.net> [2021-03-17 20:30]: > > > > On Tue, Mar 16, 2021 at 10:05 AM Ryan Harper > > > > <1918...@bugs.launchpad.net> wrote: > > > > > > > > > > Hi Dan, > > > > > > > > > > > > > 1) flash-kernel could get installed post-divert. In that case, > > > > flash-kernel's own postinst will cause it to run and then fail. This > > > > happens today if you start with a cloud image w/o flash-kernel > > > > pre-baked because Ubuntu's kernel recommends flash-kernel, causing it > > > > to be installed along with the kernel. Official cloud images happen to > > > > > > Hrm, so if we take a squashfs rootfs (with no flash-kernel present) > > > chroot into it and install the linux-image-generic package pulling in > > > flash-kernel this fails due to postinst of flash-kernel expecting > > > initramfs to already be generated? This doesn't seem like a curtin bug. > > > > If done so in a chroot that exposes the kernel interfaces (/proc & > > /sys) that claim to be hardware that requires the initramfs to be > > post-processed, yes. > > Maybe I'm missing something but if I install linux-image-generic > it populates /boot with vmlinuz-$version (and a few more things) > and /lib/modules/$version and the kernels postinst will invoke > update-initramfs. The /boot/initrd.img-$version is *generated* at > that time during the kernel's postinstall > > Now, in the arm case IIUC, the kernel package has a dep on flash-kernel > being present as it's "needed" to generate the initramfs ... so how can > flash-kernel's postinst *fail* if it is the tool that's generating said > initramfs file? What flash-kernel does is generate wrapped versions of *exisiting* vmlinuz and initrd.img files. It doesn't generate those files, rather post-processes them. The kernel doesn't depend on flash-kernel, it just recommends it like it does GRUB on x86. -dann -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919320] Re: Active Directory users unable to change expired password on logon
I tested this today with 18.04 This issue exists in 18.04 with the the samba domain join method. However Ubuntu 18.04 with SSSD and Realmd method worked as designed with the expired password. The user was able to change the expired password -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919320 Title: Active Directory users unable to change expired password on logon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1919320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667146] Re: iwlwifi 0000:01:00.0: Error sending REPLY_SCAN_ABORT_CMD: time out after 2000ms.
I have just experienced this problem for the first time (on, admittedly, Linux Mint) with kernel 5.8.0. I note also that there is a report on the problem filed against the Linux kernel itself, here: https://bugzilla.kernel.org/show_bug.cgi?id=190281 Perhaps Ubuntu devs should engage with that report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667146 Title: iwlwifi :01:00.0: Error sending REPLY_SCAN_ABORT_CMD: time out after 2000ms. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1667146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902513] Re: RM debian-installer no longer built
Removing packages from hirsute: debian-installer 20101020ubuntu622.3 in hirsute debian-installer 20101020ubuntu622.3 in hirsute amd64 debian-installer 20101020ubuntu622.3 in hirsute arm64 debian-installer 20101020ubuntu622.3 in hirsute armhf debian-installer 20101020ubuntu622.3 in hirsute ppc64el debian-installer 20101020ubuntu622.3 in hirsute s390x Comment: we no longer ship debian-installer as an installer; LP: #1902513 1 package successfully removed. ** Changed in: debian-installer (Ubuntu) Status: Triaged => 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/1902513 Title: RM debian-installer no longer built To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1902513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1920058] Re: Widevine library for Ubuntu on ARM
I don't think there is a package for now. The idea is to create a new package as soon as possible so people using ARM devices as desktop can watch videos over streaming services. On Thu, Mar 18, 2021 at 5:35 PM Ubuntu Foundations Team Bug Bot < 1920...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It seems that your bug report is not filed about a > specific source package though, rather it is just filed against Ubuntu > in general. It is important that bug reports be filed about source > packages so that people interested in the package can find the bugs > about it. You can find some hints about determining what package your > bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. > You might also ask for help in the #ubuntu-bugs irc channel on Freenode. > > To change the source package that this bug is filed about visit > https://bugs.launchpad.net/ubuntu/+bug/1920058/+editstatus and add the > package name in the text box next to the word Package. > > [This is an automated message. I apologize if it reached you > inappropriately; please just reply to this message indicating so.] > > ** Tags added: bot-comment > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1920058 > > Title: > Widevine library for Ubuntu on ARM > > Status in Ubuntu: > New > > Bug description: > Raspberry Pi OS, the official Linux distro of Raspberry Pi, released > support for Netflix, Amazon Prime, Hulu, etc. making Widevine library > (library used in the DRM system by this streaming services) available > on the repository, The ideia is do the same. The most benefited will > be the Ubuntu Desktop for Raspberry Pi 4. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1920058/+subscriptions > -- Marcos H. Alano Linux System Administrator marcoshal...@gmail.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920058 Title: Widevine library for Ubuntu on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1920058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685609] Re: Remove pepperflashplugin-nonfree from Ubuntu 17.10 "Artful Aardvark"
*** This bug is a duplicate of bug 1871471 *** https://bugs.launchpad.net/bugs/1871471 ** This bug has been marked a duplicate of bug 1871471 flash end of life soon, suggest remove from hirsute and also handle stable releases -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685609 Title: Remove pepperflashplugin-nonfree from Ubuntu 17.10 "Artful Aardvark" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pepperflashplugin-nonfree/+bug/1685609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
