[Bug 1881367] Re: Ubuntu 20.04 boot hangs when laptop unplugged
Do you still have this issue when system is fully upgraded? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881367 Title: Ubuntu 20.04 boot hangs when laptop unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
wow, thank you very much now super key it works correctly ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
Сan you please tell me what could be the reason? ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
wow, thank you very much now super key it works correctly just discovered on logout, my display is still black, and if i given my password and press enter login works -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893579] Re: Ctrl + Alt + T and Fn keys not working
Could it be a problem of this version? LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 Codename: groovy I installed first the Ubuntu 20.04, which was charminly working... could the 'gorilla groovy' be a mess? I realized that some additional shortcuts, besides the informed ones, are no longer working. And maybe even worst, not only shortcuts: the brightness adjusting bar, that one in the superior right corner is useless. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894033] Re: [RM, blacklist] debian-cloud-images: Debian-specific package, new version uninstallable
Removing packages from groovy: debian-cloud-images 0.0.1 in groovy debian-cloud-images 0.0.1 in groovy amd64 debian-cloud-images 0.0.1 in groovy arm64 debian-cloud-images 0.0.1 in groovy armhf debian-cloud-images 0.0.1 in groovy i386 debian-cloud-images 0.0.1 in groovy ppc64el debian-cloud-images 0.0.1 in groovy riscv64 debian-cloud-images 0.0.1 in groovy s390x Comment: Debian-specific, not useful in Ubuntu, new version uninstallable; LP: #1894033 1 package successfully removed. Removing packages from groovy-proposed: debian-cloud-images 0.0.3 in groovy debian-cloud-images 0.0.3 in groovy amd64 debian-cloud-images 0.0.3 in groovy arm64 debian-cloud-images 0.0.3 in groovy armhf debian-cloud-images 0.0.3 in groovy i386 debian-cloud-images 0.0.3 in groovy ppc64el debian-cloud-images 0.0.3 in groovy riscv64 debian-cloud-images 0.0.3 in groovy s390x debian-cloud-images-packages 0.0.3 in groovy amd64 debian-cloud-images-packages 0.0.3 in groovy arm64 debian-cloud-images-packages 0.0.3 in groovy ppc64el Comment: Debian-specific, not useful in Ubuntu, new version uninstallable; LP: #1894033 1 package successfully removed. and blacklisted. ** Changed in: debian-cloud-images (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894033 Title: [RM,blacklist] debian-cloud-images: Debian-specific package, new version uninstallable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cloud-images/+bug/1894033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894033] [NEW] [RM, blacklist] debian-cloud-images: Debian-specific package, new version uninstallable
Public bug reported: The debian-cloud-images package is a Debian-specific package used for building cloud images. The new version of this package in -proposed builds a binary package which depends on Debian-specific kernel packages that do not exist in Ubuntu. There is no value in introducing a delta to make this package installable on Ubuntu, because it is not relevant to Ubuntu cloud images. Let's remove it and blacklist it. ** Affects: debian-cloud-images (Ubuntu) Importance: Undecided Status: Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894033 Title: [RM,blacklist] debian-cloud-images: Debian-specific package, new version uninstallable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cloud-images/+bug/1894033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894031] [NEW] Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen
Public bug reported: The Ubuntu 20.10 version of g-c-c lacks the dropdown controls for changing screen resolution or selecting the primary monitor. Where there is normally a dropdown, there is just a label showing the current screen resolution or primary monitor. In some cases the dropdown is there, eg it might be there for the laptop monitor but not the external monitor(s). Changing the resolution of a monitor using xrandr sometimes makes the dropdown appear in g-c-c. I have attached a screenshot showing the issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu2 Uname: Linux 5.9.0-050900rc3-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 12:55:12 2020 InstallationDate: Installed on 2019-07-01 (429 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to groovy on 2020-09-01 (1 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages ** Attachment added: "g-c-c window missing dropdowns for primary display and resolution" https://bugs.launchpad.net/bugs/1894031/+attachment/5407264/+files/g-c-c%20missing%20dropdowns.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894031 Title: Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
Thanks. Next please disable your local extensions by moving or deleting: /home/adilet/.local/share/gnome-shell/extensions Then log out and in again. Does the problem still happen? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893579] Re: Ctrl + Alt + T and Fn keys not working
PrtScr and Alt-PrtScr are also not working for me. (Alt-F2 does work, though.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334577] Re: cpufreq : abnormal cpu frequences range used
Looks like I was mistaken about the frequency range of my CPU. I double checked it at: https://www.notebookcheck.net/HP-Spe289806.0.html and found that it's CPU is rated between 3100 and 4100 MHz. So the frequencies in /proc/cpuinfo from the recovery mode are correct and only change to the wrong values in the 800MHz range after a normal reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/334577 Title: cpufreq : abnormal cpu frequences range used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufrequtils/+bug/334577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
** Attachment added: "settings.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+attachment/5407263/+files/settings.txt ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+attachment/5407256/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+attachment/5407262/+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/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578001] Re: unmatched entries for isc-dhcp-server
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390212 ** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390213 ** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390214 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578001 Title: unmatched entries for isc-dhcp-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1578001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583705] Re: [SRU] unmatched entries for postfix
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390212 ** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390213 ** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390214 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583705 Title: [SRU] unmatched entries for postfix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577948] Re: unmatched entries for apparmor STATUS messages
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390212 ** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390213 ** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390214 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577948 Title: unmatched entries for apparmor STATUS messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1577948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
Thanks i followed instructions and get this result ubuntu-bug /var/crash/_usr_libexec_tracker-miner-fs.1000.crash ERROR: Cannot update /var/crash/_usr_libexec_tracker-miner-fs.1000.crash: [Errno 13] Permission denied: '/var/crash/_usr_libexec_tracker-miner-fs.1000.crash' https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4 now i will attach journalctl -b-1 > prevboot.txt lspci -kv > 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/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890749] Re: Missing perl 'Sys' module in system config summary on focal
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390212 ** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390213 ** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390214 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890749 Title: Missing perl 'Sys' module in system config summary on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892269] Re: Unmatched entry for exim with selfsigned certificate
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390212 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892269 Title: Unmatched entry for exim with selfsigned certificate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1892269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890751] Re: unmatched entry for securetty on focal
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390212 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890751 Title: unmatched entry for securetty on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890752] Re: unmatched entry for gnome-keyring-daemon on focal
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/logwatch/+git/logwatch/+merge/390212 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890752 Title: unmatched entry for gnome-keyring-daemon on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894025] Re: sudo do-release-upgrade doesn't work
*** This bug is a duplicate of bug 1611737 *** https://bugs.launchpad.net/bugs/1611737 ** Tags added: xenial2bionic ** Tags added: third-party-packages ** This bug has been marked a duplicate of bug 1611737 Can't upgrade from a release if ros packages are installed from ROS servers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894025 Title: sudo do-release-upgrade doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1894025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819924 Title: System hangs when hot-plugging dual monitor dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x
** Changed in: ubuntu-z-systems Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886814 Title: posix_spawn usage in gnu make causes failures on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885939] Re: Required dependencies not installed along with juce-tools
[Expired for juce (Ubuntu) because there has been no activity for 60 days.] ** Changed in: juce (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/1885939 Title: Required dependencies not installed along with juce-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juce/+bug/1885939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
** Attachment removed: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+attachment/5407254/+files/lspci.txt ** Attachment removed: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+attachment/5407253/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+attachment/5407254/+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/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+attachment/5407253/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] Re: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x
Thank you for your response. I apologize for not being able to give any detailed explication for the nature of my problem. The command was entered. However, the problem was fixed. I believe its due to the Nvidia proprietary 440 driver. Initially when I built the system, I used the drivers that were supplied by nvidia and they working fine and no problems while I was running my parallel programs. However, on monday there was an update for the drivers, and after that anytime I try to implement mpirun or hwloc-ls When I removed the nvidia propitiatory driver and used the open source ones and the problem was gone and both mpirun and hwloc-ls were running with no problems. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407251/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407247/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407249/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407248/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407245/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407250/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407252/+files/WifiSyslog.txt ** 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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407242/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407240/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407243/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407246/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] Re: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x
apport information ** Tags added: apport-collected wayland-session ** Description changed: The system will suffer a complete crash when the following commands are used: mpirun hwloc-ls - This occurs immediately after the execution of any of these two - commands. This started occurring only yesterday as I made a softwere - update after the weekend. Before, everything was fine. + This occurs immediately after the execution of any of these two commands. This started occurring only yesterday as I made a softwere update after the weekend. Before, everything was fine. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: salman 2116 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-08-10 (23 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + IwConfig: + enp67s0 no wireless extensions. + + lono wireless extensions. + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcFB: 0 nouveaudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=022dd10e-c967-49c2-8206-bcd0363bf6d0 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-45-generic N/A + linux-backports-modules-5.4.0-45-generic N/A + linux-firmware1.187.3 + RfKill: + + Tags: wayland-session focal + Uname: Linux 5.4.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/05/2020 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1101 + dmi.board.asset.tag: Default string + dmi.board.name: PRIME TRX40-PRO + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMETRX40-PRO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product Name + dmi.product.sku: SKU + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407237/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894028] [NEW] installer crashed after all information provided
Public bug reported: Installing on a wiped Asus K501UW laptop. I've successfully added Ubuntu MATE 20.04 to the same model with Windows still installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CasperVersion: 1.445 Date: Wed Sep 2 20:11:32 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash --- LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894028 Title: installer crashed after all information provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1894028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407244/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894027] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894027 Title: touchpad is not detected by kernals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407238/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407241/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893874] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1893874/+attachment/5407239/+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/1893874 Title: System Complete Crash Ubuntu 20.04 for parallel procedures AMD threadripper 3960x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894027] [NEW] touchpad is not detected by kernals
Public bug reported: I am using ubuntu from last year but in between after update my touchpad start giving issue, it stop working in between and not its completely undetected. Maybe i dont know the issue maybe kernals are not able to detect the touchpad. Please help ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-112-generic 4.15.0-112.113 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sachinsoni 1988 F pulseaudio /dev/snd/controlC0: sachinsoni 1988 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 09:15:46 2020 InstallationDate: Installed on 2020-03-21 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Aspire ES1-522 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=deac3d32-0fd8-4e85-8b7e-36ad67ec04cc ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07.IN01 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BELLEMERE_BE dmi.board.vendor: Acer dmi.board.version: V1.07.IN01 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07.IN01:bd04/28/2016:svnAcer:pnAspireES1-522:pvrV1.07.IN01:rvnAcer:rnBELLEMERE_BE:rvrV1.07.IN01:cvnAcer:ct9:cvrChassisVersion: dmi.product.family: CZL dmi.product.name: Aspire ES1-522 dmi.product.version: V1.07.IN01 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic ** Attachment added: "kernal is not able to detect my touchpad" https://bugs.launchpad.net/bugs/1894027/+attachment/5407214/+files/devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894027 Title: touchpad is not detected by kernals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466150] Re: grub-install breaks when ESP is on raid
Adding --no-nvram to grub-install grub-install --efi-directory=$mntpoint --target=x86_64-efi --no-nvram fixes this, the --no-nvram bypasses updating efi vars with efibootmgr but this entries don't need to be modified after install and on every grub pkg update. Modifying this line in /usr/lib/grub/grub-multi-install will allow the grub pkg update to complete succesfully... The error seems to be caused by the efibootmgr command using mduuid of raid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466150 Title: grub-install breaks when ESP is on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1466150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894025] [NEW] sudo do-release-upgrade doesn't work
Public bug reported: It says again & again Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Even though I removed all broken package. I don't know what to do now ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.30 ProcVersionSignature: Ubuntu 4.15.0-115.116~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Sep 3 12:07:09 2020 InstallationDate: Installed on 2019-05-08 (483 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2020-09-03 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894025 Title: sudo do-release-upgrade doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1894025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765484] Re: grub-install should handle /boot/efi on RAID1
*** This bug is a duplicate of bug 1466150 *** https://bugs.launchpad.net/bugs/1466150 Adding --no-nvram to grub-install grub-install --efi-directory=$mntpoint --target=x86_64-efi --no-nvram fixes this, the --no-nvram bypasses updating efi vars with efibootmgr but this entries don't need to be modified after install and on every grub pkg update. Modifying this line in /usr/lib/grub/grub-multi-install will allow the grub pkg update to complete succesfully... The error seems to be caused by the efibootmgr command using mduuid of raid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765484 Title: grub-install should handle /boot/efi on RAID1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1765484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886626] Re: after login to gnome with snd_hda_intel 0000:00:1f.3: No response from codec
** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886626 Title: after login to gnome with snd_hda_intel :00:1f.3: No response from codec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1886626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893969] Re: Screen corruption and delayed update using onboard Intel video
I can't see a problem in that screenshot or the logs. Maybe consider attaching a video instead? Also please tell us if the problem happens: * Without your custom xrandr commands * In a Wayland session (select 'Ubuntu on Wayland') from the login screen after selecting your username. ** Tags added: xrandr-scaling ** Tags added: multimonitor ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893969 Title: Screen corruption and delayed update using onboard Intel video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1893969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / X-KVM / B-KVM
** Changed in: ubuntu-kernel-tests Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / X-KVM / B-KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891421] Re: kci_test_encap_fou() in rtnetlink.sh from kselftests/net failed with "FAIL: can't add fou port 7777, skipping test"
** Tags added: sru-20200831 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891421 Title: kci_test_encap_fou() in rtnetlink.sh from kselftests/net failed with "FAIL: can't add fou port , skipping test" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1891421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893952] Re: very long boot/log in with log in window upper left corner?
I can't find a simple answer for the slowness or any evidence of it in the log. However I can see this unsupported package installed, which will affect practically everything: libc6 2.31-2ubuntu1 [origin: unknown] Please revert that package to a supported version: http://launchpadlibrarian.net/495370423/libc6_2.31-0ubuntu11_amd64.deb Please also reproduce the very long boot again and then run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1893952 Title: very long boot/log in with log in window upper left corner? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1893952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893452] Re: i386 autopkgtest fails in cross-testing
** Changed in: double-conversion (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893452 Title: i386 autopkgtest fails in cross-testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/double-conversion/+bug/1893452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893846] Re: Sound doesn't switch to headphones automatically when plugged in
Could you please test this kernel: https://people.canonical.com/~hwang4/testdetect/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893846 Title: Sound doesn't switch to headphones automatically when plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
I was doing a cleanup of my $HOME directory, and sadly I found this "snap" dir, this made me follow through and find this open issue... open for MORE than FOUR years already... is this fixable? Because if it's fixable and this much time has happened I can't help but to feel contempt for the snap project... but if it's IMPOSSIBLE to fix then I feel pity for snap... but anyways, my views on this have no relevance, I'm just a single user, and I only have three applications installed with snap: Audacity, VLC, and Chromium. I was able to build Audacity from source, and I'm sure that there is a way to use VLC and Chromium without Snap, there has to be a way, so even if I purge snap, I'm just a random person of the world, it's not going to change anything, just one more of the many affected by this design that shouldn't have even existed in the first place. So, why even write? So the people at the Snap project can see that they are getting uninstalled BECAUSE OF THIS ISSUE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893813] Re: the super key is not working to show the overview of all running applications like before
What happens when you press the Super key? Please attach a photo or video. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893813 Title: the super key is not working to show the overview of all running applications like before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893813] Re: the super key is not working to show the overview of all running applications like before
Also what do you mean by "recents"? The Super key is only meant to show windows on the current workspace. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893813 Title: the super key is not working to show the overview of all running applications like before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
We are going to have a solution from upstream soon. https://mailman.alsa-project.org/pipermail/alsa- devel/2020-September/173471.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893813] Re: the super key is not working to show the overview of all running applications like before
Please: 1. Press the Super key. 2. Open a Terminal and run: journalctl -b0 > journal.txt and then attach the resulting text file here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893813 Title: the super key is not working to show the overview of all running applications like before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
Please: 1. Follow these instructions to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment 2. After the freeze happens next, reboot and then run: journalctl -b-1 > prevboot.txt lspci -kv > lspci.txt and attach the resulting text files here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893945] Re: freezes when super key is pressed
Please also run: gsettings list-recursively org.gnome.shell > settings.txt and attach the resulting text file here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893945 Title: freezes when super key is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887821] Re: [nvidia] gnome-shell GUI freezes totally
It's suspicious the problem in comment #10 occurred as the Nvidia driver was starting. Also that seems to be an odd version of the Nvidia driver we don't distribute. If you installed the Nvidia driver manually then please uninstall it and then use the 'Additional Drivers' app to install a supported version. If you installed the Nvidia driver from an older Ubuntu update then your system is out of date and needs updating now. So run: sudo apt update sudo apt full-upgrade Reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887821 Title: [nvidia] gnome-shell GUI freezes totally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1887821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886345] Re: [i915][snb] Icons and text corrupted and/or missing
** Summary changed: - Icons and text corrupted and/or missing + [i915][snb] Icons and text corrupted and/or missing ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886345 Title: [i915][snb] Icons and text corrupted and/or missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880954] Re: Ubuntu 20.04 freezes when logging in with external monitors connected [Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-e
Please remember to answer comment #13. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** Changed in: mutter (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/1880954 Title: Ubuntu 20.04 freezes when logging in with external monitors connected [Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677067] Re: No subwoofer and frontcenter with 5.1 soundblaster x-fi
This bug is closed. Please open a new bug by running: ubuntu-bug pulseaudio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677067 Title: No subwoofer and frontcenter with 5.1 soundblaster x-fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/677067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed
Thanks for the further investigation, Christian.
So, it doesn't seem to me that /bin/systemd-tty-ask-password-agent is
the culprit here. Actually, if you look at when it is invoked, you will
notice that it is only executed when the systemctl command is issued
from the tty, which is not our case here: the command that is hanging
("systemctl reload squid") is being invoked indirectly due to the start
of dnsmasq.service.
When we issue a "systemctl start dnsmasq", we can see /bin/systemd-tty-
ask-password-agent there, but not as a child of the "systemctl reload
squid":
root9164 0.0 0.0 26164 1040 pts/0S+ 22:23 0:00 |
\_ systemctl start dnsmasq.service
root9165 0.0 0.0 12512 2084 pts/0S+ 22:23 0:00 |
\_ /bin/bash /bin/systemd-tty-ask-password-agent --watch
This is because we invoked "systemctl start dnsmasq" from the tty. We
can easily verify that /bin/systemd-tty-ask-password-agent is not to
blame by using "systemctl --no-ask-password stop dnsmasq" and then
"systemctl --no-ask-password start dnsmasq", and verifying that the hang
still happens even though /bin/systemd-tty-ask-password-agent was not
invoked.
Anyway, continuing the investigation here, this is the output of
"systemctl list-jobs":
$ systemctl list-jobs --all
JOB UNIT TYPE STATE
2512 dnsmasq.service start running
2561 squid.service reload waiting
2560 nss-lookup.target start waiting
3 jobs listed.
Nothing really new here, except the fact that the squid reload happens
*because* of the nss-lookup.target start, and both jobs are blocked
waiting. It's interesting to notice that squid's SysV init file says
that squid "Should-Start: $named", which translated to squid trying to
start nss-lookup.target itself. I think this is a strong indicator that
we might be seeing a deadlock here.
After a bit more investigation, I found
https://github.com/systemd/systemd/issues/10464, which led me to
https://github.com/systemd/systemd/pull/13860. I tried backporting the
patch (which is very simple) and seeing if it had any impact, but
unfortunately it didn't.
I then did a quick test and hacked /usr/sbin/invoke-rc.d, specifically
around line 570, and commented out the "if" surrounding sctl_args
="--job-mode=ignore-dependencies" (in other words, I made systemctl
always use this option), and unsurprisingly the bug went away. However,
just like with the "--no-block" hack I mentioned in my previous comment,
I'm not sure this is a good solution for the problem.
As I'm running out of ideas here, I'd like to propose a possible fix for
the problem, based on what Martin Pitt wrote in one of the bug reports I
mentioned (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777113).
I'd like to suggest that we expand /etc/resolvconf/update-libc.d/squid
to take into account whether systemd is being used behind the scenes,
and invoke systemctl to reload squid while also passing "--no-block" to
it. Something like this:
if [ -d /run/systemd ]; then
systemctl --no-block reload squid
else
invoke-rc.d squid reload || true
fi
Based on local tests here, this works and has the benefit of unblocking
nss-lookup.target to also finish, which means that, by the end of the
"systemctl start dnsmasq" process, we will have both successfully
reloaded squid *and* started nss-lookup.target (as well as started
dnsmasq.service, of course).
This is not the perfect solution, of course, but I feel like we're
wasting a lot of time on this old bug already, and this solution is not
entirely bad, IMHO. We could in theory try to bisect systemd between
xenial and bionic and see if we could determine what change (or changes)
made this scenario work OK on the latter, but that's assuming that it is
systemd indeed who is causing this (I think it is, but I'm not 100% sure
yet).
Anyway, I'll wait for your answer in the morning. We can discuss this
during standup too, if you'd like.
** Bug watch added: github.com/systemd/systemd/issues #10464
https://github.com/systemd/systemd/issues/10464
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761096
Title:
dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1761096/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894016] Re: package shim-signed 1.33.1~16.04.6+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
The error in your log is: Setting up grub-efi-amd64-signed (1.66.28+2.02~beta2-36ubuntu3.28) ... Installing for x86_64-efi platform. grub-install: error: cannot find EFI directory. Why is your ESP not mounted at /boot/efi? ** Changed in: shim-signed (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/1894016 Title: package shim-signed 1.33.1~16.04.6+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1894016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583705] Re: [SRU] unmatched entries for postfix
** Description changed:
[Impact]
Postfix backwards-compatibility notices aren't handled by logwatch, and
thus end up in the "Unmatched Entries" section, one per event. These
informational messages clutters up the logwatch reports unnecessarily.
-
[Test Case]
$ export CODENAME="focal"
$ lxc launch ubuntu:${CODENAME} test-logwatch
$ lxc exec test-logwatch -- bash
# apt-get update
# apt-get dist-upgrade -y
# apt-get install -y logwatch
# wget
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+attachment/5407064/+files/unmatched-entries-postfix%3Amail.log
# cat unmatched-entries-postfix%3Amail.log >> /var/log/mail.log
# logwatch --detail High --service all --range all --output stdout
Without the fix, there will be unmatched entries regarding backwards-
compatibility; with the fix there will be a simpler notice that Postfix
is running in backwards compatible mode.
(Note: For testing it's not really necessary to trigger the original
condition that produces the log entry, since for Logwatch the purpose is
more about making sure the entry is detected and processed
appropriately.)
-
[Regression Potential]
Since logwatch filters logs for errors pertinent to administrators,
standard things to watch out for are undesired changes in this filtering
behavior, such as flagging or failing to flag issues differently than
before, other than the specific messages being filtered with this
change.
-
- [Fix]
-
- [Discussion]
[Original Report]
Under the "Postfix" heading, the following lines appear as unmatched:
**Unmatched Entries**
1 May 18 16:58:35 Hostname postfix[4027]: Postfix is running with
backwards-compatible default settings
1 May 18 16:58:35 Hostname postfix[4027]: To disable backwards
compatibility use "postconf compatibility_level=2" and "postfix reload"
1 May 18 16:58:35 Hostname postfix[4027]: See
http://www.postfix.org/COMPATIBILITY_README.html for details
1 May 18 16:57:12 Hostname postgrey[2173]: Resolved [localhost]:10023
to [127.0.0.1]:10023, IPv4
-
Description: Ubuntu 16.04 LTS
Release: 16.04
logwatch:
Installed: 7.4.2-1ubuntu1
Candidate: 7.4.2-1ubuntu1
Version table:
*** 7.4.2-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
postfix:
Installed: 3.1.0-3
Candidate: 3.1.0-3
Version table:
*** 3.1.0-3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583705
Title:
[SRU] unmatched entries for postfix
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578001] Re: unmatched entries for isc-dhcp-server
** Description changed:
[Impact]
dhcp "lease under threshold" messages aren't handled by logwatch, and
thus end up in the "Unmatched Entries" section, one per event. These
innocuous notices clutters up the logwatch reports unnecessarily.
-
[Test Case]
$ export CODENAME="focal"
$ lxc launch ubuntu:${CODENAME} test-logwatch
$ lxc exec test-logwatch -- bash
# apt-get update
# apt-get dist-upgrade -y
# apt-get install -y logwatch
# wget
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1578001/+attachment/5407062/+files/unmatched-entries-isc-dhcp-server%3Akern.log
# cat unmatched-entries-isc-dhcp-server:kern.log >> /var/log/kern.log
# logwatch --detail High --service all --range all --output stdout
Without the fix, there will be unmatched entries from reuse_lease
regarding lease age thresholds; with the fix there will be no such
messages.
(Note: For testing it's not really necessary to trigger the original
condition that produces the log entry, since for Logwatch the purpose is
more about making sure the entry is detected and processed
appropriately.)
-
[Regression Potential]
Since logwatch filters logs for errors pertinent to administrators,
standard things to watch out for are undesired changes in this filtering
behavior, such as flagging or failing to flag issues differently than
before, other than the specific messages being filtered with this
change.
- [Fix]
-
- [Discussion]
[Original Report]
Under the "dhcpd" heading, the following isc-dhcp-server lines appear as
unknown:
Unknown Entries:
Config file: /etc/dhcp/dhcpd.conf: 1 Time(s)
Database file: /var/lib/dhcp/dhcpd.leases: 1 Time(s)
PID file: /run/dhcp-server/dhcpd.pid: 1 Time(s)
Server starting service.: 1 Time(s)
reuse_lease: lease age 16261 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 16268 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 16391 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 16394 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 1728 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 17474 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 17475 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 26177 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 26179 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 28852 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 28854 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 3064 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 3229 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 35305 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 35325 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 35326 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 49459 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 52188 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 811 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
-
Description: Ubuntu 16.04 LTS
Release: 16.04
logwatch:
Installed: 7.4.2-1ubuntu1
Candidate: 7.4.2-1ubuntu1
Version table:
*** 7.4.2-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
isc-dhcp-server:
Installed: 4.3.3-5ubuntu12
Candidate: 4.3.3-5ubuntu12
Version table:
*** 4.3.3-5ubuntu12 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578001
Title:
unmatched entries for isc-dhcp-server
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1578001/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
[Bug 1577948] Re: unmatched entries for apparmor STATUS messages
** Description changed:
[Impact]
Various AppArmor messages aren't handled by logwatch, and thus end up in
the "Unmatched Entries" section. Some of these are noteworthy, others
are innocuous, but given the quantity and variety of them, they can
clutter the log. Common ones should be either ignored or matched and
summarized, as appropriate.
-
[Test Case]
$ export CODENAME="focal"
$ lxc launch ubuntu:${CODENAME} test-logwatch
$ lxc exec test-logwatch -- bash
# apt-get update
# apt-get dist-upgrade -y
# apt-get install -y logwatch
# wget
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1577948/+attachment/5407058/+files/unmatched-entries-apparmor%3Akern.log
# cat unmatched-entries-apparmor:kern.log >> /var/log/kern.log
# logwatch --detail High --service all --range all --output stdout
Without the fix, there will be unmatched entries shown for
apparmor="STATUS" ... profile="unconfined"; with the fix they won't
display.
(Note: For testing it's not really necessary to trigger the original
condition that produces the log entry, since for Logwatch the purpose is
more about making sure the entry is detected and processed
appropriately.)
-
[Regression Potential]
Since logwatch filters logs for errors pertinent to administrators,
standard things to watch out for are undesired changes in this filtering
behavior, such as flagging or failing to flag issues differently than
before, other than the specific messages being filtered with this
change.
-
- [Fix]
-
- [Discussion]
[Original Report]
Under the "Kernel Audit" heading, the following apparmor lines appear as
unmatched:
**Unmatched Entries**
audit: type=1400 audit(1462209116.753:18): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/usr/sbin/named"
pid=22094 comm="apparmor_parser"
audit: type=1400 audit(1462209262.641:2): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/bin/freshclam"
pid=1760 comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:3): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1759
comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:4): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1759
comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:5): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=1759 comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:6): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/connman/scripts/dhclient-script" pid=1759 comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:7): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/clamd" pid=1765
comm="apparmor_parser"
audit: type=1400 audit(1462209262.673:8): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed"
pid=1767 comm="apparmor_parser"
audit: type=1400 audit(1462209262.677:9): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/cups/backend/cups-pdf" pid=1768 comm="apparmor_parser"
audit: type=1400 audit(1462209262.677:10): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=1768
comm="apparmor_parser"
audit: type=1400 audit(1462209262.677:11): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/sbin/cupsd//third_party" pid=1768 comm="apparmor_parser"
-
Description:Ubuntu 16.04 LTS
Release:16.04
logwatch:
Installed: 7.4.2-1ubuntu1
Candidate: 7.4.2-1ubuntu1
Version table:
*** 7.4.2-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577948
Title:
unmatched entries for apparmor STATUS messages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1577948/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892269] Re: Unmatched entry for exim with selfsigned certificate
** Description changed:
[Impact]
Exim issues a warning when self-signed certificates are used, but these
messages aren't handled by logwatch, and thus end up in the "Unmatched Entries"
section, one per event. It is not uncommon to run Exim with self-signed
certificates, since it will behave that way by default on a simple
installation, however they are worth mentioning in the log output since it
could indicate a mis-configuration if signed certs were intended, so should be
matched and summarized.
[Test Case]
$ export CODENAME="focal"
$ lxc launch ubuntu:${CODENAME} test-logwatch
$ lxc exec test-logwatch -- bash
# apt-get update
# apt-get dist-upgrade -y
# apt-get install -y logwatch
# wget
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1892269/+attachment/5407060/+files/unmatched-entries-exim%3Aexim4.mainlog.1
# cat unmatched-entries-exim:exim4.mainlog.1 >> /var/log/exim4/mainlog.1
# logwatch --detail High --service all --range all --output stdout
Without the fix, there will be unmatched entries with "BAD FORMAT"
alerts; with the fix there will be a calmer mention that self-signed
certs are in use.
(Note: For testing it's not really necessary to trigger the original
condition that produces the log entry, since for Logwatch the purpose is
more about making sure the entry is detected and processed
appropriately.)
[Regression Potential]
Since logwatch filters logs for errors pertinent to administrators,
standard things to watch out for are undesired changes in this filtering
behavior, such as flagging or failing to flag issues differently than
before, other than the specific messages being filtered with this
change.
- [Fix]
-
- [Discussion]
[Original Report]
On focal with exim installed, I'm seeing unmatched entries about self-signed
certs:
* BAD FORMAT (Possible data corruption or Exim bug) *
Suggested action: either install a certificate or change
tls_advertise_hosts option
...
**Unmatched Entries**
2020-04-24 20:30:42 Warning: No server certificate defined; will use a
selfsigned one.: 2 Time(s)
2020-04-24 21:00:42 Warning: No server certificate defined; will use a
selfsigned one.: 1 Time(s)
2020-04-24 21:30:42 Warning: No server certificate defined; will use a
selfsigned one.: 1 Time(s)
2020-04-24 22:00:42 Warning: No server certificate defined; will use a
selfsigned one.: 1 Time(s)
The logs show:
2020-04-25 10:00:42 Warning: No server certificate defined; will use a
selfsigned one.
Suggested action: either install a certificate or change tls_advertise_hosts
option
2020-04-25 10:00:42 Start queue run: pid=3512600
2020-04-25 10:00:42 End queue run: pid=3512600
So the 'BAD FORMAT' is simply a continuation of the warning line
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892269
Title:
Unmatched entry for exim with selfsigned certificate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1892269/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890752] Re: unmatched entry for gnome-keyring-daemon on focal
** Description changed:
[Impact]
Gnome keyring re-registration messages aren't handled by logwatch, and
thus end up in the "Unmatched Entries" section, one per event. As the
items are already registered, these aren't flagging actual issues and as
a result clutters up the logwatch reports unnecessarily.
-
[Test Case]
$ export CODENAME="focal"
$ lxc launch ubuntu:${CODENAME} test-logwatch
$ lxc exec test-logwatch -- bash
# apt-get update
# apt-get dist-upgrade -y
# apt-get install -y logwatch
# wget
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890752/+attachment/5407061/+files/unmatched-entries-gnome-keyring-daemon%3Aauth.log
# cat unmatched-entries-gnome-keyring-daemon:auth.log >> /var/log/auth.log
# logwatch --detail High --service all --range all --output stdout
Without the fix, there will be unmatched entries about gnome keyring re-
registration; with the fix there will be no such entries.
(Note: For testing it's not really necessary to trigger the original
condition that produces the log entry, since for Logwatch the purpose is
more about making sure the entry is detected and processed
appropriately.)
-
[Regression Potential]
Since logwatch filters logs for errors pertinent to administrators,
standard things to watch out for are undesired changes in this filtering
behavior, such as flagging or failing to flag issues differently than
before, other than the specific messages being filtered with this
change.
- [Fix]
-
- [Discussion]
[Original Report]
$ sudo logwatch --detail Low --range today --service all --output stdout
- Connections (secure-log) Begin
**Unmatched Entries**
gnome-keyring-daemon: asked to register item
/org/freedesktop/secrets/collection/login/3, but it's already registered: 1
Time(s)
-- Connections (secure-log) End
-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890752
Title:
unmatched entry for gnome-keyring-daemon on focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890752/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890749] Re: Missing perl 'Sys' module in system config summary on focal
** Description changed:
[Impact]
Logwatch's Sys perl module is optional per distro policy and only used to
display current cpu and memory levels, strictly for informational reasons.
The warnings issued by Logwatch do not indicate an actual problem, but they do
clutter the logwatch report, particularly since they're displayed at the top of
the report.
[Test Case]
$ export CODENAME="focal"
$ lxc launch ubuntu:${CODENAME} test-logwatch
$ lxc exec test-logwatch -- bash
# apt-get update
# apt-get dist-upgrade -y
# apt-get install -y logwatch
Without the fix, the start of the log will show an error message about
Sys::CPU and Sys::MemInfo not being installed. With the fix there will
be no error message.
-
[Regression Potential]
Since logwatch filters logs for errors pertinent to administrators,
standard things to watch out for are undesired changes in this filtering
behavior, such as flagging or failing to flag issues differently than
before, other than the specific messages being filtered with this
change.
- [Fix]
-
- [Discussion]
[Original Report]
$ sudo logwatch --detail Low --range today --service all --output stdout
- System Configuration Begin
No Sys::CPU module installed. To install, execute the command:
perl -MCPAN -e 'install Sys::CPU'
No Sys::MemInfo module installed. To install, execute the command:
perl -MCPAN -e 'install Sys::MemInfo'
Machine: x86_64
Release: Linux 5.4.0-40-generic
-- System Configuration End
-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890749
Title:
Missing perl 'Sys' module in system config summary on focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890749/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894017] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894017 Title: Keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894018] [NEW] Visible Network list interface disconnects without user prompt upon just clicking the netowrk name
Public bug reported: Visible Network wifi list interface Be connected to some wifi network Click on any network name (reconnects if clicked on currently connected network, and disconnects when clicked on some other network) Current wifi connection disconnects. No prompt no nothing. Just disconnects/reconnects. It would be best to ask prior to disconnect. It would be good to prompt whether user wants to initiate connection (and just then prompt for password). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 03:16:05 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-01 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894018 Title: Visible Network list interface disconnects without user prompt upon just clicking the netowrk name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578001] Re: unmatched entries for isc-dhcp-server
** Description changed:
- Under the "dhcpd" heading, the following isc-dhcp-server lines appear as
- unknown:
+ [Impact]
+
+ dhcp "lease under threshold" messages aren't handled by logwatch, and
+ thus end up in the "Unmatched Entries" section, one per event. These
+ innocuous notices clutters up the logwatch reports unnecessarily.
+
+
+ [Test Case]
+
+ $ export CODENAME="focal"
+ $ lxc launch ubuntu:${CODENAME} test-logwatch
+ $ lxc exec test-logwatch -- bash
+
+ # apt-get update
+ # apt-get dist-upgrade -y
+ # apt-get install -y logwatch
+
+ # wget
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1578001/+attachment/5407062/+files/unmatched-entries-isc-dhcp-server%3Akern.log
+ # cat unmatched-entries-isc-dhcp-server:kern.log >> /var/log/kern.log
+
+ # logwatch --detail High --service all --range all --output stdout
+
+ Without the fix, there will be unmatched entries from reuse_lease
+ regarding lease age thresholds; with the fix there will be no such
+ messages.
+
+ (Note: For testing it's not really necessary to trigger the original
+ condition that produces the log entry, since for Logwatch the purpose is
+ more about making sure the entry is detected and processed
+ appropriately.)
+
+
+ [Regression Potential]
+
+ Since logwatch filters logs for errors pertinent to administrators,
+ standard things to watch out for are undesired changes in this filtering
+ behavior, such as flagging or failing to flag issues differently than
+ before, other than the specific messages being filtered with this
+ change.
+
+ [Fix]
+
+ [Discussion]
+
+ [Original Report]
+ Under the "dhcpd" heading, the following isc-dhcp-server lines appear as
unknown:
Unknown Entries:
Config file: /etc/dhcp/dhcpd.conf: 1 Time(s)
Database file: /var/lib/dhcp/dhcpd.leases: 1 Time(s)
PID file: /run/dhcp-server/dhcpd.pid: 1 Time(s)
Server starting service.: 1 Time(s)
reuse_lease: lease age 16261 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 16268 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 16391 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 16394 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 1728 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 17474 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 17475 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 26177 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 26179 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 28852 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 28854 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 3064 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 3229 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 35305 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 35325 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 35326 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 49459 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 52188 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
reuse_lease: lease age 811 (secs) under 25% threshold, reply with
unaltered, existing lease: 1 Time(s)
-
Description: Ubuntu 16.04 LTS
Release: 16.04
logwatch:
Installed: 7.4.2-1ubuntu1
Candidate: 7.4.2-1ubuntu1
Version table:
*** 7.4.2-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
isc-dhcp-server:
- Installed: 4.3.3-5ubuntu12
- Candidate: 4.3.3-5ubuntu12
- Version table:
- *** 4.3.3-5ubuntu12 500
- 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 4.3.3-5ubuntu12
+ Candidate: 4.3.3-5ubuntu12
+ Version table:
+ *** 4.3.3-5ubuntu12 500
+ 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Bug 1583705] Re: [SRU] unmatched entries for postfix
** Description changed:
+ [Impact]
+
+ Postfix backwards-compatibility notices aren't handled by logwatch, and
+ thus end up in the "Unmatched Entries" section, one per event. These
+ informational messages clutters up the logwatch reports unnecessarily.
+
+
+ [Test Case]
+
+ $ export CODENAME="focal"
+ $ lxc launch ubuntu:${CODENAME} test-logwatch
+ $ lxc exec test-logwatch -- bash
+
+ # apt-get update
+ # apt-get dist-upgrade -y
+ # apt-get install -y logwatch
+
+ # wget
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+attachment/5407064/+files/unmatched-entries-postfix%3Amail.log
+ # cat unmatched-entries-postfix%3Amail.log >> /var/log/mail.log
+
+ # logwatch --detail High --service all --range all --output stdout
+
+ Without the fix, there will be unmatched entries regarding backwards-
+ compatibility; with the fix there will be a simpler notice that Postfix
+ is running in backwards compatible mode.
+
+ (Note: For testing it's not really necessary to trigger the original
+ condition that produces the log entry, since for Logwatch the purpose is
+ more about making sure the entry is detected and processed
+ appropriately.)
+
+
+ [Regression Potential]
+
+ Since logwatch filters logs for errors pertinent to administrators,
+ standard things to watch out for are undesired changes in this filtering
+ behavior, such as flagging or failing to flag issues differently than
+ before, other than the specific messages being filtered with this
+ change.
+
+
+ [Fix]
+
+ [Discussion]
+
+ [Original Report]
Under the "Postfix" heading, the following lines appear as unmatched:
**Unmatched Entries**
- 1 May 18 16:58:35 Hostname postfix[4027]: Postfix is running with
backwards-compatible default settings
- 1 May 18 16:58:35 Hostname postfix[4027]: To disable backwards
compatibility use "postconf compatibility_level=2" and "postfix reload"
- 1 May 18 16:58:35 Hostname postfix[4027]: See
http://www.postfix.org/COMPATIBILITY_README.html for details
- 1 May 18 16:57:12 Hostname postgrey[2173]: Resolved [localhost]:10023
to [127.0.0.1]:10023, IPv4
+ 1 May 18 16:58:35 Hostname postfix[4027]: Postfix is running with
backwards-compatible default settings
+ 1 May 18 16:58:35 Hostname postfix[4027]: To disable backwards
compatibility use "postconf compatibility_level=2" and "postfix reload"
+ 1 May 18 16:58:35 Hostname postfix[4027]: See
http://www.postfix.org/COMPATIBILITY_README.html for details
+ 1 May 18 16:57:12 Hostname postgrey[2173]: Resolved [localhost]:10023
to [127.0.0.1]:10023, IPv4
-
Description: Ubuntu 16.04 LTS
Release: 16.04
logwatch:
- Installed: 7.4.2-1ubuntu1
- Candidate: 7.4.2-1ubuntu1
- Version table:
- *** 7.4.2-1ubuntu1 500
- 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
- 100 /var/lib/dpkg/status
+ Installed: 7.4.2-1ubuntu1
+ Candidate: 7.4.2-1ubuntu1
+ Version table:
+ *** 7.4.2-1ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
+ 100 /var/lib/dpkg/status
postfix:
- Installed: 3.1.0-3
- Candidate: 3.1.0-3
- Version table:
- *** 3.1.0-3 500
- 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 3.1.0-3
+ Candidate: 3.1.0-3
+ Version table:
+ *** 3.1.0-3 500
+ 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583705
Title:
[SRU] unmatched entries for postfix
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577948] Re: unmatched entries for apparmor STATUS messages
** Description changed:
[Impact]
- Various AppArmor messages aren't handled by logwatch, and thus end up in the
"Unmatched Entries" section. Some of these are noteworthy, others are
innocuous, but given the quantity and variety of them, they can clutter the
log. Common ones should be either ignored or matched and summarized, as
appropriate.
+
+ Various AppArmor messages aren't handled by logwatch, and thus end up in
+ the "Unmatched Entries" section. Some of these are noteworthy, others
+ are innocuous, but given the quantity and variety of them, they can
+ clutter the log. Common ones should be either ignored or matched and
+ summarized, as appropriate.
[Test Case]
$ export CODENAME="focal"
$ lxc launch ubuntu:${CODENAME} test-logwatch
$ lxc exec test-logwatch -- bash
# apt-get update
# apt-get dist-upgrade -y
# apt-get install -y logwatch
# wget
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1577948/+attachment/5407058/+files/unmatched-entries-apparmor%3Akern.log
# cat unmatched-entries-apparmor:kern.log >> /var/log/kern.log
# logwatch --detail High --service all --range all --output stdout
Without the fix, there will be unmatched entries shown for
apparmor="STATUS" ... profile="unconfined"; with the fix they won't
display.
(Note: For testing it's not really necessary to trigger the original
condition that produces the log entry, since for Logwatch the purpose is
more about making sure the entry is detected and processed
appropriately.)
[Regression Potential]
Since logwatch filters logs for errors pertinent to administrators,
standard things to watch out for are undesired changes in this filtering
behavior, such as flagging or failing to flag issues differently than
before, other than the specific messages being filtered with this
change.
[Fix]
[Discussion]
[Original Report]
Under the "Kernel Audit" heading, the following apparmor lines appear as
unmatched:
**Unmatched Entries**
audit: type=1400 audit(1462209116.753:18): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/usr/sbin/named"
pid=22094 comm="apparmor_parser"
audit: type=1400 audit(1462209262.641:2): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/bin/freshclam"
pid=1760 comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:3): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1759
comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:4): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1759
comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:5): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=1759 comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:6): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/connman/scripts/dhclient-script" pid=1759 comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:7): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/clamd" pid=1765
comm="apparmor_parser"
audit: type=1400 audit(1462209262.673:8): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed"
pid=1767 comm="apparmor_parser"
audit: type=1400 audit(1462209262.677:9): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/cups/backend/cups-pdf" pid=1768 comm="apparmor_parser"
audit: type=1400 audit(1462209262.677:10): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=1768
comm="apparmor_parser"
audit: type=1400 audit(1462209262.677:11): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/sbin/cupsd//third_party" pid=1768 comm="apparmor_parser"
-
Description:Ubuntu 16.04 LTS
Release:16.04
logwatch:
Installed: 7.4.2-1ubuntu1
Candidate: 7.4.2-1ubuntu1
Version table:
*** 7.4.2-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577948
Title:
unmatched entries for apparmor STATUS messages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1577948/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894017] [NEW] Keyboard not working
Public bug reported: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894017 Title: Keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890752] Re: unmatched entry for gnome-keyring-daemon on focal
** Description changed:
+ [Impact]
+
+ Gnome keyring re-registration messages aren't handled by logwatch, and
+ thus end up in the "Unmatched Entries" section, one per event. As the
+ items are already registered, these aren't flagging actual issues and as
+ a result clutters up the logwatch reports unnecessarily.
+
+
+ [Test Case]
+
+ $ export CODENAME="focal"
+ $ lxc launch ubuntu:${CODENAME} test-logwatch
+ $ lxc exec test-logwatch -- bash
+
+ # apt-get update
+ # apt-get dist-upgrade -y
+ # apt-get install -y logwatch
+
+ # wget
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890752/+attachment/5407061/+files/unmatched-entries-gnome-keyring-daemon%3Aauth.log
+ # cat unmatched-entries-gnome-keyring-daemon:auth.log >> /var/log/auth.log
+
+ # logwatch --detail High --service all --range all --output stdout
+
+ Without the fix, there will be unmatched entries about gnome keyring re-
+ registration; with the fix there will be no such entries.
+
+ (Note: For testing it's not really necessary to trigger the original
+ condition that produces the log entry, since for Logwatch the purpose is
+ more about making sure the entry is detected and processed
+ appropriately.)
+
+
+ [Regression Potential]
+
+ Since logwatch filters logs for errors pertinent to administrators,
+ standard things to watch out for are undesired changes in this filtering
+ behavior, such as flagging or failing to flag issues differently than
+ before, other than the specific messages being filtered with this
+ change.
+
+ [Fix]
+
+ [Discussion]
+
+ [Original Report]
$ sudo logwatch --detail Low --range today --service all --output stdout
-
- - Connections (secure-log) Begin
-
- **Unmatched Entries**
- gnome-keyring-daemon: asked to register item
/org/freedesktop/secrets/collection/login/3, but it's already registered: 1
Time(s)
-
- -- Connections (secure-log) End -
+ - Connections (secure-log) Begin
+
+
+ **Unmatched Entries**
+ gnome-keyring-daemon: asked to register item
/org/freedesktop/secrets/collection/login/3, but it's already registered: 1
Time(s)
+
+ -- Connections (secure-log) End
+ -
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890752
Title:
unmatched entry for gnome-keyring-daemon on focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890752/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890749] Re: Missing perl 'Sys' module in system config summary on focal
** Description changed:
+ [Impact]
+ Logwatch's Sys perl module is optional per distro policy and only used to
display current cpu and memory levels, strictly for informational reasons.
The warnings issued by Logwatch do not indicate an actual problem, but they do
clutter the logwatch report, particularly since they're displayed at the top of
the report.
+
+ [Test Case]
+ $ export CODENAME="focal"
+ $ lxc launch ubuntu:${CODENAME} test-logwatch
+ $ lxc exec test-logwatch -- bash
+
+ # apt-get update
+ # apt-get dist-upgrade -y
+ # apt-get install -y logwatch
+
+ Without the fix, the start of the log will show an error message about
+ Sys::CPU and Sys::MemInfo not being installed. With the fix there will
+ be no error message.
+
+
+ [Regression Potential]
+
+ Since logwatch filters logs for errors pertinent to administrators,
+ standard things to watch out for are undesired changes in this filtering
+ behavior, such as flagging or failing to flag issues differently than
+ before, other than the specific messages being filtered with this
+ change.
+
+ [Fix]
+
+ [Discussion]
+
+ [Original Report]
$ sudo logwatch --detail Low --range today --service all --output stdout
- - System Configuration Begin
+ - System Configuration Begin
- No Sys::CPU module installed. To install, execute the command:
- perl -MCPAN -e 'install Sys::CPU'
-
- No Sys::MemInfo module installed. To install, execute the command:
- perl -MCPAN -e 'install Sys::MemInfo'
-
- Machine: x86_64
- Release: Linux 5.4.0-40-generic
-
- -- System Configuration End -
+ No Sys::CPU module installed. To install, execute the command:
+ perl -MCPAN -e 'install Sys::CPU'
+
+ No Sys::MemInfo module installed. To install, execute the command:
+ perl -MCPAN -e 'install Sys::MemInfo'
+
+ Machine: x86_64
+ Release: Linux 5.4.0-40-generic
+
+ -- System Configuration End
+ -
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890749
Title:
Missing perl 'Sys' module in system config summary on focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890749/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894016] [NEW] package shim-signed 1.33.1~16.04.6+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Not sure what needs to be fixed. I am just trying to apply updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.33.1~16.04.6+15+1552672080.a4a1fbe-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-180.210-generic 4.4.223 Uname: Linux 4.4.0-180-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 BootEFIContents: fw fwupx64.efi Date: Wed Sep 2 16:46:17 2020 EFITables: Aug 27 17:09:52 radame-Lenovo-G50-70 kernel: efi: EFI v2.31 by INSYDE Corp. Aug 27 17:09:52 radame-Lenovo-G50-70 kernel: efi: ACPI=0xaaffe000 ACPI 2.0=0xaaffe014 SMBIOS=0xaaebef98 Aug 27 17:09:52 radame-Lenovo-G50-70 kernel: Secure boot enabled Aug 27 17:12:17 radame-Lenovo-G50-70 fwupd[5499]: (fwupd:5499): Fu-WARNING **: disabling plugin because: failed to coldplug uefi: UEFI firmware updating not supported ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-01-07 (2065 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.33.1~16.04.6+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894016 Title: package shim-signed 1.33.1~16.04.6+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1894016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894016] Re: package shim-signed 1.33.1~16.04.6+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894016 Title: package shim-signed 1.33.1~16.04.6+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1894016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886345] Re: Icons and text corrupted and/or missing
Added CLUTTER_PAINT=disable-offscreen-redirect, still seeing corruption Ran Memtest86+ v5.31b for 8 hours, no errors detected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886345 Title: Icons and text corrupted and/or missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected
Symptom persists also with WaylandEnable=false in /etc/gdm3/custom.conf Removing "splash" in /etc/default/grub solves the problem (as stated before) Computer: DELL Notebook Precision 7520 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677067] Re: No subwoofer and frontcenter with 5.1 soundblaster x-fi
Because for my card, center channel is not called Center, LFE or CLFE like other cards, but it's Center/LFE instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677067 Title: No subwoofer and frontcenter with 5.1 soundblaster x-fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/677067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677067] Re: No subwoofer and frontcenter with 5.1 soundblaster x-fi
For Ubuntu 20.04 or any distro: I confirm that Middle/center/Subwoofer is working, when add this: [Element Center/LFE] switch = mute volume = merge override-map.1 = center,lfe To the /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf The card is Auzentech Auzen X-Fi Prelude 7.1 with Creative X-Fi 20k1 chip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677067 Title: No subwoofer and frontcenter with 5.1 soundblaster x-fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/677067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874362] Re: xenial/man8/update-smart-drivedb.8.html incorrect
I love you people and I love open source, but testing is a 'bridge too far' for me. Sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874362 Title: xenial/man8/update-smart-drivedb.8.html incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1874362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577948] Re: unmatched entries for apparmor STATUS messages
** Description changed:
- Under the "Kernel Audit" heading, the following apparmor lines appear as
- unmatched:
+ [Impact]
+ Various AppArmor messages aren't handled by logwatch, and thus end up in the
"Unmatched Entries" section. Some of these are noteworthy, others are
innocuous, but given the quantity and variety of them, they can clutter the
log. Common ones should be either ignored or matched and summarized, as
appropriate.
+
+
+ [Test Case]
+
+ $ export CODENAME="focal"
+ $ lxc launch ubuntu:${CODENAME} test-logwatch
+ $ lxc exec test-logwatch -- bash
+
+ # apt-get update
+ # apt-get dist-upgrade -y
+ # apt-get install -y logwatch
+
+ # wget
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1577948/+attachment/5407058/+files/unmatched-entries-apparmor%3Akern.log
+ # cat unmatched-entries-apparmor:kern.log >> /var/log/kern.log
+
+ # logwatch --detail High --service all --range all --output stdout
+
+ Without the fix, there will be unmatched entries shown for
+ apparmor="STATUS" ... profile="unconfined"; with the fix they won't
+ display.
+
+ (Note: For testing it's not really necessary to trigger the original
+ condition that produces the log entry, since for Logwatch the purpose is
+ more about making sure the entry is detected and processed
+ appropriately.)
+
+
+ [Regression Potential]
+
+ Since logwatch filters logs for errors pertinent to administrators,
+ standard things to watch out for are undesired changes in this filtering
+ behavior, such as flagging or failing to flag issues differently than
+ before, other than the specific messages being filtered with this
+ change.
+
+ [Fix]
+
+ [Discussion]
+
+ [Original Report]
+ Under the "Kernel Audit" heading, the following apparmor lines appear as
unmatched:
**Unmatched Entries**
audit: type=1400 audit(1462209116.753:18): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/usr/sbin/named"
pid=22094 comm="apparmor_parser"
audit: type=1400 audit(1462209262.641:2): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/bin/freshclam"
pid=1760 comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:3): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1759
comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:4): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1759
comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:5): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=1759 comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:6): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/connman/scripts/dhclient-script" pid=1759 comm="apparmor_parser"
audit: type=1400 audit(1462209262.657:7): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/clamd" pid=1765
comm="apparmor_parser"
audit: type=1400 audit(1462209262.673:8): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed"
pid=1767 comm="apparmor_parser"
audit: type=1400 audit(1462209262.677:9): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/lib/cups/backend/cups-pdf" pid=1768 comm="apparmor_parser"
audit: type=1400 audit(1462209262.677:10): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=1768
comm="apparmor_parser"
audit: type=1400 audit(1462209262.677:11): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/sbin/cupsd//third_party" pid=1768 comm="apparmor_parser"
-
-
Description:Ubuntu 16.04 LTS
Release:16.04
logwatch:
- Installed: 7.4.2-1ubuntu1
- Candidate: 7.4.2-1ubuntu1
- Version table:
- *** 7.4.2-1ubuntu1 500
- 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
- 100 /var/lib/dpkg/status
+ Installed: 7.4.2-1ubuntu1
+ Candidate: 7.4.2-1ubuntu1
+ Version table:
+ *** 7.4.2-1ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
+ 100 /var/lib/dpkg/status
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577948
Title:
unmatched entries for apparmor STATUS messages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1577948/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892269] Re: Unmatched entry for exim with selfsigned certificate
** Description changed:
- On focal with exim installed, I'm seeing unmatched entries about self-
- signed certs:
+ [Impact]
+ Exim issues a warning when self-signed certificates are used, but these
messages aren't handled by logwatch, and thus end up in the "Unmatched Entries"
section, one per event. It is not uncommon to run Exim with self-signed
certificates, since it will behave that way by default on a simple
installation, however they are worth mentioning in the log output since it
could indicate a mis-configuration if signed certs were intended, so should be
matched and summarized.
- * BAD FORMAT (Possible data corruption or Exim bug) *
- Suggested action: either install a certificate or change
tls_advertise_hosts option
- ...
+ [Test Case]
+ $ export CODENAME="focal"
+ $ lxc launch ubuntu:${CODENAME} test-logwatch
+ $ lxc exec test-logwatch -- bash
+
+ # apt-get update
+ # apt-get dist-upgrade -y
+ # apt-get install -y logwatch
+
+ # wget
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1892269/+attachment/5407060/+files/unmatched-entries-exim%3Aexim4.mainlog.1
+ # cat unmatched-entries-exim:exim4.mainlog.1 >> /var/log/exim4/mainlog.1
+
+ # logwatch --detail High --service all --range all --output stdout
+
+ Without the fix, there will be unmatched entries with "BAD FORMAT"
+ alerts; with the fix there will be a calmer mention that self-signed
+ certs are in use.
+
+ (Note: For testing it's not really necessary to trigger the original
+ condition that produces the log entry, since for Logwatch the purpose is
+ more about making sure the entry is detected and processed
+ appropriately.)
+
+ [Regression Potential]
+ Since logwatch filters logs for errors pertinent to administrators,
+ standard things to watch out for are undesired changes in this filtering
+ behavior, such as flagging or failing to flag issues differently than
+ before, other than the specific messages being filtered with this
+ change.
+
+ [Fix]
+
+ [Discussion]
+
+ [Original Report]
+ On focal with exim installed, I'm seeing unmatched entries about self-signed
certs:
+
+ * BAD FORMAT (Possible data corruption or Exim bug) *
+ Suggested action: either install a certificate or change
tls_advertise_hosts option
+ ...
**Unmatched Entries**
2020-04-24 20:30:42 Warning: No server certificate defined; will use a
selfsigned one.: 2 Time(s)
2020-04-24 21:00:42 Warning: No server certificate defined; will use a
selfsigned one.: 1 Time(s)
2020-04-24 21:30:42 Warning: No server certificate defined; will use a
selfsigned one.: 1 Time(s)
2020-04-24 22:00:42 Warning: No server certificate defined; will use a
selfsigned one.: 1 Time(s)
The logs show:
2020-04-25 10:00:42 Warning: No server certificate defined; will use a
selfsigned one.
- Suggested action: either install a certificate or change tls_advertise_hosts
option
+ Suggested action: either install a certificate or change tls_advertise_hosts
option
2020-04-25 10:00:42 Start queue run: pid=3512600
2020-04-25 10:00:42 End queue run: pid=3512600
So the 'BAD FORMAT' is simply a continuation of the warning line
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892269
Title:
Unmatched entry for exim with selfsigned certificate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1892269/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894015] [NEW] /usr/games/ktuberling:11:memcpy:memcpy_pic:put_image_yuy2:i965_sw_putimage:i965_PutImage
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding ktuberling. This problem was most recently seen with package version 4:19.12.3-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/4247d15b170bb5043492511b5ede4aa3d4528e43 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: ktuberling (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894015 Title: /usr/games/ktuberling:11:memcpy:memcpy_pic:put_image_yuy2:i965_sw_putimage:i965_PutImage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ktuberling/+bug/1894015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893717] Re: Add Ubuntu Advantage service apt urls to valid mirrors
** Merge proposal linked: https://code.launchpad.net/~chad.smith/ubuntu/+source/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/390206 ** Merge proposal linked: https://code.launchpad.net/~chad.smith/ubuntu/+source/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/390207 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893717 Title: Add Ubuntu Advantage service apt urls to valid mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1893717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887432] Re: configuration file //.config/debconf-kde-helperrc not writable
** Also affects: aptdaemon 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/1887432 Title: configuration file //.config/debconf-kde-helperrc not writable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/1887432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894012] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894012 Title: touchpad and keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
