[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
** Summary changed: - [regression] Bluetooth 3.0 mouses are automatically disconnected after connected + [regression] Logitech M337 mice are automatically disconnected after connected -- 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/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: New Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+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 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
I wonder if there is any relation to bug 1773897 here... ** Summary changed: - Mouse only pairs successfully after 4-5 tries + Logitech M535 mouse only pairs successfully after 4-5 tries -- 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/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: New Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 15 07:46:38 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 12-9Q33 ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:51:4F:1D:50:3C ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:16702 acl:290 sco:0 events:716 errors:0 TX bytes:44162 acl:142 sco:0 commands:427 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : ht
[Touch-packages] [Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
What Ubuntu version did you upgrade from? -- 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/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: New Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 15 07:46:38 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 12-9Q33 ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:51:4F:1D:50:3C ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:16702 acl:290 sco:0 events:716 errors:0 TX bytes:44162 acl:142 sco:0 commands:427 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777062/+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 1771962] Re: hanging at boot for about 30 seconds since upgrade to bionic
I have run through the test case as described and confirmed that the updated initramfs-tools in bionic-proposed eliminates this 30-second wait in the initramfs. In my test VM, the rootfs is now mounted at 6.8s (and the swap is activated at 13.0s). ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1771962 Title: hanging at boot for about 30 seconds since upgrade to bionic Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, even if the swap device is ephemeral (i.e. swap encrypted with a random key). This adds an inappropriate 30-second boot delay to any system with randomly-crypted swap, which includes any system that was installed with encrypted home directories in earlier releases. [Test case] 1. Install the ecryptfs-utils package. 2. Enable encrypted swap by running 'sudo ecryptfs-setup-swap'. 3. Run 'update-initramfs -u' to regenerate the initramfs. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] Since upgrade to Bionic ubuntu is hanging at boot for about 30s. A `dmesg` shows ``` [3.407230] clocksource: Switched to clocksource tsc [ 34.632583] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) ``` This is 100% reproducable and is always 30s minimum. I do not know in which package to report this properly – please excuse me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: i3 Date: Fri May 18 09:40:59 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-03 (1444 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1771962/+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 1777062] [NEW] Mouse only pairs successfully after 4-5 tries
Public bug reported: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 15 07:46:38 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 12-9Q33 ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 5C:51:4F:1D:50:3C ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:16702 acl:290 sco:0 events:716 errors:0 TX bytes:44162 acl:142 sco:0 commands:427 errors:0 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1777062 Title: Mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: New Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connect
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Changed in: ubiquity (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: In Progress Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Merge proposal linked: https://code.launchpad.net/~vorlon/ubiquity/+git/ubiquity/+merge/348033 ** Merge proposal linked: https://code.launchpad.net/~vorlon/ubiquity/+git/ubiquity/+merge/348034 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: In Progress Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Description changed: + [SRU Justification] + A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. + + [Test case] + 1. Install using the "Use LVM" option in the desktop installer. + 4. Reboot. + 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. + 6. Install initramfs-tools from bionic-proposed. + 7. Reboot. + 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. + 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. + 10. Reboot. + 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. + + [Regression potential] + This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. + + [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected + - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected + - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected + - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: Triaged Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
Launchpad has imported 2 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=106834. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-06-06T07:24:02+00:00 tom wrote: Been this way since at least Ubuntu 15. Plug in your headphones, boot up your laptop. No sound. Speakers and headphones are disabled. Super annoying, you have to unplug and re-plug, and go through the stupid dialogue of "what are you trying to plug in?" which has no memory, and no defaults. Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1583801/comments/33 On 2018-06-14T15:14:39+00:00 Tanu Kaskinen wrote: The "what are you trying to plug in" dialog is Ubuntu specific, it's not implemented by PulseAudio itself. If you want your last choice to be remembered, you'll need to talk to the Ubuntu UI people. Maybe there's something in PulseAudio that could be improved regarding the default behaviour. Can you attach the output of "pactl list" after boot, when you have no audio? Please use the "Add an attachment" link (sometimes people paste long texts to the comment box, which makes following the discussion difficult). Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1583801/comments/37 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => In Progress ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: Triaged Bug description: After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Two bugs: - ubiquity creates an /etc/initramfs-tools/conf.d/resume which lists the swap device by UUID; this is not the correct way to reference a device that's on LVM, and with the current lvm initramfs hooks it fails because it won't be found to be activated. - if /etc/initramfs-tools/conf.d/resume is absent, initramfs-tools itself auto-creates a file on update-initramfs -u that references the uuid. We need to fix both. I'm not sure if we should add some upgrade handling to detect broken /etc/initramfs-tools/conf.d/resume for this case and remove it on upgrade. ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: ubiquity (Ubuntu) Importance: Undecided => High ** Changed in: ubiquity (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: Triaged Bug description: After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1777045] [NEW] Initrd doesn't have proper compress format
Public bug reported: It is very similar to the bug https://bugs.launchpad.net/ubuntu/+source /initramfs-tools/+bug/1462788 reported about 3 years ago. I'm using an up-to-date Xubuntu 18. The system is still bootable. But I couldn't extract initramfs: root@Chrom-agent:/tmp# file /boot/initrd.img-4.15.0-22-generic /boot/initrd.img-4.15.0-22-generic: ASCII cpio archive (SVR4 with no CRC) After removed /usr/share/initramfs-tools/hooks/intel_microcode and regenerated initramfs, the initrd could be recognized by compress utility. Ubuntu 18.04 LTS initramfs-tools 0.130ubuntu3 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1777045 Title: Initrd doesn't have proper compress format Status in initramfs-tools package in Ubuntu: New Bug description: It is very similar to the bug https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1462788 reported about 3 years ago. I'm using an up-to-date Xubuntu 18. The system is still bootable. But I couldn't extract initramfs: root@Chrom-agent:/tmp# file /boot/initrd.img-4.15.0-22-generic /boot/initrd.img-4.15.0-22-generic: ASCII cpio archive (SVR4 with no CRC) After removed /usr/share/initramfs-tools/hooks/intel_microcode and regenerated initramfs, the initrd could be recognized by compress utility. Ubuntu 18.04 LTS initramfs-tools 0.130ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1777045/+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 1777044] Re: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1777044 Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Also my boot area is reported to be full. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.8 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 14 17:03:54 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-01-26 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1777044/+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 1777044] [NEW] package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Also my boot area is reported to be full. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.8 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 14 17:03:54 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-01-26 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1777044 Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Also my boot area is reported to be full. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.8 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 14 17:03:54 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-01-26 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1777044/+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 1421977] Re: blender crashes on python code completion
** Also affects: python Importance: Undecided Status: New ** No longer affects: libedit (Ubuntu) ** No longer affects: readline (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. https://bugs.launchpad.net/bugs/1421977 Title: blender crashes on python code completion Status in Blender: Fix Released Status in Python: New Status in blender package in Ubuntu: Confirmed Bug description: Release: ubuntu 14.10 64 bit blender version: 2.70a-2ubuntu3 Open the python console with SHIFT F4, type a blender python class, e.g. bpy., and press CTRL BLANK for code completion. Blender crashes with a segmentation fault. The expected behavior is showing a list of attributes/methods of the python class. If you need more informations like gdb backtrace or logfiles, please have a look on this blender bug report: https://developer.blender.org/T43491 We - that meens some of the guys discussing this bug - think it's a library compatibility problem which can be solved by a rebuild. As I found another segmentation fault - if you mark an object, press 'm' to move it to another layer, and click on the layer symbol - I think that the actual blender build on ubuntu is a little bit unstable. I reproduced both segfaults with an ubuntustudio 14.10 live dvd. To manage notifications about this bug go to: https://bugs.launchpad.net/blender/+bug/1421977/+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
I had the same problem with 2 Dell of the year 2008 -- 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: Confirmed Status in linux: Confirmed 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 1421977] Re: blender crashes on python code completion
** Also affects: readline (Ubuntu) Importance: Undecided Status: New ** Also affects: libedit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. https://bugs.launchpad.net/bugs/1421977 Title: blender crashes on python code completion Status in Blender: Fix Released Status in blender package in Ubuntu: Confirmed Status in libedit package in Ubuntu: New Status in readline package in Ubuntu: New Bug description: Release: ubuntu 14.10 64 bit blender version: 2.70a-2ubuntu3 Open the python console with SHIFT F4, type a blender python class, e.g. bpy., and press CTRL BLANK for code completion. Blender crashes with a segmentation fault. The expected behavior is showing a list of attributes/methods of the python class. If you need more informations like gdb backtrace or logfiles, please have a look on this blender bug report: https://developer.blender.org/T43491 We - that meens some of the guys discussing this bug - think it's a library compatibility problem which can be solved by a rebuild. As I found another segmentation fault - if you mark an object, press 'm' to move it to another layer, and click on the layer symbol - I think that the actual blender build on ubuntu is a little bit unstable. I reproduced both segfaults with an ubuntustudio 14.10 live dvd. To manage notifications about this bug go to: https://bugs.launchpad.net/blender/+bug/1421977/+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 889889] Re: Use PNG or SVG instead of GIF
$ dpkg -L blender | grep \\.gif $ dpkg -L blender-data | grep \\.gif no more gifs in blender ** Changed in: blender (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to chardet in Ubuntu. https://bugs.launchpad.net/bugs/889889 Title: Use PNG or SVG instead of GIF Status in Adium Theme Ubuntu: Fix Released Status in OpenSSL: New Status in ace package in Ubuntu: New Status in app-install-data-ubuntu package in Ubuntu: Confirmed Status in blender package in Ubuntu: Fix Released Status in chardet package in Ubuntu: New Status in cups package in Ubuntu: New Status in dvd+rw-tools package in Ubuntu: New Status in foo2zjs package in Ubuntu: New Status in libcgi-pm-perl package in Ubuntu: New Status in openssl package in Ubuntu: Won't Fix Status in python3.4 package in Ubuntu: Won't Fix Status in software-center package in Ubuntu: Invalid Bug description: Use modern file formats such as PNG or SVG instead of the legacy GIF file formats. $ find /usr -name "*.gif" To manage notifications about this bug go to: https://bugs.launchpad.net/adium-theme-ubuntu/+bug/889889/+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 1768588] Re: Blender is missing parts of the "System" tab panel and some configurations.
** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: blender (Ubuntu) Status: New => Incomplete ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1768588 Title: Blender is missing parts of the "System" tab panel and some configurations. Status in blender package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: (*)Ubuntu 18.04 (any flavor). Blender 3D Modeler is missing 2/3 the "System tab" panel options regarding to OpenGL, localization, font overrides, translations, lamp directions and options to use custom colors for bone weights. Since 18.04 beta 1 and 2, I have been comparing the blender 2.79b present at the 18.04LTS obtained via apt-get to the one downloaded directly from Blender Foundation. If you install Blender from apt-get first, and then download and extract Blender from Blender Foundation in any folder, running the software you can go to the "User preference" options using CTRL U, and navigate to the "System tab" options. Now, compare the system tab of both. 2/3 of the options are missing in the default apt-get (*)ubuntu install. Many thanks for fixing this ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blender/+bug/1768588/+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 1777021] Re: Xorg freeze
Such freezes are more likely a kernel issue. Do you have any sign of life from the machine when frozen, like being able to login remotely? Please try installing 'openssh-server' and see if you can still log in to that when it appears frozen. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - Xorg freeze + Xorg freeze after wakeup from hibernate ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1777021 Title: Xorg freeze after wakeup from hibernate Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Happens mostly after wakeup from hibernate ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 15 03:21:59 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:837f] Subsystem: Hewlett-Packard Company Device [103c:8380] InstallationDate: Installed on 2018-02-13 (121 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: HP HP ProBook 470 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.01.07 dmi.board.name: 837F dmi.board.vendor: HP dmi.board.version: KBC Version 02.21.00 dmi.chassis.asset.tag: 5CD7497QSD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 470 G5 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jun 15 03:21:12 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777021/+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 1773583] Re: hid2hci spamming log with error messages
The errors are all about "usb3" and the bug was logged from a live session. Most likely there is a connection/reconnection problem with booting this particular USB drive or the USB port. Please try a different USB stick and a different USB port. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1773583 Title: hid2hci spamming log with error messages Status in bluez package in Ubuntu: Incomplete Bug description: unable to read disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun May 27 02:25:39 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773583/+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 1745664] Re: systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create()
Tracking in: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 ** Summary changed: - systemd-logind crashed with SIGABRT in __libc_connect() + systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() ** Description changed: + https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 + + --- + configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard - Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard + Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) + LANG=en_US.UTF-8 + PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: - __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 - __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 - __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 - __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 - __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 + __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 + __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 + __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 + __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 + __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 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. + [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: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z
[Touch-packages] [Bug 1771486] Re: systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create()
*** This bug is a duplicate of bug 1745664 *** https://bugs.launchpad.net/bugs/1745664 ** This bug has been marked a duplicate of bug 1745664 systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() -- 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/1771486 Title: systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in systemd package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771486/+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 1777021] [NEW] Xorg freeze
Public bug reported: Happens mostly after wakeup from hibernate ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 15 03:21:59 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:837f] Subsystem: Hewlett-Packard Company Device [103c:8380] InstallationDate: Installed on 2018-02-13 (121 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: HP HP ProBook 470 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.01.07 dmi.board.name: 837F dmi.board.vendor: HP dmi.board.version: KBC Version 02.21.00 dmi.chassis.asset.tag: 5CD7497QSD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 470 G5 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jun 15 03:21:12 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu xenial -- 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/1777021 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Happens mostly after wakeup from hibernate ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 15 03:21:59 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:837f] Subsystem: Hewlett-Packard Company Device [103c:8380] InstallationDate: Installed on 2018-02-13 (121 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: HP HP ProBook 470 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No
[Touch-packages] [Bug 1777010] [NEW] ip token set, results in: Invalid argument
Public bug reported: Hi, I can't set any ipv6 token with ip command. It seems that it has a bug. Also it is not possible to set it with netplan (see bug #1737976) ~# ip token list token :: dev enp1s0 token :: dev enp2s0 token :: dev ovpn0 token :: dev br0 ~# ip token set ::2a:2a:2a:2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::beef dev br0 RTNETLINK answers: Invalid argument It seems, that this Bug is really old?! https://bbs.archlinux.org/viewtopic.php?id=202757 This is really fatal, because I cant set a static ip. My prefix get mixed from my provider every x days. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 15 01:26:04 2018 InstallationDate: Installed on 2018-06-12 (2 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: Hi, - i cant set any ipv6 token with ip command. It seems that it has an bug. + I can't set any ipv6 token with ip command. It seems that it has a bug. Also it is not possible to set it with netplan (see bug #1737976) ~# ip token list token :: dev enp1s0 token :: dev enp2s0 token :: dev ovpn0 token :: dev br0 ~# ip token set ::2a:2a:2a:2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::beef dev br0 RTNETLINK answers: Invalid argument It seems, that this Bug is really old?! https://bbs.archlinux.org/viewtopic.php?id=202757 This is really fatal, because I cant set a static ip. My prefix get mixed from my provider every x days. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 15 01:26:04 2018 InstallationDate: Installed on 2018-06-12 (2 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1777010 Title: ip token set, results in: Invalid argument Status in iproute2 package in Ubuntu: New Bug description: Hi, I can't set any ipv6 token with ip command. It seems that it has a bug. Also it is not possible to set it with netplan (see bug #1737976) ~# ip token list token :: dev enp1s0 token :: dev enp2s0 token :: dev ovpn0 token :: dev br0 ~# ip token set ::2a:2a:2a:2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::beef dev br0 RTNETLINK answers: Invalid argument It seems, that this Bug is really old?! https://bbs.archlinux.org/viewtopic.php?id=202757 This is really fatal, because I cant set a static ip. My prefix get mixed from my provider every x days. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 15 01:26:04 2018 InstallationDate: Installed on 2018-06-12 (2 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1777010/+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 1748147] Proposed package upload rejected
An upload of debhelper to artful-proposed has been rejected from the upload queue for the following reason: "I'm rejecting this as their is some ongoing discussion and not every SRU member should have to read the whole bug.". -- 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ su
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Bionic) Status: New => Confirmed -- 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building depend
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rsyslog (Ubuntu Bionic) Status: New => Confirmed -- 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building depend
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rsyslog (Ubuntu Artful) Status: New => Confirmed -- 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building depend
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Artful) Status: New => Confirmed -- 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building depend
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
I've rejected the uploads in -proposed to declutter the queues and save some other SRU team member's time. -- 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building dependency tree Reading state informati
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rsyslog (Ubuntu) Status: New => Confirmed -- 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building dependency tr
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building depend
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rsyslog (Ubuntu Xenial) Status: New => Confirmed -- 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building depend
[Touch-packages] [Bug 1777006] Re: package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1777006 Title: package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: attempting a do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.11 ProcVersionSignature: Ubuntu 3.2.0-126.169-generic 3.2.79 Uname: Linux 3.2.0-126-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Thu Jun 14 15:02:24 2018 DuplicateSignature: package:initramfs-tools:0.103ubuntu4.11:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-01-23 (1968 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.18 SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2018-06-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1777006/+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 1777006] [NEW] package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: attempting a do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.11 ProcVersionSignature: Ubuntu 3.2.0-126.169-generic 3.2.79 Uname: Linux 3.2.0-126-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Thu Jun 14 15:02:24 2018 DuplicateSignature: package:initramfs-tools:0.103ubuntu4.11:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-01-23 (1968 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.18 SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2018-06-14 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1777006 Title: package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: attempting a do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.11 ProcVersionSignature: Ubuntu 3.2.0-126.169-generic 3.2.79 Uname: Linux 3.2.0-126-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Thu Jun 14 15:02:24 2018 DuplicateSignature: package:initramfs-tools:0.103ubuntu4.11:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-01-23 (1968 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.18 SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu4.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2018-06-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1777006/+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 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
Hi,
we're running into the same problem and wonder whether we could use a
sub-string of the MAC address instead. Does the UDEV library support
something like $env{MAC_ADDR:6}?
--
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/1567744
Title:
USB NICs get too long name for ifupdown aliases or bridge names
Status in systemd package in Ubuntu:
Triaged
Bug description:
I have a USB NIC that is connected to my denial system. I tried to
create an alias, and after reboot, it wasn't created. When I manually
try to bring it up I have the error.
/e/n/i:
auto enx000ec688b79f
iface enx000ec688b79f inet static
address 10.90.90.1
netmask 255.255.255.0
auto enx000ec688b79f:1
iface enx000ec688b79f:1 inet static
address 192.168.100.1
netmask 255.255.255.0
ubuntu@maas00:~$ sudo ifup enx000ec688b79f
ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
RTNETLINK answers: Numerical result out of range
Failed to bring up enx000ec688b79f:1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+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 1773213] Re: U1 login dialog missing link to the privacy policy
Hello Will, or anyone else affected, Accepted gnome-online-accounts into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-online-accounts/3.28.0-0ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-online-accounts (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1773213 Title: U1 login dialog missing link to the privacy policy Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Bionic: Fix Committed Bug description: The U1 login for g-o-a is missing a link to the privacy policy. [Impact] * No way to view the privacy policy for Ubuntu One [Test Case] * Open gnome-control-center * Select "Online Accounts" on the left * Select "Ubuntu Single Sign-On" under "Add an account" * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. * Verify when clicking the window a browser window opens with our data privacy page [Regression Potential] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+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 1776975] [NEW] package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent
Public bug reported: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 En effacant /usr/share/doc/libperl5.26/changelog.Debian.gz cela semble fonctionner, mais il y a tjrs le message suivant en fin d'ugrade : libdvd-pkg: Package libdvdcss2-1.4.2-1 was removed, stop processing... ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libperl5.26 5.26.1-6ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 14 21:28:51 2018 ErrorMessage: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 InstallationDate: Installed on 2017-10-26 (231 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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: perl Title: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 UpgradeStatus: Upgraded to bionic on 2018-05-14 (31 days ago) ** Affects: perl (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 perl in Ubuntu. https://bugs.launchpad.net/bugs/1776975 Title: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 Status in perl package in Ubuntu: New Bug description: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 En effacant /usr/share/doc/libperl5.26/changelog.Debian.gz cela semble fonctionner, mais il y a tjrs le message suivant en fin d'ugrade : libdvd-pkg: Package libdvdcss2-1.4.2-1 was removed, stop processing... ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libperl5.26 5.26.1-6ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 14 21:28:51 2018 ErrorMessage: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 InstallationDate: Installed on 2017-10-26 (231 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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: perl Title: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 UpgradeStatus: Upgraded to bionic on 2018-05-14 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1776975/+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 1776956] Re: /usr/bin/dconf:11:dconf_engine_change_sync:dconf_client_write_sync:dconf_reset:_vala_main:__libc_start_main
I received a crash report in the linked bucket after upgrading from Ubuntu 16.04 to Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1776956 Title: /usr/bin/dconf:11:dconf_engine_change_sync:dconf_client_write_sync:dconf_reset:_vala_main:__libc_start_main Status in d-conf package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding d-conf. This problem was most recently seen with package version 0.26.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/78420c7b413d368ab6bcf6504f0bf62b34a401d2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1776956/+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 1776956] [NEW] /usr/bin/dconf:11:dconf_engine_change_sync:dconf_client_write_sync:dconf_reset:_vala_main:__libc_start_main
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding d-conf. This problem was most recently seen with package version 0.26.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/78420c7b413d368ab6bcf6504f0bf62b34a401d2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: d-conf (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic precise trusty zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1776956 Title: /usr/bin/dconf:11:dconf_engine_change_sync:dconf_client_write_sync:dconf_reset:_vala_main:__libc_start_main Status in d-conf package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding d-conf. This problem was most recently seen with package version 0.26.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/78420c7b413d368ab6bcf6504f0bf62b34a401d2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1776956/+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 1768610] Re: leftover conffile forces GNOME is software rendering
also, it actually ships stuff in /etc/X11/Xsession.d -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
I'd rather put it in x11-common (src:xorg), which already is full of distro specific things and is installed on every system -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser
Hi Colin
Excellent!! It working perfect. Thanks very much.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1714518
Title:
GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
shares in file chooser
Status in GTK+:
Fix Released
Status in gtk+3.0 package in Ubuntu:
Fix Released
Status in gtk+3.0 source package in Trusty:
Triaged
Status in gtk+3.0 source package in Xenial:
Triaged
Status in gtk+3.0 source package in Artful:
Triaged
Bug description:
Steps to reproduce:
1. Install any Gtk3 application such as Firefox or Chromium which use modern
file-chooser dialog.
2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS,
"sftp://"; = SFTP/SSH and so on)
3. Try to save/open file to/from the remote location from Gtk3 application.
Expected results:
* user is able to find network folder and save/open file to/from it with
GtkFileChooser dialog
Actual results:
* user is unable to find network folder and save/open file to/from it with
GtkFileChooser dialog and many user applications are affected
-
Original bug description is below:
GTK+3 doesn't show FUSE network shares in file chooser - it used to do
so in GTK+2, and the GTK+3 documentation still mentions it should do
it.
In the mean time, every user of every application switching to GTK+3
-- including Chromium, at some point between 58 and 60 -- (a change
which happened in 16.04 LTS!!), loses the functionality to open or
save directly to a network share.
I had chosen 16.04 LTS for deploying our workstations at work, and my 50
users have been suddenly unable to do a simple operation they have to do dozens
of times a day.
They now have to "buffer" these files to their local filesystem when saving
them and before uploading them, and then copy them to the company's network
shares.
They were already a little bit grumpy when it stopped working with Firefox,
and are now really side-eyeing me when they apply updates and find Chromium
broken.
I have reported the bug upstream and provided a patch to fix this. I
hope you'll be able and willing to include it to Ubuntu's GTK+3
package.
Thanks in advance.
Colin
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+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 1776943] Re: "login as other user" is a no-op
Regarding the "No upgrade log present" I think the script is broken; > du /var/log/apt/history.log* 8 /var/log/apt/history.log 8 /var/log/apt/history.log.1.gz 36 /var/log/apt/history.log.2.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1776943 Title: "login as other user" is a no-op Status in shadow package in Ubuntu: New Bug description: login as user b, lock the screen then press "login as other user" and you will not be offered the option to login as user a, control+alt+f1 seems to be the hidden workaround. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 14 13:19:13 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-22 (53 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1776943/+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 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
>From the WSL Users, they have luck with the -w option. But it doesn't help on
>my Ubuntu 18.04 system.
https://github.com/Microsoft/WSL/issues/2138
** Bug watch added: github.com/Microsoft/WSL/issues #2138
https://github.com/Microsoft/WSL/issues/2138
--
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/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync package in Ubuntu:
Confirmed
Bug description:
In the last few months my home directory backup stopped completing.
I've been able to reproduce the problem on a single subdirectory
although I had to add the --debug=all flag to reproduce it on that
smaller directory. Specifically, this command never completes:
rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
The html2 directory is a copy of
gnuradio-3.7.8.1/build/docs/doxygen/html .
When I strace the command, I see this:
write(1, "sender finished /tmp/html2/atsc_"..., 58sender finished
/tmp/html2/atsc__interleaver_8h__incl.md5
) = 58
write(1, "send_files(338, /tmp/html2/atsc_"..., 59send_files(338,
/tmp/html2/atsc__interleaver_8h__incl.png)
) = 59
open("html2/atsc__interleaver_8h__incl.png", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=264657, ...}) = 0
write(1, "html2/atsc__interleaver_8h__incl"...,
37html2/atsc__interleaver_8h__incl.png
) = 37
read(3,
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\n\253\0\0\2\233\10\6\0\0\0h\242\""...,
262144) = 262144
select(6, [5], [4], [5], {60, 0}) = 2 (in [5], out [4], left {59,
96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95)
= 95
write(4,
"r\311\0\7\177\377\232\237\264\272e\300\300\240\316\264&\314\301\252*\37\256y\225g\373^\315j\370\350"...,
51574) = 51574
select(5, [], [4], [], {60, 0}) = 1 (out [4], left {59, 97})
write(4,
"\7\320\0\7\177\377\234|\7X\223Y\273\255c\27\25f\306\212\202\214#E\272\212t\1\225A\fU"...,
53259) = 53259
select(5, [], [4], [], {60, 0}
The select command times out over and over. I get the same behavior
when trying to back up my entire home directory but I don't need the
--debug=all flag in that case.
lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
apt-cache policy rsync
rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
*** 3.1.0-2ubuntu0.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386
Packages
100 /var/lib/dpkg/status
3.1.0-2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rsync 3.1.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CurrentDesktop: KDE
Date: Wed Dec 23 09:44:17 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-09-18 (1922 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
SourcePackage: rsync
UpgradeStatus: Upgraded to trusty on 2014-12-27 (361 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+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 1753954] Re: Intel Whiskey Lake (WHL) graphics support
Hello Timo, or anyone else affected, Accepted mesa into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.0.5-0ubuntu0~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mesa (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1753954 Title: Intel Whiskey Lake (WHL) graphics support Status in libdrm package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libdrm source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: Won't Fix Status in mesa source package in Xenial: Fix Committed Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: New Status in libdrm source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in xorg-server-hwe-16.04 source package in Bionic: Invalid Bug description: [Impact] WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, libdrm, mesa and xserver. [Test Case] Test the installation on a WHL machine, the graphical session should have full acceleration after these updates. [Regression Potential] None, just adds PCI-ID's to existing drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1753954/+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 1772632] Re: Backport packages for 16.04.5 HWE stack
Hello Timo, or anyone else affected, Accepted mesa into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.0.5-0ubuntu0~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mesa (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu: New Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-6.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-ati source package in Xenial: New Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-intel source package in Xenial: New Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+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 1776475] Re: Unlocking existing session often requires several attempts.
Bug still regularly observed. This is not the same bug as #1656399 though it share some characteristics. In particular, the fact that both bugs do not always occur (but somehow randomly) suggests that both are linked to a race condition somewhere in lightdm logic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+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 1776943] [NEW] "login as other user" is a no-op
Public bug reported: login as user b, lock the screen then press "login as other user" and you will not be offered the option to login as user a, control+alt+f1 seems to be the hidden workaround. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 14 13:19:13 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-22 (53 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (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 shadow in Ubuntu. https://bugs.launchpad.net/bugs/1776943 Title: "login as other user" is a no-op Status in shadow package in Ubuntu: New Bug description: login as user b, lock the screen then press "login as other user" and you will not be offered the option to login as user a, control+alt+f1 seems to be the hidden workaround. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 14 13:19:13 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-22 (53 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1776943/+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 1772632] Re: Backport packages for 16.04.5 HWE stack
Hello Timo, or anyone else affected, Accepted xorg-server-hwe-16.04 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-hwe-16.04/2:1.19.6-1ubuntu4~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server-hwe-16.04 (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu: New Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-6.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-ati source package in Xenial: New Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-intel source package in Xenial: New Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+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 1776742] Re: [Wishlist] Add a GUI systemd service manager by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1776742 Title: [Wishlist] Add a GUI systemd service manager by default Status in systemd package in Ubuntu: Confirmed Bug description: Please add a GUI systemd services manager by default, so the end user can choose easy what to enable and disable in his system. For example CUPS service not every user on laptop needs it enabled by default= faster boot,etc.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 13 20:40:42 2018 InstallationDate: Installed on 2017-12-18 (176 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215) Lsusb: Bus 002 Device 002: ID 0402:7675 ALi Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer AO722 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=b20f465f-45a3-49da-b5ea-8351b8e94c03 ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/ureadahead.service → /etc/systemd/system/ureadahead.service.d/quiet.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE10-BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08: dmi.product.family: Type1Family dmi.product.name: AO722 dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1776742/+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 1773691] Re: software-properties-gtk --massive-debug does not output any information when switching graphics drivers
** Package changed: gparted (Ubuntu) => software-properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1773691 Title: software-properties-gtk --massive-debug does not output any information when switching graphics drivers Status in software-properties package in Ubuntu: New Bug description: Running the command 'sudo software-properties-gtk --massive-debug' and switching from nouveau to nvidia graphics drivers or vice-versa does not output any information about the process. It should log what is being done exactly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1773691/+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 1773691] [NEW] software-properties-gtk --massive-debug does not output any information when switching graphics drivers
You have been subscribed to a public bug: Running the command 'sudo software-properties-gtk --massive-debug' and switching from nouveau to nvidia graphics drivers or vice-versa does not output any information about the process. It should log what is being done exactly. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- software-properties-gtk --massive-debug does not output any information when switching graphics drivers https://bugs.launchpad.net/bugs/1773691 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- 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 1481871] Re: apt-key del silently fails to delete keys due to limited understanding of GPG key ID formats
Just as a side note: 1) apt-key via debootstrap is currently broken on Bionic anyway (gpgv1 to gpgv2 side effects probably), see https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1767319 2) apt-key seems to be deprecated and should not be used any more on newer systems, so maybe the bug is a good starter for enforcing deprecation after bionic: https://lists.gnupg.org/pipermail/gnupg- users/2018-May/060428.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1481871 Title: apt-key del silently fails to delete keys due to limited understanding of GPG key ID formats Status in apt package in Ubuntu: Triaged Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 apt: Installed: 1.0.1ubuntu2.10 apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here apt-key del 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still here # Works fine with IDs apt-key del 0E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing exported # Works fine with fingerprint on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1481871/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Thank you @egor-tensin! I've been struggling with this problem for years. This is the first work around that actually works! I added that line under the [ipv4] section of my VPN connection file and then restarted the network manager with: sudo systemctl restart NetworkManager.service Now it's actually using the DNS specified by the VPN rather than just my default ISP's DNS. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1481871] Re: apt-key del silently fails to delete keys due to limited understanding of GPG key ID formats
Confirmed on xenial: root@ubuntu:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS" root@ubuntu:~# apt-key list|grep -A3 ownCloud uid ownCloud build service sub 2048R/8DE365D9 2013-08-26 [expires: 2018-08-25] sub 2048D/86EB6027 2013-08-26 [expires: 2018-08-25] sub 2048g/1722EF54 2013-08-26 [expires: 2018-08-25] root@ubuntu:~# apt-key del 8DE365D9 OK root@ubuntu:~# apt-key list|grep -A3 ownCloud uid ownCloud build service sub 2048R/8DE365D9 2013-08-26 [expires: 2018-08-25] sub 2048D/86EB6027 2013-08-26 [expires: 2018-08-25] sub 2048g/1722EF54 2013-08-26 [expires: 2018-08-25] root@ubuntu:~# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1481871 Title: apt-key del silently fails to delete keys due to limited understanding of GPG key ID formats Status in apt package in Ubuntu: Triaged Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 apt: Installed: 1.0.1ubuntu2.10 apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here apt-key del 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still here # Works fine with IDs apt-key del 0E27C0A6 apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing exported # Works fine with fingerprint on Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1481871/+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 1772632] Re: Backport packages for 16.04.5 HWE stack
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-intel-hwe-16.04 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel- hwe-16.04/2:2.99.917+git20171229-1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xserver-xorg-video-intel-hwe-16.04 (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu: New Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-6.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: In Progress Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-ati source package in Xenial: New Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-intel source package in Xenial: New Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+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 520546] Re: Alt-f2 switches to virtual terminal 2
The bug is STILL there (after 8 years of the first report!) and no fix and not even a workaround is available?! NO, rebooting is NOT an acceptable workaround! I run Xubuntu 16.04 with all updates installed. -- 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/520546 Title: Alt-f2 switches to virtual terminal 2 Status in console-cyrillic package in Ubuntu: Invalid Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1773583] Re: errno 5
I don't see any errors about being able to read the disk, or that ubiquity even crashed. What I do see is your log spammed full of lines like this: May 26 20:55:51 ubuntu systemd-udevd[16997]: Process 'hid2hci --method=dell --devpath=/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0' failed with exit code 1. May 26 20:55:51 ubuntu upowerd[1500]: unhandled action 'unbind' on /sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 Which appear to be a problem with a program in the bluez package. ** Package changed: ubiquity (Ubuntu) => bluez (Ubuntu) ** Summary changed: - errno 5 + hid2hci spamming log with error messages -- 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/1773583 Title: hid2hci spamming log with error messages Status in bluez package in Ubuntu: New Bug description: unable to read disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun May 27 02:25:39 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773583/+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 1773583] [NEW] errno 5
You have been subscribed to a public bug: unable to read disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun May 27 02:25:39 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu -- errno 5 https://bugs.launchpad.net/bugs/1773583 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. -- 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
Re: [Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I should add that my system was an upgrade, using LVM with EXT4. I'm honestly debating about backing up, blowing it up and installing fresh without LVM, I'm not sure I see the advantage to using it. On Thu, Jun 14, 2018 at 10:31 AM Marc Pignat <1768...@bugs.launchpad.net> wrote: > This bug seems wrongly linked to ubiquity since updating the system can > also lead to the bug. Can someone find a better package to link this bug > to? the kernel? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1768230 > > Title: > Long time booting : Failed to connect to lvmetad. Falling back to > device scanning. > > Status in ubiquity package in Ubuntu: > Confirmed > > Bug description: > After choosing "Erase disk and install ubuntu" + "Use LVM with the new > Ubuntu installation", the > system is very slow to reboot. > > It shows the message : "WARNING:Failed to connect to lvmetad. Falling > back to device scanning.", > then waits 32 seconds, then continues as it should. > > I think this is a ubiquity bug, since the d-i based installer is not > affected. >- ubuntu-18.04-desktop-amd64.iso > (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : > affected >- xubuntu-18.04-desktop-amd64.iso > (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : > affected >- ubuntu-18.04-server-amd64.iso > (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not > affected > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions > -- Steve Lougheed sloughee...@gmail.com BCS Junior High Computer Science 905-843-3771 This email, including any attachments, is for the sole use of the intended recipient and may contain confidential information. If you are not the intended recipient, please immediately notify us by reply email or by telephone, delete this email and destroy any copies. Thank-you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Package changed: ubiquity (Ubuntu) => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1773438] Re: packagekitd is locking /var/lib/dpkg/lock
That is normal; it is manipulating the dpkg database. ** Package changed: gparted (Ubuntu) => packagekit (Ubuntu) ** Changed in: packagekit (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1773438 Title: packagekitd is locking /var/lib/dpkg/lock Status in packagekit package in Ubuntu: Invalid Bug description: root@ubuntu:~# apt dist-upgrade E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable) E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? root@ubuntu:~# fuser /var/lib/dpkg/lock /var/lib/dpkg/lock: 2738 root@ubuntu:~# ps aux USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 2738 12.4 0.5 491528 90328 ?Ssl 21:02 0:19 /usr/lib/packagekit/packagekitd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1773438/+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 1768230] [NEW] Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
You have been subscribed to a public bug: After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: rls-bb-incoming rls-cc-incoming -- Long time booting : Failed to connect to lvmetad. Falling back to device scanning. https://bugs.launchpad.net/bugs/1768230 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. -- 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 1772632] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-amdgpu-hwe-16.04 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu- hwe-16.04/18.0.1-1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: xserver-xorg-video-amdgpu-hwe-16.04 (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-ati-hwe-16.04 (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-intel-hwe-16.04 (Ubuntu) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-ati-hwe-16.04 (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: xserver-xorg-video-amdgpu-hwe-16.04 (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu: New Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-6.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: In Progress Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-ati source package in Xenial: New Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-intel source package in Xenial: New Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+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 1773438] [NEW] packagekitd is locking /var/lib/dpkg/lock
You have been subscribed to a public bug: root@ubuntu:~# apt dist-upgrade E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable) E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? root@ubuntu:~# fuser /var/lib/dpkg/lock /var/lib/dpkg/lock: 2738 root@ubuntu:~# ps aux USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 2738 12.4 0.5 491528 90328 ?Ssl 21:02 0:19 /usr/lib/packagekit/packagekitd ** Affects: packagekit (Ubuntu) Importance: Undecided Status: Invalid -- packagekitd is locking /var/lib/dpkg/lock https://bugs.launchpad.net/bugs/1773438 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. -- 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 1772632] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-ati-hwe-16.04 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati- hwe-16.04/1:18.0.1-1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-6.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: In Progress Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-ati source package in Xenial: New Status in xserver-xorg-video-intel source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+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 1772632] Re: Backport packages for 16.04.5 HWE stack
Hello Timo, or anyone else affected, Accepted libclc into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20180312-1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libclc (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-6.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: In Progress Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-ati source package in Xenial: New Status in xserver-xorg-video-intel source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+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 1776914] [NEW] netem queue does not accept 0.0% for loss or duplicate
Public bug reported: Upstream bug report, with patch: https://bugzilla.kernel.org/show_bug.cgi?id=199745 ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1776914 Title: netem queue does not accept 0.0% for loss or duplicate Status in iproute2 package in Ubuntu: New Bug description: Upstream bug report, with patch: https://bugzilla.kernel.org/show_bug.cgi?id=199745 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1776914/+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 1771486] Re: systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create()
Looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664 -- 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/1771486 Title: systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in systemd package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771486/+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 1745664] Re: systemd-logind crashed with SIGABRT in __libc_connect()
Neither of my systems crash when logging into a nis account. -- 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/1745664 Title: systemd-logind crashed with SIGABRT in __libc_connect() Status in systemd package in Ubuntu: Confirmed Bug description: configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 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: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664/+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 1745664] Re: systemd-logind crashed with SIGABRT in __libc_connect()
A second one of our systems is having the __libc_connect crashes. AMD Ryzen 7 1800X Nvida GT 710 ** Attachment added: "_lib_systemd_systemd-logind.0.crash" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664/+attachment/5152561/+files/_lib_systemd_systemd-logind.0.crash -- 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/1745664 Title: systemd-logind crashed with SIGABRT in __libc_connect() Status in systemd package in Ubuntu: Confirmed Bug description: configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 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: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664/+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 1776860] Re: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1776860 Title: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127 Status in apt package in Ubuntu: New Bug description: ??? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 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.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fred 1439 F pulseaudio /dev/snd/controlC2: fred 1439 F pulseaudio /dev/snd/controlC0: fred 1439 F pulseaudio Date: Thu Jun 14 10:38:07 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127 InstallationDate: Installed on 2018-05-29 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: HP-Pavilion VN433AA-ABF p6235fr ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=cde7b5ab-35ce-4bcf-8860-4a9b313d78e9 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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: grub-pc 2.02-2ubuntu8 RfKill: SourcePackage: apt Title: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.14 dmi.board.name: Eureka3 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02 dmi.chassis.asset.tag: Asset-1234 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.14:bd11/13/2009:svnHP-Pavilion:pnVN433AA-ABFp6235fr:pvr:rvnPEGATRONCORPORATION:rnEureka3:rvr1.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: VN433AA-ABF p6235fr dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1776860/+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 1776860] Re: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1776860 Title: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127 Status in apt package in Ubuntu: New Bug description: ??? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 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.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fred 1439 F pulseaudio /dev/snd/controlC2: fred 1439 F pulseaudio /dev/snd/controlC0: fred 1439 F pulseaudio Date: Thu Jun 14 10:38:07 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127 InstallationDate: Installed on 2018-05-29 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: HP-Pavilion VN433AA-ABF p6235fr ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=cde7b5ab-35ce-4bcf-8860-4a9b313d78e9 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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: grub-pc 2.02-2ubuntu8 RfKill: SourcePackage: apt Title: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.14 dmi.board.name: Eureka3 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02 dmi.chassis.asset.tag: Asset-1234 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.14:bd11/13/2009:svnHP-Pavilion:pnVN433AA-ABFp6235fr:pvr:rvnPEGATRONCORPORATION:rnEureka3:rvr1.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: VN433AA-ABF p6235fr dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1776860/+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 1768610] Re: leftover conffile forces GNOME is software rendering
Marco, I don't think there is a solution that satisfies all the requirements and doesn't involve nux cooperating in some way. I've given you mostly-working debdiffs now - can we please move forward with them? -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
I'm trying the bionic version of the proposed nux-tools (4.0.8+18.04.20180613.5-0ubuntu1) and it works fine so far. -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1542755]
http://time.jimbenhoff.com Mary Hamilton -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1542755 Title: at least 3 reinstalls due to no onshut down or restart. msg start up sometimes, tried boot repair,something was missing, sorry I can't remember terminology. Problems started with specialized downloads. Sound recorder(bad)sound converter,pixel swapper, great apps. I was thinking my att router has been compromised via win 10 updates.. Status in gcc-4.8 package in Ubuntu: Invalid Bug description: Ubuntu 14.04 over a year using with all updates worked great, then the Libre Office Writer went fooey,several re-installs,fixed.Then, I thought all my photos were getting shared live maybe via Libre Ofiice app Then Firefox sync caused me a lot of grief when I installed it on two win10 desktops with Sync Not syncing now tho. I swapped the mouse, which doesn't want to function well. Got firefox straight maybe, then Ubuntu started hanging on restart or shut down. I tried running a boot repair, it said my registry was missing. I tried for a clean install, but I think all it did was add a copy. No reinstall would shut down.Tried a different version,same problem. I have an att router & have been installing updates et al, on 2 other desktops. As soon as I get a Win 10 going, something seems to stop working on Ubuntu. I prefer Ubuntu for multiple reasons. Win 10 seems to be a barebones with a big buynow catalog or surf the win10 web. However, it has a working Sound recorder, & AIO dell usb XP printer,fax etc. Also, I have a Nook reader with lots of apps I don't use. I've started using the OverDrive only app, as the google library chromeconnection kept me confused. added new windows, froze books,etc. It is wifi which I leave on continuously. I just learned Sudo init O. Used it one time. Worked fine. These "bugs" seem to be attempts to wreak havoc, I have copies of my files/photos on DVD, which I download to desktop when I re-install. So sorry. I break things worse trying to repair them many times, but I'm experienced at starting over, just don't like to. I am trying to avoid wiping the hd, reformatting, etc. Very time consuming for a little old lady pushing 70. Time is precious, but so is money,lol, so I do it myself.This bug reequest popped up, so maybe you can connect something from others with similar occurances. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: cpp-4.8 4.8.2-19ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Sat Feb 6 18:53:42 2016 DuplicateSignature: package:cpp-4.8:4.8.2-19ubuntu1:cannot copy extracted data for './usr/bin/cpp-4.8' to '/usr/bin/cpp-4.8.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/bin/cpp-4.8' to '/usr/bin/cpp-4.8.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2016-02-06 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gcc-4.8 Title: package cpp-4.8 4.8.2-19ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/bin/cpp-4.8' to '/usr/bin/cpp-4.8.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1542755/+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 1776890] [NEW] Some loops between services while upgrading through apt
Public bug reported: While I try to upgrade my Ubuntu through "apt upgrade", it gives me many errors involving loops between services (insserv gives me the output). I've tried to purge grub-common and make upgrade again -> no result. I'm not able to understand well what's happening. The error is raised after an upgrade of ~400MB today. Some packets have been correctly installed. These others (listed in the attached file, at the bottom of it), raises an error. Thank you for you effort in resolving this bug guys !!! insserv: warning: script 'S99runmbbservice' missing LSB tags and overrides insserv: warning: script 'runmbbservice' missing LSB tags and overrides insserv: There is a loop at service plymouth if started insserv: There is a loop between service plymouth and procps if started insserv: loop involving service procps at depth 2 insserv: loop involving service udev at depth 1 insserv: There is a loop between service plymouth and urandom if started insserv: loop involving service urandom at depth 4 insserv: loop involving service hwclock at depth 3 insserv: There is a loop between service runmbbservice and mountkernfs if started insserv: loop involving service mountkernfs at depth 1 insserv: There is a loop at service runmbbservice if started insserv: Starting runmbbservice depends on plymouth and therefore on system facility `$all' which can not be true! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.4 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 14 12:50:19 2018 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2018-02-02 (131 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: console-setup Title: package keyboard-configuration 1.108ubuntu15.4 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.d.keyboard-setup: [deleted] ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial ** Attachment added: "Output of apt upgrade command giving me some errors" https://bugs.launchpad.net/bugs/1776890/+attachment/5152517/+files/apt_upgrade_output ** Description changed: - While I try to upgrade my Ubuntu through atp upgrade, it gives me many errors involving loops between services (insserv gives me the output). + While I try to upgrade my Ubuntu through "apt upgrade", it gives me many errors involving loops between services (insserv gives me the output). I've tried to purge grub-common and make upgrade again -> no result. I'm not able to understand well what's happening. The error is raised after an upgrade of ~400MB today. Some packets have been correctly installed. These others (listed in the attached file, at the bottom of it), raises an error. Thank you for you effort in resolving this bug guys !!! + + insserv: warning: script 'S99runmbbservice' missing LSB tags and overrides + insserv: warning: script 'runmbbservice' missing LSB tags and overrides + insserv: There is a loop at service plymouth if started + insserv: There is a loop between service plymouth and procps if started + insserv: loop involving service procps at depth 2 + insserv: loop involving service udev at depth 1 + insserv: There is a loop between service plymouth and urandom if started + insserv: loop involving service urandom at depth 4 + insserv: loop involving service hwclock at depth 3 + insserv: There is a loop between service runmbbservice and mountkernfs if started + insserv: loop involving service mountkernfs at depth 1 + insserv: There is a loop at service runmbbservice if started + insserv: Starting runmbbservice depends on plymouth and therefore on system facility `$all' which can not be true! + ProblemType: Package DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.4 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 14 12:50:19 2018 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2018-02-02 (131 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: - dpkg 1.18.4ubuntu1.4 - apt 1.2.26 + dpkg
[Touch-packages] [Bug 1776890] Re: Some loops between services while upgrading through apt
It seems I've resolved using theese commands:
for fil in $(cat file_list_of_errored_packets);do rm
/var/lib/dpkg/info/${fil}.postinst; done
apt install -f
Now I get no errors anymore ... I will be back just to confirm or
discard the resolution of this bug
--
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/1776890
Title:
Some loops between services while upgrading through apt
Status in console-setup package in Ubuntu:
New
Bug description:
While I try to upgrade my Ubuntu through "apt upgrade", it gives me many
errors involving loops between services (insserv gives me the output).
I've tried to purge grub-common and make upgrade again -> no result.
I'm not able to understand well what's happening.
The error is raised after an upgrade of ~400MB today. Some packets
have been correctly installed. These others (listed in the attached
file, at the bottom of it), raises an error.
Thank you for you effort in resolving this bug guys !!!
insserv: warning: script 'S99runmbbservice' missing LSB tags and overrides
insserv: warning: script 'runmbbservice' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and procps if started
insserv: loop involving service procps at depth 2
insserv: loop involving service udev at depth 1
insserv: There is a loop between service plymouth and urandom if started
insserv: loop involving service urandom at depth 4
insserv: loop involving service hwclock at depth 3
insserv: There is a loop between service runmbbservice and mountkernfs if
started
insserv: loop involving service mountkernfs at depth 1
insserv: There is a loop at service runmbbservice if started
insserv: Starting runmbbservice depends on plymouth and therefore on system
facility `$all' which can not be true!
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: keyboard-configuration 1.108ubuntu15.4
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu Jun 14 12:50:19 2018
ErrorMessage: il sottoprocesso installato script di post-installation ha
restituito lo stato di errore 1
InstallationDate: Installed on 2018-02-02 (131 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
PackageArchitecture: all
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.4
apt 1.2.26
SourcePackage: console-setup
Title: package keyboard-configuration 1.108ubuntu15.4 failed to
install/upgrade: il sottoprocesso installato script di post-installation ha
restituito lo stato di errore 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.d.keyboard-setup: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1776890/+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 1768610] Re: leftover conffile forces GNOME is software rendering
Yeah, I basically did the same too, but honestly I didn't want to change nux again with another SRU (I preferred to fix this with just one on that side); and most importantly in a such way. As it would now include some checks that depends on changes done in other packages, making from my POV things even more hackish and annoy to matain and easy to be broken. Not that other solutions wouldn't involve the other package (say mesa) to act on nux file, but that should be in a way that nux is not aware of that, creating any kind of "inter-dependency" in between them. -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1776859] Re: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571)
It appears you have a PCI-connected card: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter But it's unclear if your wifi card supports bluetooth at all. In one case on the web an engineer has mentioned "Some of the 4313's have BT, and some don't.". I still can't find evidence your laptop supports bluetooth at all. Did it work in Windows? Also, please add the missing file: dpkg -l > dpkg.txt Finally, if you installed bluez via a snap, please try removing it. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** No longer affects: bluez (Ubuntu) -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776859/+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 1768610] Re: leftover conffile forces GNOME is software rendering
** Patch added: "mesa.debdiff" https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5152448/+files/mesa.debdiff -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1776859] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152434/+files/Dependencies.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1776859] Re: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571)
** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: Incomplete => New -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776859/+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 1768610] Re: leftover conffile forces GNOME is software rendering
** Patch added: "nux.debdiff" https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5152447/+files/nux.debdiff -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1776859] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152444/+files/syslog.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1776859] Re: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571)
And I also run that command. If there is something else I can do, please, let me know. -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1768610] Re: leftover conffile forces GNOME is software rendering
This is the solution that I proposed to you in private. It is a fix to mesa (a "common" package) and a followup to nux-tools. It needs some testing. In particular I don't think I picked the right mesa package to use, and we also need to check with the mesa maintainer. There are various version numbers in there that need to be correct for the target release. A basic test worked OK though (libegl1-mesa is because I had it in an even more wrong package at the time). Remove nux-tools, broken conffile is left around, upgrade mesa, it's fixed, install new nux-tools and it's installed with the right content and no prompt: root@nux-tools-test:~# apt remove nux-tools ... root@nux-tools-test:~# ls /etc/X11/Xsession.d/50_check_unity_support /etc/X11/Xsession.d/50_check_unity_support root@nux-tools-test:~# sudo apt full-upgrade ... Broken /etc/X11/Xsession.d/50_check_unity_support and removed nux-tools found, moving aside... root@nux-tools-test:~# sudo apt install nux-tools Found saved /etc/X11/Xsession.d/50_check_unity_support.mesa-save file, moving it back in place... Unpacking nux-tools (4.0.8+18.04.20180613.5-0ubuntu2) ... Setting up nux-tools (4.0.8+18.04.20180613.5-0ubuntu2) ... Installing new version of config file /etc/X11/Xsession.d/50_check_unity_support ... root@nux-tools-test:~# cat /etc/X11/Xsession.d/50_check_unity_support # This file is sourced by Xsession(5), not executed. # If the hardware does not pass unity_support_test, fall back to LLVMpipe # which does. if [ "x$DESKTOP_SESSION" = "xubuntu" ] && [ -x "/usr/lib/nux/unity_support_test" ]; then ( IFS=':' for d in $XDG_CURRENT_DESKTOP; do if [ "x$d" = "xUnity" ] || [ "x$d" = "xUnity7" ]; then return 0 fi done return 1 ) if [ $? = 0 ]; then /usr/lib/nux/unity_support_test || export LIBGL_ALWAYS_SOFTWARE=1 fi fi -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) In
[Touch-packages] [Bug 1776859] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152442/+files/getfacl.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1776859] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152439/+files/ProcInterrupts.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1776859] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152441/+files/UdevDb.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1776859] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152443/+files/rfkill.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1776859] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152438/+files/ProcCpuinfoMinimal.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1776859] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152436/+files/Lsusb.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1776859] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152440/+files/ProcModules.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1776859] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152437/+files/ProcCpuinfo.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1776859] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152435/+files/Lspci.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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 1776859] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1776859/+attachment/5152433/+files/CurrentDmesg.txt -- 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/1776859 Title: Bluetooth doesn't work on ubuntu 18.04 LTS (Acer aspire E1-571) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have installed ubuntu 18.04 LTS on my laptop Acer aspire E1-571 and I cannot turn on the bluetooth. It's not that it doesn't find the devises, but I do not either have the option to turn it on. I've tried installing all drivers I have found (bluez gnome, blueman, shell extension...), but the same issue remains. It is no blocked either, I've tried "sudo rfkill list" in every modification and always the same: 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no Do someone know what might be happening? Any solution? Thank you so much in advance. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-15 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: bluetooth MachineType: Acer Aspire E1-571 NonfreeKernelModules: wl Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: third-party-packages bionic wayland-session Uname: Linux 4.15.0-23-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd02/19/2013:svnAcer:pnAspireE1-571:pvrV2.14:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.14: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.14 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1776859/+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
