[Bug 1835521] Re: [regression] Artifacts appears when windows are maximizing or minimizing (Intel Apollo Lake)
Thanks for that. It seems you are reporting multiple different issues here. The black flickering on window resizing seems to be a new problem so I'll make that the main bug. The asymmetric artifacts seen when restoring from maximized is an old bug (https://gitlab.gnome.org/GNOME/mutter/issues/636) so should be reported separately. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #636 https://gitlab.gnome.org/GNOME/mutter/issues/636 ** Summary changed: - [regression] Artifacts appears when windows are maximizing or minimizing (Intel Apollo Lake) + [regression] Windows flicker to black when resizing (Intel Apollo Lake) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835521 Title: [regression] Windows flicker to black when resizing (Intel Apollo Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835521] Re: [regression] Artifacts appears when windows are maximizing or minimizing
** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [regression] Artifacts appears when windows are maximizing or minimizing + [regression] Artifacts appears when windows are maximizing or minimizing (Intel Apollo Lake) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835521 Title: [regression] Windows flicker to black when resizing (Intel Apollo Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835181] Re: OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and ldap:// with STARTTLS
Apologies for misinterpreting this issue when initially triaging it - I have re-marked it as Security. I notice from your linked bug report that this was still happening with the upstream code as of September 2016 - but upstream did not appear to engage on the issue. Can you confirm whether this appears to be a Ubuntu (packaging or otherwise) specific issue or whether this is also affects upstream? If so, then this should be handled by upstream first and we can backport any fixes as appropriate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835181 Title: OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and ldap:// with STARTTLS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1835181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835700] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + phase: Ready for Packaging + phase-changed: Monday, 08. July 2019 05:44 UTC + reason: + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835700 Title: linux: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834887] Re: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1835436 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:failed + promote-to-proposed: Pending -- builds not complete in ppa main:failed,signed:building variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834887 Title: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813496] Re: powertop does not accurately determine battery discharge rate on HP Elitebook 850 G5
Do you see this issue on Linux v5.0? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813496 Title: powertop does not accurately determine battery discharge rate on HP Elitebook 850 G5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835521] Re: [regression] Artifacts appears when windows are maximizing or minimizing
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mutter (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/1835521 Title: [regression] Artifacts appears when windows are maximizing or minimizing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1835521] Re: [regression] Artifacts appears when windows are maximizing or minimizing
1. I am not using any extensions. I have done this commands. Please, take these files. пн, 8 июл. 2019 г. в 05:00, Daniel van Vugt : > 3. Please also run: > >dpkg -l > allpackages.txt > >and send us the file 'allpackages.txt'. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1835521 > > Title: > [regression] Artifacts appears when windows are maximizing or > minimizing > > Status in gnome-shell package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > > Bug description: > I see the black zones, small windows breaks. For additional details, I > use eoan-proposed and eoan-backports packages. > You can see this problem in my video: > https://photos.app.goo.gl/3rvLkqJj6hZwSscw9 > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gnome-shell 3.32.2-2ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 > Uname: Linux 5.0.0-20-generic x86_64 > ApportVersion: 2.20.11-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Jul 5 13:39:13 2019 > DisplayManager: gdm3 > InstallationDate: Installed on 2019-07-01 (3 days ago) > InstallationMedia: > > ProcEnviron: >LANGUAGE=ru_UA:ru >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=ru_UA.UTF-8 >SHELL=/bin/bash > RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835521/+subscriptions > ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/bugs/1835521/+attachment/5275542/+files/lspcik.txt ** Attachment added: "allpackages.txt" https://bugs.launchpad.net/bugs/1835521/+attachment/5275543/+files/allpackages.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835521 Title: [regression] Artifacts appears when windows are maximizing or minimizing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835521] Re: [regression] Artifacts appears when windows are maximizing or minimizing
I am not using any extensions. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1835521/+attachment/5275544/+files/lspcik.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835521 Title: [regression] Artifacts appears when windows are maximizing or minimizing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835679] Re: Calamares don't offer a partitioning scheme on mmcblk devices
** Changed in: lubuntu-meta (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835679 Title: Calamares don't offer a partitioning scheme on mmcblk devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1835679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835040] Re: Touchpd not working properly on Linux
Please test this kernel: https://people.canonical.com/~khfeng/lp1835040/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835040 Title: Touchpd not working properly on Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834887] Re: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1835436 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:failed,signed:building + promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:failed variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834887 Title: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835700] [NEW] linux: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Eoan) Importance: Medium Status: New ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.07.07-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + -- swm properties -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.07.07-1 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow 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/1835700 Title: linux: -proposed tracker To manage notifications about this bug go
[Bug 1834887] Re: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1835436 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:failed + promote-to-proposed: Pending -- builds not complete in ppa main:failed,signed:building variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834887 Title: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835682] Re: Firefox
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/1835682/+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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835682 Title: Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1835682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782608] Re: Fresh Ubuntu 18.04 install uses wrong Realtek wired network driver.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782608 Title: Fresh Ubuntu 18.04 install uses wrong Realtek wired network driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828227] Re: shiftfs: allow changing ro/rw for subvolumes
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828227 Title: shiftfs: allow changing ro/rw for subvolumes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661310] Re: Same serial number for two different certs
[Expired for xca (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xca (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661310 Title: Same serial number for two different certs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xca/+bug/1661310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824434] Re: [0-day SRU] MAAS 2.6.0beta1
[Expired for maas (Ubuntu) because there has been no activity for 60 days.] ** Changed in: maas (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824434 Title: [0-day SRU] MAAS 2.6.0beta1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792672] Re: Regression: acpi reports battery state incorrectly after sleep
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792672 Title: Regression: acpi reports battery state incorrectly after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828201] Re: package management breaks when lubuntu-desktop sub-packages uninstalled
[Expired for lubuntu-meta (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lubuntu-meta (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828201 Title: package management breaks when lubuntu-desktop sub-packages uninstalled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1828201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828206] Re: ubuntu is not upgrading because the mirror has no Release file
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828206 Title: ubuntu is not upgrading because the mirror has no Release file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1828206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826831] Re: Network card not working on kernel 4.15.0-48 but works on 4.15.0-47
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826831 Title: Network card not working on kernel 4.15.0-48 but works on 4.15.0-47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
Also applies to Cosmic, Disco & Eoan. Never been fixed. Just installed Debian Buster to see how it handled grub. I did not select an ESP and it told me to go back and choose a partition as /efi/boot. I choose sdb's ESP and it installed without issue to ESP on sda, and did not overwrite my Ubuntu boot in sda. It did make Buster first in UEFI boot order, but my Ubuntu was second in UEFI boot order & Buster's grub2 os-prober found all my other install, so I could boot them. Probably will use Debian's version of grub since it works, even to boot my Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835690] Re: finger print hardware not being detected
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so I am closing it and converting it to a question in the support tracker. I understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. I suspect this is the same issue reported in https://askubuntu.com/questions/1156639/lsusb-unable-to-detect- fingerprint-hardware which I believe is better helped in support forums such as Ask Ubuntu or in question form. ** Changed in: libfprint (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/libfprint/+question/681840 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835690 Title: finger print hardware not being detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1835690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834887] Re: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1835436 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:failed,signed:building + promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:failed variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834887 Title: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835697] [NEW] Upgrade to zfsutils-linux 0.8.1-1ubuntu5 fails on Ubuntu 19.10
Public bug reported: 1) lsb_release -rd Description:Ubuntu Eoan Ermine (development branch) Release:19.10 2) apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.1-1ubuntu5 Candidate: 0.8.1-1ubuntu5 Version table: *** 0.8.1-1ubuntu5 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status 3) Expected to upgrade from previous zfsutils-linux without error 4) What happened instead: Setting up zfsutils-linux (0.8.1-1ubuntu5) ... Installing new version of config file /etc/zfs/zfs-functions ... zfs-import-scan.service is a disabled or a static unit not running, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "restart" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2019-07-07 23:29:32 EDT; 7ms ago Docs: man:zfs(8) Process: 4265 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 4265 (code=exited, status=1/FAILURE) Jul 07 23:29:32 drb-eoanzfs systemd[1]: Starting Mount ZFS filesystems... Jul 07 23:29:32 drb-eoanzfs zfs[4265]: cannot mount '/root': directory is not empty Jul 07 23:29:32 drb-eoanzfs zfs[4265]: cannot mount '/var/cache': directory is not empty Jul 07 23:29:32 drb-eoanzfs systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Jul 07 23:29:32 drb-eoanzfs systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Jul 07 23:29:32 drb-eoanzfs systemd[1]: Failed to start Mount ZFS filesystems. dpkg: error processing package zfsutils-linux (--configure): installed zfsutils-linux package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of zfs-initramfs: zfs-initramfs depends on zfsutils-linux (>= 0.8.1-1ubuntu5); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-initramfs (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of zfs-zed: zfs-zed depends on zfsutils-linux (>= 0.8.1-1ubuntu5); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-zed (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.29-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for systemd (240-6ubuntu9) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for initramfs-tools (0.133ubuntu9) ... update-initramfs: Generating /boot/initrd.img-5.0.0-20-generic Errors were encountered while processing: zfsutils-linux zfs-initramfs zfs-zed E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: zfsutils (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/1835697 Title: Upgrade to zfsutils-linux 0.8.1-1ubuntu5 fails on Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfsutils/+bug/1835697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835697] Re: Upgrade to zfsutils-linux 0.8.1-1ubuntu5 fails on Ubuntu 19.10
This bug results in an unbootable system after the failed upgrade occurs. As this is being run in a virtual machine I will be restoring the original environment in case further testing is needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835697 Title: Upgrade to zfsutils-linux 0.8.1-1ubuntu5 fails on Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfsutils/+bug/1835697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834815] Re: usb mouse is not being detect
This sounds like a problem: [ 163.566] (II) event10 - Logitech G102 Prodigy Gaming Mouse System Control: is tagged by udev as: Keyboard [ 163.566] (II) event10 - Logitech G102 Prodigy Gaming Mouse System Control: device is a keyboard ** Package changed: xorg (Ubuntu) => xserver-xorg-input-libinput (Ubuntu) ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New ** Summary changed: - usb mouse is not being detect + Logitech G102 Prodigy Gaming Mouse detected as a keyboard, not working as a mouse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834815 Title: Logitech G102 Prodigy Gaming Mouse detected as a keyboard, not working as a mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1834815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991002] Re: Use the modern English name Bangla instead of Bengali for the language code bn
** Changed in: gnome-desktop Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991002 Title: Use the modern English name Bangla instead of Bengali for the language code bn To manage notifications about this bug go to: https://bugs.launchpad.net/cldr/+bug/991002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807056] Re: Occasional Keyboard freeze
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807056 Title: Occasional Keyboard freeze To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1807056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835677] Re: Megal33t bug: touchpad with mousewheel is broken >:]
** 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/1835677 Title: Megal33t bug: touchpad with mousewheel is broken >:] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835614] Re: Touchpad not recognized
Looks like a duplicate to bug 1835150. Please try linux-oem-osp1 version 5.0.0-1013.14 from eoan-proposed, which should have included the fix. https://launchpad.net/ubuntu/+source/linux-oem-osp1/5.0.0-1013.14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835614 Title: Touchpad not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
[D/E][PATCH 0/1] LP#1829563 bcache: pending patch for Disco/Eoan https://lists.ubuntu.com/archives/kernel-team/2019-July/102006.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 6 (for the Disco kernel) commit: 'Revert "bcache: set CACHE_SET_IO_DISABLE in bch_cached_dev_error()"' Problem: if one backing device hits I/O errors the cache device is disabled, but if that cache device is shared by other bcache devices they stop too (even with non-failing backing devices). Original kernel: all bcache devices that share cache device with failing backing device are stopped. Modified kernel: only the bcache device with the failing backing device is stopped. Original kernel: --- root@bionic-bcache:~# uname -rv 5.0.0-21-generic #22-Ubuntu SMP Tue Jul 2 13:27:33 UTC 2019 root@bionic-bcache:~# ./setup-two-bcache-one-cache.sh >/dev/null 2>&1 [ 23.323929] bcache: register_bdev() registered backing device dm-0 [ 23.330821] bcache: register_bdev() registered backing device dm-1 [ 23.335493] bcache: run_cache_set() invalidating existing data [ 23.347255] bcache: register_cache() registered cache device dm-2 [ 24.335738] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set f816e09d-f744-4fc9-b3bd-239f3d5093c6 [ 24.342388] bcache: bch_cached_dev_attach() Caching dm-1 as bcache1 on set f816e09d-f744-4fc9-b3bd-239f3d5093c6 root@bionic-bcache:~# lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache1 251:128 0 1024M 0 disk loop2 7:201G 0 loop └─fake-loop2 253:20 1024M 0 dm ├─bcache0 251:00 1024M 0 disk └─bcache1 251:128 0 1024M 0 disk # echo writeback | tee /sys/block/bcache*/bcache/cache_mode writeback # echo always | tee /sys/block/bcache*/bcache/stop_when_cache_set_failed always root@bionic-bcache:~# ./dm_fake_dev.sh /dev/loop0 bad [ 58.915344] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 58.921948] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 58.928886] bcache: register_bcache() error /dev/dm-0: device already registered (emitting change event) [ 58.931006] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 58.936386] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 58.939346] Buffer I/O error on dev bcache0, logical block 262112, async page read root@bionic-bcache:~# [ 58.944685] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 58.948468] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 58.951078] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 58.954231] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 58.957216] Buffer I/O error on dev bcache0, logical block 1, async page read # ./dm_fake_dev.sh /dev/loop0 bad [ 167.341298] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 167.347802] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 167.354959] bcache: register_bcache() error /dev/dm-0: device already registered (emitting change event) [ 167.356585] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 167.364784] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 167.369083] Buffer I/O error on dev bcache0, logical block 262112, async page read root@bionic-bcache:~# [ 167.376976] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 167.381644] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 167.384195] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 167.387144] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 167.390040] Buffer I/O error on dev bcache0, logical block 1, async page read root@guest-bcache:~# dd if=/dev/zero of=/dev/bcache1 bs=4k & dd if=/dev/zero of=/dev/bcache0 bs=4k & [1] 1464 [2] 1465 root@bionic-bcache:~# [ 178.103060] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 178.107790] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 178.111814] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 178.116428] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 178.119286] bcache:
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
@Maher AlAsfar (malasfar) What's cloud-init version on the Ubuntu16.04? The version need be greater or equal to 18.2 to make customization work. What's open-vm-tools version on the Ubuntu16.04? If you customize Ubuntu with cloud-init, please do NOT add any "After=dbus.x" to open-vm-tools.service file, since it will create dependency cycle during booting. And If it's possible, I suggest use Ubuntu18.04, not Ubuntu16.04 to work with cloud-init -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835690] [NEW] finger print hardware not being detected
Public bug reported: Hie I am currently running on Ubuntu 18.04. and my hardware is Lenovo ThinkPad l480. Lenovo ThinkPad l480 comes with an inbuild fingerprint reader. It works fine in windows os. but it is not able to detect in ubuntu. the output of lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:009a Synaptics, Inc. Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ** Affects: libfprint (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/1835690 Title: finger print hardware not being detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1835690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536309] Re: New Upstream Version
** Changed in: rtl8812au (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/1536309 Title: New Upstream Version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1536309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705820] Re: Wrong build when kernel upgrade (about kernel header path)
** Changed in: rtl8812au (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/1705820 Title: Wrong build when kernel upgrade (about kernel header path) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1705820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835687] [NEW] hwe-support-status prints wrong Ubuntu version
Public bug reported: After do-release-upgrade from 16.04.6 to 18.04.2, my login motd still keeps telling me to upgrade from 16.04 which is no longer the current version $ hwe-support-status You have packages from the Hardware Enablement Stack (HWE) installed that are going out of support on 2023-04-30. To upgrade to a supported (or longer-supported) configuration: * Upgrade from Ubuntu 16.04 LTS to Ubuntu 18.04 LTS by running: sudo do-release-upgrade -p OR * Switch to the current security-supported stack by running: sudo apt-get install and reboot your system. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic $ uname -a Linux aaa 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ /usr/lib/update-notifier/apt-check --human-readable 0 packages can be updated. 0 updates are security updates. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade ** Tags added: dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835687 Title: hwe-support-status prints wrong Ubuntu version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1835687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835686] Re: pip3 list --outdated returns HTTP 404 error
** Description changed: 1) Ubuntu version: 18.04.2 - 2) Package: python3-pip + 2) Package: python3-pip 3) Version: 9.0.1-2.3~ubuntu1.18.04.1 - 4) Expected: pip3 list --outdated should return outdated packages - 5) Actual: Got an exception with HTTP 404 error because https://pypi.org/simple/xkit/ is not found + 4) Expected: pip3 list --outdated should return outdated packages + 5) Actual: Got an exception with HTTP 404 error because https://pypi.org/simple/xkit/ was not found DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning. Exception: Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/pip/basecommand.py", line 215, in main - status = self.run(options, args) - File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 157, in run - packages = self.get_outdated(packages, options) - File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 168, in get_outdated - dist for dist in self.iter_packages_latest_infos(packages, options) - File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 168, in - dist for dist in self.iter_packages_latest_infos(packages, options) - File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 203, in iter_packages_latest_infos - all_candidates = finder.find_all_candidates(dist.key) - File "/usr/lib/python3/dist-packages/pip/index.py", line 423, in find_all_candidates - for page in self._get_pages(url_locations, project_name): - File "/usr/lib/python3/dist-packages/pip/index.py", line 568, in _get_pages - page = self._get_page(location) - File "/usr/lib/python3/dist-packages/pip/index.py", line 683, in _get_page - return HTMLPage.get_page(link, session=self.session) - File "/usr/lib/python3/dist-packages/pip/index.py", line 795, in get_page - resp.raise_for_status() - File "/usr/share/python-wheels/requests-2.18.4-py2.py3-none-any.whl/requests/models.py", line 935, in raise_for_status - raise HTTPError(http_error_msg, response=self) + File "/usr/lib/python3/dist-packages/pip/basecommand.py", line 215, in main + status = self.run(options, args) + File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 157, in run + packages = self.get_outdated(packages, options) + File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 168, in get_outdated + dist for dist in self.iter_packages_latest_infos(packages, options) + File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 168, in + dist for dist in self.iter_packages_latest_infos(packages, options) + File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 203, in iter_packages_latest_infos + all_candidates = finder.find_all_candidates(dist.key) + File "/usr/lib/python3/dist-packages/pip/index.py", line 423, in find_all_candidates + for page in self._get_pages(url_locations, project_name): + File "/usr/lib/python3/dist-packages/pip/index.py", line 568, in _get_pages + page = self._get_page(location) + File "/usr/lib/python3/dist-packages/pip/index.py", line 683, in _get_page + return HTMLPage.get_page(link, session=self.session) + File "/usr/lib/python3/dist-packages/pip/index.py", line 795, in get_page + resp.raise_for_status() + File "/usr/share/python-wheels/requests-2.18.4-py2.py3-none-any.whl/requests/models.py", line 935, in raise_for_status + raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://pypi.org/simple/xkit/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835686 Title: pip3 list --outdated returns HTTP 404 error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1835686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835677] Re: Megal33t bug: touchpad with mousewheel is broken >:]
@klfyt, please understand you must share as much information with other as possible if you need other people to help without the hardware. It's already difficult to work without physical access to the target, let alone not having any log, details from you. Changing the status to CONFIRMED doesn't mean a lot, but uploading logs as suggested by launchpad/bugzilla would. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835677 Title: Megal33t bug: touchpad with mousewheel is broken >:] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
I have been spending so many cycle on this, here are the Testing Tasks around Ubuntu 16.04 Customization with Cloud-init and its expected behaviour for vSphere Provisioning Using After=dbus.socket doesn't work so stick the KB i mentioned below if you want to do it yourself its Test 2 with DHCP and Test 4 for Static IP Please let me know if you were successful or have any comments, questions or suggestions - - Create an Ubuntu 16.04 Virtual Machine on vSphere 6.7 U2. - Apply the latest updates and upgrades -> sudo apt-get update && sudo apt-get upgrades Environment Facts - DHCP is available on the network when preparing the template and later for provisioning. - Cloud Assembly Static IP range also available for vSphere deployments. Test 1 === behavior for deploying VMs using DHCP from CAS before installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is Disconnected - Customization Starts and Succeeds, listed in the VM Events - VM Reboots During the boot time the network state is Connected - IP provided from DHCP - Host-name Updated Note: No Customization Specification used here. Test 2 == behavior for deploying VMs using DHCP from CAS After installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is Connected - Customization doesn't Start at all, so its not listed in the VM Events - IP provided from DHCP - Host-name is not Updated - Cloud Config Code executes successfully Note: No Customization Specification used here. Test 3 == behavior for deploying VMs using Static IP from CAS before installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is disconnected - Customization does start, listed in the VM Events and successful - VM reboots and network shows as connected - IP provided from Static IP Range - Host-name is Updated Note: No Customization Specification used here. Test 4 == behavior for deploying VMs using Static IP from CAS After installing cloud-init following KB https://kb.vmware.com/s/article/59687 Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is disconnected - Customization does start and successful, listed in the VM Events - VM reboots and the network shows as connected - IP provided from Static IP Range - Host-name is Updated - Cloud config executes fine Note: No Customization Specification used here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835686] [NEW] pip3 list --outdated returns HTTP 404 error
Public bug reported: 1) Ubuntu version: 18.04.2 2) Package: python3-pip 3) Version: 9.0.1-2.3~ubuntu1.18.04.1 4) Expected: pip3 list --outdated should return outdated packages 5) Actual: Got an exception with HTTP 404 error because https://pypi.org/simple/xkit/ was not found DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning. Exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/basecommand.py", line 215, in main status = self.run(options, args) File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 157, in run packages = self.get_outdated(packages, options) File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 168, in get_outdated dist for dist in self.iter_packages_latest_infos(packages, options) File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 168, in dist for dist in self.iter_packages_latest_infos(packages, options) File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 203, in iter_packages_latest_infos all_candidates = finder.find_all_candidates(dist.key) File "/usr/lib/python3/dist-packages/pip/index.py", line 423, in find_all_candidates for page in self._get_pages(url_locations, project_name): File "/usr/lib/python3/dist-packages/pip/index.py", line 568, in _get_pages page = self._get_page(location) File "/usr/lib/python3/dist-packages/pip/index.py", line 683, in _get_page return HTMLPage.get_page(link, session=self.session) File "/usr/lib/python3/dist-packages/pip/index.py", line 795, in get_page resp.raise_for_status() File "/usr/share/python-wheels/requests-2.18.4-py2.py3-none-any.whl/requests/models.py", line 935, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://pypi.org/simple/xkit/ ** Affects: python-pip (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/1835686 Title: pip3 list --outdated returns HTTP 404 error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1835686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991002] Re: Use the modern English name Bangla instead of Bengali for the language code bn
** Changed in: ibus Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991002 Title: Use the modern English name Bangla instead of Bengali for the language code bn To manage notifications about this bug go to: https://bugs.launchpad.net/cldr/+bug/991002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833623] Re: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1
I have been spending so many cycle on this, here are the Testing Tasks around Ubuntu 16.04 Customization with Cloud-init on vSphere and its expected behaviour - - Create an Ubuntu 16.04 Virtual Machine on vSphere 6.7 U2. - Apply the latest updates and upgrades -> sudo apt-get update && sudo apt-get upgrades Environment Facts - DHCP is available on the network when preparing the template and later for provisioning. - Cloud Assembly Static IP range also available for vSphere deployments. Test 1 === behavior for deploying VMs using DHCP from CAS before installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is Disconnected - Customization Starts and Succeeds, listed in the VM Events - VM Reboots During the boot time the network state is Connected - IP provided from DHCP - Host-name Updated Note: No Customization Specification used here. Test 2 == behavior for deploying VMs using DHCP from CAS After installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is Connected - Customization doesn't Start at all, so its not listed in the VM Events - IP provided from DHCP - Host-name is not Updated - Cloud Config Code executes successfully Note: No Customization Specification used here. Test 3 == behavior for deploying VMs using Static IP from CAS before installing cloud-init Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is disconnected - Customization does start, listed in the VM Events and successful - VM reboots and network shows as connected - IP provided from Static IP Range - Host-name is Updated Note: No Customization Specification used here. Test 4 == behavior for deploying VMs using Static IP from CAS After installing cloud-init following KB https://kb.vmware.com/s/article/59687 Tasks Invoked by vCenter - Clone Virtual Machine from Template - Reconfigure Virtual Machine - Customize Virtual Machine Guest OS - Power on Virtual Machine During the boot time the network state is disconnected - Customization does start and successful, listed in the VM Events - VM reboots and the network shows as connected - IP provided from Static IP Range - Host-name is Updated - Cloud config executes fine Note: No Customization Specification used here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833623 Title: VMware Guest OS Customization Fail for Ubuntu 16.04 with Cloud-init 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835576] Re: virtualbox-guest-dkms-hwe 5.2.18-dfsg-3~ubuntu18.04.3 fails to build on 5.0 based kernels [In function ‘VBoxGuest_RTR0MemUserIsValidAddr’: error: macro "access_ok" passed 3 arguments
** Summary changed: - virtualbox-guest-dkms-hwe 5.2.18-dfsg-3~ubuntu18.04.3 fails to build on 5.0 based kernels + virtualbox-guest-dkms-hwe 5.2.18-dfsg-3~ubuntu18.04.3 fails to build on 5.0 based kernels [In function ‘VBoxGuest_RTR0MemUserIsValidAddr’: error: macro "access_ok" passed 3 arguments, but takes just 2] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835576 Title: virtualbox-guest-dkms-hwe 5.2.18-dfsg-3~ubuntu18.04.3 fails to build on 5.0 based kernels [In function ‘VBoxGuest_RTR0MemUserIsValidAddr’: error: macro "access_ok" passed 3 arguments, but takes just 2] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-hwe/+bug/1835576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292398] Re: Second screen position isn't saved from one session to another
** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835585] Re: GNOME doesn't remember monitor settings/layout
*** This bug is a duplicate of bug 1292398 *** https://bugs.launchpad.net/bugs/1292398 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 1292398, 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. ** Summary changed: - Xorg doesn't remember monitor settings/layout + GNOME doesn't remember monitor settings/layout ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags added: multimonitor ** This bug has been marked a duplicate of bug 1292398 Second screen position isn't saved from one session to another -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835585 Title: GNOME doesn't remember monitor settings/layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835521] Re: [regression] Artifacts appears when windows are maximizing or minimizing
3. Please also run: dpkg -l > allpackages.txt and send us the file 'allpackages.txt'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835521 Title: [regression] Artifacts appears when windows are maximizing or minimizing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835521] Re: Artifacts appears when windows are maximazing or minimazing
1. Are you using any extensions? 2. Please run this command: lspci -k > lspcik.txt and send us the file 'lspcik.txt'. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Artifacts appears when windows are maximazing or minimazing + [regression] Artifacts appears when windows are maximizing or minimizing ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Tags added: regression -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835521 Title: [regression] Artifacts appears when windows are maximizing or minimizing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832426] Re: "Program" is not responding when debugging in gdb
I think this is fixable per comment #4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832426 Title: "Program" is not responding when debugging in gdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835487] Re: AltGr key not working as "sticky key" in wayland session
** Package changed: xorg-server (Ubuntu) => mutter (Ubuntu) ** Also affects: xorg-server (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/1835487 Title: AltGr key not working as "sticky key" in wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1835487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991002] Re: Use the modern English name Bangla instead of Bengali for the language code bn
** Bug watch added: github.com/ibus/ibus/issues #2104 https://github.com/ibus/ibus/issues/2104 ** Also affects: ibus via https://github.com/ibus/ibus/issues/2104 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991002 Title: Use the modern English name Bangla instead of Bengali for the language code bn To manage notifications about this bug go to: https://bugs.launchpad.net/cldr/+bug/991002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830358] Re: Screen flickering
Thanks for the video! This kind of flickering is going to be low-level. So we should look at the kernel log. If the kernel driver isn't reporting errors then it would probably be a hardware fault. Please wait until the problem happens again and then run: dmesg > dmesgonflicker.txt and send us the file 'dmesgonflicker.txt'. ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830358 Title: Screen flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
[C][PATCH 0/2] LP#1829563 bcache: pending patches for Cosmic https://lists.ubuntu.com/archives/kernel-team/2019-July/102001.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 6 (for the Cosmic kernel) commit: 'Revert "bcache: set CACHE_SET_IO_DISABLE in bch_cached_dev_error()"' Problem: if one backing device hits I/O errors the cache device is disabled, but if that cache device is shared by other bcache devices they stop too (even with non-failing backing devices). Original kernel: all bcache devices that share cache device with failing backing device are stopped. Modified kernel: only the bcache device with the failing backing device is stopped. Original kernel --- root@guest-bcache:~# uname -rv 4.18.0-23-generic #24-Ubuntu SMP Wed Jun 12 18:17:39 UTC 2019 root@guest-bcache:~# lsblk -e 252 root@guest-bcache:~# root@guest-bcache:~# ./setup-two-bcache-one-cache.sh >/dev/null 2>&1 [ 35.686002] bcache: register_bdev() registered backing device dm-0 [ 35.695980] bcache: register_bdev() registered backing device dm-1 [ 35.704662] bcache: run_cache_set() invalidating existing data [ 35.719046] bcache: register_cache() registered cache device dm-2 [ 36.705686] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set fce8d558-4657-47dc-ab37-226ada14daf5 [ 36.711827] bcache: bch_cached_dev_attach() Caching dm-1 as bcache1 on set fce8d558-4657-47dc-ab37-226ada14daf5 root@guest-bcache:~# lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache1 251:128 0 1024M 0 disk loop2 7:201G 0 loop └─fake-loop2 253:20 1024M 0 dm ├─bcache0 251:00 1024M 0 disk └─bcache1 251:128 0 1024M 0 disk root@guest-bcache:~# echo writeback | tee /sys/block/dm-*/bcache/cache_mode writeback root@guest-bcache:~# cat /sys/block/dm-*/bcache/cache_mode writethrough [writeback] writearound none writethrough [writeback] writearound none root@guest-bcache:~# ./dm_fake_dev.sh /dev/loop0 bad [ 76.875749] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 76.882159] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 76.889453] bcache: register_bcache() error /dev/dm-0: device already registered (emitting change event) [ 76.892183] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 76.904907] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 76.907711] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 76.912607] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 76.916905] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 76.920345] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 76.924767] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 76.928404] Buffer I/O error on dev bcache0, logical block 1, async page read root@guest-bcache:~# dd if=/dev/zero of=/dev/bcache1 bs=4k & dd if=/dev/zero of=/dev/bcache0 bs=4k & [ 175.024811] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 175.029844] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.034652] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 175.037465] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.040373] Buffer I/O error on dev bcache0, logical block 2, lost async page write ... [ 175.092196] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.096635] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.101272] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.105829] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable ... [ 175.235700] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.239457] bcache: bch_cached_dev_error() stop bcache0: too many IO errors on backing device dm-0 [ 175.239457] [ 175.324069] bcache: bch_cache_set_error() CACHE_SET_IO_DISABLE already set [ 175.328998] bcache: error on fce8d558-4657-47dc-ab37-226ada14daf5: [ 175.328999] journal io error [ 175.331022] , disabling caching [ 175.334264] bcache: conditional_stop_bcache_device() stop_when_cache_set_failed of bcache0 is "auto" and cache is dirty, stop it to avoid potential data corruption. [ 175.338865] bcache: conditional_stop_bcache_device() stop_when_cache_set_failed of bcache1 is "auto" and cache is dirty, stop it to avoid potential data corruption. [ 175.344097] bcache: cached_dev_detach_finish() Caching disabled for dm-1 [ 176.080139] bcache:
[Bug 1807056] Re: Occasional Keyboard freeze
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #907 https://gitlab.gnome.org/GNOME/gnome-shell/issues/907 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/907 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807056 Title: Occasional Keyboard freeze To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1807056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 7
commit: "bcache: fix ioctl in flash device"
This test needs QEMU+GDB since there's no way to set the variable
from the kernel, because it references incorrect memory/pointer.
In the original kernel, the ioctl() to a flash-only volume
goes from ioctl_dev() down to flash_dev_ioctl()
(which always return -ENOTTY always) only if its backing device
has io_disable == 0, but gets -EIO if io_disable == 1
(which are both wrong as flash device has no backing device).
In the modified kernel, it always go down to flash_dev_ioctl(),
thus -ENOTTY in both cases.
Original kernel:
$ uname -rv
4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019
io_disable = 0:
# ./ioctl
ioctl: Inappropriate ioctl for device
io_disable = 1:
# ./ioctl
ioctl: Input/output error
Modified kernel:
# uname -rv
4.18.0-23-generic #24+test20190619b1 SMP Wed Jun 19 22:33:22 UTC 2019
io_disable = 0:
# ./ioctl
ioctl: Inappropriate ioctl for device
io_disable = 1:
# ./ioctl
ioctl: Inappropriate ioctl for device
Steps
-
$ sudo -i
# ./setup.sh >/dev/null 2>&1
[ 57.607391] bcache: register_bdev() registered backing device dm-0
[ 57.611885] bcache: run_cache_set() invalidating existing data
[ 57.625712] bcache: register_cache() registered cache device dm-1
[ 58.605153] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set
08f1756b-081f-4545-a947-927d429f7ef1
# lsblk -e 252
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:001G 0 loop
└─fake-loop0 253:00 1024M 0 dm
└─bcache0 251:00 1024M 0 disk
loop1 7:101G 0 loop
└─fake-loop1 253:10 1024M 0 dm
└─bcache0 251:00 1024M 0 disk
# echo $((128*1024**2)) > /sys/block/dm-1/bcache/set/flash_vol_create
# lsblk -e 252
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:001G 0 loop
└─fake-loop0 253:00 1024M 0 dm
└─bcache0 251:00 1024M 0 disk
loop1 7:101G 0 loop
└─fake-loop1 253:10 1024M 0 dm
├─bcache0 251:00 1024M 0 disk
└─bcache1 251:128 0 128M 0 disk
# ls -1d /sys/block/bcache1/bcache/cache/volume*
/sys/block/bcache1/bcache/cache/volume1
# cat /sys/module/bcache/sections/.text
0xc05f4000
# cat ioctl.c
#include
#include
#include
#include
int main() {
int fd, rc;
fd = open("/dev/bcache1", O_RDWR);
if (fd == -1) {
perror("open");
return 0;
}
rc = ioctl(fd, 0xcc00ffee); // our cookie.
if (rc == -1)
perror("ioctl");
close(fd);
return 0;
}
# gcc -o ioctl ioctl.c
# ./ioctl
(gdb) add-symbol-file
~/ddeb-4.18.0-23-generic/usr/lib/debug/lib/modules/4.18.0-23-generic/kernel/drivers/md/bcache/bcache.ko
0xc05f4000
(gdb) b *ioctl_dev +0x13
(gdb) c
Thread 4 hit Breakpoint 1, ioctl_dev (b=, mode=134610975,
cmd=3422617582, arg=2) at
/build/linux-JHFGaE/linux-4.18.0/drivers/md/bcache/super.c:641
...
(gdb) p/x 3422617582
$53 = 0xcc00ffee // our cookie.
(gdb) print d.name
$54 = "volume1\000\000\000\000" // matches the volume above.
See it's an incorrect pointer.
No way to set it via any io_disable in sysfs.
(gdb) print ((struct cached_dev *)((void *)d - 0x10)).backing_dev_name
$75 =
"\017\000\000\000\260\373\212s\277\230\377\377\260\373\212s\277\230\377\377
nԇ\377\377\377\377\060qh\211"
(gdb) print ((struct cached_dev *)((void *)d - 0x10)).io_disable
$76 = 0
With the default value (io_disable = 0):
# ./ioctl
ioctl: Inappropriate ioctl for device
(gdb) c
... repeat.
With the forced value (io_disable = 1):
(gdb) set ((struct cached_dev *)((void *)d - 0x10)).io_disable = 1
(gdb) c
# ./ioctl
ioctl: Input/output error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829563
Title:
bcache: risk of data loss on I/O errors in backing or caching devices
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834887] Re: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1835436 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:failed + promote-to-proposed: Pending -- builds not complete in ppa main:failed,signed:building variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834887 Title: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357226] Re: qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Hi, I am getting the error:
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault
When I try to execute a Hello World binary on my amd64 machine, with
Hello World built by mips-linux-gnu-g++, using either mips binfmt
extensions (./hello) or qemu-mips-static hello. I have libstdc++6:mips
installed as well. My source code is as follows:
#include
using std::cout;
int main() {
cout << "Hello World!\n";
return 0;
}
Worth noting that this problem only happens with mips cross runs.
mips64el and mipsel work just fine.
I happen to be doing this in Debian 10.0.0 Buster stable amd64 on
VirtualBox on Ubuntu 19.04 Disco Dingo amd64, but it looks like the same
behavior on native Ubuntu hosts as well. I tried increasing guest RAM to
1GiB and 2GiB, with no affect on the runtime error message. Is there a
glitch in one of the mips packages?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357226
Title:
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1357226/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
[B][PATCH 00/11] LP#1829563 bcache: risk of data loss on I/O errors in backing or caching devices https://lists.ubuntu.com/archives/kernel-team/2019-July/101989.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991002] Re: Use the modern English name Bangla instead of Bengali for the language code bn
** Bug watch added: gitlab.gnome.org/GNOME/gnome-desktop/issues #49 https://gitlab.gnome.org/GNOME/gnome-desktop/issues/49 ** Also affects: gnome-desktop via https://gitlab.gnome.org/GNOME/gnome-desktop/issues/49 Importance: Unknown Status: Unknown ** No longer affects: gnome-control-center ** Bug watch removed: GNOME Bug Tracker #695939 https://gitlab.gnome.org/695939 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991002 Title: Use the modern English name Bangla instead of Bengali for the language code bn To manage notifications about this bug go to: https://bugs.launchpad.net/cldr/+bug/991002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570430] Re: libxcb-image0-dev missing header xcb/xcb_bitops.h
The xcb/xcb_bitops.h used to be part of xcb-util, but was dropped in version 0.4.0 from that package and moved to xcb-util-image. Unfortunately, the package fails to include the header, which can result in e.g. compilation failures. It is also affected by Ubuntu 19.04 disco. Compilation for xcb failed. installing xcb_util_image package there were no xcb_bitop.h header file missing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570430 Title: libxcb-image0-dev missing header xcb/xcb_bitops.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xcb-util-image/+bug/1570430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835622] Re: Cannot start desktop session with compositor enabled
** Changed in: xfwm4 Status: Confirmed => Invalid ** Bug watch added: freedesktop.org Bugzilla #107117 https://bugs.freedesktop.org/show_bug.cgi?id=107117 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835622 Title: Cannot start desktop session with compositor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Description changed: [Impact] - * The bcache code in Bionic lacks several fixes to handle -I/O errors in both backing devices and caching devices. + * The bcache code in Bionic lacks several fixes to handle + I/O errors in both backing devices and caching devices. - * Partial or permanent errors in backing or caching devices, -specially in writeback mode, can lead to data loss and/or -the application is not notified about failed I/O requests. + * Partial or permanent errors in backing or caching devices, + specially in writeback mode, can lead to data loss and/or + the application is not notified about failed I/O requests. - * The bcache device might remain available for I/O requests -even if backing device is offline, so writes are undefined. + * The bcache device might remain available for I/O requests + even if backing device is offline, so writes are undefined. [Test Case] - * Detailed test cases/steps for the behavior of almost every -patch with code logic changes are provided in bug comments. + * Detailed test cases/steps for the behavior of almost every + patch with code logic changes are provided in bug comments. - * The patchset has been tested for regressions on each cache -mode (writethrough, writeback, writearound, none) with the -xfstests test suite (on ext4), fio (random read-write) and -iozone (several read/write tests). + * The patchset has been tested for regressions on each cache + mode (writethrough, writeback, writearound, none) with the + xfstests test suite (on ext4) and fio (sequential + random +read-write). [Regression Potential] - * The patchset is relatively large and touches several areas -in bcache code, however, synthetic testing of the patches -has been performed, and extensive regression/stress tests -were run (as mentioned in Test Case section). + * The patchset is relatively large and touches several areas + in bcache code, however, synthetic testing of the patches + has been performed, and extensive regression/stress tests + were run (as mentioned in Test Case section). - * Many patches in the patchset are 'Fixes' patches to other -patches, and no further 'Fixes' currently exist upstream. + * Many patches in the patchset are 'Fixes' patches to other + patches, and no further 'Fixes' currently exist upstream. [Other Info] - * Canonical Field Eng. deploys bcache+writeback extensively -(e.g., BootStack, UA cloud, except rare all-flash cases). - + * Canonical Field Eng. deploys bcache+writeback extensively + (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. ** Description changed: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] - * Detailed test cases/steps for the behavior of almost every - patch with code logic changes are provided in bug comments. + * Detailed test cases/steps for the behavior of many patches + with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4) and fio (sequential + random -read-write). + read-write). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. -- You
[Bug 1835622]
Installed package versions are: - xfwm4 4.13.3-0ubuntu1~18.04 - libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835622 Title: Cannot start desktop session with compositor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835154] Re: Cannot start tor browser - gpg hangs refreshing keys
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: torbrowser-launcher (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835154 Title: Cannot start tor browser - gpg hangs refreshing keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/1835154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835622]
This is an issue in Mesa DRI driver for Intel, that shows when Mesa is built with asserts() enabled (typically debug). See: https://bugs.freedesktop.org/show_bug.cgi?id=107117 https://patchwork.freedesktop.org/patch/237490/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835622 Title: Cannot start desktop session with compositor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 1 commit "bcache: add CACHE_SET_IO_DISABLE to struct cache_set flags" Problem: the cacheset is not retired immediately on I/O errors in cache device if I/O requests keep coming. Original kernel: bcache device remains on top of caching device, and 'fio' never finishes. Modified kernel: bcache device is removed from caching device, and fio finishes. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # ./setup.sh >/dev/null 2>&1 [ 285.677682] bcache: register_bdev() registered backing device dm-0 [ 285.697006] bcache: run_cache_set() invalidating existing data [ 285.710938] bcache: register_cache() registered cache device dm-1 [ 287.686924] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set c589879b-b1c3-49b3-9603-9795ddc750f5 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # ./dm_fake_dev.sh /dev/loop1 bad [ 766.102586] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 766.107602] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 766.113889] bcache: register_bcache() error /dev/dm-1: device already registered On another shell: # fio --name=write --rw=randwrite --filename=/dev/bcache0 --bs=4k --iodepth=8 --ioengine=libaio --runtime=300s --continue_on_error=all write: (g=0): rw=randwrite, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=8 fio-3.1 Starting 1 process Jobs: 1 (f=1): [f(1)][100.0%][r=0KiB/s,w=0KiB/s][r=0,w=0 IOPS][eta 00m:00s] < fio never finishes, keeps showing the last line above > < console prints as below when fio starts running > [ 777.451177] bcache: bch_count_io_errors() dm-1: IO error on writing btree, recovering [ 777.490882] bcache: error on c589879b-b1c3-49b3-9603-9795ddc750f5: [ 777.490885] journal io error [ 777.494087] , disabling caching [ 807.900700] bcache: bch_count_io_errors() dm-1: IO error on writing btree, recovering (error msgs looping) bcache0 still present on top of cache device (fake-loop1) # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop fake-loop1 253:101G 0 dm └─bcache0251:00 1024M 0 disk Modified # uname -rv 4.15.0-55-generic #60+test20190703build1bcache1-Ubuntu SMP Wed Jul 3 21:41:37 UTC # ./setup.sh >/dev/null 2>&1 [ 60.542088] bcache: register_bdev() registered backing device dm-0 [ 60.550509] bcache: run_cache_set() invalidating existing data [ 60.560109] bcache: register_cache() registered cache device dm-1 [ 62.548849] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set f6833a2c-53e6-468e-bf1d-a9f48b73d783 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # ./dm_fake_dev.sh /dev/loop1 bad [ 72.639185] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 72.644876] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 72.650707] bcache: register_bcache() error /dev/dm-1: device already registered On another shell: # fio --name=write --rw=randwrite --filename=/dev/bcache0 --bs=4k --iodepth=8 --ioengine=libaio --runtime=300s --continue_on_error=all [ 97.858468] bcache: bch_count_io_errors() dm-1: IO error on writing btree, recovering [ 97.868519] bcache: error on f6833a2c-53e6-468e-bf1d-a9f48b73d783: [ 97.868520] journal io error [ 97.869998] , disabling caching [ 97.871441] bcache: conditional_stop_bcache_device() stop_when_cache_set_failed of bcache0 is "auto" and cache is clean, keep it alive. [ 97.874423] Buffer I/O error on dev bcache0, logical block 2814, lost async page write [ 97.878697] Buffer I/O error on dev bcache0, logical block 2816, lost async page write [ 97.881702] Buffer I/O error on dev bcache0, logical block 2817, lost async page write [ 97.884790] Buffer I/O error on dev bcache0, logical block 2818, lost async page write [ 97.887709] Buffer I/O error on dev bcache0, logical block 2819, lost async page write [ 97.890558] Buffer I/O error on dev bcache0, logical block 2820, lost async page write [ 97.892419] Buffer I/O error on dev bcache0, logical block 2821, lost async page write [ 97.894228] Buffer I/O error on dev bcache0, logical block 2822, lost async page write [ 97.896107] Buffer I/O error on dev bcache0, logical block 2823, lost async page write [
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 3 commit "bcache: fix inaccurate io state for detached bcache devices" Probçem: on detached bcache devices, iostat reports non-zero 'avgqu-sz' and '%util' even after IO stopped. Original kernel: iostat fields are non-zero on I/O idle. Modified kernel: iostat fields are all zero on I/O idle. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # ./setup.sh >/dev/null 2>&1 [ 118.371172] bcache: register_bdev() registered backing device dm-0 [ 118.377221] bcache: run_cache_set() invalidating existing data [ 118.386614] bcache: register_cache() registered cache device dm-1 [ 120.373682] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set 4f2b6518-1a58-42e0-8720-42b535cb826f # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # echo 1 > /sys/block/bcache0/bcache/detach [ 131.847360] bcache: cached_dev_detach_finish() Caching disabled for dm-0 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm # dd if=/dev/zero of=/dev/bcache0 bs=4k dd: error writing '/dev/bcache0': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 3.86316 s, 278 MB/s # sync # iostat -xy 1 10 /dev/bcache0 | grep bcache0 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 Modified # uname -rv 4.15.0-55-generic #60+test20190703build1bcache1-Ubuntu SMP Wed Jul 3 21:41:37 UTC # ./setup.sh >/dev/null 2>&1 [ 26.923296] bcache: register_bdev() registered backing device dm-0 [ 26.928998] bcache: run_cache_set() invalidating existing data [ 26.940144] bcache: register_cache() registered cache device dm-1 [ 28.920772] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set bf256397-22a4-40ac-8ff3-0026fd28354c # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # echo 1 > /sys/block/bcache0/bcache/detach [ 42.292538] bcache: cached_dev_detach_finish() Caching disabled for dm-0 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 2 commit "bcache: add stop_when_cache_set_failed option to backing device" Problem: upon too many io errors on cache device, bcache code retires cache set, but it doesn't stop the bcache device. (in writeback mode, if it continue to write, writes go to backing device directly; next time bcache re-registers, it writes dirty cached data again, overwriting data) Original kernel: bcache device remains available for writes. Modified kernel: bcache device is not available anymore. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # ./setup.sh >/dev/null 2>&1 [ 27.427543] bcache: register_bdev() registered backing device dm-0 [ 27.434844] bcache: run_cache_set() invalidating existing data [ 27.445652] bcache: register_cache() registered cache device dm-1 [ 29.435245] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set 68e969a1-0f60-4978-a109-b48559970472 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # echo writeback > /sys/block/bcache0/bcache/cache_mode # dd if=/dev/zero of=/dev/bcache0 bs=4k dd: error writing '/dev/bcache0': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 5.14109 s, 209 MB/s # ./dm_fake_dev.sh /dev/loop1 bad [ 135.316335] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 135.330181] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 135.337019] bcache: register_bcache() error /dev/dm-1: device already registered # dd if=/dev/zero of=/dev/bcache0 bs=4k [ 142.754766] bcache: error on 68e969a1-0f60-4978-a109-b48559970472: [ 142.754769] journal io error [ 142.757583] , disabling caching dd: error writing '/dev/bcache0': No space left on device [ 143.299557] bcache: bch_count_io_errors() dm-1: IO error on reading dirty data from cache, recovering [ 143.305560] bcache: bch_count_io_errors() dm-1: IO error on reading dirty data from cache, recovering [ 143.308463] bcache: bch_count_io_errors() dm-1: IO error on reading dirty data from cache, recovering # ./dm_fake_dev.sh /dev/loop1 good [ 171.220172] bcache: bch_count_io_errors() dm-1: IO error on reading dirty data from cache, recovering [ 171.426360] bcache: register_bcache() error /dev/dm-1: device already registered 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 32.066 s, 33.5 MB/s dd: closing input file '/dev/zero': Bad file descriptor # # [ 174.589309] bcache: cached_dev_detach_finish() Caching disabled for dm-0 [ 174.599062] bcache: cache_set_free() Cache set 68e969a1-0f60-4978-a109-b48559970472 unregistered # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm Modified # uname -rv 4.15.0-55-generic #60+test20190703build1bcache1-Ubuntu SMP Wed Jul 3 21:41:37 UTC # ./setup.sh >/dev/null 2>&1 [ 39.981825] bcache: register_bdev() registered backing device dm-0 [ 39.987359] bcache: run_cache_set() invalidating existing data [ 40.000743] bcache: register_cache() registered cache device dm-1 [ 41.985275] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set 9b509864-84be-428e-ad8a-293d546ec2e9 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # echo writeback > /sys/block/bcache0/bcache/cache_mode # dd if=/dev/zero of=/dev/bcache0 bs=4k dd: error writing '/dev/bcache0': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 5.96102 s, 180 MB/s # ./dm_fake_dev.sh /dev/loop1 bad [ 81.798129] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 81.804533] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 81.810630]
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 6 Make sure that if two bcache devices share a cache device, only one bcache device is offlined in case of I/O errors in only one backing device. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # ./setup-two-bcache-one-cache.sh >/dev/null 2>&1 [ 20.464988] bcache: register_bdev() registered backing device dm-0 [ 20.474082] bcache: register_bdev() registered backing device dm-1 [ 20.485464] bcache: run_cache_set() invalidating existing data [ 20.496253] bcache: register_cache() registered cache device dm-2 [ 21.478688] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set e247271f-eea4-46ea-8ffe-4b04299a7c24 [ 21.484183] bcache: bch_cached_dev_attach() Caching dm-1 as bcache1 on set e247271f-eea4-46ea-8ffe-4b04299a7c24 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache1 251:128 0 1024M 0 disk loop2 7:201G 0 loop └─fake-loop2 253:20 1024M 0 dm ├─bcache0 251:00 1024M 0 disk └─bcache1 251:128 0 1024M 0 disk # echo writeback | tee /sys/block/dm-*/bcache/cache_mode writeback # cat /sys/block/dm-*/bcache/cache_mode writethrough [writeback] writearound none writethrough [writeback] writearound none # ./dm_fake_dev.sh /dev/loop0 bad [ 56.142318] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 56.151754] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 56.158706] bcache: register_bcache() error /dev/dm-0: device already registered (emitting change event) [ 56.161631] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 56.169723] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 56.172303] Buffer I/O error on dev bcache0, logical block 1, async page read root@guest-bcache:~# dd if=/dev/zero of=/dev/bcache1 bs=4k & dd if=/dev/zero of=/dev/bcache0 bs=4k & [1] 1400 [2] 1401 # [ 85.400054] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 85.403138] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 85.417864] Buffer I/O error on dev bcache0, logical block 2, lost async page write [ 85.419699] Buffer I/O error on dev bcache0, logical block 3, lost async page write [ 85.421510] Buffer I/O error on dev bcache0, logical block 4, lost async page write [ 85.423301] Buffer I/O error on dev bcache0, logical block 5, lost async page write [ 85.450407] Buffer I/O error on dev bcache0, logical block 6, lost async page write [ 85.452248] Buffer I/O error on dev bcache0, logical block 7, lost async page write [ 85.453980] Buffer I/O error on dev bcache0, logical block 8, lost async page write [ 85.455722] Buffer I/O error on dev bcache0, logical block 9, lost async page write dd: error writing '/dev/bcache0': No space left on device dd: error writing '/dev/bcache1': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 4.23916 s, 253 MB/s [2]+ Exit 1 dd if=/dev/zero of=/dev/bcache0 bs=4k # 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 6.5355 s, 164 MB/s [1]+ Exit 1 dd if=/dev/zero of=/dev/bcache1 bs=4k # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache1 251:128 0 1024M 0 disk loop2 7:201G 0 loop └─fake-loop2 253:20 1024M 0 dm ├─bcache0 251:00 1024M 0 disk └─bcache1 251:128 0 1024M 0 disk fake-loop0 253:001G 0 dm └─bcache0251:00 1024M 0 disk Nothing is removed, since no I/O errors are detected. Modified # uname -rv 4.15.0-55-generic #60+test20190703build1bcache1-Ubuntu SMP Wed Jul 3 21:41:37 UTC # ./setup-two-bcache-one-cache.sh >/dev/null 2>&1 [ 29.341483] bcache: register_bdev() registered backing device dm-0 [ 29.351963] bcache: run_cache_set() invalidating existing data [ 29.365256] bcache: register_cache() registered cache device dm-2 [ 29.365566] bcache: register_bdev() registered backing device dm-1 [ 30.357267] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set ee57b847-da70-4b65-888b-e5795ecf6c46 [ 30.363117] bcache: bch_cached_dev_attach() Caching dm-1 as bcache1 on set ee57b847-da70-4b65-888b-e5795ecf6c46 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache1 251:128 0 1024M 0 disk
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 4 commit "bcache: add io_disable to struct cached_dev" Problem: in case of the backing device hits I/o errors or is disconected, the I/O can still be accepted to the bcache device. Original kernel: dd writes in writeback mode to failed backing device complete. Modified kernel: the bcache0 device is removed after some I/O errors in backing device. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # ./setup.sh >/dev/null 2>&1 [ 24.820401] bcache: register_bdev() registered backing device dm-0 [ 24.833268] bcache: run_cache_set() invalidating existing data [ 24.848314] bcache: register_cache() registered cache device dm-1 [ 26.824645] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set dd465fa7-4e85-484b-89dd-353c24c6b041 # echo writeback > /sys/block/bcache0/bcache/cache_mode # cat /sys/block/bcache0/bcache/cache_mode writethrough [writeback] writearound none # ./dm_fake_dev.sh /dev/loop0 bad [ 41.439684] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 41.445284] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 41.451846] bcache: register_bcache() error /dev/dm-0: device already registered (emitting change event) [ 41.454704] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 41.457685] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 41.457743] Buffer I/O error on dev bcache0, logical block 1, async page read # dd if=/dev/zero of=/dev/bcache0 bs=4k [ 49.048036] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 49.051702] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 49.054062] Buffer I/O error on dev bcache0, logical block 2, lost async page write [ 49.056466] Buffer I/O error on dev bcache0, logical block 3, lost async page write [ 49.058867] Buffer I/O error on dev bcache0, logical block 4, lost async page write [ 49.072020] Buffer I/O error on dev bcache0, logical block 5, lost async page write [ 49.074440] Buffer I/O error on dev bcache0, logical block 6, lost async page write [ 49.078658] Buffer I/O error on dev bcache0, logical block 7, lost async page write [ 49.079008] Buffer I/O error on dev bcache0, logical block 6834, lost async page write [ 49.079022] Buffer I/O error on dev bcache0, logical block 6835, lost async page write dd: error writing '/dev/bcache0': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 2.58342 s, 416 MB/s # dd if=/dev/zero of=/dev/bcache0 bs=4k [ 62.696034] buffer_io_error: 260992 callbacks suppressed [ 62.696037] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 62.701996] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 62.704394] Buffer I/O error on dev bcache0, logical block 2, lost async page write [ 62.706763] Buffer I/O error on dev bcache0, logical block 3, lost async page write [ 62.716025] Buffer I/O error on dev bcache0, logical block 4, lost async page write [ 62.718421] Buffer I/O error on dev bcache0, logical block 5, lost async page write [ 62.720821] Buffer I/O error on dev bcache0, logical block 6, lost async page write [ 62.723193] Buffer I/O error on dev bcache0, logical block 7, lost async page write [ 62.725584] Buffer I/O error on dev bcache0, logical block 8, lost async page write [ 62.725763] Buffer I/O error on dev bcache0, logical block 5405, lost async page write dd: error writing '/dev/bcache0': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 2.88915 s, 372 MB/s # dd if=/dev/zero of=/dev/bcache0 bs=4k [ 67.700114] buffer_io_error: 290043 callbacks suppressed [ 67.700117] Buffer I/O error on dev bcache0, logical block 40750, lost async page write [ 67.706230] Buffer I/O error on dev bcache0, logical block 40751, lost async page write [ 67.709846] Buffer I/O error on dev bcache0, logical block 40752, lost async page write [ 67.713503] Buffer I/O error on dev bcache0, logical block 40753, lost async page write [ 67.717241] Buffer I/O error on dev bcache0, logical block 40754, lost async page write [ 67.720938] Buffer I/O error on dev bcache0, logical block 40755, lost async page write [ 67.741395] Buffer I/O error on dev bcache0, logical block 40756, lost async page write dd: error writing '/dev/bcache0': No space left on device [ 67.748145] Buffer I/O error on dev bcache0, logical block 40757, lost async page write [ 67.752352] Buffer I/O error on dev bcache0, logical block 41038, lost async page write [ 67.756642] Buffer I/O error on dev bcache0, logical block 41313,
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 5 commit "bcache: stop bcache device when backing device is offline" Problem: bcache is unaware that a backing device goes offline, and accepts writes. Original kernel: bcache doesn't realize backing device is offline. Modified kernel: bcache device is removed after backing device is offline. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # apt install -y linux-modules-extra-$(uname -r)=4.15.0-55.60 # modprobe scsi_debug dev_size_mb=1024 # dmesg | tail [ 17.339336] scsi host2: scsi_debug: version 1.86 [20160430] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 17.339667] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0186 PQ: 0 ANSI: 7 [ 17.339989] sd 2:0:0:0: Power-on or device reset occurred [ 17.340184] sd 2:0:0:0: Attached scsi generic sg0 type 0 [ 17.348436] sd 2:0:0:0: [sda] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB) [ 17.352496] sd 2:0:0:0: [sda] Write Protect is off [ 17.352501] sd 2:0:0:0: [sda] Mode Sense: 73 00 10 08 [ 17.360686] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 17.451956] sd 2:0:0:0: [sda] Attached SCSI disk # ./setup-sda.sh >/dev/null 2>&1 [ 37.515474] bcache: run_cache_set() invalidating existing data [ 37.527275] bcache: register_cache() registered cache device dm-0 [ 37.625160] bcache: register_bdev() registered backing device sda [ 38.466997] bcache: bch_cached_dev_attach() Caching sda as bcache0 on set 0e23e266-6032-4700-a4c9-464964ed1349 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk sda8:001G 0 disk └─bcache0251:00 1024M 0 disk # echo writeback > /sys/block/sda/bcache/cache_mode # echo 1 > /sys/block/sda/device/delete [ 77.878624] sd 2:0:0:0: [sda] Synchronizing SCSI cache # sleep 10 # # dd if=/dev/zero of=/dev/bcache0 bs=4k [ 120.268072] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 120.271978] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 120.274554] Buffer I/O error on dev bcache0, logical block 2, lost async page write [ 120.276671] Buffer I/O error on dev bcache0, logical block 3, lost async page write [ 120.278760] Buffer I/O error on dev bcache0, logical block 4, lost async page write [ 120.288042] Buffer I/O error on dev bcache0, logical block 5, lost async page write [ 120.290178] Buffer I/O error on dev bcache0, logical block 6, lost async page write [ 120.296043] Buffer I/O error on dev bcache0, logical block 7, lost async page write [ 120.298167] Buffer I/O error on dev bcache0, logical block 8, lost async page write [ 120.300220] Buffer I/O error on dev bcache0, logical block 3260, lost async page write dd: error writing '/dev/bcache0': No space left on device 262143+0 records in 262142+0 records out 1073733632 bytes (1.1 GB, 1.0 GiB) copied, 3.49705 s, 307 MB/s # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk Modified # uname -rv 4.15.0-55-generic #60+test20190703build1bcache1-Ubuntu SMP Wed Jul 3 21:41:37 UTC # modprobe scsi_debug dev_size_mb=1024 # dmesg | tail [ 27.855163] scsi host2: scsi_debug: version 1.86 [20160430] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 27.855497] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0186 PQ: 0 ANSI: 7 [ 27.855829] sd 2:0:0:0: Power-on or device reset occurred [ 27.855883] sd 2:0:0:0: Attached scsi generic sg0 type 0 [ 27.863979] sd 2:0:0:0: [sda] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB) [ 27.868028] sd 2:0:0:0: [sda] Write Protect is off [ 27.868031] sd 2:0:0:0: [sda] Mode Sense: 73 00 10 08 [ 27.876114] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 27.966877] sd 2:0:0:0: [sda] Attached SCSI disk # # ./setup-sda.sh >/dev/null 2>&1 [ 46.294586] bcache: run_cache_set() invalidating existing data [ 46.306769] bcache: register_cache() registered cache device dm-0 [ 46.400510] bcache: register_bdev() registered backing device sda [ 47.247662] bcache: bch_cached_dev_attach() Caching sda as bcache0 on set d3d7816b-6bd9-4dea-bf0c-4bde76b45f91 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk sda8:001G 0 disk └─bcache0251:00 1024M 0 disk # echo writeback > /sys/block/sda/bcache/cache_mode # echo 1 > /sys/block/sda/device/delete [ 85.713826] sd 2:0:0:0: [sda] Synchronizing SCSI cache # sleep 10 [ 90.428125] bcache: cached_dev_status_update() sda:
[Bug 1835682] [NEW] Firefox
Public bug reported: 1) Ubuntu 19.04 2) 67.0.4+build1-0ubuntu0.19.04.1 3) When holding down F11 in FireFox, it will go into fullscreen mode and it will not do anything else as the button is held down. 4) All it takes to crash gnome-shell... this is amazing. Just open firefox and take your finger and hold down F11. LOL, guys... I don't know if this is actually a problem with Firefox itself or GNOME or whatever, but someone needs to take notes from Google Chrome. If you need to know what should actually happen, just try the same thing in Chrome. How this is still not fixed, I have no idea? Someone please help, thank you! ** Affects: ubuntu Importance: Undecided Status: New ** Tags: firefox ** Tags added: firefox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835682 Title: Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1835682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835679] Re: Calamares don't offer a partitioning scheme on mmcblk devices
This was already mentioned in the manual: “Advanced partitioning/ If you have had a previous linux install and want to put the entire disk or just replace an entire partition you will need to unmount them. In this case running sudo swapoff -a will unmount them and any partitions with data mounted can be unmounted through pcmanfm-qt”. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835679 Title: Calamares don't offer a partitioning scheme on mmcblk devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1835679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Attachment added: "setup-sda.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275534/+files/setup-sda.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
Tests with I/O errors = The I/O error tests in the caching and backing device have been simulated with the device mapper dm-linear and dm-error targets. The tests are based on the patch messages, which describe a problem and/or expected behavior, so to exercise the change. Comparisons/comments between the original & modified/test kernels are provided in the next comments. The test script initially sets up fake DM devices in 'good' state with the linear target, and later can switch them to 'bad' state with the error target, and back again. (attached script: 'dm_fake_dev.sh') The bcache setup uses the DM devices above (for caching and backing devices) on top of loop devices in a virtual machine for flexibility. (attached script: 'setup.sh') One test uses a scsi-debug SCSI disk as backing device to offline it. (attached script: 'setup-sda.sh') One test uses 2 bcache devices with 1 shared cache device to ensure only one bcache device is stopped if 1 backing device has failures. (attached script: 'setup-two-bcache-one-cache.sh') -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835679] Re: Calamares don't offer a partitioning scheme on mmcblk devices
This issue is solved. This occurred because the eMMC card in the mmcblk devices must be unmounted before we install the OS to allow the automatic partitioning option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835679 Title: Calamares don't offer a partitioning scheme on mmcblk devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1835679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Attachment added: "setup-two-bcache-one-cache.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275535/+files/setup-two-bcache-one-cache.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Attachment added: "setup.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275533/+files/setup.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835181] Re: OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and ldap:// with STARTTLS
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835181 Title: OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and ldap:// with STARTTLS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1835181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Attachment added: "test-bcache-cache-modes.fio.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275532/+files/test-bcache-cache-modes.fio.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
Tests with fio == The fio tool has been run for performance tests on the original and modified kernels in sequential (rw) and random read/write (randrw) on all cache modes available (writethrough, writeback, writearound, none). Summary: no regressions observed, same IOPS and BW metrics, run three times (test1, test2, test3) on 'orig' and 'test'. # fio \ --name=test \ --filename=/dev/bcache0 \ --runtime=180s \ --ioengine=libaio \ --rw=$RW_MODE \ --bs=4k \ --iodepth=16 \ --numjobs=8 \ --group_reporting (attached script: 'test-bcache-cache-modes.fio.sh') Details: --- The bcache device is made of - caching device: 100 GB partition in NVMe drive - backing device: 1 TB partition in SCSI disk $ dpkg -s fio | grep Version: Version: 3.1-1 # grep -e read: -e write: fio.test*/fio.*/fio.test.*.log | sed 's,/fio, fio,g' | sort -s -k4,4 -k3,3 -k2,2 fio.test1 fio.orig fio.test.none.randrw.log: read: IOPS=79, BW=318KiB/s (325kB/s)(55.9MiB/180092msec) fio.test2 fio.orig fio.test.none.randrw.log: read: IOPS=81, BW=328KiB/s (336kB/s)(57.7MiB/180137msec) fio.test3 fio.orig fio.test.none.randrw.log: read: IOPS=80, BW=324KiB/s (331kB/s)(56.9MiB/180142msec) fio.test1 fio.test fio.test.none.randrw.log: read: IOPS=81, BW=326KiB/s (334kB/s)(57.4MiB/180222msec) fio.test2 fio.test fio.test.none.randrw.log: read: IOPS=80, BW=324KiB/s (331kB/s)(56.0MiB/180177msec) fio.test3 fio.test fio.test.none.randrw.log: read: IOPS=77, BW=312KiB/s (319kB/s)(54.8MiB/180103msec) fio.test1 fio.orig fio.test.none.rw.log: read: IOPS=81.8k, BW=319MiB/s (335MB/s)(56.2GiB/180023msec) fio.test2 fio.orig fio.test.none.rw.log: read: IOPS=82.7k, BW=323MiB/s (339MB/s)(56.8GiB/180070msec) fio.test3 fio.orig fio.test.none.rw.log: read: IOPS=82.8k, BW=323MiB/s (339MB/s)(56.9GiB/180006msec) fio.test1 fio.test fio.test.none.rw.log: read: IOPS=83.2k, BW=325MiB/s (341MB/s)(57.1GiB/180035msec) fio.test2 fio.test fio.test.none.rw.log: read: IOPS=85.2k, BW=333MiB/s (349MB/s)(58.5GiB/180030msec) fio.test3 fio.test fio.test.none.rw.log: read: IOPS=82.9k, BW=324MiB/s (339MB/s)(56.9GiB/180003msec) fio.test1 fio.orig fio.test.writearound.randrw.log: read: IOPS=78, BW=315KiB/s (322kB/s)(55.3MiB/180123msec) fio.test2 fio.orig fio.test.writearound.randrw.log: read: IOPS=78, BW=313KiB/s (321kB/s)(55.1MiB/180114msec) fio.test3 fio.orig fio.test.writearound.randrw.log: read: IOPS=81, BW=325KiB/s (333kB/s)(57.2MiB/180108msec) fio.test1 fio.test fio.test.writearound.randrw.log: read: IOPS=81, BW=324KiB/s (332kB/s)(57.0MiB/180107msec) fio.test2 fio.test fio.test.writearound.randrw.log: read: IOPS=78, BW=315KiB/s (323kB/s)(55.4MiB/180069msec) fio.test3 fio.test fio.test.writearound.randrw.log: read: IOPS=78, BW=312KiB/s (320kB/s)(54.9MiB/180109msec) fio.test1 fio.orig fio.test.writearound.rw.log: read: IOPS=81.8k, BW=319MiB/s (335MB/s)(56.2GiB/180046msec) fio.test2 fio.orig fio.test.writearound.rw.log: read: IOPS=81.6k, BW=319MiB/s (334MB/s)(56.0GiB/180004msec) fio.test3 fio.orig fio.test.writearound.rw.log: read: IOPS=82.7k, BW=323MiB/s (339MB/s)(56.8GiB/180002msec) fio.test1 fio.test fio.test.writearound.rw.log: read: IOPS=82.8k, BW=323MiB/s (339MB/s)(56.9GiB/180097msec) fio.test2 fio.test fio.test.writearound.rw.log: read: IOPS=79.6k, BW=311MiB/s (326MB/s)(54.6GiB/180003msec) fio.test3 fio.test fio.test.writearound.rw.log: read: IOPS=81.7k, BW=319MiB/s (335MB/s)(56.1GiB/180056msec) fio.test1 fio.orig fio.test.writeback.randrw.log: read: IOPS=81, BW=327KiB/s (335kB/s)(57.5MiB/180146msec) fio.test2 fio.orig fio.test.writeback.randrw.log: read: IOPS=79, BW=318KiB/s (326kB/s)(55.9MiB/180075msec) fio.test3 fio.orig fio.test.writeback.randrw.log: read: IOPS=80, BW=321KiB/s (329kB/s)(56.5MiB/180103msec) fio.test1 fio.test fio.test.writeback.randrw.log: read: IOPS=80, BW=324KiB/s (331kB/s)(56.9MiB/180082msec) fio.test2 fio.test fio.test.writeback.randrw.log: read: IOPS=79, BW=317KiB/s (325kB/s)(55.8MiB/180106msec) fio.test3 fio.test fio.test.writeback.randrw.log: read: IOPS=79, BW=316KiB/s (324kB/s)(55.6MiB/180144msec) fio.test1 fio.orig fio.test.writeback.rw.log: read: IOPS=72.4k, BW=283MiB/s (297MB/s)(49.7GiB/180097msec) fio.test2 fio.orig fio.test.writeback.rw.log: read: IOPS=97.6k, BW=381MiB/s (400MB/s)(67.1GiB/180238msec) fio.test3 fio.orig fio.test.writeback.rw.log: read: IOPS=82.9k, BW=324MiB/s (339MB/s)(56.9GiB/180002msec) fio.test1 fio.test fio.test.writeback.rw.log: read: IOPS=81.5k, BW=318MiB/s (334MB/s)(55.0GiB/180002msec) fio.test2 fio.test fio.test.writeback.rw.log: read: IOPS=72.1k, BW=282MiB/s (295MB/s)(49.5GiB/180165msec) fio.test3 fio.test fio.test.writeback.rw.log: read: IOPS=81.8k, BW=319MiB/s (335MB/s)(56.2GiB/180037msec) fio.test1 fio.orig fio.test.writethrough.randrw.log: read: IOPS=80, BW=321KiB/s (329kB/s)(56.5MiB/180137msec) fio.test2 fio.orig
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
Tests with xfstests === The xfstests test suite has been run on the original and modified kernels -- on all cache modes available (writethrough, writeback, writearound, none). Summary: no regressions observed; apparently one FIX achieved in the writearound cache mode (generic/371). (attached script: 'test-bcache-cache-modes.sh') Details: --- The bcache device is made of - caching device: 1 GB partition in NVMe drive - backing device: 5 GB partition in SCSI disk ubuntu@buneary:~/xfstests-dev$ git log --oneline -1 f769a923 (HEAD -> master, origin/master, origin/HEAD) xfs: project quota ineritance flag test The comparison of the output of xfstests/check script for the 'Failures' with original (orig) and modified (test) test kernels is provided below. # grep ^Failures: xfstests.*/xfstests.*.*.log | sed 's,/, ,' | sort -k 2,2 -k 1,1 xfstests.orig xfstests.test.none.log:Failures: ext4/032 generic/484 generic/491 generic/504 generic/537 xfstests.test xfstests.test.none.log:Failures: ext4/032 generic/484 generic/491 generic/504 generic/537 xfstests.orig xfstests.test.writearound.log:Failures: ext4/032 generic/371 generic/451 generic/484 generic/491 generic/504 generic/537 xfstests.test xfstests.test.writearound.log:Failures: ext4/032 <.> generic/451 generic/484 generic/491 generic/504 generic/537 xfstests.orig xfstests.test.writeback.log:Failures: generic/484 generic/491 generic/504 generic/537 xfstests.test xfstests.test.writeback.log:Failures: generic/484 generic/491 generic/504 generic/537 xfstests.orig xfstests.test.writethrough.log:Failures: ext4/032 generic/484 generic/491 generic/504 generic/537 xfstests.test xfstests.test.writethrough.log:Failures: ext4/032 generic/484 generic/491 generic/504 generic/537 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Attachment added: "test-bcache-cache-modes.xfstests.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275531/+files/test-bcache-cache-modes.xfstests.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834887] Re: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1835436 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:failed,signed:building + promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:failed variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834887 Title: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835679] Re: Calamares don't offer a partitioning scheme on mmcblk devices
** Summary changed: - ubuntu-bug calamares + Calamares don't offer a partitioning scheme on mmcblk devices ** Description changed: - Lubuntu 19.04: Calamares don't offer a partitioning scheme on mmcblk - devices - - - During installation on mmcblk devices, Calamares detects existing partitioning and OS but fails to offer automatic partitioning scheme, being necessary to do the partition manually. + Lubuntu 19.04: during installation on mmcblk devices, Calamares detects + existing partitioning and OS but fails to offer automatic partitioning + scheme, being necessary to do the partition manually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835679 Title: Calamares don't offer a partitioning scheme on mmcblk devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1835679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835679] Re: ubuntu-bug calamares
Please provide the Calamares log and check to see if anything's mounted first. Perhaps file a new bug with `ubuntu-bug calamares`. ** Changed in: lubuntu-meta (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/1835679 Title: Calamares don't offer a partitioning scheme on mmcblk devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1835679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683383]
Need some additional help with your essays Barely manage to complete all assignments in time? Stop worrying and contact the team of professional writers of the great essays and get rid of all tasks! https://great- essays.com/article/classification-and-division-essays/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835679] Re: Calamares don't offer a partitioning scheme on mmcblk devices
** Description changed: - Lubuntu 19.04: during the installation on mmcblk devices, Calamares - detects existing partitioning and OS but fails to offer automatic - partitioning scheme, being necessary to do the partition manually. + Lubuntu 19.04: Calamares don't offer a partitioning scheme on mmcblk + devices + + + During installation on mmcblk devices, Calamares detects existing partitioning and OS but fails to offer automatic partitioning scheme, being necessary to do the partition manually. ** Summary changed: - Calamares don't offer a partitioning scheme on mmcblk devices + ubuntu-bug calamares -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835679 Title: ubuntu-bug calamares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1835679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834887] Re: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1835436 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:failed + promote-to-proposed: Pending -- builds not complete in ppa main:failed,signed:building variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834887 Title: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833319] Re: Performance degradation when copying from LVM snapshot backed by NVMe disk
I enabled -proposed and installed 4.4.0-1088-aws #99-Ubuntu, and again went through the test case on a c5.large instance on aws. The problem is solved and performance is restored, and performs the same as a non-snapshot mounted disk. Again, we can see merging has been enabled with: $ cat /sys/block/nvme1n1/queue/nomerges 0 The problem is fixed. Happy with verification status of done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833319 Title: Performance degradation when copying from LVM snapshot backed by NVMe disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835679] [NEW] Calamares don't offer a partitioning scheme on mmcblk devices
Public bug reported: Lubuntu 19.04: during the installation on mmcblk devices, Calamares detects existing partitioning and OS but fails to offer automatic partitioning scheme, being necessary to do the partition manually. ** Affects: lubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Calamares Lubuntu 1904.jpg" https://bugs.launchpad.net/bugs/1835679/+attachment/5275530/+files/Calamares%20Lubuntu%201904.jpg ** Summary changed: - Calamares don't offer partitioning scheme in mmcblk devices + Calamares don't offer partitioning scheme on mmcblk devices ** Summary changed: - Calamares don't offer partitioning scheme on mmcblk devices + Calamares don't offer a partitioning scheme on mmcblk devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835679 Title: Calamares don't offer a partitioning scheme on mmcblk devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1835679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
** Package changed: ubuntu => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834887] Re: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1835436 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:failed,signed:building + promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:failed variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834887 Title: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835677] Re: Megal33t bug: touchpad with mousewheel is broken >:]
Hi. Logs aren't needed. >:] ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835677 Title: Megal33t bug: touchpad with mousewheel is broken >:] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
This failure has not been due to Juju but rather the setup of the CI environment. We have not seen any consecutive failures of this nature, so the issue has been resolved. I am closing this report. ** Changed in: juju Status: Incomplete => Fix Released ** Changed in: dbus (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/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834887] Re: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1835436 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:failed + promote-to-proposed: Pending -- builds not complete in ppa main:failed,signed:building variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834887 Title: linux-azure-edge: 5.0.0-1012.12~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
