[Bug 1814830] Re: recent linux versions 44 and 45 do not start up
That the old version of the boot loader was not replaced might be an oversight in the updater or a feature for those systems which where installed a very long time ago. (If you are interested, see [1]). Reading [2] it sounds like it is necessary to remove menu.lst before it will get re-generated again: * sudo mv /boot/grub/menu.lst /boot/grub/menu.lst.save * sudo update-grub If menu.lst is not re-created by the update-grub command you will have to rename the saved copy back, otherwise you should be ok. [1] https://help.ubuntu.com/community/Grub2/Upgrading [2] https://ubuntuforums.org/showthread.php?t=873448 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814830 Title: recent linux versions 44 and 45 do not start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746012] Re: please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..."
Affected on 16.04 as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746012 Title: please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1746012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815008] [NEW] package vim-syntastic 3.7.0-1+deb9u2build0.16.04.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported: No detail ProblemType: Package DistroRelease: Ubuntu 16.04 Package: vim-syntastic 3.7.0-1+deb9u2build0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Feb 7 08:01:43 2019 DpkgHistoryLog: Start-Date: 2019-02-07 08:01:24 Commandline: /usr/bin/unattended-upgrade Install: linux-headers-4.4.0-142:amd64 (4.4.0-142.168, automatic), linux-image-4.4.0-142-generic:amd64 (4.4.0-142.168, automatic), linux-signed-image-4.4.0-142-generic:amd64 (4.4.0-142.168, automatic), linux-image-extra-4.4.0-142-generic:amd64 (4.4.0-142.168, automatic), linux-headers-4.4.0-142-generic:amd64 (4.4.0-142.168, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.141.147, 4.4.0.142.148), linux-libc-dev:amd64 (4.4.0-141.167, 4.4.0-142.168), linux-image-generic:amd64 (4.4.0.141.147, 4.4.0.142.148), linux-signed-image-generic:amd64 (4.4.0.141.147, 4.4.0.142.148), linux-signed-generic:amd64 (4.4.0.141.147, 4.4.0.142.148), linux-generic:amd64 (4.4.0.141.147, 4.4.0.142.148) ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2016-10-07 (852 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: vim-syntastic Title: package vim-syntastic 3.7.0-1+deb9u2build0.16.04.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim-syntastic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815008 Title: package vim-syntastic 3.7.0-1+deb9u2build0.16.04.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim-syntastic/+bug/1815008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
I can confirm that this bug exists on 18.04 and 18.10 on a Intel NUC 8i3BEH (with latest BIOS, 0056). After a few seconds after boot, the RTT spikes to well over 1s and makes the system unusable. Device: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-V (rev 30) Subsystem: Intel Corporation Ethernet Connection (6) I219-V Flags: bus master, fast devsel, latency 0, IRQ 127 Memory at c010 (32-bit, non-prefetchable) [size=128K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: e1000e Kernel modules: e1000e # ethtool -i eno1 driver: e1000e version: 3.2.6-k firmware-version: 0.4-4 expansion-rom-version: bus-info: :00:1f.6 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no Forcing the speed of the interface to 100 with autonegotiation off (via ethtool --change eno1 speed 100 autoneg off) helps somewhat - answer times stay around a few ms. Since changing the power management settings seems to solve this issue, i tried various options: Disable intel_pstate, change the governor to performance, forcing full frequency, etc. without luck. However, disabling PCIe ASPM *in the BIOS* solved the issue for me - at the price of a somewhat higher power consumption (around +5W). Please note that using pcie_aspm=off in the kernel command line (linux-image-4.18.0-14-generic) *did not work*. Here is the dmesg snippet with ASPM disabled in the BIOS: # dmesg | grep -i aspm [0.041040] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [0.177567] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.181078] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration Please let me know, if you need more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804408] Re: [19.04 FEAT] LUKS2 support for pam_mount
Thanks ifranzki, I also added automated tests to the packages on the SRU as well as in Debian [1]. Test results look good atm and will give the whole thing some more confidence: Cosmic with fix: http://paste.ubuntu.com/p/nfwBTqBdP9/ Cosmic without: http://paste.ubuntu.com/p/2rzYZJ3RYJ/ Bionic with fix: http://paste.ubuntu.com/p/WwFDY99dNh/ All we need now is a review on the MPs to check for oversights or silly mistakes - that should happen today and then I can upload to the SRU queue. [1]: https://salsa.debian.org/debian/libpam-mount/merge_requests/1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804408 Title: [19.04 FEAT] LUKS2 support for pam_mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1804408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814403] Re: Latest update causes 30 sec. menu delay timeout
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2-signed (Ubuntu Bionic) 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/1814403 Title: Latest update causes 30 sec. menu delay timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1814403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815002] Re: quick-boot-lvm.patch caused regression - menu always appear if root is on Btrfs
*** This bug is a duplicate of bug 1814403 *** https://bugs.launchpad.net/bugs/1814403 ** This bug has been marked a duplicate of bug 1814403 Latest update causes 30 sec. menu delay timeout -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815002 Title: quick-boot-lvm.patch caused regression - menu always appear if root is on Btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1815002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814403] Re: Latest update causes 30 sec. menu delay timeout
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2-signed (Ubuntu Cosmic) 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/1814403 Title: Latest update causes 30 sec. menu delay timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1814403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567050] Re: Geary sometimes crashes when I open an unread mail
Per comment #2 I'd need a stack trace to work this out, so resolving as incomplete for the moment. If someone can produce a stack trace, please report it over in GitLab: https://gitlab.gnome.org/GNOME/geary ** Changed in: geary (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/1567050 Title: Geary sometimes crashes when I open an unread mail To manage notifications about this bug go to: https://bugs.launchpad.net/geary/+bug/1567050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815002] [NEW] quick-boot-lvm.patch caused regression - menu always appear if root is on Btrfs
Public bug reported: Comments about this regression: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1800722/comments/12 https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1800722/comments/13 In my case menu starting to always appear on various devices from small tablets to workstations. First time it happened with laptop https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/736743/comments/95 and since then more devices became affected. I not 100% sure, but seems like at least one unsuccessfully boot is required to reproduce this issue, but maybe I am mistake here and issue starting to happen for all Btrfs users. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815002 Title: quick-boot-lvm.patch caused regression - menu always appear if root is on Btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1815002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
@kmously I can confirm that that kernel does NOT fix my problem, aka the system does not boot up with that kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
I looked up the "325f8e18c8ac drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5" commit and it looks like the Tails distro had the same issue with that commit https://redmine.tails.boum.org/code/issues/16224 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
I have an HD 5870. I'm not using any additional or proprietary drivers (according to that tab in Software & Updates); however, 'Proprietary drivers for devices' is enabled in the Ubuntu Software tab in Software & Updates. The only PPAs I have are for Google Chrome, PlayOnLinux, and Alexander Larsson's Launchpad. For my video card information: Cypress XT [Radeon HD 5870] Vendor: AMD/ATI Phys. ID: 0 version: 00 clock: 33MHz driver: radeon I'm not sure exactly which information you need, so here is a pastebin of the output of 'modinfo radeon': https://pastebin.com/axFRR5hw. I'm honestly not sure what to provide, so if you want the output of some commands, I can provide those easily if you tell me which/what you'd like. I didn't find any GUI-level information on my drivers or what packages they are, so that's the best I could find in the time I have for this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Changed in: ubuntu-z-systems Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583136] Re: ooo-thumbnailer doesn't work in directories with spaces
** Changed in: ooo-thumbnailer (Debian) 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/583136 Title: ooo-thumbnailer doesn't work in directories with spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ooo-thumbnailer/+bug/583136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814258] Re: USN-3867-1: Partially applies to MariaDB too
The 10.1 series update for 18.04 is now available. Please use git-buildpackage to fetch and build from the ubuntu-18.04 branch at https://salsa.debian.org/mariadb- team/mariadb-10.1/tree/ubuntu-18.04 The repository uses pristine-tar, so there is no need to separately download the sources. You can just check the signature/SHA1SUM directly from the git-buildpackage generated tarball. Test builds and testsuite passed on all platforms at https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.1/+builds?build_text=_state=all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814258 Title: USN-3867-1: Partially applies to MariaDB too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1814258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814997] [NEW] [MIR] libxmlb
Public bug reported: Rationale: libxmlb is both a build and runtime dependency for fwupd 1.2.x and later. It is also a dependency for newer versions of gnome-software and may eventually be a dependency of appstream. Quality assurance: No configuration needed No debconf questions No long term outstanding bugs No known major bugs in Debian, Ubuntu or upstream tracker. Maintained in Debian by EFI team Runs test suite during build Uses debian/watch Standards: Should be compatible to policy 4.3.0 Maintenance: Should be set to Ubuntu foundations However expected to be synced regularly Security: No CVES No services No ports open No executables in /sbin /usr/sbin No suid or sgid ** Affects: libxmlb (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [MIR] Promote libxmlb to main + [MIR] libxmlb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814997 Title: [MIR] libxmlb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxmlb/+bug/1814997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
@P.D. That's surprising. In that case, it means the offending commit is "325f8e18c8ac drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5". I was expecting the offending commit to be "d8370b8fbadf drm/i915/execlists: Force write serialisation into context image vs execution" because that appears to have been identified upstream as causing a regression with symptoms similar to what you're experiencing (the regression has upstream commit ID 987abd5c62f9 and the fix for it is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cf66b8a0ba142fbd1bf10ac8f3ae92d1b0cb7b8f ) I had built a kernel with the upstream fix for you to test and was expecting it would fix your problem. Do you mind trying it anyway to confirm that it does NOT fix your problem? That kernel is built from commit: 619b700ded65 drm/i915/execlists: Apply a full mb before execution for Braswell and can be found at: https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-619b700-ouqM/ Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814993] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1814993 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814993 Title: linux kernel 4.15.0-44 and 4.15.0-45 break tty login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814993] Re: linux kernel 4.15.0-44 and 4.15.0-45 break tty login
Additional information on installed (working) kernel, as the data provided by apt cache did not show it: linux-image-4.15.0-43-generic/bionic-updates,bionic-security 4.15.0-43.46 i386 linux-image-unsigned-4.15.0-43-generic/bionic-updates,bionic-security 4.15.0-43.46 amd64 linux-modules-4.15.0-43-generic/bionic-updates,bionic-security,now 4.15.0-43.46 amd64 [installed,automatic] linux-modules-extra-4.15.0-43-generic/bionic-updates,bionic-security,now 4.15.0-43.46 amd64 [installed] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814993 Title: linux kernel 4.15.0-44 and 4.15.0-45 break tty login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
@kmously Unfortunately, the eighth kernel doesn't boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802652] Re: keyboard backlight not working on Asus GM501
Different. I'm on an ASUS ROG GL502VM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802652 Title: keyboard backlight not working on Asus GM501 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814993] [NEW] linux kernel 4.15.0-44 and 4.15.0-45 break tty login
Public bug reported: On systems with either version of the kernel installed (4.15.0-44 or 4.15.0-45), login to the console (tty) is not possible. When the prior version, 4.15.0-43, is running this issue does not occur. 1) The release of Ubuntu via 'lsb_release -rd': Description:Ubuntu 18.04.1 LTS Release:18.04 2) The version of the package, via 'apt-cache policy pkgname' linux-generic: Installed: (none) Candidate: 4.15.0.45.47 Version table: 4.15.0.45.47 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 4.15.0.20.23 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) What I expected to happen: Normal login via tty 4) What happened instead login program would not allow login process to proceed, password prompts were interrupted. ** Affects: linux (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/1814993 Title: linux kernel 4.15.0-44 and 4.15.0-45 break tty login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
Also I did a lot of docking and unlocking (I've got 3 screen setup - built-in and two external monitors) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
Hi all, can you cross check if you have any of these Gnome Shell plug-ins installed ? https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813248/comments/10 I had both. First I uninstalled gnome-shell-extension-multi-monitors, did not help. Next, I uninstalled gnome-shell-extension-system-monitor. Many meetings, back and forth to my office, home, etc. AS it is for now, over last 3 days no issues with unlocking. Finger crossed it stays this way. ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814992] [NEW] Getting "Authentication Failed" and "Switch to greeter" message on login screen
Public bug reported: A few months back I had the same problem, then I installed lightdm and ran it and since then bug was gone. But 2 days back I got the same bug, I tried running lightdm again, so to stop it I ran sudo stop lightdm but it gives out the message "unable to connect to upstart" and ends. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 7 09:42:53 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-06-07 (244 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814992 Title: Getting "Authentication Failed" and "Switch to greeter" message on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1814992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1034878] Re: gedit doesn't notice when an open file is replaced by an older version
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (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/1034878 Title: gedit doesn't notice when an open file is replaced by an older version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1034878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147179] Re: some toolbar settings are lost during mozilla thunderbird upgrade
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (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/147179 Title: some toolbar settings are lost during mozilla thunderbird upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/147179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264818] Re: Reload file button doesn't show when File explorer is visible
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (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/1264818 Title: Reload file button doesn't show when File explorer is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103183] Re: gedit does not start from gnome-shell files search in activities overview
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (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/1103183 Title: gedit does not start from gnome-shell files search in activities overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1103183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105536] Re: When replying to an email the field to: is blank
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (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/105536 Title: When replying to an email the field to: is blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/105536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 245219] Re: Ubuntu archive server returning incorrect content-encoding - content-header incorrect type
I'm real sorry to waste bandwidth like this, but I just want to let y'all know that I'm LOLing at this point. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/245219 Title: Ubuntu archive server returning incorrect content-encoding - content- header incorrect type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-archive-publishing/+bug/245219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980432] Re: language endcoding auto-dectected always failed, I should choose Gb18030 or GBK encoding every time, though I've add the languages to auto_dectected encoding list.
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (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/980432 Title: language endcoding auto-dectected always failed,I should choose Gb18030 or GBK encoding every time,though I've add the languages to auto_dectected encoding list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/980432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773796] Re: Segmentation fault in __strcmp_ssse3
[Expired for glibc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: glibc (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/1773796 Title: Segmentation fault in __strcmp_ssse3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1773796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790020] Re: /sbin/ldconfig.real: Path `/lib/x86_64-linux-gnu' given more than once
[Expired for glibc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: glibc (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/1790020 Title: /sbin/ldconfig.real: Path `/lib/x86_64-linux-gnu' given more than once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1790020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807376] Re: can not upgrade to release 18.04 from 16.04
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807376 Title: can not upgrade to release 18.04 from 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1807376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725792] Re: Word-wrap breaks in windows with small width
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (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/1725792 Title: Word-wrap breaks in windows with small width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1725792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778915] Re: package sweethome3d 5.7+dfsg-2 failed to install/upgrade: problemas de dependência - deixando desconfigurado
[Expired for sweethome3d (Ubuntu) because there has been no activity for 60 days.] ** Changed in: sweethome3d (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/1778915 Title: package sweethome3d 5.7+dfsg-2 failed to install/upgrade: problemas de dependência - deixando desconfigurado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sweethome3d/+bug/1778915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794899] Re: ghex both installed and not-installed
[Expired for ghex (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ghex (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/1794899 Title: ghex both installed and not-installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghex/+bug/1794899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807323] Re: Unable to update 18.04 to 18.10
[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/1807323 Title: Unable to update 18.04 to 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1807323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814991] [NEW] 'lock' glitch
Public bug reported: >From within gnome: I left-click 'triangle' I left-click on the lock the screen gets stuck where it doesn't go to the lock screen, but instead the lock icon flashes orange, then back to brown, then back to orange, then back to brown over and over again. I can still move the mouse but I can't click on anything Shift-Alt-F3 gets me to a terminal, then Shift-Alt-f2 or f1 gets me back...and then there's a lock screen. It's done this twice now. ubuntu: 18.04 LTS bionic gnome: 3.28.2 graphics: Intel® HD Graphics 630 (Kaby Lake GT2) OS Type: 64-bit xserver-xorg-video-intel: 2:2.99.917+git20171229-1 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814991 Title: 'lock' glitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1814991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814938] Re: drm.edid_firmware fails to load firmware where crypsetup-initramfs is installed
[drm:drm_load_edid_firmware [drm]] *ERROR* Requesting EDID firmware "edid/edid1.bin" failed (err=-2) user@user:~$ ls -la /usr/lib/firmware/edid/edid.bin -rw-r--r-- 1 root root 256 1月 27 13:15 /usr/lib/firmware/edid/edid.bin user@user:~$ ls -la /lib/firmware/edid/edid.bin -rw-r--r-- 1 root root 256 1月 27 13:18 /lib/firmware/edid/edid.bin user@user:~$ cat /etc/default/grub |grep firmware GRUB_CMDLINE_LINUX_DEFAULT="drm.edid_firmware=/lib/firmware/edid/edid.bin quiet splash" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814938 Title: drm.edid_firmware fails to load firmware where crypsetup-initramfs is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
See if you have any *cups* packages installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
@kmously The seventh kernel doesn't boot up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
I'll test the 8th one when it becomes available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813833] Re: User without read permission on cron.allow can execute crontab
Hello Brandon, I wasn't able to use an untrusted user account to induce this behaviour. So, I'm making this bug public so that more people can be made aware of the misconfiguration that is being encouraged. It's unfortunate that the providers of this advice never actually tested it themselves. It's unfortunate that the cron manpages don't detail proper permissions for these files. It's unfortunate that crontab(1) doesn't perform this access control check while it has root privileges. It's perhaps most especially unfortunate that this check isn't actually performed by cron(8) at all -- a user listed in /etc/cron.deny isn't actually denied running cron jobs, but is denied managing cron jobs. Existing configurations would keep working. (Probably this is not news to most sysadmins but I'd long since forgotten this detail.) So now, the question is what remediation do we take? - adjusting cron(8) feels like a good idea but would take a fair chunk of effort to not be silly about the implementation. It might also break configurations using the 'gatekeeping' feature of crontab(1). - adjusting crontab(1). I'm not sure how much work this would take but feels like a good approach. - fixing the manpages to describe the correct permissions. This feels like a good idea regardless of changes we may make to crontab(1). Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1813833 Title: User without read permission on cron.allow can execute crontab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1813833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
@P.D.: I also have the eighth (and final) kernel almost ready for you. It is based on commit: 325f8e18c8ac drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5 and it should be available at: https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-325f8e1-2dRL in about 40 minutes. This should be the last kernel that you'll need to test for bisection. I think the problematic change is "drm/i915/execlists: Force write serialisation into context image vs execution". This can be confirmed by confirming that the eighth kernel (which does not have that change) boots fine. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
@P.D. Thanks for the feedback. I have the seventh kernel for you based on commit: d8370b8fbadf drm/i915/execlists: Force write serialisation into context image vs execution You can download the test kernel from: https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-d8370b8-MWga/ Please let me know if this kernel shows the same problem or not. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814983] Re: zfs poor sustained read performance from ssd pool
Oh yes, and perf top output after dropping caches: Samples: 11M of event 'cycles:ppp', Event count (approx.): 648517108833 Overhead Shared Object Symbol 19.77% [kernel][k] zfs_prune 18.96% [kernel][k] _raw_spin_lock 12.89% [kernel][k] d_prune_aliases 7.12% [kernel][k] igrab 7.10% [kernel][k] _atomic_dec_and_lock 6.98% [kernel][k] iput 2.24% [kernel][k] Skein_512_Process_Block 1.65% [kernel][k] arc_evict_state 0.89% [kernel][k] lz4_decompress_zfs 0.78% [kernel][k] mutex_unlock 0.78% [kernel][k] mutex_lock 0.69% [kernel][k] native_queued_spin_lock_slowpath 0.52% [kernel][k] clear_page_erms 0.46% [kernel][k] _raw_spin_lock_irqsave 0.44% [kernel][k] Skein_Get64_LSB_First 0.35% [kernel][k] __schedule 0.27% [kernel][k] mutex_trylock 0.26% [kernel][k] kmem_cache_free 0.26% [kernel][k] _cond_resched 0.23% [kernel][k] arc_space_consume 0.21% [kernel][k] kmem_cache_alloc 0.20% [kernel][k] menu_select 0.20% [kernel][k] multilist_sublist_move_forward 0.19% [kernel][k] arc_space_return 0.18% [kernel][k] taskq_thread 0.18% [kernel][k] __cv_signal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814983 Title: zfs poor sustained read performance from ssd pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1814983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814983] Re: zfs poor sustained read performance from ssd pool
Debugging by voodoo dolls: I made a wild guess that stumbling over cached objects was getting in the way. I dropped caches with: echo 3 > /proc/sys/vm/drop_caches and immediately the read iops to the pool skyrocketed and the ripgrep output sure looks like it's going WAY faster: capacity operations bandwidth pool alloc free read write read write --- - - - - - - fst 1.15T 679G 75 0 403K 0 mirror 588G 340G 35 0 211K 0 sdj - - 23 0 128K 0 sdk - - 11 0 83.7K 0 mirror 588G 340G 39 0 191K 0 sdl - - 16 0 79.7K 0 sdm - - 22 0 112K 0 --- - - - - - - srv 1.30T 6.86T 5 0 47.8K 0 mirror 443G 2.29T 1 0 15.9K 0 ata-HGST_HUS724030ALA640_PN2234P8KTWJYY - - 0 0 7.97K 0 ata-HGST_HUS724030ALA640_PN2234P9G620TW - - 0 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G66E2U - - 0 0 7.97K 0 mirror 443G 2.29T 0 0 7.97K 0 ata-HGST_HUS724030ALA640_PN2234P9G69TKU - - 0 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G69TXU - - 0 0 7.97K 0 ata-HGST_HUS724030ALA640_PN2234P9G69U2U - - 0 0 0 0 mirror 443G 2.29T 2 0 23.9K 0 ata-HGST_HUS724030ALA640_PN2234P9G6EBUU - - 0 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G6ESAU - - 0 0 7.97K 0 ata-HGST_HUS724030ALA640_PN2234P9G6G70U - - 1 0 15.9K 0 logs - - - - - - nvme0n1p1 900K 19.9G 0 0 0 0 cache- - - - - - nvme0n1p2 334G 764G 3 0 16.4K 0 --- - - - - - - capacity operations bandwidth pool alloc free read write read write --- - - - - - - fst 1.15T 679G 67 0 375K 0 mirror 588G 340G 43 0 255K 0 sdj - - 25 0 147K 0 sdk - - 17 0 108K 0 mirror 588G 340G 23 0 120K 0 sdl - - 6 0 31.9K 0 sdm - - 16 0 87.7K 0 --- - - - - - - srv 1.30T 6.86T 3 0 15.9K 0 mirror 443G 2.29T 0 0 3.99K 0 ata-HGST_HUS724030ALA640_PN2234P8KTWJYY - - 0 0 3.99K 0 ata-HGST_HUS724030ALA640_PN2234P9G620TW - - 0 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G66E2U - - 0 0 0 0 mirror 443G 2.29T 1 0 7.97K 0 ata-HGST_HUS724030ALA640_PN2234P9G69TKU - - 0 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G69TXU - - 0 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G69U2U - - 1 0 7.97K 0 mirror 443G 2.29T 0 0 3.99K 0 ata-HGST_HUS724030ALA640_PN2234P9G6EBUU - - 0 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G6ESAU - - 0 0 3.99K 0 ata-HGST_HUS724030ALA640_PN2234P9G6G70U - - 0 0 0 0 logs - - - - - - nvme0n1p1
[Bug 1814983] Re: zfs poor sustained read performance from ssd pool
And top(1) output after dropping caches: top - 18:42:09 up 70 days, 18:18, 3 users, load average: 17.33, 22.19, 27.87 Tasks: 826 total, 2 running, 644 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.2 us, 22.9 sy, 0.0 ni, 63.3 id, 11.5 wa, 0.0 hi, 1.1 si, 0.0 st GiB Mem : 125.805 total, 32.176 free, 91.669 used,1.960 buff/cache GiB Swap:5.694 total,5.688 free,0.007 used. 33.172 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 13548 sarnold 20 0 9231484 8.695g 3836 S 340.8 6.9 96:59.86 rg 2 root 20 0 0 0 0 S 23.7 0.0 38:06.54 kthreadd 1523 root 20 0 0 0 0 S 16.4 0.0 419:11.17 arc_reclaim 8491 root 0 -20 0 0 0 R 14.8 0.0 5:56.88 z_rd_int_0 8494 root 0 -20 0 0 0 S 14.8 0.0 5:56.75 z_rd_int_3 8489 root 0 -20 0 0 0 S 14.5 0.0 6:52.34 z_null_int 8492 root 0 -20 0 0 0 S 14.5 0.0 5:56.99 z_rd_int_1 8498 root 0 -20 0 0 0 S 14.5 0.0 5:56.66 z_rd_int_6 8499 root 0 -20 0 0 0 S 14.5 0.0 5:56.71 z_rd_int_7 8493 root 0 -20 0 0 0 S 14.1 0.0 5:56.58 z_rd_int_2 8495 root 0 -20 0 0 0 S 14.1 0.0 5:56.75 z_rd_int_4 8497 root 0 -20 0 0 0 S 14.1 0.0 5:56.61 z_rd_int_5 1271 root 0 -20 0 0 0 D 11.2 0.0 18:28.48 spl_dynamic_tas 1531 root 39 19 0 0 0 S 10.5 0.0 21:26.74 dbuf_evict 1522 root 20 0 0 0 0 S 8.2 0.0 228:11.90 arc_prune 3790 root 0 -204520 1648 1556 S 6.6 0.0 13:23.43 atopacctd 6457 mirror21 1 70928 30628 2976 D 5.6 0.0 0:44.18 rsync 30826 root 20 0 0 0 0 S 3.0 0.0 0:00.09 arc_prune 1272 root 0 -20 0 0 0 S 2.0 0.0 3:39.48 spl_kmem_cache 15868 root 20 0 0 0 0 S 1.0 0.0 0:00.03 arc_prune 16231 root 20 0 0 0 0 S 1.0 0.0 0:00.03 arc_prune 533 root 0 -20 0 0 0 I 0.7 0.0 1:38.82 kworker/3:1H 601 root 0 -20 0 0 0 I 0.7 0.0 1:37.84 kworker/21:1H 1530 root 20 0 0 0 0 S 0.7 0.0 7:11.37 dbu_evict 2116 root 20 0 0 0 0 I 0.7 0.0 0:18.64 kworker/1:1 4489 root 20 09916848664 S 0.7 0.0 6:18.54 rngd 7302 root 20 0 0 0 0 I 0.7 0.0 0:16.69 kworker/5:1 8952 root 20 0 0 0 0 I 0.7 0.0 0:22.74 kworker/2:2 12217 root 20 0 0 0 0 I 0.7 0.0 0:21.09 kworker/27:2 12258 sarnold 20 0 42620 4568 3256 R 0.7 0.0 0:00.42 top 16346 root 20 0 0 0 0 S 0.7 0.0 0:00.02 arc_prune 16394 root 20 0 0 0 0 S 0.7 0.0 0:00.02 arc_prune -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814983 Title: zfs poor sustained read performance from ssd pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1814983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813833] Re: User without read permission on cron.allow can execute crontab
** Information type changed from Private Security 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/1813833 Title: User without read permission on cron.allow can execute crontab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1813833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813833] [NEW] User without read permission on cron.allow can execute crontab
*** This bug is a security vulnerability *** You have been subscribed to a public security bug by Seth Arnold (seth-arnold): /etc/cron.allow is meant to list the users who are allowed to execute crontab. For a user who is not listed, the output should be: $ crontab -e You (ubuntu) are not allowed to use this program (crontab) See crontab(1) for more information When /etc/cron.allow is not readable by that user, though, it's treated as though the file doesn't exist at all: $ sudo chmod o-r /etc/cron.allow $ crontab -e crontab: installing new crontab The obvious workaround is to ensure that /etc/cron.allow is world readable, but unfortunately there are a lot of security tools and documentation out there that explicitly require both using cron.allow and also setting the permission on cron-related files to 600. Examples include https://secscan.acron.pl/ubuntu1604/5/1/8 and the CIS Level 1 benchmark for Ubuntu. The result of this bug is that a sysadmin attempting to lock down cron by following standard security guidance will fail to do so. ** Affects: cron (Ubuntu) Importance: Undecided Status: New -- User without read permission on cron.allow can execute crontab https://bugs.launchpad.net/bugs/1813833 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
@kmously The sixth kernel boots up fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811248] Re: systemd--networkd mounts denied for lxc guest
https://github.com/lxc/lxd/issues/5439#issuecomment-461257784 > The fix in LXD is only partial because there's currently no safe way for us to fix that for privileged containers due to an apparmor parser bug that the AppArmor team is still working on. So we've made the change only to the unprivileged policy for now as the AppArmor bug isn't causing too much damage in that case. There's no such distinction in profile in LXC, so putting those same lines in the LXC policy would allow every user to bypass all mount protections, which isn't acceptable from a security point of view. So the LXC fix is effectively blocked on the AppArmor security bug being resolved first. ** This bug is no longer a duplicate of bug 1813622 systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd ** Bug watch added: LXD bug tracker #5439 https://github.com/lxc/lxd/issues/5439 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811248 Title: systemd--networkd mounts denied for lxc guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
Recently I formatted and reinstalled the version 18.04.1 Now the overheating problem is gone. Everything is working just fine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814983] Re: zfs poor sustained read performance from ssd pool
sudo perf top output: Samples: 1M of event 'cycles:ppp', Event count (approx.): 476944550835 Overhead Shared Object Symbol 24.93% [kernel] [k] _raw_spin_lock 21.52% [kernel] [k] zfs_prune 17.29% [kernel] [k] d_prune_aliases 9.48% [kernel] [k] _atomic_dec_and_lock 9.20% [kernel] [k] iput 7.95% [kernel] [k] igrab 0.75% [kernel] [k] arc_evict_state 0.50% [kernel] [k] clear_page_erms 0.48% [kernel] [k] mutex_unlock 0.39% [kernel] [k] arc_space_consume 0.36% [kernel] [k] hdr_full_cons 0.36% [kernel] [k] arc_space_return 0.34% [kernel] [k] mutex_lock 0.28% [kernel] [k] kmem_cache_free 0.27% [kernel] [k] spl_kmem_cache_alloc 0.24% [kernel] [k] __cv_destroy 0.22% [kernel] [k] multilist_sublist_unlock 0.22% [kernel] [k] _raw_spin_lock_irqsave 0.20% [kernel] [k] _cond_resched 0.20% [kernel] [k] kmem_cache_alloc 0.17% [kernel] [k] multilist_sublist_lock 0.14% [kernel] [k] rcu_all_qs 0.14% [kernel] [k] osq_lock 0.12% [kernel] [k] spl_kmem_cache_free 0.12% [kernel] [k] __indirect_thunk_start 0.12% [kernel] [k] native_queued_spin_lock_slowpath 0.11% [kernel] [k] __init_waitqueue_head 0.11% [kernel] [k] arc_prune_async 0.11% [kernel] [k] __cv_init 0.09% [kernel] [k] __schedule -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814983 Title: zfs poor sustained read performance from ssd pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1814983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814141] Re: fail to run any snap after snapd refresh, reinstalling snapd from the archive is a temporary fix
"AFAIK, last time I looked at apparmor_parser, it was smart enough to ignore .dpkg-dist and similar files." You missed my point: yes, apparmor will ignore it and it will use the *old* one that the user left instead of the new one with any new rules. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814141 Title: fail to run any snap after snapd refresh, reinstalling snapd from the archive is a temporary fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814987] [NEW] No icon for ksystemlog
Public bug reported: As revealed by Mint Cinnamon's main menu, and the plank dock, `ksystemlog` has no icon under the gnome-wise theme (and variants of that theme?). When I use Mint's inbuilt theme, or the 'paper' theme, ksystemlog gets an icon (in plank and elsewhere). Here is '/usr/share/applications/org.kde.ksystemlog.desktop': == Start == [Desktop Entry] Type=Application Exec=ksystemlog -qwindowtitle %c Icon=utilities-log-viewer Terminal=false Categories=Qt;KDE;System;Monitor; X-DocPath=ksystemlog/index.html X-KDE-SubstituteUID=true Name=KSystemLog Name[ar]=سجلّات نظامك Name[ast]=KSystemLog Name[bg]=Системни дневници Name[bs]=KSystemLog Name[ca]=KSystemLog Name[ca@valencia]=KSystemLog Name[cs]=KSystemLog Name[da]=KSystemLog Name[de]=KSystemLog Name[el]=KSystemLog Name[en_GB]=KSystemLog Name[es]=KSystemLog Name[et]=KSystemLog Name[eu]=KSystemLog Name[fa]=KSystemLog Name[fi]=KSystemLog Name[fr]=KSystemLog Name[ga]=KSystemLog Name[gl]=KSystemLog Name[hne]=के-सिस्टम-लाग Name[hr]=KSystemLog Name[hu]=Rendszernapló-megjelenítő Name[ia]=KSystemLog Name[id]=KSystemLog Name[is]=KSystemLog Name[it]=KSystemLog Name[ja]=KSystemLog Name[kk]=KSystemLog Name[ko]=KSystemLog Name[lt]=KSystemLog Name[lv]=KSystemLog Name[ml]=കെസിസ്റ്റംലോഗ് Name[mr]=के-सिस्टीम-लॉग Name[nb]=KSystemLog Name[nds]=KSystemLog Name[nl]=KSystemLog Name[nn]=KSystemlogg Name[pa]=ਕੇ-ਸਿਸਟਮ-ਲਾਗ Name[pl]=KSystemLog Name[pt]=KSystemLog Name[pt_BR]=KSystemLog Name[ro]=KSystemLog Name[ru]=KSystemLog Name[sk]=KSystemLog Name[sl]=KSystemLog Name[sq]=KSystemLog Name[sr]=К‑системски-дневник Name[sr@ijekavian]=К‑системски-дневник Name[sr@ijekavianlatin]=K‑sistemski-dnevnik Name[sr@latin]=K‑sistemski-dnevnik Name[sv]=Ksystemlog Name[th]=ปูมบันทึกระบบ Name[tr]=KSystemLog Name[ug]=KSystemLog Name[uk]=KSystemLog Name[x-test]=xxKSystemLogxx Name[zh_CN]=KSystemLog Name[zh_TW]=KSystemLog Comment=System log viewer tool Comment[ar]=أداة لعرض سجلّات النّظام Comment[ast]=Ferramienta visora de rexistros del sistema Comment[bg]=Инструмент за преглеждане на системните дневници Comment[bs]=Alat za pregled sistemski zabilješki Comment[ca]=Eina de visualització dels registres del sistema Comment[ca@valencia]=Eina de visualització dels registres del sistema Comment[cs]=Nástroj na prohlížení záznamů systému Comment[da]=Fremviserværktøj til systemlog Comment[de]=Betrachter für Systemprotokolle Comment[el]=Εργαλείο εμφάνισης της καταγραφής του συστήματος Comment[en_GB]=System log viewer tool Comment[es]=Herramienta de visualización de registros del sistema Comment[et]=Süsteemilogi näitaja Comment[eu]=Sistema egunkariak erakusteko tresna Comment[fa]=ابزار مشاهدهگر وقایع ثبت شده سیستم Comment[fi]=Järjestelmälokien katselin Comment[fr]=Outil d'affichage des journaux du système Comment[ga]=Amharcán ar logchomhaid an chórais Comment[gl]=Visor dos rexistros do sistema Comment[he]=כלי לעיון ביומני מערכת Comment[hne]=तंत्र लाग प्रदर्सक औजार Comment[hr]=Alat za prikaz dnevnika sustava Comment[hu]=Rendszernapló-megjelenítő eszköz Comment[ia]=Instrumento pro vider registro de systema Comment[id]=Alat pembaca Catatan sistem Comment[is]=Tól til að skoða kerfisannála (system logs) Comment[it]=Strumento di visione dei registri di sistema Comment[ja]=システムログビューア Comment[kk]=Жүйелік журналын қарау құралы Comment[ko]=시스템 로그 뷰어 도구 Comment[lt]=Sistemos žurnalų žiūryklė Comment[lv]=Sistēmas žurnāla skatīšanas rīks Comment[ml]=സിസ്റ്റം ലോഗ് കാണാന്നുള്ള ടൂള് Comment[mr]=प्रणाली लॉग प्रदर्शक साधन Comment[nb]=Verktøy for å vise systemlogger Comment[nds]=Kieker för Systeem-Logböker Comment[nl]=Systeemlogs bekijken Comment[nn]=Verktøy for vising av systemloggar Comment[pa]=ਸਿਸਟਮ ਲਾਗ ਦਰਸ਼ਕ ਟੂਲ Comment[pl]=Narzędzie do przeglądania dziennika systemowego Comment[pt]=Ferramenta de visualização dos registos do sistema Comment[pt_BR]=Ferramenta de visualização de registros do sistema Comment[ro]=Unealtă de vizualizare a jurnalelor de sistem Comment[ru]=Программа просмотра системных журналов Comment[sk]=Nástroj na prehliadanie záznamov systému Comment[sl]=Orodje za pregledovanje sistemskih dnevnikov Comment[sq]=Mjeti shfaqës i hyrjeve në sistem Comment[sr]=Приказивач системских дневника Comment[sr@ijekavian]=Приказивач системских дневника Comment[sr@ijekavianlatin]=Prikazivač sistemskih dnevnika Comment[sr@latin]=Prikazivač sistemskih dnevnika Comment[sv]=Visningsverktyg för systemloggar Comment[th]=เครื่องมือแสดงปูมบันทึกของระบบ Comment[tr]=Sistem günlük kayıtlarını gösterme aracı Comment[ug]=سىستېما خاتىرىسىنى كۆرۈش قورالى Comment[uk]=Засіб перегляду системних журналів Comment[x-test]=xxSystem log viewer toolxx Comment[zh_CN]=系统日志查看工具 Comment[zh_TW]=系統紀錄檢視工具 GenericName=System Log Viewer GenericName[ar]=عارض سجلّات النّظام GenericName[ast]=Visor de rexistros del sistema GenericName[bg]=Преглед на системните дневници GenericName[bs]=Preglednik sistemskih bilješki GenericName[ca]=Visor dels registres del sistema GenericName[ca@valencia]=Visor dels registres del sistema GenericName[cs]=Prohlížeč záznamů
[Bug 1814986] Re: lxd/apparmor: Tweak default set of rules
This is a LXD commit, not a LXC one. LXC cannot be fixed in the same way as it has a single apparmor policy covering both privileged and unprivileged containers, until such time as the apparmor security issue is resolved, there's nothing we can do to fix this issue without causing a giant security hole in the process. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814986 Title: lxd/apparmor: Tweak default set of rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1814986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814905] Re: dash exits when receiving wall message
Hello Imre, thanks for the report. I can't reproduce this issue myself,
nor could I find anything in the source code that would suggest dash
would try to quit. In fact I'm not even sure that dash knows that it's
happened.
Here's the tail end of strace output (run on the same terminal as dash,
to force intermingling of syscall output and terminal output), showing
dash handling a write(1) without trouble, and checking for completed
jobs after I hit enter several times:
geteuid() = 1000
getegid() = 1000
rt_sigaction(SIGINT, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGINT, {sa_handler=0x55a82089e200, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
rt_sigaction(SIGQUIT, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGQUIT, {sa_handler=SIG_IGN, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
rt_sigaction(SIGTERM, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTERM, {sa_handler=SIG_IGN, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR)= 3
fcntl(3, F_DUPFD, 10) = 10
close(3)= 0
fcntl(10, F_SETFD, FD_CLOEXEC) = 0
ioctl(10, TIOCGPGRP, [23306]) = 0
getpgrp() = 23306
rt_sigaction(SIGTSTP, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTSTP, {sa_handler=SIG_IGN, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
rt_sigaction(SIGTTOU, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTTOU, {sa_handler=SIG_IGN, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
rt_sigaction(SIGTTIN, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTTIN, {sa_handler=SIG_DFL, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7fd3be19df20}, NULL, 8) = 0
setpgid(0, 23308) = 0
ioctl(10, TIOCSPGRP, [23308]) = 0
wait4(-1, 0x7ffcdf89717c, WNOHANG|WSTOPPED, NULL) = -1 ECHILD (No child
processes)
write(2, "$ ", 2$ ) = 2
read(0,
Message from sarnold@hunt on pts/13 at 17:41 ...
hello
EOF
"\n", 8192) = 1
wait4(-1, 0x7ffcdf89717c, WNOHANG|WSTOPPED, NULL) = -1 ECHILD (No child
processes)
write(2, "$ ", 2$ ) = 2
read(0,
"\n", 8192) = 1
wait4(-1, 0x7ffcdf89717c, WNOHANG|WSTOPPED, NULL) = -1 ECHILD (No child
processes)
write(2, "$ ", 2$ ) = 2
read(0, ^C0x55a820aa9a60, 8192) = ? ERESTARTSYS (To be restarted if
SA_RESTART is set)
--- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
rt_sigprocmask(SIG_SETMASK, [], ~[KILL STOP RTMIN RT_1], 8) = 0
write(2, "\n", 1
) = 1
wait4(-1, 0x7ffcdf89717c, WNOHANG|WSTOPPED, NULL) = -1 ECHILD (No child
processes)
write(2, "$ ", 2$ ) = 2
read(0, "", 8192) = 0
write(2, "\n", 1
) = 1
ioctl(10, TIOCSPGRP, [23306]) = 0
setpgid(0, 23306) = 0
close(10) = 0
exit_group(0) = ?
+++ exited with 0 +++
I tried both dash in a terminal (urxvt) and ssh -t sarnold@localhost /bin/dash
-- both behaved identically.
Could you try to reproduce this while you're attached to the shell with
gdb or perhaps perf trace?
Thanks
** Changed in: dash (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/1814905
Title:
dash exits when receiving wall message
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1814905/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814982] Re: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
I am unable to provide apport logs due to the nature of the problem (kernel hang on boot before console logging). ** 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/1814982 Title: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814986] [NEW] lxd/apparmor: Tweak default set of rules
Public bug reported: branches cosmic & disco the impact of current lxc aa rules in conjunction with systemd v240 is outlined here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622/comments/10 Whilst LXC committed the patch to its master https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f it has not arrived downstream and thus would be appreciated to be merged, both in cosmic and disco since impacting users of both branches, e.g. arch linux guest that already deploy systemd v240 without this patch particular ubuntu patch https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770 ** Affects: lxc (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/1814986 Title: lxd/apparmor: Tweak default set of rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1814986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814982] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1814982 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (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/1814982 Title: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
If anyone knows a way to pinpoint some process which sends some specific packets, I'd be glad to investigate further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814980] Re: timedatectl set-timezone UTC Fails
** Description changed: Sorry for the pre-mature post. First time using this interface. - I noticed this today; an automated AMI build process failed. The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu- eks/k8s_1.10/images/hvm-ssd/ubuntu- bionic-18.04-amd64-server-20190204.2). The automated build process uses a t2.micro, if that's helpful. - ``` ubuntu@ip-172-31-29-182:~$ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic ``` - Here's the bug: ``` ubuntu@ip-172-31-29-182:~$ timedatectl list-timezones UTC ubuntu@ip-172-31-29-182:~$ timedatectl set-timezone UTC Failed to set time zone: Invalid time zone 'UTC' ubuntu@ip-172-31-29-182:~$ timedatectl Local time: Thu 2019-02-07 00:10:43 UTC Universal time: Thu 2019-02-07 00:10:43 UTC RTC time: Thu 2019-02-07 00:10:44 Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: yes RTC in local TZ: no ``` + If there's anything else that you need, let me know!. - If there's anything else that you need, let me know!. + EDIT: + + + ``` + ubuntu@ip-172-31-26-66:~$ timedatectl --version + systemd 237 + +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid + ``` + + (hostname is different because this is a new instance, same AMI) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814980 Title: timedatectl set-timezone UTC Fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1814980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
I experience the same symptoms on Ubuntu 19.04 disco, but there is no cups* packages installed: # apt-cache policy cups*| grep Installed | grep -v none # The issue is definitely unrelated to CUPS. Some other process sends many strange IPv6/UDP packets to all IPv6 local nodes with 2 different types; the wireshark trace shows 2 types of "Discover scanner commands": 1. source port 8612 (canon-bjnp2) --> dest port 8610 (canon-mfnp) 2. source port 8612 (canon-bjnp2) --> dest port 8612 (canon-bjnp2) I have no canon device on the network nor on the server and no USB device connected on the server. There is no canon related package/kernel module installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
@P.D. Thanks for the feedback. I have the sixth kernel for you based on commit: 1ab407cbd9c3 (tag: sixth-bisect) drm/i915: Mark pin flags as u64 You can download the test kernel from: https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-1ab407c-XRVe/ Please let me know if this kernel shows the same problem or not. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814983] [NEW] zfs poor sustained read performance from ssd pool
Public bug reported:
Hello,
I'm seeing substantially slower read performance from an ssd pool than I
expected.
I have two pools on this computer; one ('fst') is four sata ssds, the
other ('srv') is nine spinning metal drives.
With a long-running ripgrep process on the fst pool, performance started
out really good and grew to astonishingly good (iirc ~30kiops, as
measured by zpool iostat -v 1). However after a few hours the
performance has dropped to 30-40 iops. top reports an arc_reclaim and
many arc_prune processes to be consuming most of the CPU time.
I've included a screenshot of top, some output from zpool iostat -v 1,
and arc_summary, with "===" to indicate the start of the next command's
output:
===
top (memory in gigabytes):
top - 16:27:53 up 70 days, 16:03, 3 users, load average: 35.67, 35.81, 35.58
Tasks: 809 total, 19 running, 612 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 58.1 sy, 0.0 ni, 39.2 id, 2.6 wa, 0.0 hi, 0.0 si, 0.0 st
GiB Mem : 125.805 total,0.620 free, 96.942 used, 28.243 buff/cache
GiB Swap:5.694 total,5.688 free,0.006 used. 27.840 avail Mem
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
1523 root 20 00.0m 0.0m 0.0m R 100.0 0.0 290:52.26 arc_reclaim
4484 root 20 00.0m 0.0m 0.0m R 56.2 0.0 1:18.79 arc_prune
6225 root 20 00.0m 0.0m 0.0m R 56.2 0.0 1:11.92 arc_prune
7601 root 20 00.0m 0.0m 0.0m S 56.2 0.0 2:50.25 arc_prune
30891 root 20 00.0m 0.0m 0.0m S 56.2 0.0 1:33.08 arc_prune
3057 root 20 00.0m 0.0m 0.0m S 55.9 0.0 9:00.95 arc_prune
3259 root 20 00.0m 0.0m 0.0m R 55.9 0.0 3:16.84 arc_prune
24008 root 20 00.0m 0.0m 0.0m S 55.9 0.0 1:55.71 arc_prune
1285 root 20 00.0m 0.0m 0.0m R 55.6 0.0 3:20.52 arc_prune
5345 root 20 00.0m 0.0m 0.0m R 55.6 0.0 1:15.99 arc_prune
30121 root 20 00.0m 0.0m 0.0m S 55.6 0.0 1:35.50 arc_prune
31192 root 20 00.0m 0.0m 0.0m S 55.6 0.0 6:17.16 arc_prune
32287 root 20 00.0m 0.0m 0.0m S 55.6 0.0 1:28.02 arc_prune
32625 root 20 00.0m 0.0m 0.0m R 55.6 0.0 1:27.34 arc_prune
22572 root 20 00.0m 0.0m 0.0m S 55.3 0.0 10:02.92 arc_prune
31989 root 20 00.0m 0.0m 0.0m R 55.3 0.0 1:28.03 arc_prune
3353 root 20 00.0m 0.0m 0.0m R 54.9 0.0 8:58.81 arc_prune
10252 root 20 00.0m 0.0m 0.0m R 54.9 0.0 2:36.37 arc_prune
1522 root 20 00.0m 0.0m 0.0m S 53.9 0.0 158:42.45 arc_prune
3694 root 20 00.0m 0.0m 0.0m R 53.9 0.0 1:20.79 arc_prune
13394 root 20 00.0m 0.0m 0.0m R 53.9 0.0 10:35.78 arc_prune
24592 root 20 00.0m 0.0m 0.0m R 53.9 0.0 1:54.19 arc_prune
25859 root 20 00.0m 0.0m 0.0m S 53.9 0.0 1:51.71 arc_prune
8194 root 20 00.0m 0.0m 0.0m S 53.6 0.0 0:54.51 arc_prune
18472 root 20 00.0m 0.0m 0.0m R 53.6 0.0 2:08.73 arc_prune
29525 root 20 00.0m 0.0m 0.0m R 53.6 0.0 1:35.81 arc_prune
32291 root 20 00.0m 0.0m 0.0m S 53.6 0.0 1:28.00 arc_prune
3156 root 20 00.0m 0.0m 0.0m R 53.3 0.0 3:17.68 arc_prune
6224 root 20 00.0m 0.0m 0.0m S 53.3 0.0 1:11.80 arc_prune
9788 root 20 00.0m 0.0m 0.0m S 53.3 0.0 0:46.00 arc_prune
10341 root 20 00.0m 0.0m 0.0m R 53.3 0.0 2:36.23 arc_prune
11881 root 20 00.0m 0.0m 0.0m S 53.0 0.0 2:31.57 arc_prune
[Bug 1814982] [NEW] efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
Public bug reported: [Impact] The Ubuntu kernel is not currently bootable on various arm64 laptops (HP Envy x2, Asus NovaGo, Lenovo Miix 630, Lenovo Yoga C630, Samsung ...) because of EFI memory permissions/restrictions. The reason is explained in the commit supplied below. [Test Case] Install and boot Ubuntu on one of the above arm64 laptops. [Fix] Committed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e46c2a956215482418d7b315749fb1b6c6bc224 [Regression Risk] This commit adds support for an optional kernel command line parameter so there is minimal to no risk. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: grub2 (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/1814982 Title: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814141] Re: fail to run any snap after snapd refresh, reinstalling snapd from the archive is a temporary fix
I don't know, whether this matters: I still get some apparmor="DENIED"-messages as shown in the attachment. Snapd and snap.nextcloud seem to be up and running. Thanks again! ** Attachment added: "journalctl__grep_DENIED__tail.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814141/+attachment/5236611/+files/journalctl__grep_DENIED__tail.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814141 Title: fail to run any snap after snapd refresh, reinstalling snapd from the archive is a temporary fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814980] [NEW] timedatectl set-timezone UTC Fails
Public bug reported: Sorry for the pre-mature post. First time using this interface. I noticed this today; an automated AMI build process failed. The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu- eks/k8s_1.10/images/hvm-ssd/ubuntu- bionic-18.04-amd64-server-20190204.2). The automated build process uses a t2.micro, if that's helpful. ``` ubuntu@ip-172-31-29-182:~$ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic ``` Here's the bug: ``` ubuntu@ip-172-31-29-182:~$ timedatectl list-timezones UTC ubuntu@ip-172-31-29-182:~$ timedatectl set-timezone UTC Failed to set time zone: Invalid time zone 'UTC' ubuntu@ip-172-31-29-182:~$ timedatectl Local time: Thu 2019-02-07 00:10:43 UTC Universal time: Thu 2019-02-07 00:10:43 UTC RTC time: Thu 2019-02-07 00:10:44 Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: yes RTC in local TZ: no ``` If there's anything else that you need, let me know!. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: + Sorry for the pre-mature post. First time using this interface. + + + I noticed this today; an automated AMI build process failed. + + The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu- + eks/k8s_1.10/images/hvm-ssd/ubuntu- + bionic-18.04-amd64-server-20190204.2). + + The automated build process uses a t2.micro, if that's helpful. + + + ``` + ubuntu@ip-172-31-29-182:~$ lsb_release --all + No LSB modules are available. + Distributor ID: Ubuntu + Description: Ubuntu 18.04.1 LTS + Release: 18.04 + Codename: bionic + ``` + + + Here's the bug: + ``` ubuntu@ip-172-31-29-182:~$ timedatectl list-timezones UTC ubuntu@ip-172-31-29-182:~$ timedatectl set-timezone UTC Failed to set time zone: Invalid time zone 'UTC' ubuntu@ip-172-31-29-182:~$ timedatectl - Local time: Thu 2019-02-07 00:10:43 UTC - Universal time: Thu 2019-02-07 00:10:43 UTC - RTC time: Thu 2019-02-07 00:10:44 -Time zone: n/a (UTC, +) -System clock synchronized: yes + Local time: Thu 2019-02-07 00:10:43 UTC + Universal time: Thu 2019-02-07 00:10:43 UTC + RTC time: Thu 2019-02-07 00:10:44 + Time zone: n/a (UTC, +) + System clock synchronized: yes systemd-timesyncd.service active: yes - RTC in local TZ: no + RTC in local TZ: no + ``` + + + If there's anything else that you need, let me know!. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814980 Title: timedatectl set-timezone UTC Fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1814980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652822] Re: grub efi doesn't install fs module needed to access root
Correction to that date I write above: 2019 02 06 not 2019 02 26 blargh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652822 Title: grub efi doesn't install fs module needed to access root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1652822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652822] Re: grub efi doesn't install fs module needed to access root
... Ah I see, it does look like possibly the debian upstream might have fixed it, and merely the ubuntu package has not yet got it. Which is what this bug declares at the top, so no discrepency there after all. They mention signed images, where in my own case I have uefi boot security disabled and can boot unsigned things, so I don't know if that fix will still fix me or not, but seems likely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652822 Title: grub efi doesn't install fs module needed to access root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1652822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652822] Re: grub efi doesn't install fs module needed to access root
On 19.04 I still get my grub.cfg broken by normal updates. Not by kernel updates, and not by running update-grub. But there is some package that whenever that package is updated, part of the update process generates a new grub.cfg, and it's a broken one because it makes a bad assumption somewhere. I eneded up writing myself a little "check_grub_efi_xfs" script that I run any time I think I saw anything about grub fly by when I run "apt upgrade", or, any time grub gets screwed up I run it after I get myself back in. It's only about 3 lines of code that actually matters, but writes a lot of stuff to the screen just so you don't have ANY worries about it what it did and if your boot files are currently ok before you shut down. Ideally this should run just before shutdown on every single shutdown. Then you'd never have to worry about it. The only way you'd miss an update again is if you had an ungraceful shutdown after an apt upgrade that included a grub packege update. But despite being a unix and linux admin for over 20 years, I have so far utterly failed to get systemd to do such a simple task. If someone can show me exactly how to write a freaking unit file that does that, I'd be pretty grateful. Just to refresh, the issue here is, it's possible to install ubuntu with xfs root fs to a machine that already has a factory Win10 install and boot files in a factory EFI partition, without having to make any special /boot partition. All you really need is to place a copy of xfs.mod onto the EFI partition, which is a FAT filesystem that grub already reads files from at boot. And edit the initial grub.cfg that's in the EFI filesystem so that it loads xfs.mod from there too. Then everything else is fine. The rest of /boot can be in "/", and "/" can be xfs. This allowed me to degfrag and resize the factory Win10 without wiping and reinstalling, install linux in the freed space, with xfs root fs, and no other partition or filesystem changes needed. I can boot back and forth between the original Win10 install or linux with no problem. It didn't break Win10 booting. It's a perfectly valid and "legal" arrangement, and anything that automatically writes grub config files should have to allow for this possibility without breaking it. Screen capture from a run of this fixup script, just after today's apt upgrade which broke my grub.cfg once again. This is today 2019 02 26, so I don't know where the supposed fix is. It's definitely not yet in 19.04 or in grub-* 2.02+dfsg1-5ubuntu11 So this run shows the actions when it detects that it actually has something to do. Most times, it will detect that it doesn't have to do anything, and it will take no action those times. This, and the script itself (attached) should serve as detailed documentation of the admittedly uncommon configuration, and exactly how it gets broken, and exactly how it gets un-broken. ---snip--- root@negre:~# check_grub_efi_xfs Checking for broken grub + efi + xfs config... EFI System Partition ESP_DIR=/boot/efi/EFI/ubuntu total 3488 -rwx-- 1 root root 108 Aug 14 14:47 BOOTX64.CSV -rwx-- 1 root root 141 Jan 25 11:13 emergency.cfg drwx-- 2 root root4096 Dec 14 2017 fw -rwx-- 1 root root 73565 Jan 17 23:08 fwupx64.efi -rwx-- 1 root root 117 Feb 6 12:57 grub.cfg -rwx-- 1 root root 1105784 Feb 6 12:57 grubx64.efi -rwx-- 1 root root 1153336 Aug 14 14:47 mmx64.efi -rwx-- 1 root root 141 Jan 25 11:13 old.cfg -rwx-- 1 root root 1196736 Aug 14 14:47 shimx64.efi -rwx-- 1 root root 92 Mar 5 2018 static.cfg -rwx-- 1 root root 10416 Jan 25 11:13 xfs.mod Grub-* package's xfs.mod XFS_MOD=/boot/grub/x86_64-efi/xfs.mod -rw-r--r-- 1 root root 10416 Feb 6 12:57 /boot/grub/x86_64-efi/xfs.mod Checking xfs.mod ... /boot/efi/EFI/ubuntu/xfs.mod is present -rw-r--r-- 1 root root 10416 Feb 6 12:57 /boot/grub/x86_64-efi/xfs.mod -rwx-- 1 root root 10416 Jan 25 11:13 /boot/efi/EFI/ubuntu/xfs.mod /boot/efi/EFI/ubuntu/xfs.mod is older than /boot/grub/x86_64-efi/xfs.mod Updating /boot/efi/EFI/ubuntu/xfs.mod '/boot/grub/x86_64-efi/xfs.mod' -> '/boot/efi/EFI/ubuntu/xfs.mod' Checking /boot/efi/EFI/ubuntu/grub.cfg ... /boot/efi/EFI/ubuntu/grub.cfg does not contain insmod xfs (A grub-* package update has generated a new /boot/efi/EFI/ubuntu/grub.cfg incorrectly) emergency.cfg exists Copying current emergency.cfg to old.cfg '/boot/efi/EFI/ubuntu/emergency.cfg' -> '/boot/efi/EFI/ubuntu/old.cfg' Generating a new emergency.cfg by prepending insmod xfs to the new grub.cfg Summary: /boot/efi/EFI/ubuntu/grub.cfg before apt upgrade: insmod $cmdpath/xfs.mod search.fs_uuid 7bd784f6-f235-4b24-bb7b-eb607b1f0515 root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg /boot/efi/EFI/ubuntu/grub.cfg after apt upgrade: search.fs_uuid 7bd784f6-f235-4b24-bb7b-eb607b1f0515 root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg /boot/efi/EFI/ubuntu/emergency.cfg we just generated: insmod
[Bug 1814141] Re: fail to run any snap after snapd refresh, reinstalling snapd from the archive is a temporary fix
Thanks a lot for the hint! The following fixed the problem here: $ sudo mv /etc/apparmor.d/usr.lib.snapd.snap-confine $HOME/tmp $ sudo service apparmor restart -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814141 Title: fail to run any snap after snapd refresh, reinstalling snapd from the archive is a temporary fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812317] Re: grub is prevented from booting on UEFI Arm64 Laptops - requires 4k aligned headers
** Changed in: grub2 (Debian) Status: Unknown => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812317 Title: grub is prevented from booting on UEFI Arm64 Laptops - requires 4k aligned headers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1812317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236596/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236601/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236606/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236600/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236599/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236607/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236604/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236598/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236603/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236609/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1814830] Re: recent linux versions 44 and 45 do not start up
I observe that menu.lst is used here for starting Linux. And I assume that when the 'Software Updater' sends me this, it is needed and is not obsolete. My policy is to use the most recent kernel update, provided that I can get it working. 'sudo update-grub': I have done this and it writes a new grub.cfg ; however, menu.lst is not modified. Finally: I have (manually is the word?) modified menu.lst and added an 'initrd' line in the menu for the 45 kernel update, and now Linux does start with this latest kernel update. Fine. But the question is still, how to get the Linux system or the Software Updater to create a correct and sound menu.lst automatically? Thanks so far. On 06-02-19 12:34, Stefan Bader wrote: > I missed menu.lst mentioned before. This is a grub1 file and even for a 32bit > (i386) installation I would have thought everything already migrated to use > grub2. The only thing which I thought were still using menu.lst were paravirt > Xen guests on the Amazon cloud. > There was some pain with grub1 and menu.lst related to configuration > questions (do you want to keep the current version or install a new one). > Answering keep there would any future update and basically keep people from > using any updated kernel. > > But to the problem, if changing menu.lst helped to switch back to the > previous kernel, then you are still using grub1. So the lines in there > for 43 and the 45 kernel should look the same (except version numbers). > Does manually running "sudo update-grub" fix this? I don't think there > is a update-grub-legacy-ec2 around (that would probably only be there > when using grub2) but if it is there, that normally can be used to force > menu.lst to be comparable to what grub.cfg contains. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814830 Title: recent linux versions 44 and 45 do not start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236608/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236602/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236605/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236597/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814974] Re: Kernel 4.18.0-14
apport information ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: apport-collected tara ** Description changed: - Have installed this twice through Update Manager. It does not function - on my Sony Vaio laptop running Mint 19. I have to select previous - kernel, then computer is fine. + Have installed this twice through Update Manager. It does not function on my Sony Vaio laptop running Mint 19. I have to select previous kernel, then computer is fine. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: steve 1230 F pulseaudio + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19 + HibernationDevice: RESUME=UUID=260db35a-0a3f-4f50-ad5c-a4ba614b4ba1 + InstallationDate: Installed on 2018-07-10 (211 days ago) + InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 + MachineType: Sony Corporation VPCEB4E1E + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=52fba28c-b955-4f8f-a81d-e8e164e76db8 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 + RelatedPackageVersions: + linux-restricted-modules-4.18.0-13-generic N/A + linux-backports-modules-4.18.0-13-generic N/A + linux-firmware 1.173.3 + Tags: tara + Uname: Linux 4.18.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/06/2010 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: R1140Y8 + dmi.board.asset.tag: N/A + dmi.board.name: VAIO + dmi.board.vendor: Sony Corporation + dmi.board.version: N/A + dmi.chassis.asset.tag: N/A + dmi.chassis.type: 10 + dmi.chassis.vendor: Sony Corporation + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:svnSonyCorporation:pnVPCEB4E1E:pvrC607Z7EW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: + dmi.product.family: VAIO + dmi.product.name: VPCEB4E1E + dmi.product.sku: N/A + dmi.product.version: C607Z7EW + dmi.sys.vendor: Sony Corporation ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1814974/+attachment/5236595/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814974 Title: Kernel 4.18.0-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814141] Re: fail to run any snap after snapd refresh, reinstalling snapd from the archive is a temporary fix
** Attachment added: "usr.lib.snapd.snap-confine" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814141/+attachment/5236594/+files/usr.lib.snapd.snap-confine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814141 Title: fail to run any snap after snapd refresh, reinstalling snapd from the archive is a temporary fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
@kmously The fifth kernel boots up fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
@Jan Schnackenberg: Thanks for that feedback and helpful and analysis. The Spectre-related change looked suspicious at first. However, if that was indeed the cause of your issue, then it's almost certainly a different issue than the one described in this bug report and experienced by @P.D., since at this point in the bisection, we've eliminated Spectre-related changes from the pool of possible culprits. In fact, at this point it's highly likely that the problem is a regression in the Intel i915 driver. This matches with the stacktraces in all the bug reports so far, and also coincides with a few i915 changes on which we're narrowing in in the bisection process. @Jan Schnackenberg, you are encouraged to try the test kernels that I've linked above and report your results. Your problem is almost certainly the same problem described in this bug (and if it's not, we can continue that investigation as part of another bug). As for the required .deb files, you can forgo the -headers files, so the following should be sufficient: linux-image-unsigned-4.18.0-14-generic linux-modules-4.18.0-14-generic linux-modules-extra-4.18.0-14-generic Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814141] Re: fail to run any snap after snapd refresh, reinstalling snapd from the archive is a temporary fix
According to apt-file usr.lib.snapd.snap-confine.real seems to be from snapd: $ apt-file find usr.lib.snapd.snap-confine snapd: /etc/apparmor.d/usr.lib.snapd.snap-confine.real ** Attachment added: "usr.lib.snapd.snap-confine.real" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814141/+attachment/5236593/+files/usr.lib.snapd.snap-confine.real -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814141 Title: fail to run any snap after snapd refresh, reinstalling snapd from the archive is a temporary fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814976] [NEW] eol-server dates are empty for current releases
Public bug reported: The ubuntu.csv file from distro-info-data contains a column for eol- server which one can then us ubuntu-distro-info to display the days until that milestone is reached. However, that column is empty for many Ubuntu releases (because there isn't a distinction between EoL for desktop and servers anymore) which leads to the following confusing situation. $ ubuntu-distro-info --supported -r --days=eol-server 14.04 LTS (unknown) 16.04 LTS (unknown) 18.04 LTS (unknown) 18.10 (unknown) 19.04 (unknown) I'd suggest modifying ubuntu.csv so that the eol-server column contains the same date as the eol column for all releases. ** Affects: distro-info-data (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco trusty xenial ** Tags added: bionic cosmic disco trusty xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814976 Title: eol-server dates are empty for current releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1814976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811098] Re: [SRU] ceilometer writing snmp credentials to log file
A CVE can be requested by anyone for any defect. The OpenStack VMT doesn't generally request CVEs for projects it doesn't oversee, but we have a brief overview of what we'd generally recommend putting in MITRE's CVE Request form documented at https://security.openstack.org /vmt-process.html#send-cve-request if you're interested in following a similar process. Note that for an already-public report like this one, there are fewer bits to worry about (the process documentation attempts to call out the difference between what you'd do for still private embargoed reports vs already public reports). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811098 Title: [SRU] ceilometer writing snmp credentials to log file To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1811098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813657] Re: 4.18.0-14 doesn't boot past grub
@P.D. Thanks for the feedback. I have the fifth kernel for you based on commit: ce68bab41c06 drm/i915: Fix ilk+ watermarks when disabling pipes You can download the test kernel from: https://kernel.ubuntu.com/~kmously/1813657/kernel-kmously-ce68bab-GzyB/ Please let me know if this kernel shows the same problem or not. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813657 Title: 4.18.0-14 doesn't boot past grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
