[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10
Danni, this is useful information and gives the best hope of being able to debug the problem. Was your original resolv.conf a symlink or a real file? Can you attach it to this bug report? Can you also paste the output of 'dpkg -S /etc/NetworkManager' on your system? -- 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/1725840 Title: resolvconf not correctly configured after update from 17.04 to 17.10 Status in resolvconf package in Ubuntu: Confirmed Bug description: After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS lookup on my wireless network connection did not work any more. As it seems, the file /etc/resolv.conf was static and contained wrong data assigned by the NetworkManager. When I changed the file content manually to nameserver 127.0.0.53 DNS lookup worked fine. After reboot, however, I had to repeat this operation since NetworkManager seems to have replaced the file content. Finally, I found a solution. Running sudo dpkg-reconfigure resolvconf the file /etc/resolv.conf was replaced by the link /etc/resolv.conf -> ../run/resolvconf/resolv.conf Now, the wireless network seems to work properly. Hence, there must be some kind of bug during the update process from Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured properly. Best regards, Artur ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: resolvconf 1.79ubuntu8 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 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 23:17:38 2017 InstallationDate: Installed on 2013-10-18 (1463 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724233] Re: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
is this a packaged extension? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1724233 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() Status in python2.7 package in Ubuntu: Incomplete Bug description: Booted into stock Ubuntu 17.10 release candidate from October 15, 2017 and this error message simply came up. apt-cache policy python python: Installed: 2.7.14-2ubuntu1 Candidate: 2.7.14-2ubuntu1 Version table: *** 2.7.14-2ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: python2.7-minimal 2.7.14-2ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 06:15:41 2017 ExecutablePath: /usr/bin/python2.7 InstallationDate: Installed on 2017-10-17 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) ProcCmdline: python accountable2you.pyc --username ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash 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 SegvAnalysis: Segfault happened at: 0x7f84d920daa9 : movzwl 0xa(%rdi),%r15d PC (0x7f84d920daa9) ok source "0xa(%rdi)" (0x64007d) not located in a known VMA region (needed readable region)! destination "%r15d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: python2.7 StacktraceTop: ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() 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/python2.7/+bug/1724233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734662] Re: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
it would be very nice to know the origin of this bad suggestion ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1734662 Title: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in python-setuptools package in Ubuntu: Invalid Bug description: Somethign is messed up after linking python to python 3 and after this all these issues started cropping up. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-setuptools 3.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Nov 27 16:19:13 2017 Dependencies: python-pkg-resources 3.3-1ubuntu2 DuplicateSignature: package:python-setuptools:3.3-1ubuntu2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-16 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: python-setuptools Title: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2017-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1734662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 724022] Re: [21 new] Allow use of Ubuntu Mono as .psf console-setup font
I'm closing this bug since fonts-ubuntu-font-family-console exists in all supported Ubuntu releases. ** Changed in: ubuntu-font-family-sources (Ubuntu) Status: Confirmed => Fix Released ** Changed in: ubuntu-font-family Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/724022 Title: [21 new] Allow use of Ubuntu Mono as .psf console-setup font Status in Ubuntu Font Family: Fix Released Status in ubuntu-font-family-sources package in Ubuntu: Fix Released Bug description: The text-mode console (Ctrl-Alt-F1) currently uses the default system/VGA font but a hinted version of Ubuntu Mono would be lovely to have loadable on the Linux console when it's finished. Converting a TTF so that it is usable as bitmap Linux console font appears to be a two-stage process; first rasterising to a BFD bitmap font file (bitmap with metrics), and then from that into a rawform, equal width PSF bitmap console font: otf2bdf /usr/share/fonts/truetype/ubuntu-font-family/UbuntuBetaMono-R-R21.ttf > UbuntuBetaMono-R-R21.bdf bdf2psf UbuntuBetaMono-R-R21.bdf /usr/share/bdf2psf/standard.equivalents /usr/share/bdf2psf/required.set+/usr/share/bdf2psf/useful.set 256 UbuntuBetaMono-R-R21.psf setfont -h17 UbuntuBetaMono-R-R21.psf The R21 Mono Beta has a cell bounding box of 482×1000 (including necessary leading and advance); this leads to bounding box of 8x17 rather than the traditional 8x16 and this is what the "-n17" forces upon loading. The result useful but very ugly because of the lack of manual hinting. We probably also want to make sure that at least all of the codepoints listed in the 'required.set' file are present and populated if we're going to replace the current default. = Eventually (11.10?) we should try to apply the Ubuntu fonts to the console as well. Steps 12–14 are blocked waiting for the Ubuntu Monospace to be released and available in the archive. 11) gfxboot-theme-ubuntu (Proportional) - bug #732854 12) Bterm (d-i) (Monospace) - 13) Grub2 (Monospace) - bug #729470 14) Console-setup (Monospace) - bug #724022 (this bug) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/724022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731522] Re: Cannot ping pod51041.outlook.com but can dig.
Additionally, I also looked at my nsswitch.conf file, the host line in it is: hosts: files mdns4_minimal [NOTFOUND=return] dns. I tried hosts: files dns, and all the combinations, but nothing works. -- 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/1731522 Title: Cannot ping pod51041.outlook.com but can dig. Status in systemd package in Ubuntu: New Bug description: Trying to resolve pod51041.outlook.com's domain name seems to fail for applications: $ ping pod51041.outlook.com ping: pod51041.outlook.com: Temporary failure in name resolution (Also can't access via thunderbird). However, it seems to work directly via systemd-resolve: $ systemd-resolve pod51041.outlook.com pod51041.outlook.com: 40.97.160.2 40.97.126.50 132.245.38.194 40.97.147.194 132.245.41.34 40.97.176.2 40.97.150.242 40.97.85.114 40.97.120.50 40.97.85.2 40.97.176.34 40.97.138.242 40.97.166.18 40.97.120.162 40.97.119.82 40.97.176.18 40.97.85.98 40.97.134.34 40.97.84.18 -- Information acquired via protocol DNS in 2.5ms. -- Data is authenticated: no It also works with dig and nslookup. Not quite sure why this is the case, I've spotted this issue upstream that looks similar: https://github.com/systemd/systemd/issues/6520. However, I'm not familiar enough with DNS to tell if it is the same issue. ProblemType: Bug 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 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Fri Nov 10 13:10:02 2017 InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 2324BB9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA6WW (2.66 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324BB9 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324BB9 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1731522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731522] Re: systemd-resolved sends SERVFAIL to host/nslookup for pod51041.outlook.com
The bug report here is likely inaccurate. I don't exactly know where the problem is. I did some tcpdumps for port 53 traffic. I see that if I did a ping, it requests for the A records of the domain name and indeed the IP addresses are getting returned. However, weirdly, ping then requests for the A records of pod51041.outlook.com.lan. .lan is the search domain on my network as specified with /etc/resolv.conf automatically. Furthermore, if I disable ipv6, thunderbird and firefox can access the domain, but ping still cannot. So I don't think this bug report should be filed against systemd, but I don't really know where the problem lies. ** Description changed: Trying to resolve pod51041.outlook.com's domain name seems to fail for applications: - $ nslookup - > host pod51041.outlook.com - Server: 127.0.0.53 - Address: 127.0.0.53#53 - - ** server can't find host: SERVFAIL - - - $ ping pod51041.outlook.com + $ ping pod51041.outlook.com ping: pod51041.outlook.com: Temporary failure in name resolution - (Also can't access via thunderbird). However, it seems to work directly via systemd-resolve: $ systemd-resolve pod51041.outlook.com pod51041.outlook.com: 40.97.160.2 - 40.97.126.50 - 132.245.38.194 - 40.97.147.194 - 132.245.41.34 - 40.97.176.2 - 40.97.150.242 - 40.97.85.114 - 40.97.120.50 - 40.97.85.2 - 40.97.176.34 - 40.97.138.242 - 40.97.166.18 - 40.97.120.162 - 40.97.119.82 - 40.97.176.18 - 40.97.85.98 - 40.97.134.34 - 40.97.84.18 + 40.97.126.50 + 132.245.38.194 + 40.97.147.194 + 132.245.41.34 + 40.97.176.2 + 40.97.150.242 + 40.97.85.114 + 40.97.120.50 + 40.97.85.2 + 40.97.176.34 + 40.97.138.242 + 40.97.166.18 + 40.97.120.162 + 40.97.119.82 + 40.97.176.18 + 40.97.85.98 + 40.97.134.34 + 40.97.84.18 -- Information acquired via protocol DNS in 2.5ms. -- Data is authenticated: no + + It also works with dig and nslookup. Not quite sure why this is the case, I've spotted this issue upstream that looks similar: https://github.com/systemd/systemd/issues/6520. However, I'm not familiar enough with DNS to tell if it is the same issue. ProblemType: Bug 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 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Fri Nov 10 13:10:02 2017 InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 2324BB9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA6WW (2.66 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324BB9 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324BB9 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO ** Summary changed: - systemd-resolved sends SERVFAIL to host/nslookup for pod51041.outlook.com + Cannot ping pod51041.outlook.com but can dig. -- 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/1731522 Title: Cannot ping pod51041.outlook.com but can dig. Status in systemd package in Ubuntu: New Bug description: Trying to resolve pod51041.outlook.com's domain name seems to fail for applications: $ ping pod51
[Touch-packages] [Bug 885092] Re: [pkg] Backport+SRU ubuntu-font-family=0.80 (minus Medium) for old supported
Thank you for reporting this bug to Ubuntu. The Ubuntu fonts are at version 0.80 in all supported Ubuntu releases. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases ** Changed in: ubuntu-font-family-sources (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/885092 Title: [pkg] Backport+SRU ubuntu-font-family=0.80 (minus Medium) for old supported Status in Lucid Backports: Won't Fix Status in ubuntu-font-family-sources package in Ubuntu: Won't Fix Bug description: Can you backport the 0.80 version of "ttf-ubuntu-font-family" from Oneiric or Precise for 10.04? The .deb and source code are available at http://archive.ubuntu.com/ubuntu/pool/main/u/ubuntu-font-family- sources/ and it would be a great way to give these fonts to users of the LTS versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/lucid-backports/+bug/885092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734806] [NEW] Reset Ubuntu to Factory Defaults
Public bug reported: Ubuntu users can really benefit from an easy GUI app built-into Ubuntu that allows the user to reset the OS to factory defaults and/or wipe the entire device, similar to the built-in Recovery options Microsoft offers users in Windows 10. There's already an app in development that works with Ubuntu called 'Resetter.' Maybe this or something like it can be implemented into the next release? https://github.com/gaining/Resetter ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.404.1 ProcVersionSignature: Ubuntu 4.13.0-17.20-lowlatency 4.13.8 Uname: Linux 4.13.0-17-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 27 23:59:04 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1734806 Title: Reset Ubuntu to Factory Defaults Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu users can really benefit from an easy GUI app built-into Ubuntu that allows the user to reset the OS to factory defaults and/or wipe the entire device, similar to the built-in Recovery options Microsoft offers users in Windows 10. There's already an app in development that works with Ubuntu called 'Resetter.' Maybe this or something like it can be implemented into the next release? https://github.com/gaining/Resetter ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.404.1 ProcVersionSignature: Ubuntu 4.13.0-17.20-lowlatency 4.13.8 Uname: Linux 4.13.0-17-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 27 23:59:04 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1734806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717737] Re: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status '
[Expired for graphite2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: graphite2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1717737 Title: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in graphite2 package in Ubuntu: Expired Bug description: tried to install gcc ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgraphite2-3:amd64 1.3.6-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: libgraphite2-3: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Sep 16 19:44:19 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2017-09-16 19:44:19 Commandline: apt-get install gcc Requested-By: kev (1000) DpkgTerminalLog: dpkg: error processing package libgraphite2-3:amd64 (--configure): package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-07-03 (75 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: graphite2 Title: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1717737/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1502173] Re: Python warnings: modules imported without specifying a version first
This is still happening in 17.10! Why is this marked as fixed several times but still propagating up the versions? This needs to be fixed once and for all. -- 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/1502173 Title: Python warnings: modules imported without specifying a version first Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Released Bug description: [Description] Users receive warnings about importing of python modules without a version being specified. While this isn't a big deal in itself we get lots of bug reports from people about this issue since it is so obvious. Given that Ubuntu 16.04 is an LTS release we should fix this and prevent further reporting of the issue. [Test Case] 1) run /usr/share/apport/apport-gtk in a terminal 2) Observe the following /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without specifying a version first. Use gi.require_version('GdkX11', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk with the version of apport in -proposed you'll no longer receive the warning. [Regression Potential]As with any SRU this could cause a regression in the software if the fix is typo'ed so review it carefully. If there isn't a typo and then the chance of a regression is very very very low. Original Description Hi, here is the problem: $ /usr/share/apport/apport-gtk /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without specifying a version first. Use gi.require_version('GdkX11', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk ProblemType: BugDistroRelease: Ubuntu 15.10 Package: apport-gtk 2.19-0ubuntu1 Uname: Linux 4.2.2-040202-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Fri Oct 2 16:17:14 2015 EcryptfsInUse: Yes PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1502173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734750] Re: Fail to shutdown system properly
** Changed in: network-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1734750 Title: Fail to shutdown system properly Status in network-manager package in Ubuntu: Invalid Bug description: I use Ubuntu Mate 17.10 installed from scratch on Lenovo ideapad 700-15ISK (standard hardware - no modifications). When I try to reboot or shutdown I see messages like: [ *** ] A stop job is running for Network Manager (/) OR [ *** ] A stop job is running for WPA supplicant (/) (Messages appears periodically, replacing each other), and later this INFO task kworker/ blocked for more than 120 seconds is added to the line Where could be different, for example: u8:2:169 or 0:1:33 If I wait about 6 or so minutes I finally can see: Reached target Shutdown But the laptop is still on and I have have to hold power button a few seconds to halt it. I've tried: - Update BIOS to the latest version - Update Intel microcode - Uncheck "Use Intel Microcode" from Device Manager - Install all updates But the problem is persistent and I run into it each time I want to shutdown/reboot my laptop. It even can be reproduced from live usb stick (reboot after install). However, during regular work everything is fine. Before I used Ubuntu Mate 17.04 and such problem appears in some rare cases on shutdown/reboot (hard to say exactly, roughly 1 of 10 or even more shutdowns). Before I created bug https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1733203 but it turned out to be two different bugs and there are attached photos of logs on shutdown. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Mon Nov 27 13:40:10 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-11-27 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d 802-11-wireless 1511807923 Mon 27 Nov 2017 01:38:43 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 9794efad-4922-3754-bb66-2a49594348d1 802-3-ethernet 1511807906 Mon 27 Nov 2017 01:38:26 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d /org/freedesktop/NetworkManager/ActiveConnection/1 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734794] Re: Install of ubuntu-desktop login loop
** Package changed: xorg (Ubuntu) => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1734794 Title: Install of ubuntu-desktop login loop Status in ubuntu-meta package in Ubuntu: New Bug description: Tested on clean VM. To repro install ubuntu-17.10 server edition > sudo apt update > sudo apt upgrade > sudo apt install ubuntu-desktop --no-install-recommends > sudo reboot # Reboots to graphical login screen. After entering username password returns to graphical login for both Ubuntu and Ubuntu on Xorg # Switch to tty2 > sudo apt install gsettings-ubuntu-schemas # Switch to tty1 # Login now works ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Mon Nov 27 19:50:24 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2017-11-28 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic root=UUID=3fb3b989-6bd0-43f4-a49e-04af4ecac2f2 ro rootflags=subvol=@ SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 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 N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1734794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734794] [NEW] Install of ubuntu-desktop login loop
Public bug reported: Tested on clean VM. To repro install ubuntu-17.10 server edition > sudo apt update > sudo apt upgrade > sudo apt install ubuntu-desktop --no-install-recommends > sudo reboot # Reboots to graphical login screen. After entering username password returns to graphical login for both Ubuntu and Ubuntu on Xorg # Switch to tty2 > sudo apt install gsettings-ubuntu-schemas # Switch to tty1 # Login now works ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Mon Nov 27 19:50:24 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2017-11-28 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic root=UUID=3fb3b989-6bd0-43f4-a49e-04af4ecac2f2 ro rootflags=subvol=@ SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 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 N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful crash ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1734794 Title: Install of ubuntu-desktop login loop Status in xorg package in Ubuntu: New Bug description: Tested on clean VM. To repro install ubuntu-17.10 server edition > sudo apt update > sudo apt upgrade > sudo apt install ubuntu-desktop --no-install-recommends > sudo reboot # Reboots to graphical login screen. After entering username password returns to graphical login for both Ubuntu and Ubuntu on Xorg # Switch to tty2 > sudo apt install gsettings-ubuntu-schemas # Switch to tty1 # Login now works ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Mon Nov 27 19:50:24 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2017-11-28 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic root=UUID=3fb3b989-6bd0-43f4-a49e-04af4ecac2f2 ro rootflags=subvol=@ SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh ins
[Touch-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock
Just sent a new merge request. https://code.launchpad.net/~hui.wang/pulseaudio/+git/pulseaudio/+merge/334346 -- 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/1718824 Title: The analogue audio does not work on the Dell USB Dock Status in HWE Next: In Progress Status in pulseaudio package in Ubuntu: In Progress Bug description: SRU Document: [Impact] If users use the latest Dell USB Dock, e.g. TB16, they will found the analog audio (lineout jack) can't work under ubuntu linux [Test Case] After applying the fix, users can play sound via analog speaker or lineout freely. Without the fix, users can't play sound from lineout jack. [Regression Potential] No any possibility to introduce regression since this fix just adding a new dock's support, it does not change any existing code. [Other Info] No more info here Steps: 1. Cold boot system with BME/IE connected 2. Plug in a speaker to Line-out jack 3. Set Analog Stereo Output from Sound settings Expected results: Line-out port can work Actual results: Line-out port not work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression
How long did the benchmarks actually take? The sum of the runtimes appears to be about 11 seconds. Is that correct? Is that long enough to draw useful conclusions from the results? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression Status in python2.7 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: Confirmed Bug description: I work on the OpenStack-Ansible project and we've noticed that testing jobs on 16.04 take quite a bit longer to complete than on 14.04. They complete within an hour on 14.04 but they normally take 90 minutes or more on 16.04. We use the same version of Ansible with both versions of Ubuntu. After more digging, I tested python performance (using the 'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There is a significant performance difference between each version of python. That is detailed in a spreadsheet[0]. I began using perf to dig into the differences when running the python performance module and when using Ansible playbooks. CPU migrations (as measured by perf) are doubled in Ubuntu 16.04 when running the same python workloads. I tried changing some of the kerne.sched sysctl configurables but they had very little effect on the results. I compiled python 2.7.12 from source on 14.04 and found the performance to be unchanged there. I'm not entirely sure where the problem might be now. We also have a bug open in OpenStack-Ansible[1] that provides additional detail. Thanks in advance for any help you can provide! [0] https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression
I don't feel like the change from fstack-protector-strong to fstack-protector should be made. The performance testing results in the spreadsheet don't suggest that the change positively impacts performance in a meaningful way. fstack-protector-strong slightly outperforms fstack-protector in some situations and slightly under performs in others, suggesting that the difference is within the noise threshold. I'd strongly prefer that we continue to use fstack-protector-strong. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression Status in python2.7 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: Confirmed Bug description: I work on the OpenStack-Ansible project and we've noticed that testing jobs on 16.04 take quite a bit longer to complete than on 14.04. They complete within an hour on 14.04 but they normally take 90 minutes or more on 16.04. We use the same version of Ansible with both versions of Ubuntu. After more digging, I tested python performance (using the 'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There is a significant performance difference between each version of python. That is detailed in a spreadsheet[0]. I began using perf to dig into the differences when running the python performance module and when using Ansible playbooks. CPU migrations (as measured by perf) are doubled in Ubuntu 16.04 when running the same python workloads. I tried changing some of the kerne.sched sysctl configurables but they had very little effect on the results. I compiled python 2.7.12 from source on 14.04 and found the performance to be unchanged there. I'm not entirely sure where the problem might be now. We also have a bug open in OpenStack-Ansible[1] that provides additional detail. Thanks in advance for any help you can provide! [0] https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain
My understanding is that systemd-resolved as shipped in Ubuntu is meant to not have DNS caching enabled at all. https://lists.ubuntu.com/archives/ubuntu-devel/2016-June/039375.html Looking at the default resolved.conf and the resolved.conf(5) manpage, it appears we do have DNS caching enabled. Dimitri, is this an oversight, or was there some further discussion with the Security Team that resulted in caching being enabled? -- 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/1727237 Title: systemd-resolved is not finding a domain Status in systemd package in Ubuntu: Triaged Bug description: I have an odd network situation that I have so far managed to narrow down to the inability to resolve a domain via systemd-resolved which is resolvable with nslookup. If I use nslookup against the two nameservers on this network I get answers for the domain, but ping says it is unable to resolve the same domain (as do browsers and crucially the captive portal mechanism). Here are details: NSLOOKUP: ~$ nslookup securelogin.arubanetworks.com 208.67.220.220 Server: 208.67.220.220 Address: 208.67.220.220#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 ~$ nslookup securelogin.arubanetworks.com 208.67.222.222 Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 PING: ~$ ping securelogin.arubanetworks.com ping: securelogin.arubanetworks.com: Name or service not known mark@mark-X1Y2:~$ DIG: ~$ dig @208.67.222.222 securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; AUTHORITY SECTION: arubanetworks.com.1991IN SOA dns5.arubanetworks.com. hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400 ;; Query time: 34 msec ;; SERVER: 208.67.222.222#53(208.67.222.222) ;; WHEN: Wed Oct 25 10:31:10 CEST 2017 ;; MSG SIZE rcvd: 144 MORE DIG: ~$ dig securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Oct 25 10:34:01 CEST 2017 ;; MSG SIZE rcvd: 58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 332309] Re: Support QuickTime VR files with interactive elements
** Changed in: gst-plugins-good Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/332309 Title: Support QuickTime VR files with interactive elements Status in gst-plugins-good: Won't Fix Status in gst-plugins-good0.10 package in Ubuntu: Triaged Bug description: Binary package hint: totem-mozilla totem-mozilla | 2.24.3-0ubuntu1 ubuntu 8.10 Totem Browser Plugin plays VR as a series of photos http://www.apple.com/quicktime/technologies/qtvr/gallery/times_square.html To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-good/+bug/332309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734073] Re: idk
*** This bug is a duplicate of bug 1734069 *** https://bugs.launchpad.net/bugs/1734069 ** Information type changed from Private Security to Public ** This bug has been marked a duplicate of bug 1734069 idk -- 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/1734073 Title: idk Status in xorg package in Ubuntu: New Bug description: idk ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic i686 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: i386 CompositorRunning: None Date: Thu Nov 23 01:59:44 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] InstallationDate: Installed on 2017-10-30 (24 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 (20171017.1) MachineType: LENOVO 4186 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 15CN31WW(V2.04) dmi.board.name: KIWB1 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 4186 dmi.product.version: Lenovo IdeaPad Y550 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 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: Thu Nov 23 01:49:56 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734072] Re: idk
*** This bug is a duplicate of bug 1734069 *** https://bugs.launchpad.net/bugs/1734069 ** Information type changed from Private Security to Public ** This bug has been marked a duplicate of bug 1734069 idk -- 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/1734072 Title: idk Status in xorg package in Ubuntu: New Bug description: idk ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic i686 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: i386 CompositorRunning: None Date: Thu Nov 23 01:59:44 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] InstallationDate: Installed on 2017-10-30 (24 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 (20171017.1) MachineType: LENOVO 4186 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 15CN31WW(V2.04) dmi.board.name: KIWB1 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 4186 dmi.product.version: Lenovo IdeaPad Y550 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 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: Thu Nov 23 01:49:56 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734072/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734071] Re: idk
*** This bug is a duplicate of bug 1734069 *** https://bugs.launchpad.net/bugs/1734069 ** Information type changed from Private Security to Public ** This bug has been marked a duplicate of bug 1734069 idk -- 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/1734071 Title: idk Status in xorg package in Ubuntu: New Bug description: idk ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic i686 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: i386 CompositorRunning: None Date: Thu Nov 23 01:59:44 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] InstallationDate: Installed on 2017-10-30 (24 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 (20171017.1) MachineType: LENOVO 4186 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 15CN31WW(V2.04) dmi.board.name: KIWB1 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 4186 dmi.product.version: Lenovo IdeaPad Y550 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 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: Thu Nov 23 01:49:56 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734071/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722564] Re: apport question will not accept multi-character responses
** Changed in: apport (Ubuntu Zesty) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1722564 Title: apport question will not accept multi-character responses Status in Apport: Confirmed Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Zesty: New Status in apport source package in Artful: Fix Committed Bug description: === Begin SRU Template === [Impact] Packages which provide apport integration with more than 9 options in a choice will not be able to select options numbered >= 10 on the commandline using 'ubuntu-bug ' [Test Case] Overview: 1. Update to proposed versions of cloud-init v. 17.1 and apport v. 2. Run 'ubuntu-bug cloud-init' attempt to report a bug on a cloud choice greater than 9 3. View report and make sure the proper cloud is reported Script: if [ ! -f './lxc-proposed-snapshot' ]; then wget https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot; chmod 755 lxc-proposed-snapshot; fi for release in xenial artful; do ref=$release-proposed; echo "$release START --"; lxc-proposed-snapshot --proposed --publish $release $ref; lxc init $ref test-$release; lxc start test-$release; lxc exec test-$release -- apt install apport; lxc exec test-$release -- dpkg-query --show apport; lxc exec test-$release -- ubuntu-bug cloud-init; done [Regression Potential] Minimal. This bug only affects packages with >9 bug filing options for a given choice. Worst case, is bugs filed would incorrectly represent option 1 of a selection instead of option 1X. === End SRU Template === === original description === the newly added cloud-init apport support shows a list of cloud providers and asks the user to select one. There are currently 18 options. For any option > 10, apport will just take the '1' that is typed as the answer. It should obviously wait for more than one character or a carriage return. *** Please select the cloud vendor or environment in which this instance is running Choices: 1: Amazon - Ec2 2: AliYun 3: AltCloud 4: Azure 5: Bigstep 6: CloudSigma 7: CloudStack 8: DigitalOcean 9: GCE - Google Compute Engine 10: MAAS 11: NoCloud 12: OpenNebula 13: OpenStack 14: OVF 15: Scaleway 16: SmartOS 17: VMware 18: Other C: Cancel Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu2 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 Architecture: amd64 Date: Tue Oct 10 15:21:48 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1722564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734074] Re: idk
*** This bug is a duplicate of bug 1734069 *** https://bugs.launchpad.net/bugs/1734069 ** Information type changed from Private Security to Public ** This bug has been marked a duplicate of bug 1734069 idk -- 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/1734074 Title: idk Status in xorg package in Ubuntu: New Bug description: idk ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic i686 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: i386 CompositorRunning: None Date: Thu Nov 23 01:59:44 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] InstallationDate: Installed on 2017-10-30 (24 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 (20171017.1) MachineType: LENOVO 4186 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 15CN31WW(V2.04) dmi.board.name: KIWB1 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 4186 dmi.product.version: Lenovo IdeaPad Y550 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 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: Thu Nov 23 01:49:56 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734070] Re: idk
*** This bug is a duplicate of bug 1734069 *** https://bugs.launchpad.net/bugs/1734069 ** Information type changed from Private Security to Public ** This bug has been marked a duplicate of bug 1734069 idk -- 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/1734070 Title: idk Status in xorg package in Ubuntu: New Bug description: idk ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic i686 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: i386 CompositorRunning: None Date: Thu Nov 23 01:59:44 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] InstallationDate: Installed on 2017-10-30 (24 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 (20171017.1) MachineType: LENOVO 4186 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 15CN31WW(V2.04) dmi.board.name: KIWB1 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 4186 dmi.product.version: Lenovo IdeaPad Y550 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 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: Thu Nov 23 01:49:56 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734070/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734069] Re: idk
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1734069 Title: idk Status in xorg package in Ubuntu: Incomplete Bug description: idk ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic i686 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: i386 CompositorRunning: None Date: Thu Nov 23 01:59:44 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] InstallationDate: Installed on 2017-10-30 (24 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 (20171017.1) MachineType: LENOVO 4186 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 15CN31WW(V2.04) dmi.board.name: KIWB1 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 4186 dmi.product.version: Lenovo IdeaPad Y550 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 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: Thu Nov 23 01:49:56 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722564] Re: apport question will not accept multi-character responses
** Also affects: apport (Ubuntu Zesty) Importance: Undecided Status: New -- 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/1722564 Title: apport question will not accept multi-character responses Status in Apport: Confirmed Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Zesty: New Status in apport source package in Artful: Fix Committed Bug description: === Begin SRU Template === [Impact] Packages which provide apport integration with more than 9 options in a choice will not be able to select options numbered >= 10 on the commandline using 'ubuntu-bug ' [Test Case] Overview: 1. Update to proposed versions of cloud-init v. 17.1 and apport v. 2. Run 'ubuntu-bug cloud-init' attempt to report a bug on a cloud choice greater than 9 3. View report and make sure the proper cloud is reported Script: if [ ! -f './lxc-proposed-snapshot' ]; then wget https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot; chmod 755 lxc-proposed-snapshot; fi for release in xenial artful; do ref=$release-proposed; echo "$release START --"; lxc-proposed-snapshot --proposed --publish $release $ref; lxc init $ref test-$release; lxc start test-$release; lxc exec test-$release -- apt install apport; lxc exec test-$release -- dpkg-query --show apport; lxc exec test-$release -- ubuntu-bug cloud-init; done [Regression Potential] Minimal. This bug only affects packages with >9 bug filing options for a given choice. Worst case, is bugs filed would incorrectly represent option 1 of a selection instead of option 1X. === End SRU Template === === original description === the newly added cloud-init apport support shows a list of cloud providers and asks the user to select one. There are currently 18 options. For any option > 10, apport will just take the '1' that is typed as the answer. It should obviously wait for more than one character or a carriage return. *** Please select the cloud vendor or environment in which this instance is running Choices: 1: Amazon - Ec2 2: AliYun 3: AltCloud 4: Azure 5: Bigstep 6: CloudSigma 7: CloudStack 8: DigitalOcean 9: GCE - Google Compute Engine 10: MAAS 11: NoCloud 12: OpenNebula 13: OpenStack 14: OVF 15: Scaleway 16: SmartOS 17: VMware 18: Other C: Cancel Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu2 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 Architecture: amd64 Date: Tue Oct 10 15:21:48 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1722564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732172] Re: [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04
Thanks for taking the time to report this bug and make Ubuntu better. You can see more information about these CVEs by using the CVE tracker. See https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-8858.html https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-10009.html https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-10010.html https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-10011.html https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-10012.html CVE-2016-8858 is disputed by upstream since the attacker can only DOS their own connection. CVE-2016-10012 is related to pre-auth compression which has been disabled by default for > 10 years. CVE-2016-10010 is only impactful if privilege separation is not used, however, privilege separation is enabled by default. CVE-2016-10009 and CVE-2016-20011 are both low priority. These issues are on the list to be fixed and will be fixed as soon as possible based on their priority. Will your scanning software allow you to annotate findings? ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-20011 -- 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/1732172 Title: [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04 Status in openssh package in Ubuntu: New Bug description: Does anyone know when the following OpenSSH venerabilities will be patched on Ubuntu 14.04 CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012, CVE-2016-8858 As these are coming up repeatedly on or security scans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1732172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
We will still need something that helps ensure systemd-resolved runs we reach network-online.target; and I suspect (though I've not validated yet) that we really want systemd-resolved to be running prior to systemd-networkd such that systemd-networkd can relay DNS configuration info retrieved from DHCP results, ala how resolvconf was hooked on networking config touching files in /run. -- 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/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in cloud-init source package in Zesty: Fix Released Status in systemd source package in Zesty: Fix Released Status in cloud-init source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in cloud-init source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes: -smbios "type=1,serial=ds=nocloud- net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud- metadata/linuxtst/" As documented here: http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine. I don't know if nameservice not working is by design, but it seems like it should work. The documentation states: "With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"; And https is not going to work for a raw IP address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
I agree that systemd-resolved should be DefaultDependencies=no. Of the individual dependencies of sysinit.target.wants, I'm guessing it should be After=systemd-journald.service systemd-machine-id- commit.service and possibly After=systemd-random-seed.service. -- 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/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in cloud-init source package in Zesty: Fix Released Status in systemd source package in Zesty: Fix Released Status in cloud-init source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in cloud-init source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes: -smbios "type=1,serial=ds=nocloud- net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud- metadata/linuxtst/" As documented here: http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine. I don't know if nameservice not working is by design, but it seems like it should work. The documentation states: "With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"; And https is not going to work for a raw IP address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
I suspect because in bionic/artful we're missing resolvconf package, that the systemd-resolved service ends up starting later in boot. The systemd-resolved-update-resolveconf.{service,path} require /sbin/resolvconf to run; this service had a path-based trigger that would get hooked whenever DHCP clients would call resolvconf to kick off a DNS update once config was available. I suspect that systemd-networkd itself isn't poking DNS service properly after acquiring information. The dependency loop comes from systemd-resolved using default dependencies which run after when cloud-init.service would run. This then needs systemd-resolved to specify DefaultDependencies=No and something like network-online.target to require systemd-resolved. I modified cloud-init.service to include an After=systemd- resolved.service but some other service may require dns, so I feel this is a property of network-online.target. -- 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/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in cloud-init source package in Zesty: Fix Released Status in systemd source package in Zesty: Fix Released Status in cloud-init source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in cloud-init source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes: -smbios "type=1,serial=ds=nocloud- net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud- metadata/linuxtst/" As documented here: http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine. I don't know if nameservice not working is by design, but it seems like it should work. The documentation states: "With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"; And https is not going to work for a raw IP address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
To be clear, the suggestion that xnox made causes a ordering cycle. ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- 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/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in cloud-init source package in Zesty: Fix Released Status in systemd source package in Zesty: Fix Released Status in cloud-init source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in cloud-init source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes: -smbios "type=1,serial=ds=nocloud- net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud- metadata/linuxtst/" As documented here: http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine. I don't know if nameservice not working is by design, but it seems like it should work. The documentation states: "With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"; And https is not going to work for a raw IP address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
Sorry for the delay - I was away for a week. I have deployed the packages from -proposed and will confirm after keeping an eye on DHCP lease renewals for a while. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: SRU REQUEST: Debdiff (nm-dhcp-helper.debdiff) attached. Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug was fixed upstream in 1.4. [Impact] * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP lease renewal due to a DBus race condition. * Upstream NetworkManager 1.4 fixes the race condition by changing nm-dhcp-helper's DBus notification from signal "Event" to method "Notify". * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's NM 1.2.x. [Test Case] * Not reliably reproducible. Out of hundreds of machines, only a dozen or so fail to notify NetworkManager of a DHCP lease renewal about 30-50% of the time. (i.e. It's always the same handful of machines that fail.) * All such machines with the patched packages have been fine for weeks, over many dozens of lease renewals. [Regression Potential] * The patch changes both nm-dhcp-helper and NetworkManager itself. As soon as the new packages are unpacked, the new nm-dhcp-helper will be used on DHCP lease renewals, with the new Notify mechanism. Since the running, old NetworkManager is still expecting Event notifications, the patched nm-dhcp-helper has fallback capability to Event. * Once NetworkManager is restarted and is running the patched version, it will have the new Notify support. [Other Info] * Upstream bug w/ patch: https://bugzilla.gnome.org/show_bug.cgi?id=784636 * RHEL bug with links to the 1.4 commits from which the patch was derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 * NOTE: The final comment on the upstream GNOME bug claims that the fix is incomplete. However, it is possible that the running NetworkManager was not restarted (see Regression Potential notes above), which is why nm-dhcp-helper is falling back to Event. The remainder of the log messages in that final comment are from a custom wrapper the submitter was running around nm-dhcp-helper. I have deployed the exact same patch (without said wrapper) to real-world systems and tested extensively, and see nothing but successful DHCP lease renewal notifications using D-Bus Notify, not D-Bus Event. I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound
[Touch-packages] [Bug 1734756] [NEW] package click-apparmor (not installed) failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1
Public bug reported: This error message comes up regularly after upgrade of Ubuntu Media installation from Zesty to Artful. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: click-apparmor (not installed) ProcVersionSignature: Ubuntu 4.13.0-18.21-lowlatency 4.13.13 Uname: Linux 4.13.0-18-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Sun Nov 26 21:58:45 2017 ErrorMessage: underprosessen installerte pre-removal-skript returnerte feilstatus 1 InstallationDate: Installed on 2015-09-11 (808 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422) 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: click-apparmor Title: package click-apparmor (not installed) failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1 UpgradeStatus: Upgraded to artful on 2017-05-22 (189 days ago) ** Affects: click-apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1734756 Title: package click-apparmor (not installed) failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1 Status in click-apparmor package in Ubuntu: New Bug description: This error message comes up regularly after upgrade of Ubuntu Media installation from Zesty to Artful. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: click-apparmor (not installed) ProcVersionSignature: Ubuntu 4.13.0-18.21-lowlatency 4.13.13 Uname: Linux 4.13.0-18-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Sun Nov 26 21:58:45 2017 ErrorMessage: underprosessen installerte pre-removal-skript returnerte feilstatus 1 InstallationDate: Installed on 2015-09-11 (808 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422) 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: click-apparmor Title: package click-apparmor (not installed) failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1 UpgradeStatus: Upgraded to artful on 2017-05-22 (189 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1734756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734750] Re: Fail to shutdown system properly
I decided to update system again after bug report and... it gone. Sorry for disturbing. Seems this issue can be closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1734750 Title: Fail to shutdown system properly Status in network-manager package in Ubuntu: New Bug description: I use Ubuntu Mate 17.10 installed from scratch on Lenovo ideapad 700-15ISK (standard hardware - no modifications). When I try to reboot or shutdown I see messages like: [ *** ] A stop job is running for Network Manager (/) OR [ *** ] A stop job is running for WPA supplicant (/) (Messages appears periodically, replacing each other), and later this INFO task kworker/ blocked for more than 120 seconds is added to the line Where could be different, for example: u8:2:169 or 0:1:33 If I wait about 6 or so minutes I finally can see: Reached target Shutdown But the laptop is still on and I have have to hold power button a few seconds to halt it. I've tried: - Update BIOS to the latest version - Update Intel microcode - Uncheck "Use Intel Microcode" from Device Manager - Install all updates But the problem is persistent and I run into it each time I want to shutdown/reboot my laptop. It even can be reproduced from live usb stick (reboot after install). However, during regular work everything is fine. Before I used Ubuntu Mate 17.04 and such problem appears in some rare cases on shutdown/reboot (hard to say exactly, roughly 1 of 10 or even more shutdowns). Before I created bug https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1733203 but it turned out to be two different bugs and there are attached photos of logs on shutdown. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Mon Nov 27 13:40:10 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-11-27 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d 802-11-wireless 1511807923 Mon 27 Nov 2017 01:38:43 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 9794efad-4922-3754-bb66-2a49594348d1 802-3-ethernet 1511807906 Mon 27 Nov 2017 01:38:26 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d /org/freedesktop/NetworkManager/ActiveConnection/1 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734756] Re: package click-apparmor (not installed) failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1734756 Title: package click-apparmor (not installed) failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1 Status in click-apparmor package in Ubuntu: New Bug description: This error message comes up regularly after upgrade of Ubuntu Media installation from Zesty to Artful. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: click-apparmor (not installed) ProcVersionSignature: Ubuntu 4.13.0-18.21-lowlatency 4.13.13 Uname: Linux 4.13.0-18-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Sun Nov 26 21:58:45 2017 ErrorMessage: underprosessen installerte pre-removal-skript returnerte feilstatus 1 InstallationDate: Installed on 2015-09-11 (808 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422) 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: click-apparmor Title: package click-apparmor (not installed) failed to install/upgrade: underprosessen installerte pre-removal-skript returnerte feilstatus 1 UpgradeStatus: Upgraded to artful on 2017-05-22 (189 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1734756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain
-- 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/1727237 Title: systemd-resolved is not finding a domain Status in systemd package in Ubuntu: Triaged Bug description: I have an odd network situation that I have so far managed to narrow down to the inability to resolve a domain via systemd-resolved which is resolvable with nslookup. If I use nslookup against the two nameservers on this network I get answers for the domain, but ping says it is unable to resolve the same domain (as do browsers and crucially the captive portal mechanism). Here are details: NSLOOKUP: ~$ nslookup securelogin.arubanetworks.com 208.67.220.220 Server: 208.67.220.220 Address: 208.67.220.220#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 ~$ nslookup securelogin.arubanetworks.com 208.67.222.222 Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 PING: ~$ ping securelogin.arubanetworks.com ping: securelogin.arubanetworks.com: Name or service not known mark@mark-X1Y2:~$ DIG: ~$ dig @208.67.222.222 securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; AUTHORITY SECTION: arubanetworks.com.1991IN SOA dns5.arubanetworks.com. hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400 ;; Query time: 34 msec ;; SERVER: 208.67.222.222#53(208.67.222.222) ;; WHEN: Wed Oct 25 10:31:10 CEST 2017 ;; MSG SIZE rcvd: 144 MORE DIG: ~$ dig securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Oct 25 10:34:01 CEST 2017 ;; MSG SIZE rcvd: 58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain
So I managed to reproduce this in a way that looks correct (Starbucks WiFi here uses Datavalet but fails in a way that looks the same: it thinks you're logged in once you clicked the "Login" button on the captive portal page once, but then updates DNS, but still attempts to look up secure.datavalet.io (but this is no longer resolving because we're in the public side now); and once you try to hit another site, you did not get to the "landing" page on the public side so it thinks you're still unauthenticated. One one hand, this looks like just really terrible behavior of the captive portal, and it "worked" only because we were pretty slow to deal with the changing settings; or because we were caching the DNS responses for just long enough. I got logs from my reproducer as well as packet captures, and I will have to comb through them to figure out if there's anything really obscure and wrong, but my initial guess is that this is an issue related to DNS caching. Probably the cache is invalidated when the IP changes as we get to the public side, but ought to retain the resolution address for the portal. It needs a little more investigation and testing, but I think this qualifies as "Triaged" now; and should have some fix or workaround to deal with Aruba and Datavalet, both are reasonably common hotspot infrastructure. ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1727237 Title: systemd-resolved is not finding a domain Status in systemd package in Ubuntu: Triaged Bug description: I have an odd network situation that I have so far managed to narrow down to the inability to resolve a domain via systemd-resolved which is resolvable with nslookup. If I use nslookup against the two nameservers on this network I get answers for the domain, but ping says it is unable to resolve the same domain (as do browsers and crucially the captive portal mechanism). Here are details: NSLOOKUP: ~$ nslookup securelogin.arubanetworks.com 208.67.220.220 Server: 208.67.220.220 Address: 208.67.220.220#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 ~$ nslookup securelogin.arubanetworks.com 208.67.222.222 Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 PING: ~$ ping securelogin.arubanetworks.com ping: securelogin.arubanetworks.com: Name or service not known mark@mark-X1Y2:~$ DIG: ~$ dig @208.67.222.222 securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; AUTHORITY SECTION: arubanetworks.com.1991IN SOA dns5.arubanetworks.com. hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400 ;; Query time: 34 msec ;; SERVER: 208.67.222.222#53(208.67.222.222) ;; WHEN: Wed Oct 25 10:31:10 CEST 2017 ;; MSG SIZE rcvd: 144 MORE DIG: ~$ dig securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Oct 25 10:34:01 CEST 2017 ;; MSG SIZE rcvd: 58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734750] [NEW] Fail to shutdown system properly
Public bug reported: I use Ubuntu Mate 17.10 installed from scratch on Lenovo ideapad 700-15ISK (standard hardware - no modifications). When I try to reboot or shutdown I see messages like: [ *** ] A stop job is running for Network Manager (/) OR [ *** ] A stop job is running for WPA supplicant (/) (Messages appears periodically, replacing each other), and later this INFO task kworker/ blocked for more than 120 seconds is added to the line Where could be different, for example: u8:2:169 or 0:1:33 If I wait about 6 or so minutes I finally can see: Reached target Shutdown But the laptop is still on and I have have to hold power button a few seconds to halt it. I've tried: - Update BIOS to the latest version - Update Intel microcode - Uncheck "Use Intel Microcode" from Device Manager - Install all updates But the problem is persistent and I run into it each time I want to shutdown/reboot my laptop. It even can be reproduced from live usb stick (reboot after install). However, during regular work everything is fine. Before I used Ubuntu Mate 17.04 and such problem appears in some rare cases on shutdown/reboot (hard to say exactly, roughly 1 of 10 or even more shutdowns). Before I created bug https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1733203 but it turned out to be two different bugs and there are attached photos of logs on shutdown. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Mon Nov 27 13:40:10 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-11-27 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d 802-11-wireless 1511807923 Mon 27 Nov 2017 01:38:43 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 9794efad-4922-3754-bb66-2a49594348d1 802-3-ethernet 1511807906 Mon 27 Nov 2017 01:38:26 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d /org/freedesktop/NetworkManager/ActiveConnection/1 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1734750 Title: Fail to shutdown system properly Status in network-manager package in Ubuntu: New Bug description: I use Ubuntu Mate 17.10 installed from scratch on Lenovo ideapad 700-15ISK (standard hardware - no modifications). When I try to reboot or shutdown I see messages like: [ *** ] A stop job is running for Network Manager (/) OR [ *** ] A stop job is running for WPA supplicant (/) (Messages appears periodically, replacing each other), and later this INFO task kworker/ blocked for more than 120 seconds is added to the line Where could be different, for example: u8:2:169 or 0:1:33 If I wait about 6 or so minutes I f
[Touch-packages] [Bug 1734745] [NEW] NM assumes avahi ip addres and default gw for disconnected device
Public bug reported: I have an Ubuntu 17.10 box with WiFi and Ethernet devices. The ethernet device is not connected at all. The WiFi is connected to WiFi network. The problem is, the connection drops itself after a while. I did some research and find out, the NM creates a new connection for the ethernet device, assuming Avahi IP for that connection, actually making this device a default route in a routing table. Thus, all outgoing packets are going through a non-connected ethernet device instead of gateway in WiFi network. See commands output for details. If I delete that default route manually, re-run dhclient to get a new route or disconnect enp9s0 using NM, the internet start working again. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "commands_output" https://bugs.launchpad.net/bugs/1734745/+attachment/5015325/+files/commands_output -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1734745 Title: NM assumes avahi ip addres and default gw for disconnected device Status in network-manager package in Ubuntu: New Bug description: I have an Ubuntu 17.10 box with WiFi and Ethernet devices. The ethernet device is not connected at all. The WiFi is connected to WiFi network. The problem is, the connection drops itself after a while. I did some research and find out, the NM creates a new connection for the ethernet device, assuming Avahi IP for that connection, actually making this device a default route in a routing table. Thus, all outgoing packets are going through a non-connected ethernet device instead of gateway in WiFi network. See commands output for details. If I delete that default route manually, re-run dhclient to get a new route or disconnect enp9s0 using NM, the internet start working again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731796] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878]
Or nvidia ** Also affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1731796 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878] Status in glib2.0 package in Ubuntu: New Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: This is a bug report about errors during the upgrade process. I don't know whether or not my samba installation was working immediately before the upgrade; the windows box that was intended to be a client died and has not been replaced. Don't believe my answers to the forced questions. *** My ubuntu system locks up regularly. Bugs I've reported about this get closed for inattention, after being ignored, and queries about how to do basic debugging get the same treatment, so I just power cycle whenever it happens again. This time the lock up happened while the GUI upgrade-everything-to- latest tool was running. When I power cycled the box to recover, the system was unusable - flashing "system problem detected" popups, none staying stable long enough to respond. ssh + "sudo apt-get update" + "sudo apt-get upgrade" pointed me to "sudo dpkg --configure -a" That command reported numerous errors - I don't know which of them are "normal" for this system, but hidden by the GUI, and which are new. But it got the system semi-usable from the GUI, so now I'm clicking on "yes, report it" for the many pop-ups, of which this is one. FWIW, samba is one of the ones "dpkg --reconfigure -a" complained about. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Nov 12 11:07:42 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2012-04-26 (2026 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) NmbdLog: OtherFailedConnect: Yes RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SambaServerRegression: Yes SmbConfIncluded: Yes SmbLog: SourcePackage: samba Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-03-31 (226 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1731796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731796] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878]
I added an nvidia task to the bug so its maintainer can take a look to see if it's related or not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1731796 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878] Status in glib2.0 package in Ubuntu: New Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: This is a bug report about errors during the upgrade process. I don't know whether or not my samba installation was working immediately before the upgrade; the windows box that was intended to be a client died and has not been replaced. Don't believe my answers to the forced questions. *** My ubuntu system locks up regularly. Bugs I've reported about this get closed for inattention, after being ignored, and queries about how to do basic debugging get the same treatment, so I just power cycle whenever it happens again. This time the lock up happened while the GUI upgrade-everything-to- latest tool was running. When I power cycled the box to recover, the system was unusable - flashing "system problem detected" popups, none staying stable long enough to respond. ssh + "sudo apt-get update" + "sudo apt-get upgrade" pointed me to "sudo dpkg --configure -a" That command reported numerous errors - I don't know which of them are "normal" for this system, but hidden by the GUI, and which are new. But it got the system semi-usable from the GUI, so now I'm clicking on "yes, report it" for the many pop-ups, of which this is one. FWIW, samba is one of the ones "dpkg --reconfigure -a" complained about. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Nov 12 11:07:42 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2012-04-26 (2026 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) NmbdLog: OtherFailedConnect: Yes RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SambaServerRegression: Yes SmbConfIncluded: Yes SmbLog: SourcePackage: samba Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-03-31 (226 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1731796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716190] Re: apt-key does not output to non-terminals
Or maybe we did, but I'm not sure where. ** Changed in: apt (Ubuntu) Status: Incomplete => Triaged ** Summary changed: - apt-key does not output to non-terminals + apt-key does not print Key fingerprint = in front of fingerprints ** Summary changed: - apt-key does not print Key fingerprint = in front of fingerprints + apt-key does not print "Key fingerprint =" in front of fingerprints -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1716190 Title: apt-key does not print "Key fingerprint =" in front of fingerprints Status in apt package in Ubuntu: Triaged Bug description: A common idiom for checking fingerprints for keys begins with: ' apt-key fingerprint $key|grep fingerprint|...' ... this works up to thru jessie at least.. in zesty apt-key gives a 'warning' but produces no output. "Warning: apt-key output should not be parsed (stdout is not a terminal)" If the lack of output is intended and is meant to be a proscription, it is overreaching at best. A warning makes perfect sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apt 1.4 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Sun Sep 10 01:23:46 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1716190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716190] Re: apt-key does not output to non-terminals
gpg changed the output format later on to remove "Key fingerprint=". jak@jak-x230:~/Projects/Debian/apt:master$ docker run --rm -it ubuntu:xenial sh -c 'apt-key fingerprint' /etc/apt/trusted.gpg pub 1024D/437D05B5 2004-09-12 Key fingerprint = 6302 39CC 130E 1A7F D81A 27B1 4097 6EAF 437D 05B5 uid Ubuntu Archive Automatic Signing Key sub 2048g/79164387 2004-09-12 pub 4096R/C0B21F32 2012-05-11 Key fingerprint = 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid Ubuntu Archive Automatic Signing Key (2012) pub 4096R/EFE21092 2012-05-11 Key fingerprint = 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 uid Ubuntu CD Image Automatic Signing Key (2012) pub 1024D/FBB75451 2004-12-30 Key fingerprint = C598 6B4F 1257 FFA8 6632 CBA7 4618 1433 FBB7 5451 uid Ubuntu CD Image Automatic Signing Key jak@jak-x230:~/Projects/Debian/apt:master$ docker run --rm -it ubuntu:zesty sh -c 'apt-key fingerprint' /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg -- pub rsa4096 2012-05-11 [SC] 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid [ unknown] Ubuntu Archive Automatic Signing Key (2012) /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg -- pub rsa4096 2012-05-11 [SC] 8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092 uid [ unknown] Ubuntu CD Image Automatic Signing Key (2012) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1716190 Title: apt-key does not print "Key fingerprint =" in front of fingerprints Status in apt package in Ubuntu: Triaged Bug description: A common idiom for checking fingerprints for keys begins with: ' apt-key fingerprint $key|grep fingerprint|...' ... this works up to thru jessie at least.. in zesty apt-key gives a 'warning' but produces no output. "Warning: apt-key output should not be parsed (stdout is not a terminal)" If the lack of output is intended and is meant to be a proscription, it is overreaching at best. A warning makes perfect sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apt 1.4 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Sun Sep 10 01:23:46 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1716190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716190] Re: apt-key does not output to non-terminals
Does it output anything to your terminal? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1716190 Title: apt-key does not print "Key fingerprint =" in front of fingerprints Status in apt package in Ubuntu: Triaged Bug description: A common idiom for checking fingerprints for keys begins with: ' apt-key fingerprint $key|grep fingerprint|...' ... this works up to thru jessie at least.. in zesty apt-key gives a 'warning' but produces no output. "Warning: apt-key output should not be parsed (stdout is not a terminal)" If the lack of output is intended and is meant to be a proscription, it is overreaching at best. A warning makes perfect sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apt 1.4 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Sun Sep 10 01:23:46 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1716190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716190] Re: apt-key does not output to non-terminals
Works for me: docker run --rm -it ubuntu:zesty sh -c 'apt-key fingerprint | grep Ubu' Warning: apt-key output should not be parsed (stdout is not a terminal) uid [ unknown] Ubuntu Archive Automatic Signing Key (2012) uid [ unknown] Ubuntu CD Image Automatic Signing Key (2012) ** Changed in: apt (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1716190 Title: apt-key does not print "Key fingerprint =" in front of fingerprints Status in apt package in Ubuntu: Triaged Bug description: A common idiom for checking fingerprints for keys begins with: ' apt-key fingerprint $key|grep fingerprint|...' ... this works up to thru jessie at least.. in zesty apt-key gives a 'warning' but produces no output. "Warning: apt-key output should not be parsed (stdout is not a terminal)" If the lack of output is intended and is meant to be a proscription, it is overreaching at best. A warning makes perfect sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apt 1.4 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Sun Sep 10 01:23:46 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1716190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716190] Re: apt-key does not output to non-terminals
Notably, the word fingerprint does not appear anywhere in the output, so if you search for literally that, then that's your problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1716190 Title: apt-key does not print "Key fingerprint =" in front of fingerprints Status in apt package in Ubuntu: Triaged Bug description: A common idiom for checking fingerprints for keys begins with: ' apt-key fingerprint $key|grep fingerprint|...' ... this works up to thru jessie at least.. in zesty apt-key gives a 'warning' but produces no output. "Warning: apt-key output should not be parsed (stdout is not a terminal)" If the lack of output is intended and is meant to be a proscription, it is overreaching at best. A warning makes perfect sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apt 1.4 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Sun Sep 10 01:23:46 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1716190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716190] Re: apt-key does not output to non-terminals
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1716190 Title: apt-key does not output to non-terminals Status in apt package in Ubuntu: Confirmed Bug description: A common idiom for checking fingerprints for keys begins with: ' apt-key fingerprint $key|grep fingerprint|...' ... this works up to thru jessie at least.. in zesty apt-key gives a 'warning' but produces no output. "Warning: apt-key output should not be parsed (stdout is not a terminal)" If the lack of output is intended and is meant to be a proscription, it is overreaching at best. A warning makes perfect sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apt 1.4 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Sun Sep 10 01:23:46 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1716190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734533] Re: package libgssapi3-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Thanks for filing this bug in Ubuntu. Could you please try the following (poderia por favor tentar os comandos abaixo): sudo apt update sudo apt install --reinstall libheimntlm0-heimdal sudo apt -f install Thanks ** Changed in: heimdal (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1734533 Title: package libgssapi3-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in heimdal package in Ubuntu: Incomplete Bug description: Deixa ele lento. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgssapi3-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic i686 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: i386 Date: Wed Nov 22 10:43:21 2017 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2017-03-06 (264 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: heimdal Title: package libgssapi3-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1734533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490271] Re: Mount /usr into initramfs
Closed as backported in xenial+ versions and the versions in question are no longer supported ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released -- 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/1490271 Title: Mount /usr into initramfs Status in initramfs-tools package in Ubuntu: Fix Released Bug description: After upgrading from Utopic to Vivid, I started getting some strange systemd errors and a boot time that was excessively long. After a good long while of investigation I discovered that it was due to my system having a seperate /usr partition. The two solutions seem to be to a) move /usr into the root partition, or b) mount /usr early in the initramfs. I'd prefer the b) option, but this is not available as mounting /usr from initramfs is only available in versions of initramfs-tools >= 0.117. The current version in vivid is 0.103. This is from the release file for initramfs-tools: * Mount /usr if present in the /etc/fstab on the mounted rootfs (Closes: #652459) This issue must be affecting thousands of people who have a partitioning scheme that isn't just 'all on one partition', so I would ask that the version of initramfs-tools on vivid is upgraded to at least version 0.117 as a matter of urgency. This issue was not present in trusty. Thanks Rob To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1490271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734038] Re: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty)
@mvo - this is probably obvious, but if you used '#include' instead of 'include', it would side-step the issue. -- 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/1734038 Title: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty) Status in AppArmor: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Issue found with Xenial kernel 4.4.0-102 and Zesty kernel 4.10.0-41, across different architectures Multiple tests from ubuntu_qrt_apparmor test suite failed with the same error message: ERROR: Syntax Error: Unknown line found in file /etc/apparmor.d/usr.lib.snapd.snap-confine.real line 15: include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r, (BTW the include and this ld.so.cache are not in the same line, please refer to comment #3 for attachment) This issue will gone if you downgrade the snapd and ubuntu-core-launcher package: sudo apt-get install snapd=2.28.5 ubuntu-core-launcher=2.28.5 Debug information: ubuntu@kernel01:~$ snap version snap2.29.3 snapd 2.29.3 series 16 ubuntu 16.04 kernel 4.4.0-102-generic ubuntu@kernel01:~$ apt list snapd Listing... Done snapd/xenial-proposed,now 2.29.3 s390x [installed] N: There are 2 additional versions. Please use the '-a' switch to see them. ubuntu@kernel01:~$ apt list apparmor -a Listing... Done apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 s390x [installed] apparmor/xenial-security 2.10.95-0ubuntu2.6 s390x apparmor/xenial 2.10.95-0ubuntu2 s390x Steps to run the Apparmor test from QA Regression testing suite: 1. git clone --depth 1 https://git.launchpad.net/qa-regression-testing 2. sudo ./qa-regression-testing/scripts/test-apparmor.py ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-102-generic 4.4.0-102.125 ProcVersionSignature: Ubuntu 4.4.0-102.125-generic 4.4.98 Uname: Linux 4.4.0-102-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.13 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Nov 23 01:36:31 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-102-generic N/A linux-backports-modules-4.4.0-102-generic N/A linux-firmware 1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1734038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715062] Re: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Hello Success, or anyone else affected, Accepted python-defaults into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python- defaults/2.7.13-2ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: python-defaults (Ubuntu Zesty) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1715062 Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in python-defaults package in Ubuntu: Fix Released Status in python-defaults source package in Xenial: Fix Committed Status in python-defaults source package in Zesty: Fix Committed Bug description: SRU: Replacing the shebang from python to python2 should not have regression potential. The python2 symlink is available in xenial, and earlier releases (trusty, wily), so there shouldn't be any upgrade issues. kflkt ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-six 1.10.0-3 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Sep 5 06:44:23 2017 Dependencies: ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-08-03 (32 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: six Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1715062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734719] [NEW] /usr/bin/zeitgeist-daemon:11:block_source:block_source:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding zeitgeist. This problem was most recently seen with package version 1.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/3b53e3c9f049100cb9f0b1d7dac733ee854e8dd6 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: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Tags: trusty vivid wily xenial zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1734719 Title: /usr/bin/zeitgeist- daemon:11:block_source:block_source:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate Status in zeitgeist package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding zeitgeist. This problem was most recently seen with package version 1.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/3b53e3c9f049100cb9f0b1d7dac733ee854e8dd6 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/zeitgeist/+bug/1734719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734715] [NEW] /bin/bash:11:wait_for:execute_command_internal:execute_command:reader_loop:main
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bash. This problem was most recently seen with package version 4.3-15ubuntu1, the problem page at https://errors.ubuntu.com/problem/1b8713f1ccb913cb26c39acfd8bb7b816f932fd4 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: bash (Ubuntu) Importance: Undecided Status: New ** Tags: saucy trusty vivid wily xenial yakkety -- 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/1734715 Title: /bin/bash:11:wait_for:execute_command_internal:execute_command:reader_loop:main Status in bash package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bash. This problem was most recently seen with package version 4.3-15ubuntu1, the problem page at https://errors.ubuntu.com/problem/1b8713f1ccb913cb26c39acfd8bb7b816f932fd4 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/bash/+bug/1734715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734702] [NEW] perldoc shows lots of escapes
Public bug reported: Fresh konsole: $ echo $TERM xterm-256color $ type perldoc perldoc is /usr/bin/perldoc $ dpkg -S /usr/bin/perldoc diversion by perl-doc from: /usr/bin/perldoc diversion by perl-doc to: /usr/bin/perldoc.stub perl, perl-doc: /usr/bin/perldoc $ echo $PAGER $ perldoc perlsyn (Now in pager:) ESC[1mNAMEESC[0m perlsyn - Perl syntax ESC[1mDESCRIPTIONESC[0m A Perl program consists of a sequence of declarations and statements which ... That's a lot of ESCapes. PAGER=more gets me "2NAME2" and the like. $ locate perlsyn /usr/share/man/man1/perlsyn.1.gz /usr/share/man/man1/perlsynology.1.gz /usr/share/perl/5.26.0/pod/perlsyn.pod /usr/share/perl/5.26.0/pod/perlsynology.pod No cached files apparently. This works reasonably: TERM=none perldoc perlsyn | (TERM=vt100 less) - but looses the bolds etc. This works well: man perlsyn This also works as expected, showing bolds and stuff, but I find it impractical: perldoc perlsyn | cat So perldoc applies terminal appropriate escapes where it should not? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: perl-doc 5.26.0-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: KDE Date: Mon Nov 27 15:23:57 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-07-18 (132 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: perl UpgradeStatus: Upgraded to artful on 2017-11-27 (0 days ago) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1734702 Title: perldoc shows lots of escapes Status in perl package in Ubuntu: New Bug description: Fresh konsole: $ echo $TERM xterm-256color $ type perldoc perldoc is /usr/bin/perldoc $ dpkg -S /usr/bin/perldoc diversion by perl-doc from: /usr/bin/perldoc diversion by perl-doc to: /usr/bin/perldoc.stub perl, perl-doc: /usr/bin/perldoc $ echo $PAGER $ perldoc perlsyn (Now in pager:) ESC[1mNAMEESC[0m perlsyn - Perl syntax ESC[1mDESCRIPTIONESC[0m A Perl program consists of a sequence of declarations and statements which ... That's a lot of ESCapes. PAGER=more gets me "2NAME2" and the like. $ locate perlsyn /usr/share/man/man1/perlsyn.1.gz /usr/share/man/man1/perlsynology.1.gz /usr/share/perl/5.26.0/pod/perlsyn.pod /usr/share/perl/5.26.0/pod/perlsynology.pod No cached files apparently. This works reasonably: TERM=none perldoc perlsyn | (TERM=vt100 less) - but looses the bolds etc. This works well: man perlsyn This also works as expected, showing bolds and stuff, but I find it impractical: perldoc perlsyn | cat So perldoc applies terminal appropriate escapes where it should not? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: perl-doc 5.26.0-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: KDE Date: Mon Nov 27 15:23:57 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-07-18 (132 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: perl UpgradeStatus: Upgraded to artful on 2017-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1734702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734667] Re: package linux-image-3.4.0-4-goldfish:i386 3.4.0-4.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1734667 Title: package linux-image-3.4.0-4-goldfish:i386 3.4.0-4.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: no ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-3.4.0-4-goldfish:i386 3.4.0-4.27 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Mon Nov 27 12:07:51 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2016-07-08 (506 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-3.4.0-4-goldfish:i386 3.4.0-4.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1734667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734667] [NEW] package linux-image-3.4.0-4-goldfish:i386 3.4.0-4.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: no ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-3.4.0-4-goldfish:i386 3.4.0-4.27 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Mon Nov 27 12:07:51 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2016-07-08 (506 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-3.4.0-4-goldfish:i386 3.4.0-4.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- 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/1734667 Title: package linux-image-3.4.0-4-goldfish:i386 3.4.0-4.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: no ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-3.4.0-4-goldfish:i386 3.4.0-4.27 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Mon Nov 27 12:07:51 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2016-07-08 (506 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-3.4.0-4-goldfish:i386 3.4.0-4.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1734667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734662] Re: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
Do not link python to python3. By doing that you break your system. ** Changed in: python-setuptools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1734662 Title: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in python-setuptools package in Ubuntu: Invalid Bug description: Somethign is messed up after linking python to python 3 and after this all these issues started cropping up. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-setuptools 3.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Nov 27 16:19:13 2017 Dependencies: python-pkg-resources 3.3-1ubuntu2 DuplicateSignature: package:python-setuptools:3.3-1ubuntu2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-16 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: python-setuptools Title: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2017-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1734662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734662] Re: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1734662 Title: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in python-setuptools package in Ubuntu: Invalid Bug description: Somethign is messed up after linking python to python 3 and after this all these issues started cropping up. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-setuptools 3.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Nov 27 16:19:13 2017 Dependencies: python-pkg-resources 3.3-1ubuntu2 DuplicateSignature: package:python-setuptools:3.3-1ubuntu2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-16 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: python-setuptools Title: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2017-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1734662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734660] [NEW] package python-six 1.5.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: Something is messed up after linking python to python 3 and after this all these issues started cropping up. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-six 1.5.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Nov 27 16:11:12 2017 Dependencies: DuplicateSignature: package:python-six:1.5.2-1ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-16 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: six Title: package python-six 1.5.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2017-11-27 (0 days ago) ** Affects: six (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1734660 Title: package python-six 1.5.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in six package in Ubuntu: New Bug description: Something is messed up after linking python to python 3 and after this all these issues started cropping up. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-six 1.5.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Nov 27 16:11:12 2017 Dependencies: DuplicateSignature: package:python-six:1.5.2-1ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-16 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: six Title: package python-six 1.5.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2017-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1734660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734660] Re: package python-six 1.5.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1734660 Title: package python-six 1.5.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in six package in Ubuntu: New Bug description: Something is messed up after linking python to python 3 and after this all these issues started cropping up. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-six 1.5.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Nov 27 16:11:12 2017 Dependencies: DuplicateSignature: package:python-six:1.5.2-1ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-16 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: six Title: package python-six 1.5.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2017-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1734660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734662] [NEW] package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Public bug reported: Somethign is messed up after linking python to python 3 and after this all these issues started cropping up. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-setuptools 3.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Nov 27 16:19:13 2017 Dependencies: python-pkg-resources 3.3-1ubuntu2 DuplicateSignature: package:python-setuptools:3.3-1ubuntu2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-16 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: python-setuptools Title: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2017-11-27 (0 days ago) ** Affects: python-setuptools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1734662 Title: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in python-setuptools package in Ubuntu: New Bug description: Somethign is messed up after linking python to python 3 and after this all these issues started cropping up. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-setuptools 3.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Nov 27 16:19:13 2017 Dependencies: python-pkg-resources 3.3-1ubuntu2 DuplicateSignature: package:python-setuptools:3.3-1ubuntu2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-16 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: python-setuptools Title: package python-setuptools 3.3-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2017-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1734662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734649] [NEW] package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to '/usr/lib/x86_64-lin
Public bug reported: I have this informations. What I can do about that?? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sun Nov 26 15:06:32 2017 ErrorMessage: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to '/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu tai jono InstallationDate: Installed on 2017-11-23 (3 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to '/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu tai jono UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1734649 Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux- gnu/libglib-2.0.a' to '/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg- new': odottamaton tiedoston loppu tai jono Status in glib2.0 package in Ubuntu: New Bug description: I have this informations. What I can do about that?? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sun Nov 26 15:06:32 2017 ErrorMessage: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to '/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu tai jono InstallationDate: Installed on 2017-11-23 (3 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to '/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu tai jono UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1734649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734649] Re: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to '/usr/lib/x86_64-linux
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1734649 Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux- gnu/libglib-2.0.a' to '/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg- new': odottamaton tiedoston loppu tai jono Status in glib2.0 package in Ubuntu: New Bug description: I have this informations. What I can do about that?? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sun Nov 26 15:06:32 2017 ErrorMessage: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to '/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu tai jono InstallationDate: Installed on 2017-11-23 (3 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to '/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu tai jono UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1734649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 854333] Re: ibus GUI not loading, unable to use input
sudo apt-get install gnome-icon-theme -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/854333 Title: ibus GUI not loading, unable to use input Status in ibus package in Ubuntu: Fix Released Status in ibus package in Debian: Fix Released Bug description: I'm using oneiric since alpha3, and despite all the updates and bugfixes, ibus is just not working under ubuntu, nor kubuntu. kernel: 3.0.0-11 (also previous versions) ibus: 1.3.99.20110419-1ubuntu3 (also ibus-gtk, ibus-gtk3, ibus-qt4, ibus-pinyin packages are installed and up-to-date, with all dependencies) kubuntu 11.10 The problem is that even though ibus-daemon starts up at login, but it doesn't do anything, the icon doesn't appear in the notificaion area, and I can't seem to switch to a different method with the hotkey either. When I try running ibus-daemon from the command line, i get the answer that it's already running for this session. Also there is no way under language support to install chinese language pack, only the translations, all the other options are greyed out (input methods, etc) since oneiric. There isn't any error messages whatsoever, it just doesn't work, and also the same with scim and uim too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/854333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 854333] Re: ibus GUI not loading, unable to use input
sudo apt-get install gnome-icon-theme -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/854333 Title: ibus GUI not loading, unable to use input Status in ibus package in Ubuntu: Fix Released Status in ibus package in Debian: Fix Released Bug description: I'm using oneiric since alpha3, and despite all the updates and bugfixes, ibus is just not working under ubuntu, nor kubuntu. kernel: 3.0.0-11 (also previous versions) ibus: 1.3.99.20110419-1ubuntu3 (also ibus-gtk, ibus-gtk3, ibus-qt4, ibus-pinyin packages are installed and up-to-date, with all dependencies) kubuntu 11.10 The problem is that even though ibus-daemon starts up at login, but it doesn't do anything, the icon doesn't appear in the notificaion area, and I can't seem to switch to a different method with the hotkey either. When I try running ibus-daemon from the command line, i get the answer that it's already running for this session. Also there is no way under language support to install chinese language pack, only the translations, all the other options are greyed out (input methods, etc) since oneiric. There isn't any error messages whatsoever, it just doesn't work, and also the same with scim and uim too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/854333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439687] Re: Can not report bug: SSL Certificate Verify Failure
For me the issue seems to be cause as the VMhost for this Ubuntu guest has netskope / goskope.com installed and https traffic is inspected by way of a wildcard certificate. So yes, there is an issue with the cert, but it should be possible to manually allow this operation to proceed anyway like all browsers do. -- 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/1439687 Title: Can not report bug: SSL Certificate Verify Failure Status in apport package in Ubuntu: Confirmed Status in whoopsie package in Ubuntu: Invalid Bug description: I called apport with apport-bug linux, because I wanted to report a kernel bug. However I could not send the logs to launchpad because of the following error message: Distribution: Kubuntu 15.04 64 Bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1439687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp