[Touch-packages] [Bug 1692247] Re: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed')
Hello all, this bug also prevents me from installing other OS updates. If anyone can relate to this, then I think security may actually be an issue if some important security updates cannot subsequently be installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692247 Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') Status in iproute2 package in Ubuntu: Incomplete Bug description: I dont know anything. I just try to instal some programs on my comp, and when i try to start virtualbox it cant. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3.16.04.1 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.5 AptOrdering: iproute2: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat May 20 16:22:19 2017 DpkgTerminalLog: dpkg: error processing package iproute2 (--configure): package iproute2 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-02-20 (88 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: package iproute2 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/iproute2/+bug/1692247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1678564] Re: Unable to clear the notification list
[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1678564 Title: Unable to clear the notification list Status in unity8 package in Ubuntu: Expired Bug description: Since a few weeks I can not delete notifications from the list under the green envelope in a notification area. Green LED of my M10 blinks and notification list is full of new items that I can't delete nor click them. "Clear all" deosn't work as well as clicking on a notification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1678564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688208] Re: gnome-shell crashed with SIGSEGV in foreach_city() from foreach_city() from foreach_city() from foreach_city() from foreach_city()
** Changed in: libgweather (Ubuntu Zesty) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1688208 Title: gnome-shell crashed with SIGSEGV in foreach_city() from foreach_city() from foreach_city() from foreach_city() from foreach_city() Status in libgweather: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Zesty: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.24.1-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/39b6625ed47999dab38b064b2d91bde1e11dec62 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1688208/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695567] Re: /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free or corruption (out): ADDR ***
** Changed in: libgweather (Ubuntu Zesty) Status: New => In Progress ** No longer affects: gnome-shell (Ubuntu Zesty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1695567 Title: /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free or corruption (out): ADDR *** Status in gnome-shell package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Zesty: In Progress Bug description: [Impact] Backport git patch that fixes memory corruption in libgweather that is causing gnome-shell to crash. This is particularly bad on wayland as it causes the user to lose their sessions I believe this should also fix bug 1688208 and potentially a couple of other high ranking crashes on errors.ubuntu.com. I have not however found reliable reproducers for those other bugs. [Test Case] After update of libgweather 1. Ensure org.gnome.Weather.Application locations is not set (as per default setting) 2. Disable Location Services 3. gnome-shell should not crash [Regression Potential] Low, the patch merely fixes a refcounting bug. Given the high impact of this bug, this is an important fix. Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.24.2-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695567/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695567] Re: /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free or corruption (out): ADDR ***
** Also affects: libgweather (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid ** Changed in: libgweather (Ubuntu) Status: New => Fix Released ** Also affects: libgweather (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Zesty) Importance: Undecided Status: New ** Description changed: + [Impact] + Backport git patch that fixes memory corruption in libgweather that is causing gnome-shell to crash. This is particularly bad on wayland as it causes the user to lose their sessions + + I believe this should also fix bug 1688208 and potentially a couple of + other high ranking crashes on errors.ubuntu.com. I have not however + found reliable reproducers for those other bugs. + + [Test Case] + After update of libgweather + 1. Ensure org.gnome.Weather.Application locations is not set (as per default setting) + 2. Disable Location Services + 3. gnome-shell should not crash + + [Regression Potential] + Low, the patch merely fixes a refcounting bug. Given the high impact of this bug, this is an important fix. + + Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.24.2-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1695567 Title: /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free or corruption (out): ADDR *** Status in gnome-shell package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in gnome-shell source package in Zesty: New Status in libgweather source package in Zesty: New Bug description: [Impact] Backport git patch that fixes memory corruption in libgweather that is causing gnome-shell to crash. This is particularly bad on wayland as it causes the user to lose their sessions I believe this should also fix bug 1688208 and potentially a couple of other high ranking crashes on errors.ubuntu.com. I have not however found reliable reproducers for those other bugs. [Test Case] After update of libgweather 1. Ensure org.gnome.Weather.Application locations is not set (as per default setting) 2. Disable Location Services 3. gnome-shell should not crash [Regression Potential] Low, the patch merely fixes a refcounting bug. Given the high impact of this bug, this is an important fix. Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.24.2-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695567/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
I am using Lubuntu 17.04, and when using Synaptic, I get the "...unsandboxed..." message after a completed download. One message per download. (Why only one? The package I just downloaded for testing purposes pulled in six or eight other packages, but only the last was shown in the message.) The message occurs in an error window: a large triangle with an exclamation markis shown, with the large text "An error occurred", then (smaller) "The following details are provided:" So to the user, it does not LOOK like a one-line minor warning... Synaptic does not refresh the package listing until after dismissing the window. I now provide 3 examples of the detail provided: W: Download is performed unsandboxed as root as file '/var/cache/apt/archives/partial/libreoffice-style- galaxy_1%3a5.3.1-0ubuntu2_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) W: Download is performed unsandboxed as root as file '/var/cache/apt/archives/partial/gstreamer1.0-pulseaudio_1.10.4-1ubuntu1_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) W: Download is performed unsandboxed as root as file '/var/cache/apt/archives/partial/speedtest-cli_1.0.0-1_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/cache/apt/archives/partial and /var/lib/update-notifier/package-data-downloads/partial both have Owner (Create and delete files) and Group (Access files) owned by Root. /etc/passwd contains a line: _apt:x:105:65534::/nonexistent:/bin/false ...so the user does exist, but is not assigned to the two directories comment #43 says that apparently I should do a: sudo chown _apt <...each of the two above directories...> Should I? How/when are these directories created in the first place? Surely whatever created them should have set them up with _apt as owner...? I don't think I have received this message from update-notifier, but am not sure... -- scott@scott-ASUS-M2N68-AMPLUS:~$ uname -a Linux scott-ASUS-M2N68-AMPLUS 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux scott@scott-ASUS-M2N68-AMPLUS:~$ lsb_release -dsc Ubuntu 17.04 zesty scott@scott-ASUS-M2N68-AMPLUS:~$ echo $DESKTOP_SESSION Lubuntu scott@scott-ASUS-M2N68-AMPLUS:~$ apt --version apt 1.4 (amd64) Synapticversion 0.84.2 update-notifier version 3.179 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Confirmed Status in apt package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688209] Re: gnome-shell crashed with SIGSEGV in __GI___libc_free() from g_free() from gweather_location_unref() from g_boxed_free() from boxed_finalize()
** Also affects: libgweather (Ubuntu) Importance: Undecided Status: New ** Also affects: libgweather (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Invalid ** Changed in: libgweather (Ubuntu) Status: New => Triaged ** Changed in: libgweather (Ubuntu) Status: Triaged => Fix Released ** Changed in: libgweather (Ubuntu Zesty) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1688209 Title: gnome-shell crashed with SIGSEGV in __GI___libc_free() from g_free() from gweather_location_unref() from g_boxed_free() from boxed_finalize() Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in gnome-shell source package in Zesty: New Status in libgweather source package in Zesty: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.24.1-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/36de667464128521f03dbe854aea86811961f4f0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1688209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695564] Re: package linux-firmware 1.157.10 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1695564 Title: package linux-firmware 1.157.10 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in initramfs-tools package in Ubuntu: New Bug description: I intented upgrade my ubuntu but in the end show me the message error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.10 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Fri Jun 2 20:34:42 2017 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2017-03-16 (78 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.10 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1695564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695564] [NEW] package linux-firmware 1.157.10 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Public bug reported: I intented upgrade my ubuntu but in the end show me the message error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.10 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Fri Jun 2 20:34:42 2017 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2017-03-16 (78 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.10 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1695564 Title: package linux-firmware 1.157.10 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in initramfs-tools package in Ubuntu: New Bug description: I intented upgrade my ubuntu but in the end show me the message error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.10 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Fri Jun 2 20:34:42 2017 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2017-03-16 (78 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.10 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1695564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1636503] Re: recovery mode gets borked after some time out
It looks like it is an error with the terminal display. I can still type and get commands to go through, but the display is garbled spacing. I can call nano /etc/fstab and get my fstab file without issue. Everything is properly spaced and I can type without issue. -- 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/1636503 Title: recovery mode gets borked after some time out Status in systemd package in Ubuntu: Confirmed Bug description: (Linux mint 18 / Xenial) after booting in recovery mode from grub. If you just wait 30-60seconds, a new stream of messages appear and something gets messed up, you can't use recovery mode any more, you have to do a hard reboot. You don't need to do something in particular for this to happen, simply some time out occurs. --- more precisely, one of the messages say(copied manually): "[FAILED] Failed to start Console System on Startup logging. see 'systemctl status console-kit-log-system-start.service' for more details. It seams, it tries to launch a second recovery mode on top of the previous one after the error. I confirm, this is happening on both my PC linux mint 18 64bits, laptop linux mint 18 32bits and some one else from a forum on a ThinkPad X201 with Mint 18 KDE 64-bit. On my systems, both are fully up to date, 32 and 64 bit. Kernels don't seam to change anything. systemd version 229-4ubuntu11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1636503] Re: recovery mode gets borked after some time out
Confirmed – mostly. Running: Mint 18 Cinnamon 64-bit Kernel: 4.4.0-78 Laptop: Lenovo Thinkpad Yoga 12 Backstory: I have a dual boot with windows 10, which I evidently messed up because I would get a (busybox) prompt every once in a while. Generally running a manual fsck would fix that. Last night, had problems logging in (we're talking a couple minutes to boot to login, then hours to actually get past the login screen. I went ahead and tried to go into recovery mode tonight and fix it. First glaring issue was that I kept getting a message that I had no swap. Googled a bit found a solution to try was to reformat the swap partition and reset /etc/fstab. I was able to do this with only occasionally running into this "double screen" bug. Great. Reboot. Same issue logging in. When I went into recovery mode to try again, I am now getting this option almost every time. In fact, my initial boot includes "[ OK ] Started Monitoring of LVM2 mirrors, snapsots etc. using dmeventd or progress polling." across the first entry. Because the first entry is where it places the cursor, it appears there may be a timing issue. Oooop. some crap just happened. Without touching it, it now started giving me a weird output. It starts with "[ OK ] Stopped Run anacron jobs." and has a whole misaligned lists of "[ OK ]" and a few "[FAILED]." The failed are "Failed to start Set console font and keymap" and "Failed to start Console System Startup Logging. After all of this, I get "Welcome to emergency mode! After logging in, type "journalctl -xb" to . . . ." Gave root password as requested, and now we're to the second opening screen. Lighter bluew, "root@LT-A ~#" is now on the first line, but hasn't covered the "Resume normal boot" portion. Does this help? Probably not, but I am getting extremely frustrated. There are times when I boot and was able to work in recovery mode. -- 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/1636503 Title: recovery mode gets borked after some time out Status in systemd package in Ubuntu: Confirmed Bug description: (Linux mint 18 / Xenial) after booting in recovery mode from grub. If you just wait 30-60seconds, a new stream of messages appear and something gets messed up, you can't use recovery mode any more, you have to do a hard reboot. You don't need to do something in particular for this to happen, simply some time out occurs. --- more precisely, one of the messages say(copied manually): "[FAILED] Failed to start Console System on Startup logging. see 'systemctl status console-kit-log-system-start.service' for more details. It seams, it tries to launch a second recovery mode on top of the previous one after the error. I confirm, this is happening on both my PC linux mint 18 64bits, laptop linux mint 18 32bits and some one else from a forum on a ThinkPad X201 with Mint 18 KDE 64-bit. On my systems, both are fully up to date, 32 and 64 bit. Kernels don't seam to change anything. systemd version 229-4ubuntu11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695556] [NEW] /usr/bin/zeitgeist-daemon:6:____lambda5__glog_func:g_logv:g_log:zeitgeist_data_source_registry_extension_real_unload:g_ptr_array_foreach
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding zeitgeist. This problem was most recently seen with package version 0.9.16-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/574e1ecf533881654f7b16a660950f60d8e94efe contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Tags: vivid wily xenial zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1695556 Title: /usr/bin/zeitgeist- daemon:6:lambda5__glog_func:g_logv:g_log:zeitgeist_data_source_registry_extension_real_unload:g_ptr_array_foreach Status in zeitgeist package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding zeitgeist. This problem was most recently seen with package version 0.9.16-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/574e1ecf533881654f7b16a660950f60d8e94efe contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1695556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695553] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 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 #1688721, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1688721 Packages that trigger multiple debconf prompts fail to install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1695553 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: hi it wont let me update to kodi 17.3 i have uninstalled kodi 17.1 but there must be a bin or file still hidding help now no kodi says broken ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri Jun 2 18:51:54 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-02 (0 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1695553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694989] Re: apt-mark overwrites existing held package info
Is it really /any/ which I can't confirm at the moment as holding e.g. apt & dpkg works just fine… The underlying question is: Are the packages you are trying to hold installed? If not, dpkg will accept the hold at first and record it (so apt will report it on showhold again), but as soon as the dpkg/status file is modified again (e.g. with another hold), the record for the uninstalled package is cleaned up removing the hold. That is intended behavior by dpkg upstream according to earlier talks (and in there since ever, but I think the situations in which cleanup happens increased over time). We were thinking of having some way of having dpkg store such info even for not installed packages, but then life (& freeze) happened I guess, so there is nothing to show off apart from "yeah, we should be doing something, maybe". Perhaps we should just change apt to not accept holds for non-installed packages until that is resolved in some way. -- 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/1694989 Title: apt-mark overwrites existing held package info Status in apt package in Ubuntu: Triaged Bug description: Running apt-mark hold commands overwrites / nullifies any existing held package data. Not sure if this is by design, but I assume it's meant to be cumulative. Ubuntu version: 16.04.2 LTS Package version: apt 1.2.19 amd64 Expected behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 3dchess 0ad Actual behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 0ad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695554] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 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 #1688721, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1688721 Packages that trigger multiple debconf prompts fail to install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1695554 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: hi it wont let me update to kodi 17.3 i have uninstalled kodi 17.1 but there must be a bin or file still hidding help now no kodi says broken ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri Jun 2 18:51:54 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-02 (0 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1695554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695553] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: hi it wont let me update to kodi 17.3 i have uninstalled kodi 17.1 but there must be a bin or file still hidding help now no kodi says broken ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri Jun 2 18:51:54 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-02 (0 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1695553 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: hi it wont let me update to kodi 17.3 i have uninstalled kodi 17.1 but there must be a bin or file still hidding help now no kodi says broken ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri Jun 2 18:51:54 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-02 (0 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1695553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695554] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: hi it wont let me update to kodi 17.3 i have uninstalled kodi 17.1 but there must be a bin or file still hidding help now no kodi says broken ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri Jun 2 18:51:54 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-02 (0 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1695554 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: hi it wont let me update to kodi 17.3 i have uninstalled kodi 17.1 but there must be a bin or file still hidding help now no kodi says broken ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri Jun 2 18:51:54 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-02 (0 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1695554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
@Doug Morse (dm-dougmorse): I am running Unity on Ubuntu 16.04 LTS, Pulseaudio 1:8.0-0ubuntu3.3~xenial1, looks the same as yours. More details of my system may be found in my duplicate report: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1651428 >From the reports you linked, I would assume at least the workaround from my first comment: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1582213/comments/6 could still help. -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
[Touch-packages] [Bug 1670124] Re: package libapt-pkg4.12 1.0.1ubuntu2.8 failed to install/upgrade: cannot copy extracted data for './usr/share/locale/pt/LC_MESSAGES/libapt-pkg4.12.mo' to '/usr/share/
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the package operation again. This will likely resolve your issue, but the failure can be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. If this does not resolve your bug please set its status back to New. Thanks in advance! ** Changed in: apt (Ubuntu) Status: New => Invalid ** Changed in: apt (Ubuntu) Importance: Undecided => Low ** Tags added: corrupted-package -- 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/1670124 Title: package libapt-pkg4.12 1.0.1ubuntu2.8 failed to install/upgrade: cannot copy extracted data for './usr/share/locale/pt/LC_MESSAGES /libapt-pkg4.12.mo' to '/usr/share/locale/pt/LC_MESSAGES/libapt- pkg4.12.mo.dpkg-new': unexpected end of file or stream Status in apt package in Ubuntu: Invalid Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libapt-pkg4.12 1.0.1ubuntu2.8 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Mon Mar 6 04:02:46 2017 DuplicateSignature: package:libapt-pkg4.12:1.0.1ubuntu2.8:cannot copy extracted data for './usr/share/locale/pt/LC_MESSAGES/libapt-pkg4.12.mo' to '/usr/share/locale/pt/LC_MESSAGES/libapt-pkg4.12.mo.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/share/locale/pt/LC_MESSAGES/libapt-pkg4.12.mo' to '/usr/share/locale/pt/LC_MESSAGES/libapt-pkg4.12.mo.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2015-02-05 (758 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: apt Title: package libapt-pkg4.12 1.0.1ubuntu2.8 failed to install/upgrade: cannot copy extracted data for './usr/share/locale/pt/LC_MESSAGES/libapt-pkg4.12.mo' to '/usr/share/locale/pt/LC_MESSAGES/libapt-pkg4.12.mo.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1670124/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
** Tags added: rls-aa-incoming -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694989] Re: apt-mark overwrites existing held package info
Confirmed on artful with apt version 1.4.6. ** Tags added: xenial ** Tags added: artful -- 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/1694989 Title: apt-mark overwrites existing held package info Status in apt package in Ubuntu: Triaged Bug description: Running apt-mark hold commands overwrites / nullifies any existing held package data. Not sure if this is by design, but I assume it's meant to be cumulative. Ubuntu version: 16.04.2 LTS Package version: apt 1.2.19 amd64 Expected behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 3dchess 0ad Actual behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 0ad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689978] Re: package udev 229-4ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1689978 Title: package udev 229-4ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: Confirmed Bug description: Probably the same bug as #1628868, " package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu17 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed May 10 19:47:29 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-07-03 (1408 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=82b0e4d6-77e8-401d-a09d-fc38c968920e ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package udev 229-4ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-04-17 (23 days ago) dmi.bios.date: 04/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0311 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0311:bd04/18/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1689978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser
** Branch linked: lp:~ci-train-bot/click/click-ubuntu-artful-2790 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: New Bug description: click the optparser cannot be installed in parallel with this package. Please break the conflict so they can be co-installable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
xinput didn't work for me at all. Neither was changing the sensitivity in the default mouse application or in gpointing-device-settings. What DID work for me was change the value in "/sys/devices/platform/i8042/serio1/sensitivity" to 200. It worked immediately. Good luck. -- 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/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Confirmed Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
I'm on XFCE. -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1582213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
@hife and @Mary Sherman (spot9019): You both indicate that the latest pulse-testing ppa fixes the problem for you. Can you both indicate whether you are running Unity as the desktop or KDE or perhaps some other? I still have suspicions that there may be a permissions issue that is specific to Unity (which is the desktop I use and for which the fix does NOT work, at least for me). Thanks. -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To
[Touch-packages] [Bug 1695403] Re: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1695403 Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in hicolor-icon-theme package in Ubuntu: New Bug description: no more info ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Fri Jun 2 19:08:58 2017 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-05-10 (754 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-06-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1695403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695403] [NEW] package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: no more info ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Fri Jun 2 19:08:58 2017 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-05-10 (754 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-06-02 (0 days ago) ** Affects: hicolor-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1695403 Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in hicolor-icon-theme package in Ubuntu: New Bug description: no more info ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Fri Jun 2 19:08:58 2017 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-05-10 (754 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-06-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1695403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime
I have the same issue on a fresh install of 16.10, but this only occurred AFTER I installed gnome-shell 3.22, but logged in using Unity. When I logged in using GNOME, the problem did not occur - although I suspect that this is only because the evolution-data-server wasn't started when I logged in with the GNOME desktop. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1633319 Title: memory leak in indicator-datetime Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10 on the System76 Serval WS indicator-datetime-service is consuming all the system memory from 3.7GB up to 32 GB in 30 seconds. The system kills the indicator- datetime-service process and indicator-datetime-service restarts and memory consumption repeats until killed again. All swap memory is consumed in this pattern. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 00:12:00 2016 EcryptfsInUse: Yes SourcePackage: indicator-datetime UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693158] Re: Decorations get weird when windows complete an operation
I'm using Ubuntu 17.04 with Gnome and I can't reproduce it. I see title and (x) fine and the bottom text grayed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693158 Title: Decorations get weird when windows complete an operation Status in ubuntu-themes package in Ubuntu: New Bug description: While updating packages I can see this happening for a second when the operation finishes. The decorations (font and icons in particular) become weird, like if something was broken. See the screenshot to better understand what I mean. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:38:32 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693724] Re: Context menus have no animation/fade-in under Gnome Shell
Is this a feature request or a bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693724 Title: Context menus have no animation/fade-in under Gnome Shell Status in gnome-shell package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: Context menus have no animation/fade-in under Gnome Shell. The transitions under Unity7 for context menus look nicer, less abrupt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334916] Re: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions
** Changed in: openssh (Ubuntu Trusty) Status: Confirmed => Triaged ** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1334916 Title: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Trusty: Triaged Bug description: Attached to this report is a small app the reproduces the issue by creating multiple channels within one sessions. (I fist hit this issue using JSCH library) Following information is printed to stdout if sshd is launched with -d flags (I've modified the sshd code to print PIDs next to debug level): debug3(7526): monitor_read: checking request 156 debug3(7526): mm_answer_consolekit_register entering debug1(7526): session_by_tty: session 0 tty /dev/pts/1 debug1(7573): server_input_channel_req: channel 2 request pty-req reply 1 debug1(7573): session_by_channel: session 2 channel 2 debug1(7573): session_input_channel_req: session 2 req pty-req debug1(7573): Allocating pty. debug3(7573): mm_request_send entering: type 28 debug3(7573): mm_pty_allocate: waiting for MONITOR_ANS_PTY debug3(7573): mm_request_receive_expect entering: type 29 debug3(7573): mm_request_receive entering debug1(7526): Unable to open session: The name org.freedesktop.ConsoleKit was not provided by any .service files debug3(7526): mm_request_send entering: type 157 debug3(7526): mm_request_receive entering debug3(7526): monitor_read: checking request 28 debug3(7526): mm_answer_pty entering debug2(7526): session_new: allocate (allocated 2 max 10) debug3(7526): session_unused: session id 2 unused debug1(7526): session_new: session 2 mm_request_receive_expect: read: rtype 157 != type 29 From the log, it looks as if two processes use the same set of pipes to communicate to the monitor, one of them is sending MONITOR_REQ_CONSOLEKIT_REGISTER, while another MONITOR_REQ_PTY, and because they use same set of pipes, and because both processes use same pipe FDs, monitor reply is sometimes delivered to the wrong process. I can reproduce the failure 90% of time using attached app, which expects first argument to be host name, second - login and the third - password, that are defaulted to ubuntu:ubuntu@localhost: $ ./ssh-multisession Connecting to localhost...Done! Authenticating as ubuntu...Done. Starting channel 0 Starting channel 1 ssh_channel_request_pty()=-1: Socket error: disconnected Starting channel 2 ssh_channel_open_session()=-1: Writing packet: error on socket (or connection closed): Operation now in progress Starting channel 3 The same script works fine if sshd is compiled without consolekit.patch: ./ssh-multisession debian-host debian debian Connecting to 172.17.162.237...Done! Authenticating as debian...Done. Starting channel 0 Starting channel 1 Starting channel 2 Starting channel 3 Starting channel 4 Starting channel 5 Starting channel 6 Starting channel 7 Starting channel 8 Starting channel 9 P.S. To compile a test app one needs to have libssh-dev package installed on your system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1334916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639584] Re: package light-themes 16.10+16.10.20161024-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
Probably is not a bug and you just need to reinstall the package. Try with: sudo apt-get install --reinstall light-themes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1639584 Title: package light-themes 16.10+16.10.20161024-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in ubuntu-themes package in Ubuntu: New Bug description: begins at start up ProblemType: Package DistroRelease: Ubuntu 16.10 Package: light-themes 16.10+16.10.20161024-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Nov 4 00:01:45 2016 DuplicateSignature: package:light-themes:16.10+16.10.20161024-0ubuntu1 Setting up python3-libapparmor (2.10.95-4ubuntu5.1) ... dpkg: error processing package light-themes (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-10-31 (6 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: ubuntu-themes Title: package light-themes 16.10+16.10.20161024-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1639584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693152] Re: Some icons in the decorations look overlapping
I can't see the overlaping in the screenshot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693152 Title: Some icons in the decorations look overlapping Status in ubuntu-themes package in Ubuntu: New Bug description: It seems that some icons are overlapping in the top left corner ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:26:05 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639584] Re: package light-themes 16.10+16.10.20161024-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
Also, this is not a place for asking support. There are a multitude of ways you can get help using Ubuntu, such as the Launchpad answer tracker, the Ask Ubuntu site, the Ubuntu forums, the #ubuntu channel on the Freenode IRC server, and the ubuntu-users mailing list. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1639584 Title: package light-themes 16.10+16.10.20161024-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in ubuntu-themes package in Ubuntu: New Bug description: begins at start up ProblemType: Package DistroRelease: Ubuntu 16.10 Package: light-themes 16.10+16.10.20161024-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Nov 4 00:01:45 2016 DuplicateSignature: package:light-themes:16.10+16.10.20161024-0ubuntu1 Setting up python3-libapparmor (2.10.95-4ubuntu5.1) ... dpkg: error processing package light-themes (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-10-31 (6 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: ubuntu-themes Title: package light-themes 16.10+16.10.20161024-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1639584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334916] Re: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions
** Also affects: openssh (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1334916 Title: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Trusty: Triaged Bug description: Attached to this report is a small app the reproduces the issue by creating multiple channels within one sessions. (I fist hit this issue using JSCH library) Following information is printed to stdout if sshd is launched with -d flags (I've modified the sshd code to print PIDs next to debug level): debug3(7526): monitor_read: checking request 156 debug3(7526): mm_answer_consolekit_register entering debug1(7526): session_by_tty: session 0 tty /dev/pts/1 debug1(7573): server_input_channel_req: channel 2 request pty-req reply 1 debug1(7573): session_by_channel: session 2 channel 2 debug1(7573): session_input_channel_req: session 2 req pty-req debug1(7573): Allocating pty. debug3(7573): mm_request_send entering: type 28 debug3(7573): mm_pty_allocate: waiting for MONITOR_ANS_PTY debug3(7573): mm_request_receive_expect entering: type 29 debug3(7573): mm_request_receive entering debug1(7526): Unable to open session: The name org.freedesktop.ConsoleKit was not provided by any .service files debug3(7526): mm_request_send entering: type 157 debug3(7526): mm_request_receive entering debug3(7526): monitor_read: checking request 28 debug3(7526): mm_answer_pty entering debug2(7526): session_new: allocate (allocated 2 max 10) debug3(7526): session_unused: session id 2 unused debug1(7526): session_new: session 2 mm_request_receive_expect: read: rtype 157 != type 29 From the log, it looks as if two processes use the same set of pipes to communicate to the monitor, one of them is sending MONITOR_REQ_CONSOLEKIT_REGISTER, while another MONITOR_REQ_PTY, and because they use same set of pipes, and because both processes use same pipe FDs, monitor reply is sometimes delivered to the wrong process. I can reproduce the failure 90% of time using attached app, which expects first argument to be host name, second - login and the third - password, that are defaulted to ubuntu:ubuntu@localhost: $ ./ssh-multisession Connecting to localhost...Done! Authenticating as ubuntu...Done. Starting channel 0 Starting channel 1 ssh_channel_request_pty()=-1: Socket error: disconnected Starting channel 2 ssh_channel_open_session()=-1: Writing packet: error on socket (or connection closed): Operation now in progress Starting channel 3 The same script works fine if sshd is compiled without consolekit.patch: ./ssh-multisession debian-host debian debian Connecting to 172.17.162.237...Done! Authenticating as debian...Done. Starting channel 0 Starting channel 1 Starting channel 2 Starting channel 3 Starting channel 4 Starting channel 5 Starting channel 6 Starting channel 7 Starting channel 8 Starting channel 9 P.S. To compile a test app one needs to have libssh-dev package installed on your system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1334916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334916] Re: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssh (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1334916 Title: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Trusty: Triaged Bug description: Attached to this report is a small app the reproduces the issue by creating multiple channels within one sessions. (I fist hit this issue using JSCH library) Following information is printed to stdout if sshd is launched with -d flags (I've modified the sshd code to print PIDs next to debug level): debug3(7526): monitor_read: checking request 156 debug3(7526): mm_answer_consolekit_register entering debug1(7526): session_by_tty: session 0 tty /dev/pts/1 debug1(7573): server_input_channel_req: channel 2 request pty-req reply 1 debug1(7573): session_by_channel: session 2 channel 2 debug1(7573): session_input_channel_req: session 2 req pty-req debug1(7573): Allocating pty. debug3(7573): mm_request_send entering: type 28 debug3(7573): mm_pty_allocate: waiting for MONITOR_ANS_PTY debug3(7573): mm_request_receive_expect entering: type 29 debug3(7573): mm_request_receive entering debug1(7526): Unable to open session: The name org.freedesktop.ConsoleKit was not provided by any .service files debug3(7526): mm_request_send entering: type 157 debug3(7526): mm_request_receive entering debug3(7526): monitor_read: checking request 28 debug3(7526): mm_answer_pty entering debug2(7526): session_new: allocate (allocated 2 max 10) debug3(7526): session_unused: session id 2 unused debug1(7526): session_new: session 2 mm_request_receive_expect: read: rtype 157 != type 29 From the log, it looks as if two processes use the same set of pipes to communicate to the monitor, one of them is sending MONITOR_REQ_CONSOLEKIT_REGISTER, while another MONITOR_REQ_PTY, and because they use same set of pipes, and because both processes use same pipe FDs, monitor reply is sometimes delivered to the wrong process. I can reproduce the failure 90% of time using attached app, which expects first argument to be host name, second - login and the third - password, that are defaulted to ubuntu:ubuntu@localhost: $ ./ssh-multisession Connecting to localhost...Done! Authenticating as ubuntu...Done. Starting channel 0 Starting channel 1 ssh_channel_request_pty()=-1: Socket error: disconnected Starting channel 2 ssh_channel_open_session()=-1: Writing packet: error on socket (or connection closed): Operation now in progress Starting channel 3 The same script works fine if sshd is compiled without consolekit.patch: ./ssh-multisession debian-host debian debian Connecting to 172.17.162.237...Done! Authenticating as debian...Done. Starting channel 0 Starting channel 1 Starting channel 2 Starting channel 3 Starting channel 4 Starting channel 5 Starting channel 6 Starting channel 7 Starting channel 8 Starting channel 9 P.S. To compile a test app one needs to have libssh-dev package installed on your system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1334916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
ppa:ubuntu-audio-dev/pulse-testing solves the problem for me. However, now when module-switch-on-connect is not loaded, sound will switch to bluetooth device, but neither System-Settings -> Sound nor indicator-sound make the switch to bluetooth device, making volume control unavailable without switching the setting manually. When the module is loaded, everything works as intended. -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled
[Touch-packages] [Bug 1662520] Re: openssh-server abruptly terminates multichannel sessions
*** This bug is a duplicate of bug 1334916 *** https://bugs.launchpad.net/bugs/1334916 Hello and thank you for filing this bug report. I've opened a task in the other bug for Trusty and that is the best place to follow up on it. ** This bug has been marked a duplicate of bug 1334916 sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1662520 Title: openssh-server abruptly terminates multichannel sessions Status in openssh package in Ubuntu: Confirmed Bug description: The bug fixed in https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1334916 (1:6.9p1-3) was never released for Ubuntu 14.04. The symptoms in openssh-server 1:6.6p1-2ubuntu2.8 are exactly the same as reported in that bug. Unfortunately, moving from 14.04 to a more recent release like 16.04 isn't an option for us. Neither is reverting to the previous release for 14.04, due to the security vulns that were fixed in the latest release. I'm happy to supply more information if required. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-server 1:6.6p1-2ubuntu2.8 ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: MATE Date: Tue Feb 7 13:35:30 2017 InstallationDate: Installed on 2015-03-13 (696 days ago) InstallationMedia: Ubuntu MATE 14.04.1 "Trusty Tahr" - final amd64 (2014) SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1662520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1679727] Re: Don't attempt to create devices in lx-brand containers
Check comment #4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to makedev in Ubuntu. https://bugs.launchpad.net/bugs/1679727 Title: Don't attempt to create devices in lx-brand containers Status in makedev package in Ubuntu: Confirmed Bug description: This is a similar issue to https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163 In a Joyent lx-brand container environment an upgrade of the makedev package fails at the post-installation script: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up makedev (2.3.1-93ubuntu2~ubuntu14.04.1) ... mknod: ‘mem-’: Operation not permitted makedev mem c 1 1 root kmem 0640: failed mknod: ‘kmem-’: Operation not permitted makedev kmem c 1 2 root kmem 0640: failed mknod: ‘null-’: Operation not permitted makedev null c 1 3 root root 0666: failed mknod: ‘port-’: Operation not permitted makedev port c 1 4 root kmem 0640: failed mknod: ‘zero-’: Operation not permitted makedev zero c 1 5 root root 0666: failed mknod: ‘full-’: Operation not permitted makedev full c 1 7 root root 0666: failed mknod: ‘random-’: Operation not permitted makedev random c 1 8 root root 0666: failed mknod: ‘urandom-’: Operation not permitted makedev urandom c 1 9 root root 0666: failed mknod: ‘tty-’: Operation not permitted makedev tty c 5 0 root tty 0666: failed mknod: ‘ram0-’: Operation not permitted makedev ram0 b 1 0 root disk 0660: failed mknod: ‘ram1-’: Operation not permitted makedev ram1 b 1 1 root disk 0660: failed mknod: ‘ram2-’: Operation not permitted makedev ram2 b 1 2 root disk 0660: failed mknod: ‘ram3-’: Operation not permitted makedev ram3 b 1 3 root disk 0660: failed mknod: ‘ram4-’: Operation not permitted makedev ram4 b 1 4 root disk 0660: failed mknod: ‘ram5-’: Operation not permitted makedev ram5 b 1 5 root disk 0660: failed mknod: ‘ram6-’: Operation not permitted makedev ram6 b 1 6 root disk 0660: failed mknod: ‘ram7-’: Operation not permitted makedev ram7 b 1 7 root disk 0660: failed mknod: ‘ram8-’: Operation not permitted makedev ram8 b 1 8 root disk 0660: failed mknod: ‘ram9-’: Operation not permitted makedev ram9 b 1 9 root disk 0660: failed mknod: ‘ram10-’: Operation not permitted makedev ram10 b 1 10 root disk 0660: failed mknod: ‘ram11-’: Operation not permitted makedev ram11 b 1 11 root disk 0660: failed mknod: ‘ram12-’: Operation not permitted makedev ram12 b 1 12 root disk 0660: failed mknod: ‘ram13-’: Operation not permitted makedev ram13 b 1 13 root disk 0660: failed mknod: ‘ram14-’: Operation not permitted makedev ram14 b 1 14 root disk 0660: failed mknod: ‘ram15-’: Operation not permitted makedev ram15 b 1 15 root disk 0660: failed mknod: ‘ram16-’: Operation not permitted makedev ram16 b 1 16 root disk 0660: failed mknod: ‘loop0-’: Operation not permitted makedev loop0 b 7 0 root disk 0660: failed mknod: ‘loop1-’: Operation not permitted makedev loop1 b 7 1 root disk 0660: failed mknod: ‘loop2-’: Operation not permitted makedev loop2 b 7 2 root disk 0660: failed mknod: ‘loop3-’: Operation not permitted makedev loop3 b 7 3 root disk 0660: failed mknod: ‘loop4-’: Operation not permitted makedev loop4 b 7 4 root disk 0660: failed mknod: ‘loop5-’: Operation not permitted makedev loop5 b 7 5 root disk 0660: failed mknod: ‘loop6-’: Operation not permitted makedev loop6 b 7 6 root disk 0660: failed mknod: ‘loop7-’: Operation not permitted makedev loop7 b 7 7 root disk 0660: failed mknod: ‘tty0-’: Operation not permitted makedev tty0 c 4 0 root tty 0600: failed mknod: ‘console-’: Operation not permitted makedev console c 5 1 root tty 0600: failed ln: failed to create symbolic link ‘fd/fd’: Function not implemented ln: failed to create symbolic link ‘stdin’: File exists ln: failed to create symbolic link ‘stdout’: File exists ln: failed to create symbolic link ‘stderr’: File exists /sbin/MAKEDEV: don't know how to make device "tty0" dpkg: error processing package makedev (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: makedev E: Sub-process /usr/bin/dpkg returned an error code (1) The workaround is similar to 1675163 except in this case the post- installation script should check for "container=zone" in '/proc/1/environ': if grep -q container=zone /proc/1/environ then echo "lx-brand container detected." exit 0 fi To manage notifications about this bug go to:
[Touch-packages] [Bug 1639417] Re: package ubuntu-mono 16.10+16.10.20161024-0ubuntu1 failed to install/upgrade: »/usr/share/icons/ubuntu-mono-light/status/22/battery-040-charging.svg.dpkg-new« kann ni
Please describe the process you go through to trigger this bug and then change the bug status to NEW. It seems you are trying to install without super user permission. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1639417 Title: package ubuntu-mono 16.10+16.10.20161024-0ubuntu1 failed to install/upgrade: »/usr/share/icons/ubuntu-mono- light/status/22/battery-040-charging.svg.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: ... ProblemType: Package DistroRelease: Ubuntu 16.10 Package: ubuntu-mono 16.10+16.10.20161024-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Nov 4 06:56:00 2016 ErrorMessage: »/usr/share/icons/ubuntu-mono-light/status/22/battery-040-charging.svg.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig InstallationDate: Installed on 2016-06-01 (156 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: ubuntu-themes Title: package ubuntu-mono 16.10+16.10.20161024-0ubuntu1 failed to install/upgrade: »/usr/share/icons/ubuntu-mono-light/status/22/battery-040-charging.svg.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to yakkety on 2016-10-30 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1639417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694659] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hello and thank you for filing this bug report. It appears you have a local configuration error, as indicated by sshd: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 66: Bad configuration option: X11UseForwarding /etc/ssh/sshd_config: terminating, 1 bad configuration options Per `man sshd_config`, you want either: X11Forwarding or X11UseLocalhost But I don't know which you intended. "X11UseForwarding" is not a valid option, though. ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1694659 Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Invalid Bug description: Can't upgrade my ubuntu because of this ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed May 31 11:55:36 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-02-27 (92 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 66: Bad configuration option: X11UseForwarding /etc/ssh/sshd_config: terminating, 1 bad configuration options SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1694659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1587964] Re: package ubuntu-mono 14.04+16.04.20160415-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-light/status/22/indicator-keyboard-Ku-14.sv
Thank you for taking the time to report this bug. Please describe the process you go through to trigger this bug and then change the bug status to NEW. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1587964 Title: package ubuntu-mono 14.04+16.04.20160415-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/icons/ubuntu-mono- light/status/22/indicator-keyboard-Ku-14.svg.dpkg-new': Operation not permitted Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: I DID NOT FIND THE BUT BUT THE SYSTEM DID ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-mono 14.04+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Jun 1 21:19:16 2016 DuplicateSignature: package:ubuntu-mono:14.04+16.04.20160415-0ubuntu1 Unpacking ubuntu-mono (14.04+16.04.20160415-0ubuntu2) over (14.04+16.04.20160415-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/ubuntu-mono_14.04+16.04.20160415-0ubuntu2_all.deb (--unpack): unable to open '/usr/share/icons/ubuntu-mono-light/status/22/indicator-keyboard-Ku-14.svg.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/icons/ubuntu-mono-light/status/22/indicator-keyboard-Ku-14.svg.dpkg-new': Operation not permitted InstallationDate: Installed on 2016-05-25 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: ubuntu-themes Title: package ubuntu-mono 14.04+16.04.20160415-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-light/status/22/indicator-keyboard-Ku-14.svg.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1587964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1632524] Re: package light-themes 16.10+16.10.20160926-0ubuntu1 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 1
** Description changed: - the issue happend when i try tu upgrade all packages with synaptic app + The issue happend when I try to upgrade all packages with synaptic app. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: light-themes 16.10+16.10.20160926-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 11 19:24:32 2016 ErrorMessage: el subproceso script pre-installation nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2016-09-06 (36 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160904) PackageArchitecture: all RelatedPackageVersions: - dpkg 1.18.10ubuntu1 - apt 1.3.1 + dpkg 1.18.10ubuntu1 + apt 1.3.1 SourcePackage: ubuntu-themes Title: package light-themes 16.10+16.10.20160926-0ubuntu1 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 1 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 ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1632524 Title: package light-themes 16.10+16.10.20160926-0ubuntu1 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 1 Status in ubuntu-themes package in Ubuntu: New Bug description: The issue happend when I try to upgrade all packages with synaptic app. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: light-themes 16.10+16.10.20160926-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 11 19:24:32 2016 ErrorMessage: el subproceso script pre-installation nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2016-09-06 (36 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160904) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: ubuntu-themes Title: package light-themes 16.10+16.10.20160926-0ubuntu1 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1632524/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1309777] Re: Ubuntu themes cause Nautilus to flash when changing directories
Is this bug still present? I can’t recreate this bug in Ubuntu 17.04. If the bug is still present change the bug status to NEW. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1309777 Title: Ubuntu themes cause Nautilus to flash when changing directories Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: The new theme in Trusty causes Nautilus to flash pink when a directory is entered. This only occurs when viewing files and folders in list view, not icon view. See attached image. This is just a guess, but it might be related to this fix, since in Saucy the pink flash did not occur (but the columns did shift about): https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1018718 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1309777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299838] Re: [Radiance] Selection points next to menu items disappear when highlighted
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1299838 Title: [Radiance] Selection points next to menu items disappear when highlighted Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: When using the Radiance theme, the selection points, which are next to menu items, disappear when highlighted. See the attached screen-cast which describes the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: light-themes 14.04+14.04.20140327-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 30 19:05:08 2014 InstallationDate: Installed on 2014-03-08 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140304) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1299838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 771218] Re: Submenus appear higher than, but have same shadows as, their parents
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/771218 Title: Submenus appear higher than, but have same shadows as, their parents Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Binary package hint: light-themes Problem occurs with: compiz 1:0.9.4+bzr20110415-0ubuntu2, light-themes 0.1.8.13, Ubuntu Natty Does not occur with: Windows 7, Mac OS X 1. Open a highly-nested submenu, for example in Firefox "View" > "Character Encoding" > "More Encodings". Observe that: * The top-level menu has a shadow, showing that it is raised some non-zero distance from the desktop. Let's call this distance x. * The first submenu overlaps the top-level menu by 2 pixels, showing that it is raised some non-zero distance from the top-level menu. Let's call this distance y. * The second submenu similarly overlaps the first submenu by 2 pixels, showing that it is raised still further. What you see: Somehow, the shadow the second submenu casts on the desktop is exactly the same as the shadow the top-level menu casts on the desktop. y > 0 but x + y + y = x, which is impossible. What you should see: either * submenus should have progressively deeper shadows, to show that they're raised higher and higher; or * submenus should not overlap their parents. Following the same principle as bug 659816, I suggest that Ubuntu follow Windows and Mac OS X in showing all levels of submenu as being at exactly the same height. This can be fixed by moving them 2 pixels to the right, so that they don't overlap their parents at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/771218/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 750399] Re: audio-volume-muted-blocked-panel and bluetooth-disabled incorrectly make menus appear insensitive
Thank you for taking the time to report this bug. I have tried to recreate this on the latest release of Ubuntu and cannot reproduce it. This bug is being marked as Invalid. If you believe the problem to still exist in the latest version of Ubuntu please comment on why that is the case and change the bug status to NEW. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/750399 Title: audio-volume-muted-blocked-panel and bluetooth-disabled incorrectly make menus appear insensitive Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Binary package hint: ubuntu-mono Ubuntu Natty daily 20110404 1. Switch to the Ambiance theme, if you aren't currently using it. 2. Turn off Bluetooth, if it is currently on. 3. Mute the volume, e.g. by pressing the mute key on the keyboard. 4. Look at the menu bar. What you see: * The sound menu looks insensitive, when it is not. * The Bluetooth menu looks insensitive, when it is not. What you should see: Both menus look clickable. It is inconsistent for the icon theme to use grey/transparency to try indicating off state, while text-only menus (and other controls elsewhere) are using grey/transparency to indicate that they are not clickable. The volume icon already shows that volume is muted a better way, by a cross next to the speaker. The Bluetooth menu could use the ᛒ icon without the oval around it when Bluetooth is off , and add the oval around it when Bluetooth is on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/750399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695296] Re: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1695296 Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apport package in Ubuntu: New Bug description: got the at startup, but does seem to create problems. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Jun 2 17:41:10 2017 DuplicateSignature: package:apport:2.20.4-0ubuntu4 Setting up libcuda1-375 (375.66-0ubuntu0.17.04.1) ... dpkg: error processing package apport (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-17 (16 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: apport Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1695296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695296] [NEW] package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: got the at startup, but does seem to create problems. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Jun 2 17:41:10 2017 DuplicateSignature: package:apport:2.20.4-0ubuntu4 Setting up libcuda1-375 (375.66-0ubuntu0.17.04.1) ... dpkg: error processing package apport (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-17 (16 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: apport Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- 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/1695296 Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apport package in Ubuntu: New Bug description: got the at startup, but does seem to create problems. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Jun 2 17:41:10 2017 DuplicateSignature: package:apport:2.20.4-0ubuntu4 Setting up libcuda1-375 (375.66-0ubuntu0.17.04.1) ... dpkg: error processing package apport (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-17 (16 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: apport Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1695296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1146045] Re: Merge in and replace branding-ubuntu package
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1146045 Title: Merge in and replace branding-ubuntu package Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Since ubuntu-themes is the new Raring package containing the contents of the former light-themes, ubuntu-artwork, ubuntu-mono packages, I think it would make sense for branding-ubuntu to be included too. branding-ubuntu simply contains Ubuntu-themed art for Aisleriot & Mahjongg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1146045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 139873] Re: Wishlist: Root theme to inspire caution
** Changed in: ubuntu-themes (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/139873 Title: Wishlist: Root theme to inspire caution Status in UbuntuStudio Artwork: Invalid Status in ubuntu-themes package in Ubuntu: Opinion Bug description: I know this may not be the appropriate place to file this, but if not, please alter it accordingly, or let me know where I should file it. I was just wondering if it would be doable to have a default root theme that inspires caution (and looks spiffy too), or at least have the ability to set the root theme. Right now, if the user's theme isn't installed system-wide, Root programs go from tango to retro. I guess there are three things I'm looking for: 1) A nice, caution-inducing root theme used by default (maybe just tango, but with reds) 2) The ability to set the root theme. 3) Option there to track the user's theme (if sys-installed, else fallback to the set theme, else fallback to default) Thanks for your time, -brian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntustudio-artwork/+bug/139873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 645397] Re: "Restart required" icon bad contrast with default panel background
Can you send a screenshot? ** Changed in: ubuntu-themes (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/645397 Title: "Restart required" icon bad contrast with default panel background Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: Binary package hint: ubuntu-mono The system-shutdown-panel-restart.svg is red, its combination with the default "fuscous gray" panel background makes it unpleasant, I don't know if low contrast is the issue here, but I dare you to read red text on fuscous gray without weeping. It's just a bad color combination, I don't even consider it a subjective matter. Besides, bright red is a bit "scary", it screams urgency, like something is wrong, which is not the case. IMHO a more subtle color should be chosen, yellow is commonly used for something that requires attention, orange would work too, but it's already used for icon folders and other stuff, so it may not stand out enough. Anyway, it's not my job to select a palette for this stuff, IIRC the Ayatana group was discussing this a while ago; that said, the chosen color should look fine with the default panel background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/645397/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635806] Re: dividers in rightclick menu are overpowering
It looks just fine for me. If you believe the problem to still exist in Gnome Shell please comment on why that is the case and change the bug status to NEW. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1635806 Title: dividers in rightclick menu are overpowering Status in ubuntu-themes package in Ubuntu: Invalid Bug description: as of 16.10 the dividers in the nautilus right click menu (and also else where on ubuntu) are very deep and overbearing. They were lovely in 16.04 and have no clue why this graphic was changed... ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 22 19:24:55 2016 InstallationDate: Installed on 2016-10-14 (8 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1635806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 713839] Re: keys in trusted.gpg
*** This bug is a duplicate of bug 1182932 ***
https://bugs.launchpad.net/bugs/1182932
The approach suggested here appears to have been implemented in Xenial
(Ubuntu 16.04).
After adding the Ansible PPA, I have a file
`/etc/apt/trusted.gpg.d/ansible_ubuntu_ansible.gpg`. I can also see the
Ansible key is not included in the output of:
gpg --list-keys --no-default-keyring --keyring /etc/apt/trusted.gpg
** This bug has been marked a duplicate of bug 1182932
Add PPA keys to /etc/apt/trusted.gpg.d/{owner}-{ppa}.gpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/713839
Title:
keys in trusted.gpg
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
The apt-add-repository adds a new file in /etc/apt/sources.list.d and
adds the key into /etc/apt/trusted.gpg file. Why does it not use
/etc/apt/trusted.gpg.d dir?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/713839/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693474] Re: Switches in Ambiance CSD headerbar are disproportionately big
** Changed in: ubuntu-themes (Ubuntu) Status: New => Opinion ** Changed in: ubuntu-themes (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693474 Title: Switches in Ambiance CSD headerbar are disproportionately big Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Look at the screenshot, is it expected for the switch in the top right corner to be so large? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 25 12:36:16 2017 InstallationDate: Installed on 2017-04-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695292] [NEW] I can see through the title bar when the window is maximized
Public bug reported: I'm using gnome-shell in Ubuntu 17.04 When I maximize a window in the following programs: Firefox, Terminal, Rhythmbox, LibreOffice. I can see the background colors in top and bottom margins of the title bar. The bug is present in Ambiance and Radiance themes. The bug is not present in Nautilus, Google Chrome and Gnome Tweak Tool. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: light-themes 16.10+17.04.20170406-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jun 2 16:13:15 2017 InstallationDate: Installed on 2017-02-18 (103 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to zesty on 2017-05-22 (10 days ago) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "themes-bug.png" https://bugs.launchpad.net/bugs/1695292/+attachment/4887916/+files/themes-bug.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1695292 Title: I can see through the title bar when the window is maximized Status in ubuntu-themes package in Ubuntu: New Bug description: I'm using gnome-shell in Ubuntu 17.04 When I maximize a window in the following programs: Firefox, Terminal, Rhythmbox, LibreOffice. I can see the background colors in top and bottom margins of the title bar. The bug is present in Ambiance and Radiance themes. The bug is not present in Nautilus, Google Chrome and Gnome Tweak Tool. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: light-themes 16.10+17.04.20170406-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jun 2 16:13:15 2017 InstallationDate: Installed on 2017-02-18 (103 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to zesty on 2017-05-22 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1695292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695283] Re: package krb5-locales 1.15-1ubuntu0.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.
Thank you for filing this bug in Ubuntu. I suggest to run "sudo apt-get -f install" and see if that fixes the krb5-locales problem. Alternatively, you can try to reinstall it with "sudo apt-get install --reinstall krb5-locales". ** Changed in: krb5 (Ubuntu) Status: New => Incomplete -- 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/1695283 Title: package krb5-locales 1.15-1ubuntu0.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in krb5 package in Ubuntu: Incomplete Bug description: It appears when I turno the computer on. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: krb5-locales 1.15-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: libldap-2.4-2:amd64: Install libldap-common:amd64: Install libsndfile1:i386: Install libsndfile1:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Jun 2 02:19:00 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-06-02 02:18:45 Commandline: /usr/bin/unattended-upgrade Upgrade: libldap-2.4-2:amd64 (2.4.44+dfsg-3ubuntu2, 2.4.44+dfsg-3ubuntu2.1), libldap-common:amd64 (2.4.44+dfsg-3ubuntu2, 2.4.44+dfsg-3ubuntu2.1), libsndfile1:amd64 (1.0.27-1, 1.0.27-1ubuntu0.1), libsndfile1:i386 (1.0.27-1, 1.0.27-1ubuntu0.1) ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2016-12-31 (152 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: krb5 Title: package krb5-locales 1.15-1ubuntu0.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: Upgraded to zesty on 2017-04-16 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1695283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695283] [NEW] package krb5-locales 1.15-1ubuntu0.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.
Public bug reported: It appears when I turno the computer on. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: krb5-locales 1.15-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: libldap-2.4-2:amd64: Install libldap-common:amd64: Install libsndfile1:i386: Install libsndfile1:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Jun 2 02:19:00 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-06-02 02:18:45 Commandline: /usr/bin/unattended-upgrade Upgrade: libldap-2.4-2:amd64 (2.4.44+dfsg-3ubuntu2, 2.4.44+dfsg-3ubuntu2.1), libldap-common:amd64 (2.4.44+dfsg-3ubuntu2, 2.4.44+dfsg-3ubuntu2.1), libsndfile1:amd64 (1.0.27-1, 1.0.27-1ubuntu0.1), libsndfile1:i386 (1.0.27-1, 1.0.27-1ubuntu0.1) ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2016-12-31 (152 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: krb5 Title: package krb5-locales 1.15-1ubuntu0.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: Upgraded to zesty on 2017-04-16 (46 days ago) ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- 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/1695283 Title: package krb5-locales 1.15-1ubuntu0.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in krb5 package in Ubuntu: New Bug description: It appears when I turno the computer on. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: krb5-locales 1.15-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: libldap-2.4-2:amd64: Install libldap-common:amd64: Install libsndfile1:i386: Install libsndfile1:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Jun 2 02:19:00 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-06-02 02:18:45 Commandline: /usr/bin/unattended-upgrade Upgrade: libldap-2.4-2:amd64 (2.4.44+dfsg-3ubuntu2, 2.4.44+dfsg-3ubuntu2.1), libldap-common:amd64 (2.4.44+dfsg-3ubuntu2, 2.4.44+dfsg-3ubuntu2.1), libsndfile1:amd64 (1.0.27-1, 1.0.27-1ubuntu0.1), libsndfile1:i386 (1.0.27-1, 1.0.27-1ubuntu0.1) ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2016-12-31 (152 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: krb5 Title: package krb5-locales 1.15-1ubuntu0.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: Upgraded to zesty on 2017-04-16 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1695283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)
Ｄannie, For new kernel building, please note that is not a our general/stand zesty, I though Dann use a another kernel source tree or use may patches specified for D05 board. I am not familiar with it and please contact with Dann too. thanks, Mao -- 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/1691991 Title: Xorg Segmentation fault on Hisilicon D05 board (arm64) Status in xorg package in Ubuntu: New Bug description: ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg [sudo] password for ubuntu: X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu Current Operating System: Linux ubuntu 4.10.0-20.22-generic #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug earlycon=pl011,mmio,0x602B console=tty0 Build Date: 02 November 2016 10:05:28PM xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017 (==) Using system config directory "/usr/share/X11/xorg.conf.d" pci id for fd 10: 19e5:1711, driver (null) EGL_MESA_drm_image required. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48] (EE) (EE) Segmentation fault at address 0xa0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. Aborted (core dumped) ubuntu@ubuntu:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs
@Brian Murray (brian-murray)
> Eric - Have you tested the new version of openssl which William uploaded?
I did and my test cases results are still the same as the one pre-wgrant SRU.
All good on my side.
IMHO, the only things left to check are the 2-3 regressions in X and Y
for postgresql (X,Y) and mongodb (Y) on armhf architecture.
So far at first glance I can't see how this is failure are related to
our openssl changes, but I'll look at it more in deep.
The rest of the regressions found are explained in the description above
in the "Regression section" where it says : * autopktest failure.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1674399
Title:
OpenSSL CPU detection for AMD Ryzen CPUs
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Xenial:
Fix Committed
Status in openssl source package in Yakkety:
Fix Committed
Status in openssl source package in Zesty:
Fix Committed
Status in openssl source package in Artful:
Fix Released
Bug description:
[Impact]
* Context:
AMD added support in their processors for SHA Extensions[1] (CPU flag:
sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
64bit only (Confirmed with AMD representative). Current OpenSSL
version in Ryzens still calls SHA for SSSE3 routine as result a number
of extensions were effectively masked on Ryzen and shows no
improvement.
[1] /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 23
model : 1
model name : AMD Ryzen 5 1600 Six-Core Processor
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni
pclmulqdq monitor ssse3 fma cx16 sse
4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
[2] - sha_ni: SHA1/SHA256 Instruction Extensions
[3] - https://en.wikipedia.org/wiki/Ryzen
...
All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES,
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
...
* Program to performs the CPUID check:
Reference :
https://software.intel.com/en-us/articles/intel-sha-extensions
... Availability of the Intel® SHA Extensions on a particular
processor can be determined by checking the SHA CPUID bit in
CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
using inline assembly, performs the CPUID check:
--
int CheckForIntelShaExtensions() {
int a, b, c, d;
// Look for CPUID.7.0.EBX[29]
// EAX = 7, ECX = 0
a = 7;
c = 0;
asm volatile ("cpuid"
:"=a"(a), "=b"(b), "=c"(c), "=d"(d)
:"a"(a), "c"(c)
);
// Intel® SHA Extensions feature bit is EBX[29]
return ((b >> 29) & 1);
}
--
On CPU with sha_ni the program return "1". Otherwise it return "0".
[Test Case]
* Reproducible with Xenial/Zesty/Artful release.
* Generated a checksum of a big file (e.g. 5GB file) with openssl
$ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
SHA256(/var/tmp/5Gfile)=
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8
real 0m12.835s
user 0m12.344s
sys 0m0.484s
* Openssl speed
$ openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
OpenSSL 1.0.2g 1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int)
blowfish(idx)
compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55
The performance are clearly better when using the patch which take
benefit of the sha extension. (See Regression Potential section for
result with patch)
[Touch-packages] [Bug 1695117] Re: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1695117 Title: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apport package in Ubuntu: Confirmed Bug description: To be honest, im not really sure what happened, I started up and received this error. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: python3-apport 2.20.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportLog: ApportVersion: 2.20.4-0ubuntu4 AptOrdering: skypeforlinux:amd64: Remove NULL: ConfigurePending Architecture: amd64 CrashReports: 644:0:122:0:2017-06-01 19:22:21.986094497 -0400:2017-06-01 19:22:21.986094497 -0400:/var/crash/python3-apport.0.upload 600:0:122:65859:2017-06-01 20:15:31.175392389 -0400:2017-06-01 20:15:32.175392389 -0400:/var/crash/python3-apport.0.crash 600:113:122:0:2017-06-01 19:22:24.362038086 -0400:2017-06-01 19:22:24.362038086 -0400:/var/crash/python3-apport.0.uploaded Date: Thu Jun 1 20:15:32 2017 DpkgHistoryLog: Start-Date: 2017-06-01 20:15:30 Commandline: aptdaemon role='role-remove-packages' sender=':1.167' Remove: skypeforlinux:amd64 (5.2.0.1) DuplicateSignature: package:python3-apport:2.20.4-0ubuntu4 Processing triggers for desktop-file-utils (0.23-1ubuntu2) ... dpkg: error processing package python3-apport (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-12 (20 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: apport Title: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1695117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583544] Re: an official mirror doesn't show in mirrors list in Update Center, Ubuntu 16.04
Marking this as incomplete for now. The mirror probably needs to be accessible from Launchpad, but it refuses any connection attempt. ** Changed in: python-apt (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1583544 Title: an official mirror doesn't show in mirrors list in Update Center, Ubuntu 16.04 Status in Launchpad itself: New Status in python-apt package in Ubuntu: Incomplete Bug description: There is an official mirror mirrors.cug.edu.cn and I have seen it listed in https://launchpad.net/ubuntu/+mirror/mirrors.cug.edu.cn-archive, but I can't find it in Update Center in Ubuntu 16.04, Chinese mirrors list. It seems that the package python-apt ships a template file for the list of mirrors, and then it doesnt get updated over time. There is a function called get_ubuntu_lp_mirrors but it doesnt seem to be used. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1583544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583544] Re: an official mirror doesn't show in mirrors list in Update Center, Ubuntu 16.04
Probably because "We have found no versions for any architectures on this mirror. This is normal if we have not yet successfully verified the mirror." -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1583544 Title: an official mirror doesn't show in mirrors list in Update Center, Ubuntu 16.04 Status in Launchpad itself: New Status in python-apt package in Ubuntu: Incomplete Bug description: There is an official mirror mirrors.cug.edu.cn and I have seen it listed in https://launchpad.net/ubuntu/+mirror/mirrors.cug.edu.cn-archive, but I can't find it in Update Center in Ubuntu 16.04, Chinese mirrors list. It seems that the package python-apt ships a template file for the list of mirrors, and then it doesnt get updated over time. There is a function called get_ubuntu_lp_mirrors but it doesnt seem to be used. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1583544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583544] Re: an official mirror doesn't show in mirrors list in Update Center, Ubuntu 16.04
The mirror is not listed in https://launchpad.net/ubuntu /+archivemirrors-rss and thus is not added to python-apt. ** Also affects: launchpad Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1583544 Title: an official mirror doesn't show in mirrors list in Update Center, Ubuntu 16.04 Status in Launchpad itself: New Status in python-apt package in Ubuntu: Triaged Bug description: There is an official mirror mirrors.cug.edu.cn and I have seen it listed in https://launchpad.net/ubuntu/+mirror/mirrors.cug.edu.cn-archive, but I can't find it in Update Center in Ubuntu 16.04, Chinese mirrors list. It seems that the package python-apt ships a template file for the list of mirrors, and then it doesnt get updated over time. There is a function called get_ubuntu_lp_mirrors but it doesnt seem to be used. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1583544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667769] Re: apt-daily.service running too early in boot process
This was fixed in 1.4.2 (and the 1.3.? and 1.2.? SRUs) but I forgot to mention the bug in the changelog. Aargh. ** Changed in: apt (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1667769 Title: apt-daily.service running too early in boot process Status in apt package in Ubuntu: Fix Released Bug description: System: ubuntu mate 16.04 with apt version 1.2.19 Problem: On a desktop system I noticed that the package lists were being updated very infrequently. This is apparently because on most days the apt-daily.service is triggered early in the boot process when the network is not up. Since the timer is set to run approximately every 12 hours, and the system is only on for a few days, the timer tends to lapse over night and is then triggered as soon as the system is booted the following day. Also, `apt-get update` returns true regardless of whether there is a network connection, so the apt.systemd.daily script reports success and updates the timestamp file regardless. This means that if the system is only used for a few hours per day the package list may not be updated for many days until the timer lapses while the system happens to be already switched on. System journal showing typical output during boot process: Feb 10 14:38:13 desktop systemd[1]: Starting Daily apt activities... Feb 10 14:38:13 desktop apt.systemd.daily[3679]: verbose level 3 ... [truncated] ... Feb 10 14:38:14 desktop apt.systemd.daily[3679]: + apt-get -y update Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:1 http://security.ubuntu.com/ubuntu xenial-security InRelease Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Temporary failure resolving 'security.ubuntu.com' Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:2 http://ppa.launchpad.net/ubuntu-mate-dev/welcome/ubuntu xenial InRelease Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Temporary failure resolving 'ppa.launchpad.net' Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:3 http://gb.archive.ubuntu.com/ubuntu xenial InRelease Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Temporary failure resolving 'gb.archive.ubuntu.com' Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:4 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Temporary failure resolving 'gb.archive.ubuntu.com' Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Err:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease Feb 10 14:38:14 desktop apt.systemd.daily[3679]: Temporary failure resolving 'gb.archive.ubuntu.com' Feb 10 14:38:17 desktop apt.systemd.daily[3679]: Reading package lists... Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary fa Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temp Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease Te Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Tempo Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Failed to fetch http://ppa.launchpad.net/ubuntu-mate-dev/welcome/ubuntu/dists/xenial/InR Feb 10 14:38:17 desktop apt.systemd.daily[3679]: W: Some index files failed to download. They have been ignored, or old ones used instead. Feb 10 14:38:17 desktop apt.systemd.daily[3679]: + debug_echo download updated metadata (success). Work-around: I have worked around this by creating a file /etc/systemd/system/apt- daily.service.d/network.conf containing the following options: Wants=network-online.target After=network-online.target Maybe there is a better way to specify unit dependencies or to edit the timer so it will delay on startup, but this seems to fix the issue for me. Related bug: This other bug might be related, but it states that it causes apt-get to hang indefinitely, which I have not seen on my system. https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1636049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1667769/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695257] Re: package libproxy-tools 0.4.11-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1695257 Title: package libproxy-tools 0.4.11-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libproxy package in Ubuntu: New Bug description: Failed to install the Steam software. Probably only suitable for Windows and Mac. OS. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libproxy-tools 0.4.11-5ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Fri Jun 2 13:18:59 2017 DuplicateSignature: package:libproxy-tools:0.4.11-5ubuntu1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libproxy-tools (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-29 (4 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libproxy Title: package libproxy-tools 0.4.11-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1695257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695257] [NEW] package libproxy-tools 0.4.11-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Public bug reported: Failed to install the Steam software. Probably only suitable for Windows and Mac. OS. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libproxy-tools 0.4.11-5ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Fri Jun 2 13:18:59 2017 DuplicateSignature: package:libproxy-tools:0.4.11-5ubuntu1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libproxy-tools (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-29 (4 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libproxy Title: package libproxy-tools 0.4.11-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libproxy (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1695257 Title: package libproxy-tools 0.4.11-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libproxy package in Ubuntu: New Bug description: Failed to install the Steam software. Probably only suitable for Windows and Mac. OS. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libproxy-tools 0.4.11-5ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Fri Jun 2 13:18:59 2017 DuplicateSignature: package:libproxy-tools:0.4.11-5ubuntu1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libproxy-tools (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-29 (4 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libproxy Title: package libproxy-tools 0.4.11-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1695257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664979] Re: EQ overflowing. Additional events will be discarded until existing events are processed.
Hi! I can reproduce this bug too. System just going to freeze and does not react to keyboard. After reboot sometimes it happens again (for example while watching youtube video in vivaldi browser). Here's part of syslog attached. ** Attachment added: "syslog.1" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979/+attachment/4887785/+files/syslog.1 -- 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/1664979 Title: EQ overflowing. Additional events will be discarded until existing events are processed. Status in xorg package in Ubuntu: Confirmed Bug description: I was on 14.04 and had no problem, but I started to have EQ overflow after upgrading to 14.04.3. Then I did fresh install of 16.04 on the same PC, but still EQ overflow occurs after closing SMPlayer. [640410.566] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0x4078) [640417.566] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0x4078) [640421.680] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0xf5d4) [640428.680] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0xf5d4) [640439.704] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc1, 0x3d14, 0xf680) [640446.704] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc1, 0x3d14, 0xf680) [640449.705] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf7, 0x3d14, 0xf680) [640456.705] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf7, 0x3d14, 0xf680) [640459.706] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc2, 0x3d14, 0xf724) [640466.706] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc2, 0x3d14, 0xf724) [640469.707] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf8, 0x3d14, 0xf724) [640476.707] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf8, 0x3d14, 0xf724) [640479.708] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc3, 0x3d14, 0xf7c8) [640486.708] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc3, 0x3d14, 0xf7c8) [640489.709] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf9, 0x3d14, 0xf7c8) [640496.709] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf9, 0x3d14, 0xf7c8) [640499.710] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc4, 0x3d14, 0xf86c) [640506.710] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc4, 0x3d14, 0xf86c) [640509.711] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfa, 0x3d14, 0xf86c) [640516.711] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfa, 0x3d14, 0xf86c) [640519.712] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc5, 0x3d14, 0xf910) [640526.712] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc5, 0x3d14, 0xf910) [640529.713] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfb, 0x3d14, 0xf910) [640536.713] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfb, 0x3d14, 0xf910) [640539.714] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc6, 0x3d14, 0xf9b4) [640546.714] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc6, 0x3d14, 0xf9b4) [640549.715] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfc, 0x3d14, 0xf9b4) (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade] (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x55b19d04a583] (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) [0x7fdc68ed61f3] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) [0x7fdc68ed6a5d] (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538] (EE) 6: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) [0x7fdc6fb214b0] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__sched_yield+0x7) [0x7fdc6fbd5c47] (EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0xa7c61) [0x7fdc6ac04c61] (EE) 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0xbb7bc) [0x7fdc6ac187bc] (EE) 11: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0x5b1ec2) [0x7fdc6b10eec2] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade] (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862] (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) [0x7fdc68ed61f3] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) [0x7fdc68ed6a5d] (EE) 4: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538] (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) [0x7fdc6fb214b0]
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
** Also affects: mir (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: mir (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: In Progress Status in mir source package in Yakkety: In Progress Status in mir source package in Zesty: In Progress Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
** Changed in: mir (Ubuntu Yakkety) Status: New => In Progress ** Changed in: mir (Ubuntu Zesty) Status: New => In Progress ** Changed in: mir (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: mir (Ubuntu Zesty) Importance: Undecided => High ** Changed in: mir (Ubuntu Yakkety) Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: mir (Ubuntu Zesty) Assignee: (unassigned) => Alan Griffiths (alan-griffiths) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: In Progress Status in mir source package in Yakkety: In Progress Status in mir source package in Zesty: In Progress Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664979] Re: EQ overflowing. Additional events will be discarded until existing events are processed.
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/1664979 Title: EQ overflowing. Additional events will be discarded until existing events are processed. Status in xorg package in Ubuntu: Confirmed Bug description: I was on 14.04 and had no problem, but I started to have EQ overflow after upgrading to 14.04.3. Then I did fresh install of 16.04 on the same PC, but still EQ overflow occurs after closing SMPlayer. [640410.566] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0x4078) [640417.566] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0x4078) [640421.680] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0xf5d4) [640428.680] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0xf5d4) [640439.704] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc1, 0x3d14, 0xf680) [640446.704] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc1, 0x3d14, 0xf680) [640449.705] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf7, 0x3d14, 0xf680) [640456.705] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf7, 0x3d14, 0xf680) [640459.706] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc2, 0x3d14, 0xf724) [640466.706] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc2, 0x3d14, 0xf724) [640469.707] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf8, 0x3d14, 0xf724) [640476.707] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf8, 0x3d14, 0xf724) [640479.708] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc3, 0x3d14, 0xf7c8) [640486.708] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc3, 0x3d14, 0xf7c8) [640489.709] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf9, 0x3d14, 0xf7c8) [640496.709] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf9, 0x3d14, 0xf7c8) [640499.710] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc4, 0x3d14, 0xf86c) [640506.710] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc4, 0x3d14, 0xf86c) [640509.711] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfa, 0x3d14, 0xf86c) [640516.711] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfa, 0x3d14, 0xf86c) [640519.712] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc5, 0x3d14, 0xf910) [640526.712] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc5, 0x3d14, 0xf910) [640529.713] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfb, 0x3d14, 0xf910) [640536.713] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfb, 0x3d14, 0xf910) [640539.714] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc6, 0x3d14, 0xf9b4) [640546.714] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc6, 0x3d14, 0xf9b4) [640549.715] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfc, 0x3d14, 0xf9b4) (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade] (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x55b19d04a583] (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) [0x7fdc68ed61f3] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) [0x7fdc68ed6a5d] (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538] (EE) 6: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) [0x7fdc6fb214b0] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__sched_yield+0x7) [0x7fdc6fbd5c47] (EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0xa7c61) [0x7fdc6ac04c61] (EE) 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0xbb7bc) [0x7fdc6ac187bc] (EE) 11: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0x5b1ec2) [0x7fdc6b10eec2] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade] (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862] (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) [0x7fdc68ed61f3] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) [0x7fdc68ed6a5d] (EE) 4: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538] (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) [0x7fdc6fb214b0] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__sched_yield+0x7) [0x7fdc6fbd5c47] (EE) 8: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0xa7c61) [0x7fdc6ac04c61] (EE) 9:
[Touch-packages] [Bug 1693155] Re: Squashed blurry battery indicator
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693155 Title: Squashed blurry battery indicator in gnome-shell Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693155] Re: Squashed blurry battery indicator in gnome-shell
** Summary changed: - Squashed blurry battery indicator + Squashed blurry battery indicator in gnome-shell -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693155 Title: Squashed blurry battery indicator in gnome-shell Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693155] Re: Squashed blurry battery indicator
** Summary changed: - Blurry battery indicator + Squashed blurry battery indicator -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693155 Title: Squashed blurry battery indicator in gnome-shell Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693155] Re: Squashed blurry battery indicator
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693155 Title: Squashed blurry battery indicator in gnome-shell Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693155] Re: Squashed blurry battery indicator
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-mono (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693155 Title: Squashed blurry battery indicator in gnome-shell Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: My battery indicator looks blurry ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 24 11:34:12 2017 InstallationDate: Installed on 2017-04-28 (25 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695212] Re: Desktop 20170602 - black screen on boot
gnome-shell aborts due to org.gnome-login-screen schemas not being installed. ** Package changed: ubuntu-meta (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Critical ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1695212 Title: [Desktop 20170602] gnome-shell fails to start. Black screen on boot. Status in gnome-shell package in Ubuntu: Triaged Bug description: ubuntu desktop amd64 - 20170602 ubiquity-dm and install ubuntu both boot to a black screen. the live session works fine and is running unity7 diff between 20170602 and 20170601 attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695212/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1679727] Re: Don't attempt to create devices in lx-brand containers
Joyent lx-brand user here with Ubuntu 14.04 image. Any guidance on how to work around this please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to makedev in Ubuntu. https://bugs.launchpad.net/bugs/1679727 Title: Don't attempt to create devices in lx-brand containers Status in makedev package in Ubuntu: Confirmed Bug description: This is a similar issue to https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163 In a Joyent lx-brand container environment an upgrade of the makedev package fails at the post-installation script: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up makedev (2.3.1-93ubuntu2~ubuntu14.04.1) ... mknod: ‘mem-’: Operation not permitted makedev mem c 1 1 root kmem 0640: failed mknod: ‘kmem-’: Operation not permitted makedev kmem c 1 2 root kmem 0640: failed mknod: ‘null-’: Operation not permitted makedev null c 1 3 root root 0666: failed mknod: ‘port-’: Operation not permitted makedev port c 1 4 root kmem 0640: failed mknod: ‘zero-’: Operation not permitted makedev zero c 1 5 root root 0666: failed mknod: ‘full-’: Operation not permitted makedev full c 1 7 root root 0666: failed mknod: ‘random-’: Operation not permitted makedev random c 1 8 root root 0666: failed mknod: ‘urandom-’: Operation not permitted makedev urandom c 1 9 root root 0666: failed mknod: ‘tty-’: Operation not permitted makedev tty c 5 0 root tty 0666: failed mknod: ‘ram0-’: Operation not permitted makedev ram0 b 1 0 root disk 0660: failed mknod: ‘ram1-’: Operation not permitted makedev ram1 b 1 1 root disk 0660: failed mknod: ‘ram2-’: Operation not permitted makedev ram2 b 1 2 root disk 0660: failed mknod: ‘ram3-’: Operation not permitted makedev ram3 b 1 3 root disk 0660: failed mknod: ‘ram4-’: Operation not permitted makedev ram4 b 1 4 root disk 0660: failed mknod: ‘ram5-’: Operation not permitted makedev ram5 b 1 5 root disk 0660: failed mknod: ‘ram6-’: Operation not permitted makedev ram6 b 1 6 root disk 0660: failed mknod: ‘ram7-’: Operation not permitted makedev ram7 b 1 7 root disk 0660: failed mknod: ‘ram8-’: Operation not permitted makedev ram8 b 1 8 root disk 0660: failed mknod: ‘ram9-’: Operation not permitted makedev ram9 b 1 9 root disk 0660: failed mknod: ‘ram10-’: Operation not permitted makedev ram10 b 1 10 root disk 0660: failed mknod: ‘ram11-’: Operation not permitted makedev ram11 b 1 11 root disk 0660: failed mknod: ‘ram12-’: Operation not permitted makedev ram12 b 1 12 root disk 0660: failed mknod: ‘ram13-’: Operation not permitted makedev ram13 b 1 13 root disk 0660: failed mknod: ‘ram14-’: Operation not permitted makedev ram14 b 1 14 root disk 0660: failed mknod: ‘ram15-’: Operation not permitted makedev ram15 b 1 15 root disk 0660: failed mknod: ‘ram16-’: Operation not permitted makedev ram16 b 1 16 root disk 0660: failed mknod: ‘loop0-’: Operation not permitted makedev loop0 b 7 0 root disk 0660: failed mknod: ‘loop1-’: Operation not permitted makedev loop1 b 7 1 root disk 0660: failed mknod: ‘loop2-’: Operation not permitted makedev loop2 b 7 2 root disk 0660: failed mknod: ‘loop3-’: Operation not permitted makedev loop3 b 7 3 root disk 0660: failed mknod: ‘loop4-’: Operation not permitted makedev loop4 b 7 4 root disk 0660: failed mknod: ‘loop5-’: Operation not permitted makedev loop5 b 7 5 root disk 0660: failed mknod: ‘loop6-’: Operation not permitted makedev loop6 b 7 6 root disk 0660: failed mknod: ‘loop7-’: Operation not permitted makedev loop7 b 7 7 root disk 0660: failed mknod: ‘tty0-’: Operation not permitted makedev tty0 c 4 0 root tty 0600: failed mknod: ‘console-’: Operation not permitted makedev console c 5 1 root tty 0600: failed ln: failed to create symbolic link ‘fd/fd’: Function not implemented ln: failed to create symbolic link ‘stdin’: File exists ln: failed to create symbolic link ‘stdout’: File exists ln: failed to create symbolic link ‘stderr’: File exists /sbin/MAKEDEV: don't know how to make device "tty0" dpkg: error processing package makedev (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: makedev E: Sub-process /usr/bin/dpkg returned an error code (1) The workaround is similar to 1675163 except in this case the post- installation script should check for "container=zone" in '/proc/1/environ': if grep -q container=zone /proc/1/environ then echo "lx-brand container detected." exit 0 fi To
[Touch-packages] [Bug 1695212] [NEW] Desktop 20170602 - black screen on boot
Public bug reported: ubuntu desktop amd64 - 20170602 ubiquity-dm and install ubuntu both boot to a black screen. the live session works fine and is running unity7 diff between 20170602 and 20170601 attached. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Attachment added: "artful.diff" https://bugs.launchpad.net/bugs/1695212/+attachment/4887697/+files/artful.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1695212 Title: Desktop 20170602 - black screen on boot Status in ubuntu-meta package in Ubuntu: New Bug description: ubuntu desktop amd64 - 20170602 ubiquity-dm and install ubuntu both boot to a black screen. the live session works fine and is running unity7 diff between 20170602 and 20170601 attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1695212/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682499] Re: disable dnssec
This helped me only partially - I still have issues with DNS lookup. It seems that the systemd-resolved is broken from the very idea. After solving DNSSEC problem, I see now a switching problem - if one DNS does not respond, resolved switches to another one, which may be a local DNS not serving all the information, however it responds RELIABLY with "REFUSED" for majority of queries! Thus, resolved is stuck with this "reliable" DNS, refusing almost all queries until reboot (or networking reload). There are so many bugs filled about resolved that somebody should gather them in one place and do something. Moreover, tracing problems is not easy - they are intermittent, depending on current server load. For some people in fixed setup bug may be nonexistent; when travelling across well-configured, simple and non- overloaded networks everything is OK. Then, at some hour, some connection - I start having to reload network every time I start reading mail. For now many people are switching to alternative resolver - e.g. "unbound"; what is going on with resolved looks like sabotage. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1682499 Title: disable dnssec Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * dnssec functionality in systemd-resolved prevents network access in certain intra and extra net cases, due to failure to correctly validate dnssec entries. As a work-around we should disable dnssec by default. [Test Case] * Validate systemd-resolved is compiled with --with-default-dnssec=no * Validate that systemd-resolve --status says that DNSSEC setting is no $ systemd-resolve --status good output: ... DNSSEC setting: no DNSSEC supported: no ... bad output: ... DNSSEC setting: allow-downgrade DNSSEC supported: yes ... [Regression Potential] * People who expect DNSSEC to be available by default will need to re-enable it by modifying systemd-resolve configuration file [Other Info] * See duplicate bugs and other bug reports in systemd for scenarios of DNS resolution failures when DNSSEC is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs
I've been running the fixed OpenSSL on my artful Ryzen desktop, zesty
Haswell-U laptop and xenial Sandy Bridge server and its VMs for two
weeks without incident. These hosts include a variety of VPN clients,
HTTPS clients, HTTPS servers, SSH clients and servers, etc. The SRUs for
all series build successfully on i386 and amd64 on Ryzen and Apollo Lake
(I managed to acquire some hardware), the two shipping platforms that
were exposed to the previous regression, and which FTBFS with the
original SRU due to the test suite picking up the bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1674399
Title:
OpenSSL CPU detection for AMD Ryzen CPUs
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Xenial:
Fix Committed
Status in openssl source package in Yakkety:
Fix Committed
Status in openssl source package in Zesty:
Fix Committed
Status in openssl source package in Artful:
Fix Released
Bug description:
[Impact]
* Context:
AMD added support in their processors for SHA Extensions[1] (CPU flag:
sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
64bit only (Confirmed with AMD representative). Current OpenSSL
version in Ryzens still calls SHA for SSSE3 routine as result a number
of extensions were effectively masked on Ryzen and shows no
improvement.
[1] /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 23
model : 1
model name : AMD Ryzen 5 1600 Six-Core Processor
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni
pclmulqdq monitor ssse3 fma cx16 sse
4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
[2] - sha_ni: SHA1/SHA256 Instruction Extensions
[3] - https://en.wikipedia.org/wiki/Ryzen
...
All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES,
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
...
* Program to performs the CPUID check:
Reference :
https://software.intel.com/en-us/articles/intel-sha-extensions
... Availability of the Intel® SHA Extensions on a particular
processor can be determined by checking the SHA CPUID bit in
CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
using inline assembly, performs the CPUID check:
--
int CheckForIntelShaExtensions() {
int a, b, c, d;
// Look for CPUID.7.0.EBX[29]
// EAX = 7, ECX = 0
a = 7;
c = 0;
asm volatile ("cpuid"
:"=a"(a), "=b"(b), "=c"(c), "=d"(d)
:"a"(a), "c"(c)
);
// Intel® SHA Extensions feature bit is EBX[29]
return ((b >> 29) & 1);
}
--
On CPU with sha_ni the program return "1". Otherwise it return "0".
[Test Case]
* Reproducible with Xenial/Zesty/Artful release.
* Generated a checksum of a big file (e.g. 5GB file) with openssl
$ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
SHA256(/var/tmp/5Gfile)=
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8
real 0m12.835s
user 0m12.344s
sys 0m0.484s
* Openssl speed
$ openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
OpenSSL 1.0.2g 1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int)
blowfish(idx)
compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55
The performance are clearly better when using the patch which take
benefit of the sha extension. (See Regression Potential section for
result with patch)
[Regression Potential]
* Note : IRC discussion with infinity :
[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)
Dann: thanks, will do that. Regards, Daniel -- 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/1691991 Title: Xorg Segmentation fault on Hisilicon D05 board (arm64) Status in xorg package in Ubuntu: New Bug description: ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg [sudo] password for ubuntu: X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu Current Operating System: Linux ubuntu 4.10.0-20.22-generic #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug earlycon=pl011,mmio,0x602B console=tty0 Build Date: 02 November 2016 10:05:28PM xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017 (==) Using system config directory "/usr/share/X11/xorg.conf.d" pci id for fd 10: 19e5:1711, driver (null) EGL_MESA_drm_image required. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48] (EE) (EE) Segmentation fault at address 0xa0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. Aborted (core dumped) ubuntu@ubuntu:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)
Hi,
On further investigation it turns out that one large difference between
my x86 system and the arm64 system is they way the vga arbiter is
operating in the kernel. This means that the vga card isn't labelled as
the "boot vga" card, which affects how it's picked up by X.
On the HiSilicon board, I'm seeing:
[0.815343] pci 0007:a1:00.0: vgaarb: VGA device added:
decodes=io+mem,owns=none,locks=none
[0.815355] pci 0007:a1:00.0: vgaarb: bridge control possible
[0.815360] vgaarb: loaded
On an x86 vm I'm seeing:
[0.390696] vgaarb: setting as boot device: PCI::00:02.0
[0.391245] vgaarb: device added:
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
[0.393421] vgaarb: loaded
[0.393811] vgaarb: bridge control possible :00:02.0
(The difference in the format is due to different kernel versions)
Looking at the kernel source, it looks like the owns= section is getting
blanked because of the bridge that the VGA card is sitting behind.
>From drivers/gpu/vga/vgaarb.c:
/* Mark that we "own" resources based on our enables, we will
* clear that below if the bridge isn't forwarding
*/
pci_read_config_word(pdev, PCI_COMMAND, );
if (cmd & PCI_COMMAND_IO)
vgadev->owns |= VGA_RSRC_LEGACY_IO;
if (cmd & PCI_COMMAND_MEMORY)
vgadev->owns |= VGA_RSRC_LEGACY_MEM;
/* Check if VGA cycles can get down to us */
bus = pdev->bus;
while (bus) {
bridge = bus->self;
if (bridge) {
u16 l;
pci_read_config_word(bridge, PCI_BRIDGE_CONTROL, );
if (!(l & PCI_BRIDGE_CTL_VGA)) {
vgadev->owns = 0;
break;
}
}
bus = bus->parent;
}
/* Deal with VGA default device. Use first enabled one
* by default if arch doesn't have it's own hook
*/
if (vga_default == NULL &&
((vgadev->owns & VGA_RSRC_LEGACY_MASK) == VGA_RSRC_LEGACY_MASK)) {
vgaarb_info(>dev, "setting as boot VGA device\n");
vga_set_default_device(pdev);
Perhaps X should be be picking up the card through PCI probing on arm64
rather than platform probing which seems to rely a bit on boot VGA
devices. I will check this. But first I just wanted to check the PCI
topology: is the card behind any unusual bridges or switches?
I can write some kernel code next week to find out specifically why this
isn't being picked up, but I thought I'd check for HW quirks first.
--
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/1691991
Title:
Xorg Segmentation fault on Hisilicon D05 board (arm64)
Status in xorg package in Ubuntu:
New
Bug description:
ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg
[sudo] password for ubuntu:
X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
Current Operating System: Linux ubuntu 4.10.0-20.22-generic
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug
earlycon=pl011,mmio,0x602B console=tty0
Build Date: 02 November 2016 10:05:28PM
xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see
http://www.ubuntu.com/support)
Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
pci id for fd 10: 19e5:1711, driver (null)
EGL_MESA_drm_image required.
(EE)
(EE) Backtrace:
(EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
(EE)
(EE) Segmentation fault at address 0xa0
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional
information.
(EE)
(EE) Server terminated with error (1). Closing log file.
Aborted (core dumped)
ubuntu@ubuntu:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe :
