[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Ubuntu 22.04 LTS: apt install ./tcping_amd64.deb N: Download is performed unsandboxed as root as file '/root/tcping_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) -- 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 aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: Confirmed Status in synaptic source package in Xenial: Confirmed Status in update-notifier source package in Xenial: Fix Released Status in apt source package in Hirsute: Fix Released Status in aptitude source package in Hirsute: Fix Released Status in synaptic source package in Hirsute: Won't Fix Status in update-notifier source package in Hirsute: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is only a regression on a cosmetic level. Previous versions of apt did not have any sandboxing whatsoever, so this means apt reverted back to that old behavior. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- 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 2037509] [NEW] Gnome/Ubuntu desktop wayland
Public bug reported: Good day, I hasten to inform you about a problem that has not left your distribution for several releases in a row. When the Wayland secant is launched, some window elements for control are not active. In particular, the open new tab/settings expand/collapse buttons in browsers and ower applications do not work. Snap and Deb are equally susceptible to this problem. The solution is to login to X11 and immediately log out and log into Wayland again. In the current builds of the Minotaur, the problem appeared quite recently, with the release of the public beta; in the builds for developers, this problem did not occur. I will be very upset if this problem goes into release. Please correct it if possible. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:14:33 2023 InstallationDate: Installed on 2023-06-21 (98 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230620) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2037509 Title: Gnome/Ubuntu desktop wayland Status in ubuntu-meta package in Ubuntu: New Bug description: Good day, I hasten to inform you about a problem that has not left your distribution for several releases in a row. When the Wayland secant is launched, some window elements for control are not active. In particular, the open new tab/settings expand/collapse buttons in browsers and ower applications do not work. Snap and Deb are equally susceptible to this problem. The solution is to login to X11 and immediately log out and log into Wayland again. In the current builds of the Minotaur, the problem appeared quite recently, with the release of the public beta; in the builds for developers, this problem did not occur. I will be very upset if this problem goes into release. Please correct it if possible. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:14:33 2023 InstallationDate: Installed on 2023-06-21 (98 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230620) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037509/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Is it safe to downgrade from systemd 237-3ubuntu10.54 to the previous 237-3ubuntu10.50? -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1975467] [NEW] package passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] failed to install/upgrade: unable to make backup link of './usr/bin/passwd' befor
Public bug reported: While updating Ubuntu 20.04.4 TLS I'm getting an error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 23 11:45:21 2022 DuplicateSignature: package:passwd:1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] Unpacking passwd (1:4.8.1-1ubuntu5.20.04.2) over (1:4.8.1-1ubuntu5.20.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-43VTuR/5-passwd_1%3a4.8.1-1ubuntu5.20.04.2_amd64.deb (--unpack): unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted ErrorMessage: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted InstallationDate: Installed on 2021-05-24 (363 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: shadow Title: package passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] failed to install/upgrade: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1975467 Title: package passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] failed to install/upgrade: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted Status in shadow package in Ubuntu: New Bug description: While updating Ubuntu 20.04.4 TLS I'm getting an error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 23 11:45:21 2022 DuplicateSignature: package:passwd:1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] Unpacking passwd (1:4.8.1-1ubuntu5.20.04.2) over (1:4.8.1-1ubuntu5.20.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-43VTuR/5-passwd_1%3a4.8.1-1ubuntu5.20.04.2_amd64.deb (--unpack): unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted ErrorMessage: unable to make backup link of './usr/bin/passwd' before installing new version: Operation not permitted InstallationDate: Installed on 2021-05-24 (363 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: shadow Title: package passwd 1:4.8.1-1ubuntu5.20.04 [modified: usr/bin/passwd usr/sbin/userdel] failed to install/upgrade: unable to make backup link of './usr/bin/passwd' before installing new version: 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/shadow/+bug/1975467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
I just installed the -proposed package and still no dice. Could someone post (here or elsewhere) a instructions for getting this working from scratch as of today? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1953721] [NEW] package linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
Public bug reported: _( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.8.0-59-generic:amd64: Remove linux-hwe-5.8-headers-5.8.0-59:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 10:42:13 2021 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2020-07-09 (517 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: Error: command ['readlink', '-f', "ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. , Error: [Errno 2] Нет такого файла или каталога: 'Error: command [\'readlink\', \'-f\', "ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n', unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1953721 Title: package linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным Status in initramfs-tools package in Ubuntu: New Bug description: _( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.8.0-59-generic:amd64: Remove linux-hwe-5.8-headers-5.8.0-59:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 10:42:13 2021 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2020-07-09 (517 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: Error: command ['readlink', '-f', "ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. , Error: [Errno 2] Нет такого файла или каталога: 'Error: command [\'readlink\', \'-f\', "ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n', unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным 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/1953721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1953722] [NEW] package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
Public bug reported: -( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.8.0-59-generic:amd64: Remove linux-hwe-5.8-headers-5.8.0-59:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 10:42:13 2021 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2020-07-09 (517 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: Error: command ['readlink', '-f', "ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. , Error: [Errno 2] Нет такого файла или каталога: 'Error: command [\'readlink\', \'-f\', "ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n', unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1953722 Title: package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным Status in initramfs-tools package in Ubuntu: New Bug description: -( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.8.0-59-generic:amd64: Remove linux-hwe-5.8-headers-5.8.0-59:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 10:42:13 2021 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2020-07-09 (517 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: Error: command ['readlink', '-f', "ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. , Error: [Errno 2] Нет такого файла или каталога: 'Error: command [\'readlink\', \'-f\', "ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n', unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным 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/1953722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926084] Re: [hirsute] Bluetooth speakers reconnect randomly
Issue occurs in impish as well. -- 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/1926084 Title: [hirsute] Bluetooth speakers reconnect randomly Status in bluez package in Ubuntu: Confirmed Bug description: Bluetooth speakers reconnect randomly. The onlt workaround that seems to work is to remove speakers from paired devies, restart buetooth service and connect them once again. Once these stepss are performed connection become stable until reboot or hibernation. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Apr 25 17:22:11 2021 InstallationDate: Installed on 2021-04-13 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:AF:28:F7:A9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:2239397 acl:225 sco:0 events:318945 errors:0 TX bytes:207283666 acl:315238 sco:0 commands:3564 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942883] [NEW] dont work laptop screen on intel uhd 620
Public bug reported: dont work laptop screen on intel uhd 620 driver big screen on connected by hdmi work correct ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Sep 7 14:30:54 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8538] InstallationDate: Installed on 2021-08-18 (19 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ProBook 450 G6 ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=08563b86-ae87-4e89-a3a7-9da18c4c8ca9 ro xdg.force_integrated=1 modprobe.blacklist=nouveau SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2020 dmi.bios.release: 14.1 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.14.01 dmi.board.name: 8538 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2D.00 dmi.chassis.asset.tag: 5CD944621W dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 81.45 dmi.modalias: dmi:bvnHP:bvrR71Ver.01.14.01:bd10/19/2020:br14.1:efr81.45:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2D.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G6 dmi.product.sku: 5PQ05EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107+git2109030500.d201a4~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.3~git2109070600.27f2c9~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 21.3~git2109070600.27f2c9~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1942883 Title: dont work laptop screen on intel uhd 620 Status in xorg package in Ubuntu: New Bug description: dont work laptop screen on intel uhd 620 driver big screen on connected by hdmi work correct ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Sep 7 14:30:54 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8538] InstallationDate: Installed on 2021-08-18 (19 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ProBook 450 G6 ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=08563b86-ae87-4e89-a3a7-9da18c4c8ca9 ro xdg.force_integrated=1 modprobe.blacklist=nouveau SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2020 dmi.bios.release: 14.1 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.14.01 dmi.board.name: 8538 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2D.00 dmi.chassis.asset.tag: 5CD944621W dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 81.45 dmi.modalias: dmi:bvnHP:bvrR71Ver.01.14.01:bd10/19/2020:br14.1:efr81.45:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2D.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G6 dmi.product.sku: 5PQ05EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107+git2109030500.d201a4~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.3~git2109070600.27f2c
[Touch-packages] [Bug 1904213] Re: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
Confirming, that workaround from #4 also fixes that issue in Ubuntu 20.04.2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1904213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926084] [NEW] Bluetooth speakers reconnect randomly
Public bug reported: Bluetooth speakers reconnect randomly. The onlt workaround that seems to work is to remove speakers from paired devies, restart buetooth service and connect them once again. Once these stepss are performed connection become stable until reboot or hibernation. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Apr 25 17:22:11 2021 InstallationDate: Installed on 2021-04-13 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 44:AF:28:F7:A9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:2239397 acl:225 sco:0 events:318945 errors:0 TX bytes:207283666 acl:315238 sco:0 commands:3564 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1926084 Title: Bluetooth speakers reconnect randomly Status in bluez package in Ubuntu: New Bug description: Bluetooth speakers reconnect randomly. The onlt workaround that seems to work is to remove speakers from paired devies, restart buetooth service and connect them once again. Once these stepss are performed connection become stable until reboot or hibernation. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Apr 25 17:22:11 2021 InstallationDate: Installed on 2021-04-13 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5
[Touch-packages] [Bug 1904213] Re: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
I have the same issue with that laptop using Fedora 33: https://bugzilla.redhat.com/show_bug.cgi?id=1934754 Found temporary solution here: https://github.com/thesofproject/linux/issues/2795 ** Bug watch added: github.com/thesofproject/linux/issues #2795 https://github.com/thesofproject/linux/issues/2795 ** Also affects: sound-2.6 via https://github.com/thesofproject/linux/issues/2795 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1934754 https://bugzilla.redhat.com/show_bug.cgi?id=1934754 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] Status in sound-2.6 (alsa-kernel): Unknown Status in alsa-driver package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1904213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916722] [NEW] Pulseaudio fails to start after reboot if home partition is encrypted
Public bug reported: It seems that with Ubuntu 20.10, Pulseaudio now tries to start as main user too early, before user logs in and the home partition is decrypted. Probably pulseaudio should not start as main user before login of this user. Starting pulseaudio manually after login works. grep 'pulseaudio' /var/log/syslog Feb 24 10:52:31 aziber systemd[1451]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. Feb 24 10:52:31 aziber dbus-daemon[972]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=123 pid=1497 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Feb 24 10:52:38 aziber systemd[3631]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. Feb 24 10:52:38 aziber pulseaudio[3690]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 1. Feb 24 10:52:38 aziber pulseaudio[3899]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 2. Feb 24 10:52:39 aziber pulseaudio[4128]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 3. Feb 24 10:52:39 aziber pulseaudio[4311]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 4. Feb 24 10:52:39 aziber pulseaudio[4493]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Start request repeated too quickly. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.socket: Failed with result 'service-start-limit-hit'. Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: Connection failure: Connection refused Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: pa_context_connect() failed: Connection refused Feb 24 10:52:42 aziber gnome-session[5663]: gnome-session-binary[5663]: WARNING: App 'pulseaudio.desktop' exited with code 1 Feb 24 10:52:42 aziber gnome-session-binary[5663]: WARNING: App 'pulseaudio.desktop' exited with code 1 Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed to add PIDs to scope's control group: No such process Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed with result 'resources'. Feb 24 10:52:45 aziber systemd[1432]: pulseaudio.service: Succeeded. Feb 24 10:52:55 aziber systemd[1432]: pulseaudio.socket: Succeeded. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/s
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Until the new images are available: Just update apt of the live system before installing and the installation should work. For those who don't know how to: Start Live-System/ISO-Image with internet connected Choose "Try Ubuntu" Open "Terminal" Type: sudo apt-get update sudo apt-get install apt Then start installation of Ubuntu with your favourite options - even with third party drivers. -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//
[Touch-packages] [Bug 1904213] [NEW] Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
Public bug reported: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] Status in alsa-driver package in Ubuntu: New Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1904213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
ubuntu 20.04, kernel Linux 5.4.0-52-generic samsung galaxy buds, cant switch to hsp/hfp thinkpad x1 carbon. laptop has intel BT 8087:0a2b, /lib/firmware/intel/ibt-12-16.sfi is used. tried to get "new" from here https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/intel but it has same fw file as i have on my system -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 I have the same issue. My Bose 700 connect and have sound output for A2DP, but nothing when trying to select HSP/HFP. Laptop: HP Spectre X360 2019 OS: Ubuntu 20.04.01 LTS Kernel: 5.4.0-47-generic Headset: Bose 700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
@Bob Lawrence (pilotbob42) So i'm back with a better workaround. First I enabled the intel driver like I specified in my first point.(this removes the tearing) Then I used your workaround, but this was causing the other inputs to error at startup so I on some forum that adding a command at startup applications is a better solution. So i added:"xrandr --output HDMI-3 --mode 1920x1080 --scale 0.x0." as a new command in Startup Applications. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
@Bob Lawrence (pilotbob42) I don't have .xprofile but i created it my home folder like you suggested and added the text, mine was HDMI3. Unfortunately it doesn't seem to do anything. I also observed that changing the DPI solves the issue on most distros I tried. But i don't like any other DPI than 100%. Also in regard to the workaround posted by me changing to DRI 2, mostly solves the issue on gnome on POP OS, still a few mouse trails but it is bearable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
I found a fix for the issues on kde, as I am running kubuntu 20.04, all credit goes to the original poster. My contribution was only to change the DRI setting to 3 not "false" because this caused slowdown. https://forum.manjaro.org/t/how-i-fixed-my-tearing-and-graphical-issues- completely-manjaro-kde/108390 ** Attachment added: "20-intel.conf" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+attachment/5380581/+files/20-intel.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Had a similar problem with Lenovo S740 (Ubuntu 18.04, 19.10 and 20.04). Tried different combinations in alsa-base.conf, hda-jack-retask - nothing worked. And then surprisingly this thread helped (see https://gist.github.com/hamidzr/dd81e429dc86f4327ded7a2030e7d7d9#gistcomment-3315737 ). What I've done is I appended next two lines to /etc/pulse/default.pa: # /etc/pulse/default.pa load-module module-alsa-sink device=hw:0,0 channels=2 # note that I used 2 here load-module module-alsa-source device=hw:0,6 channels=2 ``` For those of you having problems in Ubuntu 20.04 with Realtek ALC285 this could be a solution. ❯ uname -a Linux anton-Lenovo-Yoga-S740-14IIL 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Now internal microphone records audio, please try to see if it helps you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
SEARCHING IS NOT NAVIGATING, please. Besides the debate on whether the option to disable search when starting to type should exist (I think it should), #144 has raised quite an important side effect: searching should not make it look like files are deleted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6
Here is a solution https://forums.openvpn.net/viewtopic.php?t=23979#p79185 -- 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/1866611 Title: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6 Status in openssl package in Ubuntu: Confirmed Bug description: After upgrading openssl on my Focal-install this morning (upgrade openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log), my OpenVPN tunnel refuses to connect to our corporate VPN (from /var/log/syslog): corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, emailAddress=XX corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed I'm told we're running a SHA1-signed CA, which we're guessing has been deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog for -2ubuntu4 mentions importing some upstream changes, but isn't more specific than that: https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1 .1d-2ubuntu4/changelog As a work-around, the internet suggests two work-arounds (neither of which has worked for me): 1) Adding the following to /etc/defaults/openssl: OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0" 2) Adding the following to /etc/ssl/openssl.conf: CipherString= :@SECLEVEL=1 I also tried rolling back the package, but the old version doesn't seem to be available: $ sudo apt install openssl=1.1.1d-2ubuntu3 ... E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found I am no SSL-expert and would appreciate any pointers to get around this. (Our network-dept. does not have the bandwidth to roll over our CA on short notice, so I will need some other way to move ahead). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6
I have the same issue with SecurityKISS VPN. -- 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/1866611 Title: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6 Status in openssl package in Ubuntu: Confirmed Bug description: After upgrading openssl on my Focal-install this morning (upgrade openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log), my OpenVPN tunnel refuses to connect to our corporate VPN (from /var/log/syslog): corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, emailAddress=XX corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed I'm told we're running a SHA1-signed CA, which we're guessing has been deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog for -2ubuntu4 mentions importing some upstream changes, but isn't more specific than that: https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1 .1d-2ubuntu4/changelog As a work-around, the internet suggests two work-arounds (neither of which has worked for me): 1) Adding the following to /etc/defaults/openssl: OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0" 2) Adding the following to /etc/ssl/openssl.conf: CipherString= :@SECLEVEL=1 I also tried rolling back the package, but the old version doesn't seem to be available: $ sudo apt install openssl=1.1.1d-2ubuntu3 ... E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found I am no SSL-expert and would appreciate any pointers to get around this. (Our network-dept. does not have the bandwidth to roll over our CA on short notice, so I will need some other way to move ahead). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1870843] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()
Hi Sebastien and team, The bug is not reproducible. It always appeared just after login, after loading the desktop and without having started any application. El dom., 5 abr. 2020 a las 11:30, Sebastien Bacher () escribió: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please answer these questions: > * Is this reproducible? > * If so, what specific steps should we take to recreate this bug? > > This will help us to find and resolve the problem. > > ** Changed in: ibus (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1870843 > > Title: > ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync() > > Status in ibus package in Ubuntu: > Incomplete > > Bug description: > Description: Ubuntu Focal Fossa (development branch) > Release: 20.04 > > ProblemType: Crash > DistroRelease: Ubuntu 20.04 > Package: ibus 1.5.22-2ubuntu2 > ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 > Uname: Linux 5.4.0-18-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu22 > Architecture: amd64 > CrashCounter: 1 > CurrentDesktop: ubuntu:GNOME > Date: Sat Apr 4 13:03:51 2020 > ExecutablePath: /usr/libexec/ibus-ui-gtk3 > ProcCmdline: /usr/libexec/ibus-ui-gtk3 > ProcEnviron: >LANGUAGE=es_AR:es >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=es_AR.UTF-8 >SHELL=/bin/bash > SegvAnalysis: >Segfault happened at: 0x7fee4f4e8f5b : orq > $0x0,(%rsp) >PC (0x7fee4f4e8f5b) ok >source "$0x0" ok >destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region > (needed writable region)! >Stack memory exhausted (SP below stack segment) > SegvReason: writing unknown VMA > Signal: 11 > SourcePackage: ibus > StacktraceTop: >?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 >ibus_bus_get_engines_by_names () from > /lib/x86_64-linux-gnu/libibus-1.0.so.5 >?? () >?? () >g_cclosure_marshal_VOID__STRINGv () from > /lib/x86_64-linux-gnu/libgobject-2.0.so.0 > Title: ibus-ui-gtk3 crashed with SIGSEGV in > ibus_bus_get_engines_by_names() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo > separator: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1870843/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1870843 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync() Status in ibus package in Ubuntu: Incomplete Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 13:03:51 2020 ExecutablePath: /usr/libexec/ibus-ui-gtk3 ProcCmdline: /usr/libexec/ibus-ui-gtk3 ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fee4f4e8f5b : orq $0x0,(%rsp) PC (0x7fee4f4e8f5b) ok source "$0x0" ok destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () ?? () g_cclosure_marshal_VOID__STRINGv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1870843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782263] Re: NetworkManager authentication problems caused by polkit
To disable warning (and authentication) you can add: [main] auth-polkit=false To the /etc/NetworkManager/NetworkManager.conf (if you already have [main] section, just add value to it) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1782263 Title: NetworkManager authentication problems caused by polkit Status in network-manager package in Ubuntu: New Status in policykit package in Ubuntu: Confirmed Bug description: The following message, or variations upon it, appears dozens of times, one immediately after the other, in my system log. [1531853719.4893] error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: Authorization check failed: Failed to open file “/proc/10006/status”: No such file or directory The problem began when I did the following package update. apt-cache policy policykit-1 policykit-1: Installed: 0.105-20 Candidate: 0.105-20ubuntu0.18.04.1 Version table: 0.105-20ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 0.105-20 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status When (via the TimeShift backup program) I restored my system to a state before the package was installed, the problem stopped. When I did have the problem, some networks would have trouble connecting. I asked about the issue on Mint's IRC channel, and no solution - save reinstalling - emerged; but by that point I had not traced the problem to policykit. Mint 19 x64 Cinnamon. I report this problem here because it seems to me - I might be wrong - an Ubuntu rather than Mint problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1782263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800836] Re: systemd-networkd doesn't process IPv6 RA properly
We are also affected by this issue. networkd does not expire routes which causes issues with active-passive router configurations. For me it looks like the issue is fixed in this pull request: https://github.com/systemd/systemd/pull/3242 -- 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/1800836 Title: systemd-networkd doesn't process IPv6 RA properly Status in systemd package in Ubuntu: Confirmed Bug description: The gateways/firewalls in our DC are highly available and when there is a failover their IPv6 VIP (fe80::1) moves from the master to the backup one. We found that only our Bionic VMs behind those gateways had issues after a failover. Those Bionic VMs were all running systemd-networkd (from netplan) and before the failover they had: $ ip -6 route ... default via fe80::1 dev eth0 proto ra metric 1024 pref medium But after a failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 And after another failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 nexthop via fe80::210:18ff:fe77:b558 dev eth0 weight 1 This is problematic as those then use fe80::210:18ff:fe77:b558%$IFACE as their default gateway even when this gateway is unavailable: $ ip -6 route get :: :: from :: via fe80::210:18ff:fe77:b558 dev eth0 proto ra src fe80::a800:ff:fe51:8c37 metric 1024 pref medium We concluded it was a systemd-networkd bug after checking that the following combinations were NOT affected: 1) Xenial+4.4 kernel 2) Xenial+4.15 kernel 3) Bionic+ifupdown Additional information: $ apt-cache policy systemd systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 31 08:47:28 2018 Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=43b7ee2e-2ab1-4505-8e0b-d9fe0563a034 ro console=ttyS0 net.ifnames=0 vsyscall=none kaslr nmi_watchdog=0 possible_cpus=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816525] [NEW] package initramfs-tools 0.131ubuntu15.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: Don't have ProblemType: Package DistroRelease: Ubuntu 18.10 Package: initramfs-tools 0.131ubuntu15.1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 AptOrdering: initramfs-tools:amd64: Install initramfs-tools-core:amd64: Install initramfs-tools-bin:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Feb 19 09:44:10 2019 Df: Dmesg: ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2019-02-12 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.131ubuntu15.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- 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/1816525 Title: package initramfs-tools 0.131ubuntu15.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2 Status in initramfs-tools package in Ubuntu: New Bug description: Don't have ProblemType: Package DistroRelease: Ubuntu 18.10 Package: initramfs-tools 0.131ubuntu15.1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 AptOrdering: initramfs-tools:amd64: Install initramfs-tools-core:amd64: Install initramfs-tools-bin:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Feb 19 09:44:10 2019 Df: Dmesg: ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2019-02-12 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.131ubuntu15.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 2 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/1816525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812353] Re: content injection in http method (CVE-2019-3462)
Or is there anything going to happen wrt to https/TLS? I, personally, are not convinced of doing this... In this specific case, and rogue mirror could have still exploited the hole, and I'd assume there is nothing done to check the trustworthiness of mirror operators (there's no real way to do so). Also, the X.509 trust model is inherently broken. 150 root CAs alone in the mozilla bundle (many of them which cannot be trusted per se by any sane person) and even more sub CAs... all of which can issue literally any certificate. Using TLS would IMO only help (a tiny bit) if Debian (respectively the derivates) would operate their own CA (and only accept that for services they offer, like mirrors, BTS, gitlab, etc.). -- 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/1812353 Title: content injection in http method (CVE-2019-3462) Status in apt package in Ubuntu: Fix Released Status in apt source package in Precise: Fix Released Status in apt source package in Trusty: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Status in apt source package in Disco: Fix Released Bug description: apt, starting with version 0.8.15, decodes target URLs of redirects, but does not check them for newlines, allowing MiTM attackers (or repository mirrors) to inject arbitrary headers into the result returned to the main process. If the URL embeds hashes of the supposed file, it can thus be used to disable any validation of the downloaded file, as the fake hashes will be prepended in front of the right hashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812353] Re: content injection in http method (CVE-2019-3462)
Hmm that's pretty bad then (which is not to be read as blaming you or anyone else here). Are there going to be any… "consequences"? I mean trying to find out whether systems have been compromised is probably impossible... an attacker could have used this long ago to basically do everything, from silently taking over end user systems to secretly injecting code in development repos. Sure one can argue that this might have been noticed - but it also might have been not. But is there a chance to e.g. get full audits of apt done by security experts? I'd assume that aptitude was also fully affected by this, right? -- 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/1812353 Title: content injection in http method (CVE-2019-3462) Status in apt package in Ubuntu: Fix Released Status in apt source package in Precise: Fix Released Status in apt source package in Trusty: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Status in apt source package in Disco: Fix Released Bug description: apt, starting with version 0.8.15, decodes target URLs of redirects, but does not check them for newlines, allowing MiTM attackers (or repository mirrors) to inject arbitrary headers into the result returned to the main process. If the URL embeds hashes of the supposed file, it can thus be used to disable any validation of the downloaded file, as the fake hashes will be prepended in front of the right hashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812353] Re: content injection in http method (CVE-2019-3462)
Is there any more detailed evaluation of this hole? It reads absolutely catastrophic, like that secure APT is basically broken since 2011,… and if anyone has found that issue before (which one must assume in the worst case) any code could have been rather easily introduced in any Debian based system, from end users to DDs. -- 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/1812353 Title: content injection in http method (CVE-2019-3462) Status in apt package in Ubuntu: In Progress Status in apt source package in Precise: Fix Released Status in apt source package in Trusty: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Status in apt source package in Disco: In Progress Bug description: apt, starting with version 0.8.15, decodes target URLs of redirects, but does not check them for newlines, allowing MiTM attackers (or repository mirrors) to inject arbitrary headers into the result returned to the main process. If the URL embeds hashes of the supposed file, it can thus be used to disable any validation of the downloaded file, as the fake hashes will be prepended in front of the right hashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797040] Re: QtWebkit - missing doxygen tags file
Hi, Dmitry. The patch is pushed to upstream: https://github.com/annulen/webkit/commit/efa87bd9862e5c7b769efa137bf39d2b0efca264 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1797040 Title: QtWebkit - missing doxygen tags file Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: Current version of qtwebkit5-doc-html package doesn't contains qtwebkit.tags file which leads to incomplete doxygen documentation generation for external projects (kdewebkit for example). This can fixed with small patch (see attachment). I test it on my 18.04 system - all works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1797040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797040] Re: QtWebkit - missing doxygen tags file
** Patch added: "git patch to fix the problem" https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1797040/+attachment/5199390/+files/qdoc.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1797040 Title: QtWebkit - missing doxygen tags file Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: Current version of qtwebkit5-doc-html package doesn't contains qtwebkit.tags file which leads to incomplete doxygen documentation generation for external projects (kdewebkit for example). This can fixed with small patch (see attachment). I test it on my 18.04 system - all works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1797040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797040] [NEW] QtWebkit - missing doxygen tags file
Public bug reported: Current version of qtwebkit5-doc-html package doesn't contains qtwebkit.tags file which leads to incomplete doxygen documentation generation for external projects (kdewebkit for example). This can fixed with small patch (see attachment). I test it on my 18.04 system - all works as expected. ** Affects: qtwebkit-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1797040 Title: QtWebkit - missing doxygen tags file Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: Current version of qtwebkit5-doc-html package doesn't contains qtwebkit.tags file which leads to incomplete doxygen documentation generation for external projects (kdewebkit for example). This can fixed with small patch (see attachment). I test it on my 18.04 system - all works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1797040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1288182]
Is there any hope to fix it properly? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: Unknown Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
@egor-tensin you are awesome! I think there might be a few related problems (like https://github.com/systemd/systemd/issues/7182) but this seems to actually work. I actually saw this bug but didn't click that your fix would work until having wasted a huge amount of time. Some one from Ubuntu should DEFINITELY put this in the NetworkManager FAQ. And it should obviously be a GUI option - it is rather shameful that we still have to generate our configs with code because the GUI is so broken... ** Bug watch added: github.com/systemd/systemd/issues #7182 https://github.com/systemd/systemd/issues/7182 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778070] [NEW] [N501VW, Realtek ALC668, Black Headphone Out, Right] No sound at all
Public bug reported: Out of a sudden the sound off my headphones stopped working. It works when I remove the headphones. Here's the also output: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Thu Jun 21 14:08:31 UTC 2018 !!Linux Distribution !!-- Ubuntu 18.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: ASUSTeK COMPUTER INC. Product Name: N501VW Product Version: 1.0 Firmware Version: N501VW.301 Board Vendor: ASUSTeK COMPUTER INC. Board Name:N501VW !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/ATK3001:00/status 15 /sys/bus/acpi/devices/ATK4002:00/status 15 /sys/bus/acpi/devices/FTE1001:00/status 15 /sys/bus/acpi/devices/INT33A1:00/status 15 /sys/bus/acpi/devices/INT3400:00/status 15 /sys/bus/acpi/devices/INT3403:00/status 15 /sys/bus/acpi/devices/INT3403:01/status 15 /sys/bus/acpi/devices/INT3403:02/status 15 /sys/bus/acpi/devices/INT3403:03/status 15 /sys/bus/acpi/devices/INT3F0D:00/status 15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/LNXPOWER:01/status 1 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/MSFT0101:00/status 15 /sys/bus/acpi/devices/PNP0103:00/status 15 /sys/bus/acpi/devices/PNP0C02:01/status 15 /sys/bus/acpi/devices/PNP0C02:04/status 3 /sys/bus/acpi/devices/PNP0C02:06/status 3 /sys/bus/acpi/devices/PNP0C04:00/status 31 /sys/bus/acpi/devices/PNP0C0A:00/status 31 /sys/bus/acpi/devices/PNP0C0F:00/status 9 /sys/bus/acpi/devices/PNP0C0F:01/status 9 /sys/bus/acpi/devices/PNP0C0F:02/status 9 /sys/bus/acpi/devices/PNP0C0F:03/status 9 /sys/bus/acpi/devices/PNP0C0F:04/status 9 /sys/bus/acpi/devices/PNP0C0F:05/status 9 /sys/bus/acpi/devices/PNP0C0F:06/status 9 /sys/bus/acpi/devices/PNP0C0F:07/status 9 /sys/bus/acpi/devices/device:11/status 15 /sys/bus/acpi/devices/device:67/status 15 /sys/bus/acpi/devices/device:7a/status 11 !!Kernel Information !!-- Kernel release:4.15.0-23-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k4.15.0-23-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdd428000 irq 136 !!PCI Soundcards installed in the system !!-- 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0403: 8086:a170 (rev 31) Subsystem: 1043:1080 !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 jackpoll_ms : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
[Touch-packages] [Bug 1753271] Re: intermittent static during audio playback
Looks like it may have been hardware related - as part of further
debugging both the usb speaker was completely unplugged, and the pc and
monitor were powered off at the wall - after that playback seems to be
fine
** Changed in: pulseaudio (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1753271
Title:
intermittent static during audio playback
Status in pulseaudio package in Ubuntu:
Invalid
Bug description:
Recently (since yesterday), during audio playback ("Videos" app,
Chrome (google music)) the audio will go from perfectly clear to
complete static white noise. This usually starts about 5 seconds into
playback and can last from about 10 to 40 seconds before returning to
normal.
Playing with volume levels in the ubuntu audio mixer it sounds like
the audio has been auto-amplified and that is clipping and causing
static, but that's just a guess.
I've tried playing with a few pulse options to change things but can't
find anything which makes it any better.
I'm using analogue output on a usb speaker (dell soundbar), and have
not had problems since buying it or the rest of the pc, this seems to
have occurred fairly recently.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.8
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar 4 15:56:02 2018
InstallationDate: Installed on 2012-11-17 (1933 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0211
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0211:bd04/28/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1753271/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753271] [NEW] intermittent static during audio playback
Public bug reported:
Recently (since yesterday), during audio playback ("Videos" app, Chrome
(google music)) the audio will go from perfectly clear to complete
static white noise. This usually starts about 5 seconds into playback
and can last from about 10 to 40 seconds before returning to normal.
Playing with volume levels in the ubuntu audio mixer it sounds like the
audio has been auto-amplified and that is clipping and causing static,
but that's just a guess.
I've tried playing with a few pulse options to change things but can't
find anything which makes it any better.
I'm using analogue output on a usb speaker (dell soundbar), and have not
had problems since buying it or the rest of the pc, this seems to have
occurred fairly recently.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.8
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar 4 15:56:02 2018
InstallationDate: Installed on 2012-11-17 (1933 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0211
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0211:bd04/28/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
** Attachment added: "pulseaudio - --log-time=1"
https://bugs.launchpad.net/bugs/1753271/+attachment/5069066/+files/pulseverbose.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1753271
Title:
intermittent static during audio playback
Status in pulseaudio package in Ubuntu:
New
Bug description:
Recently (since yesterday), during audio playback ("Videos" app,
Chrome (google music)) the audio will go from perfectly clear to
complete static white noise. This usually starts about 5 seconds into
playback and can last from about 10 to 40 seconds before returning to
normal.
Playing with volume levels in the ubuntu audio mixer it sounds like
the audio has been auto-amplified and that is clipping and causing
static, but that's just a guess.
I've tried playing with a few pulse options to change things but can't
find anything which makes it any better.
I'm using analogue output on a usb speaker (dell soundbar), and have
not had problems since buying it or the rest of the pc, this seems to
have occurred fairly recently.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.8
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar 4 15:56:02 2018
InstallationDate: Installed on 2012-11-17 (1933 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0211
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0211:bd04/28/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1753271/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.laun
[Touch-packages] [Bug 1389813] Re: package grub-common 2.02~beta2-15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects my Ubuntu 17.10 (x86_64 Linux 4.13.0-32-generic) on installing grub-common (2.02~beta3-4ubuntu7.1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to insserv in Ubuntu. https://bugs.launchpad.net/bugs/1389813 Title: package grub-common 2.02~beta2-15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in insserv package in Ubuntu: Confirmed Bug description: just tried to upgrade and got this ProblemType: Package DistroRelease: Ubuntu 14.10 Package: grub-common ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Wed Nov 5 15:38:34 2014 DuplicateSignature: package:grub-common:2.02~beta2-15:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-02-16 (626 days ago) InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=2665a74f-e44f-4589-8554-2c954223116f ro quiet splash vt.handoff=7 SourcePackage: grub2 Title: package grub-common 2.02~beta2-15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-11-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/insserv/+bug/1389813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701726] Re: unattended upgrades removing kerberos and breaking system
Not sure if this is relevant (I don't really understand what it is telling me): unattended-upgrades.log : While building minimal partition: cache has not allowed changes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1701726 Title: unattended upgrades removing kerberos and breaking system Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Ok, so this may not be a bug specifically in unattended-upgrades, but I can't determine where else it would be. Having my server broken by unattended upgrades removing the primary login system (kerberos) once might be considered unlucky, or perhaps a typo - but now that it has happened twice it looks like a bug. The problem seems to be that several krb related packages were removed, along with puppet packages which we use to help maintain the system. The result was all remote logins (ssh/http/smtp/imap/etc) were broken and serial console had to be used to recover the sysem Pulling from logs from today: ```Start-Date: 2017-06-30 15:22:20 Commandline: /usr/bin/unattended-upgrade Upgrade: libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7) Remove: ubuntu-standard:amd64 (1.361), host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6), librarian-puppet:amd64 (2.2.1-2), libapache2-mod-auth-kerb:amd64 (5.4-2.2), krb5-admin-server:amd64 (1.13.2+dfsg-5ubuntu2), krb5-user:amd64 (1.13.2+dfsg-5ubuntu2), libpam-krb5:amd64 (4.7-2), facter:amd64 (2.4.6-1), krb5-kdc:amd64 (1.13.2+dfsg-5ubuntu2), krb5-config:amd64 (2.3), puppet:amd64 (3.8.5-2ubuntu0.1), puppet-common:amd64 (3.8.5-2ubuntu0.1) End-Date: 2017-06-30 15:22:27 Start-Date: 2017-06-30 15:22:32 Commandline: /usr/bin/unattended-upgrade Remove: libaugeas0:amd64 (1.4.0-0ubuntu1), libverto-libevent1:amd64 (0.2.4-2.1ubuntu2), virt-what:amd64 (1.14-1), libkadm5clnt-mit9:amd64 (1.13.2+dfsg-5ubuntu2), javascript-common:amd64 (11), ruby-multipart-post:amd64 (1.2.0-2), ruby2.3:amd64 (2.3.1-2~16.04), ruby-safe-yaml:amd64 (1.0.4-1), rake:amd64 (10.5.0-2), ruby-net-telnet:amd64 (0.1.1-2), ruby-thor:amd64 (0.19.1-2), ruby-librarian:amd64 (0.6.3-1), ruby-highline:amd64 (1.7.2-1), augeas-lenses:amd64 (1.4.0-0ubuntu1), ruby-minitar:amd64 (0.5.4-3), libkdb5-8:amd64 (1.13.2+dfsg-5ubuntu2), libjs-jquery:amd64 (1.11.3+dfsg-4), ruby-json:amd64 (1.8.3-1build4), ruby-augeas:amd64 (1:0.5.0-3build4), ruby-shadow:amd64 (2.4.1-1build4), ruby-minitest:amd64 (5.8.4-2), hiera:amd64 (2.0.0-2), ruby-deep-merge:amd64 (1.0.1+gitf9df6fdb-1), libruby2.3:amd64 (2.3.1-2~16.04), ruby-selinux:amd64 (2.4-3build2), ruby:amd64 (1:2.3.0+1), libgssrpc4:amd64 (1.13.2+dfsg-5ubuntu2), libverto1:amd64 (0.2.4-2.1ubuntu2), ruby-rsync:amd64 (1.0.9-1), ruby-faraday -middleware:amd64 (0.10.0-1), ruby-power-assert:amd64 (0.2.7-1), unzip:amd64 (6.0-20ubuntu1), zip:amd64 (3.0-11), ruby-semantic-puppet:amd64 (0.1.1-1), ruby-rgen:amd64 (0.7.0-2), rubygems-integration:amd64 (1.10), fonts-lato:amd64 (2.0-1), ruby-faraday:amd64 (0.9.2-3), ruby-nokogiri:amd64 (1.6.7.2-3build1), libkadm5srv-mit9:amd64 (1.13.2+dfsg-5ubuntu2), ruby-test-unit:amd64 (3.1.7-2), libyaml-0-2:amd64 (0.1.6-3), ruby-puppet-forge:amd64 (2.1.3-1), ruby-did-you-mean:amd64 (1.0.0-2) End-Date: 2017-06-30 15:22:34 ``` And the pervious time it failed in January this year: ```Start-Date: 2017-01-13 02:35:06 Commandline: /usr/bin/unattended-upgrade Install: host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, automatic) Upgrade: libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.1
[Touch-packages] [Bug 1701726] [NEW] unattended upgrades removing kerberos and breaking system
Public bug reported: Ok, so this may not be a bug specifically in unattended-upgrades, but I can't determine where else it would be. Having my server broken by unattended upgrades removing the primary login system (kerberos) once might be considered unlucky, or perhaps a typo - but now that it has happened twice it looks like a bug. The problem seems to be that several krb related packages were removed, along with puppet packages which we use to help maintain the system. The result was all remote logins (ssh/http/smtp/imap/etc) were broken and serial console had to be used to recover the sysem Pulling from logs from today: ```Start-Date: 2017-06-30 15:22:20 Commandline: /usr/bin/unattended-upgrade Upgrade: libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 1:9.10.3.dfsg.P4-8ubuntu1.7) Remove: ubuntu-standard:amd64 (1.361), host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6), librarian-puppet:amd64 (2.2.1-2), libapache2-mod-auth-kerb:amd64 (5.4-2.2), krb5-admin-server:amd64 (1.13.2+dfsg-5ubuntu2), krb5-user:amd64 (1.13.2+dfsg-5ubuntu2), libpam-krb5:amd64 (4.7-2), facter:amd64 (2.4.6-1), krb5-kdc:amd64 (1.13.2+dfsg-5ubuntu2), krb5-config:amd64 (2.3), puppet:amd64 (3.8.5-2ubuntu0.1), puppet-common:amd64 (3.8.5-2ubuntu0.1) End-Date: 2017-06-30 15:22:27 Start-Date: 2017-06-30 15:22:32 Commandline: /usr/bin/unattended-upgrade Remove: libaugeas0:amd64 (1.4.0-0ubuntu1), libverto-libevent1:amd64 (0.2.4-2.1ubuntu2), virt-what:amd64 (1.14-1), libkadm5clnt-mit9:amd64 (1.13.2+dfsg-5ubuntu2), javascript-common:amd64 (11), ruby-multipart-post:amd64 (1.2.0-2), ruby2.3:amd64 (2.3.1-2~16.04), ruby-safe-yaml:amd64 (1.0.4-1), rake:amd64 (10.5.0-2), ruby-net-telnet:amd64 (0.1.1-2), ruby-thor:amd64 (0.19.1-2), ruby-librarian:amd64 (0.6.3-1), ruby-highline:amd64 (1.7.2-1), augeas-lenses:amd64 (1.4.0-0ubuntu1), ruby-minitar:amd64 (0.5.4-3), libkdb5-8:amd64 (1.13.2+dfsg-5ubuntu2), libjs-jquery:amd64 (1.11.3+dfsg-4), ruby-json:amd64 (1.8.3-1build4), ruby-augeas:amd64 (1:0.5.0-3build4), ruby-shadow:amd64 (2.4.1-1build4), ruby-minitest:amd64 (5.8.4-2), hiera:amd64 (2.0.0-2), ruby-deep-merge:amd64 (1.0.1+gitf9df6fdb-1), libruby2.3:amd64 (2.3.1-2~16.04), ruby-selinux:amd64 (2.4-3build2), ruby:amd64 (1:2.3.0+1), libgssrpc4:amd64 (1.13.2+dfsg-5ubuntu2), libverto1:amd64 (0.2.4-2.1ubuntu2), ruby-rsync:amd64 (1.0.9-1), ruby-faraday-m iddleware:amd64 (0.10.0-1), ruby-power-assert:amd64 (0.2.7-1), unzip:amd64 (6.0-20ubuntu1), zip:amd64 (3.0-11), ruby-semantic-puppet:amd64 (0.1.1-1), ruby-rgen:amd64 (0.7.0-2), rubygems-integration:amd64 (1.10), fonts-lato:amd64 (2.0-1), ruby-faraday:amd64 (0.9.2-3), ruby-nokogiri:amd64 (1.6.7.2-3build1), libkadm5srv-mit9:amd64 (1.13.2+dfsg-5ubuntu2), ruby-test-unit:amd64 (3.1.7-2), libyaml-0-2:amd64 (0.1.6-3), ruby-puppet-forge:amd64 (2.1.3-1), ruby-did-you-mean:amd64 (1.0.0-2) End-Date: 2017-06-30 15:22:34 ``` And the pervious time it failed in January this year: ```Start-Date: 2017-01-13 02:35:06 Commandline: /usr/bin/unattended-upgrade Install: host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, automatic) Upgrade: libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 1:9.10.3.dfsg.P4-8ubuntu1.4) Remove: ubuntu-standard:amd64 (1.361), librarian-puppet:amd64 (2.2.1-2), libapache2-mod-auth-kerb:amd64 (5.4-2.2), krb5-admin-server:amd64 (1.13.2+dfsg-5), krb5-user:amd64 (1.13.2+dfsg-5), libpam-krb5:amd64 (4.7-2), facter:amd64 (2.4.6-1), krb5-kdc:amd64 (1.13.2+dfsg-5), krb5-config:amd64 (2.3), puppet:amd64 (3.8.5-2), puppet-common:amd64 (3.8.5-2) End-Date: 2017-01-13 02:35:13``` After the first failure in January the main kerb
[Touch-packages] [Bug 1698760] [NEW] [Vostro 5568, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all
Public bug reported: Hello! After installing nvidia-375 driver and switching to it no audio devices are shown in Settings/Sound/Output/Play sound through Thank you for your help. I tried this: 1. Depicts audio card in mentioned area but no sound Run the following command into the Terminal: gksudo gedit /etc/modprobe.d/alsa-base.conf Scroll down and add these lines to the end of the file: options snd-hda-intel model=generic 2. No effect at all Run the following command into the Terminal: gksudo gedit /etc/modprobe.d/alsa-base.conf Scroll down and add these lines to the end of the file: #Keep snd-pcsp from being loaded as first soundcard options snd-pcsp index=-2 alias snd-card-0 snd-hda-intel alias sound-slot-0 snd-hda-intel options snd-hda-intel model=dell-m6-amic Then, save , reboot and test sound using headphones and speakers. 3.didn't work sudo apt-get install dkms Then download and install (e.g. with ubuntu software center) the .deb file from the latest vivid alsa build at https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages 4. didn't work sudo apt-add-repository ppa:ubuntu-audio-dev/alsa-daily sudo apt-get update sudo apt-get install oem-audio-hda-daily-dkms ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 2130 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 19 11:14:37 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-03-18 (92 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 2130 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Vostro 5568, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0CWJTV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd02/14/2017:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn0CWJTV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Vostro 5568 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-19T10:23:03.715064 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1698760 Title: [Vostro 5568, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello! After installing nvidia-375 driver and switching to it no audio devices are shown in Settings/Sound/Output/Play sound through Thank you for your help. I tried this: 1. Depicts audio card in mentioned area but no sound Run the following command into the Terminal: gksudo gedit /etc/modprobe.d/alsa-base.conf Scroll down and add these lines to the end of the file: options snd-hda-intel model=generic 2. No effect at all Run the following command into the Terminal: gksudo gedit /etc/modprobe.d/alsa-base.conf Scroll down and add these lines to the end of the file: #Keep snd-pcsp from being loaded as first soundcard options snd-pcsp index=-2 alias snd-card-0 snd-hda-intel alias sound-slot-0 snd-hda-intel options snd-hda-intel model=dell-m6-amic Then, save , reboot and test sound using headphones and speakers. 3.didn't work sudo apt-get install dkms Then download and install (e.g. with ubuntu software center) the .deb file from the latest vivid alsa build at https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages 4. didn't work sudo apt-add-repository ppa:ubuntu-audio-dev/alsa-daily sudo apt-get update sudo apt-get install oem-audio-hda-daily-dkms ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.
[Touch-packages] [Bug 1697185] [NEW] vce init error (-22)
Public bug reported: gaphic display ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: [[0m[0;31m* [0m] A start job is running for Hold until boot process finishes up (22s / no limit) [K Starting WPA supplicant... [[0;32m OK [0m] Started WPA supplicant. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jun 10 21:35:59 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Carrizo [1043:13d0] InstallationDate: Installed on 2017-06-08 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555QG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=1c098302-9a84-4d05-b001-bcb26aff0602 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555QG.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555QG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555QG.304:bd10/18/2016:svnASUSTeKCOMPUTERINC.:pnX555QG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555QG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555QG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jun 10 19:37:12 2017 xserver.configfile: default xserver.errors: AMDGPU(G0): amdgpu_device_initialize failed RADEON(G1): [drm] failed to set drm interface version. RADEON(G1): Kernel modesetting setup failed xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1697185 Title: vce init error (-22) Status in xorg package in Ubuntu: New Bug description: gaphic display ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: [[0m[0;31m* [0m] A start job is running for Hold until boot process finishes up (22s / no limit) [K Starting WPA supplicant... [[0;32m OK [0m] Started WPA supplicant. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jun 10 21:35:59 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Carrizo [1043:13d0] InstallationDate: Installed on 2017-06-08 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b
[Touch-packages] [Bug 1681062] Re: Bluetooth doesn't work after update to 17.04
Some additional info: Bluetooth stop wokring after hibernation, but not always. Only way to get it work again is to completly power off computer and turn it on, reboot doesn't 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/1681062 Title: Bluetooth doesn't work after update to 17.04 Status in bluez package in Ubuntu: New Bug description: After update to 17.04 bluetooth stopped to work. some logs that could be useful: asudak@asudak-Inspiron-One-2330:~$ hciconfig hci0: Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:38 errors:7 asudak@asudak-Inspiron-One-2330:~$ sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sat Apr 8 13:04:36 2017 InstallationDate: Installed on 2013-12-27 (1197 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron One 2330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=13b39ae0-892a-4b5a-ab81-62dba9463c1a ro quiet splash radeon.dpm=1 radeon.runpm=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to zesty on 2017-02-25 (41 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09JR1D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 27147636_1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/13/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn09JR1D:rvrA00:cvnDellInc.:ct13:cvr27147636_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:40 errors:9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1681062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.
I just ran headlong into this same issue on Ubuntu 16.04 LTS using Audacity 2.1.2 on my Dell XPS15. When inserting a jack, I get a dialogue box asking whether I have a headphone, headset, or mic inserted (apparently an external amp with speakers should be considered 'headphones', but that's a different issue). It all works fine, until I start audacity. Also, when closing audacity, it still doesn't work. The same workaround still works: switch the mic source to something else but the headphone. Which IMHO isn't a fix, it is a cludgy, confusing workaround. Judging by the dialogue box, this is really more of an Audacity issue, and not so much alsa-driver, but I thought to mention it here as well. $ dpkg -l audacity ii audacity 2.1.2-1 amd64fast, cross-platform audio editor $ uname -a Linux AF-XPS-15-9550 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1257956 Title: Headphones stopped working after use of Audacity. They are detected, but no sound is produced. Status in alsa-driver package in Ubuntu: Expired Bug description: I'm running 13.10 and the latest GNOME. I've just fresh installed everything and the problem has occured again the same way. I would like to be able to use audacity, but I suppose in the mean time I will just reinstall everything. Steps to reproduce : 1) Install audacity 2.0.3 from official Ubuntu repositories 2) Open Audacity and play something with it 3) That's it : no more headphones sound. - alsa log created with 'alsa-info.sh' (https://wiki.ubuntu.com/Audio/AlsaInfo) : http://paste.ubuntu.com/7131709/ - pulse log when I plug in my headphones, I run a MP3 file with VLC, close VLC then unplug headphones (https://wiki.ubuntu.com/PulseAudio/Log) : http://paste.ubuntu.com/7131713/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1257956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681062] [NEW] Bluetooth doesn't work after update to 17.04
Public bug reported: After update to 17.04 bluetooth stopped to work. some logs that could be useful: asudak@asudak-Inspiron-One-2330:~$ hciconfig hci0: Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:38 errors:7 asudak@asudak-Inspiron-One-2330:~$ sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sat Apr 8 13:04:36 2017 InstallationDate: Installed on 2013-12-27 (1197 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron One 2330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=13b39ae0-892a-4b5a-ab81-62dba9463c1a ro quiet splash radeon.dpm=1 radeon.runpm=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to zesty on 2017-02-25 (41 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09JR1D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 27147636_1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/13/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn09JR1D:rvrA00:cvnDellInc.:ct13:cvr27147636_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:40 errors:9 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1681062 Title: Bluetooth doesn't work after update to 17.04 Status in bluez package in Ubuntu: New Bug description: After update to 17.04 bluetooth stopped to work. some logs that could be useful: asudak@asudak-Inspiron-One-2330:~$ hciconfig hci0: Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:38 errors:7 asudak@asudak-Inspiron-One-2330:~$ sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sat Apr 8 13:04:36 2017 InstallationDate: Installed on 2013-12-27 (1197 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron One 2330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=13b39ae0-892a-4b5a-ab81-62dba9463c1a ro quiet splash radeon.dpm=1 radeon.runpm=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to zesty on 2017-02-25 (41 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09JR1D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 27147636_1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/13/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn09JR1D:rvrA00:cvnDellInc.:ct13:cvr27147636_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:40 errors:9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1681062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669758] Re: Centrino Wireless-N 1000 not working on 16.10
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1669758 Title: Centrino Wireless-N 1000 not working on 16.10 Status in network-manager package in Ubuntu: New Bug description: Summary Wifi is not working on Centrino Wireless-N 1000 not working on 16.10, but does work on windows. Please see following http://paste.ubuntu.com/24101344/ http://askubuntu.com/questions/887257/device-not-ready-wifi-not-working-on-ubuntu-16-10 https://ubuntuforums.org/showthread.php?t=2354116&p=13615105#post13615105 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1669758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561096] Re: STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under Ubuntu 16.04 with added adapters (ibmveth)
This fix creates a race when booting the Ubuntu cloud images unfortunately. The networking scripts race with udev renaming, and every now and then networking fails to come up because cloud-init thinks the device is eth0 but it has been renamed to ibmveth0 in parallel. -- 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/1561096 Title: STC850:Brazos:Br16:Br16p05: Network ethernet port name changed under Ubuntu 16.04 with added adapters (ibmveth) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Bug description: Problem Description : I had installed a fresh install of Ubuntu 16.04 from an ISO image and had set up the partition as directed in the Wiki. I had set up the networking as directed in the WIKI and was able to ping "iofnim" and was able to perform updates and upgrades to the Ubuntu installation without issue. I had checked to make sure (by adding them to an existing AIX partition) that the Mason and Travis_EN adapters to be added were at the latest microcode levels. I assigned them to the partition to be used (br16p05) and then shut down the partition and restarted it to allow the partition to activate the adapters. After the partition restarted, I attempted to build the network using build_net and during its run noticed that the output for the adapters was returning "Network is unreachable". After it completed, I attempted to mount iofnim using the command: "mount iofnim.aus.stglabs.ibm.com:/nim/build_net /root/test -o nolock" which returned a "Failed" error message. I then ran "ifconfig -a" to check on the state of the network which had been working until I rebooted the partition after adding the adapters. I found the unconventional names for both the Mason and the Travis_EN adapters contained in the output from "ifconfig -a" but also found that "eth0", with which I had originally set up the network access for the partition during setupp, was no longer listed but instead "eth1" was now listed and none of the networking data including IP's reported from "ifconfig -a" were set. I consulted with Thiru and he asked I write it up and include a tar file created from /var/log which I have attached to the defect. As an additional note, I was able to go back into /etc/network/interfaces and modify the settings for "eth0" to now be set to "eth1" and after bringing the port down and back up, was able to again ping out and access the network. Please advise. == Comment: #7 - Kevin W. Rudd - 2016-02-11 12:32:49 == Thank you for the additional info. This is not quite the same as the bug I referenced earlier. It is actually a match for bug 122308 . Canonical: This is the same basic issue as originally worked in LP Bug 1437375 The ibmveth based devices are not associated with PCI bus locations, and still rely on the legacy eth? naming. The problem here is that the 75-persistent-net-generator.rules file that used to set up the 70 -persistent-net.rules file for these devices has been removed in 16.04 This creates a name-slip problem for these ibmveth devices depending on the timing of other devices (where another NIC will temporarily be assigned a name like eth0 before it is renamed by udev). Please add back persistent-net-generator support for non-PCI-based devices like this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1561096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641328] Re: Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes mDNS lookups to fail -- breaks network printing
Quite easy to fix. In Ubuntu 16.10 mdns is broken for everyone. Please release the fix! -- 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/1641328 Title: Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes mDNS lookups to fail -- breaks network printing Status in nss-mdns package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: (See also libnss-resolve:amd64 231-9ubuntu1 amd64nss module to resolve names via systemd-resolved) # fresh install of yakkety mtearle@liberation:/etc$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety # package details mtearle@liberation:~$ apt-cache policy libnss-resolve libnss-resolve: Installed: 231-9ubuntu1 Candidate: 231-9ubuntu1 Version table: *** 231-9ubuntu1 500 500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64 Packages 100 /var/lib/dpkg/status 231-9git1 500 500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages mtearle@liberation:~$ apt-cache policy systemd systemd: Installed: 231-9ubuntu1 Candidate: 231-9ubuntu1 Version table: *** 231-9ubuntu1 500 500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64 Packages 100 /var/lib/dpkg/status 231-9git1 500 500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages # attempt to ping VM elsewhere on network with mDNS hostname mtearle@liberation:/etc$ ping bazzavan.local ping: bazzavan.local: Name or service not known # can find both ipv4 and ipv6 addresses for the host mtearle@liberation:/etc$ avahi-resolve-host-name bazzavan.local bazzavan.localfe80::a00:27ff:fea5:3f51 mtearle@liberation:/etc$ avahi-resolve-host-name -4 bazzavan.local bazzavan.local172.16.44.48 # can ping it mtearle@liberation:/etc$ ping -c 1 172.16.44.48 PING 172.16.44.48 (172.16.44.48) 56(84) bytes of data. 64 bytes from 172.16.44.48: icmp_seq=1 ttl=64 time=0.265 ms --- 172.16.44.48 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.265/0.265/0.265/0.000 ms # original ordering mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf hosts: files resolve [!UNAVAIL=return] mdns4_minimal [NOTFOUND=return] dns # go away and edit /etc/nsswitch.conf # change ordering of resolve and mdns4_minimal mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns # check mdns lookups now work, and it now pings mtearle@liberation:/etc$ ping -c 1 bazzavan.local PING bazzavan.local (172.16.44.48) 56(84) bytes of data. 64 bytes from 172.16.44.48 (172.16.44.48): icmp_seq=1 ttl=64 time=0.161 ms --- bazzavan.local ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.161/0.161/0.161/0.000 ms # check libnss-resolve is still doing its thing mtearle@liberation:/etc$ ping -c 1 localhost.localdomain PING localhost.localdomain(localhost (::1%1)) 56 data bytes 64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.016 ms --- localhost.localdomain ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.016/0.016/0.016/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-mdns/+bug/1641328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 411688] Re: pulseaudio floods network with multicast packets
** Changed in: pulseaudio (Arch Linux) Importance: Undecided => Unknown ** Changed in: pulseaudio (Arch Linux) Status: New => Unknown ** Changed in: pulseaudio (Arch Linux) Remote watch: None => freedesktop.org Bugzilla #44777 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030: 0x0040: 01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto
[Touch-packages] [Bug 411688] Re: pulseaudio floods network with multicast packets
This are upstream bug with Flooding packages to Network. On pulseaudio 9.0 same problem, but upstream reqired to fix it up. Distributive: ArchLinux. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: New Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030: 0x0040: 01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x00
[Touch-packages] [Bug 411688] Re: pulseaudio floods network with multicast packets
** Also affects: pulseaudio (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: New Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030: 0x0040: 01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d18 4000 0111 2d64 0a00 0001 0x0010: e00
[Touch-packages] [Bug 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account
I faced once with the same problem after installing evolution-ews. But after I've tried to add account 3-4 times and it worked. I removed unnecessary accounts and left the only one. But there is another problem. Evolution hangs and freezes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1061195 Title: Evolution appears unable to create EWS or Exchange MAPI account Status in evolution-ews: Expired Status in evolution package in Ubuntu: Triaged Status in evolution-data-server package in Ubuntu: Triaged Status in evolution-ews package in Ubuntu: Triaged Status in evolution-mapi package in Ubuntu: Won't Fix Bug description: Evolution appears unable to create an EW or MAPI account. All the steps proceed normally, including fetching the URL (for EWS) or authenticating (for MAPI). However, at the conclusion of account creation process, no actual account appears in the list. I've tried starting Evolution from the command line using various DEBUG_ variables and there are no EWS- or MAPI-specific errors. So I'm not exactly sure what to do next. I am fairly certain the problem doesn't lie with my corporate Exchange server, as web mail works fine and any other EWS-capable client (like the mail app in Android). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evolution 3.6.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Wed Oct 3 12:40:28 2012 InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Beta amd64 (20120925) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-ews/+bug/1061195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622764] [NEW] package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в паке
Public bug reported: Problem whith Kali Linux ProblemType: Package DistroRelease: Kali 2016.2 Package: console-setup-linux 1.108ubuntu15.2 Uname: Linux 4.6.7-rt11 x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Sep 13 00:57:58 2016 ErrorMessage: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете keyboard-configuration 1.108ubuntu15.2 InstallationDate: Installed on 2016-09-12 (0 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10kali1 apt 1.2.14 SourcePackage: console-setup Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете keyboard-configuration 1.108ubuntu15.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kali-rolling third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1622764 Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете keyboard-configuration 1.108ubuntu15.2 Status in console-setup package in Ubuntu: New Bug description: Problem whith Kali Linux ProblemType: Package DistroRelease: Kali 2016.2 Package: console-setup-linux 1.108ubuntu15.2 Uname: Linux 4.6.7-rt11 x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Sep 13 00:57:58 2016 ErrorMessage: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете keyboard-configuration 1.108ubuntu15.2 InstallationDate: Installed on 2016-09-12 (0 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10kali1 apt 1.2.14 SourcePackage: console-setup Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете keyboard-configuration 1.108ubuntu15.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1622764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590226] [NEW] Language order is wrong at Greeter Screen
Public bug reported: Description:Ubuntu 16.04 LTS Release:16.04 lightdm: Installed: 1.18.1-0ubuntu1 Candidate: 1.18.1-0ubuntu1 unity-greeter: Installed: 16.04.2-0ubuntu1 Candidate: 16.04.2-0ubuntu1 Current Ubuntu box uses 2 languages, Korean Hangul and Russian, with ibus as an input engine. English is deleted as Korean IM includes English by default. At login screen language selector should contain independent set of languages with English selected by default. However, instead the selector contains 2 languages: Russian and English, with Russian selected by default. Therefore, typing English password becomes uncomfortable, since it requires manual selection of English language (using mouse). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: symap_custom_4_4_0_22_generic_x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 11:41:44 2016 InstallationDate: Installed on 2016-06-03 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1590226 Title: Language order is wrong at Greeter Screen Status in lightdm package in Ubuntu: New Bug description: Description: Ubuntu 16.04 LTS Release: 16.04 lightdm: Installed: 1.18.1-0ubuntu1 Candidate: 1.18.1-0ubuntu1 unity-greeter: Installed: 16.04.2-0ubuntu1 Candidate: 16.04.2-0ubuntu1 Current Ubuntu box uses 2 languages, Korean Hangul and Russian, with ibus as an input engine. English is deleted as Korean IM includes English by default. At login screen language selector should contain independent set of languages with English selected by default. However, instead the selector contains 2 languages: Russian and English, with Russian selected by default. Therefore, typing English password becomes uncomfortable, since it requires manual selection of English language (using mouse). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: symap_custom_4_4_0_22_generic_x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 11:41:44 2016 InstallationDate: Installed on 2016-06-03 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1590226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1288182] Re: Cyrillic not displayed in the input field
confirm this bug, Ubuntu 14.04 x64 with the latest updates. Evince 3.10.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: Confirmed Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578341] [NEW] bug with nvidia
Public bug reported: Nvidia bug i dont really know what it is ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Är en katalog: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 364.19 Tue Apr 19 14:44:55 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 4 20:41:08 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia, 364.19, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 970] [1462:3160] InstallationDate: Installed on 2016-04-24 (10 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--kylin--vg-root ro nouveau.blacklist=1 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B150M-DS3H DDR3-CF 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: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd08/19/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB150M-DS3HDDR3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.68+git1604280630.fc09c5~gd~x version.libgl1-mesa-dri: libgl1-mesa-dri 11.3+gallium-nine~git1604180800.9ce58a~gd~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.3+gallium-nine~git1604180800.9ce58a~gd~x version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed May 4 17:56:06 2016 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1578341 Title: bug with nvidia Status in xorg package in Ubuntu: New Bug description: Nvidia bug i dont really know what it is ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Är en katalog: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 364.19 Tue Apr 19 14:44:55 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
[Touch-packages] [Bug 1578336] [NEW] kerner error
Public bug reported: its a bad error 0 with amd installer on my laptop ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed May 4 20:01:31 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.302: added ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8650G] [1043:21ad] InstallationDate: Installed on 2016-05-04 (0 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. X550DP ProcEnviron: LANGUAGE=sv TERM=xterm-256color PATH=(custom, no user) LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--kylin--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550DP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd09/09/2013:svnASUSTeKCOMPUTERINC.:pnX550DP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550DP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550DP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed May 4 19:28:22 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1578336 Title: kerner error Status in xorg package in Ubuntu: New Bug description: its a bad error 0 with amd installer on my laptop ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed May 4 20:01:31 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.302: added ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8650G] [1043:21ad] InstallationDate: Installed on 2016-05-04 (0 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. X550DP ProcEnviron: LANGUAGE=sv TERM=xterm-256color PATH=(custom, no user) LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--kylin--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550DP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.
[Touch-packages] [Bug 1559805] Re: suspend not working with latest xenial and kernel 4.4.0
Confirming that new kernel fix this issue. Tested on 4.6-rc3 -- 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/1559805 Title: suspend not working with latest xenial and kernel 4.4.0 Status in xorg package in Ubuntu: Confirmed Bug description: suspend stops but never finishes and needs a reboot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 20 22:45:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-04 (168 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-03-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1559805] Re: suspend not working with latest xenial and kernel 4.4.0
I have same bug. After closing lid system going to suspend but never woke up. here is suspend log Апр 16 21:08:50 LissAmour systemd-logind[648]: Lid closed. Апр 16 21:08:50 LissAmour systemd-logind[648]: Suspending... Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2340] manager: sleep requested (sleeping: no enabled: yes) Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2340] manager: sleeping... Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2341] device (wlan0): state change: activated -> unmanaged (reason 'sleeping') [100 Апр 16 21:08:50 LissAmour /usr/lib/gdm3/gdm-x-session[1643]: gnome-session-binary[1653]: DEBUG(+): GsmSystemd: received logind signal: PrepareForSleep Апр 16 21:08:50 LissAmour /usr/lib/gdm3/gdm-x-session[1643]: gnome-session-binary[1653]: DEBUG(+): GsmSystemd: ignoring PrepareForSleep signal Апр 16 21:08:50 LissAmour gnome-session-binary[1653]: DEBUG(+): GsmSystemd: received logind signal: PrepareForSleep Апр 16 21:08:50 LissAmour gnome-session-binary[1653]: DEBUG(+): GsmSystemd: ignoring PrepareForSleep signal Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2519] dhcp4 (wlan0): canceled DHCP transaction, DHCP client pid 1003 Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Withdrawing address record for 192.168.0.104 on wlan0. Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2520] dhcp4 (wlan0): state changed bound -> done Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.104. Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Interface wlan0.IPv4 no longer relevant for mDNS. Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Withdrawing address record for fe80::9ead:97ff:fe36:bf45 on wlan0. Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::9ead:97ff:fe36:bf45. Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Interface wlan0.IPv6 no longer relevant for mDNS. Апр 16 21:08:50 LissAmour kernel: wlan0: deauthenticating from c0:4a:00:56:d8:56 by local choice (Reason: 3=DEAUTH_LEAVING) Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2596] dns-mgr: Writing DNS information to /sbin/resolvconf Апр 16 21:08:50 LissAmour dnsmasq[1014]: setting upstream servers from DBus Апр 16 21:08:50 LissAmour wpa_supplicant[935]: wlan0: CTRL-EVENT-DISCONNECTED bssid=c0:4a:00:56:d8:56 reason=3 locally_generated=1 Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] Cannot reach: https://daisy.ubuntu.com Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] offline Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2906] manager: NetworkManager state is now ASLEEP Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] Cannot reach: https://daisy.ubuntu.com Апр 16 21:08:50 LissAmour kernel: cfg80211: World regulatory domain updated: Апр 16 21:08:50 LissAmour kernel: cfg80211: DFS Master region: unset Апр 16 21:08:50 LissAmour kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Апр 16 21:08:50 LissAmour kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Апр 16 21:08:50 LissAmour kernel: cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Апр 16 21:08:50 LissAmour kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: Regulatory domain changed to country: UA Апр 16 21:08:50 LissAmour kernel: cfg80211: DFS Master region: ETSI Апр 16 21:08:50 LissAmour kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Апр 16 21:08:50 LissAmour kernel: cfg80211: (240 KHz - 2483500 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (515 KHz - 535 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (549 KHz - 567 KHz @ 8 KHz), (N/A, 2000 mBm), (0 s) Апр 16 21:08:50 LissAmour kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (5700 KHz - 6600 KHz @ 216 KHz), (N/A, 4000 mBm), (N/A) Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.5255] device (44:D4:E0:B7:73:D4): state change: disconnected ->
[Touch-packages] [Bug 1569184] Re: variety crashed during open a file in Terminal (betty)
Hello, the error occurs, with an old SSL-paket, it's invalid at the date, but we solved the fail, see here for more information : https://github.com/pickhardt/betty/issues/171 but it's only for betty, Variety crash in spite of all. ** Also affects: openssl (Ubuntu) Importance: Undecided Status: New ** Package changed: openssl (Ubuntu) => cathead -- 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/1569184 Title: variety crashed during open a file in Terminal (betty) Status in cathead: New Status in Variety: New Bug description: Hello to all, at 1st I use UBUNTU 16.04 and variety and a lot of other stuff. So, my two problems are : 1st when I open a Terminal and in the terminal I start a file "betty" and in that program, when I write that line betty turn web on, variety crashes every time I do this, this fault happens also, when I start variety manually. 2nd when I open variety and I'll go in preferences / settings and when I want delete some pictures, variety shows up a error. So, when I want to delete a lot of pictures, I let the error on, after I finished with the deleting of the pictures. I press that button, where the error is shown up, and variety restarts and all is fine, but after approximately 1 or 2 hours it crashed complete, so I must restart it manually. My question is : Has anyone of you the same trouble with variety, or I'm the only one ? cu Toni PS: and sorry for my English, but I'm from the south of German and I doesn't speak English very often. To manage notifications about this bug go to: https://bugs.launchpad.net/cathead/+bug/1569184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1566954] [NEW] package linux-image-4.2.0-35-generic 4.2.0-35.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127
Public bug reported: Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Paketaktualisierung (Upgrade) wird berechnet... Fertig 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. 4 nicht vollständig installiert oder entfernt. Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt. Möchten Sie fortfahren? [J/n] j linux-image-4.2.0-35-generic (4.2.0-35.40) wird eingerichtet ... Running depmod. update-initramfs: deferring update (hook will be called later) The link /initrd.img is a dangling linkto /boot/initrd.img-4.2.0-35-generic vmlinuz(/boot/vmlinuz-4.2.0-35-generic ) points to /boot/vmlinuz-4.2.0-35-generic (/boot/vmlinuz-4.2.0-35-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.2.0-35-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.2.0-35-generic /boot/vmlinuz-4.2.0-35-generic /etc/kernel/postinst.d/apt-auto-removal: 85: /etc/kernel/postinst.d/apt-auto-removal: mv: not found run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.2.0-35-generic.postinst line 1025. dpkg: Fehler beim Bearbeiten des Paketes linux-image-4.2.0-35-generic (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-image-extra-4.2.0-35-generic: linux-image-extra-4.2.0-35-generic hängt ab von linux-image-4.2.0-35-generic; aber: Paket linux-image-4.2.0-35-generic ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes linux-image-extra-4.2.0-35-generic (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-image-generic: linux-image-generic hängt ab von linux-image-4.2.0-35-generic; aber: Paket linux-image-4.2.0-35-generic ist noch nicht konfiguriert. linux-image-generic hängt ab von linux-image-extra-4.2.0-35-generic; aber: Paket linux-image-extra-4.2.0-35-generic ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes linux-image-generic (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-generic: linux-generic hängt ab von linux-image-generic (= 4.Es wurde kein Apport-Bericht verfasst, da die Fehlermeldung darauf hindeutet, dass dies lediglich ein Folgefehler eines vorherigen Problems ist. Es wurde kein Apport-Bericht verfasst, da die Fehlermeldung darauf hindeutet, dass dies lediglich ein Folgefehler eines vorherigen Problems ist. Es wurde kein Apport-Bericht verfasst, da das Limit MaxReports bereits erreicht ist. 2.0.35.38); aber: Paket linux-image-generic ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes linux-generic (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert Fehler traten auf beim Bearbeiten von: linux-image-4.2.0-35-generic linux-image-extra-4.2.0-35-generic linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic 4.2.0-35.40 ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1543 F pulseaudio Date: Wed Apr 6 17:35:52 2016 DuplicateSignature: package:linux-image-4.2.0-35-generic:4.2.0-35.40:run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127 ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127 HibernationDevice: RESUME=UUID=731235ff-6242-45bc-a313-904ba6adee6d InstallationDate: Installed on 2014-12-31 (462 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP EliteBook 2540p ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: apt Title: package linux-image-4.2.0-35-generic 4.2.0-35.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CSU Ver. F.24 dmi.board.name: 7008 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 38.34 dmi.chassis.asset.tag: C
[Touch-packages] [Bug 1543556] Re: Xorg crash while using netbeans
I'm unable to reproduce crash with latest updates, so I guess that issue was fixed. ** Changed in: xorg (Ubuntu) Status: Incomplete => Fix Released -- 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/1543556 Title: Xorg crash while using netbeans Status in xorg package in Ubuntu: Fix Released Bug description: xorg randomly crashes while I using NetBeans 8.1. Crash reproducable with oracle and openjdk version 7 and 8. backtrace I got after another crash Program received signal SIGABRT, Aborted. 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #0 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x7f5412e74e8a in __GI_abort () at abort.c:89 #2 0x7f5412eb6bb3 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f5412fcf128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x7f5412ebebc9 in malloc_printerr (ptr=, str=0x7f5412fcf1c8 "free(): corrupted unsorted chunks", action=1) at malloc.c:4965 #4 _int_free (av=, p=, have_lock=0) at malloc.c:3834 #5 0x7f5412ec27fc in __GI___libc_free (mem=) at malloc.c:2950 #6 0x55a20f705500 in present_event_notify () #7 0x7f540f11ec05 in present_flip_handler (event=, data=0x55a21054b7f0) at ../../../src/sna/sna_present.c:552 #8 0x7f540f08a2b0 in sna_mode_wakeup (sna=, sna@entry=0x7f5415041000) at ../../../src/sna/sna_display.c:9014 #9 0x7f540f08df80 in sna_wakeup_handler (arg=, result=1, read_mask=0x55a20fa244e0) at ../../../src/sna/sna_driver.c:733 #10 0x55a20f6286fa in WakeupHandler () #11 0x55a20f77e1df in WaitForSomething () #12 0x55a20f623811 in ?? () #13 0x55a20f627b9b in ?? () #14 0x7f5412e5ea00 in __libc_start_main (main=0x55a20f611f00, argc=14, argv=0x7fff2d756f58, init=, fini=, rtld_fini=, stack_end=0x7fff2d756f48) at libc-start.c:289 #15 0x55a20f611f39 in _start () ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:58:56 2016 InstallationDate: Installed on 2013-12-27 (773 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-01-30 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1543556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1543556] [NEW] Xorg crash while using netbeans
Public bug reported: xorg randomly crashes while I using NetBeans 8.1. Crash reproducable with oracle and openjdk version 7 and 8. backtrace I got after another crash Program received signal SIGABRT, Aborted. 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #0 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x7f5412e74e8a in __GI_abort () at abort.c:89 #2 0x7f5412eb6bb3 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f5412fcf128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x7f5412ebebc9 in malloc_printerr (ptr=, str=0x7f5412fcf1c8 "free(): corrupted unsorted chunks", action=1) at malloc.c:4965 #4 _int_free (av=, p=, have_lock=0) at malloc.c:3834 #5 0x7f5412ec27fc in __GI___libc_free (mem=) at malloc.c:2950 #6 0x55a20f705500 in present_event_notify () #7 0x7f540f11ec05 in present_flip_handler (event=, data=0x55a21054b7f0) at ../../../src/sna/sna_present.c:552 #8 0x7f540f08a2b0 in sna_mode_wakeup (sna=, sna@entry=0x7f5415041000) at ../../../src/sna/sna_display.c:9014 #9 0x7f540f08df80 in sna_wakeup_handler (arg=, result=1, read_mask=0x55a20fa244e0) at ../../../src/sna/sna_driver.c:733 #10 0x55a20f6286fa in WakeupHandler () #11 0x55a20f77e1df in WaitForSomething () #12 0x55a20f623811 in ?? () #13 0x55a20f627b9b in ?? () #14 0x7f5412e5ea00 in __libc_start_main (main=0x55a20f611f00, argc=14, argv=0x7fff2d756f58, init=, fini=, rtld_fini=, stack_end=0x7fff2d756f48) at libc-start.c:289 #15 0x55a20f611f39 in _start () ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:58:56 2016 InstallationDate: Installed on 2013-12-27 (773 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-01-30 (9 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1543556 Title: Xorg crash while using netbeans Status in xorg package in Ubuntu: New Bug description: xorg randomly crashes while I using NetBeans 8.1. Crash reproducable with oracle and openjdk version 7 and 8. backtrace I got after another crash Program received signal SIGABRT, Aborted. 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #0 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x7f5412e74e8a in __GI_abort () at abort.c:89 #2 0x7f5412eb6bb3 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f5412fcf128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x7f5412ebebc9 in malloc_printerr (ptr=, str=0x7f5412fcf1c8 "free(): corrupted unsorted chunks", action=1) at malloc.c:4965 #4 _int_free (av=, p=, have_lock=0) at malloc.c:3834 #5 0x7f5412ec27fc in __GI___libc_free (mem=) at malloc.c:2950 #6 0x55a20f705500 in present_event_notify () #7 0x7f540f11ec05 in present_flip_handler (event=, data=0x55a21054b7f0) at ../../../src/sna/sna_present.c:552 #8 0x7f540f08a2b0 in sna_mode_wakeup (sna=, sna@entry=0x7f5415041000) at ../../../src/sna/sna_display.c:9014 #9 0x7f540f08df80 in sna_wakeup_handler (arg=, result=1, read_mask=0x55a20fa244e0) at ../../../src/sna/sna_driver.c:733 #10 0x55a20f6286fa in WakeupHandler () #11 0x55a20f77e1df in WaitForSomething () #12 0x55a20f623811 in ?? () #13 0x55a20f627b9b in ?? () #14 0x7f5412e5ea00 in __libc_start_main (main=0x55a20f611f00, argc=14, argv=0x7fff2d756f58, init=, fini=, rtld_fini=, stack_end=0x7fff2d756f48) at libc-start.c:289 #15 0x55a20f611f39 in _start () ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:58:56 2016 InstallationDate: Installed on 2013-12-27 (773 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-01-30 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1543556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1542747] [NEW] Empathy stop working with accounts setup with GOA after last telepathy update
Public bug reported: I have google account setup with gnome online accounts. After updating telepathy-mission control from 1:5.16.3-1ubuntu4 to 1:5.16.3-1ubuntu5 empathy stopped recognizing this account. Another account (icq) that was setup directly in empathy works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: telepathy-mission-control-5 1:5.16.3-1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Feb 7 02:22:11 2016 InstallationDate: Installed on 2013-12-27 (771 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) SourcePackage: telepathy-mission-control-5 UpgradeStatus: Upgraded to xenial on 2016-01-30 (7 days ago) ** Affects: telepathy-mission-control-5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1542747 Title: Empathy stop working with accounts setup with GOA after last telepathy update Status in telepathy-mission-control-5 package in Ubuntu: New Bug description: I have google account setup with gnome online accounts. After updating telepathy-mission control from 1:5.16.3-1ubuntu4 to 1:5.16.3-1ubuntu5 empathy stopped recognizing this account. Another account (icq) that was setup directly in empathy works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: telepathy-mission-control-5 1:5.16.3-1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Feb 7 02:22:11 2016 InstallationDate: Installed on 2013-12-27 (771 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) SourcePackage: telepathy-mission-control-5 UpgradeStatus: Upgraded to xenial on 2016-01-30 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1542747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1542328] [NEW] package bluez 5.35-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: bluez failes to install in LXC container. It's come as a dependency of ubuntu-desktop and therefore breaks its installation on Wily. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 NonfreeKernelModules: btrfs ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c xt_multiport unix_diag tcp_diag inet_diag xt_nat ip6table_filter ip6_tables bluetooth veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_hdmi kvm_amd kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw snd_hda_codec_realtek usblp fam15h_power k10temp edac_core edac_mce_amd snd_hda_intel snd_hda_codec nouveau snd_hwdep snd_pcm snd_page_alloc mxm_wmi i2c_piix4 video snd_timer ttm drm_kms_helper drm snd soundcore i2c_algo_bit mac_hid shpchp wmi parport_pc ppdev lp parport dm_snapshot pata_acpi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 pata_atiixp raid0 r8169 mii multipath ahci libahci linear ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Feb 5 16:47:05 2016 DuplicateSignature: package:bluez:5.35-0ubuntu2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InterestingModules: bluetooth Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=/dev/mapper/system-root ro nosplash nomdmonddf nomdmonisw RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: bluez Title: package bluez 5.35-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: 970DE3/U3S3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd10/05/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970DE3/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. getfacl: Error: command ['getfacl', '/dev/rfkill'] failed with exit code 1: getfacl: /dev/rfkill: No such file or directory hciconfig: Error: command hciconfig failed with exit code 1: Can't open HCI socket.: Address family not supported by protocol rfkill: Can't open RFKILL control device: No such file or directory ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- 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/1542328 Title: package bluez 5.35-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: bluez failes to install in LXC container. It's come as a dependency of ubuntu-desktop and therefore breaks its installation on Wily. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 NonfreeKernelModules: btrfs ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c xt_multiport unix_diag tcp_diag inet_diag xt_nat ip6table_filter ip6_tables bluetooth veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_hdmi kvm_amd kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw snd_hda_codec_realtek usblp fam15h_power k10temp edac_core edac_mce_amd snd_hda_intel snd_hda_codec nouveau snd_hwdep snd_pcm snd_page_alloc mxm_wmi i2c_piix4 video snd_timer ttm drm_kms_helper drm snd soundcore i2c_algo_bit mac_hid shpchp wmi parport_pc ppdev lp parport dm_snapshot pata_acpi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xo
[Touch-packages] [Bug 1446906] Re: lxc container with postfix, permission denied on mailq
@jjohansen, I've tested your build and can confirm it fixes the issue. root@host:~# uname -a Linux host 3.19.0-31-generic #36+lp1446906v3 SMP Fri Dec 18 08:37:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@lxc:~# mailq Mail queue is empty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1446906 Title: lxc container with postfix, permission denied on mailq Status in lxc package in Ubuntu: Confirmed Bug description: Hello, on three Vivid host, all of them up-to-date, I have the problem described here: https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1390223 That bug report shows the problem was fixed, but it is not (at least on current Vivid) ii linux-image-generic 3.19.0.15.14 amd64 Generic Linux kernel image ii lxc 1.1.2-0ubuntu3 amd64 Linux Containers userspace tools ii apparmor2.9.1-0ubuntu9 amd64 User-space parser utility for AppArmor Reproducible with: $ sudo lxc-create -n test -t ubuntu $ sudo lxc-start -n test (inside container) $ sudo apt-get install postfix $ mailq postqueue: warning: close: Permission denied dmesg shows: [82140.386109] audit: type=1400 audit(1429661150.086:17067): apparmor="DENIED" operation="file_perm" profile="lxc-container-default" name="public/showq" pid=27742 comm="postqueue" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zoolook1913 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=aa25401d-0553-43dc-b7c8-c530fe245fb6 InstallationDate: Installed on 2015-02-27 (53 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 20150 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 Tags: vivid Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-29 (24 days ago) UserGroups: adm docker libvirtd lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5ECN95WW(V9.00) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G580 dmi.modalias: dmi:bvnLENOVO:bvr5ECN95WW(V9.00):bd12/19/2012:svnLENOVO:pn20150:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG580: dmi.product.name: 20150 dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446906] Re: lxc container with postfix, permission denied on mailq
I encountered this problem too on Ubuntu 15.04 running 3.19.0-39 kernel. Fixed it by turned off apparmor profile for LXC container by adding "lxc.aa_profile = unconfined" into container's config. In my case increased security risk is acceptable, but it's desirable to fix it the right way. Is there any information in what kernel version it will be fixed and when this updates will be available in standartd ubuntu repositories? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1446906 Title: lxc container with postfix, permission denied on mailq Status in lxc package in Ubuntu: Confirmed Bug description: Hello, on three Vivid host, all of them up-to-date, I have the problem described here: https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1390223 That bug report shows the problem was fixed, but it is not (at least on current Vivid) ii linux-image-generic 3.19.0.15.14 amd64 Generic Linux kernel image ii lxc 1.1.2-0ubuntu3 amd64 Linux Containers userspace tools ii apparmor2.9.1-0ubuntu9 amd64 User-space parser utility for AppArmor Reproducible with: $ sudo lxc-create -n test -t ubuntu $ sudo lxc-start -n test (inside container) $ sudo apt-get install postfix $ mailq postqueue: warning: close: Permission denied dmesg shows: [82140.386109] audit: type=1400 audit(1429661150.086:17067): apparmor="DENIED" operation="file_perm" profile="lxc-container-default" name="public/showq" pid=27742 comm="postqueue" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zoolook1913 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=aa25401d-0553-43dc-b7c8-c530fe245fb6 InstallationDate: Installed on 2015-02-27 (53 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 20150 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 Tags: vivid Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-29 (24 days ago) UserGroups: adm docker libvirtd lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5ECN95WW(V9.00) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G580 dmi.modalias: dmi:bvnLENOVO:bvr5ECN95WW(V9.00):bd12/19/2012:svnLENOVO:pn20150:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG580: dmi.product.name: 20150 dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1098738] Re: apt-get source only checks md5 hashes in Sources files
Hey Julian... How has this been fixed eventually? As I proposed, that all available hash algos are verified and if any fails consider it completely failed,... plus a minimum hash algo (that is not md5 or sha1 ^^)? Cheers, Chris. -- 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/1098738 Title: apt-get source only checks md5 hashes in Sources files Status in apt package in Ubuntu: Fix Released Bug description: 'apt-get source' only validates the md5 hash in the Sources file. Ideally, it should check the sha hashes also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1098738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515615] Re: Disk quotas don't work in LXC containers
You are right, I have got other problems after adding the device to the container. I see it is possible to get quota working, but it's too tricky and unpredictrable for production use. I'm wondering why LXC is not using real device by default for LVM (XFS etc.)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1515615 Title: Disk quotas don't work in LXC containers Status in lxc package in Ubuntu: Confirmed Bug description: I'm trying to enable disk quotas in LXC container by adding option to its config: lxc.rootfs.options = usrquota After booting the container I'm trying to initialize quotas but getting the following error: r...@test.lxc:~# quotacheck -gum / quotacheck: Cannot stat() mounted device /dev/lxc/test: No such file or directory quotacheck: Mountpoint (or device) / not found or has no quota enabled. quotacheck: Cannot find filesystem to check or filesystem not mounted with quota option. Host OS: Ubuntu 15.04 Guest OS: Ubuntu 14.04.3 LTS lxc 1.1.2-0ubuntu3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515615] Re: Disk quotas don't work in LXC containers
As LXC manpage states the 'lxc.rootfs.optionst' option is "extra mount options to use when mounting the rootfs". In my case this is an LVM device. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1515615 Title: Disk quotas don't work in LXC containers Status in lxc package in Ubuntu: New Bug description: I'm trying to enable disk quotas in LXC container by adding option to its config: lxc.rootfs.options = usrquota After booting the container I'm trying to initialize quotas but getting the following error: r...@test.lxc:~# quotacheck -gum / quotacheck: Cannot stat() mounted device /dev/lxc/test: No such file or directory quotacheck: Mountpoint (or device) / not found or has no quota enabled. quotacheck: Cannot find filesystem to check or filesystem not mounted with quota option. Host OS: Ubuntu 15.04 Guest OS: Ubuntu 14.04.3 LTS lxc 1.1.2-0ubuntu3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515615] [NEW] Disk quotas don't work in LXC containers
Public bug reported: I'm trying to enable disk quotas in LXC container by adding option to its config: lxc.rootfs.options = usrquota After booting the container I'm trying to initialize quotas but getting the following error: r...@test.lxc:~# quotacheck -gum / quotacheck: Cannot stat() mounted device /dev/lxc/test: No such file or directory quotacheck: Mountpoint (or device) / not found or has no quota enabled. quotacheck: Cannot find filesystem to check or filesystem not mounted with quota option. Host OS: Ubuntu 15.04 Guest OS: Ubuntu 14.04.3 LTS lxc 1.1.2-0ubuntu3.2 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1515615 Title: Disk quotas don't work in LXC containers Status in lxc package in Ubuntu: New Bug description: I'm trying to enable disk quotas in LXC container by adding option to its config: lxc.rootfs.options = usrquota After booting the container I'm trying to initialize quotas but getting the following error: r...@test.lxc:~# quotacheck -gum / quotacheck: Cannot stat() mounted device /dev/lxc/test: No such file or directory quotacheck: Mountpoint (or device) / not found or has no quota enabled. quotacheck: Cannot find filesystem to check or filesystem not mounted with quota option. Host OS: Ubuntu 15.04 Guest OS: Ubuntu 14.04.3 LTS lxc 1.1.2-0ubuntu3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506947] [NEW] Xorg process is too heavy
Public bug reported: I need rebooting my computer every 5-6 hours for cleaning memory, Open Sourse AMD driver not working correctly. please help me ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin Date: Fri Oct 16 23:28:17 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.19.0-25-generic, x86_64: installed fglrx-core, 15.200, 3.19.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:03ca] InstallationDate: Installed on 2015-10-08 (8 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer P5K-E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=05ea51e2-929b-4736-90e9-0a594fd0fc5a ro nopat splash quiet plymouth:debug=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1305 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1305:bd06/19/2009:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Oct 16 16:13:44 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3.1~trusty1 xserver.video_driver: fglrx ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1506947 Title: Xorg process is too heavy Status in xorg package in Ubuntu: New Bug description: I need rebooting my computer every 5-6 hours for cleaning memory, Open Sourse AMD driver not working correctly. please help me ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin Date: Fri Oct 16 23:28:17 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.200, 3.19.0-25-generic, x86_64: installed fglrx-core, 15.200, 3.19.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:03ca] InstallationDate: Installed on 2015-10-08 (8 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer P5K-E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=05ea51e2-929b-4736-90e9-0a594fd0fc5a ro nopat splash quiet plymouth:debug=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1305 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K-
[Touch-packages] [Bug 1503382] Re: unable to install python3.4 dev on fresh ubuntu cloud image
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1503382 Title: unable to install python3.4 dev on fresh ubuntu cloud image Status in amulet package in Ubuntu: Confirmed Status in python3.4 package in Ubuntu: Confirmed Bug description: Latest cloud ubuntu trusty image (06-Oct-2015 10:34) https://cloud- images.ubuntu.com/trusty/current/ apt-get update && apt-get upgrade # works fine # apt-get install python3.4-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3.4-dev : Depends: python3.4 (= 3.4.0-2ubuntu1.1) but 3.4.3-1ubuntu1~14.04.1 is to be installed Depends: libpython3.4-dev (= 3.4.0-2ubuntu1.1) but it is not going to be installed Depends: libpython3.4 (= 3.4.0-2ubuntu1.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. # apt-get install libpython3.4-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libpython3.4-dev : Depends: libpython3.4-stdlib (= 3.4.0-2ubuntu1.1) but 3.4.3-1ubuntu1~14.04.1 is to be installed Depends: libpython3.4 (= 3.4.0-2ubuntu1.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python3.4-dev (not installed) ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Tue Oct 6 17:36:17 2015 SourcePackage: python3.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amulet/+bug/1503382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389954] Re: Make .lxc domain name resolution easier to discover and enable
Tried to follow the documentation on Ubuntu Server 15.04 with no luck. I have activated LXC_DOMAIN="lxc" in /etc/default/lxc-net, then created /etc/dnsmasq.conf and added server=/lxc/10.0.3.1 (there is no NetworkManager installed). Tried to reboot, but still getting "ping: unknown host container.lxc". It seems that dnsmasq doesn't read the config. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1389954 Title: Make .lxc domain name resolution easier to discover and enable Status in lxc package in Ubuntu: Confirmed Bug description: The lxc package on ubuntu does almost nothing to help a user enable DNS resolution for containers via dnsmaq, let alone discover that it is possible. How about enabling it by default? I think all it would take is adding server=/lxc/10.0.3.1 to a file in /etc/NetworkManager/dnsmasq.d/ and uncommenting LXC_DOMAIN="lxc" in /etc/default/lxc-net. Even if there's a good reason not to enable this by default, shouldn't it at least be clearly documented someplace obvious instead of buried in a system config file with a misleading comment that mentions the wrong dnsmasq file to edit? (The one currently mentioned by /etc/default/lxc-net does nothing on ubuntu desktop systems, because ubuntu's NetworkManager starts dnsmasq with a special config directory.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490276] Re: Qt5 apps display squares instead of kana characters
** Attachment added: "main.py" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1490276/+attachment/4454506/+files/main.py -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1490276 Title: Qt5 apps display squares instead of kana characters Status in qtbase-opensource-src package in Ubuntu: New Bug description: Qt5 applications can't display kana characters (see screenshot). That problem occurs not always, sometimes everything works fine, but if I try to launch app several times in a row it can be reproduced. I've attached example script on pyqt. There're similar problem with qt5.2 on Arch, but there it happens each time: https://bugs.archlinux.org/task/38430 https://bugreports.qt.io/browse/QTBUG-36066 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1490276/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490276] [NEW] Qt5 apps display squares instead of kana characters
Public bug reported: Qt5 applications can't display kana characters (see screenshot). That problem occurs not always, sometimes everything works fine, but if I try to launch app several times in a row it can be reproduced. I've attached example script on pyqt. There're similar problem with qt5.2 on Arch, but there it happens each time: https://bugs.archlinux.org/task/38430 https://bugreports.qt.io/browse/QTBUG-36066 ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: trusty ** Attachment added: "qt-japanese-bug.png" https://bugs.launchpad.net/bugs/1490276/+attachment/4454505/+files/qt-japanese-bug.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1490276 Title: Qt5 apps display squares instead of kana characters Status in qtbase-opensource-src package in Ubuntu: New Bug description: Qt5 applications can't display kana characters (see screenshot). That problem occurs not always, sometimes everything works fine, but if I try to launch app several times in a row it can be reproduced. I've attached example script on pyqt. There're similar problem with qt5.2 on Arch, but there it happens each time: https://bugs.archlinux.org/task/38430 https://bugreports.qt.io/browse/QTBUG-36066 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1490276/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1038479] Re: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while
Does not look like a hardware issue with my Toshiba Satellite L750-129. I have Windows 7 in dual-boot with OpenSuSe 13.2 and speakers do ALWAYS work on Windows 7, and do not work on OpenSuSe. Claims about overheating do not explain this. Moreover my colleague has Satellite L755 with same Win7/OpenSuSe13.2 configuration and experiences exactly same problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1038479 Title: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: Restart will fix the issue, but sound always quits from internal speaker. Headphones work always. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernie 1838 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xc060 irq 44' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f15069,1179fc50,00100302 HDA:80862805,1179fc50,0010' Controls : 24 Simple ctrls : 11 Date: Sat Aug 18 11:18:34 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Sound works for a while, then breaks Title: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 2.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.20:bd07/13/2011:svnTOSHIBA:pnSatelliteL755:pvrPSK1WU-05N004:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L755 dmi.product.version: PSK1WU-05N004 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1038479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1469837] Re: [Aspire V5-572G, Realtek ALC282] sound volume control keys stopped working
** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1469837 Title: [Aspire V5-572G, Realtek ALC282] sound volume control keys stopped working Status in alsa-driver package in Ubuntu: Invalid Bug description: After recent update to linux-image-3.19.0-21-generic, sound volume control keys stopped working. It kind of works, I still can assign them in System Settings -> Keyboard -> Shortcuts, but it does not control sound volume. xev output shows correct keybindings: $ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 36 = (keysym 0xff0d, Return), state = 0x0 keycode 123 = (keysym 0x1008ff13, XF86AudioRaiseVolume), state = 0x0 keycode 122 = (keysym 0x1008ff11, XF86AudioLowerVolume), state = 0x0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: egoisto3581 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 29 23:25:25 2015 InstallationDate: Installed on 2011-12-21 (1285 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Volume slider, or mixer problems Title: [Aspire V5-572G, Realtek ALC282, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to vivid on 2015-05-10 (50 days ago) dmi.bios.date: 05/22/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Dazzle_CX dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd05/22/2013:svnAcer:pnAspireV5-572G:pvrV2.06:rvnAcer:rnDazzle_CX:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-572G dmi.product.version: V2.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1469837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1469837] [NEW] [Aspire V5-572G, Realtek ALC282] sound volume control keys stopped working
Public bug reported: After recent update to linux-image-3.19.0-21-generic, sound volume control keys stopped working. It kind of works, I still can assign them in System Settings -> Keyboard -> Shortcuts, but it does not control sound volume. xev output shows correct keybindings: $ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 36 = (keysym 0xff0d, Return), state = 0x0 keycode 123 = (keysym 0x1008ff13, XF86AudioRaiseVolume), state = 0x0 keycode 122 = (keysym 0x1008ff11, XF86AudioLowerVolume), state = 0x0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: egoisto3581 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 29 23:25:25 2015 InstallationDate: Installed on 2011-12-21 (1285 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Volume slider, or mixer problems Title: [Aspire V5-572G, Realtek ALC282, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to vivid on 2015-05-10 (50 days ago) dmi.bios.date: 05/22/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Dazzle_CX dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd05/22/2013:svnAcer:pnAspireV5-572G:pvrV2.06:rvnAcer:rnDazzle_CX:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-572G dmi.product.version: V2.06 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1469837 Title: [Aspire V5-572G, Realtek ALC282] sound volume control keys stopped working Status in alsa-driver package in Ubuntu: New Bug description: After recent update to linux-image-3.19.0-21-generic, sound volume control keys stopped working. It kind of works, I still can assign them in System Settings -> Keyboard -> Shortcuts, but it does not control sound volume. xev output shows correct keybindings: $ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode \2 = \3, state = \1/p' keycode 36 = (keysym 0xff0d, Return), state = 0x0 keycode 123 = (keysym 0x1008ff13, XF86AudioRaiseVolume), state = 0x0 keycode 122 = (keysym 0x1008ff11, XF86AudioLowerVolume), state = 0x0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: egoisto3581 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 29 23:25:25 2015 InstallationDate: Installed on 2011-12-21 (1285 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Volume slider, or mixer problems Title: [Aspire V5-572G, Realtek ALC282, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to vivid on 2015-05-10 (50 days ago) dmi.bios.date: 05/22/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Dazzle_CX dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd05/22/2013:svnAcer:pnAspireV5-572G:pvrV2.06:rvnAcer:rnDazzle_CX:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-572G dmi.product.version: V2.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1469837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398614] Re: mediascanner-service-2.0 using large amounts of CPU
The same bug for me. Ubuntu 15.04, amd64. I've installed unity8-desktop-session-mir for testing. I'm using Unity 7 environment, but forget to remove unity8 packages with dependencies. When I plug-in my 500GB usb harddrive, mediascanner-service eats all resources and I can't use my computer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1398614 Title: mediascanner-service-2.0 using large amounts of CPU Status in mediascanner2 package in Ubuntu: Confirmed Bug description: Each time I plug my external USB hard disk the mediascanner-service process is activ and is using large amount of CPU for long minutes without interruption. I have the same problem in utopic and vivid ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mediascanner2.0 0.105+15.04.20141030.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 3 00:29:43 2014 InstallationDate: Installed on 2011-05-26 (1286 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: mediascanner2 UpgradeStatus: Upgraded to vivid on 2013-11-26 (371 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1398614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file
This was fixed in Fedora 18 in 2012, works with SELinux, same version of dhcp-server (4.2.4) as trusty. Maybe a similar method can be used with AppArmor? https://bugzilla.redhat.com/show_bug.cgi?id=866714 http://pkgs.fedoraproject.org/cgit/dhcp.git/tree/dhcp-paranoia.patch ** Bug watch added: Red Hat Bugzilla #866714 https://bugzilla.redhat.com/show_bug.cgi?id=866714 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp source package in Trusty: Confirmed Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445239] Re: apt's lists/partial fills disk
I think I see the issue. We parse both Content-Length: and Content- Range: headers. When parsing the Content-Range: header, we set Size to the total size of the file. If the Content-Length header comes last, we reset Size to the size of the data we are receiving, not the total size of the file. The attached patch fixes it for me, although we do get the infamous Hash sum mismatch which clears after rerunning apt-get: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/vivid- security/universe/i18n/Translation-en Hash Sum mismatch Another issue, but I'd love to fix that one day. ** Patch added: "Don't parse Content-Length if Content-Range has been parsed" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1445239/+attachment/4396561/+files/apt-fills-disk.patch -- 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/1445239 Title: apt's lists/partial fills disk Status in APT: New Status in apt package in Ubuntu: Confirmed Status in apt source package in Vivid: Confirmed Bug description: Since I upgraded to vivid, apt fills the disk space at /var/lib/apt/lists/partial. This was triggered by the automatic update every day, and as a solution I killed the processes named `http` spawned by apt, and removed the offending file from lists/partial manually. Until now, `apt-get update` and `apt-get upgrade` had been working. However, today, when I tried `apt-get update`, it got stuck in some file, continuously increasing its size when at 100%. I tried inspecting the file to see if there is a repetition of data, and there seems to be, as I have suspected. First of all, the file is it.archive.ubuntu .com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 this time, but I'm not sure if the previous time it was also this file. I used `tail` and `hexdump` to figure out whether a certain pattern shows up in the file. Here are some examples: $ tail -c 20 it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | hexdump | grep '\' c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0010c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0020c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0030c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a $ tail -c 20 it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | hexdump | grep '\<9b95\>' c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0010c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0020c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0030c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a $ tail -c 20 it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | hexdump | grep '\<1234\>' 0002630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd 0012630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd 0022630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd $ tail -c 20 it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | hexdump | grep '\<76a8\>' 000fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c 001fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c 002fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c As you can see, it seems that after the error, a certain pattern seems to repeat every exactly 0x1 bytes. I attached a copy of those 0x1 bytes that keep repeating (from an arbitrary offset). --- $ lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 $ apt-cache policy apt apt: Installed: 1.0.9.7ubuntu4 Candidate: 1.0.9.7ubuntu4 Version table: *** 1.0.9.7ubuntu4 0 500 http://it.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status --- Do let me know if I can test further to see what could be wrong. I'll keep an eye next times the behavior repeat to make sure the file is the same / the pattern is the same and I'll report back. If you think the problem could be the Italy server, let me know and I'll try with a different one. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 17 00:04:05 2015 SourcePackage: apt UpgradeStatus: Upgraded to vivid on 2015-03-28 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1445239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445239] Re: apt's lists/partial fills disk
I took another look at this. The problem begins in ServerState::HeaderLine() Where we parse a Content-Range header: Content-Range: bytes 587-600/601 So we set StartPos to 587. Then in HttpServerState::RunData() we do In.Limit(Size - StartPos); where Size is 14. We pass a negative number into Limit() which means MaxGet is set to something less than OutP, and we loop forever. -- 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/1445239 Title: apt's lists/partial fills disk Status in APT: New Status in apt package in Ubuntu: Confirmed Status in apt source package in Vivid: Confirmed Bug description: Since I upgraded to vivid, apt fills the disk space at /var/lib/apt/lists/partial. This was triggered by the automatic update every day, and as a solution I killed the processes named `http` spawned by apt, and removed the offending file from lists/partial manually. Until now, `apt-get update` and `apt-get upgrade` had been working. However, today, when I tried `apt-get update`, it got stuck in some file, continuously increasing its size when at 100%. I tried inspecting the file to see if there is a repetition of data, and there seems to be, as I have suspected. First of all, the file is it.archive.ubuntu .com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 this time, but I'm not sure if the previous time it was also this file. I used `tail` and `hexdump` to figure out whether a certain pattern shows up in the file. Here are some examples: $ tail -c 20 it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | hexdump | grep '\' c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0010c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0020c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0030c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a $ tail -c 20 it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | hexdump | grep '\<9b95\>' c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0010c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0020c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a 0030c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a $ tail -c 20 it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | hexdump | grep '\<1234\>' 0002630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd 0012630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd 0022630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd $ tail -c 20 it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 | hexdump | grep '\<76a8\>' 000fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c 001fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c 002fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c As you can see, it seems that after the error, a certain pattern seems to repeat every exactly 0x1 bytes. I attached a copy of those 0x1 bytes that keep repeating (from an arbitrary offset). --- $ lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 $ apt-cache policy apt apt: Installed: 1.0.9.7ubuntu4 Candidate: 1.0.9.7ubuntu4 Version table: *** 1.0.9.7ubuntu4 0 500 http://it.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status --- Do let me know if I can test further to see what could be wrong. I'll keep an eye next times the behavior repeat to make sure the file is the same / the pattern is the same and I'll report back. If you think the problem could be the Italy server, let me know and I'll try with a different one. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 17 00:04:05 2015 SourcePackage: apt UpgradeStatus: Upgraded to vivid on 2015-03-28 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1445239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451337] [NEW] Pressing the Super key inside a VMWare Horizon View window causes the Shortcut Overlay to pop up
Public bug reported: Hi, I often work with remote machines through VMWare Horizon Client. Whenever I use shortcuts with the Super key inside a remote machine, Unity thinks I'm long-pressing it, and shows me the Shortcut Hints Overlay, and also highlights icon numbers in the Unity Launcher. The main point here is the overlay pops up immediately, even though the Super key pressed and released in a split second. This should happen only when the Super key is long-pressed outside of VMWare Horizon Client. This issue is reproducible on Ubuntu 14.10 and 15.04, VMWare Clients 2.2.0 (available in the official repos for Trusty as vmware-view-client) and 3.2.0 (from VMWare's website). I understand that it may not be a Unity problem, but rather the way the Horizon Client handles keys grabbing. Hopefully, there's a way to fix or a workaround it on the Unity side. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon May 4 09:07:02 2015 InstallationDate: Installed on 2015-04-25 (8 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1451337 Title: Pressing the Super key inside a VMWare Horizon View window causes the Shortcut Overlay to pop up Status in unity package in Ubuntu: New Bug description: Hi, I often work with remote machines through VMWare Horizon Client. Whenever I use shortcuts with the Super key inside a remote machine, Unity thinks I'm long-pressing it, and shows me the Shortcut Hints Overlay, and also highlights icon numbers in the Unity Launcher. The main point here is the overlay pops up immediately, even though the Super key pressed and released in a split second. This should happen only when the Super key is long-pressed outside of VMWare Horizon Client. This issue is reproducible on Ubuntu 14.10 and 15.04, VMWare Clients 2.2.0 (available in the official repos for Trusty as vmware-view-client) and 3.2.0 (from VMWare's website). I understand that it may not be a Unity problem, but rather the way the Horizon Client handles keys grabbing. Hopefully, there's a way to fix or a workaround it on the Unity side. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon May 4 09:07:02 2015 InstallationDate: Installed on 2015-04-25 (8 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445239] Re: apt's lists/partial fills disk
I've seen this a few times. It appears to be an issue with recovering
partially downloaded files, and my workaround was to rm
/var/lib/apt/lists/partial/*
Looking through some notes from a few weeks ago, the backtrace was:
(gdb) backtrace
#0 0x3fffb5b5d6ec in SHA1Transform (state=state@entry=0x3fffecb9b5e0,
buffer=buffer@entry=0x3fffecb97043
"f\350'\315\060\372C343\345\030\301b\212'\371\376\271\202\237uiF\247\325\361\245\017o\277\344\031\245\275\370\361\256=C\033\277Y\b\242\021\257I\233\245\321FU\220\216{(\327J\nlB\021\364\360\373\311\066$\304\303\001\031\\\352ނ\024\271\\\321\f\023\255\342tK?b\f\361\306j\037\325\323\nH\036\061\026J\313A0d\306Bo\006\031\246q8\361W\247b@\243\373\322\316a\240y\226tC\213\271#'\"\301N\030pDb\203D\234gEz\237\031\341\062\020Ċ٪K\276\232\201!\332T\227\\\026\242\034\270\031ی\273\272\036\033\006\257q\255u\350\243*\332\373\256\256\205m1
\213\266*\\eN\033\272a"...)
at /build/buildd/apt-1.0.9.7ubuntu4/apt-pkg/contrib/sha1.cc:108
#1 0x3fffb5b5ec9c in SHA1Summation::Add (this=0x3fffecb9b598,
data=0x3fffecb87c10
"n\202\341\067\231\267g\251N\316\324[0\361\070\230`sxtй\300b\200Y\347\252V\323
\310ƃ\273I'\236", len=65536)
at /build/buildd/apt-1.0.9.7ubuntu4/apt-pkg/contrib/sha1.cc:262
#2 0x3fffb5c7a6e0 in Add (Size=65536,
Data=0x3fffecb87c10
"n\202\341\067\231\267g\251N\316\324[0\361\070\230`sxtй\300b\200Y\347\252V\323
\310ƃ\273I'\236", this=0x3fffecb9b530)
at ../build/include/apt-pkg/hashes.h:167
#3 CircleBuf::Write (this=0x3fffecb83b90, Fd=4)
at /build/buildd/apt-1.0.9.7ubuntu4/methods/http.cc:222
#4 0x3fffb5c7b518 in HttpServerState::Go (this=0x3fffecb83960, File=
0x3fffecb81980, ToFile=true)
at /build/buildd/apt-1.0.9.7ubuntu4/methods/http.cc:652
We were stuck in the circular buffer code, the input and output pointers
got out of whack such that we would write the same buffer continually.
--
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/1445239
Title:
apt's lists/partial fills disk
Status in APT:
New
Status in apt package in Ubuntu:
Incomplete
Bug description:
Since I upgraded to vivid, apt fills the disk space at
/var/lib/apt/lists/partial. This was triggered by the automatic update
every day, and as a solution I killed the processes named `http`
spawned by apt, and removed the offending file from lists/partial
manually. Until now, `apt-get update` and `apt-get upgrade` had been
working. However, today, when I tried `apt-get update`, it got stuck
in some file, continuously increasing its size when at 100%.
I tried inspecting the file to see if there is a repetition of data,
and there seems to be, as I have suspected.
First of all, the file is it.archive.ubuntu
.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 this time, but
I'm not sure if the previous time it was also this file.
I used `tail` and `hexdump` to figure out whether a certain pattern
shows up in the file. Here are some examples:
$ tail -c 20
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 |
hexdump | grep '\'
c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
0010c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
0020c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
0030c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
$ tail -c 20
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 |
hexdump | grep '\<9b95\>'
c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
0010c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
0020c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
0030c80 8d9e 63ad bbdf 40a7 3f3e 2b4a 9b95 aa5a
$ tail -c 20
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 |
hexdump | grep '\<1234\>'
0002630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd
0012630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd
0022630 fd50 b08d 7082 1234 85b3 a61e 2921 e0cd
$ tail -c 20
it.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages.bz2 |
hexdump | grep '\<76a8\>'
000fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c
001fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c
002fa90 747d 76a8 078a 67b6 60d9 83f5 5ff3 787c
As you can see, it seems that after the error, a certain pattern seems
to repeat every exactly 0x1 bytes. I attached a copy of those
0x1 bytes that keep repeating (from an arbitrary offset).
---
$ lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
$ apt-cache policy apt
apt:
Installed: 1.0.9.7ubuntu4
Candidate: 1.0.9.7ubuntu4
Version table:
*** 1.0.9.7ubuntu4 0
500 http://it.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
---
Do let me know if I can test further to see what could be wrong. I'll
keep an eye next times the behavior repeat to make sure the file is
the same
[Touch-packages] [Bug 1447955] [NEW] package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
Public bug reported: This bug is reproduced during upgrade from 14.10 to 15.04. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: modemmanager ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri Apr 24 09:00:25 2015 DuplicateSignature: package:modemmanager:1.4.0-1:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2014-12-09 (135 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: modemmanager Title: package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1447955 Title: package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 Status in modemmanager package in Ubuntu: New Bug description: This bug is reproduced during upgrade from 14.10 to 15.04. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: modemmanager ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri Apr 24 09:00:25 2015 DuplicateSignature: package:modemmanager:1.4.0-1:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2014-12-09 (135 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: modemmanager Title: package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1447955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1048430] Re: "dnsmasq not available on the bus"
Wow! I thought that this bug was corrected about three years ago! Since 2012 I do not use my "big" computer as WiFi router, so this problem was disappeared from my horizon... Anton 2015-04-22 15:42 GMT+03:00, Laurent Bonnaud : > This bug still exists in Ubuntu 15.04. Here is what I see in > journalctl: > > Apr 21 22:01:15 xeelee NetworkManager[1493]: dnsmasq not available on > the bus, can't update servers. > Apr 21 22:01:15 xeelee NetworkManager[1493]: [1429646475.907895] > [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: > Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no > such name > Apr 21 22:01:15 xeelee NetworkManager[1493]: DNS: plugin dnsmasq > update failed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1048430 > > Title: > "dnsmasq not available on the bus" > > Status in network-manager package in Ubuntu: > Confirmed > > Bug description: > Dnsmasq seems to be having some issues. This occurs whenever I try to > connect to my wireless network; sometimes it only happens once, but > sometimes the error loops for a while. > > Sep 9 17:43:51 bkerensa NetworkManager[935]: DNS: starting > dnsmasq... > Sep 9 17:43:51 bkerensa NetworkManager[935]: [1347237831.899067] > [nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't > update servers. > Sep 9 17:43:51 bkerensa NetworkManager[935]: [1347237831.899142] > [nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not > get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name > Sep 9 17:43:51 bkerensa NetworkManager[935]: DNS: plugin dnsmasq > update failed > Sep 9 17:43:51 bkerensa NetworkManager[935]: ((null)): writing > resolv.conf to /sbin/resolvconf > > ProblemType: Bug > DistroRelease: Ubuntu 12.10 > Package: dnsmasq (not installed) > ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 > Uname: Linux 3.5.0-13-generic x86_64 > ApportVersion: 2.5.1-0ubuntu7 > Architecture: amd64 > Date: Sun Sep 9 17:47:22 2012 > EcryptfsInUse: Yes > InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 > (20120425) > ProcEnviron: >TERM=xterm >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: dnsmasq > UpgradeStatus: Upgraded to quantal on 2012-08-08 (32 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1048430/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1048430 Title: "dnsmasq not available on the bus" Status in network-manager package in Ubuntu: Confirmed Bug description: Dnsmasq seems to be having some issues. This occurs whenever I try to connect to my wireless network; sometimes it only happens once, but sometimes the error loops for a while. Sep 9 17:43:51 bkerensa NetworkManager[935]: DNS: starting dnsmasq... Sep 9 17:43:51 bkerensa NetworkManager[935]: [1347237831.899067] [nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update servers. Sep 9 17:43:51 bkerensa NetworkManager[935]: [1347237831.899142] [nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Sep 9 17:43:51 bkerensa NetworkManager[935]: DNS: plugin dnsmasq update failed Sep 9 17:43:51 bkerensa NetworkManager[935]: ((null)): writing resolv.conf to /sbin/resolvconf ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sun Sep 9 17:47:22 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to quantal on 2012-08-08 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1048430/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440383] Re: see: can't handle files with spaces in name
https://anonscm.debian.org/cgit/collab-maint/mime- support.git/commit/?id=40f72a77b42803248aad4e4e631449cdd1a61332 That was fixed in upstream but in v3.55, so it's in Utopic only. ** Bug watch added: Debian Bug tracker #723708 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723708 ** Also affects: mime-support (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723708 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1440383 Title: see: can't handle files with spaces in name Status in mime-support package in Ubuntu: New Status in mime-support package in Debian: Unknown Bug description: 'see' command can't open files if they contains spaces in their name - they are not escaped and so it will try to open several files with incorrect names. How to reproduce: $ touch 'test test.pdf' $ see 'test test.pdf' Result: it will open atril twice with 'Error opening file: No such file or directory' message. Also, if filename will contain at least one bracket everything will work fine, eg: $ touch 'test test[.pdf' $ see 'test test[.pdf' That command will open only one instance of atril. Reproduced in 'mime-support 3.54ubuntu1.1'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1440383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440383] Re: see: can't handle files with spaces in name
** Project changed: ubuntu-mate => mime-support (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1440383 Title: see: can't handle files with spaces in name Status in mime-support package in Ubuntu: New Bug description: 'see' command can't open files if they contains spaces in their name - they are not escaped and so it will try to open several files with incorrect names. How to reproduce: $ touch 'test test.pdf' $ see 'test test.pdf' Result: it will open atril twice with 'Error opening file: No such file or directory' message. Also, if filename will contain at least one bracket everything will work fine, eg: $ touch 'test test[.pdf' $ see 'test test[.pdf' That command will open only one instance of atril. Reproduced in 'mime-support 3.54ubuntu1.1'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1440383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431582] Re: there is no wi-fi after suspend mode
The same bug- Asus U38N, Vivid ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Anton (anton-postbox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431582 Title: there is no wi-fi after suspend mode Status in network-manager package in Ubuntu: Confirmed Bug description: During last three days: after suspend mode there is no wi-fi. I have to turn off Network-manager and turn it on again- only after that wi- fi works again ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu10 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 00:56:10 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-18 (510 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 1024 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.18 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 802-11-wireless 1426197268 Пт. 13 марта 2015 00:54:28 yes no /org/freedesktop/NetworkManager/Settings/0 yes wlan0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393169] Re: Double mouse cursor
I've found the reason of this bug (at least in my case)
Double cursor appears once the cursor moves over item with custom CSS cursor
property as "cursor:url('link_to_cursor')"
--
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/1393169
Title:
Double mouse cursor
Status in xorg package in Ubuntu:
Incomplete
Bug description:
Last up to date Xubuntu 64 bits installed on a laptop
Since 2 days, the mouse cursor is double with only the left part as
active and a bar just behing of both arrow (see picture joined).
I tried to change the theme but no way to go back to a normal mouse
cursor
Regards
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Nov 16 11:12:21 2014
InstallationDate: Installed on 2013-01-03 (681 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64
(20121017.1)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: Fresh install
DistroCodename: utopic
DistroRelease: Ubuntu 14.10
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Device [1179:fde0]
Subsystem: Toshiba America Info Systems Device [1179:fde0]
InstallationDate: Installed on 2013-01-03 (695 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64
(20121017.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background:
Impossible d'ouvrir le fichier «
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission
non accordée
** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper:
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
LightdmGreeterLogOld:
** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background:
Impossible d'ouvrir le fichier «
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission
non accordée
** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper:
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
MachineType: TOSHIBA Satellite Pro C650
Package: xorg 1:7.7+7ubuntu2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic
root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
Tags: utopic ubuntu
Uname: Linux 3.16.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/01/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDE:bvr1.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite Pro C650
dmi.product.version: PSC09E-00R01YMV
dmi.sys.vendor: TOSHIBA
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.11-1ubuntu2
xserver.bootTime: Fri Nov 28 08:29:52 2014
xserver.configfil
[Touch-packages] [Bug 1397348] [NEW] GT215 crash PGRAPH TLB flush idle timeout fail
Public bug reported: I'm using ubuntu 14.04 LTS, as well as tried to load 15.04 dev build downloaded today. Display showing black and white rectangles with some color noise. When in switch to text i see errors from nouveau driver telling "PGRAPH TLB flush idle timeout fail". And i see it is happening in infinite loop. the only way to me to boot into X is to use "nomodeset". I dont want install nvidia proprietary drivers, since i will need to use Xen later and it won't work with them. Description:Ubuntu 14.04.1 LTS Release:14.04 xserver-xorg-video-nouveau: Installed: 1:1.0.10-1ubuntu2 Candidate: 1:1.0.10-1ubuntu2 Version table: *** 1:1.0.10-1ubuntu2 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 32.027037] init: plymouth-upstart-bridge main process ended, respawning [ 60.120737] audit_printk_skb: 132 callbacks suppressed [ 60.120740] type=1400 audit(1417187362.092:62): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2358 comm="apparmor_parser" [ 60.120747] type=1400 audit(1417187362.092:63): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2358 comm="apparmor_parser" [ 60.121191] type=1400 audit(1417187362.092:64): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2358 comm="apparmor_parser" Date: Fri Nov 28 18:11:23 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff50] InstallationDate: Installed on 2014-11-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Qosmio X505 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic root=UUID=fc1ea7a5-ebe4-412b-a55a-6e47c007c4ec ro nomodeset vga=795 quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.90 dmi.board.name: Qosmio X505 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.90:bd12/10/2010:svnTOSHIBA:pnQosmioX505:pvrPQX33U-01J00H:rvnTOSHIBA:rnQosmioX505:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Qosmio X505 dmi.product.version: PQX33U-01J00H dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Nov 28 18:08:52 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1397348 Title: GT215 crash PGRAPH TLB flush idle timeout fail Status in xorg package in Ubuntu: New Bug description: I'm using ubuntu 14.04 LTS, as well as tried to load 15.04 dev build downloaded today. Display showing black and white rectangles with some color noise. When in switch to text i see errors from nouveau driver telling "PGRAPH TLB flush idle timeout fail". And i see it is happening in infinite loop. the only way to me to boot into X is to use "nomodeset". I dont want install nvidia proprietary drivers, since i will need to use Xen later and it won't work with them. Description: Ubuntu 14.04.1 LTS
[Touch-packages] [Bug 1391779] [NEW] curl not build with metalink support
Public bug reported: The manpage for curl talks about having support for the --metalink flag but trying to use it in Ubuntu 14.04 fails with the following warning: Warning: --metalink option is ignored because the binary is built without the Warning: Metalink support. Can we get curl built with metalink support please? ** Affects: curl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1391779 Title: curl not build with metalink support Status in “curl” package in Ubuntu: New Bug description: The manpage for curl talks about having support for the --metalink flag but trying to use it in Ubuntu 14.04 fails with the following warning: Warning: --metalink option is ignored because the binary is built without the Warning: Metalink support. Can we get curl built with metalink support please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1391779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304534] Re: Backspace doesn't remove utf-8 multibyte characters
** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1304534 Title: Backspace doesn't remove utf-8 multibyte characters Status in “bash” package in Ubuntu: New Status in “terminal” package in Ubuntu: Confirmed Bug description: In Ubuntu 13.10 backspace in terminal only deletes one byte of multibyte character. For example: # cat > /tmp/test tыt # cat /tmp/test t�t # hexdump -C /tmp/test 74 d1 74 0a Where 'ы' is a russian letter (D18B in hexadecimal form). You may see that only second byte of multibyte character was deleted by backspace. I saw similar problem for ssh, but it's not the case. Here I'm not using ssh, just normal Terminal session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1304534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365664] Re: gdb source test suites are failing in Ubuntu14.10
Of course it's the actual section headers at that offset. Now the question is, should we fix bfd_from_remote_memory so it can read sections after the section headers assuming they are in memory. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1365664 Title: gdb source test suites are failing in Ubuntu14.10 Status in “gdb” package in Ubuntu: Confirmed Bug description: ---Problem Description--- gdb source test suites are failing in Ubuntu14.10 Machine Type = P8 ---Steps to Reproduce--- Install a P8 system with Power KVM and then install Ubuntu 14.10 guest. Then try to build and execute the gdb source test suites as below. root@ubuntu:~# apt-get source gdb root@ubuntu:~# cd gdb-7.8/ root@ubuntu:~/gdb-7.8# dpkg-buildpackage -b 2>&1 | tee gdblog === gdb Summary === # of expected passes25009 # of unexpected failures287 # of unexpected successes 2 # of expected failures 66 # of unknown successes 1 # of known failures 59 # of unresolved testcases 3 # of untested testcases 19 # of unsupported tests 100 ---uname output--- Linux ubuntu 3.16.0-11-generic #16-Ubuntu SMP Mon Aug 25 20:02:00 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux I've retested gdb from Ubuntu 14.04 (gdb-7.7-0ubuntu3.1) in the Ubuntu 14.10 VM provided by Pavaman and the number of failures curiously increased to 250 (in comparison to less than 140 on 14.04), which leads me to believe that there is something in the environment of Ubuntu 14.10 compromising gdb functionality in several testcases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1365664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365664] Re: gdb source test suites are failing in Ubuntu14.10
Still trawling through gdb, but the issue appears to be in bfd/elfcode.h, bfd_from_remote_memory: shdr_end = i_ehdr.e_shoff + i_ehdr.e_shnum * i_ehdr.e_shentsize; [17] .shstrtab STRTAB 001603 be 00 0 0 1 [18] .symtab SYMTAB 001bc8 000318 18 19 21 8 i_ehdr.e_shoff = 0x16c8. What is in the gap between 0x16c8 and 0x1bc8? Do we have a VDSO linker script issue? (entire elf segment listing is in comment #9) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1365664 Title: gdb source test suites are failing in Ubuntu14.10 Status in “gdb” package in Ubuntu: Confirmed Bug description: ---Problem Description--- gdb source test suites are failing in Ubuntu14.10 Machine Type = P8 ---Steps to Reproduce--- Install a P8 system with Power KVM and then install Ubuntu 14.10 guest. Then try to build and execute the gdb source test suites as below. root@ubuntu:~# apt-get source gdb root@ubuntu:~# cd gdb-7.8/ root@ubuntu:~/gdb-7.8# dpkg-buildpackage -b 2>&1 | tee gdblog === gdb Summary === # of expected passes25009 # of unexpected failures287 # of unexpected successes 2 # of expected failures 66 # of unknown successes 1 # of known failures 59 # of unresolved testcases 3 # of untested testcases 19 # of unsupported tests 100 ---uname output--- Linux ubuntu 3.16.0-11-generic #16-Ubuntu SMP Mon Aug 25 20:02:00 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux I've retested gdb from Ubuntu 14.04 (gdb-7.7-0ubuntu3.1) in the Ubuntu 14.10 VM provided by Pavaman and the number of failures curiously increased to 250 (in comparison to less than 140 on 14.04), which leads me to believe that there is something in the environment of Ubuntu 14.10 compromising gdb functionality in several testcases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1365664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365664] Re: gdb source test suites are failing in Ubuntu14.10
I see what is going on, but don't know how to fix it yet.
Gdb must be checking for program headers that are marked load or
segments that are marked allocate (not exactly sure what yet). The
.symtab and .strtab are not, because normally they are not loaded into
memory.
The problem is bfd_elf_get_elf_syms tries to bfd_seek too far, and
fails. The VDSO looks like:
[Nr] Name TypeAddress OffSize ES Flg Lk
Inf Al
[ 0] NULL 00 00 00
0 0 0
[ 1] .hash HASH0120 000120 4c 04 A
2 0 8
[ 2] .dynsym DYNSYM 0170 000170 000150 18 A
3 2 8
[ 3] .dynstr STRTAB 02c0 0002c0 00010d 00 A
0 0 1
[ 4] .gnu.version VERSYM 03ce 0003ce 1c 02 A
2 0 2
[ 5] .gnu.version_dVERDEF 03f0 0003f0 38 00 A
3 2 8
[ 6] .note NOTE0428 000428 3c 00 A
0 0 4
[ 7] .text PROGBITS0470 000470 000324 00 AX
0 0 8
[ 8] .dynamic DYNAMIC 0798 000798 000100 10 WA
3 0 8
[ 9] .eh_frame_hdr PROGBITS0898 000898 6c 00 A
0 0 4
[10] .eh_frame PROGBITS0908 000908 000538 00 A
0 0 8
[11] .got PROGBITS0e40 000e40 08 08 WA
0 0 8
[12] .debug_arangesPROGBITS 000e50 f0 00
0 0 16
[13] .debug_info PROGBITS 000f40 00034c 00
0 0 1
[14] .debug_abbrev PROGBITS 00128c 64 00
0 0 1
[15] .debug_line PROGBITS 0012f0 000313 00
0 0 1
[16] .rela.dyn RELA0e40 000e40 00 18 A
2 0 8
[17] .shstrtab STRTAB 001603 be 00
0 0 1
[18] .symtab SYMTAB 001bc8 000318 18
19 21 8
[19] .strtab STRTAB 001ee0 000127 00
0 0 1
strace output:
open("/proc/19509/mem", O_RDONLY|O_CLOEXEC) = 10
pread64(10,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\25\0\1\0\0\0p\4\0\0\0\0\0\0"..., 64,
70367535824896) = 64
close(10) = 0
open("/proc/19509/mem", O_RDONLY|O_CLOEXEC) = 10
pread64(10,
"\1\0\0\0\5\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 224,
70367535824960) = 224
close(10) = 0
open("/proc/19509/mem", O_RDONLY|O_CLOEXEC) = 10
pread64(10,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\25\0\1\0\0\0p\4\0\0\0\0\0\0"..., 7112,
70367535824896) = 7112
close(10) = 0
We read up to 7112 (0x1bc8), right up to before the symtab. Not sure it
reads to there and not the limit of the program load header or all
section headers marked allocate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1365664
Title:
gdb source test suites are failing in Ubuntu14.10
Status in “gdb” package in Ubuntu:
Confirmed
Bug description:
---Problem Description---
gdb source test suites are failing in Ubuntu14.10
Machine Type = P8
---Steps to Reproduce---
Install a P8 system with Power KVM and then install Ubuntu 14.10 guest.
Then try to build and execute the gdb source test suites as below.
root@ubuntu:~# apt-get source gdb
root@ubuntu:~# cd gdb-7.8/
root@ubuntu:~/gdb-7.8# dpkg-buildpackage -b 2>&1 | tee gdblog
=== gdb Summary ===
# of expected passes25009
# of unexpected failures287
# of unexpected successes 2
# of expected failures 66
# of unknown successes 1
# of known failures 59
# of unresolved testcases 3
# of untested testcases 19
# of unsupported tests 100
---uname output---
Linux ubuntu 3.16.0-11-generic #16-Ubuntu SMP Mon Aug 25 20:02:00 UTC 2014
ppc64le ppc64le ppc64le GNU/Linux
I've retested gdb from Ubuntu 14.04 (gdb-7.7-0ubuntu3.1) in the Ubuntu 14.10
VM provided by Pavaman and the number of failures curiously increased to 250
(in comparison to less than 140 on 14.04), which leads me to believe that there
is something in the environment of Ubuntu 14.10 compromising gdb functionality
in several testcases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1365664/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365664] Re: gdb source test suites are failing in Ubuntu14.10
(gdb) break /home/ubuntu/binutils-gdb/gdb/testsuite/gdb.base/annota1.c:28
Breakpoint 1 at 0x16e4: file
/home/ubuntu/binutils-gdb/gdb/testsuite/gdb.base/annota1.c, line 28.
(gdb) run
Starting program: /tmp/foo
Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated
Breakpoint 1, main () at
/home/ubuntu/binutils-gdb/gdb/testsuite/gdb.base/annota1.c:28
28int my_array[3] = { 1, 2, 3 }; /* break main */
I wonder if the gdb complaint about the kernel VDSO is causing the test to
fail. The warning is almost certainly a result of
this kernel patch:
commit 24b659a13866b935eca72748ce725279bd3c4466
Author: Anton Blanchard
Date: Wed Feb 12 17:18:50 2014 +1100
powerpc: Use unstripped VDSO image for more accurate profiling data
We are seeing a lot of hits in the VDSO that are not resolved by perf.
A while(1) gettimeofday() loop shows the issue:
27.64% [vdso] [.] 0x060c
22.57% [vdso] [.] 0x0628
16.88% [vdso] [.] 0x0610
12.39% [vdso] [.] __kernel_gettimeofday
6.09% [vdso] [.] 0x05f8
3.58% test[.] 0037.plt_call.gettimeofday@@GLIBC_2.18
2.94% [vdso] [.] __kernel_datapage_offset
2.90% test[.] main
We are using a stripped VDSO image which means only symbols with
relocation info can be resolved. There isn't a lot of point to
stripping the VDSO, the debug info is only about 1kB:
4680 arch/powerpc/kernel/vdso64/vdso64.so
5815 arch/powerpc/kernel/vdso64/vdso64.so.dbg
By using the unstripped image, we can resolve all the symbols in the
VDSO and the perf profile data looks much better:
76.53% [vdso] [.] __do_get_tspec
12.20% [vdso] [.] __kernel_gettimeofday
5.05% [vdso] [.] __get_datapage
3.20% test[.] main
2.92% test[.] 0037.plt_call.gettimeofday@@GLIBC_2.18
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1365664
Title:
gdb source test suites are failing in Ubuntu14.10
Status in “gdb” package in Ubuntu:
Confirmed
Bug description:
---Problem Description---
gdb source test suites are failing in Ubuntu14.10
Machine Type = P8
---Steps to Reproduce---
Install a P8 system with Power KVM and then install Ubuntu 14.10 guest.
Then try to build and execute the gdb source test suites as below.
root@ubuntu:~# apt-get source gdb
root@ubuntu:~# cd gdb-7.8/
root@ubuntu:~/gdb-7.8# dpkg-buildpackage -b 2>&1 | tee gdblog
=== gdb Summary ===
# of expected passes25009
# of unexpected failures287
# of unexpected successes 2
# of expected failures 66
# of unknown successes 1
# of known failures 59
# of unresolved testcases 3
# of untested testcases 19
# of unsupported tests 100
---uname output---
Linux ubuntu 3.16.0-11-generic #16-Ubuntu SMP Mon Aug 25 20:02:00 UTC 2014
ppc64le ppc64le ppc64le GNU/Linux
I've retested gdb from Ubuntu 14.04 (gdb-7.7-0ubuntu3.1) in the Ubuntu 14.10
VM provided by Pavaman and the number of failures curiously increased to 250
(in comparison to less than 140 on 14.04), which leads me to believe that there
is something in the environment of Ubuntu 14.10 compromising gdb functionality
in several testcases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1365664/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
