[Touch-packages] [Bug 1792294] Re: Generates unbootable initrd: Out of Memory Error
This bug seems to be fixed in the latest release (0.131ubuntu15). -- 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/1792294 Title: Generates unbootable initrd: Out of Memory Error Status in initramfs-tools package in Ubuntu: New Bug description: I am currently using Cosmic (which is not released yet) and version 0.131ubuntu10 of "initramfs-tools" always generates unbootable initrd. After I select the kernel to boot during GRUB it says: "Loading initial ramdisk... Error: Out of memory". And then it halts forever. This issue appears on all kernel versions. The system is on UEFI + GPT. Note that I don't have a swap partition on my system, but I don't think it's the cause. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: initramfs-tools 0.131ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 13 13:36:35 2018 InstallationDate: Installed on 2018-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: initramfs-tools 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/1792294/+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 1798740] Re: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1
Degraded systemctl is probably irrelevant. It was fixed with `dpkg- reconfigure postfix`. -- 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/1798740 Title: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Happened during upgrade to release 18.10. I am using xubuntu. It was reported an issue with systemd during upgrade. Then it took much time (6 hours or more) to reach final error about problem with upgrade and rollback message. Seems systemd was not working during upgrade. After restart it's state is degraded in `systemctl status`. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 05:04:56 2018 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-07-24 (451 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 2320EPG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: systemd Title: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) dmi.bios.date: 09/25/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2320EPG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn2320EPG:pvrThinkPadX230:rvnLENOVO:rn2320EPG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2320EPG dmi.product.sku: LENOVO_MT_2320 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1798740/+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 1798740] Re: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1
Degraded systemctl is probably irrelevant. It was fixed with `dpkg- reconfigure postfix`. -- 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/1798740 Title: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Happened during upgrade to release 18.10. I am using xubuntu. It was reported an issue with systemd during upgrade. Then it took much time (6 hours or more) to reach final error about problem with upgrade and rollback message. Seems systemd was not working during upgrade. After restart it's state is degraded in `systemctl status`. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 05:04:56 2018 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-07-24 (451 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 2320EPG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: systemd Title: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) dmi.bios.date: 09/25/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2320EPG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn2320EPG:pvrThinkPadX230:rvnLENOVO:rn2320EPG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2320EPG dmi.product.sku: LENOVO_MT_2320 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1798740/+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 1644666] Re: Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
According to https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1750937?comments=all a fix for this Problem has been released. ** Changed in: xorg (Ubuntu) Status: Confirmed => In Progress ** Changed in: xorg (Ubuntu) Status: In Progress => Fix Released -- 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/1644666 Title: Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop Status in xorg package in Ubuntu: Fix Released Bug description: Ubuntu 16.04.1 (Automatic Upgrade from 14.04) My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): Nvidia C61 [GeForce 7025 / nForce 630a] --- In the Past: => System and Apps worked well with Auto-Login enabled. To eliminate Hardware-Errors: > Memtest > Boot with Windows-XP => No Problems Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart) -- 1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop 2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen --- I don't know in which Category to sort the Bugs So this one is for the (Nr.1) Login-Loop (from tty-Terminal) (I already filed another Bug-Report for the (Nr.2) System-(Freeze)-Crash with Stripes-Screen) First Problem startet on 2016-Nov-05: => Login-Loop --- I later found out, that one Day before, the following Auto-Updates had been installed: --- libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2) nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2) nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2) libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2) --- After Shutdown, the next Computer-Start was stuck in a => Login-Loop: After entering the correct Password, the Screen turns black for a Second, then the Login-Form shows up again. --- I tried a few things, that did not help, like: > CTRL+F2 => Terminal > sudo .. > apt autoclean > apt clean > apt autoremove > apt update > apt upgrade > apt dist-upgrade > shutdown -r now > mv .Xauthority .Xauthority.alt > shutdown -r now > service lightdm restart > shutdown -r now > apt purge lightdm > apt install lightdm > shutdown -r now > .. Boot into different Linux-Kernel, .. (upstart), > .. Boot into Recovery-Mode > .. > Repair > .. > .. I also tried to install other nvidia-drivers, which, sadly, i did not document. => Did NOT work --- Only Thing that helped was: --- > sudo apt purge nvidia-* > sudo shutdown -r now => (nouveau-Driver was automatically installed) => Auto-Login to Desktop But then there was a second Problem: When > starting Thunderbird, mostly at once, sometimes after > opening some E-Mail-Windows, another Error occurred: => System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => Total (Freeze-)Crash -- Later, even with DISabled Hardware-Acceleration, starting both, Firefox and Thunderbird led to the System-Crash. (Sometimes, the System with nouveau booted and auto-logined into a Black Screen with a Mouse-Pointer. Nevertheless the System seemed to work and could be rebooted normally.) --- > CTRL+ALT+F2 => did NOT work > Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work > ping to IP => unreachable --- After cold Reboot, i tried again to switch back from nouveau- to nvidia-Drivers > Additional Drivers > Nvidia-304.132 => Login-Loop --- > sudo apt purge nvidia-* > sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau => Auto-Login > Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen --- > .. removed and tried to install the old driver (I probably did wrong): > sudo apt purge nvidia-* > sudo add-apt-repository ppa:graphics-drivers/ppa > sudo apt update > sudo apt install nvidia-current=304.131-0ubuntu3 => Login-Loop --- > sudo apt purge nvidia-* > Additional Drivers > nouveau > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 4.4.0-47-generic" (NO Option=SYSTEMD?) => Auto-Login > Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen What seemed to help was: > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 4.4.0-47-generic (upstart)" (UPSTART!) => Auto-Login > Firefox / Thunderbird => seem to work stable! => After half an Hour of testing: > open Firefox (Hardware-Acceleration disabled) => System-(Freeze)-Crash with Stripes-Screen - Because this is far more stable: Changed Standard-Boot in Grub-2 to UpStart instead of SystemD --- > Terminal > sudo apt install upstart-sysv su sudo shutd
[Touch-packages] [Bug 1798740] Re: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1
Eventually I see no errors. -- 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/1798740 Title: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Happened during upgrade to release 18.10. I am using xubuntu. It was reported an issue with systemd during upgrade. Then it took much time (6 hours or more) to reach final error about problem with upgrade and rollback message. Seems systemd was not working during upgrade. After restart it's state is degraded in `systemctl status`. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 05:04:56 2018 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-07-24 (451 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 2320EPG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: systemd Title: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) dmi.bios.date: 09/25/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2320EPG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn2320EPG:pvrThinkPadX230:rvnLENOVO:rn2320EPG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2320EPG dmi.product.sku: LENOVO_MT_2320 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1798740/+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 1798778] [NEW] package fdisk 2.31.1-0.4ubuntu3.1 failed to install/upgrade: unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error
Public bug reported: I was installing ubuntu on my new laptop using a USB and i faced that ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fdisk 2.31.1-0.4ubuntu3.1 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 Date: Fri Oct 19 11:53:42 2018 DpkgTerminalLog: Preparing to unpack .../fdisk_2.31.1-0.4ubuntu3.2_amd64.deb ... Unpacking fdisk (2.31.1-0.4ubuntu3.2) over (2.31.1-0.4ubuntu3.1) ... dpkg: error processing archive /var/cache/apt/archives/fdisk_2.31.1-0.4ubuntu3.2_amd64.deb (--unpack): unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error DuplicateSignature: package:fdisk:2.31.1-0.4ubuntu3.1 Unpacking fdisk (2.31.1-0.4ubuntu3.2) over (2.31.1-0.4ubuntu3.1) ... dpkg: error processing archive /var/cache/apt/archives/fdisk_2.31.1-0.4ubuntu3.2_amd64.deb (--unpack): unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error ErrorMessage: unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 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.3 SourcePackage: util-linux Title: package fdisk 2.31.1-0.4ubuntu3.1 failed to install/upgrade: unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (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 util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1798778 Title: package fdisk 2.31.1-0.4ubuntu3.1 failed to install/upgrade: unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error Status in util-linux package in Ubuntu: New Bug description: I was installing ubuntu on my new laptop using a USB and i faced that ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fdisk 2.31.1-0.4ubuntu3.1 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 Date: Fri Oct 19 11:53:42 2018 DpkgTerminalLog: Preparing to unpack .../fdisk_2.31.1-0.4ubuntu3.2_amd64.deb ... Unpacking fdisk (2.31.1-0.4ubuntu3.2) over (2.31.1-0.4ubuntu3.1) ... dpkg: error processing archive /var/cache/apt/archives/fdisk_2.31.1-0.4ubuntu3.2_amd64.deb (--unpack): unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error DuplicateSignature: package:fdisk:2.31.1-0.4ubuntu3.1 Unpacking fdisk (2.31.1-0.4ubuntu3.2) over (2.31.1-0.4ubuntu3.1) ... dpkg: error processing archive /var/cache/apt/archives/fdisk_2.31.1-0.4ubuntu3.2_amd64.deb (--unpack): unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error ErrorMessage: unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 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.3 SourcePackage: util-linux Title: package fdisk 2.31.1-0.4ubuntu3.1 failed to install/upgrade: unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1798778/+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 1670959] Re: systemd-resolved using 100% CPU
This annoying bug affected all upgrades to Bionic and Cosmic Cuttlefish
I did so far and also effects Cosmic Cuttlefish. systemd-resolv and
dnsmasq consume each 100% CPU and internet access becomes extremely
slow.
My latest workaround is to disable automatic overwriting to
/etc/resolf.conf with sudo dpkg-reconfigure resolvconf, and to replaced
the spurious nameserver 127.0.01 in /etc/resolv.conf with nameserver
8.8.8.8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
Status in dnsmasq package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Sometimes systemd-resolved process is using 100% CPU.
After a while it changes back to normal.
It happens usually after connecting to the (wifi) network, like
starting the OS.
strace output:
sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}],
msg_flags=0}, 0) = 81
sendmsg(3, {msg_name(0)=NULL,
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}},
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0)
= 53
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\365I", 2, GRND_NONBLOCK)= 2
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\203;", 2, GRND_NONBLOCK)= 2
clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
connect(18, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576,
u64=94565471566608}}) = 0
write(18,
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
53) = 53
clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL) = 0
close(18) = 0
journalctl output:
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS
queries reached (max: 150)
As you can see, I would use it together with dnsmasq.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-18ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Wed Mar 8 08:20:18 2017
MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
SourcePackage: systemd
Upgrade
[Touch-packages] [Bug 1798778] Re: package fdisk 2.31.1-0.4ubuntu3.1 failed to install/upgrade: unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1798778 Title: package fdisk 2.31.1-0.4ubuntu3.1 failed to install/upgrade: unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error Status in util-linux package in Ubuntu: New Bug description: I was installing ubuntu on my new laptop using a USB and i faced that ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fdisk 2.31.1-0.4ubuntu3.1 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 Date: Fri Oct 19 11:53:42 2018 DpkgTerminalLog: Preparing to unpack .../fdisk_2.31.1-0.4ubuntu3.2_amd64.deb ... Unpacking fdisk (2.31.1-0.4ubuntu3.2) over (2.31.1-0.4ubuntu3.1) ... dpkg: error processing archive /var/cache/apt/archives/fdisk_2.31.1-0.4ubuntu3.2_amd64.deb (--unpack): unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error DuplicateSignature: package:fdisk:2.31.1-0.4ubuntu3.1 Unpacking fdisk (2.31.1-0.4ubuntu3.2) over (2.31.1-0.4ubuntu3.1) ... dpkg: error processing archive /var/cache/apt/archives/fdisk_2.31.1-0.4ubuntu3.2_amd64.deb (--unpack): unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error ErrorMessage: unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 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.3 SourcePackage: util-linux Title: package fdisk 2.31.1-0.4ubuntu3.1 failed to install/upgrade: unable to make backup link of './sbin/sfdisk' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1798778/+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 1770429] Re: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3
same problem when i upgraded from 18.04 to 18.10 pactl load-module module-detect helped -- 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/1770429 Title: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3 Status in alsa-driver package in Ubuntu: Confirmed Bug description: I updated my Surface Pro 3 From Ubuntu 17.10 to Ubuntu 18.04 (did a clean install) and the only audio working was from the headphone jack. I tried all these: [troubleshooting guide](https://help.ubuntu.com/community/SoundTroubleshootingProcedure) [this answer](https://askubuntu.com/questions/117842/no-sound-from-speakers-but-headphones-work) [another answer](https://askubuntu.com/questions/829520/ubuntu-16-04-no-sound-from-speakers-only-headphones-working) I went back and tested the live CD and even the live cd has no audio through the speakers. so this must be related to 18.04. I never had sound issues before and under windows audio still works correctly. here is my alsa iformation http://www.alsa- project.org/db/?f=8bf135db52610a603014779ef24041a491c8a32d and here is how I fixed it: renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa- base.bk , then rebooting the computer fixed the my speaker sound issue. I then restored line by line in to /etc/modprobe.d/alsa-base.conf, rebooting between restored lines, until all lines were back and ... it still worked! so I restored the original /etc/modprobe.d/alsa-base.conf and rebooted the computer and everything was still working so I am not sure what the problem was but is now fixed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carlosr2267 F pulseaudio /dev/snd/controlC0: carlosr2267 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 10 10:15:29 2018 InstallationDate: Installed on 2018-04-27 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.2350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2350:bd01/23/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.family: Surface dmi.product.name: Surface Pro 3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-09T14:04:13.313882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1770429/+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
Re: [Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
Thanks for the solution :) Tim On Friday, 19 October 2018, 02:06:26 GMT+1, Duane Ellis <1754...@bugs.launchpad.net> wrote: for an Explanation of the problem, and a work around see: https://github.com/GitTools/GitVersion/issues/1508 the problem started with libcurl3 having an incorrect symlink named: 'libcurl.so.4' ** Bug watch added: github.com/GitTools/GitVersion/issues #1508 https://github.com/GitTools/GitVersion/issues/1508 -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798797] [NEW] Drucker
Public bug reported: Kompliziert ... Ich möchte nur den Drucker zum laufen bringen. Zeigt an, Drucker druckt nicht. Bei Ubuntu 16.4 ist alles einwandfrei gelaufen... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Fri Oct 19 12:21:45 2018 DistUpgraded: 2018-10-17 18:15:17,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:365d] InstallationDate: Installed on 2018-03-08 (224 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 6596 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ae1dcc47-b3c8-4069-bedd-acb8c12fdbfb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-17 (1 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: LENOVO dmi.bios.version: EKKT25BUS dmi.board.name: Remore CRB dmi.board.vendor: LENOVO dmi.board.version: Win8 STD MM DPK IPG dmi.chassis.type: 13 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrEKKT25BUS:bd08/28/2012:svnLENOVO:pn6596:pvrLenovoC445:rvnLENOVO:rnRemoreCRB:rvrWin8STDMMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.: dmi.product.family: IdeaCentre dmi.product.name: 6596 dmi.product.version: Lenovo C445 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 17 11:04:23 2018 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 ** 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/1798797 Title: Drucker Status in xorg package in Ubuntu: New Bug description: Kompliziert ... Ich möchte nur den Drucker zum laufen bringen. Zeigt an, Drucker druckt nicht. Bei Ubuntu 16.4 ist alles einwandfrei gelaufen... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Fri Oct 19 12:21:45 2018 DistUpgraded: 2018-10-17 18:15:17,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:365d] InstallationDate: Installed on 2018-03-08 (224 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 6596 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ae1dcc47-b3c8-4069-bedd-acb8c12fdbfb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-17 (1 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: LENOVO dmi.bios.version: EKKT25BUS dmi.board.name: Remore CRB dmi.board.vendor: LENOVO dmi.board.version: Win8 STD MM DPK IPG dmi.chassis.type: 13 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrEKKT25BUS:bd08/28/2012:svnLENOVO:pn6596:pvrLenovoC445:rvnLENOVO:rnRemoreCRB:rvrWin8STDMMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO
[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
I guess every sysadmin installing an agent-based configuration management system via di will experience this problem, too. Funny how there was no progress on this in half a year. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1798740] Re: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1
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/1798740 Title: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Confirmed Bug description: Happened during upgrade to release 18.10. I am using xubuntu. It was reported an issue with systemd during upgrade. Then it took much time (6 hours or more) to reach final error about problem with upgrade and rollback message. Seems systemd was not working during upgrade. After restart it's state is degraded in `systemctl status`. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 05:04:56 2018 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-07-24 (451 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 2320EPG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: systemd Title: package systemd 239-7ubuntu10 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) dmi.bios.date: 09/25/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2320EPG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn2320EPG:pvrThinkPadX230:rvnLENOVO:rn2320EPG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2320EPG dmi.product.sku: LENOVO_MT_2320 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1798740/+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 1795407] Re: python-apt frontend locking
FTR, with the locking with statement, without the SRU, it fails, as
expected (both in bionic and xenial), e.g.:
dpkg: error: dpkg status database is locked by another process
E:Sub-process /usr/bin/dpkg returned an error code (2)
Traceback (most recent call last):
File "/home/jak/Projects/Ubuntu/Scratch/foo.py", line 11, in
c.commit()
File "/usr/lib/python3/dist-packages/apt/cache.py", line 610, in commit
raise SystemError("installArchives() failed")
SystemError: installArchives() failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1795407
Title:
python-apt frontend locking
Status in python-apt package in Ubuntu:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
Fix Committed
Bug description:
[Impact]
Add support to python-apt for frontend locking. This is a bit more
complicated, and also requires some other restructuring:
(1) The archives lock was only taken for a short time, when it should
have been kept for the duration of an installation, as otherwise debs
could disappear from archives/ while the install is running.
(2) There was no lock handling at all. Tools essentially acquire the
lock, and then release it before commit().
The fix is based on the apt fix, which makes apt_pkg.SystemLock()
manage both the frontend and the normal lock, and allows code to call
apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner()
around dpkg invocations to release the inner lock.
Cache.commit() takes care of locking itself now. It releases the inner
lock as needed for dpkg invocations. It also now requires
apt_pkg.SystemLock to be hold - if it is not, it will acquire it
itself.
[Test case]
1. Mark a package in the cache for install/removal and commit() - FE lock
should be taken while dpkg is running.
2. Mark a package in the cache for install/removal and commit() while holding
the lock. Releasing the lock afterwards should still work correctly, and the FE
lock should never be released
3. Observe that the archive lock is not released until the last dpkg run
The locking behavior can be observed via strace.
[Regression potential]
The dpkg lock changed the most: Some lock counting might go wrong and
programs might fail as a result. Any problems will be isolated, though - dpkg
still acquires its locks, and if a lock miscount happens, apt would not tell
dpkg to skip acquiring the frontend lock, so even if we were losing the lock
anywhere, dpkg would still try to acquire it and not run unlocked.
The archive lock done by commit()/fetch_archives() in apt.Cache() is
now hold as long as the fetcher object exists though (as it uses the
fetcher's get_lock method), which might cause unexpected behavior in
apps not expecting that.
The lists/ lock is unaffected by the changes, so there should not be
any regressions when it comes to updating index files.
[Other info (1)]
CI changes: There were some improvements to type hints for mypy needed to
make type checks pass, and changes to the CI's Dockerfile to pull a new apt
from the apt stable PPA (as a new enough apt is only in unapproved atm).
Neither of those files are used anywhere outside of the package, so they should
not cause any problems.
[Other info (2)]
This is part of a wider series of SRUs for frontend locking
- dpkg (bug 1796081)
- apt (bug 1781169)
- python-apt (bug 1795407)
- packagekit (bug 1795614)
- unattended-upgrades (bug 1789637)
- aptdaemon (no bug filed yet)
Further details about frontend locking can be found in
https://lists.debian.org/debian-dpkg/2017/01/msg00044.html
- This SRU depends on the apt SRU above, and breaks unattended-
upgrades in bionic without its SRU due to a bug in the u-u code in
handling the new API.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 1795407] Re: python-apt frontend locking
bionic 1.6.3: 1. Verified that the lock is hold during dpkg run added lslocks to aptitude prerm: $ lxc exec bbb -- strace -o $PWD/log -e openat,open,close,fcntl python3 $PWD/foo.py (Reading database ... 28970 files and directories currently installed.) Removing aptitude (0.8.10-6ubuntu1) ... COMMAND PID TYPE SIZE MODE M START END PATH atd 198 POSIX 4B WRITE 0 0 0 /run/atd.pid python3 2751 POSIX 0B WRITE 0 0 0 /var/lib/dpkg/lock-frontend python3 2751 POSIX 0B WRITE 0 0 0 /var/cache/apt/archives/lock cron 196 FLOCK 4B WRITE 0 0 0 /run/crond.pid dpkg 2761 POSIX 0B WRITE 0 0 0 /var/lib/dpkg/lock Removing aptitude-common (0.8.10-6ubuntu1) ... Processing triggers for man-db (2.8.3-2) ... 2. With system lock helt in my script: #!/usr/bin/python3 import apt, apt_pkg c = apt.Cache() if c["aptitude-common"].is_installed: c["aptitude-common"].mark_delete() else: c["aptitude-common"].mark_install() with apt_pkg.SystemLock(): c.commit() $ lxc exec bbb -- strace -o $PWD/log.locked -e openat,open,close,fcntl python3 $PWD/foo.py (Reading database ... 28970 files and directories currently installed.) Removing aptitude (0.8.10-6ubuntu1) ... COMMAND PID TYPE SIZE MODE M START END PATH atd 198 POSIX 4B WRITE 0 0 0 /run/atd.pid dpkg 3106 POSIX 0B WRITE 0 0 0 /var/lib/dpkg/lock cron 196 FLOCK 4B WRITE 0 0 0 /run/crond.pid python3 3096 POSIX 0B WRITE 0 0 0 /var/lib/dpkg/lock-frontend python3 3096 POSIX 0B WRITE 0 0 0 /var/cache/apt/archives/lock Removing aptitude-common (0.8.10-6ubuntu1) ... Processing triggers for man-db (2.8.3-2) ... Works fine. 3. Investigating strace also shows that the lock-frontend is acquired once, and not released until the end. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Bug description: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. [Other info (1)] CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. [Other info (2)] This is part of a wider series of SRUs for f
[Touch-packages] [Bug 1795407] Re: python-apt frontend locking
Same for xenial (1.1.0~beta1ubuntu0.16.04.3).
Also, strace logs look like this, in case we want to see how we can be
sure it's kept locked all the time:
[...]
open("/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 39
fcntl(39, F_SETFD, FD_CLOEXEC) = 0
fcntl(39, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 40
fcntl(40, F_SETFD, FD_CLOEXEC) = 0
fcntl(40, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
open("/var/lib/dpkg/updates/", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 41
close(41) = 0
close(41) = 0
close(41) = 0
open("/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/lib/x86_64-linux-gnu/libnss_compat.so.2", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/lib/x86_64-linux-gnu/libnsl.so.1", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/lib/x86_64-linux-gnu/libnss_nis.so.2", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/lib/x86_64-linux-gnu/libnss_files.so.2", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
close(41) = 0
close(41) = 0
open("/etc/group", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/etc/group", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/var/lib/apt/lists/partial", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) =
41
close(41) = 0
open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/etc/group", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/var/cache/apt/archives/partial",
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 41
close(41) = 0
open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/etc/group", O_RDONLY|O_CLOEXEC) = 41
close(41) = 0
open("/var/cache/apt/archives/partial",
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 41
close(41) = 0
open("/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 41
fcntl(41, F_SETFD, FD_CLOEXEC) = 0
fcntl(41, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 42
close(42) = 0
open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 42
close(42) = 0
close(40) = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=6098, si_uid=0,
si_status=0, si_utime=6, si_stime=3} ---
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 40
fcntl(40, F_SETFD, FD_CLOEXEC) = 0
fcntl(40, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
close(39) = 0
[ ... more closes ... ]
+++ exited with 0 +++
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1795407
Title:
python-apt frontend locking
Status in python-apt package in Ubuntu:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
Fix Committed
Bug description:
[Impact]
Add support to python-apt for frontend locking. This is a bit more
complicated, and also requires some other restructuring:
(1) The archives lock was only taken for a short time, when it should
have been kept for the duration of an installation, as otherwise debs
could disappear from archives/ while the install is running.
(2) There was no lock handling at all. Tools essentially acquire the
lock, and then release it before commit().
The fix is based on the apt fix, which makes apt_pkg.SystemLock()
manage both the frontend and the normal lock, and allows code to call
apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner()
around dpkg invocations to release the inner lock.
Cache.commit() takes care of locking itself now. It releases the inner
lock as needed for dpkg invocations. It also now requires
apt_pkg.SystemLock to be hold - if it is not, it will acquire it
its
[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Easy workaround which does not require another apt-setup.udeb: d-i preseed/late_commandstring \ in-target wget -q -O /etc/apt/trusted.gpg.d/bla.asc http://bla.de/bla.asc ; \ in-target sed -i '/keyword to uncomment specific line in file/s/^# *//' /etc/apt/sources.list ; \ in-target apt-get update ; \ in-target apt-get -y install packages to install ; -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1798808] [NEW] Canon ts202 does not print
Public bug reported: It is listed on the USB. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4ubuntu0.5 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: Unity Date: Fri Oct 19 06:01:46 2018 InstallationDate: Installed on 2016-05-06 (896 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) Lpstat: device for Canon-TS200-series: usb://Canon/TS200%20series?serial=508E03 device for HP-Officejet-Pro-8600-FAX: usb://HP/Officejet%20Pro%208600%20FAX?serial=CN248BT18X05KC&interface=3 device for Officejet-Pro-8600: hp:/usb/Officejet_Pro_8600?serial=CN248BT18X05KC MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Officejet-Pro-8600-FAX.ppd', '/etc/cups/ppd/Canon-TS200-series.ppd', '/etc/cups/ppd/Officejet-Pro-8600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Officejet-Pro-8600-FAX.ppd: Permission denied grep: /etc/cups/ppd/Canon-TS200-series.ppd: Permission denied grep: /etc/cups/ppd/Officejet-Pro-8600.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-137-generic root=UUID=daa1b19a-2288-41ef-8f2e-981af0d06013 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: C70M1 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd03/04/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnC70M1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1798808 Title: Canon ts202 does not print Status in cups package in Ubuntu: New Bug description: It is listed on the USB. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4ubuntu0.5 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: Unity Date: Fri Oct 19 06:01:46 2018 InstallationDate: Installed on 2016-05-06 (896 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) Lpstat: device for Canon-TS200-series: usb://Canon/TS200%20series?serial=508E03 device for HP-Officejet-Pro-8600-FAX: usb://HP/Officejet%20Pro%208600%20FAX?serial=CN248BT18X05KC&interface=3 device for Officejet-Pro-8600: hp:/usb/Officejet_Pro_8600?serial=CN248BT18X05KC MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Officejet-Pro-8600-FAX.ppd', '/etc/cups/ppd/Canon-TS200-series.ppd', '/etc/cups/ppd/Officejet-Pro-8600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Officejet-Pro-8600-FAX.ppd: Permission denied grep: /etc/cups/ppd/Canon-TS200-series.ppd: Permission denied grep: /etc/cups/ppd/Officejet-Pro-8600.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-137-generic root=UUID=daa1b19a-2288-41ef-8f2e-981af0d06013 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: C70M1 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd03/04/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnC70M1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1798808/+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 1752053] Re: nvidia-390 fails to boot graphical display
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia- driver-390) -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1798656] Re: gtk3 frontend gives no widget for answering a boolean prompt
** Tags added: id-5bc8d8d314a23f6c8499198e -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1798656 Title: gtk3 frontend gives no widget for answering a boolean prompt Status in debconf package in Ubuntu: New Bug description: On upgrade from bionic to cosmic with update-manager, I was shown a debconf prompt about docker.io that asked: Automatically restart Docker daemon? There was no widget in the window that allowed me to select either yes or no. This is a grave deficiency in the default debconf frontend on the Ubuntu desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1798656/+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 1798657] Re: gtk3 frontend 'help' window is huge and not resizeable
** Tags added: id-5bc8da67e4137c26d1f5d350 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1798657 Title: gtk3 frontend 'help' window is huge and not resizeable Status in debconf package in Ubuntu: New Bug description: If I click on 'help' on a debconf question when using the gtk3 frontend, I get a huge window with a 'close' button in the bottom right corner and a small amount of text in the middle of the screen. The window can be resized horizontally, but not vertically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1798657/+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 1742912] Re: Please confine guest sessions again
** Tags added: id-5a57962350afc7d4aa391919 -- 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/1742912 Title: Please confine guest sessions again Status in lightdm package in Ubuntu: Confirmed Bug description: This is a continuation of LP: #1663157 where as a workaround for the guest session not being confined the session got disabled. This bug tracks the fix for proper confinement. Original bug report text: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1742912/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
I'm very much in favor of this. Does this imply an update to Apache 2.4.37, too? (see https://github.com/apache/httpd/blob/2.4.x/CHANGES) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: Confirmed Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via security updates * TLS v1.3 support in GnuTLS is expected to be available in 19.04 * Test OpenSSL is being prepared in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+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 1781440] Re: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wayland (Ubuntu) Status: New => Confirmed -- 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/1781440 Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 Status in wayland package in Ubuntu: Confirmed Bug description: Occured when upgrading from Bionic to Cosmic. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-dev 1.15.0-2 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Thu Jul 12 18:41:26 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224e] InstallationDate: Installed on 2018-02-07 (155 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207) MachineType: LENOVO 20JDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=150ad8bc-1d20-4de9-a767-b2b0679455f3 ro quiet splash acpi_osi= vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: wayland Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET33W(1.20):bd10/26/2017:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 2nd dmi.product.name: 20JDCTO1WW dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1781440/+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 1794957] Re: pipelining on archive.u.c aborts after 101 packages
** Description changed: [Impact] Downloading many packages on archive.ubuntu.com or some other mirrors seems to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1 (commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure with a 200 response as meaning that the server does not support pipelining, hence disabling it for any further downloads. With high speed connections at higher latency, this can cause a severe reduction in usable bandwidth. For example, I saw speeds drop from 40 MB/s to 15 MB/s due to this. The fix ensures that we continue pipelining if the previous connection to the server successfully retrieved at least 3 files with pipelining enabled. [Test case] Pick a package that would cause a large number (200/300 packages of packages to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run apt install -d $package. Ensure that after the first 101 packages the progress does not slow down - you should not see a lot "working" in the progress output. The speed should be substantially higher. Don't run in a container setup by cloud-init, as cloud-init disables pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see bug 1794982). Requirements: - * High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is enough) + * High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is enough); or just increase latency, e.g. +sudo tc qdisc add dev wlp61s0 root netem delay 300ms + until you see the slow down * Not a terribly slow CPU, as we'd get slowed down by hashing otherwise [Regression potential] This fix is isolated to code enabling/disabling pipelining on subsequent connections. It could cause more pipelining to be tried on servers who are not particularly good at it, but can deal with 3 items correctly. -- 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/1794957 Title: pipelining on archive.u.c aborts after 101 packages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] Downloading many packages on archive.ubuntu.com or some other mirrors seems to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1 (commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure with a 200 response as meaning that the server does not support pipelining, hence disabling it for any further downloads. With high speed connections at higher latency, this can cause a severe reduction in usable bandwidth. For example, I saw speeds drop from 40 MB/s to 15 MB/s due to this. The fix ensures that we continue pipelining if the previous connection to the server successfully retrieved at least 3 files with pipelining enabled. [Test case] Pick a package that would cause a large number (200/300 packages of packages to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run apt install -d $package. Ensure that after the first 101 packages the progress does not slow down - you should not see a lot "working" in the progress output. The speed should be substantially higher. Don't run in a container setup by cloud-init, as cloud-init disables pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see bug 1794982). Requirements: * High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is enough); or just increase latency, e.g. sudo tc qdisc add dev wlp61s0 root netem delay 300ms until you see the slow down * Not a terribly slow CPU, as we'd get slowed down by hashing otherwise [Regression potential] This fix is isolated to code enabling/disabling pipelining on subsequent connections. It could cause more pipelining to be tried on servers who are not particularly good at it, but can deal with 3 items correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+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 1771185] Re: Secondary monitor not connecting in 18.04 LTS
I have a dell inspiron 15 5000 2 in 1, Running ubuntu 18.04, and I am also affected by this bug. I have a DELL U2414M monitor. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-2 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x258) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x259) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x25a) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz 1920x1080i (0x25b) 74.250MHz +HSync +VSync Interlace h: width 1920 start 2008 end 2052 total 2200 skew0 clock 33.75KHz v: height 1080 start 1084 end 1
[Touch-packages] [Bug 1778984] Re: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades
I have just hit this problem on Ubuntu 18.04, and I was able to solve it by
running
root@ubuntu:~# sudo dpkg-reconfigure apparmor
Unlike the previous poster, I am not aware of any sudden powercycles. I
simply attempted to run a docker container. The docker command and
output are below, with PII redacted.
docker run --rm -v /home/[REDACTED]/projects/snap/out/log:/log -v
/home/[REDACTED]/projects/snap/django:/tmslogs -v
/home/[REDACTED]/projects/snap/out/db:/db -v
/home/[REDACTED]/projects/snap/out/media:/media -v
/home/[REDACTED]/projects/snap/out/dumps:/dumps -v
/home/[REDACTED]/projects/snap/config:/config -t -i
[REDACTED].com/tmslogs:latest /bin/bash
docker: Error response from daemon: AppArmor enabled on system but the
docker-default profile could not be loaded: running
`/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-
default964375229` failed with output: AppArmor parser error for
/var/lib/docker/tmp/docker-default964375229 in
/etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected
character: ''
root@ubuntu:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"
root@ubuntu:~# uname -a
Linux ubuntu 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu:~# docker --version
Docker version 17.12.1-ce, build 7390fc6
root@ubuntu:~# cat /etc/apparmor.d/tunables/home.d/ubuntu
# This file is auto-generated. It is recommended you update it using:
# $ sudo dpkg-reconfigure apparmor
#
# The following is a space-separated list of where additional user home
# directories are stored, each must have a trailing '/'. Directories added
# here are appended to @{HOMEDIRS}. See tunables/home for details.
root@ubuntu:~#
I followed the hint in /etc/apparmor.d/tunables/home.d/ubuntu and ran
root@ubuntu:~# sudo dpkg-reconfigure apparmor
This solved the problem.
After this solved the problem, this reminded me that I have modified my
/home directories. After installing Ubuntu 18.04 and creating my
default user account, I logged in and mounted a second drive into
'/home'. Perhaps anyone looking into this issue, or experiencing this
issue could take this clue and run with it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1778984
Title:
Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after
unattended-upgrades
Status in apparmor package in Ubuntu:
New
Bug description:
Environment:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL="http://help.ubuntu.com/";
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Docker Details:
Client:
Version: 17.06.2-ce
API version: 1.30
Go version: go1.8.3
Git commit: cec0b72
Built:Tue Sep 5 20:00:17 2017
OS/Arch: linux/amd64
Server:
Version: 17.06.2-ce
API version: 1.30 (minimum version 1.12)
Go version: go1.8.3
Git commit: cec0b72
Built:Tue Sep 5 19:59:11 2017
OS/Arch: linux/amd64
Experimental: false
Problem: Docker containers will not restart due error
/etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: ''
How to recreate problem:
1. initiate unattended upgrades: sudo unattened-upgrades -d
2. Wait until Apparmor is installing...
Installing new version of config file /etc/init.d/apparmor ...
Installing new version of config file /etc/init/apparmor.conf ...
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
3. Pull the power from the computer to simulate a complete power failure.
4. Plug the system back in and try to restart a docker container using "sudo
docker restart
Error upon attempting to restart docker container:
Error response from daemon: Cannot restart container updater-nodejs: AppArmor
enabled on system but the docker-default profile could not be loaded: running
/sbin/apparmor_parser apparmor_parser -Kr
/var/lib/docker/tmp/docker-default480199246 failed with output: AppArmor parser
error for /var/lib/docker/tmp/docker-default480199246 in
/etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: ''
error: exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1778984/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~t
[Touch-packages] [Bug 1778984] Re: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades
Clarification: I followed the hint in /etc/apparmor.d/tunables/home.d/ubuntu and ran root@ubuntu:~# sudo dpkg-reconfigure apparmor In the window that popped up, I added "/home/" (which is the location of my home directories) and clicked OK. This solved the problem -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1778984 Title: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades Status in apparmor package in Ubuntu: New Bug description: Environment: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial Docker Details: Client: Version: 17.06.2-ce API version: 1.30 Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 20:00:17 2017 OS/Arch: linux/amd64 Server: Version: 17.06.2-ce API version: 1.30 (minimum version 1.12) Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 19:59:11 2017 OS/Arch: linux/amd64 Experimental: false Problem: Docker containers will not restart due error /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' How to recreate problem: 1. initiate unattended upgrades: sudo unattened-upgrades -d 2. Wait until Apparmor is installing... Installing new version of config file /etc/init.d/apparmor ... Installing new version of config file /etc/init/apparmor.conf ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd 3. Pull the power from the computer to simulate a complete power failure. 4. Plug the system back in and try to restart a docker container using "sudo docker restart Error upon attempting to restart docker container: Error response from daemon: Cannot restart container updater-nodejs: AppArmor enabled on system but the docker-default profile could not be loaded: running /sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default480199246 failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default480199246 in /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' error: exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1778984/+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 1794957] Re: pipelining on archive.u.c aborts after 101 packages
** Attachment added: "bionic: network bandwidth before (1.6.3ubuntu0.1)" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+attachment/5203090/+files/Screenshot%20from%202018-10-19%2015-55-47.png -- 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/1794957 Title: pipelining on archive.u.c aborts after 101 packages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] Downloading many packages on archive.ubuntu.com or some other mirrors seems to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1 (commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure with a 200 response as meaning that the server does not support pipelining, hence disabling it for any further downloads. With high speed connections at higher latency, this can cause a severe reduction in usable bandwidth. For example, I saw speeds drop from 40 MB/s to 15 MB/s due to this. The fix ensures that we continue pipelining if the previous connection to the server successfully retrieved at least 3 files with pipelining enabled. [Test case] Pick a package that would cause a large number (200/300 packages of packages to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run apt install -d $package. Ensure that after the first 101 packages the progress does not slow down - you should not see a lot "working" in the progress output. The speed should be substantially higher. Don't run in a container setup by cloud-init, as cloud-init disables pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see bug 1794982). Requirements: * High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is enough); or just increase latency, e.g. sudo tc qdisc add dev wlp61s0 root netem delay 300ms until you see the slow down * Not a terribly slow CPU, as we'd get slowed down by hashing otherwise [Regression potential] This fix is isolated to code enabling/disabling pipelining on subsequent connections. It could cause more pipelining to be tried on servers who are not particularly good at it, but can deal with 3 items correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+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 1794957] Re: pipelining on archive.u.c aborts after 101 packages
Same for xenial; 1.2.27 shows the symptoms, and the 1.2.29 SRU fixes them. Not going to attach more images or text as it basically looks identical. ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-xenial -- 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/1794957 Title: pipelining on archive.u.c aborts after 101 packages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] Downloading many packages on archive.ubuntu.com or some other mirrors seems to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1 (commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure with a 200 response as meaning that the server does not support pipelining, hence disabling it for any further downloads. With high speed connections at higher latency, this can cause a severe reduction in usable bandwidth. For example, I saw speeds drop from 40 MB/s to 15 MB/s due to this. The fix ensures that we continue pipelining if the previous connection to the server successfully retrieved at least 3 files with pipelining enabled. [Test case] Pick a package that would cause a large number (200/300 packages of packages to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run apt install -d $package. Ensure that after the first 101 packages the progress does not slow down - you should not see a lot "working" in the progress output. The speed should be substantially higher. Don't run in a container setup by cloud-init, as cloud-init disables pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see bug 1794982). Requirements: * High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is enough); or just increase latency, e.g. sudo tc qdisc add dev wlp61s0 root netem delay 300ms until you see the slow down * Not a terribly slow CPU, as we'd get slowed down by hashing otherwise [Regression potential] This fix is isolated to code enabling/disabling pipelining on subsequent connections. It could cause more pipelining to be tried on servers who are not particularly good at it, but can deal with 3 items correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+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 1794957] Re: pipelining on archive.u.c aborts after 101 packages
Here is a short graphical comparison of before/after in the bionic SRU in a container. I modified the container's network bridge to add 300ms delay using sudo tc qdisc add dev lxdbr0 root netem delay 300ms which made things quite more visible on a slower 12 Mbit/s connection. I could clearly see that _without_ the 1.6.6 SRU, speed dropped a lot after the first 100 (101?) packages were fetched, you could see in the progress that it fetched one file and then started fetching the next one. In contrast, with the SRU installed, progress sometimes shows lines with multiple files very quickly; i.e. it drains the entire pipe of 10 items in what feels like one update of the progress output. You can also see this in the pictures: In the old graph, network speed has a sudden drop in the middle; in the second picture (which was running a bit longer, so it starts more on the left), you see that performance can be sustained. ** Attachment added: "bionic: network bandwidth after (1.6.6)" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+attachment/5203091/+files/Screenshot%20from%202018-10-19%2015-57-57.png -- 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/1794957 Title: pipelining on archive.u.c aborts after 101 packages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] Downloading many packages on archive.ubuntu.com or some other mirrors seems to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1 (commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure with a 200 response as meaning that the server does not support pipelining, hence disabling it for any further downloads. With high speed connections at higher latency, this can cause a severe reduction in usable bandwidth. For example, I saw speeds drop from 40 MB/s to 15 MB/s due to this. The fix ensures that we continue pipelining if the previous connection to the server successfully retrieved at least 3 files with pipelining enabled. [Test case] Pick a package that would cause a large number (200/300 packages of packages to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run apt install -d $package. Ensure that after the first 101 packages the progress does not slow down - you should not see a lot "working" in the progress output. The speed should be substantially higher. Don't run in a container setup by cloud-init, as cloud-init disables pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see bug 1794982). Requirements: * High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is enough); or just increase latency, e.g. sudo tc qdisc add dev wlp61s0 root netem delay 300ms until you see the slow down * Not a terribly slow CPU, as we'd get slowed down by hashing otherwise [Regression potential] This fix is isolated to code enabling/disabling pipelining on subsequent connections. It could cause more pipelining to be tried on servers who are not particularly good at it, but can deal with 3 items correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
I would love to be able to Use OpenSSL 1.1.1 (TLS 1.3) with Apache2 on 18.04 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: Confirmed Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via security updates * TLS v1.3 support in GnuTLS is expected to be available in 19.04 * Test OpenSSL is being prepared in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+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 1797872] Re: ntpd keeps Soliciting pool server
It is transmitting and receiving, so it doesn't look like it is blocked: Looking for host 0.ubuntu.pool.ntp.org and service ntp host found : 85.199.214.102 transmit(85.199.214.102) receive(85.199.214.102) transmit(145.239.118.233) receive(145.239.118.233) transmit(139.162.219.252) receive(139.162.219.252) transmit(185.53.93.157) receive(185.53.93.157) transmit(85.199.214.102) receive(85.199.214.102) transmit(145.239.118.233) receive(145.239.118.233) transmit(139.162.219.252) receive(139.162.219.252) transmit(185.53.93.157) receive(185.53.93.157) transmit(85.199.214.102) receive(85.199.214.102) transmit(145.239.118.233) receive(145.239.118.233) transmit(139.162.219.252) receive(139.162.219.252) transmit(185.53.93.157) receive(185.53.93.157) transmit(85.199.214.102) receive(85.199.214.102) transmit(145.239.118.233) receive(145.239.118.233) transmit(139.162.219.252) receive(139.162.219.252) transmit(185.53.93.157) receive(185.53.93.157) server 85.199.214.102, port 123 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1797872 Title: ntpd keeps Soliciting pool server Status in ntp package in Ubuntu: New Bug description: ntpd keeps printing "Soliciting pool server" in the syslog (once every 5 seconds). $ ntpq -c pe remote refid st t when poll reach delay offset jitter == 0.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 1.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 2.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 3.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 ntp.ubuntu.com .POOL. 16 p- 6400.0000.000 0.000 $ sudo ntpq -c rv associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart, version="ntpd 4.2.8p4@1.3265-o Fri Jul 6 20:10:51 UTC 2018 (1)", processor="x86_64", system="Linux/4.15.0-33-generic", leap=11, stratum=16, precision=-24, rootdelay=0.000, rootdisp=0.360, refid=INIT, reftime=. Thu, Feb 7 2036 6:28:16.000, clock=df6ee808.934d239d Mon, Oct 15 2018 11:18:48.575, peer=0, tc=3, mintc=3, offset=0.00, frequency=6.224, sys_jitter=0.00, clk_jitter=0.000, clk_wander=0.000 I have changed nothing in the default configuration of ntp or the firewall. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.9 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 15 11:17:45 2018 InstallationDate: Installed on 2018-04-20 (177 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1797872/+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 1797872] Re: ntpd keeps Soliciting pool server
Both of them work. I don't understand how the last command can work and I may still be behind a firewall. Also: $ timedatectl status Network time on: yes NTP synchronized: yes So it seems it is synchronized, it just re-tries too frequently. ** Changed in: ntp (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1797872 Title: ntpd keeps Soliciting pool server Status in ntp package in Ubuntu: New Bug description: ntpd keeps printing "Soliciting pool server" in the syslog (once every 5 seconds). $ ntpq -c pe remote refid st t when poll reach delay offset jitter == 0.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 1.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 2.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 3.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 ntp.ubuntu.com .POOL. 16 p- 6400.0000.000 0.000 $ sudo ntpq -c rv associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart, version="ntpd 4.2.8p4@1.3265-o Fri Jul 6 20:10:51 UTC 2018 (1)", processor="x86_64", system="Linux/4.15.0-33-generic", leap=11, stratum=16, precision=-24, rootdelay=0.000, rootdisp=0.360, refid=INIT, reftime=. Thu, Feb 7 2036 6:28:16.000, clock=df6ee808.934d239d Mon, Oct 15 2018 11:18:48.575, peer=0, tc=3, mintc=3, offset=0.00, frequency=6.224, sys_jitter=0.00, clk_jitter=0.000, clk_wander=0.000 I have changed nothing in the default configuration of ntp or the firewall. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.9 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 15 11:17:45 2018 InstallationDate: Installed on 2018-04-20 (177 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1797872/+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 1798839] [NEW] Canonical Livepatch doesn't appear in "Updates" tab.
Public bug reported: Livepatch was working and appearing fine in 'Software & Updates' until after the upgrade from Ubuntu 18.04 LTS to Ubuntu 18.10; Livepatch does not appear as an option anymore after upgrading. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-gtk 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 11:04:03 2018 InstallationDate: Installed on 2018-08-17 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic cosmic -- 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/1798839 Title: Canonical Livepatch doesn't appear in "Updates" tab. Status in software-properties package in Ubuntu: New Bug description: Livepatch was working and appearing fine in 'Software & Updates' until after the upgrade from Ubuntu 18.04 LTS to Ubuntu 18.10; Livepatch does not appear as an option anymore after upgrading. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-gtk 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 11:04:03 2018 InstallationDate: Installed on 2018-08-17 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1798839/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xkeyboard-config (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1798839] Re: Canonical Livepatch doesn't appear in "Updates" tab.
Livepatch is only available for LTS releases of Ubuntu. That is why the option has been removed. -- 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/1798839 Title: Canonical Livepatch doesn't appear in "Updates" tab. Status in software-properties package in Ubuntu: New Bug description: Livepatch was working and appearing fine in 'Software & Updates' until after the upgrade from Ubuntu 18.04 LTS to Ubuntu 18.10; Livepatch does not appear as an option anymore after upgrading. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-gtk 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 11:04:03 2018 InstallationDate: Installed on 2018-08-17 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1798839/+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 1798212] Re: systemd stuck in uninterruptible sleep state
** Changed in: systemd (Ubuntu) Importance: Undecided => High -- 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/1798212 Title: systemd stuck in uninterruptible sleep state Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 systemd 229 may get stuck in an uninterruptible sleep state. Any subsequent systemctl command times out with "Failed to execute operation: Connection timed out" error message. gdb and strace is unable to attach to systemd process 1. $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN $ cat /proc/1/stack [<0>] flush_work+0x129/0x1e0 [<0>] flush_delayed_work+0x3f/0x50 [<0>] fsnotify_wait_marks_destroyed+0x15/0x20 [<0>] fsnotify_destroy_group+0x48/0xd0 [<0>] inotify_release+0x1e/0x50 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x8a/0xb0 [<0>] exit_to_usermode_loop+0xc4/0xd0 [<0>] do_syscall_64+0xf4/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x $ cat /proc/1/status Name: systemd Umask: State:D (disk sleep) Tgid: 1 Ngid: 0 Pid: 1 PPid: 0 TracerPid:9724 Uid: 0 0 0 0 Gid: 0 0 0 0 FDSize: 128 Groups: NStgid: 1 NSpid:1 NSpgid: 1 NSsid:1 VmPeak: 251136 kB VmSize: 185728 kB VmLck: 0 kB VmPin: 0 kB VmHWM:6620 kB VmRSS:6264 kB RssAnon: 2380 kB RssFile: 3884 kB RssShmem:0 kB VmData: 18752 kB VmStk: 132 kB VmExe:1392 kB VmLib:3692 kB VmPTE: 128 kB VmSwap: 0 kB HugetlbPages:0 kB CoreDumping: 0 Threads: 1 SigQ: 1/257098 SigPnd: 0004 ShdPnd: 0001 SigBlk: 7be3c0fe28014a03 SigIgn: 1000 SigCgt: 000184ec CapInh: CapPrm: 003f CapEff: 003f CapBnd: 003f CapAmb: NoNewPrivs: 0 Seccomp: 0 Speculation_Store_Bypass: vulnerable Cpus_allowed: Cpus_allowed_list:0-31 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0003 Mems_allowed_list:0-1 voluntary_ctxt_switches: 716968 nonvoluntary_ctxt_switches: 9565 $ dmesg [...] [1255076.993707] INFO: task systemd:1 blocked for more than 120 seconds. [1255077.000295] Not tainted 4.15.0-32-generic #35~16.04.1-Ubuntu [1255077.006804] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [1255077.014996] systemd D0 1 0 0x [1255077.015000] Call Trace: [1255077.015011] __schedule+0x3d6/0x8b0 [1255077.015019] ? enqueue_entity+0x112/0x670 [1255077.015021] schedule+0x36/0x80 [1255077.015025] schedule_timeout+0x1db/0x370 [1255077.015028] ? check_preempt_curr+0x54/0x90 [1255077.015030] ? ttwu_do_wakeup+0x1e/0x150 [1255077.015033] wait_for_completion+0xb4/0x140 [1255077.015035] ? wake_up_q+0x70/0x70 [1255077.015040] flush_work+0x129/0x1e0 [1255077.015043] ? worker_detach_from_pool+0xb0/0xb0 [1255077.015045] flush_delayed_work+0x3f/0x50 [1255077.015052] fsnotify_wait_marks_destroyed+0x15/0x20 [1255077.015055] fsnotify_destroy_group+0x48/0xd0 [1255077.015058] inotify_release+0x1e/0x50 [1255077.015063] __fput+0xea/0x220 [1255077.015065] fput+0xe/0x10 [1255077.015068] task_work_run+0x8a/0xb0 [1255077.015074] exit_to_usermode_loop+0xc4/0xd0 [1255077.015077] do_syscall_64+0xf4/0x130 [1255077.015080] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1255077.015084] RIP: 0033:0x7f29c9c3457d [1255077.015085] RSP: 002b:7ffec956fe30 EFLAGS: 0293 ORIG_RAX: 0003 [1255077.015088] RAX: RBX: 0010 RCX: 7f29c9c3457d [1255077.015090] RDX: RSI: RDI: 0010 [1255077.015092] RBP: 7f29cb36d700 R08: 5625f0043420 R09: 0001 [1255077.015093] R10: R11: 0293 R12: 000b [1255077.015095] R13: 5625eeed6040 R14: 5625eff179b8 R15: 5625eeed7460 [1255077.015421] INFO: task kworker/u66:2:108669 blocked for more than 120 seconds. [1255077.022960] Not tainted 4.15.0-32-generic #35~16.04.1-Ubuntu
[Touch-packages] [Bug 1798861] [NEW] Tooltips flicker constantly in GTK3 applications
Public bug reported: Tooltips are flicker constantly (i.e. repeatedly shown and the hidden again) in GTK3 applications under XFCE. It is a regression in the recent GTK 3.24. This is the upstream report and fix: https://gitlab.gnome.org/GNOME/gtk/issues/1371 https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2 A workaround for XFCE is as follows: Open Settings Editor. Set xsettings -> Gtk -> CursorThemeSize to 16. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgtk-3-0 3.24.1-1ubuntu2 Uname: Linux 4.19.0-041900rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 12:23:53 2018 InstallationDate: Installed on 2017-02-01 (624 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1798861 Title: Tooltips flicker constantly in GTK3 applications Status in gtk+3.0 package in Ubuntu: New Bug description: Tooltips are flicker constantly (i.e. repeatedly shown and the hidden again) in GTK3 applications under XFCE. It is a regression in the recent GTK 3.24. This is the upstream report and fix: https://gitlab.gnome.org/GNOME/gtk/issues/1371 https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2 A workaround for XFCE is as follows: Open Settings Editor. Set xsettings -> Gtk -> CursorThemeSize to 16. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgtk-3-0 3.24.1-1ubuntu2 Uname: Linux 4.19.0-041900rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 12:23:53 2018 InstallationDate: Installed on 2017-02-01 (624 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+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 1798867] [NEW] Compiz Crashed with SIGSEGV [Radeon]
You have been subscribed to a public bug: Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the issue in mid-July of 2018. System: Acer 5100 Ubuntu 16.04 (64-bit) Graphics card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] Believed to be mesa-related, as symptoms very similar to bug #1741447 and #1735594. I have been informed by a mesa developer that my issue is different because that bug affects Intel GPUs. This system has a Radeon GPU. Log files are as attached to bug #1795709. That bug was declared invalid by Apport because it says I don't have the necessary debug packages installed. However, I could not find the debug packages in the repository, so that is why I am submitting this report manually. Many thanks for any help. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- Compiz Crashed with SIGSEGV [Radeon] https://bugs.launchpad.net/bugs/1798867 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa 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 1798868] [NEW] Compiz Crashed with SIGSEGV [Radeon]
Public bug reported: Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the issue in mid-July of 2018. System: Acer 5100 Ubuntu 16.04 (64-bit) Graphics card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] Believed to be mesa-related, as symptoms very similar to bug #1741447 and #1735594. I have been informed by a mesa developer that my issue is different because that bug affects Intel GPUs. This system has a Radeon GPU. Log files are as attached to bug #1795709. That bug was declared invalid by Apport because it says I don't have the necessary debug packages installed. However, I could not find the debug packages in the repository, so that is why I am submitting this report manually. Many thanks for any help. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1798868 Title: Compiz Crashed with SIGSEGV [Radeon] Status in mesa package in Ubuntu: New Bug description: Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the issue in mid-July of 2018. System: Acer 5100 Ubuntu 16.04 (64-bit) Graphics card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] Believed to be mesa-related, as symptoms very similar to bug #1741447 and #1735594. I have been informed by a mesa developer that my issue is different because that bug affects Intel GPUs. This system has a Radeon GPU. Log files are as attached to bug #1795709. That bug was declared invalid by Apport because it says I don't have the necessary debug packages installed. However, I could not find the debug packages in the repository, so that is why I am submitting this report manually. Many thanks for any help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1798868/+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 1798867] [NEW] Compiz Crashed with SIGSEGV [Radeon]
Public bug reported: Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the issue in mid-July of 2018. System: Acer 5100 Ubuntu 16.04 (64-bit) Graphics card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] Believed to be mesa-related, as symptoms very similar to bug #1741447 and #1735594. I have been informed by a mesa developer that my issue is different because that bug affects Intel GPUs. This system has a Radeon GPU. Log files are as attached to bug #1795709. That bug was declared invalid by Apport because it says I don't have the necessary debug packages installed. However, I could not find the debug packages in the repository, so that is why I am submitting this report manually. Many thanks for any help. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Invalid ** Package changed: compiz (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1798867 Title: Compiz Crashed with SIGSEGV [Radeon] Status in mesa package in Ubuntu: Invalid Bug description: Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the issue in mid-July of 2018. System: Acer 5100 Ubuntu 16.04 (64-bit) Graphics card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] Believed to be mesa-related, as symptoms very similar to bug #1741447 and #1735594. I have been informed by a mesa developer that my issue is different because that bug affects Intel GPUs. This system has a Radeon GPU. Log files are as attached to bug #1795709. That bug was declared invalid by Apport because it says I don't have the necessary debug packages installed. However, I could not find the debug packages in the repository, so that is why I am submitting this report manually. Many thanks for any help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1798867/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
@Mario: Wanted you to know that I saw your objection, but too late.. Sorry. Let's deal with it in the beginning of the 19.04 cycle. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
No worries, as the Dell shows it seems not a no-brainer anyway, so better to postpone. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
@Eric, i just tested what you suggested at your comment #31 with Ubuntu 18.10 release ... KERNEL http://pxe-server/nfs/ubuntu-x64/casper/vmlinuz INITRD http://pxe-server/nfs/ubuntu-x64/casper/initrd APPEND nfsroot=192.168.1.1:/srv/nfs/ubuntu-x64 ro netboot=nfs file=/cdrom/preseed/ubuntu.seed boot=casper systemd.mask=dev-hugepages.mount -- debian-installer/language=de console-setup/layoutcode=de keyboard-configuration/layoutcode=de keyboard-configuration/variant=German ... but then i again run straight into emergency console. (not sure, if that information still is helpful) at the moment "systemd.mask=tmp.mount" still is the best solution. but with the issues of: - having few red "FAILED" messages at boot time; - at reboot/poweroff often run into "stop jobs" are running endless at shutting down; - or hangs for ever at "Starting Shuts down the 'live' preinstalled system clearly..."; the second best solution is "toram", there i never observed the issues of any "FAILED" message and never hat the issues at reboot/poweroff (maybe there are race conditions - "toram" nothing has to be loaded fron nfs via network). but "toram" takes a lot of time, because the whole squashfs-image has to be loaded into ram first, before it can be mounted. BTW: lununtu 18.10 shows the same behavior as ubuntu 18.10, but it does not show up the issues with reboot/poweroff hanging or endles running stop jobs. -- 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/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Daemon' dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") fuse: device not found, try 'modprobe fuse' first dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Metadata' (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed A connection to the bus can't be made done. Begin: Setting up init... ... done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+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 1798884] [NEW] Upgrade or install fails 1:7.2p2-4ubuntu2.5
Public bug reported: Today I've got an update to openssh-server version 1:7.2p2-4ubuntu2.5 but installation fails. Also when I purge the package and install it again, I get the same error message: openssh-server (1:7.2p2-4ubuntu2.5) wird eingerichtet ... insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "start" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fr 2018-10-19 20:53:49 CEST; 12ms ago Process: 29682 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Process: 29678 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Main PID: 29682 (code=exited, status=255) Okt 19 20:53:48 zulu1451.server4you.de systemd[1]: Starting OpenBSD Secure Shell server... Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Main process exited, code=code=exited, status=255/n/a Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: Failed to start OpenBSD Secure Shell server. Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Unit entered failed state. Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: Fehler beim Bearbeiten des Paketes openssh-server (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von ssh: ssh hängt ab von openssh-server (>= 1:7.2p2-4ubuntu2.5); aber: Paket openssh-server ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes ssh (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert Fehler traten auf beim Bearbeiten von: openssh-server ssh The system is: Description:Ubuntu 16.04.5 LTS Release:16.04 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1798884 Title: Upgrade or install fails 1:7.2p2-4ubuntu2.5 Status in openssh package in Ubuntu: New Bug description: Today I've got an update to openssh-server version 1:7.2p2-4ubuntu2.5 but installation fails. Also when I purge the package and install it again, I get the same error message: openssh-server (1:7.2p2-4ubuntu2.5) wird eingerichtet ... insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "start" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fr 2018-10-19 20:53:49 CEST; 12ms ago Process: 29682 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Process: 29678 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Main PID: 29682 (code=exited, status=255) Okt 19 20:53:48 zulu1451.server4you.de systemd[1]: Starting OpenBSD Secure Shell server... Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Main process exited, code=code=exited, status=255/n/a Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: Failed to start OpenBSD Secure Shell server. Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Unit entered failed state. Okt 19 20:53:49 zulu1451.server4you.de systemd[1]: ssh.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: Fehler beim Bearbeiten des Paketes openssh-server (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von ssh: ssh hängt ab von openssh-server (>= 1:7.2p2-4ubuntu2.5); aber: Paket openssh-server ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes ssh (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert Fehler traten auf beim Bearbeiten von: openssh-server ssh The system is: Description:Ubuntu 16.04.5 LTS Release:16.04 To manage notifications abou
[Touch-packages] [Bug 1798883] [NEW] Ubuntu 18.04 LTS: pam_systemd: Failure to create session under heavy I/O load
Public bug reported: I have a file server running Ubuntu 18.04 LTS which has strange behavior with systemd and dbus during heavy I/O load. The file server is set up with RAID60 with mdadm serving via NFS. When I/O load becomes high, it appears that dbus and systemd-logind are slowing down for SSH connections and I lose SSH connectivity due to login failure with pam_systemd: Oct 19 11:14:56 nfsserver sshd[20635]: pam_systemd(sshd:session): Failed to create session: Connection timed out Oct 19 11:15:06 nfsserver sshd[20821]: pam_systemd(sshd:session): Failed to create session: Connection timed out Oct 19 11:15:06 nfsserver sshd[20837]: pam_systemd(sshd:session): Failed to create session: Connection timed out Oct 19 12:05:58 nfsserver sshd[25143]: pam_systemd(sshd:session): Failed to create session: Connection timed out Oct 19 13:03:07 nfsserver sshd[47296]: pam_systemd(sshd:session): Failed to release session: Connection timed out Oct 19 13:05:39 nfsserver sshd[48532]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying Oct 19 13:05:39 nfsserver sshd[48570]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without rep CPU load gets near 50 or 60%, but not 100%. Looking through bug reports and issues that others have experienced with previous versions, it seems that when systemd-logind doesn't process the IPC queue from dbus fast enough, dbus will kick systemd-logind resulting in this failure. This appears to be so in socket statistics whereby the dbus IPC Send-Q fills and does not move during heavy load: Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port u_str ESTAB 0 153088 /var/run/dbus/system_bus_socket -2002184190 * -2002209306 The Recv-Q on the other end does not keep up: Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port u_str ESTAB 37892 0 * -2002209306 * -2002184190 I have tried to renice dbus, systemd, systemd-logind without success. The only way to resolve this issue is to reduce I/O load. Any thoughts? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1798883 Title: Ubuntu 18.04 LTS: pam_systemd: Failure to create session under heavy I/O load Status in systemd package in Ubuntu: New Bug description: I have a file server running Ubuntu 18.04 LTS which has strange behavior with systemd and dbus during heavy I/O load. The file server is set up with RAID60 with mdadm serving via NFS. When I/O load becomes high, it appears that dbus and systemd-logind are slowing down for SSH connections and I lose SSH connectivity due to login failure with pam_systemd: Oct 19 11:14:56 nfsserver sshd[20635]: pam_systemd(sshd:session): Failed to create session: Connection timed out Oct 19 11:15:06 nfsserver sshd[20821]: pam_systemd(sshd:session): Failed to create session: Connection timed out Oct 19 11:15:06 nfsserver sshd[20837]: pam_systemd(sshd:session): Failed to create session: Connection timed out Oct 19 12:05:58 nfsserver sshd[25143]: pam_systemd(sshd:session): Failed to create session: Connection timed out Oct 19 13:03:07 nfsserver sshd[47296]: pam_systemd(sshd:session): Failed to release session: Connection timed out Oct 19 13:05:39 nfsserver sshd[48532]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying Oct 19 13:05:39 nfsserver sshd[48570]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without rep CPU load gets near 50 or 60%, but not 100%. Looking through bug reports and issues that others have experienced with previous versions, it seems that when systemd-logind doesn't process the IPC queue from dbus fast enough, dbus will kick systemd-logind resulting in this failure. This appears to be so in socket statistics whereby the dbus IPC Send-Q fills and does not move during heavy load: Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port u_str ESTAB 0 153088 /var/run/dbus/system_bus_socket -2002184190 * -2002209306 The Recv-Q on the other end does not keep up: Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port u_str ESTAB 37892 0 * -2002209306 * -2002184190 I have tried to renice dbus, systemd, systemd-logind without success. The only way to resolve this issue is to reduce I/O load. Any thoughts? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1798883/+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 1768026] Re: echo message hides cursor
Please update the package! It breaks vim for ale users, which surely make up a significant percentage of serious users. -- 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/1768026 Title: echo message hides cursor Status in vim: Fix Released Status in vim package in Ubuntu: Confirmed Bug description: https://github.com/w0rp/ale/issues/1536#issuecomment-385056702 upstream bug https://github.com/vim/vim/issues/2612 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1 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: Mon Apr 30 14:16:35 2018 InstallationDate: Installed on 2017-05-17 (347 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-04-26 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1768026/+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 1765832] Re: Two finger scrolling not working after suspend
*** This bug is a duplicate of bug 1722478 *** https://bugs.launchpad.net/bugs/1722478 I had the same issue, and got it fixed by using the following comment: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478/comments/72 -- 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/1765832 Title: Two finger scrolling not working after suspend Status in xorg package in Ubuntu: Confirmed Bug description: When waking up my laptop, two finger scrolling is not working anymore. Running: $ modprobe -r psmouse $ modprobe psmouse restores the functionality. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 20 08:23:33 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2227] InstallationDate: Installed on 2018-04-10 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: LENOVO 20BTS09800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET26W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS09800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET26W(1.04):bd01/23/2015:svnLENOVO:pn20BTS09800:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS09800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS09800 dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765832/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797714 Title: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta
I've upgraded today to 18.10, after fist reboot no audio and the UI only shows a 'Dummy Device'. With a "alsa force-reload" the sound become available, but after a reboot same problem. Removing timidity the issue appear solved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797714 Title: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta
My hardware 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Q87 Express LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP108 High Definition Audio Controller (rev a1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797714 Title: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1785764] Re: Chrome/Chromium and Image Viewer distort colours if a colour profile is enabled.
** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Changed in: colord (Ubuntu) Importance: Undecided => High ** Changed in: eog (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1785764 Title: Chrome/Chromium and Image Viewer distort colours if a colour profile is enabled. Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Using Ubuntu 18.04.1 LTS Running on an i7-6700k with a GTX 1080 Reproducible with nvidia-driver-396 or xserver-xorg-video-nouveau and a single 4K screen (TV) connected via HDMI. The issue: Any dark content displayed by an effected application (e.g. a very dark image or dark themed web page) is much darker than intended making it almost unusable. This only effects applications that are launched when the 4K screen is connected. If i disconnect the 4K screen, launch the app via a different 1080p monitor then reconnect the 4K screen the app remains unaffected. The only apps i have found so far that are effected by this are Google Chrome and Image Viewer. That said this is only noticeable when the app is displaying dark contend so if other apps are affected it may be impossible to tell. The attached screenshot uses a black to white gradient image to clearly demonstrate the issue. Is seems like it may be an issue with colour depth as bellow a certain brightness it just goes strait to black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1785764/+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 1798906] [NEW] jackdbus file grows to enormous sizes
Public bug reported: Looks like this has been fixed in kxstudio? https://bugs.launchpad.net/kxstudio/+bug/619014 Unfortunately still a problem in Ubuntu 18.04. The file that grows forever is ~/.log/jack/jackdbus.log. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: jackd2 1.9.12~dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-36.39-lowlatency 4.15.18 Uname: Linux 4.15.0-36-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 18:15:03 2018 ExecutablePath: /usr/bin/jackdbus InstallationDate: Installed on 2017-10-23 (361 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jackd2 (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 jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1798906 Title: jackdbus file grows to enormous sizes Status in jackd2 package in Ubuntu: New Bug description: Looks like this has been fixed in kxstudio? https://bugs.launchpad.net/kxstudio/+bug/619014 Unfortunately still a problem in Ubuntu 18.04. The file that grows forever is ~/.log/jack/jackdbus.log. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: jackd2 1.9.12~dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-36.39-lowlatency 4.15.18 Uname: Linux 4.15.0-36-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 18:15:03 2018 ExecutablePath: /usr/bin/jackdbus InstallationDate: Installed on 2017-10-23 (361 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1798906/+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 1793640] Re: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card
*** This bug is a duplicate of bug 1781294 *** https://bugs.launchpad.net/bugs/1781294 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1793640 Title: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After upgrading to the 18.10 development version from 18.04 only "Dummy sound" is shown. The speakers are not recognized, but plugging headphones works. The system was working well in 18.04. With: sudo alsa force-reload the speakers start to be shown in the sound system parameters and sound is reproduced through the speakers normally. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 21 07:18:03 2018 InstallationDate: Installed on 2018-04-09 (164 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-09-18 (2 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793640/+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 1793640] Re: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card
*** This bug is a duplicate of bug 1781294 *** https://bugs.launchpad.net/bugs/1781294 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1793640 Title: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After upgrading to the 18.10 development version from 18.04 only "Dummy sound" is shown. The speakers are not recognized, but plugging headphones works. The system was working well in 18.04. With: sudo alsa force-reload the speakers start to be shown in the sound system parameters and sound is reproduced through the speakers normally. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 21 07:18:03 2018 InstallationDate: Installed on 2018-04-09 (164 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-09-18 (2 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793640/+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 1783183] Re: apparmor profile denied for kerberos client keytab and credential cache files
Confirmed finally, sorry for the delay. I'll get this fixed. ** Changed in: openldap (Ubuntu) Status: Triaged => In Progress ** Changed in: openldap (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1783183 Title: apparmor profile denied for kerberos client keytab and credential cache files Status in openldap package in Ubuntu: In Progress Bug description: Can we get /etc/krb5/** and /tmp/krb5cc_* added with the appropriate permissions to the slapd apparmor profile? I'm getting the following kinds of errors: apparmor="DENIED" operation="open" profile="/usr/sbin/slapd" name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd" requested_mask="r" denied_mask="r" fsuid=389 ouid=389 apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd" name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k" denied_mask="k" fsuid=389 ouid=389 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1783183/+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 1783183] Re: apparmor profile denied for kerberos client keytab and credential cache files
I used this for now: root@bionic-slapd-consumer:/etc/apparmor.d# cat local/usr.sbin.slapd # Site-specific additions and overrides for usr.sbin.slapd. # For more details, please see /etc/apparmor.d/local/README. /etc/krb5/user/[0-9]*/client.keytab rk, /tmp/krb5cc_[0-9]* rwk, I'm checking if there is some apparmor macro or variable we could use for something like "my own uid" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1783183 Title: apparmor profile denied for kerberos client keytab and credential cache files Status in openldap package in Ubuntu: In Progress Bug description: Can we get /etc/krb5/** and /tmp/krb5cc_* added with the appropriate permissions to the slapd apparmor profile? I'm getting the following kinds of errors: apparmor="DENIED" operation="open" profile="/usr/sbin/slapd" name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd" requested_mask="r" denied_mask="r" fsuid=389 ouid=389 apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd" name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k" denied_mask="k" fsuid=389 ouid=389 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1783183/+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
Re: [Touch-packages] [Bug 1797872] Re: ntpd keeps Soliciting pool server
On Fri, Oct 19, 2018 at 14:36:35 -, Manuel López-Ibáñez wrote: > Both of them work. I don't understand how the last command can work and > I may still be behind a firewall. "ntpdate -d" sends packets using an unprivileged source port, so a firewall could allow those packets but block outgoing packets from ntpd itself, which use a source port of 123 Nathan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1797872 Title: ntpd keeps Soliciting pool server Status in ntp package in Ubuntu: New Bug description: ntpd keeps printing "Soliciting pool server" in the syslog (once every 5 seconds). $ ntpq -c pe remote refid st t when poll reach delay offset jitter == 0.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 1.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 2.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 3.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 ntp.ubuntu.com .POOL. 16 p- 6400.0000.000 0.000 $ sudo ntpq -c rv associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart, version="ntpd 4.2.8p4@1.3265-o Fri Jul 6 20:10:51 UTC 2018 (1)", processor="x86_64", system="Linux/4.15.0-33-generic", leap=11, stratum=16, precision=-24, rootdelay=0.000, rootdisp=0.360, refid=INIT, reftime=. Thu, Feb 7 2036 6:28:16.000, clock=df6ee808.934d239d Mon, Oct 15 2018 11:18:48.575, peer=0, tc=3, mintc=3, offset=0.00, frequency=6.224, sys_jitter=0.00, clk_jitter=0.000, clk_wander=0.000 I have changed nothing in the default configuration of ntp or the firewall. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.9 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 15 11:17:45 2018 InstallationDate: Installed on 2018-04-20 (177 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1797872/+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
Re: [Touch-packages] [Bug 1797872] Re: ntpd keeps Soliciting pool server
On Fri, Oct 19, 2018 at 14:36:35 -, Manuel López-Ibáñez wrote: > $ timedatectl status > Network time on: yes > NTP synchronized: yes > > So it seems it is synchronized, it just re-tries too frequently. (I am not sure what exactly timedatectl looks at when checking the status of ntpd, but the fact that in the ntpq output all your servers show a stratum of 16 and a reach of 0 means that ntpd is defintely not synchronized to anything When it's functioning properly, your pool server stratums should show up somewhere between 1 and 3 or 4, and the reach will be an octal flag showing progressively more bits turned on as responses are received from the server in question [e.g. 1, 3, 7, 17, 37... on until 377, assuming that there aren't any lost packets along the way].) Nathan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1797872 Title: ntpd keeps Soliciting pool server Status in ntp package in Ubuntu: New Bug description: ntpd keeps printing "Soliciting pool server" in the syslog (once every 5 seconds). $ ntpq -c pe remote refid st t when poll reach delay offset jitter == 0.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 1.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 2.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 3.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 ntp.ubuntu.com .POOL. 16 p- 6400.0000.000 0.000 $ sudo ntpq -c rv associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart, version="ntpd 4.2.8p4@1.3265-o Fri Jul 6 20:10:51 UTC 2018 (1)", processor="x86_64", system="Linux/4.15.0-33-generic", leap=11, stratum=16, precision=-24, rootdelay=0.000, rootdisp=0.360, refid=INIT, reftime=. Thu, Feb 7 2036 6:28:16.000, clock=df6ee808.934d239d Mon, Oct 15 2018 11:18:48.575, peer=0, tc=3, mintc=3, offset=0.00, frequency=6.224, sys_jitter=0.00, clk_jitter=0.000, clk_wander=0.000 I have changed nothing in the default configuration of ntp or the firewall. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.9 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 15 11:17:45 2018 InstallationDate: Installed on 2018-04-20 (177 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1797872/+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 1771185] Re: Secondary monitor not connecting in 18.04 LTS
Same problem with ASUS S406 (no graphic card, CPU i5-8250U) The most awkward thing is sometimes it is working, sometimes it's not. I can't figure out why. When not working, even a restart does not re- enable it but xrandr can enable mirroring laptop display. Any advice? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-2 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x258) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x259) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x25a) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz 1920x1080i (0x25b) 74.250MHz +HSync +VS
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
New install ubuntu 18.10. Nvidia-390, nvidia-410 freezes before login. Only purge drivers makes system back to boot -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia- driver-390) -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
So I've found a complete work-around for this. I also found that this issue is NOT new in 18.04 as it also affects 16.x (and likely 15 and 17 too). However it is DIFFERENT in 18.04. More details below. TL;DR: You need to netboot with an initramfs that doesn't have 'scripts/casper-bottom/25disable_cdrom.mount' in it. This script masks the dynamically-generated cdrom.mount systemd unit (where the NFS mount goes). That causes all the issues described in this bug. >From whatever machine where netboot initramfs is created: # Disable/block the problem script mkdir -p /etc/initramfs-tools/scripts/casper-bottom touch /etc/initramfs-tools/scripts/casper-bottom/25disable_cdrom.mount # rebuild initramfs update-initramfs -u # Move/copy the new file to the netboot server The issue here is that systemd isn't able to update its mount status properly. In the case of 18.04, all of the 'failed' mounts are actually successfully mounted. This includes /tmp. BUT systemd doesn't recognize that fact and marks them all as red/failed. In 16.04 this issue is a bit different. When booting, all of the same mounts are again mounted successfully AND systemd shows them all as green/active. BUT if you try to stop/unmount any of them you will see a similar situation. The unmount will actually succeed, but systemd will report an unmount failure and continue to show the unit as green/active. Per the call trace thh noted in comment #21: >From what I can tell, mount_load_proc_self_mountinfo iterates through every >active mount on the system (some perhaps more than once). When it gets to the >nfs-mount on /cdrom, it does fail in unit_set_slice and generate the "Failed >to set up mount unit: Device or resource busy" error. For whatever reason, >that failure seems to completely bork systemd's ability to update its mount >status. Thus mounts get 'stuck' either mounted or not from systemd's >perspective. The failure seems to be caused by the fact that the cdrom.mount unit (NFS mount) is masked. Once it's unmasked the failure doesn't occur and all mounts work as expected. You can actually observe this from within a 'broken' boot at the emergency prompt: rm /lib/systemd/system/cdrom.mount systemctl daemon-reload umount /tmp (ensure it's gone, there may be multiple mounts) systemctl reset-failed tmp.mount systemctl start tmp.mount ..and it will succeed I did verify this issue by actually booting from a 'real' DVD and the problem doesn't happen there. It's something specific to having the image mounted over NFS and masking it's unit. For reference, the disable_cdrom.mount script was the solution for this bug https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1436715 -- 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/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Daemon' dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") fuse: device not found, try 'modprobe fuse' first dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Metadata' (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed A connection to the bus can't be made done. Begin: Setting up init... ... done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+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 1576114] Re: Xubuntu 16.04 failing installing software , Have to run apt-get update everytime
[Expired for apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apt (Ubuntu) Status: Incomplete => Expired -- 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/1576114 Title: Xubuntu 16.04 failing installing software , Have to run apt-get update everytime Status in apt package in Ubuntu: Expired Bug description: Hi, Using : Description: Ubuntu 16.04 LTS Release: 16.04 Almost everytime I need to install a software on command line, Following appears: Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package skype After running apt-get update, The installation works as expected. The Canonical partners is activated in repo. options. Feels like this is a system bug. Anybody with same problem? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1576114/+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 1571511] Re: hpcups ppd fails to print; hpijs ppd works (hplip printer)
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1571511 Title: hpcups ppd fails to print; hpijs ppd works (hplip printer) Status in cups package in Ubuntu: Expired Status in hplip package in Ubuntu: Expired Bug description: The hplip in xenial is not compatible with the versions of cups and dbus (and various other libraries) in xenial. The initial symptoms were that after running hp-setup -i (text mode only box), and attempting to print a test page from hplip, there was no output. After cancelling that job from http://:631/... and attempting to print another test page from the CUPS interface, CUPS reporter 'filter failed'. Reviewing error_log revealed the message 'unable to open inital device. quitting'. While this *sounds* like a device error, hp-levels and hp-clean both work, so clearly the issue is not with access to the usb device (and the appropriate /dev/bus/usb/*/* device has group lp and group rw permissions). Also some web searching reveals that this can be caused by e.g. ghostscript errors and is not necessarily indicative of an hardware device access issue. Running hp-doctor gives the attached result hplip version 3.16.3+repack0-1 cups 2.1.3-4 dbus 1.10.6-1ubuntu3 On an up-to-date as of 2016-04-18 01:00:00 -0400 Xenial system installed from final beta alternate CD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1571511/+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 1555381] Re: Printer won't work
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1555381 Title: Printer won't work Status in cups package in Ubuntu: Expired Bug description: I have a Hewlett-Packard LaserJet 1020 printer and it doesn't work to print out anything from it! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.7 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-51-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 10 00:30:56 2016 InstallationDate: Installed on 2015-11-15 (115 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lpstat: device for HP-LaserJet-1020: usb://HP/LaserJet%201020?serial=JL3GVG2 MachineType: LENOVO 2349C62 Papersize: a4 PpdFiles: HP-LaserJet-1020: HP LaserJet 1020 Foomatic/foo2zjs-z1 (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-51-generic root=UUID=90caf42d-63c7-441f-8592-0bbae0b1d227 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET41WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349C62 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET41WW(1.16):bd05/25/2012:svnLENOVO:pn2349C62:pvrThinkPadT430:rvnLENOVO:rn2349C62:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2349C62 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1555381/+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 1553494] Re: Intermec PC43t prints only the first job, usb-no-reattach-default=true solves the issue
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1553494 Title: Intermec PC43t prints only the first job, usb-no-reattach-default=true solves the issue Status in cups package in Ubuntu: Expired Bug description: I had a bad time until I get this printer working. In the beggining I could not set it up because bad commands makes the printer freeze. After strugling for about a week I found the ideal combination of driver and configurations, but the printer was printing only the first job sent, after this it won't accept anymore. I installed the Intermec CUPS drivers (version 1.2-56) available at: http://apps.intermec.com/EFulfillment/SoftwareListForm.aspx?SoftwareID=3149 Searching for syslog I found that the printer was disconnecting after a job sent. "DebuggingPrintingProblems" Wiki Page helped me to solve the issue. After installing the printer, I ran (lpstat -p -d) to find the printer name, then (lpadmin -p Intermec-PC43t-203-FP -o usb-no- reattach-default=true) to fix the disconnecting behaiver. On research I found that is possible to fix the issue also editing the file (/usr/share/cups/usb/org.cups.usb-quirks) but I will wait untill a fix is released, probably using this configuration file. I'm now using Direct Protocol with specific PC43t drivers (not generic Intermec drivers) and eveything is working properly. I will also report this problem to CUPS upstream at http://www.cups.org/str.php and past the link here. $ lsusb Bus 008 Device 003: ID 067e:0042 Intermec Technologies Corp. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.7 ProcVersionSignature: Ubuntu 3.16.0-62.83~14.04.1-generic 3.16.7-ckt23 Uname: Linux 3.16.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CupsErrorLog: W [05/Mar/2016:09:00:18 -0300] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'Intermec-PC43t-203-FP-Gray..' already exists CurrentDesktop: LXDE Date: Sat Mar 5 09:24:38 2016 Lpstat: device for DCP7065DN: lpd://BRN001BA976321F/BINARY_P1 device for HP-8100-antiga: hp:/net/Officejet_Pro_8100?zc=HPC7E7F8 device for HP-8100-nova: hp:/net/Officejet_Pro_8100?zc=HP92316B device for Intermec-PC43t-203-FP: usb://Intermec/PC43t-203-FP?serial=128C1230268 device for L355-Series: lpd://192.168.254.15:515/PASSTHRU MachineType: To be filled by O.E.M. To be filled by O.E.M. Papersize: a4 PpdFiles: DCP7065DN: Brother DCP7065DN for CUPS Intermec-PC43t-203-FP: Intermec PC43t (203dpi) HP-8100-antiga: HP Officejet Pro 8100, hpcups 3.14.3 HP-8100-nova: HP Officejet Pro 8100, hpcups 3.14.3 L355-Series: Epson L355 Series - epson-inkjet-printer 1.0.0-1lsb3.2 (Seiko Epson Corporation LSB 3.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-62-generic root=UUID=49a849d6-d410-4fee-8447-d08bdd5af3ef ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd01/11/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1553494/+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 1545701] Re: printer lbp2900
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1545701 Title: printer lbp2900 Status in cups package in Ubuntu: Expired Bug description: my canon printer lbp2900 is not getting installed as i have tried all the command may times. plz can u help me in getting installed and more over i m new to linux os. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.8 ProcVersionSignature: Ubuntu 3.19.0-50.56~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-50-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CrashDB: ubuntu Date: Mon Feb 15 18:13:57 2016 InstallationDate: Installed on 2016-02-07 (7 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1545701/+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 1559270] Re: package cups-daemon 2.1.0-4ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1559270 Title: package cups-daemon 2.1.0-4ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups package in Ubuntu: Expired Bug description: This bug came up multiple times. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: cups-daemon 2.1.0-4ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CupsErrorLog: Date: Fri Mar 18 12:06:50 2016 DuplicateSignature: package:cups-daemon:2.1.0-4ubuntu3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-01-11 (432 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: TOSHIBA Satellite L775D Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=7a1dfffa-2f95-4a7c-9668-a1c4e29a0c66 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic root=UUID=7a1dfffa-2f95-4a7c-9668-a1c4e29a0c66 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: cups Title: package cups-daemon 2.1.0-4ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2016-03-18 (0 days ago) dmi.bios.date: 05/11/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TKBSS dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.30 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd05/11/2011:svnTOSHIBA:pnSatelliteL775D:pvrPSK40U-00R003:rvnPEGATRONCORPORATION:rnTKBSS:rvr1.30:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite L775D dmi.product.version: PSK40U-00R003 dmi.sys.vendor: TOSHIBA modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2014-07-22T15:20:18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1559270/+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 1548930] Re: package cups-daemon 2.0.2-1ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1548930 Title: package cups-daemon 2.0.2-1ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in cups package in Ubuntu: Expired Bug description: my ubuntu 14.10 restarts itself after some minutes of using, above all when I surf on Youtube ProblemType: Package DistroRelease: Ubuntu 15.04 Package: cups-daemon 2.0.2-1ubuntu3.2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Tue Feb 23 13:58:39 2016 DuplicateSignature: package:cups-daemon:2.0.2-1ubuntu3.2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-02-21 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) Lpstat: device for HP-Officejet-5600-series: hp:/usb/Officejet_5600_series?serial=CN87IF80ZZ04B2 device for Officejet_5600: hp:/usb/Officejet_5600_series?serial=CN87IF80ZZ04B2 device for Officejet_5600_fax: hpfax:/usb/Officejet_5600_series?serial=CN87IF80ZZ04B2 Papersize: a4 PpdFiles: Officejet_5600: HP Officejet 5600 Series, hpcups 3.14.6 Officejet_5600_fax: HP Fax hpcups HP-Officejet-5600-series: HP Officejet 5600 Series, hpcups 3.14.6 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: cups Title: package cups-daemon 2.0.2-1ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to vivid on 2016-02-23 (0 days ago) dmi.bios.date: 09/08/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: P4i65G dmi.board.version: 1.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd09/08/2006:svn:pnP4i65G:pvr1.00:rvn:rnP4i65G:rvr1.00: dmi.product.name: P4i65G dmi.product.version: 1.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1548930/+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 1571511] Re: hpcups ppd fails to print; hpijs ppd works (hplip printer)
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1571511 Title: hpcups ppd fails to print; hpijs ppd works (hplip printer) Status in cups package in Ubuntu: Expired Status in hplip package in Ubuntu: Expired Bug description: The hplip in xenial is not compatible with the versions of cups and dbus (and various other libraries) in xenial. The initial symptoms were that after running hp-setup -i (text mode only box), and attempting to print a test page from hplip, there was no output. After cancelling that job from http://:631/... and attempting to print another test page from the CUPS interface, CUPS reporter 'filter failed'. Reviewing error_log revealed the message 'unable to open inital device. quitting'. While this *sounds* like a device error, hp-levels and hp-clean both work, so clearly the issue is not with access to the usb device (and the appropriate /dev/bus/usb/*/* device has group lp and group rw permissions). Also some web searching reveals that this can be caused by e.g. ghostscript errors and is not necessarily indicative of an hardware device access issue. Running hp-doctor gives the attached result hplip version 3.16.3+repack0-1 cups 2.1.3-4 dbus 1.10.6-1ubuntu3 On an up-to-date as of 2016-04-18 01:00:00 -0400 Xenial system installed from final beta alternate CD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1571511/+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 1691556] Re: Can't send audio to Amazon Echo via Bluetooth
On 18.04, I'm having this same issue. I can pair to an Echo, but cannot connect nor setup as an Audio Sink. I get errors like "dbusfailederror input/output error" in blueman. -- 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/1691556 Title: Can't send audio to Amazon Echo via Bluetooth Status in bluez package in Ubuntu: Confirmed Bug description: Pairing and coupling to Amazon Echo works, but no sound is heard. I believe the issue is related to the fact that Amazon Echo is paired as a handset (i.e., speaker + microphone) rather than just as a speaker. I believe the critical error is found in a dmesg line such as: Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect failed for 50:F5:DA:A6:3F:EA: Device or resource busy as I describe in the askubuntu.com discussion at: https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo- via-bluetooth I have clarified there my thinking and the steps I've taken thus far on this issue, which includes trying debug bluetooth per the Ubuntu wiki page which describes how to do so. This is probably an upstream issue, as Mike H-R has commented there that the problem also occurs on ArchLinux. I and a few others would like to get this resolved, and I am happy to help (I'm a software developer). However, at this point, I'm not sure how to proceed without some assistance. I suppose I could report it to Debain, but I've only ever used Debain vis a vis Ubuntu, so I thought it best to start here. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 17 22:27:59 2017 InstallationDate: Installed on 2015-12-26 (507 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:53:60:97:55:17 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0 TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+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 1798562] [NEW] After a side by side installation, resized filesystem is corrupted
You have been subscribed to a public bug: Test Case: 1. Perform a first installation of Ubuntu 2. Reboot into the freshly installed system and verify everything works as expected 3. Do a second installation and select "Install alonogside". Keep the size proposed by the installer and proceed to the end of installation 4. Reboot 5. On boot, in the list of installed systems, select the first system installed on the machine 6. Verify that it boots, you can login and it works as expected Actual Result The FS is corrupted and depending on the corruption it goes to initramfs, boots but cannot login, ... Attached is the journal of the system installed on the corrupted partition. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 10:53:57 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- InstallationDate: Installed on 2018-10-18 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: e2fsprogs (Ubuntu) Importance: High Status: Confirmed ** Tags: amd64 apport-bug cosmic iso-testing ubiquity-18.10.12 -- After a side by side installation, resized filesystem is corrupted https://bugs.launchpad.net/bugs/1798562 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs 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 1798562] Re: After a side by side installation, resized filesystem is corrupted
** Package changed: ubiquity (Ubuntu) => e2fsprogs (Ubuntu) ** Changed in: e2fsprogs (Ubuntu) Importance: High => Critical ** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1798562 Title: After a side by side installation, resized filesystem is corrupted Status in e2fsprogs package in Ubuntu: Confirmed Bug description: Test Case: 1. Perform a first installation of Ubuntu 2. Reboot into the freshly installed system and verify everything works as expected 3. Do a second installation and select "Install alonogside". Keep the size proposed by the installer and proceed to the end of installation 4. Reboot 5. On boot, in the list of installed systems, select the first system installed on the machine 6. Verify that it boots, you can login and it works as expected Actual Result The FS is corrupted and depending on the corruption it goes to initramfs, boots but cannot login, ... Attached is the journal of the system installed on the corrupted partition. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 10:53:57 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- InstallationDate: Installed on 2018-10-18 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+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 1798562] Re: After a side by side installation, resized filesystem is corrupted
** Description changed: - Test Case: + Test Case 1: + With e2fsprogs 1.44.4-2: + + Download this file system image: + https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz + + Run the following commands: + + bunzip2 vda1b.qcow2.bz + qemu-img convert vda1b.qcow2 vda1b.raw + e2fsck -f vda1b.raw + resize2fs vda1b.raw 6200M + e2fsck -f vda1b.raw + + e2fsck 1.44.4 (18-Aug-2018) + Pass 1: Checking inodes, blocks, and sizes + Inode 45746 extent block passes checks, but checksum does not match extent + (logical block 1272, physical block 466167, len 776) + Fix? + + + Test Case 2 (Use case of the installer): 1. Perform a first installation of Ubuntu 2. Reboot into the freshly installed system and verify everything works as expected 3. Do a second installation and select "Install alonogside". Keep the size proposed by the installer and proceed to the end of installation - 4. Reboot + 4. Reboot 5. On boot, in the list of installed systems, select the first system installed on the machine 6. Verify that it boots, you can login and it works as expected Actual Result The FS is corrupted and depending on the corruption it goes to initramfs, boots but cannot login, ... Attached is the journal of the system installed on the corrupted partition. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 10:53:57 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- InstallationDate: Installed on 2018-10-18 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ubiquity 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 e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1798562 Title: After a side by side installation, resized filesystem is corrupted Status in e2fsprogs package in Ubuntu: Confirmed Bug description: Test Case 1: With e2fsprogs 1.44.4-2: Download this file system image: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz Run the following commands: bunzip2 vda1b.qcow2.bz qemu-img convert vda1b.qcow2 vda1b.raw e2fsck -f vda1b.raw resize2fs vda1b.raw 6200M e2fsck -f vda1b.raw e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Inode 45746 extent block passes checks, but checksum does not match extent (logical block 1272, physical block 466167, len 776) Fix? Test Case 2 (Use case of the installer): 1. Perform a first installation of Ubuntu 2. Reboot into the freshly installed system and verify everything works as expected 3. Do a second installation and select "Install alonogside". Keep the size proposed by the installer and proceed to the end of installation 4. Reboot 5. On boot, in the list of installed systems, select the first system installed on the machine 6. Verify that it boots, you can login and it works as expected Actual Result The FS is corrupted and depending on the corruption it goes to initramfs, boots but cannot login, ... Attached is the journal of the system installed on the corrupted partition. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 10:53:57 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- InstallationDate: Installed on 2018-10-18 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+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
