[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
Thanks Andreas, yes I see it nearly everywhere as well. Also thanks to spot that I missed to uopdate impact - done. Discussion on the MP going on ... ** Description changed: [Impact] - * An explanation of the effects of the bug on users and - - * justification for backporting the fix to the stable release. - - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. + * NTP has new isolation features which makes it trigger apparmor issues. + * Those apparmor issues not only clutter the log and make other things +less readable, they also prevent ntp from reporting its actual +messages. + * Fix is opening the apparmor profile to follow ntp through the +disconnect by the isolation feature. [Test Case] - * This is hard to trigger, but then also not. Which means it is not -entirely sorted out when it triggers and when not, but the following -does trigger it in tests of Pitti and also mine (while at the same time -sometimes it does not - mabye I had other guests or kvm instead of lxd) + * This is hard to trigger, but then also not. Which means it is not + entirely sorted out when it triggers and when not, but the following + does trigger it in tests of Pitti and also mine (while at the same time + sometimes it does not - mabye I had other guests or kvm instead of lxd) - * First install ntp in Artful (or above unless fixed) -* Then you have to cause soemthing that ntp "needs" to complain about - in my case I had spawned more virtual guests and NTP failed to bind - on their virtual interface, but you could setup anything else that it - fails on after the initial start (there it passed over to private - TMP) -* Once an issue triggers instead of the error in syslog you'll see the - apparmor Deny like: -apparmor="DENIED" operation="sendmsg" info="Failed name lookup - -disconnected path" error=-13 profile="/usr/sbin/ntpd" -name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" -requested_mask="w" denied_mask="w" fsuid=0 ouid=0 + * First install ntp in Artful (or above unless fixed) + * Then you have to cause soemthing that ntp "needs" to complain about + in my case I had spawned more virtual guests and NTP failed to bind + on their virtual interface, but you could setup anything else that it + fails on after the initial start (there it passed over to private + TMP) + * Once an issue triggers instead of the error in syslog you'll see the + apparmor Deny like: + apparmor="DENIED" operation="sendmsg" info="Failed name lookup - + disconnected path" error=-13 profile="/usr/sbin/ntpd" + name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" + requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [Regression Potential] - * We are slightly opening up the apparmor profile which is far lower risk -than adding more constraints. So safe from that POV. + * We are slightly opening up the apparmor profile which is far lower risk + than adding more constraints. So safe from that POV. - * OTOH one could think this might be a security issue, but in fact this -isn't a new suggestion if you take a look at [1] with an ack by Seth of -the Security Team. + * OTOH one could think this might be a security issue, but in fact this + isn't a new suggestion if you take a look at [1] with an ack by Seth of + the Security Team. [Other Info] - - * n/a + + * n/a [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu-stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Artful: Triaged Status in ntp source package in
[Touch-packages] [Bug 1738958] [NEW] Ordering of start and apparmor reload upgrade can cause issues
Public bug reported: We found this in ntp, but I think it is a general issue in the ordering. The tail of NTPs postinst looks like that: if [ "$1" = "triggered" ]; then # The default configuration uses a leapfile from tzdata # restart ntp on changes invoke-rc.d ntp try-restart || true fi #DEBHELPER# Therefore on an upgrade it is restarted one more time restarted "the old way". E.g. if there are changes delivered by #DEBHELPER# generated maintainer script snippets e.g. apparmor profiles, then this try-restart will be without them. Also this might be a bad "combo" with "--no-restart-after-upgrade" that is set in debian/rules. --no-restart-after-upgrade Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to be stopped in the prerm script and started again in the postinst script. I think no-restart-after-upgrade + try-restart means try-restart will do nothing as "try-restart" on the (now stopped service) does nothing. So what happens seems to be this: 1. prerm stops ntp 2. postinst try-restart does nothing as it is stopped (not important to this cases but good to know) 3. postinst dh_installinit will "invoke-rc.d ntp start" with the old profile 4. postinst dh_apparmor reloads apparmor profiles So if you have issues triggered by the start on #3 before the new profile is in place due to #4 this causes issues. I think #3 (as well as similar systemd things) and #4 should be reordered so that the new profile is loaded BEFORE ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Ordering of try-restart and debhelper on upgrade can cause issues + Ordering of start and apparmor reload upgrade can cause issues -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1738958 Title: Ordering of start and apparmor reload upgrade can cause issues Status in apparmor package in Ubuntu: New Status in ntp package in Ubuntu: New Bug description: We found this in ntp, but I think it is a general issue in the ordering. The tail of NTPs postinst looks like that: if [ "$1" = "triggered" ]; then # The default configuration uses a leapfile from tzdata # restart ntp on changes invoke-rc.d ntp try-restart || true fi #DEBHELPER# Therefore on an upgrade it is restarted one more time restarted "the old way". E.g. if there are changes delivered by #DEBHELPER# generated maintainer script snippets e.g. apparmor profiles, then this try-restart will be without them. Also this might be a bad "combo" with "--no-restart-after-upgrade" that is set in debian/rules. --no-restart-after-upgrade Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to be stopped in the prerm script and started again in the postinst script. I think no-restart-after-upgrade + try-restart means try-restart will do nothing as "try-restart" on the (now stopped service) does nothing. So what happens seems to be this: 1. prerm stops ntp 2. postinst try-restart does nothing as it is stopped (not important to this cases but good to know) 3. postinst dh_installinit will "invoke-rc.d ntp start" with the old profile 4. postinst dh_apparmor reloads apparmor profiles So if you have issues triggered by the start on #3 before the new profile is in place due to #4 this causes issues. I think #3 (as well as similar systemd things) and #4 should be reordered so that the new profile is loaded BEFORE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1738958/+subscrip
[Touch-packages] [Bug 1737662] Comment bridged from LTC Bugzilla
--- Comment From indira.pr...@in.ibm.com 2017-12-19 01:56 EDT--- Please update the bug once daily build picks up the fix for installer issue, we are waiting for the fix as both NV and KVM test environments are blocked with test execution. Regards, Indira -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1737662 Title: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system Status in The Ubuntu-power-systems project: Fix Committed Status in busybox package in Ubuntu: Fix Released Status in debian-installer package in Ubuntu: Fix Released Bug description: Problem Description: === Ubuntu1804 installer shows Debootstrap warning messages and not able to proceed with installation Steps to re-create: == > on Witherspoon test system, tried to install ubuntu1804 using netboot install. > Selected mirror path:http://10.xx.11.31:3128 [!] Choose a mirror of the Ubuntu archive ? ? ? Please select an Ubuntu archive mirror. You should use a mirror in ? ? your country or region if you do not know which mirror has the best ? ? Internet connection to you. ? ? ? ? Usually, .archive.ubuntu.com is a good choice. ? ? ? ? Ubuntu archive mirror: ? ? ? ? us.ports.ubuntu.com ? ? ? ?? ? ? ??? > Able to select the disks ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ?/dev/nvme0n1 - 409.6 GB Unknown ? ?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB ? ?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB ? ? ? ?? ? ? ??? > Started installing base system ??? Installing the base system ? ? ?6% ? ? ? ? Retrieving libc6... ? ? ? ??? > Then seen Debootstrap warning messages as below ??? [!!] Install the base system ??? ? ? ?? ? ? Debootstrap warning? ? ? ? Warning: Failure trying to run: chroot /target dpkg-deb -f ? ? ? ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ? ? ? Ex? ? ? ? ? ? ? ? ? ?? ??? [!!] Install the base system ?? ? ? ? ? ? ? Debootstrap warning? ? ? ? W
[Touch-packages] [Bug 1738936] [NEW] package libgcc1 1:4.9.1-0ubuntu1 failed to install/upgrade: there is no script in the new version of the package - giving up
Public bug reported: release update via ssh ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgcc1 1:4.9.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Tue Dec 19 18:50:31 2017 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.13 DuplicateSignature: package:libgcc1:1:4.9.1-0ubuntu1:there is no script in the new version of the package - giving up ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2013-04-21 (1703 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.0.1ubuntu2.17 SourcePackage: gccgo-4.9 Title: package libgcc1 1:4.9.1-0ubuntu1 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to xenial on 2017-12-19 (0 days ago) ** Affects: gccgo-4.9 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gccgo-4.9 in Ubuntu. https://bugs.launchpad.net/bugs/1738936 Title: package libgcc1 1:4.9.1-0ubuntu1 failed to install/upgrade: there is no script in the new version of the package - giving up Status in gccgo-4.9 package in Ubuntu: New Bug description: release update via ssh ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgcc1 1:4.9.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Tue Dec 19 18:50:31 2017 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.13 DuplicateSignature: package:libgcc1:1:4.9.1-0ubuntu1:there is no script in the new version of the package - giving up ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2013-04-21 (1703 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.0.1ubuntu2.17 SourcePackage: gccgo-4.9 Title: package libgcc1 1:4.9.1-0ubuntu1 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to xenial on 2017-12-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1738936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738936] Re: package libgcc1 1:4.9.1-0ubuntu1 failed to install/upgrade: there is no script in the new version of the package - giving up
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gccgo-4.9 in Ubuntu. https://bugs.launchpad.net/bugs/1738936 Title: package libgcc1 1:4.9.1-0ubuntu1 failed to install/upgrade: there is no script in the new version of the package - giving up Status in gccgo-4.9 package in Ubuntu: New Bug description: release update via ssh ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgcc1 1:4.9.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Tue Dec 19 18:50:31 2017 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.13 DuplicateSignature: package:libgcc1:1:4.9.1-0ubuntu1:there is no script in the new version of the package - giving up ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2013-04-21 (1703 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.0.1ubuntu2.17 SourcePackage: gccgo-4.9 Title: package libgcc1 1:4.9.1-0ubuntu1 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to xenial on 2017-12-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1738936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703377] Re: Gnome online account login prevents paste or autotype
Same situation here but not specific to Ubuntu. Same situation on Debian Stretch with Gnome 3.22.2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1703377 Title: Gnome online account login prevents paste or autotype Status in gnome-online-accounts package in Ubuntu: New Bug description: On entering Login data to an online account such as google. Using keepass as password manager I now can not enter my password via paste nor via autotype. Trying any of them results in an invalid password. Ubuntu 16.10 - GNOME Shell 3.20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1703377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735088] Re: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Had to boot to 4.10.0.42 or 4.14.0-11 to get command to run. Issue seen on both 4.13.0-17-generic and 4.13.0-19-generic. Another issue that accompanied this issue was that after updating to 17.10 PC would no longer reboot or shutdown. Updating kernel manually to 4.14.0-11 and manually booting to 4.14.0-11 linux-image resolved issue. I was then able to install software needed, update-initramfs, boot, and reboot normally. Currently running with 17.10 package set and newer kernel. -- 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/1735088 Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in initramfs-tools package in Ubuntu: New Bug description: running update-initramfs -u never completes. Any package install that that attempts to update initramfs sit and hangs. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Tue Nov 28 23:51:18 2017 ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2016-11-01 (393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1735088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379628] Re: gedit crashed with signal 5 in _XReply()
[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Expired -- 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/1379628 Title: gedit crashed with signal 5 in _XReply() Status in gtk+3.0 package in Ubuntu: Expired Bug description: Don't recall exactly what happened, but gedit crashed while I was typing up a document. :( ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: gedit 3.10.4-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Oct 9 18:54:33 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-09-26 (13 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) ProcCmdline: gedit ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XIGetClientPointer () from /usr/lib/x86_64-linux-gnu/libXi.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gedit crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1379628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721472] Re: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
[Expired for console-setup (Ubuntu) because there has been no activity for 60 days.] ** Changed in: console-setup (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1721472 Title: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in console-setup package in Ubuntu: Expired Bug description: Post install for console-setup failed. Had to edit postinstall script to exit 0 to install other packages ProblemType: Package DistroRelease: Ubuntu 17.10 Package: console-setup 1.166ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 4 09:24:06 2017 DpkgTerminalLog: Setting up keyboard-configuration (1.166ubuntu6) ... Setting up console-setup-linux (1.166ubuntu6) ... Setting up console-setup (1.166ubuntu6) ... [1mdpkg:[0m error processing package console-setup (--configure): subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: console-setup Title: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1721472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738925] [NEW] PCI/internal sound card not detected
Public bug reported: Audio issue precipitated when linux kernel was updated to 4.13.0-19 from 4.13.0-17 in Ubuntu 17.10. Loading kernel 4.13.0-17 fixes the issue. Currently using alsa-base 1.0.25. I expected to have sound options for onboard audio, hdmi video card audio, and headphones, but a dummy output was listed instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Dec 18 22:03:24 2017 InstallationDate: Installed on 2010-11-27 (2578 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to artful on 2017-10-22 (57 days ago) dmi.bios.date: 08/25/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78 PLUS 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.:bvr2301:bd08/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-26T22:10:32.289419 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1738925 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Audio issue precipitated when linux kernel was updated to 4.13.0-19 from 4.13.0-17 in Ubuntu 17.10. Loading kernel 4.13.0-17 fixes the issue. Currently using alsa-base 1.0.25. I expected to have sound options for onboard audio, hdmi video card audio, and headphones, but a dummy output was listed instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Dec 18 22:03:24 2017 InstallationDate: Installed on 2010-11-27 (2578 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to artful on 2017-10-22 (57 days ago) dmi.bios.date: 08/25/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78 PLUS 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.:bvr2301:bd08/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-26T22:10:32.289419 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1738925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724285] Re: Diffie Hellman parameter created with paramter "-dsaparam" stopped working with slapd
[Expired for openldap (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openldap (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1724285 Title: Diffie Hellman parameter created with paramter "-dsaparam" stopped working with slapd Status in openldap package in Ubuntu: Expired Bug description: If the dh parameter is created with openssl and the '-dsaparam' parameter is set the resulting diffi hellman paramter can not be added to the openldap server. If a existing dhparam is replaced with one which is create with '-dsaparam' slapd wont start anymore. From the openssl manpage: -dsaparam If this option is used, DSA rather than DH parameters are read or created; they are converted to DH format. Otherwise, "strong" primes (such that (p-1)/2 is also prime) will be used for DH parameter generation. DH parameter generation with the -dsaparam option is much faster, and the recommended exponent length is shorter, which makes DH key exchange more efficient. Beware that with such DSA-style DH parameters, a fresh DH key should be created for each use to avoid small-subgroup attacks that may be possible otherwise. # Works with openldap 2.4.44+dfsg-3ubuntu2.1 and 2.4.45+dfsg-1ubuntu1 openssl dhparam -outform PEM -out dhparam.pem 2048 # Works only with 2.4.44+dfsg-3ubuntu2.1 openssl dhparam -dsaparam -outform PEM -out dhparam.pem 2048 Adding to ldap: dn: cn=config changetype: modify replace: olcTLSDHParamFile olcTLSDHParamFile: /etc/ldap/ssl/dhparam.pem Error message from ldap server: ldap_modify: Other (e.g., implementation specific) error (80) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1724285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695872] Re: GNOME on Wayland session could not be started from lightdm
** Changed in: lightdm (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1695872 Title: GNOME on Wayland session could not be started from lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: GNOME on Wayland session could not be started from lightdm ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 5 11:23:22 2017 InstallationDate: Installed on 2016-09-09 (268 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system
This bug was fixed in the package debian-installer - 20101020ubuntu526 --- debian-installer (20101020ubuntu526) bionic; urgency=medium * Rebuild with fixed busybox 1:1.27.2-2ubuntu3. LP: #1737662. -- Steve Langasek Mon, 18 Dec 2017 17:06:18 -0800 ** Changed in: debian-installer (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 busybox in Ubuntu. https://bugs.launchpad.net/bugs/1737662 Title: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system Status in The Ubuntu-power-systems project: Fix Committed Status in busybox package in Ubuntu: Fix Released Status in debian-installer package in Ubuntu: Fix Released Bug description: Problem Description: === Ubuntu1804 installer shows Debootstrap warning messages and not able to proceed with installation Steps to re-create: == > on Witherspoon test system, tried to install ubuntu1804 using netboot install. > Selected mirror path:http://10.xx.11.31:3128 [!] Choose a mirror of the Ubuntu archive ? ? ? Please select an Ubuntu archive mirror. You should use a mirror in ? ? your country or region if you do not know which mirror has the best ? ? Internet connection to you. ? ? ? ? Usually, .archive.ubuntu.com is a good choice. ? ? ? ? Ubuntu archive mirror: ? ? ? ? us.ports.ubuntu.com ? ? ? ?? ? ? ??? > Able to select the disks ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ?/dev/nvme0n1 - 409.6 GB Unknown ? ?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB ? ?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB ? ? ? ?? ? ? ??? > Started installing base system ??? Installing the base system ? ? ?6% ? ? ? ? Retrieving libc6... ? ? ? ??? > Then seen Debootstrap warning messages as below ??? [!!] Install the base system ??? ? ? ?? ? ? Debootstrap warning? ? ? ? Warning: Failure trying to run: chroot /target dpkg-deb -f ? ? ? ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ? ? ? Ex? ? ? ? ? ? ? ? ? ?? ??? [!!] Install the base system ?? ? ? ? ? ?
[Touch-packages] [Bug 1738605] Re: Yesterday I had sound. Today I don't.
Thanks. That crash file is an unrelated program (graphics rather than audio), but also attaching crash files is a security risk for you. So the attachment has been removed. If you have more crash files in future please use the 'ubuntu-bug' command to submit them. ** Attachment removed: "_usr_bin_compiz.1000.crash" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738605/+attachment/5024347/+files/_usr_bin_compiz.1000.crash -- 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/1738605 Title: Yesterday I had sound. Today I don't. Status in pulseaudio package in Ubuntu: Incomplete Bug description: Happens every single time I install Ubuntu on every single computer I have ever install it on. This time, it doesn't seem to have a solution. Shows audio in volume control under output devices, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: master 1752 F pulseaudio /dev/snd/pcmC0D0c: master 1752 F...m pulseaudio /dev/snd/pcmC0D0p: master 1752 F...m pulseaudio /dev/snd/controlC0: master 1752 F pulseaudio Date: Sat Dec 16 23:23:28 2017 InstallationDate: Installed on 2017-12-15 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738205] Re: no sound while playing audio/video
Thanks. That seems to say the same thing: !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - No I'm not familiar with pulseaudio on Ubuntu 14.04 but you may want to try starting it manually like in my 16.04 system: /usr/bin/pulseaudio --start --log-target=syslog If that works and yours never really crashed then it sounds like a login session problem (failing to start the daemon) rather than a pulseaudio problem. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1738205 Title: no sound while playing audio/video Status in pulseaudio package in Ubuntu: Incomplete Bug description: Not able to hear audio through headset on ubuntu 14.04. Also, volume icon is not visible.. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-80-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu Dec 14 18:47:12 2017 InstallationDate: Installed on 2016-02-04 (679 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Acer dmi.bios.version: P01-A4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Veriton M6610 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAcer:bvrP01-A4:bd07/26/2011:svnAcer:pnVeritonSeries:pvr:rvnAcer:rnVeritonM6610:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton Series dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738404] Re: Bluetooth sound extreme low quality
OK. If you wish to use Ubuntu 17.10 or later and still have a problem then please try the next step: Find an older kernel more in line with what 17.04 had (kernel version 4.10 or older): http://kernel.ubuntu.com /~kernel-ppa/mainline/?C=N;O=D If you can find the kernel version it stopped working in then we can work with the kernel team to get a fix. -- 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/1738404 Title: Bluetooth sound extreme low quality Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded today from ubuntu 17.04 to ubuntu 17.10. I use 3 different bluetooth audio devices ( BT earphones, BT speaker, BT BOSE Soundlink speaker) , all of them worked properly on 17.04. Since the upgrade, the sound gets continuous interruptions/cracking. These sound interruptions and cracking are so annoying that I cannot keep on listening to music. I could relate this to the fact that a new BT stack has replaced the former in Ubuntu. If I use wired devices (hdmi connected screen+audio, the sound quality is good and as before) so the issue is related to the use of the new Bluetooth stack. I have not found a way to parameterise it neither. I have not found any similar report. "apport" seems not ot exist in thise version, I cannot find and execute it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738838] Re: bluetooth does not turn on; settings interfaces are nonsensical
** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1738838 Title: bluetooth does not turn on; settings interfaces are nonsensical Status in bluez package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: See video. I have installed bluetooth, blueman, bluez but it makes no difference to a broken interface to control bluetooth under Gnome 17.10, as shown in the attached video. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluetooth 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 17 22:32:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-18 (30 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: bnep btusb bluetooth MachineType: LENOVO 20BXCTO1WW PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash psmouse.synaptics_intertouch=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738907] Re: Bluetooth audio latency / delay increasing on video streamig
If the delay increases over time then mathematically it sounds like the output is consuming bits slower than the input. So /maybe/ you have 48kHz audio being played at 44.1kHz but I would have thought that would be noticeable (sounding distorted - too low). And even if that's not the problem, the delay should hit a limit via some buffering limit, after which it turns into skipping (bug 405294). Another thought is to see the suggestion in bug 1677202. -- 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/1738907 Title: Bluetooth audio latency / delay increasing on video streamig Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: With my bluetooth headset (A2DP audio protocole) when I watch videos streaming with Google Chrome for example. there is a delay increasing between audio and video. I tried to change and set up the audio latency, but the delay increase, as much as I play bigger video ubuntu 17.04 or 17.10 64bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738907] Re: Bluetooth audio latency / delay increasing on video streamig
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags added: a2dp -- 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/1738907 Title: Bluetooth audio latency / delay increasing on video streamig Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: With my bluetooth headset (A2DP audio protocole) when I watch videos streaming with Google Chrome for example. there is a delay increasing between audio and video. I tried to change and set up the audio latency, but the delay increase, as much as I play bigger video ubuntu 17.04 or 17.10 64bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677202] Re: Sound playback delays
Stuart, can we assume you're using wired audio and not Bluetooth? -- 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/1677202 Title: Sound playback delays Status in pulseaudio package in Ubuntu: New Bug description: Sound playback on my machine seems to be delayed. Playing an error beep hangs for half a second or so before playing, making tab completion extremely irritating (because the completion itself also hangs); starting a video or music track is silent for the first second or so. This seems to be fixed, as per http://askubuntu.com/questions/218444/sound-output-starts- delayed/440787#440787, by disabling pulseaudio's "module-suspend-on- idle" feature. I don't need this feature at all because my machine is a desktop box without a battery, permanently plugged into power, and therefore any minimal power saving it produces is far outweighed by the annoyance. However, since other people don't experience this problem, perhaps it's chipset specific? I also experience Audacity taking a long time to start up, which also seems to have been helped by this fix. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 29 11:56:24 2017 InstallationDate: Installed on 2014-04-07 (1087 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to xenial on 2016-08-04 (237 days ago) dmi.bios.date: 12/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1707 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: PCS dmi.chassis.type: 3 dmi.chassis.vendor: PC SPECIALIST dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnPCSPECIALIST:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2017-03-29T11:51:11.884294 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1677202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567796] Re: It is sometimes unable to find DELL WWAN module.
** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1567796 Title: It is sometimes unable to find DELL WWAN module. Status in OEM Priority Project: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: I have a DELL WWAN module (DW5580) on my platform. Normally it could be detect and used in Ubuntu 16.04 daily image. However it is sometimes unusable and can not be detected. After debugging, we found there is an upstream patch that can fix the issue: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8a386218690aeff7e2c923a14f91da7bbc046ed2 Please merge the fix to modem manager to fix the issue. Ubuntu Xenial (daily image) Release: 16.04 modemmanager: Installed: 1.4.12-1ubuntu1 Candidate: 1.4.12-1ubuntu1 Version table: *** 1.4.12-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status * 2017-06-20 Update details for SRU [Impact] DELL WWAN module (DW5580) is sometimes unusable and can not be detected by ModemManager. The fix consisted in the correct initialization of a "retry" variable in modem's probing. Without this initialization, the "retry" variable might assume random big values, forcing the modem to retry the same step a semi-infinite number of times. [Test Case] 1. Start/restart the ModemManager service with debug messages enabled a. Open ModemManager.service file and add the flag --debug to the ExecStart entry ExecStart=/usr/local/sbin/ModemManager --debug b. run systemctl daemon-reload c. run systemctl restart Modemmanager 2. Connect Dell WWAN module DW5580 (if the modem is integrated, skip this step) 3. Open ModemManager logs: journalctl -fu ModemManager 4. ModemManager logs show that the service is continuously sending AT command "AT+CGMI" preventing the modem to be recognized [Regression Potential] Considering the nature of the fix (a variable that was not initialized), I can not think of a real potential regression and the patch has been tested and showed no issues so far. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1567796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1712921] Re: enabling networkd appears to eat up entropy
Verification-done: xenial: 0.32~16.04.3 zesty: 0.32~17.04.1 artful: 0.32~17.10.1 netplan running at boot-time no longer appears to block on missing entropy; does not appear to be calling to uuid_generate() while setting this up for the networkd generator (uuid generation is still required for NetworkManager and also appears to still work). ** Tags removed: verification-needed-artful verification-needed-xenial verification-needed-zesty ** Tags added: verification-done-artful verification-done-xenial verification-done-zesty ** Tags removed: verification-needed ** Tags removed: adt-fail -- 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/1712921 Title: enabling networkd appears to eat up entropy Status in nplan package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Status in nplan source package in Xenial: Fix Committed Status in openssh source package in Xenial: New Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Status in openssh source package in Zesty: New Status in systemd source package in Zesty: New Status in nplan source package in Artful: Fix Committed Status in openssh source package in Artful: Fix Released Status in systemd source package in Artful: Triaged Status in nplan source package in Bionic: Fix Released Status in openssh source package in Bionic: Fix Released Status in systemd source package in Bionic: Triaged Bug description: [Impact] Booting systems have a limited amount of entropy, especially in some of the cloud cases. We should avoid using it up unnecessarily. [Test cases] == netplan == 1) Boot system with netplan config; using networkd renderer 2) Validate that it starts and does not cause undue delay. 2b) strace nplan at boottime (the netplan generator at /lib/systemd/system-generators/netplan) and validate it does not call get_random() / uuid_generate(). 3) Validate that config with NetworkManager renderer generates UUIDs. [Regression potential] Netplan depends on UUID generation to create correct networkManager configuration for VLANs. This is a specific use-case that is typically not hit, but any failure to generate valid NetworkManager configuration would be a regression from this SRU. --- enabling networkd appears to eat up entropy as seen in openssh autopkgtest failing, when networkd is enabled by default. See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with triggers systemd/234-2ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1712921/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
** Tags added: risk -- 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/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Confirmed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option. Remove file 50-bluetooth-hci-auto-poweron.rules located in /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be powered off now. [Regression Potential] Cannot think of any [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738784] Re: package libxml2 2.9.1+dfsg1-3ubuntu4.12 failed to install/upgrade: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1738784 Title: package libxml2 2.9.1+dfsg1-3ubuntu4.12 failed to install/upgrade: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) Status in libxml2 package in Ubuntu: New Bug description: Please let me know what is the solutions of this error? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxml2 2.9.1+dfsg1-3ubuntu4.12 ProcVersionSignature: Ubuntu 3.13.0-133.182-generic 3.13.11-ckt39 Uname: Linux 3.13.0-133-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Dec 18 18:41:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DuplicateSignature: package:libxml2:2.9.1+dfsg1-3ubuntu4.12:64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) ErrorMessage: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) InstallationDate: Installed on 2017-10-09 (70 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: libxml2 Title: package libxml2 2.9.1+dfsg1-3ubuntu4.12 failed to install/upgrade: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1738784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738785] Re: package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to install/upgrade: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because lib
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcursor in Ubuntu. https://bugs.launchpad.net/bugs/1738785 Title: package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to install/upgrade: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) Status in libxcursor package in Ubuntu: Incomplete Bug description: Please let me know what is the solutions of this error? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxcursor1 1:1.1.14-1ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-133.182-generic 3.13.11-ckt39 Uname: Linux 3.13.0-133-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.27 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: Mon Dec 18 18:41:01 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-133-generic, x86_64: installed oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-137-generic, x86_64: built oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-45-generic, x86_64: installed wifi-bt-dw1820b, 1.1, 3.13.0-133-generic, x86_64: installed wifi-bt-dw1820b, 1.1, 3.13.0-45-generic, x86_64: installed DuplicateSignature: package:libxcursor1:1:1.1.14-1ubuntu0.14.04.1:63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) ErrorMessage: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06f0] InstallationDate: Installed on 2017-10-09 (70 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude 3460 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-133-generic.efi.signed root=UUID=7daf6ad4-13cf-4d52-bba5-f4cf9cfacda8 ro locale=en_IN quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: libxcursor Title: package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to install/upgrade: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0XPKP0 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/02/2017:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn0XPKP0:rvrA04:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3460 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1.01 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Dec 18 11:05:50 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5264 vendor CMN xserver.version: 2:1.15.1-0ubuntu2.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcursor/+bug/1738785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1526956] Re: klibc does not support rfc3442; needed for netboot
** Changed in: klibc (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1526956 Title: klibc does not support rfc3442; needed for netboot Status in klibc package in Ubuntu: Confirmed Status in klibc package in Debian: Confirmed Bug description: klibc does not support classless static routes. If classes routing is used for a netboot device (NFS, iscsi) these devices will fail to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1526956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738785] Re: package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to install/upgrade: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because lib
If you're going to have both amd64 and i386 versions of a package installed then you have to upgrade them in lockstep. Thanks ** Changed in: libxcursor (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcursor in Ubuntu. https://bugs.launchpad.net/bugs/1738785 Title: package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to install/upgrade: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) Status in libxcursor package in Ubuntu: Incomplete Bug description: Please let me know what is the solutions of this error? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxcursor1 1:1.1.14-1ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-133.182-generic 3.13.11-ckt39 Uname: Linux 3.13.0-133-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.27 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: Mon Dec 18 18:41:01 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-133-generic, x86_64: installed oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-137-generic, x86_64: built oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-45-generic, x86_64: installed wifi-bt-dw1820b, 1.1, 3.13.0-133-generic, x86_64: installed wifi-bt-dw1820b, 1.1, 3.13.0-45-generic, x86_64: installed DuplicateSignature: package:libxcursor1:1:1.1.14-1ubuntu0.14.04.1:63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) ErrorMessage: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06f0] InstallationDate: Installed on 2017-10-09 (70 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude 3460 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-133-generic.efi.signed root=UUID=7daf6ad4-13cf-4d52-bba5-f4cf9cfacda8 ro locale=en_IN quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: libxcursor Title: package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to install/upgrade: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0XPKP0 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/02/2017:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn0XPKP0:rvrA04:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3460 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1.01 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Dec 18 11:05:50 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5264 vendor CMN xserver.version: 2:1.15.1-0ubuntu2.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcursor/+bug/1738785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1738784] Re: package libxml2 2.9.1+dfsg1-3ubuntu4.12 failed to install/upgrade: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is
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 libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1738784 Title: package libxml2 2.9.1+dfsg1-3ubuntu4.12 failed to install/upgrade: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) Status in libxml2 package in Ubuntu: New Bug description: Please let me know what is the solutions of this error? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxml2 2.9.1+dfsg1-3ubuntu4.12 ProcVersionSignature: Ubuntu 3.13.0-133.182-generic 3.13.11-ckt39 Uname: Linux 3.13.0-133-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Dec 18 18:41:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DuplicateSignature: package:libxml2:2.9.1+dfsg1-3ubuntu4.12:64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) ErrorMessage: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) InstallationDate: Installed on 2017-10-09 (70 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: libxml2 Title: package libxml2 2.9.1+dfsg1-3ubuntu4.12 failed to install/upgrade: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1738784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738784] Re: package libxml2 2.9.1+dfsg1-3ubuntu4.12 failed to install/upgrade: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is
Hello, if you're going to install both amd64 and i386 versions of a package you have to upgrade them in lockstep. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1738784 Title: package libxml2 2.9.1+dfsg1-3ubuntu4.12 failed to install/upgrade: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) Status in libxml2 package in Ubuntu: New Bug description: Please let me know what is the solutions of this error? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxml2 2.9.1+dfsg1-3ubuntu4.12 ProcVersionSignature: Ubuntu 3.13.0-133.182-generic 3.13.11-ckt39 Uname: Linux 3.13.0-133-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Dec 18 18:41:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DuplicateSignature: package:libxml2:2.9.1+dfsg1-3ubuntu4.12:64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) ErrorMessage: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) InstallationDate: Installed on 2017-10-09 (70 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: libxml2 Title: package libxml2 2.9.1+dfsg1-3ubuntu4.12 failed to install/upgrade: 64.1026:package libxml2:amd64 2.9.1+dfsg1-3ubuntu4.12 cannot be configured because libxml2:i386 is at a different version (2.9.1+dfsg1-3ubuntu4.10) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1738784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738606] Re: package cups-server-common 1.7.2-0ubuntu1.8 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status `ha
** Tags removed: need-duplicate-check -- 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/1738606 Title: package cups-server-common 1.7.2-0ubuntu1.8 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status `half-installed') Status in cups package in Ubuntu: New Bug description: Processing triggers for libc-bin (2.19-0ubuntu6.13) ... Errors were encountered while processing: cups-server-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-server-common 1.7.2-0ubuntu1.8 ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-80-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 CupsErrorLog: E [10/Dec/2017:11:53:47 +0530] Filter "rastertopwg" not found. E [17/Dec/2017:12:19:55 +0530] Filter "rastertopwg" not found. E [17/Dec/2017:13:15:06 +0530] Filter "rastertopwg" not found. Date: Sun Dec 17 13:31:43 2017 Dependencies: DuplicateSignature: package:cups-server-common:1.7.2-0ubuntu1.8:package cups-server-common is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package cups-server-common is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2017-09-16 (92 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Inspiron 3542 PackageArchitecture: all Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic root=UUID=c380b433-4a9c-4fe4-bddb-d05eb1dae6d8 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic root=UUID=c380b433-4a9c-4fe4-bddb-d05eb1dae6d8 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: cups Title: package cups-server-common 1.7.2-0ubuntu1.8 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0KHNVP dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0KHNVP:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738785] Re: package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to install/upgrade: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because lib
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 libxcursor in Ubuntu. https://bugs.launchpad.net/bugs/1738785 Title: package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to install/upgrade: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) Status in libxcursor package in Ubuntu: Incomplete Bug description: Please let me know what is the solutions of this error? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxcursor1 1:1.1.14-1ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-133.182-generic 3.13.11-ckt39 Uname: Linux 3.13.0-133-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.27 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: Mon Dec 18 18:41:01 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-133-generic, x86_64: installed oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-137-generic, x86_64: built oem-audio-hda-daily, 0.201508251546~ubuntu14.04.1, 3.13.0-45-generic, x86_64: installed wifi-bt-dw1820b, 1.1, 3.13.0-133-generic, x86_64: installed wifi-bt-dw1820b, 1.1, 3.13.0-45-generic, x86_64: installed DuplicateSignature: package:libxcursor1:1:1.1.14-1ubuntu0.14.04.1:63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) ErrorMessage: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06f0] InstallationDate: Installed on 2017-10-09 (70 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude 3460 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-133-generic.efi.signed root=UUID=7daf6ad4-13cf-4d52-bba5-f4cf9cfacda8 ro locale=en_IN quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: libxcursor Title: package libxcursor1 1:1.1.14-1ubuntu0.14.04.1 failed to install/upgrade: 63.9316:package libxcursor1:amd64 1:1.1.14-1ubuntu0.14.04.1 cannot be configured because libxcursor1:i386 is at a different version (1:1.1.14-1) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0XPKP0 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/02/2017:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn0XPKP0:rvrA04:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3460 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1.01 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Dec 18 11:05:50 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5264 v
[Touch-packages] [Bug 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system
** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Changed in: debian-installer (Ubuntu) Status: New => In Progress ** Changed in: debian-installer (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1737662 Title: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system Status in The Ubuntu-power-systems project: Fix Committed Status in busybox package in Ubuntu: Fix Released Status in debian-installer package in Ubuntu: Fix Committed Bug description: Problem Description: === Ubuntu1804 installer shows Debootstrap warning messages and not able to proceed with installation Steps to re-create: == > on Witherspoon test system, tried to install ubuntu1804 using netboot install. > Selected mirror path:http://10.xx.11.31:3128 [!] Choose a mirror of the Ubuntu archive ? ? ? Please select an Ubuntu archive mirror. You should use a mirror in ? ? your country or region if you do not know which mirror has the best ? ? Internet connection to you. ? ? ? ? Usually, .archive.ubuntu.com is a good choice. ? ? ? ? Ubuntu archive mirror: ? ? ? ? us.ports.ubuntu.com ? ? ? ?? ? ? ??? > Able to select the disks ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ?/dev/nvme0n1 - 409.6 GB Unknown ? ?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB ? ?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB ? ? ? ?? ? ? ??? > Started installing base system ??? Installing the base system ? ? ?6% ? ? ? ? Retrieving libc6... ? ? ? ??? > Then seen Debootstrap warning messages as below ??? [!!] Install the base system ??? ? ? ?? ? ? Debootstrap warning? ? ? ? Warning: Failure trying to run: chroot /target dpkg-deb -f ? ? ? ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ? ? ? Ex? ? ? ? ? ? ? ? ? ?? ??? [!!] Install the base system ?? ? ? ? ? ? ? Debootstrap warning? ? ? ? Warnin
[Touch-packages] [Bug 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system
** Branch linked: lp:~vorlon/debian-installer/ppc64el-netboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1737662 Title: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system Status in The Ubuntu-power-systems project: Fix Committed Status in busybox package in Ubuntu: Fix Released Status in debian-installer package in Ubuntu: Fix Committed Bug description: Problem Description: === Ubuntu1804 installer shows Debootstrap warning messages and not able to proceed with installation Steps to re-create: == > on Witherspoon test system, tried to install ubuntu1804 using netboot install. > Selected mirror path:http://10.xx.11.31:3128 [!] Choose a mirror of the Ubuntu archive ? ? ? Please select an Ubuntu archive mirror. You should use a mirror in ? ? your country or region if you do not know which mirror has the best ? ? Internet connection to you. ? ? ? ? Usually, .archive.ubuntu.com is a good choice. ? ? ? ? Ubuntu archive mirror: ? ? ? ? us.ports.ubuntu.com ? ? ? ?? ? ? ??? > Able to select the disks ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ?/dev/nvme0n1 - 409.6 GB Unknown ? ?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB ? ?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB ? ? ? ?? ? ? ??? > Started installing base system ??? Installing the base system ? ? ?6% ? ? ? ? Retrieving libc6... ? ? ? ??? > Then seen Debootstrap warning messages as below ??? [!!] Install the base system ??? ? ? ?? ? ? Debootstrap warning? ? ? ? Warning: Failure trying to run: chroot /target dpkg-deb -f ? ? ? ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ? ? ? Ex? ? ? ? ? ? ? ? ? ?? ??? [!!] Install the base system ?? ? ? ? ? ? ? Debootstrap warning? ? ? ? Warning: See the log for details ? ? ? Extracting zlib1g.? ? ? ? ? ? ? ?
[Touch-packages] [Bug 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system
This is not yet resolved because debian-installer needs rebuilt to pick the fixed busybox up into the d-i initramfs. I have uploaded this now. ** Changed in: debian-installer (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 busybox in Ubuntu. https://bugs.launchpad.net/bugs/1737662 Title: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system Status in The Ubuntu-power-systems project: Fix Committed Status in busybox package in Ubuntu: Fix Released Status in debian-installer package in Ubuntu: Fix Committed Bug description: Problem Description: === Ubuntu1804 installer shows Debootstrap warning messages and not able to proceed with installation Steps to re-create: == > on Witherspoon test system, tried to install ubuntu1804 using netboot install. > Selected mirror path:http://10.xx.11.31:3128 [!] Choose a mirror of the Ubuntu archive ? ? ? Please select an Ubuntu archive mirror. You should use a mirror in ? ? your country or region if you do not know which mirror has the best ? ? Internet connection to you. ? ? ? ? Usually, .archive.ubuntu.com is a good choice. ? ? ? ? Ubuntu archive mirror: ? ? ? ? us.ports.ubuntu.com ? ? ? ?? ? ? ??? > Able to select the disks ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ?/dev/nvme0n1 - 409.6 GB Unknown ? ?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB ? ?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB ? ? ? ?? ? ? ??? > Started installing base system ??? Installing the base system ? ? ?6% ? ? ? ? Retrieving libc6... ? ? ? ??? > Then seen Debootstrap warning messages as below ??? [!!] Install the base system ??? ? ? ?? ? ? Debootstrap warning? ? ? ? Warning: Failure trying to run: chroot /target dpkg-deb -f ? ? ? ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ? ? ? Ex? ? ? ? ? ? ? ? ? ?? ??? [!!] Install the base system ?? ? ? ? ? ? ? Debootstrap warning? ? ? ? Warning: See the log for details ?
[Touch-packages] [Bug 1738606] Re: package cups-server-common 1.7.2-0ubuntu1.8 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status `ha
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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1738606 Title: package cups-server-common 1.7.2-0ubuntu1.8 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status `half-installed') Status in cups package in Ubuntu: New Bug description: Processing triggers for libc-bin (2.19-0ubuntu6.13) ... Errors were encountered while processing: cups-server-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-server-common 1.7.2-0ubuntu1.8 ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-80-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 CupsErrorLog: E [10/Dec/2017:11:53:47 +0530] Filter "rastertopwg" not found. E [17/Dec/2017:12:19:55 +0530] Filter "rastertopwg" not found. E [17/Dec/2017:13:15:06 +0530] Filter "rastertopwg" not found. Date: Sun Dec 17 13:31:43 2017 Dependencies: DuplicateSignature: package:cups-server-common:1.7.2-0ubuntu1.8:package cups-server-common is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package cups-server-common is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2017-09-16 (92 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Inspiron 3542 PackageArchitecture: all Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic root=UUID=c380b433-4a9c-4fe4-bddb-d05eb1dae6d8 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic root=UUID=c380b433-4a9c-4fe4-bddb-d05eb1dae6d8 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: cups Title: package cups-server-common 1.7.2-0ubuntu1.8 failed to install/upgrade: package cups-server-common is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0KHNVP dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0KHNVP:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1738606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738581] Re: apport is leaking environment variables (including passwords!) to public bug reports
Indeed you should assume these credentials have been acquired already and reset them as appropriate. Thank you for the report. -- 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/1738581 Title: apport is leaking environment variables (including passwords!) to public bug reports Status in apport package in Ubuntu: New Bug description: See the bug report https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564 created with ubuntu-bug. Apport includes the file JournalErrors.txt This file includes e.g. the following line. Dez 16 19:11:31 hostname /usr/lib/gdm3/gdm-x-session[9679]: dbus-update-activation-environment: setting MPD_HOST=...@.xxx.org Normally it would be not problem that gdm-x-session write this to the journal, because the journal is not intended to be published on the internet. Setting confidential informations via environment is maybe not the best idea, but a legal procedure and for `mpc` the only way to set this information. IMHO the apport utility is here the problem, because it includes the file with risky information to a public visible bug report. Note: I manually delete the attachment in the mentioned bug report. But how can I sure that a web crawlser hasn't read/preserved that attachment? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738581/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1526956] Re: klibc does not support rfc3442; needed for netboot
Patch attached to Debian bug report https://bugs.debian.org/884716 ** Bug watch added: Debian Bug tracker #884716 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884716 ** Also affects: klibc (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884716 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1526956 Title: klibc does not support rfc3442; needed for netboot Status in klibc package in Ubuntu: Confirmed Status in klibc package in Debian: Unknown Bug description: klibc does not support classless static routes. If classes routing is used for a netboot device (NFS, iscsi) these devices will fail to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1526956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709135] Re: add bond primary parameter
Verification-done zesty with 0.32~17.04.01: Tested bond in balance-tlb mode and active-backup mode, both correctly set the primary for the bond. ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- 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/1709135 Title: add bond primary parameter Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Released Status in nplan source package in Zesty: Fix Committed Status in systemd source package in Zesty: Fix Released Status in nplan source package in Artful: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] Some complex bond configurations require setting a "primary" interface for the bond, or setting this greatly improves performance on the network bond. [Test case] See below for a configuration example. 1) Apply configuration on a system with netplan. 2) Run 'netplan apply' 3) Validate that netplan apply does not return with an error 4) Validate that netplan properly sets the "primary_slave" value on the bond. This can be verified by looking at /sys/class/net//bonding/primary_slave. 5) Validate that there are no parsing errors from systemd-networkd in the journalctl [Regression potential] If existing configuration fails to be parsed, or lack of primary interface breaks configuration for existing bonds, this would be a regression caused by this update. --- ifenslave/eni support a bond parameter: bond-primary which accepts an interface name that can be used to tell the kernel bonding driver which interface it should preferred in active-backup (and other modes). This config option is missing in netplan. % cat bond-primary.yaml network: version: 2 ethernets: eth0: match: driver: virtio ens4: match: driver: e1000 bonds: bond0: parameters: mode: active-backup mii-monitor-interval: 100 primary: e1000 dhcp4: true % ./generate -r `pwd`/target Error in network definition /home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 column 8: unknown key primary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738884] Re: python 3.6 ubuntu 16.04 needs updated lib
Python 3.6 is not part of 16.04 and so no package that contains extension modules has them built for python 3.6. 17.10 has everything built for 3.6 and obviously 18.04 will too. ** Changed in: python-apt (Ubuntu) Status: New => Invalid -- 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/1738884 Title: python 3.6 ubuntu 16.04 needs updated lib Status in python-apt package in Ubuntu: Invalid Bug description: 16.04 comes with apt_pkg.cpython-35m-x86_64-linux-gnu.so but places it in the /usr/lib/python3/dist-packages directory, not the /usr/lib/python3.5/dist-packages directory. I'm guessing that apt isn't adding the 3.6 version correctly when installing python3.6, as we are getting errors in modules that depend on this when using py3.6 ( error is "not found apt_pkg" ) regretfully beyond us to know if the problem is here or in how py3.6 is maintained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1738884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738907] [NEW] Bluetooth audio latency / delay increasing on video streamig
Public bug reported: With my bluetooth headset (A2DP audio protocole) when I watch videos streaming with Google Chrome for example. there is a delay increasing between audio and video. I tried to change and set up the audio latency, but the delay increase, as much as I play bigger video ubuntu 17.04 or 17.10 64bit ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1738907 Title: Bluetooth audio latency / delay increasing on video streamig Status in bluez package in Ubuntu: New Bug description: With my bluetooth headset (A2DP audio protocole) when I watch videos streaming with Google Chrome for example. there is a delay increasing between audio and video. I tried to change and set up the audio latency, but the delay increase, as much as I play bigger video ubuntu 17.04 or 17.10 64bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738746] Re: /usr/bin/vlc:6:qt_message_fatal:QMessageLogger::fatal:init_platform:QGuiApplicationPrivate::createPlatformIntegration:QGuiApplicationPrivate::createEventDispatcher
So Qt still doesn't get its dependencies right? ** Package changed: vlc (Ubuntu) => qtbase-opensource-src (Ubuntu) -- 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/1738746 Title: /usr/bin/vlc:6:qt_message_fatal:QMessageLogger::fatal:init_platform:QGuiApplicationPrivate::createPlatformIntegration:QGuiApplicationPrivate::createEventDispatcher Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding vlc. This problem was most recently seen with package version 3.0.0~rc1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/677957cdc1692a92544001d6111d0c9e8eacc234 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1738746/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738429] Re: systemd crashed with SIGABRT
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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1738429 Title: systemd crashed with SIGABRT Status in systemd package in Ubuntu: New Bug description: I am concerned there is some sort of code that has attached to the firmware of all of my devices. the more i look, the more questions i find ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 15 06:43:00 2017 ExecutablePath: /lib/systemd/systemd LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcCmdline: systemd --test ProcEnviron: LANG=C.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no User Name) ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 06/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd06/07/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1738429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738746] [NEW] /usr/bin/vlc:6:qt_message_fatal:QMessageLogger::fatal:init_platform:QGuiApplicationPrivate::createPlatformIntegration:QGuiApplicationPrivate::createEventDispatcher
You have been subscribed to a public bug: The Ubuntu Error Tracker has been receiving reports about a problem regarding vlc. This problem was most recently seen with package version 3.0.0~rc1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/677957cdc1692a92544001d6111d0c9e8eacc234 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: artful bionic wily xenial yakkety zesty -- /usr/bin/vlc:6:qt_message_fatal:QMessageLogger::fatal:init_platform:QGuiApplicationPrivate::createPlatformIntegration:QGuiApplicationPrivate::createEventDispatcher https://bugs.launchpad.net/bugs/1738746 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src 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 1738382] Re: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Hello, this machine may have significant hardware issues. I don't know what to suggest but pay attention to the log entries as they are made, which hardware you're using at the moment, etc. Good luck. Thanks -- 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/1738382 Title: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apport package in Ubuntu: New Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 apport: Installed: 2.20.1-0ubuntu2.13 Candidate: 2.20.1-0ubuntu2.14 Version table: 2.20.1-0ubuntu2.14 500 500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages *** 2.20.1-0ubuntu2.13 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 2.20.1-0ubuntu2 500 500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://in.archive.ubuntu.com/ubuntu xenial/main i386 Packages The system reported this bug to me at start-up. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.13 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Fri Dec 15 06:24:34 2017 DuplicateSignature: package:apport:2.20.1-0ubuntu2.13 Unpacking linux-headers-generic-hwe-16.04 (4.10.0.42.44) over (4.10.0.40.42) ... dpkg: error processing package apport (--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-08-28 (108 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.13 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/apport/+bug/1738382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738899] [NEW] failed boot, hanging on CPU lockup
Public bug reported: fresh install unbuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.14 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: Mon Dec 18 22:52:32 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS740 [Radeon 2100] [1002:796e] (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp RS740 [Radeon 2100] [1565:0117] InstallationDate: Installed on 2017-11-26 (22 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: BIOSTAR Group A740G M2+ ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=UUID=bf3ff630-d843-47fc-8fff-004d1b054357 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A740G M2+ dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd05/02/2008:svnBIOSTARGroup:pnA740GM2+:pvr6.0:rvnBIOSTARGroup:rnA740GM2+:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0: dmi.product.name: A740G M2+ dmi.product.version: 6.0 dmi.sys.vendor: BIOSTAR Group version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 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: Mon Dec 18 22:47:08 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt USB Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1738899 Title: failed boot, hanging on CPU lockup Status in xorg package in Ubuntu: New Bug description: fresh install unbuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.14 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: Mon Dec 18 22:52:32 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS740 [Radeon 2100] [1002:796e] (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp RS740 [Radeon 2100] [1565:0117] InstallationDate: Installed on 2017-11-26 (22 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: BIOSTAR Group A740G M2+ ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=UUID=bf3ff630-d843-47fc-8fff-004d1b054357 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A740G M2+ dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: N
[Touch-packages] [Bug 1733700] Re: python tools do not understand 'non-magic' include rules
** Description changed:
- The apparmor_parser now supports 'include' rules in addition to
- '#include', but the python tools only understand '#include'. This
- manifested itself in Ubuntu in bug #1734038 (see
- https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/comments/15
- of that bug for details).
+ The apparmor parser supports 'include' and '#include' rules for
+ specifying absolute paths, but the python tools only understand include
+ rules for so called 'magic' '<>' file locations.
+
+ Reproducer:
+
+ $ mkdir /tmp/test1 /tmp/test2
+
+ $ cat /etc/apparmor.d/lp1733700
+ profile lp1733700 {
+ #include "/tmp/test1"
+ include "/tmp/test2"
+ }
+
+ $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
+
+ $ sudo aa-enforce /etc/apparmor.d/lp1733700
+
+ ERROR: Syntax Error: Missing '}' or ','. Reached end of file
+ /etc/apparmor.d/lp1733700 while inside profile lp1733700Note that the pr
+
+ Note that the original description said that changing the rule from
+ 'include' to '#include' fixed the issue when in reality it only allowed
+ the rule to parse as a comment instead of erroring.
+
+ = Original description =
+ The apparmor_parser now supports 'include' rules in addition to '#include',
but the python tools only understand '#include'. This manifested itself in
Ubuntu in bug #1734038 (see
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/comments/15 of
that bug for details).
Reproducer:
$ mkdir /tmp/test
$ cat /etc/apparmor.d/lp1733700
profile lp1733700 {
- include "/tmp/test"
+ include "/tmp/test"
}
$ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
ok
$ sudo aa-enforce /etc/apparmor.d/lp1733700
ERROR: Syntax Error: Missing '}' or ','. Reached end of file
/etc/apparmor.d/lp1733700 while inside profile lp1733700
Changing the 'include' to '#include' results in:
- $ sudo aa-enforce /etc/apparmor.d/lp1733700
+ $ sudo aa-enforce /etc/apparmor.d/lp1733700
Setting /etc/apparmor.d/lp1733700 to enforce mode.
At least aa-logprof is also affected.
= Original report =
On Ubuntu artful, I'm seeing the following behavior:
- $ aa-enforce usr.bin.chromium-browser
-
- ERROR: Syntax Error: Unknown line found in file
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
- include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,
+ $ aa-enforce usr.bin.chromium-browser
+
+ ERROR: Syntax Error: Unknown line found in file
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
+ include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,
I have never touched snap.core.3440.usr.lib.snapd.snap-confine.
This is snapd 2.28.5+17.10.
** Description changed:
The apparmor parser supports 'include' and '#include' rules for
specifying absolute paths, but the python tools only understand include
rules for so called 'magic' '<>' file locations.
Reproducer:
$ mkdir /tmp/test1 /tmp/test2
$ cat /etc/apparmor.d/lp1733700
profile lp1733700 {
- #include "/tmp/test1"
- include "/tmp/test2"
+ #include "/tmp/test1"
+ include "/tmp/test2"
}
$ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
$ sudo aa-enforce /etc/apparmor.d/lp1733700
ERROR: Syntax Error: Missing '}' or ','. Reached end of file
- /etc/apparmor.d/lp1733700 while inside profile lp1733700Note that the pr
+ /etc/apparmor.d/lp1733700 while inside profile lp1733700.
Note that the original description said that changing the rule from
'include' to '#include' fixed the issue when in reality it only allowed
the rule to parse as a comment instead of erroring.
= Original description =
The apparmor_parser now supports 'include' rules in addition to '#include',
but the python tools only understand '#include'. This manifested itself in
Ubuntu in bug #1734038 (see
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/comments/15 of
that bug for details).
Reproducer:
$ mkdir /tmp/test
$ cat /etc/apparmor.d/lp1733700
profile lp1733700 {
include "/tmp/test"
}
$ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
ok
$ sudo aa-enforce /etc/apparmor.d/lp1733700
ERROR: Syntax Error: Missing '}' or ','. Reached end of file
/etc/apparmor.d/lp1733700 while inside profile lp1733700
Changing the 'include' to '#include' results in:
$ sudo aa-enforce /etc/apparmor.d/lp1733700
Setting /etc/apparmor.d/lp1733700 to enforce mode.
At least aa-logprof is also affected.
= Original report =
On Ubuntu artful, I'm seeing the following behavior:
$ aa-enforce usr.bin.chromium-browser
ERROR: Syntax Error: Unknown line found in file
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,
I have never touched snap.core.3440.usr.lib.snapd.snap-confine.
This is
Re: [Touch-packages] [Bug 1738605] Re: Yesterday I had sound. Today I don't.
Hello, I went back to the very start and removed every audio related package I could and then reinstalled them and ran through all the trouble shooting lists I had and have fixed audio. I'm don't know what was causing it or what fixed it, but what was notable was that trying to stop/start PulseAudio manually was returning; daemon is already running when trying to start, and daemon is not running when trying to stop it. I think PulseAudio was the problem, but I think it was being caused by some ancillary thing that doesn't install/remove with it, as I purged/reinstalled PA and Alsa half a dozen times or so, but it wasn't fixed until I purged everything I could find related to audio. I'm unfamiliar with the .crash files, but maybe it will provide something useful for you. I wish I could be more helpful. GT On 12/18/2017 02:49 AM, Daniel van Vugt wrote: > It appears the reason is in the bug description: > > "PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon." > > Do you have any crash files in /var/crash ? > > ** Changed in: pulseaudio (Ubuntu) > Status: New => Incomplete > ** Attachment added: "_usr_bin_compiz.1000.crash" https://bugs.launchpad.net/bugs/1738605/+attachment/5024347/+files/_usr_bin_compiz.1000.crash -- 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/1738605 Title: Yesterday I had sound. Today I don't. Status in pulseaudio package in Ubuntu: Incomplete Bug description: Happens every single time I install Ubuntu on every single computer I have ever install it on. This time, it doesn't seem to have a solution. Shows audio in volume control under output devices, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: master 1752 F pulseaudio /dev/snd/pcmC0D0c: master 1752 F...m pulseaudio /dev/snd/pcmC0D0p: master 1752 F...m pulseaudio /dev/snd/controlC0: master 1752 F pulseaudio Date: Sat Dec 16 23:23:28 2017 InstallationDate: Installed on 2017-12-15 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733700] Re: python tools do not understand 'non-magic' include rules
** Summary changed:
- apparmor python tools do not understand 'include' rules
+ python tools do not understand 'non-magic' include rules
** Changed in: apparmor (Ubuntu Trusty)
Status: New => Triaged
** Changed in: apparmor (Ubuntu Xenial)
Status: New => Triaged
** Changed in: apparmor (Ubuntu Zesty)
Status: New => Triaged
** Changed in: apparmor (Ubuntu Artful)
Status: New => Triaged
** Changed in: apparmor (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1733700
Title:
python tools do not understand 'non-magic' include rules
Status in AppArmor:
In Progress
Status in apparmor package in Ubuntu:
Triaged
Status in apparmor source package in Trusty:
Triaged
Status in apparmor source package in Xenial:
Triaged
Status in apparmor source package in Zesty:
Triaged
Status in apparmor source package in Artful:
Triaged
Status in apparmor source package in Bionic:
Triaged
Bug description:
The apparmor_parser now supports 'include' rules in addition to
'#include', but the python tools only understand '#include'. This
manifested itself in Ubuntu in bug #1734038 (see
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/comments/15
of that bug for details).
Reproducer:
$ mkdir /tmp/test
$ cat /etc/apparmor.d/lp1733700
profile lp1733700 {
include "/tmp/test"
}
$ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
ok
$ sudo aa-enforce /etc/apparmor.d/lp1733700
ERROR: Syntax Error: Missing '}' or ','. Reached end of file
/etc/apparmor.d/lp1733700 while inside profile lp1733700
Changing the 'include' to '#include' results in:
$ sudo aa-enforce /etc/apparmor.d/lp1733700
Setting /etc/apparmor.d/lp1733700 to enforce mode.
At least aa-logprof is also affected.
= Original report =
On Ubuntu artful, I'm seeing the following behavior:
$ aa-enforce usr.bin.chromium-browser
ERROR: Syntax Error: Unknown line found in file
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,
I have never touched snap.core.3440.usr.lib.snapd.snap-confine.
This is snapd 2.28.5+17.10.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1733700/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
Ubuntu: 17.10 Mainline Kernel: 4.14.7 Still not working :( anti-egos fix didn't help. -- 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/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733700] Re: apparmor python tools do not understand 'include' rules
https://gitlab.com/apparmor/apparmor/merge_requests/44
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1733700
Title:
apparmor python tools do not understand 'include' rules
Status in AppArmor:
In Progress
Status in apparmor package in Ubuntu:
New
Status in apparmor source package in Trusty:
New
Status in apparmor source package in Xenial:
New
Status in apparmor source package in Zesty:
New
Status in apparmor source package in Artful:
New
Status in apparmor source package in Bionic:
New
Bug description:
The apparmor_parser now supports 'include' rules in addition to
'#include', but the python tools only understand '#include'. This
manifested itself in Ubuntu in bug #1734038 (see
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/comments/15
of that bug for details).
Reproducer:
$ mkdir /tmp/test
$ cat /etc/apparmor.d/lp1733700
profile lp1733700 {
include "/tmp/test"
}
$ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
ok
$ sudo aa-enforce /etc/apparmor.d/lp1733700
ERROR: Syntax Error: Missing '}' or ','. Reached end of file
/etc/apparmor.d/lp1733700 while inside profile lp1733700
Changing the 'include' to '#include' results in:
$ sudo aa-enforce /etc/apparmor.d/lp1733700
Setting /etc/apparmor.d/lp1733700 to enforce mode.
At least aa-logprof is also affected.
= Original report =
On Ubuntu artful, I'm seeing the following behavior:
$ aa-enforce usr.bin.chromium-browser
ERROR: Syntax Error: Unknown line found in file
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,
I have never touched snap.core.3440.usr.lib.snapd.snap-confine.
This is snapd 2.28.5+17.10.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1733700/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738884] [NEW] python 3.6 ubuntu 16.04 needs updated lib
Public bug reported: 16.04 comes with apt_pkg.cpython-35m-x86_64-linux-gnu.so but places it in the /usr/lib/python3/dist-packages directory, not the /usr/lib/python3.5/dist-packages directory. I'm guessing that apt isn't adding the 3.6 version correctly when installing python3.6, as we are getting errors in modules that depend on this when using py3.6 ( error is "not found apt_pkg" ) regretfully beyond us to know if the problem is here or in how py3.6 is maintained. ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New -- 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/1738884 Title: python 3.6 ubuntu 16.04 needs updated lib Status in python-apt package in Ubuntu: New Bug description: 16.04 comes with apt_pkg.cpython-35m-x86_64-linux-gnu.so but places it in the /usr/lib/python3/dist-packages directory, not the /usr/lib/python3.5/dist-packages directory. I'm guessing that apt isn't adding the 3.6 version correctly when installing python3.6, as we are getting errors in modules that depend on this when using py3.6 ( error is "not found apt_pkg" ) regretfully beyond us to know if the problem is here or in how py3.6 is maintained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1738884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: autofs needs to be restarted to pick up some shares
Would there be an updated version in the next xenial point release? Is there any chance to get autofs (5.1.2-1) at all? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/40189 Title: autofs needs to be restarted to pick up some shares Status in autofs package in Ubuntu: Confirmed Status in autofs5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Bug description: I am using autofs to access shares on a Windows XP machine from a Kubuntu AMD64 machine. The problems applies in both Breezy and Dapper. EDIT: confirmed with similar configuration on Intrepid with a NetApp filer hosting NFS. Server OS removed from summary. When I first try to access the mount point via cd or in Konqueror it does not exist. However, if I then restart autofs (/etc/init.d/autofs restart) everythin then works OK. My config files are: auto.master # # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $ # # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). #/misc/etc/auto.misc --timeout=60 #/misc/etc/auto.misc #/net /etc/auto.net /petunia /etc/petunia.misc --timeout=60 petunia.misc # # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $ # # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/tony chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/chris shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/SharedDocs linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/linuxbackups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738582] Re: [MIR] ibus-libpinyin and dependencies
On 2017-12-18 19:52, Gunnar Hjalmarsson wrote:
> ~desktop-packages is bug subscriber to ibus-sunpinyin currently, so
> I'd suggest the same for ibus-libpinyin and libpinyin.
@Sebastien, is that fine with you?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1738582
Title:
[MIR] ibus-libpinyin and dependencies
Status in ibus-libpinyin package in Ubuntu:
New
Status in libpinyin package in Ubuntu:
New
Bug description:
Please include these packages in Ubuntu's component main:
* ibus-libpinyin
* libpinyin (the ibus-libpinyin binary depends on libpinyin7)
As has been discussed at bug #1735362 we would like to replace ibus-
sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
and as the default input method for typing Simplified Chinese. Reasons
for the switch are:
- ibus-libpinyin is better maintained
- ibus-libpinyin is built with and depends on Python3
(not yet in Debian: https://bugs.debian.org/883631)
- ibus-libpinyin is default input method in GNOME
Bugs ibus-libpinyin
---
https://github.com/libpinyin/ibus-libpinyin/issues
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin
Bugs libpinyin
--
https://github.com/libpinyin/libpinyin/issues
(no open Debian or Ubuntu bugs)
I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, and
haven't found any issues that would prevent the proposed main inclusion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1738582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733700] Re: apparmor python tools do not understand 'include' rules
** Changed in: apparmor
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: apparmor
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1733700
Title:
apparmor python tools do not understand 'include' rules
Status in AppArmor:
In Progress
Status in apparmor package in Ubuntu:
New
Status in apparmor source package in Trusty:
New
Status in apparmor source package in Xenial:
New
Status in apparmor source package in Zesty:
New
Status in apparmor source package in Artful:
New
Status in apparmor source package in Bionic:
New
Bug description:
The apparmor_parser now supports 'include' rules in addition to
'#include', but the python tools only understand '#include'. This
manifested itself in Ubuntu in bug #1734038 (see
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/comments/15
of that bug for details).
Reproducer:
$ mkdir /tmp/test
$ cat /etc/apparmor.d/lp1733700
profile lp1733700 {
include "/tmp/test"
}
$ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
ok
$ sudo aa-enforce /etc/apparmor.d/lp1733700
ERROR: Syntax Error: Missing '}' or ','. Reached end of file
/etc/apparmor.d/lp1733700 while inside profile lp1733700
Changing the 'include' to '#include' results in:
$ sudo aa-enforce /etc/apparmor.d/lp1733700
Setting /etc/apparmor.d/lp1733700 to enforce mode.
At least aa-logprof is also affected.
= Original report =
On Ubuntu artful, I'm seeing the following behavior:
$ aa-enforce usr.bin.chromium-browser
ERROR: Syntax Error: Unknown line found in file
/etc/apparmor.d/snap.core.3440.usr.lib.snapd.snap-confine line 15:
include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,
I have never touched snap.core.3440.usr.lib.snapd.snap-confine.
This is snapd 2.28.5+17.10.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1733700/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664205] Update Released
The verification of the Stable Release Update for nux has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1664205 Title: Copy-paste and text selection doesn't work when caps-lock is on Status in nux package in Ubuntu: Fix Released Status in nux source package in Xenial: Fix Released Bug description: [Impact] Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps Lock is on [Test case] 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off [Possible regression] Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling won't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on
This bug was fixed in the package nux - 4.0.8+16.04.20170816-0ubuntu1
---
nux (4.0.8+16.04.20170816-0ubuntu1) xenial; urgency=medium
* TextEntry: Make sure Ctr+{C,V,X,A} work with caps-lock on (LP:
#1664205)
-- Marco Trevisan (Treviño) Wed, 16 Aug 2017 22:04:15
+
** Changed in: nux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/1664205
Title:
Copy-paste and text selection doesn't work when caps-lock is on
Status in nux package in Ubuntu:
Fix Released
Status in nux source package in Xenial:
Fix Released
Bug description:
[Impact]
Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps
Lock is on
[Test case]
0) Set Caps-Lock on in your keyboard
1) Open dash, and write something
2) Ctrl+A should select all the text, Ctrl+C should copy,
Ctrl+V should paste and Ctrl+X should cut
Currently they don't work unless caps-lock is turned off
[Possible regression]
Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling
won't work anymore
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738582] Re: [MIR] ibus-libpinyin and dependencies
I successfully built the existing version of ibus-libpinyin with lua5.3
instead of lua5.1, and the resulting binary seems to work fine. Debdiff
attached to bug #1735362.
So even if it would be desirable to update to newer upstream versions,
that's not a blocker for this MIR, is it?
~desktop-packages is bug subscriber to ibus-sunpinyin currently, so I'd
suggest the same for ibus-libpinyin and libpinyin.
** Changed in: ibus-libpinyin (Ubuntu)
Status: Incomplete => New
** Description changed:
Please include these packages in Ubuntu's component main:
* ibus-libpinyin
* libpinyin (the ibus-libpinyin binary depends on libpinyin7)
- * lua5.1 (the ibus-libpinyin binary depends on liblua5.1-0)
As has been discussed at bug #1735362 we would like to replace ibus-
sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
and as the default input method for typing Simplified Chinese. Reasons
for the switch are:
- ibus-libpinyin is better maintained
- ibus-libpinyin is built with and depends on Python3
- (not yet in Debian: https://bugs.debian.org/883631)
+ (not yet in Debian: https://bugs.debian.org/883631)
- ibus-libpinyin is default input method in GNOME
Bugs ibus-libpinyin
---
https://github.com/libpinyin/ibus-libpinyin/issues
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin
Bugs libpinyin
--
https://github.com/libpinyin/libpinyin/issues
(no open Debian or Ubuntu bugs)
- Bugs lua5.1
- ---
- http://www.lua.org/bugs.html#5.1.5
-
- https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lua5.1
-
- https://bugs.launchpad.net/ubuntu/+source/lua5.1
-
I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, and
haven't found any issues that would prevent the proposed main inclusion.
** No longer affects: lua5.1 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1738582
Title:
[MIR] ibus-libpinyin and dependencies
Status in ibus-libpinyin package in Ubuntu:
New
Status in libpinyin package in Ubuntu:
New
Bug description:
Please include these packages in Ubuntu's component main:
* ibus-libpinyin
* libpinyin (the ibus-libpinyin binary depends on libpinyin7)
As has been discussed at bug #1735362 we would like to replace ibus-
sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
and as the default input method for typing Simplified Chinese. Reasons
for the switch are:
- ibus-libpinyin is better maintained
- ibus-libpinyin is built with and depends on Python3
(not yet in Debian: https://bugs.debian.org/883631)
- ibus-libpinyin is default input method in GNOME
Bugs ibus-libpinyin
---
https://github.com/libpinyin/ibus-libpinyin/issues
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin
Bugs libpinyin
--
https://github.com/libpinyin/libpinyin/issues
(no open Debian or Ubuntu bugs)
I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, and
haven't found any issues that would prevent the proposed main inclusion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1738582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
fwiw, I can see the error in every reboot on my artful vm when it's deployed with maas. I can also therefore verify the fix :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Artful: Triaged Status in ntp source package in Bionic: Fix Released Bug description: [Impact] * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. [Test Case] * This is hard to trigger, but then also not. Which means it is not entirely sorted out when it triggers and when not, but the following does trigger it in tests of Pitti and also mine (while at the same time sometimes it does not - mabye I had other guests or kvm instead of lxd) * First install ntp in Artful (or above unless fixed) * Then you have to cause soemthing that ntp "needs" to complain about in my case I had spawned more virtual guests and NTP failed to bind on their virtual interface, but you could setup anything else that it fails on after the initial start (there it passed over to private TMP) * Once an issue triggers instead of the error in syslog you'll see the apparmor Deny like: apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [Regression Potential] * We are slightly opening up the apparmor profile which is far lower risk than adding more constraints. So safe from that POV. * OTOH one could think this might be a security issue, but in fact this isn't a new suggestion if you take a look at [1] with an ack by Seth of the Security Team. [Other Info] * n/a [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
Can you please update the "[Impact]" section of this SRU? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Artful: Triaged Status in ntp source package in Bionic: Fix Released Bug description: [Impact] * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. [Test Case] * This is hard to trigger, but then also not. Which means it is not entirely sorted out when it triggers and when not, but the following does trigger it in tests of Pitti and also mine (while at the same time sometimes it does not - mabye I had other guests or kvm instead of lxd) * First install ntp in Artful (or above unless fixed) * Then you have to cause soemthing that ntp "needs" to complain about in my case I had spawned more virtual guests and NTP failed to bind on their virtual interface, but you could setup anything else that it fails on after the initial start (there it passed over to private TMP) * Once an issue triggers instead of the error in syslog you'll see the apparmor Deny like: apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [Regression Potential] * We are slightly opening up the apparmor profile which is far lower risk than adding more constraints. So safe from that POV. * OTOH one could think this might be a security issue, but in fact this isn't a new suggestion if you take a look at [1] with an ack by Seth of the Security Team. [Other Info] * n/a [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738838] [NEW] bluetooth does not turn on; settings interfaces are nonsensical
Public bug reported: See video. I have installed bluetooth, blueman, bluez but it makes no difference to a broken interface to control bluetooth under Gnome 17.10, as shown in the attached video. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluetooth 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 17 22:32:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-18 (30 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: bnep btusb bluetooth MachineType: LENOVO 20BXCTO1WW PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash psmouse.synaptics_intertouch=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "Bluetooth options are to turn off only; turning on gives strange behaviour. Sliders do not work, effect is not as expected." https://bugs.launchpad.net/bugs/1738838/+attachment/5024237/+files/out-1.ogv -- 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/1738838 Title: bluetooth does not turn on; settings interfaces are nonsensical Status in bluez package in Ubuntu: New Bug description: See video. I have installed bluetooth, blueman, bluez but it makes no difference to a broken interface to control bluetooth under Gnome 17.10, as shown in the attached video. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluetooth 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 17 22:32:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-18 (30 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: bnep btusb bluetooth MachineType: LENOVO 20BXCTO1WW PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash psmouse.synaptics_intertouch=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
The script worked for me too with an HP Spectre x360 13-w013dx. -- 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 1738809] Re: Indicator icons scale 200%
They don't look much better on 100% either. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1738809 Title: Indicator icons scale 200% Status in indicator-network package in Ubuntu: New Bug description: Ubuntu 17.10 fresh install Display scale set to 200%, see how icons look like in the attachment (slack, steam). Generally I think they are just missing some padding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1738809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738809] [NEW] Indicator icons scale 200%
Public bug reported: Ubuntu 17.10 fresh install Display scale set to 200%, see how icons look like in the attachment (slack, steam). Generally I think they are just missing some padding. ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2017-12-18 16-21-01.png" https://bugs.launchpad.net/bugs/1738809/+attachment/5024192/+files/Screenshot%20from%202017-12-18%2016-21-01.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1738809 Title: Indicator icons scale 200% Status in indicator-network package in Ubuntu: New Bug description: Ubuntu 17.10 fresh install Display scale set to 200%, see how icons look like in the attachment (slack, steam). Generally I think they are just missing some padding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1738809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724152] Re: ISST-LTE: pVM: aureport couldn't get the right auid from the audit log on ubuntu16.04
** Tags added: triage-g -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1724152 Title: ISST-LTE: pVM: aureport couldn't get the right auid from the audit log on ubuntu16.04 Status in The Ubuntu-power-systems project: Fix Committed Status in audit package in Ubuntu: Invalid Status in audit source package in Xenial: Fix Committed Status in audit source package in Zesty: Fix Committed Bug description: [Impact] The aureport command, part of the audit userspace utilities, incorrectly reports the user id of successful logins. "-1" is printed instead of the expected user id. [Test Case] As root, run `login`. Proceed as follows: 1. Login with a blank username and any password 2. Login with an invalid username and any password 3. Login with a valid username and an invalid password 4. Login with a valid username and a valid password 5. Exit from the login shell 6. Run `aureport -l` and examine the last for login records An unpatched aureport will print the following: # date time auid host term exe success event ... 2. 10/17/2017 23:45:32 UNKNOWN ? /dev/pts/8 /bin/login no 97 3. 10/17/2017 23:45:39 UNKNOWN ? /dev/pts/8 /bin/login no 99 4. 10/17/2017 23:45:45 tyhicks ? /dev/pts/8 /bin/login no 101 5. 10/17/2017 23:45:49 -1 ? /dev/pts/8 /bin/login yes 107 A patch aureport will print the correct output: Login Report # date time auid host term exe success event ... 2. 10/17/2017 23:52:44 UNKNOWN ? /dev/pts/8 /bin/login no 165 3. 10/17/2017 23:52:52 UNKNOWN ? /dev/pts/8 /bin/login no 167 4. 10/17/2017 23:52:58 tyhicks ? /dev/pts/8 /bin/login no 169 5. 10/17/2017 23:53:02 1000 ? /dev/pts/8 /bin/login yes 175 Note the "1000" in the auid column on the #5 row. It should *not* be "-1". [Regression Potential] The regression potential is limited due to the change only affecting a single line of code, the fix comes from upstream, and that the aureport utility is not critical. [Original Report] == Comment: #0 - Miao Tao Feng - 2016-11-23 02:46:25 == When we develop new testcase for audit, we found that command "aureport -l" print out wrong auid "-1" on ubuntu16.04 and it should be 1000 according to the audit.log. The following are details: root@roselp2:~# aureport -l Login Report # date time auid host term exe success event 1. 11/23/2016 02:20:12 -1 10.33.24.118 /dev/pts/0 /usr/sbin/sshd yes 18 The auid "-1" on the above line should be "1000? according to the audit.log. root@roselp2:~# grep ":18" /var/log/audit/audit.log type=USER_LOGIN msg=audit(1479889212.292:18): pid=4177 uid=0 auid=1000 ses=4 msg='op=login id=1000 exe="/usr/sbin/sshd" hostname=10.33.24.118 addr=10.33.24.118 terminal=/dev/pts/0 res=success' root@roselp2:~# dpkg -s auditd Package: auditd Status: install ok installed Priority: extra Section: admin Installed-Size: 1051 Maintainer: Ubuntu Developers Architecture: ppc64el Source: audit Version: 1:2.4.5-1ubuntu2 Depends: lsb-base (>= 3.0-6), mawk | gawk, init-system-helpers (>= 1.18~), libaudit1 (>= 1:2.4.2), libauparse0 (>= 1:2.3.1), libc6 (>= 2.17) Suggests: audispd-plugins root@roselp2:~# uname -a Linux roselp2 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:38:24 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@roselp2:~# service auditd status ? auditd.service - Security Auditing Service Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor preset: e Active: active (running) since Wed 2016-11-23 02:19:21 CST; 19s ago Main PID: 4085 (auditd) CGroup: /system.slice/auditd.service ??4085 /sbin/auditd -n Nov 23 02:19:21 roselp2 auditctl[4086]: enabled 0 Nov 23 02:19:21 roselp2 auditctl[4086]: failure 1 Nov 23 02:19:21 roselp2 auditctl[4086]: pid 0 Nov 23 02:19:21 roselp2 auditctl[4086]: rate_limit 0 Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_limit 320 Nov 23 02:19:21 roselp2 auditctl[4086]: lost 0 Nov 23 02:19:21 roselp2 auditctl[4086]: backlog 0 Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_wait_time 15000 Nov 23 02:19:21 roselp2 systemd[1]: Started Security Auditing Service. Nov 23 02:19:21 roselp2 auditd[4085]: Init complete, auditd 2.4.5 listening for Please cherry pick https://github.com/linux-audit/audit- userspace/commit/25097d64344828a80acf681da5c1dacc4ea3c069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1724152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.la
[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
Testing:: 1. using the bluez without the patch - reboot - try to pair and connect 2. using bluez with patch - reboot - try to pair and connect In some cases pairing and connecting works better with the patch applied. There is no negative behavior observed with patch applied compared to w/o the patch. -- 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/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Confirmed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option. Remove file 50-bluetooth-hci-auto-poweron.rules located in /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be powered off now. [Regression Potential] Cannot think of any [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738234] Re: package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash package pre-installation script subprocess was killed by signal (Aborted), core dumped
Been researching this issue, seems it's fixed in windows insider build 17046 and later Reference issue: https://github.com/Microsoft/WSL/issues/1878 Reference comment: https://github.com/Microsoft/WSL/issues/1878#issuecomment-350325140 ** Bug watch added: github.com/Microsoft/WSL/issues #1878 https://github.com/Microsoft/WSL/issues/1878 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1738234 Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash package pre-installation script subprocess was killed by signal (Aborted), core dumped Status in bash package in Ubuntu: Confirmed Bug description: Installing 18.07 on WSL using do-distribution-upgrade -d ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bash 4.3-14ubuntu1.2 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Dec 14 17:46:10 2017 Dmesg: ErrorMessage: new bash package pre-installation script subprocess was killed by signal (Aborted), core dumped RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.2.24 SourcePackage: bash Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash package pre-installation script subprocess was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to xenial on 2017-12-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1738234/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732735] Re: hostname lookup broken in ldap.conf
It looks like, that there is a problem, when the ldap-client searches with exponential backoff for the servers: Following change seems to fix the problem, BUT a rational sounding has to be changed? In /etc/ldap.conf: default Reconnect policy: bind_policy hard has to be changed to: bind_policy soft then: In /etc/ldap.conf: -> host ldap01 ldap02 works as expected, and PC without network-cable boots normal. ** Summary changed: - hostname lookup broken in ldap.conf + bind_policy hard broken in ldap.conf ** Package changed: xorg (Ubuntu) => ldap-auth-client (Ubuntu) ** Summary changed: - bind_policy hard broken in ldap.conf + bind_policy hard broken in ldap.conf in 17.10 -- 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/1732735 Title: bind_policy hard broken in ldap.conf in 17.10 Status in ldap-auth-client package in Ubuntu: New Bug description: A scripted installation of an ldap-client WORKING in ubuntu 16.04 is broken in ubuntu 17.10. In ldap.conf: host ldap01 ldap02 (was working in 16.04) has to be replaced with: host 10.0.0.9 10.0.0.10 otherwise the system stays in an endless loop at boot up! Change from hostname to ip has to be done with a rescue system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldap-auth-client/+bug/1732735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727687] Re: systemd boots system offline ("Breaking ordering cycle by deleting job network.target/stop")
Today my system booted offline again.
With the same symptoms. Where should I find help?
--
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/1727687
Title:
systemd boots system offline ("Breaking ordering cycle by deleting job
network.target/stop")
Status in systemd package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Install Ubuntu 16.04 LTS
2. Install LTSP server (dnsmasq as proxy DHCP and tftp; NBD, SSH)
3. Reboot.
4. Boot system
Expected results:
* system boots to online
Actual results:
* system boots offline; it's a security vulnerability as denial of service
Interesting messages from syslog:
Oct 19 15:25:56 server systemd[1]: network-online.target: Found ordering
cycle on network-online.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
network.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
NetworkManager.service/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
basic.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
paths.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
cups.path/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
sysinit.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
nbd-client.service/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
network-online.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Breaking ordering
cycle by deleting job network.target/stop
Oct 19 15:25:56 server systemd[1]: network.target: Job network.target/stop
deleted to break ordering cycle starting with network-online.target/stop
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu19
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
CurrentDesktop: MATE
Date: Thu Oct 26 13:50:49 2017
InstallationDate: Installed on 2016-04-21 (552 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic
root=UUID=26069a01-c072-4021-83c5-f6df23dc51d5 ro net.ifnames=0 biosdevname=0
quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/09/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FD
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A55M-DS2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727687/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) -- 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/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Confirmed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option. Remove file 50-bluetooth-hci-auto-poweron.rules located in /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be powered off now. [Regression Potential] Cannot think of any [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
** Changed in: bluez (Ubuntu Xenial) Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Confirmed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option. Remove file 50-bluetooth-hci-auto-poweron.rules located in /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be powered off now. [Regression Potential] Cannot think of any [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738787] [NEW] graphics trouble
Public bug reported: black screen ato start up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.14.7-041407-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.14 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: Mon Dec 18 22:39:18 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [104d:9005] Subsystem: Sony Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) [104d:9005] InstallationDate: Installed on 2016-10-22 (422 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VGN-FZ150E PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.7-041407-generic root=UUID=c78640c7-3852-4766-beeb-c68e0cb30c08 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0040J7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0040J7:bd04/03/2007:svnSonyCorporation:pnVGN-FZ150E:pvrC3LP36QQ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-FZ150E dmi.product.version: C3LP36QQ dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Dec 18 22:24:31 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1738787 Title: graphics trouble Status in xorg package in Ubuntu: New Bug description: black screen ato start up ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.14.7-041407-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.14 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: Mon Dec 18 22:39:18 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [104d:9005] Subsystem: Sony Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) [104d:9005] InstallationDate: Installed on 2016-10-22 (422 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VGN-FZ150E PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.7-041407-generic root=UUID=c78640c7-3852-4766-beeb-c68e0cb30c08 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0040J7 dmi.bo
[Touch-packages] [Bug 1738205] Re: no sound while playing audio/video
Still not able to hear the audio. Please find the attached file for your reference for debugging.. ** Attachment added: "Log for No Sound Issue" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738205/+attachment/5024159/+files/alsa-info.txt.frMecibxIs -- 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/1738205 Title: no sound while playing audio/video Status in pulseaudio package in Ubuntu: New Bug description: Not able to hear audio through headset on ubuntu 14.04. Also, volume icon is not visible.. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-80-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu Dec 14 18:47:12 2017 InstallationDate: Installed on 2016-02-04 (679 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Acer dmi.bios.version: P01-A4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Veriton M6610 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAcer:bvrP01-A4:bd07/26/2011:svnAcer:pnVeritonSeries:pvr:rvnAcer:rnVeritonM6610:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton Series dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738781] Re: networkmanager does not recognize the names of the internet servers
journalctl -xe ** Attachment added: "journalctl -xe" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+attachment/5024158/+files/T5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1738781 Title: networkmanager does not recognize the names of the internet servers Status in resolvconf package in Ubuntu: New Bug description: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738205] Re: no sound while playing audio/video
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- 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/1738205 Title: no sound while playing audio/video Status in pulseaudio package in Ubuntu: New Bug description: Not able to hear audio through headset on ubuntu 14.04. Also, volume icon is not visible.. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-80-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu Dec 14 18:47:12 2017 InstallationDate: Installed on 2016-02-04 (679 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Acer dmi.bios.version: P01-A4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Veriton M6610 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAcer:bvrP01-A4:bd07/26/2011:svnAcer:pnVeritonSeries:pvr:rvnAcer:rnVeritonM6610:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton Series dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738781] Re: networkmanager does not recognize the names of the internet servers
manual copy of the network restarting command ** Attachment added: "manual copy of the network restarting command" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+attachment/5024124/+files/T3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1738781 Title: networkmanager does not recognize the names of the internet servers Status in resolvconf package in Ubuntu: New Bug description: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738781] Re: networkmanager does not recognize the names of the internet servers
systemctl status Networkmanager.service ** Attachment added: "systemctl status Networkmanager.servic" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+attachment/5024125/+files/T4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1738781 Title: networkmanager does not recognize the names of the internet servers Status in resolvconf package in Ubuntu: New Bug description: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738781] Re: networkmanager does not recognize the names of the internet servers
good ping ** Attachment added: "good ping" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+attachment/5024123/+files/T2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1738781 Title: networkmanager does not recognize the names of the internet servers Status in resolvconf package in Ubuntu: New Bug description: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738781] [NEW] networkmanager does not recognize the names of the internet servers
Public bug reported: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ubuntu version" https://bugs.launchpad.net/bugs/1738781/+attachment/5024121/+files/T1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1738781 Title: networkmanager does not recognize the names of the internet servers Status in resolvconf package in Ubuntu: New Bug description: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738778] [NEW] package libxdmcp6 1:1.1.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxdmcp6/changelog.Debian.gz', which is different from other ins
Public bug reported: Don't know exactly ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libxdmcp6 1:1.1.2-3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Dec 14 10:34:57 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libbsd0 0.8.6-1 libc6 2.26-0ubuntu2 libgcc1 1:6.3.0-12ubuntu2 DistUpgraded: 2017-11-12 10:05:53,525 ERROR No view can be imported, aborting DistroCodename: artful DistroVariant: ubuntu ErrorMessage: trying to overwrite shared '/usr/share/doc/libxdmcp6/changelog.Debian.gz', which is different from other instances of package libxdmcp6:i386 GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2017-08-18 (121 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HDIV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=f9645c3f-ec8f-4a54-9c80-30f3ef313009 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: libxdmcp Title: package libxdmcp6 1:1.1.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxdmcp6/changelog.Debian.gz', which is different from other instances of package libxdmcp6:i386 UpgradeStatus: Upgraded to artful on 2017-11-12 (36 days ago) dmi.bios.date: 03/15/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET51W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HDIV dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1QET51W(1.26):bd03/15/2017:svnLENOVO:pn20HDIV:pvrThinkPadT470:rvnLENOVO:rn20HDIV:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HDIV dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 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.15-2 xserver.bootTime: Mon Dec 18 14:25:34 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset ** Affects: libxdmcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful compiz-0.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxdmcp in Ubuntu. https://bugs.launchpad.net/bugs/1738778 Title: package libxdmcp6 1:1.1.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libxdmcp6/changelog.Debian.gz', which is different from other instances of package libxdmcp6:i386 Status in libxdmcp package in Ubuntu: New Bug description: Don't know exactly ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libxdmcp6 1:1.1.2-3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Dec 14 10:34:57 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libbsd0 0.8.6-1 libc6 2.26-0ubuntu2 libgcc1 1:6.3.0-12ubuntu2 DistUpgraded: 2017-11-12 10:05:53,525 ERROR No view can be imported, aborting DistroCodename: artful DistroVariant: ubuntu ErrorMessage: trying to overwrite shared '/usr/share/doc/libxdmcp6/changelog.Debian.gz', which is different from other instances of package libxdmcp6:i386 GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed
[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/335314 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Artful: Triaged Status in ntp source package in Bionic: Fix Released Bug description: [Impact] * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. [Test Case] * This is hard to trigger, but then also not. Which means it is not entirely sorted out when it triggers and when not, but the following does trigger it in tests of Pitti and also mine (while at the same time sometimes it does not - mabye I had other guests or kvm instead of lxd) * First install ntp in Artful (or above unless fixed) * Then you have to cause soemthing that ntp "needs" to complain about in my case I had spawned more virtual guests and NTP failed to bind on their virtual interface, but you could setup anything else that it fails on after the initial start (there it passed over to private TMP) * Once an issue triggers instead of the error in syslog you'll see the apparmor Deny like: apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [Regression Potential] * We are slightly opening up the apparmor profile which is far lower risk than adding more constraints. So safe from that POV. * OTOH one could think this might be a security issue, but in fact this isn't a new suggestion if you take a look at [1] with an ack by Seth of the Security Team. [Other Info] * n/a [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
** Description changed: + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test Case] + + * This is hard to trigger, but then also not. Which means it is not +entirely sorted out when it triggers and when not, but the following +does trigger it in tests of Pitti and also mine (while at the same time +sometimes it does not - mabye I had other guests or kvm instead of lxd) + + * First install ntp in Artful (or above unless fixed) +* Then you have to cause soemthing that ntp "needs" to complain about + in my case I had spawned more virtual guests and NTP failed to bind + on their virtual interface, but you could setup anything else that it + fails on after the initial start (there it passed over to private + TMP) +* Once an issue triggers instead of the error in syslog you'll see the + apparmor Deny like: +apparmor="DENIED" operation="sendmsg" info="Failed name lookup - +disconnected path" error=-13 profile="/usr/sbin/ntpd" +name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" +requested_mask="w" denied_mask="w" fsuid=0 ouid=0 + + [Regression Potential] + + * We are slightly opening up the apparmor profile which is far lower risk +than adding more constraints. So safe from that POV. + + * OTOH one could think this might be a security issue, but in fact this +isn't a new suggestion if you take a look at [1] with an ack by Seth of +the Security Team. + + [Other Info] + + * n/a + + [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html + + + Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 - (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu-stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Artful: Triaged Status in ntp source package in Bionic: Fix Released Bug description: [Impact] * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. [Test Case] * This is hard to trigger, but then also not. Which means it is not entirely sorted out when it triggers and when not, but the following does trigger it in tests of Pitti and also mine (while at the same time sometimes it does not - mabye I had other guests or kvm instead of lxd) * First install ntp in Artful (or above unless fixed) * Then you have to cause soemthing that ntp "needs" to complain about in my case I had spawned more virtual guests and NTP failed to bind on their virtual interface, but you could setup anything else that it fails on after the initial start (there it passed over to private TMP) * Once an issue triggers instead of the error in syslog you'll see the apparmor Deny like: apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [Regression Potential] * We are slightly opening up the apparmor profile which is far lower risk than adding more constraints. So safe from that POV. * OTOH one could think this might be a security issue, but in fact this isn't a new suggestion if you take a look at [1] with an ack by Seth of the Security Team. [Other Info] * n/a [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html Merely installing and starting ntp.ser
[Touch-packages] [Bug 1738582] Re: [MIR] ibus-libpinyin and dependencies
- libpinyin wasn't updated for a year. There is now a
2.1 release.
https://github.com/libpinyin/libpinyin/releases
- same with ibus-libpinyin 1.9.2
https://github.com/libpinyin/ibus-libpinyin/releases
and it looks like this version has support for lua5.2,
please check for 5.3 as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1738582
Title:
[MIR] ibus-libpinyin and dependencies
Status in ibus-libpinyin package in Ubuntu:
Incomplete
Status in libpinyin package in Ubuntu:
New
Status in lua5.1 package in Ubuntu:
New
Bug description:
Please include these packages in Ubuntu's component main:
* ibus-libpinyin
* libpinyin (the ibus-libpinyin binary depends on libpinyin7)
* lua5.1 (the ibus-libpinyin binary depends on liblua5.1-0)
As has been discussed at bug #1735362 we would like to replace ibus-
sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
and as the default input method for typing Simplified Chinese. Reasons
for the switch are:
- ibus-libpinyin is better maintained
- ibus-libpinyin is built with and depends on Python3
(not yet in Debian: https://bugs.debian.org/883631)
- ibus-libpinyin is default input method in GNOME
Bugs ibus-libpinyin
---
https://github.com/libpinyin/ibus-libpinyin/issues
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin
Bugs libpinyin
--
https://github.com/libpinyin/libpinyin/issues
(no open Debian or Ubuntu bugs)
Bugs lua5.1
---
http://www.lua.org/bugs.html#5.1.5
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lua5.1
https://bugs.launchpad.net/ubuntu/+source/lua5.1
I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, and
haven't found any issues that would prevent the proposed main inclusion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1738582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738582] Re: [MIR] ibus-libpinyin and dependencies
- both ibus-libpinyin and libpinyin look okish.
- not happy about the dependency on lua5.1, which is superseded by
lua5.2 and lua5.3 (both in main). Can this be updated?
- both pinyin packages need bug subscribers. Who will that be?
** Changed in: ibus-libpinyin (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1738582
Title:
[MIR] ibus-libpinyin and dependencies
Status in ibus-libpinyin package in Ubuntu:
Incomplete
Status in libpinyin package in Ubuntu:
New
Status in lua5.1 package in Ubuntu:
New
Bug description:
Please include these packages in Ubuntu's component main:
* ibus-libpinyin
* libpinyin (the ibus-libpinyin binary depends on libpinyin7)
* lua5.1 (the ibus-libpinyin binary depends on liblua5.1-0)
As has been discussed at bug #1735362 we would like to replace ibus-
sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
and as the default input method for typing Simplified Chinese. Reasons
for the switch are:
- ibus-libpinyin is better maintained
- ibus-libpinyin is built with and depends on Python3
(not yet in Debian: https://bugs.debian.org/883631)
- ibus-libpinyin is default input method in GNOME
Bugs ibus-libpinyin
---
https://github.com/libpinyin/ibus-libpinyin/issues
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin
Bugs libpinyin
--
https://github.com/libpinyin/libpinyin/issues
(no open Debian or Ubuntu bugs)
Bugs lua5.1
---
http://www.lua.org/bugs.html#5.1.5
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lua5.1
https://bugs.launchpad.net/ubuntu/+source/lua5.1
I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, and
haven't found any issues that would prevent the proposed main inclusion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1738582/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
The Bionic fix is about to complete now'ish. Since this (if triggered) is effectively blocking the messages to appear in the syslog this can hide an arbitrary amount of further issues that the user then has next to no grasp on how to tackle. So SRU worthy for Artful IMHO. Adding template soon. ** Changed in: ntp (Ubuntu Artful) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Artful: Triaged Status in ntp source package in Bionic: Fix Released Bug description: Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream
Still not fixed. :-( -- 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/1707898 Title: systemd translations are not synced with upstream Status in Ubuntu Translations: New Status in systemd package in Ubuntu: New Bug description: Translations for systemd are outdated because they do not seem to be synced with the upstream ones. For example the Czech one: Launchpad: https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate - 0% translated Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% translated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1707898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
This bug was fixed in the package ntp - 1:4.2.8p10+dfsg-5ubuntu4 --- ntp (1:4.2.8p10+dfsg-5ubuntu4) bionic; urgency=medium * debian/apparmor-profile: add attach_disconnected which is needed in some cases to let ntp report its log messages (LP: #1727202). -- Christian Ehrhardt Wed, 13 Dec 2017 16:31:30 +0100 ** Changed in: ntp (Ubuntu Bionic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp source package in Bionic: Fix Released Bug description: Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1738404] Re: Bluetooth sound extreme low quality
Hi Daniel, - Cambridge Silicon Radio dongles are historically unreliable. I found my Bluetooth devices were excessively buggy with them. And other people found the same. Try a different brand if you can. I have reverted back to Ubuntu 17.04 some minutes ago and the 3x bluetooth audio devices work again correctly, as they did before and as they do with my android devices. So I do not think, this is related to any hardware issue. I have then installed all the updates and that is stilll working. - Can you please check what audio profile you're using in sound settings for Bluetooth? Make sure it is A2DP for the best quality. Not HSP/HFP. Is the problem just the wrong profile defaulting? The only available profile was A2DP in 17.10, which I already used. HSP/FSP did not appear in the list. --- I also tested form an USB with 17.10 for installation, same issues. I think I am not doing any other actions, as my immediate incident is solved by reverting to the former version. I hope the actual problem get fixed until next Ubuntu stable release. Best regards, Carlos Blanquer Bogacz ___ 水に流す mizu ni nagasu : let us flow in the water On 18 December 2017 at 11:45, Daniel van Vugt wrote: > A few ideas come to mind: > > - Cambridge Silicon Radio dongles are historically unreliable. I found > my Bluetooth devices were excessively buggy with them. And other people > found the same. Try a different brand if you can. > > - Can you please check what audio profile you're using in sound settings > for Bluetooth? Make sure it is A2DP for the best quality. Not HSP/HFP. > Is the problem just the wrong profile defaulting? > > - Bug 405294 > > - Kernel regressions... Please try an older kernel more in line with > what 17.04 had (kernel version 4.10 or older): http://kernel.ubuntu.com > /~kernel-ppa/mainline/?C=N;O=D > > > Probably less relevant: > > - A regression in bluetooth in 17.10; sounds like it is Intel specific > though: bug 1729389 > > ** Changed in: bluez (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1738404 > > Title: > Bluetooth sound extreme low quality > > Status in bluez package in Ubuntu: > Incomplete > > Bug description: > I upgraded today from ubuntu 17.04 to ubuntu 17.10. > > I use 3 different bluetooth audio devices ( BT earphones, BT speaker, > BT BOSE Soundlink speaker) , all of them worked properly on 17.04. > > Since the upgrade, the sound gets continuous interruptions/cracking. > These sound interruptions and cracking are so annoying that I cannot > keep on listening to music. > I could relate this to the fact that a new BT stack has replaced the > former in Ubuntu. > > If I use wired devices (hdmi connected screen+audio, the sound quality > is good and as before) so the issue is related to the use of the new > Bluetooth stack. > I have not found a way to parameterise it neither. > > I have not found any similar report. "apport" seems not ot exist in > thise version, I cannot find and execute it. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/ > 1738404/+subscriptions > -- 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/1738404 Title: Bluetooth sound extreme low quality Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded today from ubuntu 17.04 to ubuntu 17.10. I use 3 different bluetooth audio devices ( BT earphones, BT speaker, BT BOSE Soundlink speaker) , all of them worked properly on 17.04. Since the upgrade, the sound gets continuous interruptions/cracking. These sound interruptions and cracking are so annoying that I cannot keep on listening to music. I could relate this to the fact that a new BT stack has replaced the former in Ubuntu. If I use wired devices (hdmi connected screen+audio, the sound quality is good and as before) so the issue is related to the use of the new Bluetooth stack. I have not found a way to parameterise it neither. I have not found any similar report. "apport" seems not ot exist in thise version, I cannot find and execute it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]
** Changed in: gtk+3.0 (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: gtk+3.0 (Ubuntu) Status: In Progress => Confirmed -- 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/1552577 Title: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] Status in Apport: New Status in GTK+: Confirmed Status in apport package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347 --- Crash displayed after logging in. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-gtk 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 1 22:13:24 2016 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2016-02-21 (10 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208 InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk SegvAnalysis: Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi PC (0x7f3a0219cb89) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1552577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738762] Re: Window controls padding when scale is set to 200%
** Tags added: hidpi ** Also affects: ubuntu-themes Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1738762 Title: Window controls padding when scale is set to 200% Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: New Bug description: Padding is small and often inconsistent, see screen-shot attached. Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1738762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738605] Re: Yesterday I had sound. Today I don't.
Also, does 'ps auxw | grep pulseaudio' show anything? This is starting to remind me of a daemon vs non-daemon problem, but I can't remember the details. -- 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/1738605 Title: Yesterday I had sound. Today I don't. Status in pulseaudio package in Ubuntu: Incomplete Bug description: Happens every single time I install Ubuntu on every single computer I have ever install it on. This time, it doesn't seem to have a solution. Shows audio in volume control under output devices, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: master 1752 F pulseaudio /dev/snd/pcmC0D0c: master 1752 F...m pulseaudio /dev/snd/pcmC0D0p: master 1752 F...m pulseaudio /dev/snd/controlC0: master 1752 F pulseaudio Date: Sat Dec 16 23:23:28 2017 InstallationDate: Installed on 2017-12-15 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738528] Re: Sound applet reflects volume of different device when bluetooth device auto-connects
Good news... we introduced switch-on-connect in Ubuntu 17.10 onward. I'm not sure if it's appropriate to backport that feature to 16.04 since it's arguably not a bug fix but we'll note your request for it in xenial. ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1738528 Title: Sound applet reflects volume of different device when bluetooth device auto-connects Status in pulseaudio package in Ubuntu: Fix Released Bug description: As currently set up in Ubuntu 16.04, when an audio device connects via bluetooth, it starts being used by programs automatically. However, the sound applet still "points to" the previously selected audio output. Therefore, changing the volume has no immediate audible effect. The way to change that, currently, is to go to Sound settings, select the bluetooth device as current output (again?), and then the volume will change. I would expect that, when a bluetooth device is connected, it starts being used, *and* changing the volume immediately will affect the bluetooth device. I googled a bit, and people have suggested [1] that the file /etc/pulse/default.pa should contain load-module module-switch-on- connect before the volume is restored. My installation does not have that line, but it does have: ### Should be after module-*-restore but before module-*-detect load-module module-switch-on-port-available According to [1], maybe this should be listed in that file *before* the aforementioned module-*-restore lines. [1] https://askubuntu.com/questions/233277/when-a-bluetooth-audio- device-auto-connects-volume-settings-wont-work-until-i-m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738605] Re: Yesterday I had sound. Today I don't.
It appears the reason is in the bug description: "PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon." Do you have any crash files in /var/crash ? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1738605 Title: Yesterday I had sound. Today I don't. Status in pulseaudio package in Ubuntu: Incomplete Bug description: Happens every single time I install Ubuntu on every single computer I have ever install it on. This time, it doesn't seem to have a solution. Shows audio in volume control under output devices, but there is no sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: master 1752 F pulseaudio /dev/snd/pcmC0D0c: master 1752 F...m pulseaudio /dev/snd/pcmC0D0p: master 1752 F...m pulseaudio /dev/snd/controlC0: master 1752 F pulseaudio Date: Sat Dec 16 23:23:28 2017 InstallationDate: Installed on 2017-12-15 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1738605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738762] [NEW] Window controls padding when scale is set to 200%
Public bug reported: Padding is small and often inconsistent, see screen-shot attached. Ubuntu 17.10 ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2017-12-18 11-51-00.png" https://bugs.launchpad.net/bugs/1738762/+attachment/5024088/+files/Screenshot%20from%202017-12-18%2011-51-00.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1738762 Title: Window controls padding when scale is set to 200% Status in ubuntu-themes package in Ubuntu: New Bug description: Padding is small and often inconsistent, see screen-shot attached. Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1738762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738404] Re: Bluetooth sound extreme low quality
A few ideas come to mind: - Cambridge Silicon Radio dongles are historically unreliable. I found my Bluetooth devices were excessively buggy with them. And other people found the same. Try a different brand if you can. - Can you please check what audio profile you're using in sound settings for Bluetooth? Make sure it is A2DP for the best quality. Not HSP/HFP. Is the problem just the wrong profile defaulting? - Bug 405294 - Kernel regressions... Please try an older kernel more in line with what 17.04 had (kernel version 4.10 or older): http://kernel.ubuntu.com /~kernel-ppa/mainline/?C=N;O=D Probably less relevant: - A regression in bluetooth in 17.10; sounds like it is Intel specific though: bug 1729389 ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1738404 Title: Bluetooth sound extreme low quality Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded today from ubuntu 17.04 to ubuntu 17.10. I use 3 different bluetooth audio devices ( BT earphones, BT speaker, BT BOSE Soundlink speaker) , all of them worked properly on 17.04. Since the upgrade, the sound gets continuous interruptions/cracking. These sound interruptions and cracking are so annoying that I cannot keep on listening to music. I could relate this to the fact that a new BT stack has replaced the former in Ubuntu. If I use wired devices (hdmi connected screen+audio, the sound quality is good and as before) so the issue is related to the use of the new Bluetooth stack. I have not found a way to parameterise it neither. I have not found any similar report. "apport" seems not ot exist in thise version, I cannot find and execute it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
I actually tried removing the module with the upgrade to PA 11.1 in Ubuntu 18.04. The release notes for PA 11.0 suggested that switch-on- connect would not be required, but my testing shows it still is needed for both Bluetooth and USB audio devices. Sorry about that. -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659902] Re: Please sync logrotate from Debian testing
logrotate 3.11.0-0.1ubuntu1 is available in Ubuntu 17.10 and later, so I believe this can be marked as fix released. If there are specific bugs (like the ones mentioned in the description) which should be fixed in older Ubuntu releases, they may qualify for Stable Release Updates. Please take a look at the SRU Procedure [1] (https://wiki.ubuntu.com/StableReleaseUpdates#Procedure) when it comes to these. ** Changed in: logrotate (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1659902 Title: Please sync logrotate from Debian testing Status in logrotate package in Ubuntu: Fix Released Bug description: logrotate 3.8.7 contains multiple bugs, including: 1) error creating output file [e.g.] /var/log/syslog.1.gz: File exists https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734688 I encounter this bug on many machines, with many different logfiles, both system logs and application logs. 2) segfault with certain configuration/path combos https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818793 The submitter mentions a specific set of conditions, but they are not limited to these alone, as confirmed in additional reports, and in my own testing. Changelog (appears very incomplete): logrotate (3.11.0-0.1) unstable; urgency=low * Non-maintainer upload * New upstream version 3.11.0 Closes: #734688 * Refresh patch queue, and fix several regressions * Update watch file. Closes: #844578, also Homepage information * Specify bsd-mailx as default mailx provider. Closes: #849743 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1659902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 651566] Re: Re : interesting
Take a examine what I've just read , this is so interesting , read more at http://www.natalquilombo.com/tgx.php?UE82NTE1NjZAYnVncy5sYXVOQ2hwYUQubmVU - Ce mail et les pièces jointes sont confidentiels et sont destinés seulement à la nécessité de l'individu de laquelle ils sont adressés . Toutes la philosophie ou jugement exprimées sont seulement celles de l'auteur et ne constituent pas impérativement celle des États-Unis . dans le cas ou n'êtes pas le allocutaire de cet e-mail , vous ne devez réaliser aucune action selon ses textes , ni le copier ou le prouver à n'importe qui . Veuillez contacter l'expéditeur si vous rêvez avoir subi cet e-mail par erreur . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/651566 Title: package avahi-daemon 0.6.25-1ubuntu6.1 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 139 Status in avahi package in Ubuntu: Invalid Bug description: executing automatic update ProblemType: Package DistroRelease: Ubuntu 10.04 Package: avahi-daemon 0.6.25-1ubuntu6.1 ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 Architecture: i386 Date: Wed Sep 29 23:11:18 2010 ErrorMessage: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 139 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: avahi Title: package avahi-daemon 0.6.25-1ubuntu6.1 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/651566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738731] [NEW] package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: le paquet isc-dhcp-common n'est pas prêt pour la configuration configuration impossible (état
Public bug reported: I cannot do anything... Please help me! Thanks ProblemType: Package DistroRelease: Ubuntu 16.04 Package: isc-dhcp-common 4.3.3-5ubuntu12.7 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Dec 18 08:36:42 2017 Dependencies: debianutils 4.7 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 sensible-utils 0.0.9 ErrorMessage: le paquet isc-dhcp-common n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») InstallationDate: Installed on 2017-03-30 (262 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: isc-dhcp Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: le paquet isc-dhcp-common n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1738731 Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: le paquet isc-dhcp-common n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») Status in isc-dhcp package in Ubuntu: New Bug description: I cannot do anything... Please help me! Thanks ProblemType: Package DistroRelease: Ubuntu 16.04 Package: isc-dhcp-common 4.3.3-5ubuntu12.7 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Dec 18 08:36:42 2017 Dependencies: debianutils 4.7 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 sensible-utils 0.0.9 ErrorMessage: le paquet isc-dhcp-common n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») InstallationDate: Installed on 2017-03-30 (262 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: isc-dhcp Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: le paquet isc-dhcp-common n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1738731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
