[Touch-packages] [Bug 1711483] Re: Crackling sound after resuming from suspend
Disregard, further testing in progress. ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1711483 Title: Crackling sound after resuming from suspend Status in pulseaudio package in Ubuntu: Invalid Bug description: PulseAudio exhibits abnormal behavior after resuming from suspend: Crackling sound present during HTML5 video playback in Chromium 60. I tried adding tsched=0 to load-module module-udev-detect in /etc/pulse/default.pa, and it didn't work. I slightly increased fragment number and size in /etc/pulse/daemon.conf, didn't work either. Before suspending, multiple sound sources can be handled without problems nor audible noise. After suspending machine, sound source is noisy/crackling, as if there were buffer underruns. $ lsb_release -rd Description: elementary OS 0.4.1 Loki (based on Ubuntu 16.04, official kernel 4.10.0-32-generic) Release: 0.4.1 $ apt-cache policy pulseaudio pulseaudio: Instalados: 1:8.0-0ubuntu3.3 Candidato: 1:8.0-0ubuntu3.3 Tabla de versión: *** 1:8.0-0ubuntu3.3 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:8.0-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: elementary 0.4.1 Package: pulseaudio 1:8.0-0ubuntu3.3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dmayr 10024 F pulseaudio /dev/snd/pcmC0D0p: dmayr 10024 F...m pulseaudio /dev/snd/controlC0: dmayr 10024 F pulseaudio CurrentDesktop: Pantheon Date: Thu Aug 17 22:57:28 2017 InstallationDate: Installed on 2017-06-01 (77 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924BV6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924BV6:pvrThinkPadT410s:rvnLENOVO:rn2924BV6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924BV6 dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-08-17T15:17:20.438064 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
Device = BCM43142 802.11b/g/n Manufacturer = Broadcom Limited Driver = wl0 Driverversion = 6.30.223.271 (r587334) I have this same problem with a build-in wifi I had to add: [Device] wifi.scan-rand-mac-address=no to NetworkManager.conf to make it work -- 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/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613050] Re: SAMBA Authentication fails with CUPS print job
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1613050 Title: SAMBA Authentication fails with CUPS print job Status in cups package in Ubuntu: Expired Status in samba package in Ubuntu: Expired Bug description: Print jobs fail to authenticate CUPS print jobs via an Active Directory joined system using pam_authenticate. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Aug 14 20:56:12 2016 InstallationDate: Installed on 2016-06-24 (51 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer Test: Ricoh Aficio MP C5502A , Postscript-Ricoh 20160606 (OpenPrinting LSB 3.2) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1613050/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613050] Re: SAMBA Authentication fails with CUPS print job
[Expired for samba (Ubuntu) because there has been no activity for 60 days.] ** Changed in: samba (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1613050 Title: SAMBA Authentication fails with CUPS print job Status in cups package in Ubuntu: Expired Status in samba package in Ubuntu: Expired Bug description: Print jobs fail to authenticate CUPS print jobs via an Active Directory joined system using pam_authenticate. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Aug 14 20:56:12 2016 InstallationDate: Installed on 2016-06-24 (51 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer Test: Ricoh Aficio MP C5502A , Postscript-Ricoh 20160606 (OpenPrinting LSB 3.2) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1613050/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694296] Re: package libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
[Expired for nspr (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nspr (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nspr in Ubuntu. https://bugs.launchpad.net/bugs/1694296 Title: package libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in nspr package in Ubuntu: Expired Bug description: Sempre estou tendo problemas para adicionar novos pacotes nao consigo reproduzir videos . Por favor gostaria de ajuda ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Mon May 29 12:05:30 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2 libgcc1 1:6.3.0-12ubuntu2 DuplicateSignature: package:libnspr4:amd64:2:4.13.1-0ubuntu0.17.04.1 Processing triggers for update-notifier-common (3.179) ... ttf-mscorefonts-installer: processing... dpkg: error processing package libnspr4: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-05-06 (23 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: nspr Title: package libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.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/nspr/+bug/1694296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698704] Re: NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/zesty
[Expired for python-apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: python-apt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1698704 Title: NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/zesty Status in python-apt package in Ubuntu: Expired Bug description: I'm trying to get GCC 7 on a machine to test C++17 and std::byte. According to https://askubuntu.com/questions/859256/how-to-install- gcc-7-or-clang-4-0: $ sudo add-apt-repository ppa:ubuntu-toolchain-r/test Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 95, in sp = SoftwareProperties(options=options) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 114, in __init__ self.reload_sourceslist() File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 607, in reload_sourceslist self.distro.get_sources(self.sourceslist) File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 89, in get_sources (self.id, self.codename)) aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/zesty ** $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Zesty Zapus (development branch) Release:17.04 Codename: zesty $ uname -a Linux goldmont 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1698704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576341] Re: systemd in degraded state on startup in LXD containers
I assume the failures in comment #37 for nfs-common were also caused by systemd failing to set the Nice priority. ** No longer affects: nfs-utils (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 open-iscsi package in Ubuntu: Fix Released 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 1576341] Re: systemd in degraded state on startup in LXD containers
With a fully updated daily image (lxc launch ubuntu-daily:artful; lxc exec apt update; lxc exec apt full-upgrade; lxc exec reboot; lxc exec systemctl status): State: running Jobs: 0 queued Failed: 0 units Nice work everyone! Now, ideally, any package that shows up in the container image by default is checked that this doesn't regress going forward :) ** Changed in: lvm2 (Ubuntu) Assignee: Nish Aravamudan (nacc) => (unassigned) ** Changed in: open-iscsi (Ubuntu) Assignee: Nish Aravamudan (nacc) => (unassigned) -- 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 Released 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 1576341] Re: systemd in degraded state on startup in LXD containers
This bug was fixed in the systemd with 234-2ubuntu6 - Ignore failures to set Nice priority on services in containers. --- systemd (234-2ubuntu2) artful; urgency=medium * Ignore failures to set Nice priority on services in containers. * Disable execute test on armhf. * units: set ConditionVirtualization=!private-users on journald audit socket. It fails to start in unprivileged containers. * boot-smoke: refactor ADT test. Wait for system to settle down and get to either running or degraded state, then collect all metrics, and exit with an error if any of the tests failed. -- Dimitri John Ledkov Wed, 02 Aug 2017 03:02:03 +0100 -- 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 Released 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 1576341] Re: systemd in degraded state on startup in LXD containers
open-iscsi (2.0.874-4ubuntu1) artful; urgency=medium * Merge with Debian unstable. Remaining changes: - debian/tests: Add Ubuntu autopkgtests. - debian/iscsi-network-interface.rules, debian/net-interface-handler, debian/open-iscsi.install: Prevent network interface that contains iscsi root from bouncing during boot or going down during shutdown. Integrates with resolvconf and initramfs code that writes /run/initramfs/open-iscsi.interface - debian/open-iscsi.maintscript: clean up the obsolete iscsi-network-interface upstart job, file on upgrade. - Let iscsid systemd job run in privileged containers but not in unprivileged ones - Start open-iscsi systemd job when either /etc/iscsi/nodes or /sys/class/iscsi_session have content Based on patch by Nish Aravamudan, thanks! (LP #1576341) - add IPv6 support + add support for IPV6{DOMAINSEARCH,DNS0,DNS1} to net-interface-handler LP #1621507 + Source /run/net6-*.conf when needed. + debian/extra/initramfs.local-top: handle IPv6 configs being shipped in DEVICE6 or /run/net6-*.conf in the initramfs, so we can fill in /run/initramfs/open-iscsi.interface (LP #1621507) * Drop: - d/extra/initramfs.local-top: When booting from iBFT, set the PROTO= entry in /run/net-*.conf accordingly, so that other tools, such as cloud-init, can use that information. (cloud-init fails if the current PROTO=none is used.) (LP: #1684039) (Closes: #866213) [ Fixed in Debian 2.0.874-4 ] * d/t/test-open-iscsi.py: drop test_daemon test - With the updates to the systemd units, the services do not run unless iSCSI is configured. -- Nishanth Aravamudan Tue, 08 Aug 2017 16:16:27 -0700 ** Changed in: open-iscsi (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 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 Released 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 1711768] [NEW] Gnome shell menu extensions won't install on 17.10
Public bug reported: Description:Ubuntu Artful Aardvark (development branch) Release:17.10 On a fresh install of 17.10 application menu extensions (Gno-Menu, Arc Menu etc) will not install from extensions.gnome.org "gir1.2-gmenu-3.0" and "libgnome-menu-3-0" should be included in the standard meta package for menu extensions to work. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- 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/1711768 Title: Gnome shell menu extensions won't install on 17.10 Status in ubuntu-meta package in Ubuntu: New Bug description: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 On a fresh install of 17.10 application menu extensions (Gno-Menu, Arc Menu etc) will not install from extensions.gnome.org "gir1.2-gmenu-3.0" and "libgnome-menu-3-0" should be included in the standard meta package for menu extensions to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1711768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711760] [NEW] [2.3] resolv.conf is not set (during commissioning)
Public bug reported: Using MAAS 2.3, during commissioning (and likely in the rest of the ephemeral environment) we have noticed that resolv.conf is not set with the DNS server. That said, during the commissioning process, MAAS does not send any metadata to cloud-init to configure the network, rather, we expect the image to boot from the network via DHCP. So, cloud-init writes: ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} auto lo iface lo inet loopback # control-manual ens3 iface ens3 inet dhcp broadcast 192.168.122.255 dns-nameservers 192.168.122.2 gateway 192.168.122.1 netmask 255.255.255.0 Which correctly includes the DNS server. However: ubuntu@manual:~$ ping google.com ping: unknown host google.com If restart the interfacE: ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3 ifdown: interface ens3 not configured Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/ens3/52:54:00:ea:57:31 Sending on LPF/ens3/52:54:00:ea:57:31 Sending on Socket/fallback DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354) DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354) DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 (xid=0x5403eb14) DHCPOFFER of 192.168.122.195 from 192.168.122.2 DHCPACK of 192.168.122.195 from 192.168.122.2 Restarting ntp (via systemctl): ntp.service. bound to 192.168.122.195 -- renewal in 290 seconds. ubuntu@manual:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.122.2 search maas ubuntu@manual:~$ ping google.com PING google.com (216.58.192.46) 56(84) bytes of data. 64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1 ttl=52 time=7.47 ms ^C --- google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 7.472/7.472/7.472/0.000 ms As such, this either seems like a bug in Ubuntu, or caused by cloud-init when writing e/n/i.d/50-cloud-init.cfg ubuntu@manual:~$ dpkg -l | grep cloud-init ii cloud-init 0.7.9-153-g16a7302f-0ubuntu1~16.04.2 all Init scripts for cloud instances ii cloud-initramfs-copymods 0.27ubuntu1.4 all copy initramfs modules into root filesystem for later use ii cloud-initramfs-dyn-netconf 0.27ubuntu1.4 all write a network interface file in /run for BOOTIF ubuntu@manual:~$ uname -a Linux manual 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ubuntu@manual:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial ubuntu@manual:~$ pastebinit /var/log/cloud-init.log http://paste.ubuntu.com/25342738/ ubuntu@manual:~$ pastebinit /var/log/cloud-init-output.log http://paste.ubuntu.com/25342740/ ** Affects: maas Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Description changed: Using MAAS 2.3, during commissioning (and likely in the rest of the ephemeral environment) we have noticed that resolv.conf is not set with the DNS server. That said, during the commissioning process, MAAS does not send any metadata to cloud-init to configure the network, rather, we expect the image to boot from the network via DHCP. So, cloud-init writes: - ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg + ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} auto lo iface lo inet loopback # control-manual ens3 iface ens3 inet dhcp - broadcast 192.168.122.255 - dns-nameservers 192.168.122.2 - gateway 192.168.122.1 - netmask 255.255.255.0 + broadcast 192.168.122.255 + dns-nameservers 192.168.122.2 + gateway 192.168.122.1 + netmask 255.255.255.0 Which correctly includes the DNS server. However: ubuntu@manual:~$ ping goo
[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
The patch has been uploaded in the xenial upload queue. It is now waiting for the SRU verification team approval for the CUPS derived binary packages to start building in xenial-proposed and re- enter in the users test phase. - 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: In Progress 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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Here's a debdiff[1] that I have tested and mitigate the situation with the reproducer using VirtualBox. The proposal patch integrate a custom "debian/cups-daemon.prerm" maintainer script in case the pre-removal "old-version" from the installed package fails (as seen using the above reproducer) and then switch to the pre-removal script from the "new version" from the package to-be install in order to stop cups.socket and cups.path indivually before #DEBHELPER#. [1] debdiff: lp1642966_xenial.debdiff - Eric ** Patch added: "lp1642966_xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+attachment/4934958/+files/lp1642966_xenial.debdiff ** Changed in: cups (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: cups (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) ** Tags removed: verification-done-xenial ** Tags added: regression-proposed -- 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: In Progress 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 189617] Re: policykit integration missing
This bug was fixed in the package gdebi - 0.9.5.7+nmu1ubuntu1 --- gdebi (0.9.5.7+nmu1ubuntu1) artful; urgency=medium * Add a gdebi-gtk-pkexec executable to launch without gksu (LP: #189617). * debian/control: - Make gdebi depends on policykit-1 | gksu. -- Julien Lavergne Fri, 18 Aug 2017 22:45:38 +0200 ** Changed in: gdebi (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 gdebi in Ubuntu. https://bugs.launchpad.net/bugs/189617 Title: policykit integration missing Status in gdebi package in Ubuntu: Fix Released Status in gdebi package in Debian: New Bug description: Binary package hint: gdebi this package is missing policykit bindings version 0.3.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/189617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576341] Re: systemd in degraded state on startup in LXD containers
This bug was fixed in the package systemd - 234-2ubuntu6 --- systemd (234-2ubuntu6) artful; urgency=medium * Disable KillUserProcesses, yet again, with meson this time. * Re-enable reboot tests. -- Dimitri John Ledkov Thu, 17 Aug 2017 15:22:35 +0100 ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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 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 1708051] Re: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances
This bug was fixed in the package systemd - 234-2ubuntu6 --- systemd (234-2ubuntu6) artful; urgency=medium * Disable KillUserProcesses, yet again, with meson this time. * Re-enable reboot tests. -- Dimitri John Ledkov Thu, 17 Aug 2017 15:22:35 +0100 ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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/1708051 Title: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances Status in systemd package in Ubuntu: Fix Released Bug description: ppc64el is fine. Given that everything is fixed to start containers and vms non- degraded, let's enforce that we boot not degraded. Also network online timeout is 30s, thus it makes no sense to only give the boot 10s. Especially since machines can be overcommitted with capacity. update: tests were improved somewhat, to be more deterministic and always wait for the boot to fully finish before rebooting. On the infrastructure - all but i386/amd64 pass. But locally it is not reproducible. It almost feels like openstack-nova-autopkgtest-reboot- marker integration is broken; or systemd fails to reboot in scalingstack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1708051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1265418] Re: Gtk3 bookmark can't be removed if it points to a file
** Changed in: gtk Status: Unknown => Confirmed ** Changed in: gtk Importance: Unknown => Medium -- 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/1265418 Title: Gtk3 bookmark can't be removed if it points to a file Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: In the file requestor of Gtk3 you can drag files and directories to the sidebar to create bookmarks. If the user drags a file here the bookmark can never be deleted because the option is disabled. To reproduce: 1. Open a Gtk3 application such as firefox, gedit etc. 2. Open the File Open requester. 3. Drag a file to the bookmarks. 4. Right click on the file bookmark. Expected result: Should be able to click on "Remove" to remove the bookmark. Actual result: The remove option is always disabled. Workaround: Edit ~/.config/gtk-3.0/bookmarks and delete the bookmark line. Also affects trusty. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk-3-0 3.8.6-0ubuntu3.1 Uname: Linux 3.11.0-031100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Jan 2 02:49:04 2014 InstallationDate: Installed on 2013-08-27 (127 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827) MarkForUpload: True SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1265418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711483] Re: Crackling sound after resuming from suspend
I checked in Firefox 55, which routes all audio via PulseAudio, and sound is perfect. There may be a problem between chromium-browser and pulseaudio. ** Description changed: PulseAudio exhibits abnormal behavior after resuming from suspend: - Crackling sound present during HTML5 video playback in browsers (Chromium, Firefox, Chrome). + Crackling sound present during HTML5 video playback in Chromium 60. I tried adding tsched=0 to load-module module-udev-detect in /etc/pulse/default.pa, and it didn't work. I slightly increased fragment number and size in /etc/pulse/daemon.conf, didn't work either. Before suspending, multiple sound sources can be handled without problems nor audible noise. After suspending machine, sound source is noisy/crackling, as if there were buffer underruns. - - $ lsb_release -rd + $ lsb_release -rd Description: elementary OS 0.4.1 Loki (based on Ubuntu 16.04, official kernel 4.10.0-32-generic) Release: 0.4.1 $ apt-cache policy pulseaudio pulseaudio: - Instalados: 1:8.0-0ubuntu3.3 - Candidato: 1:8.0-0ubuntu3.3 - Tabla de versión: - *** 1:8.0-0ubuntu3.3 500 - 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1:8.0-0ubuntu3 500 - 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages + Instalados: 1:8.0-0ubuntu3.3 + Candidato: 1:8.0-0ubuntu3.3 + Tabla de versión: + *** 1:8.0-0ubuntu3.3 500 + 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1:8.0-0ubuntu3 500 + 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: elementary 0.4.1 Package: pulseaudio 1:8.0-0ubuntu3.3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: dmayr 10024 F pulseaudio - /dev/snd/pcmC0D0p: dmayr 10024 F...m pulseaudio - /dev/snd/controlC0: dmayr 10024 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: dmayr 10024 F pulseaudio + /dev/snd/pcmC0D0p: dmayr 10024 F...m pulseaudio + /dev/snd/controlC0: dmayr 10024 F pulseaudio CurrentDesktop: Pantheon Date: Thu Aug 17 22:57:28 2017 InstallationDate: Installed on 2017-06-01 (77 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924BV6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924BV6:pvrThinkPadT410s:rvnLENOVO:rn2924BV6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924BV6 dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-08-17T15:17:20.438064 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1711483 Title: Crackling sound after resuming from suspend Status in pulseaudio package in Ubuntu: New Bug description: PulseAudio exhibits abnormal behavior after resuming from suspend: Crackling sound present during HTML5 video playback in Chromium 60. I tried adding tsched=0 to load-module module-udev-detect in /etc/pulse/default.pa, and it didn't work. I slightly increased fragment number and size in /etc/pulse/daemon.conf, didn't work either. Before suspending, multiple sound sources can be handled without problems nor audible noise. After suspending machine, sound source is noisy/crackling, as if there were buffer underruns. $ lsb_release -rd Description: elementary OS 0.4.1 Loki (based on Ubuntu 16.04, official kernel 4.10.0-32-generic) Release: 0.4.1 $ apt-cache policy pulseaudio pulseaudio: Instalados: 1:8.0-0ubuntu3.3 Candidato: 1:8.0-0ubuntu3.3 Tabla de versión: *** 1:8.0-0ubuntu3.3 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:8.0-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: elementary 0.4.1 Package: pulseaudio 1:8.0-0ubuntu3.3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: L
[Touch-packages] [Bug 1417370] Re: Qt 5 uses grayscale instead of subpixel font antialiasing
@Alex what release of Ubuntu Budgie are you running? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1417370 Title: Qt 5 uses grayscale instead of subpixel font antialiasing Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: Qt 5 applications like Qt Creator or the Ubuntu web browser (webbrowser-app) use grayscale font antialiasing. GTK 3, GTK 2, and Qt 4 use subpixel antialiasing as expected, so fonts in Qt 5 look weird. Attached screenshot shows an example of the problem. This upstream bug report might be related: https://bugreports.qt.io/browse/QTBUG-36445 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libqt5gui5 5.2.1+dfsg-1ubuntu14.2 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 2 19:35:10 2015 InstallationDate: Installed on 2014-08-30 (156 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1417370/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 189617] Re: policykit integration missing
uploaded. ** Changed in: gdebi (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/189617 Title: policykit integration missing Status in gdebi package in Ubuntu: Fix Committed Status in gdebi package in Debian: New Bug description: Binary package hint: gdebi this package is missing policykit bindings version 0.3.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/189617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1265418] Re: Gtk3 bookmark can't be removed if it points to a file
Just because the upstream report was marked as a duplicate, does not mean it is invalid. ** Bug watch added: GNOME Bug Tracker #762252 https://bugzilla.gnome.org/show_bug.cgi?id=762252 ** Changed in: gtk Importance: Medium => Unknown ** Changed in: gtk Status: Invalid => Unknown ** Changed in: gtk Remote watch: GNOME Bug Tracker #721321 => GNOME Bug Tracker #762252 -- 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/1265418 Title: Gtk3 bookmark can't be removed if it points to a file Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Triaged Bug description: In the file requestor of Gtk3 you can drag files and directories to the sidebar to create bookmarks. If the user drags a file here the bookmark can never be deleted because the option is disabled. To reproduce: 1. Open a Gtk3 application such as firefox, gedit etc. 2. Open the File Open requester. 3. Drag a file to the bookmarks. 4. Right click on the file bookmark. Expected result: Should be able to click on "Remove" to remove the bookmark. Actual result: The remove option is always disabled. Workaround: Edit ~/.config/gtk-3.0/bookmarks and delete the bookmark line. Also affects trusty. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk-3-0 3.8.6-0ubuntu3.1 Uname: Linux 3.11.0-031100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Jan 2 02:49:04 2014 InstallationDate: Installed on 2013-08-27 (127 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827) MarkForUpload: True SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1265418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709193] Re: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer
The trusty-proposed version (2.12.23-12ubuntu2.9) doesn't work and introduces a regression preventing successful TLS/SSL connections. I'll check if there is an easy fix for gnutls26. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnutls26 in Ubuntu. https://bugs.launchpad.net/bugs/1709193 Title: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer Status in gnutls26 package in Ubuntu: Invalid Status in gnutls28 package in Ubuntu: Fix Released Status in gnutls26 source package in Trusty: Fix Committed Status in gnutls28 source package in Trusty: Won't Fix Status in ssmtp source package in Trusty: Invalid Status in gnutls26 source package in Xenial: Invalid Status in gnutls28 source package in Xenial: Fix Committed Status in ssmtp source package in Xenial: Invalid Status in gnutls26 source package in Zesty: Invalid Status in gnutls28 source package in Zesty: Fix Committed Status in ssmtp source package in Zesty: Invalid Status in gnutls26 source package in Artful: Invalid Status in gnutls28 source package in Artful: Fix Released Status in ssmtp source package in Artful: Invalid Status in gnutls28 package in Debian: Fix Released Bug description: [Impact] Applications using GnuTLS OpenSSL compat layer [1] are be unable to use modern TLS versions (1.1 and 1.2) when relying on the SSLv23_{client,server}_method functions. There is an industry-wide push to use modern TLS versions, see [2] and [3] for example. The proposed fix changes the compat layer to use GnuTLS' "NORMAL" priority [4] instead of hard-coding which protocol versions and ciphers to enable. [Test Case] 1) Setup a mail submission server that uses StartTLS 2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay through the mail relay using StartTLS 3) Send an email while capturing with tcpdump/tshark 4) Inspect the submission connection (TCP/587) and look for the protocol version negotiated by the client. Without the fix, you should see TLSv1.0. With the fix, it should be TLSv1.2. Please see the original issue description for more details. [Regression Potential] Regression risk should be low since it's a backport of a simple fix that landed in Debian in April 2017. [References] 1: $ apt-cache rdepends libgnutls-openssl27 libgnutls-openssl27 Reverse Depends: libgnutls-dev libgnutls-dev zoneminder yaskkserv tf5 ssmtp snowdrop sngrep slrnpull slrn sipsak macopix-gtk2 gnss-sdr gkrellm freewheeling boinctui iputils-ping 2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html 3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls 4: https://gnutls.org/manual/html_node/Priority-Strings.html [Original issue description] sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with it. Here's a packet capture when ssmtp connects to smtp.sdeziel.info:587 that offers TLSv1.0 and higher: $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)' Version: TLS 1.0 (0x0301) Handshake Protocol: Client Hello Version: TLS 1.0 (0x0301) Cipher Suites Length: 30 Cipher Suites (15 suites) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041) Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084) Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045) Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088) Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016) Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032) Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038) Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0044) Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0087) Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013) I would expect ssmtp to use TLSv1.2 and a recent cipher like the openssl s_client is able to do: $ echo | openssl s_client -connect smtp.sdeziel.info:587 -starttls smtp 2>/dev/null | grep -E '^[[:space:]]+(Protocol|Cipher)' Protocol : TLSv1.2 Cipher: ECDHE-RSA-AES128-GCM-SHA256 Additional information: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ apt-cache policy ssmtp libg
[Touch-packages] [Bug 1681528] Re: Include information about python versions
** Branch linked: lp:~ubuntu-core-dev/ubuntu/artful/apport/ubuntu -- 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/1681528 Title: Include information about python versions Status in apport package in Ubuntu: In Progress Status in apport source package in Artful: In Progress Bug description: We are see lots of package installation failures that look like: package:apport:2.20.3-0ubuntu8 Preparing to unpack .../023-apport_2.20.3-0ubuntu8.2_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax One explanation for this is that pyclean is actually be run by python3 instead of python2.7. To confirm and invalidate reports like this apport should check to see what /usr/bin/python and /usr/bin/python3 are symlinks to or double check the versions of /usr/bin/python and /usr/bin/python3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1681528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681528] Re: Include information about python versions
** Changed in: apport (Ubuntu Artful) Status: New => In Progress -- 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/1681528 Title: Include information about python versions Status in apport package in Ubuntu: In Progress Status in apport source package in Artful: In Progress Bug description: We are see lots of package installation failures that look like: package:apport:2.20.3-0ubuntu8 Preparing to unpack .../023-apport_2.20.3-0ubuntu8.2_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax One explanation for this is that pyclean is actually be run by python3 instead of python2.7. To confirm and invalidate reports like this apport should check to see what /usr/bin/python and /usr/bin/python3 are symlinks to or double check the versions of /usr/bin/python and /usr/bin/python3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1681528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709193] Re: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer
Verified on Zesty with: $ apt-cache policy libgnutls-openssl27:amd64 libgnutls-openssl27: Installed: 3.5.6-4ubuntu4.2 Candidate: 3.5.6-4ubuntu4.2 Version table: *** 3.5.6-4ubuntu4.2 500 500 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.5.6-4ubuntu4.1 500 500 http://archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages 3.5.6-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages ** Tags removed: verification-done-xenial verification-needed-zesty ** Tags added: verification-done-zesty verification-needed-xenial ** Tags removed: verification-needed-trusty verification-needed-xenial ** Tags added: verification-done-xenial verification-failed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnutls26 in Ubuntu. https://bugs.launchpad.net/bugs/1709193 Title: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer Status in gnutls26 package in Ubuntu: Invalid Status in gnutls28 package in Ubuntu: Fix Released Status in gnutls26 source package in Trusty: Fix Committed Status in gnutls28 source package in Trusty: Won't Fix Status in ssmtp source package in Trusty: Invalid Status in gnutls26 source package in Xenial: Invalid Status in gnutls28 source package in Xenial: Fix Committed Status in ssmtp source package in Xenial: Invalid Status in gnutls26 source package in Zesty: Invalid Status in gnutls28 source package in Zesty: Fix Committed Status in ssmtp source package in Zesty: Invalid Status in gnutls26 source package in Artful: Invalid Status in gnutls28 source package in Artful: Fix Released Status in ssmtp source package in Artful: Invalid Status in gnutls28 package in Debian: Fix Released Bug description: [Impact] Applications using GnuTLS OpenSSL compat layer [1] are be unable to use modern TLS versions (1.1 and 1.2) when relying on the SSLv23_{client,server}_method functions. There is an industry-wide push to use modern TLS versions, see [2] and [3] for example. The proposed fix changes the compat layer to use GnuTLS' "NORMAL" priority [4] instead of hard-coding which protocol versions and ciphers to enable. [Test Case] 1) Setup a mail submission server that uses StartTLS 2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay through the mail relay using StartTLS 3) Send an email while capturing with tcpdump/tshark 4) Inspect the submission connection (TCP/587) and look for the protocol version negotiated by the client. Without the fix, you should see TLSv1.0. With the fix, it should be TLSv1.2. Please see the original issue description for more details. [Regression Potential] Regression risk should be low since it's a backport of a simple fix that landed in Debian in April 2017. [References] 1: $ apt-cache rdepends libgnutls-openssl27 libgnutls-openssl27 Reverse Depends: libgnutls-dev libgnutls-dev zoneminder yaskkserv tf5 ssmtp snowdrop sngrep slrnpull slrn sipsak macopix-gtk2 gnss-sdr gkrellm freewheeling boinctui iputils-ping 2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html 3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls 4: https://gnutls.org/manual/html_node/Priority-Strings.html [Original issue description] sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with it. Here's a packet capture when ssmtp connects to smtp.sdeziel.info:587 that offers TLSv1.0 and higher: $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)' Version: TLS 1.0 (0x0301) Handshake Protocol: Client Hello Version: TLS 1.0 (0x0301) Cipher Suites Length: 30 Cipher Suites (15 suites) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041) Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084) Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045) Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088) Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016) Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032) Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0
[Touch-packages] [Bug 1681528] Re: Include information about python versions
The python information will be gathered under the following conditions: 57 if report.get('ProblemType') == 'Package' or \ 58 'python' in report.get('InterpreterPath', '') or \ 59 'python' in report.get('ExecutablePath', ''): One way to test the 'Package' type of problem is to use the crash-in- postinst package from the daisy pluckers PPA. https://launchpad.net/~daisy-pluckers/+archive/daisy-seeds It is not enough to use 'dpkg -i' to trigger the crash though. -- 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/1681528 Title: Include information about python versions Status in apport package in Ubuntu: New Status in apport source package in Artful: New Bug description: We are see lots of package installation failures that look like: package:apport:2.20.3-0ubuntu8 Preparing to unpack .../023-apport_2.20.3-0ubuntu8.2_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax One explanation for this is that pyclean is actually be run by python3 instead of python2.7. To confirm and invalidate reports like this apport should check to see what /usr/bin/python and /usr/bin/python3 are symlinks to or double check the versions of /usr/bin/python and /usr/bin/python3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1681528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710995] Re: mythbuntu 16.04 install - whoopsie not online
Restarting networking does not bring whoopsie online. $ sudo systemctl restart networking $ sudo systemctl status whoopsie ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Fr 2017-08-18 19:16:28 CEST; 56min ago Main PID: 1320 (whoopsie) CGroup: /system.slice/whoopsie.service └─1320 /usr/bin/whoopsie -f Aug 18 20:04:57 obelix whoopsie[1320]: [20:04:57] Cannot reach: https://daisy.ubuntu.com Aug 18 20:04:57 obelix whoopsie[1320]: [20:04:57] Cannot reach: https://daisy.ubuntu.com Aug 18 20:05:55 obelix whoopsie[1320]: [20:05:55] Cannot reach: https://daisy.ubuntu.com Aug 18 20:07:58 obelix whoopsie[1320]: [20:07:58] Not online; processing later (/var/crash/_lib_systemd_systemd-udevd.0.crash). Aug 18 20:10:25 obelix whoopsie[1320]: [20:10:25] Cannot reach: https://daisy.ubuntu.com Aug 18 20:10:25 obelix whoopsie[1320]: [20:10:25] Cannot reach: https://daisy.ubuntu.com Aug 18 20:10:25 obelix whoopsie[1320]: [20:10:25] Cannot reach: https://daisy.ubuntu.com Aug 18 20:10:26 obelix whoopsie[1320]: [20:10:26] Cannot reach: https://daisy.ubuntu.com Aug 18 20:10:27 obelix whoopsie[1320]: [20:10:27] Cannot reach: https://daisy.ubuntu.com Aug 18 20:10:27 obelix whoopsie[1320]: [20:10:27] Cannot reach: https://daisy.ubuntu.com -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: mythbuntu 16.04 install - whoopsie not online Status in whoopsie package in Ubuntu: Confirmed Bug description: Reporting crashes from /var/crash/* is not possible any more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.5 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashReports: 640:1000:139:81264064:2017-08-12 10:41:39.397392016 +0200:2017-08-16 00:23:25.391175383 +0200:/var/crash/_usr_bin_mythwelcome.1000.crash 640:0:139:936170:2017-08-12 17:56:15.728615283 +0200:2017-08-16 00:34:15.013084038 +0200:/var/crash/_lib_systemd_systemd-udevd.0.crash 640:1000:139:1194610:2017-08-11 17:52:56.113431094 +0200:2017-08-11 17:55:44.737433966 +0200:/var/crash/_usr_bin_xfce4-power-manager.1000.crash 640:1000:139:60309601:2017-08-16 00:18:13.511184669 +0200:2017-08-16 00:18:13.515184669 +0200:/var/crash/_usr_lib_x86_64-linux-gnu_kodi_kodi.bin.1000.crash Date: Wed Aug 16 00:37:18 2017 RelatedPackageVersions: apport-noui 2.20.1-0ubuntu2.10 SourcePackage: whoopsie UpgradeStatus: Upgraded to xenial on 2016-08-06 (374 days ago) --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: whoopsie 0.2.52.5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 RelatedPackageVersions: apport-noui N/A Tags: xenial autoreport-false Uname: Linux 4.10.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-08-06 (374 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin mythtv netdev plugdev sambashare scanner tape vboxusers video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711667] Re: no xorg.conf after nvidia driver installation
I don't think that's a bug, you need to switch to nvidia via the gui ** Package changed: xorg (Ubuntu) => nvidia-prime (Ubuntu) ** Changed in: nvidia-prime (Ubuntu) Status: New => Invalid -- 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/1711667 Title: no xorg.conf after nvidia driver installation Status in nvidia-prime package in Ubuntu: Invalid Bug description: no any config file about graphics system: Ubuntu 17.04 64bit, latest drivers the machine is laptop Asus i7 with Intel Graphics integrated and second card nVidia GT740m ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 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: Fri Aug 18 16:33:30 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-30-generic, x86_64: installed bbswitch, 0.8, 4.10.0-32-generic, x86_64: installed nvidia-384, 384.59, 4.10.0-32-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:122d] Subsystem: ASUSTeK Computer Inc. GK208M [GeForce GT 740M] [1043:122d] InstallationDate: Installed on 2017-05-11 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. X750JB ProcEnviron: LANGUAGE=pl PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=bf9a973b-54f4-401b-9341-a587fcaf877c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X750JB.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X750JB 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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X750JB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Thu Aug 17 14:17:54 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1711667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather
2017-08-18 - Ubuntu Gnome 17.04 - meteo mix franche and english. Exemple : "Broken clouds, puis Drizzle, suivi par Overcast plus tard. Température ressentie : 22,0°C" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in Ubuntu Translations: New Status in gnome-weather package in Ubuntu: In Progress Status in libgweather package in Ubuntu: Confirmed Bug description: In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1704533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711718] [NEW] bluez
Public bug reported: Aug 19 00:50:32 lee-H55M-D2H gnome-system-lo[7025]: Allocating size to GtkScrolledWindow 0x17024f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Aug 19 00:51:35 lee-H55M-D2H bluetooth-sendt[7042]: GtkDialog mapped without a transient parent. This is discouraged. Aug 19 00:51:35 lee-H55M-D2H dbus[928]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Aug 19 00:51:35 lee-H55M-D2H systemd[1]: Starting Hostname Service... Aug 19 00:51:35 lee-H55M-D2H dbus[928]: [system] Successfully activated service 'org.freedesktop.hostname1' Aug 19 00:51:35 lee-H55M-D2H systemd[1]: Started Hostname Service. Aug 19 00:51:38 lee-H55M-D2H dbus-daemon[1558]: Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' Aug 19 00:51:38 lee-H55M-D2H dbus-daemon[1558]: Activation via systemd failed for unit 'dbus-org.bluez.obex.service': Unit dbus-org.bluez.obex.service not found. Aug 19 00:51:38 lee-H55M-D2H indicator-bluetooth-service[1773]: Acquiring proxy failed: 为 org.bluez.obex 调用 StartServiceByName 出错: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.obex.service not found. Aug 19 00:51:38 lee-H55M-D2H unity-panel-ser[1930]: menus_destroyed: assertion 'IS_WINDOW_MENU(wm)' failed ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 BootLog: CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Aug 19 00:45:52 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-30-generic, x86_64: installed bbswitch, 0.8, 4.10.0-32-generic, x86_64: installed nvidia-375, 375.66, 4.10.0-30-generic, x86_64: installed nvidia-375, 375.66, 4.10.0-32-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GM107 [GeForce GTX 750] [1462:3104] InstallationDate: Installed on 2017-08-07 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Gigabyte Technology Co., Ltd. H55M-D2H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic root=UUID=c654de12-156a-415e-b05f-aa3c098bfb1c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: H55M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd05/04/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-D2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-D2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H55M-D2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Fri Aug 18 23:09:40 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New
[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
Unfortunately for me this fix hasn't worked given that the subwoofer and microphone on my Pavilion 15-aw054sa do not produce/record any sound. I, of course, have an ALC295 and I'm running Mint Sonya (which is based on Ubuntu). I have made two comments on the Bugzilla entry (https://bugzilla.kernel.org/show_bug.cgi?id=195457#c9) and nothing has happened regarding the bug. I have run alsa-tools after running Robert's fix and this is the result: (https://bugzilla.kernel.org/attachment.cgi?id=257171) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Patch removed: "lp1642966_xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+attachment/4934838/+files/lp1642966_xenial.debdiff -- 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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
lp1642966_xenial.debdiff ** Patch added: "lp1642966_xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+attachment/4934838/+files/lp1642966_xenial.debdiff -- 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 1707393] Re: vlc no longer displays certain streams since update vdpau
Reporter of #1710503 uses mesa-vdpau-driver. Re-assigning accordingly. ** Package changed: vlc (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1707393 Title: vlc no longer displays certain streams since update vdpau Status in mesa package in Ubuntu: Incomplete Bug description: Display was fine until apdate of vdpau was applied. Vlc codec info from stream: Video MPEG-4 Video (mp4v) Resolution: 640x480 Framerate: 1000 Decode format: planar 4:2:0 YUV Previous recordings of this stream will also do not display anymore, while the standard Videos apllication does play them back fine. New recordings via vlc cannot be played back by both the vlc and Videos application. Console output while starting the stream: VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80) [01589088] core libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [7f86a9b8] core input error: ES_OUT_RESET_PCR called [7f86b00092d8] vdpau_avcodec generic error: decoder profile not supported: 12 [7f86b0007ac8] vdpau_avcodec generic error: decoder profile not supported: 12 [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [mpeg4 @ 0x7f869803dfa0] warning: first frame is no keyframe [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 29 15:02:01 2017 InstallationDate: Installed on 2017-06-17 (42 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709881] Re: [xenial] QT5 gles support for arm64 architecture
There is no possibility of updating qtbase-opensource-src, as that will break the whole Qt stack. What I can do is adding arm64 builds to a separate package, qtbase- opensource-src-gles. Please try the package in this PPA: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/2912/+packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1709881 Title: [xenial] QT5 gles support for arm64 architecture Status in qtbase-opensource-src package in Ubuntu: Invalid Bug description: According to the Xenial's build log, it did not build as gles for the arm64 even though it should be built with -opengl es2 option. > debian/rules gles2_architectures := armel armhf arm64 ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH), $(gles2_architectures))) extra_configure_opts += -opengl es2 else extra_configure_opts += -opengl desktop endif Here is the xenial's build log and it shows OpenGL as Desktop version. - Xenial build log: https://launchpadlibrarian.net/319422529/buildlog_ubuntu-xenial-arm64.qtbase-opensource-src_5.5.1+dfsg-16ubuntu7.5_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... desktop However, the zesty's build log shows OpenGL as ES2. - Zesty build log: https://launchpadlibrarian.net/328680692/buildlog_ubuntu-zesty-arm64.qtbase-opensource-src_5.7.1+dfsg-2ubuntu4~1.17.04.1_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... yes (OpenGL ES 2.0+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1709881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707393] [NEW] vlc no longer displays certain streams since update vdpau
You have been subscribed to a public bug: Display was fine until apdate of vdpau was applied. Vlc codec info from stream: Video MPEG-4 Video (mp4v) Resolution: 640x480 Framerate: 1000 Decode format: planar 4:2:0 YUV Previous recordings of this stream will also do not display anymore, while the standard Videos apllication does play them back fine. New recordings via vlc cannot be played back by both the vlc and Videos application. Console output while starting the stream: VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80) [01589088] core libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [7f86a9b8] core input error: ES_OUT_RESET_PCR called [7f86b00092d8] vdpau_avcodec generic error: decoder profile not supported: 12 [7f86b0007ac8] vdpau_avcodec generic error: decoder profile not supported: 12 [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [mpeg4 @ 0x7f869803dfa0] warning: first frame is no keyframe [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 29 15:02:01 2017 InstallationDate: Installed on 2017-06-17 (42 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug xenial -- vlc no longer displays certain streams since update vdpau https://bugs.launchpad.net/bugs/1707393 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
@iiro, I just uploaded a new version of the test package a few minutes ago... Please make sure when you will give the PPA a try that you are upgrading to "2.1.3-4ubuntu0.3+test1" version. - 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 1711020] Re: package linux-image-extra-4.4.0-91-generic 4.4.0-91.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1711020 Title: package linux-image-extra-4.4.0-91-generic 4.4.0-91.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I don't know. System alerted me of an issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-91-generic 4.4.0-91.114 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-headers-4.4.0-91-generic: Remove linux-headers-4.4.0-91: Remove linux-image-extra-4.4.0-91-generic: Remove linux-image-4.4.0-91-generic: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wayne 1743 F pulseaudio Date: Tue Aug 15 22:48:09 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=7fc64e3c-6cfa-4c1f-9988-fb544d761dac InstallationDate: Installed on 2016-12-17 (241 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire 5733Z ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic root=UUID=56c8a1ca-2097-4f05-ac45-97f85b1480c9 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-91-generic 4.4.0-91.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5733Z dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnAcer:bvrV1.07:bd11/07/2011:svnAcer:pnAspire5733Z:pvrV1.07:rvnAcer:rnAspire5733Z:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire 5733Z dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1711020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700753] Re: Merge adduser 3.115 (main) from Debian unstable (main)
Ping! ** Summary changed: - Merge adduser 3.115 (main) from Debian unstable (main) + Merge adduser 3.116 (main) from Debian unstable (main) ** Description changed: Please merge adduser 3.115 (main) from Debian unstable (main) Sorry, I cannot work on the merge myself. I am filing this for reference. Explanation of the Ubuntu delta: - * testsuite/runsuite.sh: Add the testsuite directory to @INC, so it can find - the tests. - * extrausers support for adduser (LP: #1323732) - * Add autopkgtest. (LP: #1246331) - * Move ecryptfs-utils from recommends, to suggests. (LP: #1188108) - Adduser has moved from required to minimal set, and thus started to - pull ecryptfs-utils and cryptsetup into minimal installs, which is an - undesired effect. - * Merge from Debian unstable, remaining changes: - - AdduserCommon.pm, adduser, adduser.8, adduser.conf.5: Allow uppercase - letters in the names of system users. This is done by having a separate - NAME_REGEX_SYSTEM configuration setting which applies when --system is - specified. (Soren Hansen) - - Add support for encrypting home directories: - + adduser: Add --encrypt-home option, which calls ecryptfs-setup-private - for the hard work. - + doc/adduser.8: document the --encrypt-home option - + debian/control: recommend ecryptfs-utils >= 67-1 - + deluser: remove all of /var/lib/ecryptfs/$user with --remove-home - * Dropped changes, included in Debian: - - Mark adduser Multi-Arch: foreign. + * testsuite/runsuite.sh: Add the testsuite directory to @INC, so it can find + the tests. + * extrausers support for adduser (LP: #1323732) + * Add autopkgtest. (LP: #1246331) + * Move ecryptfs-utils from recommends, to suggests. (LP: #1188108) + Adduser has moved from required to minimal set, and thus started to + pull ecryptfs-utils and cryptsetup into minimal installs, which is an + undesired effect. + * Merge from Debian unstable, remaining changes: + - AdduserCommon.pm, adduser, adduser.8, adduser.conf.5: Allow uppercase + letters in the names of system users. This is done by having a separate + NAME_REGEX_SYSTEM configuration setting which applies when --system is + specified. (Soren Hansen) + - Add support for encrypting home directories: + + adduser: Add --encrypt-home option, which calls ecryptfs-setup-private + for the hard work. + + doc/adduser.8: document the --encrypt-home option + + debian/control: recommend ecryptfs-utils >= 67-1 + + deluser: remove all of /var/lib/ecryptfs/$user with --remove-home + * Dropped changes, included in Debian: + - Mark adduser Multi-Arch: foreign. Changelog entries since current artful version 3.113+nmu3ubuntu5: + adduser (3.116) unstable; urgency=medium + + * Advise installation of 'perl' rather than 'perl-modules' + (Closes: #840982) + * Improve distinction between informational and essential messages + (Closes: #763055) + * Improve message accompanying error code for creating system user + (Closes: #708073, #759740) + * testsuite: add current directory to Perl module search path + * Use /usr/sbin/nologin instead of /bin/false for default system shell + (Closes: #845791) + * Bump Standards-Version to 4.0.1 + + -- Afif Elghraoui Sat, 12 Aug 2017 16:05:34 -0400 + adduser (3.115) unstable; urgency=medium - [ Afif Elghraoui ] - * Adopt package (Closes: #811411) - * Set Vcs-* fields to point to Git repository - * Bump Standards-Version to 3.9.8 - * Extend last_{u,g}id to 5 to match policy update from 3.9.0 - (Closes: #776203) - * Note to work on the lintian error for debconf template. - * Fix path to rpcinfo, used for NIS support. - (Thanks to Nis Martensen for report and patch). - * Update Vietnamese translations (Closes: #825610) - Thanks to all translators for providing updates + [ Afif Elghraoui ] + * Adopt package (Closes: #811411) + * Set Vcs-* fields to point to Git repository + * Bump Standards-Version to 3.9.8 + * Extend last_{u,g}id to 5 to match policy update from 3.9.0 + (Closes: #776203) + * Note to work on the lintian error for debconf template. + * Fix path to rpcinfo, used for NIS support. + (Thanks to Nis Martensen for report and patch). + * Update Vietnamese translations (Closes: #825610) + Thanks to all translators for providing updates - [ Helge Kreutzmann ] - * Debconf: - * Update Turkish translation. Closes: #676356. - * Fix language field in Norwegian translation. Closes: #695997. - * Program (translation): - * Use "--previous" when generating the updated po files. - * Mention "--add_extra_groups" in --help output. Closes: #547911. - * Update Japanese translation. Closes: #697109. - * Update Czech translation. Closes: #825734. - * Update Slovak translation. Closes: #825770.
[Touch-packages] [Bug 1417370] Re: Qt 5 uses grayscale instead of subpixel font antialiasing
** Attachment added: "budgie_qt_no_antialias.png" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1417370/+attachment/4934805/+files/budgie_qt_no_antialias.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1417370 Title: Qt 5 uses grayscale instead of subpixel font antialiasing Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: Qt 5 applications like Qt Creator or the Ubuntu web browser (webbrowser-app) use grayscale font antialiasing. GTK 3, GTK 2, and Qt 4 use subpixel antialiasing as expected, so fonts in Qt 5 look weird. Attached screenshot shows an example of the problem. This upstream bug report might be related: https://bugreports.qt.io/browse/QTBUG-36445 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libqt5gui5 5.2.1+dfsg-1ubuntu14.2 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 2 19:35:10 2015 InstallationDate: Installed on 2014-08-30 (156 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1417370/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417370] Re: Qt 5 uses grayscale instead of subpixel font antialiasing
Here is enlargement of screenshot from Ubuntu-Budgie and Krita. This issue seems still unresolved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1417370 Title: Qt 5 uses grayscale instead of subpixel font antialiasing Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: Qt 5 applications like Qt Creator or the Ubuntu web browser (webbrowser-app) use grayscale font antialiasing. GTK 3, GTK 2, and Qt 4 use subpixel antialiasing as expected, so fonts in Qt 5 look weird. Attached screenshot shows an example of the problem. This upstream bug report might be related: https://bugreports.qt.io/browse/QTBUG-36445 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libqt5gui5 5.2.1+dfsg-1ubuntu14.2 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 2 19:35:10 2015 InstallationDate: Installed on 2014-08-30 (156 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1417370/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710995] Re: whoopsie not online
I've confirmed this with my mythbuntu 16.04 install with whoopsie 0.2.52.5 from xenial-updates. It might be interesting to try and bring down the network interface and then bring it back on line and see if whoopsie then comes on-line. ** Changed in: whoopsie (Ubuntu) Status: Incomplete => Confirmed ** Changed in: whoopsie (Ubuntu) Importance: Undecided => High ** Summary changed: - whoopsie not online + mythbuntu 16.04 install - whoopsie not online -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: mythbuntu 16.04 install - whoopsie not online Status in whoopsie package in Ubuntu: Confirmed Bug description: Reporting crashes from /var/crash/* is not possible any more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.5 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashReports: 640:1000:139:81264064:2017-08-12 10:41:39.397392016 +0200:2017-08-16 00:23:25.391175383 +0200:/var/crash/_usr_bin_mythwelcome.1000.crash 640:0:139:936170:2017-08-12 17:56:15.728615283 +0200:2017-08-16 00:34:15.013084038 +0200:/var/crash/_lib_systemd_systemd-udevd.0.crash 640:1000:139:1194610:2017-08-11 17:52:56.113431094 +0200:2017-08-11 17:55:44.737433966 +0200:/var/crash/_usr_bin_xfce4-power-manager.1000.crash 640:1000:139:60309601:2017-08-16 00:18:13.511184669 +0200:2017-08-16 00:18:13.515184669 +0200:/var/crash/_usr_lib_x86_64-linux-gnu_kodi_kodi.bin.1000.crash Date: Wed Aug 16 00:37:18 2017 RelatedPackageVersions: apport-noui 2.20.1-0ubuntu2.10 SourcePackage: whoopsie UpgradeStatus: Upgraded to xenial on 2016-08-06 (374 days ago) --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: whoopsie 0.2.52.5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 RelatedPackageVersions: apport-noui N/A Tags: xenial autoreport-false Uname: Linux 4.10.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-08-06 (374 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin mythtv netdev plugdev sambashare scanner tape vboxusers video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709193] Re: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer
Verified on Xenial with: $ apt-cache policy libgnutls-openssl27:amd64 libgnutls-openssl27: Installed: 3.4.10-4ubuntu1.4 Candidate: 3.4.10-4ubuntu1.4 Version table: *** 3.4.10-4ubuntu1.4 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.4.10-4ubuntu1.3 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 3.4.10-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnutls26 in Ubuntu. https://bugs.launchpad.net/bugs/1709193 Title: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer Status in gnutls26 package in Ubuntu: Invalid Status in gnutls28 package in Ubuntu: Fix Released Status in gnutls26 source package in Trusty: Fix Committed Status in gnutls28 source package in Trusty: Won't Fix Status in ssmtp source package in Trusty: Invalid Status in gnutls26 source package in Xenial: Invalid Status in gnutls28 source package in Xenial: Fix Committed Status in ssmtp source package in Xenial: Invalid Status in gnutls26 source package in Zesty: Invalid Status in gnutls28 source package in Zesty: Fix Committed Status in ssmtp source package in Zesty: Invalid Status in gnutls26 source package in Artful: Invalid Status in gnutls28 source package in Artful: Fix Released Status in ssmtp source package in Artful: Invalid Status in gnutls28 package in Debian: Fix Released Bug description: [Impact] Applications using GnuTLS OpenSSL compat layer [1] are be unable to use modern TLS versions (1.1 and 1.2) when relying on the SSLv23_{client,server}_method functions. There is an industry-wide push to use modern TLS versions, see [2] and [3] for example. The proposed fix changes the compat layer to use GnuTLS' "NORMAL" priority [4] instead of hard-coding which protocol versions and ciphers to enable. [Test Case] 1) Setup a mail submission server that uses StartTLS 2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay through the mail relay using StartTLS 3) Send an email while capturing with tcpdump/tshark 4) Inspect the submission connection (TCP/587) and look for the protocol version negotiated by the client. Without the fix, you should see TLSv1.0. With the fix, it should be TLSv1.2. Please see the original issue description for more details. [Regression Potential] Regression risk should be low since it's a backport of a simple fix that landed in Debian in April 2017. [References] 1: $ apt-cache rdepends libgnutls-openssl27 libgnutls-openssl27 Reverse Depends: libgnutls-dev libgnutls-dev zoneminder yaskkserv tf5 ssmtp snowdrop sngrep slrnpull slrn sipsak macopix-gtk2 gnss-sdr gkrellm freewheeling boinctui iputils-ping 2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html 3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls 4: https://gnutls.org/manual/html_node/Priority-Strings.html [Original issue description] sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with it. Here's a packet capture when ssmtp connects to smtp.sdeziel.info:587 that offers TLSv1.0 and higher: $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)' Version: TLS 1.0 (0x0301) Handshake Protocol: Client Hello Version: TLS 1.0 (0x0301) Cipher Suites Length: 30 Cipher Suites (15 suites) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041) Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084) Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045) Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088) Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016) Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032) Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038) Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0044) Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0087)
[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted
A workaround. Have/Had the same issue. As the logrotate is executed by the daily cronjob, I modified /etc/cron.daily/logrotate to the following: - #!/bin/sh /usr/sbin/logrotate -s /var/lib/logrotate/logrotate.status /etc/logrotate.conf EXITVALUE=$? if [ $EXITVALUE != 0 ]; then /usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]" fi /bin/systemctl restart rsyslog exit 0 And that resolved the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/940030 Title: rsyslog stops working after logrotate until restarted Status in rsyslog package in Ubuntu: Confirmed Bug description: This could otherwise be titled, rsyslog reload does not create log files; only restart does. This is happening on a number of machines I work on. It's happening on 10.04 and 11.04. It might be similar to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862 But in my case after the restart there is no /var/log/syslog being created, nor auth.log, kern.log, etc. The files are rotated, rsyslog is reloaded, and none of the log files are created and nothing is being logged. This has been plaguing my systems since moving from syslog-ng, which I may return to as it seems it was actually production ready. Without manually restarting those files don't exist so here's what I did on an 11.04 system: logrotate --force --verbose /etc/logrotate.conf gives: rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog log /var/log/syslog does not exist -- skipping not running postrotate script, since no logs were rotated rotating pattern: /var/log/mail.info /var/log/mail.warn /var/log/mail.err /var/log/mail.log /var/log/daemon.log /var/log/kern.log /var/log/auth.log /var/log/user.log /var/log/lpr.log /var/log/cron.log /var/log/debug /var/log/messages forced from command line (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/mail.info log /var/log/mail.info does not exist -- skipping considering log /var/log/mail.warn log /var/log/mail.warn does not exist -- skipping considering log /var/log/mail.err log does not need rotating considering log /var/log/mail.log log does not need rotating considering log /var/log/daemon.log log /var/log/daemon.log does not exist -- skipping considering log /var/log/kern.log log /var/log/kern.log does not exist -- skipping considering log /var/log/auth.log log /var/log/auth.log does not exist -- skipping considering log /var/log/user.log log /var/log/user.log does not exist -- skipping considering log /var/log/lpr.log log /var/log/lpr.log does not exist -- skipping considering log /var/log/cron.log log /var/log/cron.log does not exist -- skipping considering log /var/log/debug log /var/log/debug does not exist -- skipping considering log /var/log/messages log /var/log/messages does not exist -- skipping not running postrotate script, since no logs were rotated Then /sbin/reload rsyslog logger -i testing At this point there is no /var/log/syslog Then: /sbin/restart rsyslog And voila there is a /var/log/syslog beginning with: Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg started. Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com";] (re)start Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114 Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108 Then to recreate: logrotate --force --verbose /etc/logrotate.conf rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog log needs rotating rotating log /var/log/syslog, log->rotateCount is 7 dateext suffix '-20120223' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' compressing log with: /bin/gzip renaming /var/log/syslog to /var/log/syslog-20120223 running postrotate script removing old log /var/log/syslog-20111219.gz rotating pattern: /var/log/mail.info /var/log/mail.warn /var/log/mail.err /var/log/mail.log /var/log/daemon.log /var/log/kern.log /var/log/auth.log /var/log/user.log /var/log/lpr.log /var/log/cron.log /var/log/debug /var/log/messages forced from command line (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/mail.info log /var/log/mail.info does not exist -- skipping considering log /var/log/mail.warn log /var/log/mail.war
[Touch-packages] [Bug 1711667] [NEW] no xorg.conf after nvidia driver installation
Public bug reported: no any config file about graphics system: Ubuntu 17.04 64bit, latest drivers the machine is laptop Asus i7 with Intel Graphics integrated and second card nVidia GT740m ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 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: Fri Aug 18 16:33:30 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-30-generic, x86_64: installed bbswitch, 0.8, 4.10.0-32-generic, x86_64: installed nvidia-384, 384.59, 4.10.0-32-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:122d] Subsystem: ASUSTeK Computer Inc. GK208M [GeForce GT 740M] [1043:122d] InstallationDate: Installed on 2017-05-11 (98 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. X750JB ProcEnviron: LANGUAGE=pl PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=bf9a973b-54f4-401b-9341-a587fcaf877c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X750JB.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X750JB 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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X750JB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Thu Aug 17 14:17:54 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty -- 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/1711667 Title: no xorg.conf after nvidia driver installation Status in xorg package in Ubuntu: New Bug description: no any config file about graphics system: Ubuntu 17.04 64bit, latest drivers the machine is laptop Asus i7 with Intel Graphics integrated and second card nVidia GT740m ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 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: Fri Aug 18 16:33:30 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-30-generic, x86_64: installed bbswitch, 0.8, 4.10.0-32-generic, x86_64: installed nvidia-384, 384.59, 4.10.0-32-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller
[Touch-packages] [Bug 1710911] Re: apt-ftparchive does not correctly cache filesizes for packages > 4GB
** Changed in: apt (Debian) Status: Unknown => New -- 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/1710911 Title: apt-ftparchive does not correctly cache filesizes for packages > 4GB Status in apt package in Ubuntu: New Status in apt package in Debian: New Bug description: Release: 16.04 Version: 1.2.19 apt-ftparchive is a utility for, among other things, generating a Packages file from a set of .deb packages. Because generating Packages files for a large directory tree of .deb packages is expensive, it can cache the properties of .deb packages it has already inspected in a Berkeley database file. Historically, apt-ftparchive stored the size of a .deb package as a 32-bit unsigned integer in network byte-order in this cache. This field was later enlarged to 64-bits - which caused other problems; see: LP #1274466. However, even after this integer field was enlarged, apt-ftparchive continued to use the htonl() and ntohl() libc functions to convert file-sizes to and from network byte-order when reading and writing to its cache. These functions unconditionally emit 32-bit unsigned integers, which means that apt-ftparchive remained unable to correctly record the file-sizes for packages > 32bits (i.e. > 4GB). Consequently, if apt-ftparchive is asked (with caching enabled) to generate a Packages file for a .deb package larger than 4GB, it will produce a Packages file with the correct Size: field the first time, but with incorrect Size: fields subsequently. I have developed a small patch which replaces the use of the ntohl() family of functions with suitable replacements from . This produces correct output on new installations. However, caution is necessary: the existing code is incorrectly storing the 32 least significant bits of a 64-bit number in the upper 32-bits of a 64-bit field, in big-endian byte order. The application of this patch will cause new values to be stored correctly, but in a binary-incompatible way with existing caches. For example, a package of size 7162161474 bytes will today have the following sequence of bytes stored in its cache entry: \xaa\xe5\xe9\x42\x00\x00\x00\x00 (When re-read, this will produce a file-size value of 7162161474 mod 32bits, i.e. 2867194178.) With this patch applied, apt-ftparchive will correctly store this entry: \x00\x00\x00\x01\xaa\xe5\xe9\x42 However, this correct cache entry, when interpreted by the current broken code, will return a file-size of 1 byte. Worse, the existing broken entry will be interpreted by my fixed code as containing the value 12314505225791602688. It would be good to have this patch, or some derivative of it, applied to the main APT code-base. Before this can happen, however, some mechanism to detect and correct broken cache entries will be needed if we are to avoid a repeat of LP #1274466. I would suggest this could be done by checking the trailing four bytes of the 64-bit filesize field: if they are all zero, then the cache entry is broken, and should be rewritten. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1710911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 541595] Re: [Master] package failed to install/upgrade: package is already installed and configured
** Changed in: dpkg Status: New => Invalid ** Changed in: apt (Ubuntu) Status: Confirmed => Invalid -- 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/541595 Title: [Master] package failed to install/upgrade: package is already installed and configured Status in dpkg: Invalid Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Fix Released Bug description: Binary package hint: dpkg For yet unknown reasons packages fail to install with an error like: dpkg: error processing flashplugin-installer (--configure): package flashplugin-installer is already installed and configured without further error. This is a "one time" failure. Another run of the installation doesn't produce any error. Users reporting this error are also experiencing bug 545790 and bug 545738 . ProblemType: Bug Architecture: i386 Date: Fri Mar 19 00:09:06 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes Package: dpkg 1.15.5.6ubuntu3 ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: dpkg Uname: Linux 2.6.32-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/dpkg/+bug/541595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1265418] Re: Gtk3 bookmark can't be removed if it points to a file
** Changed in: gtk Status: Confirmed => Invalid -- 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/1265418 Title: Gtk3 bookmark can't be removed if it points to a file Status in GTK+: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Bug description: In the file requestor of Gtk3 you can drag files and directories to the sidebar to create bookmarks. If the user drags a file here the bookmark can never be deleted because the option is disabled. To reproduce: 1. Open a Gtk3 application such as firefox, gedit etc. 2. Open the File Open requester. 3. Drag a file to the bookmarks. 4. Right click on the file bookmark. Expected result: Should be able to click on "Remove" to remove the bookmark. Actual result: The remove option is always disabled. Workaround: Edit ~/.config/gtk-3.0/bookmarks and delete the bookmark line. Also affects trusty. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk-3-0 3.8.6-0ubuntu3.1 Uname: Linux 3.11.0-031100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Jan 2 02:49:04 2014 InstallationDate: Installed on 2013-08-27 (127 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827) MarkForUpload: True SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1265418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697283] Re: Denial of Service Vulnerability in Librsvg
** Information type changed from Private Security to Public Security ** Changed in: librsvg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1697283 Title: Denial of Service Vulnerability in Librsvg Status in librsvg package in Ubuntu: Confirmed Bug description: An SIGFPE is raised in function box_blur_line of rsvg-filter.c when the librsvg try to parse a craft SVG file. https://github.com/GNOME/librsvg/blob/master/rsvg-filter.c#L1439 if (output >= 0) dest[bpp * output + i] = (ac[i] + (coverage >> 1)) / coverage; } The coverage could be zero. testcase.svg http://www.w3.org/2000/svg"; xmlns:xlink="http://www.w3.org/1999/xlink";> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1697283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708931] Re: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04
Does Ubuntu Budgie has TLP preinstalled? Thats would explain everything. -- 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/1708931 Title: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04 Status in bluez package in Ubuntu: New Bug description: It happens at every reset, after using bluetooth mouse for a few minutes. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Aug 6 16:42:56 2017 InstallationDate: Installed on 2017-08-05 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80E5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic root=UUID=0585caf9-68a0-4a81-ba3d-c030affa951e ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN97WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: B4:6D:83:B1:A7:87 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:301634 acl:15117 sco:0 events:1578 errors:0 TX bytes:2425 acl:31 sco:0 commands:169 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1708931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711605] [NEW] a2dp profile still alive even though disconnected
Public bug reported: Since the pulseaudio of Xenial has been updated from 8.0-0ubuntu3.2 to 8.0-0ubuntu3.3 at last May, I failed my TestCase The test case is just repeating connect/disconnect with BT headset through bluetoothctl. The change[1] can be retrieved from Xenial's pulseaudio source but I can't ensure which patch causes the problem. You can see the error log[2] when the error has been occurred. [1] pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium [Luke Yelavich, Konrad Zapałowicz] * Fixed multiple interrelated problems with using Bluetooth audio (A2DP), where users would experience some combination of: - Bluetooth headset/speakers listed but not selectable in Sound settings (LP: #1283003) - [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) (LP: #1438510) - [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first (LP: #1582213) * Specific patches from upstream used to address the above problems: - 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch . Backport from upstream to fix a bug in Xenial where an incorrect audio profile is applied for a headset connected over Bluetooth making using it impossible. - 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch . Fix a crash that happens if the BT headset is the only non-monitor source in the system and the last "phone" stream dies. - 0700-pulsecore-add-new-card-profile-hook.patch . Backport from upstream (commit 7b6260140149) to allow for correct profile selection. - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch . Backport from upstream waiting for all profiles to connect before creating a card. -- Daniel van Vugt Tue, 23 May 2017 16:24:14 +0800 [2] Error log D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, interface=org.bluez.Profile1, member=NewConnection D: [pulseaudio] backend-native.c: dbus: NewConnection path=/org/bluez/hci0/dev_00_18_09_2C_1F_41, fd=18 D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 state changed from disconnected to idle D: [pulseaudio] backend-native.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 available for profile headset_head_unit D: [pulseaudio] backend-native.c: RFCOMM << AT+VGS=07 D: [pulseaudio] backend-native.c: RFCOMM >> OK D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=SelectConfiguration D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Introspectable found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.bluez.MediaTransport1 found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Properties found, skipping D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=SetConfiguration D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 state changed from disconnected to idle D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 available for profile a2dp_sink D: [pulseaudio] bluez5-util.c: Properties changed in device /org/bluez/hci0/dev_00_18_09_2C_1F_41 D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, interface=org.bluez.Profile1, member=RequestDisconnection D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, interface=org.bluez.MediaEndpoint1, member=ClearConfiguration D: [pulseaudio] bluez5-util.c: Clearing transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 profile a2dp_sink D: [pulseaudio] bluez5-util.c: Transport /org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 state changed from idle to disconnected D: [pulseaudio] bluez5-util.c: Unknown interface org.freedesktop.DBus.Introspectable found, skipping D: [pulseaudio] bluez5-util.c: Unknown interface org.bluez.MediaTransport1 found, skipping D: [pulseau
[Touch-packages] [Bug 1591672] Re: update-manager does not obey require-password policy
** No longer affects: policykit-1 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1591672 Title: update-manager does not obey require-password policy Status in update-manager package in Ubuntu: New Bug description: In order to enforce password check prior an update to occur, policy file was installed. /var/lib/polkit-1/localauthority/50-local.d/require-password-to-update.pkla [Require password to upgrade already installed software] Identity=unix-group:admin Action=org.debian.apt.upgrade-packages ResultActive=auth_admin Up to a recent update this was working as expected. No anymore. What happens Updates are performed without requesting administrative password Expected result --- update-manager to request administrative password prior performing the update System info --- # lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 # dpkg -l | grep update-manager ii python3-update-manager 1:16.04.3 all python 3.x module for update-manager ii update-manager 1:16.04.3 all GNOME application that manages apt updates ii update-manager-core 1:16.04.3 all manage release upgrades # dpkg -l | grep policy ii libnuma1:amd64 2.0.11-1ubuntu1 amd64Libraries for controlling NUMA policy ii libsemanage-common 2.3-1build3 all Common files for SELinux policy management libraries ii libsemanage1:amd64 2.3-1build3 amd64SELinux policy management library ii plainbox-secure-policy 0.25-1 all policykit policy required to use plainbox (secure version) ii policykit-1 0.105-14.1 amd64framework for managing administrative policies and privileges ii policykit-1-gnome0.105-2ubuntu2 amd64GNOME authentication agent for PolicyKit-1 ii policykit-desktop-privileges 0.20 all run common desktop actions without password # apt-cache policy update-manager update-manager: Installed: 1:16.04.3 Candidate: 1:16.04.3 Version table: *** 1:16.04.3 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status # find /var/lib/polkit-1/localauthority /var/lib/polkit-1/localauthority /var/lib/polkit-1/localauthority/50-local.d /var/lib/polkit-1/localauthority/50-local.d/require-password-to-update.pkla /var/lib/polkit-1/localauthority/90-mandatory.d /var/lib/polkit-1/localauthority/20-org.d /var/lib/polkit-1/localauthority/10-vendor.d /var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla /var/lib/polkit-1/localauthority/10-vendor.d/fwupd.pkla /var/lib/polkit-1/localauthority/10-vendor.d/com.canonical.unity.webapps.pkla /var/lib/polkit-1/localauthority/10-vendor.d/50-com.canonical.indicator.sound.AccountsService.pkla /var/lib/polkit-1/localauthority/10-vendor.d/unity-greeter.pkla /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla /var/lib/polkit-1/localauthority/30-site.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1591672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652381] Re: systematic way to refresh the random-seed again and again
Hi John, We get the current random seed unit from systemd. Please file a bug with the upstream systemd project, or discuss these changes on the systemd mailing list. Once your changes are accepted by systemd, we will inherit them. Thanks! ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist -- 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/1652381 Title: systematic way to refresh the random-seed again and again Status in systemd package in Ubuntu: Confirmed Bug description: Background and rationale: There ought to be a nice systematic way to refresh the random-seed again and again, while the system is running normally, not just at boot time or at shutdown time. Sometimes a system may crash without carrying out an orderly shutdown. Indeed some systems never carry out an orderly shutdown; they run until they die. Therefore all the reasons why it is important to refresh the random-seed during shutdown are also good reasons for refreshing it from time to time during normal operations ... not just at startup. Desired behavior: The logical, systematic, traditional, and expected way to refresh the seed would be either "systemctl start systemd- random-seed" or equivalently "/etc/init.d/urandom start". The command should happily run as many times as desired, and should refresh the random-seed each time. Observed behavior: "systemctl start systemd-random-seed" doesn't have the desired effect. Apparently systemd considers the previous instance of systemd-random-seed.service to be still active, so additional starts don't do any good. Furthermore, "/etc/init.d/urandom start" has been re-implemented in terms of "systemctl start systemd-random-seed", so that doesn't work either. This is a significant regression relative to the pre-systemd behavior. Constructive suggestion. See attached patch. Recipe: :; systemctl start systemd-random-seed -- Observe that /var/lib/systemd/random-seed does not get refreshed. :; systemctl stop systemd-random-seed -- Apply the patch. :; systemctl daemon-reload :; systemctl start systemd-random-seed :; sleep 60 :; systemctl start systemd-random-seed -- observe that the seed now does get refreshed. There may be other ways of dealing with the issue, but this seems nice and simple. Tangent: In a non-essential way, this might touch on decisions about how best to address https://bugs.launchpad.net/bugs/1651947 Digression: There is a policy question as to how often to refresh the seed during normal operations. That is a question for another day. --- Observed on :; lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 :; apt-cache policy systemd systemd: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu13 Version table: *** 229-4ubuntu13 500 500 http://ubuntu.cs.utah.edu/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1652381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711600] Re: package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: eglibc (Ubuntu) Importance: Undecided => Low ** Changed in: eglibc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1711600 Title: package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135 Status in eglibc package in Ubuntu: Invalid Bug description: I obtain this error after giving the command 'apt-get upgrade' ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libc-bin 2.19-0ubuntu6.13 ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-66-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Thu Aug 17 20:42:54 2017 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.13 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.9 DuplicateSignature: package:libc-bin:2.19-0ubuntu6.13:il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135 InstallationDate: Installed on 2015-12-24 (602 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: eglibc Title: package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1711600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711600] [NEW] package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135
Public bug reported: I obtain this error after giving the command 'apt-get upgrade' ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libc-bin 2.19-0ubuntu6.13 ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-66-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Thu Aug 17 20:42:54 2017 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.13 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.9 DuplicateSignature: package:libc-bin:2.19-0ubuntu6.13:il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135 InstallationDate: Installed on 2015-12-24 (602 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: eglibc Title: package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eglibc (Ubuntu) Importance: Low Status: Invalid ** Tags: apport-package hardware-error i386 need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1711600 Title: package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135 Status in eglibc package in Ubuntu: Invalid Bug description: I obtain this error after giving the command 'apt-get upgrade' ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libc-bin 2.19-0ubuntu6.13 ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-66-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Thu Aug 17 20:42:54 2017 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.13 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.9 DuplicateSignature: package:libc-bin:2.19-0ubuntu6.13:il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135 InstallationDate: Installed on 2015-12-24 (602 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: eglibc Title: package libc-bin 2.19-0ubuntu6.13 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 135 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1711600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700937] Re: Heap-buffer overflow in nodeAcquire
** Changed in: sqlite3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1700937 Title: Heap-buffer overflow in nodeAcquire Status in sqlite3 package in Ubuntu: Confirmed Bug description: A heap-buffer overflow (sometimes a crash) can arise when running a SQL request on malformed sqlite3 databases such as the one attached to this ticket {{{ $ valgrind sqlite3 clusterfuzz-testcase-minimized-4960347410661376 "SELECT pkid FROM 'idx_byte_metadata_geometry' WHERE xmax > 0 AND xmin < 0 AND ymax > 0 AND ymin < 0" ==21234== Memcheck, a memory error detector ==21234== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==21234== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==21234== Command: sqlite3 clusterfuzz-testcase-minimized-4960347410661376 SELECT\ pkid\ FROM\ 'idx_byte_metadata_geometry'\ WHERE\ xmax\ \>\ 0\ AND\ xmin\ \<\ 0\ AND\ ymax\ \>\ 0\ AND\ ymin\ \<\ 0 ==21234== Invalid read of size 1 ==21234==at 0x1B3945: nodeAcquire (in /usr/bin/sqlite3) ==21234==by 0x1B5056: rtreeFilter (in /usr/bin/sqlite3) ==21234==by 0x186EAA: sqlite3VdbeExec (in /usr/bin/sqlite3) ==21234==by 0x190316: sqlite3_step (in /usr/bin/sqlite3) ==21234==by 0x11886F: shell_exec.constprop.12 (in /usr/bin/sqlite3) ==21234==by 0x114693: main (in /usr/bin/sqlite3) ==21234== Address 0x5ae5b00 is 0 bytes after a block of size 48 alloc'd ==21234==at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==21234==by 0x14C176: sqlite3MemMalloc (in /usr/bin/sqlite3) ==21234==by 0x128380: sqlite3Malloc (in /usr/bin/sqlite3) ==21234==by 0x1B38DF: nodeAcquire (in /usr/bin/sqlite3) ==21234==by 0x1B5056: rtreeFilter (in /usr/bin/sqlite3) ==21234==by 0x186EAA: sqlite3VdbeExec (in /usr/bin/sqlite3) ==21234==by 0x190316: sqlite3_step (in /usr/bin/sqlite3) ==21234==by 0x11886F: shell_exec.constprop.12 (in /usr/bin/sqlite3) ==21234==by 0x114693: main (in /usr/bin/sqlite3) }}} This bug is no longer reproducible with at least sqlite3 3.17 {{{ $ valgrind ~/install-sqlite-3.17.0/bin/sqlite3 clusterfuzz-testcase-minimized-4960347410661376 "SELECT pkid FROM 'idx_byte_metadata_geometry' WHERE xmax > 0 AND xmin < 0 AND ymax > 0 AND ymin < 0" ==21265== Memcheck, a memory error detector ==21265== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==21265== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==21265== Command: /home/even/install-sqlite-3.17.0/bin/sqlite3 clusterfuzz-testcase-minimized-4960347410661376 SELECT\ pkid\ FROM\ 'idx_byte_metadata_geometry'\ WHERE\ xmax\ \>\ 0\ AND\ xmin\ \<\ 0\ AND\ ymax\ \>\ 0\ AND\ ymin\ \<\ 0 ==21265== Error: database disk image is malformed }}} This bug has been originally uncovered by OSS-Fuzz when running on the GDAL library that uses libsqlite3: https://bugs.chromium.org/p/oss- fuzz/issues/detail?id=2405 (content not viewable during the grace period) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: sqlite3 3.11.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed Jun 28 11:18:29 2017 InstallationDate: Installed on 2016-11-04 (235 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: sqlite3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1700937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704981] Re: I don't know
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1704981 Title: I don't know Status in xorg package in Ubuntu: New Bug description: I don't know ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.135 Tue Jan 17 15:26:26 PST 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.4 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: Tue Jul 18 14:29:35 2017 DistUpgraded: 2017-07-06 00:41:39,254 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.10.0-26-generic, x86_64: installed nvidia-304, 304.135, 4.10.0-28-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:7214] InstallationDate: Installed on 2017-06-15 (33 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=240611b4-d432-4f3c-8456-44874ab831c6 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-07-05 (12 days ago) dmi.bios.date: 11/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-PRO 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.:bvr0402:bd11/29/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-PRO: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.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Tue Jul 18 14:16:14 2017 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709881] Re: [xenial] QT5 gles support for arm64 architecture
Hi Dmitry, Thanks for the information about version difference. Is there no possibility to update the Xenial's qt5 build as yakkety because the Xenial is LTS version and I need the feature for the arm64. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1709881 Title: [xenial] QT5 gles support for arm64 architecture Status in qtbase-opensource-src package in Ubuntu: Invalid Bug description: According to the Xenial's build log, it did not build as gles for the arm64 even though it should be built with -opengl es2 option. > debian/rules gles2_architectures := armel armhf arm64 ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH), $(gles2_architectures))) extra_configure_opts += -opengl es2 else extra_configure_opts += -opengl desktop endif Here is the xenial's build log and it shows OpenGL as Desktop version. - Xenial build log: https://launchpadlibrarian.net/319422529/buildlog_ubuntu-xenial-arm64.qtbase-opensource-src_5.5.1+dfsg-16ubuntu7.5_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... desktop However, the zesty's build log shows OpenGL as ES2. - Zesty build log: https://launchpadlibrarian.net/328680692/buildlog_ubuntu-zesty-arm64.qtbase-opensource-src_5.7.1+dfsg-2ubuntu4~1.17.04.1_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... yes (OpenGL ES 2.0+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1709881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711020] Re: package linux-image-extra-4.4.0-91-generic 4.4.0-91.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1711020 Title: package linux-image-extra-4.4.0-91-generic 4.4.0-91.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I don't know. System alerted me of an issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-91-generic 4.4.0-91.114 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-headers-4.4.0-91-generic: Remove linux-headers-4.4.0-91: Remove linux-image-extra-4.4.0-91-generic: Remove linux-image-4.4.0-91-generic: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wayne 1743 F pulseaudio Date: Tue Aug 15 22:48:09 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=7fc64e3c-6cfa-4c1f-9988-fb544d761dac InstallationDate: Installed on 2016-12-17 (241 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire 5733Z ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic root=UUID=56c8a1ca-2097-4f05-ac45-97f85b1480c9 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12 SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-91-generic 4.4.0-91.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5733Z dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnAcer:bvrV1.07:bd11/07/2011:svnAcer:pnAspire5733Z:pvrV1.07:rvnAcer:rnAspire5733Z:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire 5733Z dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1711020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711033] Re: errors
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1711033 Title: errors Status in xorg package in Ubuntu: New Bug description: not sure what happened ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 CasperVersion: 1.376.2 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 Aug 16 04:48:49 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b0] LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) MachineType: Dell Inc. Inspiron N5110 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 034W60 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd04/18/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn034W60:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 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: Wed Aug 16 04:10:35 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1711033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711132] Re: make crashed with SIGSEGV in variable_hash_1()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1711132 Title: make crashed with SIGSEGV in variable_hash_1() Status in make-dfsg package in Ubuntu: New Bug description: i don't know ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: make 4.1-9.1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 Date: Wed Aug 16 17:37:40 2017 Dependencies: gcc-7-base 7.1.0-13ubuntu1 libc6 2.24-12ubuntu1 libgcc1 1:7.1.0-13ubuntu1 ExecutablePath: /usr/bin/make InstallationDate: Installed on 2017-08-02 (14 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1) ProcCmdline: make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia-375/375.82/build ProcEnviron: LC_COLLATE=C PATH=(custom, no user) LC_NUMERIC=C LANG=en_US.UTF-8 TERM=linux SegvAnalysis: Segfault happened at: 0x698913f28f: movzbl (%rax),%esi PC (0x698913f28f) ok source "(%rax)" (0x406989d94420) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: make-dfsg StacktraceTop: ?? () hash_find_slot () target_environment () ?? () ?? () Title: make crashed with SIGSEGV in hash_find_slot() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1711132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711107] Re: package apport 2.20.4-0ubuntu4 failed to install/upgrade: サブプロセス 新しい pre-removal スクリプト はエラー終了ステータス 127 を返しました
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1711107 Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: サブプロセス 新しい pre-removal スクリプト はエラー終了ステータス 127 を返しました Status in apport package in Ubuntu: New Bug description: cannot detect wireless devices ProblemType: Package DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed Aug 16 19:10:08 2017 ErrorMessage: サブプロセス 新しい pre-removal スクリプト はエラー終了ステータス 127 を返しました InstallationDate: Installed on 2017-08-06 (10 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64(20170427.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: apport Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: サブプロセス 新しい pre-removal スクリプト はエラー終了ステータス 127 を返しました UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1711107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1691096] Re: mysql in lxd fails to start with systemd 233: failed at step KEYRING
This also affects Artful running a sid container in lxd. Nothing is particularly MySQL specific I here I think, since the failure happens before MySQL runs at all. The only special systemd things I see in the service unit are the use of ExecStartPre on a bash script and PermissionsStartOnly=true. The full service unit definition is: # MySQL systemd service file [Unit] Description=MySQL Community Server After=network.target [Install] WantedBy=multi-user.target [Service] User=mysql Group=mysql PermissionsStartOnly=true ExecStartPre=/usr/share/mysql/mysql-systemd-start pre ExecStart=/usr/sbin/mysqld ExecStartPost=/usr/share/mysql/mysql-systemd-start post TimeoutSec=600 Restart=on-failure RuntimeDirectory=mysqld RuntimeDirectoryMode=755 -- 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/1691096 Title: mysql in lxd fails to start with systemd 233: failed at step KEYRING Status in systemd package in Ubuntu: Triaged Status in systemd source package in Artful: Triaged Bug description: artful unprivileged container on a xenial host xnox hinted that https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7 might be related With systemd 233, mysql-server-5.7 in an artful lxd unprivileged container fails to start: Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=237/KEYRING) May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set invocation ID on control group /system.slice/mysql.service, ignoring: Operation not permitted (...) May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We start with systemd-232 in the artful lxd: ubuntu@intense-sunbeam:~$ apt-cache policy systemd systemd: Installed: 232-21ubuntu3 Candidate: 233-6ubuntu1 Version table: 233-6ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages *** 232-21ubuntu3 100 100 /var/lib/dpkg/status Then we install mysql-server-5.7: ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7 ... Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ... update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → /lib/systemd/system/mysql.service. Processing triggers for libc-bin (2.24-9ubuntu2) ... Processing triggers for systemd (232-21ubuntu3) ... Which starts just fine: ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. ... We then upgrade systemd: ubuntu@intense-sunbeam:~$ sudo apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libpam-systemd libsystemd0 (...) Setting up libpam-systemd:amd64 (233-6ubuntu1) ... mysql is still running: ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. (...) But restarting mysql fails: ubuntu@intense-sunbeam:~$ sudo service mysql restart Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) More logs attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1691096] Re: mysql in lxd fails to start with systemd 233: failed at step KEYRING
AFAICT, /usr/share/mysql/mysql-systemd-start is never run: Aug 18 10:53:51 autopkgtest-lxd-mnbewo systemd[1]: Starting MySQL Community Server... -- Subject: Unit mysql.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit mysql.service has begun starting up. Aug 18 10:53:51 autopkgtest-lxd-mnbewo systemd[1649]: mysql.service: Failed at step KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied -- Subject: Process /usr/share/mysql/mysql-systemd-start could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /usr/share/mysql/mysql-systemd-start could not be executed and failed. -- -- The error number returned by this process is 13. -- 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/1691096 Title: mysql in lxd fails to start with systemd 233: failed at step KEYRING Status in systemd package in Ubuntu: Triaged Status in systemd source package in Artful: Triaged Bug description: artful unprivileged container on a xenial host xnox hinted that https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7 might be related With systemd 233, mysql-server-5.7 in an artful lxd unprivileged container fails to start: Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=237/KEYRING) May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set invocation ID on control group /system.slice/mysql.service, ignoring: Operation not permitted (...) May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We start with systemd-232 in the artful lxd: ubuntu@intense-sunbeam:~$ apt-cache policy systemd systemd: Installed: 232-21ubuntu3 Candidate: 233-6ubuntu1 Version table: 233-6ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages *** 232-21ubuntu3 100 100 /var/lib/dpkg/status Then we install mysql-server-5.7: ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7 ... Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ... update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → /lib/systemd/system/mysql.service. Processing triggers for libc-bin (2.24-9ubuntu2) ... Processing triggers for systemd (232-21ubuntu3) ... Which starts just fine: ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. ... We then upgrade systemd: ubuntu@intense-sunbeam:~$ sudo apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libpam-systemd libsystemd0 (...) Setting up libpam-systemd:amd64 (233-6ubuntu1) ... mysql is still running: ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. (...) But restarting mysql fails: ubuntu@intense-sunbeam:~$ sudo service mysql restart Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) More logs attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
We can disable it for now: https://github.com/snapcore/snapd/pull/3763 -- 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/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in snapd: New Status in systemd package in Ubuntu: Fix Committed Bug description: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1709536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709881] Re: [xenial] QT5 gles support for arm64 architecture
Hi! It looks like you are quoting wrong debian/rules. Mine (5.5.1+dfsg- 16ubuntu7.5) have: gles2_architectures := armel armhf And arm64 was added to this list only in Yakkety and later versions. So not having OpenGL ES on arm64 is intentional in Xenial. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1709881 Title: [xenial] QT5 gles support for arm64 architecture Status in qtbase-opensource-src package in Ubuntu: Invalid Bug description: According to the Xenial's build log, it did not build as gles for the arm64 even though it should be built with -opengl es2 option. > debian/rules gles2_architectures := armel armhf arm64 ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH), $(gles2_architectures))) extra_configure_opts += -opengl es2 else extra_configure_opts += -opengl desktop endif Here is the xenial's build log and it shows OpenGL as Desktop version. - Xenial build log: https://launchpadlibrarian.net/319422529/buildlog_ubuntu-xenial-arm64.qtbase-opensource-src_5.5.1+dfsg-16ubuntu7.5_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... desktop However, the zesty's build log shows OpenGL as ES2. - Zesty build log: https://launchpadlibrarian.net/328680692/buildlog_ubuntu-zesty-arm64.qtbase-opensource-src_5.7.1+dfsg-2ubuntu4~1.17.04.1_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... yes (OpenGL ES 2.0+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1709881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709881] Re: [xenial] QT5 gles support for arm64 architecture
Gently ping about this issue :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1709881 Title: [xenial] QT5 gles support for arm64 architecture Status in qtbase-opensource-src package in Ubuntu: New Bug description: According to the Xenial's build log, it did not build as gles for the arm64 even though it should be built with -opengl es2 option. > debian/rules gles2_architectures := armel armhf arm64 ifeq ($(DEB_HOST_ARCH),$(findstring $(DEB_HOST_ARCH), $(gles2_architectures))) extra_configure_opts += -opengl es2 else extra_configure_opts += -opengl desktop endif Here is the xenial's build log and it shows OpenGL as Desktop version. - Xenial build log: https://launchpadlibrarian.net/319422529/buildlog_ubuntu-xenial-arm64.qtbase-opensource-src_5.5.1+dfsg-16ubuntu7.5_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... desktop However, the zesty's build log shows OpenGL as ES2. - Zesty build log: https://launchpadlibrarian.net/328680692/buildlog_ubuntu-zesty-arm64.qtbase-opensource-src_5.7.1+dfsg-2ubuntu4~1.17.04.1_BUILDING.txt.gz OpenGL / OpenVG: EGL .. yes OpenGL ... yes (OpenGL ES 2.0+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1709881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710145] Re: "mid-click lower" not woking with headerbar in Wayland session
** Tags added: wayland ** Package changed: meta-gnome3 (Ubuntu) => wayland (Ubuntu) ** Changed in: wayland (Ubuntu) Status: New => Confirmed ** Changed in: wayland (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1710145 Title: "mid-click lower" not woking with headerbar in Wayland session Status in wayland package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 - WAYLAND SESSION Mid-click lower (it can be set with Tweaks → Windows → Titlebar Actions → Middle Click → Lower) doesn't work any more with all the Gnome applications that use the new titlebar (headerbar). It's still working with some apps that use the classic titlebar (like Firefox, Gimp, Nemo..). While with other apps (LibreOffice, Transmission..) it seems to have problems too. No problem at all using the old Xorg-session. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome (not installed) ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 11 13:53:20 2017 InstallationDate: Installed on 2017-07-20 (22 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170719) SourcePackage: meta-gnome3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1710145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710145] [NEW] "mid-click lower" not woking with headerbar in Wayland session
You have been subscribed to a public bug: Ubuntu 17.10 - WAYLAND SESSION Mid-click lower (it can be set with Tweaks → Windows → Titlebar Actions → Middle Click → Lower) doesn't work any more with all the Gnome applications that use the new titlebar (headerbar). It's still working with some apps that use the classic titlebar (like Firefox, Gimp, Nemo..). While with other apps (LibreOffice, Transmission..) it seems to have problems too. No problem at all using the old Xorg-session. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome (not installed) ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 11 13:53:20 2017 InstallationDate: Installed on 2017-07-20 (22 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170719) SourcePackage: meta-gnome3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland wayland-session -- "mid-click lower" not woking with headerbar in Wayland session https://bugs.launchpad.net/bugs/1710145 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
this is in snapd since may https://github.com/snapcore/snapd/pull/3270 why did this break all of a sudden ? -- 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/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in snapd: New Status in systemd package in Ubuntu: Fix Committed Bug description: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1709536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685705] Re: package libgstreamer-plugins-base0.10-0 0.10.36-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Deb
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gst-plugins-base0.10 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1685705 Title: package libgstreamer-plugins-base0.10-0 0.10.36-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer-plugins- base0.10-0:amd64 Status in gst-plugins-base0.10 package in Ubuntu: Confirmed Bug description: i having issue with this plugin ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgstreamer-plugins-base0.10-0 0.10.36-1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Apr 24 11:13:18 2017 DpkgTerminalLog: Preparing to unpack .../libgstreamer-plugins-base0.10-0_0.10.36-2ubuntu0.1_amd64.deb ... Unpacking libgstreamer-plugins-base0.10-0:amd64 (0.10.36-2ubuntu0.1) over (0.10.36-1) ... dpkg: error processing archive /var/cache/apt/archives/libgstreamer-plugins-base0.10-0_0.10.36-2ubuntu0.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer-plugins-base0.10-0:amd64 DuplicateSignature: package:libgstreamer-plugins-base0.10-0:0.10.36-1 Unpacking libgstreamer-plugins-base0.10-0:amd64 (0.10.36-2ubuntu0.1) over (0.10.36-1) ... dpkg: error processing archive /var/cache/apt/archives/libgstreamer-plugins-base0.10-0_0.10.36-2ubuntu0.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer-plugins-base0.10-0:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer-plugins-base0.10-0:amd64 InstallationDate: Installed on 2016-03-30 (389 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: gst-plugins-base0.10 Title: package libgstreamer-plugins-base0.10-0 0.10.36-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer-plugins-base0.10-0:amd64 UpgradeStatus: Upgraded to xenial on 2016-05-01 (357 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base0.10/+bug/1685705/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711545] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1711545/+attachment/4934697/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1711545 Title: glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64 -linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x002601a1d1e0 *** Status in glib2.0 package in Ubuntu: New Bug description: Got that crash while upgrading some packages: Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ... Unpacking ubuntu-minimal (1.395) over (1.394) ... Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ... Unpacking ubuntu-standard (1.395) over (1.394) ... Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ... Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ... Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ... Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ... Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ... Unpacking ubuntu-settings (17.10.12) over (17.10.11) ... Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ... Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ... Processing triggers for gconf2 (3.2.6-4ubuntu1) ... Processing triggers for mime-support (3.60ubuntu1) ... Setting up ubuntu-web-launchers (17.10.12) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... Setting up ubuntu-settings (17.10.12) ... Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ... No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x002601a1d1e0 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9] /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421] /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a] === Memory map: 25ff8c6000-25ff8d r-xp 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 25ffacf000-25ffad r--p 9000 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 25ffad-25ffad1000 rw-p a000 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 26018a6000-2601b18000 rw-p 00:00 0 [heap] 7fb4df48f000-7fb4df4a5000 r-xp 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a6000-7fb4df981000 r--p 08:04 522184 /usr/lib/locale/locale-archive 7fb4df981000-7fb4df999000 r-xp 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb9b000-7fb4dfb9f000 rw-p 00:00 0 7fb4dfb9f000-7fb4dfc11000 r-xp 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfc11000-7fb4dfe1 ---p 00072000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfe1-7fb4dfe11000 r--p 00071000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfe11000-7fb4dfe12000 rw-p 00072000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfe12000-7fb4dffce000 r-xp 08:04 54 /lib/x86_64-linux-gnu/libc-2.24.so 7f
[Touch-packages] [Bug 1684973] Re: Crashes (segfault) under Wayland in Ubuntu GNOME 17.04
Thanks for your report. I cannot reproduce this issue on artful. Could you please try again and tell us if you can reproduce and the detailed steps to reproduce it. Thanks. ** Changed in: gdebi (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1684973 Title: Crashes (segfault) under Wayland in Ubuntu GNOME 17.04 Status in gdebi package in Ubuntu: Incomplete Bug description: While trying to run gdebi-gtk to install a .deb package, program won't open under Wayland session. Running from terminal produces the following: No protocol specified Unable to init server: Could not connect: Connection refused No protocol specified Unable to init server: Could not connect: Connection refused No protocol specified Unable to init server: Could not connect: Connection refused Segmentation fault (core dumped) BUG DISCOVERED RUNNING Ubuntu GNOME 17.04 x64 GNOME 3.24.0 desktop environment Wayland session Linux kernel 4.10.0-19-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1684973/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711545] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1711545/+attachment/4934698/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1711545/+attachment/4934682/+files/CoreDump.gz ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Medium ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1711545 Title: glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64 -linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x002601a1d1e0 *** Status in glib2.0 package in Ubuntu: New Bug description: Got that crash while upgrading some packages: Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ... Unpacking ubuntu-minimal (1.395) over (1.394) ... Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ... Unpacking ubuntu-standard (1.395) over (1.394) ... Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ... Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ... Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ... Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ... Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ... Unpacking ubuntu-settings (17.10.12) over (17.10.11) ... Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ... Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ... Processing triggers for gconf2 (3.2.6-4ubuntu1) ... Processing triggers for mime-support (3.60ubuntu1) ... Setting up ubuntu-web-launchers (17.10.12) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... Setting up ubuntu-settings (17.10.12) ... Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ... No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x002601a1d1e0 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9] /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421] /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a] === Memory map: 25ff8c6000-25ff8d r-xp 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 25ffacf000-25ffad r--p 9000 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 25ffad-25ffad1000 rw-p a000 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 26018a6000-2601b18000 rw-p 00:00 0 [heap] 7fb4df48f000-7fb4df4a5000 r-xp 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a6000-7fb4df981000 r--p 08:04 522184 /usr/lib/locale/locale-archive 7fb4df981000-7fb4df999000 r-xp 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb9b000-7fb4dfb9f000 rw-p 00:00 0 7fb4dfb9f000-7fb4dfc11000 r-xp 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfc11000-7fb4dfe1 ---p 00072000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfe1-7fb4dfe11000 r--p 00071000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb
[Touch-packages] [Bug 1711545] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1711545/+attachment/4934696/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1711545 Title: glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64 -linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x002601a1d1e0 *** Status in glib2.0 package in Ubuntu: New Bug description: Got that crash while upgrading some packages: Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ... Unpacking ubuntu-minimal (1.395) over (1.394) ... Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ... Unpacking ubuntu-standard (1.395) over (1.394) ... Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ... Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ... Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ... Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ... Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ... Unpacking ubuntu-settings (17.10.12) over (17.10.11) ... Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ... Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ... Processing triggers for gconf2 (3.2.6-4ubuntu1) ... Processing triggers for mime-support (3.60ubuntu1) ... Setting up ubuntu-web-launchers (17.10.12) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... Setting up ubuntu-settings (17.10.12) ... Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ... No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x002601a1d1e0 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9] /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421] /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a] === Memory map: 25ff8c6000-25ff8d r-xp 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 25ffacf000-25ffad r--p 9000 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 25ffad-25ffad1000 rw-p a000 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 26018a6000-2601b18000 rw-p 00:00 0 [heap] 7fb4df48f000-7fb4df4a5000 r-xp 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a6000-7fb4df981000 r--p 08:04 522184 /usr/lib/locale/locale-archive 7fb4df981000-7fb4df999000 r-xp 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb9b000-7fb4dfb9f000 rw-p 00:00 0 7fb4dfb9f000-7fb4dfc11000 r-xp 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfc11000-7fb4dfe1 ---p 00072000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfe1-7fb4dfe11000 r--p 00071000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfe11000-7fb4dfe12000 rw-p 00072000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfe12000-7fb4dffce000 r-xp 08:04 54 /lib/x86_64-linux-gnu/libc-2.24.so 7fb4dffce000-7
[Touch-packages] [Bug 1711545] glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x0000002601a1d1e0 ***
StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fb4dffa0f68 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ar_ptr=0x0, ptr=, str=0x7fb4dffa0f90 "munmap_chunk(): invalid pointer", action=) at malloc.c:5049 munmap_chunk (p=) at malloc.c:2857 __GI___libc_free (mem=) at malloc.c:2980 g_free (mem=) at ../../../../glib/gmem.c:189 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1711545 Title: glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64 -linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x002601a1d1e0 *** Status in glib2.0 package in Ubuntu: New Bug description: Got that crash while upgrading some packages: Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ... Unpacking ubuntu-minimal (1.395) over (1.394) ... Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ... Unpacking ubuntu-standard (1.395) over (1.394) ... Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ... Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ... Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ... Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ... Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ... Unpacking ubuntu-settings (17.10.12) over (17.10.11) ... Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ... Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ... Processing triggers for gconf2 (3.2.6-4ubuntu1) ... Processing triggers for mime-support (3.60ubuntu1) ... Setting up ubuntu-web-launchers (17.10.12) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... Setting up ubuntu-settings (17.10.12) ... Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ... No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x002601a1d1e0 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9] /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421] /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a] === Memory map: 25ff8c6000-25ff8d r-xp 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 25ffacf000-25ffad r--p 9000 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 25ffad-25ffad1000 rw-p a000 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 26018a6000-2601b18000 rw-p 00:00 0 [heap] 7fb4df48f000-7fb4df4a5000 r-xp 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a6000-7fb4df981000 r--p 08:04 522184 /usr/lib/locale/locale-archive 7fb4df981000-7fb4df999000 r-xp 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb9b000-7fb4dfb9f000 rw-p 00:00 0 7fb4dfb9f000-7fb4dfc11000 r-xp 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfc11000-7fb4dfe1 ---p 00072000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfe1-7fb4dfe11000 r--p 00071000 08:04 523149 /li
[Touch-packages] [Bug 1711545] [NEW] glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x0000002601a1d1e0 **
Public bug reported: Got that crash while upgrading some packages: Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ... Unpacking ubuntu-minimal (1.395) over (1.394) ... Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ... Unpacking ubuntu-standard (1.395) over (1.394) ... Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ... Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ... Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ... Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ... Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ... Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ... Unpacking ubuntu-settings (17.10.12) over (17.10.11) ... Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ... Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ... Processing triggers for gconf2 (3.2.6-4ubuntu1) ... Processing triggers for mime-support (3.60ubuntu1) ... Setting up ubuntu-web-launchers (17.10.12) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... Setting up ubuntu-settings (17.10.12) ... Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ... No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x002601a1d1e0 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9] /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421] /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a] === Memory map: 25ff8c6000-25ff8d r-xp 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 25ffacf000-25ffad r--p 9000 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 25ffad-25ffad1000 rw-p a000 08:04 523111 /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas 26018a6000-2601b18000 rw-p 00:00 0 [heap] 7fb4df48f000-7fb4df4a5000 r-xp 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 /lib/x86_64-linux-gnu/libgcc_s.so.1 7fb4df6a6000-7fb4df981000 r--p 08:04 522184 /usr/lib/locale/locale-archive 7fb4df981000-7fb4df999000 r-xp 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 /lib/x86_64-linux-gnu/libpthread-2.24.so 7fb4dfb9b000-7fb4dfb9f000 rw-p 00:00 0 7fb4dfb9f000-7fb4dfc11000 r-xp 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfc11000-7fb4dfe1 ---p 00072000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfe1-7fb4dfe11000 r--p 00071000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfe11000-7fb4dfe12000 rw-p 00072000 08:04 523149 /lib/x86_64-linux-gnu/libpcre.so.3.13.3 7fb4dfe12000-7fb4dffce000 r-xp 08:04 54 /lib/x86_64-linux-gnu/libc-2.24.so 7fb4dffce000-7fb4e01cd000 ---p 001bc000 08:04 54 /lib/x86_64-linux-gnu/libc-2.24.so 7fb4e01cd000-7fb4e01d1000 r--p 001bb000 08:04 54 /lib/x86_64-linux-gnu/libc-2.24.so 7fb4e01d1000-7fb4e01d3000 rw-p 001bf000 08:04 54 /lib/x86_64-linux-gnu/libc-2.24.so 7fb4e01d3000-7fb4e01d7000 rw-p 00:00 0 7fb4e01d7000-7fb4e02e8000 r-xp 08:04 523029 /lib/x86_64-linux-gnu/libglib-2.0.so.0.5304.0 7fb4e02e8000-7fb4e04e8000 ---p 00111000 08:04 523029 /lib/x86_64-linux-gnu/libglib-2.0.so.0.5304.0 7fb4e04e8000-7fb4e04e9000 r--
[Touch-packages] [Bug 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power
** Changed in: libmatemixer (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1580394 Title: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power Status in alsa-driver package in Ubuntu: New Status in libmatemixer package in Ubuntu: Invalid Bug description: I have noticed that when I am on battery power on a Dell Latitude 3340 laptop with headphones plugged in , and there is no audio playing on the computer, there is a consistent static sound that comes through the headphones at a constant volume that is not affected by changing the volume level. I think it may be picking up some kind of analog loopback signal because keyboard presses and disk activity seem to influence the noise. When I plug the power cable into the laptop , the static immediately goes away. I reported this earlier to the upstream Linux Kernel bug tracker, but it seems to be fixed in any distro running a 4.4 kernel or greater that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This make me think it is not a kernel level issue and is found somewhere either in the audio settings on Ubuntu MATE or a pulseaudio bug. I cannot reproduce it on any other 16.04 distro version, but it also affects all the 14.04.4 distros as well. Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent the static. The BIOS Firmware version is up to date. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu-mate 1718 F pulseaudio /dev/snd/controlC0: ubuntu-mate 1718 F pulseaudio CasperVersion: 1.376 CurrentDesktop: MATE Date: Wed May 11 00:43:52 2016 LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711079] Re: Mobile bradband doesnt work after suspend/logout
mobile-broadband-provider-info 20140317-1 ** Package changed: ubuntu => mobile-broadband-provider-info (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mobile-broadband-provider- info in Ubuntu. https://bugs.launchpad.net/bugs/1711079 Title: Mobile bradband doesnt work after suspend/logout Status in mobile-broadband-provider-info package in Ubuntu: New Bug description: When I turn on my laptop (HP EliteBook Folio 9470m), I can use my sim card internet, but when I log in after my laptop was suspended, I can not connect to network again. I need to restart it to connect again. Ubuntu version 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1711079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 882878] Re: With IPv6 disabled, openssh will not forward X connections
I don't like to delta for that with upstream agreement - as it is a hard change in behavior. I checked latest openssh git and the code is still as-is. @CJWatson - with your openssh experience - what do you think about suggesting the Suse patch [1] or [2] - actually[3] is the latest version of the same - to upstream? [1]: https://bugzilla.novell.com/attachment.cgi?id=580591&action=diff [2]: https://build.opensuse.org/package/view_file/openSUSE:Factory/openssh/openssh-6.5p1-X_forward_with_disabled_ipv6.patch?rev=1c09c84b8dda320105cf7b59928951c4 [3]: https://build.opensuse.org/package/view_file/openSUSE:Factory/openssh/openssh-7.2p2-X_forward_with_disabled_ipv6.patch?expand=1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/882878 Title: With IPv6 disabled, openssh will not forward X connections Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Status in openssh package in openSUSE: Fix Released Bug description: If you disable IPv6 in /etc/sysctl.conf sshd will not forward X11. It logs the failue in /var/log/auth.log Oct 27 18:49:26 uscps002 sshd[14722]: Accepted password for root from 172.20.10.50 port 60322 ssh2 Oct 27 18:49:26 uscps002 sshd[14722]: pam_unix(sshd:session): session opened for user root by (uid=0) Oct 27 18:49:27 uscps002 sshd[14722]: error: Failed to allocate internet-domain X11 display socket. Aparently the compiled sshd version will not try an ipv4 localhost if an ipv6 localhost does not exist. Placing the following line in /etc/ssh/sshd_config fixes the issue X11UseLocalHost no root@uscps002:/var/log# lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 root@uscps002:/var/log# root@uscps002:/var/log# uname -a Linux uscps002 3.0.0-12-server #20-Ubuntu SMP Fri Oct 7 16:36:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/882878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711079] [NEW] Mobile bradband doesnt work after suspend/logout
You have been subscribed to a public bug: When I turn on my laptop (HP EliteBook Folio 9470m), I can use my sim card internet, but when I log in after my laptop was suspended, I can not connect to network again. I need to restart it to connect again. Ubuntu version 16.04 LTS ** Affects: mobile-broadband-provider-info (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment xenial -- Mobile bradband doesnt work after suspend/logout https://bugs.launchpad.net/bugs/1711079 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mobile-broadband-provider-info in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp