[Touch-packages] [Bug 1712171] Re: New release 17.2.0-rc5
17.2.0 is in artful since some time ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1712171 Title: New release 17.2.0-rc5 Status in mesa package in Ubuntu: Fix Released Bug description: Hello, https://github.com/mesa3d/mesa/releases/tag/mesa-17.2.0-rc5 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mesa-va-drivers 17.2.0~rc4-0ubuntu3 Uname: Linux 4.13.0-041300rc6-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 21 15:40:51 2017 InstallationDate: Installed on 2017-07-05 (46 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: mesa UpgradeStatus: Upgraded to artful on 2017-07-05 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1712171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717839] Re: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717839 Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: Not able to upgrade ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-sysv 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 Date: Sun Sep 17 19:49:21 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2017-09-16 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: systemd Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to zesty on 2017-09-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717839] [NEW] package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
Public bug reported: Not able to upgrade ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-sysv 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 Date: Sun Sep 17 19:49:21 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2017-09-16 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: systemd Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to zesty on 2017-09-18 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 third-party-packages zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717839 Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: Not able to upgrade ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-sysv 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 Date: Sun Sep 17 19:49:21 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2017-09-16 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: systemd Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to zesty on 2017-09-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704713] Re: please improve my lappy
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1704713 Title: please improve my lappy Status in xorg package in Ubuntu: Expired Bug description: my laptop is not working well please see error log and improve my laptop performance ,i'll very thankful for you ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 NonfreeKernelModules: openafs wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jul 17 11:18:30 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.4.0-81-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-83-generic, x86_64: installed openafs, 1.6.15, 4.4.0-81-generic, x86_64: installed openafs, 1.6.15, 4.4.0-83-generic, x86_64: installed GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics [103c:80c2] InstallationDate: Installed on 2016-11-24 (234 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Notebook ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=f110cba6-8b9c-4548-8ed4-f543954307e6 ro splash quiet vesafb.invalid=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd05/17/2016:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C2:rvr96.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Jul 17 11:13:45 2017 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20049 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.
E.g. Apt could have --autoremove-new option which would work with apt and apt-get -- 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/1624644 Title: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software. Status in apt package in Ubuntu: New Status in gnome-software package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in apt source package in Artful: New Status in gnome-software source package in Artful: New Status in unattended-upgrades source package in Artful: New Status in update-manager source package in Artful: New Bug description: When using default settings for unattended-upgrade i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, unattended-upgrade is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because unattended-upgrade compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. Consequently, if user installs new kernels using e.g. update-manager, the excessive kernels will not be removed by unattended-upgrade, and eventually (small) /boot will become full. Expected behavior: handle removing of unused packages differently at least until other package management software installed by default can handle removing of new unused packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.
** Description changed: - When using default settings for unattended-upgrades i.e. + When using default settings for unattended-upgrade i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, - U-U is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because U-U compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. + unattended-upgrade is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because unattended-upgrade compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. + + Consequently, if user installs new kernels using e.g. update-manager, + the excessive kernels will not be removed by unattended-upgrade, and + eventually (small) /boot will become full. Expected behavior: handle removing of unused packages differently at least until other package management software installed by default can handle removing of new unused packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: unattended-upgrades (Ubuntu Artful) Status: Opinion => New ** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1624644 Title: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software. Status in apt package in Ubuntu: New Status in gnome-software package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in apt source package in Artful: New Status in gnome-software source package in Artful: New Status in unattended-upgrades source package in Artful: New Status in update-manager source package in Artful: New Bug description: When using default settings for unattended-upgrade i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, unattended-upgrade is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because unattended-upgrade compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. Consequently, if user installs new kernels using e.g. update-manager, the excessive kernels will not be removed by unattended-upgrade, and eventually (small) /boot will become full. Expected behavior: handle removing of unused packages differently at least until other package management software installed by default can handle removing of new unused packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.
** Summary changed: - Unable to automatically remove packages that become unused in conjunction with updating by other software + By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software. ** Description changed: When using default settings for unattended-upgrades i.e. - Unattended-Upgrade::Remove-Unused-Dependencies "false"; + Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" - Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; + Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, U-U is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because U-U compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. + + Expected behavior: handle removing of unused packages differently at + least until other package management software installed by default can + handle removing of new unused packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1624644 Title: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software. Status in apt package in Ubuntu: New Status in gnome-software package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in apt source package in Artful: New Status in gnome-software source package in Artful: New Status in unattended-upgrades source package in Artful: New Status in update-manager source package in Artful: New Bug description: When using default settings for unattended-upgrade i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, unattended-upgrade is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because unattended-upgrade compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. Consequently, if user installs new kernels using e.g. update-manager, the excessive kernels will not be removed by unattended-upgrade, and eventually (small) /boot will become full. Expected behavior: handle removing of unused packages differently at least until other package management software installed by default can handle removing of new unused packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624644] Re: Unable to automatically remove packages that become unused in conjunction with updating by other software
Anyway, it would be good, if other software could optionally remove new unused packages. I do not consider Unattended-Upgrade::Remove-New-Unused-Dependencies as an reasonable default option for unattended-upgrades before the feature has been released for at least apt, update-manager, gnome-software and possible other related software installed by default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1624644 Title: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software. Status in unattended-upgrades package in Ubuntu: Opinion Status in update-manager package in Ubuntu: New Status in unattended-upgrades source package in Artful: Opinion Status in update-manager source package in Artful: New Bug description: When using default settings for unattended-upgrades i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, U-U is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because U-U compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. Expected behavior: handle removing of unused packages differently at least until other package management software installed by default can handle removing of new unused packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716775] Re: Add option to disable gnome-shell animations
There was this from a long time ago that sorta set the 'policy' on not providing much on config, since then it was always like pulling teeth to get things in (somewhat.. https://bugs.launchpad.net/ubuntu/+source/unity/+bug/748739 It would be nice to see a some basic options provided in something obvious to the general user. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1716775 Title: Add option to disable gnome-shell animations Status in ubuntu-settings package in Ubuntu: Invalid Bug description: I believe doing so will provide the better experience for most users. Those that see use in it can enable if desired. Am filing this bug first rather than specific against gnome-shell because this is immediately remedied in settings & there are reports of other poor behavior than the below test case. Test case 1: In current 'pseudo' default of xorg In any common video player (totem, vlc, mpv, ect.) open a video. Go from window to fullscreen, fullscreen to windowed, notice the distortion. May be even worse in wayland or when using hw decoding. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.15 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 17:21:52 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1716775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
Everyone please open new bugs instead of commenting here. This bug is closed per comment #48. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716775] Re: Add option to disable gnome-shell animations
I would prefer gnome-tweak-tool did not exist... It's annoying that basic configuration options are not available in the standard settings GUI. P.S. Unity's performance problems were actually Unity itself. Compiz performs brilliantly if you don't have the unity plugin loaded :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1716775 Title: Add option to disable gnome-shell animations Status in ubuntu-settings package in Ubuntu: Invalid Bug description: I believe doing so will provide the better experience for most users. Those that see use in it can enable if desired. Am filing this bug first rather than specific against gnome-shell because this is immediately remedied in settings & there are reports of other poor behavior than the below test case. Test case 1: In current 'pseudo' default of xorg In any common video player (totem, vlc, mpv, ect.) open a video. Go from window to fullscreen, fullscreen to windowed, notice the distortion. May be even worse in wayland or when using hw decoding. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.15 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 17:21:52 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1716775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717589] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Could be the same issue as any of these: bug 1426228 bug 1640468 bug 1682731 bug 1698650 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1717589 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: I was trying to perform the update on linux 16.04 LTE of my QNAP TS- 253A NAS server when the error occurred. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 Uname: Linux 4.2.8 x86_64 NonfreeKernelModules: vfio_pci vfio_virqfd vfio_iommu_type1 vfio vhost_scsi target_core_mod vhost_net vhost macvtap macvlan tun vringh virtio_scsi virtio_pci virtio_net virtio_mmio virtio_console virtio_blk virtio_balloon virtio_rng virtio_ring virtio kvm_intel kvm xt_nat rfcomm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fbdisk cdc_ether ipt_MASQUERADE iptable_nat nf_nat_masquerade_ipv4 nf_nat_ipv4 nf_nat xt_policy xt_mark bonding br_netfilter bridge stp 8021q ipv6 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core snd_usb_caiaq snd_usb_audio snd_usbmidi_lib snd_seq_midi snd_rawmidi fnotify udf isofs sp5100_tco iTCO_wdt tbs_keys ufsd jnl pl2303 usbserial qm2_i2c intel_ips drbd flashcache dm_tier_btier_algo dm_thin_pool dm_bio_prison dm_persistent_data hal_netlink k10temp coretemp r8152 usbnet mii igb e1000e mpt3sas mpt2sas scsi_transport_sas raid_class usb_storage xhci_pci xhci_hcd usblp uhci_hcd ehci_pci ehci_hcd ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Sep 15 21:39:42 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InterestingModules: rfcomm Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1005:b155 Apacer Technology, Inc. Bus 001 Device 002: ID 045e:0800 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: consoleblank=0 console=ttyS0,115200n8 video=HDMI-A-1:800x600@60 video=HDMI-A-2:800x600@60 i915.disable_dp_dual_mode=1 i915.disable_power_well=0 memmap=2M$0x800 ramoops.mem_address=0x800 ramoops.mem_size=0x20 ramoops.console_size=0x10 BOOT_IMAGE=/boot/bzImage root=/dev/ram0 rw RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) getfacl: Error: command ['getfacl', '/dev/rfkill'] failed with exit code 1: getfacl: /dev/rfkill: No such file or directory hciconfig: Error: command hciconfig failed with exit code 1: Can't open HCI socket.: Address family not supported by protocol rfkill: Can't open RFKILL control device: No such file or directory upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717589/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle
We need some stack information to help us determine the cause of the CPU spikes. 1. Download the attached dstack script to your home directory. 2. Log in to a virtual terminal (Ctrl+Alt+F1), and switch back (Ctrl+Alt+F7) 3. When the spike happens, switch to Ctrl+Alt+F1 and run this: sudo -s sh ./dstack bluetoothd >> stacks.txt sh ./dstack bluetoothd >> stacks.txt sh ./dstack bluetoothd >> stacks.txt sh ./dstack bluetoothd >> stacks.txt sh ./dstack bluetoothd >> stacks.txt (yes, five times) 4. Attach the resulting stacks.txt to this bug. ** Attachment added: "dstack" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/+attachment/4951926/+files/dstack ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1717796 Title: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle Status in bluez package in Ubuntu: Incomplete Bug description: When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At this point you have to press any key to reconnect the device and let bluetoothd to return to work normally. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 17 19:02:40 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2016-08-06 (406 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: GIGABYTE GB-BXBT-2807 ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBAYAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GB-BXBT-2807 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:85:DE:FD:2F:BC ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN ISCAN RX bytes:528225 acl:32183 sco:0 events:1134 errors:0 TX bytes:33849 acl:338 sco:0 commands:388 errors:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1712417] Re: New release 3.22.19
https://launchpad.net/ubuntu/+source/gtk+3.0/3.22.19-0ubuntu1 ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1712417 Title: New release 3.22.19 Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: Hello, https://git.gnome.org/browse/gtk+/commit/?h=3.22.19=efbf6f183ecd24cddea743a02fe8ce545f1b55f8 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgtk-3-0 3.22.18-1ubuntu1 Uname: Linux 4.13.0-041300rc6-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 22 16:45:33 2017 InstallationDate: Installed on 2017-07-05 (48 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1712417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717820] [NEW] gedit: Use 'builder' color scheme by default
Public bug reported: By default, gedit uses the 'classic' color scheme. I think the 'builder' color scheme looks a bit closer to Ubuntu's colors. (grey, orange, green, and blue instead of blue, green, red, and purple). It's also nice because it has a Dark variant and it is the same color scheme used by default in GNOME Builder. You can change the color scheme by opening gedit. I recommend opening a typical source code file. Click the app menu in the top bar and select Preferences. Switch to the Fonts & Colors tab. Select the Color Scheme you want. The gsettings is [org.gnome.gedit.preferences.editor scheme] 'builder' We are now past Ubuntu 17.10 User Interface Freeze, but I think this change is worth considering for 18.04 LTS. ** Affects: ubuntu-settings (Ubuntu) Importance: Wishlist Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1717820 Title: gedit: Use 'builder' color scheme by default Status in ubuntu-settings package in Ubuntu: New Bug description: By default, gedit uses the 'classic' color scheme. I think the 'builder' color scheme looks a bit closer to Ubuntu's colors. (grey, orange, green, and blue instead of blue, green, red, and purple). It's also nice because it has a Dark variant and it is the same color scheme used by default in GNOME Builder. You can change the color scheme by opening gedit. I recommend opening a typical source code file. Click the app menu in the top bar and select Preferences. Switch to the Fonts & Colors tab. Select the Color Scheme you want. The gsettings is [org.gnome.gedit.preferences.editor scheme] 'builder' We are now past Ubuntu 17.10 User Interface Freeze, but I think this change is worth considering for 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1717820/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702078] Re: Boot to blank screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1702078 Title: Boot to blank screen Status in xorg package in Ubuntu: Confirmed Bug description: Made the test case Install (entire disk) in Ubuntu Desktop amd64 in Artful Daily Installation went OK. At boot the grub menu is shown. After selection of Ubuntu the screen gets blank. The plymouth screen isn't shown. When I press Ctrl repeatedly the plymouth screen is shown and then the login screen. The installation is set to use the swedish keyboard, but the english keyboard is used. Except for that the installation behaves OK. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 BootLog: /dev/sdc1: clean, 153910/39075840 files, 4226467/156282624 blocks CompositorRunning: None CurrentDesktop: GNOME Date: Mon Jul 3 13:56:41 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD 6850] [174b:e174] InstallationDate: Installed on 2017-07-03 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170703) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=e83ef1bc-3743-4dde-a4e8-b774b544ef66 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Jul 3 15:28:22 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputCHICONY Compaq USB Keyboard KEYBOARD, id 8 inputCHICONY Compaq USB Keyboard KEYBOARD, id 9 inputMicrosoft Corporation Microsoft ® Laser Mouse 6000 MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1245287] Re: upower showing keyboard at 0% charge
** Changed in: upower (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1245287 Title: upower showing keyboard at 0% charge Status in Upower: Fix Released Status in upower package in Ubuntu: Fix Released Bug description: This bug is new upon upgrading to 13.10; bug did not exist on 13.04, 12.10 or 12.04. I'm using an apple wireless keyboard. I have replaced the batteries and confirmed they are fully charged with voltmeter. Keyboard is working fine but indicator says it's 0% and is red indicating some problem. Also upower says "keyboard not present"; bluetooth shows keyboards. To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1245287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650666] Re: GVim crashes when opening new tab
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: vim (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1650666 Title: GVim crashes when opening new tab Status in vim package in Ubuntu: Confirmed Status in vim source package in Xenial: Confirmed Bug description: [Impact] A severe regression has been found in the GTK 3 variant of Gvim. Upon start-up, it crashes immediately with multiple failed assertions. A second related, but less severe problem may occur when opening new tabs within the GTK 3 variant of Gvim. [Test Case] Please note that in the following test cases, a given machine may experience either of the test cases, while being unable to experience the other test case. Please do /not/ discount the merits of this SRU on being able to only confirm a single test case, but not both. This patch equally corrects both test cases listed below, to produce a working GTK 3 Gvim variant. IMPORTANT: Both test cases below require the package "vim-gtk3" to be installed, prior to testing for either test case's impact to one's machine. [[TEST CASE #1]] 1. From a terminal window, launch the GTK 3 variant of Gvim: $ vim.gtk3 2. Immediately upon launch (whereby the window may or may not briefly display); the terminal window will show error messages relating to `unity_gtk_menu_*` critical assertions. A full example of the experienced error output shown is: ``` (gvim:13519): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <= (gint)rarray->len' failed ** (gvim:13519): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_child_shell: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed ** (gvim:13519): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_label: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_icon: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed ``` [[TEST CASE #2]] 1. From a terminal window, launch the GTK 3 variant of Gvim: $ vim.gtk3 2. Upon the window opening, attempt to open a new tab by entering the key sequences ":tabnew" and pressing . The program should now SEGV and abort. [Regression Potential] * The bug is possibly applicable to all later Ubuntu releases, which combine Unity and GTK 3. * The upstream Vim project has not incorporated the fix, and most likely will not. The specifics behind the fix might be construed as too specific to the combination of Ubuntu, Unity, and GTK 3; and not general enough to patch for all downstream distributions. [Other Info] * Further information about this bug is available at the URLs: https://github.com/vim/vim/issues/851 https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1650666 --- When I open new tab using :tabnew command, GVim crashes in unity_gtk_menu_section_get_item_attributes function of libunity- gtk3-parser0 package. Steps to reproduce: 1. Run gvim from vim-gtk3 package 2. Type `:tabnew` 3. GVim exits, the window closes Stack trace obtained via gdb: mymedia@comp2:~$ gdb -silent --args gvim -f -u /dev/null -U /dev/null --noplugin Reading symbols from gvim...(no debugging symbols found)...done. gdb$ run Starting program: /usr/bin/gvim -f -u /dev/null -U /dev/null --noplugin [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe986d700 (LWP 11042)] [New Thread 0x7fffe906c700 (LWP 11043)] [New Thread 0x7fffe886b700 (LWP 11044)] (gvim:11038): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <= (gint)rarray->len' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_child_shell: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= index && index < items->len' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_label: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_icon: assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed Thread 1 "gvim" received signal SIGSEGV, Segmentation fault. unity_gtk_menu_section_get_item_attributes (model=, item_index=, attributes=0x7fff8b90) at ../../../lib/unity-gtk-menu-section.c:130 130 ../../../lib/unity-gtk-menu-section.c: Нет такого файла или каталога. gdb$ backtrace #0
[Touch-packages] [Bug 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle
This is my kernel.log when bluetoothd goes at 100%: " Sep 17 18:41:43 GB-BXBT-2807 kernel: [ 7738.885123] hid-generic 0005:0A5C:8502.000B: unknown main item tag 0x0 Sep 17 18:41:43 GB-BXBT-2807 kernel: [ 7738.885475] input: Bluetooth Keyboard as /devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/bluetooth/hci0/hci0:2/0005:0A5C:8502.000B/input/input17 Sep 17 18:41:43 GB-BXBT-2807 kernel: [ 7738.886183] hid-generic 0005:0A5C:8502.000B: input,hidraw1: BLUETOOTH HID v0.01 Keyboard [Bluetooth Keyboard] on dc:85:de:fd:2f:bc " -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1717796 Title: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle Status in bluez package in Ubuntu: New Bug description: When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At this point you have to press any key to reconnect the device and let bluetoothd to return to work normally. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 17 19:02:40 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2016-08-06 (406 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: GIGABYTE GB-BXBT-2807 ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBAYAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GB-BXBT-2807 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:85:DE:FD:2F:BC ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN ISCAN RX bytes:528225 acl:32183 sco:0 events:1134 errors:0 TX bytes:33849 acl:338 sco:0 commands:388 errors:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717795] Re: apport-gtk crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1622414 *** https://bugs.launchpad.net/bugs/1622414 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1622414, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1717795/+attachment/4951783/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1717795/+attachment/4951786/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1717795/+attachment/4951789/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1717795/+attachment/4951790/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1717795/+attachment/4951791/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1717795/+attachment/4951792/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1717795/+attachment/4951793/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1622414 ** Information type changed from Private Security to Public Security ** Tags removed: need-amd64-retrace -- 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/1717795 Title: apport-gtk crashed with SIGABRT in g_assertion_message() Status in apport package in Ubuntu: New Bug description: just this say ERROR ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: apport-gtk 2.20.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 17 13:38:44 2017 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2017-07-24 (54 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.14rc1, python-minimal, 2.7.13-2 Signal: 6 SourcePackage: apport StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1717795/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717796] [NEW] Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle
Public bug reported: When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At this point you have to press any key to reconnect the device and let bluetoothd to return to work normally. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 17 19:02:40 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2016-08-06 (406 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: GIGABYTE GB-BXBT-2807 ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBAYAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GB-BXBT-2807 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: DC:85:DE:FD:2F:BC ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN ISCAN RX bytes:528225 acl:32183 sco:0 events:1134 errors:0 TX bytes:33849 acl:338 sco:0 commands:388 errors:1 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1717796 Title: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle Status in bluez package in Ubuntu: New Bug description: When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At this point you have to press any key to reconnect the device and let bluetoothd to return to work normally. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 17 19:02:40 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2016-08-06 (406 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: GIGABYTE GB-BXBT-2807 ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBAYAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GB-BXBT-2807 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:85:DE:FD:2F:BC ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN ISCAN RX bytes:528225 acl:32183 sco:0 events:1134 errors:0 TX bytes:33849 acl:338 sco:0 commands:388 errors:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1245287] Re: upower showing keyboard at 0% charge
** Changed in: upower Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1245287 Title: upower showing keyboard at 0% charge Status in Upower: Fix Released Status in upower package in Ubuntu: Confirmed Bug description: This bug is new upon upgrading to 13.10; bug did not exist on 13.04, 12.10 or 12.04. I'm using an apple wireless keyboard. I have replaced the batteries and confirmed they are fully charged with voltmeter. Keyboard is working fine but indicator says it's 0% and is red indicating some problem. Also upower says "keyboard not present"; bluetooth shows keyboards. To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1245287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716833] Re: NM manages /etc/resolv.conf directly in artful after removal of resolvconf
So if /etc/resolv.conf was pointing at stub-resolv.conf everything would have worked. However, at closer inspection, netplan test suite has also been miss detecting the backends used by NetworkManager and whether or not resolved was enabled. For resolved, it was only considering nss module and was not checking if stub resolver is enabled. After updating the checks for backend detection the tests started to pass both on fixed and broken hosts. ** Package changed: network-manager (Ubuntu Artful) => nplan (Ubuntu Artful) ** Changed in: nplan (Ubuntu Artful) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1716833 Title: NM manages /etc/resolv.conf directly in artful after removal of resolvconf Status in nplan package in Ubuntu: Fix Released Status in nplan source package in Artful: Fix Released Bug description: The nplan autopkgtests are now failing in artful following the removal of resolvconf from the base system, with the following error: == FAIL: test_manual_addresses (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.4I4oae/build.Xcu/nplan-0.26/tests/integration.py", line 1110, in test_manual_addresses self.assertRegex(resolv_conf, 'search.*fakesuffix') AssertionError: Regex didn't match: 'search.*fakesuffix' not found in '# Generated by NetworkManager\nnameserver 127.0.1.1\n' It is possible that there is *also* a bug with nplan's integration with systemd-resolved; however, what this error message exposes is that NM is overwriting /etc/resolv.conf when this should now be managed by systemd-resolved instead. NM needs to inject its DNS server information into resolved instead of editing /etc/resolv.conf directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1716833/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
oh shit i've forget to insert my Wifi adapter in my post. is a rtl8188eus chpset -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Zesty: Triaged Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
I've same problem under Ubuntu 17.04 since mainline kernel 4.13.2 is installed. My Wifi dobngle is connecting to router but no internet connection will be established, the last working kernel is the mainline kernel 4.12.13. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Zesty: Triaged Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1696735] Re: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt
This is the error that I received. I am on Ubuntu 17.04 John Johnson On 09/14/2017 10:36 AM, Andreas Hasenack wrote: > I don't know, you didn't say if you ran the commands I asked for in > comment #8. > > But since this is a new installation, could you please show what error > you got, and then I can try suggesting something again? > ** Attachment added: "mkkeeadcfbblombd.png" https://bugs.launchpad.net/bugs/1696735/+attachment/4951738/+files/mkkeeadcfbblombd.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1696735 Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in krb5 package in Ubuntu: Expired Bug description: unknown ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 8 08:22:46 2017 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-02-12 (481 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: krb5 Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2016-05-22 (381 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1696735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] PstreeP.txt
apport information ** Attachment added: "PstreeP.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951700/+files/PstreeP.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951692/+files/ProcCpuinfoMinimal.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] PstreeP.txt
apport information ** Attachment added: "PstreeP.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951693/+files/PstreeP.txt ** Description changed: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ApportVersion: 2.20.1-0ubuntu2.10 + Architecture: amd64 + CasperVersion: 1.376.2 + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + Package: apparmor 2.10.95-0ubuntu2.6 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity + ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 + Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled + Tags: xenial + Uname: Linux 4.10.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease:
[Touch-packages] [Bug 1717517] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951699/+files/ProcCpuinfoMinimal.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951690/+files/JournalErrors.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951691/+files/KernLog.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951697/+files/JournalErrors.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951698/+files/KernLog.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] ApparmorStatusOutput.txt
apport information ** Attachment added: "ApparmorStatusOutput.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951688/+files/ApparmorStatusOutput.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] ApparmorStatusOutput.txt
apport information ** Attachment added: "ApparmorStatusOutput.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951695/+files/ApparmorStatusOutput.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] ApparmorPackages.txt
apport information ** Attachment added: "ApparmorPackages.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951694/+files/ApparmorPackages.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951696/+files/Dependencies.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951689/+files/Dependencies.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717517] Re: AppArmor initialization Failed, computer not starting
apport information ** Tags added: apport-collected xenial ** Description changed: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. + --- + ApportVersion: 2.20.1-0ubuntu2.10 + Architecture: amd64 + CasperVersion: 1.376.2 + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + Package: apparmor 2.10.95-0ubuntu2.6 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity + ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 + Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled + Tags: xenial + Uname: Linux 4.10.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ApparmorPackages.txt" https://bugs.launchpad.net/bugs/1717517/+attachment/4951687/+files/ApparmorPackages.txt -- 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/1717517 Title: AppArmor initialization Failed, computer not starting Status in apparmor package in Ubuntu: New Bug description: When I start my computer, the following message appears then nothing else happens. /dev/sda1: clean, 2013302/58957824 files, 114215880/235816448 blocks [FAILED] Failed to start LSB: AppArmor initialization. See 'Systemct1 status apparmor.service' for details. Mounting Arbitrary Executable File Formats File System... [ OK ] Started udev Coldplug all Devices. Starting Show Plymouth Boot screen... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Mounted Arbitrary Executable File Formats System. [ OK ] Listening on Load/Save RF Kill switch Status /dev/rfkill Watch. [ OK ] Started clean up any mess keft by 0dns-up. Starting Nameserver information manager... [ OK ] Started Enable support for additional executable binary formats. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: apparmor 2.10.95-0ubuntu2.6 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Syslog: Sep 17 13:03:04 ubuntu dbus[1344]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to:
[Touch-packages] [Bug 1717769] Re: day of week in german despite i configured the system in english
** Attachment added: "Region configuration screenshot" https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1717769/+attachment/4951686/+files/Screenshot%20from%202017-09-17%2013-24-24.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en in Ubuntu. https://bugs.launchpad.net/bugs/1717769 Title: day of week in german despite i configured the system in english Status in language-pack-en package in Ubuntu: New Bug description: Description --- I chose the english language and live in Belgium. So I chose Brussels for the Time Zone, and the Belgian keymap. The Ubuntu date & time applet, in the top bar of the Ubuntu desktop interface shows me "Son HH:MM", Son standing for "Sonntag" which is german. I don't get why there is german in my interface since I configured this language nowhere but English. Expected Behavior -- Having the day of week in English. My configuration to reproduce the problem - Here is the region & language configuration as seen in the settings pannel: Language: English (United States) Formats : Belgien Input Sources: Belgian In the "Date & Time" settings: Time Zone: CEST (Brussels, Belgium) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1717769/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717769] [NEW] day of week in german despite i configured the system in english
Public bug reported: Description --- I chose the english language and live in Belgium. So I chose Brussels for the Time Zone, and the Belgian keymap. The Ubuntu date & time applet, in the top bar of the Ubuntu desktop interface shows me "Son HH:MM", Son standing for "Sonntag" which is german. I don't get why there is german in my interface since I configured this language nowhere but English. Expected Behavior -- Having the day of week in English. My configuration to reproduce the problem - Here is the region & language configuration as seen in the settings pannel: Language: English (United States) Formats : Belgien Input Sources: Belgian In the "Date & Time" settings: Time Zone: CEST (Brussels, Belgium) ** Affects: language-pack-en (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2017-09-17 13-25-15.png" https://bugs.launchpad.net/bugs/1717769/+attachment/4951685/+files/Screenshot%20from%202017-09-17%2013-25-15.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en in Ubuntu. https://bugs.launchpad.net/bugs/1717769 Title: day of week in german despite i configured the system in english Status in language-pack-en package in Ubuntu: New Bug description: Description --- I chose the english language and live in Belgium. So I chose Brussels for the Time Zone, and the Belgian keymap. The Ubuntu date & time applet, in the top bar of the Ubuntu desktop interface shows me "Son HH:MM", Son standing for "Sonntag" which is german. I don't get why there is german in my interface since I configured this language nowhere but English. Expected Behavior -- Having the day of week in English. My configuration to reproduce the problem - Here is the region & language configuration as seen in the settings pannel: Language: English (United States) Formats : Belgien Input Sources: Belgian In the "Date & Time" settings: Time Zone: CEST (Brussels, Belgium) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1717769/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1609546] Re: DNS lookup through Netgear DG834G V4 router slow or times out
Laurent, if disabling DNSSEC does not fix it then it is not the same bug. I suggest submitting a new bug. -- 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/1609546 Title: DNS lookup through Netgear DG834G V4 router slow or times out Status in systemd package in Ubuntu: Triaged Bug description: Update: On Zesty I am seeing a timeout both with systemd-resolve and dnslookup rather than just a slow resolution. The workaround in comment #6 which disables DNSSEC still corrects the problem. --- On up to date Yakkety if I specify my Netgear router as the DNS server (via Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I run, for example, systemd-resolve www.google.com or wget www.google.com I do not see the same delay if I run nslookup www.google.com A clue may be that in syslog I see Aug 3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 127.0.1.1. Aug 3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set (UDP+EDNS0) for DNS server 127.0.1.1. Aug 3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set (UDP) for DNS server 127.0.1.1. I do not see the issue if I specify an external DNS server. I do not see the issue on 16.04, nor previous versions, or on other devices connected to the network. I have been using this router for years. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 3 21:24:07 2016 InstallationDate: Installed on 2016-08-02 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802) MachineType: Hewlett-Packard Presario CQ57 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.47 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3577 dmi.board.vendor: Hewlett-Packard dmi.board.version: 24.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Presario CQ57 Notebook PC dmi.product.version: 068E1220491620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1609546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717764] [NEW] 1
Public bug reported: 1 ProblemType: Bug DistroRelease: Ubuntu Kylin 17.10 Package: xorg 1:7.7+19ubuntu2 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.69 Wed Aug 16 19:34:54 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-4ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 17 13:34:44 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-11-generic, x86_64: installed nvidia-384, 384.69, 4.13.0-11-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750] [1043:84ad] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=36d5b420-89f3-4900-904b-30f5ba9fb9f4 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LE/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLE/USB3:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1 version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.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: Sun Sep 17 13:18:31 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful single-occurrence third-party-packages 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/1717764 Title: 1 Status in xorg package in Ubuntu: New Bug description: 1 ProblemType: Bug DistroRelease: Ubuntu Kylin 17.10 Package: xorg 1:7.7+19ubuntu2 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.69 Wed Aug 16 19:34:54 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-4ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 17 13:34:44 2017 DistUpgraded: Fresh
[Touch-packages] [Bug 1717367] Re: FTBFS: segfaults in testsuite with perl 5.26.0-7
** Changed in: glibc (Debian) Status: Unknown => Confirmed -- 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/1717367 Title: FTBFS: segfaults in testsuite with perl 5.26.0-7 Status in glibc package in Ubuntu: Invalid Status in libanyevent-perl package in Ubuntu: Invalid Status in perl package in Ubuntu: Fix Released Status in glibc package in Debian: Confirmed Bug description: The autopkgtests segfault against perl 5.26.0-7 in Ubuntu, and the new version of the package also fails to build in -proposed because the tests are segfaulting at package build time. $ perl ./t/02_signals.t 1..5 ok 1 Segmentation fault (core dumped) $ gdb --args perl ./t/02_signals.t GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. [...] (gdb) run Starting program: /usr/bin/perl ./t/02_signals.t [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 1..5 ok 1 Program received signal SIGSEGV, Segmentation fault. 0x7738811e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x7738811e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7626591d in ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Async/Interrupt/Interrupt.so #2 0x762672a9 in ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Async/Interrupt/Interrupt.so #3 0x5562fab1 in Perl_pp_entersub () #4 0x556278e6 in Perl_runops_standard () #5 0x555a8d87 in perl_run () #6 0x55580332 in main () (gdb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1717367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC
$ gcc --version gcc (Ubuntu 5.4.0-6ubuntu1~16.04.5) 5.4.0 20160609 Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ gcc -fcheck-pointer-bounds -mmpx foo.c $ ldd a.out linux-vdso.so.1 => (0x7fff289d1000) libmpx.so.0 => /usr/lib/x86_64-linux-gnu/libmpx.so.0 (0x7fce0497a000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fce045b) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fce04393000) /lib64/ld-linux-x86-64.so.2 (0x7fce04b81000) ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1623418 Title: gcc-as-needed.diff patch broke mpx support in GCC Status in gcc: Unknown Status in binutils package in Ubuntu: Fix Released Status in gcc-5 package in Ubuntu: Fix Released Status in gcc-6 package in Ubuntu: Fix Released Status in binutils source package in Xenial: Fix Released Status in gcc-5 source package in Xenial: Fix Committed Status in binutils source package in Yakkety: Won't Fix Status in gcc-5 source package in Yakkety: Won't Fix Status in gcc-6 source package in Yakkety: Won't Fix Bug description: [SRU Justification] gcc-5 from Ubuntu is configured with MPX support, but it is broken due to always-added linker option "-as-needed". [Test case] 1. Pass -mmpx to gcc when building an arbitrary project on x86. 2. Verify with ldd that the resulting executable is not linked against libmpx.so because the -as-needed flag has discarded the mpx library from being linked in. 3. Install binutils and gcc-5 from -proposed. 4. Rebuild the target, again with -mmpx. 5. Verify with ldd that the new executable is linked against libmpx.so. 6. Verify that there are no regressions in the binutils testsuite on any architectures, by manually checking the results in the build log. [Regression potential] This binutils patch implements new --push-state / --pop-state options which will not be used in the common case, only when -mmpx is passed. When these flags are not in use, which is the default, it should have no effect on the behavior of the toolchain, so risk of regression is minimal. Here is the GCC upstream bug & fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267 https://gcc.gnu.org/viewcvs/gcc?view=revision=240057 Would it be possible to backport this fix to Ubuntu gcc-5 build? To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1623418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1609546] Re: DNS lookup through Netgear DG834G V4 router slow or times out
Same case than Gannet after Zesty upgrade. Disabling DNSEC does not fix anything. -- 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/1609546 Title: DNS lookup through Netgear DG834G V4 router slow or times out Status in systemd package in Ubuntu: Triaged Bug description: Update: On Zesty I am seeing a timeout both with systemd-resolve and dnslookup rather than just a slow resolution. The workaround in comment #6 which disables DNSSEC still corrects the problem. --- On up to date Yakkety if I specify my Netgear router as the DNS server (via Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I run, for example, systemd-resolve www.google.com or wget www.google.com I do not see the same delay if I run nslookup www.google.com A clue may be that in syslog I see Aug 3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 127.0.1.1. Aug 3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set (UDP+EDNS0) for DNS server 127.0.1.1. Aug 3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set (UDP) for DNS server 127.0.1.1. I do not see the issue if I specify an external DNS server. I do not see the issue on 16.04, nor previous versions, or on other devices connected to the network. I have been using this router for years. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 3 21:24:07 2016 InstallationDate: Installed on 2016-08-02 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802) MachineType: Hewlett-Packard Presario CQ57 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.47 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3577 dmi.board.vendor: Hewlett-Packard dmi.board.version: 24.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Presario CQ57 Notebook PC dmi.product.version: 068E1220491620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1609546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717367] Re: FTBFS: segfaults in testsuite with perl 5.26.0-7
** Bug watch added: Debian Bug tracker #875927 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875927 ** Also affects: glibc (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875927 Importance: Unknown Status: Unknown ** Changed in: libanyevent-perl (Ubuntu) Status: New => Invalid ** Changed in: glibc (Ubuntu) Status: New => Invalid -- 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/1717367 Title: FTBFS: segfaults in testsuite with perl 5.26.0-7 Status in glibc package in Ubuntu: Invalid Status in libanyevent-perl package in Ubuntu: Invalid Status in perl package in Ubuntu: Fix Released Status in glibc package in Debian: Unknown Bug description: The autopkgtests segfault against perl 5.26.0-7 in Ubuntu, and the new version of the package also fails to build in -proposed because the tests are segfaulting at package build time. $ perl ./t/02_signals.t 1..5 ok 1 Segmentation fault (core dumped) $ gdb --args perl ./t/02_signals.t GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. [...] (gdb) run Starting program: /usr/bin/perl ./t/02_signals.t [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 1..5 ok 1 Program received signal SIGSEGV, Segmentation fault. 0x7738811e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x7738811e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7626591d in ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Async/Interrupt/Interrupt.so #2 0x762672a9 in ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Async/Interrupt/Interrupt.so #3 0x5562fab1 in Perl_pp_entersub () #4 0x556278e6 in Perl_runops_standard () #5 0x555a8d87 in perl_run () #6 0x55580332 in main () (gdb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1717367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717738] 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 '
*** This bug is a duplicate of bug 1717737 *** https://bugs.launchpad.net/bugs/1717737 ** This bug has been marked a duplicate of bug 1717737 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') -- 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/1717738 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: New 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/1717738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
