[Bug 1790223] [NEW] ubiquity crashed
Public bug reported: installing ubuntu on a second ssd while still running ubuntu 18, crashs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Aug 31 23:22:11 2018 EcryptfsInUse: Yes InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper pci=noaer iso-scan/filename=/isos/ubuntu-17.04-desktop-amd64.iso quiet splash nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off -- disablemodules=nouveau InstallationDate: Installed on 2017-04-25 (493 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubiquity-17.04.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790223 Title: ubiquity crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1790223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759836] Re: systemd-udevd consumes 100% of CPU
on bionic, stopping udevd and starting it again correct the problem: sudo systemctl stop systemd-udevd systemd-udevd-control.socket systemd-udevd-kernel.socket sudo systemctl start systemd-udevd systemd-udevd-control.socket systemd-udevd-kernel.socket -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774768] Re: systemd-udevd eats cpu in infinite loop when nvidia card is not plugged
** Description changed: i have a roaming ssd disk ubuntu 18.04 with proprietaty nvidia drivers installed from ubuntu thid party repository: ii nvidia-cuda-dev 9.1.85-3ubuntu1amd64 NVIDIA CUDA development files ii nvidia-cuda-doc 9.1.85-3ubuntu1all NVIDIA CUDA and OpenCL documentation ii nvidia-cuda-gdb 9.1.85-3ubuntu1amd64 NVIDIA CUDA Debugger (GDB) ii nvidia-cuda-toolkit 9.1.85-3ubuntu1amd64 NVIDIA CUDA development toolkit ii nvidia-dkms-396 396.24-0ubuntu0~gpu18.04.1 amd64 NVIDIA DKMS package ii nvidia-kernel-common-396 396.24-0ubuntu0~gpu18.04.1 amd64 Shared files used with the kernel module ii nvidia-kernel-source-396 396.24-0ubuntu0~gpu18.04.1 amd64 NVIDIA kernel source package ii nvidia-profiler 9.1.85-3ubuntu1amd64 NVIDIA Profiler for CUDA and OpenCL ii nvidia-settings 396.24-0ubuntu0~gpu18.04.1 amd64 Tool for configuring the NVIDIA graphics driver ii nvidia-visual-profiler 9.1.85-3ubuntu1amd64 NVIDIA Visual Profiler for CUDA and OpenCL r When i boot on my nvidia system , no problem. when i boot on other system , with other card, systemd-udevd eats lots cpu (nearby 100% or little more) and in logs i see infinite loop logging: Jun 2 11:23:16 localhost [19963]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/usr/bin/nvidia-smi' failed with exit code 2. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Start request repeated too quickly. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. Jun 2 11:23:16 localhost systemd[1]: Failed to start NVIDIA Persistence Daemon. Jun 2 11:23:16 localhost kernel: [ 2227.682538] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.682917] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.683149] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jun 2 11:23:16 localhost kernel: [ 2227.756646] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.756971] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.757149] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jun 2 11:23:16 localhost kernel: [ 2227.824072] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.824383] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.824596] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jun 2 11:23:16 localhost [19972]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/usr/bin/nvidia-smi' failed with exit code 2. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Start request repeated too quickly. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. Jun 2 11:23:16 localhost systemd[1]: Failed to start NVIDIA Persistence Daemon. the nvidia-uvm module is listed in /etc/modules. # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. nvidia-uvm it should just fail at boot time and do nothing else. + + when stopping systemd-udevd and starting it again, the problem disappear. + + + i hadn't this problem with ubuntu 16.X/17.X. it may be a nvidia driver/software pb too, so i will do a bug report on nvidia driver too. Regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 60-vlan-network-interface.rules 70-snap.core.rules Date: Sat Jun 2 11:16:41 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-25 (402 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64
[Bug 1774768] Re: systemd-udevd eats cpu in infinite loop when nvidia card is not plugged
** Description changed: i have a roaming ssd disk ubuntu 18.04 with proprietaty nvidia drivers installed . When i boot on my nvidia system , no problem. when i boot on other system , with other card, systemd-udevd eats lots cpu (nearby 100% of one core) and in logs i see infinite loop logging: Jun 2 11:23:16 localhost [19963]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/usr/bin/nvidia-smi' failed with exit code 2. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Start request repeated too quickly. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. Jun 2 11:23:16 localhost systemd[1]: Failed to start NVIDIA Persistence Daemon. Jun 2 11:23:16 localhost kernel: [ 2227.682538] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.682917] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.683149] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jun 2 11:23:16 localhost kernel: [ 2227.756646] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.756971] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.757149] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jun 2 11:23:16 localhost kernel: [ 2227.824072] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.824383] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.824596] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jun 2 11:23:16 localhost [19972]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/usr/bin/nvidia-smi' failed with exit code 2. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Start request repeated too quickly. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. Jun 2 11:23:16 localhost systemd[1]: Failed to start NVIDIA Persistence Daemon. + the nvidia-uvm module is listed in /etc/modules. + + + # /etc/modules: kernel modules to load at boot time. + # + # This file contains the names of kernel modules that should be loaded + # at boot time, one per line. Lines beginning with "#" are ignored. + nvidia-uvm + + it should just fail at boot time and do nothing else. + + i hadn't this problem with ubuntu 16.X/17.X. - it may be a nvidia driver/software pb too, so i will do a bug report on nvidia driver too. + it may be a nvidia driver/software pb too, so i will do a bug report on nvidia driver too. Regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 60-vlan-network-interface.rules 70-snap.core.rules Date: Sat Jun 2 11:16:41 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-25 (402 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE MRHM3AP ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=UUID=9ed36b5d-9fea-4544-b33c-a7c75c2cdfa5 ro rootflags=subvol=@ disablemodules=nouveau pci=noaer elevator=noop net.ifnames=0 ipv6.disable=1 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MRHM3AP dmi.board.vendor: GIGABYTE dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd01/29/2014:svnGIGABYTE:pnMRHM3AP:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnMRHM3AP:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MRHM3AP
[Bug 1774768] Re: systemd-udevd eats cpu in infinite loop when nvidia card is not plugged
** Description changed: - i have a roaming ssd disk ubuntu 18.04. - + i have a roaming ssd disk ubuntu 18.04 with proprietaty nvidia drivers installed . When i boot on my nvidia system , no problem. when i boot on other system , with other card, systemd-udevd eats lots cpu (nearby 100% of one core) and in logs i see infinite loop logging: - Jun 2 11:23:16 localhost [19963]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/usr/bin/nvidia-smi' failed with exit code 2. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Start request repeated too quickly. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. Jun 2 11:23:16 localhost systemd[1]: Failed to start NVIDIA Persistence Daemon. Jun 2 11:23:16 localhost kernel: [ 2227.682538] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.682917] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.683149] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jun 2 11:23:16 localhost kernel: [ 2227.756646] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.756971] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.757149] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jun 2 11:23:16 localhost kernel: [ 2227.824072] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.824383] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.824596] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jun 2 11:23:16 localhost [19972]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/usr/bin/nvidia-smi' failed with exit code 2. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Start request repeated too quickly. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. Jun 2 11:23:16 localhost systemd[1]: Failed to start NVIDIA Persistence Daemon. - i hadn't this problem with ubuntu 16.X/17.X. Regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 60-vlan-network-interface.rules 70-snap.core.rules Date: Sat Jun 2 11:16:41 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-25 (402 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE MRHM3AP ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=UUID=9ed36b5d-9fea-4544-b33c-a7c75c2cdfa5 ro rootflags=subvol=@ disablemodules=nouveau pci=noaer elevator=noop net.ifnames=0 ipv6.disable=1 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MRHM3AP dmi.board.vendor: GIGABYTE dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd01/29/2014:svnGIGABYTE:pnMRHM3AP:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnMRHM3AP:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MRHM3AP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: GIGABYTE ** Description changed: i have a roaming ssd disk ubuntu 18.04 with proprietaty nvidia drivers installed . When i boot on my nvidia system , no problem. when i boot on other system , with other card, systemd-udevd eats lots cpu (nearby 100% of one core) and in logs i see infinite loop logging:
[Bug 1774768] [NEW] systemd-udevd eats cpu in infinite loop when nvidia card is not plugged
Public bug reported: i have a roaming ssd disk ubuntu 18.04. When i boot on my nvidia system , no problem. when i boot on other system , with other card, systemd-udevd eats lots cpu (nearby 100% of one core) and in logs i see infinite loop logging: Jun 2 11:23:16 localhost [19963]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/usr/bin/nvidia-smi' failed with exit code 2. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Start request repeated too quickly. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. Jun 2 11:23:16 localhost systemd[1]: Failed to start NVIDIA Persistence Daemon. Jun 2 11:23:16 localhost kernel: [ 2227.682538] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.682917] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.683149] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jun 2 11:23:16 localhost kernel: [ 2227.756646] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.756971] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.757149] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jun 2 11:23:16 localhost kernel: [ 2227.824072] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 Jun 2 11:23:16 localhost kernel: [ 2227.824383] NVRM: No NVIDIA graphics adapter found! Jun 2 11:23:16 localhost kernel: [ 2227.824596] nvidia-nvlink: Unregistered the Nvlink Core, major device number 241 Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jun 2 11:23:16 localhost [19972]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory Jun 2 11:23:16 localhost systemd-udevd[492]: Process '/usr/bin/nvidia-smi' failed with exit code 2. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Start request repeated too quickly. Jun 2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. Jun 2 11:23:16 localhost systemd[1]: Failed to start NVIDIA Persistence Daemon. i hadn't this problem with ubuntu 16.X/17.X. Regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 60-vlan-network-interface.rules 70-snap.core.rules Date: Sat Jun 2 11:16:41 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-25 (402 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE MRHM3AP ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=UUID=9ed36b5d-9fea-4544-b33c-a7c75c2cdfa5 ro rootflags=subvol=@ disablemodules=nouveau pci=noaer elevator=noop net.ifnames=0 ipv6.disable=1 quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MRHM3AP dmi.board.vendor: GIGABYTE dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd01/29/2014:svnGIGABYTE:pnMRHM3AP:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnMRHM3AP:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MRHM3AP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: GIGABYTE ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774768 Title: systemd-udevd eats cpu in infinite loop when nvidia card is not plugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759836] Re: systemd-udevd consumes 100% of CPU
i have: - stopped systemd-udevd - uninstalled nvidia-compute-utils-396 - started systemd-udevd it s ok now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759836] Re: systemd-udevd consumes 100% of CPU
and cannot disable nvidia-persistenced.service: systemctl disable nvidia-persistenced.service -> wait a lng time and still here -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759836] Re: systemd-udevd consumes 100% of CPU
on official bionic , upgraded from artful: systemd-udevd eats lot cpu , trying to repeatly modprobe nvidia indefinitly , while it is not install in this computer : it is on a usb bootable ssd disk. i boot it on several computers, some have nvidia, some have not. it was working fine with artfull and zesty. i am using proprietary nvidia version 396 May 2 13:35:46 localhost kernel: [ 866.436341] nvidia-nvlink: Nvlink Core is being initialized, major device number 240 May 2 13:35:46 localhost kernel: [ 866.436566] NVRM: No NVIDIA graphics adapter found! May 2 13:35:46 localhost kernel: [ 866.436718] nvidia-nvlink: Unregistered the Nvlink Core, major device number 240 May 2 13:35:46 localhost kernel: [ 866.506576] nvidia-nvlink: Nvlink Core is being initialized, major device number 240 May 2 13:35:46 localhost kernel: [ 866.506832] NVRM: No NVIDIA graphics adapter found! May 2 13:35:46 localhost kernel: [ 866.506937] nvidia-nvlink: Unregistered the Nvlink Core, major device number 240 May 2 13:35:46 localhost systemd-udevd[19441]: Process '/usr/bin/nvidia-smi' failed with exit code 9. May 2 13:35:46 localhost systemd[1]: nvidia-persistenced.service: Start request repeated too quickly. May 2 13:35:46 localhost systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186662] Re: isc-dhcp-server fails to renew lease file
ubuntu 17.10 32 bits: the same Nov 17 22:02:45 nas dhclient[736]: can't create /var/lib/dhcp/dhclient.enp3s0.leases: Read-only file system drwxr-xr-x 1 root root 44 déc. 13 2016 . drwxr-xr-x 1 root root 738 juil. 16 18:11 .. -rw-r--r-- 1 root root 1094 nov. 17 22:02 dhclient.enp3s0.leases and there is no dhcp user account: root@nas:/etc# grep -i dhcp /etc/passwd /etc/group root@nas:/etc# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694987] Re: zesty: udev/rules.d empty
** Changed in: udev (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/udev/+question/638633 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694987 Title: zesty: udev/rules.d empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1694987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694987] [NEW] zesty: udev/rules.d empty
Public bug reported: On zesty, i am surprised to see that /etc/udev/rules.d is empty. Is it normal? What is the procedure to set wlan name for example? should i copy myself /lib/udev/rules.d/60-vlan-network-interface.rules in /etc/udev/rules.d? Regards. Gaetan ** Affects: udev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694987 Title: zesty: udev/rules.d empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1694987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448418] Re: Logout not working in Cairo Dock
ubuntu 17.04, cairo-dock 3.4.1: logout does nothing. gnome-session-quit --logout --no-prompt --force works fine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448418 Title: Logout not working in Cairo Dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock/+bug/1448418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685642] Re: 17.04: virt-manager package missing
apt update corrected the pb. ** Changed in: virt-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685642 Title: 17.04: virt-manager package missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1685642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685642] [NEW] 17.04: virt-manager package missing
Public bug reported: on live usb key ubuntu 17.04, trying to install libvirt and virt- manager. installing libvirt daemon and binaries: ok installing virt-manager: no package ... root@ubuntu:/home/ubuntu# apt search virt-manager Sorting... Done Full Text Search... Done root@ubuntu:/home/ubuntu# Regards ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685642 Title: 17.04: virt-manager package missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1685642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677417] Re: /etc/ld.so.conf.d/conjure-up.conf breaks apt on host system
To correct it temporaly: comment out the content: /etc/ld.so.conf.d/conjure-up.conf -> #/snap/conjure-up/156/usr/lib/x86_64-linux-gnu/ and call ldconfig. apt will work again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677417 Title: /etc/ld.so.conf.d/conjure-up.conf breaks apt on host system To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1677417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676127] [NEW] apacheds 2.0.0~M15 obsolete - do not work with apache directory studio
Public bug reported: Using apache directory studio in Eclipse (2.0.0 M23) , we cannot open apache-ds 2.0.0 M15.3 configuration file, since it is not compatible. We need M21 at least so why not the last M23. Is it possible to package a new version? Regards. ** Affects: apache-directory-server (Ubuntu) Importance: Undecided Status: New ** Tags: needs-packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676127 Title: apacheds 2.0.0~M15 obsolete - do not work with apache directory studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache-directory-server/+bug/1676127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676035] [NEW] apache directory server: do not start with systemctl
Public bug reported:
Environment:
--
on ubuntu 16.04.2 TLS
Issue:
systemctl start apacheds.service
Failed to start apacheds.service: Unit apacheds.service is not loaded properly:
Invalid argument.
See system logs and 'systemctl status apacheds.service' for details.
Steps to reproduce:
--
- install oracle jdk8 :
apt install oracle-java8-installer oracle-java8-unlimited-jce-policy
oracle-java8-set-default
- install apacheds:
apt install apacheds
- start apacheds:
systemctl enable apacheds.service
systemctl start apacheds.service
Logs/output/files:
root@security:~# systemctl status apacheds.service
● apacheds.service - Apache Directory Server
Loaded: error (Reason: Invalid argument)
Active: inactive (dead)
Mar 25 11:14:04 security systemd[1]: [/lib/systemd/system/apacheds.service:11]
Executable path is not absolute, ignoring: ${JAVA_HOME}/bin/java ${JAVA_OPTS}
-Dapacheds.controls=${ADS_CONTROLS}
Mar 25 11:14:04 security systemd[1]: apacheds.service: Service lacks both
ExecStart= and ExecStop= setting. Refusing.
Root cause
--
- first: apacheds.service contains syntax error
systemctl edit apacheds.service:
with won't work:
ExecStart=${JAVA_HOME}/bin/java ${JAVA_OPTS} \
-Dapacheds.controls=${ADS_CONTROLS} \
-Dapacheds.extendedOperations=${ADS_EXTENDED_OPERATIONS} \
-Dlog4j.configuration=file:${ADS_INSTANCES}/${ADS_INSTANCE}/conf/log4j.properties
\
-Dapacheds.log.dir=${ADS_INSTANCES}/${ADS_INSTANCE}/log \
-cp '${ADS_HOME}/lib/*' \
org.apache.directory.server.UberjarMain \
${ADS_INSTANCES}/${ADS_INSTANCE}/
this works fine:
ExecStart=/bin/sh -c "${JAVA_HOME}/bin/java ${JAVA_OPTS} \
-Dapacheds.controls=${ADS_CONTROLS} \
-Dapacheds.extendedOperations=${ADS_EXTENDED_OPERATIONS} \
-Dlog4j.configuration=file:${ADS_INSTANCES}/${ADS_INSTANCE}/conf/log4j.properties
\
-Dapacheds.log.dir=${ADS_INSTANCES}/${ADS_INSTANCE}/log \
-cp '${ADS_HOME}/lib/*' \
org.apache.directory.server.UberjarMain \
${ADS_INSTANCES}/${ADS_INSTANCE}/"
- second:
/usr/lib/jvm/default-java do not exists if oracle jdk is installed: i had to
create it:
cd /usr/lib/jvm/ && ln -s java-8-oracle default-java
** Affects: apache-directory-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676035
Title:
apache directory server: do not start with systemctl
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache-directory-server/+bug/1676035/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030471] Re: software-properties-gtk crashed with UnicodeDecodeError in record(): 'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte
NO. I don't think this is the root problem. There is a file read by software-property* somewhere which is not utf-8 compliant. This problem came after a long working fine system with 16.04. locale didn't changed. Could it be possible to output in the softawre-properties-tgk* code , the read failure "file name" which is in failure ? Telling it in the output could be helpfull to track problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1030471 Title: software-properties-gtk crashed with UnicodeDecodeError in record(): 'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1030471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1030471] Re: software-properties-gtk crashed with UnicodeDecodeError in record(): 'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte
ubuntu 16.04:
sudo software-properties-gtk -m -d
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:40:
PyGIWarning: Gdk was imported without specifying a version first. Use
gi.require_version('Gdk', '3.0') before import to ensure that the right version
gets loaded.
from gi.repository import GObject, Gdk, Gtk, Gio, GLib
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:40:
PyGIWarning: Gtk was imported without specifying a version first. Use
gi.require_version('Gtk', '3.0') before import to ensure that the right version
gets loaded.
from gi.repository import GObject, Gdk, Gtk, Gio, GLib
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 101, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 172, in __init__
self.show_keys()
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 867, in show_keys
for key in self.apt_key.list():
File "/usr/lib/python3/dist-packages/softwareproperties/AptAuth.py", line 78,
in list
for line in p:
File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xdf in position 3182:
invalid continuation byte
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1030471
Title:
software-properties-gtk crashed with UnicodeDecodeError in record():
'utf-8' codec can't decode byte 0x92 in position 1017: invalid start
byte
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1030471/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648143] [NEW] tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"
Public bug reported: Environment: Distribution: ubuntu Distribution version: 16.10 lxc info: apiextensions: storage_zfs_remove_snapshots container_host_shutdown_timeout container_syscall_filtering auth_pki container_last_used_at etag patch usb_devices https_allowed_credentials image_compression_algorithm directory_manipulation container_cpu_time storage_zfs_use_refquota storage_lvm_mount_options network profile_usedby container_push apistatus: stable apiversion: "1.0" auth: trusted environment: addresses: 163.172.48.149:8443 172.20.10.1:8443 172.20.11.1:8443 172.20.12.1:8443 172.20.22.1:8443 172.20.21.1:8443 10.8.0.1:8443 architectures: x86_64 i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificatefingerprint: 3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b driver: lxc driverversion: 2.0.5 kernel: Linux kernelarchitecture: x86_64 kernelversion: 4.8.0-27-generic server: lxd serverpid: 32694 serverversion: 2.4.1 storage: btrfs storageversion: 4.7.3 config: core.https_address: '[::]:8443' core.trust_password: true Container: ubuntu 16.10 Issue description -- tor can't start in a non privileged container Logs from the container: - Dec 7 15:03:00 anonymous tor[302]: Configuration was valid Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step APPARMOR spawning /usr/bin/tor: No such file or directory Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process exited, code=exited, status=231/APPARMOR Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed state. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 'exit-code'. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off time over, scheduling restart. Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset devices.list: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted] Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/chr Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/blk Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Logs from the host audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" pid=12164 comm="(tor)" Steps to reproduce - install ubuntu container 16.10 on a ubuntu 16.10 host install tor in the container Launch tor ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: tor (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor lxd tor ** Also affects: tor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648143 Title: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1648143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1593293] Re: brd module compiled as built-in
I have the problem too on ubuntu 16.04. To reproduce: sudo lsmod | grep brd : (nothing) : it is builtin sudo modprobe brd rd_size=123456 sudo mkfs.ext4 /dev/ram0 sudo mount /dev/ram0 /var/cache/ramdisk/ df -m | grep ramdisk : /dev/ram0 58 2 53 3% /var/cache/ramdisk -> useless Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593293 Title: brd module compiled as built-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
