[Touch-packages] [Bug 2003790] Re: After successful pairing new bluetooth headphones + mix - sound crash
The following log appears ``` [ 4540.040364] Bluetooth: hci0: Opcode 0x 401 failed: -16 ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2003790 Title: After successful pairing new bluetooth headphones + mix - sound crash Status in pulseaudio package in Ubuntu: Confirmed Bug description: Bluetooth pairing reports established using bluetoothctl, but the sound device is not available on the Ubuntu device(?settings) manager. Only the existing speakers (non buetooth) are showing as sound outputs (sinks). Bluetooth data: beadon@semiauto:~$ bluetoothctl Agent registered [CHG] Controller 28:DF:EB:B6:9B:66 Pairable: yes [Shure TW1]# show Controller 28:DF:EB:B6:9B:66 (public) Name: semiauto Alias: semiauto Class: 0x007c Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0541 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0c (12) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded Headphones: disable bluetooth, enable bluetooth, attempt connection. Bluetooth device is connected to another device (Android phone). Expected behavior is to disconnect the existing connection to the phone and pair only with the laptop. an 24 09:31:07 semiauto systemd[1]: Stopped target Bluetooth Support. Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/sbc_xq Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_1 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_0 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/faststream Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/faststream_duplex Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSink/opus_05 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_51 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_71 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSink/opus_05_duplex Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_duplex Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_pro Jan 24 09:31:07 semiauto systemd[1]: Started Load/Save RF Kill Switch Status. Jan 24 09:31:12 semiauto systemd[1]:
[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
Hello Heinrich, yes, very gladly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) Status in ifupdown package in Ubuntu: Fix Released Bug description: Syslog error: nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir: not found I think it's because of this line: if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface <- this is interpreted as a 'mystatedir' command and fails interface=$IFACE if [ ! "$interface" ]; then Perhaps the intention was to 'export mystatedir statedir ...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
Hi, as of today the fix is not available via apt at Ubuntu jammy x64. Am I doing something wrong? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) Status in ifupdown package in Ubuntu: Fix Released Bug description: Syslog error: nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir: not found I think it's because of this line: if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface <- this is interpreted as a 'mystatedir' command and fails interface=$IFACE if [ ! "$interface" ]; then Perhaps the intention was to 'export mystatedir statedir ...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1900727] [NEW] Update ca-certificates with latest NSS roots
Public bug reported: Please refresh the default ca-certificates package with the latest NSS roots? Specifically, we would like to ensure these two roots from NSS 3.54 (26 June 2020) are included in the package: Bug 1641716 - Microsoft ECC Root Certificate Authority 2017 SHA-256 Fingerprint: 358DF39D764AF9E1B766E9C972DF352EE15CFAC227AF6AD1D70E8E4A6EDCBA02 Bug 1641716 - Microsoft RSA Root Certificate Authority 2017 SHA-256 Fingerprint: C741F70F4B2A8D88BF2E71C14122EF53EF10EBA0CFA5E64CFA20F418853073E0 ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1900727 Title: Update ca-certificates with latest NSS roots Status in ca-certificates package in Ubuntu: New Bug description: Please refresh the default ca-certificates package with the latest NSS roots? Specifically, we would like to ensure these two roots from NSS 3.54 (26 June 2020) are included in the package: Bug 1641716 - Microsoft ECC Root Certificate Authority 2017 SHA-256 Fingerprint: 358DF39D764AF9E1B766E9C972DF352EE15CFAC227AF6AD1D70E8E4A6EDCBA02 Bug 1641716 - Microsoft RSA Root Certificate Authority 2017 SHA-256 Fingerprint: C741F70F4B2A8D88BF2E71C14122EF53EF10EBA0CFA5E64CFA20F418853073E0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1900727/+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 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 Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=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. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+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 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
[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
[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 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
[Touch-packages] [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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=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. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/+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 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=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. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/+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 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=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. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/+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 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 Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Triaged Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1698171] [NEW] package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet openssl n'est pas prêt pour la configuration configuration impossible (état actuel « half-i
Public bug reported: je voudrais installer Minecraft pour y jouer, j'ai été sur un site qui m'a demander de faire un commande sur "Terminal". je l'ai effectuer ( voici le site :https://doc.ubuntu-fr.org/minecraft) j'espère que vous trouverez une solution très rapidement merci. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssl 1.0.2g-1ubuntu4.6 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: minecraft-installer: Install openssl: Configure minecraft-installer: Configure NULL: ConfigurePending Architecture: i386 Date: Thu Jun 15 19:13:14 2017 ErrorMessage: le paquet openssl n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») InstallationDate: Installed on 2017-05-14 (31 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet openssl n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1698171 Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet openssl n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») Status in openssl package in Ubuntu: New Bug description: je voudrais installer Minecraft pour y jouer, j'ai été sur un site qui m'a demander de faire un commande sur "Terminal". je l'ai effectuer ( voici le site :https://doc.ubuntu-fr.org/minecraft) j'espère que vous trouverez une solution très rapidement merci. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssl 1.0.2g-1ubuntu4.6 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: minecraft-installer: Install openssl: Configure minecraft-installer: Configure NULL: ConfigurePending Architecture: i386 Date: Thu Jun 15 19:13:14 2017 ErrorMessage: le paquet openssl n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») InstallationDate: Installed on 2017-05-14 (31 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet openssl n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698171/+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 1682386] Re: systemd-resolved can not resolve .coop domain names
It seems to work again with systemd 232-1ubuntu3 which disable DNSSEC. -- 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/1682386 Title: systemd-resolved can not resolve .coop domain names Status in systemd package in Ubuntu: Confirmed Bug description: I am using Ubuntu Gnome 17.04, systemd version 232-21ubuntu2. I found that .coop domain nomes are not being resolved. If I switch to another DNS server (instead of 127.0.0.53, which is the current default in 17.04), then .coop domains are resolved: $ nslookup > www.somenergia.coop Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find www.somenergia.coop: SERVFAIL > server 8.8.8.8 Default server: 8.8.8.8 Address: 8.8.8.8#53 > www.somenergia.coop Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: www.somenergia.coop Address: 164.132.200.9 > To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682386/+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 1682386] Re: systemd-resolved can not resolve .coop domain names
Same problem after upgrading my two computers from Xubuntu 16.10 and from Kubuntu 16.10 to X/Kubuntu 17.04 today. -- 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/1682386 Title: systemd-resolved can not resolve .coop domain names Status in systemd package in Ubuntu: Confirmed Bug description: I am using Ubuntu Gnome 17.04, systemd version 232-21ubuntu2. I found that .coop domain nomes are not being resolved. If I switch to another DNS server (instead of 127.0.0.53, which is the current default in 17.04), then .coop domains are resolved: $ nslookup > www.somenergia.coop Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find www.somenergia.coop: SERVFAIL > server 8.8.8.8 Default server: 8.8.8.8 Address: 8.8.8.8#53 > www.somenergia.coop Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: www.somenergia.coop Address: 164.132.200.9 > To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682386/+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 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 Touch seeded packages, which is subscribed to python-apt in 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 Status in python-apt package in Ubuntu: Invalid Bug description: clicked 'settings' in software updater (xubuntu) ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: software-properties-gtk 0.91 ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic i686 ApportVersion: 2.4-0ubuntu6 Architecture: i386 Date: Sun Jul 29 10:26:40 2012 ExecutablePath: /usr/bin/software-properties-gtk InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724) InterpreterPath: /usr/bin/python3.2mu PackageArchitecture: all ProcCmdline: /usr/bin/python3.2 /usr/bin/software-properties-gtk --open-tab 2 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2'] SourcePackage: software-properties Title: software-properties-gtk crashed with UnicodeDecodeError in record(): 'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1030471/+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 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
Touch seeded packages, which is subscribed to python-apt in 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
Status in python-apt package in Ubuntu:
Confirmed
Bug description:
clicked 'settings' in software updater (xubuntu)
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: software-properties-gtk 0.91
ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
Uname: Linux 3.5.0-6-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
Date: Sun Jul 29 10:26:40 2012
ExecutablePath: /usr/bin/software-properties-gtk
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724)
InterpreterPath: /usr/bin/python3.2mu
PackageArchitecture: all
ProcCmdline: /usr/bin/python3.2 /usr/bin/software-properties-gtk --open-tab 2
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2']
SourcePackage: software-properties
Title: software-properties-gtk crashed with UnicodeDecodeError in record():
'utf-8' codec can't decode byte 0x92 in position 1017: invalid start byte
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1030471/+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 1633845] Re: network-manager does not connect to wifi
*** This bug is a duplicate of bug 1642507 *** https://bugs.launchpad.net/bugs/1642507 ** This bug has been marked a duplicate of bug 1642507 Not internet after waking from suspend -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1633845 Title: network-manager does not connect to wifi Status in network-manager package in Ubuntu: Confirmed Bug description: When trying to connect to wifi network, network-manager remains blocked in waiting for authentification state then fails after cca 1min. This started to happen after I updated to kubuntu 16.10. Stopping network manager from service and trying to manually connect with wpa_supplicant works fine. The only way to fix this for me was to stop network manager and/or networking and restart the services sometimes more than once. os: Kubuntu 16.10 network-manager: 1.2.4 hardware: dell xps 9550 network controller: BCM43602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845/+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 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 Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1648143 Title: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor" Status in apparmor package in Ubuntu: New Status in tor package in Ubuntu: New Bug description: 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
[Touch-packages] [Bug 1642507] Re: Not internet after waking from suspend
The issue was already submitted in #1633845 Maybe we should merge the two issues to give it more visibility ? https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1642507 Title: Not internet after waking from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Release Information: Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety Package Information: network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status System Information: Dell XPS 15 9550 Wireless: Network controller: Broad com Limited BCM43602 802.11ac Wireless LAN SoC (rev 01) Wired: Wired Ethernet via Apple USB Ethernet Adapter (ID 05ac:1402 Apple, Inc. Ethernet Adapter [A1277]) Problem Description: I have noticed the problem on both wired and wireless. Ever since upgrading to 16.10(from 16.04), the system loses internet after waking from suspend. Internet works fine after a reboot or when powering on normally. "service network-manager restart" fixes the problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 17 09:37:30 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-31 (169 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.80.1 dev enx7cc3a187f0f2 proto static metric 100 default via 192.168.80.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.80.0/24 dev enx7cc3a187f0f2 proto kernel scope link src 192.168.80.209 metric 100 192.168.80.0/24 dev wlp2s0 proto kernel scope link src 192.168.80.225 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-28 (19 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enx7cc3a187f0f2 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 e6493319-b925-3b33-92a7-259922dccdaa /org/freedesktop/NetworkManager/ActiveConnection/1 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 whymusticry_fast 1 b51f9098-d053-45d7-ba42-97bf2e87bda2 /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1642507/+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 1633845] Re: network-manager does not connect to wifi
Same issue on ubuntu-gnome 16.10 after resuming from sleep. Network controller: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC (rev 01) Hardware: Dell XPS 9550 It is required to restart the network manager. There was the same issue in Ubuntu 16.04 6/7 months ago and it was fixed in an update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1633845 Title: network-manager does not connect to wifi Status in network-manager package in Ubuntu: Confirmed Bug description: When trying to connect to wifi network, network-manager remains blocked in waiting for authentification state then fails after cca 1min. This started to happen after I updated to kubuntu 16.10. Stopping network manager from service and trying to manually connect with wpa_supplicant works fine. The only way to fix this for me was to stop network manager and/or networking and restart the services sometimes more than once. os: Kubuntu 16.10 network-manager: 1.2.4 hardware: dell xps 9550 network controller: BCM43602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845/+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 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial
This issue happens to us because libvirt is being used inside a Docker
container which share systemd with the host. Therefore, neither of these
units exist on the host and as mentioned above, when a non-existing unit
is specified in the `After` clause - listed first - the `Before` clause
makes systemd fail.
--
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/1529079
Title:
Can't start virtual machines with installed systemd-container package
on Xenial
Status in libvirt package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
Can't start virtual machines after upgrade to Xenial.
On Ubuntu Server 16.04:
# virsh start testserver
Cannot set property Before, or unknown property.
On Kubuntu 16.04:
Cannot set property Before, or unknown property.
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in
do_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: Cannot set property Before, or unknown property.
At this moment there is no libvirt or systemd-related error messages in
syslog when this error appear on the screen (or virsh output). Both systems was
upgraded from 15.10.
---
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: libvirt (not installed)
ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial
quiet nomdmonddf nomdmonisw
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
Tags: xenial
Uname: Linux 4.3.3-040303-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.libvirt.qemu.networks.default.xml:
2015-02-27T11:49:59.773560
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial
Just created an issue on libvirt's upstream bug tracker:
https://bugzilla.redhat.com/show_bug.cgi?id=1350909
** Bug watch added: Red Hat Bugzilla #1350909
https://bugzilla.redhat.com/show_bug.cgi?id=1350909
--
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/1529079
Title:
Can't start virtual machines with installed systemd-container package
on Xenial
Status in libvirt package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
Can't start virtual machines after upgrade to Xenial.
On Ubuntu Server 16.04:
# virsh start testserver
Cannot set property Before, or unknown property.
On Kubuntu 16.04:
Cannot set property Before, or unknown property.
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in
do_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: Cannot set property Before, or unknown property.
At this moment there is no libvirt or systemd-related error messages in
syslog when this error appear on the screen (or virsh output). Both systems was
upgraded from 15.10.
---
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: libvirt (not installed)
ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial
quiet nomdmonddf nomdmonisw
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
Tags: xenial
Uname: Linux 4.3.3-040303-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.libvirt.qemu.networks.default.xml:
2015-02-27T11:49:59.773560
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial
We do experience that issue too on CoreOS. Until CoreOS 1010, it worked
just fine (systemd v225), and afterwards (systemd v229), the issue is
present.
The libvirt code mentioned above did not change since 2014. Therefore,
it seems that a change to systemd between 225 and 229 generates that
issue.
Not sure of the importance of that `Before` close there yet. I need to
document myself more. We could try without it and see how it goes.
--
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/1529079
Title:
Can't start virtual machines with installed systemd-container package
on Xenial
Status in libvirt package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
Can't start virtual machines after upgrade to Xenial.
On Ubuntu Server 16.04:
# virsh start testserver
Cannot set property Before, or unknown property.
On Kubuntu 16.04:
Cannot set property Before, or unknown property.
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in
do_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: Cannot set property Before, or unknown property.
At this moment there is no libvirt or systemd-related error messages in
syslog when this error appear on the screen (or virsh output). Both systems was
upgraded from 15.10.
---
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: libvirt (not installed)
ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial
quiet nomdmonddf nomdmonisw
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
Tags: xenial
Uname: Linux 4.3.3-040303-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.libvirt.qemu.networks.default.xml:
2015-02-27T11:49:59.773560
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial
I do experience it too in CoreOS+CentOS (docker).
Question is why is it a problem now?
These lines have been present there since 2014.
--
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/1529079
Title:
Can't start virtual machines with installed systemd-container package
on Xenial
Status in libvirt package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
Can't start virtual machines after upgrade to Xenial.
On Ubuntu Server 16.04:
# virsh start testserver
Cannot set property Before, or unknown property.
On Kubuntu 16.04:
Cannot set property Before, or unknown property.
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in
do_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in
createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: Cannot set property Before, or unknown property.
At this moment there is no libvirt or systemd-related error messages in
syslog when this error appear on the screen (or virsh output). Both systems was
upgraded from 15.10.
---
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 16.04
Package: libvirt (not installed)
ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial
quiet nomdmonddf nomdmonisw
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
Tags: xenial
Uname: Linux 4.3.3-040303-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.libvirt.qemu.networks.default.xml:
2015-02-27T11:49:59.773560
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1571454] Re: Wifi + cable only works after network-manager restart
I have the same issue, but I can also add that my wifi is being seen as a wired connexion. A service restart makes it work perfectly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1571454 Title: Wifi + cable only works after network-manager restart Status in network-manager package in Ubuntu: Confirmed Bug description: Wifi and cable only get activated after i sudo service network-manager restart, before wifi and cable are greyed out Ubuntu 16.04 daily with all recent updates on 18/4/2016 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 18 04:35:49 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-04 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 192.168.1.1 dev wlp7s0 proto static metric 600 169.254.0.0/16 dev wlp7s0 scope link metric 1000 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH belkin7 67e4a5b3-4e8e-4428-bc43-c25952f33558 802-11-wireless 1460946871 ma 18 apr 2016 04:34:31 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/0 yes wlp7s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 Wired connection 1 bab26653-acb8-45fe-8b43-c5fe98488989 802-3-ethernet 1460946867 ma 18 apr 2016 04:34:27 CEST yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp7s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 belkin7 67e4a5b3-4e8e-4428-bc43-c25952f33558 /org/freedesktop/NetworkManager/ActiveConnection/0 enp6s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1571454/+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 1467347] [NEW] Whitespace is trimmed.. WHY?
Public bug reported: When sending a text message, and after carefully spacing things for example to make an ascii art picture. The spacing is removed and it messes up the text, I do not understand why this is done at all. Example: (-,-) --(__:__)-- (___) I made this snowman© and I used to send it to people on my old phone, now this is impossible to do as the whitespace is removed. Another Example: Here is some text I want this text to be in a new paragraph Then some more text In this example there is no way to produce the blank lines in the text. Please fix! ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Description changed: When sending a text message, and after carefully spacing things for example to make an ascii art picture. The spacing is removed and it messes up the text, I do not understand why this is done at all. Example: + + (-,-) + --( : )-- +( ) + -(-,-) - --( : )-- - ( ) - - - I made this snowman© and I used to send it to people on my old phone, + I made this snowman© and I used to send it to people on my old phone, now this is impossible to do as the whitespace is removed. Another Example: -Here is some text + Here is some text -I want this text to be in a new paragraph + I want this text to be in a new paragraph -Then some more text + Then some more text In this example there is no way to produce the blank lines in the text. Please fix! ** Description changed: When sending a text message, and after carefully spacing things for example to make an ascii art picture. The spacing is removed and it messes up the text, I do not understand why this is done at all. Example: - - (-,-) - --( : )-- -( ) - + + (-,-) + --( : )-- + (___) I made this snowman© and I used to send it to people on my old phone, now this is impossible to do as the whitespace is removed. Another Example: Here is some text I want this text to be in a new paragraph Then some more text In this example there is no way to produce the blank lines in the text. Please fix! ** Description changed: When sending a text message, and after carefully spacing things for example to make an ascii art picture. The spacing is removed and it messes up the text, I do not understand why this is done at all. Example: (-,-) - --( : )-- + --(__:__)-- (___) I made this snowman© and I used to send it to people on my old phone, now this is impossible to do as the whitespace is removed. Another Example: Here is some text I want this text to be in a new paragraph Then some more text In this example there is no way to produce the blank lines in the text. Please fix! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1467347 Title: Whitespace is trimmed.. WHY? Status in messaging-app package in Ubuntu: New Bug description: When sending a text message, and after carefully spacing things for example to make an ascii art picture. The spacing is removed and it messes up the text, I do not understand why this is done at all. Example: (-,-) --(__:__)-- (___) I made this snowman© and I used to send it to people on my old phone, now this is impossible to do as the whitespace is removed. Another Example: Here is some text I want this text to be in a new paragraph Then some more text In this example there is no way to produce the blank lines in the text. Please fix! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1467347/+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 1443051] Re: Some texts deliver a blank message
Alright I have done some testing and I can't paste in the web browser with the phone (different bug -_- lol) But if I send a message with about 78 emojis in it, the text is received blank message I realise this is an extreme case and I have an example of an everyday text that I sent twice that delivered blank but I can't paste it from my phone atm. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1443051 Title: Some texts deliver a blank message Status in messaging-app package in Ubuntu: Incomplete Bug description: When I send a text message to someone sometimes they receive a blank text. This has happened on two occasions, first when the text was rather long, after I split it into two texts it delivered fine. And another time which I sent a few times which became blank on the receiving phone I removed the emoji character and then the text went through fine, the receiving person has an Iphone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1443051/+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 1443051] Re: Some texts deliver a blank message
I enter the emoji character with the emoji keyboard and it does not appear to be specific emoji. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1443051 Title: Some texts deliver a blank message Status in messaging-app package in Ubuntu: Incomplete Bug description: When I send a text message to someone sometimes they receive a blank text. This has happened on two occasions, first when the text was rather long, after I split it into two texts it delivered fine. And another time which I sent a few times which became blank on the receiving phone I removed the emoji character and then the text went through fine, the receiving person has an Iphone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1443051/+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 1443051] Re: Some texts deliver a blank message
It seems to happen at random, I have noticed it more but only when emoji are sent in medium-long messages, this wouldn't be by any chance the emoji being split in text messages? I will try and find some more examples of these messages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1443051 Title: Some texts deliver a blank message Status in messaging-app package in Ubuntu: Incomplete Bug description: When I send a text message to someone sometimes they receive a blank text. This has happened on two occasions, first when the text was rather long, after I split it into two texts it delivered fine. And another time which I sent a few times which became blank on the receiving phone I removed the emoji character and then the text went through fine, the receiving person has an Iphone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1443051/+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 1443051] [NEW] Some texts deliver a blank message
Public bug reported: When I send a text message to someone sometimes they receive a blank text. This has happened on two occasions, first when the text was rather long, after I split it into two texts it delivered fine. And another time which I sent a few times which became blank on the receiving phone I removed the emoji character and then the text went through fine, the receiving person has an Iphone. ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1443051 Title: Some texts deliver a blank message Status in messaging-app package in Ubuntu: New Bug description: When I send a text message to someone sometimes they receive a blank text. This has happened on two occasions, first when the text was rather long, after I split it into two texts it delivered fine. And another time which I sent a few times which became blank on the receiving phone I removed the emoji character and then the text went through fine, the receiving person has an Iphone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1443051/+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 1442582] Re: Wait for reception to send texts, don't fail straight away!
*** This bug is a duplicate of bug 1424625 *** https://bugs.launchpad.net/bugs/1424625 ** This bug has been marked a duplicate of bug 1424625 Cannot send SMS message when there is no network. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1442582 Title: Wait for reception to send texts, don't fail straight away! Status in messaging-app package in Ubuntu: New Bug description: when I send a text and I don't have reception at the time, I don't want to wait around for reception before I manually resend it, I want the message to send automatically when I get reception. Id like to prepare a text and send it and let the phone manage that, this is a requisite of a smart-phone my phone knows I'm trying to send a text and should try and send the text when it can. Having to manually resend the text is not very smart Thanks, I'm reporting this bug on my BQ Aquarius! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1442582/+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 1424625] Re: Cannot send SMS message when there is no network.
Affects me too, just want to refer to this bug as my opinion on this issue: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1442582 when I send a text and I don't have reception at the time, I don't want to wait around for reception before I manually resend it, I want the message to send automatically when I get reception. Id like to prepare a text and send it and let the phone manage that, this is a requisite of a smart-phone my phone knows I'm trying to send a text and should try and send the text when it can. Having to manually resend the text is not very smart -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1424625 Title: Cannot send SMS message when there is no network. Status in messaging-app package in Ubuntu: Confirmed Bug description: I am unable to send a SMS message when there is no network (no coverage). I think that the System should save the message and automatically send the SMS when the telephone will find the coverage. It's very frustrating because to send a SMS in poorly coveraged area I have to wait a few minutes and try sending the message. Device: MAKO, OS build number: 15, Ubuntu Image part: 20150129, Device Image part: 20150116 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1424625/+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
