[Touch-packages] [Bug 1642828] Re: mixing of English and Khmer fonts
** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1642828 Title: mixing of English and Khmer fonts Status in xorg package in Ubuntu: Confirmed Bug description: I am using Ubuntu 16.4. Displays of dates mix fonts, so that dates are presented partly in Khmer and partly in English. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 18 13:47:26 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 4th Gen Core Processor Integrated Graphics Controller [1025:0920] Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940M] [1025:0993] InstallationDate: Installed on 2016-09-29 (49 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire E5-572G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=a5288db4-02d8-45b8-9509-9852995479ed ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HWS dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/24/2015:svnAcer:pnAspireE5-572G:pvrV1.08:rvnAcer:rnEA50_HWS:rvrV1.08:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-572G dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Nov 18 06:35:28 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5567 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1642828/+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 1637601] Re: UbuntuKVM: migration using NFS mount fails #190
** Bug watch added: Debian Bug tracker #844339 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844339 ** Also affects: libvirt via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844339 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1637601 Title: UbuntuKVM: migration using NFS mount fails #190 Status in libvirt: Unknown Status in base-passwd package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Triaged Bug description: <...> Please see comments for the problem description, and summary of originally bridged comments in the description. Sorry about the inconvenience. <...> To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1637601/+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 1642790] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
apt-get -f install solved the problem for me -- 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/1642790 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: occurred during upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 20:46:19 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-06-11 (525 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for HP-Officejet-Pro-8600: socket://192.168.1.9:9100 MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD5 Papersize: letter PpdFiles: HP-Officejet-Pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F12 dmi.board.name: GA-990FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd10/03/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790/+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 1642828] Re: mixing of English and Khmer fonts
** Changed in: xorg (Ubuntu) Assignee: (unassigned) => Skynet (asstaroid) -- 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/1642828 Title: mixing of English and Khmer fonts Status in xorg package in Ubuntu: New Bug description: I am using Ubuntu 16.4. Displays of dates mix fonts, so that dates are presented partly in Khmer and partly in English. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 18 13:47:26 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 4th Gen Core Processor Integrated Graphics Controller [1025:0920] Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940M] [1025:0993] InstallationDate: Installed on 2016-09-29 (49 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire E5-572G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=a5288db4-02d8-45b8-9509-9852995479ed ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HWS dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/24/2015:svnAcer:pnAspireE5-572G:pvrV1.08:rvnAcer:rnEA50_HWS:rvrV1.08:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-572G dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Nov 18 06:35:28 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5567 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1642828/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
Hi, Can we get some attention to this? We are unable to use Xenial, since the instance boots up without a default gateway. Not sure if we are hit harder because we are using vmware as hypervisor, but should not be a problem since Trusty works fine. -- 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/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) Status in systemd: New Status in cloud-init package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in cloud-init source package in Xenial: Confirmed Status in systemd source package in Xenial: Triaged Bug description: Ubuntu Core 16 images using cloud-init fail to function when the DataSource is over the network (Like OpenStack) as networking is not yet available when cloud-init.service runs. cloud-init service unit deps look like this: [Unit] Description=Initial cloud-init job (metadata service crawler) DefaultDependencies=no Wants=cloud-init-local.service Wants=local-fs.target Wants=sshd-keygen.service Wants=sshd.service After=cloud-init-local.service After=networking.service Requires=networking.service Before=basic.target Before=dbus.socket Before=network-online.target Before=sshd-keygen.service Before=sshd.service Before=systemd-user-sessions.service Conflicts=shutdown.target Here's networkd unit deps: [Unit] Description=Network Service Documentation=man:systemd-networkd.service(8) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be # dropped once tuntap is moved to netlink After=systemd-udevd.service dbus.service network-pre.target systemd-sysusers.service systemd-sysctl.service Before=network.target multi-user.target shutdown.target Conflicts=shutdown.target Wants=network.target # On kdbus systems we pull in the busname explicitly, because it # carries policy that allows the daemon to acquire its name. Wants=org.freedesktop.network1.busname After=org.freedesktop.network1.busname And a critical-chain output: root@snap-test7:~# systemd-analyze critical-chain systemd-networkd Failed to get ID: Unit name systemd-networkd is not valid. The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. systemd-networkd.service +440ms └─dbus.service @11.461s └─basic.target @11.403s └─sockets.target @11.401s └─dbus.socket @11.398s └─cloud-init.service @10.127s +1.266s └─networking.service @9.305s +799ms └─network-pre.target @9.295s └─cloud-init-local.service @3.822s +5.469s └─local-fs.target @3.813s └─run-cgmanager-fs.mount @12.687s └─local-fs-pre.target @1.393s └─systemd-tmpfiles-setup-dev.service @1.116s +195ms └─kmod-static-nodes.service @887ms +193ms └─system.slice @783ms └─-.slice @721ms cloud-init would need networkd to run at or before 'networking.service' so it can raise networking to then find and use network-based datasources. # grep systemd /usr/share/snappy/dpkg.list ii libnss-resolve:amd64 229-4ubuntu11 amd64nss module to resolve names via systemd-resolved ii libpam-systemd:amd64 229-4ubuntu11 amd64system and service manager - PAM module ii libsystemd0:amd64 229-4ubuntu11 amd64systemd utility library ii systemd 229-4ubuntu11 amd64system and service manager ii systemd-sysv 229-4ubuntu11 amd64system and service manager - SysV links # grep cloud-init /usr/share/snappy/dpkg.list ii cloud-init 0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all Init scripts for cloud instances To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636912/+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 1642828] [NEW] mixing of English and Khmer fonts
Public bug reported: I am using Ubuntu 16.4. Displays of dates mix fonts, so that dates are presented partly in Khmer and partly in English. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 18 13:47:26 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 4th Gen Core Processor Integrated Graphics Controller [1025:0920] Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940M] [1025:0993] InstallationDate: Installed on 2016-09-29 (49 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire E5-572G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=a5288db4-02d8-45b8-9509-9852995479ed ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HWS dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/24/2015:svnAcer:pnAspireE5-572G:pvrV1.08:rvnAcer:rnEA50_HWS:rvrV1.08:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-572G dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Nov 18 06:35:28 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5567 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1642828 Title: mixing of English and Khmer fonts Status in xorg package in Ubuntu: New Bug description: I am using Ubuntu 16.4. Displays of dates mix fonts, so that dates are presented partly in Khmer and partly in English. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 18 13:47:26 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 4th Gen Core Processor Integrated Graphics Controller [1025:0920] Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940M] [1025:0993] InstallationDate: Installed on 2016-09-29 (49 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire E5-572G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=a5288db4-02d8-45b8-9509-9852995479ed ro quiet splash
[Touch-packages] [Bug 1642823] Re: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1642823 Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: I am very new in Ubuntu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 22:07:42 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-10-06 (42 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC Papersize: letter ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1802 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.5A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1A:bd06/22/2012:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1802:rvr10.5A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 05931120461620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642823/+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 1642823] [NEW] package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: I am very new in Ubuntu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 22:07:42 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-10-06 (42 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC Papersize: letter ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1802 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.5A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1A:bd06/22/2012:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1802:rvr10.5A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 05931120461620100 dmi.sys.vendor: Hewlett-Packard ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-from-proposed 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/1642823 Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: I am very new in Ubuntu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 22:07:42 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-10-06 (42 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC Papersize: letter ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1802 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.5A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1A:bd06/22/2012:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1802:rvr10.5A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 05931120461620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642823/+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 1642790] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
-f works for me. -- 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/1642790 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: occurred during upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 20:46:19 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-06-11 (525 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for HP-Officejet-Pro-8600: socket://192.168.1.9:9100 MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD5 Papersize: letter PpdFiles: HP-Officejet-Pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F12 dmi.board.name: GA-990FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd10/03/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790/+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 1642819] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: This package failed during installation. I have had problems with this OS since it did a upgrade to Ubuntu 16.04 LTS. On start up it is very slow to load, and I have lost the right sound channel and it will at times do two or three reboots on any given day for no reason. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 00:28:41 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-19 (182 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic root=UUID=0199b1c0-57ea-4370-b236-66ee8f4d069c ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic root=UUID=0199b1c0-57ea-4370-b236-66ee8f4d069c ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-10-17 (31 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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: 2015-02-18T14:37:53 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check 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/1642819 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: This package failed during installation. I have had problems with this OS since it did a upgrade to Ubuntu 16.04 LTS. On start up it is very slow to load, and I have lost the right sound channel and it will at times do two or three reboots on any given day for no reason. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 00:28:41 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-19 (182 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic root=UUID=0199b1c0-57ea-4370-b236-66ee8f4d069c ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic root=UUID=0199b1c0-57ea-4370-b236-66ee8f4d069c ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-10-17 (31 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modifi
[Touch-packages] [Bug 1574029] Re: Upgrade failed
Have the same problem, close of error message fails "ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/shared-mime-info.0.crash' upgrade hang afterwards; last line: Unpacking libcairo2:i386 ** Attachment added: "/var/crash/shared-mime-info.0.crash" https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1574029/+attachment/4779012/+files/crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1574029 Title: Upgrade failed Status in shared-mime-info package in Ubuntu: New Bug description: At the end of the upgrade, a dialog box appeared "The upgrade has aborted. Your system could be in an unstable state. A recovery will run now (dpkg -configure - a). Nothing happened after closing the dialog box. After shutdown, boot up failed after grub tries to load something with this message "Starting up", then after 10 seconds this message "Gave up waiting for root device., common problems:.ALERT! UUID = 2476e..does not exist. The the boot process stopped at the initramfs prompt. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shared-mime-info 1.5-2 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 17:34:29 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-11-12 (162 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.5-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1574029/+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 1642809] [NEW] no audio on boot and stuttering afterwards
Public bug reported: Right after boot I have no audio on my machine until I run pulseaudio -k. Then I have normal audio for a very short time (a few seconds) until it begins stuttering. The stuttering gets progressively worse with time, and re-running pulseaudio -k DOESN'T solve it. Sometimes it disappears by itself for a few minutes only to restart as described later. While trying to play audio, I get many of the following two messages in /var/log/syslog, both when I have no audio and when I get stuttering: Nov 16 23:04:45 prower-desktop rtkit-daemon[14282]: Successfully made thread 20064 of process 4156 (n/a) owned by '1000' RT at priority 5. Nov 16 23:04:45 prower-desktop rtkit-daemon[14282]: Supervising 1 threads of 1 processes of 1 users. Nov 16 23:04:48 prower-desktop rtkit-daemon[14282]: Warning: Reached burst limit for user '1000', denying request. Nov 16 23:04:48 prower-desktop rtkit-daemon[14282]: Supervising 0 threads of 0 processes of 1 users. The process number mentioned in the first message is invariably /usr/bin/pulseaudio --start --log-target=syslog. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 17 23:35:55 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-27 (204 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67BL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10189-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-206:cvn:ct3:cvr: ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1642809 Title: no audio on boot and stuttering afterwards Status in pulseaudio package in Ubuntu: New Bug description: Right after boot I have no audio on my machine until I run pulseaudio -k. Then I have normal audio for a very short time (a few seconds) until it begins stuttering. The stuttering gets progressively worse with time, and re-running pulseaudio -k DOESN'T solve it. Sometimes it disappears by itself for a few minutes only to restart as described later. While trying to play audio, I get many of the following two messages in /var/log/syslog, both when I have no audio and when I get stuttering: Nov 16 23:04:45 prower-desktop rtkit-daemon[14282]: Successfully made thread 20064 of process 4156 (n/a) owned by '1000' RT at priority 5. Nov 16 23:04:45 prower-desktop rtkit-daemon[14282]: Supervising 1 threads of 1 processes of 1 users. Nov 16 23:04:48 prower-desktop rtkit-daemon[14282]: Warning: Reached burst limit for user '1000', denying request. Nov 16 23:04:48 prower-desktop rtkit-daemon[14282]: Supervising 0 threads of 0 processes of 1 users. The process number mentioned in the first message is invariably /usr/bin/pulseaudio --start --log-target=syslog. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 17 23:35:55 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-27 (204 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67BL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10189-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-206:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1642809/+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 1642807] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: BrokenCount>0 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 18 05:34:57 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-09-13 (796 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lpstat: device for Canon-MG3100-series: dnssd://Canon%20MG3100%20series._printer._tcp.local/ MachineType: ASUSTeK COMPUTER INC. X501A1 Papersize: a4 PpdFiles: Canon-MG3100-series: Canon MG3100 series - CUPS+Gutenprint v5.2.11 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed root=UUID=22fd747a-8649-4775-94db-9fa3a626f6c0 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed root=UUID=22fd747a-8649-4775-94db-9fa3a626f6c0 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X501A1.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X501A1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX501A1.213:bd12/03/2012:svnASUSTeKCOMPUTERINC.:pnX501A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX501A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X501A1 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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-23T00:20:18 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check 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/1642807 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: BrokenCount>0 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 18 05:34:57 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-09-13 (796 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lpstat: device for Canon-MG3100-series: dnssd://Canon%20MG3100%20series._printer._tcp.local/ MachineType: ASUSTeK COMPUTER INC. X501A1 Papersize: a4 PpdFiles: Canon-MG3100-series: Canon MG3100 series - CUPS+Gutenprint v5.2.11 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed root=UUID=22fd747a-8649-4775-94db-9fa3a626f6c0 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed root=UUID=22fd747a-8649-4775-94db-9fa3a626f6c0 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X501A1.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X501A1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX501A1.213:bd12/03/2012:svnASUSTeKCOMPUTERINC.:pnX501A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX501A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X501A1 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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-23T00:20:18 To manage
[Touch-packages] [Bug 1642535] Re: need /var/snap writable-path for snappy global data
** Changed in: lxc-android-config (Ubuntu) Assignee: (unassigned) => Vicamo Yang (vicamo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1642535 Title: need /var/snap writable-path for snappy global data Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: This is a follow-up for bug 1632272. From snap-confine source code[1], when running on classic distribution as we're for ubuntu-touch, some additional paths are mounted. They are /dev, /etc, /home, /root, /proc, /sys, /tmp, /var/snap, /var/lib/snapd, /var/tmp, /run, /lib/modules, /media, etc. Among them, /var/snap is necessary for lxd snap global data like pid file, daemon socket, and images. [1]: https://github.com/snapcore/snap-confine/blob/master/src/mount- support.c#L556 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642535/+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 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
I got this bug trying to download the linux source, fixed it with the following line (which was posted in this bug's duplicate thread): sudo chown _apt /var/lib/update-notifier/package-data-downloads/partial/ -- 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/1522675 Title: Can't drop privileges for downloading : _apt user not allowed Status in apt package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1642796] [NEW] package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: idk wtf, i just want my tethering working, i cant adb clockworkmod or nothing ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 17 20:35:35 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-10-21 (27 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check 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/1642796 Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: idk wtf, i just want my tethering working, i cant adb clockworkmod or nothing ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 17 20:35:35 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-10-21 (27 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642796/+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 1642386] Re: At least one invalid signature was encountered.
Turns out the valgrind messages aren't regressions either. Here's the older apt packages again which seemed to work okay: ==25043== ==25043== HEAP SUMMARY: ==25043== in use at exit: 13,118,211 bytes in 170,033 blocks ==25043== total heap usage: 626,066 allocs, 456,033 frees, 69,255,845 bytes allocated ==25043== ==25043== LEAK SUMMARY: ==25043==definitely lost: 0 bytes in 0 blocks ==25043==indirectly lost: 0 bytes in 0 blocks ==25043== possibly lost: 0 bytes in 0 blocks ==25043==still reachable: 13,118,211 bytes in 170,033 blocks ==25043== suppressed: 0 bytes in 0 blocks ==25043== Rerun with --leak-check=full to see details of leaked memory ==25043== ==25043== For counts of detected and suppressed errors, rerun with: -v ==25043== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==23213== Conditional jump or move depends on uninitialised value(s) ==23213==at 0x4F4D240: pkgCache::ReMap(bool const&) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4F55598: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4F577E4: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4EBA081: pkgCacheFile::BuildCaches(OpProgress*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x51EC5A1: DoUpdate(CommandLine&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==23213==by 0x4ECDFA5: CommandLine::DispatchArg(CommandLine::Dispatch const*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x51BEDF2: DispatchCommandLine(CommandLine&, std::vector > const&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==23213==by 0x10BB38: ??? (in /usr/bin/apt-get) ==23213==by 0x59B482F: (below main) (libc-start.c:291) ==23213== Uninitialised value was created by a stack allocation ==23213==at 0x4F5527D: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213== ==23213== Syscall param write(buf) points to uninitialised byte(s) ==23213==at 0x5A8A6E0: __write_nocancel (syscall-template.S:84) ==23213==by 0x4ED5CAB: FileFd::Write(void const*, unsigned long long) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4E7A150: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4F57876: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4EBA081: pkgCacheFile::BuildCaches(OpProgress*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x51EC5A1: DoUpdate(CommandLine&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==23213==by 0x4ECDFA5: CommandLine::DispatchArg(CommandLine::Dispatch const*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x51BEDF2: DispatchCommandLine(CommandLine&, std::vector > const&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==23213==by 0x10BB38: ??? (in /usr/bin/apt-get) ==23213==by 0x59B482F: (below main) (libc-start.c:291) ==23213== Address 0xe401007 is in a rw- anonymous segment ==23213== ==23213== Syscall param write(buf) points to uninitialised byte(s) ==23213==at 0x5A8A6E0: __write_nocancel (syscall-template.S:84) ==23213==by 0x4ED5CAB: FileFd::Write(void const*, unsigned long long) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4E7A1A7: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4F57876: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4EBA081: pkgCacheFile::BuildCaches(OpProgress*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x51EC5A1: DoUpdate(CommandLine&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==23213==by 0x4ECDFA5: CommandLine::DispatchArg(CommandLine::Dispatch const*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x51BEDF2: DispatchCommandLine(CommandLine&, std::vector > const&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==23213==by 0x10BB38: ??? (in /usr/bin/apt-get) ==23213==by 0x59B482F: (below main) (libc-start.c:291) ==23213== Address 0xe401007 is in a rw- anonymous segment ==23213== ==23213== Syscall param write(buf) points to uninitialised byte(s) ==23213==at 0x5A8A6E0: __write_nocancel (syscall-template.S:84) ==23213==by 0x4ED5CAB: FileFd::Write(void const*, unsigned long long) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4E7A150: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4F574E4: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x4EBA081: pkgCacheFile::BuildCaches(OpProgress*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23213==by 0x51EC5A1: DoUpdate(CommandLine&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==23213==by 0x4ECDFA5: CommandLine::DispatchArg(CommandLine::Dispatch const*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==23
[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.
On a whim I ran apt-get update through valgrind: ==22064== ==22064== HEAP SUMMARY: ==22064== in use at exit: 695,606 bytes in 7,018 blocks ==22064== total heap usage: 67,584 allocs, 60,566 frees, 18,503,180 bytes allocated ==22064== ==22064== LEAK SUMMARY: ==22064==definitely lost: 0 bytes in 0 blocks ==22064==indirectly lost: 0 bytes in 0 blocks ==22064== possibly lost: 0 bytes in 0 blocks ==22064==still reachable: 695,606 bytes in 7,018 blocks ==22064== suppressed: 0 bytes in 0 blocks ==22064== Rerun with --leak-check=full to see details of leaked memory ==22064== ==22064== For counts of detected and suppressed errors, rerun with: -v ==22064== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==20846== Conditional jump or move depends on uninitialised value(s) ==20846==at 0x4F4DA00: pkgCache::ReMap(bool const&) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4F55E68: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4F580B4: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4EBAA51: pkgCacheFile::BuildCaches(OpProgress*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x51EE809: DoUpdate(CommandLine&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==20846==by 0x4ECEA25: CommandLine::DispatchArg(CommandLine::Dispatch const*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x51C0E62: DispatchCommandLine(CommandLine&, std::vector > const&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==20846==by 0x10BB38: ??? (in /usr/bin/apt-get) ==20846==by 0x59B682F: (below main) (libc-start.c:291) ==20846== Uninitialised value was created by a stack allocation ==20846==at 0x4F55B4D: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846== ==20846== Syscall param write(buf) points to uninitialised byte(s) ==20846==at 0x5A8C6E0: __write_nocancel (syscall-template.S:84) ==20846==by 0x4ED6B13: FileFd::Write(void const*, unsigned long long) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4E7A460: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4F58146: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4EBAA51: pkgCacheFile::BuildCaches(OpProgress*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x51EE809: DoUpdate(CommandLine&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==20846==by 0x4ECEA25: CommandLine::DispatchArg(CommandLine::Dispatch const*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x51C0E62: DispatchCommandLine(CommandLine&, std::vector > const&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==20846==by 0x10BB38: ??? (in /usr/bin/apt-get) ==20846==by 0x59B682F: (below main) (libc-start.c:291) ==20846== Address 0xd003007 is in a rw- anonymous segment ==20846== ==20846== Syscall param write(buf) points to uninitialised byte(s) ==20846==at 0x5A8C6E0: __write_nocancel (syscall-template.S:84) ==20846==by 0x4ED6B13: FileFd::Write(void const*, unsigned long long) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4E7A4B7: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4F58146: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4EBAA51: pkgCacheFile::BuildCaches(OpProgress*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x51EE809: DoUpdate(CommandLine&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==20846==by 0x4ECEA25: CommandLine::DispatchArg(CommandLine::Dispatch const*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x51C0E62: DispatchCommandLine(CommandLine&, std::vector > const&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==20846==by 0x10BB38: ??? (in /usr/bin/apt-get) ==20846==by 0x59B682F: (below main) (libc-start.c:291) ==20846== Address 0xd003007 is in a rw- anonymous segment ==20846== ==20846== Syscall param write(buf) points to uninitialised byte(s) ==20846==at 0x5A8C6E0: __write_nocancel (syscall-template.S:84) ==20846==by 0x4ED6B13: FileFd::Write(void const*, unsigned long long) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4E7A460: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4F57DB4: ??? (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x4EBAA51: pkgCacheFile::BuildCaches(OpProgress*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x51EE809: DoUpdate(CommandLine&) (in /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0.0) ==20846==by 0x4ECEA25: CommandLine::DispatchArg(CommandLine::Dispatch const*, bool) (in /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0.0) ==20846==by 0x51C0E62: DispatchCommandLine(CommandLine&, std::vector > const&) (in /
[Touch-packages] [Bug 1642792] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1
Public bug reported: *sudo apt-get update *sudo apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 23:52:23 2016 ErrorMessage: sub-processo novo script pre-removal retornou estado de saída de erro 1 InstallationDate: Installed on 2016-01-30 (292 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lpstat: device for psc-1310-series: hp:/usb/psc_1310_series?serial=BR49O3H14YO2 MachineType: Dell Inc. Vostro 5470 Papersize: a4 PpdFiles: psc-1310-series: HP PSC 1310 Series, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1 UpgradeStatus: Upgraded to xenial on 2016-06-18 (152 days ago) dmi.bios.date: 01/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 019TFD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/21/2015:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn019TFD:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5470 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.default.cups: 2015-02-18T17:37:53 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1642792 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1 Status in cups package in Ubuntu: New Bug description: *sudo apt-get update *sudo apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 23:52:23 2016 ErrorMessage: sub-processo novo script pre-removal retornou estado de saída de erro 1 InstallationDate: Installed on 2016-01-30 (292 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lpstat: device for psc-1310-series: hp:/usb/psc_1310_series?serial=BR49O3H14YO2 MachineType: Dell Inc. Vostro 5470 Papersize: a4 PpdFiles: psc-1310-series: HP PSC 1310 Series, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1 UpgradeStatus: Upgraded to xenial on 2016-06-18 (152 days ago) dmi.bios.date: 01/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 019TFD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/21/2015:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn019TFD:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5470 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.default.cups: 2015-02-18T17:37:53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642792/+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 1642790] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1642790 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: occurred during upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 20:46:19 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-06-11 (525 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for HP-Officejet-Pro-8600: socket://192.168.1.9:9100 MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD5 Papersize: letter PpdFiles: HP-Officejet-Pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F12 dmi.board.name: GA-990FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd10/03/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790/+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 1642791] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1
Public bug reported: *sudo apt-get update *sudo apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 23:52:23 2016 ErrorMessage: sub-processo novo script pre-removal retornou estado de saída de erro 1 InstallationDate: Installed on 2016-01-30 (292 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lpstat: device for psc-1310-series: hp:/usb/psc_1310_series?serial=BR49O3H14YO2 MachineType: Dell Inc. Vostro 5470 Papersize: a4 PpdFiles: psc-1310-series: HP PSC 1310 Series, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1 UpgradeStatus: Upgraded to xenial on 2016-06-18 (152 days ago) dmi.bios.date: 01/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 019TFD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/21/2015:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn019TFD:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5470 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.default.cups: 2015-02-18T17:37:53 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1642791 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1 Status in cups package in Ubuntu: New Bug description: *sudo apt-get update *sudo apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 23:52:23 2016 ErrorMessage: sub-processo novo script pre-removal retornou estado de saída de erro 1 InstallationDate: Installed on 2016-01-30 (292 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lpstat: device for psc-1310-series: hp:/usb/psc_1310_series?serial=BR49O3H14YO2 MachineType: Dell Inc. Vostro 5470 Papersize: a4 PpdFiles: psc-1310-series: HP PSC 1310 Series, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1 UpgradeStatus: Upgraded to xenial on 2016-06-18 (152 days ago) dmi.bios.date: 01/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 019TFD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/21/2015:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn019TFD:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5470 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.default.cups: 2015-02-18T17:37:53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642791/+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 1617348] Re: unity shell is crashing for apps without icon
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released ** Changed in: canonical-devices-system-image Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1617348 Title: unity shell is crashing for apps without icon Status in Canonical System Image: Fix Released Status in ubuntu-app-launch package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: Trying to launch a app from terminal that does not contains a "Icon" etry on it desktop file causes the shell to crash. How to test === * Create a desktop entry without the icon entry (something like that): [Desktop Entry] Name=Sync Monitor Comment=Ask for online account authentication if the token expires Exec=/usr/lib/arm-linux-gnueabihf/sync-monitor/sync-monitor-helper %u Terminal=false Type=Application Version=1.0 X-Ubuntu-Gettext-Domain=sync-monitor * try to launch it from terminal or url launch: /usr/lib/arm-linux-gnueabihf/sync-monitor/sync-monitor-helper --desktop-file-hint=/usr/share/applications/sync-monitor-helper.desktop Expected App appears Current === Shell crashes and go back to login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617348/+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 1642790] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
The system is now reporting Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: cups : Depends: cups-daemon (>= 2.1.3-4ubuntu0.1) cups-core-drivers : Depends: cups-daemon (>= 2.1.3-4ubuntu0.1) cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.1 is installed E: Unmet dependencies. Try using -f. -- 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/1642790 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: occurred during upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 20:46:19 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-06-11 (525 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for HP-Officejet-Pro-8600: socket://192.168.1.9:9100 MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD5 Papersize: letter PpdFiles: HP-Officejet-Pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F12 dmi.board.name: GA-990FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd10/03/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790/+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 1642790] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: occurred during upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 20:46:19 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-06-11 (525 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for HP-Officejet-Pro-8600: socket://192.168.1.9:9100 MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD5 Papersize: letter PpdFiles: HP-Officejet-Pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F12 dmi.board.name: GA-990FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd10/03/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: cups (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package need-duplicate-check third-party-packages 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/1642790 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: occurred during upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Thu Nov 17 20:46:19 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-06-11 (525 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for HP-Officejet-Pro-8600: socket://192.168.1.9:9100 MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD5 Papersize: letter PpdFiles: HP-Officejet-Pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=acc6d16a-821d-416e-b8c5-8eb389d3a212 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F12 dmi.board.name: GA-990FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd10/03/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790/+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 1542029] Re: New windows have incorrect dimensions on launch (not the dimensions the app specifies)
Specific examples: (1) Open a drop-down menu in a GTK app and verify it looks the right size. (2) Hover over some elements that will pop up a tooltip and to verify the tooltip is a sane size. (3) xclock -geometry 100x100 (4) Run 'zenity --scale' and verify the default window size fits neatly around the widgets like in X. I think you've probably fixed all this recently but it's mostly been discussed in bug 1543467 as mentioned above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1542029 Title: New windows have incorrect dimensions on launch (not the dimensions the app specifies) Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: New Status in Ubuntu UX: Invalid Status in miral package in Ubuntu: Incomplete Status in puritine package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: currently, the shell is picking some random window size. They are about to change it to be close to what is on the phone - as this will match most apps. however the Xapps should have something "larger" shell is landing the ability to communicate to it, the desire default first launch window size it would also be good to have design input on this selection To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542029/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
@jasauders Problem is that bug is present not only for suspend/resume scenario, but also for wifi on/off. And for me it even drop connection sometimes and can't reconnect without wifi restart. It's a problem with wifi drivers and devs not seems to care about it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1642386] Re: At least one invalid signature was encountered.
The files in partial/ don't look too damning: root@hunt:/var/lib/apt/lists/partial# file * ftp.debian.org_debian_dists_jessie-updates_contrib_source_Sources: empty ftp.debian.org_debian_dists_wheezy-updates_contrib_source_Sources: empty mirrors.kernel.org_ubuntu_dists_xenial-proposed_restricted_source_Sources: empty mirrors.kernel.org_ubuntu_dists_yakkety-proposed_multiverse_source_Sources: empty mirrors.kernel.org_ubuntu_dists_yakkety-proposed_restricted_source_Sources: empty mirrors.kernel.org_ubuntu_dists_yakkety-security_restricted_source_Sources: empty mirrors.kernel.org_ubuntu_dists_yakkety-updates_restricted_source_Sources: empty mirrors.kernel.org_ubuntu_dists_zesty-proposed_restricted_source_Sources: empty security.debian.org_dists_jessie_updates_contrib_source_Sources: ASCII text, with very long lines root@hunt:/var/lib/apt/lists/partial# cat security.debian.org_dists_jessie_updates_contrib_source_Sources Package: virtualbox Binary: virtualbox-qt, virtualbox, virtualbox-dbg, virtualbox-dkms, virtualbox-source, virtualbox-guest-dkms, virtualbox-guest-source, virtualbox-guest-x11, virtualbox-guest-utils Version: 4.3.36-dfsg-1+deb8u1 Maintainer: Debian Virtualbox Team Uploaders: Ritesh Raj Sarraf , Gianfranco Costamagna Build-Depends: bzip2, debhelper (>= 9), default-jdk, dh-python, dkms (>= 2.1.1.1), docbook-xml, docbook-xsl, dpkg-dev (>= 1.15.6~), g++-multilib, genisoimage, gsoap (>= 2.8.16), iasl, imagemagick, kbuild (>= 1:0.1.9998svn2695), libasound2-dev, libcap-dev, libcurl4-gnutls-dev, libdevmapper-dev, libdrm-dev, libgl1-mesa-dev, libglu1-mesa-dev, libidl-dev, libpam0g-dev, libpixman-1-dev, libpng-dev, libpulse-dev, libqt4-dev (>= 4.4.0), libqt4-network (>= 4.4.0), libqt4-opengl-dev (>= 4.4.0), libsdl1.2-dev, libssl-dev, libvncserver-dev, libvpx-dev, libx11-dev, libxcomposite-dev, libxcursor-dev, libxdamage-dev, libxext-dev, libxi-dev, libxinerama-dev, libxml2-dev, libxmu-dev, libxrandr-dev, libxrender-dev, libxslt1-dev, libxt-dev, lsb-release, lynx-cur, makeself, module-assistant, python-dev (>= 2.6.6-3~), texlive-fonts-extra, texlive-fonts-recommended, texlive-latex-extra, texlive-latex-recommended, uuid-dev, x11proto-gl-dev, x11proto-xf86dri-dev, xserver-xorg-dev, xsltproc, yasm (>= 0.7.0) , zlib1g-dev Architecture: amd64 i386 all Standards-Version: 3.9.6 Format: 3.0 (quilt) Files: a21ddb4a21ad729519508d28b14e20b5 3696 virtualbox_4.3.36-dfsg-1+deb8u1.dsc 1423337a5a9970dda72e60fcaa0f8d05 47713148 virtualbox_4.3.36-dfsg.orig.tar.xz 8010c3b4e28f7910e44d9ec9ea9376ef 75292 virtualbox_4.3.36-dfsg-1+deb8u1.debian.tar.xz Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-virtualbox/virtualbox.git Vcs-Git: git://anonscm.debian.org/pkg-virtualbox/virtualbox.git Checksums-Sha1: 686d044b04e48816db96db89b425f3758ba80e26 3696 virtualbox_4.3.36-dfsg-1+deb8u1.dsc b458c3c7ce0f1e9081dbcde9e39325653962a449 47713148 virtualbox_4.3.36-dfsg.orig.tar.xz 55a72ca9a4ddcd19fa983b31f2a519273eea51b8 75292 virtualbox_4.3.36-dfsg-1+deb8u1.debian.tar.xz Checksums-Sha256: f5703f0247ad06c375f529ace969cee15627a4d670fc948f13e8c9ebef1f9710 3696 virtualbox_4.3.36-dfsg-1+deb8u1.dsc 09e7159d4e406ec9f0834e680bb4f3651519a5bbf535c8cc83fb635c2fd96f39 47713148 virtualbox_4.3.36-dfsg.orig.tar.xz d06cd6dde60e6cdfb44ac03feede7ce10bc6e720a38781cb2c9d84b0f7099bae 75292 virtualbox_4.3.36-dfsg-1+deb8u1.debian.tar.xz Homepage: http://www.virtualbox.org/ Package-List: virtualbox deb contrib/misc optional arch=amd64,i386 virtualbox-dbg deb contrib/debug extra arch=amd64,i386 virtualbox-dkms deb contrib/kernel optional arch=all virtualbox-guest-dkms deb contrib/kernel optional arch=all virtualbox-guest-source deb contrib/kernel optional arch=all virtualbox-guest-utils deb contrib/misc optional arch=amd64,i386 virtualbox-guest-x11 deb contrib/x11 optional arch=amd64,i386 virtualbox-qt deb contrib/misc optional arch=amd64,i386 virtualbox-source deb contrib/kernel optional arch=all Directory: pool/updates/contrib/v/virtualbox Priority: source Section: contrib/misc -- 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/1642386 Title: At least one invalid signature was encountered. Status in apt package in Ubuntu: New Bug description: Hello, a recent apt update appears to have broken apt entirely. A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/ To test, I upgraded my laptop then immediately re-ran apt-get update && apt-get -u dist-upgrade: sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease
[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.
Based on the funny git results, I re-installed the packages: 3243aa899fcf2f09b910b7429eeae6205a71c379a45c0e8e31723836bb094163 apt_1.2.12~ubuntu16.04.1_amd64.deb 5b9a82b1dc1f82fc3655038336d099410d643d5188629aba475050d7f9bd99c3 apt-transport-https_1.2.12~ubuntu16.04.1_amd64.deb 25af186c488f2b7f31dcef15776bfe4dd1a7a3c98a1d378937f07365eb9aa95a libapt-inst2.0_1.2.12~ubuntu16.04.1_amd64.deb b84273b8bfddea9aa5be26b2dd2e7ed449503a93c92ac5522fdfa74ae6f61c22 libapt-pkg5.0_1.2.12~ubuntu16.04.1_amd64.deb With these packages installed, apt-get update works as I expect: sarnold@hunt:/mnt/ubuntu/.zfs/snapshot/rsync.30/pool/main/a/apt$ sudo apt-get update Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease Hit:5 http://security.debian.org jessie/updates InRelease Hit:6 http://mirrors.kernel.org/ubuntu precise-updates InRelease Hit:7 http://mirrors.kernel.org/ubuntu precise-security InRelease Hit:8 http://mirrors.kernel.org/ubuntu precise-proposed InRelease Hit:9 http://security.debian.org wheezy/updates InRelease Ign:10 http://mirrors.kernel.org/ubuntu trusty InRelease Hit:11 http://mirrors.kernel.org/ubuntu trusty-updates InRelease Hit:12 http://mirrors.kernel.org/ubuntu trusty-security InRelease Hit:13 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease Hit:14 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease Hit:15 http://mirrors.kernel.org/ubuntu yakkety InRelease Ign:16 http://archive.canonical.com/ubuntu precise InRelease Hit:17 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid InRelease Hit:18 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:19 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease Hit:20 http://ftp.debian.org/debian unstable InRelease Hit:21 http://mirrors.kernel.org/ubuntu yakkety-security InRelease Hit:22 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease Hit:23 http://mirrors.kernel.org/ubuntu zesty InRelease Hit:24 http://mirrors.kernel.org/ubuntu zesty-updates InRelease Hit:25 http://mirrors.kernel.org/ubuntu zesty-security InRelease Hit:26 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease Ign:27 http://archive.canonical.com/ubuntu trusty InRelease Hit:28 http://ppa.launchpad.net/snappy-dev/image/ubuntu vivid InRelease Hit:29 http://mirrors.kernel.org/ubuntu precise Release Hit:30 http://ftp.debian.org/debian testing InRelease Hit:31 http://mirrors.kernel.org/ubuntu trusty Release Hit:32 http://archive.canonical.com/ubuntu xenial InRelease Hit:33 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial InRelease Ign:34 http://ftp.debian.org/debian jessie InRelease Hit:35 http://archive.canonical.com/ubuntu yakkety InRelease Hit:36 http://ftp.debian.org/debian jessie-updates InRelease Hit:37 http://archive.canonical.com/ubuntu zesty InRelease Ign:38 http://ftp.debian.org/debian wheezy InRelease Hit:39 http://archive.canonical.com/ubuntu precise Release Hit:40 http://ftp.debian.org/debian wheezy-updates InRelease Hit:41 http://archive.canonical.com/ubuntu trusty Release Hit:42 http://ftp.debian.org/debian jessie Release Hit:43 http://ftp.debian.or
[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.
I reinstalled the latest xenial packages: ii apt 1.2.15 amd64commandline package manager ii apt-transport-https 1.2.15 amd64https download transport for APT ii libapt-inst2.0:amd64 1.2.15 amd64deb package format runtime library ii libapt-pkg-perl 0.1.29build7 amd64Perl interface to libapt-pkg ii libapt-pkg5.0:amd64 1.2.15 amd64package management runtime library and now apt-get update is unhappy again: sarnold@hunt:/mnt/ubuntu/.zfs/snapshot/rsync.30/pool/main/a/apt$ sudo apt-get update Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease Hit:2 http://security.debian.org jessie/updates InRelease Hit:3 http://security.debian.org wheezy/updates InRelease Hit:4 http://mirrors.kernel.org/ubuntu xenial-updates InRelease Hit:5 http://mirrors.kernel.org/ubuntu xenial-security InRelease Ign:6 http://mirrors.kernel.org/ubuntu precise InRelease Hit:7 http://mirrors.kernel.org/ubuntu precise-updates InRelease Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease At least one invalid signature was encountered. Hit:8 http://mirrors.kernel.org/ubuntu precise-security InRelease Hit:9 http://mirrors.kernel.org/ubuntu precise-proposed InRelease Ign:10 http://mirrors.kernel.org/ubuntu trusty InRelease Err:2 http://security.debian.org jessie/updates InRelease At least one invalid signature was encountered. Hit:11 http://mirrors.kernel.org/ubuntu trusty-updates InRelease Hit:12 http://mirrors.kernel.org/ubuntu trusty-security InRelease Err:3 http://security.debian.org wheezy/updates InRelease At least one invalid signature was encountered. Hit:13 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease Hit:14 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease Hit:15 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid InRelease Ign:16 http://archive.canonical.com/ubuntu precise InRelease Get:17 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB] Err:4 http://mirrors.kernel.org/ubuntu xenial-updates InRelease At least one invalid signature was encountered. Hit:18 http://mirrors.kernel.org/ubuntu yakkety InRelease Hit:19 http://ftp.debian.org/debian unstable InRelease Hit:20 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease Hit:21 http://mirrors.kernel.org/ubuntu yakkety-security InRelease Err:5 http://mirrors.kernel.org/ubuntu xenial-security InRelease At least one invalid signature was encountered. Hit:22 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease Hit:23 http://mirrors.kernel.org/ubuntu zesty InRelease Err:7 http://mirrors.kernel.org/ubuntu precise-updates InRelease At least one invalid signature was encountered. Hit:24 http://mirrors.kernel.org/ubuntu zesty-updates InRelease Ign:25 http://archive.canonical.com/ubuntu trusty InRelease Hit:26 http://ppa.launchpad.net/snappy-dev/image/ubuntu vivid InRelease Hit:27 http://mirrors.kernel.org/ubuntu zesty-security InRelease Hit:28 http://ftp.debian.org/debian testing InRelease Err:8 http://mirrors.kernel.org/ubuntu precise-security InRelease At least one invalid signature was encountered. Hit:29
[Touch-packages] [Bug 1616107] Comment bridged from LTC Bugzilla
--- Comment From wil...@us.ibm.com 2016-11-17 19:00 EDT--- I can reproduce the problem using the following steps: brctl addbr boom brctl stp boom off brctl addif boom enP2p1s0f3 brctl delif boom enP2p1s0f3 enP2p1s0f3 is a port on a bnx2. The Oops will occur when "brctl delif" is run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1616107 Title: Kernel oops + system freeze on network-bridge shutdown Status in bridge-utils package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in bridge-utils source package in Xenial: Confirmed Status in linux source package in Xenial: Confirmed Status in bridge-utils source package in Yakkety: Confirmed Bug description: A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver. This error does not appear in Ubuntu 14.04 however. The error is reproducible whenever issuing the commands "shutdown", "service networking stop" or "brctl delbr br0". Manually creating the bridge and subsequently bringing it down results in the same error. /var/log/kern.log: [...] Aug 23 15:09:46 base1 kernel: [ 617.996677] device ens1f0 left promiscuous mode Aug 23 15:09:46 base1 kernel: [ 617.996699] br0: port 1(ens1f0) entered disabled state Aug 23 15:09:46 base1 kernel: [ 617.996730] BUG: unable to handle kernel NULL pointer dereference at 00d2 Aug 23 15:09:46 base1 kernel: [ 618.008306] IP: [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.020549] PGD 10374c0067 PUD 1033927067 PMD 0 Aug 23 15:09:46 base1 kernel: [ 618.032773] Oops: 0002 [#1] SMP Aug 23 15:09:46 base1 kernel: [ 618.044434] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio libcrc32c wmi fjes Aug 23 15:09:46 base1 kernel: [ 618.058563] CPU: 3 PID: 4049 Comm: brctl Not tainted 4.4.0-34-generic #53-Ubuntu Aug 23 15:09:46 base1 kernel: [ 618.058564] Hardware name: HP ProLiant DL120 Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016 Aug 23 15:09:46 base1 kernel: [ 618.058574] task: 881030676040 ti: 8810341e4000 task.ti: 8810341e4000 Aug 23 15:09:46 base1 kernel: [ 618.058576] RIP: 0010:[] [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058754] RSP: 0018:8810341e7d68 EFLAGS: 00010206 Aug 23 15:09:46 base1 kernel: [ 618.058769] RAX: RBX: RCX: Aug 23 15:09:46 base1 kernel: [ 618.058774] RDX: 881038470848 RSI: RDI: Aug 23 15:09:46 base1 kernel: [ 618.058775] RBP: 8810341e7d78 R08: R09: 8170d949 Aug 23 15:09:46 base1 kernel: [ 618.058776] R10: ead61340 R11: 8810329d2c00 R12: 00c0 Aug 23 15:09:46 base1 kernel: [ 618.058777] R13: 881030044000 R14: 881038470840 R15: Aug 23 15:09:46 base1 kernel: [ 618.058782] FS: 7f9aebc94700() GS:88107fcc() knlGS: Aug 23 15:09:46 base1 kernel: [ 618.058789] CS: 0010 DS: ES: CR0: 80050033 Aug 23 15:09:46 base1 kernel: [ 618.058790] CR2: 00d2 CR3: 00102fe83000 CR4: 001406e0 Aug 23 15:09:46 base1 kernel: [ 618.058802] Stack: Aug 23 15:09:46 base1 kernel: [ 618.058806] 8810356a4c00 8810341e7d98 c0489258 Aug 23 15:09:46 base1 kernel: [ 618.058822] 8810356a4c00 881038470840 8810341e7dc0 c0479bd8 Aug 23 15:09:46 base1 kernel: [ 618.058825] 881038470838 881038470848 88103847 8810341e7df8 Aug 23 15:09:46 base1 kernel: [ 618.058827] Call Trace: Aug 23 15:09:46 base1 kernel: [ 618.058863] [] nbp_vlan_flush+0x28/0x65 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058870] [] del_nbp+0x98/0x130 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058889] [] br_dev_delete+0x42/0xb0 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058895] [] br_del_bridge+0x4a/0x70 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058911] [] br_ioctl_deviceless_stub+0x153/0x230 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058984
[Touch-packages] [Bug 1422795] Re: bash crashes often if inputrc contains revert-all-at-newline
Hello Sven, or anyone else affected, Accepted bash into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bash/4.3-7ubuntu1.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: bash (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1422795 Title: bash crashes often if inputrc contains revert-all-at-newline Status in bash package in Ubuntu: Fix Released Status in bash source package in Trusty: Fix Committed Status in bash package in Debian: Fix Released Bug description: Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341 The Debian bug includes complete reproduction case. Basically: with .inputrc containing set revert-all-at-newline On Go back in the commandline history, edit a command, then submit a different command (may be empty) Such as: $ ls something $ Attached diff is confirmed to fix the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bash 4.3-7ubuntu1.5 [origin: goobuntu-trusty-testing-desktop] ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Feb 17 15:49:30 2015 SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.bash.bashrc: [modified] mtime.conffile..etc.bash.bashrc: 2015-01-27T03:27:18.751405 [Test Case] Adapted from the Debian bug report: 1. echo "set revert-all-at-newline on" > bug.inputrc 2. INPUTRC=bug.inputrc bash 3. echo hello 4. ^P^U^N^M [Hold down control and type "punm".] Bash should die immediately with SIGABRT. [Regression Potential] Relatively low. The change has no effect at all unless _rl_revert_all_lines() is called, which only happens if revert-all-at-newline is set, and then only when a newline is typed. So, the potential for regression is essentially zero for non-interactive shells and for anyone not using revert-all-at-newline (which is not the default). Further, this change appeared upstream and in both Debian and Ubuntu over a year ago, so it's had plenty of public testing. lib/readline/misc.c:_rl_revert_all_lines() contains a loop which iterates over history entries, reverting changes to each history entry. This patch causes entry->data, which points to the per-entry undo list, to be cleared before reverting edits rather than after. At first glance, this shouldn't make any difference. However, it prevents rl_do_undo() from replacing the history entry with one reflecting the change. Otherwise, the entry gets freed, leaving _rl_revert_all_lines() with an invalid pointer. _Not_ having an invalid pointer and double-free certainly can't be worse than the current situation. Since we're avoiding is making the pointer invalid rather than not doing the free, the chance of a new leak is pretty much nonexistent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1422795/+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 1598300] Re: CUPS web interface stops responding after a while
Hello dominix, or anyone else affected, Accepted cups into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cups (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue
Hello Frank, or anyone else affected, Accepted openssl-ibmca into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl- ibmca/1.3.0-0ubuntu2.16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: openssl-ibmca (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1605511 Title: openssl engine error if trying to exploit hw crypto on z due to library issue Status in libica package in Ubuntu: Invalid Status in openssl package in Ubuntu: Invalid Status in openssl-ibmca package in Ubuntu: Fix Released Status in libica source package in Xenial: Invalid Status in openssl source package in Xenial: Invalid Status in openssl-ibmca source package in Xenial: Fix Committed Status in libica source package in Yakkety: Invalid Status in openssl source package in Yakkety: Invalid Status in openssl-ibmca source package in Yakkety: Fix Committed Bug description: [Testcase] * configure ibmca engine as per below instructions * execute openssl engine -c - * it should complete without any loading errors [Impact] * Out of the box stock configuration results in non-usable engine which errors out * Thus currently, without workarounds, the acceleration engine does not work. Meaning regression potential is low Please note this is the first time we are integrating openssl-ibmca, and it is not enabled by default. Hopefully things will be better / more stable going forward. openssl-ibmca usually requires libica2 and libica-utils for proper functioning and all required tooling (like icainfo, icastats, etc.) But after the installation of these packages and the configuration, with is like this: sudo tee -a /etc/ssl/openssl.cnf < /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample sudo vi /etc/ssl/openssl.cnf adding the following line as the first active one: openssl_conf = openssl_def and removing or commenting all other occurrences of that line in the config file and saving and closing the openssl.cnf file this output of the openssl engine command is expected: $ openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support or even more precise these chiphers should be listed in case of "-c": $ openssl engine -c (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512] But instead openssl is giving this error, due to a missing "libica.so": $ openssl engine Error configuring OpenSSL 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:260BC066:engine routines:INT_ENGINE_CONFIGURE:engine configuration error:eng_cnf.c:191:section=ibmca_section, name=init, value=1 4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module initialization error:conf_mod.c:223:module=engines, value=engine_section, retcode=-1 $ There is no libica.so that is shipped with any of the above packages (verified with dpkg -l) or otherwise available in the filesystem: $ s
[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths
** Branch linked: lp:~renatofilho/mediaplayer-app/shared-snappy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: Confirmed Status in address-book-service package in Ubuntu: New Status in dialer-app package in Ubuntu: In Progress Status in history-service package in Ubuntu: In Progress Status in indicator-bluetooth package in Ubuntu: New Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: New Status in indicator-location package in Ubuntu: New Status in indicator-messages package in Ubuntu: New Status in indicator-network package in Ubuntu: New Status in indicator-power package in Ubuntu: New Status in indicator-session package in Ubuntu: New Status in indicator-sound package in Ubuntu: New Status in indicator-transfer package in Ubuntu: New Status in mediascanner2 package in Ubuntu: New Status in messaging-app package in Ubuntu: In Progress Status in pay-service package in Ubuntu: New Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: New Status in ubuntu-keyboard package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: New Status in unity-scope-scopes package in Ubuntu: New Status in unity-scopes-api package in Ubuntu: In Progress Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
Possibly related: when the problem is triggered, I notice that my guest instances start with no /etc/resolv.conf and no inet address. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown Status in lxc package in Ubuntu: New Bug description: If I run lxc-start with umask 007 (or any other value that masks the world-execute bit), my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down my host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. I can reproduce this at will with either an old-ish container or a fresh new one. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1642767/+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 1642767] [NEW] starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
Public bug reported: If I run lxc-start with umask 007 (or any other value that masks the world-execute bit), my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down my host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. I can reproduce this at will with either an old-ish container or a fresh new one. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown Status in lxc package in Ubuntu: New Bug description: If I run lxc-start with umask 007 (or any other value that masks the world-execute bit), my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down my host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644]
[Touch-packages] [Bug 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
16.10 have unity-panel-service taking up 3.5 GB of RAM. I've mainly noticed it after resume, as Firefox randomly begins to crash/freeze before the entire system becomes unstable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in Unity HUD: Confirmed Status in Application Menu Indicator: Confirmed Status in Unity: Won't Fix Status in firefox package in Ubuntu: Incomplete Status in hud package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Status in firefox source package in Xenial: Incomplete Status in hud source package in Xenial: Confirmed Status in unity source package in Xenial: Invalid Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/987060/+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 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue
Hello Frank, or anyone else affected, Accepted openssl-ibmca into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl- ibmca/1.3.0-0ubuntu2.16.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: openssl-ibmca (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1605511 Title: openssl engine error if trying to exploit hw crypto on z due to library issue Status in libica package in Ubuntu: Invalid Status in openssl package in Ubuntu: Invalid Status in openssl-ibmca package in Ubuntu: Fix Released Status in libica source package in Xenial: Invalid Status in openssl source package in Xenial: Invalid Status in openssl-ibmca source package in Xenial: In Progress Status in libica source package in Yakkety: Invalid Status in openssl source package in Yakkety: Invalid Status in openssl-ibmca source package in Yakkety: Fix Committed Bug description: [Testcase] * configure ibmca engine as per below instructions * execute openssl engine -c - * it should complete without any loading errors [Impact] * Out of the box stock configuration results in non-usable engine which errors out * Thus currently, without workarounds, the acceleration engine does not work. Meaning regression potential is low Please note this is the first time we are integrating openssl-ibmca, and it is not enabled by default. Hopefully things will be better / more stable going forward. openssl-ibmca usually requires libica2 and libica-utils for proper functioning and all required tooling (like icainfo, icastats, etc.) But after the installation of these packages and the configuration, with is like this: sudo tee -a /etc/ssl/openssl.cnf < /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample sudo vi /etc/ssl/openssl.cnf adding the following line as the first active one: openssl_conf = openssl_def and removing or commenting all other occurrences of that line in the config file and saving and closing the openssl.cnf file this output of the openssl engine command is expected: $ openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support or even more precise these chiphers should be listed in case of "-c": $ openssl engine -c (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512] But instead openssl is giving this error, due to a missing "libica.so": $ openssl engine Error configuring OpenSSL 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:260BC066:engine routines:INT_ENGINE_CONFIGURE:engine configuration error:eng_cnf.c:191:section=ibmca_section, name=init, value=1 4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module initialization error:conf_mod.c:223:module=engines, value=engine_section, retcode=-1 $ There is no libica.so that is shipped with any of the above packages (verified with dpkg -l) or otherwise
[Touch-packages] [Bug 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue
** Description changed: [Testcase] * configure ibmca engine as per below instructions * execute openssl engine -c - * it should complete without any loading errors + [Impact] + * Out of the box stock configuration results in non-usable engine which errors out + * Thus currently, without workarounds, the acceleration engine does not work. Meaning regression potential is low - openssl-ibmca usually requires libica2 and libica-utils for proper functioning and all required tooling (like icainfo, icastats, etc.) + Please note this is the first time we are integrating openssl-ibmca, and + it is not enabled by default. Hopefully things will be better / more + stable going forward. + + openssl-ibmca usually requires libica2 and libica-utils for proper + functioning and all required tooling (like icainfo, icastats, etc.) But after the installation of these packages and the configuration, with is like this: sudo tee -a /etc/ssl/openssl.cnf < /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample sudo vi /etc/ssl/openssl.cnf adding the following line as the first active one: openssl_conf = openssl_def and removing or commenting all other occurrences of that line in the config file and saving and closing the openssl.cnf file this output of the openssl engine command is expected: $ openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support or even more precise these chiphers should be listed in case of "-c": $ openssl engine -c (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512] But instead openssl is giving this error, due to a missing "libica.so": $ openssl engine Error configuring OpenSSL 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:260BC066:engine routines:INT_ENGINE_CONFIGURE:engine configuration error:eng_cnf.c:191:section=ibmca_section, name=init, value=1 4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module initialization error:conf_mod.c:223:module=engines, value=engine_section, retcode=-1 $ There is no libica.so that is shipped with any of the above packages (verified with dpkg -l) or otherwise available in the filesystem: $ sudo find / -name "libica.so" 2>/dev/null ubuntu@HWE0001:~$ But there is a different verison of that libica: $ sudo find / -name "*libica.so*" 2>/dev/null /usr/lib/s390x-linux-gnu/libica.so.2 /usr/lib/s390x-linux-gnu/libica.so.2.6.1 $ So there are right now two workarounds: 1) creating a (symbolic) link from libica.so.2 to libica.so, like $ sudo ln -s /usr/lib/s390x-linux-gnu/libica.so.2 /usr/lib/s390x-linux-gnu/libica.so that allows openssl to find a library named 'libica.so': 18:15:00: frank.hei...@canonical.com: ubuntu@HWE0001:~$ openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support But this could lead to issues in case of any potential functions or interface changes there we introduced with libica.so.2 2) installation of the "libica-dev" package that provides a (development) version of libica.so: $ dpkg -L libica-dev | grep libica.so /usr/lib/s390x-linux-gnu/libica.so $ But the hardware crypto exploitation should work out of the box w/o the link or the libica-dev package. Either libica.so should be shipped (in addition to libica.so.2) with the proper dependency to openssl-ibmca - openssh-ibmca should make use of libica2 instead of libica.so.2... -- 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/1605511 Title: openssl engine error if trying to exploit hw crypto on z due to library issue Status in libica package in Ubuntu: Invalid Status in openssl package in Ubuntu: Invalid Status in openssl-ibmca package in Ubuntu: Fix Released Status in libica source
[Touch-packages] [Bug 1624641] Re: security updates with a new dependency don't get installed
Appears to be working ok now. thanks for the hard work brian and martin! :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1624641 Title: security updates with a new dependency don't get installed Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Released Bug description: Test Case - 1) Boot a xenial system w/o chromium browser and w/o libspeechd2 installed 2) Install the release version of chromium browser e.g. "sudo apt-get install chromium-browser=49.0.2623.108-0ubuntu1.1233 chromium-browser-l10n=49.0.2623.108-0ubuntu1.1233 chromium-codecs-ffmpeg-extra=49.0.2623.108-0ubuntu1.1233" 3) Run apt-get update if you didn't already 4) Run "sudo /usr/bin/unattended-upgrades -v -d" 5) Observe the following output "Checking: chromium-browser ([, ]) pkg 'libspeechd2' not in allowed origin sanity check failed" With the version of unattended-upgrades from -proposed libspeechd2 should be from an allowed origin and chromium-browser will get updated. Regression Potential This change modifies the behavior of unattended-upgrades such that new packages will be installed on a user's system and they may not except such behavior (e.g. why was libspeechd2 insalled?). However, this seems better than not installing security updates and leaving people's systems vulnerable to attack. Original Description E.g. chromium-browser has an update, but U-U does not update it. I saw in update-manager that the security update is available before running U-U. Afterwards I can install the update by update-manager. ProblemType: BugDistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:13:40 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: allSourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624641/+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 370066] Re: LSB 4.0 support
** Changed in: lsb (Ubuntu) Assignee: Mick bunching (micksta87) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/370066 Title: LSB 4.0 support Status in lsb package in Ubuntu: Fix Released Status in lsb source package in Hardy: Fix Released Status in lsb source package in Jaunty: Fix Released Bug description: Binary package hint: lsb Attached is a patch to include the proper information for the lsb package to support LSB 4.0. A similar patch will be filed against Debian soon. SRU justfication: with the release of LSB 4.0, third-party packages will begin to rely on its features, which will be relevant in the 8.04 LTS and 9.04 support timeframes. TEST CASE: because Ubuntu packages are not LSB packages, there is very little testing to be done here of the LSB functionality per se, beyond what testing the LSB upstream will do to check for compliance with the LSB. However, in Ubuntu the lsb-base and lsb-release packages also provide core functionality for our init scripts and other bits of the system, so testing should be done to make sure systems still boot correctly after the update and appear to work correctly in general. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/370066/+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 1642360] Re: Display occasionally stays on forever after boot in rc-proposed
This bug was fixed in the package ubuntu-touch-session - 0.108+17.04.20161117-0ubuntu1 --- ubuntu-touch-session (0.108+17.04.20161117-0ubuntu1) zesty; urgency=medium * Fix potential upstart job race between lightdm and keep-display-on- during-boot (LP: #1642360) (LP: #1642360) -- Alexandros Frantzis Thu, 17 Nov 2016 15:41:40 + ** Changed in: ubuntu-touch-session (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 ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1642360 Title: Display occasionally stays on forever after boot in rc-proposed Status in Canonical System Image: In Progress Status in ubuntu-touch-session package in Ubuntu: Fix Released Bug description: Occasionally the display stays on forever after boot in rc-proposed, due to a keep display on request. The problem seems to be that the keep-display-on-request introduced to fix bug 1623853, sometimes doesn't get released due to races in the upstart scripts. This happens if the lightdm job starts before the keep-display-on-during-boot job starts, in which case the keep- display-on-during-boot job never gets the signal it needs to stop ("stop on started lightdm"). This issue can be reproduced easily by changing the related upstart script timings, for example, by inserting a "sleep 10" at the end of the repowerd.conf pre-start stanza (or post-start stanza, it has the same effect). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642360/+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 370066] Re: LSB 4.0 support
** Changed in: lsb (Ubuntu) Assignee: Steve Langasek (vorlon) => Mick bunching (micksta87) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/370066 Title: LSB 4.0 support Status in lsb package in Ubuntu: Fix Released Status in lsb source package in Hardy: Fix Released Status in lsb source package in Jaunty: Fix Released Bug description: Binary package hint: lsb Attached is a patch to include the proper information for the lsb package to support LSB 4.0. A similar patch will be filed against Debian soon. SRU justfication: with the release of LSB 4.0, third-party packages will begin to rely on its features, which will be relevant in the 8.04 LTS and 9.04 support timeframes. TEST CASE: because Ubuntu packages are not LSB packages, there is very little testing to be done here of the LSB functionality per se, beyond what testing the LSB upstream will do to check for compliance with the LSB. However, in Ubuntu the lsb-base and lsb-release packages also provide core functionality for our init scripts and other bits of the system, so testing should be done to make sure systems still boot correctly after the update and appear to work correctly in general. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/370066/+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 1575319] Re: [Ubuntu Touch] Manage Scopes doesn't scroll up/down when modifying position
** Branch linked: lp:~josharenson/unity8/autoscroller-alternative -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1575319 Title: [Ubuntu Touch] Manage Scopes doesn't scroll up/down when modifying position Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Triaged Bug description: When managing the order of available scopes, if the list of scopes is longer than what can be shown on the screen, dragging scope to top or bottom of screen doesn't automatically begin to scroll screen. Scope would have to be dropped near then top, then scroll screen, then move scope into final position. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1575319/+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 1576424] Please test proposed package
Hello z3z, or anyone else affected, Accepted gtk+2.0 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.30-1ubuntu1.16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576424 Title: Gimp crashes with text tool & caps lock Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in gtk+2.0 source package in Xenial: Fix Committed Status in gtk+2.0 source package in Yakkety: Fix Committed Bug description: [Impact] Gimp crashes with a segfault when I use caps lock while renaming a layer. It is possible Caps lock causes crashes in other events also. [Test Case] Steps to reproduce: 1. Open a new blank gimp document 2. select the text tool 3. type a couple of words of text (gimp will create a text layer above the background layer) 4. with the text tool still selected, click on the background layer (just to move away from the text layer) 5. now double click on the text layer to rename the layer (layer name gets highlighted) 6. press the caps lock key 7. click on the background layer again (without renaming or doing anything to the text layer) Now repeat steps 5 and 6. Gimp crashes. [Regression Potential] None expected. The patch used has been taken from upstream development. https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad Packages for Xenial and Yakkety have been built in a PPA and regression tested. [ Other Info ] I can force this to happen every time I launch Gimp. Rebooting makes no difference. It seems to be the second time I press caps lock that forces the crash. I tried launching Gimp with caps lock on vs caps lock off, but I don't believe it made any difference. I can force a crash every time following the above sequence. I deleted my gimp preferences folder then rebooted for good measure. Gimp created a fresh preferences folder, but it hasn't solved the problem. I was originally in single window mode, but the new preferences folder put me back to multi window, but it crashes either way. I ran dmesg | tail after the crash and got the following line: gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0 error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000] I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver (available from the Additional Drivers tab). In that same tab, I also have enabled Processor microcode firmware for Intel CPUs. Terminal tells me Gimp version is 2.8.16-1ubuntu1 I'm not very experienced with bug reporting and not sure what other information I need to supply. Gimp was absolutely rock solid on this machine with 15.10, so it may be a Xubuntu issue. Hope someone can take a look at this. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1576424/+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 1576424] Re: Gimp crashes with text tool & caps lock
Hello z3z, or anyone else affected, Accepted gtk+2.0 into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.30-4ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gtk+2.0 (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: gtk+2.0 (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576424 Title: Gimp crashes with text tool & caps lock Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in gtk+2.0 source package in Xenial: Fix Committed Status in gtk+2.0 source package in Yakkety: Fix Committed Bug description: [Impact] Gimp crashes with a segfault when I use caps lock while renaming a layer. It is possible Caps lock causes crashes in other events also. [Test Case] Steps to reproduce: 1. Open a new blank gimp document 2. select the text tool 3. type a couple of words of text (gimp will create a text layer above the background layer) 4. with the text tool still selected, click on the background layer (just to move away from the text layer) 5. now double click on the text layer to rename the layer (layer name gets highlighted) 6. press the caps lock key 7. click on the background layer again (without renaming or doing anything to the text layer) Now repeat steps 5 and 6. Gimp crashes. [Regression Potential] None expected. The patch used has been taken from upstream development. https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad Packages for Xenial and Yakkety have been built in a PPA and regression tested. [ Other Info ] I can force this to happen every time I launch Gimp. Rebooting makes no difference. It seems to be the second time I press caps lock that forces the crash. I tried launching Gimp with caps lock on vs caps lock off, but I don't believe it made any difference. I can force a crash every time following the above sequence. I deleted my gimp preferences folder then rebooted for good measure. Gimp created a fresh preferences folder, but it hasn't solved the problem. I was originally in single window mode, but the new preferences folder put me back to multi window, but it crashes either way. I ran dmesg | tail after the crash and got the following line: gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0 error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000] I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver (available from the Additional Drivers tab). In that same tab, I also have enabled Processor microcode firmware for Intel CPUs. Terminal tells me Gimp version is 2.8.16-1ubuntu1 I'm not very experienced with bug reporting and not sure what other information I need to supply. Gimp was absolutely rock solid on this machine with 15.10, so it may be a Xubuntu issue. Hope someone can take a look at this. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1576424/+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 1447756] Re: [SRU] segfault in log.c code causes phone reboot loops
Not really. The bug is hugely intermittent as it stands. However, I can confirm we're experiencing this on our fleet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: [SRU] segfault in log.c code causes phone reboot loops Status in Canonical System Image: Fix Released Status in upstart : Fix Committed Status in upstart package in Ubuntu: Fix Released Status in upstart source package in Utopic: Won't Fix Status in upstart source package in Vivid: Won't Fix Status in upstart source package in Wily: Fix Released Status in upstart package in Ubuntu RTM: Fix Released Bug description: = Summary = The version of Upstart in vivid is affected by a coule of bugs relating to the flushing data from early-boot jobs to disk which can both result in a crash: == Problem 1 == An internal list is mishandled meaning a crash could occur randomly. == Problem 2 == Jobs which spawn processes in the background then themselves exit can cause a crash due. = Explanation of how Upstart flushes early job output = If an Upstart job starts *and ends* early in the boot sequence (before the log partition is mounted and writable) and produces output to its stdout/stderr, Upstart will cache the output for later flushing by adding the 'Log' object associated with the 'Job' to a list. When the log partition is mounted writable, the /etc/init/flush-early-job-log.conf job is run which calls "initctl notify-disk-writeable". This is a signal to Upstart to flush its cache of early-boot job output which takes the form of iterating the 'log_unflushed_files' list and flushing all the 'Log' entries to disk. = Code Specifics = There are 2 issues (note that the numbers used below match those used in the Summary). == Problem 1 detail == Due to a bug in the way the 'log_unflushed_files' list is handled (the 'Log' cannot be added to the list directly, so is added via an intermediary ('NihListElem') node), a crash can result when iterating the list since the 'Log' is freed, but NOT the intermediary node. The implication is that it is possible for the intermediary node to be attempt to dereference already-freed data, resulting in a crash. == Problem 2 detail == If a job spawns a process in the background, then itself exits, that jobs 'Log' entry will be added to the 'log_unflushed_files' list. But, if the background process produces output and then exits before Upstart attempts to flush the original jobs data to disk, the 'NihIo' corresponding to the log will be serviced automatically and the data flushed to disk. The problem comes when Upstart receives the notification to flush the 'log_unflushed_files' list, since that list now contains an entry which has already been freed (since all its data has already been flushed). The result is an assertion failure. = Fix = == Problem 1 fix == Correct the 'log_unflushed_files' list handling by freeing the 'NihListElem' (which will automatically free the 'Log' object), not by simply freeing the 'Log' object itself. * Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/ * New Upstart test added to avoid regression?: Yes. == Problem 2 fix == Correct the assumption that the only entries in the 'log_unflushed_files' list will always have data to flush by checking if there is in fact any data to flush; if not, remove the entry from the 'log_unflushed_files' list since it has already been handled automatically by the 'NihIo'. * Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix * New Upstart test added to avoid regression?: Yes. = Workarounds = If a system is affected by this bug, it will be manifested by a crash early in the boot sequence. To overcome the issue, either: a) Boot by adding "--no-log" to the kernel command-line. b) Disable the flush-early-job-log job (assuming the machine is bootable) by running the following: $ echo manual | sudo tee -a /etc/init/flush-early-job-log.override = Impact = The issue has been present in Upstart since logging was introduced but no known instances of crashes relating to these problems have been reported prior to this bug being reported (which relates the the issue being seen on a very small subset of specific Ubuntu Touch phone hardware where Upstart is used as the system init daemon). Note that vivid still uses Upstart for managing the graphical session, but now uses systemd by default for the system init daemon. Since the session (Upstart) init does not even require a flush-early-job-log, the exposure to both the bug and the updated fix codepath is extremely limited. = Test Case = This bug is extremely hard to surface so the approach is simply to check that the internal list can be iterated correctly by: 1) Booting the system
[Touch-packages] [Bug 1447756] Re: [SRU] segfault in log.c code causes phone reboot loops
Justin, please see comment #42. Can you provide a reproducer for this on trusty? That this has not been widely reported on 14.04 means it has not been a priority for fixing; less so now that a newer LTS release is available. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: [SRU] segfault in log.c code causes phone reboot loops Status in Canonical System Image: Fix Released Status in upstart : Fix Committed Status in upstart package in Ubuntu: Fix Released Status in upstart source package in Utopic: Won't Fix Status in upstart source package in Vivid: Won't Fix Status in upstart source package in Wily: Fix Released Status in upstart package in Ubuntu RTM: Fix Released Bug description: = Summary = The version of Upstart in vivid is affected by a coule of bugs relating to the flushing data from early-boot jobs to disk which can both result in a crash: == Problem 1 == An internal list is mishandled meaning a crash could occur randomly. == Problem 2 == Jobs which spawn processes in the background then themselves exit can cause a crash due. = Explanation of how Upstart flushes early job output = If an Upstart job starts *and ends* early in the boot sequence (before the log partition is mounted and writable) and produces output to its stdout/stderr, Upstart will cache the output for later flushing by adding the 'Log' object associated with the 'Job' to a list. When the log partition is mounted writable, the /etc/init/flush-early-job-log.conf job is run which calls "initctl notify-disk-writeable". This is a signal to Upstart to flush its cache of early-boot job output which takes the form of iterating the 'log_unflushed_files' list and flushing all the 'Log' entries to disk. = Code Specifics = There are 2 issues (note that the numbers used below match those used in the Summary). == Problem 1 detail == Due to a bug in the way the 'log_unflushed_files' list is handled (the 'Log' cannot be added to the list directly, so is added via an intermediary ('NihListElem') node), a crash can result when iterating the list since the 'Log' is freed, but NOT the intermediary node. The implication is that it is possible for the intermediary node to be attempt to dereference already-freed data, resulting in a crash. == Problem 2 detail == If a job spawns a process in the background, then itself exits, that jobs 'Log' entry will be added to the 'log_unflushed_files' list. But, if the background process produces output and then exits before Upstart attempts to flush the original jobs data to disk, the 'NihIo' corresponding to the log will be serviced automatically and the data flushed to disk. The problem comes when Upstart receives the notification to flush the 'log_unflushed_files' list, since that list now contains an entry which has already been freed (since all its data has already been flushed). The result is an assertion failure. = Fix = == Problem 1 fix == Correct the 'log_unflushed_files' list handling by freeing the 'NihListElem' (which will automatically free the 'Log' object), not by simply freeing the 'Log' object itself. * Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/ * New Upstart test added to avoid regression?: Yes. == Problem 2 fix == Correct the assumption that the only entries in the 'log_unflushed_files' list will always have data to flush by checking if there is in fact any data to flush; if not, remove the entry from the 'log_unflushed_files' list since it has already been handled automatically by the 'NihIo'. * Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix * New Upstart test added to avoid regression?: Yes. = Workarounds = If a system is affected by this bug, it will be manifested by a crash early in the boot sequence. To overcome the issue, either: a) Boot by adding "--no-log" to the kernel command-line. b) Disable the flush-early-job-log job (assuming the machine is bootable) by running the following: $ echo manual | sudo tee -a /etc/init/flush-early-job-log.override = Impact = The issue has been present in Upstart since logging was introduced but no known instances of crashes relating to these problems have been reported prior to this bug being reported (which relates the the issue being seen on a very small subset of specific Ubuntu Touch phone hardware where Upstart is used as the system init daemon). Note that vivid still uses Upstart for managing the graphical session, but now uses systemd by default for the system init daemon. Since the session (Upstart) init does not even require a flush-early-job-log, the exposure to both the bug and the updated fix codepath is extremely limited. = Test Case = This bug is extremely hard to surface so the
[Touch-packages] [Bug 1617564] Re: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is
** Also affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Changed in: account-plugins (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1617564 Title: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package account- plugin-facebook 0.12+16.04.20160126-0ubuntu1 Status in One Hundred Papercuts: Confirmed Status in account-plugins package in Ubuntu: Confirmed Status in kaccounts-providers package in Ubuntu: Confirmed Bug description: showing this error when installing kde environment in ubuntu 16.04. it say kaccounts niot installed. so i think it may cause some security issue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Aug 27 18:11:18 2016 DuplicateSignature: package:kaccounts-providers:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2016-08-25 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1617564/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
I'm surprised this is still a thing. I added the common systemd "restart network-manager on resume" script most folks with this issue have used. I added it quite a while ago. My system has been working consistently since then without issue... to the point I actually forgot that this bug existed. I understand the burning desire to fix the problem at hand, but months (soon to be a year) later, this issue still exists. I don't see the trade-off/downsides/consequences with this work-around being applied. If a downside does exist, I haven't seen it, but what I have seen is the benefit of it being in place as it circumvents this issue entirely. Sorry - I just don't see the point of this bug trailing on longer and longer while users unaware of the "restart network-manager on resume" fix continue to deal with the headache, while on the other hand, had that work-around been issued, folks wouldn't be as angry about this issue as they clearly are. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1642704] [NEW] initramfs-tools on Trusty doesn't handle symlinks in newer linux-firmware packages correctly
Public bug reported: $ update-initramfs -k 4.4.0-47-generic -c update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic $ sudo cat /boot/initrd.img-4.4.0-47-generic |unxz |cpio -i --no-absolute-filenames 185780 blocks $ ls lib/firmware/i915/ $ ls /lib/firmware/i915/ bxt_dmc_ver1_04.bin bxt_dmc_ver1.bin@skl_dmc_ver1.bin@ skl_guc_ver4_3.bin bxt_dmc_ver1_05.bin skl_dmc_ver1_23.bin skl_guc_ver1_1059.bin skl_guc_ver4.bin@ bxt_dmc_ver1_06.bin skl_dmc_ver1_26.bin skl_guc_ver1.bin@ $ ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1642704 Title: initramfs-tools on Trusty doesn't handle symlinks in newer linux- firmware packages correctly Status in initramfs-tools package in Ubuntu: Confirmed Bug description: $ update-initramfs -k 4.4.0-47-generic -c update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic $ sudo cat /boot/initrd.img-4.4.0-47-generic |unxz |cpio -i --no-absolute-filenames 185780 blocks $ ls lib/firmware/i915/ $ ls /lib/firmware/i915/ bxt_dmc_ver1_04.bin bxt_dmc_ver1.bin@skl_dmc_ver1.bin@ skl_guc_ver4_3.bin bxt_dmc_ver1_05.bin skl_dmc_ver1_23.bin skl_guc_ver1_1059.bin skl_guc_ver4.bin@ bxt_dmc_ver1_06.bin skl_dmc_ver1_26.bin skl_guc_ver1.bin@ $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642704/+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 1612367] Re: [Touch] Incoming call gets silent randomly
@Andrea, Anupam, Robie: That's interesting indeed and might explain why I've never been able to reproduce this myself. I would always have been actively engaged with the phone when trying to reproduce this. -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1642704] Re: initramfs-tools on Trusty doesn't handle symlinks in newer linux-firmware packages correctly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1642704 Title: initramfs-tools on Trusty doesn't handle symlinks in newer linux- firmware packages correctly Status in initramfs-tools package in Ubuntu: Confirmed Bug description: $ update-initramfs -k 4.4.0-47-generic -c update-initramfs: Generating /boot/initrd.img-4.4.0-47-generic $ sudo cat /boot/initrd.img-4.4.0-47-generic |unxz |cpio -i --no-absolute-filenames 185780 blocks $ ls lib/firmware/i915/ $ ls /lib/firmware/i915/ bxt_dmc_ver1_04.bin bxt_dmc_ver1.bin@skl_dmc_ver1.bin@ skl_guc_ver4_3.bin bxt_dmc_ver1_05.bin skl_dmc_ver1_23.bin skl_guc_ver1_1059.bin skl_guc_ver4.bin@ bxt_dmc_ver1_06.bin skl_dmc_ver1_26.bin skl_guc_ver1.bin@ $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642704/+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 1642617] Re: UITK FTBFS on Qt 5.7.1
** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1642617 Title: UITK FTBFS on Qt 5.7.1 Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: https://launchpadlibrarian.net/293820525/buildlog_ubuntu-zesty-amd64.ubuntu-ui-toolkit_1.3.2141+16.10.20161013.5build1~1_BUILDING.txt.gz --- cc1plus: all warnings being treated as errors Makefile:1005: recipe for target '.obj/header_ubuntutoolkitmodule.o' failed make[3]: *** [.obj/header_ubuntutoolkitmodule.o] Error 1 --- https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1642617/+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 1642707] Re: initramfs-tools on Trusty doesn't include i915_bpo.ko
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1642707 Title: initramfs-tools on Trusty doesn't include i915_bpo.ko Status in initramfs-tools package in Ubuntu: Confirmed Bug description: initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems on Skylake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642707/+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 1642707] Re: initramfs-tools on Trusty doesn't include i915_bpo.ko
Bug is on hooks/framebuffer: add a line "copy_modules_dir kernel/ubuntu/i915" -- 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/1642707 Title: initramfs-tools on Trusty doesn't include i915_bpo.ko Status in initramfs-tools package in Ubuntu: Confirmed Bug description: initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems on Skylake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642707/+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 1642707] [NEW] initramfs-tools on Trusty doesn't include i915_bpo.ko
Public bug reported: initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems on Skylake ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: trusty ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1642707 Title: initramfs-tools on Trusty doesn't include i915_bpo.ko Status in initramfs-tools package in Ubuntu: Confirmed Bug description: initramfs-tools on Trusty doesn't include i915_bpo.ko, causing problems on Skylake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1642707/+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 1642122] Re: Screen flashes when "flash" is disabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: camera-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1642122 Title: Screen flashes when "flash" is disabled Status in camera-app package in Ubuntu: Confirmed Bug description: When using the camera app the screen flashes bright white - this was implemented for illuminating your face when using the camera pointing towards you https://bugs.launchpad.net/camera-app/+bug/1124574 However, when using the camera pointing away from you, and when using the camera with "flash" disabled, the screen still flashes bright white. This has caused a museum I visited that has a ban on flash photography to think I was still using flash even though it was specifically disabled - the screen flash was bright enough to be "disturbing" what they didn't want exposed to bright light, or at least catch enough attention to be confused with having the flash on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1642122/+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 1590321] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:get_dpkg_log_content
This bug was fixed in the package unattended-upgrades - 0.92ubuntu1.1 --- unattended-upgrades (0.92ubuntu1.1) yakkety; urgency=medium * Modify data/50unattended-upgrades.Ubuntu such that the release pocket is an allowed origin so that security updates with a new dependency will be upgraded and the new dependency will be installed. (LP: #1624641) * Create logfile_dpkg if it does not exist so that the file can be read later, thereby preventing a FileNotFound crash. (LP: #1590321) * Create the directory /var/lib/apt/periodic/, if it does not exist, so that we don't receive a Traceback when trying to write a stampfile there. (LP: #1639977) -- Brian Murray Mon, 07 Nov 2016 12:41:10 -0800 ** Changed in: unattended-upgrades (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1590321 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:get_dpkg_log_content Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Released Status in unattended-upgrades source package in Zesty: Fix Released Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo /usr/bin/unattended-upgrades (to update the system) 4) sudo /usr/bin/unattended-upgrades (a second time for some reason) 5) sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 6) sudo /usr/bin/unattended-upgrades Observe the following crash: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1406, in main log_content = get_dpkg_log_content(logfile_dpkg, install_start_time) File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content with io.open(logfile_dpkg, encoding='utf-8') as fp: FileNotFoundError: [Errno 2] No such file or directory: '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' With the version of the package from -proposed you won't receive the crash in step 6 and /var/log/unattended-upgrades/unattended-upgrades- dpkg.log will exist. Regression Potential This patch just ends up creating a file if it does not exist. Potential regressions would be a result of the patch being typo'ed e.g. typo'ing os.path.exits instead of os.path.exists and the code failing when a logfile does exist. So read the patch carefully! Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with version 0.90, the problem page at https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1590321/+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 1624641] Re: security updates with a new dependency don't get installed
This bug was fixed in the package unattended-upgrades - 0.92ubuntu1.1 --- unattended-upgrades (0.92ubuntu1.1) yakkety; urgency=medium * Modify data/50unattended-upgrades.Ubuntu such that the release pocket is an allowed origin so that security updates with a new dependency will be upgraded and the new dependency will be installed. (LP: #1624641) * Create logfile_dpkg if it does not exist so that the file can be read later, thereby preventing a FileNotFound crash. (LP: #1590321) * Create the directory /var/lib/apt/periodic/, if it does not exist, so that we don't receive a Traceback when trying to write a stampfile there. (LP: #1639977) -- Brian Murray Mon, 07 Nov 2016 12:41:10 -0800 ** Changed in: unattended-upgrades (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1624641 Title: security updates with a new dependency don't get installed Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Released Bug description: Test Case - 1) Boot a xenial system w/o chromium browser and w/o libspeechd2 installed 2) Install the release version of chromium browser e.g. "sudo apt-get install chromium-browser=49.0.2623.108-0ubuntu1.1233 chromium-browser-l10n=49.0.2623.108-0ubuntu1.1233 chromium-codecs-ffmpeg-extra=49.0.2623.108-0ubuntu1.1233" 3) Run apt-get update if you didn't already 4) Run "sudo /usr/bin/unattended-upgrades -v -d" 5) Observe the following output "Checking: chromium-browser ([, ]) pkg 'libspeechd2' not in allowed origin sanity check failed" With the version of unattended-upgrades from -proposed libspeechd2 should be from an allowed origin and chromium-browser will get updated. Regression Potential This change modifies the behavior of unattended-upgrades such that new packages will be installed on a user's system and they may not except such behavior (e.g. why was libspeechd2 insalled?). However, this seems better than not installing security updates and leaving people's systems vulnerable to attack. Original Description E.g. chromium-browser has an update, but U-U does not update it. I saw in update-manager that the security update is available before running U-U. Afterwards I can install the update by update-manager. ProblemType: BugDistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:13:40 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: allSourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624641/+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 1639977] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file
This bug was fixed in the package unattended-upgrades - 0.92ubuntu1.1 --- unattended-upgrades (0.92ubuntu1.1) yakkety; urgency=medium * Modify data/50unattended-upgrades.Ubuntu such that the release pocket is an allowed origin so that security updates with a new dependency will be upgraded and the new dependency will be installed. (LP: #1624641) * Create logfile_dpkg if it does not exist so that the file can be read later, thereby preventing a FileNotFound crash. (LP: #1590321) * Create the directory /var/lib/apt/periodic/, if it does not exist, so that we don't receive a Traceback when trying to write a stampfile there. (LP: #1639977) -- Brian Murray Mon, 07 Nov 2016 12:41:10 -0800 ** Changed in: unattended-upgrades (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1639977 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:write_stamp_file Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Released Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo rm -fr /var/lib/apt/periodic 4) sudo /usr/bin/unattended-upgrade 5) observe the following Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1419, in main write_stamp_file() File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"): FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/periodic/unattended-upgrades-stamp' With the version of the package from -proposed you'll receive no such Traceback. Regression Potential This patch just ends up creating a directory if it does not exist. Potential regressions would be a result of the patch being typo'ed e.g. typo'ing os.path.exits instead of os.path.exists and the code failing when a statedir does exist. So read the patch carefully! Original description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1639977/+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 1612367] Re: [Touch] Incoming call gets silent randomly
I can reproduce this fairly reliably (~50%) if my phone hasn't been used in a while. Enough that I've caught a video of it doing it. media- hub.log attached. If I unlock the phone and go into the sound settings (from the sound indicator), then turn the screen off, then the phone reliably doesn't fail a second time. I believe there's some race associated with slow I/O. Perhaps it happens if relevant code paths need to be swapped in on an incoming call? I also believe this is a regression in the last or previous OTA. Please ping me on IRC (rbasak) if I can help further with debugging this. ** Attachment added: "media-hub.log" https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1612367/+attachment/4778735/+files/media-hub.log -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1612367] Re: [Touch] Incoming call gets silent randomly
This part from the description of bug #1642635 sounds interesting: "It seems to me that this is most likely to happen if I haven't used the phone in a while. If I answer the call (because I notice the screen) or make a call, testing immediately after the phone does seem to consistently ring." I experienced the same. Once I couldn't pick up the call because of no ringtone. Then I called the same person after ~5 minutes and asked them to call me back in an attempt to reproduce the issue. They called after ~5 minutes, but that time the ringer worked fine. Also as I mentioned in comment #18, I got two calls within ~1 minute. First one didn't ring, but the second one rang. -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1590321] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1590321 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:get_dpkg_log_content Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Committed Status in unattended-upgrades source package in Zesty: Fix Released Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo /usr/bin/unattended-upgrades (to update the system) 4) sudo /usr/bin/unattended-upgrades (a second time for some reason) 5) sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 6) sudo /usr/bin/unattended-upgrades Observe the following crash: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1406, in main log_content = get_dpkg_log_content(logfile_dpkg, install_start_time) File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content with io.open(logfile_dpkg, encoding='utf-8') as fp: FileNotFoundError: [Errno 2] No such file or directory: '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' With the version of the package from -proposed you won't receive the crash in step 6 and /var/log/unattended-upgrades/unattended-upgrades- dpkg.log will exist. Regression Potential This patch just ends up creating a file if it does not exist. Potential regressions would be a result of the patch being typo'ed e.g. typo'ing os.path.exits instead of os.path.exists and the code failing when a logfile does exist. So read the patch carefully! Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with version 0.90, the problem page at https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1590321/+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 1590321] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:get_dpkg_log_content
This bug was fixed in the package unattended-upgrades - 0.90ubuntu0.2 --- unattended-upgrades (0.90ubuntu0.2) xenial-proposed; urgency=medium * Create logfile_dpkg if it does not exist so that the file can be read later, thereby preventing a FileNotFound crash. (LP: #1590321) * Create the directory /var/lib/apt/periodic/, if it does not exist, so that we don't receive a Traceback when trying to write a stampfile there. (LP: #1639977) -- Brian Murray Mon, 07 Nov 2016 14:38:04 -0800 ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1590321 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:get_dpkg_log_content Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Committed Status in unattended-upgrades source package in Zesty: Fix Released Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo /usr/bin/unattended-upgrades (to update the system) 4) sudo /usr/bin/unattended-upgrades (a second time for some reason) 5) sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 6) sudo /usr/bin/unattended-upgrades Observe the following crash: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1406, in main log_content = get_dpkg_log_content(logfile_dpkg, install_start_time) File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content with io.open(logfile_dpkg, encoding='utf-8') as fp: FileNotFoundError: [Errno 2] No such file or directory: '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' With the version of the package from -proposed you won't receive the crash in step 6 and /var/log/unattended-upgrades/unattended-upgrades- dpkg.log will exist. Regression Potential This patch just ends up creating a file if it does not exist. Potential regressions would be a result of the patch being typo'ed e.g. typo'ing os.path.exits instead of os.path.exists and the code failing when a logfile does exist. So read the patch carefully! Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with version 0.90, the problem page at https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1590321/+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 1639977] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1639977 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:write_stamp_file Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Committed Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo rm -fr /var/lib/apt/periodic 4) sudo /usr/bin/unattended-upgrade 5) observe the following Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1419, in main write_stamp_file() File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"): FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/periodic/unattended-upgrades-stamp' With the version of the package from -proposed you'll receive no such Traceback. Regression Potential This patch just ends up creating a directory if it does not exist. Potential regressions would be a result of the patch being typo'ed e.g. typo'ing os.path.exits instead of os.path.exists and the code failing when a statedir does exist. So read the patch carefully! Original description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1639977/+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 1639977] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file
This bug was fixed in the package unattended-upgrades - 0.90ubuntu0.2 --- unattended-upgrades (0.90ubuntu0.2) xenial-proposed; urgency=medium * Create logfile_dpkg if it does not exist so that the file can be read later, thereby preventing a FileNotFound crash. (LP: #1590321) * Create the directory /var/lib/apt/periodic/, if it does not exist, so that we don't receive a Traceback when trying to write a stampfile there. (LP: #1639977) -- Brian Murray Mon, 07 Nov 2016 14:38:04 -0800 ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1639977 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:write_stamp_file Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Committed Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo rm -fr /var/lib/apt/periodic 4) sudo /usr/bin/unattended-upgrade 5) observe the following Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1419, in main write_stamp_file() File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"): FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/periodic/unattended-upgrades-stamp' With the version of the package from -proposed you'll receive no such Traceback. Regression Potential This patch just ends up creating a directory if it does not exist. Potential regressions would be a result of the patch being typo'ed e.g. typo'ing os.path.exits instead of os.path.exists and the code failing when a statedir does exist. So read the patch carefully! Original description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1639977/+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 1642685] [NEW] problems with drivers
Public bug reported: I am having several problems, I lose my mouse pad from time to time, I have also noticed that I am having issues with the screen, but I am not sure if this is a problem or not, sometimes when I travel up to the top using the mouse the problem starts with the way that it displays, hard to explain, distorts sometimes.Have also noticed just recently a problem with the software center installed a new app today and it would not show the installation process, froze with the installation screen showing what was in the information about the program, the app still installed.I feel that the O.S. should be working better than what it is, maybe I am comparing it to Micro soft, I am not fully familiar with this O.S. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Nov 17 13:44:59 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: langford, 0.0.20130108, 4.4.0-43-generic, x86_64: installed langford, 0.0.20130108, 4.4.0-45-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1022] InstallationDate: Installed on 2016-10-05 (43 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 2386:0401 Bus 001 Device 002: ID 04f2:b520 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire R3-131T ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=6686fbd6-4da5-4729-af86-2319fb4418c8 ro plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire R3-131T dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd07/21/2015:svnAcer:pnAspireR3-131T:pvrV1.09:rvnAcer:rnAspireR3-131T:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.name: Aspire R3-131T dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Nov 17 08:02:37 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4188 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1642685 Title: problems with drivers Status in xorg package in Ubuntu: New Bug description: I am having several problems, I lose my mouse pad from time to time, I have also noticed that I am having issues with the screen, but I am not sure if this is a problem or not, sometimes when I travel up to the top using the mouse the problem starts with the way that it displays, hard to explain, distorts sometimes.Have also noticed just recently a problem with the software center installed a new app today and it would not show the installation process, froze with the installation screen showing what was in the information about the program, the app still installed.I feel that the O.S. should be working better than what it is, maybe I am comparing it to Micro soft, I am not fully familiar with this O.S. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package:
[Touch-packages] [Bug 1642078] Re: Black screen at startup
This is a big problem with amdgpu on the Carrizo card. The screen just goes black, and I am unable to get it to do otherwise, even after rebooting. Using nomodeset as a kernel parameter during grub boot-up allows me to boot it up in low-graphics mode. I do not have this issue in Ubuntu 14.04, since Ubuntu 14.04 still allows users to install fglrx/Catalyst, which works perfectly with Carrizo. But support for that package has been dropped in later installments of 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/1642078 Title: Black screen at startup Status in xorg package in Ubuntu: Confirmed Bug description: Problem description: The laptop starts up fine but the screen is black; even though the screen is black I can hear the drum sound prompting me to log in. After rebooting laptop all is well with the screen and I have a fully functional system. Sometimes, though, I have to restart twice. After some search I found people reporting the same issue: https://ubuntuforums.org/showthread.php?t=2337274 or similar issues: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1577074?comments=all Additional information: 1) Ubuntu release: Description: Ubuntu 16.04.1 LTS Release: 16.04 2) Package version: xorg: Instalados: 1:7.7+13ubuntu3 Candidato: 1:7.7+13ubuntu3 Tabla de versión: *** 1:7.7+13ubuntu3 500 500 http://co.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) Computer information: Processor: AMD A10-8700 Radeon R6 Graphic card: Gallium 0.4 on AMD Carrizo (DRM 3.1.0, LLVM 3.8.0) Kind regards, Victor ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 15 17:56:57 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:8246] InstallationDate: Installed on 2016-11-10 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Pavilion Notebook ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8246 dmi.board.vendor: HP dmi.board.version: 98.11 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.03:bd05/03/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn8246:rvr98.11:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Nov 15 17:21:18 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1642078/+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 1642078] Re: Black screen at startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1642078 Title: Black screen at startup Status in xorg package in Ubuntu: Confirmed Bug description: Problem description: The laptop starts up fine but the screen is black; even though the screen is black I can hear the drum sound prompting me to log in. After rebooting laptop all is well with the screen and I have a fully functional system. Sometimes, though, I have to restart twice. After some search I found people reporting the same issue: https://ubuntuforums.org/showthread.php?t=2337274 or similar issues: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1577074?comments=all Additional information: 1) Ubuntu release: Description: Ubuntu 16.04.1 LTS Release: 16.04 2) Package version: xorg: Instalados: 1:7.7+13ubuntu3 Candidato: 1:7.7+13ubuntu3 Tabla de versión: *** 1:7.7+13ubuntu3 500 500 http://co.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) Computer information: Processor: AMD A10-8700 Radeon R6 Graphic card: Gallium 0.4 on AMD Carrizo (DRM 3.1.0, LLVM 3.8.0) Kind regards, Victor ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 15 17:56:57 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:8246] InstallationDate: Installed on 2016-11-10 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Pavilion Notebook ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8246 dmi.board.vendor: HP dmi.board.version: 98.11 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.03:bd05/03/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn8246:rvr98.11:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Nov 15 17:21:18 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1642078/+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 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)
This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu12.4 --- isc-dhcp (4.3.3-5ubuntu12.4) xenial; urgency=medium * ipv6: wait for duplicate address detection to finish (LP: #1633479). -- Scott Moser Mon, 31 Oct 2016 14:32:14 -0400 ** Changed in: isc-dhcp (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1633479 Title: dhclient does not wait for ipv6 dad (duplicate address detection) Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Precise: Fix Committed Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Xenial: Fix Released Status in isc-dhcp source package in Yakkety: Fix Committed Bug description: dhclient -6 does not wait for an interface go through duplicate address detection. As a result the following will almost always fail: $ dev=eth0 $ ip link set down dev $dev $ dhclient -6 -1 -v eth0 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. $ echo $? 1 Related bugs: * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign requested address * bug 1633562: 'dhclient -6 -S' does not bring interface up ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: isc-dhcp-client 4.3.3-5ubuntu15 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 09:18:52 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (449 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+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 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)
** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1633479 Title: dhclient does not wait for ipv6 dad (duplicate address detection) Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Precise: Fix Committed Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Xenial: Fix Released Status in isc-dhcp source package in Yakkety: Fix Committed Bug description: dhclient -6 does not wait for an interface go through duplicate address detection. As a result the following will almost always fail: $ dev=eth0 $ ip link set down dev $dev $ dhclient -6 -1 -v eth0 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. $ echo $? 1 Related bugs: * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign requested address * bug 1633562: 'dhclient -6 -S' does not bring interface up ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: isc-dhcp-client 4.3.3-5ubuntu15 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 09:18:52 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (449 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+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 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'
Looks like this is still on in 1:6.6p1-2ubuntu2.8 version of openssh- client and server -- 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/1254085 Title: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY' Status in openssh package in Ubuntu: Confirmed Bug description: ssh -vvv is failing for me where is a VPN system. VPN is configured and connected via network-manager. Last messages from ssh (hangs forever): debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY = Workaround = $ sudo apt-get install putty $ putty This works perfectly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.4p1-1 ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0 Uname: Linux 3.12.0-3-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Fri Nov 22 15:37:18 2013 InstallationDate: Installed on 2010-10-21 (1128 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) RelatedPackageVersions: ssh-askpass 1:1.2.4.1-9 libpam-sshN/A keychain 2.7.1-1 ssh-askpass-gnome 1:6.4p1-1 SSHClientVersion: OpenSSH_6.4p1 Ubuntu-1, OpenSSL 1.0.1e 11 Feb 2013 SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2013-11-01 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+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 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags
This bug was fixed in the package klibc - 2.0.3-0ubuntu1.14.04.2 --- klibc (2.0.3-0ubuntu1.14.04.2) trusty; urgency=medium * debian/patches/fix_broadcast_flag-bit.patch: the previous patch set the wrong bit in the bootp flags field, instead of 0x800 it must be 0x8000. (LP: #1624014) -- Dan Streetman Tue, 20 Sep 2016 14:07:24 -0500 ** Changed in: klibc (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1624014 Title: Wrong bit set in klibc PXE dhcp/bootp flags Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: Fix Released Status in klibc source package in Xenial: Fix Released Status in klibc source package in Yakkety: Fix Released Bug description: [Description] The patch for bug 1327412 set the wrong bit in the bootp flags field. It set flags to 0x800, but the correct value is 0x8000. That sets the "broadcast" bit, and the spec requires all other bits to be 0. Setting one of the "must be zero" bits in the flags field causes some DHCP relay agents to drop the packets, causing PXE to fail. [Test Case] Get a DHCP relay agent that drops PXE packets with an invalid bootp.flags bit set, and try to PXE boot; it fails. [Regression] None, the previous patch introduced this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+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 1641975] Re: Noise and distortion
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluetooth-touch (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluetooth-touch in Ubuntu. https://bugs.launchpad.net/bugs/1641975 Title: Noise and distortion Status in bluetooth-touch package in Ubuntu: Confirmed Bug description: I'm trying to use my Meizu Pro 5 Ubuntu to connect to bluetooth car systems for making phone calls. Previously I hav a system based on Windows CE 6. When I had connected to the system and made or answered a call I always heart a lot of noise and distortion. I was just able to recognise the voice at the other side of the line, but not able to understand and words. My old HTC HD2 worked fine on that car system. I recently got a new car with a Pioneer multimedia set in it (F960DAB). I was hoping and expecting that bluetooth would work well now. Unfortunately I still have the same problem (noise and distortion). I also had the problem of answering a call and the car system would still ring while the phone had answered the call already. I upgraded the Pioneer to the latest firmware/bluetooth version and still had the same sound problems. At that time I also had the disconnection problem reported in other bugs, but when I told the phone to forget the system and re-paired the connection was constant avalable again. The sound is still big noise and distortion. Our Iphone works fine on the Pioneer set. My phone uses Ubuntu 15.04 (OTA-13). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1641975/+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 1641975] Re: Noise and distortion
Same issue with my Meizu Pro 5 (OTA-13). Tried both Sony MBH10, and car handsfree as well.To both of them the phone is connects withouth an issue, the music playback works great, but phone calls are distorting not being able to understand a word from the other side. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluetooth-touch in Ubuntu. https://bugs.launchpad.net/bugs/1641975 Title: Noise and distortion Status in bluetooth-touch package in Ubuntu: Confirmed Bug description: I'm trying to use my Meizu Pro 5 Ubuntu to connect to bluetooth car systems for making phone calls. Previously I hav a system based on Windows CE 6. When I had connected to the system and made or answered a call I always heart a lot of noise and distortion. I was just able to recognise the voice at the other side of the line, but not able to understand and words. My old HTC HD2 worked fine on that car system. I recently got a new car with a Pioneer multimedia set in it (F960DAB). I was hoping and expecting that bluetooth would work well now. Unfortunately I still have the same problem (noise and distortion). I also had the problem of answering a call and the car system would still ring while the phone had answered the call already. I upgraded the Pioneer to the latest firmware/bluetooth version and still had the same sound problems. At that time I also had the disconnection problem reported in other bugs, but when I told the phone to forget the system and re-paired the connection was constant avalable again. The sound is still big noise and distortion. Our Iphone works fine on the Pioneer set. My phone uses Ubuntu 15.04 (OTA-13). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1641975/+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 1266492] Re: ld:i386 crashes with -static -fPIE -pie
** Changed in: binutils (Ubuntu Trusty) Assignee: (unassigned) => Diego (dmggears3) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1266492 Title: ld:i386 crashes with -static -fPIE -pie Status in GLibC: Incomplete Status in binutils package in Ubuntu: Confirmed Status in eglibc package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in binutils source package in Trusty: Confirmed Status in eglibc source package in Trusty: Fix Released Status in evolution-data-server source package in Trusty: Triaged Status in xorg-server source package in Trusty: Fix Released Status in eglibc package in Debian: Fix Released Bug description: Making a simple file conftest.c with the following contents: int main() { return 0; } And then compiling it on i386 with gcc -fPIE -pie -static conftest.c returns: *** Error in `/usr/bin/ld': corrupted double-linked list: 0x08dddb38 *** This breaks compilation xorg-server on i386. I believe that -static -fPIE -pie is probably invalid, and it fails on amd64 too. $ gcc -fPIE -pie -static conftest.c /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginT.o: relocation R_X86_64_32 against `__TMC_END__' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginT.o: error adding symbols: Bad value collect2: error: ld returned 1 exit status But autoconf hangs on the corrupted double-linked list, which times out the xorg-server build. To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1266492/+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 1642634] Re: indicator-datetime uses excessive memory
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1642634 Title: indicator-datetime uses excessive memory Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: On my Aquaris 4.5, OTA-13, indicator-datetime 15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS is 315892, almost three times as much as unity8. I believe this is an OTA regression. I'm not sure if it regressed from OTA-11 or OTA-12. Just now, I got caught in an oom killer loop with constant killing of unity8-dash because of this, making my phone unusable. I had to kill indicator-datetime manually. It then restarted automatically and now uses 80456 RSS only. I see bug 1633319 exists complaining about a memory leak. It's not exactly the same version since mine is 15.10+15.04.20160820.1-0ubuntu1 and that one is 15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are the same or something? Perhaps the two are dupes, but I'll let someone more familiar make that determination. I have only a handful of alarms (perhaps five on average; rarely more) but I do have my Google calendar syncing with perhaps hundreds of events. However, there's no reason that this should cause indicator- datetime to use more RSS; it shouldn't be keeping these in memory. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+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 1642638] Re: backspace is not working on upright bq e5
also please post a screenshot and the version of the OS (you can find that in system settings) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1642638 Title: backspace is not working on upright bq e5 Status in unity8 package in Ubuntu: Incomplete Bug description: Hi, I bought last week bq e5 ubuntu, just updated the system. have problem with backspace deleting on upright (default position,power button upper right) it does not work on horrizontally it works in both directions on upright buttom up(power button down left) it also works "only" the default position does not work see questions: https://answers.launchpad.net/ubuntu/+source/unity8/+question/404069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1642638/+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 1642638] Re: backspace is not working on upright bq e5
I'm afraid it's not clear what you're trying to do and what is not working. Can you please describe a bit more, what app are you using, what "backspace" are you referring to? Are you using a keyboard connected to the phone? ** Changed in: unity8 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1642638 Title: backspace is not working on upright bq e5 Status in unity8 package in Ubuntu: Incomplete Bug description: Hi, I bought last week bq e5 ubuntu, just updated the system. have problem with backspace deleting on upright (default position,power button upper right) it does not work on horrizontally it works in both directions on upright buttom up(power button down left) it also works "only" the default position does not work see questions: https://answers.launchpad.net/ubuntu/+source/unity8/+question/404069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1642638/+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 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up
** Merge proposal linked: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/311163 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1629797 Title: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up Status in cloud-init: Fix Committed Status in D-Bus: Unknown Status in cloud-init package in Ubuntu: Fix Released Status in dbus package in Ubuntu: Won't Fix Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Fix Released Bug description: === Begin SRU Template === [Impact] In cases where cloud-init used dns during early boot and system was configured in nsswitch.conf to use systemd-resolvd, the system would timeout on dns attempts making system boot terribly slow. [Test Case] Boot a system on GCE. check for WARN in /var/log/messages check that time to boot is reasonable (<30 seconds). In failure case the times would be minutes. [Regression Potential] Changing order in boot can be dangerous. There is real chance for regression here, but it should be fairly small as xenial does not include systemd-resolved usage. This was first noticed on yakkety where it did. [Other Info] It seems useful to SRU this in the event that systemd-resolvd is used on 16.04 or the case where user upgrades components (admittedly small use case). === End SRU Template === During boot, cloud-init does DNS resolution checks to if particular metadata services are available (in order to determine which cloud it is running on). These checks happen before systemd-resolved is up[0] and if they resolve unsuccessfully they take 25 seconds to complete. This has substantial impact on boot time in all contexts, because cloud-init attempts to resolve three known-invalid addresses ("does- not-exist.example.com.", "example.invalid." and a random string) to enable it to detect when it's running in an environment where a DNS server will always return some sort of redirect. As such, we're talking a minimum impact of 75 seconds in all environments. This increases when cloud-init is configured to check for multiple environments. This means that yakkety is consistently taking 2-3 minutes to boot on EC2 and GCE, compared to the ~30 seconds of the first boot and ~10 seconds thereafter in xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1629797/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
** Merge proposal linked: https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/311163 -- 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/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) Status in systemd: New Status in cloud-init package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in cloud-init source package in Xenial: Confirmed Status in systemd source package in Xenial: Triaged Bug description: Ubuntu Core 16 images using cloud-init fail to function when the DataSource is over the network (Like OpenStack) as networking is not yet available when cloud-init.service runs. cloud-init service unit deps look like this: [Unit] Description=Initial cloud-init job (metadata service crawler) DefaultDependencies=no Wants=cloud-init-local.service Wants=local-fs.target Wants=sshd-keygen.service Wants=sshd.service After=cloud-init-local.service After=networking.service Requires=networking.service Before=basic.target Before=dbus.socket Before=network-online.target Before=sshd-keygen.service Before=sshd.service Before=systemd-user-sessions.service Conflicts=shutdown.target Here's networkd unit deps: [Unit] Description=Network Service Documentation=man:systemd-networkd.service(8) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be # dropped once tuntap is moved to netlink After=systemd-udevd.service dbus.service network-pre.target systemd-sysusers.service systemd-sysctl.service Before=network.target multi-user.target shutdown.target Conflicts=shutdown.target Wants=network.target # On kdbus systems we pull in the busname explicitly, because it # carries policy that allows the daemon to acquire its name. Wants=org.freedesktop.network1.busname After=org.freedesktop.network1.busname And a critical-chain output: root@snap-test7:~# systemd-analyze critical-chain systemd-networkd Failed to get ID: Unit name systemd-networkd is not valid. The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. systemd-networkd.service +440ms └─dbus.service @11.461s └─basic.target @11.403s └─sockets.target @11.401s └─dbus.socket @11.398s └─cloud-init.service @10.127s +1.266s └─networking.service @9.305s +799ms └─network-pre.target @9.295s └─cloud-init-local.service @3.822s +5.469s └─local-fs.target @3.813s └─run-cgmanager-fs.mount @12.687s └─local-fs-pre.target @1.393s └─systemd-tmpfiles-setup-dev.service @1.116s +195ms └─kmod-static-nodes.service @887ms +193ms └─system.slice @783ms └─-.slice @721ms cloud-init would need networkd to run at or before 'networking.service' so it can raise networking to then find and use network-based datasources. # grep systemd /usr/share/snappy/dpkg.list ii libnss-resolve:amd64 229-4ubuntu11 amd64nss module to resolve names via systemd-resolved ii libpam-systemd:amd64 229-4ubuntu11 amd64system and service manager - PAM module ii libsystemd0:amd64 229-4ubuntu11 amd64systemd utility library ii systemd 229-4ubuntu11 amd64system and service manager ii systemd-sysv 229-4ubuntu11 amd64system and service manager - SysV links # grep cloud-init /usr/share/snappy/dpkg.list ii cloud-init 0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all Init scripts for cloud instances To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636912/+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 1642638] [NEW] backspace is not working on upright bq e5
Public bug reported: Hi, I bought last week bq e5 ubuntu, just updated the system. have problem with backspace deleting on upright (default position,power button upper right) it does not work on horrizontally it works in both directions on upright buttom up(power button down left) it also works "only" the default position does not work see questions: https://answers.launchpad.net/ubuntu/+source/unity8/+question/404069 ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1642638 Title: backspace is not working on upright bq e5 Status in unity8 package in Ubuntu: New Bug description: Hi, I bought last week bq e5 ubuntu, just updated the system. have problem with backspace deleting on upright (default position,power button upper right) it does not work on horrizontally it works in both directions on upright buttom up(power button down left) it also works "only" the default position does not work see questions: https://answers.launchpad.net/ubuntu/+source/unity8/+question/404069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1642638/+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 1642634] [NEW] indicator-datetime uses excessive memory
Public bug reported: On my Aquaris 4.5, OTA-13, indicator-datetime 15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS is 315892, almost three times as much as unity8. I believe this is an OTA regression. I'm not sure if it regressed from OTA-11 or OTA-12. Just now, I got caught in an oom killer loop with constant killing of unity8-dash because of this, making my phone unusable. I had to kill indicator-datetime manually. It then restarted automatically and now uses 80456 RSS only. I see bug 1633319 exists complaining about a memory leak. It's not exactly the same version since mine is 15.10+15.04.20160820.1-0ubuntu1 and that one is 15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are the same or something? Perhaps the two are dupes, but I'll let someone more familiar make that determination. I have only a handful of alarms (perhaps five on average; rarely more) but I do have my Google calendar syncing with perhaps hundreds of events. However, there's no reason that this should cause indicator- datetime to use more RSS; it shouldn't be keeping these in memory. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1642634 Title: indicator-datetime uses excessive memory Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: New Bug description: On my Aquaris 4.5, OTA-13, indicator-datetime 15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS is 315892, almost three times as much as unity8. I believe this is an OTA regression. I'm not sure if it regressed from OTA-11 or OTA-12. Just now, I got caught in an oom killer loop with constant killing of unity8-dash because of this, making my phone unusable. I had to kill indicator-datetime manually. It then restarted automatically and now uses 80456 RSS only. I see bug 1633319 exists complaining about a memory leak. It's not exactly the same version since mine is 15.10+15.04.20160820.1-0ubuntu1 and that one is 15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are the same or something? Perhaps the two are dupes, but I'll let someone more familiar make that determination. I have only a handful of alarms (perhaps five on average; rarely more) but I do have my Google calendar syncing with perhaps hundreds of events. However, there's no reason that this should cause indicator- datetime to use more RSS; it shouldn't be keeping these in memory. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
And coming back to my workaround script NetworkManagerRestartWorkaroundForBug1380480.sh, I tried the more friendly '(sleep 3;sudo wpa_cli scan)' solution, but it dit not always work. The only solution I found to have networking working reliably after resume is to have NetworkManager restarted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1642593] Re: [rc krillin#69] dialer crashes on close
** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Bill Filler (bfiller) ** Changed in: dialer-app (Ubuntu) Importance: Undecided => Critical ** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1642593 Title: [rc krillin#69] dialer crashes on close Status in Canonical System Image: In Progress Status in dialer-app package in Ubuntu: Confirmed Bug description: current build number: 69 device name: krillin channel: ubuntu-touch/rc/bq-aquaris.en Test Case 1. Launch the dialler 2. Wait until the UI is fully rendered and close the app from the spread Actual result It crashes Expected result It doesn't crash https://errors.ubuntu.com/oops/105e7a5a-acc8-11e6-8fd9-fa163ebeb28a https://errors.ubuntu.com/oops/d9ebfd8c-acca-11e6-9b33-fa163eec78fa https://errors.ubuntu.com/oops/76148854-acc7-11e6-92df-fa163eec78fa To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642593/+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 1642360] Re: Display occasionally stays on forever after boot in rc-proposed
** Changed in: ubuntu-touch-session (Ubuntu) Status: New => In Progress ** Changed in: canonical-devices-system-image Assignee: Alexandros Frantzis (afrantzis) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1642360 Title: Display occasionally stays on forever after boot in rc-proposed Status in Canonical System Image: In Progress Status in ubuntu-touch-session package in Ubuntu: In Progress Bug description: Occasionally the display stays on forever after boot in rc-proposed, due to a keep display on request. The problem seems to be that the keep-display-on-request introduced to fix bug 1623853, sometimes doesn't get released due to races in the upstart scripts. This happens if the lightdm job starts before the keep-display-on-during-boot job starts, in which case the keep- display-on-during-boot job never gets the signal it needs to stop ("stop on started lightdm"). This issue can be reproduced easily by changing the related upstart script timings, for example, by inserting a "sleep 10" at the end of the repowerd.conf pre-start stanza (or post-start stanza, it has the same effect). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642360/+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 1542029] Re: New windows have incorrect dimensions on launch (not the dimensions the app specifies)
Unity8 is overriding the client-requested window size in phone/tablet mode, but this shouldn't be happening for desktop mode. We also need to save the client-requested window geometry in case shell later wishes to apply that. Agreed I'd like a specific example ** Changed in: qtmir (Ubuntu) Status: New => Confirmed ** Changed in: qtmir (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1542029 Title: New windows have incorrect dimensions on launch (not the dimensions the app specifies) Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: New Status in Ubuntu UX: Invalid Status in miral package in Ubuntu: Incomplete Status in puritine package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: currently, the shell is picking some random window size. They are about to change it to be close to what is on the phone - as this will match most apps. however the Xapps should have something "larger" shell is landing the ability to communicate to it, the desire default first launch window size it would also be good to have design input on this selection To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542029/+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 1642360] Re: Display occasionally stays on forever after boot in rc-proposed
** Changed in: canonical-devices-system-image Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1642360 Title: Display occasionally stays on forever after boot in rc-proposed Status in Canonical System Image: In Progress Status in ubuntu-touch-session package in Ubuntu: In Progress Bug description: Occasionally the display stays on forever after boot in rc-proposed, due to a keep display on request. The problem seems to be that the keep-display-on-request introduced to fix bug 1623853, sometimes doesn't get released due to races in the upstart scripts. This happens if the lightdm job starts before the keep-display-on-during-boot job starts, in which case the keep- display-on-during-boot job never gets the signal it needs to stop ("stop on started lightdm"). This issue can be reproduced easily by changing the related upstart script timings, for example, by inserting a "sleep 10" at the end of the repowerd.conf pre-start stanza (or post-start stanza, it has the same effect). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642360/+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 1642622] [NEW] UITK E305 expected 2 blank lines after class or function definition, found 1
Public bug reported: When trying a build with Qt 5.7.1: --- /<>/ubuntu-ui-toolkit-1.3.2141+16.10.20161013.5+isreallystaging1~1/.bazaar/plugins/makecheck_ubuntu_ui_toolkit.py:38:1: E305 expected 2 blank lines after class or function definition, found 1 /<>/ubuntu-ui-toolkit-1.3.2141+16.10.20161013.5+isreallystaging1~1/.bazaar/plugins/packaging_sorting.py:55:1: E305 expected 2 blank lines after class or function definition, found 1 Makefile:688: recipe for target 'check' failed --- https://launchpadlibrarian.net/293823357/buildlog_ubuntu-zesty-armhf.ubuntu-ui-toolkit_1.3.2141+16.10.20161013.5+isreallystaging1~1_BUILDING.txt.gz https://wiki.ubuntu.com/Touch/QtTesting ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.7 ** Branch linked: lp:~timo-jyrinki/ubuntu-ui- toolkit/uitk_more_blank_lines -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1642622 Title: UITK E305 expected 2 blank lines after class or function definition, found 1 Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: When trying a build with Qt 5.7.1: --- /<>/ubuntu-ui-toolkit-1.3.2141+16.10.20161013.5+isreallystaging1~1/.bazaar/plugins/makecheck_ubuntu_ui_toolkit.py:38:1: E305 expected 2 blank lines after class or function definition, found 1 /<>/ubuntu-ui-toolkit-1.3.2141+16.10.20161013.5+isreallystaging1~1/.bazaar/plugins/packaging_sorting.py:55:1: E305 expected 2 blank lines after class or function definition, found 1 Makefile:688: recipe for target 'check' failed --- https://launchpadlibrarian.net/293823357/buildlog_ubuntu-zesty-armhf.ubuntu-ui-toolkit_1.3.2141+16.10.20161013.5+isreallystaging1~1_BUILDING.txt.gz https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1642622/+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 1612367] Re: [Touch] Incoming call gets silent randomly
I can reproduce this bug often when i want to use viva-voce during a call.. Suddently the bigger speaker stops playing any sound and this can last hours. -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1184262] Re: times out too early, stuck in PrepareForSleep, causing network and other services to not resume
still present in Xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: times out too early, stuck in PrepareForSleep, causing network and other services to not resume Status in systemd-shim package in Ubuntu: Fix Released Status in systemd-shim source package in Saucy: Fix Released Status in systemd-shim source package in Trusty: Fix Released Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. SRU INFORMATION: Reproducer: - Force suspend to take very long by adding a sleep: echo -e '#!/bin/sh\nsleep 15\nexit 1' | sudo tee /usr/lib/pm-utils/sleep.d/00break (this will also make suspend fail, which eases testing) - Suspend from the menu or with sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.Suspend true - With the 13.10 final version, systemd-shim will (often) time out, and the next Suspend call from above will fail with "Operation already in progress" and the network does not come back up. With the fixed version, network should be back up and the Suspend() call can be issued many times. Fix: https://github.com/desrt/systemd-shim/commit/136ed1143077d13c2 https://github.com/desrt/systemd-shim/commit/16a7fdc0652ad78f4 Regression potential: Errors in this code could potentially break suspend/shutdown completely, so for verification both of these functionalities ought to be tested on real hardware. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1184262/+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 1642617] Re: UITK FTBFS on Qt 5.7.1
** Branch linked: lp:~timo-jyrinki/ubuntu-ui- toolkit/uitk_fix_qt571_ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1642617 Title: UITK FTBFS on Qt 5.7.1 Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: https://launchpadlibrarian.net/293820525/buildlog_ubuntu-zesty-amd64.ubuntu-ui-toolkit_1.3.2141+16.10.20161013.5build1~1_BUILDING.txt.gz --- cc1plus: all warnings being treated as errors Makefile:1005: recipe for target '.obj/header_ubuntutoolkitmodule.o' failed make[3]: *** [.obj/header_ubuntutoolkitmodule.o] Error 1 --- https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1642617/+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 1642617] [NEW] UITK FTBFS on Qt 5.7.1
Public bug reported: https://launchpadlibrarian.net/293820525/buildlog_ubuntu-zesty-amd64.ubuntu-ui-toolkit_1.3.2141+16.10.20161013.5build1~1_BUILDING.txt.gz --- cc1plus: all warnings being treated as errors Makefile:1005: recipe for target '.obj/header_ubuntutoolkitmodule.o' failed make[3]: *** [.obj/header_ubuntutoolkitmodule.o] Error 1 --- https://wiki.ubuntu.com/Touch/QtTesting ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1642617 Title: UITK FTBFS on Qt 5.7.1 Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: https://launchpadlibrarian.net/293820525/buildlog_ubuntu-zesty-amd64.ubuntu-ui-toolkit_1.3.2141+16.10.20161013.5build1~1_BUILDING.txt.gz --- cc1plus: all warnings being treated as errors Makefile:1005: recipe for target '.obj/header_ubuntutoolkitmodule.o' failed make[3]: *** [.obj/header_ubuntutoolkitmodule.o] Error 1 --- https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1642617/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
btw, merely restarting Network Manager never worked for me. I have to remove iwlwifi and reload it. derek On Thu, Nov 17, 2016 at 2:18 PM, Derek Broughton wrote: > We used to have this. I'm sure, a decade ago, I could actually tell > whatever was managing the hibernate/suspend, in the gui, to remove certain > kernel modules on suspend and load them on resume. Now we're right back to > needing it. > > derek > > On Thu, Nov 17, 2016 at 1:59 PM, Hans Deragon wrote: > >> This serious issue is dragging to long. People want computers that >> "just work". If pinpointing the source of the problem is difficult and >> few resources are available, why not package a workaround that restarts >> NetworkManager upon resume? >> >> Attached is my workaround. Works nicely. Finally, I have a computer >> that "just works" and it's not a Mac (well, I have other issues but this >> one is solved). >> >> Simple move the script under /lib/systemd/system-sleep and ensure it is >> executable. >> >> ** Attachment added: "Workaround that restarts the NetworkManager upon >> resume." >>https://bugs.launchpad.net/ubuntu/+source/network-manager/+ >> bug/1585863/+attachment/4778652/+files/NetworkManagerR >> estartWorkaroundForBug1380480.sh >> >> -- >> You received this bug notification because you are subscribed to a >> duplicate bug report (1448555). >> https://bugs.launchpad.net/bugs/1585863 >> >> Title: >> WiFi malfunction after suspend & resume stress - sudo wpa_cli scan >> required to fix it. >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions >> > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
We used to have this. I'm sure, a decade ago, I could actually tell whatever was managing the hibernate/suspend, in the gui, to remove certain kernel modules on suspend and load them on resume. Now we're right back to needing it. derek On Thu, Nov 17, 2016 at 1:59 PM, Hans Deragon wrote: > This serious issue is dragging to long. People want computers that > "just work". If pinpointing the source of the problem is difficult and > few resources are available, why not package a workaround that restarts > NetworkManager upon resume? > > Attached is my workaround. Works nicely. Finally, I have a computer > that "just works" and it's not a Mac (well, I have other issues but this > one is solved). > > Simple move the script under /lib/systemd/system-sleep and ensure it is > executable. > > ** Attachment added: "Workaround that restarts the NetworkManager upon > resume." >https://bugs.launchpad.net/ubuntu/+source/network- > manager/+bug/1585863/+attachment/4778652/+files/ > NetworkManagerRestartWorkaroundForBug1380480.sh > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1448555). > https://bugs.launchpad.net/bugs/1585863 > > Title: > WiFi malfunction after suspend & resume stress - sudo wpa_cli scan > required to fix it. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1542029] Re: New windows have incorrect dimensions on launch (not the dimensions the app specifies)
Can we have a specific example of the bug? The size of the window requested is a hint to the window manager, not a requirement. The requested size may legitimately be overridden (e.g. for layout reasons). I.e. There is no guarantee that size created matches the requested size. ** Changed in: miral (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1542029 Title: New windows have incorrect dimensions on launch (not the dimensions the app specifies) Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: New Status in Ubuntu UX: Invalid Status in miral package in Ubuntu: Incomplete Status in puritine package in Ubuntu: Invalid Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: currently, the shell is picking some random window size. They are about to change it to be close to what is on the phone - as this will match most apps. however the Xapps should have something "larger" shell is landing the ability to communicate to it, the desire default first launch window size it would also be good to have design input on this selection To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542029/+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 1624251] Re: gsettings-qt fails a test on Qt 5.7
Still fails with Qt 5.7.1, testable from the PPA. ** Summary changed: - gsettings-qt fails a test on Qt 5.7 + gsettings-qt fails a test on Qt 5.7.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-qt in Ubuntu. https://bugs.launchpad.net/bugs/1624251 Title: gsettings-qt fails a test on Qt 5.7.1 Status in gsettings-qt package in Ubuntu: New Bug description: -- FAIL! : GSettings::test_reset() property count Actual (): 0 Expected (): 1 Loc: [/«BUILDDIR»/gsettings-qt-0.1+16.04.20160329/tests/tst_GSettings.qml(102)] (process:7207): GLib-GIO-WARNING **: g_settings_set_value: value for key 'test-enum' in schema 'com.canonical.gsettings.Test' is outside of valid range -- (https://launchpadlibrarian.net/284597323/buildlog_ubuntu-yakkety- amd64.gsettings-qt_0.1+16.04.20160329-0ubuntu2~5_BUILDING.txt.gz) More information about Qt 5.7 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1624251/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
This serious issue is dragging to long. People want computers that "just work". If pinpointing the source of the problem is difficult and few resources are available, why not package a workaround that restarts NetworkManager upon resume? Attached is my workaround. Works nicely. Finally, I have a computer that "just works" and it's not a Mac (well, I have other issues but this one is solved). Simple move the script under /lib/systemd/system-sleep and ensure it is executable. ** Attachment added: "Workaround that restarts the NetworkManager upon resume." https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863/+attachment/4778652/+files/NetworkManagerRestartWorkaroundForBug1380480.sh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1642605] [NEW] maliit-framework segmentation fault with Qt 5.7.1
Public bug reported: It seems there is a segmentation fault with Qt 5.7.1 with maliit- framework as shown at https://launchpadlibrarian.net/293811765 /buildlog_ubuntu-zesty-amd64.maliit-framework_0.99.1+git20151118 +62bd54b-0ubuntu13~1_BUILDING.txt.gz -- TESTING_IN_SANDBOX=1 TESTPLUGIN_PATH=../plugins TESTDATA_PATH=/<>/maliit-framework-0.99.1+git20151118+62bd54b/tests LD_LIBRARY_PATH=../../lib:../../lib/plugins:../plugins: ./ut_mimsettings * Start testing of Ut_MImSettings * Config: Using QtTest library 5.7.1, Qt 5.7.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 6.2.0 20161109) PASS : Ut_MImSettings::initTestCase() PASS : Ut_MImSettings::testValue() PASS : Ut_MImSettings::testModifyValue() PASS : Ut_MImSettings::testUnsetValue() PASS : Ut_MImSettings::testModifyValueNotification() PASS : Ut_MImSettings::testListDirs() PASS : Ut_MImSettings::testListEntries() PASS : Ut_MImSettings::cleanupTestCase() Totals: 8 passed, 0 failed, 0 skipped, 0 blacklisted, 44ms * Finished testing of Ut_MImSettings * Segmentation fault (core dumped) Makefile:336: recipe for target 'check' failed make[4]: *** [check] Error 139 -- More information about Qt 5.7.1 at https://wiki.ubuntu.com/Touch/QtTesting ** Affects: maliit-framework (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1642605 Title: maliit-framework segmentation fault with Qt 5.7.1 Status in maliit-framework package in Ubuntu: New Bug description: It seems there is a segmentation fault with Qt 5.7.1 with maliit- framework as shown at https://launchpadlibrarian.net/293811765 /buildlog_ubuntu-zesty-amd64.maliit-framework_0.99.1+git20151118 +62bd54b-0ubuntu13~1_BUILDING.txt.gz -- TESTING_IN_SANDBOX=1 TESTPLUGIN_PATH=../plugins TESTDATA_PATH=/<>/maliit-framework-0.99.1+git20151118+62bd54b/tests LD_LIBRARY_PATH=../../lib:../../lib/plugins:../plugins: ./ut_mimsettings * Start testing of Ut_MImSettings * Config: Using QtTest library 5.7.1, Qt 5.7.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 6.2.0 20161109) PASS : Ut_MImSettings::initTestCase() PASS : Ut_MImSettings::testValue() PASS : Ut_MImSettings::testModifyValue() PASS : Ut_MImSettings::testUnsetValue() PASS : Ut_MImSettings::testModifyValueNotification() PASS : Ut_MImSettings::testListDirs() PASS : Ut_MImSettings::testListEntries() PASS : Ut_MImSettings::cleanupTestCase() Totals: 8 passed, 0 failed, 0 skipped, 0 blacklisted, 44ms * Finished testing of Ut_MImSettings * Segmentation fault (core dumped) Makefile:336: recipe for target 'check' failed make[4]: *** [check] Error 139 -- More information about Qt 5.7.1 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1642605/+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