[Touch-packages] [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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1774768 Title: systemd-udevd eats cpu in infinite loop when nvidia card is not plugged Status in systemd package in Ubuntu: New Bug description: 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 infini
[Touch-packages] [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:
[Touch-packages] [Bug 1774717] Re: Saying goodbye to search.cpan.org
Here is a relevant thread on debian-perl: https://lists.debian.org /debian-perl/2018/05/msg00046.html In short: yes, but there is no urgency. I don't think a bug on perl in ubuntu is needed to track this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1774717 Title: Saying goodbye to search.cpan.org Status in perl package in Ubuntu: New Bug description: search.cpan.org is being retired and will transparently redirect to the new https://metacpan.org/ replacement site. Are there any plans to update the URLs like FreeBSD did? https://svnweb.freebsd.org/ports?view=revision&revision=470993 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1774717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 dmi.product.ver
[Touch-packages] [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 (201
[Touch-packages] [Bug 1774136] Re: apport mistakenly duplicates bugs with similar but not identical python stacktraces
** Tags added: id-5b115fda12527f1175ac133e -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1774136 Title: apport mistakenly duplicates bugs with similar but not identical python stacktraces Status in apport package in Ubuntu: New Bug description: apport duplicates bug 1774131 and bug 1269397 with similar but different python stack traces. bug 1269397 update-manager crashed with AttributeError in resize_to_standard_width(): 'NoneType' object has no attribute 'get_resolution' bug 1774131 update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed' The following bucket also collect both traces based only on the first part of the trace: update-manager (AttributeError) → resize_to_standard_width https://errors.ubuntu.com/problem/76971c92f002117650d5630a6b13a8ba683e2343 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 09:34:27 2018 InstallationDate: Installed on 2014-07-15 (1414 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to cosmic on 2018-03-24 (66 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774782] [NEW] Horizontal stripes flickering
Public bug reported: I've go horizontal stripes flickering on my laptop screen. It's really annoying and I couldn't concentrate on my work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 2 15:44:32 2018 DistUpgraded: 2018-06-02 14:32:32,469 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d] InstallationDate: Installed on 2016-04-20 (773 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 20354 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=14857e5e-1fd5-4571-b7e9-c3394bee4e34 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-06-02 (0 days ago) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jun 2 12:35:03 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5579 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1774782 Title: Horizontal stripes flickering Status in xorg package in Ubuntu: New Bug description: I've go horizontal stripes flickering on my laptop screen. It's really annoying and I couldn't concentrate on my work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 2 15:44:32 2018 DistUpgraded: 2018-06-02 14:32:32,469 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d] InstallationDate: Installed on 2016-04-20 (773 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 20354 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=14857e5e-1fd5-4571-b7e9-c3394bee4e34 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-06-02 (0 days ago) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 319
[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)
# LANG=C apt-cache policy libnvidia-gl-390 libnvidia-gl-390: Installed: 390.48-0ubuntu3 Candidate: 390.48-0ubuntu3 Version table: *** 390.48-0ubuntu3 500 500 http://hu.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages 100 /var/lib/dpkg/status # LANG=C dpkg -l libnvidia-gl-390 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===--- ii libnvidia-gl-390:amd64 390.48-0ubuntu3 amd64 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD) Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: After upgrading to Ubuntu 18.04, my desktop uses software rendering, no matter what I do. As far as I know, all necessary packages are installed. Formerly I had oibaf installed, but suspecting that this may cause the problem, I removed it with ppa-purge. It didn't help. First I noticed the problem when I tried to play HD videos. It was fine before the upgrade. My hardware is capable for 3D acceleration, as it worked on 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 13 06:13:09 2018 DistUpgraded: 2018-05-12 22:26:52,663 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2014-06-10 (1432 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@ Renderer: Software SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 6474B84 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun May 13 06:01:23 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1770913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774788] [NEW] Daemon won't start at boot up (18LTS fully patched)
Public bug reported: By adding the 'address=' option to the /etc/rsyncd.conf file, the daemon fails at boot. Once the NIC(s) is/are up, it will start fine when executed via systemctl start rsync ● rsync.service - fast remote file copy program daemon Loaded: loaded (/lib/systemd/system/rsync.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10) Main PID: 851 (code=exited, status=10) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873 Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873 Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 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: GNOME Date: Sat Jun 2 08:48:15 2018 InstallationDate: Installed on 2018-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1774788 Title: Daemon won't start at boot up (18LTS fully patched) Status in rsync package in Ubuntu: New Bug description: By adding the 'address=' option to the /etc/rsyncd.conf file, the daemon fails at boot. Once the NIC(s) is/are up, it will start fine when executed via systemctl start rsync ● rsync.service - fast remote file copy program daemon Loaded: loaded (/lib/systemd/system/rsync.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10) Main PID: 851 (code=exited, status=10) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873 Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873 Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 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: GNOME Date: Sat Jun 2 08:48:15 2018 InstallationDate: Installed on 2018-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1774788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
Still not solved, even after the official release of Ubuntu 18.04 LTS? I was using Slimjet as my browser, and now I cannot anymore because of its dependency to libcurl3... and I cannot just replace libcurl4 by libcurl3 because many other applications depend on libcurl4. What can I do?! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
On my system, the Slimjet browser is broken by this mess. It is non- functional after the update to libcurl4 and it cannot be re-installed successfully. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774831] [NEW] package systemd 237-3ubuntu10 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: I tried to install a package (libboost-all-dev) and this error message was in my terminal, after a while a report problem popup box popped up on my screen and i want to fix this issue that is why i reported the error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 2 23:57:29 2018 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP EliteBook 8460p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2dbe94c9-bbad-4c6a-b67e-5b4c0eb387b0 ro quiet splash Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 237-3ubuntu10 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag: CNU2241WLL dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1774831 Title: package systemd 237-3ubuntu10 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in systemd package in Ubuntu: New Bug description: I tried to install a package (libboost-all-dev) and this error message was in my terminal, after a while a report problem popup box popped up on my screen and i want to fix this issue that is why i reported the error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 2 23:57:29 2018 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP EliteBook 8460p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2dbe94c9-bbad-4c6a-b67e-5b4c0eb387b0 ro quiet splash Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 237-3ubuntu10 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag: CNU2241WLL dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ub
[Touch-packages] [Bug 1774837] [NEW] package systemd 237-3ubuntu10 failed to install/upgrade: problemas de dependencias - no se procesarán los disparadores
Public bug reported: i want to insatll open cv for python in root mode ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sat Jun 2 21:50:53 2018 ErrorMessage: problemas de dependencias - no se procesarán los disparadores MachineType: LENOVO 80TQ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=a7b8ef33-d969-4dd5-8a4c-efd90f94afd3 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 237-3ubuntu10 failed to install/upgrade: problemas de dependencias - no se procesarán los disparadores UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN18WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 4B1 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-14AST dmi.modalias: dmi:bvnLENOVO:bvr3UCN18WW:bd11/01/2016:svnLENOVO:pn80TQ:pvrLenovoideapad110-14AST:rvnLENOVO:rnNano4B1:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-14AST: dmi.product.family: IDEAPAD dmi.product.name: 80TQ dmi.product.version: Lenovo ideapad 110-14AST dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1774837 Title: package systemd 237-3ubuntu10 failed to install/upgrade: problemas de dependencias - no se procesarán los disparadores Status in systemd package in Ubuntu: New Bug description: i want to insatll open cv for python in root mode ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sat Jun 2 21:50:53 2018 ErrorMessage: problemas de dependencias - no se procesarán los disparadores MachineType: LENOVO 80TQ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=a7b8ef33-d969-4dd5-8a4c-efd90f94afd3 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 237-3ubuntu10 failed to install/upgrade: problemas de dependencias - no se procesarán los disparadores UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN18WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 4B1 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-14AST dmi.modalias: dmi:bvnLENOVO:bvr3UCN18WW:bd11/01/2016:svnLENOVO:pn80TQ:pvrLenovoideapad110-14AST:rvnLENOVO:rnNano4B1:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-14AST: dmi.product.family: IDEAPAD dmi.product.name: 80TQ dmi.product.version: Lenovo ideapad 110-14AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
3597 lines here on ubuntu 18.04 upgraded from 16.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736072] Re: Encrypted swap does not work
[Expired for cryptsetup (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cryptsetup (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1736072 Title: Encrypted swap does not work Status in cryptsetup package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Status in ubiquity package in Ubuntu: Expired Bug description: On a working system, i've added a new hdd, and decided to use it as the main device storage. So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've set a bionic iso installation. Ubiquity then have proposed to set an encrypted swap dir, which i have accepted, and then smootly terminated the installation. Booting with that new install, i hit a cryptswap1 timeout after beeing frozen around 1 minute. oem@ubuntu:~$ journalctl | grep cryptswap systemd[1]: Starting Cryptography Setup for cryptswap2... systemd[1]: Started Cryptography Setup for cryptswap2. systemd[1]: Found device /dev/mapper/cryptswap2. systemd[1]: Activating swap /dev/mapper/cryptswap2... kernel: Adding 10584572k swap on /dev/mapper/cryptswap2. Priority:-1 extents:1 across:10584572k FS systemd[1]: Activated swap /dev/mapper/cryptswap2. systemd[1]: Starting Cryptography Setup for cryptswap1... systemd[1]: Started Cryptography Setup for cryptswap1. oem@ubuntu:~$ journalctl | grep timeout systemd[1]: dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device: Job dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device/start failed with result 'timeout'. Note: cryptswap2 refer to the new hdd's swap partition, cryptswap1 refer to the old hdd's swap partition. /etc/fstab have been tested with only the active (mounted) disk, and with both. In both cases the timeout happens. oem@ubuntu:~$ swapon -s Filename TypeSizeUsedPriority /dev/dm-0 partition 10584572 221184 -1 Conclusion: -ubiquity is proposing a non working feature (at least with multiple storage devices/swap partitions - the cryptsetup version is not well supporting the kernel/systemd settings/configs As Debian has more recent versions: 1.7.5-1 (sid) and 2.0.0 (experimental) with some new features and cleanups, it should be a positive test to replace the actual not working version with one of these. http://metadata.ftp-master.debian.org/changelogs/main/c/cryptsetup/cryptsetup_2.0.0~rc1-1_changelog ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cryptsetup 2:1.7.3-4ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 4 07:26:17 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1736072/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759329] Re: bionic netboot installer fails with local repository
[Expired for console-setup (Ubuntu) because there has been no activity for 60 days.] ** Changed in: console-setup (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1759329 Title: bionic netboot installer fails with local repository Status in console-setup package in Ubuntu: Expired Bug description: preseed file with local repositoryw fails when package from repo is trying to be installed. Bionic preseed file with: d-i apt-setup/local0/repository string deb http://example.com/PatchSet/latest/willu bionic main d-i apt-setup/local0/comment string This is the stuff d-i apt-setup/local0/key string http://dists.example.com/PatchSet/latest/f5-ubuntu/willu.pubkey This paragraph works in Precise, Trusty, and Xenial. Watching /target/etc/apt/source.lists, I see it's created correctly, then at some point after the base install, the file gets overwritten and the entry for the local repo(s) are commented out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1759329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717015 Title: libc resolver stops searching domain search list after getting back NSEC record Status in systemd package in Ubuntu: Expired Bug description: Suppose that: 1. you have a "search" line in your /etc/resolv.conf file; 2. it has two domains in it; and 3. the first of the two domains does DNSSEC, including returning NSEC records for nonexisting hosts. In this situation, when you try to look up a host name in the second domain without specifying the domain part of the host name, the libc resolver will stop after it gets back the NSEC record and report that the host name doesn't exist, rather than moving on to the second domain in the search list and searching for the host in that domain. See also https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1717014 . ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libc6 2.24-9ubuntu2.2 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Sep 13 16:00:45 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 InstallationDate: Installed on 2016-08-09 (400 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: glibc UpgradeStatus: Upgraded to zesty on 2017-04-19 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736072] Re: Encrypted swap does not work
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1736072 Title: Encrypted swap does not work Status in cryptsetup package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Status in ubiquity package in Ubuntu: Expired Bug description: On a working system, i've added a new hdd, and decided to use it as the main device storage. So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've set a bionic iso installation. Ubiquity then have proposed to set an encrypted swap dir, which i have accepted, and then smootly terminated the installation. Booting with that new install, i hit a cryptswap1 timeout after beeing frozen around 1 minute. oem@ubuntu:~$ journalctl | grep cryptswap systemd[1]: Starting Cryptography Setup for cryptswap2... systemd[1]: Started Cryptography Setup for cryptswap2. systemd[1]: Found device /dev/mapper/cryptswap2. systemd[1]: Activating swap /dev/mapper/cryptswap2... kernel: Adding 10584572k swap on /dev/mapper/cryptswap2. Priority:-1 extents:1 across:10584572k FS systemd[1]: Activated swap /dev/mapper/cryptswap2. systemd[1]: Starting Cryptography Setup for cryptswap1... systemd[1]: Started Cryptography Setup for cryptswap1. oem@ubuntu:~$ journalctl | grep timeout systemd[1]: dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device: Job dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device/start failed with result 'timeout'. Note: cryptswap2 refer to the new hdd's swap partition, cryptswap1 refer to the old hdd's swap partition. /etc/fstab have been tested with only the active (mounted) disk, and with both. In both cases the timeout happens. oem@ubuntu:~$ swapon -s Filename TypeSizeUsedPriority /dev/dm-0 partition 10584572 221184 -1 Conclusion: -ubiquity is proposing a non working feature (at least with multiple storage devices/swap partitions - the cryptsetup version is not well supporting the kernel/systemd settings/configs As Debian has more recent versions: 1.7.5-1 (sid) and 2.0.0 (experimental) with some new features and cleanups, it should be a positive test to replace the actual not working version with one of these. http://metadata.ftp-master.debian.org/changelogs/main/c/cryptsetup/cryptsetup_2.0.0~rc1-1_changelog ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cryptsetup 2:1.7.3-4ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 4 07:26:17 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1736072/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736072] Re: Encrypted swap does not work
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1736072 Title: Encrypted swap does not work Status in cryptsetup package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Status in ubiquity package in Ubuntu: Expired Bug description: On a working system, i've added a new hdd, and decided to use it as the main device storage. So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've set a bionic iso installation. Ubiquity then have proposed to set an encrypted swap dir, which i have accepted, and then smootly terminated the installation. Booting with that new install, i hit a cryptswap1 timeout after beeing frozen around 1 minute. oem@ubuntu:~$ journalctl | grep cryptswap systemd[1]: Starting Cryptography Setup for cryptswap2... systemd[1]: Started Cryptography Setup for cryptswap2. systemd[1]: Found device /dev/mapper/cryptswap2. systemd[1]: Activating swap /dev/mapper/cryptswap2... kernel: Adding 10584572k swap on /dev/mapper/cryptswap2. Priority:-1 extents:1 across:10584572k FS systemd[1]: Activated swap /dev/mapper/cryptswap2. systemd[1]: Starting Cryptography Setup for cryptswap1... systemd[1]: Started Cryptography Setup for cryptswap1. oem@ubuntu:~$ journalctl | grep timeout systemd[1]: dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device: Job dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device/start failed with result 'timeout'. Note: cryptswap2 refer to the new hdd's swap partition, cryptswap1 refer to the old hdd's swap partition. /etc/fstab have been tested with only the active (mounted) disk, and with both. In both cases the timeout happens. oem@ubuntu:~$ swapon -s Filename TypeSizeUsedPriority /dev/dm-0 partition 10584572 221184 -1 Conclusion: -ubiquity is proposing a non working feature (at least with multiple storage devices/swap partitions - the cryptsetup version is not well supporting the kernel/systemd settings/configs As Debian has more recent versions: 1.7.5-1 (sid) and 2.0.0 (experimental) with some new features and cleanups, it should be a positive test to replace the actual not working version with one of these. http://metadata.ftp-master.debian.org/changelogs/main/c/cryptsetup/cryptsetup_2.0.0~rc1-1_changelog ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cryptsetup 2:1.7.3-4ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 4 07:26:17 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1736072/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
I have the same problem with a Logitech M337 mouse and the 4.15.0-22-lowlatency kernel on my Dell Inspiron 15 laptop. I also with a different Logitech M337 on the 4.4.15.0-22-generic kernel on an Asus Transformer T300 Chi. Its bluetooth docking station reports zero battery, too. All three bluetooth devices reported credible power levels under their 17.10 systems they were running before upgrading to bionic. Is it a coincidence the two machines have Intel wifi/bluetooth adapters which use iwlwifi-7265D-29.ucode? I can run apport from these two machines if that would be helpful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
