[Touch-packages] [Bug 1704726] Re: Please merge openldap 2.4.44+dfsg-8 (main) from Debian unstable (main)
Closing as Gianfranco Costamagna already merged it on his own. ** Changed in: openldap (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1704726 Title: Please merge openldap 2.4.44+dfsg-8 (main) from Debian unstable (main) Status in openldap package in Ubuntu: Fix Released Bug description: Hi, I just uploaded openldap 2.4.44+dfsg-8 in response to the new Heimdal upload. It includes the following fixes: - fixed FTBFS on ppc64el with kernel 4.9 and newer - fixed FTBFS with Heimdal 7.2.0 and newer Please consider sponsoring this merge, thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1704726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706848] [NEW] This error message appears at startup
Public bug reported: [ 2.235485] nouveau :01:00.0: bus: MMIO read of FAULT at 3e6684 [IBUS] Even after the xorg update the error continues. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: 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 Jul 27 00:59:38 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM107 [GeForce GTX 750 Ti] [3842:3753] InstallationDate: Installed on 2017-07-21 (5 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=73638941-2a1f-4419-940b-ee07b54dce2b ro locale=pt_BR quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jul 27 00:56:08 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMOSART Semi. 2.4G RF Keyboard & Mouse KEYBOARD, id 8 inputMOSART Semi. 2.4G RF Keyboard & Mouse KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: nouveau ** 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/1706848 Title: This error message appears at startup Status in xorg package in Ubuntu: New Bug description: [ 2.235485] nouveau :01:00.0: bus: MMIO read of FAULT at 3e6684 [IBUS] Even after the xorg update the error continues. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: 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 Jul 27 00:59:38 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM107 [GeForce GTX 750 Ti] [3842:3753] InstallationDate: Installed on 2017-07-21 (5 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=73638941-2a1f-4419-940b-ee07b54dce2b ro locale=pt_BR quiet splash SourcePackage: xorg UpgradeStatus:
[Touch-packages] [Bug 1576341] Re: systemd in degraded state on startup in LXD containers
** No longer affects: lxd (Ubuntu) -- 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/1576341 Title: systemd in degraded state on startup in LXD containers Status in lvm2 package in Ubuntu: Fix Released Status in nfs-utils package in Ubuntu: New Status in open-iscsi package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Bug description: The ubuntu:xenial image shows 'degraded' state in lxd on initial boot. $ lxc launch xenial x1 $ sleep 10 $ lxc file pull x1/etc/cloud/build.info - build_name: server serial: 20160420-145324 $ lxc exec x1 systemctl is-system-running degraded $ lxc exec x1 -- systemctl --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 28 17:28:04 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682499] Re: Disable DNSSEC by default
** Summary changed: - disable dnssec + Disable DNSSEC by default ** Changed in: systemd (Ubuntu) Milestone: zesty-updates => None -- 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/1682499 Title: Disable DNSSEC by default Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * dnssec functionality in systemd-resolved prevents network access in certain intra and extra net cases, due to failure to correctly validate dnssec entries. As a work-around we should disable dnssec by default. [Test Case] * Validate systemd-resolved is compiled with --with-default-dnssec=no * Validate that systemd-resolve --status says that DNSSEC setting is no $ systemd-resolve --status good output: ... DNSSEC setting: no DNSSEC supported: no ... bad output: ... DNSSEC setting: allow-downgrade DNSSEC supported: yes ... [Regression Potential] * People who expect DNSSEC to be available by default will need to re-enable it by modifying systemd-resolve configuration file [Other Info] * See duplicate bugs and other bug reports in systemd for scenarios of DNS resolution failures when DNSSEC is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593907] Re: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot
** Summary changed: - ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just need to apply it and release a new version + ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot ** Bug watch removed: Debian Bug tracker #823533 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823533 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1593907 Title: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Trusty: Fix Committed Status in ntp source package in Xenial: Fix Committed Status in ntp source package in Yakkety: Fix Released Status in ntp source package in Zesty: Fix Committed Bug description: [Impact] * Fixes several broken cases, those are: * Case 1 - ntp configured to drift time slowly, but time jumping - ntp is running and drifts time towards a target being way off - an interface comes up - stop ntpd - warp time via ntpdate-debian (static interfaces will even set -b) - (re-)start ntpd - if users relied on non-time warp they are now in trouble * Case 2 - ntp start/stop storms - ntpd comes up normally - the admin brings interfaces up/down rather often - ntp is restarted very very often due to this for no reason => reason for bugs like debian 823533 * Case 3 - unintentional enablement of ntp - ntpd is installed but disabled (for whatever reason) - all is fine on any ifup/down - one installs ntpdate, maybe even without realizing due to a depends - now on the next ifup ntpd (or openntpd) will be started * Solution, drop the broken Delta [Test Case] * Testing Case 2/3 as it is the easiest, case 1 needs a more complex setup to cause the time drift but otherwise works the same way. - install ntp and ntpdate - stop ntp - ifup/ifdown an interface multiple times; as simplification you can also call /etc/network/if-up.d/ntpdate directly (not that this spawns the change asnchronous and locks concurrency, so do that a few times over the time of a minute or so) - the service of ntp should still be stopped and not report plenty of restarts [Regression Potential] * It improves a lot of cases (otherwise we wouldn't SRU), but there is one regression potential I can see: - users that relied on starting NTP later on after other interfaces got up due to that code in ntpdate which did that as a side effect. But that is outweigh by Case2/3 for the majority of users. And even Case1 only hits this potential regression on e.g. late network intialization, but in that case please remind that the default (systemd timedatectl) would handle that. - Since most users of ntp do not install ntpdate (which doesn't work when ntp is active) we should be rather safe to assume that almost no one should rely on that side effect. - Furthermore this is a Ubuntu Delta for very long, cause issues (see the references on the git commit) but never made it into Debian - in that sense another indicator it isn't an important delta to have. [Other Info] * The original intention "what if net is available too late" fixed correctly would not be part of ntpdate, but ntp and additionally check if it is actually meant to be enabled - but I never seen/heard of any of it since systemd is around - maybe new ordering mostly avoids the original issue. --- I've installed ntp service on the clean ubuntu 16.04 server system. Configured it. Checked that it works, but, after reboot, it doesn't start automatically. When I check: 'systemctl is-enabled ntp', it shows enabled. If I manually start it 'systemctl start ntp' it starts just fine and woks correctly, but until I manually start it, 'systemctl status ntp' shows: Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled) Active: inactive (deadi) Installed 1.29ubuntu2 version of init-systems-helper, but it didn't fix the problem. Found a bugreport on ntpd package: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596 led to solution that involves a change to be made in file: /etc/network/if-up.d/ntpdate of ntpdate package After changing from: __CODE_START__ invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true # Avoid running more than one at a time flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null || : invoke-rc.d --quiet
[Touch-packages] [Bug 1706837] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1706837/+attachment/4922151/+files/ThreadStacktrace.txt ** Tags added: apport-failed-retrace ** Tags removed: need-amd64-retrace -- 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/1706837 Title: systemd-journald crashed with SIGABRT in error_tail() Status in systemd package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Wed Jul 26 21:03:54 2017 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2015-03-25 (854 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: error_tail (status=0, errnum=0, message=0x1 , args=0x87baad0551274a00) at error.c:267 sd_event_run () from /lib/systemd/libsystemd-shared-233.so ?? () ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libgpg-error.so.0 Title: systemd-journald crashed with SIGABRT in error_tail() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-yakkety dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-yakkety dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1706837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706837] systemd-journald crashed with SIGABRT in error_tail()
Stacktrace: #0 0x7fe7053b3773 in ?? () No symbol table info available. #1 0x in ?? () No symbol table info available. StacktraceSource: #0 0x7fe7053b3773 in ?? () #1 0x in ?? () StacktraceTop: ?? () ?? () -- 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/1706837 Title: systemd-journald crashed with SIGABRT in error_tail() Status in systemd package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Wed Jul 26 21:03:54 2017 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2015-03-25 (854 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: error_tail (status=0, errnum=0, message=0x1 , args=0x87baad0551274a00) at error.c:267 sd_event_run () from /lib/systemd/libsystemd-shared-233.so ?? () ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libgpg-error.so.0 Title: systemd-journald crashed with SIGABRT in error_tail() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-yakkety dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-yakkety dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1706837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706837] [NEW] systemd-journald crashed with SIGABRT in error_tail()
Public bug reported: . ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Wed Jul 26 21:03:54 2017 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2015-03-25 (854 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: error_tail (status=0, errnum=0, message=0x1 , args=0x87baad0551274a00) at error.c:267 sd_event_run () from /lib/systemd/libsystemd-shared-233.so ?? () ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libgpg-error.so.0 Title: systemd-journald crashed with SIGABRT in error_tail() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-yakkety dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-yakkety dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash artful need-amd64-retrace -- 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/1706837 Title: systemd-journald crashed with SIGABRT in error_tail() Status in systemd package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Wed Jul 26 21:03:54 2017 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2015-03-25 (854 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: error_tail (status=0, errnum=0, message=0x1 , args=0x87baad0551274a00) at error.c:267 sd_event_run () from /lib/systemd/libsystemd-shared-233.so ?? () ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libgpg-error.so.0 Title: systemd-journald crashed with SIGABRT in error_tail() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-yakkety dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-yakkety dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1706837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692152] Re: package apport 2.20.3-0ubuntu8.2 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: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1692152 Title: package apport 2.20.3-0ubuntu8.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in apport package in Ubuntu: Confirmed Bug description: i am getting following error: when i am trying to install anything ubuntu@ubuntu:~$ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apport The following packages will be upgraded: apport 1 upgraded, 0 newly installed, 0 to remove and 410 not upgraded. 3 not fully installed or removed. Need to get 0 B/121 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 291353 files and directories currently installed.) Preparing to unpack .../apport_2.20.4-0ubuntu4_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax dpkg: error processing archive /var/cache/apt/archives/apport_2.20.4-0ubuntu4_all.deb (--unpack): subprocess new pre-removal script returned error exit status 1 Error: Timeout was reached E: Sub-process /usr/bin/dpkg exited unexpectedly ProblemType: Package DistroRelease: Ubuntu 17.04 Package: apport 2.20.3-0ubuntu8.2 ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportLog: ApportVersion: 2.20.3-0ubuntu8.2 AptOrdering: apport:amd64: Install NULL: ConfigurePending Architecture: amd64 CrashReports: 644:0:116:0:2017-05-20 07:24:12.658019135 +0530:2017-05-20 07:24:12.658019135 +0530:/var/crash/_usr_bin_pyclean.0.upload 640:0:116:60537:2017-05-20 07:24:09.354035139 +0530:2017-05-20 07:24:10.354035139 +0530:/var/crash/_usr_bin_pyclean.0.crash 600:0:116:1700582:2017-05-20 07:23:00.490636348 +0530:2017-05-20 07:23:01.490636348 +0530:/var/crash/apport.0.crash 640:0:116:14562:2017-05-20 07:23:00.998641622 +0530:2017-05-20 07:23:00.998641622 +0530:/var/crash/_usr_bin_pycompile.0.crash Date: Sat May 20 07:23:00 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-05 (75 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: apport Title: package apport 2.20.3-0ubuntu8.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to zesty on 2017-05-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1692152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1525526] Re: evince/atril is excruciatingly slow
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: poppler (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1525526 Title: evince/atril is excruciatingly slow Status in poppler package in Ubuntu: Confirmed Bug description: For image-heavy PDF files, both Atril and Evince are extremely slow when rendering the page. 'Slow' being in the region of 5-30s (timed), depending on the page, and depending on focus. Thumbnails take an equally long time to render. The same PDF files opened in muPDF render pages instantly. Currently version of libpoppler is 0.30.0-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1525526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Changed in: debconf Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Confirmed Status in Debconf: New Status in aptdaemon package in Ubuntu: Incomplete Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706598] Re: Update bluez to 5.46 in artful
** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1706598 Title: Update bluez to 5.46 in artful Status in bluez package in Ubuntu: In Progress Bug description: The new bluez version is being packaged for artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1706598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694455] Re: Bluetooth: Cannot receive files, due to OBEX configuration
Per the description: 1. OBEX disabled This part is bug 1645631, so please remove part #1 of the description and just mention bug 1645631 instead. 2. OBEX silently fails Let's make #2 the focus of this bug, so it is not seen as a duplicate of bug 1645631 ** Summary changed: - Bluetooth: Cannot receive files, due to OBEX configuration + Bluetooth: Cannot receive files ** Description changed: # Use case Ubuntu 17.04, quite fresh installation, updated. Bluetooth file transmission I want to send files to my smartphone, and receive files sent by my smartphone via bluetooth. I pair both devices, initiate file transfer from one of the devices, and the other device asks me what to do. # Problems This is a mix from usability and technical issues. - 1. OBEX disabled + 1. OBEX disabled (bug 1645631) The bluetooth file transmission service OBEX was not started. I started and enabled OBEX: `systemctl --user start obex` `systemctl --user enable obex` ``` Mai 30 14:47:55 tp systemd[1661]: Starting Bluetooth OBEX service... Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 ``` - 2. OBEX silently fails + 2. OBEX silently fails (this bug) After having OBEX enabled, I was able to transmit files from laptop to smartphone, yet I could not receive files on the laptop. In the system log, you could see that OBEX fails (please note `FORBIDDEN`): ``` Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x0) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), FORBIDDEN(0x43) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20) Mai 30 14:48:04 tp obexd[8168]: disconnected: Transport got disconnected ``` I did not receive a popup notification asking me to receive the file or not. In the file sharing preferences `gnome-file-share-properties`, there is a setting to automatically receive files via bluetooth. With this box checked, you're finally able to receive files from your smartphone. Successful log for comparison: ``` Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x) Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x0) Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), (null)(0x) Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), CONTINUE(0x10) Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), (null)(0x) Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20) Mai 30 14:56:28 tp obexd[8168]: disconnected: Transport got disconnected ``` # Expected behaviour OBEX is started by default to handle bluetooth file transfers. If no automatic file receipt is configured, a popup notification asks me if I want to receive the file or not. If this is not possible, there should be a notification pointing the user to the configuration. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1694455 Title: Bluetooth: Cannot receive files Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: # Use case Ubuntu 17.04, quite fresh installation, updated. Bluetooth file transmission I want to send files to my smartphone, and receive files sent by my smartphone via bluetooth. I pair both devices, initiate file transfer from one of the devices, and the other device asks me what to do. # Problems This is a mix from usability and technical issues. 1. OBEX disabled (bug 1645631) The bluetooth file transmission service OBEX was not started. I started and enabled OBEX: `systemctl --user start obex` `systemctl --user enable obex` ``` Mai 30 14:47:55 tp systemd[1661]: Starting Bluetooth OBEX service... Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 ``` 2. OBEX silently fails (this bug) After having OBEX enabled, I was able to transmit files from laptop to smartphone, yet I could not receive files on the laptop. In the system log, you could see that OBEX fails (please note `FORBIDDEN`): ``` Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x0) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), FORBIDDEN(0x43) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20) Mai 30 14:48:04 tp obexd[8168]: disconnected: Transport got disconnected ``` I did not receive a popup notification asking me to receive the file or not. In the file sharing preferenc
[Touch-packages] [Bug 1706818] [NEW] mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
Public bug reported: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: New Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705571] Re: Add ~/.local/bin to the path in /etc/skel/.profile
** Changed in: gnubash Status: Unknown => New -- 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/1705571 Title: Add ~/.local/bin to the path in /etc/skel/.profile Status in Gnu Bash: New Status in bash package in Ubuntu: Confirmed Bug description: This appears to be a regression of https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1588562 In 16.04, per the above bug it is set with bash 4.3 # Working in 16.04 $ dpkg -l bash | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii bash 4.3-14ubuntu1.2 amd64GNU Bourne Again SHell $ tail -n 2 /etc/skel/profile # set PATH so it includes user's private bin directories PATH="$HOME/bin:$HOME/.local/bin:$PATH" # Regression in 17.04 $ dpkg -l bash | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--= ii bash 4.4-2ubuntu1.1 amd64GNU Bourne Again SHell $ tail -n 4 /etc/skel/.profile # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi # Regression in 17.10 $ dpkg -l bash | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii bash 4.4-5ubuntu1 amd64GNU Bourne Again SHell $ tail -n 4 /etc/skel/.profile # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi foo@76ee9ed7d4f5:~$ echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games The issue could be fixed with a diff on /etc/skel/.profile like: # Patch Diff diff --git a/.profile b/.profile index c9db459..da82446 100644 --- a/.profile +++ b/.profile @@ -20,3 +20,8 @@ fi if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi + +# set PATH so it includes user's private python-pip bin if it exists +if [ -d "$HOME/.local/bin" ] ; then +PATH="$HOME/.local/bin:$PATH" +fi LSB info $ lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 $ lsb_release -rd Description:Ubuntu Artful Aardvark (development branch) Release:17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gnubash/+bug/1705571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706690] Re: [needs-packaging] Please sync openssl from debian stretch
*** This is an automated message *** This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs- packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist. ** Summary changed: - Please sync openssl from debian stretch + [needs-packaging] Please sync openssl from debian stretch ** Changed in: openssl (Ubuntu) Importance: Undecided => Wishlist -- 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/1706690 Title: [needs-packaging] Please sync openssl from debian stretch Status in openssl package in Ubuntu: Confirmed Bug description: OpenSSL 1.1 contains major improvements over 1.0. https://packages.debian.org/stretch/openssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1706690/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698529] Re: package libpam-systemd:amd64 229-4ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1698529 Title: package libpam-systemd:amd64 229-4ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: Confirmed Bug description: failed upgrade of the system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam-systemd:amd64 229-4ubuntu17 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sat Jun 17 11:18:13 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-08-30 (290 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package libpam-systemd:amd64 229-4ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705571] Re: Add ~/.local/bin to the path in /etc/skel/.profile
I will claim the upstream and try to get a fix in. ** Bug watch added: Debian Bug tracker #839155 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839155 ** Also affects: gnubash via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839155 Importance: Unknown Status: Unknown -- 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/1705571 Title: Add ~/.local/bin to the path in /etc/skel/.profile Status in Gnu Bash: Unknown Status in bash package in Ubuntu: Confirmed Bug description: This appears to be a regression of https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1588562 In 16.04, per the above bug it is set with bash 4.3 # Working in 16.04 $ dpkg -l bash | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii bash 4.3-14ubuntu1.2 amd64GNU Bourne Again SHell $ tail -n 2 /etc/skel/profile # set PATH so it includes user's private bin directories PATH="$HOME/bin:$HOME/.local/bin:$PATH" # Regression in 17.04 $ dpkg -l bash | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--= ii bash 4.4-2ubuntu1.1 amd64GNU Bourne Again SHell $ tail -n 4 /etc/skel/.profile # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi # Regression in 17.10 $ dpkg -l bash | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii bash 4.4-5ubuntu1 amd64GNU Bourne Again SHell $ tail -n 4 /etc/skel/.profile # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi foo@76ee9ed7d4f5:~$ echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games The issue could be fixed with a diff on /etc/skel/.profile like: # Patch Diff diff --git a/.profile b/.profile index c9db459..da82446 100644 --- a/.profile +++ b/.profile @@ -20,3 +20,8 @@ fi if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi + +# set PATH so it includes user's private python-pip bin if it exists +if [ -d "$HOME/.local/bin" ] ; then +PATH="$HOME/.local/bin:$PATH" +fi LSB info $ lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 $ lsb_release -rd Description:Ubuntu Artful Aardvark (development branch) Release:17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gnubash/+bug/1705571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706789] Re: installer crashed grub-efi signed not installed
*** This bug is a duplicate of bug 1633913 *** https://bugs.launchpad.net/bugs/1633913 ** This bug has been marked a duplicate of bug 1633913 lubuntu and ubuntustudio are missing pool; can not install without internet connection -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1706789 Title: installer crashed grub-efi signed not installed Status in apport package in Ubuntu: New Bug description: On a lubuntu next install I tried to install offline following this testcase on an hp laptop that had previously worked with lubuntu and secure boot. ubiquity: Installed: 17.10.2 Candidate: 17.10.2 Version table: *** 17.10.2 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Description:Ubuntu Artful Aardvark (development branch) Release:17.10 I expected this install to work with secure boot like it should instead it did not install a signed version of grub so no bootloader points to the new install meaning the new install cannot immediately be booted into. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.6-0ubuntu4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: LXQt Date: Wed Jul 26 14:52:35 2017 LiveMediaBuild: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1706789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706789] [NEW] installer crashed grub-efi signed not installed
Public bug reported: On a lubuntu next install I tried to install offline following this testcase on an hp laptop that had previously worked with lubuntu and secure boot. ubiquity: Installed: 17.10.2 Candidate: 17.10.2 Version table: *** 17.10.2 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Description:Ubuntu Artful Aardvark (development branch) Release:17.10 I expected this install to work with secure boot like it should instead it did not install a signed version of grub so no bootloader points to the new install meaning the new install cannot immediately be booted into. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.6-0ubuntu4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: LXQt Date: Wed Jul 26 14:52:35 2017 LiveMediaBuild: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1706789 Title: installer crashed grub-efi signed not installed Status in apport package in Ubuntu: New Bug description: On a lubuntu next install I tried to install offline following this testcase on an hp laptop that had previously worked with lubuntu and secure boot. ubiquity: Installed: 17.10.2 Candidate: 17.10.2 Version table: *** 17.10.2 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Description:Ubuntu Artful Aardvark (development branch) Release:17.10 I expected this install to work with secure boot like it should instead it did not install a signed version of grub so no bootloader points to the new install meaning the new install cannot immediately be booted into. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.6-0ubuntu4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: LXQt Date: Wed Jul 26 14:52:35 2017 LiveMediaBuild: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1706789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706784] Re: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1706784 Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: error of instalation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu19 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CustomUdevRuleFiles: 98_smfpautoconf_samsung.rules 99_smfpautoconf_samsung.rules Date: Wed Jul 26 12:55:38 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-07-02 (24 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=404deb76-582a-4e9b-a33c-fb2155196ece ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK 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.:bvrN550JK.208:bd09/26/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1706784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706784] [NEW] package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: error of instalation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu19 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CustomUdevRuleFiles: 98_smfpautoconf_samsung.rules 99_smfpautoconf_samsung.rules Date: Wed Jul 26 12:55:38 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-07-02 (24 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=404deb76-582a-4e9b-a33c-fb2155196ece ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK 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.:bvrN550JK.208:bd09/26/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1706784 Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: error of instalation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu19 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CustomUdevRuleFiles: 98_smfpautoconf_samsung.rules 99_smfpautoconf_samsung.rules Date: Wed Jul 26 12:55:38 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-07-02 (24 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=404deb76-582a-4e9b-a33c-fb2155196ece ro quiet splash acpi_osi= vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK 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.:bvrN550JK.208:bd09/26/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1706784/+subscriptions -- Mailing list: https://launchpad.net/~touch-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: Warning messages about unsandboxed downloads
(sighs) I don't think I really understand this bug well enough to put it in the right format. Norbert and anyone else who really wants this fixed in Ubuntu that's not 17.10 please can you do that? Check '3.1. SRU Bug Template' on the link Julian gave and then edit the bug with the relevant details. Thank you! :D -- 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: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released 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 1153266] Re: nm-applet crashed with SIGSEGV in add_to_object_array_unique()
** Changed in: network-manager Status: Incomplete => Expired -- 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/1153266 Title: nm-applet crashed with SIGSEGV in add_to_object_array_unique() Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Fix Released Bug description: Booted freshly downloaded daily-live image raring-desktop-amd64.iso on my T61p. Crash messages popped up once the desktop came up and the installer became visible. System was unstable until I stopped Network Manager and brought up ethernet manually. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: network-manager-gnome 0.9.8.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2 Uname: Linux 3.8.0-11-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 CasperVersion: 1.330 Date: Sun Mar 10 14:36:15 2013 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130310) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: nm-applet ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7ffc11b534ba:mov0x8(%rdi),%edx PC (0x7ffc11b534ba) ok source "0x8(%rdi)" (0xaab2) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: network-manager-applet StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libnm-glib.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libnm-glib.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libnm-glib.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libnm-glib.so.4 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nm-applet crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1d827ba83-7339-403d-9c86-22f060ab7cfc 802-3-ethernet1362926055 Sun 10 Mar 2013 02:34:15 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetdisconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0disconnectedenabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1153266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC
** Changed in: binutils (Ubuntu Yakkety) Status: Fix Committed => Won't Fix ** Changed in: gcc-5 (Ubuntu Yakkety) Status: New => Won't Fix ** Changed in: gcc-6 (Ubuntu Yakkety) Status: New => Won't Fix -- 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/1623418 Title: gcc-as-needed.diff patch broke mpx support in GCC Status in gcc: Unknown Status in binutils package in Ubuntu: Fix Released Status in gcc-5 package in Ubuntu: Fix Released Status in gcc-6 package in Ubuntu: Fix Released Status in binutils source package in Xenial: Fix Released Status in gcc-5 source package in Xenial: New Status in binutils source package in Yakkety: Won't Fix Status in gcc-5 source package in Yakkety: Won't Fix Status in gcc-6 source package in Yakkety: Won't Fix Bug description: [SRU Justification] gcc-5 from Ubuntu is configured with MPX support, but it is broken due to always-added linker option "-as-needed". [Test case] 1. Pass -mmpx to gcc when building an arbitrary project on x86. 2. Verify with ldd that the resulting executable is not linked against libmpx.so because the -as-needed flag has discarded the mpx library from being linked in. 3. Install binutils and gcc-5 from -proposed. 4. Rebuild the target, again with -mmpx. 5. Verify with ldd that the new executable is linked against libmpx.so. 6. Verify that there are no regressions in the binutils testsuite on any architectures, by manually checking the results in the build log. [Regression potential] This binutils patch implements new --push-state / --pop-state options which will not be used in the common case, only when -mmpx is passed. When these flags are not in use, which is the default, it should have no effect on the behavior of the toolchain, so risk of regression is minimal. Here is the GCC upstream bug & fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267 https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=240057 Would it be possible to backport this fix to Ubuntu gcc-5 build? To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1623418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package xfonts-utils - 1:7.7+3ubuntu0.16.04.2 --- xfonts-utils (1:7.7+3ubuntu0.16.04.2) xenial; urgency=medium * control: Add autoconf to build-depends, because the build is picky. (LP: #1687981) -- Timo Aaltonen Mon, 26 Jun 2017 14:27:33 +0300 ** Changed in: xfonts-utils (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
** Changed in: xfonts-utils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package xorg-server-hwe-16.04 - 2:1.19.3-1ubuntu1~16.04.2 --- xorg-server-hwe-16.04 (2:1.19.3-1ubuntu1~16.04.2) xenial; urgency=medium * SECURITY UPDATE: DoS and possible code execution in endianness conversion of X Events - debian/patches/CVE-2017-10971-1.patch: do not try to swap GenericEvent in Xi/sendexev.c. - debian/patches/CVE-2017-10971-2.patch: verify all events in ProcXSendExtensionEvent in Xi/sendexev.c. - debian/patches/CVE-2017-10971-3.patch: disallow GenericEvent in SendEvent request in dix/events.c, dix/swapreq.c. - CVE-2017-10971 * SECURITY UPDATE: information leak in XEvent handling - debian/patches/CVE-2017-10972.patch: zero target buffer in SProcXSendExtensionEvent in Xi/sendexev.c. - CVE-2017-10972 -- Marc Deslauriers Tue, 25 Jul 2017 09:04:30 -0400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package libdrm - 2.4.76-1~ubuntu16.04.1 --- libdrm (2.4.76-1~ubuntu16.04.1) xenial; urgency=medium * Backport to xenial. (LP: #1687981) - use debhelper 9 -- Timo Aaltonen Wed, 03 May 2017 16:36:59 +0300 ** Changed in: libclc (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package virtualbox-hwe - 5.0.40-dfsg- 0ubuntu1.16.04.1~16.04.3 --- virtualbox-hwe (5.0.40-dfsg-0ubuntu1.16.04.1~16.04.3) xenial; urgency=medium * Backport to xenial. (LP: #1687981) - build against hwe 16.04.3 stack. - build only guest-* modules. - backport patch for xorg 1.19 -- Gianfranco Costamagna Tue, 11 Jul 2017 08:02:00 +0200 ** Changed in: xorg-server-hwe-16.04 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10971 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10972 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package mesa - 17.0.7-0ubuntu0.16.04.1 --- mesa (17.0.7-0ubuntu0.16.04.1) xenial; urgency=medium * Backport to xenial. (LP: #1687981) - rules: Force -O2 to fix ppc64el FTBFS -- Timo Aaltonen Mon, 26 Jun 2017 15:29:20 +0300 ** Changed in: xorg-hwe-16.04 (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package libclc - 0.2.0+git20170213-1~16.04.1 --- libclc (0.2.0+git20170213-1~16.04.1) xenial; urgency=medium * Backport to xenial. (LP: #1687981) * Don't use debhelper 10. libclc (0.2.0+git20170213-1) experimental; urgency=medium [ Andreas Boll ] * Simplify clang version updates even more. [ Timo Aaltonen ] * New upstream snapshot. * clang: Bump clang version to 4.0. libclc (0.2.0+git20160907-3) unstable; urgency=medium * Simplify clang version updates. * Drop de-duplication of files that aren't duplicate any more. libclc (0.2.0+git20160907-2) unstable; urgency=medium [ Andreas Boll ] * Declare Multi-Arch: foreign for all packages (closes: #845314). [ Michael Gilbert ] * Update to debhelper 10. libclc (0.2.0+git20160907-1) experimental; urgency=medium * New upstream snapshot (closes: #836960). * Build with clang 3.9. * Drop devices.patch, upstream. * Use https for Vcs-Git field. libclc (0.2.0+git20150813-3) unstable; urgency=medium * Bump standards version. * Build with clang 3.8 (closes: #832014). * Add support for additional GPU devices (closes: #823677). -- Timo Aaltonen Fri, 24 Mar 2017 10:11:06 +0200 ** Changed in: libinput (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package libinput - 1.6.3-1ubuntu1~16.04.1 --- libinput (1.6.3-1ubuntu1~16.04.1) xenial; urgency=medium * Backport to xenial. (LP: #1687981) -- Timo Aaltonen Thu, 04 May 2017 14:36:32 +0300 ** Changed in: mesa (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package xorg-hwe-16.04 - 1:7.7+16ubuntu3~16.04.1 --- xorg-hwe-16.04 (1:7.7+16ubuntu3~16.04.1) xenial; urgency=medium * Backport for hwe-16.04 stack. (LP: #1687981) * control: xserver-xorg-hwe-16.04 now Recommends xserver-xorg-legacy-hwe-16.04. -- Timo Aaltonen Thu, 04 May 2017 19:39:20 +0300 ** Changed in: virtualbox-hwe (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package libwacom - 0.22-1~ubuntu16.04.1 --- libwacom (0.22-1~ubuntu16.04.1) xenial; urgency=medium * Backport to xenial. (LP: #1687981) -- Timo Aaltonen Thu, 04 May 2017 15:10:08 +0300 ** Changed in: libdrm (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package vulkan - 1.0.42.0+dfsg1-1ubuntu1~16.04.1 --- vulkan (1.0.42.0+dfsg1-1ubuntu1~16.04.1) xenial; urgency=medium * Backport to xenial. (LP: #1687981) -- Timo Aaltonen Tue, 09 May 2017 13:36:58 +0300 ** Changed in: libwacom (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package wayland - 1.12.0-1~ubuntu16.04.1 --- wayland (1.12.0-1~ubuntu16.04.1) xenial; urgency=medium * Backport to xenial. (LP: #1687981) - use debhelper 9 -- Timo Aaltonen Sat, 25 Mar 2017 12:33:25 +0200 ** Changed in: vulkan (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package libxfont2 - 1:2.0.1-3~ubuntu16.04.1 --- libxfont2 (1:2.0.1-3~ubuntu16.04.1) xenial; urgency=medium * Backport to xenial. (LP: #1687981) - use debhelper 9 * Rename source to libxfont2 for this backport only. -- Timo Aaltonen Wed, 03 May 2017 17:51:02 +0300 ** Changed in: llvm-toolchain-4.0 (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package llvm-toolchain-4.0 - 1:4.0-1ubuntu1~16.04.1 --- llvm-toolchain-4.0 (1:4.0-1ubuntu1~16.04.1) xenial; urgency=medium * Backport to xenial. (LP: #1687981) -- Timo Aaltonen Thu, 23 Mar 2017 13:37:43 +0200 ** Changed in: wayland (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Update Released
The verification of the Stable Release Update for x11proto-core 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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package libxfont - 1:1.5.1-1ubuntu0.16.04.1 --- libxfont (1:1.5.1-1ubuntu0.16.04.1) xenial; urgency=medium * Rename libxfont-dev to libxfont1-dev. (LP: #1687981) -- Timo Aaltonen Sat, 13 May 2017 08:01:15 +0300 ** Changed in: libxfont (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: libxfont2 (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
This bug was fixed in the package x11proto-core - 7.0.31-1~ubuntu16.04.1 --- x11proto-core (7.0.31-1~ubuntu16.04.1) xenial; urgency=medium * Backport to xenial. (LP: #1687981) -- Timo Aaltonen Wed, 03 May 2017 17:15:04 +0300 ** Changed in: x11proto-core (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 libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Released Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in libinput source package in Xenial: Fix Released Status in libwacom source package in Xenial: Fix Released Status in libxfont source package in Xenial: Fix Released Status in libxfont2 source package in Xenial: Fix Released Status in llvm-toolchain-4.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Released Status in wayland source package in Xenial: Fix Released Status in x11proto-core source package in Xenial: Fix Released Status in xfonts-utils source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: Fix Released Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC
This bug was fixed in the package binutils - 2.26.1-1ubuntu1~16.04.4 --- binutils (2.26.1-1ubuntu1~16.04.4) xenial-proposed; urgency=medium * SRU * POWER backports (LP: #1655181) - Don't treat .opd section specially when ELFv2. - Fix PowerPC64 ELFv1 undefined weak functions. - Modify POWER9 support to match final ISA 3.0 documentation. * Fix PR gold/18989. Implement --push-state/--pop-state. LP: #1623418. -- Matthias Klose Fri, 10 Feb 2017 02:30:30 +0100 ** Changed in: binutils (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 binutils in Ubuntu. https://bugs.launchpad.net/bugs/1623418 Title: gcc-as-needed.diff patch broke mpx support in GCC Status in gcc: Unknown Status in binutils package in Ubuntu: Fix Released Status in gcc-5 package in Ubuntu: Fix Released Status in gcc-6 package in Ubuntu: Fix Released Status in binutils source package in Xenial: Fix Released Status in gcc-5 source package in Xenial: New Status in binutils source package in Yakkety: Fix Committed Status in gcc-5 source package in Yakkety: New Status in gcc-6 source package in Yakkety: New Bug description: [SRU Justification] gcc-5 from Ubuntu is configured with MPX support, but it is broken due to always-added linker option "-as-needed". [Test case] 1. Pass -mmpx to gcc when building an arbitrary project on x86. 2. Verify with ldd that the resulting executable is not linked against libmpx.so because the -as-needed flag has discarded the mpx library from being linked in. 3. Install binutils and gcc-5 from -proposed. 4. Rebuild the target, again with -mmpx. 5. Verify with ldd that the new executable is linked against libmpx.so. 6. Verify that there are no regressions in the binutils testsuite on any architectures, by manually checking the results in the build log. [Regression potential] This binutils patch implements new --push-state / --pop-state options which will not be used in the common case, only when -mmpx is passed. When these flags are not in use, which is the default, it should have no effect on the behavior of the toolchain, so risk of regression is minimal. Here is the GCC upstream bug & fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267 https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=240057 Would it be possible to backport this fix to Ubuntu gcc-5 build? To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1623418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623418] Update Released
The verification of the Stable Release Update for binutils 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. ** Tags removed: verification-needed ** Tags added: verification-done-xenial -- 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/1623418 Title: gcc-as-needed.diff patch broke mpx support in GCC Status in gcc: Unknown Status in binutils package in Ubuntu: Fix Released Status in gcc-5 package in Ubuntu: Fix Released Status in gcc-6 package in Ubuntu: Fix Released Status in binutils source package in Xenial: Fix Released Status in gcc-5 source package in Xenial: New Status in binutils source package in Yakkety: Fix Committed Status in gcc-5 source package in Yakkety: New Status in gcc-6 source package in Yakkety: New Bug description: [SRU Justification] gcc-5 from Ubuntu is configured with MPX support, but it is broken due to always-added linker option "-as-needed". [Test case] 1. Pass -mmpx to gcc when building an arbitrary project on x86. 2. Verify with ldd that the resulting executable is not linked against libmpx.so because the -as-needed flag has discarded the mpx library from being linked in. 3. Install binutils and gcc-5 from -proposed. 4. Rebuild the target, again with -mmpx. 5. Verify with ldd that the new executable is linked against libmpx.so. 6. Verify that there are no regressions in the binutils testsuite on any architectures, by manually checking the results in the build log. [Regression potential] This binutils patch implements new --push-state / --pop-state options which will not be used in the common case, only when -mmpx is passed. When these flags are not in use, which is the default, it should have no effect on the behavior of the toolchain, so risk of regression is minimal. Here is the GCC upstream bug & fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267 https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=240057 Would it be possible to backport this fix to Ubuntu gcc-5 build? To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1623418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1655181] Re: P9 support in binutils
This bug was fixed in the package binutils - 2.26.1-1ubuntu1~16.04.4 --- binutils (2.26.1-1ubuntu1~16.04.4) xenial-proposed; urgency=medium * SRU * POWER backports (LP: #1655181) - Don't treat .opd section specially when ELFv2. - Fix PowerPC64 ELFv1 undefined weak functions. - Modify POWER9 support to match final ISA 3.0 documentation. * Fix PR gold/18989. Implement --push-state/--pop-state. LP: #1623418. -- Matthias Klose Fri, 10 Feb 2017 02:30:30 +0100 ** Changed in: binutils (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 binutils in Ubuntu. https://bugs.launchpad.net/bugs/1655181 Title: P9 support in binutils Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Xenial: Fix Released Bug description: [SRU Justification] Hardware enablement of new P9 architecture on 16.04 LTS [Test case] Verify that the binutils testsuite still passes. This requires manual review of the build logs. [Regression potential] One of the patches changes the behavior around handling of undefined weak symbols on ppc64el as a whole. This behavior change could cause regressions on code built for existing ppc64el targets. This is unlikely because nothing should be relying on the current behavior, and this is an upstream patch driven by the architecture owner. One of the patches changes the set of assembly mnemonics available for POWER9 opcodes. This should have no impact because nothing should be relying on the not-yet-finalized P9 support in xenial. The upstream binutils (2.27 and trunk) is almost complete for POWER9, but unfortunately the changes expected to land in DD2 hardware have not yet been set in stone. With that said, the remaining changes are fairly small and will only affect user space; there are no kernel dependencies on the unresolved architecture changes. == Comment: #3 - Peter E. Bergner - 2016-11-01 10:43:16 == Complete POWER9 support is upstream and exists in trunk and the binutils 2.27 and 2.26 release branches. == Comment: #4 - Breno Henrique Leitao - 2016-11-21 12:45:53 == (In reply to comment #3) > Complete POWER9 support is upstream and exists in trunk and the binutils > 2.27 and 2.26 release branches. Binutils version 2.27 is already in Ubuntu 17.04. Is there anything else required? == Comment: #5 - William J. Schmidt - 2016-11-21 13:32:50 == (In reply to comment #4) > (In reply to comment #3) > > Complete POWER9 support is upstream and exists in trunk and the binutils > > 2.27 and 2.26 release branches. > > Binutils version 2.27 is already in Ubuntu 17.04. Is there anything else > required? Well, as long as they pick up the backported fixes, nothing else is required. That's what this feature is there to ensure. == Comment: #6 - Breno Henrique Leitao - 2016-11-24 06:52:51 == Hi, > Well, as long as they pick up the backported fixes, nothing else is > required. That's what this feature is there to ensure. Do you know, at this time, which are the fixes that will be requested to be backported? == Comment: #7 - William J. Schmidt - 2016-11-28 09:17:01 == (In reply to comment #6) > Hi, > > > Well, as long as they pick up the backported fixes, nothing else is > > required. That's what this feature is there to ensure. > > Do you know, at this time, which are the fixes that will be requested to be > backported? Peter, can you please respond to Breno's question? == Comment: #8 - Peter E. Bergner - 2016-11-29 12:08:11 == CC'ing Alan in case he has an extra input. Looking through the binutils-2_27-branch log, I see the following commits we would want picked up: commit 799b679496c98eb1f31625b00bb5db67a6f608d7 Author: Peter Bergner Date: Fri Sep 16 16:17:46 2016 -0500 Backport lastest POWER9 support to match final ISA 3.0 documentation. opcodes/ Apply from master. 2016-09-14 Peter Bergner * ppc-opc.c (powerpc_opcodes) : New mnemonic. : Delete mnemonics. : Rename mnemonic from ... : ...to this. : Change to a X form instruction. : Change to 1 operand form. : Delete mnemonic. : Rename mnemonic from ... : ...to this. : Delete mnemonics. : Rename mnemonic from ... : ...to this. gas/ Apply from master. 2016-09-14 Peter Bergner * testsuite/gas/ppc/power9.d New tests. : Remove tests. : Update tests. * testsuite/gas/ppc/power9.s: Likewise. commit c6a7c521c14e0cc188ccc0388e0d5d21c2042c94 Author: Alan Modra Date: Thu Sep 1 14:56:52 2016 +0930 Don't
[Touch-packages] [Bug 1655181] Update Released
The verification of the Stable Release Update for binutils 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 binutils in Ubuntu. https://bugs.launchpad.net/bugs/1655181 Title: P9 support in binutils Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Xenial: Fix Committed Bug description: [SRU Justification] Hardware enablement of new P9 architecture on 16.04 LTS [Test case] Verify that the binutils testsuite still passes. This requires manual review of the build logs. [Regression potential] One of the patches changes the behavior around handling of undefined weak symbols on ppc64el as a whole. This behavior change could cause regressions on code built for existing ppc64el targets. This is unlikely because nothing should be relying on the current behavior, and this is an upstream patch driven by the architecture owner. One of the patches changes the set of assembly mnemonics available for POWER9 opcodes. This should have no impact because nothing should be relying on the not-yet-finalized P9 support in xenial. The upstream binutils (2.27 and trunk) is almost complete for POWER9, but unfortunately the changes expected to land in DD2 hardware have not yet been set in stone. With that said, the remaining changes are fairly small and will only affect user space; there are no kernel dependencies on the unresolved architecture changes. == Comment: #3 - Peter E. Bergner - 2016-11-01 10:43:16 == Complete POWER9 support is upstream and exists in trunk and the binutils 2.27 and 2.26 release branches. == Comment: #4 - Breno Henrique Leitao - 2016-11-21 12:45:53 == (In reply to comment #3) > Complete POWER9 support is upstream and exists in trunk and the binutils > 2.27 and 2.26 release branches. Binutils version 2.27 is already in Ubuntu 17.04. Is there anything else required? == Comment: #5 - William J. Schmidt - 2016-11-21 13:32:50 == (In reply to comment #4) > (In reply to comment #3) > > Complete POWER9 support is upstream and exists in trunk and the binutils > > 2.27 and 2.26 release branches. > > Binutils version 2.27 is already in Ubuntu 17.04. Is there anything else > required? Well, as long as they pick up the backported fixes, nothing else is required. That's what this feature is there to ensure. == Comment: #6 - Breno Henrique Leitao - 2016-11-24 06:52:51 == Hi, > Well, as long as they pick up the backported fixes, nothing else is > required. That's what this feature is there to ensure. Do you know, at this time, which are the fixes that will be requested to be backported? == Comment: #7 - William J. Schmidt - 2016-11-28 09:17:01 == (In reply to comment #6) > Hi, > > > Well, as long as they pick up the backported fixes, nothing else is > > required. That's what this feature is there to ensure. > > Do you know, at this time, which are the fixes that will be requested to be > backported? Peter, can you please respond to Breno's question? == Comment: #8 - Peter E. Bergner - 2016-11-29 12:08:11 == CC'ing Alan in case he has an extra input. Looking through the binutils-2_27-branch log, I see the following commits we would want picked up: commit 799b679496c98eb1f31625b00bb5db67a6f608d7 Author: Peter Bergner Date: Fri Sep 16 16:17:46 2016 -0500 Backport lastest POWER9 support to match final ISA 3.0 documentation. opcodes/ Apply from master. 2016-09-14 Peter Bergner * ppc-opc.c (powerpc_opcodes) : New mnemonic. : Delete mnemonics. : Rename mnemonic from ... : ...to this. : Change to a X form instruction. : Change to 1 operand form. : Delete mnemonic. : Rename mnemonic from ... : ...to this. : Delete mnemonics. : Rename mnemonic from ... : ...to this. gas/ Apply from master. 2016-09-14 Peter Bergner * testsuite/gas/ppc/power9.d New tests. : Remove tests. : Update tests. * testsuite/gas/ppc/power9.s: Likewise. commit c6a7c521c14e0cc188ccc0388e0d5d21c2042c94 Author: Alan Modra Date: Thu Sep 1 14:56:52 2016 +0930 Don't treat .opd section specially when ELFv2 Fixes a gdb segfault if a section named .opd is found in ELFv2 bina
[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Changed in: aptdaemon (Ubuntu) Assignee: kirill (kirill-yalta) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Confirmed Status in Debconf: Unknown Status in aptdaemon package in Ubuntu: Incomplete Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706760] Re: lightdm/login session fails to resume after display is locked and goes to black
This is running on Xenial/16.04. Buggy behavior is similar to that described in https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1543888 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706760 Title: lightdm/login session fails to resume after display is locked and goes to black Status in lightdm package in Ubuntu: New Bug description: Logging in after a fresh boot works fine. Subsequently, after locking the screen (either Super + L or allow to auto-lock) and letting the screen turn off automatically, then attempting to wake the machine, only a black screen and the mouse cursor are visible. The desktop and authentication prompt do not re-appear, and though the mouse cursor moves, the machine doesn't respond to keyboard entry except to switch to a virtual console with Ctrl + Alt + 1 (2, 3, etc). From there it's possible to reboot or kill -HUP lightdm, but in either case, the active Unity login session is lost. I've check various log files, including /var/log/lightdm/* but haven't noticed any obvious culprits. This started after the following system updates on 2017-07-25 (/var/log/apt/history.log): Start-Date: 2017-07-25 08:32:14 Commandline: apt upgrade Requested-By: myusername (1000) Upgrade: libfwup0:amd64 (0.5-2ubuntu4, 0.5-2ubuntu5), unity-control-center-faces:amd64 (15.04.0+16.04.20160705-0ubuntu1, 15.04.0+16.04.20170214-0ubuntu1), linux-libc-dev:amd64 (4.4.0-83.106, 4.4.0-87.110), xserver-common:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), libgtk2.0-bin:amd64 (2.24.30-1ubuntu1, 2.24.30-1ubuntu1.16.04.1), imagemagick:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libsystemd0:amd64 (229-4ubuntu17, 229-4ubuntu19), libmagickwand-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libgail-common:amd64 (2.24.30-1ubuntu1, 2.24.30-1ubuntu1.16.04.1), libgtk2.0-0:amd64 (2.24.30-1ubuntu1, 2.24.30-1ubuntu1.16.04.1), coreutils:amd64 (8.25-2ubuntu2, 8.25-2ubuntu3~16.04), udev:amd64 (229-4ubuntu17, 229-4ubuntu19), libepoxy0:amd64 (1.3.1-1ubuntu0.16.04.1, 1.3.1-1ubuntu0.16.04.2), libgail18:amd64 (2.24.30-1ubuntu1, 2.24.30-1ubuntu1.16.04.1), fwupdate:amd64 (0.5-2ubuntu4, 0.5-2ubuntu5), libudev1:amd64 (229-4ubuntu17, 229-4ubuntu19), unity-control-center:am d64 (15.04.0+16.04.20160705-0ubuntu1, 15.04.0+16.04.20170214-0ubuntu1), imagemagick-6.q16:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), systemd-sysv:amd64 (229-4ubuntu17, 229-4ubuntu19), session-shortcuts:amd64 (1.2, 1.2ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu17, 229-4ubuntu19), systemd:amd64 (229-4ubuntu17, 229-4ubuntu19), libmagickcore-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libgtk2.0-common:amd64 (2.24.30-1ubuntu1, 2.24.30-1ubuntu1.16.04.1), xserver-xorg-core-hwe-16.04:amd64 (2:1.18.4-1ubuntu6.1~16.04.1, 2:1.18.4-1ubuntu6.1~16.04.2), libunity-control-center1:amd64 (15.04.0+16.04.20160705-0ubuntu1, 15.04.0+16.04.20170214-0ubuntu1), imagemagick-common:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), fwupdate-signed:amd64 (1.11+0.5-2ubuntu4, 1.11.1+0.5-2ubuntu5) End-Date: 2017-07-25 08:34:11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 26 12:43:23 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-19 (68 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1706760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706760] [NEW] lightdm/login session fails to resume after display is locked and goes to black
Public bug reported: Logging in after a fresh boot works fine. Subsequently, after locking the screen (either Super + L or allow to auto-lock) and letting the screen turn off automatically, then attempting to wake the machine, only a black screen and the mouse cursor are visible. The desktop and authentication prompt do not re-appear, and though the mouse cursor moves, the machine doesn't respond to keyboard entry except to switch to a virtual console with Ctrl + Alt + 1 (2, 3, etc). From there it's possible to reboot or kill -HUP lightdm, but in either case, the active Unity login session is lost. I've check various log files, including /var/log/lightdm/* but haven't noticed any obvious culprits. This started after the following system updates on 2017-07-25 (/var/log/apt/history.log): Start-Date: 2017-07-25 08:32:14 Commandline: apt upgrade Requested-By: myusername (1000) Upgrade: libfwup0:amd64 (0.5-2ubuntu4, 0.5-2ubuntu5), unity-control-center-faces:amd64 (15.04.0+16.04.20160705-0ubuntu1, 15.04.0+16.04.20170214-0ubuntu1), linux-libc-dev:amd64 (4.4.0-83.106, 4.4.0-87.110), xserver-common:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), libgtk2.0-bin:amd64 (2.24.30-1ubuntu1, 2.24.30-1ubuntu1.16.04.1), imagemagick:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libsystemd0:amd64 (229-4ubuntu17, 229-4ubuntu19), libmagickwand-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libgail-common:amd64 (2.24.30-1ubuntu1, 2.24.30-1ubuntu1.16.04.1), libgtk2.0-0:amd64 (2.24.30-1ubuntu1, 2.24.30-1ubuntu1.16.04.1), coreutils:amd64 (8.25-2ubuntu2, 8.25-2ubuntu3~16.04), udev:amd64 (229-4ubuntu17, 229-4ubuntu19), libepoxy0:amd64 (1.3.1-1ubuntu0.16.04.1, 1.3.1-1ubuntu0.16.04.2), libgail18:amd64 (2.24.30-1ubuntu1, 2.24.30-1ubuntu1.16.04.1), fwupdate:amd64 (0.5-2ubuntu4, 0.5-2ubuntu5), libudev1:amd64 (229-4ubuntu17, 229-4ubuntu19), unity-control-center:amd6 4 (15.04.0+16.04.20160705-0ubuntu1, 15.04.0+16.04.20170214-0ubuntu1), imagemagick-6.q16:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), systemd-sysv:amd64 (229-4ubuntu17, 229-4ubuntu19), session-shortcuts:amd64 (1.2, 1.2ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu17, 229-4ubuntu19), systemd:amd64 (229-4ubuntu17, 229-4ubuntu19), libmagickcore-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libgtk2.0-common:amd64 (2.24.30-1ubuntu1, 2.24.30-1ubuntu1.16.04.1), xserver-xorg-core-hwe-16.04:amd64 (2:1.18.4-1ubuntu6.1~16.04.1, 2:1.18.4-1ubuntu6.1~16.04.2), libunity-control-center1:amd64 (15.04.0+16.04.20160705-0ubuntu1, 15.04.0+16.04.20170214-0ubuntu1), imagemagick-common:amd64 (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), fwupdate-signed:amd64 (1.11+0.5-2ubuntu4, 1.11.1+0.5-2ubuntu5) End-Date: 2017-07-25 08:34:11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 26 12:43:23 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-19 (68 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1706760 Title: lightdm/login session fails to resume after display is locked and goes to black Status in lightdm package in Ubuntu: New Bug description: Logging in after a fresh boot works fine. Subsequently, after locking the screen (either Super + L or allow to auto-lock) and letting the screen turn off automatically, then attempting to wake the machine, only a black screen and the mouse cursor are visible. The desktop and authentication prompt do not re-appear, and though the mouse cursor moves, the machine doesn't respond to keyboard entry except to switch to a virtual console with Ctrl + Alt + 1 (2, 3, etc). From there it's possible to reboot or kill -HUP lightdm, but in either case, the active Unity login session is lost. I've check various log files, including /var/log/lightdm/* but haven't noticed any obvious culprits. This started after the following system updates on 2017-07-25 (/var/log/apt/history.log): Start-Date: 2017-07-25 08:32:14 Commandline: apt upgrade Requested-By: myusername (1000) Upgrade: libfwup0:amd64 (0.5-2ubuntu4, 0.5-2ubuntu5), unity-control-center-faces:amd64 (15.04.0+16.04.20160705-0ubuntu1, 15.04.0+16.04.20170214-0ubuntu1), linux-libc-dev:amd64 (4.4.0-83.106, 4.4.0-87.110), xserver-common:amd64 (2:1.18.4-0ubuntu0.2, 2:1.18.
[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Changed in: aptdaemon (Ubuntu) Assignee: (unassigned) => kirill (kirill-yalta) ** Changed in: debconf Importance: Undecided => Unknown ** Changed in: debconf Status: New => Unknown ** Changed in: debconf Remote watch: None => Debian Bug tracker #469354 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Confirmed Status in Debconf: Unknown Status in aptdaemon package in Ubuntu: Incomplete Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706749] Re: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1706749 Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Trying to install vmware-player ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu19 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Jul 26 21:01:00 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-07-16 (10 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7181 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic root=UUID=3d325940-e5d7-4eb5-9234-f636a71bba76 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7181 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 1.00 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/16/2005:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7181:pvr1.00:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7181:rvr1.00:cvn:ct3:cvr: dmi.product.name: MS-7181 dmi.product.version: 1.00 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1706749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706749] [NEW] package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Trying to install vmware-player ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu19 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Jul 26 21:01:00 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-07-16 (10 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7181 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic root=UUID=3d325940-e5d7-4eb5-9234-f636a71bba76 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7181 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 1.00 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/16/2005:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7181:pvr1.00:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7181:rvr1.00:cvn:ct3:cvr: dmi.product.name: MS-7181 dmi.product.version: 1.00 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1706749 Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Trying to install vmware-player ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu19 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Jul 26 21:01:00 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-07-16 (10 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7181 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic root=UUID=3d325940-e5d7-4eb5-9234-f636a71bba76 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package udev 229-4ubuntu19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7181 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 1.00 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/16/2005:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7181:pvr1.00:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7181:rvr1.00:cvn:ct3:cvr: dmi.product.name: MS-7181 dmi.product.version: 1.00 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1706749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1678606] Re: [packaging] Missing dnsmasq-base dependency causes wifi hotspot/network sharing feature broken
This bug was fixed in the package network-manager - 1.8.2-1ubuntu2 --- network-manager (1.8.2-1ubuntu2) artful; urgency=medium * Restore dnsmasq-base recommends. This was dropped on switching to resolved but is still needed for creating Ad-hoc connections and connection sharing. (LP: #1678606) -- Jeremy Bicha Wed, 26 Jul 2017 09:22:49 -0400 ** Changed in: network-manager (Ubuntu) Status: Fix Committed => Fix Released -- 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/1678606 Title: [packaging] Missing dnsmasq-base dependency causes wifi hotspot/network sharing feature broken Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Zesty: Triaged Bug description: Impact === In Ubuntu 17.04, the dnsmasq-base dependency has been dropped from network-manager, and the wifi network sharing feature failed to work because of this: NetworkManager[874]: [1491134643.1581] device (wlp3s0): share: (wlp3s0) failed to start dnsmasq: Could not find "dnsmasq" binary In my opinion it should at least in Recommends, refer following for related info: Bug #992411 “network-manager: Please don't Depend on dnsmasq-bas...” : Bugs : network-manager package : Ubuntu https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/992411 This recommends was dropped here: https://launchpadlibrarian.net/279417634/network-manager_1.2.2-0ubuntu6_1.2.2-0ubuntu7.diff.gz Test Case = Install the update and ensure that dnsmasq-base is installed (it is a recommends so it should be pulled in automatically by this update). This test case requires a laptop (or desktop with Wi-Fi hardware) running Ubuntu 17.04 with an ethernet connection to the Internet. Open a terminal and run journalctl -f Then open the Settings app (unity-control-center if running Unity, gnome-control-center if running GNOME) and click the Network panel. Enable the Wi-Fi hotspot. Use another device to connect to the Wi-Fi hotspot with the Access Point name and the password presented. Use the Internet on the other device. There should not be any warnings in the journal output in the terminal about "could not find dnsmasq" Regression Potential Other Info == This change was agreed upon by the Ubuntu Desktop Team and Martin Pitt who spearheaded the resolved transition for Ubuntu 17.04. https://irclogs.ubuntu.com/2017/07/25/%23ubuntu-desktop.html#t13:27 (until 14:45) This drops a diff with Debian because Debian already recommends dnsmasq-base. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Apr 2 20:28:25 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-03-30 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) IpRoute: default via 192.168.1.1 dev enp4s0f2 proto static metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev enp4s0f2 proto kernel scope link src 192.168.1.119 metric 100 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f2 ethernet connected /org/freedesktop/NetworkManager/Devices/1 由 DHCP 伺服器自動配發 IP 地址的網路 66cd739f-4bfd-4cbc-909f-1cd96e9ec8bb /org/freedesktop/NetworkManager/ActiveConnection/8 wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/2 林博仁的模擬 Wi-Fi 網路 2547ce2c-a517-4d31-83a2-4bb38fc704cb /org/freedesktop/NetworkManager/ActiveConnection/14 loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
Yes, I believe this still affects 16.04. I applied the patch on machines that System76 ships, but it is not upstream. It is the same patch as was applied to 17.04. -- 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/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: New Status in ubiquity source package in Xenial: New Status in wpa source package in Xenial: New Bug description: * Steps to reproduce: 1. Install image 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619844] Re: [Xenial] shutdown/reboot hangs at "Reached target Shutdown"
Same issue here, on a Supermicro 6018R-WTR server. I've attached a screenshot of the hung state. Note that the watchdog message is because I've set up IPMI watchdog on this machine (as a workaround for this issue). The hang on reboot is not happening every time for me - something like 10%-20% of reboots result in a hang. Kernel version is 4.4.0-87. I have tried setting reboot=pci on the kernel command line and blacklisting mei and mei_me modules, but neither of those resolved the problem. ** Attachment added: "screenshot of hung state" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1619844/+attachment/4921830/+files/screenshot.png -- 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/1619844 Title: [Xenial] shutdown/reboot hangs at "Reached target Shutdown" Status in systemd package in Ubuntu: Confirmed Bug description: I tried getting more information in the debug-shell but I was unsuccessful in doing so. I was able to switch to the debug shell via ctrl+alt+f9 but I couldn't actually type anything in. I could switch back to the stuck shutdown screen via ctrl+alt+f1, and hitting NumLock would turn the light on my keyboard on and off, but I couldn't do anything else. I captured a journal of the stuck reboot. Interestingly, the journal shows a few more lines after "Reached target Shutdown", which is as far as I get on my screen. This system was installed with Xenial 16.04.1 (never been upgraded) and has had this problem since the very first boot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Sep 3 00:33:19 2016 InstallationDate: Installed on 2016-08-17 (16 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=5f709fed-48c9-4830-87be-acd13f263eb1 ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/mariadb.service → /etc/systemd/system/mariadb.service.d/migrated-from-my.cnf-settings.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1619844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706740] [NEW] ruby upgrade broke redmine dependency
Public bug reported: On a Ubuntu 16.04 system deploying a Redmine issue tracker using the Ubuntu redmine package this night's (the systemd apt-daily timer has been rescheduled to run at 00:30) unattended upgrade of USN-3365 security updates to Ruby packages (https://usn.ubuntu.com/usn/usn-3365-1/) caused the Redmine application to break. Accessing the site caused Phusion Passenger to come up with a "We're sorry, but something went wrong.". The problem was identified and notified by email during the upgrade's processing of triggers on the redmine package where it was determined that the gem dependency "webrat" somehow was unavailable. The situation was resolved by running "bundle install" in the base directory /usr/share/redmine which caused most of the gems to be updated but I feel uneasy about this being a problem at all and fear breakage on future upgrades. I'm not too familiar with ruby, gems, bundler and apt triggers, so I've been unable to grasp where things go wrong and where a remedy is best deployed. Could it be as simple as adding a bundle update/install to the redmine trigger? Besides the core dependency to webrat, I got a plugin referring to webrat also: $ grep -r webrat /var/lib/redmine/ /usr/share/redmine /var/lib/redmine/Gemfile.lock:webrat (0.7.3) /var/lib/redmine/Gemfile.lock: webrat /usr/share/redmine/plugins/redmine_timesheet_plugin/Gemfile: gem 'webrat' /usr/share/redmine/plugins/redmine_timesheet_plugin/test/test_helper.rb:require "webrat" >From /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Log started: 2017-07-26 00:30:16 Reading changelogs... (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 286395 files and directories currently installed.) Preparing to unpack .../ruby2.3-dev_2.3.1-2~16.04.2_amd64.deb ... Unpacking ruby2.3-dev:amd64 (2.3.1-2~16.04.2) over (2.3.1-2~16.04) ... Preparing to unpack .../libruby2.3_2.3.1-2~16.04.2_amd64.deb ... Unpacking libruby2.3:amd64 (2.3.1-2~16.04.2) over (2.3.1-2~16.04) ... Preparing to unpack .../ruby2.3_2.3.1-2~16.04.2_amd64.deb ... Unpacking ruby2.3 (2.3.1-2~16.04.2) over (2.3.1-2~16.04) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... Processing triggers for redmine (3.2.1-2) ... Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. ESC[31mCould not find gem 'webrat' in any of the gem sources listed in your Gemfile or available on this machine.ESC[0m dpkg: error processing package redmine (--unpack): subprocess installed post-installation script returned error exit status 7 Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: redmine Log ended: 2017-07-26 00:30:21 >From /var/log/unattended-upgrades/unattended-upgrades.log 2017-07-26 00:30:11,371 INFO Starting unattended upgrades script 2017-07-26 00:30:11,371 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] 2017-07-26 00:30:15,947 INFO Packages that will be upgraded: libruby2.3 ruby2.3 ruby2.3-dev 2017-07-26 00:30:15,948 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2017-07-26 00:30:21,299 ERROR Installing the upgrades failed! 2017-07-26 00:30:21,299 ERROR error message: 'installArchives() failed' 2017-07-26 00:30:21,299 ERROR dpkg returned a error! See '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' for details $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial $ apt-cache policy redmine passenger redmine: Installed: 3.2.1-2 Candidate: 3.2.1-2 Version table: *** 3.2.1-2 500 500 http://dk.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://dk.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status passenger: Installed: 5.0.27-2 Candidate: 5.0.27-2 Version table: *** 5.0.27-2 500 500 http://dk.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- 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/1706740 Title: ruby upgra
[Touch-packages] [Bug 1694455] Re: Bluetooth: Cannot receive files, due to OBEX configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-bluetooth (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1694455 Title: Bluetooth: Cannot receive files, due to OBEX configuration Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: # Use case Ubuntu 17.04, quite fresh installation, updated. Bluetooth file transmission I want to send files to my smartphone, and receive files sent by my smartphone via bluetooth. I pair both devices, initiate file transfer from one of the devices, and the other device asks me what to do. # Problems This is a mix from usability and technical issues. 1. OBEX disabled The bluetooth file transmission service OBEX was not started. I started and enabled OBEX: `systemctl --user start obex` `systemctl --user enable obex` ``` Mai 30 14:47:55 tp systemd[1661]: Starting Bluetooth OBEX service... Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 ``` 2. OBEX silently fails After having OBEX enabled, I was able to transmit files from laptop to smartphone, yet I could not receive files on the laptop. In the system log, you could see that OBEX fails (please note `FORBIDDEN`): ``` Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x0) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), FORBIDDEN(0x43) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20) Mai 30 14:48:04 tp obexd[8168]: disconnected: Transport got disconnected ``` I did not receive a popup notification asking me to receive the file or not. In the file sharing preferences `gnome-file-share-properties`, there is a setting to automatically receive files via bluetooth. With this box checked, you're finally able to receive files from your smartphone. Successful log for comparison: ``` Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x) Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x0) Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), (null)(0x) Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), CONTINUE(0x10) Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), (null)(0x) Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20) Mai 30 14:56:28 tp obexd[8168]: disconnected: Transport got disconnected ``` # Expected behaviour OBEX is started by default to handle bluetooth file transfers. If no automatic file receipt is configured, a popup notification asks me if I want to receive the file or not. If this is not possible, there should be a notification pointing the user to the configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1694455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694455] Re: Bluetooth: Cannot receive files, due to OBEX configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1694455 Title: Bluetooth: Cannot receive files, due to OBEX configuration Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: # Use case Ubuntu 17.04, quite fresh installation, updated. Bluetooth file transmission I want to send files to my smartphone, and receive files sent by my smartphone via bluetooth. I pair both devices, initiate file transfer from one of the devices, and the other device asks me what to do. # Problems This is a mix from usability and technical issues. 1. OBEX disabled The bluetooth file transmission service OBEX was not started. I started and enabled OBEX: `systemctl --user start obex` `systemctl --user enable obex` ``` Mai 30 14:47:55 tp systemd[1661]: Starting Bluetooth OBEX service... Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 ``` 2. OBEX silently fails After having OBEX enabled, I was able to transmit files from laptop to smartphone, yet I could not receive files on the laptop. In the system log, you could see that OBEX fails (please note `FORBIDDEN`): ``` Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43 Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x0) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), FORBIDDEN(0x43) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), (null)(0x) Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20) Mai 30 14:48:04 tp obexd[8168]: disconnected: Transport got disconnected ``` I did not receive a popup notification asking me to receive the file or not. In the file sharing preferences `gnome-file-share-properties`, there is a setting to automatically receive files via bluetooth. With this box checked, you're finally able to receive files from your smartphone. Successful log for comparison: ``` Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x) Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x0) Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), (null)(0x) Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), CONTINUE(0x10) Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), (null)(0x) Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20) Mai 30 14:56:28 tp obexd[8168]: disconnected: Transport got disconnected ``` # Expected behaviour OBEX is started by default to handle bluetooth file transfers. If no automatic file receipt is configured, a popup notification asks me if I want to receive the file or not. If this is not possible, there should be a notification pointing the user to the configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1694455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
** Changed in: cloud-init (Ubuntu Yakkety) Status: Fix Committed => Won't Fix -- 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/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Confirmed Status in cloud-init: Confirmed Status in apt package in Ubuntu: New Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: Won't Fix Status in cloud-init source package in Zesty: Fix Released Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: $ cat my.yaml #cloud-config packages: ['hello'] [Test Case] lxc-proposed-snapshot is https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot It publishes an image to lxd with proposed enabled and cloud-init upgraded. a.) launch an instance with proposed version of cloud-init and some user-data. This is platform independent. The test case demonstrates lxd. $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ "package_upgrade: true" > config.yaml $ release=xenial $ ref=proposed-$release $ ./lxc-proposed-snapshot --proposed --publish $release $ref; b.) start the instance $ name=$release-1693361 $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) $ sleep 1 $ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log # watch this boot. c.) Look for evidence of systemd failure journalctl -o short-precise | grep -i break journalctl -o short-precise | grep -i order [Regression Potential] Regression chance here is low. Its possible that ordering loops could occur. When that does happen, journalctl will mention it. Unfortunately in such cases systemd somewhat randomly picks a service to kil so behavior is somewhat undefined. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11121fe4 === End SRU Template === apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f- 0ubuntu1~17.04.2 --- cloud-init (0.7.9-153-g16a7302f-0ubuntu1~17.04.2) zesty-proposed; urgency=medium * cherry-pick 5fb49bac: azure: identify platform by well known value in chassis asset (LP: #1693939) * cherry-pick 003c6678: net: remove systemd link file writing from eni renderer * cherry-pick 1cd4323b: azure: remove accidental duplicate line in merge. * cherry-pick ebc9ecbc: Azure: Add network-config, Refactor net layer to handle duplicate macs. (LP: #1690430) * cherry-pick 11121fe4: systemd: make cloud-final.service run before apt daily (LP: #1693361) -- Scott Moser Wed, 28 Jun 2017 17:20:51 -0400 ** Changed in: cloud-init (Ubuntu Zesty) Status: Fix Committed => Fix Released -- 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/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Confirmed Status in cloud-init: Confirmed Status in apt package in Ubuntu: New Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: Won't Fix Status in cloud-init source package in Zesty: Fix Released Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: $ cat my.yaml #cloud-config packages: ['hello'] [Test Case] lxc-proposed-snapshot is https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot It publishes an image to lxd with proposed enabled and cloud-init upgraded. a.) launch an instance with proposed version of cloud-init and some user-data. This is platform independent. The test case demonstrates lxd. $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ "package_upgrade: true" > config.yaml $ release=xenial $ ref=proposed-$release $ ./lxc-proposed-snapshot --proposed --publish $release $ref; b.) start the instance $ name=$release-1693361 $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) $ sleep 1 $ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log # watch this boot. c.) Look for evidence of systemd failure journalctl -o short-precise | grep -i break journalctl -o short-precise | grep -i order [Regression Potential] Regression chance here is low. Its possible that ordering loops could occur. When that does happen, journalctl will mention it. Unfortunately in such cases systemd somewhat randomly picks a service to kil so behavior is somewhat undefined. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11121fe4 === End SRU Template === apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Additionally, when I modified my reboot script to reboot when linux- headers were half-installed I ran into the following: bdmurray@clean-xenial-amd64:~$ sudo apt-get dist-upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. I thought that is what we are trying to avoid. Here's the script: bdmurray@clean-xenial-amd64:~$ cat u-u-reboot.sh #!/bin/sh loop=1 count=0 today=$(date +%Y-%m-%d) while [ $loop -gt 0 ] do count=$(expr $count + 1) echo "loop...$count" time=$(date +%H:%M) if [ $(grep -r -e "$today $time.*status half-installed linux-headers.*" /var/log/dpkg.log | wc -l) -ge 1 ]; then aplay /usr/share/sounds/alsa/Front_Right.wav sudo reboot fi sleep 1 done -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1525628] Re: tracker needs to be killed on every boot
Similar problem, if I stop work it takes over and everything locks up, even though there doesn't appear to be anything to index according to "tracker status". Have had to remove it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1525628 Title: tracker needs to be killed on every boot Status in tracker package in Ubuntu: Confirmed Bug description: At every boot, tacker-miner-fs and tracker-extract uses all of the processor and needs to be killed manually for computer to work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tracker 1.6.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 13 13:02:58 2015 InstallationDate: Installed on 2015-04-24 (232 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1525628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698181] Re: Switch to netplan renderer in Artful
** Branch linked: lp:~vorlon/ubuntu-seeds/ubuntu.artful-drop-ifupdown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1698181 Title: Switch to netplan renderer in Artful Status in cloud-images: New Status in cloud-init package in Ubuntu: Fix Released Status in ifupdown package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Status in maas package in Ubuntu: New Status in resolvconf package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Ubuntu server ISOs are moving to netplan and cloud images must follow suit. We are requesting that the default renderer in 17.10 be switched to netplan to be consistent across all cloud images and ISO installs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1698181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704288] Re: Ubuntu 16.04 VPN : DNS information leaking through dnsmasq
Do you have your vpn configuration in network-manager so that all traffic should go through it, or do you have "Use this connection only for resources on its network" checked? That's in ipv4-settings->routes, same under ipv6-settings. Also, I assume your /etc/resolv.conf, *after* connecting to the vpn, still has only one "nameserver" entry and pointing at 127.0.1.1? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1704288 Title: Ubuntu 16.04 VPN : DNS information leaking through dnsmasq Status in dnsmasq package in Ubuntu: Incomplete Bug description: Hi, After connecting the VPN # killall -USR1 dnsmasq # tail syslog.log ... Jul 13 02:18:56 tp dnsmasq[1476]: time 1499905136 Jul 13 02:18:56 tp dnsmasq[1476]: cache size 0, 0/0 cache insertions re-used unexpired cache entries. Jul 13 02:18:56 tp dnsmasq[1476]: queries forwarded 154, queries answered locally 1 Jul 13 02:18:56 tp dnsmasq[1476]: queries for authoritative zones 0 Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.1#53: queries sent 0, retried or failed 0 Jul 13 02:18:56 tp dnsmasq[1476]: server 198.18.0.2#53: queries sent 0, retried or failed 0 Jul 13 02:18:56 tp dnsmasq[1476]: server 192.168.0.254#53: queries sent 12, retried or failed 0 The first two name server are provided by the vpn connection. The last 192.168.0.254 name server is running on my local router and forward request to my ISP (this is the default name server when VPN is not activated). When I query the DNS, queries are sent to each name server which makes a DNS information leaking to my ISP I validated that by the mean of tcpdump on eth and tun interfaces and also by using that site: https://www.dnsleaktest.com/ I tried to force the VPN DNS server IPs in the VPN configuration (edit Vpn connection -> ipv4 - > Automatic Adresses only ..) but the result is the same. dnsmasq must not have the local DNS present while VPN connection is established. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1704288/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698181] Re: Switch to netplan renderer in Artful
On Wed, Jul 26, 2017 at 04:48:22PM -, Scott Moser wrote: > I think that resolvconf should be listed here, as it Depends on ifupdown. > also resolvconf is rdepend'd on by ubuntu-minimal, so I think that > ubuntu-meta probably needs another bump. The intent is to drop resolvconf from minimal. I believe Dimitri is in the process of landing the necessary systemd changes to let us remove resolvconf integration. ** Changed in: resolvconf (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: resolvconf (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1698181 Title: Switch to netplan renderer in Artful Status in cloud-images: New Status in cloud-init package in Ubuntu: Fix Released Status in ifupdown package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Status in maas package in Ubuntu: New Status in resolvconf package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Ubuntu server ISOs are moving to netplan and cloud images must follow suit. We are requesting that the default renderer in 17.10 be switched to netplan to be consistent across all cloud images and ISO installs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1698181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698181] Re: Switch to netplan renderer in Artful
marking cloud-init fix-released under bug 1705639. ** Changed in: cloud-init (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1698181 Title: Switch to netplan renderer in Artful Status in cloud-images: New Status in cloud-init package in Ubuntu: Fix Released Status in ifupdown package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Status in maas package in Ubuntu: New Status in resolvconf package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Ubuntu server ISOs are moving to netplan and cloud images must follow suit. We are requesting that the default renderer in 17.10 be switched to netplan to be consistent across all cloud images and ISO installs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1698181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698181] Re: Switch to netplan renderer in Artful
apt-get upgraded lxc container just now, shows: root@a2:~# apt-get remove ifupdown Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: ifenslave ifupdown resolvconf ubuntu-minimal 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded. After this operation, 543 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. root@a2:~# cat /etc/cloud/build.info build_name: server serial: 20170725 Also note # apt-cache rdepends ifenslave ifenslave Reverse Depends: ifenslave-2.6 ubuntu-server So thats another change we probably need for ubuntu-meta/seeds. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1698181 Title: Switch to netplan renderer in Artful Status in cloud-images: New Status in cloud-init package in Ubuntu: Fix Released Status in ifupdown package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Status in maas package in Ubuntu: New Status in resolvconf package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Ubuntu server ISOs are moving to netplan and cloud images must follow suit. We are requesting that the default renderer in 17.10 be switched to netplan to be consistent across all cloud images and ISO installs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1698181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal
** Description changed: + The ubuntu-advantage-tools package is a bit odd as it was first landed + in precise to support the ESM effort inside canonical. [0] In order to + bring this package up to date across other series in ubuntu, it has been + recommended by the Ubuntu Foundations team to land into trusty next, + then forward-port pocket-copy to all supported series until we get to + the devel release. + + The version here: + + https://github.com/CanonicalLtd/ubuntu-advantage-script/releases/tag/v2 + + ... has all on-disk bits correctly working, for all series, but no-ops + on any release other than precise (ESM is only for "unsupported" LTS + releases as it were). This is a request to land ESM into trusty, then + pocket-copy it to supported series of ubuntu once that is finished. + + [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html + + [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04-esm- + extended-security-maintenance/ ** Description changed: The ubuntu-advantage-tools package is a bit odd as it was first landed in precise to support the ESM effort inside canonical. [0] In order to bring this package up to date across other series in ubuntu, it has been recommended by the Ubuntu Foundations team to land into trusty next, then forward-port pocket-copy to all supported series until we get to the devel release. The version here: https://github.com/CanonicalLtd/ubuntu-advantage-script/releases/tag/v2 ... has all on-disk bits correctly working, for all series, but no-ops on any release other than precise (ESM is only for "unsupported" LTS - releases as it were). This is a request to land ESM into trusty, then - pocket-copy it to supported series of ubuntu once that is finished. - + releases as it were). This is a request to land ubuntu-advantage-tools + into trusty, then pocket-copy it to supported series of ubuntu once that + is finished. [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04-esm- extended-security-maintenance/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal Status in ubuntu-advantage-tools package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-advantage-tools source package in Precise: Fix Released Status in ubuntu-meta source package in Precise: Fix Released Status in ubuntu-advantage-tools source package in Trusty: New Status in ubuntu-meta source package in Trusty: New Status in ubuntu-advantage-tools source package in Xenial: New Status in ubuntu-meta source package in Xenial: New Status in ubuntu-advantage-tools source package in Yakkety: New Status in ubuntu-meta source package in Yakkety: New Status in ubuntu-advantage-tools source package in Zesty: New Status in ubuntu-meta source package in Zesty: New Status in ubuntu-advantage-tools source package in Artful: New Status in ubuntu-meta source package in Artful: New Bug description: The ubuntu-advantage-tools package is a bit odd as it was first landed in precise to support the ESM effort inside canonical. [0] In order to bring this package up to date across other series
[Touch-packages] [Bug 1698181] Re: Switch to netplan renderer in Artful
I think that resolvconf should be listed here, as it Depends on ifupdown. also resolvconf is rdepend'd on by ubuntu-minimal, so I think that ubuntu-meta probably needs another bump. ** Also affects: resolvconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1698181 Title: Switch to netplan renderer in Artful Status in cloud-images: New Status in cloud-init package in Ubuntu: Fix Released Status in ifupdown package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Status in maas package in Ubuntu: New Status in resolvconf package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Ubuntu server ISOs are moving to netplan and cloud images must follow suit. We are requesting that the default renderer in 17.10 be switched to netplan to be consistent across all cloud images and ISO installs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1698181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
I had previously recommended (and consequently installed for them) Ubuntu 16.04 LVM to my parents however their"/boot" partition was constantly filling up to 100% and they kept complaining to me about it (as they are computer illiterate) so I had to eventually reinstall windows 10 for them and scrap Ubuntu all together. A pretty sad state of affairs. This is definitely a bug and it is making people turn away from Linux in favor of Windows. I wish someone would provide a simple fix for this. -- 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/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706305] Re: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
Thank you for taking the time to file a bug report. One of your packages is reporting that it is in an inconsistent state. This needs to be solved before you continue further operations. To help you get started please see this question and response: https://askubuntu.com/questions/148715/how-to-fix-package-is-in-a-very-bad-inconsistent-state-error Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: libnl3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1706305 Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libnl3 package in Ubuntu: Incomplete Bug description: I don't know what is the problem. I only have read the notification telling me I have a problem in ubuntu. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Tue Jul 25 12:18:43 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 libnl-3-200 3.2.29-0ubuntu2.1 DuplicateSignature: package:libnl-genl-3-200:amd64:3.2.29-0ubuntu2.1 Setting up mythes-en-au (2.1-5.4) ... dpkg: error processing package libnl-genl-3-200:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-07-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1706305/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706305] Re: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
>From logs: dpkg: error processing package libnl-genl-3-200:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1706305 Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libnl3 package in Ubuntu: Incomplete Bug description: I don't know what is the problem. I only have read the notification telling me I have a problem in ubuntu. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Tue Jul 25 12:18:43 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 libnl-3-200 3.2.29-0ubuntu2.1 DuplicateSignature: package:libnl-genl-3-200:amd64:3.2.29-0ubuntu2.1 Setting up mythes-en-au (2.1-5.4) ... dpkg: error processing package libnl-genl-3-200:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-07-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1706305/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706414] Re: package libwind0-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package libwind0-heimdal:amd64 is not ready for configuration cannot
>From log: Processing triggers for update-notifier-common (3.168.4) ... dpkg: error processing package libwind0-heimdal:amd64 (--configure): package libwind0-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1706414 Title: package libwind0-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package libwind0-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in heimdal package in Ubuntu: Incomplete Bug description: I was trying to update my software when I faced this bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libwind0-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: flashplugin-installer: Remove libwind0-heimdal: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 25 18:23:15 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libcomerr2 1.42.13-1ubuntu1 libgcc1 1:6.0.1-0ubuntu1 libroken18-heimdal 1.7~git20150920+dfsg-4ubuntu1.16.04.1 DpkgTerminalLog: Removing flashplugin-installer (26.0.0.131ubuntu0.16.04.1) ... Processing triggers for update-notifier-common (3.168.4) ... dpkg: error processing package libwind0-heimdal:amd64 (--configure): package libwind0-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') DuplicateSignature: package:libwind0-heimdal:amd64:1.7~git20150920+dfsg-4ubuntu1.16.04.1 Processing triggers for update-notifier-common (3.168.4) ... dpkg: error processing package libwind0-heimdal:amd64 (--configure): package libwind0-heimdal:amd64 is not ready for configuration ErrorMessage: package libwind0-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-07 (48 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: heimdal Title: package libwind0-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package libwind0-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1706414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706414] Re: package libwind0-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package libwind0-heimdal:amd64 is not ready for configuration cannot
Thank you for taking the time to file a bug report. It looks like the install did not complete. Can you try running: 'sudo apt-get install -f' and see what it says? Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: heimdal (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1706414 Title: package libwind0-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package libwind0-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in heimdal package in Ubuntu: Incomplete Bug description: I was trying to update my software when I faced this bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libwind0-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: flashplugin-installer: Remove libwind0-heimdal: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 25 18:23:15 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libcomerr2 1.42.13-1ubuntu1 libgcc1 1:6.0.1-0ubuntu1 libroken18-heimdal 1.7~git20150920+dfsg-4ubuntu1.16.04.1 DpkgTerminalLog: Removing flashplugin-installer (26.0.0.131ubuntu0.16.04.1) ... Processing triggers for update-notifier-common (3.168.4) ... dpkg: error processing package libwind0-heimdal:amd64 (--configure): package libwind0-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') DuplicateSignature: package:libwind0-heimdal:amd64:1.7~git20150920+dfsg-4ubuntu1.16.04.1 Processing triggers for update-notifier-common (3.168.4) ... dpkg: error processing package libwind0-heimdal:amd64 (--configure): package libwind0-heimdal:amd64 is not ready for configuration ErrorMessage: package libwind0-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-07 (48 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: heimdal Title: package libwind0-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package libwind0-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1706414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706709] [NEW] After installing a new sounds package the sounds were not picked up
Public bug reported: The sound theme was missing a dedicated sound for testing mono speakers. We "fixed" this by symlinking to an existing sound which was deemed suitable for testing. See LP:1703946 Once that package was installed the new sound still didn't play for some users. In the end laney worked out that we needed to "sudo touch /usr/share/sounds" and after that the new sound played. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcanberra0 0.30-3ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 26 12:05:55 2017 InstallationDate: Installed on 2017-06-07 (48 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170606.1) SourcePackage: libcanberra UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libcanberra (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1706709 Title: After installing a new sounds package the sounds were not picked up Status in libcanberra package in Ubuntu: New Bug description: The sound theme was missing a dedicated sound for testing mono speakers. We "fixed" this by symlinking to an existing sound which was deemed suitable for testing. See LP:1703946 Once that package was installed the new sound still didn't play for some users. In the end laney worked out that we needed to "sudo touch /usr/share/sounds" and after that the new sound played. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libcanberra0 0.30-3ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 26 12:05:55 2017 InstallationDate: Installed on 2017-06-07 (48 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170606.1) SourcePackage: libcanberra UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1706709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
So far this seems to work, I don't get an inconsistent system while
testing on Ubuntu 16.04, I did notice a crash report in /var/crash from
unattended-upgrades. Here's the Traceback:
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 918, in do_install
cache, logfile_dpkg, options.verbose or options.debug)
File "/usr/bin/unattended-upgrade", line 433, in upgrade_normal
res, error = cache_commit(cache, logfile_dpkg, verbose)
File "/usr/bin/unattended-upgrade", line 424, in cache_commit
res = cache.commit(install_progress=iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in
install_archives
res = install_progress.run(pm)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 208, in run
res = self.wait_child()
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 279, in
wait_child
self.update_interface()
File "/usr/bin/unattended-upgrade", line 227, in update_interface
self._do_verbose_output_if_needed()
File "/usr/bin/unattended-upgrade", line 244, in _do_verbose_output_if_needed
os.write(1, os.read(self.output_logfd, 1024))
OSError: [Errno 5] Input/output error
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1581, in
main(options)
File "/usr/bin/unattended-upgrade", line 1468, in main
logfile_dpkg)
File "/usr/bin/unattended-upgrade", line 921, in do_install
os.write(2, ("Exception: %s\n" % e).encode('utf-8'))
OSError: [Errno 5] Input/output error
--
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/1690980
Title:
unattended-upgrades does not block shutdown of system, as it is
designed to
Status in OEM Priority Project:
Triaged
Status in OEM Priority Project xenial series:
New
Status in apt package in Ubuntu:
Fix Committed
Status in unattended-upgrades package in Ubuntu:
Fix Committed
Bug description:
Title: No pop-up window to warn users that system should not reboot or
shutdown while installing security updates
Summary:
No pop-up window to warn users that system should not reboot or shutdown
while installing security updates
Steps:
1. trigger unattended-upgrades
2. reboot or shutdown system while installing packages
Expected results: There is a pop-up window to warn users that system
should not reboot or shutdown
Actual results: There is no pop-up window to warn users
Additional information:
$ apt-cache policy unattended-upgrades
unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590590] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie yakkety. The bug task representing the yakkety nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Yakkety) Status: New => Won't Fix -- 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/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in xserver-xorg-input-synaptics source package in Xenial: New Status in linux source package in Yakkety: Won't Fix Status in xserver-xorg-input-synaptics source package in Yakkety: New Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1645037] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie
yakkety. The bug task representing the yakkety nomination is being
closed as Won't Fix.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu Yakkety)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1645037
Title:
apparmor_parser hangs indefinitely when called by multiple threads
Status in apparmor package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Triaged
Status in linux source package in Yakkety:
Won't Fix
Status in linux source package in Zesty:
Fix Released
Bug description:
This bug surfaced when starting ~50 LXC container with LXD in parallel
multiple times:
# Create the containers
for c in c foo{1..50}; do lxc launch images:ubuntu/xenial $c; done
# Exectute this loop multiple times until you observe errors.
for c in c foo{1..50}; do lxc restart $c & done
After this you can
ps aux | grep apparmor
and you should see output similar to:
root 19774 0.0 0.0 12524 1116 pts/1S+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
root 19775 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
root 19776 0.0 0.0 13592 3224 pts/1D+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
root 19778 0.0 0.0 13592 3384 pts/1D+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
root 19780 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
root 19782 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
root 19783 0.0 0.0 13592 3388 pts/1D+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
root 19784 0.0 0.0 13592 3252 pts/1D+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
root 19794 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo25
root 19795 0.0 0.0 13592 3256 pts/1D+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo25
apparmor_parser remains stuck even after all LXC/LXD commands have
exited.
dmesg output yields lines like:
[41902.815174] audit: type=1400 audit(1480191089.678:43):
apparmor="STATUS" operation="profile_load" profile="unconfined" name
="lxd-foo30_" pid=12545 comm="apparmor_parser"
and cat /proc/12545/stack shows:
[] aa_remove_profiles+0x88/0x270
21:19 brauner [] profile_remove+0x144/0x2e0
21:19 brauner [] __vfs_write+0x18/0x40
21:19 brauner [] vfs_write+0xb8/0x1b0
21:19 brauner [] SyS_write+0x55/0xc0
21:19 brauner [] entry_SYSCALL_64_fastpath+0x1e/0xa8
21:19 brauner [] 0x
This looks like a potential kernel bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1645037/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706702] [NEW] Can't login after lock screen (black screen)
Public bug reported: After locking screen and as a result the monitor going into sleep mode, I can't get the login screen anymore, the monitor stays in sleep mode forever. In previous Ubuntu versions after pressing any key or the mouse, the login screen showed up, but not anymore. I have to do a Ctrl+Alt+Backspace ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: /dev/sdc5: clean, 307593/23363584 files, 5157711/93435648 blocks 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: Wed Jul 26 11:47:17 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK107GL [Quadro K2000] [10de:0ffe] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GL [Quadro K2000] [103c:094c] InstallationDate: Installed on 2017-07-17 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP Z620 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=5db25c2a-88a7-429c-9a7d-445e7694f7d6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.18 dmi.board.asset.tag: 2UA33318D4 dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: 2UA33318D4 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.18:bd07/01/2013:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z620 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jul 26 11:43:34 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB CAT5 KEYBOARD, id 8 inputUSB CAT5 MOUSE, id 9 inputHP WMI hotkeys KEYBOARD, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.2 xserver.video_driver: nouveau ** 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/1706702 Title: Can't login after lock screen (black screen) Status in xorg package in Ubuntu: New Bug description: After locking screen and as a result the monitor going into sleep mode, I can't get the login screen anymore, the monitor stays in sleep mode forever. In previous Ubuntu versions after pressing any key or the mouse, the login screen showed up, but not anymore. I have to do a Ctrl+Alt+Backspace ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: /dev/sdc5: clean, 307593/23363584 files, 5157711/93435648 blocks 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: Wed Jul 26 11:47:17 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Cor
[Touch-packages] [Bug 1706701] [NEW] Default Keyring is not unlocked for the user in Lubuntu
Public bug reported: Example scenario: 1. Go to the file manager (e.g. Nautilus, PCManFM) 2. Connect to a server via FTP 3. Enter the password and select "Remember forever" In Ubuntu, this is correctly placed into the Default Keyring, and remembered (even after a reboot) so that the password does not have to be retyped. But in Lubuntu, the Default Keyring is locked, and the user has to enter the account password to unlock it before it can be used by the system. • This must be done every time when attempting reconnection after reboot or after logging out and in again. • When this happens, even though the correct account password is entered, the first time, the FTP password is not retrieved. • If the Default Keyring is manually unlocked beforehand (e.g. via seahorse), the connection proceeds without hindrance. Anything that requires access to the Default Keyring within Lubuntu would be affected. This has been tested on Lubuntu 16.04 including a vanilla installation, on both PCManFM and Nautilus. Note that if Lubuntu is used by installing lubuntu-desktop over an Ubuntu 16.04 installation, this problem does not occur. Ubuntu Forums discussion: https://ubuntuforums.org/showthread.php?t=2367062 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnupg 1.4.20-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Jul 26 16:39:16 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-17 (38 days ago) InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnupg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnupg (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 gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1706701 Title: Default Keyring is not unlocked for the user in Lubuntu Status in gnupg package in Ubuntu: New Bug description: Example scenario: 1. Go to the file manager (e.g. Nautilus, PCManFM) 2. Connect to a server via FTP 3. Enter the password and select "Remember forever" In Ubuntu, this is correctly placed into the Default Keyring, and remembered (even after a reboot) so that the password does not have to be retyped. But in Lubuntu, the Default Keyring is locked, and the user has to enter the account password to unlock it before it can be used by the system. • This must be done every time when attempting reconnection after reboot or after logging out and in again. • When this happens, even though the correct account password is entered, the first time, the FTP password is not retrieved. • If the Default Keyring is manually unlocked beforehand (e.g. via seahorse), the connection proceeds without hindrance. Anything that requires access to the Default Keyring within Lubuntu would be affected. This has been tested on Lubuntu 16.04 including a vanilla installation, on both PCManFM and Nautilus. Note that if Lubuntu is used by installing lubuntu-desktop over an Ubuntu 16.04 installation, this problem does not occur. Ubuntu Forums discussion: https://ubuntuforums.org/showthread.php?t=2367062 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnupg 1.4.20-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Jul 26 16:39:16 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-17 (38 days ago) InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnupg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1706701/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705599] Re: GDM login screen is not Ubuntu-themed, it is grey and blue
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1705599 Title: GDM login screen is not Ubuntu-themed, it is grey and blue Status in gdm3 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: GDM login screen is not Ubuntu themed, it is grey and blue. In the least the blue should be something different like orange. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 Date: Fri Jul 21 09:45:57 2017 InstallationDate: Installed on 2017-05-03 (78 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-20T13:56:59.913179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706690] Re: Please sync openssl from debian stretch
Note: we will maybe *require* openssl 1.1.x for borgbackup 1.2 because of thread-safety and ciphers offered. For borg 1.2 *developers*, it would be nice to have openssl 1.1 in ubuntu ASAP. -- 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/1706690 Title: Please sync openssl from debian stretch Status in openssl package in Ubuntu: Confirmed Bug description: OpenSSL 1.1 contains major improvements over 1.0. https://packages.debian.org/stretch/openssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1706690/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706690] [NEW] Please sync openssl from debian stretch
Public bug reported: OpenSSL 1.1 contains major improvements over 1.0. https://packages.debian.org/stretch/openssl ** Affects: openssl (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: needs-packaging -- 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/1706690 Title: Please sync openssl from debian stretch Status in openssl package in Ubuntu: Confirmed Bug description: OpenSSL 1.1 contains major improvements over 1.0. https://packages.debian.org/stretch/openssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1706690/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706690] Re: Please sync openssl from debian stretch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssl (Ubuntu) Status: New => Confirmed -- 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/1706690 Title: Please sync openssl from debian stretch Status in openssl package in Ubuntu: Confirmed Bug description: OpenSSL 1.1 contains major improvements over 1.0. https://packages.debian.org/stretch/openssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1706690/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705599] Re: GDM login screen is not Ubuntu-themed, it is grey and blue
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1705599 Title: GDM login screen is not Ubuntu-themed, it is grey and blue Status in gdm3 package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: GDM login screen is not Ubuntu themed, it is grey and blue. In the least the blue should be something different like orange. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 Date: Fri Jul 21 09:45:57 2017 InstallationDate: Installed on 2017-05-03 (78 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-20T13:56:59.913179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706692] [NEW] Ha to clean RAM with thinner
Public bug reported: After cleaning ram it took a long time to start and after restarting shows long DOS like information and took a few more seconds to get normal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Wed Jul 26 20:27:44 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF119 [GeForce GT 610] [19da:6222] InstallationDate: Installed on 2017-07-16 (9 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=b40ad340-49e7-4bf6-852c-cc2dea3a5d6e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BEH6110H.86A.0016.2011.0118.1128 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61WW dmi.board.vendor: Intel Corporation dmi.board.version: AAG23116-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0016.2011.0118.1128:bd01/18/2011:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-203:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jul 26 20:25:16 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt Microsoft USB Optical Mouse MOUSE, id 8 inputDell KB216 Wired Keyboard KEYBOARD, id 9 inputDell KB216 Wired Keyboard KEYBOARD, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.2 xserver.video_driver: nouveau ** 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/1706692 Title: Ha to clean RAM with thinner Status in xorg package in Ubuntu: New Bug description: After cleaning ram it took a long time to start and after restarting shows long DOS like information and took a few more seconds to get normal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Wed Jul 26 20:27:44 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF119 [GeForce GT 610] [19da:6222] InstallationDate: Installed on 2017-07-16 (9 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=b40ad340-49e7-4bf6-852c-cc2dea3a5d6e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2011 dmi.bi
[Touch-packages] [Bug 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM
This bug was fixed in the package sudo - 1.8.19p1-1ubuntu1.2 --- sudo (1.8.19p1-1ubuntu1.2) zesty; urgency=medium * Terminate with the same signal as the command (LP: #1686803) This fixes a regression introduced in sudo 1.8.15 changeset 10229:153f016db8f1. -- Balint Reczey Tue, 13 Jun 2017 10:00:00 +0200 ** Changed in: sudo (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686803 Title: sudo returns exit code 0 if child is killed with SIGTERM Status in sudo: Unknown Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: Fix Released Status in sudo source package in Yakkety: Fix Committed Status in sudo source package in Zesty: Fix Released Status in sudo source package in Artful: Fix Released Bug description: [Impact] * sudo returns exit code 0 if child is killed with signals other than SIGINT * This can break scripts assuming successful execution of the command ran by sudo [Test Case] * Open two separate shells 1. In shell 1. run: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 2. In shell 2. run: root@tough-calf:~# killall -TERM sleep 3. In broken versions shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 0 4. Install fixed version 5. Execute steps 1. and 2. 6. In fixed version shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? Terminated 143 [Regression Potential] * sudo may exit with a different status than expected [Other Info] original bug description: Please backport upstream sudo changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" to xenial, yakkety, and zesty versions of sudo. This will fix a regression documented by this upstream bug report: https://bugzilla.sudo.ws/show_bug.cgi?id=784 sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is running is killed by a signal, sudo will" introduced a regression where the exit status is always 0 when a command is killed by a signal other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1 This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the". https://www.sudo.ws/repos/sudo/rev/50b988d0c97f trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty sudo based off 1.8.19 need the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1686803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686803] Update Released
The verification of the Stable Release Update for sudo 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 sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686803 Title: sudo returns exit code 0 if child is killed with SIGTERM Status in sudo: Unknown Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: Fix Released Status in sudo source package in Yakkety: Fix Committed Status in sudo source package in Zesty: Fix Released Status in sudo source package in Artful: Fix Released Bug description: [Impact] * sudo returns exit code 0 if child is killed with signals other than SIGINT * This can break scripts assuming successful execution of the command ran by sudo [Test Case] * Open two separate shells 1. In shell 1. run: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 2. In shell 2. run: root@tough-calf:~# killall -TERM sleep 3. In broken versions shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 0 4. Install fixed version 5. Execute steps 1. and 2. 6. In fixed version shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? Terminated 143 [Regression Potential] * sudo may exit with a different status than expected [Other Info] original bug description: Please backport upstream sudo changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" to xenial, yakkety, and zesty versions of sudo. This will fix a regression documented by this upstream bug report: https://bugzilla.sudo.ws/show_bug.cgi?id=784 sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is running is killed by a signal, sudo will" introduced a regression where the exit status is always 0 when a command is killed by a signal other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1 This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the". https://www.sudo.ws/repos/sudo/rev/50b988d0c97f trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty sudo based off 1.8.19 need the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1686803/+subscriptions -- Mailing list: https://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 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1
On 26 July 2017 at 10:18, Shahar Or wrote: > I do not seem to have the /etc/init.d/systemd-resolved symlink at all. > Is this normal? > Yes normal, Ubuntu only supports systemd as the init system, and /etc/init & /etc/init.d are not in use for most services. And, specifically, init.d scripts have never been used for systemd-resolved. -- Regards, Dimitri. -- 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/1685900 Title: On artful, no working dns after upgrading to systemd 233-5ubuntu1 Status in systemd package in Ubuntu: Invalid Bug description: After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got no nameserver (dns). This is very likely a DNS issue. As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS work fine. Or instead, I must manually start systemd-resolved: ~$ sudo service systemd-resolved restart So something odd has happened between these versions. Systemd-resolved is not starting automatically at boot anymore. My setup is a fully upgraded artful with proposed repo turned on. I use only Gnome DE with GDM. Everything else works fine, but not systemd 233-5ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM
This bug was fixed in the package sudo - 1.8.16-0ubuntu1.5 --- sudo (1.8.16-0ubuntu1.5) xenial; urgency=medium * Terminate with the same signal as the command (LP: #1686803) This fixes a regression introduced in sudo 1.8.15 changeset 10229:153f016db8f1. -- Balint Reczey Tue, 13 Jun 2017 11:10:50 +0200 ** Changed in: sudo (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 sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686803 Title: sudo returns exit code 0 if child is killed with SIGTERM Status in sudo: Unknown Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: Fix Released Status in sudo source package in Yakkety: Fix Committed Status in sudo source package in Zesty: Fix Released Status in sudo source package in Artful: Fix Released Bug description: [Impact] * sudo returns exit code 0 if child is killed with signals other than SIGINT * This can break scripts assuming successful execution of the command ran by sudo [Test Case] * Open two separate shells 1. In shell 1. run: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 2. In shell 2. run: root@tough-calf:~# killall -TERM sleep 3. In broken versions shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 0 4. Install fixed version 5. Execute steps 1. and 2. 6. In fixed version shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? Terminated 143 [Regression Potential] * sudo may exit with a different status than expected [Other Info] original bug description: Please backport upstream sudo changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" to xenial, yakkety, and zesty versions of sudo. This will fix a regression documented by this upstream bug report: https://bugzilla.sudo.ws/show_bug.cgi?id=784 sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is running is killed by a signal, sudo will" introduced a regression where the exit status is always 0 when a command is killed by a signal other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1 This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the". https://www.sudo.ws/repos/sudo/rev/50b988d0c97f trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty sudo based off 1.8.19 need the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1686803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
I tried to reproduce on my side using the reproducer explain in comment #98 and #99, and I couldn't reproduce it. @xnox Since foundation know how to fix it, can we try to fixing it blind for now ? Upload in xenial-proposed, and wait for users feedbacks ? If something goes wrong, we can still drop the code and set the bug to "verification-xenial-failed". Thoughts ? - Eric -- 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/1642966 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: Fix Released Status in cups source package in Xenial: Triaged Status in cups source package in Yakkety: Fix Released Status in cups source package in Zesty: Fix Released Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db 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: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Changed in: apt (Ubuntu) Status: New => Fix Committed -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1678606] Re: [packaging] Missing dnsmasq-base dependency causes wifi hotspot/network sharing feature broken
** Description changed: - In Ubuntu 17.04, the dnsmasq-tools dependency has been dropped from - network-manager, and the wifi network sharing feature failed to work - because of this: + Impact + === + In Ubuntu 17.04, the dnsmasq-base dependency has been dropped from network-manager, and the wifi network sharing feature failed to work because of this: NetworkManager[874]: [1491134643.1581] device (wlp3s0): share: (wlp3s0) failed to start dnsmasq: Could not find "dnsmasq" binary In my opinion it should at least in Recommends, refer following for related info: Bug #992411 “network-manager: Please don't Depend on dnsmasq-bas...” : Bugs : network-manager package : Ubuntu https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/992411 + + This recommends was dropped here: + https://launchpadlibrarian.net/279417634/network-manager_1.2.2-0ubuntu6_1.2.2-0ubuntu7.diff.gz + + Test Case + = + Install the update and ensure that dnsmasq-base is installed (it is a recommends so it should be pulled in automatically by this update). + + This test case requires a laptop (or desktop with Wi-Fi hardware) + running Ubuntu 17.04 with an ethernet connection to the Internet. + + Open a terminal and run journalctl -f + + Then open the Settings app (unity-control-center if running Unity, + gnome-control-center if running GNOME) and click the Network panel. + + Enable the Wi-Fi hotspot. + + Use another device to connect to the Wi-Fi hotspot with the Access Point + name and the password presented. Use the Internet on the other device. + + There should not be any warnings in the journal output in the terminal + about "could not find dnsmasq" + + Regression Potential + + + Other Info + == + This change was agreed upon by the Ubuntu Desktop Team and Martin Pitt who spearheaded the resolved transition for Ubuntu 17.04. + + https://irclogs.ubuntu.com/2017/07/25/%23ubuntu-desktop.html#t13:27 + (until 14:45) + + This drops a diff with Debian because Debian already recommends dnsmasq- + base. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Apr 2 20:28:25 2017 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2017-03-30 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) IpRoute: - default via 192.168.1.1 dev enp4s0f2 proto static metric 100 - 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 - 169.254.0.0/16 dev wlp3s0 scope link metric 1000 - 192.168.1.0/24 dev enp4s0f2 proto kernel scope link src 192.168.1.119 metric 100 + default via 192.168.1.1 dev enp4s0f2 proto static metric 100 + 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 + 169.254.0.0/16 dev wlp3s0 scope link metric 1000 + 192.168.1.0/24 dev enp4s0f2 proto kernel scope link src 192.168.1.119 metric 100 NetworkManager.conf: - [main] - plugins=ifupdown,keyfile - - [ifupdown] - managed=false + [main] + plugins=ifupdown,keyfile + + [ifupdown] + managed=false NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true ProcEnviron: - LANGUAGE=zh_TW:zh - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=zh_TW.UTF-8 - SHELL=/bin/bash + LANGUAGE=zh_TW:zh + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=zh_TW.UTF-8 + SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: - DEVICETYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH - enp4s0f2 ethernet connected /org/freedesktop/NetworkManager/Devices/1 由 DHCP 伺服器自動配發 IP 地址的網路 66cd739f-4bfd-4cbc-909f-1cd96e9ec8bb /org/freedesktop/NetworkManager/ActiveConnection/8 - wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/2 林博仁的模擬 Wi-Fi 網路 2547ce2c-a517-4d31-83a2-4bb38fc704cb /org/freedesktop/NetworkManager/ActiveConnection/14 - loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- + DEVICETYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH + enp4s0f2 ethernet connected /org/freedesktop/NetworkManager/Devices/1 由 DHCP 伺服器自動配發 IP
[Touch-packages] [Bug 1678606] Re: [packaging] Missing dnsmasq-base dependency causes wifi hotspot/network sharing feature broken
** Changed in: network-manager (Ubuntu) Status: Triaged => Fix Committed -- 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/1678606 Title: [packaging] Missing dnsmasq-base dependency causes wifi hotspot/network sharing feature broken Status in network-manager package in Ubuntu: Fix Committed Status in network-manager source package in Zesty: Triaged Bug description: In Ubuntu 17.04, the dnsmasq-tools dependency has been dropped from network-manager, and the wifi network sharing feature failed to work because of this: NetworkManager[874]: [1491134643.1581] device (wlp3s0): share: (wlp3s0) failed to start dnsmasq: Could not find "dnsmasq" binary In my opinion it should at least in Recommends, refer following for related info: Bug #992411 “network-manager: Please don't Depend on dnsmasq-bas...” : Bugs : network-manager package : Ubuntu https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/992411 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Apr 2 20:28:25 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-03-30 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) IpRoute: default via 192.168.1.1 dev enp4s0f2 proto static metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev enp4s0f2 proto kernel scope link src 192.168.1.119 metric 100 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f2 ethernet connected /org/freedesktop/NetworkManager/Devices/1 由 DHCP 伺服器自動配發 IP 地址的網路 66cd739f-4bfd-4cbc-909f-1cd96e9ec8bb /org/freedesktop/NetworkManager/ActiveConnection/8 wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/2 林博仁的模擬 Wi-Fi 網路 2547ce2c-a517-4d31-83a2-4bb38fc704cb /org/freedesktop/NetworkManager/ActiveConnection/14 loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1678606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1678606] Re: [packaging] Missing dnsmasq-base dependency causes wifi hotspot/network sharing feature broken
** Also affects: network-manager (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Zesty) Importance: Undecided => High ** Changed in: network-manager (Ubuntu Zesty) Status: New => Triaged -- 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/1678606 Title: [packaging] Missing dnsmasq-base dependency causes wifi hotspot/network sharing feature broken Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Zesty: Triaged Bug description: In Ubuntu 17.04, the dnsmasq-tools dependency has been dropped from network-manager, and the wifi network sharing feature failed to work because of this: NetworkManager[874]: [1491134643.1581] device (wlp3s0): share: (wlp3s0) failed to start dnsmasq: Could not find "dnsmasq" binary In my opinion it should at least in Recommends, refer following for related info: Bug #992411 “network-manager: Please don't Depend on dnsmasq-bas...” : Bugs : network-manager package : Ubuntu https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/992411 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Apr 2 20:28:25 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-03-30 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) IpRoute: default via 192.168.1.1 dev enp4s0f2 proto static metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev enp4s0f2 proto kernel scope link src 192.168.1.119 metric 100 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f2 ethernet connected /org/freedesktop/NetworkManager/Devices/1 由 DHCP 伺服器自動配發 IP 地址的網路 66cd739f-4bfd-4cbc-909f-1cd96e9ec8bb /org/freedesktop/NetworkManager/ActiveConnection/8 wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/2 林博仁的模擬 Wi-Fi 網路 2547ce2c-a517-4d31-83a2-4bb38fc704cb /org/freedesktop/NetworkManager/ActiveConnection/14 loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1678606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701780] Re: GTK file chooser shows entries from /sys, /dev, etc.
Thank you for your bug report. Could you add the output of the "mount" command as well? ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1701780 Title: GTK file chooser shows entries from /sys, /dev, etc. Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: On Kubuntu 17.10 Alpha 1, the GTK file chooser shows several unwanted entries from /sys, /dev, etc. For me, this occurs in the GTK3 file chooser opened from Firefox, GNOME Disks, etc. At the time of writing, I haven't tested whether it occurs in the GTK2 chooser as well. I have attached a screenshot showing the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706601] [NEW] Atstart up the bud appears But te program continous package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux
Public bug reported: At start up the bug appears. However the program continous ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so usr/share/doc/libssl1.0.0/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Jul 26 14:51:13 2017 ErrorMessage: pakket libssl1.0.0:amd64 is niet gereed voor configuratie kan het niet configureren (huidige status 'half-installed') InstallationDate: Installed on 2017-06-06 (49 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1706601 Title: Atstart up the bud appears But te program continous package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux- gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to install/upgrade: pakket libssl1.0.0:amd64 is niet gereed voor configuratie kan het niet configureren (huidige status 'half- installed') Status in openssl package in Ubuntu: New Bug description: At start up the bug appears. However the program continous ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so usr/share/doc/libssl1.0.0/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Jul 26 14:51:13 2017 ErrorMessage: pakket libssl1.0.0:amd64 is niet gereed voor configuratie kan het niet configureren (huidige status 'half-installed') InstallationDate: Installed on 2017-06-06 (49 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/u
[Touch-packages] [Bug 1706598] [NEW] Update bluez to 5.46 in artful
Public bug reported: The new bluez version is being packaged for artful ** Affects: bluez (Ubuntu) Importance: Low Status: In Progress ** Tags: upgrade-software-version ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Changed in: bluez (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1706598 Title: Update bluez to 5.46 in artful Status in bluez package in Ubuntu: In Progress Bug description: The new bluez version is being packaged for artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1706598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Fix Committed -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470075] Re: [address book] Fast scroll letters overlap RTL contacts
** Tags added: rtl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1470075 Title: [address book] Fast scroll letters overlap RTL contacts Status in Ubuntu UX: Fix Committed Status in address-book-app package in Ubuntu: Confirmed Bug description: Steps to reproduce 1) Add a contact with a Hebrew name 2) Scroll the contact list Expected result Contact name shouldn't be obscured Actual result Contact name is overlapped by the fast scroll letters (see attached screenshot) --- The placement of the text should be the same as the visual spec and read from right to left. But the text should not actually be placed on the right hand side of the page. Please see attached examples in the comments. So the layout should still follow the visual spec https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit#slide=id.g183c60488_058 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1470075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
