[Touch-packages] [Bug 1809709] Re: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit st
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1809709 Title: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 Status in ibus package in Ubuntu: New Bug description: I removed python and it caused the gui to go, so i installed gnome through tty1 and then later installed ubuntu-desktop . After this all these happened ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Dec 24 20:56:01 2018 DuplicateSignature: package:gir1.2-ibus-1.0:amd64:1.5.17-3ubuntu4 Removing gir1.2-ibus-1.0:amd64 (1.5.17-3ubuntu4) ... /var/lib/dpkg/info/gir1.2-ibus-1.0:amd64.prerm: 6: /var/lib/dpkg/info/gir1.2-ibus-1.0:amd64.prerm: py3clean: not found dpkg: error processing package gir1.2-ibus-1.0:amd64 (--remove): installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2018-12-17 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ibus Title: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1809709/+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 1809712] [NEW] Not responding to input after switch user to auto-login account
Public bug reported: Step: 1. There are two users, A and B. A is adminstrator, B is standard user, B is automatic login. 2. Boot into Ubuntu 18.04.1 LTS, it will automatically login to user B. 3. Switch User to user A without logging out. 4. Switch User back to user B, either by logging out from user A or not. Expected: it will be back to user B normally. Actual: it backs to user B but become not responding to keyboard, touchpad, or mouse input. Closing the lid is responded normally, which is locking the screen, the three-arrows in the lock screen is animated normally, clock is updated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 14:19:34 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:183a] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-12-23 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=3182b497-aa0e-491d-aad5-e1c8e049dda1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.01 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183A dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.0E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.01:bd01/18/2012:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn183A:rvr56.0E:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 07911020561620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1809712 Title: Not responding to input after switch user to auto-login account Status in xorg package in Ubuntu: New Bug description: Step: 1. There are two users, A and B. A is adminstrator, B is standard user, B is automatic login. 2. Boot into Ubuntu 18.04.1 LTS, it will automatically login to user B. 3. Switch User to user A without logging out. 4. Switch User back to user B, either by logging out from user A or not. Expected: it will be back to user B normally. Actual: it backs to user B but become not responding to keyboard, touchpad, or mouse input. Closing the lid is responded normally, which is locking the screen, the three-arrows in the lock screen is animated normally, clock is updated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 14:19:34 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:183a] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-12-23 (2 days ago)
[Touch-packages] [Bug 1809709] [NEW] package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit
Public bug reported: I removed python and it caused the gui to go, so i installed gnome through tty1 and then later installed ubuntu-desktop . After this all these happened ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Dec 24 20:56:01 2018 DuplicateSignature: package:gir1.2-ibus-1.0:amd64:1.5.17-3ubuntu4 Removing gir1.2-ibus-1.0:amd64 (1.5.17-3ubuntu4) ... /var/lib/dpkg/info/gir1.2-ibus-1.0:amd64.prerm: 6: /var/lib/dpkg/info/gir1.2-ibus-1.0:amd64.prerm: py3clean: not found dpkg: error processing package gir1.2-ibus-1.0:amd64 (--remove): installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2018-12-17 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ibus Title: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1809709 Title: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 Status in ibus package in Ubuntu: New Bug description: I removed python and it caused the gui to go, so i installed gnome through tty1 and then later installed ubuntu-desktop . After this all these happened ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Dec 24 20:56:01 2018 DuplicateSignature: package:gir1.2-ibus-1.0:amd64:1.5.17-3ubuntu4 Removing gir1.2-ibus-1.0:amd64 (1.5.17-3ubuntu4) ... /var/lib/dpkg/info/gir1.2-ibus-1.0:amd64.prerm: 6: /var/lib/dpkg/info/gir1.2-ibus-1.0:amd64.prerm: py3clean: not found dpkg: error processing package gir1.2-ibus-1.0:amd64 (--remove): installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2018-12-17 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ibus Title: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1809709/+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 1807077] Re: [SRU] mountall crashes on udev node with missing devname
** Description changed: [Impact] - * udev block nodes without a devname will crash mountall, resulting in + * udev block nodes without a devname will crash mountall, resulting in an unbootable system (emergency root shell) - * While this is not likely to happen in a matched distro/kernel + * While this is not likely to happen in a matched distro/kernel environment (it was discovered while needing to run a bionic 4.15 kernel on trusty), it is possible. - * The code in try_udev_device() assumes a block subsystem will always + * The code in try_udev_device() assumes a block subsystem will always have a devname; the SRU patches explicitly check for a devname and return if null. [Test Case] - * HPE DL385 Gen10, Samsung a822 NVMe controller, trusty install + * HPE DL385 Gen10, Samsung a822 NVMe controller, trusty install - * Kernels <4.15 (or possibly 4.14) do not expose nvme0c33n1 and do not + * Kernels <4.15 (or possibly 4.14) do not expose nvme0c33n1 and do not trigger the bug. Tested on 4.13, 4.4 and 3.13. - * Kernel 4.15 exposes nvme0c33n1 in udev but does not have a devname, + * Kernel 4.15 exposes nvme0c33n1 in udev but does not have a devname, mountall crash ensues. [Regression Potential] - * Patch might ignore legitimate block devices on existing + * Patch might ignore legitimate block devices on existing installations. Unlikely, since the logic path for null devname leads directly to a program crash. [Other Info] - - * Additional context for Canonical employees: PS4.5 is a trusty backend cloud, but we now have Gen10 hardware incoming (this was discovered while adding new nova-compute hardware). Older kernels are not usable because Gen10 requires ilorest, which requires a >4.4 kernel (at least artful 4.13 is known good). So trusty+4.15 is the only viable combination for continued support of the cloud while adding new hardware. This is done via apt pinning of bionic for the kernel packages, and, mountall notwithstanding, is working fine so far. + + * Additional context for Canonical employees: PS4.5 is a trusty backend + cloud, but we now have Gen10 hardware incoming (this was discovered + while adding new nova-compute hardware). Older kernels are not usable + because Gen10 requires ilorest, which requires a >4.4 kernel (at least + artful 4.13 is known good). So trusty+4.15 is the only viable + combination for continued support of the cloud while adding new + hardware. This is done via apt pinning of bionic for the kernel + packages, and, mountall notwithstanding, is working fine so far. + + TEST CASE: + 1. Enable -proposed + 2. apt-get install mountall=2.53ubuntu1 + 3. update-initramfs -k all -u + 4. Reboot + + VERIFICATION DONE + Rebooted successfully on affected Gen10 systems. Confirmed no regression on unaffected systems. Original description: Running bionic's 4.15 kernel on trusty on an HPE DL385 Gen10 results in a device node for the NVMe controller, /devices/pci:40/:40:03.1/:43:00.0/nvme/nvme0/nvme0c33n1 which itself does not have a devname. When mountall gets to it: fsck_update: updating check priorities try_mount: /srv/nova/instances waiting for device try_udev_device: ignored /dev/loop5 (not yet ready?) try_udev_device: ignored /dev/loop6 (not yet ready?) try_udev_device: ignored /dev/loop1 (not yet ready?) try_udev_device: ignored /dev/loop0 (not yet ready?) try_udev_device: block (null) (null) (null) and then crashes, leaving the boot at an emergency root shell. A successful scan looks like this for comparison: try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sda (null) (null) try_udev_device: block /dev/nvme0n1 ed56e3a9-60f7-4636-85a2-b53137b598e7 (null) try_udev_device: block /dev/bcache0 756cb2c6-b999-4905-a021-c2e688e81a86 instances The debdiffs check for a null devname in try_udev_device() and will not attempt to process it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname Status in mountall package in Ubuntu: Invalid Status in mountall source package in Trusty: Fix Committed Status in mountall source package in Xenial: Won't Fix Bug description: [Impact] * udev block nodes without a devname will crash mountall, resulting in an unbootable system (emergency root shell) * While this is not likely to happen in a matched distro/kernel environment (it was discovered while needing to run a bionic 4.15 kernel on trusty), it is possible. * The code in try_udev_device() assumes a block subsystem will always have a devname; the SRU patches explicitly check for a devname and return if null. [Test Case] * HPE DL385 Gen10,
[Touch-packages] [Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname Status in mountall package in Ubuntu: Invalid Status in mountall source package in Trusty: Fix Committed Status in mountall source package in Xenial: Won't Fix Bug description: [Impact] * udev block nodes without a devname will crash mountall, resulting in an unbootable system (emergency root shell) * While this is not likely to happen in a matched distro/kernel environment (it was discovered while needing to run a bionic 4.15 kernel on trusty), it is possible. * The code in try_udev_device() assumes a block subsystem will always have a devname; the SRU patches explicitly check for a devname and return if null. [Test Case] * HPE DL385 Gen10, Samsung a822 NVMe controller, trusty install * Kernels <4.15 (or possibly 4.14) do not expose nvme0c33n1 and do not trigger the bug. Tested on 4.13, 4.4 and 3.13. * Kernel 4.15 exposes nvme0c33n1 in udev but does not have a devname, mountall crash ensues. [Regression Potential] * Patch might ignore legitimate block devices on existing installations. Unlikely, since the logic path for null devname leads directly to a program crash. [Other Info] * Additional context for Canonical employees: PS4.5 is a trusty backend cloud, but we now have Gen10 hardware incoming (this was discovered while adding new nova-compute hardware). Older kernels are not usable because Gen10 requires ilorest, which requires a >4.4 kernel (at least artful 4.13 is known good). So trusty+4.15 is the only viable combination for continued support of the cloud while adding new hardware. This is done via apt pinning of bionic for the kernel packages, and, mountall notwithstanding, is working fine so far. TEST CASE: 1. Enable -proposed 2. apt-get install mountall=2.53ubuntu1 3. update-initramfs -k all -u 4. Reboot VERIFICATION DONE Rebooted successfully on affected Gen10 systems. Confirmed no regression on unaffected systems. Original description: Running bionic's 4.15 kernel on trusty on an HPE DL385 Gen10 results in a device node for the NVMe controller, /devices/pci:40/:40:03.1/:43:00.0/nvme/nvme0/nvme0c33n1 which itself does not have a devname. When mountall gets to it: fsck_update: updating check priorities try_mount: /srv/nova/instances waiting for device try_udev_device: ignored /dev/loop5 (not yet ready?) try_udev_device: ignored /dev/loop6 (not yet ready?) try_udev_device: ignored /dev/loop1 (not yet ready?) try_udev_device: ignored /dev/loop0 (not yet ready?) try_udev_device: block (null) (null) (null) and then crashes, leaving the boot at an emergency root shell. A successful scan looks like this for comparison: try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sda (null) (null) try_udev_device: block /dev/nvme0n1 ed56e3a9-60f7-4636-85a2-b53137b598e7 (null) try_udev_device: block /dev/bcache0 756cb2c6-b999-4905-a021-c2e688e81a86 instances The debdiffs check for a null devname in try_udev_device() and will not attempt to process it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+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 1809692] [NEW] distorted lines when using google chrome browser
Public bug reported: I get dynamically changing distorted lines when using google chrome browser, I suppose it is due to my graphics card. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-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: Tue Dec 25 04:18:51 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07d0] InstallationDate: Installed on 2018-04-12 (256 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0c45:6717 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic.efi.signed root=UUID=72a3879f-b71f-40a0-b09b-ceb983af1dbf ro acpi_rev_override quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0D0XXK dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd01/30/2018:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn0D0XXK:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.name: Latitude 5480 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Dec 24 22:28:33 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1368 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1809692 Title: distorted lines when using google chrome browser Status in xorg package in Ubuntu: New Bug description: I get dynamically changing distorted lines when using google chrome browser, I suppose it is due to my graphics card. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-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: Tue Dec 25 04:18:51 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07d0] InstallationDate: Installed on 2018-04-12 (256 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b
[Touch-packages] [Bug 1699660] Re: systemd-resolve breaks resolution of local network hostnames
IIRC what could be happening is that the additional timeout introduced by systemd-resolved first doing the newly implemented LLMNR lookup (which fails if not implemented by any device) causes some network tools to not even try doing a DNS lookup using the DHCP- or user-supplied DNS search domain suffixes. The second invocation then maybe finds a cached result which is however invalidated after some time - thus the varying or seemingly random results. -- 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/1699660 Title: systemd-resolve breaks resolution of local network hostnames Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.04 (zesty), resolution of my local network's host names is completely broken. Apparently the upgrade replaced my existing resolver with systemd-resolve, which deliberately refuses to pass "single-label" domain names to my domain name server. That is the server where all my network's host names are kept, so I can no longer resolve any of them. Apparently, this is yet another example of Poettering's upstream decisions causing denial of service to people who have been saddled with his malware. https://github.com/systemd/systemd/issues/2514#issuecomment-179203186 Would someone sensible please put a stop to this forced breakage during upgrade, and advise on how to fix it now that the damage has been done? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699660/+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 1699660] Re: systemd-resolve breaks resolution of local network hostnames
Hi, Ubuntu 18.10 using systemd version 239-7ubuntu10.5: I also see random results for dot-less domain or host names, i.e. it seems after a certain timeout, a hostname is not found e.g. when trying to establish an SSH connection to that machine using a single-label name. Immediately followed by a second try however, all is working again. This looks like a time-out or caching issue. Quoting https://github.com/systemd/systemd/issues/6224#issuecomment-312639959: "LLMNR lookups for missing names need to time out (because it is a true multicasting peer-to-peer protocol, and a name that doesn't exist means that there's nobody responding to an LLMNR query), but the host command on the client side times out even earlier than that, and then doesn't continue with the search domains, as search domains have to be honoured client-side, i.e. inside the "host" command." I have now disabled LLMNR in /etc/systemd/resolved.conf and will observer in the next days if this changes the behaviour. ** Bug watch added: github.com/systemd/systemd/issues #6224 https://github.com/systemd/systemd/issues/6224 -- 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/1699660 Title: systemd-resolve breaks resolution of local network hostnames Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.04 (zesty), resolution of my local network's host names is completely broken. Apparently the upgrade replaced my existing resolver with systemd-resolve, which deliberately refuses to pass "single-label" domain names to my domain name server. That is the server where all my network's host names are kept, so I can no longer resolve any of them. Apparently, this is yet another example of Poettering's upstream decisions causing denial of service to people who have been saddled with his malware. https://github.com/systemd/systemd/issues/2514#issuecomment-179203186 Would someone sensible please put a stop to this forced breakage during upgrade, and advise on how to fix it now that the damage has been done? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699660/+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 1698979] Re: ftbfs with python 3.6
** Changed in: autopilot (Ubuntu)
Status: New => Triaged
** Changed in: autopilot (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1698979
Title:
ftbfs with python 3.6
Status in autopilot package in Ubuntu:
Triaged
Bug description:
Tests fail with Python 3.6:
==
FAIL:
autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_launcher_wrapper_raises_runtimeerror
--
Traceback (most recent call last):
File
"/<>/autopilot-1.6.0+17.04.20170313/autopilot/tests/unit/test_application_launcher.py",
line 1091, in test_get_application_launcher_wrapper_raises_runtimeerror
raises(RuntimeError(expected_error))
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 435, in
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: RuntimeError("Command '['ldd',
'autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_launcher_wrapper_raises_runtimeerror-1']'
returned non-zero exit status 1.",) has different arguments to
RuntimeError("Command '['ldd',
'autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_launcher_wrapper_raises_runtimeerror-1']'
returned non-zero exit status 1",).
==
FAIL:
autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_path_raises_when_cant_find_app
--
Traceback (most recent call last):
File
"/<>/autopilot-1.6.0+17.04.20170313/autopilot/tests/unit/test_application_launcher.py",
line 1076, in test_get_application_path_raises_when_cant_find_app
raises(ValueError(expected_error))
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 435, in
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: ValueError("Unable to find path for
application
autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_path_raises_when_cant_find_app-1:
Command '['which',
'autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_path_raises_when_cant_find_app-1']'
returned non-zero exit status 1.",) has different arguments to
ValueError("Unable to find path for application
autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_path_raises_when_cant_find_app-1:
Command '['which',
'autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_path_raises_when_cant_find_app-1']'
returned non-zero exit status 1",).
It's a bit hard to see but I think the difference is just that there
is a period at the end of the error messages now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1698979/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I managed to solve it in my Asus ZenBook UX433F. I'm running Ubuntu 18.04. I upgraded the Kernel to v4.19.11 as to Jorge Castro's answer to this question: https://askubuntu.com/questions/119080/how-to-update-kernel-to-the- latest-mainline-version-without-any-distro-upgrade Here are the exact steps I followed: 1. Download the appropriate files from: https://kernel.ubuntu.com/~kernel-ppa/mainline/ For example: linux-headers-4.19.11-041911_4.19.11-041911.201812191931_all.deb linux-headers-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb linux-image-unsigned-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb linux-modules-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb 2. Install each one in the appropriate order: sudo dpkg -i linux-headers-4.19.11-041911_4.19.11-041911.201812191931_all.deb sudo dpkg -i linux-headers-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb sudo dpkg -i linux-modules-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb sudo dpkg -i linux-image-unsigned-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb 3. Restart. In GRUB choose "Advanced options for Ubuntu". Select the new Kernel version. Cheers -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1779340] Re: systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge
My setup is a little bit different, but the problem is the same. I have a bridge device for LXD. This is an extra bridge for testing purpose. root@rapper:~# cat /etc/netplan/91-test-bridges.yaml network: version: 2 renderer: networkd bridges: # the key name is the name for virtual (created) interfaces; # no ‘match’ or ‘set-name’ attributes are allowed. testbr0: addresses: - 10.82.0.1/24 # gateway4: 192.168.178.1 At startup there are no containers using this bridge, and that causes the 2 minute timeout of systemd-networkd-wait-online root@rapper:~# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp2s0 ether carrier configured 3 testbr0 ether no-carrier configuring 4 br0 ether routableconfigured root@rapper:~# /lib/systemd/systemd-networkd-wait-online --timeout=20 --interface testbr0 ignoring: lo Event loop failed: Connection timed out I couldn't find a way to skip my test bridge for this online check, and still keep it controlled by networkd. -- 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/1779340 Title: systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge Status in systemd package in Ubuntu: Confirmed Bug description: The following simple netplan config results in a 2-minut unneccessary delay on boot. Everything works like it should in the end. The bridge has no interfaces due to a regression in Ubuntu migrating to netplan (see https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779341). ubuntu@molnix3:~$ cat /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more information, see netplan(5). network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: yes dhcp6: yes ubuntu@molnix3:~$ cat /etc/netplan/br1.yaml network: version: 2 bridges: br1: addresses: [10.1.0.9/16] interfaces: [] ubuntu@molnix3:~$ cat /usr/lib/networkd-dispatcher/routable.d/tap0 #!/bin/sh set -e if [ "$IFACE" = tap0 ]; then brctl addif br1 tap0 ip link set tap0 promisc on ifmetric tap0 5 fi ubuntu@molnix3:~$ journalctl -u systemd-networkd-wait-online.service -b -- Logs begin at Thu 2018-06-28 10:07:29 UTC, end at Fri 2018-06-29 14:09:18 UTC. -- Jun 29 13:58:16 molnix3 systemd[1]: Starting Wait for Network to be Configured... Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:19 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:21 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 14:00:16 molnix3 systemd-networkd-wait-online[1468]: Event loop failed: Connection timed out Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Jun 29 14:00:16 molnix3 systemd[1]: Failed to start Wait for Network to be Configured. ubuntu@molnix3:~$ /lib/systemd/systemd-networkd-wait-online managing: br1 managing: enp4s0 ignoring: lo ubuntu@molnix3:~$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp4s0 ether routableconfigured 3 br1 ether routableconfigured 4 tap0 ether routableunmanaged 4 links listed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779340/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1779340] Re: systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge
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/1779340 Title: systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge Status in systemd package in Ubuntu: Confirmed Bug description: The following simple netplan config results in a 2-minut unneccessary delay on boot. Everything works like it should in the end. The bridge has no interfaces due to a regression in Ubuntu migrating to netplan (see https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779341). ubuntu@molnix3:~$ cat /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more information, see netplan(5). network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: yes dhcp6: yes ubuntu@molnix3:~$ cat /etc/netplan/br1.yaml network: version: 2 bridges: br1: addresses: [10.1.0.9/16] interfaces: [] ubuntu@molnix3:~$ cat /usr/lib/networkd-dispatcher/routable.d/tap0 #!/bin/sh set -e if [ "$IFACE" = tap0 ]; then brctl addif br1 tap0 ip link set tap0 promisc on ifmetric tap0 5 fi ubuntu@molnix3:~$ journalctl -u systemd-networkd-wait-online.service -b -- Logs begin at Thu 2018-06-28 10:07:29 UTC, end at Fri 2018-06-29 14:09:18 UTC. -- Jun 29 13:58:16 molnix3 systemd[1]: Starting Wait for Network to be Configured... Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:19 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 13:58:21 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo Jun 29 14:00:16 molnix3 systemd-networkd-wait-online[1468]: Event loop failed: Connection timed out Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Jun 29 14:00:16 molnix3 systemd[1]: Failed to start Wait for Network to be Configured. ubuntu@molnix3:~$ /lib/systemd/systemd-networkd-wait-online managing: br1 managing: enp4s0 ignoring: lo ubuntu@molnix3:~$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp4s0 ether routableconfigured 3 br1 ether routableconfigured 4 tap0 ether routableunmanaged 4 links listed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779340/+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 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop
Bug is still present in 18.04 LTS. Very low sound/volume with this sound card in Ubuntu. Works fine in Windows 10. -- 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/1737614 Title: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I have a new laptop HP-15-BS576TX which has this Intel Corporation Sunrise Point-LP HD Audio. 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) The laptop sound works perfectly fine in Windows 10 with realtek drivers. However, in Ubuntu 17.10, the volume is significantly low, that I've to scroll the volume slider above 100% mark in pulseaudio to the maximum to get acceptable level of sound. I suspect the sound quality also is low (mono-like), may be not coming from all speakers (perhaps subwoofer exist for this model). Also alsamixer shows the speaker volume at the maximum. Details about the audio hardware are below: :~$ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Hewlett-Packard Company Device 832b Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- /proc/asound/card0/codec#0 <== Codec: Realtek ALC3227 ==> /proc/asound/card0/codec#2 <== Codec: Intel Kabylake HDMI :~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 I have gone through Linux kernel sources ALSA and Snd-HDA lists and unable to find any optimizations for this laptop. Here is the relevant dmesg details: [ 15.502856] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 16.310503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3227: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 16.310506] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 16.310507] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 16.310508] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 16.310509] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 16.310510] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 [ 16.310512] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 16.451397] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input9 [ 16.451451] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 16.451496] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 16.451538] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input12 [ 16.451581] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input13 [ 16.451624] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input14 [ 16.451687] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input15 Any further information needed, please let me know. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 [modified: usr/share/alsa-base/alsa-info.sh] ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: ndiswrapper ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admin2018 1246 F pulseaudio CurrentDesktop: GNOME Date: Tue Dec 12 00:46:12 2017 InstallationDate: Installed on 2017-11-22 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP
[Touch-packages] [Bug 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
Just had this happen again with a systemd-journald system problem error report. /var/crash/_lib_systemd_systemd-journald.0.crash: "Invalid core dump: BFD: warning: /tmp/apport_core_4z_uh8nz is truncated: expected core file size >= 18833408, found: 274432" apport log: ERROR: apport (pid 6651) Mon Dec 24 14:33:49 2018: called for pid 314, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 6651) Mon Dec 24 14:33:49 2018: executable: /lib/systemd/systemd-journald (command line "/lib/systemd/systemd-journald") ERROR: apport (pid 6651) Mon Dec 24 14:33:50 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6651) Mon Dec 24 14:45:33 2018: wrote report /var/crash/_lib_systemd_systemd-journald.0.crash ** Summary changed: - chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated + Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated Status in apport package in Ubuntu: New Status in chromium-browser package in Ubuntu: Invalid Bug description: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). UnreportableReason: Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: expected core file size >= 1245646848, found: 760283136 warning: core file may not match specified executable file. Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+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 1789924] Re: Missing Intel GPU pci-id's
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Cosmic) Status: New => Confirmed -- 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
Not much to go off of in the apport log ** Attachment added: "apport.log" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1808861/+attachment/5224676/+files/apport.log ** Changed in: apport (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated Status in apport package in Ubuntu: New Status in chromium-browser package in Ubuntu: Invalid Bug description: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). UnreportableReason: Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: expected core file size >= 1245646848, found: 760283136 warning: core file may not match specified executable file. Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+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 1809668] Re: packagekitd crashed with SIGABRT
*** This bug is a duplicate of bug 1796315 *** https://bugs.launchpad.net/bugs/1796315 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1796315, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1809668/+attachment/5224666/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224668/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224671/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224672/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224673/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224674/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224675/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1796315 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1809668 Title: packagekitd crashed with SIGABRT Status in packagekit package in Ubuntu: New Bug description: Don't know, apport just popped up randomly about it while I was working. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: packagekit 1.1.10-1ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sun Dec 23 03:35:46 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2018-09-27 (88 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/sh Signal: 6 SourcePackage: packagekit StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (46 days ago) UserGroups: modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1809668/+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 1809656] [NEW] Small windows output corrupted in XWayland clients
Public bug reported: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Снимок экрана от 2018-12-24 13-38-38.png" https://bugs.launchpad.net/bugs/1809656/+attachment/5224638/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202018-12-24%2013-38-38.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+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 1809653] Re: packagekitd crashed with SIGABRT
*** This bug is a duplicate of bug 1796315 *** https://bugs.launchpad.net/bugs/1796315 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1796315, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1809653/+attachment/5224624/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1809653/+attachment/5224626/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1809653/+attachment/5224630/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1809653/+attachment/5224631/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1809653/+attachment/5224632/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1809653/+attachment/5224633/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1809653/+attachment/5224634/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1796315 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1809653 Title: packagekitd crashed with SIGABRT Status in packagekit package in Ubuntu: New Bug description: Hello, Wat's this linux package ? wer's the bug ? Could you explain me ? Best regards Happy charisms Best regards Battant ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: packagekit 1.1.11-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu17 Architecture: amd64 CrashCounter: 1 Date: Mon Dec 24 11:50:06 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2018-09-04 (110 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: mtime.conffile..etc.apport.crashdb.conf: 2018-12-09T17:27:52.004901 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1809653/+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 1230374] Re: vi editor for loop syntax problem
** Package changed: gnome-terminal (Ubuntu) => vim (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1230374 Title: vi editor for loop syntax problem Status in vim package in Ubuntu: New Bug description: for (( i=0; i<=5; i++ )) do echo "$i Echoed" done this is what wrote in "bubble.sh" with vi editor and it gave me this error "bubble.sh: 1: bubble.sh: Syntax error: Bad for loop variable " i don't seem to understand why this is happening..please help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1230374/+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 1739948] Re: Missing French-Belgian keyboard layout
I actually had the same issue while trying to add the Belgian keyboard. I had to reload gnome-shell to get the Belgian input method despite I had several other French ones, and the Belgian regional settings. It's confusing that the Belgian layout does not appear automatically. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1739948 Title: Missing French-Belgian keyboard layout Status in ibus package in Ubuntu: New Bug description: Description: Ubuntu 17.10 Release: 17.10 ibus: Installed: 1.5.14-2ubuntu1 Candidate: 1.5.14-2ubuntu1 Version table: *** 1.5.14-2ubuntu1 500 500 http://be.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status After my update on 17.10 I couldn't get a french Belgian keyboard in the input sources. During install time I have tried to find my keyboard layout by using the "Type this key process" without success. I have also tried all the French keyboard but none of them allow me to type "@" or "-"... sut to mention main missing keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1739948/+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 941517] Re: libnfnetlink0« kann nicht geöffnet werden: Kein passendes Gerät bzw. keine passende Adresse gefunden
** Package changed: gnome-terminal (Ubuntu) => libnfnetlink (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnfnetlink in Ubuntu. https://bugs.launchpad.net/bugs/941517 Title: libnfnetlink0« kann nicht geöffnet werden: Kein passendes Gerät bzw. keine passende Adresse gefunden Status in libnfnetlink package in Ubuntu: New Bug description: libnfnetlink0« kann nicht geöffnet werden: Kein passendes Gerät bzw. keine passende Adresse gefunden ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Feb 26 17:47:55 2012 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2012-02-17 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnfnetlink/+bug/941517/+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 1230374] [NEW] vi editor for loop syntax problem
You have been subscribed to a public bug: for (( i=0; i<=5; i++ )) do echo "$i Echoed" done this is what wrote in "bubble.sh" with vi editor and it gave me this error "bubble.sh: 1: bubble.sh: Syntax error: Bad for loop variable " i don't seem to understand why this is happening..please help ** Affects: vim (Ubuntu) Importance: Undecided Status: New -- vi editor for loop syntax problem https://bugs.launchpad.net/bugs/1230374 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim 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 941517] [NEW] libnfnetlink0« kann nicht geöffnet werden: Kein passendes Gerät bzw. keine passende Adresse gefunden
You have been subscribed to a public bug: libnfnetlink0« kann nicht geöffnet werden: Kein passendes Gerät bzw. keine passende Adresse gefunden ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Feb 26 17:47:55 2012 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2012-02-17 (9 days ago) ** Affects: libnfnetlink (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi oneiric running-unity -- libnfnetlink0« kann nicht geöffnet werden: Kein passendes Gerät bzw. keine passende Adresse gefunden https://bugs.launchpad.net/bugs/941517 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnfnetlink 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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hey Dennis, the value you put in RESUME variable must match your logical volume path. /dev/vg_system/lv_swap matches mine, but yours might be different. Check with lvdisplay what is the name of your logical volume and then use it inside the resume file. -- 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: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Confirmed 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
